D5LE2 SOW_NEWFOLLOWON_2024_DRAFT for SSN Purposes.docx

STATEMENT OF WORK

CLIN 0001 Trident D5 Life Extension 2 (LE2) Systems Engineering (CPFF/LOE) (WPN)

During the period of 01 October 2024 through 30 September 2025, the Contractor shall make available and employ its facilities, personnel at the level of effort (LOE) set forth in Section F, services of others, and materials, and shall use its best efforts to perform the following:

1.1 D5LE2 Systems Engineering Management

· Perform Systems Engineering Management activities to include:

· Develop, deliver, and execute System Engineering Management Plans (SEMP) to include, but not limited to, a Plan of Action and Milestone (POA&M) schedule, with time-phased execution and resource allocations to execute program support requirements (CDRL A0XX) supporting identified D5LE2 program efforts

· Develop and maintain schedules for the overall system engineering activities, Requirements IPT, System Design and Assessment (SDA) IPT, Integration Working Group, and Verification Working Group deliverables and activities through the Initial Operating Capability milestone

· Conduct Technical Data Management and Configuration Management activities for D5LE2 Systems Engineering data and artifacts

· Maintain Configuration and Data Management tools, storage, and account access in support of D5LE2 Systems Engineering

· Conduct Risk, Issue, and Opportunity identification, development, management, and resolution for the D5LE2 Systems Engineering Group

· Provide support to the D5LE2 Systems Engineering Management Team

· Develop technical content for D5LE2 program level systems engineering documents, to include but not limited to the Systems Engineering Plan

· Update the SSP Systems Engineering Process Ordnance Document (CDRL A0XX)

· Conduct Program Management Reviews

· Lead, coordinate, prepare, plan, deliver plan, and close out a model based SWS Preliminary Design Review (PDR) for the D5LE2 program (CDRL A0XX)

· Identify, coordinate, and review entrance and exit criteria and deliverables for the PDR

· Plan, prepare for, and participate in familiarization events, dry runs, and pre-briefs leading to PDR

· Prepare briefing materials and execute PDR

· Conduct closeout activities and close action items from PDR

· Provide engineering services in support of the system-level integration of the subsystem KPs, SRSAs and SETR events and artifacts/outputs

· Provide expert knowledge of the Technical Objectives & Guidelines (TOG) to facilitate subsystem traceability and verification planning. Participate in subsystem traceability and verification activities

· Provide expert knowledge of the architecture and interfaces to facilitate subsystem traceability and integration planning. Participate in subsystem traceability and verification activities

· Assess and deliver a report on subsystem artifacts in support of system level activities (CDRL AXXX)

1.2 D5LE2 Systems Requirements and Architecture Maintenance

· Perform ongoing Strategic Weapon System (SWS) Requirements Management including:

· Co-Lead, with the Government, the Requirements IPT

· Manage and maintain requirements for the D5LE2 Technical Objectives & Guidelines (TOG)

· Deliver the TOG for Preliminary Design Review (PDR) based on information available at the time (A0XX)

· Maintain requirements management plans and processes

· Maintain and manage the Requirements Verification and Traceability Matrix (RVTM) (CDRL A0XX)

· Maintain and deliver the Requirements Development and Management Implementation Plan (RDMIP) (CDRL A0XX)

· Perform ongoing SWS Architecture and Interface development and management including:

· Co-Lead, with the Government, the System Design and Assessment IPT

