N00024-23-R-6201 Draft Solicitation.pdf

NOTE: The draft solicitation only includes sections B, C, D, F, H, and I

DRAFT

N0002423R6201

Section B - Supplies or Services and Prices

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

CLIN

Number

96,312 Hours

Engineering and Technical Support

CPFF

The total number of hours set forth on this CLIN is a maximum ceiling number of hours. The Government may not order all hours estimated herein. The

Government will fund these hours as needed during contract performance in accordance with Section H text “LEVEL OF EFFORT”. Subline items (SLINs) will be established with a funding appropriation, FY designation, and Program

Office customer. Technical Instructions will be issued in accordance with

Section C text entitled “TECHNICAL INSTRUCTIONS” to clarify the tasks required of the SOW.

FOB: Destination

PURCHASE REQUEST NUMBER: COMPETESMALL

PSC CD: 1260

ESTIMATED COST

FIXED FEE

TOTAL EST COST + FEE

Lot

OPTION COST

Material, Travel and Subsistence

Incidental materials and travel that are used or consumed directly in connection with performance of CLIN [INSERT] during the performance of this contract will be reimbursed on a cost only basis; no fee will be paid on this line item. If exercised, this line item will be clarified by Technical Instructions issued by the

Contracting Officer and Contracting Officer’s Representative (COR).

NOT-TO-EXCEED

Provisioned Item Order

FFP

Provisioned Items Orders (PIO). If issued, Orders under this Line Item shall be in accordance with the requirements of Section C of this contract entitled

PROVISIONED ITEMS ORDERS. Firm Fixed Pricing will be set forth on each order. When the request is determined to be commercial items, commercial clauses shall apply.

NET AMT

95,407 Hours

OPTION Engineering and Technical Support

CPFF

The total number of hours set forth on this CLIN is a maximum ceiling number of hours. The Government may not order all hours estimated herein. The

Government will fund these hours as needed during contract performance in accordance with Section H text “LEVEL OF EFFORT”. Subline items (SLINs) will be established with a funding appropriation, FY designation, and Program

Office customer. Technical Instructions will be issued in accordance with

OPTION FOB: Destination

COST

Material, Travel and Subsistence

Incidental materials and travel that are used or consumed directly in connection with performance of CLIN [INSERT] during the performance of this contract will be reimbursed on a cost only basis; no fee will be paid on this line item. If

Contracting Officer and Contracting Officer’s Representative.

94,570 Hours

CPFF

The total number of hours set forth on this CLIN is a maximum ceiling number of hours. The Government may not order all hours estimated herein. The

Government will fund these hours as needed during contract performance in accordance with Section H text “LEVEL OF EFFORT”. Subline items (SLINs) will be established with a funding appropriation, FY designation, and Program

Office customer. Technical Instructions will be issued in accordance with

Material, Travel and Subsistence

Incidental materials and travel that are used or consumed directly in connection with performance of CLIN [INSERT] during the performance of this contract will be reimbursed on a cost only basis; no fee will be paid on this line item. If

93,701 Hours

CPFF

The total number of hours set forth on this CLIN is a maximum ceiling number of hours. The Government may not order all hours estimated herein. The

Government will fund these hours as needed during contract performance in accordance with Section H text “LEVEL OF EFFORT”. Subline items (SLINs) will be established with a funding appropriation, FY designation, and Program

Office customer. Technical Instructions will be issued in accordance with

Material, Travel and Subsistence

Incidental materials and travel that are used or consumed directly in connection with performance of CLIN [INSERT] during the performance of this contract will be reimbursed on a cost only basis; no fee will be paid on this line item. If

92,802 Hours

CPFF

The total number of hours set forth on this CLIN is a maximum ceiling number of hours. The Government may not order all hours estimated herein. The

Government will fund these hours as needed during contract performance in accordance with Section H text “LEVEL OF EFFORT”. Subline items (SLINs) will be established with a funding appropriation, FY designation, and Program

Office customer. Technical Instructions will be issued in accordance with

Material, Travel and Subsistence

Incidental materials and travel that are used or consumed directly in connection with performance of CLIN [INSERT] during the performance of this contract will be reimbursed on a cost only basis; no fee will be paid on this line item. If

91,965 Hours

CPFF

The total number of hours set forth on this CLIN is a maximum ceiling number of hours. The Government may not order all hours estimated herein. The

Government will fund these hours as needed during contract performance in accordance with Section H text “LEVEL OF EFFORT”. Subline items (SLINs) will be established with a funding appropriation, FY designation, and Program

Office customer. Technical Instructions will be issued in accordance with

Material, Travel and Subsistence

Incidental materials and travel that are used or consumed directly in connection with performance of CLIN [INSERT] during the performance of this contract will be reimbursed on a cost only basis; no fee will be paid on this line item. If

91,098 Hours

CPFF

The total number of hours set forth on this CLIN is a maximum ceiling number of hours. The Government may not order all hours estimated herein. The

Government will fund these hours as needed during contract performance in accordance with Section H text “LEVEL OF EFFORT”. Subline items (SLINs) will be established with a funding appropriation, FY designation, and Program

