Modular Open Systems Architecture/Approaches

1. Modular Open Systems Architecture/Approaches Stephen J. Falcone Director of Engineering for Battle Management Directorate 6 February 2018 66ABG/PA Clearance Number: 66 ABG-2018-0011 DISTRIBUTION A: Approved for public release: Distribution Unlimited

2. Agenda • What is MOSA? • Definitions • Why the shift from Architecture to Approaches? • Benefits of MOSA • Is Modular and Open synonymous? • Are we done? Nirvana Achieved???

3. FY17 NDAA Sec 805 ‘‘(1) The term ‘modular open system approach’ means, with respect to a major defense acquisition program, an integrated business and technical strategy that— ‘‘(A) employs a modular design that uses major system interfaces between a major system platform and a major system component, between major system components, or between major system platforms; ‘‘(B) is subjected to verification to ensure major system interfaces comply with, if available and suitable, widely supported and consensus-based standards; ‘‘(C) uses a system architecture that allows severable major system components at the appropriate level to be incrementally added, removed, or replaced throughout the life cycle of a major system platform to afford opportunities for enhanced competition and innovation while yielding— ‘‘(i) significant cost savings or avoidance; ‘ ‘(ii) schedule reduction; ‘‘(iii) opportunities for technical upgrades; ‘‘(iv) increased interoperability, including system of systems interoperability and mission integration; or ‘‘(v) other benefits during the sustainment phase of a major weapon system; and ‘‘(D) complies with the technical data rights set forth in section 2320 of this title.

4. ODASD Systems and Engineering • DoD seeks five primary benefits of MOSA: • Enhance competition – open architecture with severable modules, allowing components to be openly competed. • Facilitate technology refresh – delivery of new capabilities or replacement technology without changing all components in the entire system. • Incorporate innovation – operational flexibility to configure and reconfigure available assets to meet rapidly changing operational requirements. • Enable cost savings/cost avoidance – reuse of technology, modules, and/or components from any supplier across the acquisition life cycle. • Improve interoperability – severable software and hardware modules to be changed independently.

5. Instance Implementation ArchitectureDefinitions InstanceDesign Instance Architecture HouseSpec ShedSpec FactorySpec Reference Architecture Standards National ElectricCode Slide provided by General Dynamics Mission Systems (GDMS); requests for further use of slide should be directed to GDMS

6. Government Reference Architecture (GRA) Communications Radar Distributed REX Antenna Radar to OMS Adapter Mission Intercoms Filtering and Antennas Mode Software Sensor Manager Middleware Software Radio Terminals Cryptographic Storage & Loading Operating System Software Processor Hardware Interface(s) Communications Backplane Avionics Service Bus (ASB)/Critical Abstraction Layer (CAL) (as specified by OMS) Data Services Planning and Execution Core Services Exploitation OMS Isolator Support Equipment/ Spares Mission Planning Services Flight Deck Mods SIL Training Systems Presentation Platform Mods Off-the-Shelf Ground Support Systems Aircraft Missionized System

7. Standards are good aren’t they? • widely supported and consensus-based standards; • VHS versus Beta • Internet Protocols – TCP/IP versus X.25

8. OSA Radar Architecture • Segregate front and back ends to facilitate CPU upgrades • Base software on radar open systems specification • Define open interfaces early to enable competitive refresh Antenna Distributed REX Radar Adapter Service Exciter AESA Mode Software C AESA Receivers Sensor Manager D Middleware Software A B Operating System Software Front End Processor Hardware Signal Processor Hardware Control Processor Hardware AESA Exciter Key Interfaces AESA Receivers Communications Backplane Front End Back End

9. DOD MOSA Working Group Survey (AF PEOs) Where do you believe your program/programs stand with respect to implementing modularity and OSA regarding both hardware andsoftware? 14% 16% 4% Fully Implementing Partial but substantial Limited efforts Not possible Other 33% 33%

10. DOD MOSA Working Group Survey (AF PEOs) 13% 25% For new development orboth 11% 3% 26% Fully Implementing Partial but substantial Limited efforts Not possible 17% Other 43% If some new development, then nearly 70% fully or substantially implementing modularity or OSA intiatives 43%

11. DOD MOSA Working Group Survey (AF PEOs) What are the challenges/barriers to implementing more modular or open system architectures ? 15% 21% 15% 21% Lack ref arch or tools Lack Govt skill sets IP/industry resistance Not a priority Other 15% 15% 15% 34% 34% Slightly more than half of respondents cited IP/industry resistance as one of their challenges/barriers

