Attachment_1_-_Appendix_G_Eng_Svcs_(DRAFT).doc

N00024-18-NR-98173

APPENDIX G TO ATTACHMENT 1

APPENDIX G

TO

ATTACHMENT 1

Engineering Support Services and Studies [CLINs 0001-0004, 0101-0104, 0201-0204, 0301-0304, 0401-0404, 0501–0504, 0601-0604, 0701-0704]

TABLE OF CONTENTS

11.

SYSTEMS ENGINEERING

11.1 Engineering Documentation Database

11.2 Studies and Analyses

11.3 Meetings, Integrated Product Teams and Working Groups

21.4 System Requirements

21.4.1 Requirements Documentation

21.4.2 Interface Requirements Management

31.4.3 System Architecture and Design

42.

SYSTEM DEVELOPMENT

42.1 PCS SW Development

42.2 Problem Reporting

42.2.1 Test Procedures

Statement of Work for

Engineering Support Services and Studies [CLINs 0001-0004, 0101-0104, 0201-0204, 0301-0304, 0401-0404, 0501-0504, 0601-0604, 0701-0704] The Contractor shall provide a level of engineering and technical services supporting the development, sustainment, and maintenance of on-going Technology Insertion (TI) efforts as well as other engineering and analysis tasks as requested by the Government and authorized under Technical Instructions. The level of engineering and technical services shall support United States Navy (USN) variants, common efforts for Royal Australian Navy (RAN), and RAN-unique requirements. The efforts shall include approved Capability Improvements (CIs), Fleet and new construction problem assessment and adjudication; configuration control; software (SW), hardware (HW) and logistics troubleshooting; and End of Life (EoL) issue assessment. Efforts shall also include engineering support for other unique studies and analysis, not associated with the specific TI/APB development efforts defined in Appendices A through F, which may be required during the Period of Performance (PoP) of this contract.

The following Statement of Work (SOW) provides the summation of the two (2) elements efforts:

1) The Contractor shall conduct the Systems Engineering (SE) effort for TI-20/APB-21, TI-22/APB-21, TI-22/APB-23, TI-24/APB-23, TI-24/APB-25 and TI-26/APB-25 authorized approved CIs through Test Reading Review (TRR) under the applicable Engineering Support Services and Studies Contract Line Item Numbers (CLINs). The approved CI shall be supported for USN variants, common efforts for RAN, and/or RAN-unique requirements. During this phase of development, the engineering, logistics, and management efforts and other associated tasks shall be conducted under the applicable TI/APB CLIN. The Contractor shall conduct test and delivery efforts for the approved CIs under the applicable TI/APB USN/RAN Shared or RAN Unique CLINs.

2) The Contractor shall provide support to the TI-20/APB-21, TI-22/APB-21, TI-22/APB-23, TI-24/APB-23, TI-24/APB-25 and TI-26/APB-25 configurations after completion of the initial variant Delivery Readiness Review (DRR) (Legacy Support).

1. SYSTEMS ENGINEERING

The Contractor shall provide a SE Lead for the engineering efforts under this contract. The SE Lead shall ensure the application of disciplined SE processes and Integrated Process and Product Development (IPPD) principles toward all legacy and other efforts as authorized under Technical Instruction.

1.1 Engineering Documentation Database

The Contractor shall update and maintain the Contractor Integrated Digital Environment (IDE) databases (i.e. Dynamic Object-Oriented Requirements System (DOORS) in support of effort through TRR for authorized CIs and post-DRR (Legacy) changes to the TI-20/APB-21, TI-22/APB-21, TI-22/APB-23, TI-24/APB-23, TI-24/APB-25 and TI-26/APB-25 requirements, plans and procedures [CDRL A016]

1.2 Studies and Analyses

The Contractor shall deliver and/or assist the Government in developing strategies and studies, performing SE analysis, and developing implementation plans to ensure legacy Payload Control System (PCS) configurations meet and/or sustain the specified performance. [CDRLs A010 and A011]

1.3 Meetings, Integrated Product Teams and Working Groups

The Contractor shall participate in and/or support the following Government-established Integrated Product Teams (IPTs) and Working Groups (WG) supporting design, legacy configuration updates, integration, installation and performance assessment:

a) AN/BYG-1 System Engineering Integrated Product Team (SEIPT)

b) AN/BYG-1 Requirements Architecture Design Working Group (RADWG)

c) AN/BYG-1 Integration and Test Working Group (ITWG)