Office customer. Technical Instructions will be issued in accordance with

OPTION FOB: Destination

COST

Material, Travel and Subsistence

Incidental materials and travel that are used or consumed directly in connection with performance of CLIN [INSERT] during the performance of this contract will be reimbursed on a cost only basis; no fee will be paid on this line item. If

Data

Data deliverables shall be produced and submitted in accordance with the applicable Contract Data Requirements List (CDRLs) in Exhibit A listed under

Section J.

CLAUSES INCORPORATED BY FULL TEXT

B-215-H002 REFUNDS (SPARES AND SUPPORT EQUIPMENT) (NAVSEA) (OCT 2018)

(a) In the event that the price of a spare part or item of support equipment delivered under this contract significantly exceeds its intrinsic value, the Contractor agrees to refund the difference. Refunds will not be made to recoup the amount of cost decreases that occur over time due to productivity gains (excluding economic purchase quantity considerations) or changes in market conditions.

(b) For purposes of this requirement, the intrinsic value of an item is defined as follows:

(1) If the item is one which is sold or is substantially similar or functionally equivalent to one that is sold in substantial quantities to the general public, intrinsic value is the established catalog or market price, plus the value of any unique requirements, including delivery terms, inspection, packaging, or labeling.

(2) If there is no comparable item sold in substantial quantities to the general public, intrinsic value is defined as the price an individual would expect to pay for the item based upon an economic purchase quantity as defined in FAR

52.207-4, plus the value of any unique requirements, including delivery terms, inspection, packaging or labeling.

(c) At any time up to two years after delivery of a spare part or item of support equipment, the Contracting Officer may notify the Contractor that based on all information available at the time of the notice, the price of the part or item apparently exceeds its intrinsic value.

(d) If notified in accordance with paragraph (c) above, the Contractor agrees to enter into good faith negotiations with the Government to determine if, and in what amount, the Government is entitled to a refund.

(e) If agreement pursuant to paragraph (d) above cannot be reached, and the Navy's return of the new or unused item to the Contractor is practical, the Navy, subject to the Contractor's agreement, may elect to return the item to the Contractor.

Upon return of the item to its original point of Government acceptance, the Contractor shall refund in full the price paid.

If no agreement pursuant to paragraph (d) above is reached, and return of the item by the Navy is impractical, the

Contracting Officer may, with the approval of the Head of the Contracting Activity, issue a Contracting Officer's final decision on the matter, subject to Contractor appeal as provided in the "Disputes" clause (FAR 52.233-1).

(f) The Contractor shall make refunds, as required under this requirement, in accordance with instructions from the

Contracting Officer.

(g) The Contractor shall not be liable for a refund if the Contractor advised the Contracting Officer in a timely manner that the price it would propose for a spare part or item of support equipment exceeded its intrinsic value, and with such advice, specified the estimated proposed price, the estimated intrinsic value and known alternative sources or item, if any, that can meet the requirement.

(h) This requirement does not apply to any spare parts or items of support equipment whose price is determined through adequate price competition. This requirement also does not apply to any spare part or item of support equipment if the

Contractor submitted, and certified the currency, accuracy and completeness of, cost or pricing data applicable to the item.

(End of text)

B-216-H006 FEE TABLE (NAVSEA) (MAR 2019)

Labor CLIN Labor Hours Cost Per

Hour*

Fee Rate Per

Hour*

Loaded

Hourly Rate

0001 96,312 Fill out by Offeror Fill out by Offeror Fill out by Offeror

1001 95,407 Fill out by Offeror Fill out by Offeror Fill out by Offeror

2001 94,570 Fill out by Offeror Fill out by Offeror Fill out by Offeror

3001 93,701 Fill out by Offeror Fill out by Offeror Fill out by Offeror

4001 92,802 Fill out by Offeror Fill out by Offeror Fill out by Offeror

5001 91,965 Fill out by Offeror Fill out by Offeror Fill out by Offeror

6001 91,098 Fill out by Offeror Fill out by Offeror Fill out by Offeror

*The offeror shall divide the proposed fee for each CLIN by the quantity of labor hours indicated to complete the table. Fee is calculated based on cost less FCCOM; if FCCOM is proposed, necessary columns may be added.

In the event of any inconsistency between the above table and the CLIN pricing, the CLIN pricing shall take precedence.

B-231-H001 TRAVEL COSTS (NAVSEA) (OCT 2018)

(a) Except as otherwise provided herein, the Contractor shall be reimbursed for its actual travel costs in accordance with FAR 31.205-46. The travel costs to be reimbursed shall be those costs for which the Contractor has maintained appropriate documentation and which have been determined to be allowable, allocable, and reasonable by the

Procuring Contracting Officer, Administrative Contracting Officer, or their duly authorized representative.

(b) Reimbursable travel costs include only that travel performed from the Contractor's facility to the worksite, in and around the worksite, and from the worksite to the Contractor's facility.

(c) Relocation costs and travel costs incidental to relocation are allowable to the extent provided in FAR 31.205-35;

however, Procuring Contracting Officer approval shall be required prior to incurring relocation expenses and travel costs incidental to relocation.

