United States Joint Staff J7

1. UNCLASSIFIED United States Joint Staff J7 U.S. Joint M&S Strategy NATO M&S Group (NMSG) Presentation to MSG-94 Symposium October, 2012 COL Mark Edgren Technical Solutions Officer

2. UNCLASSIFIED Our Problem Requirement for Accessibility Cost Complexity Relevance What’s Next?

3. UNCLASSIFIED Mandate for Change JTEA Training Framework • Instead of Stovepiped Efforts . . .Joint Training EnterpriseArchitecture“…..the process of translating business vision and strategy into effective enterprise change” • Converged infrastructure and shared resources (cloud computing) • Web 2.0 technologies • Lean processes • Requirements-based, risk-managed • Linking Training to Joint Information Environment (JIE)

4. UNCLASSIFIED JIE End-State • Defensibility/Redundancy/Resiliency • Federation/Shared Infrastructure • Enterprise Services • Identity Access Management • Cost: ???? Deployed Environment Mission Applications Data Computing “Enterprise Information Environment” Coalition Forces DCO Enterprise Email Close Combat TM Data AFATDS APEX Computing AT21 iEHR Navy ERP Airman Fundamentals Defense Travel Applications “Enterprise Information Environment” ?? Mobile (TDY/Deploy) Future devices Work Home Access at the Point of Need

5. UNCLASSIFIED JTEA & JLVC

6. UNCLASSIFIED Decomposition Migrate Constructive Sims Modular Services Cloud Enabled

7. UNCLASSIFIED Lego Production & CEMS All Lego photos and images from internet (Bloomberg Business Week article by Mr. Pisani, November 2006)

8. UNCLASSIFIED Simple Complexity All Lego photos and images from internet (public domain)

9. UNCLASSIFIED Reference Models Tech Stds Arch Guidance Laws, Regs, and Policy OMB FEA Tools DODAF Laws Regs Policy DISR DARS DITPR Solution Architectures Army DON Air Force Joint M&S in IT Context Refresh at the speed of the Adaptive Enterprise Architecture Change at the speed of the operational environment Notional Future Enterprise Architecture Business Warfighting Intelligence Enterprise Information Environment Federated Operational Architectures Dept of Air Force DIA NGA NRO NSA DLA DISA COCOMS Other Accessible Sustainable Validated Operational Architectures / JMT Discoverable

10. UNCLASSIFIED Joint M&S Way-Ahead • Unsustainability of Current M&S • JLVC is a federation of Service/Joint developed models • Manpower (cost) intensive • Constant burden on integration (version control) • DoD Mandates to Move M&S to DoD IT Enterprise • Training enclave joining “mainstream” without being consumed • joint M&S available wherever NIPR/SIPR are • Discoverability & Accessibility • Driving jointness deeper = joint training context for Service use • Current Joint M&S is too monolithic (i.E., Not composable) • Trainers have to compete for sim center support • Technology Changes • Cloud enables linkages now to facilitate trainer involvement • Hardware speed = more efficient modular software approaches • More can be automated to reduce manpower costs • Efficiency • Trainers are unique with specific training objectives – thus need unique training environments • Providing a bigger, more complex training environment than trainers require is wasteful • Fidelity • Trainers have varying need for fidelity (usually related to C4ISR devices M&S input to) • One-size-fits-all approach (either JLVC or JTLS) is too restrictive • We Want Joint M&S to be: • Relevant to Warfighter Needs • Less Expensive to Sustain • Within DoD IT Enterprise Framework • Discoverable & Accessible to Home-Station • Optimized for Cloud & Faster/Better Hardware • A Composable Training Environment (Right-Sized)

11. UNCLASSIFIED Expectation Management You are here

12. UNCLASSIFIED Technical Characteristics • Web-based access to joint M&S for trainers and M&S operators. • Scenario development, MSEL management, C2 stimulation, open orders. • Model operator interface. • Thin clients, Ozone Widget Framework, “app store” model, etc. • Single data exchange model that links high level missions/tasks to low-level simulation behaviors. • Cloud-based computing infrastructure. • Common data services: • OOB, terrain, targets and networks, 3D models, weapons effects, etc. • Common simulation services? • Which functions can be effectively decomposed with current computing resources, networks and technology? • Virtual world framework and a Virtual Training Interface • Shared Computational Power (Economy of Scale) • Rapid Scenario Creation (Hours, Not Weeks)

13. UNCLASSIFIED CEMS Framework • Major Components • Virtual Training Interface (VTI) • Scenario Management Tool (SMT) • Cloud-Enabled Modular Services (CEMS) • Data Service Broker (DSB) • Correlated Data Layer • Opportunities for Collaboration: • Service/Agency/JDir Intellectual partnership • Coalition partnership (MSG) • Funding partnership ($ investment leads to greater fidelity) • OSD Partnership via MSCO • Rapid Data Generation Project • Geospatial Data Correlation • Force Development Mission Process Modeling in Virtual Environments • 3 Priority Projects • Modular service specification • Data service broker prototype • Data management schema Agile Accessible Composable Efficient Tailorable “The Joint Force…will have cutting edge capabilities, exploiting our technological, joint, and networked advantage….” Cover Memo, DoD Strategic Guidance, Januray 2012

