Solicitation - N6660426R0063.pdf

SECTION

15A. NAME AND

ADDRESS

OF OFFEROR

SOLICITATION, OFFER, AND AWARD 1. This Contract is a Rated Order under the Defense Priorities and Allocations System (DPAS) - Code of Federal Regulations - at 15 CFR 700.

RATING PAGE OF PAGES

2. CONTRACT NUMBER 3. SOLICITATION NUMBER 4. TYPE OF SOLICITATION 5. DATE ISSUED 6. REQUISITION/PURCHASE NUMBER

CODE7. ISSUED BY 8. ADDRESS OFFER TO (If other than item 7)

NOTE: In sealed bid solicitations "offer" and "offeror" mean "bid" and "bidder".

SOLICITATION

9. Sealed offers in original and copies for furnishings the supplies or services in the Schedule will be received at the place specified in item 8, or if hand carried, in the depository located in until local time

CAUTION - LATE Submissions, Modifications, and Withdrawals: See Section L, Provision Number 52.214-7 or 52.215-1. All offers are subject to all terms and conditions contained in this solicitation.

10. FOR

INFORMATION

CALL:

A. NAME B. TELEPHONE (NO COLLECT CALLS)

AREA CODE NUMBER EXTENSION

C. EMAIL ADDRESS

11. TABLE OF CONTENTS

(X) DESCRIPTION PAGE(S) (X) SECTION PAGE(S)DESCRIPTION

A B C D E F G H

I

J

K

L

M EVALUATION FACTORS FOR AWARD

INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS

REPRESENTATIONS, CERTIFICATIONS AND OTHER

STATEMENTS OF OFFERORS

PART IV - REPRESENTATIONS AND INSTRUCTIONS

LIST OF ATTACHMENTS

PART III - LIST OF DOCUMENTS, EXHIBITS AND OTHER ATTACHMENTS

CONTRACT CLAUSESSOLICITATION/CONTRACT FORM

SUPPLIES OR SERVICES AND PRICES/COSTS

DESCRIPTION/SPECIFICATIONS/WORK STATEMENT

PACKAGING AND MARKING

INSPECTION AND ACCEPTANCE

DELIVERIES OR PERFORMANCE

CONTRACT ADMINISTRATION DATA

SPECIAL CONTRACT REQUIREMENTS

NOTE: Item 12 does not apply if the solicitation includes the provisions at 52.214-16, Minimum Bid Acceptance Period.

OFFER (Must be fully completed by offeror)

12. In compliance with the above, the undersigned agrees, if this offer is accepted within calendar days (60 calendar days unless a different period is inserted by the offeror) from the date for receipt of offers specified above, to furnish any or all items upon which prices are offered at the set opposite each item, delivered at the designated point(s), within the time specified in the schedule.

13. DISCOUNT FOR PROMPT PAYMENT

(See Section I, Clause Number 52.232-8)

14. ACKNOWLEDGMENT OF AMENDMENTS

(The offeror acknowledges receipt of amendments to the SOLICITATION for offerors and related documents numbered and dated):

10 CALENDAR DAYS (%) 20 CALENDAR DAYS (%) 30 CALENDAR DAYS (%) CALENDAR DAYS (%)

DATEAMENDMENT NUMBERAMENDMENT NUMBER DATE

CODE FACILITY 16. NAME AND THE TITLE OF PERSON AUTHORIZED TO SIGN OFFER

(Type or print)

15B. TELEPHONE NUMBER

AREA CODE NUMBER EXTENSION

15C. CHECK IF REMITTANCE ADDRESS IS

DIFFERENT FROM ABOVE - ENTER

SUCH ADDRESS IN SCHEDULE.

17. SIGNATURE 18. OFFER DATE

AWARD (To be completed by Government)

19. ACCEPTED AS TO ITEMS NUMBERED 20. AMOUNT 21. ACCOUNTING AND APPROPRIATION

22. AUTHORITY FOR USING OTHER THAN FULL OPEN COMPETITION UNDER THE

UNITED STATES CODE AT:

10 U.S.C. 3204(a) ( )41 U.S.C. 3304(a)

24. ADMINISTERED BY (If other than Item 7)

26. NAME OF CONTRACTING OFFICER (Type or print)

IMPORTANT - Award will be made on this Form, or on Standard Form 26, or by other authorized official written notice.

AUTHORIZED FOR LOCAL REPRODUCTION

Previous edition is unusable

23. SUBMIT INVOICES TO ADDRESS SHOWN IN

(4 copies unless otherwise specified)

25. PAYMENT WILL BE MADE BY

27. UNITED STATES OF AMERICA

(Signature of Contracting Officer)

28. AWARD DATE

CODE

ITEM

STANDARD FORM 33 (REV. 12/2022)

Prescribed by GSA - FAR (48 CFR) 53.214 (c)

SEALED BID (IFB) INVITATION FOR BID

NEGOTIATED (RFP) REQUEST FOR

PROPOSAL

(Hour) (Date)

PART I - THE SCHEDULE PART II - CONTRACT CLAUSES

Section A - Solicitation/Contract Form

Payload Control System (PCS)

Product Service Code: AC33

GENERAL INFORMATION

Distribution: FILE, KR, NUWC 0121, DCMA, DFAS, COR PID Number: N66604-25-RFPREQ-NPT-25-0209 NUWCDIVNPT POC: Nico Montanari, nico.s.montanari.civ@us.navy.mil

