FY26 Draft SSN SOW.docx

20 Feb 2025

Section C- Descriptions and Specifications Statement of Work

1.0 Strategic Weapon System (SWS) Launcher Support (D5LE, D5LE2, and Columbia Dreadnought (CDLP)) and Nuclear Weapons Security (NWS)Scope

This Statement of Work (SOW) sets forth the requirements for professional, technical, and management efforts for the continuing system engineering, programmatic, security, and operational support to Strategic Weapons Facility, Atlantic (SWFLANT) in Kings Bay, Georgia, and Pacific (SWFPAC) in Silverdale, Washington, the Program Management Office (PMO) located in Pittsfield, Massachusetts, Sunnyvale, CA, Denver, Colorado, Magna, Utah, Cape Canaveral, Florida, Launcher support efforts with Naval Surface Warfare Center (NSWC), Crane, Indiana, and Strategic Systems Programs Headquarters (SPHQ) in Washington Navy Yard, D.C. These services are in support of operations managed by Strategic Systems Programs (SSP), a Direct Reporting Program Manager (DRPM) in the Department of the Navy (DON).

2.0 General Requirements – Applicable to All Contract Line Item Numbers (CLIN)

2.1 Implementation of the Defense Industrial Base (DIB) Memo

The following SOW language supplements Defense Federal Acquisition Regulation Supplement (DFARS) Clause 252.204-7012 (MAY 2024) (DEVIATION 2024-O0013, REVISION 1) cited in Section I in accordance with the requirements of Navy Marine Corps Acquisition Regulation Supplement (NMCARS) SUBPART 5204.73-SAFEGUARDING COVERED DEFENSE INFORMATION AND CYBER INCIDENT REPORTING:

2.1.1 System Security Plan and Plans of Action and Milestones Reviews (Contract Data Requirements List (CDRL) A001)

a. Within thirty (30) days of contract award, the Contractor shall make its System Security Plan(s) for its covered contractor information system(s) available for review by the Government at the contractor’s facility. The System Security Plan(s) shall implement the security requirements in DFARS clause 252.204-7012 (MAY 2024) (DEVIATION 2024-O0013, REVISION 1), which is included in this contract. The Contractor shall fully cooperate in the Government’s review of the System Security Plan(s) at the Contractor’s facility.

