Attachment_1_-_CIS_SOW.pdf

N00024-16-R-6414

ATTACHMENT 1

STATEMENT OF WORK

FOR THE

COMMON INFRASTRUCTURE SERVICES

SUBSYSTEM

DEPARTMENT OF THE NAVY

PROGRAM EXECUTIVE OFFICER, SUBMARINES

SUBMARINE COMBAT AND WEAPONS CONTROL SYSTEMS (PMS425)

1333 ISAAC HULL AVENUE SE

WASHINGTON, NAVY YARD

WASHINGTON, DC 20376

10 June 2016 i

TABLE OF CONTENTS

1. SCOPE 1

1.1 Navy Organization 2

1.2 Background 2

1.3 System Overview 3

1.4 Program Phasing 4

2. REQUIREMENTS AND CONTRACTUAL COMPLIANCE 5

2.1 Applicable Documents 5

2.1.1 Specifications and Standards (NAVSEA) (AUG 1994) 5

2.1.2 Applicable Documents 5

3. GENERAL REQUIREMENTS 7

3.1 Program and Contract Management 7

3.1.1 Post Award Conference (PAC) 7

3.1.2 Contractor Perfromance Management and Progress Reporting 7

3.1.3 Contract Work Breakdown Structure (CWBS) 8

3.1.4 Integrated Master Schedule 8

3.1.5 Subcontract Management 8

3.1.6 Program Reviews 9

3.1.7 Meeting Support 9

3.2 Systems Engineering 10

3.2.1 Systems Engineering Management Plan (SEMP) 10

3.2.2 Engineering Documentation Database 11

3.2.3 Capaility Item Enhancements, Studies and Analysis 11

3.2.4 Meetings, Integrated Product Teams (IPTs) and Working Groups (WGs) 11

3.2.5 System Requirements 12

3.3 System Development 15

3.3.1 CIS Software Development 15

3.3.2 Problem Reporting 16

3.3.3 System Integration Planning 16

3.3.4 Safety 17

3.3.5 Information Assurance (IA) 17

3.4 Test and Evaluation 17

3.4.1 Test Conduct 18

3.4.2 Testing Support to the Government 18

3.5 Platform Integration 18

3.5.1 System Delivery 18

3.6 Integrated Logistics Support 19

3.6.1 Interactive Electronic Technical Manual (IETM) 19

3.6.2 Training and Training Support 19

3.6.3 Preventative Maintenance System (PMS) 19

3.7 Facilities 19

ii

3.7.1 Hardware/Software Integration and Test (HSIT) Facilities 19

3.8 Licenses 20

3.9 Government Access to Contractor Facilities and Digital Environment 20

3.10 Risk Management 21

3.11 Quality Assurance (QA) 21

3.12 Configuration Management 21

3.12.1 ECPs and NORs 21

3.12.2 Requests for Variance (RFV) 22

3.13 Data and Deliverables 22

3.13.1 RESERVED 22

3.13.2 Data Management 22

3.13.3 Data Delivery 22

3.13.4 Public Key Infrastructures 23

3.14 Government Furnished Information (GFI) Management 24

3.15 Government-Furnished Property/Equipment/Material (GFP/E/M) Management 24

ATTACHMENT 1

STATEMENT OF WORK

FOR THE

COMMON INFRASTRUCTURE SERVICES (CIS)

1. SCOPE

This Statement of Work (SOW) defines the effort required to design, develop, integrate, test, and deliver the Common Infrastructure Services (CIS) Subsystem for Technology Insertion (TI)-2018 Advanced Processor Build (APB)-2017, TI-18 APB-19, TI-20 APB-19, TI-20 APB-21 and TI-22 APB-21 for all applicable variants. CIS is being developed as a new independent subsystem within the Submarine Warfare Federated Tactical System (SWFTS), and will be provided hotel services within the AN/BYG-1 Submarine Combat and Weapons Control System shipboard physical footprint for all U.S. Navy (USN) new construction and in-service submarines and Royal Australian Navy (RAN) submarines.

The Contractor shall ensure CIS functionality and performance is in accordance with the applicable System Performance Specification for CIS Subsystem. The Contractor can assume for their initial CIS configuration (TI-18 APB-17) performance is required to be equal to or better than the TI-16 APB-17 baseline, with additional functionality as required by Technical Instruction.

The production effort included in this SOW shall include growing the reliability of the Step-tested APB CIS software on the CIS hardware suite and porting existing APB software onto a new CIS TI hardware baseline. In an APB year, the addition of new functionality and other significant changes are not expected following APB Step testing. However, the Contractor shall include a plan to address unplanned changes in their development and integration plans. 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 software components delivered from multiple vendors into the CIS computing environment both in line with standard TI/APB modernizations and asynchronously. It is imperative the Contractor demonstrate the ability to work in a collaborative environment with a consortium of Navy, Navy Laboratories, Academia and other industry partners to ensure success of the program. All tasks defined herein shall be accomplished and delivered in accordance with the IMP.