This requirement is being solicited as a sole source SBIR (Small Business Innovative Research) Phase III to SEACORP in accordance with the Small Business Act (15 U.S.C. 638).

The North American Industry Classification System (NAICS) Code for this requirement is 541715 - Research and Development in the Physical Engineering, and Life Sciences (except Nanotechnology and Biotechnology). The small business size standard is 1,000 employees.

Companies requesting to view Applicable Documents, which include CUI Specific Controlled Information, must be registered according to the DoD Joint Certification Program (JCP) to access the applicable documents. See the following website for further information: https://www.dla.mil /Logistics-Operations /Services/JCP/.

To request applicable documents, please contact the POC and follow the instructions as specified below:

STEP ONE: Point of Contact: Nico Montanari, Email: nico.s.montanari.civ@us.navy.mil

Please include your vendor CAGE Code and certified DD2345 when sending the POC a request to view the documents.

NOTE: The name and e-mail address of the individual requesting the documents must match those listed as the JCP data custodian on the certified DD2345, as well as the active company CAGE Code.

STEP TWO: DoD Secure Access File Exchange (SAFE) LINK: https://safe.apps.mil.

The POC will use the "Drop Off' feature to upload the Applicable Documents to the DoD SAFE website. The certified JCP data custodian will receive an email containing a link and a passcode to access the documents on the DoD SAFE website. The link to the documents will expire seven (7) days from the day the link and passcode is sent.

Note: Minimum Guarantee: The Government has determined a minimum guarantee of $75,000.00 on this contract.

N6660426R0063 https://safe.apps.mil.

Section B - Supplies or Services & Prices or Costs

Additional Information/Notes

MARK FOR INFORMATION:

The Contractor shall include the following "Mark For" information clearly marked on all packages (or items themselves if they are not packaged) delivered under this contract:

Mark For Information for NUWCDIVNPT Receiving Officer, Naval Station Newport 47 Chandler Street Newport, RI 02841-1716 NUWC Division, Newport, Code: TBD at the delivery/task order level Contract/Order #: TBD at the delivery/task order level

Item Supplies/Service Estimated Quantity

Unit Unit Price Amount

Payload Control System (PCS) Engineering Services Services in accordance with Statement of Work in Section C, and as specified in individual orders during the ordering period.

The Government estimates 228,130 labor hours through the five (5) year ordering period.

Pricing Arrangement: Cost Plus Fixed Fee

1 Job

Other Direct Costs associated with labor under CLIN 0001

THE OFFEROR SHALL INCLUDE A MATERIAL/ODC

ESTIMATE OF $1,718,220.00 AND A TRAVEL ESTIMATE OF

$443,842.00 (FIGURES DO NOT INCLUDE BURDENS). THE

OFFEROR SHOULD ADD APPLICABLE BURDENS TO THESE

ESTIMATES, ROUNDED TO THE WHOLE DOLLAR.

THE OFFEROR SHALL NOT INCLUDE FEE ON BURDENED

ODCS.

Pricing Arrangement: Cost No Fee

1 Lot

Contractor Data Requirements List (CDRLs) Data in support of the Statement of Work tasking. Specific applicable CDRLs will be attached to individual delivery and task orders as required.

Pricing Arrangement: Firm Fixed Price

1 Lot

Additional Regulation or Supplemental Clauses Incorporated by Full Text

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

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

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

N6660426R0063

(c) Relocation costs and travel costs incidental to relocation are allowable to the extent provided in FAR 31.205-35; however, Procuring Contracting Officer approval shall be required prior to incurring relocation expenses and travel costs incidental to relocation.

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

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

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

(iii) travel costs incurred in the replacement of personnel when such replacement is accomplished for the Contractor's or employee's convenience.

(End of Text)

B-232-H003 PAYMENTS OF FEE (S) (COMPLETION) (NAVSEA) (OCT 2018) (Oct 2018)

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

(b) The Government shall make payments to the Contractor, subject to and per the clause in this contract entitled "Fixed Fee" (FAR 52.216-8) or "Incentive Fee", (FAR 52.216-10), as applicable. Such payments shall be equal to TO BE PROPOSED BY OFFEROR percent (TO BE PROPOSED BY OFFEROR) of the allowable cost of each invoice submitted by and payable to the Contractor pursuant to the clause of this contract entitled "Allowable Cost And Payment" (FAR52.216-7), subject to the withholding terms and conditions of the "Fixed Fee" or "Incentive Fee" clause, as applicable (percentage of fee payable is based on fee dollars divided by estimated cost dollars including facilities capital cost of money). Fee shall not be applied on Facilities Capital Cost of Money per FAR 15.404-4(c)(3) and DFARS 215-404-71-4. Total fee(s) paid to the Contractor shall not exceed the fee amount(s) set forth in this contract.

(c) In the event of discontinuance of the work under this contract, or any specified phase of the contract, per the clause of this contract entitled "Limitation of Funds" (FAR 52.232-22) or "Limitation of Cost" (FAR 52.232-20), as applicable, the fee shall be equitably adjusted by mutual agreement to reflect the diminution of work. If the adjusted fee is less than the sum of all fee payments made to the Contractor under this contract, the Contractor shall repay the excess amount to the Government. If the adjusted fee exceeds all payments made to the Contractor under this contract, the Contractor shall be paid the additional amount, subject to the availability of funds. In no event shall the Government be required to pay the Contractor any amount in excess of the funds obligated under this contract at the time of the discontinuance of work.

