Attachment_J-03_IWS_1IT_ITS_SEP_1_Sept_2015.pdf

UNCLASSIFIED

DISTRIBUTION STATEMENT C: DISTRIBUTION AUTHORIZED TO U.S. GOVERNMENT AGENCIES AND THEIR CONTRACTORS (ADMINISTRATIVE OR OPERATIONAL USE) (03 NOVEMBER 1997). OTHER REQUESTS FOR THIS DOCUMENT SHALL BE REFERRED TO THE PROGRAM EXECUTIVE OFFICE INTEGRATED WARFARE SYSTEMS 1IT.

PEO IWS 1IT

INTEGRATED TRAINING SYSTEMS (ITS)

Family of Systems (FoS)

SYSTEMS ENGINEERING PLAN (SEP)

Initial Issue

PEO IWS 1IT

Integrated Training Systems

19 June 2015

ITS FoS SEP UNCLASSIFIED 19 June 2015 ii

Integrated Training Systems (ITS) Family of Systems (FoS) – ACAT IVM Systems Engineering Plan (SEP), Supporting Milestone and Modernization

1 SEPT 2015

Mr. Joseph Louden

PEO IWS 1IT

Principal Assistant Program Manager (PAPM), Training Systems

Date iii

LIST OF EFFECTIVE PAGES

Date of issue for original and change pages are:

Initial Issue - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 19 June 2015

Page: *Rev:

Cover/Title - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 0

Signature Pages - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 0

List of Effective Pages - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 0

Record of Changes - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 0

Table of Contents - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 0

List of Tables - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 0

List of Figures - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 0

1-1 through 1-4 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 0

2-1 through 2-6 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 0

3-1 through 3-15 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 0

4-1 through 4-15 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 0

5-1 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 0

A-1 through A-7 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 0

B-1 through B-4 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 0

C-1 through C-2 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 0

D-1 through D-10 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 0

E-1 through E-2 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 0

*Zero in the Rev column indicates an initial page iv

RECORD OF CHANGES

Revision Date Log of Changes Made and Description of Reason Changes

Initial Issue 19 June 2015 Initial development and release of the Integrated Training Systems (ITS) Family of Systems (FoS) Systems Engineering Plan (SEP).

Initial Issue 1 Sept 2015 Restructured engineering organization to reflect lean structured approach focusing on external dependencies.

v

TABLE OF CONTENTS

1 INTRODUCTION ........................................................................................................................................... 1-1

1.1 Abstract ...................................................................................................................................................... 1-1

1.1.1 Introduction........................................................................................................................................ 1-1

1.1.2 Overview ........................................................................................................................................... 1-1

1.1.3 Conclusion ......................................................................................................................................... 1-1

1.2 Purpose ...................................................................................................................................................... 1-2

1.2.1 The Purpose of the SEP ..................................................................................................................... 1-2

1.2.2 The Purpose of Integrated Training Systems ..................................................................................... 1-2

1.3 Background ................................................................................................................................................ 1-2

1.4 Training Capability Requirements/Needs .................................................................................................. 1-3

1.5 Description of the Training Problem ......................................................................................................... 1-3

1.6 Description of ITS Components ................................................................................................................ 1-3

1.6.1 Advanced Training Domain (ATD) (Future - Shipboard) ................................................................. 1-3

1.6.2 ACTS/IAMD (Legacy - Shipboard) .................................................................................................. 1-3

1.6.3 BFTT (Legacy - Shipboard)............................................................................................................... 1-4

1.6.4 Distributed Training (Shore-based) ................................................................................................... 1-4

1.7 SEP Updates .............................................................................................................................................. 1-4

1.8 SEP Updating Authority ............................................................................................................................ 1-4

2 PROGRAM TECHNICAL REQUIREMENTS ........................................................................................... 2-1

2.1 ITS Modernization Systems Engineering Process Model .......................................................................... 2-1

2.2 ITS Architectures ....................................................................................................................................... 2-1

2.2.1 Architecture Development ................................................................................................................. 2-1

2.2.2 Program Operational Concept (Operational View) ............................................................................ 2-3

2.2.3 Program Sustainment (Baseline Architecture) ................................................................................... 2-4

2.2.4 ITS Modernization (Objective Architecture) ..................................................................................... 2-5

2.2.5 Combat Systems Product Line Architecture (PLA) ........................................................................... 2-5

2.3 Interface Control ........................................................................................................................................ 2-5

2.4 Technical Certifications ............................................................................................................................. 2-6

3 ENGINEERING RESOURCES AND MANAGEMENT ............................................................................ 3-1

3.1 Technical Organization .............................................................................................................................. 3-1

