SOW_FINAL.docx

STATEMENT OF WORK (SOW)

NAVY Strategic Systems Programs (SSP) Nuclear Weapons Systems (NWS) Support Services

Part 1 General Information

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

1.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) ANNEX 16-STATEMENT OF WORK LANGUAGE IMPLEMENTING “THE DIB” MEMO :

1.1.1 System Security Plan and Plans of Action and Milestones Reviews (Contract Data Requirements List)

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.

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

1.1.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_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.

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

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

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

1.3 Status Reporting

The overall contract financial, technical and schedule status 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)

b. Contract Work Breakdown Structure (CWBS)

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

1.4 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 desires for all computer software and technical data developed under this contract be delivered with at least Government Purpose Rights (GPR), as defined in DFARS clauses 252.227-7989, 252.227-7990 and 252.227-7992, 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.

1.5 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 allow 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.

Statement of Work (SOW)

2.0 CLIN 0001 (O&MN) (Cost Plus Fixed Fee) (Level of Effort) NWS Acquisition, Systems Engineering, System Security Engineering, Operations and Deployed Systems, and Training Support

From the effective date of Contract Award through a period of 12 months thereafter, the Contractor shall make available and employ its facilities and personnel at the level of effort set forth in Section F, services of others, and materials and shall utilize its best efforts to perform management and acquisition services as defined herein, with expenditure data to be delivered in the System Security Plan and Plans of Action and Milestones Reviews, Technical Reports to be delivered (as required), and Post Completion Report of Man Hours and Expenditures.

Integrated Nuclear Weapons Security Systems (INWSS) includes all systems and operations utilized to provide Nuclear Weapons Security (NWS) at the Strategic Weapons Facilities (SWFs) and to Fleet assets through the Transit Protection Program (TPP).

2.1 NWS Acquisition Support

The Contractor shall provide acquisition strategy technical, programmatic, and budget development, execution, monitoring, and assessment support that captures Nuclear Weapons Security program requirements by translating them to budget and contract requirements while adhering to Navy’s Program Planning Budget Execution (PPBE) policies, Federal Acquisition Regulation (FAR), and SSP contracting policies

The Contractor shall support the Government technical teams with existing and future contracting actions and to provide an accurately submitted contracting package within SSP contracting standards. The contracting package includes but not limited to market research, including sources sought notices and market research reports; drafting, reviewing and routing of acquisition and procurement documentation (e.g., Statement of Work (SOW), Contract Data Requirements Lists (CDRLs), DoD Contract Security Classification Specification (DD Form 254) including SCI, Earned Value Management (EVM) documentation, Determinations and Findings (D&Fs) and Justification and Approvals (J&As)); drafting, reviewing and routing documentation for, and assisting with the coordination and conduct of, Procurement Planning Conferences (PPCs) and Procurement Request Approval Conferences (PRACs). The Contractor shall support the Government technical teams in conducting requirement analysis of submitted proposals; provide recommendations during Government Fact Finding; all in the effort of developing a Government Technical Evaluation to accurately match program needs with vendor work.

The Contractor shall provide analysis and recommendations for alternative technical and programmatic approaches, future technologies and specific acquisition activities related to problem identification and resolution relative to the INWSS development, production, installation and operational support strategies and efforts.

The Contractor shall conduct necessary travel to perform these support activities.

2.2 NWS Systems Engineering (SE) Support

The Contractor shall advise on the implementation of Systems Engineering policies and requirements into INWSS policy, process and documentation to remain compliant for safety purposes. The Contractor shall assist in the development, review, updating and implementation monitoring of INWS SE policies, processes and documentation (e.g., Weapons Specifications, Quality Control (T9001C), and NWS Ordnance Documents (ODs)).

The Contractor shall act as INWSS Integrated Project Team (IPT) leads when assigned and shall assist various INWSS IPTs and Working Groups (WGs).

The Contractor shall provide analysis and recommendations for alternative technical and programmatic approaches, future technologies and specific SE activities related to problem identification and resolution relative to the INWSS development, production, installation and operational support strategies and efforts.

The Contractor shall assist in Risk Management, Root Cause Analysis, Corrective Action, and Continuous Improvement activities to mitigate and identify NWS risks when required.

