Joint Distributed Engineering Plant (JDEP): Joint Distributed Engineering Plant (JDEP) Mr. George J. Rumford JDEP Program Office, GES Engineering Directorate 703-681-1129 rumfordg@ncr.disa.mil 7 Jan 2004


JDEP Overview: JDEP Overview JDEP is DoD-wide capability for Service and Joint engineering, integration, and test resources to provide system of systems battlefield representative environments in support of developer, tester, and warfighter requirements Based on JS/PUSD(AT&L) Letter, JETF Report, PBD 725, DPG, FY02-FY07 PDM, & Transition Memo Doctrine and operations are increasingly dependent on Joint SoS Demands new approaches to SoS development, integration, test and assessment Addresses need by providing users the means to create SoS environments by linking existing capabilities Capabilities shared and applied in different configurations to address SoS issues JDEP supports users to select/configure the existing resources, using common reusable assets, to address interoperability issues Why JDEP?


JDEP Vision: JDEP Vision Improve the interoperability of weapon systems, platforms, and C2 within and across the Services by providing the capability to create environments to support engineering, development, integration, testing, evaluation, and certification in a replicated battlefield environment, leveraging Service and Joint combat system engineering and test sites


JDEP VisionDepicted: JDEP Vision Depicted


Testing Interoperabilityusing JDEP: Testing Interoperability using JDEP Verify the interoperability of weapon systems earlier in development by integrating the existing hardware-in-the-loop labs used to develop and test the weapon systems Immerse the weapon systems under test in an integrated test environment Simulate other weapon systems that are unavailable


JDEP Bridges Across theAcquisition Process: JDEP Bridges Across the Acquisition Process Transition from “Everything is Simulated” to “Everything is Live” Data Coherency throughout Acquisition Appropriate Level of Fidelity Repeatable & Controllable Validated & Accredited Operationally Realistic JDEP Technical Framework instituted with Model Driven Architecture (MDA) principles


JDEP Goals: JDEP Goals Create a capability to integrate DoD and Industry laboratories, test sites, and facilities to address and resolve weapon system interoperability issues for warfighters, system developers, & testers Support users in selecting, accessing, and integrating HWILs, simulations, and range systems, using supporting tools, under a set of common standards and procedures


JDEP Program Elements: PDM add funds as shown in the table to fund the JDEP at levels specified in the Defense Planning Guidance and to transfer the JDEP responsibility to the Joint Interoperability Test Command at Fort Huachuca, AZ FY02 FY03 FY04 FY05 FY06 FY07 FY02-07 JTAMDO $ 10M $ 10M $ 10M $ 10M $ 10.2M $ 10.4M $ 60.6M Marine Corps 0.9M 1.0M 1.2M 1.4M 1.2M 1.2M 6.9M Navy 5.0M 5.9M 5.2M 5.9M 5.9M $5.9M 33.8M Air Force 4.6M 6.4M 6.7M 6.7M 5.0M 5.0M 34.4M Army 1.7M 3.4M 4.0M 3.7M 3.8M 3.8M 20.4M DISA/JITC 4.2M 4.3M 4.4M 4.5M 4.5M 4.5M 26.4M Total Requirement 26.4M 31.0M 31.5M 32.2M 30.6M 30.8M 182.5M JDEP Program Elements


FY03 JDEP AMD Events : FY03 JDEP AMD Events SIAP SE TF: Pilot Events Inject bias to experiment with time synchronization, sensor tracking, data registration, and PPLI accuracy USSPACECOM: TBM Early Warning Investigate TIBS/TRS/GCCS interface and TIBS timing issues USAF: Critical Area Air Defense (CAAD) Event Experiment using existing sensors in Homeland Defense Architectures USAF: Distributed Joint Cruise Missile Defense (JCMD) Identify and verify potential improvements to CMD warfighting concepts USAF: Korean Secondary Automated Air Defense System (SAADS) Evaluation Event (Cancelled) Assess the Multi-Source Correlator Tracker (MSCT) capabilities USAF: Time Sensitive Targeting (TST) Network Investigate tactics, techniques, and procedures (TTP) concepts


