SOSCOE: Custom, COTS, and OSS & An Architecture for Market-Driven Orchestration Al Williams, The Boeing Company

1. SOSCOE System of Systems Common Operating Environment Overview Presented to NCW 2010 Paul Schoen SOSCOE Executive Director The Boeing Company January 25, 2010

9. Information Assurance has been integrated into the base fabric of user and application interactions - Controlled Access-Controller Server Application Untrusted Client Application RMI API Class ScAuthorizationAgent Comms SOSCOE Authorization Server 3. For the specified RBAC session and action create a signed authorization which includes the authorization indicator, of the authorization server who signed the authorization. and signature Information Assurance is built in to the System from the Start RBAC Database 1. Client calls RMI API 7. If access is granted call implementation code. Comms ScAuthorizationEvaluator Implementation Layer 2. Request signed authorization 4. Signed authorization 5. Send signed authorization 6. Verify signature on authorization, validity of the nonce, and the check authorization indicator before permitting access.

12. SOSCOE Provides Full Interoperability with Existing Systems SOSCOE interoperability services allow for incremental updates to match external systems “capability blocking strategy”

13. SOSCOE provides interoperability between NCES/GES Web Services and the Tactical Edge BCTM Service BCTM Solider Accessing a GIG Service

15. Standard-based APIs Allow for Easy Migration Over Time and Isolate Application Services SW from the HW and OS Native OS Native OS Reuse Model API Integration Code Reuse Code New Code Model API SOSCOE Implementation Software Buy Model API Integration Code COTS/GOTS SOSCOE Services SOSCOE Services SOSCOE Native OS Battle Command Applications By basing the SOSCOE APIs on standards (DISR, WSTAWG, OMG, etc.), the Battle Command Services are isolated from any dependence on the computer HW, OS and COTS products. This allows applications to take advantage of newer HW, OS and COTS with Minimal impact and cost

16. “TIERS” of Use of SOSCOE - An Investment Strategy in Reuse Tier 0 Interfacing Tier 1 Net-Centric Exchange Tier 2 Platform Integration Tier 3 Int. BC Net-Centric Threshold There is no impact to the external system to interoperate with BCTM but communication is limited to existing message sets and NR KPP not satisfied Provides complete and seamless interoperability between systems, allows for the complete leverage of BCTM Battle Command Applications at the component level. External systems “adopt” enough SOSCOE services to discover, be discovered, and exchange Data in a trustable manner, BUT no ability to participate as a full member of the BCTM COI with respect to Application Services External systems “port” their systems on top of SOSCOE but do not decompose the software into “TIN-ABLE Components”. External systems can exploit BCTM but BCTM can not fully exploit external system beyond Data External systems implemented using WEB Services (SOAP, WSDL, HTTP, etc) Interact with BCTM via the BCTM “Edge Node”. Limited to high bandwidth connections and “subset” of data exposed Integration Goal Required SOSCOE Enabling BCTM Capabilities Supported / Req Transport External Capabilities Integrated into Battle Command BC Infrastructure Components (TIN, Policy, …) WMI Compliance Integrated on Platform COE Components ICS OS Compliant Health to PSMRS Co-exist with WMI Integrated into Tactical NCIE Tactical Service-based Components Common Transient Data model Topics NMS >=JTRS SRW/WNW Waveforms Integrated into Strategic NCIE Strategic SOA Components COI-coordinated web service interfaces >= WIN-T/JNN Comms GIG-BE NCES Discovery Legacy Interoperability NONE SOSCOE Interop Legacy Waveforms (EPLRS, SINCGARS, …) Native formatted message interface standards