The Contractor shall support new development and legacy CIS efforts for the following CIS system variants:

BYG-1/CIS (V)1: VIRGINIA Class Blocks I and II (SSNs 774-783) BYG-1/CIS (V)2: 688i (SSNs 751-773) BYG-1/CIS (V)5: OHIO Class Ballistic Missile (SSBNs 730-743) BYG-1/CIS (V)7: OHIO Class Guided Missile (SSGNs 726-729) BYG-1/CIS (V)8: Royal Australian Navy COLLINS Class (SSGs 73-78) BYG-1/CIS (V)9: VIRGINIA Class BLK III/IV (SSNs 784 -800) BYG-1/CIS (V)10* VIRGINIA Class BLK V (SSN 801 and up) BYG-1/CIS (V)11* OHIO Relacement

* Nomenclature not yet assigned. PMS425 will submit nomenclature request when Block V and OR RFP is approved.

The scope covered by this SOW includes efforts for system requirements definition, design, development, integration, and test through fielding and life cycle support. In general, these efforts include the following:

“End to end” system engineering for development, integration, test, delivery, and life-cycle support for all CIS configurations for the duration of this Period of Performance (PoP)

Integration of new CIS software onto TI hardware suites Porting of CIS software onto a new TI hardware suite Program, Contract and Financial management and oversight for the Contractor’s CIS program CIS 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.

Integration and test of CIS integrated components including, but not limited to, CIS System Status, Interactive Electronic Technical Manual (IETM), System of System (SoS) services, SoS monitoring tools, training applications, and providing the landing pad architecture for future application hosting.

Integration and test of the CIS with other SWFTS subsystems including, but not limited to, the Tactical Control System (TCS), SONAR (ARCI), Imaging (ISIS), Electronic Warfare (EW) and Information Assurance (IA).

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

Re-architecture and modernization of SoS Infrastructure components in accordance with needs identified by SWFTS Architecture team to enable more flexible and seamless updates to capability at a reduced cost, including tailoring of the design for RAN submarine combat systems

Development of CIS and other SoS logistics source data and the integration, test, publish, and delivery of the SWFTS CIS IETM for USN and RAN

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

Participate in platform-level integration and test of the CIS system with other external-interfacing electronic subsystems for USN and RAN submarines

Technical/troubleshooting support as required for modernization and new construction system installation and test periods

Provide CIS software and logistics product support post-Delivery Readiness Review (DRR) Validation and assessment of CIS effectiveness, suitability and sustainability, including safety

1.1 Navy Organization

The Program Executive Officer, Submarines (PEO SUB) is the acquisition executive for this procurement. The Submarine Combat and Weapons Control Systems Program Office (PMS425), in coordination with the SWFTS program office, SUB-S, is responsible for the acquisition, development, production, fleet introduction and support of the CIS for all classes of U.S. Navy submarines. Under a cooperative development program with the Royal Australian Navy (RAN), the CIS development, test, integration and life-cycle support efforts under this acquisition will also support RAN COLLINS Class submarines.

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 software to the submarine Fleet. This concept, which provides progressive capability through APB software, relies upon an Open System Architecture (OSA) structure coupled with a second, complementary initiative involving periodic refreshes of Commercial Off the Shelf (COTS) hardware. This second initiative, the cyclical TI process, mitigates the impacts of obsolescence through the regular planned replacement or upgrade of older hardware. Given advancements in power and capability with each hardware generation (most notably in the microprocessor industry), the repetitive TI process provides the opportunity to introduce greater processing capacity and thereby a more capable and efficient “landing pad” for the software APBs with each successive hardware 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. The collaborative development of CIS, specifically in regard to computing infrastructure and SoS services, will be executed in partnership with PEO SUB-S (SWFTS).

The CIS efforts under this procurement shall follow the time-phased TI/APB cycle whereby a new APB software baseline is generated in odd years and a new TI hardware baseline in even years. The odd-year software baselines, the primary focus of this procurement, are integrated into both the prior-year and next-year TI hardware baselines.

It is essential that the Contractor conduct the efforts required under this CIS procurement following the TI/APB process and working within the supporting collaborative development environment of the Navy, Navy Laboratories, Academia and other Government and industry partners. CIS will integrate advanced development APB software products from PEO IWS 5 that will include SoS functions such as enhanced learning or training tools, supporting SoS services, and/or SoS monitoring aids. As such, CIS will follow the TI/APB cycle and APB naming convention for software updates.

For the purposes of this SOW, the following terminology will be used in relation to the CIS efforts to be performed by the Contractor.

