Bob Marcus robert.marcus@sri

1. NCOIC MSD Initiative: Net-Centric Operations 2.0, Domain-Specific SOA Frameworks, and M&S Testbed Demos Bob Marcus robert.marcus@sri.com

2. Executive Summary • The NCOIC and its customers are implementing service-oriented architectures (SOA) in multiple domains • Domain-specific SOA frameworks can be used to provide a foundation for specifying required capabilities for projects • NCOIC M&S demonstrations can test and evaluate the available capabilities of emerging technologies for these frameworks • There is a suite of new technologies that will enable future agile implementation and deployment of new applications • These technologies and applications can be characterized as “Net-Centric Operations (NCO) 2.0” Proposed Initiative: Work with multiple NCOIC and customer projects to design and implement test and evaluation demos of NCO 2.0 technologies applied to domain-specific SOA framework scenarios

3. NCOIC Initiative Summary Diagram Customers Customer Domain-Specific Framework Requirements Set of Requirements New capabilities available Capability specifications (with priorities) and possible new capabilities NCOIC Matchmaking Testing Mediating Capability description (with cost of implementation) and possible new capabilities Set of Services New capabilities needed Net-Centric Operations 2.0 Emerging Technologies

4. Net-Centric Operations 2.0

5. Operations = Enterprise and Tactical Networks From RTI

6. Net-Centric Operations 2.0 Architecture 1. Web Client Application Browser – RIA, AJAX, Mashups XML over HTTP HTTP XMLHttpRequest SOAP over HTTP 2. Web Message Bus Web Server 3.Enterprise Service Manager SOAP Server, WCF Host, Application Server Enterprise Mashups/Pipes Aggregation 4. Composites Orchestration – BPEL, BizTalk 5. Enterprise Service Buses Services, SCA Services, SCA ESBs with multiple transports and XML and binary XML data Adaptor Data Data 6. Enterprise Data and Systems System Gateway Server – Protocol and data transformations 7. Gateway Sensor Networks, Mobile Platforms, Devices, Gateways 8. Tactical Networks

7. Issues for Net-Centric Operations 2.0 Rich Interface Applications (RIA) Web Message Bus Enterprise Service Managers ESB ESB ESB Interoperability Interoperability Enterprise Service Buses Near Real-time Data Gateways Tactical Networks Connections and nodes in bold are key issues for Net-Centric Operations 2.0

8. Physical Domain where strike, protect, and maneuver take place across different environments Information Domain where information is created, manipulated and shared Cognitive Domain where perceptions, awareness, beliefs, and values reside and where, as a result of sensemaking, decisions are made Social Domain interactions between and among force entities Office of Force Transformation Domains Tactical Networks Enterprise Systems Rich Interfaces Web 2.0 Applications Source: http://www.oft.osd.mil/library/library_files/document_353_NCO%20CF%20Version%201.0%20(FINAL).doc

9. NCO 2.0 Enabled Applications in OFT Domains • Physical – Gateway servers support integration across networks • Information – Mashups, adapters, and grids support data sharing • Cognitive – Rich Interface Applications support decision support • Social – Web 2.0 applications supported by Web Message Bus

10. Domain-Specific Frameworks for SOA

11. NCOIC and Customer Projects • DISA Network Enabled Command Capability • JFCOM Modeling & Simulation • SPAWAR Maritime Domain Awareness • ASD NII End-to-end QoS and Network Management • NATO Network Enabled Command and Control • NCOIC Sense and Response Logistics • NCOIC Net-Enabled Emergency Response • NCOIC Building Blocks Certification

12. Domain-Specific Frameworks for SOA Domain Framework including Service Specifications, XML Message Formats, Customized Displays, and Process Models Domain Framework including Service Specifications, XML Message Formats, Customized Displays, and Process Models Domain Framework including Service Specifications, XML Message Formats, Customized Displays, and Process Models Interfaces Services Interfaces Services Common Services Across Multiple Domains

13. Domain-Specific Frameworks for SOA Steps • Divide the enterprise into domains • Identify and implement common services across domain • For each domain; specify domain-specific services, XML message formats, process models, customized displays, and other needed standards • Document the interface services needed between domains • Implement the domain-specific SOA framework by: • Choosing middleware (e.g. enterprise service bus), • Selecting and/or creating services meeting specifications • Map standard data models to XML message formats • Developing customized user interfaces • Create executable processes across services using middleware • Build interface services across domains

14. NCOIC M&S Testbed Demos and Capabilities Mediation

15. Capabilities Testing and Evaluation (Mediation) USERS User Requirements and Derived Requirements Set of Requirements New capabilities available Capability specifications (with priorities) and possible new capabilities Matchmaking Testing Mediating Capability description (with cost of implementation) and possible new capabilities Set of Services New capabilities needed Existing, Enhanced, Composite and possible new services and/or systems