3.1.1 Government Program Office Organization ........................................................................................ 3-1

3.1.1.1 Fleet Introduction and Sustainment Manager ................................................................................ 3-2

3.1.1.2 In-Service Engineering Agent (ISEA) Lead .................................................................................. 3-2

3.1.2 ITS Systems Engineering Team ......................................................................................................... 3-2

3.1.2.1 Chief Engineer ............................................................................................................................... 3-3

3.1.2.2 Lead Systems Engineer .................................................................................................................. 3-4

3.1.2.3 Software Development Manager ................................................................................................... 3-4

3.1.2.4 Requirements Management Group (RMG) .................................................................................... 3-5

3.1.2.5 Integration Manager ......................................................................... Error! Bookmark not defined.

3.1.2.6 Information Assurance (IA) System Engineer (SE) ....................................................................... 3-5

3.1.2.7 Software Support Agent (SSA) Lead ............................................................................................. 3-5

3.1.2.8 Test Director and Certification Lead (TD & CL) .......................................................................... 3-6

3.1.2.9 Test and Evaluation (T&E) Coordinator ........................................................................................ 3-6

3.1.2.10 Integration Engineering Support .................................................................................................... 3-7

3.2 Relationships with External Technical Organizations ............................................................................... 3-7

3.3 Systems Engineering IPT........................................................................................................................... 3-9

3.4 Technical Schedule and Plans .................................................................................................................... 3-9

3.4.1 Integrated Master Plan (IMP) and Integrated Master Schedule (IMS) .............................................. 3-9

3.4.2 IWS 1IT Master Build Schedule ........................................................................................................ 3-9

3.4.3 Program Management Plan (PMP) .................................................................................................... 3-9 vi

3.4.4 Work Breakdown Structure (WBS) ................................................................................................... 3-9

3.5 Risk and Issue Assessment and Management .......................................................................................... 3-11

3.5.1 Risk Management Board ................................................................................................................. 3-12

3.5.2 Technical Risks and Mitigation Planning ............................................ Error! Bookmark not defined.

3.5.3 Technical Performance Measures and Metrics ................................................................................ 3-13

4 TECHNICAL ACTIVITIES AND PRODUCTS .......................................................................................... 4-1

4.1 Planned SE Activities ................................................................................................................................ 4-1

4.2 Requirements Development and Change Process ...................................................................................... 4-2

4.2.1 Programmatic Requirements Responsibility ...................................................................................... 4-2

4.2.2 Analysis and Decomposition ............................................................................................................. 4-3

4.2.3 Requirements Management and Change Process .............................................................................. 4-5

4.3 Technical Reviews ..................................................................................................................................... 4-5

4.3.1 Technical Review Process ................................................................................................................. 4-5

4.3.2 Planned System-Level Technical Reviews ........................................................................................ 4-6

4.4 Configuration Change Process ................................................................................................................... 4-7

4.4.1 Technical Baseline Artifacts .............................................................................................................. 4-7

4.4.2 Configuration Management/Control (and Change) Process Description ........................................... 4-8

4.4.3 Roles, Responsibilities, and Authorities ............................................................................................ 4-8

4.4.4 The Baseline Change Process ............................................................................................................ 4-8

4.4.5 IRP/ECP Preparation ......................................................................................................................... 4-8

4.4.6 IRP/ECP Review Process .................................................................................................................. 4-9

4.4.7 Tracking and Reporting Status ......................................................................................................... 4-10

4.4.8 IRP/ECP Cost Estimation ................................................................................................................ 4-10

4.4.9 Navy Modernization Entitled Process.............................................................................................. 4-10

4.5 Design Considerations ............................................................................................................................. 4-11

4.6 Engineering Tools .................................................................................................................................... 4-12

4.6.1 Dynamic Object-Oriented Requirements Systems (DOORS) ......................................................... 4-12

4.6.2 MagicDraw ...................................................................................................................................... 4-12

4.6.3 IWS 1IT Portal ................................................................................................................................. 4-12

4.6.4 MS Office Suite of Products ............................................................................................................ 4-13

4.6.5 RequisitePro ..................................................................................................................................... 4-13

5 CONCLUSION/SUMMARY .......................................................................................................................... 5-1

APPENDIX A ACRONYMS .............................................................................................................................. A-1

APPENDIX B ABBREVIATED GLOSSARY .................................................................................................. B-1

APPENDIX C REFERENCE DOCUMENTS .................................................................................................. C-1

DoD, SECNAV, OPNAV, and NAVSEA Instructions ............................................................................. C-1 C.1 IWS/IWS 1IT Documents .......................................................................................................................... C-1 C.2 Military Specifications and Standards ....................................................................................................... C-2 C.3