· Deliver updated Architecture Definition for Preliminary Design Review (PDR) (develop plans, management, traceability, records, trade studies (CDRL A0XX) based on information available at the time

· Maintain and deliver Descriptive System Modeling (DSM) plans (CDRL A0XX)

· Manage and maintain the interfaces and architectures

· Maintain and execute the Strategic Systems Programs (SSP) Coordination Process

· Maintain and deliver Interface Development Management Plan (IFDMP) (CDRL A0XX)

· Coordinate with all SSP technical branch stakeholders to create and mature plans for the orderly transition between the current and future-state SWS technical information

1.3 D5LE2 System Integration, Verification and Validation (IV&V) Management

· Provide IV&V engineering services for D5LE2 as follows:

· Co-Lead, with the Government, the Integration Working Group and the Verification and Validation (V&V) Management working Groups

· Lead the overall D5LE2 system integration effort, coordinating with other stakeholders as required

· Lead the overall D5LE2 system verification effort, coordinating with other stakeholders as required

· Lead the overall D5LE2 system validation effort, coordinating with other stakeholders as required

· Update, deliver, and maintain the D5LE2 SWS Integration Plan (CDRL A011) based on information and artifacts available at the time to integrate:

· SWS subsystems with other SWS subsystems,

· SWS subsystems into the SWS system, and

· SWS with the COLUMBIA and OHIO class submarines

· Provide IV&V technical SME guidance in requirements, architecture, integration, Verification and Validation (V&V), and test to working groups and integrated product teams

· Identify environment, facility, personnel, modeling and simulation, software, hardware, and other resource needs to support IV&V

· Develop, deliver, maintain, and manage the ITM based on information and artifacts available at the time (CDRL A0XX)

· Develop and deliver an LE2 Modeling and Simulation (M&S) Management Plan (CDRL A013) in support of IV&V activities

· Identify M&S capability gaps and deliver proposal to the Government to fulfill those capability gaps

· Develop M&S guidance for technical branches to deliver M&S products to the system level (CDRL A0XX)

· Update, deliver, and maintain the D5LE2 SWS Verification and Validation Plan (CDRL A012) based on information and artifacts available at the time to:

· Verify requirements contained in the D5LE2 System Requirements Specification, and

· Validate requirements contained in the D5LE2 Mission Requirements Book and Decision Coordination Paper (DCP)

· Conduct general verification and validation documentation reviews and impact analyses XXX

· Develop proficiency in capability and uses of resources (software, hardware, models and simulations) at designated test sites

1.4 D5LE2 System Digital Integration

· Perform SWS digital non-real time functional integration activities IAW the D5LE2 Integration Plan to include:

· Deliver and maintain plans and processes to execute the SWS system level integration tasking (CDRL A0XX)

· Conduct proof of concept integration activities and deliver a report of the results (CDRL A0XX)

1.5 D5LE2 System Verification

· Perform Strategic Weapon System (SWS) system verification activities IAW the D5LE2 Verification and Validation Plan to include

· Assess the verifiability of requirements when requirements are modified

· Develop and refine verification methods, identify supporting activities and events, and other data for input to the RVTM

· Deliver and maintain plans and processes to execute the SWS system level V&V Plan (CDRL A0XX)

CLIN 0002 Trident D5 Life Extension 2 (LE2) Configuration Management (CM) (CPFF/LOE) (WPN)

During the period of 01 October 2024 through 30 September 2025, the Contractor shall make available and employ its facilities, personnel at the level of effort set forth in Section F, services of others, and materials, and shall use its best efforts to perform the following:

· Provide and maintain D5LE2 technical data support activities to include:

· Maintain current, consistent, enduring and authoritative sources for SSP D5LE2 digital models and data IAW Data Management Plan (CDRL A00X). Plans should include industry best practices to promote sharing data across organizations and lifecycle activities. Ensure that development, quality, security, and accessibility of the technical information architecture supports the business strategy

· Assist with the development and management of the D5LE2 technical data management policy outlining appropriate data stewardship and data audit requirements, as well as contractor service-level agreements, to support the appropriate quality and use of information in business and IT processes

· Coordinate with SSP stakeholders to create and mature road maps for the orderly transition between the current and future-state technical data governance architectures

· Identify CM data, integrate D5LE2 technical data and data sources using existing SSP electronic data management systems and deliver (CDRL A00X) reports.

· Provide Government Furnished Item (GFI) DM services for D5LE2 specific GFI

· Provide support for D5LE2 CM Strategic Systems Programs Alteration (SPALT) activities to include:

· Maintain SSP CM D5LE2 SPALT implementation plan (CDRL A00X)

· Establish and maintain D5LE2 SPALT information in the SSP SPALT database by receiving SPALT data from program participants and providing timely accurate responses to the Technical Branches as well as SSP identified stakeholders.

· Establish the D5LE2 SPALT review workflow process and associated data, provide technical and programmatic support for the SPALT review process and deliver plan (CDRL A00X)

· Coordinate and deliver the System Level Impact Analysis of unapproved D5LE2 SPALT Requests (CDRL A00X) and SPALT dependencies for each unapproved SPALT Request and superseded SPALT (CDRL A00X)

· Review D5LE2 draft SPALT Requests and SPALT Implementation utilizing OD 70035 for compliance with SSP procedures, results and plans

· Assist with SWS D5LE2 SPALT Request

· Assist with SWS D5LE2 SPALT Implementation Plan

· Establish and control D5LE2 Configuration Items (CI) and structure within the CM Product Lifecycle Management (PLM) toolset and deliver (CDRL A00X)

CLIN 0003 Trident D5 Life Extension 2 (LE2) System Security Engineering (CPFF/LOE) (RDT&E)

During the period of 01 October 2024 through 30 Sept 2026, the Contractor shall make available and employ its facilities, personnel at the level of effort set forth in Section F, services of others, and materials, and shall use its best efforts to perform the following:

The contractor shall provide System Security Engineering (SSE) support for the D5 LE2 SPALT effort leading to PDR in accordance with OD 65406 and OD71694.

· Provide direct support through Subject Matter Expertise (SME) and SSE management planning

· Provide systems integration functions for SSE in preparation for D5LE2 Systems Engineering Technical Reviews (SETR), specifically subprogram PDR, SDR/KP-1, and PDR/SRSA-2, as well as other leadership level reviews to include Technical Director or Director Reviews as required.

· Deliver a System Security Engineering D5LE2 PDR Assessment (CDRL A0XX)

· Provide systems engineering support for Trident II Criticality Analysis (CA) mission threads that have not been completed prior to SRR to define the complete set of system level Trident II D5 SWS Mission Critical Functions (MCFs) and Critical Components (CCs) (CDRL AXXX).

· Provide Model Based Engineering support for integration of SSE requirements, trust zones, MCFs, CCs, and security control traceability into the DSM.

· Provide the structure for and development of a Blue Force Database (CDRL AYYY)

· Provide support for SSE updates the D5LE2 SCG Annex as required by SP333

· Provide Supply Chain Security support including:

· Support the development and maintenance of D5LE2 Supply Chain Security Plans, Vendor Authoritative Unified List (VAULT)

· Support to maintain SCS risk and mitigation information as required

· Support Secure Packaging, Handling, Storage, Transportation, Vendor Analysis, Blind Buy, and Counterfeit Part policy, process, planning, monitoring, and execution as required

· Support branch and system level meetings, briefs, and collaboration as requested

· Deliver D5LE2 SWS Supply Chain Security Assessment Report for each system level SETR or as requested (CDRL A00X)

· Provide Criticality Trust and Assurance support including:

· Support for critical program information assessments for D5LE2 subsystems (missile and guidance) prior to each SETR. Review proposed CPI for submission to SP201 as candidate-CPI.

· The D5LE2 Anti-Tamper Concept Plan (CDRL AZZZ)

· Support to maintain the D5LE2 critical program information, critical components and mission critical functions list (CDRL A00X)

· Perform non-enterprise Cybersecurity support of D5 LE2 SWS including

· Support any updates or comment adjudications to the D5LE2 SSE Strategy for sPDR

· Support for traceability and analysis of security controls to system and sub- system requirements.

· Management services for the Information Assurance (IA) Vulnerability Management Program associated with non-enterprise systems, as required by OD 68327, including monitoring all IA alerts and bulletins issued, sending notifications to points-of- contact for affected systems, tracking responses and completion of mitigation plans submitted, and delivering status reports to SP2012 (CDRL A00X)

CLIN 0005 Trident D5 Life Extension 2 (LE2) Safety Risk Management (CPFF/LOE) (WPN)

During the period of 01 October 2024 through 30 September 2025, the Contractor shall make available and employ its facilities, personnel at the level of effort set forth in Section F, services of others, and materials, and shall use its best efforts to perform the following:

· Perform Safety Risk Management activities for D5LE2 including the following:

· Conduct safety reviews and assessments of, and provide safety support for, D5LE2 alterations plans (SPALT, Ship Alteration (SHIPALTs)/ Trident Ship Alteration (Naval Sea System Command) (TRIDs), Temporary Alteration(s) (TEMPALTs), Operational Alteration(s) (OPALTs), and Nuclear Weapon(s) Retrofit Orders (NWROs) and deliver all documents via CDRL AXXX

· Conduct safety assessments of D5LE2 system interfaces, including performing safety engineering reviews of Coordination artifacts, and proposed SWS system architectures,

· Participate in the development of D5LE2 system safety requirements

· Participate in D5LE2 Trade Studies providing nuclear weapon system safety risk management expertise,

· Provide support to develop and maintain D5LE2 features in the Nuclear Weapon System Surety Model (NWSSM),

· Support D5LE2 nuclear weapon system safety risk management architecture development,

· Provide support in the creation of safety assessment artifacts to support D5LE2 systems engineering and technical review (SETR) milestones (e.g. Systems Requirements Review (SRR)).

CLIN 0006 Trident D5 Life Extension 2 (LE2) Infrastructure Operations and Environment Cybersecurity (CPFF/LOE) (RDT&E)

During the period of 1 October 2024 through 30 September 2026, the Contractor shall make available and employ its facilities, personnel at the level of effort (LOE) set forth in Section F, services of others, and materials, and shall use its best efforts to perform the following:

6.1 Systems Engineering Support for SSP D5LE2 Infrastructure Operations (Model Based Engineering – MBE)

The contractor shall provide systems engineering support for Strategic Systems Programs (SSP) Electronic Working Environment to support D5LE2 MBE including:

· Identify and implement strategies to improve business performance through enterprise information solutions and capabilities within the context of the D5LE2 MBE environment.

· Provide operational support for the D5LE2 MBE environments integrated Information Systems (IS),

· Provide support for the configuration control of SSP D5LE2 MBE environment IS support technology equipment and facilities,

· Coordinate the planning, design, and deployment of IS resources in support of the D5LE2 MBE environment,

· Provide tailored electronic D5LE2 MBE environment support services, including messaging, collaboration, remote access, classified processing, access management, data access, supporting resources, supporting communication networks, and external communication networks, desktops and virtual desktops necessary for SSP workforce and business partners to complete work loads

· Coordinate D5LE2 MBE environment messaging services with Fleet Ballistic Missile (FBM) and other SSP business partners,

6.2 Systems Engineering Support for SSP D5LE2 MBE Environment Cybersecurity

The contractor shall provide systems engineering support for D5LE2 MBE environment Information Assurance (IA) including:

· Provide technical and management services for IA activities, and deliverables including conducting security risk assessments, security test and evaluation, system certification, and accreditation of the D5LE2 MBE environment Platform Information Technology and SWS support systems,

· Provide support for evaluating current and emerging cyber threats and their impact to D5LE2 MBE environment IS.

CLIN 0008 Trident D5 Life Extension 2 (LE2) Special Projects (CPFF/LOE) (RDT&E)

During the period 1 October 2024 through 30 September 2027, the Contractor shall make available and employ its facilities, personnel at the level of effort set forth in Section F, services of others, and materials, and shall use its best efforts to perform the following:

Provide support services relating to the development of future weapon systems to significantly enhance capability and performance in the areas of systems engineering, configuration management, data management, test engineering, safety engineering, system security engineering, SPALT, technical documentation, and touch labor support for Special Projects as defined by SP201. These services shall be provided in accordance with all pertinent SSP policies and procedures. The special project will utilize a skillset of electrical, mechanical, systems engineers, technologists, and program analysts to develop future weapon system solution capabilities that will significantly enhance Fleet performance and solves advanced weapon system problems and failures in support of the Fleet.

The contractor will deliver a Technical Instruction Project summary report in accordance with CDRL A0XX.

See SSP H-18 Technical Instructions.

CLIN 0009 Trident D5 Life Extension 2 (LE2) Special Projects (CPFF/LOE) (WPN)

During the period 1 October 2024 through 30 September 2027, the Contractor shall make available and employ its facilities, personnel at the level of effort set forth in Section F, services of others, and materials, and shall use its best efforts to perform the following:

Provide support services relating to the development of future weapon systems to significantly enhance capability and performance in the areas of systems engineering, configuration management, data management, test engineering, safety engineering, system security engineering, SPALT, technical documentation, and touch labor support for Special Projects as defined by SP201. These services shall be provided in accordance with all pertinent SSP policies and procedures. The special project will utilize a skillset of electrical, mechanical, systems engineers, technologists, and program analysts to develop future weapon system solution capabilities that will significantly enhance Fleet performance and solves advanced weapon system problems and failures in support of the Fleet.

The contractor will deliver a Technical Instruction Project summary report in accordance with CDRL A0XX.

See SSP H-18 Technical Instructions.

CLIN 0010 Trident D5 Life Extension 2 (LE2) Product Support and Supportability Engineering (CPFF/LOE) (WPN)

During the period of 01 October 2024 through 30 September 2025, the Contractor shall make available and employ its facilities, personnel at the level of effort set forth in Section F, services of others, and materials, and shall use its best efforts.

· Product Support and Supportability Engineering Support for D5LE2:

· Provide supportability engineering subject matter expertise in support of system and subsystem technical reviews including SRR/PDR and Flight and Shipboard system SRSAs

· Provide subject matter expertise in the review and update to the Trident II D5LE2 Technical Objectives and Guidelines (TOG)

· Provide technical expertise to the creation of D5LE2 subsystem development contracts to ensure incorporation of product support best practices

· Support technical branches and PMOs in the development of product support tools and models including but not limited to: OPUS, Windchill Risk and Reliability (WRR) models

· Support technical branches with the product support analysis of Original Equipment Manufacturing (OEM) contractor deliverables

· Serve as the product support technical expert and liaison to system engineering, test and evaluation, supply chain management and industrial base management meetings

· Provide technical and administrative support to all cross branch product support meetings

· Support technical branch and Program Management Offices in the development of subsystem Lifecycle Sustainment Plans (LCSP)

· Jira, Confluence and SSP Rainbow Network Administrator Support for D5LE2:

· Establish, maintain and manage a product support folder within SSP Blue

· Electronically file and maintain configuration control over SP206P documents via Confluence

· Manage internal tasks, action items, and external deadlines via Jira

· Serve as an administrative interface between the SSP system engineering and product support to ensure product support team compliance with deliverables on SSP Blue and SSP Red

· Electronic Product Lifecycle Management (ePLM) Support for D5LE2:

· Provide subject matter expertise to the development of a system and/or subsystem specific ePLM to ensure each tool is architected with a product support oriented product structure

· Serve as the product support liaison to ePLM and configuration management meetings

· Product Support Competency Development Support for D5LE2:

· Provide technical expertise to the development of SWS level product support policy, guidance and best practice documentation

· Provide technical expertise to the development of product support professional development training materials

· Provide administrative support for the development of product support competency related briefings and documentation

CLIN 0011 Trident D5 Life Extension 2 (LE2) System Test (CPFF/LOE) (WPN)

During the period 1 October 2024 through 30 September 2025, the Contractor shall make available and employ its facilities, personnel at the level of effort set forth in Section F, services of others, and materials, and shall use its best efforts to perform the following:

11.1 D5LE2 System Physical Integration

· Perform SWS physical integration activities IAW the D5LE2 Integration Plan to include:

· Develop proficiency in capability and uses of resources (software, hardware, models and simulations) at designated test sites

· Perform preliminary Hardware in the Loop (HWIL) integration of subsystem models and simulations IAW the Integration Plan and ITM as they become available and based on information and artifacts available at the time

· Deliver assessments of preliminary physical component interface compliance and interoperability based on information and artifacts available at the time

11.2 D5LE2 System Verification

· Perform Strategic Weapon System (SWS) system verification activities IAW the D5LE2 Verification and Validation Plan to include:

· Develop Test Procedures to test D5LE SRS requirements

· Perform preliminary test activities IAW the V&V Plan, Test Plan, and RVTM as they become available and based on information and artifacts available at the time

· Deliver preliminary Test Reports based on information and artifacts available at the time

CLIN 0012 Trident D5 Life Extension 2 (LE2) Technical Information Tools and Applications (CPFF/LOE) (WPN)

During the period 1 October 2024 through 30 September 2025, the Contractor shall make available and employ its facilities, personnel at the level of effort set forth in Section F, services of others, and materials, and shall use its best efforts to perform the following:

12.1 D5LE2 Technical Information Technology (IT) Program Management Services

· Develop and deliver an integrated program plan across all SP201 cognizant tools and applications that support the active management of system level technical data for D5LE2 in-service support under the cognizance of the Chief Engineer (SP201) (CDRL AXXX). This delivery includes, but is not limited to:

· Identification of required resources to execute this CLIN.

· A Plan of Actions and Milestones (POA&M) with traceability to higher level programmatic schedules (e.g. SPOSE and JPR).

· Provide IT focused advice and support for the development of policies and processes for configuration managed and data managed datasets in support of D5LE2.

· Provide IT focused advice and support for the development of policies and processes related to program protection of D5LE2 data under the cognizance of SP201.

12.2 D5LE2 Data & Information Technology (IT) Architecture

· Develop and deliver a Data Strategy to support the active management of D5LE2 in-service system level technical data support under the cognizance of the Chief Engineer (SP201) (CDRL AXXX). This delivery includes, but is not limited to:

· Identification of configuration managed and data managed datasets under the cognizance of SP201.

· Identification of relationships between data elements within and across datasets under the cognizance of SP201 required to support integrated engineering analysis of the D5LE2 system.

· Identification of policies and processes used to manage datasets under the cognizance of SP201 and identification of process integration opportunities within and across SP201 cognizant datasets.

· Identification and definition of IT Architecture to support the management and integration of configuration managed and data managed system level technical data for in service support of the D5LE2 Program under the cognizance of the Chief Engineer (SP201). The IT Architecture shall focus on the configuration and integration of Government-Off-The-Shelf (GOTS) or Commercial-Off-The-Shelf (COTS) software. Customization of COTS software and development of custom software shall be minimized.

12.3 D5LE2 Data Management Implementation

· The contractor shall provide Data Management services for D5LE2 as follows:

· Design, develop, and deliver tools and applications (CDRL A0XX) that manage datasets under the cognizance of SP201. This includes but is not limited to:

· Identification of appropriate tool per the data and IT architecture to support a given datasets.

· Establishing data elements with associated metadata required to enable efficient search and discovery.

· Establishing workflows to implement the policy and processes for a given dataset.

· Investigation and development of cross tool or application integration to support the digital thread.

· Investigation and development of cross-classification-domain data integration.

· Manage User Accounts within the purview of technical applications under the cognizance of SP201.

· Provide SSP Community training in the use of the IT tools and applications implemented within this CLIN.

CLIN 00XX Contract Data Requirements List (CDRLs) (Not Separately Priced)

The data called for in this Statement of Work shall be delivered in accordance with the applicable CDRL, DD Form 1423, Section J, Exhibit A. Non-CDRL deliverables required under the Statement of Work shall be delivered pursuant to the requirements of the contract. All deliverables shall be submitted electronically. Electronic delivery of technical data and software required by the CDRLs, or any other requirement of this contract, shall constitute delivery for purposes of the technical data and software clauses incorporated into Section I of this contract. All reports shall be inspected and approved by the Contracting Officer’s Representative (COR).

Not separately priced. The cost is included in the cost of the applicable CLINS. Financial / Status Reporting CDRLs In addition to the technical CDRLs identified in the SOW above, the following financial related CDRLs shall be delivered in accordance with the content and timeline requirements identified in the CDRLS, Section J, Exhibit A:

A0XX – Quarterly Expenditure Report A0XX - Quarterly Contractor Financial Management Report A0XX - LOE Post Completion Report

CLIN 00XX Contractor Acquired Property (CAP) (Not Separately Priced)

Delivery of CAP under this line item shall be completed as soon as the CAP item is identified if the value of the item meets or exceeds the capitalization threshold as identified in the memorandum issued jointly by the Under Secretary of Defense (USD) Comptroller and the USD (Acquisition, Technology, and Logistics) on 20 September 2013, entitled, “Elimination of Military Equipment Definition and Increase to Capitalization Thresholds for General Property, Plant and Equipment” or if the item is categorized as special tooling, special test equipment, or equipment designated for preservation and storage under a major defense acquisition program (see Section 815 of the National Defense Authorization Act for Fiscal Year 2009 (Pub. L. 110-417).

"Residual CAP" means property acquired, fabricated, or otherwise provided by the Contractor for performing this contract, and to which the Government has title pursuant to FAR 52.245-1 (e)(3), and that is not incorporated in, or consumed in the production of, a deliverable under this contract. This includes any CAP items identified through plant clearance in accordance with the clause at DFARS 252.245-7004, Reporting, reutilization, and Disposal; inventory reports provided by the Contractor in accordance with FAR clause 52.245-1; or other reporting requirements, as specified in this contract. All Residual CAP shall be delivered upon completion of performance under all Contract Line Items.

During contract performance, oversight and visibility of CAP shall be accomplished through reviews and audits of Contractor business systems, including the Contractors accounting systems, property management systems, and material management and accounting in accordance with FAR 52.245-1, Government Property.

The contractual transfer of accountability for CAP from one contract to another is prohibited. Only upon delivery and acceptance by the Government under this line item can this property be transferred to other contracts and/or other locations not currently specified under a line item or exhibit of this contract as Government-furnished property (GFP), with written authorization by the Contracting Officer. Written authorization may only be accomplished by contract modification(s) issued on a Standard Form (SF) 30 by the Contracting Officer, or as delegated to the Administrative Contracting Officer (ACO), to execute transfers of Government property accountability between existing contracts. No other forms or documents, such as the DD Form 1149, Requisition and Invoice/Shipping Document, are authorized for the transfer of Government property (CAP or GFP) accountability from one contract to another. Upon delivery and acceptance by the Government, and when retained by the Contractor for use under this contract, the delivered CAP items become GFP and shall be added to the contract and referenced under the GFP list attached to the contract in Section J. A list in the format outlined in CDRL A015 shall accompany all deliveries of CAP under this contract.

When delivering CAP and updating this list (CDRL A015):

A. The value of any delivered CAP item shall be at the Contractor provided fully burdened cost, i.e., normal or provisional burdens to the direct costs in accordance with the applicable disclosed accounting practices, including an appropriate amount for fee or profit (as reflected in the contract under which the estimate is prepared) in addition to the direct and indirect costs.

B. Unless otherwise noted by the Contractor at the time of delivery to the Government, the placed-in-service date shall be the date of acquisition or, if fabricated, the date of completed manufacture.

Applicable to all CLINs

1. NMCARS 5207.103(d)(i):"The contractor shall not assert any claim, in any jurisdiction, based on trademark or other name or design-based causes of action that are based on rights the contractor believes it has in the term(s): SSP (Strategic Systems Programs), PMOSSP (Shipboard Systems), PMOSSP (Flight Systems), SWFPAC (Strategic Weapons Facility Pacific), SWFLANT Strategic Weapons Facility Atlantic), POLARIS, POSIEDON, TRIDENT, TRIDENT II, D5LE2 (Life Extension), NTIP (Naval Treaty Implementation Program), NOTU (Naval Ordnance Test Unit), CPS (Conventional Prompt Strike), FBM Operational Test Support Unit Two, SPUK (Strategic Systems Program Liaison Office), (the "Designation(s)"), against the Government or others authorized by the Government to use the Designation(s) (including the word(s), name, symbol, or design) acting within the scope of such authorization (i.e. claims for trademark infringement, dilution, trade dress infringement, unfair competition, false advertising, palming off, passing off, or counterfeiting). Such authorization shall be implied by the award of a Government contract to any party for the manufacture, production, distribution, use, modification, maintenance, sustainment, or packaging of the products and services identified under this contract, and the scope of such implied authorization is defined as the use of the Designation(s) in performance under such contract by the prime contractor and its subcontractors and suppliers at any tier. In all other cases, the scope of the authorization will be defined by the Government in writing.

2. MOSA - Interfacing development: The contractor and its subcontractors will follow DOD INST 5000.02 dated (August 10, 2017) as to Modular Open Systems Approach (MOSA) to the Major System Interfaces and ensure that the Government will acquire at least Government Purpose Rights (GPR) to data and intellectual property and to minimize proprietary elements to the lowest component level is critical to this effort. This includes all technical data, hardware, computer software, and computer software documentation to all interfaces for the Navy subsystems/elements.

3. The following SOW language supplements DFARS Clause 252.204-7012 cited in Section I in accordance with NMCARS SUBPART 5204.73-SAFEGUARDING COVERED DEFENSE INFORMATION AND CYBER INCIDENT REPORTING:

3.1. System Security Plan and Plans of Action and Milestones (SSP/POA&M) Reviews

a) Within thirty (30) days of contract award, the Contractor shall make its System Security Plan(s) (SSP(s)) for its covered contractor information system(s) available for review by the Government at the contractor’s facility. The SSP(s) shall implement the security requirements in Defense Federal Acquisition Regulation Supplement (DFARS) clause 252.204-7012, which is included in this contract. The Contractor shall fully cooperate in the Government’s review of the SSPs at the Contractor’s facility.

b) If the Government determines that the SSP(s) does not adequately implement the requirements of DFARS clause 252.204-7012 then the Government shall notify the Contractor of each identified deficiency. The Contractor shall correct any identified deficiencies within thirty (30) days of notification by the Government. The contracting officer may provide for a correction period longer than thirty (30) days and, in such a case, may require the Contractor to submit a plan of action and milestones (POA&M) for the correction of the identified deficiencies. The Contractor shall immediately notify the contracting officer of any failure or anticipated failure to meet a milestone in such a POAM.

c) Upon the conclusion of the correction period, the Government may conduct a follow-on review of the SSP(s) at the Contractor’s facilities. The Government may continue to conduct follow-on reviews until the Government determines that the Contractor has corrected all identified deficiencies in the SSP(s).

