Attachment_1_-_SOW__29_Aug_18.pdf

ATTACHMENT 1

STATEMENT OF WORK (SOW)

FOR THE

TACTICAL CONTROL SYSTEM (TCS)

16 29 August 2018

DEPARTMENT OF THE NAVY

PROGRAM EXECUTIVE OFFICER, SUBMARINES (PEOSUB)

SUBMARINE COMBAT AND WEAPONS CONTROL SYSTEM (PMS425)

1333 ISAAC HULL AVE, SE

WASHINGTON NAVY YARD

WASHINGTON, DC 20376

Attachment 1: Statement of Work N00024-18-R-6407 i

Table of Contents

Statement of Work for the Tactical Control System

1. Scope

1.1. Navy Organization

1.2. Background

1.3. System Overview

1.4. Program Phasing

2. Requirements and Contractual Compliance

2.1. Applicable Documents

3. General Requirements

3.1. Program and Contract Management

3.1.1. Contractor Performance Management and Progress Reporting

3.1.2. Work Breakdown Structure (WBS)

3.1.3. PPC

3.1.4. Subcontract Management

3.1.5. Program Reviews

3.1.6. Meeting Support

3.2. Licenses

3.3. Government Access to Contractor Facilities and Digital Environment

3.4. Risk Management

3.5. Quality Assurance

3.6. Configuration Management Plan

3.6.1. ECPs and NORs

3.6.2. RFVs

3.6.3. Contractor CM Policy and Procedures

3.6.4. CM Data Distribution/Access

3.6.5. Configuration Identification

3.6.6. Configuration Control

3.6.7. Configuration Status Accounting (CSA) System

3.7. Data and Deliverables

3.7.1. Data Management

3.7.2. Data Delivery

3.8. Public Key Infrastructure (PKI)

3.9. GFI Management

3.10. GFP/E/M Management

3.11. Legacy Support [CLINS 0207, 0307, 0407, 0507, 0605, and 0705]

3.11.1. Integrated Logistics Support (ILS)

ii

3.11.2. Platform Support

3.11.3. ECP Development

3.12. Facilities

3.13. Security Requirements

3.13.1. System Security Program

APPENDIX A: TI18/APB19 AN/BYG-1 AND TCS DESIGN, INTEGRATION, TEST AND DELIVERY

A1. Scope ......................................................................................................................................................... A-1

A2. Systems Engineering ................................................................................................................................. A-1

Systems Engineering Management Plan (SEMP) ................................................................................. A-1

CI Enhancements, Studies, and Analysis .............................................................................................. A-2

A3. Post Award Conference (PAC) [CLIN 0001 only] ................................................................................... A-2

Transition Planning ............................................................................................................................... A-3

A4. Meetings, IPTs and Working Groups ........................................................................................................ A-3

A5. System Requirements ................................................................................................................................ A-3

Requirements Documentation ............................................................................................................... A-4

Interface Requirements Management ................................................................................................... A-4

A6. System Architecture and Design ............................................................................................................... A-4

Modular Open Systems Architecture (MOSA) Approach .................................................................... A-4

CSCI Design ......................................................................................................................................... A-4

Software Design Documents ................................................................................................................. A-5

Technical and Design Reviews ............................................................................................................. A-5

A7. HW ............................................................................................................................................................ A-6

A8. System Development................................................................................................................................. A-6

TCS SW Development .......................................................................................................................... A-6

Problem Reporting ................................................................................................................................ A-7

System Integration Planning ................................................................................................................. A-7

A9. Safety ........................................................................................................................................................ A-7

Safety Program ..................................................................................................................................... A-7

A10. Cybersecurity ............................................................................................................................................ A-8

A11. Test and Evaluation ................................................................................................................................... A-8

Test Conduct ......................................................................................................................................... A-9

Testing Support to the Government ...................................................................................................... A-9

System Delivery .................................................................................................................................. A-10

A12. Platform Support ..................................................................................................................................... A-10

AN/BYG-1 Integration ....................................................................................................................... A-10

Advance Development STEP .............................................................................................................. A-10

Delivery Requirements ....................................................................................................................... A-11

A13. Integrated Logistics Support ................................................................................................................... A-11 iii

IETM/ Ready Reference Manual (RRM) ............................................................................................ A-11

IETM and RRM Source Material Development ................................................................................. A-11

Integration of IETM/RRM Source Data ............................................................................................. A-11

IETM/RRM QA .................................................................................................................................. A-12