APPENDIX D STANDARD REVIEW CHECKLISTS ................................................................................... D-1

Standard Review Tasks ............................................................................................................................. D-2 D.1 Baseline/Build Kickoff (Build Definition) Meeting ................................................................................. D-3 D.2 System Requirements Review (SRR) ....................................................................................................... D-4 D.3 System Functional Review (SFR) ............................................................................................................. D-5 D.4 System Preliminary Design Review (PDR) .............................................................................................. D-6 D.5 System Critical Design Review (CDR) Review Event: System Critical Design Review (CDR) ............ D-7 D.6 Test Readiness Review (TRR) .................................................................................................................. D-9 D.7

APPENDIX E SYSTEMS ENGINEERING (SE) IPT CHARTER ................................................................. E-1 vii

LIST OF TABLES

Table 4-1: ITS Technical Review Summary ..............................................................................................................4-6 Table 4-2: Example - Technical Review Checklist ..................................................... Error! Bookmark not defined.

Table 4-3: Technical Baseline Artifacts ...................................................................... Error! Bookmark not defined.

Table 4-4: Technical and Management Tools .......................................................................................................... 4-12

LIST OF FIGURES

Figure 2-1: Systems Engineering V-Model ................................................................................................................2-1 Figure 2-2: Sample SSDS Functional Architecture Diagram .....................................................................................2-2 Figure 2-3: Sample AEGIS Functional Architecture Diagram ...................................................................................2-2 Figure 2-4: Example Operational View (BFTT) ........................................................................................................2-3 Figure 2-5: Legacy BFTT FoS ...................................................................................................................................2-4 Figure 3-1: IWS 1IT Integrated Training ...................................................................................................................3-1 Figure 3-2: IWS 1IT Systems Engineering Team .......................................................................................................3-2 Figure 3-3: Example of a BFTT Build Plan (NOT to be used for planning purposes) ............................................. 3-10 Figure 3-4: ITS Risk Management Process ................................................................. Error! Bookmark not defined.

Figure 3-5: DOD Risk Cube ........................................................................................ Error! Bookmark not defined.

Figure 4-1: Training Capability Evolution .................................................................. Error! Bookmark not defined.

Figure 4-2: TSTC Spec Tree .......................................................................................................................................4-2 Figure 4-3: Requirements Decomposition/Specification Tree/Baselines ...................................................................4-4 Figure 4-4: IRP/ECP Process ......................................................................................................................................4-9

1-1

1 INTRODUCTION

1.1 Abstract

1.1.1 Introduction

This System Engineering Plan (SEP) provides the Program Executive Office (PEO) Integrated Warfare Systems (IWS) Integrated Training Systems Directorate (1 IT) with a structured approach for managing engineering activities associated with the Integrated Training Systems (ITS) Family of Systems (FoS) For the purposes of this SEP, ITS includes all systems under PEO IWS 1IT purview. As the Integrated Training Organization for IWS 1, IWS 1IT integrates training requirements and systems that enable the Warfighter to “train as we fight”, enhancing current and future readiness. The SEP provides the program’s overall technical approach, including systems engineering (SE) processes, resources, key technical tasks, and measures of success. The SEP will be used by the component government and contractor organizations as guidance for SE activities per program phase, as well as to describe the PEO IWS 1IT approach to program coordination with stakeholders. It is written at a level such that it can be applied to any of the IWS 1IT component programs and tailored further as necessary and as indicated in the individual programs’ Build Plans. The intention of this document is to suggest all potentially applicable reviews and artifacts that shall be used on the most complex of Training System Builds. For less complex builds the Chief Engineer shall provide IWS 1IT a recommendation for tailoring the requirements of this SEP and rationale for why required artifacts or reviews are not necessary for a given build, which will be represented in a Build Plan as needed. IWS 1IT will approve appropriate tailoring of SEP requirements as presented by the Chief Engineer.

1.1.2 Overview

The SEP is the authoritative document that defines the program’s systems engineering activities, including the requirements and design review processes outlined in the PEO IWS Technical Review Manual (TRM). It shall address both government and contractor technical activities and responsibilities to include development of more detailed documents like a Systems Engineering Management Plan or SEMP (Contractor) and Build Plans (Government) for each system development cycle, also referred to as “builds.” These plans are based on technical management processes to include advanced planning;

requirements management; interface management; risk management; configuration management;

technical data management; technical assessments; and decision analysis. Other plans that shall be included in the purview of this SEP are acquisition plans, installation plans, and Fleet support plans. This plan complies with guidance provided by the Secretary of the Navy Instruction (SECNAVINST) 5000.2E and Department of Defense (DoD) 5000 series acquisition instructions.