The Contractor shall conduct necessary travel to perform these support activities.

2.3 NWS Systems Security Engineering (SSE) Support

The Contractor shall provide INWSS SME with in-depth understanding of the INWSS policy, system and subsystem requirements, INWSS missions at the SWFs, and submarine transit protection in support of INWSS SSE, including Cybersecurity, strategy, policy, process and requirements, development, implementation, monitoring and assessment.

The Contractor shall leverage their expertise in the SSP Risk Management Framework (RMF) processes and INWSS non-enterprise systems to provide Cybersecurity support in coordinating, implementing and enforcing information system security policies, standards and methodologies, including acting as a SP207 Information Systems Security Officer (ISSO) as required. The Contractor shall assist the SP207 Information Systems Security Manager (ISSM) in monitoring other INWSS contractor’s SSE practices, including Cybersecurity, and provide recommendations to address assessed security risks and mitigation efforts. The Contractor shall assist the SP207 ISSM in assessing the INWSS Operational Support activities and provide recommendations to address identified evolving security threats. The Contractor shall assist the SP207 ISSM in reviewing and rewriting aging INWSS Cybersecurity documents, leveraging their SSP RMF SME and innate knowledge of INWSS non-enterprise systems to realign INWSS Cybersecurity documentation with evolving SSP SSE and Cybersecurity processes and documentation. The Cybersecurity support shall extend to interfacing with other entities (e.g., Coast Guard, Space and Naval Warfare Systems Center (SPAWAR), and other Government Agencies) to support the INWSS, including the Transit Protection Program. Any such activities shall be coordinated with the Contracting Officer’s Representative (COR) and SSP Chief Information Officer (SPCIO) as may be needed.

The Contractor shall provide analysis and recommendations for alternative technical and programmatic approaches, future technologies and specific SSE activities related to problem identification and resolution relative to the INWSS development, production, installation and operational support strategies and efforts.

The Contractor shall conduct necessary travel to perform these support activities.

2.4 NWS Operations and Deployed Systems Support

The Contractor shall provide INWSS SME with in-depth operational understanding of the INWSS policy, system and subsystem requirements, INWSS missions at the SWFs, and submarine transit protection to support INWSS operations and deployed system support. The Contractor shall provide analysis and recommendations for concepts of operations, organizational structures and alignment, alternative technical and programmatic approaches, future technologies and specific problem identification and resolution relative to the INWSS operational support strategies and prime contractor’s statements of work.

The Contractor shall provide analysis and recommendations for prime contractor’s INWSS acquisition and sustainment strategies; assist with evaluations of the INWSS prime contractor relative to contract requirements including performance parameters, Trouble and Failure reporting and assessment, Cybersecurity and operational metrics; evaluate the prime contractor performance regarding operational incentives scoring; and provide recommendations for modifications to policy, processes, and acquisition activities to address programmatic changes and emerging issues.

The Contractor shall provide SME for assessing operational support of deployed products within the Transit Protection Program (TPP), to include coordination with TPP prime contractors, SWFs, United States Coast Guard, local law enforcement, and other applicable agencies. The Contractor shall utilize its knowledge of the roles and responsibilities of, and memorandums of agreement between, TPP stakeholders to review and assess program efforts and provide the Government with recommendations on operational requirements of systems and personnel.

The Contractor shall act as WG Lead during Government absence and shall assist as assigned in the management of all activities. The Contractor shall assist in the development of all operational performance and technical evaluations.

The Contractor shall provide analysis and recommendations for technical and programmatic approaches, future technologies and deployed system activities related to problem identification and resolution.

The Contractor shall assist and support SSP evaluations and facilitate the closure of any findings or deficiencies noted.

The Contractor shall conduct necessary travel to perform these support activities.

2.5 NWS Training Support

The Contractor shall provide INWSS SME with in-depth operational understanding of the INWSS policy, system and subsystem requirements, INWSS missions at the SWFs, and submarine transit protection to support INWSS training across the enterprise, to include the SWFs and Marine Corps Security Battalions, closely coordinating with all INWSS stakeholders to develop and implement training strategies and plans, track execution, and develop feedback mechanisms to evaluate training effectiveness. The Contractor will facilitate training working groups and meetings, record meeting minutes, and provide after-action reports outlining follow-on actions. The Contractor will support developing training modules (including introductory and refresher training) for existing and new SSP staff and others as directed. The Contractor will support SP207 in the review, development, and writing of INWSS Training Requirements documents.