d) The Government may, in its sole discretion, conduct subsequent reviews at the Contractor’s site to verify the information in the SSP(s). The Government will conduct such reviews at least every three (3) years (measured from the date of contract award) and may conduct such reviews at any time upon thirty (30) days’ notice to the Contractor.

3.2. Compliance to NIST 800-171

a) The Contractor shall fully implement the CUI Security Requirements (Requirements) and associated Relevant Security Controls (Controls) in NIST Special Publication 800-171 (Rev. 1) (NIST SP 800-171), or establish a SSP(s) and POA&Ms that varies from NIST 800-171 only in accordance with DFARS clause 252.204-7012(b)(2), for all covered contractor information systems affecting this contract.

b) Notwithstanding the allowance for such variation, the contractor shall identify in any SSP and POA&M their plans to implement the following, at a minimum:

(1) Implement Control 3.5.3 (Multi-factor authentication). This means that multi-factor authentication is required for all users, privileged and unprivileged accounts that log into a network. In other words, any system that is not standalone should be required to utilize acceptable multi-factor authentication. For legacy systems and systems that cannot support this requirement, such as CNC equipment, etc., a combination of physical and logical protections acceptable to the Government may be substituted;

(2) Implement Control 3.1.5 (least privilege) and associated Controls, and identify practices that the contractor implements to restrict the unnecessary sharing with, or flow of, covered defense information to its subcontractors, suppliers, or vendors based on need-to-know principles;