1.1.3 Conclusion

The SEP shall initially be released as a signed version and will be re-evaluated on a yearly basis according to Section 1.7 SEP Updates. The SEP shall provide continuity of operations between each of the component systems indicated by Section 1.6 Description of ITS Components. This SEP shall cover every activity performed over the lifetime of the system as it pertains to Systems Engineering. It shall be the overarching guidance for development but should never be applied without temperance to specific build items and processes. This SEP shall be the parent document of all PEO IWS 1IT Systems Engineering functions, subject only to the published DOD, DON, NAVSEA, and PEO directives. It shall be maintained current with the Program Management Plan (PMP) and will be reviewed by the Chief Engineer for currency at least annually.

1-2

1.2 Purpose

1.2.1 The Purpose of the SEP

Identify technical planning objectives that support the ITS Modernization and Sustainment Program objectives

Define the Systems Engineering process to implement rigor and define technical reviews to achieve these objectives

Define an integrated process to capture, analyze and trace system level requirements, appropriate design specifications, and adherence to standard Configuration Management (CM) practices

Assure all technical work is clearly identified and described to a level of detail that can be monitored, measured, and managed

Define the resources required to sustain the ITS Systems Engineering efforts Establish metrics or guidance for metrics for monitoring and controlling work to provide visibility and evaluation criteria of the contractor’s work Document the technical decisions made during program execution Comply with guidance provided by the Secretary of the Navy Instruction (SECNAVINST)

5000.2E and Department of Defense (DoD) 5000 series acquisition instructions

1.2.2 The Purpose of Integrated Training Systems

The Integrated Training Systems (ITS) fielded and maintained by IWS 1IT provide realistic, high fidelity training to the Fleet, supporting current and future readiness. Its objectives include training in a manner that is representative of how combat systems (CS) are actually used, preparing the Warfighter for situations that they may encounter. ITS integrate its components/systems with the CS simulating and/or stimulating the CS with those entities the CS would normally sense or experience operationally. ITS’s scope shall be defined in accordance with the Total Ship Training Capability (TSTC) Training Requirements Document (TRD). The TRD is the top level training requirements document and is derived from JCIDS and based on Fleet requirements.

1.3 Background

ITS have evolved from and are comprised of different component systems. The main thrust of IWS 1 IT’s efforts have remained within the Tactical Training environment. The major component of that effort has been the Battle Force Tactical Training (BFTT). Along with the BFTT program, PEO IWS 1IT also manages the Aegis Combat Training System (ACTS), Electronic Warfare (EW) Trainer, Trainer Simulator Stimulator System (TSSS), and ITS-related elements of Distributed Training. The program originally started as a single ship training capability that was intended to be as close as possible to how the Warfighter routinely operated the CS. The objective remains “Train as we fight.” This continues to be the driving factor for the evolution of ITS to include unit level training, and multi-ship Distributed/Joint level Training. ITS are present on nearly every ship in the Fleet as well as on a network of shore based sites that provide the highest fidelity training possible. The focus of this evolution and growth continues to be current and future readiness of the Warfighter. Current BFTT and ACTS embedded training systems will be replaced with an Advanced Training Domain (ATD), which will be a training capability hosted within the combat system architecture. The ATD will take advantage of product Line capabilities within the training capability and the combat system to optimize the fidelity and performance of the training experience.

1-3

1.4 Training Capability Requirements/Needs

IWS 1IT shall strive to ensure integrated training capabilities are robust, realistic and remain commensurate with tactical, doctrinal, and educational standards for Navy, Coast Guard, Expeditionary and Joint/Allied/Coalition Forces. Our support to the Fleet includes:

Provide full Life Cycle Support for the integrated training systems which are installed widely on AEGIS cruisers and destroyers, aircraft carriers and large deck amphibious ships. These systems provide fully integrated & coordinated single to multi-ship combat system team training in a singular synthetic environment.

Provide engineering expertise for NWDC in support of NCTE-ITS integration. The efforts, in collaboration with NWDC, set and uphold the integration standards for all Fleet Synthetic Training (FST) events. Efforts include Modeling and Simulation (M&S), experimentation and Cyber Security for single ship to large-scale Navy or theater exercises such as Terminal Fury, Bold Alligator, and FST-J.

1.5 Description of the Training Problem

Current and Future Readiness are the Chief of Naval Operations (CNO’s) number two and three top priorities. Training system improvements are integral to achieving warfighter competencies and mission readiness both now and in the future. Interface upgrades implement Fleet prioritized warfighting training improvements to the ITS FoS in order to meet evolving combat system capabilities. As a part of Deployment Certification, ITS shipboard systems must be tested and certified during Combat Systems Certification events. Commercial off the Shelf (COTS) obsolescence requires replacement and upgrade of obsolete and out-of-production COTS components in systems installed throughout the Fleet.