Platform: An individual submarine Variant: The specific submarine class (or a submarine class separated by unique platform characteristics) that drives software and/or hardware differences Baseline: A term applied to either software or hardware or a combination of both. A hardware baseline is the sum total of CIS system hardware selected for a given TI (i.e., TI-16). A software baseline is the sum of approved functional capability for a given APB software build (i.e., APB-17). A baseline can also be a combined baseline (hardware plus software capability) such as TI-16/APB-17. A baseline is all-inclusive and not variant specific.

Configuration: A variant plus the combined hardware and software baseline. Example: CIS (V)2 TI-

18/APB-17.

Please note that minor individual platform differences also exist within system variants. The contractor shall be required to accommodate those platform-unique differences within each configuration for all products delivered under this SOW for USN and RAN submarines.

1.3 System Overview

The CIS is an integrated suite of System of System (SoS) applications and services, the underlying computing environment hosting them, and the SWFTS Network backbone (i-Net). The vast majority of SWFTS subsystems connect to each other and to external enclaves via i-Net. The solution will also need to be adapted for the RAN submarines, with the aim to minimize any unique development efforts unless a compeling case can be provided to do so.

The CIS is a fully integrated, mission critical subsystem that provides SWFTS-connected subsystems with SoS infrastructure services including, but not limited to:

Directory Services via Lightweight Directory Access Protocal (LDAP) Mediation Services Time Distribution Print Services Video Distribution

Reliability Monitoring Intersubsystem Monitoring Tool via (ISMT) On Board Team Training – Master Controller via (OBTT-MC) Data Archiving Information Assurance (IA) Landing pad architecture for future application hosting

The CIS software shall operate on processing, display and networking hardware procured via separate contract vehicles with other industry partners and shipbuilders. No shipboard hardware procurement is planned for this contract. However, the Contractor shall be responsible for procuring developmental and Simulation/Stimulation laboratory assets supporting each TI/APB baseline and disclosing the design in accordance with (IAW) the System Engineering Plan (SEP). Additionally, the Contractor shall support the TI-20 and TI-22 hardware refreshment process in decomposing subsystem requirements to specific technology hardware and infrastructure requirements and assessing and selecting candidate hardware. Any tactical system hardware that is required to support the Contractor's Government-approved development, test and integration approach, shall be provided as Government Furnished Equipment (GFE) following contract award and shall be maintained as GFE under the provisions of the contract.

1.4 Program Phasing

The scope of services required to design, develop, deliver and support each CIS 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 PoP of this contract.

The table below is the expected development schedule and variants across years of the contract PoP. All CIS baselines shall be supported over the contract PoP.

Sept

Dec

Jan

Apr

May

Aug

Sept

Dec

Jan

Apr

May

Aug

Sept

Dec

Jan

Apr

May

Aug

Sept

Dec

Jan

Apr

May

Aug

Sept

Dec

Jan

Apr

May

Aug

Sept

Dec

Jan

Apr

May

Aug

Sept

Dec

Jan

Apr

May

Aug

TI‐18/APB17

TI‐18/APB19

TI‐20/ APB19

TI‐20/APB21

TI‐22/APB21

Contract CLINs Option Year 6

CLIN 0601

CLIN 0603

(V) 2, 5, 6, 8

(V) 2, 5,7, 8

(V) 2, 5, 7, 8

(V) 1, 9, 10, 11

(V) 1, 9, 10, 11

Base

CLIN 0001

CLIN 0005

Option Year 1

CLIN 0101

CLIN 0103

Option Year 2

CLIN 0201

CLIN 0203

Option Year 3

CLIN 0301

CLIN 0303

Option Year 4

CLIN 0401

CLIN 0403

Option Year 5

CLIN 0501

CLIN 0503

Figure 1: CIS Configuration, Variants and Contract Years

NOTE: The number of variants in each TI/APB is subject to change depending on platform modernization schedules.

CIS engineering, logistics, and management efforts will be performed as described in this document. The System Engineering Contract Data Requirements List (CDRL) development and delivery shall be executed under the applicable Technical Instruction (TI) Engineering Services Contract Line Item Numbers (CLINs). The requirements and design details shall be incorporated into engineering milestones reviews including System Requirements Review (SRR), Preliminary Design Review (PDR), Critical Design Review (CDR), Test Readiness Review (TRR) and

DRR.

The CIS TI-18/APB-19 engineering, logistics, and management efforts, including upgrades associated with APB-19 developed by IWS5A, shall be conducted as part of the requirements specified in this document and executed using the same approach as TI-18/APB-17.

The CIS TI-20/APB-19 engineering, logistics, and management efforts, including upgrades associated with TI-20, shall be conducted as part of this document and executed using the same approach as TI-18/APB-17.