The Contractor shall conduct necessary travel to perform these support activities.

OPTION CLIN 0002

3.0 FY27 (OPN) (CPFF) (LOE) NWS Procurement Project Support

CLIN 0002 applies only if the Government exercises the option for CLIN 0002. From the effective date of option exercise for a period of 12 months thereafter, the Contractor shall make available and employ its facilities and personnel at the level of effort set forth in Section F, services of others, and materials and shall utilize its best efforts to perform management and acquisition services as defined herein, with expenditure data to be delivered in System Security Plan and Plans of Action and Milestones Reviews, Technical Reports to be delivered (as required), and Post Completion Report of Man Hours and Expenditures.

NWS Procurement Project Programmatic, SE and SSE Support

The Contractor shall provide INWSS SME with in-depth understanding of the NWS policy, system and subsystem requirements, NWS missions at the SWFs, and submarine transit protection in support of INWSS procurement project activities, including developing, reviewing and providing recommendations on project acquisition plans, programmatics (i.e., new technology, plans, schedules, documentation, implementation and costs) and technical aspects (i.e., plans, assessments, documentation, testing, verification and implementation) for development, production and installation phases of INWSS projects.

The Contractor shall assist in programmatic, technical and financial reviews of prime contractor plans, documentation and work, and provide guidance and recommendations to the Government during all phases of INWSS Projects.

The Contractor shall attend or lead project reviews and working meetings as required to assist the Government in management of these activities.

The Contractor shall leverage their expertise in the SSP Risk Management Framework (RMF) processes and INWSS non-enterprise systems to provide Cybersecurity support in coordinating, implementing and enforcing information system security policies, standards and methodologies, including acting as a SP207 Information Systems Security Officer (ISSO) as required. The Contractor shall assist the SP207 Information Systems Security Manager (ISSM) in monitoring other INWSS contractor’s SSE practices, including Cybersecurity, and provide recommendations to address assessed security risks and mitigation efforts. The Contractor shall assist the SP207 ISSM in assessing the INWSS Operational Support activities and provide recommendations to address identified evolving security threats. The Contractor shall assist the SP207 ISSM in reviewing and rewriting aging INWSS Cybersecurity documents, leveraging their SSP RMF SME and innate knowledge of INWSS non-enterprise systems to realign INWSS Cybersecurity documentation with evolving SSP SSE and Cybersecurity processes and documentation. The Cybersecurity support shall extend to interfacing with other entities (e.g., Coast Guard, Space and Naval Warfare Systems Center (SPAWAR), and other Government Agencies) to support the INWSS, including the Transit Protection Program. Any such activities shall be coordinated with the Contracting Officer’s Representative (COR) and SSP Chief Information Officer (SPCIO) as may be needed.

The Contractor shall assist the Government by providing analysis and recommendations of project concepts of operations, organizational structures and alignment, training and logistical support planning, alternative technical and programmatic approaches, advanced technologies and specific problem identification and resolution relative to INWSS procurement projects during the project development and implementation.

The Contractor assist the Government by providing analysis and recommendations of the prime contractor’s INWSS procurement project acquisition and sustainment strategies; assist with evaluations of the INWSS prime contractor relative to procurement project contract requirements including performance parameters, Cybersecurity and project metrics; evaluate the prime contractor performance regarding incentives scoring and provide recommendations for modifications to address programmatic changes and emerging issues.

The Contractor shall participate in the Transit Protection System software testing, preliminary hardware checkout, and unit simulation on developmental products to verify and validate hardware and software requirements. The Contractor shall evaluate performance to the requirements and shall recommend appropriate management actions relative to support contractor performance. The Contractor shall assess the compliance of support contractors and shall ensure all deliverable products and services, including data deliverables, comply with the contract requirements. The Contractor shall organize, track, summarize, validate, verify, interpret, archive and make recommendations on the status, documentation, analysis and coordination of all aspects of support contractors.