16. Implementation of Capabilities Testing • Organization – Domain experts, emerging technology leaders, and NCOIC M&S Test and Evaluation group • Domains – Multiple domains that require SOA deployment • Tools – Framework design, capability matching, SOA implementation, modeling and simulation • Process – Receive required capabilities from domain experts and end-users. Determine available technology capabilities from emerging technology leaders and suppliers. Perform initial matchmaking to determine possible gaps. Use NCOIC M&S testbed demonstrations to evaluate the need and/or availability of additional capabilities • Communication – Iterative discussions with project teams and emerging technology suppliers • Skills – Understanding of emerging technology descriptions (e.g. NCO 2.0) and domain-specific framework specifications

17. Capabilities Mediation Example Needs sent to Emerging Technology Strategy Needs consolidated, prioritized and documented Clarify need System of System Program solicited for ST&T needs Capabilities Mediation Group Match needs with offerings Consumers Producers Evaluate producers Needs Systems Engineering Group (1) (2) System of Systems Program Management Contractors (3) Emerging Technology Strategy Group (3) Vendors (4) (8) (7) Open Source Libraries Ensure offerings meet needs and constrains and final acceptance for Program (7) Offerings (6) (5) Standards Bodies Scrub list of offerings and do final offering selections, Develop list of possible offerings (9)

18. NCOIC Demos for Capabilities Testing DomainMissionModels Common Framework of Guidance to AchieveInteroperability Domain GeneralArchitectures Specific NodeArchitectures High Level Models MilitaryImplementation Net-Centric Interoperability Military e.g. Models ofcustomerobjectives Tailored High LevelEnterprise& Reference & Capability Models(e.g. FEA, OSI, etc) Net-CentricInteroperability Demos using M&S Command &Control NIF HomelandSecurity/Police/Fire e.g. NESI,NATO NC3TA Model forAlignment ofBoundaries &Interfaces ofboth Functions and Services Others Others e.g. E-commerceWeb Services Government/Commercial Implementation ….…. ..…… .. .. SCOPE NIF BB NCAT CR The NCOIC Tools work together to assist in achieving interoperable systems

19. Capabilities Mediation for NCOIC • Domain-specific SOA Frameworks will be used to define top-down required capabilities for NCOIC projects • Net-Centric Operations 2.0 will be used for bottom-up identification of emerging technologies • Domain-specific services and data models will also be part of the emerging technologies evaluated • Demonstrations will be created based on project scenarios to analyze the fit between domain-specific frameworks and technology implementation using emerging Net-Centric Operations 2.0 technologies • The results of the demonstrations will be reported back to the projects with recommendations for additional service needed or additional operation capabilities available,

20. Net-Centric Operations 2.0 Backup Slides

21. Net-Centric Operations 2.0 Elements • 1. Web Client Application Container (RIA, AJAX, Mashups) - Browser extended with scripting, XML, and asynchronous server access (e.g. Ajax frameworks). Provides greater flexibility for creating rich customizable applications.  • 2. Web Message Bus  - HTTP and XMLHtttpRequest (asynchronous) extended for reliability and two communication. Adds needed enterprise capabilities to application client containers. • 3. Enterprise Service Manager (App Servers, SOAP Servers, Containers) - Combination of Web Server, Application Server, and Web Services Server. Core middleware for accessing enterprise SOA environments.

22. Net-Centric Operations 2.0 Elements (con.) • 4. Composites ( Aggregation, Mashups, Orchestration) -  Orchestration, Business Process Execution, Enterprise Mashups, and Pipes are examples of composites of services and/or data. Enables the rapid creation of new applications and data views from multiple underlying sources.  • 5. Enterprise Service Bus (Message Brokers, Service-oriented) - This is the key infrastructure middleware for creating a large-scale Service Oriented Architecture. It combines messaging, multiple transports, data transformation and adapters to provide the foundation for enterprise SOA.

23. Net-Centric Operations 2.0 Elements (con.) • 6. Enterprise Data, Services and Systems (Data, Services, Systems) - Legacy and new enterprise resources. Standardized adapters and data access methods are needed to interface these resources to the enterprise SOA • 7. Gateway Servers - Connects diverse networks and platforms to an enterprise or backbone network. Performs the require data and protocol transformations needed for efficient interoperability • 8 . Mobile Tactical Networks (Vehicles, Devices, Sensors) – Networks that are used during field operations including combinations of mobile platforms, wireless communication, sensors and handheld devices. These networks will often have to support dynamic or ad hoc network protocols.