The CIS TI-20/APB-21 engineering, logistics, and management efforts, including upgrades associated with APB-21 developed by IWS5A, shall be conducted as part of the requirements specified in this document and executed using the same approach as TI-18/APB-17.

The CIS TI-22/APB-21 engineering, logistics, and management efforts, including upgrades associated with APB-21 developed by IWS5A, shall be conducted as part of the requirements specified in this document and executed using the same approach as TI-18/APB-17.

2. REQUIREMENTS AND CONTRACTUAL COMPLIANCE

The work required by this contract shall meet the requirements of the Draft System Performance Specification (P- SPEC) for CIS Subsystem, PMS425C7-CIS-0216 dated 30 June 2016 (Attachment 9) and shall be 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

2.1.1 Specifications and Standards (NAVSEA) (AUG 1994)

(a) Definitions.

(i) A “zero-tier reference” is a specification, standard, or drawing that is cited in the contract (including its attachments).

(ii) A “first-tier reference” is either: (1) a specification, standard or drawing cited in a zero-tier reference, or (2) a specification cited in a first-tier drawing.

(b) Requirements.

All zero-tier and first-tier references, as defined above, are mandatory for use. All lower tier references shall be used for guidance only.

2.1.2 Applicable Documents

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

AN/BYG-1 MOU Amendment 1 Memorandum of Understanding between the Department of Defense of November 2009 the United States of America and the Department of Defence of

Austalia for the Cooperative Development Production and Support of The AN/BYG-1 Tactical and Wespon Control System

COMNAVNETWARCOM

Communications Tasking Order

(CTO) 11-16A

Secure Configuration Compliance Validation Initiative and Vulnerability Remediation Asset Manager (VRAM) Requirements

September 2011

DODD 8500.01

14 March 2014

Information Assurance (IA)

DOD 8570.01-M

19 December 2005

Information Assurance Workforce Improvement Program

ISO/IEC/IEEE 12207-2008

21 March 2008

ISO/IEC/IEEE Standard for Systems and Software Engineering – Software Life Cycle Processes

OSA 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 for Defense Materiel Items

MIL-STD-882E

11 May 2012

Standard Practice for System Safety

NAS411 thru Rev. 3 30 September 2013

Hazardous Materials Management Program

NAVSEA 9400.2

18 August 2010

Implementation of NAVSEA Afloat IA Governance and Guidance

NAVSEAINST 9410.02A

24 August 2012

Naval Warfare Systems Certification Policy

PMS425 Configuration Management Plan 22 January 2014

Submarine Combat and Weapon Control System Program Office Configuration Management Plan Version 1.0

PMS425 ltr Ser 425/0092 dated 23 March 2015

Information Assurance Vulnerability Management Policy for SWFTS

IMP Rev K

PMS425 Integrated Master Plan (IMP)

PMS425 Risk Management Plan May 2013

Submarine Combat and Weapon Control System Program Office Risk Management Plan Version 1.0

PMS425 SEP

15 December 2015

Submarine Combat and Weapon Control System Systems Engineering Plan (SEP), Version 1.1.3

SAFETY-SSMP-02

21 May 2007

PMS425 System Safety Management Plan (SSMP)

PMS425 WBS

11 March 2014

PMS425 Work Breakdown Structure (WBS)

Virginia (ssn 774) Class Non-Propulsion Electronic Systems (NPES)

19 July 2012

Block IV Functional Requirements Documents (FRD)

3. GENERAL REQUIREMENTS

This section provides the Program Management and general requirements that shall be applicable to all work to be accomplished under the contract. This document provides the specific technical efforts applicable to the Engineering Support Services and Studies efforts (CLINs 0001, 0005, 0101, 0103, 0201, 0203, 0301, 0303, 0401, 0403, 0501, 0503, 0601 and 0603) under this contract.

3.1 Program and Contract Management

The Contractor shall designate a single Program Manager 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 Post Award Conference (PAC)

The Contractor shall conduct a PAC with the Government within thirty (30) days of contract award. The PAC shall be no longer than two (2) business days. The Contractor shall develop the PAC structure and agenda. The Contractor shall generate and record minutes, attendance list, and action items of the PAC, and produce copies of all information presented. The Conference shall be held at the Contractor’s facility. Representatives from each subcontractor on the Contractor's team shall attend. [CDRLs A003, A004]

The purpose of the PAC is as follows:

a) Review the Contract and Technical requirements

b) Discuss the roles and working relationships between the Contractor and the Government

c) Discuss the Contractor’s planned management effort and requirements verification process

d) Discuss required meetings, periodicity, and reporting requirements

e) Review the Contractor’s facility plans

f) Review the Contractor’s recommendations for CIS Integration and Test

g) Identify the Integrated Product Teams (IPT’s) and their respective roles and responsibilities

h) Management and Contract Mechanics