(3) Implement Control 3.1.12 (monitoring and control remote access sessions) - Require monitoring and controlling of remote access sessions and include mechanisms to audit the sessions and methods.

(4) Audit user privileges on at least an annual basis;

(5) Implement:

i. Control 3.13.11 (FIPS 140-2 validated cryptology or implementation of NSA or NIST approved algorithms (i.e. FIPS 140-2 Annex A: AES or Triple DES) or compensating controls as documented in a SSP and POAM); and,

ii. NIST Cryptographic Algorithm Validation Program (CAVP) (see https://csrc.nist.gov/projects/cryptographic- algorithm-validation-program);

(6) Implement Control 3.13.16 (Protect the confidentiality of CUI at rest) or provide a POAM for implementation which shall be evaluated by the Navy for risk acceptance.

(7) Implement Control 3.1.19 (encrypt CUI on mobile devices) or provide a plan of action for implementation which can be evaluated by the Government Program Manager for risk to the program.

3.3 Cyber Incident Response:

a) The Contractor shall, within fifteen (15) days of discovering the cyber incident (inclusive of the 72-hour reporting period), deliver all data used in performance of the contract that the Contractor determines is impacted by the incident and begin assessment of potential warfighter/program impact.

b) Incident data shall be delivered in accordance with the Department of Defense Cyber Crimes Center (DC3) Instructions for Submitting Media available at http://www.acq.osd.mil/dpap/dars/pgi/docs/Instructions_for_Submitting_Me In delivery of the incident data, the Contractor shall, to the extent practical, remove contractor-owned information from Government covered defense information.