The Contractor shall support the conduct of T-AGSE system level testing on all developmental products delivered to the Government for qualification and fielding, to include assuming responsibilities as the test director or to act in other support capacity as directed by the Government. Additionally, the Contractor shall analyze developmental product performance through the subsystem test reports provided by support contractors. The Contractor shall review final functional, performance, and environmental test plans to support shore-based qualification testing. The Contractor shall review and evaluate final at-sea sensor subsystem test plans for execution. The Contractor shall participate in the installation of developmental units and provide recommendations for future installations.

CLIN 0003

4.0 (O&MN) (Cost-Plus-Fixed-Fee) (Level of Effort) Nuclear Weapons Security (NWS) Sea Launched Cruise Missile Nuclear (SLCM-N) Program Management Support From the effective date of Contract Award through a period of 12 months thereafter, the Contractor shall make available and employ its facilities and personnel at the level of effort set forth in Section F, services of others, and materials and shall utilize its best efforts to perform the management and acquisition services as defined herein, with expenditure data to be delivered in the System Security Plan and Plans of Action and Milestones Reviews, Technical Reports to be delivered (as required), and Post Completion Report of Man Hours and Expenditures.

Integrated Nuclear Weapons Security Systems (INWSS) includes all systems and operations utilized to provide Nuclear Weapons Security (NWS) at the Strategic Weapons Facilities (SWFs) and to Fleet assets through the Transit Protection Program (TPP).

4.1 SLCM-N Program Management and NWS Acquisition Support

The Contractor shall provide program management support for SSP capability activation to include military construction (MILCON) activities within the current and future years Defense Program.

The Contractor shall assist Government personnel in coordinating activities needed to achieve SLCM-N and other program capabilities during facility planning, MILCON, and activation with respect to NWS requirements and operations.

The Contractor shall support inter-branch coordination between SP207 and other stakeholders such as SP00S31, SP25, SP04, and SP27.

The Contractor shall assist the Government in the generation of activation charters to identify stakeholder’s roles and responsibilities, activity scope, and integrated schedules for all projects involving NWS.

The Contractor shall provide Program Management support to accomplish activities related to the program plans/charters for facilities and NWS.

The Contractor shall incorporate NWS lessons learned from past capability activations and associated MILCON activities.

The Contractor shall support working groups, IPTs and other coordination meetings.

The Contractor shall support Leadership status briefings.

The Contractor shall support any Government contracting and acquisition process.

4.2 NWS Systems Engineering (SE) Support

The Contractor shall advise on the implementation of Systems Engineering policies and requirements into INWSS policy, process, and documentation to remain compliant for NWS purposes.

The Contractor shall assist in the development, review, updating and implementation monitoring of INWS SE policies, processes and documentation (e.g., Weapons Specifications, Quality Control (T9001C), and NWS Ordnance Documents (ODs).

The Contractor shall act as the INWSS IPT lead when assigned and shall assist various INWSS IPTs and Working Groups (WGs).

The Contractor shall provide analysis and recommendations for alternative technical and programmatic approaches, future technologies and specific SE activities related to problem identification and resolution relative to the INWSS development, production, installation and operational support strategies and efforts.

The Contractor shall assist in risk management, root cause analysis, corrective action, and continuous improvement activities to mitigate and identify NWS risks, when required.

The Contractor shall support resolution of engineering issues encountered during efforts to design, build, integrate and test the SLCM-N submarine platforms and facilities.

The Contractor shall support Strategic Weapon System (SWS) and NWS coordination and system engineering efforts, assist in preparation for SWS and NWS program reviews, and develop program plans and related documents to support the acquisition process.

The Contractor shall eview policy documents, SSP branch reports, and assist the NWS Branch in conducting technical assessments and analyses.

4.3 Technical Branch/PMO Support

The Contractor shall support the development of facility requirements and the subsequent testing, special NWS studies and certification required to establish Facility SLCM-N capability.

The Contractor shall support the shipboard system test program, identify issues and recommend methods for resolution.

The Contractor shall support activities related to implementing program plans and charters for facilities and NWS.

The Contractor shall assist in coordinating interfaces, identifying any related issues, and recommending resolution strategies.

The Contractor shall assist technical branches in the development of Program related presentations, letters, memorandums, white papers, and other documentation.

4.4 Travel