(d) Fee(s) withheld pursuant to the terms and conditions of this contract shall not be paid until the contract has been modified to reduce the fee(s) per paragraph(c) above, or until the Procuring Contracting Officer has advised the paying office in writing that no fee adjustment is required.

(End of Text)

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

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

(End of Text)

Section C - Description/Specifications/Statement of Work

STATEMENT OF WORK (SOW)

Submarine Portable Launch System

1.0 Background

The Submarine Combat and Weapons Control Program Office (PMS 425) is the acquisition lead for the Submarine Combat Control System (CCS) and Submarine Launcher programs. The Program Management Office (PMO) is responsible for the design, testing and fielding of these systems across all variants of United States Navy (USN) submarines. Naval Undersea Warfare Center, Division Newport (NUWCDIVNPT) Code 25 supports PMS425 as the Submarine CCS Technical Direction Agent (TDA), In-Service Engineering Agent (ISEA) and Installation lead, and has been in this role for decades starting with AN/BYG-1 predecessor programs including the MK 117 and 118 Fire Control Systems (FCS), Combat Control System (CCS) MK I and CCS MK2 systems. These roles involve tasking inclusive of prototyping hardware and software for future payload integration into the CCS and Launchers, executing land based and at-sea testing of future concepts and production baselines, executing systems engineering activities, test & evaluation activities and fielding and sustainment of these systems.

This contract will focus on modifying the payload control system (PCS) technology to adapt the CCS to new payload interfaces planned for submarine introduction. Code 25 is the Subject Matter Expert (SME) for the CCS and launcher interfaces and with this Small Business Innovation Research (SBIR) technology will have the capability to execute the future prototyping tasking being requested by the PMO and various payload sponsors to accelerate program of record capability integration and fleet fielding.

Code 25 requires the evolutionary development of the PCS technology to address new capabilities on the horizon for integration into the submarine CCS. The technology needs to be modified to work with the newest modernizations of the tactical PCS baselines. These baselines are established as part of the Advance Processor Build (APB) process. Every two years, a PCS baseline with new and improved capabilities is released to the Fleet. Implementation of these capabilities affects underlying software architecture and infrastructure. The PCS technology is built on this architecture and accordingly needs to be modified in order to enable payload integration prototypes.

1.1 Places of Performance

NUWCDIVNPT, Newport, RI and Contractor facility at Middletown, RI

1.2 Authorized Users

NUWCDIVNPT Codes 25, 34, 45, and 85 are authorized to place task orders on this contract.

1.3 Sponsors

The Government anticipates that the following sponsors will fund task orders on this contract: PMS 351, PMS 394, PMS 397, PMS 404, PMS 406, PMS 415, PMS 425, PMS 450, Commonwealth of Australia, PEO-SUB International, SP-C, SP04, Strategic Capabilities Office (SCO), Office of Naval Research (ONR), PMA201, PMA280, PMA281, AUKUS A&I, IWS-3, and PMW 770.

1.4 Types of Funding

The Government anticipates that the following types of money will be used to fund task orders on this contract: Research, Development, Test and Evaluation (RDT&E); Special Deposits (SPDP); Other Procurement, Navy (OPN); Weapons Procurement, Navy (WPN); Operation & Maintenance, Navy (O&MN); Foreign Military Sales (FMS); Ship Construction and Conversion, Navy (SCN); National Sea-Based Deterrence Fund (NSBDF); and NUWCDIVNPT Overhead (OH).

2.0 Scope

The contractor shall perform architecture development, interface specification development and modification, prototype development, software /hardware integration and testing, capstone demonstration to further develop PCS Technology and CSA-PI Data Interface (CDI) software to enable payload integration prototypes, and early platform installation, test, and analysis efforts to validate technology advancements.

2.1 Program or Systems Supported

The scope of the effort includes modifications of AN/BYG-1 and CDI software, for:

(a) Each Advanced Processor Build (APB),

(b) Each Technical Insertion Hardware (TIH),

(c) The payloads being integrated with PCS,

(d) The payloads integrating with PCS interface protocols, and

(e) The payloads integrating with the Non-Propulsion Electronic Systems (NPES)

3.0 Applicable Documents

The contractor shall perform the tasking required in Section 4.0 in accordance with the below Applicable Documents.

NUMBER TITLE REVISION

/DATE

APPLICABLE

TASK NUMBER

3.1 DOD INSTRUCTION 4120.24 DEFENSE STANDARIZATION PROGRAM March 2022 4.1, 4.2, 4.3, 4.4, 4.5

3.2 IEEE/EIA 12207 Information Technology - Software Life Cycle Processes 2017-11-15 4.2, 4.3, 4.4, 4.5

3.3 MIL-STD-31000C Detail Specification Technical Data Packages 03-FEB-2025 4.2, 4.3, 4.4, 4.5,4.6

3.4 Technical Requirements Manual for Temporary Submarine Alterations, (NAVSEA S9070- AA-MME-010/SSN/SSBN), Third Revision, ACN-4

6 JUN 2013 4.5, 4.6

3.5 MIL-STD-882E Standard Practice for System Safety

Change 1, 27-SEP-

4.4, 4.5, 4.6

3.6 MIL-STD-961E Department of Defense Standard Practice for Defense Specifications Change 4, 16-JUL-

4.2, 4.3, 4.4

3.7 NAVSEAINT 3960.2E Test and Evaluation 3 FEB 2025 4.4, 4.5, 4.6

3.8 NAVSEAINST 5510.1D Department of the Navy Information and Personnel Security Program Regulation

9 JAN 2023