JDEP Event SitesFY02-FY03: JDEP Event Sites FY02-FY03 Air Force TACCSF, Kirkland AFB: CRC, AWACS 1st AF, Tyndall AFB: MSCT ESC, Hanscom AFB: AWSIM Navy NAVAIR, China Lake: F/A 18 USN NSWC, Moorestown: AEGIS, A-STATS ESTEL, PAX River: E-2C, RISS Dahlgren, Aegis, DS3 Marines MCTSSA, Camp Pendleton: TAOC, RES Army SED, Redstone Arsenal: Patriot FMS-D Joint Sites JPO: DISN-LES Provider JITC, Fort Huachuca: JDEP Operations JNIC, Schriever AFB: JSWS Contractor Sites Boeing, Seattle: E-3 AWACS VWC, St. Louis: F-15 Raytheon, Bedford: JLENS, MSCT Raytheon, Tucson: Interceptor Missile, Aircraft Model, Threat Generator Boeing, Seattle: AWACS, AMASIM


FY03 JDEP AccomplishmentsBeyond the AMD Events: FY03 JDEP Accomplishments Beyond the AMD Events Established the SIAP Testbed for the Integrated Air Defense Integrated Architectures Advanced JDEP Technical Framework Expanded JDEP Communication Network Initiated Configuration Management Guide for JDEP Communication Nodes Discussions with Acquisition Programs Future Combat System (FCS) Joint Strike Fighter (F-35) Cooperative Engagement Capability (CEC) Groundwork for Partnerships with: JFCOM (J6, J7, J8, J9) DOT&E


FY04 JDEP AMD Events: FY04 JDEP AMD Events Process of selection for the Air & Missile Defense JDEP Events has been overseen by the JTAMD process 15 Events nominated: SIAP SE TF: 3 events Army: 1 event USSTRATCOM / MDA: 5 events Navy: 2 events Air Force: 4 events JCoCaC (Joint Council of Captains and Colonels) prioritized the FY04 AMD JDEP Events on 24 July 2003 JNIC (Joint National Integration Center) is currently building the Execution Plan striving to execute as many nominated FY04 events as funding permits


Methodology for FY04 AMDEvent Prioritization: Methodology for FY04 AMD Event Prioritization Step 1: JNIC meets with Event Sponsors to review each proposed event Step 2: JNIC meets with JITC to discuss FY04 infrastructure requirements Step 3: Event Sponsors, JNIC, JITC meet for detailed planning and schedule coordination Step 4: JNIC meets with Event Sponsors to refine proposals and coordinate briefings Step 5: Event Sponsors brief OAR WIPT Working Group Step 6: OAR WIPT Working Group prioritizes events for presentation to JCoCaC Step 7: JCoCaC approves TAMD Event priorities Step 8: JNIC builds Execution Plan


Proposed FY04 AMD Objectives: Proposed FY04 AMD Objectives Block 0 Upgrade to Patriot PDB-6 Assess Correlation/De-correlation, Formation Tracking, and Data Registration Participants: Patriot, Aegis, E-2C Defense of Korea/Japan Assess TTPs, Caps and Lims and support CID & Coalition interoperability Participants: 4xCVBG, Patriot, AWACS, CAOC, TAOC/TPS-59 Integrated Fire Control Foundation Assess interoperability of Aegis 6ph3 and ability of force to conduct cooperative engagements Participants: Aegis, E-2C, AWACS, F-15, CAOC, TAOC/TPS-59, Patriot, JLENS Constellation Test Bed Assess operational concepts, performance, & military utility of Integrated GMTI systems Participants: ESC, CWIN, VWC, LM GVN, Aegis-Dahlgren, AFRL Joint Engagement Assessment Network Address FIOP Task 2 Focus, support DCGS and JFN Development, delineate Interoperability issues and foster Joint Acquisition for DCGS and JFN Participants: Navy Strike Cell, ESC, TAOC, AFRL Capability Upgrades Continue development of better comm, sensor and environmental representations Integrate digital representations for SIAP SE Aegis (LMC representation – MADUSA) Patriot (Sim being developed by SED) E2-C (Identified E2XV (NG effort) to SIAP SE TF) Integrate Hardware-in-the-Loops for SIAP SE AWACS, TAOC, F/A-18 for SIAP SE