(d) The Contractor shall not be reimbursed for the following daily local travel costs:

(i) travel at U.S. Military Installations where Government transportation is available,

(ii) travel performed for personal convenience/errands, including commuting to and from work, and

(iii) travel costs incurred in the replacement of personnel when such replacement is accomplished for the

Contractor's or employee's convenience.

B-232-H005 PAYMENTS OF FEE(S) (LEVEL OF EFFORT)--ALTERNATE I (NAVSEA) (OCT 2018)

(a) For purposes of this contract, "fee" means "target fee" in cost-plus-incentive-fee type contracts, "base fee" in cost-plus-award-fee type contracts, or "fixed fee" in cost-plus-fixed-fee type contracts.

(b) The Government shall make payments to the Contractor, subject to and per the clause in this contract entitled "Fixed

Fee" (FAR 52.216-8) or "Incentive Fee", (FAR 52.216-10), as applicable. Such payments shall be submitted by and payable to the Contractor pursuant to the clause of this contract entitled "Allowable Cost and Payment" (FAR 52.216-7), subject to the withholding terms and conditions of the "Fixed Fee" or "Incentive Fee" clause, as applicable. Fee paid per hour shall be based on total fee dollars divided by total hours to be provided. Total fee(s) paid to the Contractor shall not exceed the fee amount(s) set forth in this contract. In no event shall the Government be required to pay the Contractor any amount in excess of the funds obligated under this contract.

B-232-H006 LIMITATION OF COST OR LIMITATION OF FUNDS CLARIFICATION (NAVSEA) (OCT 2018)

The clause entitled "Limitation of Cost" (FAR 52.232-20) or "Limitation of Funds" (FAR 52.232-22), as appropriate, shall apply separately and independently to each separately identified estimated cost.

Section C - Descriptions and Specifications

STATEMENT OF WORK

C.0 Statement of Work

C.3. STATEMENT OF WORK

SUBMARINE WARFARE FEDERATED TACTICAL SYSTEMS (SWFTS)

COMMON INFRASTRUCTURE SERVICES (CIS)

COMMON COMPUTING ENVIRONMENT (CCE)

22 NOVEMBER 2022

DEPARTMENT OF THE NAVY

PROGRAM EXECUTIVE OFFICER, UNDERSEA WARFARE SYSTEMS (PEO UWS)

SUBMARINE COMBAT AND WEAPONS CONTROL SYSTEMS (PMS425)

1333 ISAAC HULL AVENUE SE

WASHINGTON, NAVY YARD

WASHINGTON, DC 20376

DISTRIBUTION STATEMENT D: Distribution authorized to the Department of Defense and U.S. DoD contractors. Release to Australia authorized under the Memorandum of Understanding between the Department of

Defense of the United States of America and the Department of Defense of Australia for the Cooperative

Development, Production and Support of the AN/BYG-1 Combat Control System, signed 07 JUL 2019. Other requests must be referred to the Program Executive Officer, Undersea Warfare Systems or the Submarine Combat

Systems Program Office (PMS 425).

WARNING - This document contains technical data whose export is restricted by the Arms Export Control Act

(Title 22, U.S.C. Sec. 2751 et seq.) or the Export Administration Act of 1979, as amended, Title 50, U.S.C., App

2401, et seq. Violations of these export laws are subject to severe criminal penalties.

Disseminate in accordance with provisions of DoD Directive 5230.25.

Destruction Notice: Destroy by any method that will prevent disclosure of contents or reconstruction of the document. This information is furnished upon the condition that it or knowledge of its possession will not be released to another nation, and that it will not be used for other than military purposes for which it is being provided without specific authority from the U.S. Department of the Navy; that individual or corporate rights contained within, whether patented or not, will be respected; that the information will be provided the same degree of security afforded it by the U.S. Department of Defense. Regardless of any declassification markings, this information may not be downgraded or declassified by a foreign recipient without the written approval of the originating U.S. agency.

Controlled By: Program Executive Officer, Undersea Warfare Systems

Controlled By: PMS 425

CUI Category: CUI//SP-PROCURE

Distribution/Dissemination Control: FEDCON

POC: Common Infrastructure Services Assistant Program Manager

NOTE: The CDRL numbering is “TBD” throughout this draft SOW as the Government intends to streamline and reduce the number of CDRLS to the maximum extent possible without losing integrity of the regulatory reporting requirements and those necessary for management and oversight of the contract and system performance. The

Government welcomes feedback to assist with this intent.

C.3.1. Background and System & Functional Overview

This requirement is for Submarine Warfare Federated Tactical Systems (SWFTS) Common Infrastructure Services

(CIS) & Common Computing Environment (CCE) software (SW) design, engineering development, integration, testing, logistics, delivery, and life cycle sustainment support. The SWFTS CIS is a subsystem within the AN/BYG-

1 Submarine Combat and Weapons Control System. CIS will deliver the SWFTS CCE as a component of CIS that will be hosted across hardware from multiple SWFTS subsystems. CIS will be designed in accordance with (IAW)