1.6 Description of ITS Components

1.6.1 Advanced Training Domain (ATD) (Future - Shipboard)

The Advanced Training Domain (ATD) is IWS 1 IT’s combination of two of its legacy component programs; ACTS/IAMD and BFTT into one cohesive training product to be fielded on all classes of Ships. It will combine common processes of each of the legacy systems, upgrade pieces into newly defined and capable processes, and eliminate those functions that are redundant or no longer required by the Fleet. ATD will also be the realization of Product Line Architecture (PLA) in the Program of Record (POR) Training Systems where it is economical.

1.6.2 ACTS/IAMD (Legacy - Shipboard)

AEGIS Combat System Trainer (ACTS) is embedded into the AEGIS Weapon System to provide training for Combat System Team in Navy AEGIS Cruisers (CG’s) and Destroyers (DDG’s), both in-port and at sea. ACTS provides realistic warfare training across the spectrum of armed conflict; realistic unit level team training in all warfare areas including the ability to train the ship Ballistic Missile Defense (BMD) team. For multi-ship training events, ACTS interfaces with NCTE via BFTT as means to link AEGIS ships together which are in different homeports for coordinated training; external stimulation of shipboard training systems; and simulation of non-shipboard forces.

1-4

1.6.3 BFTT (Legacy - Shipboard)

The Battle Force Tactical Training (BFTT) Program provides realistic joint warfare training across the spectrum of armed conflict; realistic unit level team training in all warfare areas; a means to link ships together which are in different homeports for coordinated training; external stimulation of shipboard training systems; and simulation of non-shipboard forces. BFTT uses a distributed architecture, integrating existing training systems, and uses Distributed Interactive Simulation (DIS) and High Level Architecture (HLA) protocols. BFTT provides ships' Commanding Officers and Strike Group/Strike Force Commanders with the ability to conduct coordinated, realistic, high stress, combat system-level team training as an integral part of the Afloat Training Groups (ATGs), the Tactical Training Groups and C2F/C3F Fleet Synthetic Training (FSTs) exercises.

1.6.4 Distributed Training (Shore-based)

The Navy Continuous Training Environment (NCTE) is the U.S. Fleet Forces Command infrastructure used to conduct Fleet Synthetic Training (FST). FST events are in-port unit level and multi-ship distributed tactical training events conducted by means of multi-warfare synthetic exercises. FST provides graduated warfare proficiency training, interoperability training, operational training, in port mission rehearsal training, and joint interoperability training on the ship's own equipment, through a series of training and evaluation events. FST integrates multi-unit/multi-warfare in-port training into the Fleet Response Training Program (FRTP) using shore-based and ship-embedded simulation and stimulation systems connected via distribution networks. FST develops and maintains warfighting proficiency through tactical exercises and contributes to Fleet readiness.

1.7 SEP Updates

This SEP provides the guidance necessary to support the IWS 1IT Modernization process. It will be revised as required in accordance with SECNAVINST 5000.2E during the course of the modernization and be reviewed and updated as required during the Systems Engineering Technical Review (SETR) process. PEO IWS 1IT and the Systems Engineering Integrated Product Team (SE-IPT) have established methods for process improvements that are likely to drive changes to the SEP over time. The training community (via the Fleet Training Support or Fleet Synthetic Training (FST) representatives), may also have inputs and feedback regarding the defined processes and may independently solicit change and process improvements. Each request will be reviewed independently and if warranted, will be distributed throughout the PEO IWS 1IT ITS community as a SEP Temporary Change Directive in the interim before the next scheduled SEP release. Interim changes will be reviewed and forwarded by the IWS 1IT Chief Engineer and approved by the IWS 1IT PAPM. The process for approval and distribution of program guidance through the Temporary Change Directive shall be defined in the IWS 1IT Configuration Management Plan (CMP). These interim changes will be incorporated in the original document at the next planned review/update cycle.

1.8 SEP Updating Authority

SE planning is kept current throughout the acquisition lifecycle. The IWS 1IT Principal Assistant Program Manager (PAPM) approves SEP updates to support SE technical reviews and program changes that impact the technical strategy. Upon Major Program Manager (MPM) approval, this SEP provides authority and empowers the Lead SE (LSE)/Chief Engineer to execute the program’s technical planning.

This SEP may be updated after contractor award (where applicable) to reflect winning contractor(s)’ technical strategy reflected in the Systems Engineering Management Plan (SEMP).

2-1

2 PROGRAM TECHNICAL REQUIREMENTS