b. If the Government determines that the System Security Plan(s) does not adequately implement the requirements of DFARS clause 252.204-7012 (MAY 2024) (DEVIATION 2024-O0013, REVISION 1) 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 (POAM) 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 System Security Plan(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 System Security Plan(s).

d. The Government may, in its sole discretion, conduct subsequent reviews at the Contractor’s site to verify the information in the System Security Plan(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.

2.1.2 Compliance to National Institute of Standards and Technology (NIST) 800-171

a. The Contractor shall fully implement the Controlled Unclassified Information (CUI) Security Requirements (Requirements) and associated Relevant Security Controls (Controls) in NIST Special Publication (SP) 800-171 (Rev. 2) (NIST SP 800-171), or establish System Security Plan(s) and POAMs that varies from NIST 800-171 only in accordance with DFARS clause 252.204-7012 (DEVIATION 2024-O0013, REVISION 1), paragraph (b)(2), for all covered contractor information systems affecting this contract.

b. Notwithstanding the allowance for such variation, the contractor shall identify in any System Security Plan and POAM 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 Computer Numerical Control (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 (Federal Information Processing Standards (FIPS) 140-2 validated cryptology or implementation of National Security Agency or NIST approved algorithms (i.e. FIPS 140-2 Annex A: Advanced Encryption Standard (AES) or Triple Data Encryption Standard (DES) or compensating controls as documented in a System Security Plan 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.

2.1.3 Cyber Incident Response (CDRL A002)

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_Media.docx. 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.

2.1.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.

2.1.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 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 (IT) 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 SOW shall be in accordance with federal, state, and non-US law.

2.2 Program Management

a. The Contractor shall be responsible for performance of the requirements delineated in this SOW and shall institute appropriate management actions relative to subcontractor and consultant performance. The Contractor shall be accountable and responsible for all subcontractor and consultant for compliance and shall be responsible for ensuring all deliverable products and services, including data deliverables, comply with the contract requirements.

b. The Contractor shall provide a full range of program management support to SSP to include organizing, tracking, summarizing, validating, verifying, interpreting, archiving and making recommendations on the status, documentation, analysis and coordination of all aspects of SSP’s programs and services.

c. The Contractor shall provide support in the development and maintenance of program schedules, program plans, and other program documentation necessary to plan, monitor, and control each project.

d. The Contractor shall provide support and actively participate on SPHQ program planning and coordination meetings to include, but not limited to:

(1) Program Management/Key Initiative Reviews;

(2) Periodic leadership reviews;

(3) SP22/SP32 or other SSP designated Integrated Project Teams (IPT) and Working Group meetings; and

(4) SSP Monday Morning and Field Activity Meetings.

2.3 Status Reporting

The overall contract financial, technical and schedule status (to include all research and development (R&D) tasks, refresh and development projects, procurement and installation (P&I) projects, and the deployed systems support efforts) shall be presented to the Government through various periodic reviews and reports. The following data deliverables are required for all CLINs:

a. Monthly/Quarterly Contractor Financial Management Reports (CFMR M/Q) (CDRL A003); and

b. Contract Work Breakdown Structure (CWBS) (CDRL A004);

c. Post Completion Report of Man Hours and Expenditures, Level of Effort (LOE) CLINs only (CDRL A005);

d. Technical Report . The Contractor shall report progress, highlights, and problem areas along with resolution plans. These reports are concise engineering documents that outline an issue, approach, resolution, and recommended action. These reports may include technical analysis and briefs to provide system engineering positions, analytical results and information on a wide variety of issues. The contractor will provide various documentation in support of the program such as letters, memorandums, and white papers (CDRL A006).

2.4 Personnel Certifications

a. All personnel performing maintenance and repair on Lenel security systems and servers are required, at a minimum, to be a Lenel Certified Associate (LCA).

b. All personnel performing maintenance and repair on GSA security containers must be a GSA certified locksmith.

2.4.1 Nuclear Weapons Surety Program Protection

NWS Program Protection is part of the Trident II Strategic Weapon System (SWS) Program Protection Plan (PPP), which is used to identify, manage, and mitigate risks to Critical Program Information (CPI) and to Information and Communications Technology (ICT). Program protection ensures that system security engineering is integrated in the systems engineering process for managing risks from foreign and domestic threats from hardware, software, and cyber vulnerabilities; or supply chain exploitation throughout the system life cycle.

2.4.2 Program Protection

a. The Contractor shall develop and update mission criticality analysis(-es), vulnerability assessments, risk assessments, and identification and counter measurement implementation(s) for Mission Critical functions, the failure of which would result in either a total compromise of mission capability (catastrophic) or significant mission degradation (critical.) In accordance with (IAW) Department of Defense Instruction (DoDI) 5200.44, Protection of Mission Critical Functions to Achieve Trusted Systems & Networks.

b. The Contractor shall have, and demonstrate, mechanisms in place to effectively monitor the supply chain for critical components, understand how supply chain risks can be introduced through those components, and implement or provide plans to implement countermeasures to mitigate such risk.

c. The Contractor shall ensure that updated assumptions, rationale, and results related to the criticality analysis, vulnerability assessments, risk assessments, supply chain risk information, and risk mitigations are made available for Government review at identified System Engineering milestones.

d. The Contractor shall comply with the SSP Instructions (SSPINST) 5239.7B (SSP Cybersecurity Implementation for Technical Divisions), SSPINST 3070.1A (Operations Security Program) to ensure safeguarding of SSP’s Critical Information (CI), and DoDI 5200.39 Ch-3, CPI Identification and Protection Within Research, Development, Test, and Evaluation (RDT&E). The Contractor shall describe and deliver their safeguarding of SSP’s CI in their Program Plan (CDRL A007).

e. The Contractor shall ensure that their Systems Security Engineering Program protection processes to include Hardware and Software Assurance processes are documented and implemented. These processes shall be made available for Government review.

2.4.3 Cybersecurity

a. Contractor shall adhere to DoDI 8500.01 Cybersecurity and DoDI 8510.01 Risk Management Framework for DoD IT. The Contractor shall implement NIST SP 800-171, protecting CUI.

b. The Contractor shall ensure that cybersecurity test and evaluation (T&E) activates (e.g., cyber test objectives, methodology, procedures, schedules, and resources) supporting engineering developmental & operational testing (DT/OT), risk management, and acquisition decisions are programed in the systems test plan and that incremental testing of selected cyber controls are evaluated in conjunction with developmental engineering tests.

2.4.4 Cybersecurity Workforce

Contractor employees assigned cybersecurity duties or having privileged access to IT systems must: (1) be registered with the Command cybersecurityManager; (2) achieve the appropriate cybersecurity workforce baseline certification IAW DoDD 8140.01 Ch-1 (Cyberspace Workforce Management) for his/her level within six months of cybersecurity assignment; (3) maintain cybersecurity workforce certification throughout their tenure; (4) be classified as an IT Level 1 position per SECNAV M-5239.2 (DON Cyberspace Information Technology and cybersecurity Workforce Management and Qualification Manual, and DoDM 5200.02 Ch-1 (Procedures for the DoD Personnel Security Program (PSP)); and (5) meet the qualifications and skillsets commensurate with the systems they are maintaining.

2.4.5 Government Data Rights (GPR)

a. Data (technical data and computer software) shall be protected in accordance with the appropriate PPPs and Cybersecurity guidelines.

b. The Government intends for all computer software and technical data developed under this contract be delivered with at least GPR, as defined in DFARS clauses 252.227.7013, -7014, -7015 and -7017, and appropriately marked as such unless a waiver has been submitted and approved by the Government. In this context, technical data and computer software developed under this contract do not include embedded open source software or COTS software products. This shall include documentation developed by the Contractor or received in support of working groups and IPTs.

c. 10 United States Code (USC) 2446a.(b), Sec 805: Modular Open Systems Approach (MOSA) - Interfacing development: The Contractor and its subcontractors will follow DoDI 5000.02 (dated 23 Jan 2020, Ch-1 8 Jun 2022) and 5010.44 (dated October 16, 2019) as to MOSA to the Major System Interfaces and ensure that the Government will acquire at least 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. When any existing subsystem/elements incorporates other company proprietary information or Intellectual Property, it is up to the contractor and its subcontractors to obtain non-disclosure agreements (NDAs) from each of those companies.

2.4.6 48 Code of Federal Regulations (CFR) § 227.7108 - Contractor data repositories and database.

a. This applies to all CLINS having a Contractor database and 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 unlimited rights 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 NDAs 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.

3.0 CLIN 0001 – Launcher Systems Engineering (O&MN) (CPFF-LOE)

From the effective date of the contract award through 20 December 2026, the Contractor shall make available and employ its facilities, personnel at the LOE set forth in Section F, services of others, and materials, and shall use its best efforts to perform the following on-site services for Trident II D5 Submarine Launched Ballistic Missile (SLBM) SWS equipment, components, technical documentation, plans and programs.

3.1 SWS Integration Support

The Contractor shall support Launcher Branch (SP22), SSPs field activities, Naval Surface Warfare Center (NSWC) Crane and other Contractors to ensure system integration of all elements of the SWS subsystems are being considered in performing technical, operational, and programmatic tradeoffs. The Contractor’s efforts shall include systems analyses, independent studies, technology and engineering evaluations, document development, trade analysis and participation in working groups and integrated product teams.

3.2 Information Assurance (IA)

The Contractor shall provide engineering services in support of SP22 IA implementation. The Contractor shall provide technical reviews on IA packages in accordance with the certification and accreditation (C&A) processes for Trident II SWS and associated testing equipment, trainers and support systems. The Contractor shall provide technical assistance on interpreting SSP’s IA policies, requirements and C&A processes to Technical Division’s personnel. The Contractor shall participate in System Requirements Reviews (SRRs), Preliminary Design Reviews (PDRs), Critical Design Reviews (CDRs), Development and Deployment Teams (DDTs), Concept Development Teams (CDTs), focus teams and working groups. The Contractor shall assist in the generating of IA related presentations, letters, memorandums, white papers.

3.3 Technical Branch/PMO Support

The Contractor shall provide support to SSP in Management, Receipt, Review and Storage of materials and information products to be approved by the PMO. The Contractor will provide support in the generation of strategies and planning to maintain and coordinate controls and processing between SP22, Program Management Office SSP (PMOSSP) Flight Systems Detachment Sunnyvale (SPF(S)) PMO and entities that provide products to SSP for review, processing and approval. The Contractor shall support the on-going initiatives by the SP22 and SPF(S) PMO to update, integrate and/or consolidate approved products and management infrastructure. The Contractor shall receive, review, record, disseminate, track and report products within SP22 and SPF(S) PMO and maintain configuration control of the latest approved products and those products in the review process. The Contractor shall provide recommendations for streamlining, optimizing, or improving upon current policies, processes, and standards for data, documentation, and information management infrastructure.

3.4 Financial Improvement and Audit Readiness (FIAR)

The contractor shall provide support for onsite inventory events. Assisting the site item managers with identification and disposition recommendations. The Contractor shall maintain branch documentation for the location and management of the items stored at each facility. While working with government and contractor material managers, the contractor will provide the branch with recommendations for stored items and obtain the required permissions for the disposition of materials.

3.5 Fleet Planning and SPALT Implementation

The contractor will provide support as the SP22 liaison to the Fleet Planning Meetings. As the liaison the contractor will provide SPALT requirements and accomplishment timelines to the Fleet Planners and report back to the branch program managers the time frame allotted for installation on the units.

3.6 Fleet Liaison Officer (FLO) Support

The Contractor will provide the FLO with detailed, experienced based analysis of launcher subsystem issues to assist in technical resolution. The contractor shall provide assistance in developing/writing outgoing message traffic to ensure ship-side understanding of branch direction.

3.7 Documentation Assistance

The contractor shall review and assess documentation changes for validity and effects on current guidance. The contractor will perform grammatical reviews of SP22 documents for external use and assess for the technical correctness. For documentation tabletop review or proofing events, the contractor shall attend and participate in the reviews and provide feedback.

3.8 Facility Technical Proficiency Evaluations

The Contractor shall provide support during facility evaluations. Contractor will assist the SP22 Evaluation Lead to evaluate facility/contractor compliance with Contract requirements as well as other program directives.

3.9 Training

The Contractor shall provide assistance to prepare/update training material, secure training location and facilitate training. The contractor shall assist the Launcher Training Program Manager with maintaining training materials to ensure they are updated, fully disseminated and incorporated into training program requirements.

3.10 Support Emergent Efforts

The Contractor shall assist on emergent issues that affect the deployed launcher systems, fleet readiness, maintenance, storage and repair of support systems.

3.11 Integrated Project Team (IPT) Support

The Contractor shall participate in projects and programs associated with SP22 as a member of the IPT as technical assistance to the SP22 Program Manager.

3.12 Strategic Programs Alteration (SPALT) and Refresh Support

The contractor will provide programmatic assistance and track requirements for the equipment to undergo alterations, improvements or refreshes. The contractor will assess programmatic documentation generated by system update, increments, SPALTs, configuration changes and upgrades throughout the review and approval process. The contractor will ensure the products are received, logged, distributed, reviewed and returned to the cognizant entity with comments for adjudication or having been approved. The contractor will ensure gating requirements are met by ensuring that they are received, reviewed and approved for milestone reviews with approved versions stored on the SSP repository for government control and management.

3.13 Travel

The Contractor shall travel in performance of this contract. Travel shall be for the purpose of supporting tasks listed in this Item. All travel shall be in accordance with the Government’s Joint Travel Regulations (JTR) or Joint Federal Travel Regulation (JFTR). Fee shall not be applied to travel.

4.0 CLIN 0003 – Columbia Dreadnought Launcher Development (CDLP) Systems Engineering (SCN) (CPFF- LOE)

Tasks from the effective date of the contract award through 20 December 2026, the Contractor shall make available and employ its facilities, personnel at the LOE set forth in Section F, services of others, and materials, and shall use its best efforts to perform the following on-site services for CDLP Common Missile Compartment (CMC) equipment, components, technical documentation, plans and programs.

4.1 Schedule Support

The contractor will provide schedule oversite and impacts to the program as project schedules are adjusted or affected. The Contractor shall review schedules provided to the section by industry partners for accuracy and consistency. The contractor is responsible for the evaluation of project schedule changes to the branch program plan.

4.2 Branch Risk Management

The contractor will maintain a Branch Risk Database by collecting new risks from across all programs and frequently updating active ones. The Contractor shall provide risk reports, analysis, and metrics to the branch while maintaining a working knowledge of all branch risks.

4.3 Long-term Contract Planning

The contractor will maintain a long-range contract plan for major CLDP milestones and will coordinate with program managers across the section to ensure contracts are being worked on in a timely manner.

4.4 Branch Deliverable Management

The contractor will maintain the deliverables in the SWS Network (SWSNET) repository. The contractor will upload all files provided by the group leader and maintain an orderly, easily accessible folder structure. The contractor will manage the dissemination, review, approval and completion of the deliverables. The contractor shall provide an instruction for the management of deliverable products at the branch level.

4.5 Technical Support

Assist in providing responses to Technical Program Management Evaluation (TPME) findings. Provide recommendations, courses of action, and milestone development. Track findings to completion and close the findings.

4.6 System Engineering and Integration Team (SEIT) Support

The Contractor shall provide support to the Program Manager in areas of coordination and correlation to ensure that the requirements of the launcher system are met. The contractor shall participate in meetings to provide system knowledge and user interface integration to the launcher system.

4.7 Information Assurance

The Contractor shall provide engineering services in support of SP22 IA implementation. The Contractor shall provide technical reviews on IA packages in accordance with the C&A processes for Trident II SWS and associated testing equipment, trainers and support systems. The Contractor shall provide technical assistance on interpreting SSP’s IA policies, requirements and C&A processes to Technical Division’s personnel. Participate in SRRs, PDRs, CDRs, DDTs, CDTs, focus teams, and working groups. The Contractor shall assist in the generating of IA related presentations, letters, memorandums, white papers.

4.8 Documentation Tracking and Configuration Control

The contractor shall manage and track programmatic documentation generated by system update, increments, SPALTs, configuration changes, and upgrades throughout the review and approval process. The contractor shall ensure the documents are received, logged, distributed, reviewed and returned to the cognizant entity with comments for adjudication or having been approved. The contractor shall ensure gating documentation is received, reviewed and approved for milestone reviews with approved versions stored on the SSP repository for government control and management. The contractor will provide review and assessment of documentation changes for validity and effects on current guidance. The contractor will perform grammatical reviews of branch documentation for external use and assess for the technical correctness. The contractor will assist with documentation tabletop reviews or proofing events, the contractor shall attend and participate in the reviews and provide feedback.

4.9 Travel

The Contractor shall travel in performance of this contract. Travel shall be for the purpose of supporting tasks listed in this Item. All travel shall be in accordance with the Government’s JTR or JFTR. Fee shall not be applied to travel.

5.0 CLIN 0005 – Support Equipment Overhaul Support (OPN) (CPFF-LOE)

Tasks from the effective date of the contract award through 20 December 2026, the Contractor shall make available and employ its facilities, personnel at the LOE set forth in Section F, services of others, and materials, and shall use its best efforts to perform the following on-site services for Trident II D5 Submarine Launched Ballistic Missile (SLBM) SWS equipment, components, technical documentation, plans and programs.

5.1 Support Equipment Overhaul Support

The Contractor shall assist the SP22 in the implementation and execution of Support Equipment Overhauls and technical requirements to support the preparation of equipment and system designs. The Contractor shall support in-service engineering of equipment and system. The Contractor shall support integration and planning efforts to include working with SSP field activities, NWSC Crane and other Contractors in programmatic documentation efforts, technology and engineering evaluations, provide planning support for and participation in working groups and ensure implementation of action items.

5.2 Systems Integration Support

The Contractor shall support the on-going initiatives by the SSP to update, integrate and consolidate documentation and information infrastructure. The Contractor shall recommend strategies to integrate these disparate initiatives and systems.

5.3 Field Operations Support

The Contractor shall provide support to the Field Operations Manager in the area of field activity site visit coordination, issue resolution, engineering exhibitions and SPALT accomplishment for support equipment.

5.4 Site Activation Support

The Contractor shall participate in meetings concerning operations, coordination, correlation, site proofing and final inspection processes to ensure the capabilities meet the needs of the SP22 and systems. They will be assigned to the IPT and reviews to assist the Program Manager through Activation.

5.5 Travel

The Contractor shall travel in performance of this contract. Travel shall be for the purpose of supporting tasks listed in this Item. All travel shall be in accordance with the Government’s JTR or JFTR. Fee shall not be applied to travel.

6.0 CLIN 0006 –PMO SPF/SPF(B)/SPF(C) Support – Denver, CO, Cape Canaveral, FL, and Magna, UT (O&MN) (CPFF-LOE)

Tasks from the effective date of the contract award through 20 December 2026, the Contractor shall make available and employ its facilities, personnel at the LOE set forth in Section F, services of others, and materials, and shall use its best efforts to perform the following services to the SSP Director (DIRSSP) through support to SPF Denver, CO (PMOSPF), SPF Detachment Magna, Utah (SPF(B)), and SPF Detachment Cape Canaveral, Florida (SPF(C)).

6.1 Technical Support

The contractor shall conduct reports, surveys, assessments and technical analyses. To accomplish this, the contractor shall:

6.1.1 Review PMOSPF briefings, program objectives and plans, and other similar documents to correspondence, and provide database management. Ensure consistency with the DIRSSP’s policy statements and directives, and the overall SSP program direction and priorities.

6.2 Program Management Support

The contractor shall facilitate and integrate PMOSPF core organizational processes. To accomplish this support, the contractor shall:

6.2.1 Support the preparation of mission policies, administrative standards and executive processes to facilitate staff actions and to coordinate decisions.

6.2.2 Effectively integrate with the PMOSPF team to reduce tasking/action cycle times.

6.2.3 Provide rapid response and support to official correspondence/taskers.

6.2.4 Support preparation of general PMOSPF office procedures and processes necessary to interface with customers both internal and external to the PMO.

6.2.5 Provide managerial support as necessary to assist the Government in conceptualizing, preparing and coordinating the PMOSPF mission.

6.3. Fleet Documentation

Provide Technical Editing assistance to PMOSPF for the SWS/Integrated Nuclear Weapons Security System (INWSS) program, The Technical Editing assistance will provide documentation support for projects as requested, including writing, editing, and coordinating reviews of technical and procedural documents. Participates in the preparation of standards and processes, including documenting and archiving.

6.3.1 Prepare and maintain templates and template indexes to ensure they are current and aligned.

6.3.2 Perform tasks within systems specific to SSP to set up and maintain customer and internal documentation.

6.3.3 Support and contribute to internal communication tools.

6.4. Analyst Support

Provide Analyst assistance to PMOSPF for the SWS/INWSS program. This will assist with efforts applicable to the SWS/INWSS to facilitate program integration and maximize efficiencies in the program and shall provide the following services:

6.4.1 Conduct meeting support for PMOSPF working groups, weekly PMO staff meetings, industry partner forums, program reviews, and management reviews.

6.4.2 Execute meetings logistics, build meeting agendas and coordinate brief contents with presenters.

6.4.3 Document/promulgate meeting minutes.

6.4.4 Provide liaison support PMO Detachments (PMODET) and the PMO Headquarters Office.

6.4.5 Assist with other administrative support efforts as required by the technical director/manager.

6.5 Security Assistance Tasks

The Contractor shall assist the PMO, with guidance from the Command Security Manager in Denver, CO in the areas of security program management (personnel, physical, information, and industrial) program execution, and administrative functions within the SPF10 Operations and Administration Division.

6.5.1 The contractor shall ensure classified documents are properly received, marked, and stored in accordance with DON and DOD regulations.

6.5.2 The contractor shall prepare and package classified material for shipping and mailing.

6.5.3 The contractor shall create out-going request within the Defense Information Security System (DISS).

6.5.4 The contractor shall process in-coming visit requests and confirm clearance and access level for visitors to SPF within DISS.

6.5.5 The contractor shall process badge request for new employees, visitors, and employees within the SPF spaces.

6.5.6 The contractor shall brief newly appointed or transferred personnel and to those who require foreign travel briefing.

6.5.7 The contractor shall conduct inventories and destruction.

6.5.8 The contractor shall attend field activity inspection meetings.

6.5.9 The contractor shall ensure effective security program requirements (personnel, physical, and industrial) are established and maintained.

6.5.10 The contractor shall support the security of SPF and all three subordinate detachments.

6.5.11 The contractor shall assist the security assistants at the detachments with the execution of physical, industrial, information, and personnel security.

6.5.12 The contractor shall support execution of meeting logistics, scheduling, building agenda’s, coordinating brief contents, taking notes, running slides, and etc.

6.5.13 The contractor shall provide liaison support between SPF, SPHQ, and SPF detachment’s.

6.5.14 The contractor shall provide support in the issuance of the courier authorization card, airline transportation letters for SPF employees.

6.5.15 The contractor shall develop, coordinate, maintain and update security standard operating procedures (SOP) for security duties including securing government approval of all SOPs.

6.5.16 The contractor shall develop and provide training briefs to personnel (civilian, military, and contractors).

6.5.17 The contractor shall generate/approve System Authorization Access Request – Navy (SAAR-N) packages for personnel and ensure all supporting documents are received and maintain finalized SAAR-N records.

6.5.18 The contractor shall support annual security reviews. (Personnel, physical, and information).

6.5.19 The contractor shall respond to prospective candidate’s questions in references to personnel security forms and request missing information from candidates.

6.5.20 The contractor shall maintain personnel security records and ensure records are current and in accordance with applicable personnel security requirements.

6.5.21 The contractor shall assist with other administrative support efforts as required by the security manager to include, but not limited to investigations, instructions/notices, reports, etc.

6.6. Travel

The Contractor shall be required to travel for purposes of performing tasks required under CLIN 0006. All travel shall be in accordance with the Government’s JTR or JFTR. Reimbursable travel costs include travel performed from the Contractor or Government facility to the worksite, in and around the worksite, and from the worksite to the Contractor or Government facility. Charges for Personal Owned Vehicle (POV) mileage in furtherance of these tasks shall be reimbursable. Contractor certifies that it possesses the required insurance in accordance with FAR 28.307-2 requirements.

7.0 CLIN 0007 - Trident II D5 SLBM Weapon System Flight Test Operations Support, Spectrum Allocation and Frequency Assignment Support, and Travel (WPN) (CPFF-LOE) (OPTION)

During the period beginning on the date on which the option for Item 0007 is exercised through 20 December 2026, the Contractor shall make available and employ its facilities, personnel at the LOE set forth in Section F, services of others, and materials, and shall use its best efforts to perform the following services.

Perform programmatic, development, T&E, and operations support for the Trident II D5 Submarine Launched Ballistic Missile (SLBM) Weapon System flight test operations. Support SSP in operating and maintaining the spectrum allocation and frequency assignment database, using SSP’s Spectrum XXI System, for all the radio frequency transmitters under the control of SSP.

In performance of these efforts, the contractor shall provide:

7.1 Program Support

The contractor shall provide programmatic test instrumentation support, assist SSP in the development of planning documents, implementation plans, procurement strategies, and participate in various program reviews, working groups and flight test planning meetings, conduct schedule reviews and identify critical elements, and assist SSP in the development and conduct of Range subsystem tests in support of systems engineering processes and the Special Engineering Test Process (as it relates to the Trident II D5 flight test requirements). The contractor shall support the SSP Systems Engineering and Risk Management process as it relates to Flight Test Instrumentation. The contractor shall liaise within SSP and with Test and Evaluation Commands to pursue endorsements for Small Business Innovation Research (SBIR), Science and Technology Needs, and Central Test and Evaluation Investment Program (CTEIP) opportunities in the best interest of SSP. The contractor shall assist with modeling and simulation as directed, including assessing existing tools, strategy and modeling plans, and verification, validation, and accreditation plans.

7.2 Flight Test Instrumentation (FTI) Planning & Support

The contractor shall support down range planning and support, Launch Area Support Ship (LASS), and Navy Mobile Instrumentation System (NMIS) operations planning and support, equipment development and testing, range scheduling, and support SSP as the secretary of the Flight Test Working Group (FTWG). The contractor shall support SP2734 in its role as the primary SSP representative to the Reliance Panel and various other T&E working groups supporting the Test Resource Advisory Group. The contractor shall provide liaison assistance with other DoD offices and activities as required. The contractor shall assist in supporting Range architecture discussions with Test Resources Management Center, Missile Defense Agency, Ground Based Strategic Deterrence, Commercial Space Industry, the National Aeronautical and Space Administration (NASA), the Air Force, and the United States Space Force. The contractor shall support as an intermediary between SSP partner stakeholders and SPHQ in processing and delivery of flight test data and analysis as required.

7.3 Spectrum Management

The contractor shall support SSP in establishing and maintaining a complete paper and electronic file of all submitted Equipment Location - Certification Information Database (EL-CID) requests for equipment spectrum certifications (formerly known as DD 1494s), approved Applications for Equipment Frequency Allocations (JF-12s), Host Nation Coordination requests to transmit with the territories of partner sovereign nations, and Notes to Holder for transmitters requiring spectrum allocation and frequency assignment. The contractor shall support SSP in submitting updates to JF-12s when the configuration of transmitting equipment occurs during a field change or SSP Alteration (SPALT) that changes the performance characteristics of the equipment/system.

7.4 Liaison Support

The contractor shall support SSP with frequency management issues and act as liaison with Navy and other DoD offices and activities, as required. The contractor will support SP2734 in its role of representing SSP spectrum interests to National, DoD, and Navy authorities, including to the Range Commanders Council Frequency Management Group, Navy and Marine Corps Spectrum Center, Navy and Marine Corps Spectrum Offices (worldwide), and area frequency coordinators, and will attend Spectrum Management conferences applicable to SSP and represent SSP interests.

7.5 Compliancy Support

The contractor will provide support with conducting periodic reviews of all JF-12s and frequency assignments approved for SSP in accordance with the National Telecommunications and Information Agency (NTIA) Manual.

7.6 Travel

Travel will be required in supporting Flight Test Operations and Spectrum Management. Travel will be required as a condition of the Contractor’s performance. A trip report shall be submitted 10 days following the completion of required travel. The Trip Report shall include as a minimum, the purpose of the trip, date of travel, tasks performed, and significant outcome of the trip, all travel cost shall comply with and be performed in accordance with the JTR or JFTR. Fee shall not be applied to travel.

8.0 CLIN 0008 - Trident II D5 Life Extension Studies (D5LE2) (WPN) (CPFF-LOE) (OPTION)

During the period beginning on the date on which the option for Item 0008 is exercised through 20 December 2026, the Contractor shall make available and employ its facilities, personnel at the LOE set forth in Section F, services of others, and materials, and shall use its best efforts to perform the following services.

Support programmatic, development, T&E, and operations support for the Trident II D5 missile and missile components and subsystems. Assess components with obsolescence and affordability risks necessary to sustain the viability of the Trident II D5 SWS, which will support planning for the second life extension efforts of the Trident II missile. The contractor shall support the development of planning documents, implementation plans, procurement strategies, and participate in various program reviews and working groups using systems engineering processes. The contractor shall provide input on trade studies, requirements definition, design, and identification of critical elements and risks with mitigation strategies to support system deployment in the fleet. The contractor shall provide support with recommendations to descriptive model practices for consistency with SSP’s digital engineering objectives.

8.1 Travel

Travel will be required as a condition of the Contractor’s performance. A trip report shall be submitted 10 days following the completion of required travel. The Trip Report shall include as a minimum, the purpose of the trip, date of travel, tasks performed, and significant outcome of the trip, all travel cost shall comply with and be performed in accordance with the JTR or JFTR. Fee shall not be applied to travel.

9.0 CLIN 0009 – SWS Subject Matter Expert (SME) Support (O&MN) (CPFF-LOE) (OPTION)

During the period beginning on the date on which the option for Item 0009 is exercised through 20 December 2026, the Contractor shall make available and employ its facilities, personnel at the LOE set forth in Section F, services of others, and materials, and shall use its best efforts to perform the following services.

Contractor shall provide program and project management planning and assessment in support of the SWS Program. The contractor shall support the Technical Director for the following efforts: document efforts (prepare briefings, point papers, issue papers, POAM’s), evaluate project status, coordinate staffing and propose recommendations and provide options assessments for tasks defined herein to ensure consistency with SSP policy and procedures during all program and project management planning and assessment activities.

9.1 Program Analyst Support

Assist SP20 with controlling workflow to ensure efficient effective program management, prioritize daily focus/manage actions to maximize execution of weekly/monthly deadlines. Prepare talking points for public speaking engagements/in-house weekly meetings. Manage the master calendar, draft executive correspondence, and provide database management.

9.2 Program Management Support

The contractor shall facilitate and integrate core organizational processes. To accomplish this support, the contractor shall:

9.2.1 Support the preparation of mission policies, administrative standards and executive processes to facilitate staff actions and to coordinate decisions.

9.2.2 Create, facilitate, and support draft acquisition plans and strategies for overall programs, and for specific elements of the program.

9.2.3 Effectively integrate with the SP20 branches to reduce tasking/action cycle times.

9.2.4 Provide rapid response and support to…