PEO Reference Architecture Description Document (RADD) "Skinny"

PEO Reference Architecture DescriptionDocument (RADD) “Skinny”Matt SipeDirector, MOSA Transformation OfficeDISTRIBUTION STATEMENT A: Approvedfor Public Release; Distribution is UnlimitedThe appearance of commercial entitiesdoes not imply Army or Department ofDefense endorsement.September 2021

UNCLASSIFIEDRADD Executive Summary and OutlineThe PEO Aviation Reference Architecture (RA) will guide and constrain the development of Army Aviation assets, systems,and components. This PEO Aviation Reference Architecture Description Document (RADD) is a readable description of theRA which is being developed and maintained within the Army Aviation Enterprise Architecture Framework (EAF) modelingenvironment. Concepts were derived from DoD “Reference Architecture Description” document, dated June 2010.SectionSubsection1.0 Introduction1.1 Strategic Purpose1.2 Background1.3 Approach1.4 Stakeholders2.0 Document Structure2.1 Relationship to Modeling Environment2.2 Architectural Model Management3.0 Principles3.1 Architecture Context3.2 Requirements Traceability4.0 Open System Architecture Strategy4.1 Existing Standards – Technical Positions4.2 PEO Reference Architecture Key Interfaces4.3 Enduring Fleet Open Systems Architecture Strategy5.0 Major System Components (MSCs)5.1 MSC Priorities5.2 MSC Descriptions5.3 Key InterfacesUNCLASSIFIED2

UNCLASSIFIEDIntroduction Strategic Purpose Guide and constrain the development of Army Aviation SystemsDefine boundaries to promote reuse across platformsInform ongoing development, maintenance, and operations across thefleet in an operational environment MOSA Objectives Improved Lifecycle AffordabilityIncreased ReadinessEnhanced CapabilitiesReduced Schedule PressureReduced Supply Chain Risk Approach Establish a comprehensive Enterprise Architecture Framework Functional decomposition traceable back to common capabilitiesAll Major System Components identified to inform Key InterfacesKey Interfaces used to determine Open StandardsGovernance to constrain future implementations to avoid duplication of effortsUNCLASSIFIED3

UNCLASSIFIEDStakeholders CongressOperational UsersRequirements AuthoritiesASA (ALT)Program Executive OfficeAirworthiness AuthoritiesProgram OfficesArmy Lab Facilities and StaffOriginal Equipment ManufacturersMajor Mission System IntegratorsComponent SuppliersUNCLASSIFIED4

UNCLASSIFIEDModeling and Architectures Modeling Collaborative Digital Environment managedby PEO AviationArchitectural Model Management- Model-based content aligned to MBSE- Library of common resources- Communication of key concepts, requirements,and resources- Consistency of architecture development Architectures Reference Architecture RelationshipsArchitecture LevelsRequirements TraceabilityUNCLASSIFIED5

UNCLASSIFIEDOpen System Architecture Strategy FACE and HOST serve as the foundational open system standards thatwill apply across the Army Aviation Enterprise portfolio of systems Additional interface standards will be prescribed based on KeyInterfaces as developed through the ACWG and modeled in the EAF Architectural elements with corresponding relevantstandards are shown in the above tableArchitecture Pattern MechanismsArchitectural Element HOST [Foundational Standard]CMOSS Umbrella of Applicable Standardso OMSo VICTORYo SOSAPhysical Data Bus Interfaces FACE [Foundational Standard]ARINC 661ARINC 653CMOSS FACE DSDM (Enterprise level DSDM) AV/MSA functionJCAJCSFL Physical Networking StandardsMessaging StandardsInteroperability As defined in the EAF EAF Model Element GuideEAF Pattern DescriptionsArchitecture Requirements HardwareSoftwareData DescriptionFunctionDigital BackboneKey and Critical NCLASSIFIED6

UNCLASSIFIEDMajor System Components (MSCs)MSC An MSC is a high-level subsystem orassembly, including hardware,software, or an integrated assemblyof both that can be mounted orinstalled on an MSP (Major SystemPlatform) through well-definedinterfaces (i.e., Key Interfaces, MajorSystem Interfaces). Additionalinterface standards will beprescribed based on Key Interfacesas developed through the ACWG andmodeled in the EAF. The MSCs identified within thisdocument serve as the initial PEOAVN Enterprise prioritization forMSCs common to multiple enduringand future platforms.DescriptionAviation Mission ComputingEnvironment (AMCE)Configurable processing environment supporting open graphics, transport services, software loading,decoupling from board support with means to produce display symbology and Common OperatingPicture informationLink 16Solution that enables host aircraft to join the tactical Link 16 networkAirborne Radio Control Manager(ARCM)Common voice and digital communicationsNavigationIntegrated implementation supporting TACAN, VOR/ILS, EGI, IFF, and ADS-BAircraft Survivability Equipment(ASE)Common A-Kit and ASE subsystem architecture applicable across Army Aviation programsDynamic Airspace and MissionPlanning Environment (DAMPE)Combination of legacy AMPS and TAIS functionalityMission Planning Data LoaderCommon capability to load mission planning information applicable across Army Aviation programsCommon Pilot Vehicle Interface (PVI)Common “look and feel” implemented to ARINC-661 requirementsDegraded Visual Environment (DVE)Architecture consisting of sensors and software supporting operations in DVEPower DistributionSolution that employs Electronic Circuit Breakers and handles power management, generators,conversion electronics, batteries, and supplemental power unitsUnmanned Vehicle ControlControls to command Air Launched Effects and other Army Unmanned Air SystemsUNCLASSIFIED7