4.1, 4.2, 4.3, 4.4, 4.5, 4.7

3.9 DODM 8140.03 Cyberspace Workforce Qualification and Management Program 15 FEB 2023 4.2, 4.3, 4.4, 4.5, 4.6, 4.7

3.10 DoDM 5200.01, Vol 1, DoD Information Security Program

Change 3, 17 January 2025

4.1, 4.2, 4.3, 4.4, 4.5, 4.6

3.11 DoDM 5200.01, Vol 2, DoD Information Security Program

Change 4, 28 July

4.1, 4.2, 4.3, 4.4, 4.5, 4.6

3.12 DoDM 5200.01, Vol 3, DoD Information Security Program

Change 4, 17 January 2025

4.1, 4.2, 4.3, 4.4, 4.5, 4.6

3.13 DoDM 5200.48 Controlled Unclassified Information 06 March 2020 4.1, 4.2, 4.3, 4.4, 4.5, 4.6

3.14 NUWCDIVNPTINST 4000.1B Receipt, Delivery, Inspection, and Shipment of Material 11 September 2023 4.1, 4.2, 4.3, 4.4, 4.5, 4.6

3.15 NAVSEA M-5510.1, NAVSEA Security Program Manual July 2022 4.1, 4.2, 4.3, 4.4, 4.5, 4.6

3.16 NSWCHQ/NUWCHQINST 5510.1, Security Program Manual 09 November 2020 4.1, 4.2, 4.3, 4.4, 4.5, 4.6

3.17 NUWCDIVNPT 5500.4, NUWCDIVNPT Command Security Manual 19 April 2023 4.1, 4.2, 4.3, 4.4, 4.5, 4.6

3.18

DoD 8570.01-M, Information

Assurance Workforce Improvement

Program

Change 4, 10

November

4.7

3.19 Naval Undersea Warfare Center Division Newport Critical Information and Indicators List

(CIIL)

22 Oct 2025 All

3.2 COMSEC Applicable Documents

3.2.1 CMS-1B, DoN COMSEC Policy and Procedures 31 March 2025 4.4,4.5,4.6

3.2.2 OPNAVINST 2221.5, Release of COMSEC Material to U.S. Industrial Firms under Contract to USN.

Change 4, 10 November 2015

4.4,4.5,4.6

3.2.3 NUWCDIVNPTINST 2280.1H Local Handling and Accountability of COMSEC Materials 12 December 2022 4.4,4.5,4.6

3.2.4 NUWCDIVNPTINST 2280.2H COMSEC Emergency Action Plan 24 March 2021 4.4,4.5,4.6

4.0 Technical Requirements

The following tasks shall be accomplished in accordance with Government Specifications and

Standards in Section 3.0. The Contractor shall perform tasks using Government Furnished

Information (GFI) identified in Section 6.0. Specific requirements will be identified in the task order statements of work.

4.1 Concept of Operations (CONOPS) and Top-Level Requirement (TLR) Development

Upon receipt of a task order, the contractor shall modify existing payload mission CONOPs, provided as GFI, to capture performance characteristics and limitations of the payload that is planned for integration. In the CONOPs, the contractor shall identify requirements for targeting, pre-launch, launch, and post-launch, as well as potential impacts to safety, security, and data classification and retention, on the representative combat system and platform identified in the task order. The contractor shall attend payload systems engineering working group meetings to gather information regarding design and CONOPs constraints.

Deliverable: The contractor shall deliver revised CONOPs in accordance with CDRL A001 (DI-ADMN- 80925A).

Upon Government approval of the CONOPs, the contractor shall recommend TLRs for capabilities of new payloads and submarine variants interfacing with CDI software. In the TLR, the contractor shall include software interface requirements in terms of both objective and threshold requirements. The contractor shall provide a detailed analysis of the potential impacts of the TLRs to existing systems and the CDI software. In the analysis, the contractor shall discuss: recommended production combat system design changes; impacts to existing interfaces; and any new CDI software changes.

Deliverable: The contractor shall deliver TLR in accordance with CDRL A002 (DI-MISC-80652) and Technical Report in accordance with CDRL A003 (DI-MISC-80508B).

4.2 Architecture Development

Upon Government approval of TLR and in preparation for design reviews, the contractor shall provide a CDI software architecture design package, which shall include software components (identifying open source and proprietary components), abstraction layers, software development kits (SDKs), and application program interfaces (APIs). The contractor shall also provide combat system implementation approaches and software integration plans in the architecture design package. The contractor shall provide a read-ahead of the architecture design package one week in advance of scheduled design review. At the design review, the contractor shall present the architecture design package, and record meeting minutes and action items assigned.

The contractor shall track action items for closure.

Deliverable: The contractor shall deliver CDI Software Architecture Design Package in accordance with CDRL A004 (DI-SESS-82176) and .Meeting Minutes in accordance with CDRL A005 (DI-ADMN-81505)

4.3 Software Development

In accordance with Clause C-227-H007, the contractor shall prepare a Software Development Plan (SDP) for Government review and concurrence for computer software developed and maintained under this contract. The contractor shall identify any changes, modifications, additions or substitutions to the SDP, and upon Government concurrence, update the SDP for the specific computer software throughout the life of this contract.

Upon closure of the design review and Government approval of the architecture design package, and using Combat System software provided as GFI:

- The contractor shall update existing CDI software code for compatibility with the existing payload control system, applicable variants, and launcher systems.

- The contractor shall present status of software development at working group meetings and software design reviews.