12. Please list any widely accepted reference architectures or common interface standards you’re currently using or plan to use • DOD Open Systems Architecture Contract Guidebook forPMs • IPv4 and IPv6 addressing and IPSec—Ethernet, serial, and RS-422interfaces • N-Layer Architecture Layer and OSI referencemodel • ANSI, ARINC, IEEE/EIA, and ISOstandards • MIL-STD-1553 , RS-XXX, ARINC, Ethernet,etc • Client Server & N-Tier—newer systems implement Open Systems Interconnection model for networkarchitectures • IEEE Std 1516 series High Level Architectures(HLA) • IEEE STD 1278 std for Distributed Interactive SimulationSeries • SIS-REF 010 Enumerations for SimulationInteroperability • SIS-REF 010.1 Operations Manual for DistributedInteractive • ICD-GPS-059C GPS User Equipment ICD for MIL-STD -1552 Mulit BusInterface • LAN eXtentions for Instrumentation (LXI) – IEEE 1588, VXI,PXI • Automatic Test Markup Language (ATML) – IEEE 1636, IEEE1671 • Virtual Instrument Software Architecture(VISA) • Oracle RAC Joint METOC Broker Language(JMBL) • KML,XML,ApacheCommons,ApacheAxisArcGis • JC2 Objective Architecture, NESI, and NCES (akaGES) • IC ISM standard for XML security classificationmarkup • OMS, COARPS, NATO STANAGs, MIL-STDS, andCDL • SEIWG-ICD-0100 and XML1.0 • 2nd Gen DVB-S/2, HTTP, HTTPS, TCP/IP, SFTP, UDIP, andMPEG-4 • ANSI/IEEE Std1471-2000 • FACE ReferenceArchitecture, CORBA 3.3. IEEE 1003.1-2001 for POSIX(R) • MIL-HDBK1553A/MIL-STD-1553B • ANSI X.366 ADCCP—Advanced Data Communications ControlProcedures • Spacewire • UAS C2 Standard Initiative(UCI) • Entire list would be several more pages … answers depend ondomain

13. DOD MOSA Working Group Survey (AF PEOs) Do you have the tools you need to assess where your system/systems stand regarding modularity or OSA? (if yes, please list what assessment tools you’re using) 3% 2%1% 25% Yes No NA Limited I don’t know 69% Clear need for assessment methodology andtools

14. OSA Guidance – Are we done? • What it does well: • Provides RFP language • What else is needed • Government Reference Architecture • Government led Integration/Environment • Assessments • Green Field versus Brown Field Approach • What about Agile Dev/OPS? It’s all about integration

15. Government Reference Architecture (GRA) Communications Radar Avionics Service Bus (ASB)/Critical Abstraction Layer (CAL) (as specified by OMS) OMS Isolator Battle Management Ground Support Systems Aircraft Missionized System

16. Use of Adaptors • OMS architecture standards boost competition and simplify sustainment • Risk reduction efforts confirmed OMS suitability • Software system spec’d for Tier 3 (highest) compliance Government Reference Architecture (GRA) Air vehicle Subsystem Radar Subsystem Comms Subsystem OMS Open Computing Environment (OCE) Isolation Layer OMS Adaptor Service OMS Adaptor Service OMS Gateway OMS Messages OMS Messages OMS Messages OMS Messages OMS Messages OMS Critical Abstraction Layer (CAL) OMS Avionics Service Bus (ASB)

17. Migration to an Open Architecture (Brown to Green) Cost Avoidance Opportunities Re-Hosted Apps running on Common Hardware x86 (Not – Virtualized) Re-Hosted Apps on Common Hardware (Virtualized) MAAS (GEOINT) AIMES (GEOINT) GWE (GEOINT) NSANet (VM/VPN via JWICS) ACES HY GALE DotMatrix Web Based - METRICS - Intel Book (DART) - LINKS (DART) - MIST (DART) - DataMinr - JEMA - NSA Pulse - C3PED New/Re-Hosted Apps Interfacing with PaaS GSEG+, DGETS, MTA (SEAM) SKS, Dragonfly (RESA) Federated Search App (DDF) New/Re-Hosted Apps Integrated with PaaS Closed Environment (Pre OA DCGS) Custom Hardware | Custom Work Stations | Custom Services Accredited Applications Decreasing Testing Timeline Cloud Orchestration (Pivotal Cloud Foundry) SOA (DDF/RESA) Accredited PaaS Enterprise Services (IAAD, Auditing, DNS, NTP, Metrics, CND, Asset Mgt, Puppet) Common Secured Operating Systems (RedHat 6.6, Microsoft Server 2012, Solaris 10) Virtualization Layer (VMware 6.x/Docker) Accredited IaaS Hardware (EMC Isilon, Dell, Cisco)

18. Risk Management in Agile/DevOPS Legacy AOC Waterfall Delivery Build/Deploy Code Test Design Manual Deploy Manual Test Modernized App Agile/“Scrumfall” Delivery Build/Deploy Design Code Test Test Test Code Code Manual Deploy Manual Test AOC DevOps Delivery Goal • Pipeline • Continuous Feedback • Continuous Integration • Continuous Delivery Continuous Automated Testing / IA Design Today’s Focus