14. UNCLASSIFIED JLVC2020 Project Plan FY13 FY14 FY15 FY16 FY17 FY18 FY19 FY20 Cap’s CONOPs (Enhance Joint Training Environment) Hybrid CEMS-Service Simulations (Consistent, Competitive CAX) Limited Tier-III/IV Modules (Service Need for High Fidelity) M&S JLVC JLVC + V6.X JLVC2020 V.6 V4.0 V6.0 V3.0 V1.0 V2.0 V.5 V.3 V.4 CDR Wargame MSEL-Driven CAX for Less $$$ (CAX/MSEL Integration) Composable Environment (Modular at Tier-I/II Level) Accessible Cap’s War- Fighter Relevance CDR-Focused M&S Spt to CCMD Events Easier, Less Expensive, MSEL-Driven/CAX-Supported Events Enhanced JLVC Training Environment (JLVC 6.0 & 6.X) Enhanced JLVC Training Environment (JLVC2020) CCMD Training Requirement Analysis Composability Effect on JELC(Increasing Number of JLVC2020 High-Fidelity Events) A Cloud DSB Prototype Production Production CDIS HLA Guard Solution TS Gateway (Virtuals) Data-Oriented Classification (Multiple Release Levels) Data Data Exchange Model-1 Data Exchange Model-2 Data Exchange Model-3 CAX-Supported Events Unwieldy (Too Complex, Expensive, etc.) JLVC2020 High-Fidelity Coverage Risk JLVC 6.X Decay V.6 V3.0 V4.0 V1.0 DPs $ JELC = Joint Exercise Life Cycle (Planning for Big Training Events) CCMD = Combatant Command (DoD regionally-oriented or functionally-focused joint commands) Training Tiers = Tier-I (CCMD); Tier-II (Joint Task Force); Tier-III (Component Command); Tier-IV (Tactical) CDIS = Cross Domain Information Sharing (moving data across classification/national barriers) CEMS = Cloud-Enabled Modular Services (new M&S framework) CAX = Computer Assisted Exercise MSEL = Master Sequence Event List (scripted events) DSB = Data Service Broker (key component of CEMS framework) JLVC = Joint Live Virtual Constructive training capability HLA = High Level Architecture (M&S interoperability standard) DP’s = Decision Points (leadership opportunity to re-direct) B C E D

15. UNCLASSIFIED Accessibility (Notional)

16. UNCLASSIFIED United States Joint Staff J7 U.S. Joint M&S Strategy NATO M&S Group (NMSG) Presentation to MSG-94 Symposium October, 2012 COL Mark Edgren Technical Solutions Officer

17. UNCLASSIFIED Lots of Modular Services

18. UNCLASSIFIED JLVC2020 V .3

19. UNCLASSIFIED JLVC2020 V .6

20. UNCLASSIFIED JLVC2020 V 1.0

21. UNCLASSIFIED JLVC2020 Services Data Services Modeling Services Examples: OOB, terrain, targets, networks, weather Authoritative source of simulation data Primarily a data repository Transaction-based Loosely coupled, minimal dependencies Key attributes are speed and accuracy Can be decomposed for cloud environment Examples: air dynamics, sensor modeling, population modeling Authoritative source of simulation behavior Primarily a data producer Algorithm-based Tightly coupled, multiple dependencies Key attributes are speed and fidelity Can be decomposed for cloud environment?

22. UNCLASSIFIED ‘Simple’ Visual Detection Entity A Sensor Modeling Line of Sight Terrain Service Entity B 1. Entity A queries sensor modeling service to determine if Entity B can be sensed. 2. Sensor modeling service calls line of sight service for certain sensor detections (i.e. visual). 3 & 4. Line of sight service calls terrain service and Entity B to determine inter-visibility. 5 & 6. Terrain service and Entity B return required data to line of sight service. 7. Line of sight service returns response on inter-visibility to sensor modeling service. 8. Sensor modeling service returns response to Entity A on whether Entity B can be sensed. 1 2 3 4 5 6 7 8 Sequence diagram, showing the modular services invoked to determine a simple visual detection between two entities. Does not include other potential sensor modeling support services, such as weather and environment, emitter signatures, RF propagation, physical movement of the sensor platforms, etc.

23. UNCLASSIFIED Questions . . . • Are there modeling functions that lend themselves to modular decomposition? • How would the inter-module communication work? What protocols and interface specs? • How would decomposed wargaming services be phased in? • How would existing federates phase out existing simulation functionality in place of modular services? • Can existing federates make up the wargaming layer? • Can we use Service federates as a wargaming layer without rearchitecting them in the short term? • How do we bring in new modular services in-stride? • Can we increase fidelity in-stride? Or are we locked into what we start the game with? • How sensitive will CEMS be to latency/distribution?