- The contractor shall deliver source code, software documentation, developer notes, and development environment.

- The contractor shall implement information assurance into the software design in accordance with Applicable Document 3.10.

- The contractor shall develop and maintain a problem trouble report (PTR) tracker.

- The contractor shall provide updates of PTR status at Configuration Control Board (CCB) meetings and provide a list of recommended PTR adjudications.

- Upon Government approval, the contractor shall adjudicate PTRs identified as approved-to-fix.

Deliverable: The contractor shall deliver Software Development Plan in accordance with CDRL A006 (DI-IPSC- 81427B), CDI Source Code in accordance with CDRL A007 (DI-IPSC-81488), PTR Tracker in accordance with CDRL A008 (DI-MISC-80508B), and PTR Adjudications in accordance with

CDRL A009 (DI-MISC-80508B).

4.4 Hardware/Software Integration and Testing

The contractor shall develop and deliver simulator/stimulator software and prototype hardware (as required) for validation of the CDI software for the portable launch system. The contractor shall deliver simulator/stimulator software code, simulator/stimulator software design and user documentation, and any prototype hardware required for the integration and installation prior to Government evaluation.

The contractor shall develop, deliver, integrate, and install prototype hardware and software in an Engineering Development Module (EDM) laboratory at NUWCDIVNPT to support formal evaluation of the new design to be performed by the Government. The contractor shall provide peripheral equipment to be used during the development and testing of the CDI Software. The contractor shall develop test plans and procedures to validate that the software meets the approved TLRs. The contractor shall develop, or recommend revisions to, design documents, test plans, and procedures to demonstrate adjudication of completed PTRs that were generated from

4.3 tasking. In accordance with Government approved test plans and procedures, the contractor shall test the software and deliver test reports.

Deliverable: The contractor shall deliver Simulator/Stimulator Software Code in accordance with CDRL A00A (DI-IPSC-81488), Simulator/Stimulator Software Design and User Documentation in accordance with CDRL A00B (DI-AVCS-80700A), Test Plans and Procedures in accordance with CDRL A00C (DI-SESS-81704), and Test Reports in accordance with CDRL A00D (DI-NDTI-80809).

4.5 Capstone Demonstration

The contractor shall demonstrate the full end-to-end thread for mission areas of the payload defined in the CONOPs in a formal Concept of Operations Exercise (COOPEX) for the portable launch system. Upon completion of the COOPEX, the contractor shall document the results of the COOPEX and deliver a formal report detailing the results of all testing and post-test analysis. In the report, the contractor shall identify any limitations and impacts to other subsystems and identify operational and security impacts of the current concept design. The contractor shall include recommended changes or modifications to design, requirements, or the CONOPS in the report.

Deliverable: The contractor shall deliver Capstone Report in accordance with CDRL A00E (DI-MISC 80508B).

4.6 Shipboard Demonstration

4.6.1 Alterations

Once the Capstone Demonstration is completed and the Government concurs that software/hardware PTR is acceptable, the contractor shall review the GFI (shipboard alteration data packages for Ship Alterations (SHIPALTs), Temporary Alterations (TEMPALTs), Engineering Change Instructions (ECI), and Temporary Engineering Change Instructions (TECIs)) and provide recommendations for improvement to shipboard installation efforts. Additionally, upon Government review and approval of recommendations, the contractor shall update the alteration TDPs to encompass the approved recommendations.

Deliverable: The contractor shall deliver Updated Alteration Technical Data Packages in accordance with CDRL A00F (DI-SESS-80776B), User's and Operating Guides in accordance with CDRL A00G (DI-MISC- 80508B), Test Plans in accordance with CDRL A00H (DI-NDTI-80566A).

4.6.2 Installation and Checkout

As identified in a Government installation schedule, provided as GFI, and upon receipt of approved shipboard alteration data packages, provided as GFI, the contractor shall perform installation and checkout of demonstration systems.

Deliverable: The contractor shall deliver System Operational Verification report in accordance with CDRL A00J (DI-NDTI-80809B), Trip Reports in accordance with CDRL A00K (DI-MISC-81943).

4.6.3 Demonstration of Software/Hardware

In accordance with Government approved Test Plans and Procedures, the contractor shall perform dockside and at-sea test periods to conduct system performance assessments of the portable launch system to include the collection of data required to assess the system.

Deliverable: The contractor shall deliver Trip Reports in accordance with CDRL A00K (DI-MISC-81943).

4.6.4 Analysis and Recommendations

Upon completion of shipboard demonstrations, the contractor shall review post-mission analysis data, provided as GFI, and perform analysis, assessments, and recommendations for system improvements.

Deliverable: The contractor shall deliver Test Reports in accordance with A00J (DI-NDTI-80809B).

4.7 Cyberspace/Cyber Workforce (CWF)

4.7.1 Cyberspace Qualifications

Per DFARS 252.239-7001 'Information Assurance Contracting Training and Certification,' all personnel performing cyber functions must be trained and qualified. In addition, personnel shall maintain the appropriate security clearance per SECNAV M-5510.30C to perform the tasks associated with their assigned positions.

Note: DFARS uses Information Assurance (IA) which is the old title and acronym; it has been replaced by Cyberspace/Cyber Workforce (CWF).

The contractor is required to earn and maintain appropriate baseline certification as identified in DOD 8570.01- M for the position and tasking being performed.

If privileged access is required, the contractor shall complete a privileged access agreement, SECNAV 5239/1, and submit it to the COR. Contractors have up to 6 months to obtain applicable operating system and computing environment training or the account(s) will be suspended. The contractor shall provide a copy of the certificate