Contract Administration Team Introductions Contractor Performance Management and Progress Reporting System Quarterly Program Reviews (QPR) Quarterly Financial Reviews (QFR)

i) Technical Discussions Requirements Traceability overview Configuration Management processes Major Technical Risk Areas Design Review execution and schedule Configuration Management processes

3.1.2 Contractor Perfromance Management and Progress Reporting

The Contractor shall prepare and deliver monthly Progress, Status and Management Reports to provide status of 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 provide two (2) separate weekly informal reports to the Government via E-mail. The first report shall contain 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 Integrated Master Schedule (IMS). The contract and financial report shall be delivered to the Government Contracting Officer Representative (COR), the PMS425 Principal Assistant Program Manager (PAPM) and the PMS425 Assistant Program Manager (APM). The second weekly report shall address technical status and shall identify progress toward, and any changes to, the CIS critical path, near-term major milestones, and TI/APB developmental task or activity actual start and/or actual finish date variances. The Contractor shall also include work-around(s) and/or recovery schedules/plans, identification of any risks, and associated impacts due to program changes. The technical report shall be delivered to the Government COR, the PMS425APM, and the SUB-S CIS Chief Engineer (CHENG).

3.1.3 Contract Work Breakdown Structure (CWBS)

The Contractor shall tailor the requirements of MIL-STD-881C to develop and maintain a CIS Contractor Work Breakdown Structure (CWBS) that correlates cost and schedule performance with technical progress. The Contractor shall ensure the CWBS extends down to the appropriate 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 system specification and shall use the PMS425 Work Breakdown Structure (WBS) as guidance (GFI, Attachment 2) to create a CWBS structure representing the products and services that comprise the entire work effort under the contract. The Contractor shall ensure traceability to the level four (4). The Contractor, if necessary, shall update the CWBS during the execution of the contract. Changes to the CWBS or associated definitions, at any reporting level, require approval of the Government. [CDRL A002]

3.1.4 Integrated Master Schedule

The IMS shall consist of key CIS program milestones, as derived from the PMS425 Integrated Master Plan (IMP) provided as GFI (Attachment 2). The IMS shall also include specific lower-level milestones for each TI/APB baseline consistent with the CWBS and as mutually agreed upon between the Contractor and the Government. The IMS shall include efforts of all activities including subcontractors. Events of particular interest to the Government include, but are not limited to: acceptance of GFI; Program Reviews; Technical Reviews; CIS and SWFTS test events; CIS and SWFTS integration events; major acquisition milestones; delivery of software upgrades with new functionality; and introduction and delivery to the fleet. [CDRL A026]

The Contractor shall use the IMS as a day-to-day execution tool and to periodically assess progress in meeting program requirements. The Contractor shall maintain and update the IMS 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 IMS. The Contractor shall perform appropriate analyses of the IMS tasks and report potential or existing problem areas, risks, and recommend corrective actions to eliminate or reduce schedule impact.

3.1.5 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 ensure their functional leads and/or Control Account Managers (CAMs) are actively engaged in the preparation of all subcontract specifications and statements of work. 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 (ACO) 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.6 Program Reviews

The Contractor shall conduct QPRS and 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. 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.

3.1.6.1 Quarterly Program Review (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:

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

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

c) Technical and program status and metrics

d) Test and evaluation activities

e) Logistics source data development and support efforts

f) Risk analysis activities

g) Quality program status

h) Safety program status

i) GFP and GFI status

j) Proposed changes to the Program baseline

3.1.6.2 Quarterly Financial Review (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:

a) Cost/Schedule performance and variances against plan

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

c) Performance against the contract incentives

d) Risk analysis activities