c) If the Contractor subsequently identifies any such data not previously delivered to DC3, then the Contractor shall immediately notify the contracting officer in writing and shall deliver the incident data within ten (10) days of identification. In such a case, the Contractor may request a delivery date later than ten (10) days after identification. The contracting officer will approve or disapprove the request after coordination with DC3.

3.4. Naval Criminal Investigative Service (NCIS) Outreach

The Contractor shall engage with NCIS industry outreach efforts and consider recommendations for hardening of covered contractor information systems affecting DON programs and technologies.

3.5. NCIS/Industry Monitoring

a) In the event of a cyber-incident or at any time the Government has indication of a vulnerability or potential vulnerability, the Contractor shall cooperate with the Naval Criminal Investigative Service (NCIS), which may include cooperation related to: threat indicators; pre-determined incident information derived from the Contractor's infrastructure systems; and the continuous provision of all Contractor, subcontractor or vendor logs that show network activity, including any additional logs the contractor, subcontractor or vendor agrees to initiate as a result of the cyber incident or notice of actual or potential vulnerability.

b) If the Government determines that the collection of all logs does not adequately protect its interests, the Contractor and NCIS will work together to implement additional measures, which may include allowing the installation of an appropriate network device that is owned and maintained by NCIS, on the Contractor's information systems or information technology assets. The specific details (e.g., type of device, type of data gathered, monitoring period) regarding the installation of an NCIS network device shall be the subject of a separate agreement negotiated between NCIS and the Contractor. In the alternative, the Contractor may install network sensor capabilities or a network monitoring service, either of which must be reviewed for acceptability by NCIS. Use of this alternative approach shall also be the subject of a separate agreement negotiated between NCIS and the Contractor.