(s) of completion to the COR.

4.7.2 Cyberspace Reporting

The contractor shall provide a list of all personnel assigned to the contract performing cyber functions as a part of a monthly CWF Report. The report shall include employee name, contract number, the applicable CWF category and level, required certifications and fulfillment status. Note that Contractor CWF personnel must receive designation approval in writing by the Commanding Officer, or the C-ISSM via "By Direction" authority, prior to performing CWF functions.

The contractor shall submit new hire information for tasking requiring cyber functions to the COR at least seven

(7) days prior to the new hire employee beginning performance of any cyber functions. New hire information shall include name, contract number, list of applicable cyber functions category, level, required certifications and fulfillment status, as well as a copy of the baseline certification documentation. Per DFARS 252.239-7001 (c), "Contractor personnel who do not have proper and current certifications shall be denied access to DoD information systems for the purpose of performing information assurance functions, and therefore may not be allowed to charge to the contract.

Deliverable: The Contractor shall deliver a monthly CWF Report in accordance with CDRL A00L (DI-MGMT- 82160).

4.8 Meeting Support

The contractor shall attend Working Group meetings to gather necessary information about any planned system modifications to allow for payload integration. For all relevant meetings as identified in a Government meeting schedule, provided as GFI, the contractor shall coordinate, attend, prepare agendas and briefing material, take minutes and track actions.

Deliverable: The contractor shall deliver Presentation Material in accordance with CDRL A00M (DI-ADMN- 81373). Meeting Minutes in accordance with CDRL A005 (DI-ADMN-81505)

5.0 Progress Reports

5.1 Contract Status Report

The Contractor shall prepare a Contractor's Status Report that indicates the progress of work, status of the program(s), and existing or potential problem areas for all assigned tasks. The Contractor shall submit the Contract Status Report for the same timeframe as each invoice submitted in the Wide Area Workflow (WAWF) Module of the Procurement Integrated Enterprise Environment (PIEE).

Deliverable: The contractor shall deliver Contractor's Status Reports in accordance with CDRL A00N - DI-

MGMT-81991.

5.2 Training

5.2.1 The Contractor shall require all Contractor employees performing work at any NUWC Division Newport site, who has a Common Access Card (CAC) and an NMCI Account, to complete all required Mandatory trainings.

5.2.2 The Contractor shall require Contractor employees to complete any applicable Limited Audience required training(s). Note: Limited Audience required training(s) may be applicable regardless of performance site location.

5.2.3 The Contractor shall fill out and submit to the Government the Training Completion Status Report, GFI 6.10, affirming all Mandatory training and any applicable Limited Audience required training(s) are completed. The required training and required training schedule is available at the following website: [WILL BE PROVIDED AT AWARD] under Mandatory Training Instructions. See the .pdf Mandatory Training Instruction - Contractors Only.

5.2.4 The Contractor shall validate the Government's DRAFT Limited Audience Training Applicability List GFI 6.10 for accuracy and completeness and submit to the Government a finalized Limited Audience Training Applicability List. The following Limited Audience required training(s) are applicable to this requirement:

NATO

5.2.5 The Training Completion Status Report and Limited Audience Training Applicability List shall include the contract number, contactor employee name, specific training course title and identification number, and completion date for all contractor employees asserting training completion. Contact the COR identified in Section G if additional access instructions are needed. If specific training questions arise, contact the POC listed for the training in the above-specified .pdf(s).

Deliverable: The contractor shall deliver Training Status Reports in accordance with CDRL A00P (DI-MISC- 80508B).

6.0 Government Furnished Information

The following Government Furnished Information (GFI) will be made available under this contract.

Number Title Task Number

6.1 Existing Payload Mission CONOPS 4.1

6.2 PMA-280 Tomahawk Weapon System

Integrated Master Schedule (IMS) 4.1, 4.2, 4.3, 4.4, 4.5, 4.6

6.3

PMA-281 Theatre Mission Planning Center

(TMPC) Integrated Master Schedule

(IMS)

4.1, 4.2, 4.3, 4.4, 4.5, 4.6

6.4 PMS-425 AN/BYG-1 Integrated Master Schedule (IMS) 4.1, 4.2, 4.3, 4.4, 4.5, 4.6

6.5 Operational Document (OD) 44979 Firing

Craft Operating Procedures 4.1, 4.2, 4.3, 4.4, 4.5, 4.6

6.6

Virginia Strike Requirements Working

Group (VSRWG) Charter, 13 August 2015

4.1, 4.2, 4.3, 4.4, 4.5

6.7

TBD - Future Submarine Payload

Capability Concept Specification and

Requirements Documents

4.1, 4.2, 4.3, 4.4, 4.5

6.8 Subsystem Requirements Specifications 4.2, 4.3, 4.4

6.9 Interface Requirements Specifications 4.2, 4.3, 4.4

6.10 Monthly CWF Report template 4.7

7.0 Government Furnished Property

The Government may provide Government Furnished Property (GFP) as listed in Attachment The contractor 2.

shall adhere to DFARS Clause 252.245-7005 for the management and reporting of Government Property and shall use the GFP Module of the Procurement Integrated Enterprise Environment (PIEE) as specified in the clause. In addition, the Contractor shall prepare and submit a Government Property (GP) Inventory Report to capture GFP status IAW CDRL A00Q (DI-MGMT-80441D).

Deliverable: The contractor shall deliver Government Property (GP) Inventory Reports in accordance with