RRM/IETM Development Tasking..................................................................................................... A-12

System Note WG (SNWG) ................................................................................................................. A-12

Delivery Requirements ....................................................................................................................... A-12

Training and Training Support ............................................................................................................ A-12

Training Curriculum Development ..................................................................................................... A-12

Multipurpose Interactive Trainer (MIT) Development / Maintenance ............................................... A-12

Train-The-Trainer ............................................................................................................................... A-13

Preventative Maintenance System ...................................................................................................... A-13

Supportability Working Groups .......................................................................................................... A-13

ILS Plan .............................................................................................................................................. A-13

Supportability Analyses ...................................................................................................................... A-13

APPENDIX B: TACTICAL CONTROL DEVELOPMENT, INTEGRATION, TESTING AND DELIVERY

B1. Scope ..........................................................................................................................................................B-1

B1.1. Completion Criteria .............................................................................................................................. B-1

B2. System Engineering ...................................................................................................................................B-1

B2.1. Systems Engineering Management Plan ............................................................................................... B-1

B2.2. Engineering Documentation Database .................................................................................................. B-2

B2.3. Meetings, IPTs and WGs ...................................................................................................................... B-2

B2.4. System Requirements ............................................................................................................................ B-3

B2.5. Requirements Documentation ............................................................................................................... B-3

Interface Requirements Management ........................................................................................... B-3

System Architecture and Design ................................................................................................ B-43

Modular Open Systems Architecture (MOSA) Approach ....................................................... B-4

CSCI Design................................................................................................................................. B-4

Technical and Design Reviews .................................................................................................... B-4

B2.6. Safety Program ..................................................................................................................................... B-5

B2.7. Cybersecurity ........................................................................................................................................ B-5

B3. System Development..................................................................................................................................B-6

B3.1. TCS SW Development .......................................................................................................................... B-6

B3.2. Problem Reporting ................................................................................................................................ B-6

B3.3. SIP ......................................................................................................................................................... B-7

B4. Test and Evaluation ....................................................................................................................................B-7

B4.1. Test Conduct ......................................................................................................................................... B-7

B4.2. Testing Support to the Government ...................................................................................................... B-8 iv

B5. Platform Support ........................................................................................................................................B-8

B5.1. System Delivery .................................................................................................................................... B-8

B6. ILS ..............................................................................................................................................................B-9

B6.1. TCS ILS Products ................................................................................................................................. B-9

B6.2. IETM/RRM Source Material Development .......................................................................................... B-9

B6.3. Training Curriculum Source Data Development .................................................................................. B-9

B6.4. TCS Software Development in Support of MIT ................................................................................... B-9

B7. Facilities ...................................................................................................................................................B-10

B7.1. HSIT Facilities .................................................................................................................................... B-10

B7.2. Licenses .............................................................................................................................................. B-10

B7.3. Government Access to Contractor Facilities and Digital Environment .............................................. B-10

B8. Risk Management .....................................................................................................................................B-11

APPENDIX C: AN/BYG-1 COMBAT AND WEAPON CONTROL SUBSYSTEM INTEGRATION FOR

USN AND RAN SHARED

C1 Scope ......................................................................................................................................................... C-1

C1.1 Completion Criteria ....................................................................................................................................... C-1

C2 Integration Management ........................................................................................................................... C-1

1 Program Schedules .................................................................................................................................... C-1

C2.1.1 PPC ............................................................................................................................................................. C-1

Meetings, IPTs and WGs .......................................................................................................................... C-2

AN/BYG-1 Integration .............................................................................................................................. C-2

C2.3.1 External Program Engagement ................................................................................................................... C-2

C2.3.2 Advance Development STEP ..................................................................................................................... C-2

C2.3.3 Delivery Requirements ............................................................................................................................... C-3

C3 ILS ............................................................................................................................................................. C-3

IETM /RRM .............................................................................................................................................. C-3

C3.1.1 Integration of IETM/RRM Source Data ..................................................................................................... C-3

C3.1.2 IETM/RRM QA ........................................................................................................................................ C-3

C3.1.3 RRM Development Tasking ...................................................................................................................... C-4

C3.1.4 System Note Working Group (SNWG) ..................................................................................................... C-4

C3.1.5 Delivery Requirements .............................................................................................................................. C-4

Training and Training Support .................................................................................................................. C-4

C3.2.1 Training Curriculum Development ........................................................................................................... C-4