2.1 ITS Modernization Systems Engineering Process Model

ITS Modernization effort will follow the developmental process represented in the Systems Engineering V-Model, Figure 2-1, and the PEO IWS / NAVSEA 05H Technical Review Manual (TRM). This SEP provides guidance on the management and goals of the Modernization Process.

Figure 2-1: Systems Engineering V-Model

2.2 ITS Architectures

ITS are based on a conceptual framework that is designed to accept controlled changes and solutions with minimal impact to hardware, software, people, and engineering process cost. Central to this architecture are the core training capabilities outlined in the TSTC TRD. These core capabilities are to be implemented with common services that aid in integrating the system components used by several training domains, functionally distinct trainer components for the training domains, and stand-alone training tools and aids that support both the trainer and trainee. The following examples provide a reference for how some of the legacy components of ITS are documented within this conceptual framework.

2.2.1 Architecture Development

The Lead System Engineer (LSE) is responsible to the Chief Engineer for the development and maintenance of the training system’s functional architecture diagrams. Updated diagrams will be produced for each major Advanced Capabilities Baseline (ACB) and training system baseline upgrade.

The Requirements Management Group (RMG) (see 3.1.2.3 for definition) will ensure traceability to approved requirements and that the diagrams correctly reflect the build definition direction. The diagrams will be submitted to the Integrated Training Systems Working Group (ITS WG) to ensure planning coordination across the various Participating Acquisition Resource Managers (PARMS). Figure 2-2 and Figure 2-3 are examples of training systems functional architecture diagrams.

2-2

Figure 2-2: Sample SSDS Functional Architecture Diagram

Figure 2-3: Sample AEGIS Functional Architecture Diagram

2-3

2.2.2 Program Operational Concept (Operational View)

Figure 2-4 is an example of an Operational View of one component (BFTT) of ITS. The BFTT Operational Concept, representing the high-level operational domain as it applies to the desired shipboard training environment. The overview includes:

Notional paths and infrastructure of connectivity in the operational environment including external systems and networks

Applicable individual training components within a single-ship, between multiple ships, and among platforms and shore sites to support the integrated training requirements

Connectivity needed to support the in-port, at-sea, and neighboring architectural environments

Shore site connectivity for shipboard integrated training systems (ATD, ACTS, and BFTT) are provided by Navy Continuous Training Environment (NCTE) as part of Distributed Training Events. NCTE establishes the distributed training environment that enables the scenario and stimulus for the overall Virtual, and Constructive (VC) Training Environment (VC-TE) and IWS 1IT Shipboard Training systems are the host platforms for Simulation/Stimulation (SIM/STIM).

Figure 2-4: Example Operational View (BFTT)

2-4

2.2.3 Program Sustainment (Baseline Architecture)

IWS 1IT currently fields multiple builds of each of its component systems encompassing the majority of in service and new construction ships and nearly every shore site. Sustainment of these various builds is crucial and is the focus of IWS 1IT Legacy Support.

The In Service Engineering Agent (ISEA) is represented on the SE-IPT in order to 1) be able to obtain technical assistance in resolution of issues and 2) provide input into the IWS 1IT Modernization process on current system performance observations

Figure 2-5 Legacy BFTT FoS shows an example of the complexity of an IWS 1IT component system, it includes but is not limited to:

AN/USQ-T46(V):

o BFTT Operator Processor Consoles (BOPC) o Data Collection Module (DCM) o Navigation Simulator (NAVSIM) o CEC Training Adjunct (CTA) o Simulation Control Gateway (Digital Computer/Gateway) o SQQ-89 LAU o SSDS Training LAU

AN/USQ-T47(V)

o BFTT Electronic Warfare Trainer (BEWT) o BFTT Electronic Warfare Trainer II (BEWT II)

AN/USQ-T48(V)

o Training Simulator/Stimulator System (TSSS)

Figure 2-5: Legacy BFTT FoS

2-5

2.2.4 ITS Modernization (Objective Architecture)

PEO IWS 1IT has initiated a FoS Modernization effort. This effort is aimed at incorporating new training capabilities needed to ensure that training systems remain current based on improvements to combat systems, meeting the increasing demand by the Fleet for realistic synthetic training and addressing obsolescence. Also targeted are component and architecture updates that focus on value, reliability, and the reduction of total ownership cost. Near term and long term modernization goals include:

Near Term o Improve integration between the Combat System and the Training System to improve usability, and improve the user experience o Add Warfighter improvements that focus on current threats and tactical capabilities o Transition to Service Oriented Architecture (SOA), an integrated format that blends seamlessly with the Combat System o Transition Combat System element trainers and other Sim/Stim devices to High-Level