CDRL A00Q.

8.0 Quality Surveillance and Performance Standards

The Government will conduct quality surveillance via various methods including formal and informal meetings, review of technical reports, review of monthly progress reports, and review of deliverables. Contractor performance will be evaluated in the areas of technical quality, cost control, schedule/timeliness, management, and regulatory compliance as follows:

- Technical Quality: The government will evaluate technical quality using the criteria defined in the Performance Requirements Summary Table (PRST), Attachment 4;

- Cost Control: The government will evaluate the contractor's effectiveness in forecasting, managing, and controlling actual costs in comparison to negotiated costs;

- Schedule/Timeliness: The government will evaluate the contractor's ability to meet negotiated milestones and delivery schedules;

- Management: The government will evaluate the contractor's ability to integrate and coordinate all activities needed to execute the contract;

Regulatory Compliance: The government will evaluate the contractor's compliance with the terms and conditions of the contract relating to applicable regulations and codes.

9.0 Information and Communication Technology (ICT) Accessibility Requirements

The Government has determined that this procurement is an exception to the Information and Communication Technology (ICT) Accessibility Standards (36 C.F.R. Part 1194, Appendix A). Notwithstanding that an exception exists, the Contractor may furnish items or services provided under this contract that comply with the ICT Accessibility Standards (36 C.F.R. Part 1194, Appendix A).

Exception #1 national security for United States Submarines.

10.0 Security Compliance

10.1 Program Protection

SECURITY: All Contractor personnel shall adhere to the Security provisions of 32 CFR Part 117 - National Industrial Security Program Operating Manual (NISPOM) and the security requirements of the attached DD254.

While performing work at a Government Facility, Contractor personnel shall comply with the security regulations of the host facility. Applicable FAR, DFARS, NMCARS clauses, and NAVSEA text shall be adhered to in the performance of this contract. Security incidents shall be promptly reported through the companies Facility Security Officer (FSO), to the Contracting Officer's Representative (COR), Technical Point of Contact (TPOC), and the Cognizant Security Office to NUWCDIVNPT Security.

Communications Security (COMSEC)

COMSEC is required for the contractors to perform tasks 4.1-4.8.

The contractor shall primarily use COMSEC access at NUWCDIVNPT facilities and while performing work aboard naval vessels.

Restricted Data (RD)

RD is required for the contractor to perform tasks 4.1-4.4, 4.8.

The contractor shall use RD access for payload information required for performance specification and interface development.

Critical Nuclear Weapon Design Information (CNWDI)

CNWDI is required for the contractor to perform tasks 4.1-4.4, 4.8.

The contractor shall use CNWDI access for payload information required for performance specification and interface development.

Formerly Restricted Data (FRD)

FRD is required for the contractor to perform tasks 4.1-4.4, 4.8.

The contractor shall use FRD access for payload information required for performance specification and interface development.

Sensitive Compartmented Information (SCI)

SCI is required for the contractor to perform tasks 4.1-4.8.

The contractor shall use SCI access to perform services in support of all SOW tasks.

Non-Sensitive Compartmented Information (non-SCI)

Non-SCI is required for the contractor to perform tasks 4.1-4.8.

The contractor shall use Non-SCI access to perform services in support of all SOW tasks.

North Atlantic Treaty Organization (NATO) Information

NATO information is required for the contractor to perform tasks 4.1-4.8.

The contractor shall use NATO access for payload information required for performance specification and interface development, software development, and testing.

Foreign Government Information (FGI)

FGI is required for the contractor to perform tasks 4.1-4.8.

The contractor shall use FGI access for payload information required for performance specification and interface development, software development, and testing.

Secret Internet Protocol Router Network (SIPRNET)

SIPRNET is required for the contractor to perform tasks 4.1-4.8.

The contractor shall use SIPRNET access to perform services in support of all SOW tasks.

Controlled Unclassified Information (CUI) including Legacy FOUO and Covered Defense Information (meeting the definition of 48 CFR 252.204-7012(a)) generated and/or provided under this contract shall be marked and safeguarded as specified in DoD Instruction 5200.48, CUI available at:

https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/520048p.PDF. Any product containing Covered Defense Information shall be assigned a distribution statement (distribution statements B through F) in accordance with DoDI 5230.24 (Distribution Statements on Technical Documents); and DoDI 5230.24, Enclosure 3 Procedures, available at https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi /523024p.pdf

INFORMATION SECURITY: If the work is performed at the Contractor's facility, the Contractor shall implement and maintain security procedures and controls to prevent unauthorized disclosure of classified information and controlled unclassified information (CUI) and to control distribution of CUI in accordance with National Industrial Security Program Operating Manual (NISPOM) codifying 32 CFR Part 117, NISPOM Rule, and SECNAV M-5510.36B. If the work is performed at the Government's facility, the Contractor shall comply with facility policy.

CUI INCIDENT REPORTING AND RESPONSE: The Contractor shall promptly report any unauthorized, inadvertent, or illegal release or disclosure of CUI to the Contracting Officer's Representative / Technical Point of Contact (TPOC), Procuring Contracting Officer, and the Security Office. Contractor personnel shall coordinate this effort through the relevant industry site FSO.

PUBLIC RELEASE: Any controlled unclassified information pertaining to this contract shall not be released for public dissemination, including posting to any social media sites such as Facebook or Twitter, unless it has been approved for public release by appropriate U.S. Government authority. Proposed public releases shall be submitted for approval prior to release through the appropriate U.S. Government Office.