C3.2.2 MIT Development / Maintenance ............................................................................................................. C-4

C3.2.3 Train-The-Trainer (TTT) ........................................................................................................................... C-5

Preventative Maintenance System (PMS) ................................................................................................. C-5

Supportability Working Group (SWG) ..................................................................................................... C-5

ILSP .......................................................................................................................................................... C-5

Supportability Analyses (SA) .................................................................................................................... C-5 v

APPENDIX D: SHARED ENGINEERING AND TECHNICAL SERVICES FOR USN AND RAN

D1. Scope ......................................................................................................................................................... D-1

D2. Systems Engineering ................................................................................................................................. D-1

D2.1. Engineering Documentation Database .................................................................................................. D-1

D2.2. Studies and Analyses ............................................................................................................................ D-1

D2.3. Meetings, IPTs and WGs ...................................................................................................................... D-1

D2.4. System Requirements ............................................................................................................................ D-2

D2.5. Requirements Documentation ............................................................................................................... D-2

D2.6. Interface Requirements Management ................................................................................................... D-2

D2.7. Problem Reporting ................................................................................................................................ D-2

D2.8. Test Procedures ..................................................................................................................................... D-3

D3. System Architecture and Design ............................................................................................................... D-3

D3.1. MOSA Approach .................................................................................................................................. D-3

D3.2. System Design Documents ................................................................................................................... D-3

D4. System Development................................................................................................................................. D-3

APPENDIX E: ROYAL AUSTRALIAN NAVY UNIQUE DEVELOPMENT

E1. Scope ..........................................................................................................................................................E-1

E2. Systems Engineering ..................................................................................................................................E-1

E2.1. CI Enhancements, Studies and Analysis ................................................................................................ E-1

E2.2. Meetings, IPTs and WGs ....................................................................................................................... E-1

E3. TCS Software Development .......................................................................................................................E-2

E3.1. Production Software Development ........................................................................................................ E-2

E4. Test and Evaluation ....................................................................................................................................E-2

E4.1. Test Conduct .......................................................................................................................................... E-2

E5. Training and Training Support ...................................................................................................................E-3

APPENDIX F: TCS REARCHITECTURE

F1. Scope .......................................................................................................................................................... F-1

F1.1. Completion Criteria ............................................................................................................................... F-1

F2. TCS Architecture Study and Design .......................................................................................................... E-1

F3. Systems Engineering .................................................................................................................................. F-3

F4. Meetings, IPTs and WGs ........................................................................................................................... F-3

F5. System Requirements ................................................................................................................................. F-3

F6. Requirements Documentation .................................................................................................................... F-3

F7. System Architecture and Design ................................................................................................................ F-3

F7.1. MOSA Approach ................................................................................................................................... F-3

F8. System Design Documents ......................................................................................................................... F-4

F9. Technical and Design Reviews .................................................................................................................. F-4 vi

F10. Cybersecurity ............................................................................................................................................. F-5

F11. System Development.................................................................................................................................. F-5

F11.1. TCS Architecture Software Development ............................................................................................. F-5

F11.2. Architecture Demonstration ................................................................................................................... F-5

F12. Problem Reporting ..................................................................................................................................... F-5

ACRONYM LIST ...................................................................................................................................................... a

Statement of Work for the Tactical Control System

1. Scope

This SOW defines requirements to design, develop, integrate, test, and deliver the TCS for the AN/BYG-1

Submarine Combat Control System. TCS is a subsystem within the AN/BYG-1 Combat and Weapons Control

System, and is integrated with the Payload Control System (PCS). TCS will be hosted within the AN/BYG-1

Submarine Combat and Weapons Control System shipboard physical footprint for all USN and RAN new construction and in-service submarines.

This effort will include design, development and engineering services for the Technology Insertion (TI)-2018

Advanced Processor Build (APB)-2019, TI-20 APB-19, TI-20 APB-21, TI-22 APB-21, TI-22 APB-23 and TI-24

APB-23 for US (USN) and Royal Australian Navy (RAN) submarines. This effort also includes the integration of the TCS, PCS, Common Infrastructure Services (CIS), and Information Assurance (IA) Subsystems into the

AN/BYG-1 Submarine Combat Control System.

The TCS is an integrated subsystem of the larger AN/BYG-1 Combat and Weapons Control System. The primary function of the TCS system is to support Submarine mission sets by providing Command and Control tools to accurately localize and track contacts of interest, fuse various sensor/data inputs, and support contact management.

