Software Systems Technology Conference

Size: px
Start display at page:

Download "Software Systems Technology Conference"

Transcription

1 Capabilities Composition Software Systems Technology Conference 22 April 2009 Mr. Terry Simpson Space & Naval Warfare Systems Center Atlantic (843) DSN

2 Agenda Background Today Tomorrow Getting There Stakeholders The Challenge Governance (alignment of the pieces) Example: Navy Technical Reference Model (NTRM) Collaboration Environments Innovation & Composition Summary & Discussion 2

3 Where We Are Today A Systems focus. Inflexible systems cannot be easily reconfigured to meet changing mission needs Systems are the centers of gravity, and all data is stored within them Multiple systems are often required to execute a mission thread Every link and interface must be tested/accredited Capabilities delivery & upgrades are expensive and time consuming Business logic (and data) is still largely buried in stove-pipe systems 3

4 Where We re Heading A Mission Focus. Far fewer connections, much more agile development cycle Data Sources are centers of gravity - data is stored within data enclaves Compose capabilities to meet warfighter / mission needs Expose and tailor business logic to meet mission needs Deliver component capabilities incrementally to meet dynamic mission needs Business logic (and data) is delivered through components rather than systems 4

5 Service Orientation of a Mission Thread PLAN FIND FIX TRACK TARGET ENGAGE ASSESS ISRT MP Deliver e components C2 rather than systems Components are provided as information services Components can be arranged in any way to provide overall composite application Component design p pp provides flexibility, higher re-use, and better manageability Orchestrated Composite Application Core/Enterprise/Infrastructure Services Common Computing Environment 5

6 Getting from Today to Tomorrow Warfighter Needs define the goal Operational Architectures define deployable approaches to deliver mission capabilities Capability Portfolio Managers guide and drive capabilities developed and delivered for C2, BA, L, NC. Resource Sponsors use CONOPS, Scenarios, Mission Threads and wargames to determine appropriate investment areas Operational Test Authorities test systems and capabilities against mission thread, interoperability, and technical guidelines OSD NII and Service Directives guide NetCentric ece Data aasharing gand Data aa Exchange Programs of Record direct and manage capabilities Fielding and life-cycle management Fielding Operational Architectures Warfighter Needs Resource Allocation Data Sharing Capability Development Infrastructure Services Test & Certification Governance & Collaboration Capability Composition focuses Data, Applications and Infrastructure on Warfighter needs 6

7 The Challenge using CANES as an example Governance (Operational, Acquisition, Engineering, Enterprise) C2 Applications PMW 150 IO/ISR Applications PMW 120 Business Applications various providers (Naval, Joint) Other COI Applications various Providers (Naval Joint) CANES Infrastructure (CCE, SOA, IA) (Naval, Joint) Align & synchronize capabilities and processes to enable development 7

8 Dimensions of Governance Portfolio Management of : OPERATIONAL Requirements Operational requirements Acquisition priorities and funding Engineering solutions ACQUISITION Scale and align with the Funding Testing larger Service / Joint enterprise environment Leverage intersections ENGINEERING between key elements of (Technical Joint and Service specific Authority) efforts 8

9 Quality of Service (QO OS) Information Assurance e (IA) Data Architecture Quality of Service (QO OS) Information Assurance (IA) Data Architecture e Navy Technical Reference Model (NTRM) Overview Application Services (2 of 2) Aviation Systems Command & Control Combat Systems Application Services (1 of 2) Support Systems Command Structure ISR Ship Control Combat Identification Business Apps Intelligence, Surveillance Integrated Bridge Operational and Planning Reconnaissance Voyage Management Logistics Monitor and Synchronize Execution Information Ops Weapon Mgmt ERP Situation Awareness Engineering Control Vehicle Control Meteorological & Damage Control Distance Learning Oceanographic Distance Training Support Readiness Organizational Messaging Medical Common Services Basic Services SOA Core Services (Tactical Edge) Enterprise Services Application Services Support Systems Aviation Systems Application Services ISR Command & Control Ship Control Combat Systems Platform Training Object Invocation Computing Systems Management Data Management Data Extraction/Recording Display Video Portal Notification Service Discovery Messaging Enterprise Service Mgmt Workflow Mgmt Orchestration Credential Validation Authorization Directory Services Service Management Collaboration Common Services Basic Services Common Services SOA Core Services (Tactical Edge) Enterprise Services Navigation, Position & Time Application Framework Distributed Computing Visualization Security /IA Collaboration Mediation Search Catalog Common Computing Environment ecommon Computing Environment Common Computing Environment Hosting Environment Computing Hardware Common Computing Environment Hosting Environment Computing Hardware Communications & Networks WANs SATCOM Communications & Networks LANs Wireless Network/ Circuit Mgmt Security Computing Environment Virtualization Data Hosting Processors Enclosures Storage PDA s Servers Peripherals Navy Technical Reference Model Level 0 Navy Technical Reference Model Level 1 Workstations Communications & Networks WANs LANs Network/ Circuit Mgmt DISN Core Networks Afloat Shore Network Mgmt Terrestrial C2 Network Ashore Transport/Backhaul Afloat Network Mgmt Interior Comms Afloat Network WAN Gateway Communications Circuit (Shore) Telephony Mgmt Secure Voice SATCOM Wireless Security (Communication Non- Narrowband SATCOM) Computer Net Defense Tactical Data Links Wideband Encryption Services Protected Tactical Comms Key Mgmt Services Broadcast Sensor Netting Comms Public Key Infrastructure Navy Technical Reference Model Level 2