10.2 Operations Security (OPSEC)

OPSEC is a process that identifies critical information to determine if friendly actions can be observed by adversary intelligence systems, determines if information obtained by adversaries could be interpreted to be useful to them, and then executes selected measures that eliminate or reduce adversary exploitation of friendly critical information.

The Contractor shall develop and implement, and update and maintain an OPSEC program to protect controlled unclassified and classified activities, information, equipment, and material used or developed by the Contractor and any subcontractor during performance of the contract. The Contractor shall be responsible for the subcontractor implementation of the OPSEC requirements. The Contractor developed OPSEC program may include Information Assurance and Communications Security (COMSEC). The OPSEC program shall be in accordance with National Security Presidential Memorandum (NSPM) 28, and at a minimum shall include:

1) Assignment of responsibility for OPSEC direction and implementation.

2) Issuance of procedures and planning guidance for the use of OPSEC techniques to identify vulnerabilities and apply applicable countermeasures.

3) Establishment of OPSEC education and awareness training.

4) Provisions for management, annual review, and evaluation of OPSEC programs.

5) Flow down of OPSEC requirements to subcontractors when applicable.

While performing aboard Government sites, the contractor shall: comply with all OPSEC instructions and policies; include OPSEC as part of its ongoing security awareness program and take all required Agency training; Be responsive to the Supporting OPSEC Manager on a non-interference basis; and Protect sensitive unclassified information and activities, which could compromise classified information or operations, or degrade the planning and execution of operations performed by the Requiring Organization and contractor in support of the mission.

10.3 Electronic Spillage

Electronic Spillage (ES) is defined as a situation where information of higher classification than a system is authorized to process is introduced into that system, intentionally or otherwise. If a Contractor is determined to be responsible for an ES, all direct and indirect costs incurred by the Government for ES remediation will be charged to the Contractor.

Requirements See Gen Info

Additional Regulation or Supplemental Clauses Incorporated by Full Text

C-202-H001 ADDITIONAL DEFINITIONS--BASIC (Oct 2018)

(a) Department means the Department of the Navy.

(b) Commander, Naval Sea Systems Command means the Commander of the Naval Sea Systems Command of the Department of the Navy or his duly appointed successor.

(c) References to The Federal Acquisition Regulation (FAR) All references to the FAR in this contract shall be deemed to also reference the appropriate sections of the Defense FAR Supplement (DFARS), unless clearly indicated otherwise.

(d) National Stock Numbers Whenever the term Federal Item Identification Number and its acronym FIIN or the term Federal Stock Number and its acronym FSN appear in the contract, order or their cited specifications and standards, the terms and acronyms shall be interpreted as National Item Identification Number (NIIN) and National Stock Number (NSN) respectively which shall be defined as follows:

(1) . The number assigned to each approved Item Identification under the National Item Identification Number (NIIN) Federal Cataloging Program. It consists of nine numeric characters, the first two of which are the National Codification Bureau (NCB) Code. The remaining positions consist of a seven digit nonsignificant number.

(2) . The National Stock Number (NSN) for an item of supply consists of the applicable National Stock Number (NSN) four-position Federal Supply Class (FSC) plus the applicable nine-position NIIN assigned to the item of supply.

(Endof Text)

C-204-H001 USE OF NAVY SUPPORT CONTRACTORS FOR OFFICIAL CONTRACT FILES (Oct 2018)

(a) NAVSEA may use a file room management support contractor, hereinafter referred to as "the support contractor", to manage its file room, in which all official contract files, including the official file supporting this procurement, are retained. These official files may contain information that is considered a trade secret, proprietary, business sensitive or otherwise protected pursuant to law or regulation, hereinafter referred to as "protected information". File room management services consist of any of the following: secretarial or clerical support; data entry; document reproduction, scanning, imaging, or destruction; operation, management, or maintenance of paper-based or electronic mail rooms, file rooms, or libraries; and supervision in connection with functions listed herein.

(b) The cognizant Contracting Officer will ensure that any NAVSEA contract under which these file room management services are acquired will contain a requirement that:

(1) The support contractor not disclose any information;

(2) Individual employees are to be instructed by the support contractor regarding the sensitivity of the official contract files;

(3) The support contractor performing these services be barred from providing any other supplies and/or services, or competing to do so, to NAVSEA for the period of performance of its contract and for an additional three years thereafter unless otherwise provided by law or regulation; and,

(4) In addition to any other rights the contractor may have, it is a third party beneficiary who has the right of direct action against the support contractor, or any person to whom the support contractor has released or disclosed protected information, for the unauthorized duplication, release, or disclosure of such protected information.

(c) Execution of this contract by the contractor is considered consent to NAVSEA's permitting access to any information, irrespective of restrictive markings or the nature of the information submitted, by its file room management support contractor for the limited purpose of executing its file room support contract responsibilities.

(d) NAVSEA may, without further notice, enter into contracts with other contractors for these services. Contractors should enter into separate non-disclosure agreements with the file room contractor. Contact the Procuring Contracting Officer for contractor specifics. However, any such agreement will not be considered a prerequisite before information submitted is stored in the file room or otherwise encumber the government.

(End of Text)

C-204-H002 IMPLEMENTATION OF ENHANCED SECURITY CONTROLS ON SELECT

DEFENSE INDUSTRIAL BASE PARTNER NETWORKS

(Sep 2024)

1. System Security Plan and Plans of Action and Milestones (SSP/POAM) 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 (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 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.

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. 2) (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.