A typical configuration of TCS and AN/BYG-1 is provided in Figure 1.

Figure 1: Overview of TCS within the AN/BYG-1 Submarine Combat and Weapons Control System

TCS functionality and performance is defined by the applicable TCS System Performance Specification (P-SPEC).

The initial TCS configuration (TI-18 APB-19) performance is required to be equal to or better than the TI-18 APB-

17 baseline, with additional functionality as defined in the TI18 APB19 PSPEC, which will be provided upon contract award. While the new P-SPEC is not yet available, the rate of change from baseline to baseline can be assumed to be consistent with past P-SPEC updates as provided as Government Furnished Information (GFI).

The production effort included in this SOW includes growing the reliability of the APB TCS software (SW) on the

TCS hardware (HW) suite and porting existing APB SW onto a new TCS TI HW baseline. In an initial APB development year, the addition of new functionality and other significant changes are not expected following APB

Step testing. However, unplanned changes to development and integration do occur. In TI years, all new functionality and changes to existing functionality are introduced as part of the production effort associated with that TI/APB.

The Contractor will be responsible for integrating SW components delivered from multiple vendors into the TCS computing environment both in line with standard TI/APB modernizations and asynchronously. AN/BYG-1 is developed in a collaborative environment with a consortium of Navy, Navy Laboratories, Academia and other industry partners to ensure success of the program.

TCS will be developed for the following AN/BYG-1 system variants:

AN/BYG-1 System Variants

(V)1 VIRGINIA Class Blocks I and II SSNs 774-783

(V)2 688i SSNs 751-773

(V)5 OHIO Class Ballistic Missile SSBN 730-743

(V)6 SEAWOLF Class SSNs 21-23

(V)7 OHIO Class Guided Missile SSGNs 726-729

(V)8 RAN COLLINs Class SSGs 73-78

(V)9 VIRGINIA Class BLK III/IV SSNs 784-800

(V)10* VIRGINIA Class BLK V SSN 801 and up

(V)11* COLUMBIA Class SSBN 826-838

*Nomenclature not yet assigned. PMS425 will submit nomenclature request when Block V, COLUMBIA CLASS RFP and RAN Future Submarine is approved.

This SOW scope includes the design, development, delivery, and test of the TCS software required to support APB baselines 19, 21, and 23; each integrated and fully functional on TI HW baselines 18, 20, and 22. The SOW also includes engineering services required to TCS SW lifecycle support (including potential updates post-delivery) and integration of TCS, PCS, CIS, and IA into the AN/BYG-1 Combat and Weapons Control System. In general, the efforts include:

Provide end-to-end system engineering for development, integration, test, delivery, and life-cycle support for all TCS configurations for the duration of this contract.

Develop TCS configuration variants to support various platforms as applicable. Each initial delivery will include all baseline engineering documentation, product lists, logistics support products, curriculum and support materials, spares and installation and checkout spares as necessary to provide the as-developed product support, including trainers.

Support the management and oversight of system level test (SLT) and evaluation plans as part of

Command, Control Communications, Computers, Combat and Intelligence (C5I) system platform integration design/build team for all platform variants to include RAN Submarines.

Define the optimum balance of cost, schedule, and performance of simulation and stimulation equipment needed to execute subsystem level testing and integration.

Define the interface baseline including all requirements necessary to connect to the Submarine Warfare

Federated Tactical System (SWFTS) network and share information at the subsystem level.

Participate in SWFTS integration efforts including technology refresh/insertion planning and post-subsystem validation testing and integrations across SWFTS boundaries.

Support platform level Installation and Checkout planning requirements, including participation in

Installation Integrated Product Team (IPT), Modernization Plan and various reviews and working group

(WG) meetings.

Develop source material for Logistics Data, Interactive Electronic Technical Manual (IETM), Interactive

Courseware (ICW)/Computer Based Training (CBT) and Interactive Multimedia Instruction (IMI) using common authoring systems and formats to allow for efficient integration with SWFTS. This includes integrating source material as delivered by the interfacing shipboard subsystems contractors for integration for a complete TCS delivery.

Support installation, field integration, repair and refurbishment to include technical and other troubleshooting efforts as required.

Program, Contract and Financial management and oversight for the Contractor’s TCS program.

TCS external interface definition including the determination of all necessary requirements to connect to the SWFTS and provide connectivity among SWFTS subsystems and between SWFTS subsystems and external enclaves, including the RAN submarine combat system.