3.1.7 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 reviewed jointly between the Government and Contractor. [CDRL A003]

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

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 electronic mail (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, TDA, and other partners. The Contractor shall plan for a minimum of four (4) face-to-face meetings each fiscal year, with travel to the Washington Navy Yard, NUWC Division Newport, or other support activities locations.

The Contractor shall prepare and electronically submit minutes of the meetings and ensure the latest meeting materials are posted on the Contractors project website (i.e. CITIS, Alliance) within ten (10) working days unless otherwise directed by the Government. Minutes shall include a summary of discussions, attendees, and a listing of action items. [CDRL A004]

3.2 Systems Engineering

The Contractor shall provide a Systems Engineering Lead for all efforts under this contract. The Systems Engineering Lead shall ensure the application of disciplined Systems Engineering processes and Integrated Process and Product Development (IPPD) principles toward the development of the CIS baselines supporting the final certified system configurations of the SWFTS.

3.2.1 Systems Engineering Management Plan (SEMP)

The Contractor shall provide a Systems Engineering Management Plan (SEMP) to describe the Contractor’s approach for planning, controlling and conducting a fully integrated engineering effort under this contract. The Contractor shall ensure the SEMP incorporates the principles, and effectively aligns with the processes, of the Submarine Combat and Weapon Control System SEP. [CDRL A007]

The SEMP shall describe how the CIS development will progress from initial requirements definition through the build management and test and integration processes and how various technical inputs to the systems engineering effort will be integrated into a collaborative development environment. The SEMP process shall ensure the compatibility, interoperability, and integration of all functional and physical interfaces and shall ensure that the system definition and design reflect the requirements for all system elements: hardware, software, facilities, people, and data, as well as characterize and manage technical risks. Paramount to the SEMP is the process for receiving and integrating third (3rd) party software components into the CIS.

The SEMP shall also include a detailed description of the Contractor’s approach for ensuring that all system requirements are accounted for through a demonstrated ability to trace each requirement to the Specification Requirement Verification Matrix (SRVM) [CDRL A010], the Software Requirements Specifications (SRSs) [CDRL A011], System/Subsystem Specifications (SSSs) [CDRL A009] and Test Procedures [CDRL A016].

The SEMP shall define the full extent of internal and external CIS integration plans, identify the Contractor’s approach and support for overall CIS subsystem and system-level integration, and identify the necessary development and integration resources required to conduct CIS system integration, and identify the process to address all problems identified by the Government during the formal Software Design and Certification Test (SDCT) period. The Contractor should describe the approach to find and address as many software issues as possible prior to entrance into SDCT such that discovery of new issues while in SDCT and post-DRR is limited.

The SEMP shall describe the processes to be used to manage system interfaces. At a minimum, the Contractor shall address the following:

a) The Contractor shall identify processes for specifying the lowest level (i.e., subsystem or component) at which it intends to control and define interfaces by proprietary or vendor-unique standards, as well as the impact of those standards upon the proposed modularity and logistics approach.

b) The Contractor shall describe how it will define and record all subsystem and SoS level interfaces to provide fully functional specifications.

The Contractor's System Engineering processes shall include support for efforts to ensure the "design-in" of high reliability, maintainability, and availability requirements, including on-line and off-line diagnostics, maintenance documentation (e.g. built-in IETM), and embedded training capabilities, including use of Interactive Courseware, Computer Based Training, and Interactive Multimedia using common authoring standards to ensure seamless, efficient integration with SWFTS.

3.2.2 Engineering Documentation Database

The Contractor shall develop and maintain a Contractor Integrated Digital Environment database (i.e. Dynamic Object-Oriented Requirements System (DOORS)) to support the generation, traceability and configuration management of requirements, plans and procedures. At a minimum, the database shall trace all PSPEC requirements to the SSS, SRSs, SRVM, and Test Procedures. The database shall also allow for storage of these deliverables when in draft form. Upon formal delivery all engineering deliverables will be stored on Advanced Interactive Management Technology Center (AIMTC) (see section 3.13.3). The Contractor shall ensure the Government has full real-time access to the database. [CDRL A032]

The Contractor shall provide for the initial requirements database for TI-18/APB-17; however, the database shall be suited for all development efforts under this contract and shall be updated as required for subsequent TI/APB efforts.

3.2.3 Capaility Item Enhancements, Studies and Analysis

The Contractor shall provide level of effort engineering and technical services supporting the development, sustainment, and maintenance of on-going TI efforts as well as other engineering and analysis tasks as requested by the Government and authorized under Technical Instructions. The level of effort engineering and technical services shall support United States Navy variants, common efforts for Royal Australian Navy (RAN), and RAN-unique requirements. The efforts shall include approved Capability Improvements, Fleet and new construction problem assessment and adjudication; configuration control; software, hardware and logistics troubleshooting; and End of Life 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 this SOW, which may be required during the PoP of this contract. All requirements in the SOW apply to Capability Item Enhancement services.

This SOW provides the summation of the two (2) elements efforts:

1) The Contractor shall conduct systems engineering, development, integration and studies for TI-18/APB- 17, TI-18/APB-19, TI-20/APB-19, TI-20/APB-21, TI-22/APB-21 and approved Capability Improvements (CIs) through DRR under the applicable Engineering Services CLINs. The approved CI’s shall be supported for United States Navy 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 TI16/APB17, TI18/APB17, TI18/APB19, TI20/APB19, TI20/APB21 and TI22/APB21 configurations after completion of the initial variant DRR (Legacy Support).

The Contractor shall assist the Government in developing strategies and studies, performing system engineering analysis, and developing implementation plans to ensure the CIS achieves the specified performance. [CDRL A021]

The Contractor shall provide a Transition plan within sixty (60) days after contract award. [CDRL A029] The Contractor shall submit a transition plan to include the following elements:

Identification of required hardware and software to initiate TI-18/APB-17 development Proposed schedule Facility plan for development and test efforts Reconstitution of the software build plan and schedule