c) In all cases, the collection or provision of data and any activities associated with this statement of work shall be in accordance with federal, state, and non-US law.

4.0 7108: DFARS 227.7108 - Contractor managed repositories

48 CFR § 227.7108 - Contractor data repositories and database.

(a) This applies to all CLINS having a Contractor managed or owned database and/or repository. Contractor databases and repositories may be established when permitted by agency procedures. The contractual instrument establishing the database and repository must require, as a minimum, the database and repository management contractor to—

(1) Establish and maintain adequate procedures for protecting technical data delivered to or stored at the database and repository from unauthorized release or disclosure;

(2) Establish and maintain adequate procedures for controlling the release or disclosure of technical data from the database and repository to third parties consistent with the Government's rights in such data;

(3) When required by the contracting officer, deliver data to the Government on paper or in other specified media;

(4) Be responsible for maintaining the currency of data delivered directly by Government contractors or subcontractors to the database/repository;

(5) Obtain use and non-disclosure agreements from all persons to whom government purpose rights data is released or disclosed; and

(6) Indemnify the Government from any liability to data owners or licensors resulting from, or as a consequence of, a release or disclosure of technical data made by the database and repository contractor or its officers, employees, agents, or representatives.

(b) If the contractor is or will be the database and repository manager, the contractor's data management and distribution responsibilities must be identified in the contract or the contract must reference the agreement between the Government and the contractor that establishes those responsibilities.