Participate in TI HW refresh planning, including support for TI HW resource estimations and product selection ensuring adequate computing resources are selected for TCS and hotel services (power, cooling, footprint) are provided in the AN/BYG-1 cabinets.

Develop, test, and support Government certification of the required Simulation/Stimulation product(s) required for TCS development, integration, and test.

Validate and assess TCS effectiveness, suitability and sustainability, including safety against system requirements.

Incorporate IA/Cybersecurity modifications and updates to support accreditations.

Coordinate with PCS, CIS and IA Contractors for AN/BYG-1 development, integration, and test.

1.1. Navy Organization

PEO SUB is the acquisition executive for this procurement. PMS425 is responsible for the acquisition, development, production, fleet introduction and support of the TCS for all classes of Submarines and appropriate

Joint Program Office efforts. The collaborative development environment has applicability to all Navy Combat

Systems processing environments for all host platforms and classes of ships both USN and allied forces for those common processing elements.

1.2. Background

Utilizing a collaborative development process originally introduced in Acoustics programs, PMS425 and Program

Executive Office, Integrated Warfare Systems (PEO IWS 5) jointly operate and maintain a Combat Systems

Research and Development (R&D) model to accelerate the transition of advanced development SW to the submarine Fleet. This concept, which provides progressive capability through APB SW, relies upon an Open

System Architecture (OSA) structure coupled with a second (2nd), complementary initiative involving periodic refreshes of Commercial Off the Shelf (COTS) HW. This second (2nd) initiative, the cyclical TI process, mitigates the impacts of obsolescence through the regular planned replacement or upgrade of older HW. Given advancements in power and capability with each HW generation (most notably in the microprocessor industry), the continual TI process introduces greater processing capacity and thereby a more capable and efficient “landing pad” for the SW APBs with each successive HW refresh.

To date, three (3) of the major submarine electronics Program Offices (PMS425, PMS401 and PMS435) follow this process and work cooperatively to systematically provide advanced capability for Combat and

Weapons/Payload Control, Acoustics, Imaging systems, and Electronic Warfare (EW), as well as the underlying computing infrastructure hosting it.

This contract follows the time-phased TI/APB cycle: A new APB SW baseline is developed in odd years and a new TI HW baseline is developed in even years. The primary focus of this procurement is the odd-year SW baseline development. The odd year SW baselines will be integrated into the current TI HW baseline at the time the SW baseline is development and the following year TI HW baseline update. This TI/APB time-phased cycle requires close collaboration with the Navy, Navy Laboratories, Academia, and other Government and industry partners. As such, TCS will follow APB naming convention for SW updates.

The following terminology will be used in relation to the TCS requirement:

Platform: An individual submarine.

Variant: The specific submarine class (or a submarine class separated by unique platform characteristics) that drives SW and/or HW differences.

Baseline: A HW baseline is the sum total of AN/BYG-1 system HW selected for a given TI cycle (i.e., TI-18). A SW baseline is the sum of approved functional capability for a given APB SW build (i.e., APB-

17). A baseline can also be a combined baseline (HW plus SW capability) such as TI-18/APB-17. A baseline is all-inclusive and not variant specific.

Configuration*: A variant plus the combined HW and SW baseline. Example: TCS (V)2 TI- 18/APB-17.

Capability Item (CI): A new capability that will be integrated into TCS. This capability may be developed by the TCS Contractor, or be provided as a Non-Developmental Item (NDI) by another developer.

Additionally, these items may be developed under the IWS5A Step process, or be developed as part of the production process for TCS. CI may also be used to refer to a significant update to an existing component of TCS. Requirements changes that do not require significant re-design of an existing capability are not considered CIs.