SWFTS community design requirements for all applicable submarine variants per the SWFTS Baseline Roadmap and Execution Plan associated with AN/BYG-1 Technology Insertion (TI) 2024 (TI24), TI26, legacy baselines, and future baselines. CIS core components will be hosted within the AN/BYG-1 Submarine Combat and Weapons

Control System shipboard physical footprint for all United States Navy (USN) and Royal Australian Navy (RAN) new construction and in-service submarines.

The CIS is an integrated subsystem of the larger AN/BYG-1 Combat and Weapons Control System. The primary function of the CIS system is to provide SWFTS-connected subsystems with system of systems (SoS) infrastructure services and the SWFTS CCE. The SWFTS CCE hosts, statuses, and manages applications provided by combat and weapons control, sonar, imaging, electronic warfare, and other AN/BYG-1 and SWFTS subsystems. Typical configurations of CIS and AN/BYG-1 in USN and RAN submarines are provided in Figures 1 and 2.

Figure 1: TI20 AN/BYG-1 and CIS USN Functional Overview

Figure 2: TI20 AN/BYG-1 and CIS RAN Functional Overview

The Contractor shall support development and legacy CIS efforts for the following AN/BYG-1 system variants:

AN/BYG-1 System Variants

(V)1 VIRGINIA Class SSNs 774-783

(V)2 688i SSNs 751-773

(V)3 688 SSNs 719-725, 750