3.2.4 Meetings, Integrated Product Teams (IPTs) and Working Groups (WGs)

The Contractor shall participate in and/or support the following Government-established IPTs and working groups supporting the design, development, integration and installation of CIS:

a) System Engineering Integrated Product Team (SEIPT)

b) Requirements Architecture Design Working Group (RADWG)

c) Integration and Test Working Group (ITWG)

d) Integrated Logistics Support Working Group (ILSWG)

e) SWFTS CIS IETM Development Group

f) Problem Trouble Report (PTR) Review Board

g) SWFTS Architecture Working Group (SAWG)

h) Technology Insertion IPT (TI IPT)

i) Advanced Processor Build (APB) Integration IPT (IIPT)

j) Advanced Processor Build (APB) Architecture Splinter Group (ASG)

k) VIRGINIA, OHIO, and Ohio Replacement (OR) Class new construction technical team meetings and

Platform Integration Teams (PITs)

l) S1000D IPT

m) Design reviews and working groups for the design and development of the CIS baselines

Additionally, the Contractor shall support splinter groups of the above IPTs/WGs and other weekly, bi-weekly, etc.

and PMS 425, SWFTS, and Ship Acquisition Program Manager (SHAPM) coordination meetings as deemed necessary by the Government. The Contractor shall participate in and conduct meetings, conferences, teleconferences, video teleconferences, drumbeats, IPTs, peer reviews, and working groups supporting all efforts under this contract and related SWFTS efforts. Participating and conducting includes meeting preparation, travel, attending meetings and providing information for the IPT, peer review, or working group to make decisions.

In addition, the Contractor may, in agreement with the Government, establish additional IPTs with members from Government, the Contractor, subcontractors, industry partners and vendors in order to address specific programmatic issues or to support general CIS development and fielding including the consolidation and integration of cost, schedule and performance data to provide a global perspective into the managerial and technical aspects impacting Government and industry.

For the Contractor-established IPTs, the Contractor shall develop IPT charters and present these charters during program reviews for Government approval. Potential functions for Contractor IPTs may include:

a) Monitoring and reporting of CIS status and progress for both the Government and the Contractor

b) Joint identification, evaluation, management, and reporting of risk mitigation and cost reduction initiative efforts

c) Identification, collection, analysis, and reporting of appropriate metrics for measurement of cost/schedule control, engineering and production progress

d) Joint evaluation and management resolution of major issues associated with hardware and software engineering, production, integration, test, and I&C activities

e) Verification that the Contractor’s ‘early and often’ design disclosure process is providing data that is current, complete and accurate to third party developers

f) Joint evaluation and management of the ILS effort

g) Joint recommended approval of data items requiring approval under this contract

3.2.5 System Requirements

The Contractor shall assist the Government in defining and documenting the capabilities and requirements for all applicable baselines under this contract. TI-18/APB-17 requirements are defined in the CIS P-SPEC. The P-SPEC will be updated for subsequent Baselines.

3.2.5.1 Requirements Documentation

The Contractor shall deliver the following requirements documents for all variants; however, these documents shall apply to all efforts under this contract and shall be updated as required for subsequent TI/APBs.

System/Subsystem Specifications (SSS) [CDRL A009] Specification Requirement Verification Matrix (SRVM) [CDRL A010]

The Contractor shall document required Simulation/Stimulation equipment that will be utilized for each test in the SRVM. To support development of the SRVM for all variants, the Contractor may elect to review the latest approved SSS and SRVM requirements documentation that is maintained on AIMTC.

3.2.5.2 Interface Requirements Management

As part of the Contractor’s System/Subsystem Design Description (SSDD) [CDRL A008], covered in section 3.2.5.4, and in accordance with the SEMP, the Contractor shall describe the CIS interfaces and interaction with SWFTS subsystems, controlled interfaces, guarding components, and applicable external network enclaves. At a minimum, the Contractor shall address the following:

1. Interfaces described shall ensure compliance with all applicable documents including, but not limited to, Interface Control Drawings (ICDs), Interface Requirements Specifications (IRSs), CIS System PSPEC, and the SWFTS baseline products hosted on the SWFTS SE&I Contractor’s technical information system.

2. The Contractor shall address the interface and data exchange standards between the component, module or system and the interconnecting or underlying information exchange medium.

3. The Contractor shall state how these interfaces support an overall Cyber Defense / Information Assurance strategy that provides a defense in depth in accordance with NAVSEA Instruction 9400.2

The Contractor shall ensure the external interface integrity of the CIS and manage interface change IAW the below.

a) The Contractor shall participate in the SWFTS Baseline Management System and notify the Program Office of any required Non-Propulsion Electronics System (NPES) Baseline Change Requests (NBCRs) required to support CIS 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 CIS project schedule or that result in unplanned costs.