Integration: The process of combining multiple software components into one system and ensuring that the components function together as a system. This term is used for both the TCS Subsystem for combining multiple applications and software units into the TCS Subsystem, and for overall AN/BYG-1 integration for combining multiple AN/BYG-1 Subsystems (including, but not limited to TCS, PCS, IA, and (CIS into AN/BYG-1.

*Minor individual platform differences exist within system variants. The Contractor will be required to accommodate those platform-unique differences within each configuration for all products delivered under this contract for USN and RAN submarines.

1.3. System Overview

The TCS is a fully integrated, mission critical subsystem to the submarine Combat and Weapons Control System.

The TCS provides the Submarine platform the following functionality and services, among others:

Contact Management

Target Motion Analysis (TMA)

System Parameter Management

Off-Board Contact Management & Interoperability

Periscope Video ((V)8 Only)

Platform Command and Control

Rapid weapon and countermeasure engagement support

Operational Mission Planning

Unmanned Systems Integration

Collins Sensor Data Server (CSDS) ((V)8 only)

Training and Maintenance

Sensor Open System Interface/ Tactical Open System Interface SOSI/TOSI ((V)8 only)

Tactical Web Server / Reconstruction

The TCS SW operates on processing, display, and networking HW developed by the Tech Insertion Integrated

Product Team (TI IPT) and the TIH Contractor. The TCS contractor will participate in the TI IPT, and be provided with source control drawings (SCDs) for each new HW baseline.

1.4. Program Phasing

The scope of effort required to design, develop, deliver and support each TCS TI/APB configuration under this procurement is proportional to the number of different combat system configurations undergoing modernization change or requiring new construction installation over the Period of Performance (PoP) of this contract. The schedule including milestone dates for each TCS TI/APB configuration is documented in the PMS425 Integrated

Master Plan (IMP) provided as GFI in Attachment 2.

The execution of the TI-18/APB-19 transition, engineering, logistics, and management efforts for both TCS and

AN/BYG-1 Integration through initial delivery of all variants will be performed as described in Appendix A.

The development of the engineering, logistics, and management efforts for TCS for all other baselines covered by this SOW (TI-20 APB-21; TI-22 APB-21; TI-22 APB-23; and TI-24 APB-23) is detailed in Appendix B.

The Integration, Test, and Delivery of the integrated AN/BYG-1 system, including all engineering, logistics, and management efforts for TI-20 APB-21; TI-22 APB-21; TI-22 APB-23; and TI-24 APB-23 is described in

Appendix C.

The design and development of new CIs through Test Readiness Review (TRR) of will be executed under the

Engineering Services Level of Effort (LOE) Contract Line Item Number (CLIN) as detailed in Appendix D.

Specific requirements will be directed by Technical Instruction. The requirements and design details will be incorporated into engineering milestones reviews including System Requirements Review (SRR), Preliminary

Design Review (PDR), Critical Design Review (CDR), and TRR

RAN Unique development is covered in Appendix E.

The development of a new Architecture design for TI-20/APB-21 and later baselines shall support all variants and is described in Appendix F.

Once the Design Readiness Review (DRR) for the relevant TI/APB has been successfully completed, continued support for each configuration will transfer to its respective Engineering Services LOE CLIN. These completed

TCS baselines (termed “Legacy”) shall then be supported over the contract PoP under the Legacy LOE CLIN

(CLINs 0207, 0307, 0407, 0507, 0605, and 0705) designated for that specific configuration.

2. Requirements and Contractual Compliance

Initially, the work required by this contract shall meet the requirements of the P-SPEC for TCS Subsystem, PMS4253-TCSPS-002 dated 27 November 2017. This specification will be updated by PMS425 annually for each new TI/APB baseline and shall be used as the basis for work performed in accordance with this SOW and Other

Documents/Exhibits/Attachments listed in SECTION J and all provisions of this contract.

2.1. Applicable Documents

The following documents are applicable to this SOW and attached appendices to the extent specified herein:

DODI 8500.01

14 March 2014

Cybersecurity

DOD 8570.01-M Change 4

10 Nov 2015

IA Workforce Improvement Program

ISO/IEC/IEEE 12207-2017

Nov 2017

ISO/IEC/IEEE Standard for Systems and SW Engineering –

SW Life Cycle Process

OSA Contract Guidebook

13 June 2013

DoD Open System Architecture Contract Guidebook, V1.1

MIL-HDBK-61A (SE)

7 February 2001

Military Handbook: Configuration Management Guidance

MIL-STD-881C

3 October 2011

Work Breakdown Structures (WBS) for Defense Material Items

MIL-STD-882E

11 May 2012

Standard Practice for System Safety

NAS411 thru Rev.1

30 September 2013

Hazardous Materials Management Program

NAVSEA 9400.2

18 August 2010

Implementation of NAVSEA Afloat IA Governance and Guidance

NAVSEAINST 9410.2A

24 August 2012

Naval Warfare Systems Certification Policy

PMS425 CM Plan

01 December 2014

Submarine Combat and Weapons Control System

Program Office, Configuration Management Plan, Version 1.0

PMS425 ltr Ser 425/0092

23 March 2015

Information Assurance Vulnerability Management Policy for SWFTS

PMS425 IMP

17 May 2018

PMS425 Integrated Master Plan (IMP)

PMS425 Risk Management Plan

May 2013

Submarine Combat and Weapons Control System

Program Office, Risk Management Plan, Version 1.0

AN/BYG-1 SEP

15 December 2015

AN/BYG-1 Submarine Combat and Weapons Control System

Systems Engineering Plan (SEP), Version 1.1.3

SAFETY-SSMP-03

20 June 2017

PMS425 System Safety Management Plan (SSMP)

PMS425 WBS

11 March 2014

PMS425 Work Breakdown Structure (WBS)

P-SPEC System Performance Specification for the AN/BYG-1 Tactical Control

System TI18/APB19

AN/BYG-1 MOU Amendment 1

November 2009

Memorandum of Understanding (MOU) between the Department of

Defense (DoD), the United States of America, the DoD of Australia for the Cooperative Development, Production and Support of the

AN/BYG-1 Tactical and Weapons Control System

COMNAVWARCOM

Communications Tasking Order

(CTO) 11-16A

Secure Configuration Compliance Validation Initiative and

Vulnerability Remediation Asset Manager (VRAM) Requirement

SWFTS IA Baseline

Requirements Document

30 Nov 2016

TI-16 APB15 SWFTS & Submarine Tactical Systems Information

Assurance Baseline Requirements, Version 2

TMCR NO. SNIPP-160115-000

09 August 2018

Technical Manual (IETM) COMBAT CONTROL SYSTEM (CCS)

AN/BYG-1(V)X

TECHNICAL INSERTION XX (TIXX) ADVANCED PROCESSOR

BUILD XX

(APBXX) IETM reflecting organizational-level maintenance., ASD/AIA S1000D Issue 4.0.1 S1000D Specification International Specification for Technical

Publications Utilizing a Common Source Database;

https://public.s1000d.org/

MIL-PRF-29612B

31 August 2001

Performance Specification Training Data Products

TI-XX Installation Schedule TI-XX Installation Schedule 20180216_FOUO.xlsm

MIL-HDBK-1785 DOD SYSTEM SECURITY ENGINEERING PROGRAM

MANAGEMENT REQUIREMENTS

DoDD 5220.22-M National Industrial Security Program Operating Manual (NISPOM)

3. General Requirements

The following sections are applicable across all the CLINs performed under this contract, identified in either LOE

Technical Instructions or Completion Efforts. Additionally, the LOE and Completion Efforts have specific functional area requirements that are addressed separately in Appendices A through F. Tasking for legacy support under CLINS 0207, 0307, 0407, 0507, 0605, and 0705 will be provided by Technical Instruction and are described in section 3.11.

3.1. Program and Contract Management

The Contractor shall designate a single Program Manager (PM) who shall have responsibility for all aspects of this contract and shall have the authority to commit the Contractor to specific courses of action. The Contractor shall establish and maintain an integrated management control system to control costs and schedule for all work under all CLINs covered by the contract. The Contractor shall organize, coordinate, and control all services and supplies related to this contract including the identification and monitoring of subcontractor technical, quality, schedule and milestone achievements.

3.1.1. Contractor Performance Management and Progress Reporting

The Contractor shall prepare and deliver monthly Progress, Status, and Management Reports regarding all assigned tasks, report progress against milestones, report progress against contract incentives and identify technical or schedule problem areas or risks along with recommendations for resolution. [CDRL A001]

In addition to the monthly Progress, Status and Management Reports, the Contractor shall participate in an informal PM telephone meeting, generally not to exceed one (1) hour each week. The meeting will discuss current contract and financial status, identification of any potential issues or risks and recommendations for resolution, and progress toward contract deliverable schedules as defined in the Project Planning Chart (PPC).

3.1.2. Work Breakdown Structure (WBS)

The Contractor shall tailor the requirements of MIL-STD-881C to develop and maintain a TCS WBS that correlates cost and schedule performance with technical progress. The Contractor shall ensure the WBS extends down to the level required to provide adequate internal management, surveillance, performance measurement and financial management, regardless of the reporting level stipulated in the Contract for Government visibility. The

Contractor shall analyze the system requirements specified in the SOW and P-SPEC and shall use the PMS425

WBS as guidance (GFI, Attachment 2) to create a WBS structure representing the products and services that comprise the entire work effort under the contract. The Contractor shall ensure traceability to level three (3) of the

Government WBS. The Contractor, if necessary, shall update the WBS during the execution of the contract.

Changes to the WBS or associated definitions, at any reporting level, require approval of the Government. [CDRL

A002]

3.1.3. PPC

The PPC shall consist of key TCS program milestones, as derived from the PMS425IMP) provided as GFI

(Attachment 2). The PPC shall also include specific lower-level milestones for each TI/APB baseline consistent with the WBS. The PPC shall include efforts of all activities including subcontractors. Events of particular interest to the Government include, but are not limited to: receipt of GFI; Program Reviews; Technical Reviews; TCS and

SWFTS test events; TCS and SWFTS integration events; major acquisition milestones; delivery of SW upgrades with new functionality (including interim internal SW drops); and introduction and delivery events. [CDRL A003]

The Contractor shall use the PPC as a day-to-day execution tool and to periodically assess progress in meeting program requirements. The Contractor shall maintain and update the PPC to reflect Government-approved change requests or changes in the Contractor’s detailed execution activities or schedule. All Contractor schedule information delivered to the Government or presented at program reviews shall originate from the PPC. The

Contractor shall perform appropriate analyses of the PPC tasks and report potential or existing problem areas, risks, and recommend corrective actions to eliminate or reduce schedule impact.

3.1.4. Subcontract Management

The Contractor shall actively manage the performance and quality of all work performed under subcontract.

Appropriate prime contract requirements shall be flowed down to all subcontractors. The Contractor shall invite

Government contracting and technical representatives to participate in Subcontractor visits and reviews. The

Contractor shall provide fifteen (15) working days’ advance notice to the Government Contract Administrative

Contracting Officer and/or Procuring Contracting Officer (PCO) and designated Government technical representatives prior to planned Subcontractor visits and reviews. Attendance at these reviews or tests is optional on the part of the Government and failure of the Government representative to attend shall not constitute an excusable delay on the part of the Contractor.

3.1.5. Program Reviews

The Contractor shall conduct Quarterly Program Reviews (QPRs) and Quarterly Financial Reviews (QFRs) every three (3) months at its facility or alternate Government facility per direction of the Government for a period not to exceed one (1) day. The QPR may be combined with other AN/BYG-1 Subsystems’ QPRs to provide a unified program status.

An informal “read-ahead” brief shall be provided electronically to the Government ten (10) working days prior to the review, and the final five (5) days prior to review. [CDRLs A004 & A005]

3.1.5.1. QPR

The purpose of the QPR is to ensure the Contractor’s approach and progresses are technically sound, meet the requirements, and are mutually understood and properly documented. At each QPR, the Contractor shall report status, issues, risks and recommendations for the following items (at a minimum) for all exercised CLINs:

Schedule progress against the PPC (three (3) month history and six (6) months projected)

Contract deliverables completed and projected (three (3) month history and six (6) months projected)

Technical and program status and metrics

Integration, test and evaluation activities

Logistics source data development and support efforts

Risk analysis activities

Quality program status

Safety program status

Government Furnished Property (GFP) and GFI status

Proposed changes to the Program baseline

3.1.5.2. QFR

The purpose of the QFR is to ensure the Contractor has adequate financial resources and planning to execute the contract. At each QFR, the Contractor shall report status of the following (at a minimum) for all exercised CLINs:

Cost/Schedule performance and variances against plan

Financial projection/actual (three (3) month history, six (6) month future)

Staffing Plan evaluation to include Key Personnel

Performance against the contract incentives

Risk analysis activities

3.1.6. Meeting Support

The Contractor shall prepare agendas for Contractor-hosted meetings, program reviews, IPTs and all other meetings/reviews. The agendas shall be provided by the Contractor via electronic mail (E-mail) two (2) weeks prior to meetings and shall be jointly developed between the Government and Contractor. [CDRL A004]

The Contractor shall be capable of hosting in-person meetings up to the SECRET level.

The Contractor shall have the capability to support controlled access to Voice and Web Conferencing up to the

SECRET level. The Contractor shall provide the web-teleconference connection to those offsite and required to attend. The web- teleconference information shall be provided by the Contractor via E-mail one (1) week prior to the meetings.

The Contractor shall maintain the capability to participate in face-to-face coordination meetings and telephone conversations with the Government program office, Technical Direction Agent (TDA), and other PMS 425 and

SWFTS contractors. The Contractor shall plan for a minimum of four (4) face-to-face meetings each fiscal year, with travel to the Washington Navy Yard (WNY), Naval Undersea Warfare Center Division…