UNCLASSIFIEDKey Interfaces Under Consideration Key interfaces are defined atdifferent levels of abstractionand implementation. Interfacescan be defined as architecturepatterns. Key interfaces are compositionalin nature. An implementationmay realize multiple interfaces.From a definition perspective, itmay be adequate to specify onlya part of an interface as a keyinterface. Key interfaces are applied to aspecific platform or componentdevelopment as requirements. As part of the key interfacedetermination, requirements arecreated that describe the keyinterface and are levied on aplatform or components.Aircraft Systems Monitoring ServiceInterfaceMission Data Management ServiceInterfaceSystem Time Service InterfaceWireless Communications InterfaceFlight Data Recording InterfaceEvent Audit Service InterfaceNavigation Data Management ServiceInterfaceTactical Data Link : ARC-220Aerial Refueling InterfaceGeoInt TargetingBlue Force Tracker InterfaceNetwork & Transport ProtocolsTactical Data Link : BFTAir-Ground Radio CommunicationHazard Information Service InterfaceData Logging Service InterfaceNetwork Configuration & DiscoveryTactical Data Link : Global InformationGrid connectionArchitectural InterfacesImageryDataload Interface Analysis ContextNetwork QoSTactical Data Link : LINK16Areas Of Interest Service InterfaceMap Data Management ServiceInterfaceDigital Signature Service InterfaceNetwork Route ManagementTactical Data Link : MUOSAudioMotion ImageryEncryption Decryption ServiceInterfaceOperational Mode ManagementService InterfaceTactical Data Link : SATURNCharts & MapsNavaid TuningExternal Power InterfacePosition Data Service InterfaceTactical Data Link : SINCGARSCivil DatalinkObstacle Information ServiceInterfaceFuel Port InterfacePower Control InterfaceTerrain Data Management ServiceInterfaceCivil SurveillancePlatform Configuration Data ServiceInterfaceGraphical User Interface ServicesSatellite Navigation Interface AnalysisContextUAS Control System InterfaceCommon Operating Picture ServiceInterfacePlatform Performance Data ServiceInterfaceIdentify Friend or FoeStores InterfaceUser (Physical/Cognitive) InterfaceAnalysis ContextData Storage Service InterfaceStores Management ServiceInternal Power InterfaceSystem Capability Registry ServiceInterfaceUser Authentication Service InterfaceElements Of Interest Service InterfaceThreat Information Service InterfaceKey Management Service InterfaceSystem Health Management ServiceInterfaceVoice over IP communicationElevation & Obstacle DataTrack Management Service InterfaceUNCLASSIFIED8

UNCLASSIFIEDRADD Path Forward Will be the result of Reference Architecture (RA)model-based content Serves as authoritative source of information thatwill guide and constrain the development of PEOAVN “solution” (i.e. System) architectures byproviding:-Strategic Purpose (Authoritative Source)Principles (Fundamental Statements)Technical Positions (Policy, Standards, Reuse Library)Patterns (Proven solutions to common problems)Vocabulary (Semantic classification and meaning of Terms andDefinitions) Will contain multiple RA’s that are subject areaspecific (i.e. Army’s APNT RA) that provide afocused or a different emphasisUNCLASSIFIEDImplementation Guidance: contains statutory (legal), regulatory, and policy along withclarifications of Commander’s Intent for a portfolio of systemsNDAA (2017 & 2021)OSD MOSWG GuidanceASA(ALT) MOSA ImplementationGuidePEO Aviation MOSA ImplementationGuideReference Architecture: Guides and constrains solution architectures, containing: purpose,principles, technical positions, patterns, and vocabularyDoD ReferenceArchitecture Instruction(5 key topics)Patterns for TechStandard Guidance(FACE, HOST, SOSA,VICTORY, etc.)Framework Guidance(DoDAF, UAF, customframeworks, etc.)MBSE Profiles, modellibrary guidance, styleguides, etc.Enterprise StakeholderConcerns andDocumentationTemplatesEnterprise Core AssetLibrary (Major SystemComponents (MSC),Tools, and Functions)Solution (System) Architecture: specific to a system, subsystem, or MSC of interest, containingthe fundamental elements with their properties and relationships in context of an environmentPlatform specificrequirements, includingperformance, structure,behavior, and qualitiesConceptual and Logicalmodels of the modularsolution (to inform designconstraints)Architecture Rationale formeeting defined anddocumented StakeholderConcerns for the solutionTechnical PerformanceAllocated functionalMeasures (TPMs), including requirements traced to thespecific standards applied at Enterprise MSCs and defineda module levelplatform-specific MSCs9

UNCLASSIFIEDClosing Comments and QuestionsUNCLASSIFIED10

and components. This PEO Aviation Reference Architecture Description Document (RADD) is a readable description of the RA which is being developed and maintained within the Army Aviation Enterprise Architecture Framework (EAF) modeling environment. Concepts were derived from DoD "ReferenceArchitecture Description" document, dated June 2010.