b) The Contractor shall initiate appropriate interface change requests for applicable technical documents when updates are required.

3.2.5.3 System Architecture and Design

The Contractor shall design, develop, and/or integrate CIS configurations utilizing the existing baseline functionality, as well as additional functions and services identified in the applicable CIS PSPEC.

3.2.5.3.1 Modular Open Systems Architecture Approach

The Contractor shall establish and maintain a modular open systems architecture approach in accordance with the requirements of the DoD Open System Architecture Contract Guidebook, v1.1. 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. The Contractor shall specify the process to avoid compromise of the intellectual property rights of third party developers. The Contractor shall establish an Associate Contractor agreement with each third (3rd)party developer and coordinate disclosure and delivery schedule directly with the developers. The Contractor shall ensure the following system architecture characteristics are maintained for all CIS baselines:

a) Open Architecture - The Contractor shall develop and maintain a CIS architecture that incorporates appropriate considerations for reconfigurability, portability, maintainability, technology insertion, vendor independence, reusability, scalability, interoperability, upgradeability, and long-term supportability.

b) Modular, Open Design – The Contractor shall develop and maintain a CIS architecture that is layered and modular and uses COTS/NDI hardware, 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 and shall provide for ease of integration of third party

(3rd) Non-Developmental Items (NDI) components into the CIS computing environment. 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) Modular Open Systems Approach (MOSA) –The Contractor’s design approach shall produce a system that consists of hierarchical collections of software and hardware configuration items (components).

In technical and design reviews, the Contractor shall provide the approach to be used relating to the overall Software Computer Software Configuration Item (CSCI) structure, functional flows, and interface requirements and shall describe how their approach supports Open Architecture goals while interfacing with the other SWFTS systems simultaneously under development and those already fielded on the target platforms. The Contractor shall disclose the approach to support the CIS collaborative development environment including frequent and continuous design disclosure to Navy designated third (3rd) party developers throughout the development process. Additionally, as part of technical and design reviews, the Contractor shall, at a minimum:

a) Describe how the proposed system architecture meets the modular, open design goals, including the steps taken to use non-proprietary or non-vendor unique COTS or reusable NDI components wherever practicable.

b) Describe its rationale for the modularization choices made to generate the design.

c) Provide rationale to explicitly address any tradeoffs performed, particularly those that compromise the modular and open nature of the system.

d) Describe the plan to maintain awareness of, and access to, modern and developing technologies and products from industry. Describe how it will mitigate the risks associated with technology obsolescence.

e) Describe how it will avoid being locked into proprietary or vendor-unique technology and reliance on a single source of supply over the life of the system

3.2.5.4 System Design Documents

The Contractor shall deliver the following documents for all variants; however, these documents shall apply to all efforts under this contract and shall be updated as required for subsequent TI/APBs.

System/Subsystem Design Description (SSDD) [CDRL A008] Software Requirements Specifications (SRSs) [CDRL A011] Software Design Description (SDD) [CDRL A012]

The Contractor shall ensure the above documents fully describe the overall CSCI structure, functional flows and interface requirements, including external CIS interface requirements, if applicable. The Contractor shall include separate sections that detail any unique variant or platform requirements. To support development of this effort, for the Contractor may elect to review the latest approved SSDD, SRS and Sim/Stim Design Description that is maintained on AIMTC.

The Contractor shall also generate and review all applicable SWFTS-level interface baseline documentation including, but not limited to, the Group Requirements Lists (GRLs), Interface Implementation Database (IIDB), System Initialization & Fault Tolerance (SIFT), Internet Protocol Spreadsheet (IPSS) and Any Display Any Where (ADAW) matrices hosted on the SWFTS SE&I Contractor’s technical information system.

3.2.5.5 Technical and Design Reviews

Technical and design reviews shall be held at the Contractor’s facility to discuss and evaluate overall design progress and the status of entrance and exit criteria as defined in the PMS425 SEP. The structure and intervals shall be defined in the IMS. However, the scope of the technical reviews shall be limited to the impact of the new, deleted or changing capabilities. The Contractor shall address all review action items within the scope of the changes and document any effort involving legacy issues.

The Contractor shall provide for the following technical and design reviews:

System Requirements Review (SRR) Preliminary Design Review (PDR) Critical Design Review (CDR)

The Contractor shall provide Design Review packages supporting these reviews two (2) weeks prior to the design review. These packages shall be of final, ‘To-be-presented’ quality. [CDRL A027]

3.2.5.6 Hardware Design

As the award of this contract is anticipated to be final near the end of the TI-18 process, the Contractor will be provided a CIS TI-18 hardware baseline design that has been assessed to meet CIS processing and networking needs and will not be technologically obsolete when fielded.