Architecture (HLA) o Address hardware obsolescence issues through the systematic removal of legacy hardware and aggressive harvesting of scarce components o Simplify the logistics and sustainment paths by transitioning to a common hardware architecture shared with the Combat System

Long-Term o Integrate training services with combat services to provide a seamless training architecture that acts as a native component of the Combat System o Transition training components to service based Product Line Architecture (PLA), where the tactical system has already matured the interface o Transition from BOPC consoles to natively present in the training system via combat consoles o Improve combat system requirements to support training systems as a native component that supports all enterprise training needs from navigation, to display, to all aspects of the training continuum.

2.2.5 Combat Systems Product Line Architecture (PLA)

Program Executive Office Integrated Warfare Systems (PEO IWS) has adopted a product line approach to surface combat system acquisition based on a common product line strategy that aligns combat system architectures, decouples combat system capability development from platform integration, and reuses common components across ship classes. This approach represents a fundamental change in Navy acquisition strategy that seeks to achieve efficiencies through early technology testing, software re-use, and a reduction in lead time from concept to Fleet introduction.

ITS software components will be system engineered to conform to the combat system software PLA’s as they mature. These components will be developed in accordance with the ACB/TI processes as common assets to be leveraged across multiple platforms.

2.3 Interface Control

ITS have external interfaces and dependencies that shall be defined in Training System Interface Documents (TSID’s). TSID’s identify which Software Requirements Specifications (SRS), Hardware

2-6

Requirements Specifications (HRS), or Weapon Specifications (WS) will define each of the interfaces.

Compatibility with other interfacing systems and common architectures are maintained throughout the development/design process.

2.4 Technical Certifications

The system-level technical certifications shall be obtained during ITS components’ program life-cycle within Combat Systems Certification events. Examples include software builds that must be certified with each combat system baseline that it will be fielded on.

3-1

3 ENGINEERING RESOURCES AND MANAGEMENT

3.1 Technical Organization

3.1.1 Government Program Office Organization

The Program Management Team (PMT) shown in Figure 3-1: IWS 1IT Integrated Training is the forum established by the PAPM to ensure overall integration of the various training program components and their activities. The PMT is chaired by the PAPM and includes IWS 1IT Chief Engineer, Software Development Manager, the Budget and Financial Manager (BFM), Fleet Introduction and Sustainment Manager, Test Director and Certification Lead, IA System Engineer, and Principal for Safety (PFS).

Team members are empowered to make decision as appropriate for areas for which they represent. The PMT meets weekly to discuss project status, ongoing issues, concerns, and risk management.

To be supplied in next revision.

Figure 3-1: IWS 1IT Integrated Training

3-2

3.1.1.1 Fleet Introduction and Sustainment Manager

The Fleet Introduction and Sustainment Manager is responsible for installation of ship and shore products.

The Fleet Introduction and Sustainment Manager has the following responsibilities:

SCD initiation, development and submission Develop installation/ fielding plan briefs to present to ECCB for approval of SCDS Manage Ship check schedules and oversight of ICD/SID development Execution of FY installation budget Perform periodic AIT audits

3.1.1.2 In-Service Engineering Agent (ISEA) Lead

The ISEA Lead is responsible to the Fleet Introduction and Sustainment Manager for ISEA activities.

This function is assigned to ISEA. The ISEA Lead has the following responsibilities:

Designing and deploying the support system utilizing performance-based logistics Acquire and concurrently deploying supportable systems, including support infrastructure Maintain the Integrated Logistics Support Plan (ILSP) Maintaining/ improving readiness, improving affordability, and minimizing logistic footprint Maintain approved Configuration Management Plan Collaborating with the system users to ensure proper operation and maintenance Perform system reliability checks, assisting in the maintenance of the system, helping users diagnose problems with systems Supporting the use of the system for major training events such as Fleet Synthetic Training (FST) events and joint training events

3.1.2 ITS Systems Engineering Team

The IWS 1IT Systems Engineering Team is organized, as shown in Figure 3-2. The Engineering team reports to the Chief Engineer as delineated on the organizational chart. The team is responsible for engineering activities within their individual technical area, and for supporting PMO development of the roadmap for the ITS modernization. The Engineering team will work as required to support the Fleet Introduction and Sustainment Manager in maintaining the operation of fielded ITS components/systems.

PEO IWS 1IT relies heavily on Naval Surface Warfare Center (NSWC) SMEs to augment the program office staff.

To be supplied in next revision.

Figure 3-2: IWS 1IT Systems Engineering Team

3-3

3.1.2.1 Chief Engineer