(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 SSNs 784-802

(V)10 VIRGINIA Class Block 5 SSNs 803 - 811

(V)11 COLUMBIA Class SSBN 826-837

This procurement includes the following:

Engineering, technical, and programmatic support

System modification / upgrades, test and evaluation (T&E) efforts, and delivery

Procurement of hardware to support development, integration, and T&E

Integrate and test SWFTS subsystem applications with CIS

Port CIS SW onto new TI hardware suites, while maintaining backward TI compatibility

Develop CIS hardware requirements

Participate in integrated product teams (IPT) and working groups (WG)

Develop CIS and SoS logistics source data; deliver CIS subsystem interactive electronic technical manual

(IETM) (CDRL TBD)

Integrate and enable AN/BYG-1 and SWFTS SoS non-development items (NDI) from multiple vendors

Incorporate information assurance (IA) / cybersecurity updates to support accreditations

Enable SWFTS transformation by incorporating continuous integration / continuous development (CI/CD) and cyber resilience into CIS

Navy Organization & Sponsors

PEO UWS is the acquisition executive for this procurement. PMS425, in coordination with the SWFTS program office, PEO 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 RAN, the CIS development, test, integration, and life-cycle support efforts will also include support for applicable RAN submarines.

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 model to accelerate the transition of advanced development SW to the submarine fleet. This concept, which provides progressive capability through advanced processor build (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) hardware (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.

Three submarine electronics Program Offices (PMS401, PMS425 and PMS435) follow this process and work cooperatively to provide advanced capability for combat and weapons / payload control, acoustics, imaging systems, and electronic warfare, as well as the underlying computing infrastructure in which it hosts.

This contract follows the time-phased TI/APB cycle: new APB SW baselines are developed in odd years and new TI

HW baselines are developed in even years. The primary focus of this procurement is the odd-year SW baseline development. The odd year SW baselines shall be integrated into the current TI HW baseline at the time the SW baseline is in 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, CIS shall follow APB naming convention for SW updates. This requirement is for TI24, TI26, legacy baselines, and future baselines.

Figure 3 is the notional SoS integration and delivery schedule depicting expected configurations. This notional execution plan will be updated based on fleet planning requirements and submarine platform availability.

Figure 3: Notional CIS Configuration Delivery Plan

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

Figure 4 depicts a generic development and integration cycle overview to highlight the overlap of planning and execution activities required to support the SWFTS continuous capability insertion (CI) model.

Figure 4: Development and Integration Cycle Overview

Figure 5 provides an example of CIS delivery requirements to support multiple baselines at various stages of

SWFTS development and SoS activities.

Figure 5: CIS Delivery Across Multiple Baselines

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

SWFTS CCE and Resiliency Computing Environment (RCE): Distinct software infrastructure deployments

Platform: An individual submarine

Variant: The specific submarine class (or a submarine class separated by unique platform characteristics) which drives software and/or hardware differences

Baseline: A HW baseline is the sum of AN/BYG-1 system HW selected for a given TI cycle (e.g., TI-24).

A SW baseline is the sum of approved functional capability for a given APB SW build (e.g., APB-23). A baseline can also be a combined baseline (HW plus SW capability) such as TI-24/APB-23. A baseline is all-inclusive and not variant specific.

Platform Configuration*: A variant plus the combined hardware and software baseline. Example: SWFTS

CIS VA BLK V TI-24/APB23

New Baseline Change Request (NBCR): A new capability that will be integrated into CIS. This capability may be developed by the CIS Contractor or be provided as an NDI by another developer. Additionally, these items may be developed under the IWS5 A-Step process or be developed as part of the production process for CIS. An NBCR may also be used to refer to a significant update to an existing component of

CIS. Requirements changes which do not require significant re-design of an existing capability are not considered NBCRs.

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 combining multiple applications and software units into the CIS.

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

System Overview

The CIS is an integrated suite of SoS applications and services, the underlying hosting computing environment, and the SWFTS Network backbone (i-Net). The CIS applications and services perform network monitoring, reliability management, training, mediation, time distribution, directory services, geographic imagery services, data recording and archiving, information assurance, and video distribution. The CIS SW operates on processing, display, and networking HW developed by the Technology Insertion Integrated Product Team (TI IPT) and the Technology

Insertion Hardware (TIH) Contractor. The Contractor shall participate in the TI IPT and be provided with source control drawings for each new HW baseline via secure site.

The CIS is part of the PMS425 AN/BYG-1 family of products; however, it is designed, developed, and able to be delivered independent of the AN/BYG-1 software suite. This intentional separation ensures SWFTS Enterprise requirements and priorities can be met independent of any AN/BYG-1 or SWFTS subsystem. The CIS includes a combination of core development and NDIs delivered by third party vendors, as provided in Figure 6 below.

Figure 6: CIS Development and NDIs

Application / Service NDI (Yes / No)

Connectivity Services

Tactical Network Infrastructure (iNet) and Secure

Network (SecureNet)

No

Directory Services including:

Domain Name Service

CORBA Name Service

Lightweight Directory Access Protocol

No

Cybersecurity Services

Cybersecurity Services Common Components Yes

(Information Assurance Tool Kit)

Cybersecurity CCE Policies and Security Configurations No

EdgeGuard Services Yes

(TBD)

System of Systems (SoS) Services

Time Distribution No

Globe Services No

System of Systems Alerts Service No

Printing Service No

Overlay Service No

Common Recording Service No

Tactical Software Repository No

Platform and Interface Monitoring No

Chart Distribution Service No

Data Mediation and Translation Services Yes

(Real-Time Service Based Architecture)

Common Recording No

Data Archival No

IETM Framework No

Landing Pad Hosting Service No

Application Hosting

System of Systems Network and Interface Management Yes

(Inter Subsystem Monitoring Tool)

Reliability Monitoring and Management Service Yes

(Submarine Reliability Monitoring Service)

On Board Team Training Yes

(On-Board Team Training-Master Controller)

SWFTS CIS IETM No

Training Environment Yes (Learning Management System)

CIS Integrator stands up LMS environment and integrates various products as noted in the

SWFTS CIS PSPEC.

Video Distribution

VDS Switching No

Digital VDS Sources/Sinks No

CIS System Management

System Management No

Reconfiguration Management No

Performance Monitoring No

CIS Operating System

No

Use SWFTS Common selected by SWFTS IPT

Network and CCE resource monitoring No

*List is subject to change

C.3.2. Applicable Documents

The following documents are to be used as guidance in the performance of the requirements identified herein.

C.3.3. Program and Contract Management

The Contractor shall designate a single Program Manager (PM); this position is considered a Key Person in accordance with C-237-H005. The PM shall be responsible for all efforts under this contract and be authorized to commit the Contractor to specific courses of action.

C.3.3.1. Management and Progress Reporting

The Contractor shall submit Progress and Status Reports (CDRL TBD). The Contractor shall provide a Government

Property Inventory Report (CDRL TBD). The Contractor shall submit phase-in and phase-out transition plans

(CDRLs TBD, TBD). The phase-in transition plan shall include the following:

• Reconstitution of requirements baseline

• Identification of required hardware and software to initiate TI-24 development

• Proposed ramp-up schedule

• Facility plan for development and test efforts

• Reconstitution of the software build plan and schedule

• Staffing

• Integrated logistics support (ILS) transition

Date of Latest Version Document

07 October 2019 DODI 8500.01 - Cybersecurity

05 October 2020 DODD 8140.01 - Cyberspace Workforce Management

07 March 2019 DoD 8570.01-M – Information Assurance Workforce Improvement Program

Nov 2017 ISO/IEC/IEEE 12207:2017 ISO/IEC/IEEE Standard for Systems and SW Engineering

– SW Life Cycle Process

June 2013 OSA Contract Guidebook - DoD Open System Architecture Contract Guidebook, v1.1

11 May 2012 MIL-STD-882E - Standard Practice for System Safety

01 August 1995 MIL-HDBK-1785 - System Security Engineering Program Management Requirements

28 June 2019 ASD/AIA S1000D Issue 5.0 - S1000D Specification International Specification for

Technical Publications Utilizing a Common Source Database;

https://public.s1000d.org/

31 August 2001 MIL-PRF-29612B - Performance Specification Training Data Products

06 March 2020 DoDI 5200.48 - Controlled Unclassified Information

10 December 2021 DoDI 5220.22 - National Industrial Security Program

February 2020 NIST Special Publication 800-171 (Rev. 2) - Protecting Controlled Unclassified

Information in Nonfederal Systems and Organizations

6 March 2017 DoD Cloud Computing SRG v1r3 - Department of Defense Cloud Computing Security

Requirements Guide

12 August 2019 DoD Enterprise DevSecOps Reference Design, Version 1.0

December 2021 NIST Special Publication 800-160

Volume 2 Revision 1

Developing Cyber-Resilient Systems:

A Systems Security Engineering Approach

September 2020 NIST Special Publication 800-53

Volume 2

Security and Privacy Controls for Information Systems and Organizations

07 March 2018 TMCR SNIPP-170052-000 - Electronic Equipment Interactive Electronic Technical

Manual (IETM) SWFTS CIS & SoS IETM Reflecting Organizational-level

Maintenance DRAFT

• Problem Trouble Report (PTR) transition

The Contractor shall support weekly telephonic discussions with Government representatives to discuss contractual, financial, and technical topics. The Contractor shall discuss contractual, financial, and technical risks to the program and provide recommendations to mitigate the risks.

The Contractor shall provide a weekly synopsis email to Government representatives the COR and the Assistant

Program Manager (APM). Brevity shall be utilized in the email. The purpose of this email is to ensure a common understanding and situational awareness across stakeholders and leadership. The Contractor shall discuss the following topics at a minimum:

• Current priority of effort

• Efforts performed over the last business week

• Efforts planned for the next business week

• Contractual risks

• Financial risks

• Technical risks

• Issues / recommendations

C.3.3.2. Integrated Master Schedule

The Contractor shall develop a CIS program integrated master schedule (IMS) and provide key program milestones to the SWFTS IMS to ensure program transparency to all participating SWFTS subsystems (CDRL TBD). The CIS

IMS shall be derived from the PMS425 Integrated Master Plan (IMP) and SWFTS Baseline Roadmap. The

Contractor shall also provide specific lower-level milestones for each baseline. The provided milestones 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

• CIS and SWFTS test events

• CIS and SWFTS integration events

• Major acquisition milestones regarding performance

• Delivery of software upgrades with new functionality

• Introduction and delivery to the fleet

The internal development pipeline shall align to SWFTS CI/CD Framework Requirements and support automated deployment, configuration management, T&E, and certification.

The Contractor shall use the SWFTS execution schedule and IMS as day-to-day execution tools to periodically assess progress in meeting program requirements. The Contractor shall maintain and update the IMS milestones 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 CIS IMS. The Contractor shall perform appropriate analyses of the milestones and report potential or existing problem areas, risks, and recommended corrective actions to eliminate or reduce schedule impact. The Contractor shall provide Government real-time access to the Contractor’s working integrated master schedule.

C.3.3.3. Program Reviews

The Contractor shall conduct/support 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 CIS APM and COR ten (10) business days prior to the review. The final agenda and presentation shall be provided five (5) days prior to the review (CDRLs

TBD). The Contractor shall ensure the widest distribution of the final agenda and presentation material to the appropriate Government stakeholders and support staff. The Contractor shall collaborate with the CIS APM and

COR to identify the Government stakeholders and support staff.

C.3.3.3.1. Quarterly Program Reviews

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

• Schedule progress against the IMS (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

• GFP and GFI status

• Proposed changes to the Program baseline

C.3.3.3.2. Quarterly Financial Reviews

The purpose of the QFR is to ensure the Contractor has sufficient financial resources. At each QFR, the Contractor shall report the following (at a minimum) for all exercised CLINs (CDRLs TBD):

• Cost/Schedule performance and variances against plan

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

• Unexpended funding on expired CLINS available for de-obligation in any amount

C.3.3.4. Meeting Support

The Contractor shall prepare agendas, record and distribute meeting minutes, and presentation materials for

Contractor-hosted meetings, QPRs, QFRs, IPTs, design reviews, and all other meetings/reviews (CDRLs TBD).

The Contractor shall e-mail informal meeting agendas to appropriate Government stakeholders ten (10) business days prior to meetings for Government input and feedback.

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 unclassified 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 Contractor shall provide the web-teleconference information to the COR and the APM one

(1) week prior to meetings.

C.3.4. Software Licenses

The Contractor shall procure software licenses leveraging existing DoD or DoN Enterprise License Agreements to support delivery of CIS baselines.

NDI. The Contractor shall procure software licenses for non-GFP NDI products delivered in this contract including both Contractor developed and third (3rd) party NDI. If the Contractor obtains a license for any NDI incorporated into a deliverable under this contract, the Contractor shall notify the Government. This notification shall specify whether the license(s) are transferable to the Government and/or any of its other Contractors. The license shall be of the appropriate scope to allow the Government to develop, maintain, use, release, disclose and support (including updates and modifications) the end item throughout the life cycle of the product.

Modified NDI. The Contractor shall provide to the Government all licenses and documentation required to support any NDI that is modified by the Contractor.

The Contractor shall provide copies of license agreements related to all COTS and NDI components.

C.3.5. Government Access to Contractor Facilities and Digital Environment

The Government and Government- designated representative’s access includes individuals from both the U.S. and the

Australian Governments. The Contractor shall enable and facilitate the Government and Government-designated representative’s access to Contractor facilities and Contractor integrated digital environment (IDE) databases (e.g., Dynamic Object-Oriented Requirements System, PTR database). Government personnel attendance will be controlled by the PMS425’s Program Manager. Government support contractors may seek access to facilities and digital environments and will be subject to appropriate controls, such as non-disclosure agreements and Government sponsorship.

The Contractor shall provide secure office space and provide office services for up to three (3) technical representatives, authorized by the Government, on-site at the Contractor’s facility beginning at contract award and continuing through the end of the contract.

The Government may witness all Contractor efforts (to include all peer reviews, tests, test-like events, and inspections) to accomplish the SOW requirements and maintains the right to comment on processes. The Contractor shall notify the Government a minimum of fourteen (14) calendar days in advance of any peer review, test, major event, and/or inspection.

C.3.6. Integrated Product Teams, Peer Reviews, and Working Groups (WG)

The Contractor shall support the following Government-established IPTs and WGs or any similar replacement IPTs:

• SWFTS IPT and WG Structure o ILS & Engineering Change Instruction WG

• CIS IETM Development Group

• IETM to IETM Linking WG

• S1000D IETM data display/IETM Tools WG

• PTR Review Board

• Applicable APB IPT Forums

• VIRGINIA, OHIO, and COLUMBIA Class new construction technical team meetings and platform integration teams

• CIS baseline design reviews and WGs

• Agile ceremonies as identified in the SEP Agile Addendum

The Contractor shall support splinter groups of the above IPTs/WGs and other weekly, bi-weekly, etc. and PMS425, SWFTS, and Ship Acquisition Program Manager coordination meetings. The Contractor shall participate in and conduct meetings, conferences, teleconferences, video teleconferences, drumbeats, IPTs, peer reviews, and working groups. Participating and conducting includes meeting preparation, possible travel, attending meetings and providing technical and schedule details for the IPT, peer review, or working group to make decisions.

The Contractor may, in agreement with the Government, establish additional IPTs with members from Government, the Contractor, subcontractors, industry partners and vendors to address specific programmatic issues or to support general SWFTS CIS development and fielding. For Contractor-established IPTs, the Contractor shall develop IPT charters and present these charters during program reviews for Government approval.

C.3.7. Risk Management

The Contractor shall continuously assess and manage program and technical risks IAW the PMS425 Risk

Management Plan. The Contractor shall identify technical and non-technical risks, risk impacts, conduct risk assessments, develop mitigations to effectively manage these risks, and track potential impacts to cost, schedule, or performance. Risk analysis shall be provided in the Contractor’s Progress and Status Reports (CDRL TBD), weekly synopsis emails, and presented during program and technical reviews.

The Contractor shall support the PMS425 Risk Management Board and WG meetings IAW the PMS425 Risk

Management Plan. The Contractor shall elevate high priority SoS impact risks to the SWFTS Execution IPT.

C.3.8. Quality Assurance

The Contractor shall implement and maintain a quality assurance (QA) program. The Contractor shall develop, present, implement, and supplement quality and timeliness control procedures to meet the standards set forth in the

SOW. The quality management process shall include the following key QA activities:

• Establish and implement a quality control program

• Monitor and control critical processes and product variation

• Establish mechanisms for feedback of field product performance

• Implement an effective root-cause analysis and corrective action system

• Continuous process improvement

C.3.9. Configuration Management

In addition to the requirements of C-243-H003, the following requirements pertain to CM.

The Contractor shall maintain a CIS Configuration Management Program (CMP) consistent with the principles and processes contained within the PMS425 CMP and the PMS425 SEP (Attach J-#). The Contractor shall support

Government oversight and audits of the Contractor’s configuration management and control process.

Engineering Change Proposals (ECPs), Notice of Revisions (NORs) and Requests for Variance (RFVs) shall be unclassified (CDRLs TBD, TBD, TBD). Classified data essential to the Government’s evaluation and disposition of an ECP, NOR, or RFV must be submitted separately and referenced in the unclassified submission.

The Contractor shall support the preparation of Government-generated engineering change instruction documents necessary to retrofit approved Class I Engineering Changes into delivered kits.

ECPs shall not be submitted for new TI/APB configurations prior to the first successful delivery readiness review;

the PTR and/or SWFTS NBCR processes shall be used for defining configuration baseline changes for any in-development (prior to first delivery readiness review (DRR)) TI/APB. ECPs shall only be submitted post-DRR to support either the next TI/APB configuration to be developed or to satisfy an urgent change to a legacy TI/APB configuration. Approved ECPs shall be considered as new Capability Items (CI) to the relevant TI/APB configuration.

The Contractor shall revise ECP(s) as required by the Government’s reviews.

The Contractor shall prepare and submit a NOR concurrent with ECPs that would require revision to any

Government specification or technical document if the ECP was approved. The NOR shall be used to describe the proposed change to the document (CDRL TBD).

The Contractor shall classify deviations IAW the PMS425 CMP.

C.3.10. Data Deliverables

C.3.10.1. Data Management

The Contractor shall implement data management procedures for complete and timely flow of data deliverables and track document versions, clearly identifying document changes/additions. The Contractor shall plan, schedule, and report the status of all Contractor and subcontractor data generated in support of this contract. The Contractor shall deliver a data accession list (CDRL TBD). All data shall be developed, managed, used, and delivered/exchanged electronically. The Contractor shall maintain proper levels of data control and security IAW program protection plans and IA guidelines.

C.3.10.2. Data Delivery

All products and data shall be delivered with unlimited usage rights as defined in DFARS clauses 252.227.7013, 252.227-7014, and 252.227-7017 and appropriately marked as such, unless a waiver has been submitted and approved by the Government. A report verifying the appropriate markings, including security classification, and data rights shall be delivered with the product.

The Contractor shall upload all unclassified CDRL documents to the (Advanced Interactive Management

Technology Center) AIMTC hosted by NUWCDIVNPT, or identified replacement, to include all applicable attachments and enclosures. The Contractor shall place data generated on this contract and any software models/applications necessary to use this data on AIMTC. AIMTC will be the digital repository for finished products/contract deliverables and data.

The Contractor shall provide an E-mail notification to the respective “CDRL Distribution List” representatives upon completion of uploading the CDRL delivery to AIMTC. The notification shall include the Contract #, CDRL Item #, Title/Subtitle, the classification, the method of delivery (posting to AIMTC, hard copy via regular mail, etc.), and the path and link to the AIMTC location.

The CDRL document deliverable shall include a cover page with CDRL Item Number, CDRL Title and Subtitle, classification, Distribution Statement, and Cage Code/ Document # and Document date. When numerous items are provided under a specific CDRL, the Contractor shall include unique identifiers to identify the CDRL delivery.

The Contractor shall make available to Government on-site technical representatives all program data (e.g., working documents, databases, test results), including electronic access to computer files, that pertain to the Contractor and subcontractor activities in the performance of this contract. The Government may request the Contractor to deliver internal data developed or modified under this contract.

The Contractor shall comply to Controlled Unclassified Information marking guidance per DoDI 5200.48.

The Contractor shall tailor delivered data to the appropriate releasable country level for United States and Australia deliverables (e.g., SPS source code).

C.3.11. Public Key Infrastructure

Portions of product development require access to Government networks. The DoD has established the External

Certification Authority (ECA) program to support the issuance of DoD approved Public Key Infrastructures (PKI) certificates to industry partners and other external entities and organizations. The ECA program is designed to provide the mechanism for these entities to securely communicate with the DoD and authenticate to DoD

Information Systems. An ECA is required for AIMTC access for CDRL delivery and transfer of other program and contract data including CUI documentation.

The Contractor shall procure ECA certificates from the approved list of ECA vendors (https://public.cyber.mil/eca).

The certificates shall be procured within 30 days of contract award.

The Contractor shall have PKI certification and a static internet protocol address (or group of addresses) to access

AIMTC. The Contractor shall coordinate with the Government on the approach to handling classified data and/or the requirement to access the SIPRNET or other encrypted links. CUI submitted via e-mail shall be digitally signed and encrypted.

C.3.12. Systems Engineering

The Contractor shall provide a Systems Engineering Lead for all engineering efforts. The Systems Engineering Lead shall apply Systems Engineering processes and SWFTS Integrated Product and Process Development (IPPD) principles to develop CIS baselines.

The Contractor's system engineering processes shall include support for efforts to ensure the "design-in" of high reliability, maintainability, and availability requirements using common authoring standards to ensure seamless, efficient integration with SWFTS. These requirements include 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.

CIS shall be developed IAW SWFTS community design requirements (Attach J-#) managed under and documented by the SWFTS IPT.

Development, Security, and Operations (DevSecOps) principles and best practices shall be implemented for a common, continuous development, integration, test, and delivery environment. This is to provide flexibility and faster decisions to accelerate development and delivery of secure software and accompanying logistics products to the fleet. SWFTS, including AN/BYG-1, shall be developing and delivering software and accompanying logistics products in this secure software development, integration and testing environment with automated tools and processes. The Contractor shall develop and deliver CIS software and logistics products to the DevSecOps environment in support of the future baselines.

The CIS includes a CCE and RCE to provide the runtime infrastructure environment to host SWFTS applications.

The runtime infrastructure includes network and connectivity services, cybersecurity services, SoS services, application hosting, video distribution, and system management.

The Contractor shall develop the Production CCE and RCE environments based on the CIS Performance

Specification (P-SPEC) (Attach J-#), SWFTS service level agreements (SLAs), latest available SWFTS CCE developed under TI22, and direction from the SWFTS IPPD community.

C.3.13. Agile Development Plan

The Contractor shall provide an Agile Development Management Plan (ADMP) no later than 60 calendar days after contract award (CDRL TBD). The ADMP shall consolidate the content requirements covered in a configuration management plan, software development plan, test and evaluation program plan, and systems engineering management plan into one synchronized document applying agile methodologies. The ADMP shall describe the

Contractor’s approach for planning, controlling, and conducting a fully integrated engineering effort using agile methodologies. The Contractor shall ensure the ADMP incorporates the principles and effectively aligns with the

DoD Enterprise DevSecOps Reference Design (Attach J-#), SWFTS processes (Attach J-#), and the PMS425 SEP

(Attach J-#).

The ADMP process shall ensure the compatibility, interoperability, and integration of all functional and physical interfaces. The ADMP shall ensure 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.