10 NTRM Level 2 (With R&R Based on Existing Acquisition Efforts) MULTIPLE Common Services PEO C4I PEO IWS Basic Services SOA Core Services (Tactical Edge) Enterprise Services PEO EIS PEO SHIPS PEO LMW NAVAIR JTRS Object Invocation Computing Systems Management Data Management Data Extraction/Recording Portal Notification Service Discovery Messaging g Enterprise Service Mgmt Credential Validation Authorization Directory Services Service Management Collaboration SERVICES Display Orchestration DISA Video Security /IA Navigation, Position & Time Collaboration Application Framework Mediation Distributed Computing Search Visualization Catalog

11 ONR Core Services Architecture Evolution Reference Framework CS-RI CS-RI (Open Source) CS-RI (COTS) Core Services Reference Implementation ti (CS-RI) CS-RA Core Services Reference Architecture (CS-RA) CS-Reference Element Architecture CS-Layered Reference Architecture CS-REA CS-LRA CS-RM CS-SRM CS-IRM Core Services Reference Model (CS-RM) CS-Service Reference Model CS-Infrastructure Reference Model

12 Engineering Governance Enabler Engineering Governance is enabled by collaboration and the co-evolution of tools and engineering processes to support interoperability Co-evolution requires a flexible Collaborative Engineering i and Certification Environment (CECE) A CECE is a key collaboration & reuse enabler Discovery Context Service Descriptions Unintended Consumer ($$$$) Scalability and Extensibility Interfaces 12

13 Guiding Composition Warfighter Req Collaborative Test Thread Architecture System Architecture 13

14 [1] OPNAV N6F, 2008, Enterprise Engineering Implementation White Paper (Draft) Linking Innovation to Acquisition

15 Summary - the challenge continues Service Orientation is still evolving Design patterns, technologies, and implementation and support processes (including ITIL v3) Understanding of Governance is still evolving Engineering, Acquisition and Operational Governance enables interoperability via flexible, transparent,collaborative processes Re-use goes beyond just code and applies to knowledge, processes, artifacts, approaches, and testing (there is no single answer apply a full spectrum of SSPPs) CECE provides the foundation for development agility Persistent engineering and test facility transparency and collaboration Alignment and traceability of Capability Modules and Mission Threads Rapid assessment via experimentation and MUAs 15 SOA is not the answer to everything; one SOA is not the answer to anything

16 List of Acronyms SOA Service Oriented Architecture C2 Command & Control ISRT Intelligence, Surveillance, Reconnaissance & Targeting MP Mission Planning L Logistics NC Net-Centric ONR Office of Naval Research OPNAV Navy Echelon 1 resource organization NWDC Naval Warfare Development Command PEO Program Executive Officer CECE Collaborative Engineering & Certification Environment CES Core Enterprise Services CCE Common Computing Environment CPM Capability Portfolio Management ITIL v3 Information Technology Infrastructure Library version 3 MUA Military Utility Assessment SSPP Standards, d Specifications, Patterns and Practices CM Configuration Management 16

17 Questions & Answers 17 17

18 Navy SOA Reference Implementation * See ONRRI-SSPA.doc for supported Standards, Specifications, Protocols and API versions. * See ONRRI-Blueprints.doc for guidelines, patterns and code examples.