The Chief Engineer manages all engineering inputs to the project IMP/IMS and organizes and maintains requirements for each capability baseline and provides overarching guidance in development of the products. The Chief Engineer roles and responsibilities include, but are not limited to:

Develop a total system design solution that balances cost, schedule, performance, and risk Coordinate with Fleet Training Stakeholders, SYSCOMs, and PEO IWS PARMS on all areas related to integrated combat systems training.

Develop and track technical information needed for decision making Verify technical solutions satisfy sponsor requirements Develop a system that is economically produced and supported throughout its life cycle Develop and monitor internal and external interface compatibility of the system and subsystems using an open systems approach Establish a Risk Management process to identify, evaluate, track, and mitigate system technical risks Establish IMP/IMS and Work Breakdown Structure (WBS) Establish training system baselines Charter Systems Engineering Integrated Product Teams (SE-IPT’s) as required Direct Program technical reviews in accordance with PEO IWS/NAVSEA 05 TRM

3-4

3.1.2.2 Lead Systems Engineer

The Lead Systems Engineer (LSE) is responsible to the Chief Engineer for communicating engineering decisions and status of ongoing assigned actions. The LSE coordinates technical efforts with the Chief Engineer, and organizes technical briefings as necessary to keep the PAPM and the PMT members advised of design decisions and readiness for all formal technical reviews.

The LSE has the following responsibilities:

Chair the IWS 1IT SE-IPT Maturing top level requirements Generating total system views with external interfaces defined Coordinating all build definitions and managing the Build Plan Leading the technical activities directed to be engaged by the Integrated Training System

Working Group (ITS WG) Member of IWS 1IT Local Configuration Control Board (L-CCB) Coordinating concept to realization activities for all new subsystem integration efforts Coordinating system engineering activities with the functional leads Providing system and software cost, schedule, performance and risk inputs Providing POM inputs and future training systems strategies to the PAPM and PM IPT, and maintains POM supporting technical data Cross-functional integration with both functional leads and technical product teams, ensuring the inter-dependencies in the project plan reflect the nature and sequence of tasks on the project baseline

Reviewing test plans (functional and technical) to ensure integrity and quality of production system

Assigning resources where detailed engineering focus is required

3.1.2.3 Software Development Manager

The Software Development Manager (SDM) is responsible to the CHENG for management of individual build plans for ITS component systems. SDM responsibilities include but are not limited to the following:

Assisting the CHENG with coordinating build definitions and managing an individual build plan Assisting the CHENG with coordinating concept to realization activities for a new subsystem integration effort Coordinating system engineering activities with the functional leads supporting a given build plan Providing system and software cost, schedule, performance and risk inputs to the CHENG Cross-functional integration with both functional leads and technical product teams, ensuring the inter-dependencies in the project plan reflect the nature and sequence of tasks on the project baseline for a given build

Reviewing test plans (functional and technical) to ensure integrity and quality of production system for a given build

Assigning resources where detailed engineering focus is required on a given build

3-5

3.1.2.4 Requirements Management Group (RMG)

The RMG is responsible to the LSE for documenting and recording all requirements levied on training systems maintained by IWS 1IT. The RMG will submit requirements to the SE-IPT for action.

Responsibilities include:

Manage the Requirements Development Process; including, receipt of the initial requirement input, tracking, and management of the requirement as it is processed

Conduct Initial Review and Validation of submitted requirements Generate Concept Papers, IRP’s and ECP’s as directed by the Develop and maintain Technical Documentation in support of OPNAV top level requirements.

Maintain traceability of requirements to fielded capabilities Conduct and Support Requirements Reviews. The RMG will support all in-process reviews as directed by the PMO

3.1.2.5 Information Assurance (IA) System Engineer (SE)

The Information Assurance SE reports to the PEO IWS 1SE IA Manager (PEO IWS IAM) for guidance and concurrence in IWS 1IT’s engineering approach to meeting IADAA requirements. Responsible to the PAPM for ensuring IWS 1IT products meet the requirements of DODI 8500.2, CJCS, DOD, DON and NAVSEA Policy and guidance. This function is assigned to ISEA.

The IA Lead has the following responsibilities:

Coordinating all IA efforts with the PEO IWS IAM Provide PAPM updates on current IA efforts and IA programmatic risk during staff meetings and periodically as required Ensuring the alignment of policy with requirements Articulating requirements to the PAPM Coordinating C&A external efforts with the PEO IWS IAM Interfacing with the NAVSEA 05 Tech Warrant Holder

3.1.2.6 Software Support Agent (SSA) Lead

The Software Support Agent Lead has the primary responsibility to the Software Development Manager (SDM) for development of all integrated training system software.

SSA Lead responsibilities include:

Oversight of Software Development of “ALL” ITS products.

Development…