(c) If the contractor is not and will not be the database and repository manager, do not require a contractor or subcontractor to deliver technical data marked with limited rights legends to a database and repository managed by another contractor unless the contractor or subcontractor who has asserted limited rights agrees to release the data to the database and repository or has authorized, in writing, the Government to do so.

(d) Repository/database procedures may provide for the acceptance, delivery, and subsequent distribution of technical data in storage media other than paper, including direct electronic exchange of data between two computers. The procedures must provide for the identification of any portions of the data provided with restrictive legends, when appropriate. The acceptance criteria must be consistent with the authorized delivery format.

(e) The Government will desire at least government purpose right unless unlimited rights are already obtained to all data stored in the repositories and databases and the Contractor agrees to deliver such data to covered government support contractors and will secure non-disclosure agreements to such data when required for release.

(f) The U.S. Government will have unlimited access to the databases and any support government contractors working on behalf of the U.S. Government in support of government contract or audit. The U.S. Government will have unlimited rights to all documents developed under this contract. The Government may at any time have the database/repository and its contents delivered to the Government at request from the Government within a reasonable time

(e) and (f) are negotiable

CLIN 1001 Trident D5 Life Extension 2 (LE2) Systems Engineering (CPFF/LOE) (WPN)

During the period of 01 October 2025 through 30 September 2026, the Contractor shall make available and employ its facilities, personnel at the level of effort (LOE) set forth in Section F, services of others, and materials, and shall use its best efforts to perform the following:

1.1 D5LE2 System Engineering Management

· Perform Systems Engineering Management activities to include:

· Develop, deliver, and execute System Engineering Management Plans (SEMP) to include, but not limited to, a Plan of Action and Milestone (POA&M) schedule, with time-phased execution and resource allocations to execute program support requirements (CDRL A00X) to support the identified D5LE2 program efforts

· Develop and maintain schedules for the overall system engineering activities, Requirements IPT, System Design and Assessment (SDA) IPT, Integration Working Group, and Verification Working Group deliverables and activities through the Initial Operating Capability milestone

· Conduct Technical Data Management and Configuration Management activities for D5LE2 Systems Engineering data and artifacts

· Maintain Configuration and Data Management tools, storage, and account access in support of D5LE2 Systems Engineering

· Conduct Risk, Issue, and Opportunity identification, development, management, and resolution for the D5LE2 Systems Engineering Group

· Provide support to the D5LE2 Systems Engineering Management Team

· Develop technical content for D5LE2 program level systems engineering documents, to include but not limited to the Systems Engineering Plan

· Update the SSP Systems Engineering Process Ordnance Document (CDRL A00X)

· Conduct Program Management Reviews

· Provide engineering services in support of the system-level integration of the subsystem KPs, SRSAs and SETR events and artifacts/outputs

· Provide expert knowledge of the TOG to facilitate subsystem traceability and verification planning. Participate in subsystem traceability and verification activities

· Provide expert knowledge of the architecture and interfaces to facilitate subsystem traceability and integration planning. Participate in subsystem traceability and verification activities

· Assess and deliver a report on subsystem artifacts in support of system level activities (CDRL A00X)

1.2 D5LE2 Systems Requirements and Architecture Maintenance

· Perform ongoing Strategic Weapon System (SWS) Requirements Management including:

· Co-Lead, with the Government, the Requirements IPT

· Requirements management and maintenance functions for the D5LE2 Technical Objectives & Guidelines (TOG)

· Maintain requirements management plans and processes

· Maintain and manage the Requirements Verification and Traceability Matrix (RVTM) (CDRL A00X)

· Update and deliver the TOG and RVTM with results from system and subsystem SETR events based on information and artifacts available at the time (CDRL A00X and CDRL A00X)

· Perform and deliver an assessment of feasibility and resources required to combine the LE and LE2 requirement documentation and to transition the TOG to the DOORS Next tool

· Perform ongoing SWS Architecture and Interface development and management including:

· Co-Lead, with the Government, the System Design and Assessment IPT

· Deliver updated draft Architecture Definitions for Knowledge Point 2 based on information available at the time (develop plans, management, traceability, records, trade studies (CDRL A00X))

· Maintain and deliver Descriptive System Modeling (DSM) plans (CDRL A00X)

· Manage and maintain the interfaces and architectures

· Maintain and execute the Strategic Systems Programs (SSP) Coordination Process

· Maintain and deliver Interface Development Management Plan (IFDMP) (CDRL A00X)

· Coordinate with all SSP technical branch stakeholders to create and mature plans for the orderly transition between the current and future-state SWS technical information

1.3 D5LE2 System Integration, Verification and Validation (IV&V) Management

· Provide IV&V engineering services for D5LE2 as follows:

· Co-Lead, with the Government, the Integration Working Group and the Verification and Validation (V&V) Management working Groups

· Lead the overall D5LE2 system integration effort, coordinating with other stakeholders as required

· Lead the overall D5LE2 system verification effort, coordinating with other stakeholders as required

· Lead the overall D5LE2 system validation effort, coordinating with other stakeholders as required

· Update, deliver, and maintain the D5LE2 SWS Integration Plan (CDRL A011) based on information and artifacts available at the time to integrate:

· SWS subsystems with other SWS subsystems,

· SWS subsystems into the SWS system, and

· SWS with the COLUMBIA and OHIO class submarines

· Develop and deliver…