Slide1: Boeing, Future Combat Systems, and The OMG Dave Sharp Chief Architect– FCS System Of Systems Software 28 April 2004 This briefing is subject to the following limitations: Where marked GOVERNMENT PURPOSE RIGHTS: The Government is granted Government Purpose Rights to this Data or Software. Use, duplication, or disclosure is subject to the restrictions as stated in Agreement DAAE07-03-9-F001 between The Boeing Company and the Government.


Select Boeing OMG Standards Use: Select Boeing OMG Standards Use DCAC/MRM (Seattle) Leading deployment of CORBA in late 1990s Integrating hundreds of new and legacy systems in the commercial aircraft design and manufacturing chain Software-based Communications (Anaheim) Joint Tactical Radio System (JTRS) Cluster 1 prime contractor Real Time Embedded Systems (St. Louis, Seattle, SoCal…) Boeing Bold Stroke Avionics Affordability Initiative Real Time CORBA Heavy research funder/early adopter of CORBA for real-time applications First company to fly CORBA in mission critical embedded avionics (OS-JTF OSAT-II project, 1998) Annual Real-time Embedded Workshops Active participant every year since inception In 2003, over half of the technical presentations were related to research associated with Boeing Continuing involvement in RT CORBA, CORBA Component Model, and related research as part of DARPA, AFRL, USN, and OS-JTF research programs Bold Stroke


Boeing OMG Participation: Boeing OMG Participation Platform Technology Committee Task Forces Analysis & Design Middleware and Related Services Real-time, Embedded and Specialized Systems Special Interest Groups Model Integrated Computing Weapon Systems Technical Architecture Working Group (WSTAWG) Domain Technology Committee Task Forces C4I Software-based Communications Special Interest Groups Systems Engineering


Future Combat Systems: Future Combat Systems Use or disclosure of data contained on this page is subject to restrictions on title page.


Future Combat Systems Architecture Overview: Future Combat Systems Architecture Overview Logical Database Information Layer “UA Infosphere” Interoperable export WIN-T UE/HQ JTRS Hierarchical Ad-Hoc Network Data Images Voice Video Planning Fires & Effects Information Ops RSTA C4ISR Mgmt Combat Support Situation Awareness Execution Intelligence Airspace C2 Training & Rehearsal Nontactical Support Warfighter Interface Vetronics Common Vehicle Subsystems Battle Command EO/IR EO/IR SAR/MTI UGS Reachback HHQ Joint Common Database XX stubnet O&O V1.0 RT Synchronization Information Domain Platform Systems Domain Network-Centric Warfighting Domain Interoperability Domain FIOP (Approved for Public Release, Distribution Unlimited) Open Software Architecture Use or disclosure of data contained on this page is subject to restrictions on title page.


FCS Software and SOSCOE: Crew Stations  Supportability  Integration Software Network  Combat Support Systems Integrated Electronic Tech Manuals (IETM) Brigade Logistics Commander Planner Trainers Institutional Software (HSOC) Non Platform Training Non Platform Sustainment Battle Command Mission Planning And Preparation Situational Understanding Logistics Decision Support System (LDSS) Embedded Training  C2 Networked Communications Warfighter Machine Interface Manned Ground Vehicle Autonomous Navigation System (ANS) Unmanned Aerial Vehicles Ground Sensors Communications Unmanned Ground Vehicle Modeling & Simulation PS-MRS DAVS (HSOC) Forward Support Base Support Equipment SOS Common Operating Environment SOSCOE FCS Software and SOSCOE Use or disclosure of data contained on this page is subject to restrictions on title page.


Slide7: Eliminate Software stovepipes and reliance on special purpose systems Common C2 software systems for all warfighters Echelon- and mission-appropriate functionality conditioned by C2 policies Minimum number of special purpose systems for specialized functions Develop an evolving system based on open system architectures and standards based interfaces Use of legacy codes within a modular software architecture Minimum use of legacy systems Distribute functionality to the lowest level possible by resource allocation Dynamic, automatic allocation of resources based on Commander’s Intent, Priorities, and Rule Sets (Orders). Rapid response of support to units (Fires, etc.) New codes and capabilities to enable core NCW functionality Automatic allocation Dynamic adjustment Commander sets thresholds and parameters SOSCOE: Foundation For System of Systems Integration Use or disclosure of data contained on this page is subject to restrictions on title page.


SOSCOE – FCS Scope: SOSCOE – FCS Scope SOSCOE Network Foundation Operating System Domain Applications SOSCOE Network Foundation Operating System Domain Applications C4ISR Sustainment Training Manned Ground Vehicles Unmanned Air Vehicles Unmanned Ground Vehicles Soldier Systems Supports real time/non real time, safety critical/non safety critical, and large/small footprint systems Use or disclosure of data contained on this page is subject to restrictions on title page.


Active FCS OMG Standards Usage: Active FCS OMG Standards Usage Weapon Systems Technical Architecture Working Group (WSTAWG) Operating Environment (OE) API Data Distribution Service (DDS) Unified Modeling Language ODBC / JDBC Model Driven Architecture (MDA) concepts Use or disclosure of data contained on this page is subject to restrictions on title page.


Missions Modeled As“Task Integration Networks”: Missions Modeled As “Task Integration Networks” Task Integration Network maps knowledge of mission tasks and context Task Network COP Use or disclosure of data contained on this page is subject to restrictions on title page.


TIN Execution Engine (TINEX)Runtime Diagram: TIN Execution Engine (TINEX) Runtime Diagram Service A Instance TINEX Manager TIN Manager TINEX TDD A TIN Manager TIN Manager TM Sends: Commands Control Data TM Receives: Status Data Instantiates/Connects TDD B TDD TM Sends: Commands Control Data TM Receives: Status Data TM Sends: Commands Control Data TM Receives: Status Data Service A Instance Service B Instance Service B Instance Service C Instance Service B Instance Service C Instance TDD A TDD B Instantiates/Connects Instantiates/Connects Could be the same or different instances Use or disclosure of data contained on this page is subject to restrictions on title page.


Conclusion: Conclusion Boeing Is Glad To Welcome The OMG To The Gateway City OMG Standards Provide Underpinnings For A Number Of Large-Scale Boeing Programs Many Challenges Remain In Establishing The Technology And Standardization Baseline Necessary For Increasing Complex Boeing Systems