d) AN/BYG-1 Integrated Logistics Support Working Group (ILSWG)

e) AN/BYG-1 Problem Trouble Report (PTR) Review Board

f) SWFTS Architecture Working Group (SAWG)

g) SWFTS Systems Engineering Working Group (SEWG)

h) Technology Insertion IPT (TI IPT)

i) Integration IPT (I&T IPT)

j) Installation IPT

k) VIRGINIA Class and COLUMBIA Class new construction technical team meetings and Platform Integration Teams (PITs)

l) Submarine Combat System Combined Safety Working Group; the SW System Safety Technical Review Panel (SSSTRP); and the Weapons System Explosives Safety Review Board (WSESRB)

m) Design reviews and working groups for the design and development of the AN/BYG-1 TI HW baselines

1.4 System Requirements

The Contractor shall deliver and/or assist the Government in defining, assessing and documenting capability and requirements changes for the TI-20/APB-21, TI-22/APB-21, TI-22/APB-23, TI-24/APB-23, TI-24/APB-25 and TI-26/APB-25 configurations. Capability changes to these configurations shall be adjudicated and authorized by the Government via Technical Instruction. The Contractor shall maintain the PCS requirements in the Contractor IDE database (i.e., DOORS) with updates required for the TI-20/APB-21, TI-22/APB-21, TI-22/APB-23, TI-24/APB-23, TI-24/APB-25 and TI-26/APB-25 configurations.

The Contractor shall develop and deliver the TI-20/APB-21, TI-22/APB-21, TI-22/APB-23, TI-24/APB-23, TI-24/APB-25 and TI-26/APB-25 PCS capabilities as approved and authorized by the Government.

The Contractor shall assist in coordinating efforts between modernization and new construction VIRGINIA Class programs to target and support a common (to the extent practicable) TI-20/APB-21 baseline for installation during new construction. This shall include efforts for functional requirements determination and interface definition. The Contractor shall assist in reviewing and providing PCS inputs for all applicable VIRGINIA Class Block IV TI-20 new construction ship specifications and Functional Requirements Documents (FRDs).

1.4.1 Requirements Documentation

The Contractor shall develop and provide updates of the following requirements documentation for legacy PCS configurations based on changes adjudicated and authorized by the Government:

· System/Subsystem Specifications (SSS) [CDRL A017]

· Specification Requirement Verification Matrix (SRVM) [CDRL A018] The Contractor shall document the specific weapon/payload tubes and launcher equipment provided as Government Furnished Equipment (GFE) (Attachment 5) that will be utilized for each test in the SRVM.

To support development of the SRVM, the Contractor may elect to review the TI-16/APB-15 SSS and SRVM requirements documentation that is maintained on AIMTC.

1.4.2 Interface Requirements Management

For legacy changes, the Contractor shall continue to manage interface requirements and ensure PCS interface integrity, based on changes adjudicated and authorized by the Government, in accordance with the processes established by the Government-approved Contractor SEMP [CDRL A015] and System/Subsystem Design Description (SSDD) [CDRL A019] originally provided for TI-20/APB-21 development.

The Contractor shall interact with the Submarine Warfare Federated Tactical Systems (SWFTS) subsystems and weapons/payload/launcher systems to ensure continued compliance with the Interface Control Drawings (ICDs), Interface Requirements Documents (IRDs), and Interface Requirements Specifications (IRSs), including weapons and payloads, as defined in the PCS Performance Specification (P-SPEC) (provided as GFI, Attachment 4).

The Contractor shall manage interface change activity and participate in the SWFTS Baseline Management System. The Contractor shall notify the Program Office of any required Non-Propulsion Electronics System (NPES) Baseline Change Requests (NBCRs) required to support PCS external interface changes. The Contractor shall create NBCRs as directed by the Program Office. The Contractor shall evaluate NBCRs submitted by other SWFTS systems for impact to the PCS. The Contractor shall also initiate appropriate interface change requests for other interface specifications, including weapons and payload when updates are required.

1.4.3 System Architecture and Design

1.4.3.1 Modular Open Systems Architecture Approach

The Contractor shall establish and maintain a Modular Open Systems Architecture (MOSA) approach in accordance with the requirements of the DoD Open System Architecture Contract Guidebook, v1.1. The Contractor shall ensure the following system architecture characteristics are maintained for legacy PCS configurations:

a) Open Architecture - The Contractor shall develop and maintain a PCS architecture that incorporates appropriate considerations for re-configurability, portability, maintainability, TI, vendor independence, reusability, scalability, interoperability, upgradeability, and long-term supportability.

b) Modular, Open Design – The Contractor shall develop and maintain a PCS architecture that is layered and modular and uses Commercial Off-the-Shelf/ Non-Developmental Item (COTS/NDI) HW, operating systems, and middleware that utilizes non-proprietary or non-vendor-unique, key Application Programming Interfaces (APIs). The Contractor’s design approach shall be applied to all subsystems and components. The Contractor shall provide the Government (and/or Government support contractors) electronic access to its integrated development environment throughout the term of the contract.

c) MOSA –The Contractor’s design approach shall produce a system that consists of hierarchical collections of SW and HW CIs (components). These components shall be of a size that supports competitive acquisition as well as reuse. The Contractor’s design approach shall emphasize the selection of components that are available commercially or within the DoD, to avoid the need to redevelop products that already exist and that can be re-used.

For any changes to legacy PCS baselines, the Contractor shall ensure frequent and continuous design disclosure to Navy designated third-party (3rd) developers throughout the development/upgrade process.

1.4.3.2 System Design Documents

The Contractor shall provide for the update and delivery of the following design documentation for legacy PCS configurations based on changes adjudicated and authorized by the Government:

· System/Subsystem Design Description (SSDD) [CDRL A019]

· SW Requirements Specifications (SRSs) [CDRL A020]

· SW Design Description (SDD) [CDRL A021] The Contractor shall ensure the above documents fully describe the changes, if any, to the overall SW Computer SW Configuration Item (CSCI) structure, functional flows and interface requirements, including external PCS interface requirements. The Contractor shall update the separate variant or platform sections as required due to unique variant or platform requirements changes.

The Contractor shall also generate SWFTS-level interface documentation changes, including Group Requirements Lists (GRLs), as required to support legacy PCS configuration changes.

2. SYSTEM DEVELOPMENT

2.1 PCS SW Development

The Contractor shall maintain its SW engineering process in support of the PCS CIs and legacy configurations.

The Contractor shall provide updates to the SW Development Plan (SDP) as required to accommodate modifications in processes driven by, or additional processes required to support, the legacy configuration changes. The Contractor shall manage, develop, update, test and deliver the authorized PCS computer SW updates in accordance with the SDP. [CDRL A023] The Contractor shall provide the following SW development services for the CI changes and for new legacy builds driven by changes authorized by the Government:

· Execute Code and Unit Test (CUT)

· Perform code review

· Assess, adjudicate, and resolve PTRs

· Generate and deliver SW builds as necessary to support SW development and integration requirements [CDRL A024]

· Generate SW Version Description (SVD) documents for the generated SW builds [CDRL A025]

· Generate SW configuration build procedures

· Provide IAVM support

2.2 Problem Reporting

The Contractor shall maintain a single PTR system for the identification, tracking and resolution of all PCS SWand baseline documentation problems identified prior to and post Release to Fleet (RTF). In addition, the PTR system shall be used to track test documentation problems and technical manual errors. The Contractor shall ensure the Government has full real-time access to the database.

The Contractor shall co-lead the AN/BYG-1 PTR Review Board (PTRB) with the government to assess, adjudicate, and provide recommendations to the Government. The Contractor shall use NAVSEAINST 9410.02 in providing PTR classification recommendations. The Government will designate and approve final classification of PTR severity. The Contractor shall provide support and conduct a technical assessment in adjudication of the PTR; however, the Government will determine which PTRs to authorize for correction during the integration and test events including incorporation into SW builds. A synopsis of all problems identified under this PTR system shall be included with the monthly Integrated Program Management Report (IPMR). The PTR shall reference applicable requirements, system notes, any other applicable interface system PTR (Ex. Tactical Control PTR) and COATs Common Problem Reports. For PTRs adjudicated by the Government as requiring a System Note, the Contractor shall provide data supporting Ready Reference Manual (RRM) preparation. For PTRs adjudicated as requiring a Hazard Analysis Report (HAR), the Contractor shall provide input to the PMS425 Principal for Safety for preparation of the HAR.

The Contractor shall support the VIRGINIA Class CPR Adjudication Board for new construction TI/APB configurations.

2.2.1 Test Procedures

The Contractor shall review the applicable PCS legacy configuration Test Procedures and update and deliver new procedures as required to support legacy configuration changes. [CDRL A027]