Air & Missile DefenseLong Range Plan (FY05-09): Air & Missile Defense Long Range Plan (FY05-09) JCoCaC approved POA&M in May Plans received to date SIAP Systems Engineer Navy Air Force Army MDA/USSTRATCOM Early Warning JNIC is in the process of drafting an encompassing Long Range Plan


JDEP Strategic PlanPurpose: JDEP Strategic Plan Purpose Provide the Foundation to Guide the Operation of JDEP Starting point to answer core questions Why create JDEP? Why use JDEP? (Vision) What is JDEP? (JDEP Capability Definition) What constitutes a JDEP node? (Tech. Framework) How do you use JDEP? (Concept of Operations) Who owns/runs what in JDEP? (Management Plan) Who pays for what in JDEP? (Business Model) How do you expand and grow JDEP? (Expansion Plan)


JDEP Strategic PlanOverview: JDEP Strategic Plan Overview JDEP Capability Definition Technical Framework Requirements Documentation Development Plan Operational Process for an Event Event Definition, Planning, Set-up, Execution, & Analysis Management Plan Concept of Operations Management Structure Roles and Responsibilities Business Model Sustainment Plan Modernization Plan Extension Plan New Domains Partnerships


JDEP Technical Framework: JDEP Technical Framework Data Transport Capability Technical Architecture for JDEP Events Data Elements and Definitions Data Exchange Software (i.e., RTI / Middleware) Definition of Compliance Simulation Resources (employed as needed) Synthetic Environmental Effects Generation (Terrain, Weather, EMI, etc.) Other Blue Force Systems Generation (Behaviors, Communications, Sensors, etc.) Threat Generation (Behaviors, Communications, Sensors, etc.) Process to Plan, Conduct, & Analyze Events Repository of Data Definitions, Interfaces, and Tools for Reuse Persistent Data Archive for Post-Event Analysis Supporting Tools


JDEP Management Plan: JDEP Management Plan Concept of Operations Covers the operations of JDEP at a macro-level (rather than at an event level) How do users schedule an event in JDEP? Management Structure Roles and Responsibilities Who does what & when? What are the R&R for non-AMD events? Business Model Sustainment Plan How are events paid for? What part of the Technical Framework does DISA pay for and what part is consider “event specific”? Who should POM for what? Modernization Plan Who pays for site upgrades? Who pays for technical framework upgrades?


JDEP Management Structure(Augmented): JDEP Management Structure (Augmented) Infrastructure Issues Event Issues Issue #1 JITC manages Capability Owners provide input Programmatic Technical Issue #1 JNIC manages for AMD Event Managers provide input Programmatic Technical


JDEP Technical Working Group (JTWG-01): JDEP Technical Working Group (JTWG-01) Held 3-4 Dec 2003 in Crystal City, VA Over 70 attendees Reviewed lessons learned from the FY03 events Many, many issues identified Network very expensive and difficult to set-up Many concerns identified with HLA Many process issues identified (planning, set-up, accreditation, configuration management, etc.) No prevalent solution for timing A number of tools identified with lessons learned 22 action items taken Next meeting scheduled for 18-19 Feb 2004


Extension Plan Beyond AMD: Extension Plan Beyond AMD Future of the Department is integrated systems based upon integrated architectures Weapon System Acquisition will be driven by Functional Capabilities Boards (FCBs) for requirements Battlespace Awareness Command & Control Focused Logistics Force Protection Force Application Continue to work with core acquisition programs Future Combat System (FCS) Cooperative Engagement Capability (CEC) Joint Strike Fighter (F-35) Partnerships with OSD(P&R), JFCOM, and DOT&E


Key Acquisition Programs in Dialogue with JDEP: Key Acquisition Programs in Dialogue with JDEP Future Combat System Joint Strike Fighter Joint Integration and Interoperability of Special Operations Joint Test and Evaluation CVN 21 (future aircraft carrier) Distributed Common Ground/Surface Systems Multi-Sensor Command and Control Aircraft System Common Aviation Command and Control System DD(X) Future Surface Combatant Program


Summary: Summary JDEP is providing the capability needed to integrate our development and test resources to better develop, test, & assess interoperability JDEP is currently focused on Air & Missile Defense JDEP is extending into other mission area by working directly with Acquisition Programs as well as coordinating with the Functional Capabilities Boards (FCBs) Next JDEP Technical Working Group Meeting scheduled for 18-19 Feb 2003 in Crystal City