CSS N0016726Q0016 MS Blades.pdf

This is a combined synopsis/solicitation for commercial items prepared in accordance with Federal Acquisition Regulation (FAR) Part 12, as supplemented with additional information included in this notice. This announcement constitutes the only solicitation that Naval Surface Warfare Center Carderock Division (NSWCCD) intends to issue and is a Request for Quotes (RFQ) for the following Supplies and/or Services.

Naval Surface Warfare, Carderock Division (NSWCCD), has a procurement request for Concurrent MS Processor Blade Cards on a Brand Name basis.

The provisions and clauses included and/or incorporated in this solicitation document are those in effect through the Federal Acquisition Circular. This RFQ incorporates all provisions and clauses in effect through Federal Acquisition Circular FAC 2025-06 effective 10/01/2025 located on https://www.acquisition.gov/?q=browsefar and the Defense Federal Acquisition Regulation Supplement (DFARS) DPN 20251001 effective 10/1/2025 located at https://www.acq.osd.mil/dpap/dars/change_notices.html. SEE ATTACHED SOLICITATION FOR CLAUSES AND PROVISIONS. The NAICS code is 334418 and the associated PSC code is 7B22. This procurement IS being set-aside for small business.

Interested parties may identify their interest in this requirement by submitting a quote and/or capabilities statement no later than 10:00 AM on 08 September 2026. It is anticipated that one firm-fixed price purchase order will be issued in response to this RFQ.

All responses shall include the following.

1. Quote on company’s Letterhead

2. Pricing

3. Cage Code

4. FOB Destination

5. Point of contact

6. GSA contract number (if applicable)

7. Business Size

8. Quote should be rounded off to the nearest whole dollar

Each response must clearly indicate the capability of the quoter to meet all specifications and requirements. Please also include Lead Time for product delivery.

Responses to this notice are due on or before 10:00 AM on 08 September 2026, Eastern Standard Time (EST) to kylie.cox3.civ@us.navy.mil.

Point of Contact for this notice is Kylie Cox, 227-224-3139, kylie.cox3.civ@us.navy.mil https://www.acquisition.gov/?q=browsefar https://www.acq.osd.mil/dpap/dars/change_notices.html mailto:kylie.cox3.civ@us.navy.mil mailto:kylie.cox3.civ@us.navy.mil

Solicitation/Contract Form Continuation

Concurrent MS Processor Blade Cards

N0016726Q0016

Continuation of Supplies or Services and Prices/Costs

Additional Information/Notes

Item Supplies/Service Quantity Unit Unit Price Amount

2.5" SATA Drive mounting kit (no drive)

Manufacturer's Part Number: AD 110/001-71 Internal Number: 1023778510 Pricing Arrangement: Firm Fixed Price

34 Each

CPCI RTM for PP B76/msd & PP B84/msd. Without J4.

Internal Number: 1023778512 Manufacturer's Part Number: AD PP5/013-00 Pricing Arrangement: Firm Fixed Price

17 Each

6-core 2.7 GHz (4.4 GHz) (45 W) Intel(r) Xeon(r) Processor E- 2176M. 32 Gbytes DRAM, VITA 42.0 XMC Connectors. Rear I/O:

J3=2x GigE (with Magnetics). J4= Without J4, J5=1x USB 2.0, 2x SATA, HD Digital Audio.

Internal Number: 1023778514 Manufacturer's Part Number: PP B76/042-20-020 Pricing Arrangement: Firm Fixed Price

34 Each

0004 Shipping

Pricing Arrangement: Firm Fixed Price

1 Job

Continuation of Description

REQUIREMENT

MS Processor Blade Cards

LINE

ITEM

DESCRIPTION PART NUMBER BRAND QUANTITY

2.5" SATA Drive mounting kit (no drive)

AD 110/001-71

Concurrent Technologies Inc.

CPCI RTM for use w/ PPB76 SBC & PPB84/msd. Without J4.

AD PP5/013-00

Concurrent Technologies

Inc.

6U CPCI SBC w/ 6-core Intel XEON e-2176M; 32GB

DRAM

PP B76/042-20-

Concurrent Technologies Inc.

Early and/or partial deliveries are acceptable.

Requirements Concurrent MS Processor Blade Cards

Continuation of Packaging and Marking

Continuation of Inspection and Acceptance

Overall Contract Inspection/Acceptance Locations

Authorized Accepting Official

Acceptance Other Instructions: Inform TPOC upon delivery.

DoDAAC: N00167 CountryCode: USA

NSWC CARDEROCK

CARDEROCK DIVISION, 9500 MACARTHUR

BOULEVARD

BETHESDA, MD 20817-5700

UNITED STATES

TBD, TBD

Email: TBD Telephone: TBD

Inspection Location

Inspection Destination Instructions: Inform TPOC upon delivery.

DoDAAC: N30492 CountryCode: USA

NAVAL SURFACE WARFARE CENTER

CARDEROCK DIV DET PUGET SOUND, 7131 SEALION

SILVERDALE, WA 98315

UNITED STATES

TBD, TBD

Email: TBD Telephone: TBD

Authorized Accepting Official

Acceptance Other Instructions: Inform TPOC upon delivery.

DoDAAC: N00167 CountryCode: USA

NSWC CARDEROCK

CARDEROCK DIVISION, 9500 MACARTHUR

BOULEVARD

BETHESDA, MD 20817-5700

UNITED STATES

TBD, TBD

Email: TBD Telephone: TBD

Inspection Location

Inspection Destination Instructions: Inform TPOC upon delivery.

DoDAAC: N30492 CountryCode: USA

NAVAL SURFACE WARFARE CENTER

CARDEROCK DIV DET PUGET SOUND, 7131 SEALION

SILVERDALE, WA 98315

UNITED STATES

TBD, TBD

Email: TBD Telephone: TBD

Authorized Accepting Official

Acceptance Other Instructions: Inform TPOC upon delivery.

DoDAAC: N00167 CountryCode: USA

NSWC CARDEROCK

CARDEROCK DIVISION, 9500 MACARTHUR

BOULEVARD

BETHESDA, MD 20817-5700

UNITED STATES

TBD, TBD

Email: TBD Telephone: TBD

Inspection Location

Inspection Destination Instructions: Inform TPOC upon delivery.

DoDAAC: N30492 CountryCode: USA

NAVAL SURFACE WARFARE CENTER

CARDEROCK DIV DET PUGET SOUND, 7131 SEALION

SILVERDALE, WA 98315

UNITED STATES

TBD, TBD

Email: TBD Telephone: TBD

Authorized Accepting Official Inspection Location

Acceptance Other Instructions: Inform TPOC upon delivery.

DoDAAC: N00167 CountryCode: USA

NSWC CARDEROCK

CARDEROCK DIVISION, 9500 MACARTHUR

BOULEVARD

BETHESDA, MD 20817-5700

UNITED STATES

TBD, TBD

Email: TBD Telephone: TBD

Inspection Destination Instructions: Inform TPOC upon delivery.

DoDAAC: N30492 CountryCode: USA

NAVAL SURFACE WARFARE CENTER

CARDEROCK DIV DET PUGET SOUND, 7131 SEALION

SILVERDALE, WA 98315

UNITED STATES

TBD, TBD

Email: TBD Telephone: TBD

Continuation of Deliveries or Performance

Overall Contract Delivery Period

Contractor Destination

Line Item Delivery Schedule Quantity Address and POC

Delivery Requested By Delivery Date 30 Sep 2027

34 Each Ship To DoDAAC: N30492 CountryCode: USA

NAVAL SURFACE WARFARE CENTER

CARDEROCK DIV DET PUGET SOUND, 7131 SEALION ROAD

SILVERDALE, WA 98315

UNITED STATES

TBD, TBD

Email: TBD Telephone: TBD

Delivery Requested By Delivery Date 30 Sep 2027

17 Each Ship To DoDAAC: N30492 CountryCode: USA

NAVAL SURFACE WARFARE CENTER

CARDEROCK DIV DET PUGET SOUND, 7131 SEALION ROAD

SILVERDALE, WA 98315

UNITED STATES

TBD, TBD

Email: TBD Telephone: TBD

Delivery Requested By Delivery Date 30 Sep 2027

34 Each Ship To DoDAAC: N30492 CountryCode: USA

NAVAL SURFACE WARFARE CENTER

CARDEROCK DIV DET PUGET SOUND, 7131 SEALION ROAD

SILVERDALE, WA 98315

UNITED STATES

TBD, TBD

Email: TBD Telephone: TBD

Delivery Requested By Delivery Date 30 Sep 2027

1 Job Ship To DoDAAC: N30492 CountryCode: USA

NAVAL SURFACE WARFARE CENTER

CARDEROCK DIV DET PUGET SOUND, 7131 SEALION ROAD

SILVERDALE, WA 98315

UNITED STATES

TBD, TBD

Email: TBD Telephone: TBD

Continuation of Accounting and Appropriation Data

Contract Clauses

FAR Clauses Incorporated by Reference

Number Title Effective Date

Alternate/ Deviation

Variation Effective Date

52.226-8 Encouraging Contractor Policies to Ban Text Messaging While Driving. May 2024 52.233-3 Protest after Award. (Deviation 2026-O0038) Feb 2026 52.233-4 Applicable Law for Breach of Contract Claim. (Deviation 2026-O0038) Feb 2026

52.212-4 Terms and Conditions-Commercial Products and Commercial Services. (Deviation 2026- O0038)

Feb 2026

52.204-13 System for Award Management-Maintenance. (Deviation 2026-O0038) Feb 2026 52.203-19 Prohibition on Requiring Certain Internal Confidentiality Agreements or Statements. Jan 2017 52.232-33 Payment by Electronic Funds Transfer-System for Award Management. Oct 2018 52.232-40 Providing Accelerated Payments to Small Business Subcontractors. Mar 2023

DFARS Clauses Incorporated by Reference

Number Title Effective Date

Alternate/ Deviation

Variation Effective Date

252.204-7012 Safeguarding Covered Defense Information and Cyber Incident Reporting. May 2024 252.203-7000 Requirements Relating to Compensation of Former DoD Officials. Sep 2011 252.203-7002 Requirement to Inform Employees of Whistleblower Rights. Dec 2022 252.225-7056 Prohibition Regarding Business Operations with the Maduro Regime. Jan 2023 252.225-7060 Prohibition on Certain Procurements from the Xinjiang Uyghur Autonomous Region. Jun 2023 252.232-7003 Electronic Submission of Payment Requests and Receiving Reports. Dec 2018 252.232-7010 Levies on Contract Payments. Dec 2006 252.244-7000 Subcontracts for Commercial Products or Commercial Services. Nov 2023 252.247-7023 Transportation of Supplies by Sea. Oct 2024

DFARS Clauses Incorporated by Full Text

252.232-7006 Wide Area WorkFlow Payment Instructions. (Tailored) (Jan 2023)

WIDE AREA WORKFLOW PAYMENT INSTRUCTIONS (JAN 2023)

(a) As used in this clause- Definitions.

"Department of Defense Activity Address Code (DoDAAC)" is a six position code that uniquely identifies a unit, activity, or organization.

"Document type" means the type of payment request or receiving report available for creation in Wide Area WorkFlow (WAWF).

"Local processing office (LPO)" is the office responsible for payment certification when payment certification is done external to the entitlement system.

"Payment request" and "receiving report" are defined in the clause at 252.232-7003, Electronic Submission of Payment Requests and Receiving Reports.

(b) The WAWF system provides the method to electronically process vendor payment requests and receiving reports, as Electronic invoicing.

authorized by Defense Federal Acquisition Regulation Supplement (DFARS) 252.232-7003, Electronic Submission of Payment Requests and Receiving Reports.

(c) To access WAWF, the Contractor shall- WAWF access.

(1) Have a designated electronic business point of contact in the System for Award Management at https://www.sam.gov; and

(2) Be registered to use WAWF at https://wawf.eb.mil/ following the step-by-step procedures for self-registration available at this web site.

(d) The Contractor should follow the training instructions of the WAWF Web-Based Training Course and use the Practice WAWF training.

Training Site before submitting payment requests through WAWF. Both can be accessed by selecting the "Web Based Training" link on the WAWF home page at https://wawf.eb.mil/

(e) Document submissions may be via web entry, Electronic Data Interchange, or File Transfer WAWF methods of document submission.

Protocol.

(f) The Contractor shall use the following information when submitting payment requests and receiving reports in WAWF payment instructions.

WAWF for this contract or task or delivery order:

(1) The Contractor shall submit payment requests using the following document type(s): Document type.

(i) For cost-type line items, including labor-hour or time-and-materials, submit a cost voucher.

(ii) For fixed price line items-

(A) That require shipment of a deliverable, submit the invoice and receiving report specified by the Contracting Officer.

Invoice and Receiving Report (COMBO)

(B) For services that do not require shipment of a deliverable, submit either the Invoice 2in1, which meets the requirements for the invoice and receiving report, or the applicable invoice and receiving report, as specified by the Contracting Officer.

Invoice and Receiving Report (COMBO)

(iii) For customary progress payments based on costs incurred, submit a progress payment request.

(iv) For performance based payments, submit a performance based payment request.

(v) For commercial financing, submit a commercial financing request.

(2) ) Fast Pay requests are only permitted when Federal Acquisition Regulation (FAR) 52.213-1 is included in the contract.

[Note: The Contractor may use a WAWF "combo" document type to create some combinations of invoice and receiving report in one step.]

(3) The Contractor shall use the information in the Routing Data Table below only to fill in applicable fields in WAWF Document routing.

when creating payment requests and receiving reports in the system.

Routing Data Table*

Field Name in WAWF Data to be entered in WAWF

Pay Official DoDAAC N62825

Issue By DoDAAC N00167

Admin DoDAAC N00167

Inspect By DoDAAC N30492

Ship To Code N30492

Ship From Code ____

Mark For Code ____

Service Approver (DoDAAC) N00167

Service Acceptor (DoDAAC) N00167

Accept at Other DoDAAC N00167

LPO DoDAAC ____

DCAA Auditor DoDAAC ____

Other DoDAAC(s) ____

(4) The Contractor shall ensure a payment request includes documentation appropriate to the type of payment request in Payment request.

accordance with the payment clause, contract financing clause, or Federal Acquisition Regulation 52.216-7, Allowable Cost and Payment, as applicable.

(5) The Contractor shall ensure a receiving report meets the requirements of DFARS Appendix F. Receiving report.

(g) WAWF point of contact.

(1) The Contractor may obtain clarification regarding invoicing in WAWF from the following contracting activity's WAWF point of contact.

usn.ncr.sea-01.mbx.wawf-hq-functional-mail-box@us.navy.mil

(2) Contact the WAWF helpdesk at 866-618-5988, if assistance is needed.

(End of clause)

N0016726Q0016 mailto:usn.ncr.sea-01.mbx.wawf-hq-functional-mail-box@us.navy.mil

Addendum to 52.212-4, Contract Terms and Conditions - Commercial Products and Commercial Services

Contract Terms and Conditions Required To Implement Statutes or Executive Orders — Commercial Products and Commercial Services

Addendum to Contract Clauses

Contract Clauses

FAR Clauses Incorporated by Reference

Number Title Effective Date

Alternate/ Deviation

Variation Effective Date

52.222-90 Addressing DEI Discrimination by Federal Contractors. (Deviation 2026-O0038) Apr 2026 52.232-39 Unenforceability of Unauthorized Obligations. Jun 2013 52.247-34 F.o.b. Destination. Jan 1991 52.249-1 Termination for Convenience of the Government (Fixed-Price) (Short Form). Apr 1984

DFARS Clauses Incorporated by Reference

Number Title Effective Date

Alternate/ Deviation

Variation Effective Date

252.204-7018 Prohibition on the Acquisition of Covered Defense Telecommunications Equipment or Services.

Jan 2023

252.237-7010 Prohibition on Interrogation of Detainees by Contractor Personnel. Jan 2023 252.204-7022 Expediting Contract Closeout. May 2021 252.225-7013 Duty-Free Entry. Aug 2025 252.239-7010 Cloud Computing Services. Jan 2023 252.225-7012 Preference for Certain Domestic Commodities. Apr 2022

DFARS Clauses Incorporated by Full Text

252.211-7003 Item Unique Identification and Valuation. (Jan 2023)

ITEM UNIQUE IDENTIFICATION AND VALUATION (JAN 2023)

(a) . As used in this clause- Definitions

"Automatic identification device" means a device, such as a reader or interrogator, used to retrieve data encoded on machine-readable media.

"Concatenated unique item identifier" means-

(1) For items that are serialized within the enterprise identifier, the linking together of the unique identifier data elements in order of the issuing agency code, enterprise identifier, and unique serial number within the enterprise identifier; or

(2) For items that are serialized within the original part, lot, or batch number, the linking together of the unique identifier data elements in order of the issuing agency code; enterprise identifier; original part, lot, or batch number; and serial number within the original part, lot, or batch number.

"Data matrix" means a two-dimensional matrix symbology, which is made up of square or, in some cases, round modules arranged within a perimeter finder pattern and uses the Error Checking and Correction 200 (ECC200) specification found within International Standards Organization (ISO)/International Electrotechnical Commission (IEC) 16022.

"Data qualifier" means a specified character (or string of characters) that immediately precedes a data field that defines the general category or intended use of the data that follows.

"DoD recognized unique identification equivalent" means a unique identification method that is in commercial use and has been recognized by DoD. All DoD recognized unique identification equivalents are listed at . https://www.acq.osd.mil/asda/dpc/ce/ds/unique-id.html

"DoD item unique identification" means a system of marking items delivered to DoD with unique item identifiers that have machine-readable data elements to distinguish an item from all other like and unlike items. For items that are serialized within the enterprise identifier, the unique item identifier shall include the data elements of the enterprise identifier and a unique serial number. For items that are serialized within the part, lot, or batch number within the enterprise identifier, the unique item identifier shall include the data elements of the enterprise identifier; the original part, lot, or batch number; and the serial number.

" Enterprise " means the entity (e.g., a manufacturer or vendor) responsible for assigning unique item identifiers to items.

" Enterprise identifier" means a code that is uniquely assigned to an enterprise by an issuing agency.

"Government's unit acquisition cost" means-

(1) For fixed-price type line, subline, or exhibit line items, the unit price identified in the contract at the time of delivery;

(2) For cost-type or undefinitized line, subline, or exhibit line items, the Contractor's estimated fully burdened unit cost to the Government at the time of delivery; and

(3) For items produced under a time-and-materials contract, the Contractor's estimated fully burdened unit cost to the Government at the time of delivery.

"Issuing agency" means an organization responsible for assigning a globally unique identifier to an enterprise, as indicated in the Register of Issuing Agency Codes for ISO/IEC 15459, located at http://www.aimglobal.org/?Reg_Authority15459.

"Issuing agency code" means a code that designates the registration (or controlling) authority for the enterprise identifier.

"Item" means a single hardware article or a single unit formed by a grouping of subassemblies, components, or constituent parts.

" Lot or batch number" means an identifying number assigned by the enterprise to a designated group of items, usually referred to as either a lot or a batch, all of which were manufactured under identical conditions.

"Machine-readable" means an automatic identification technology media, such as bar codes, contact memory buttons, radio frequency identification, or optical memory cards.

"Original part number" means a combination of numbers or letters assigned by the enterprise at item creation to a class of items with the same form, fit, function, and interface.

"Parent item" means the item assembly, intermediate component, or subassembly that has an embedded item with a unique item identifier or DoD recognized unique identification equivalent.

"Serial number within the enterprise identifier" means a combination of numbers, letters, or symbols assigned by the enterprise to an item that provides for the differentiation of that item from any other like and unlike item and is never used again within the enterprise.

"Serial number within the part, lot, or batch number" means a combination of numbers or letters assigned by the enterprise to an item that provides for the differentiation of that item from any other like item within a part, lot, or batch number assignment.

"Serialization within the enterprise identifier" means each item produced is assigned a serial number that is unique among all the tangible items produced by the enterprise and is never used again. The enterprise is responsible for ensuring unique serialization within the enterprise identifier.

"Serialization within the part, lot, or batch number" means each item of a particular part, lot, or batch number is assigned a unique serial number within that part, lot, or batch number assignment. The enterprise is responsible for ensuring unique serialization within the part, lot, or batch number within the enterprise identifier.

"Type designation" means a combination of letters and numerals assigned by the Government to a major end item, assembly or subassembly, as appropriate, to provide a convenient means of differentiating between items having the same basic name and to indicate modifications and changes thereto.

"Unique item identifier" means a set of data elements marked on items that is globally unique and unambiguous. The term includes a concatenated unique item identifier or a DoD recognized unique identification equivalent.

"Unique item identifier type" means a designator to indicate which method of uniquely identifying a part has been used. The current list of accepted unique item identifier types is maintained at .https://www.acq.osd.mil/asda/dpc/ce/ds/unique-id.html

(b) The Contractor shall deliver all items under a contract line, subline, or exhibit line item.

(c) Unique item identifier.

(1) The Contractor shall provide a unique item identifier for the following:

(i) Delivered items for which the Government's unit acquisition cost is $5,000 or more, except for the following line items:

Contract Line, Subline, or

Exhibit Line Item Number Item Description

(ii) Items for which the Government's unit acquisition cost is less than $5,000 that are identified in the Schedule or the following table:

Contract Line, Subline, or

Exhibit Line Item Number Item Description

(If items are identified in the Schedule, insert "See Schedule in this table.)

(iii) Subassemblies, components, and parts embedded within delivered items, items with warranty requirements, DoD serially managed reparables and DoD serially managed nonreparables as specified in Attachment Number .____

(iv) Any item of special tooling or special test equipment as defined in FAR 2.101 that have been designated for preservation and storage for a Major Defense Acquisition Program as specified in Attachment Number .____

(v) Any item not included in (i), (ii), (iii), or (iv) for which the contractor creates and marks a unique item identifier for traceability.

(2) The unique item identifier assignment and its component data element combination shall not be duplicated on any other item marked or registered in the DoD Item Unique Identification Registry by the contractor.

(3) The unique item identifier component data elements shall be marked on an item using two dimensional data matrix symbology that complies with ISO/IEC International Standard 16022, Information technology - International symbology specification - Data matrix; ECC200 data matrix specification.

(4) The Contractor shall ensure that- Data syntax and semantics of unique item identifiers.

(i) The data elements (except issuing agency code) of the unique item identifier are encoded within the data matrix symbol that is marked on the item using one of the following three types of data qualifiers, as determined by the Contractor:

(A) Application Identifiers (AIs) (Format Indicator 05 of ISO/IEC International Standard 15434), in accordance with ISO/IEC International Standard 15418, Information Technology - EAN/UCC Application Identifiers and Fact Data Identifiers and Maintenance and ANSI MH

10.8.2 Data Identifier and Application Identifier Standard.

(B) Data Identifiers (DIs) (Format Indicator 06 of ISO/IEC International Standard 15434), in accordance with ISO/IEC International Standard 15418, Information Technology - EAN/UCC Application Identifiers and Fact Data Identifiers and Maintenance and ANSI MH

10.8.2 Data Identifier and Application Identifier Standard.

(C) Text Element Identifiers (TEIs) (Format Indicator 12 of ISO/IEC International Standard 15434), in accordance with the Air Transport Association Common Support Data Dictionary; and

(ii) The encoded data elements of the unique item identifier conform to the transfer structure, syntax, and coding of messages and data formats specified for Format Indicators 05, 06, and 12 in ISO/IEC International Standard 15434, Information Technology - Transfer Syntax for High Capacity Automatic Data Capture Media.

(5) . Unique item identifier

(i) The Contractor shall-

(A) Determine whether to-

Serialize within the enterprise identifier; (1)

Serialize within the part, lot, or batch number; or (2)

Use a DoD recognized unique identification equivalent (e.g. Vehicle Identification Number); and (3)

(B) Place the data elements of the unique item identifier (enterprise identifier; serial number; DoD recognized unique identification equivalent; and for serialization within the part, lot, or batch number only: original part, lot, or batch number) on items requiring marking by paragraph (c)(1) of this clause, based on the criteria provided in MIL-STD-130, Identification Marking of U.S. Military Property, latest version;

(C) Label shipments, storage containers and packages that contain uniquely identified items in accordance with the requirements of MIL-STD-129, Military Marking for Shipment and Storage, latest version; and

(D) Verify that the marks on items and labels on shipments, storage containers, and packages are machine readable and conform to the applicable standards. The contractor shall use an automatic identification technology device for this verification that has been programmed to the requirements of Appendix A, MIL-STD-130, latest version.

(ii) The issuing agency code-

(A) Shall not be placed on the item; and

(B) Shall be derived from the data qualifier for the enterprise identifier.

(d) For each item that requires item unique identification under paragraph (c)(1)(i), (ii), or (iv) of this clause or when item unique identification is provided under paragraph (c)(1)(v), in addition to the information provided as part of the Material Inspection and Receiving Report specified elsewhere in this contract, the Contractor shall report at the time of delivery, as part of the Material Inspection and Receiving Report, the following information:

(1) Unique item identifier.

(2) Unique item identifier type.

(3) Issuing agency code (if concatenated unique item identifier is used).

(4) Enterprise identifier (if concatenated unique item identifier is used).

(5) Original part number (if there is serialization within the original part number).

(6) Lot or batch number (if there is serialization within the lot or batch number).

(7) Current part number (optional and only if not the same as the original part number).

(8) Current part number effective date (optional and only if current part number is used).

(9) Serial number (if concatenated unique item identifier is used).

(10) Government's unit acquisition cost.

(11) Unit of measure.

(12) Type designation of the item as specified in the contract schedule, if any.

(13) Whether the item is an item of Special Tooling or Special Test Equipment.

(14) Whether the item is covered by a warranty.

(e) For embedded subassemblies, components, and parts that require DoD item unique identification under paragraph (c)(1)(iii) of this clause or when item unique identification is provided under paragraph (c)(1)(v), the Contractor shall report as part of the Material Inspection and Receiving Report specified elsewhere in this contract, the following information:

(1) Unique item identifier of the parent item under paragraph (c)(1) of this clause that contains the embedded subassembly, component, or part.

(2) Unique item identifier of the embedded subassembly, component, or part.

(3) Unique item identifier type.**

(4) Issuing agency code (if concatenated unique item identifier is used).**

(5) Enterprise identifier (if concatenated unique item identifier is used).**

(6) Original part number (if there is serialization within the original part number).**

(7) Lot or batch number (if there is serialization within the lot or batch number).**

(8) Current part number (optional and only if not the same as the original part number).**

(9) Current part number effective date (optional and only if current part number is used).**

(10) Serial number (if concatenated unique item identifier is used).**

(11) Description.

** Once per item.

(f) The Contractor shall submit the information required by paragraphs (d) and (e) of this clause as follows:

(1) End items shall be reported using the receiving report capability in Wide Area WorkFlow (WAWF) in accordance with the clause at 252.232-7003. If WAWF is not required by this contract, and the contractor is not using WAWF, follow the procedures at http://dodprocurementtoolbox.com/site/uidregistry/.

(2) Embedded items shall be reported by one of the following methods-

(i) Use of the embedded items capability in WAWF;

(ii) Direct data submission to the IUID Registry following the procedures and formats at http://dodprocurementtoolbox.com/site /uidregistry/; or

(iii) Via WAWF as a deliverable attachment for exhibit line item number (fill in) , Unique Item Identifier Report for Embedded ____ Items, Contract Data Requirements List, DD Form 1423.

(g) . If the Contractor acquires by subcontract, any item(s) for which item unique identification is required in accordance with Subcontracts paragraph (c)(1) of this clause, the Contractor shall include this clause, including this paragraph (g), in the applicable subcontract(s), including subcontracts for commercial products or commercial services.

(End of clause)

252.204-7021 Contractor Compliance with the Cybersecurity Maturity Model Certification Level Requirements. (Tailored)

(Nov 2025)

CONTRACTOR COMPLIANCE WITH THE CYBERSECURITY MATURITY MODEL CERTIFICATION LEVEL REQUIREMENTS (NOV 2025)

(a) . As used in this clause- Definitions

"Controlled unclassified information" means information the Government creates or possesses, or information an entity creates or possesses for or on behalf of the Government, that a law, regulation, or Governmentwide policy requires or permits an agency to handle using safeguarding or dissemination controls (32 CFR 2002.4(h)).

"Current" means-

(1) With regard to Conditional Cybersecurity Maturity Model Certification (CMMC) Status-

(i) Not older than 180 days for Conditional Level 2 (Self) assessments and Conditional Level 2 (certified third-party assessment organization (C3PAO)) assessments, with-

(A) No changes in compliance with the requirements at 32 CFR part 170 since the Conditional CMMC Status date (see 32 CFR

170.16 and 170.17); and

(B) A corresponding affirmation of continuous compliance by an affirming official (see 32 CFR 170.4); and

(ii) Not older than 180 days for Conditional Level 3 (Defense Industrial Base Cybersecurity Assessment Center (DIBCAC)) assessments, with-

(A) No changes in compliance with the requirements at 32 CFR part 170 since the Conditional CMMC Status date (see 32 CFR 170.18); and

(B) A corresponding affirmation of continuous compliance by an affirming official;

(2) With regard to Final CMMC Status-

(i) Not older than 1 year for Final Level 1 (Self), with-

(A) No changes in compliance with the requirements at 32 CFR part 170 since the Final CMMC Status date (see 32 CFR 170.15);

and

(B) A corresponding affirmation of continuous compliance, not older than 1 year, by an affirming official;

(ii) Not older than 3 years for Final Level 2 (Self) assessments and Final Level 2 (C3PAO) assessments, with-

(A) No changes in compliance with the requirements at 32 CFR part 170 since the Final CMMC Status date (see 32 CFR 170.16 and 170.17); and

(B) A corresponding affirmation of continuous compliance, not older than 1 year, by an affirming official; and

(iii) Not older than 3 years for Final Level 3 (DIBCAC) assessments, with-

(A) No changes in compliance with the requirements at 32 CFR part 170 since the Final CMMC Status date (see 32 CFR 170.18);

and

(B) A corresponding affirmation of continuous compliance, not older than 1 year, by an affirming official; and

(3) With regard to affirmation of continuous compliance (32 CFR 170.22), not older than 1 year with no changes in compliance with the requirements at 32 CFR part 170.

"Cybersecurity Maturity Model Certification (CMMC) status" means the result of meeting or exceeding the minimum required score for the corresponding assessment. The potential statuses are as follows:

(1) Final Level 1 (Self).

(2) Conditional Level 2 (Self).

(3) Final Level 2 (Self).

(4) Conditional Level 2 (C3PAO).

(5) Final Level 2 (C3PAO).

(6) Conditional Level 3 (DIBCAC).

(7) Final Level 3 (DIBCAC).

"Cybersecurity Maturity Model Certification unique identifier (CMMC UID)" means 10 alpha-numeric characters assigned to each CMMC assessment and reflected in the Supplier Performance Risk System (SPRS) for each contractor information system.

"Federal contract information (FCI)" means information, not intended for public release, that is provided by or generated for the Government under a contract to develop or deliver a product or service to the Government. It does not include information provided by the Government to the public, such as on public websites, or simple transactional information, such as information necessary to process payments.

"Plan of action and milestones" means a document that identifies tasks to be accomplished. It details resources required to accomplish the elements of the plan, any milestones in meeting the tasks, and scheduled completion dates for the milestones, as defined in National Institute of Standards and Technology Special Publication 800-115 (32 CFR 170.21).

(b) . The Cybersecurity Maturity Model Certification (CMMC) is a framework for assessing a contractor's compliance with Framework applicable information security protections (see 32 CFR part 170).

(c) . The CMMC assessments will not duplicate efforts from any other comparable DoD assessment, except for rare circumstances Duplication when a reassessment may be necessary, for example, when there are indications of issues with cybersecurity and/or compliance with CMMC requirements.

(d) . The Contractor shall- Requirements

(1)(i) Have and maintain for the duration of the contract a current CMMC status at the following CMMC level, or higher: CMMC Level 1 for all information systems used in performance of the contract, task order, or delivery order that process, store, or transmit FCI or CUI; and(Self)

(ii) Consult 32 CFR 170.23 related to the flowdown of the CMMC requirements, and flow down the correct CMMC level to subcontracts and other contractual instruments;

(2) Only process, store, or transmit FCI or CUI on contractor information systems that have a CMMC status at the CMMC level required in paragraph (d)(1) of this clause, or higher;

(3) Complete on an annual basis, and maintain as current, an affirmation, by the affirming official (see 32 CFR 170.4), of continuous compliance with the requirements associated with the CMMC level required in paragraph (d)(1) of this clause in the Supplier Performance Risk System (SPRS) ( ) for each CMMC UID applicable to each of the contractor information systems that process, store, or transmit FCI https://piee.eb.mil or CUI and that are used in performance of the contract;

(4) Ensure all subcontractors and suppliers complete prior to subcontract award, and maintain on an annual basis, an affirmation, by the affirming official (see 32 CFR 170.4), of continuous compliance with the requirements associated with the CMMC level required for the subcontract or other contractual instrument for each of the subcontractor information systems that process, store, or transmit FCI or CUI and that are used in performance of the subcontract; and

(5) If the Contractor has a CMMC Status of Conditional, successfully close out a valid plan of action and milestones (32 CFR 170.21) to achieve a CMMC Status of Final.

(e) . The Contractor shall- Reporting

(1) Submit to the Contracting Officer-

(i) The CMMC UID(s) issued by SPRS for contractor information systems that will process, store, or transmit FCI or CUI during performance of the contract; and

(ii) Any changes in the CMMC UIDs generated in SPRS throughout the life of the contract, task order, or delivery order, if applicable;

(2) Enter into SPRS the results of a current self-assessment for each CMMC UID, not covered by a C3PAO assessment or DIBCAC assessment, applicable to each of the contractor information systems that process, store, or transmit FCI or CUI and that are used in performance of the contract; and

(3) Complete in SPRS on an annual basis and maintain as current an affirmation of continuous compliance by the affirming official (see 32 CFR 170.4) for each self-assessment, C3PAO assessment, or DIBCAC assessment required under the contract in SPRS.

(f) . The Contractor shall- Subcontracts

(1) Insert the substance of this clause, including this paragraph (f) and excluding paragraph (e)(1), in subcontracts and other contractual instruments, including those for the acquisition of commercial products or commercial services, excluding commercially available off-the-shelf items, if the subcontract or other contractual instrument will contain a requirement to process, store, or transmit FCI or CUI; and

(2) Prior to awarding a subcontract or other contractual instrument, ensure that the subcontractor has a current CMMC certificate or current CMMC status at the CMMC level that is appropriate for the information that is being flowed down to the subcontractor based on the requirements at

32 CFR 170.23.

(End of clause)

Additional Regulation or Supplemental Clauses Incorporated by Full Text

L-204-H003 NOTIFICATION OF USE OF NAVY SUPPORT CONTRACTORS FOR OFFICIAL

CONTRACT FILES (NAVSEA) (APR 2019)

(Apr 2019)

(a) NAVSEA may use a contractor to manage official contract files here in after referred to as "the support contractor", including the official file supporting this procurement. These official files may contain information that is considered a trade secret, proprietary, business sensitive or otherwise protected pursuant to law or regulation, here in after referred to as "protected information". File 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 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 offeror 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) Submission of a proposal will be considered as consent to NAVSEA's permitting access to any information, irrespective of restrictive markings or the nature of the information submitted, by its file management support contractor for the limited purpose of executing its file support contract responsibilities.

(d) NAVSEA may, without further notice, enter into contracts with other contractors for these services. Offerors are free to enter into separate non-disclosure agreements with the file support 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 files or otherwise encumber the government.

(End of Provision)

H-209-H003 REQUIRED DISCLOSURE OF ORGANIZATIONAL CONFLICT OF INTEREST

(NAVSEA) (NOV 2022)

(Nov 2022)

(a) "Organizational Conflict of Interest" means that because of other activities or relationships with other persons, a person is unable or potentially unable to render impartial assistance or advice to the Government, or the person's objectivity in performing the contract work is or might be otherwise impaired, or a person has an unfair competitive advantage. "Person" as used herein includes Corporations, Partnerships, Joint Ventures, and other business enterprises.

(b) The Contractor warrants that to the best of its knowledge and belief, and except as otherwise set forth in the contract, at the time of execution of this contract the Contractor does not have any organizational conflict of interest(s) as defined in paragraph (a).

(c) The Contractor agrees that, if after award, it discovers an actual or potential organizational conflict of interest, it shall make immediate and full disclosure in writing to the Contracting Officer. The notification shall include a description of the actual or potential organizational conflict of interest, a description of the action which the Contractor has taken or proposes to take to avoid, mitigate, or neutralize the conflict, and any other relevant information that would assist the Contracting Officer in making a determination on this matter. Notwithstanding this notification, the Government may terminate the contract for the convenience of the Government if determined to be in the best interest of the Government.

(d) Notwithstanding paragraph (c) above, if the Contractor was aware, or should have been aware, of an organizational conflict of interest prior to the award of this contract or becomes, or should become, aware of an organizational conflict of interest after award of this contract and does not make an immediate and full disclosure in writing to the Contracting Officer, the Government may terminate this contract for default.

(e) If the Contractor fails to take action required by this requirement, or required by the Contracting Officer upon receipt of the Contractor's disclosure required by paragraph (c), the Government may terminate this contract for default.

(f) The Contracting Officer's decision as to the existence or nonexistence of an actual or potential organizational conflict of interest shall be final.

(g) The Contractor shall promptly notify the Contracting Officer, in writing, if it has been tasked to evaluate or advise the Government concerning its own products or activities, those of its subcontractors, those of one of its prime contractors (to which the contractor is a subcontractor), or those of a competitor in order to ensure proper safeguards exist to guarantee objectivity and to protect the Government's interest.

(h) The Contractor shall include this requirement in subcontracts of any tier which involve access to information or situations/conditions covered by the preceding paragraphs, substituting "subcontractor" for "contractor" where appropriate.

(i) The rights and remedies described herein shall not be exclusive and are in addition to other rights and remedies provided by law or elsewhere included in this contract.

(j) Compliance with this requirement is a material requirement of this contract.

(End of Text)

M-247-H001 F.O.B. EVALUATION CRITERIA (NAVSEA) (DEC 2018) (Dec 2018)

OFFERS SUBMITTED ON AN F.O.B. BASIS OTHER THAN THAT SPECIFIED IN SECTION F SHALL BE REJECTED

AS UNACCEPTABLE.

(End of Provision)

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)

D-247-W001 PROHIBITED PACKING MATERIALS (NAVSEA) (OCT 2018) (Oct 2018)

The use of asbestos, excelsior, newspaper or shredded paper (all types including waxed paper, computer paper and similar hygroscopic or non-neutral material) is prohibited. In addition, the use of yellow wrapping or packaging material is prohibited except where used for the containment of radioactive material. Loose fill polystyrene is prohibited for shipboard use.

(End of Text)

G-232-H005- SUPPLEMENTAL INSTRUCTIONS REGARDING INVOICING (NAVSEA) (JAN

2019)

(Jan 2019)

(a) For other than firm fixed priced contract line item numbers (CLINs), the Contractor agrees to segregate costs incurred under this contract/task order (TO), as applicable, at the lowest level of performance, either at the sub line item number (SLIN) or CLIN level, rather than at the total contract/TO level, and to submit invoices reflecting costs incurred at that level. Supporting documentation in Wide Area Workflow (WAWF) for invoices shall include summaries of work charged during the period covered as well as overall cumulative summaries by individual labor categories, rates, and hours (both straight time and overtime) invoiced; as well as, a cost break down of other direct costs (ODCs), materials, and travel, by technical instruction (TI), SLIN, or CLIN level. For other than firm fixed price subcontracts, subcontractors are also required to provide labor categories, rates, and hours (both straight time and overtime) invoiced; as well as, a cost breakdown of ODCs, materials, and travel invoiced. Supporting documentation may be encrypted before submission to the prime contractor for WAWF invoice submittal. Subcontractors may email encryption code information directly to the Contracting Officer and Contracting Officer Representative (COR). Shouldthe subcontractor lack encryption capability, the subcontractor may also email detailed supporting cost information directly to the Contracting Officer and COR; or other method as agreed to by the Contracting Officer.

(b) Contractors submitting payment requests and receiving reports to WAWF using either Electronic Data Interchange (EDI) or Secure File Transfer Protocol (SFTP) shall separately send an email notification to the COR and Contracting Officer on the same date they submit the invoice in WAWF. No payments shall be due if the contractor does not provide the COR and Contracting Officer email notification as required herein.

(End of Text)

G-232-H002- H002 PAYMENT INSTRUCTIONS (NAVSEA) (FEB 2024) (Feb 2024)

Payment office allocation methods can be found in the table at DFARS PGI 204.7108(b)(2) (https://www.acq.osd.mil/dpap /dars/pgi/pgi_htm/current/PGI204_71.htm#payment_instructions).

(End of text)

G-242-H001 - GOVERNMENT CONTRACTADMINISTRATION POINTS-OF-CONTACT AND

RESPONSIBILITIES (NAVSEA) (OCT 2023)

(Oct 2023)

(a) The Government reserves the right to administratively substitute any of the points of contact listed below at any time.

(b) The contracting officer is the only person authorized to change this contract or orders issued thereunder. The Contractor shall not comply with any order, direction or request of Government personnel - that would constitute a change - unless it is issued in writing and signed by the Contracting Officer or is pursuant to specific authority otherwise included as part of this contract. If, in the opinion of the contractor, an effort outside the existing scope of this contract is requested, the contractor shall promptly comply with the Notification of Changes clause of this contract.

(c) The points of contact are as follows:

(i) The Procuring Contracting Officer (PCO) is:

Name: Sydney Mcdonald-Johnson Address: 904 Corporate Lane Chesapeake, VA 23320 Phone: (757) 773-0329 E-mail: sydney.m.mcdonald-johnson.civ@us.navy.mil

(ii) The Contract Specialist is:

Name: Kylie Cox Address: 904 Corporate Lane Chesapeake, VA 23320 Phone: (227) 224-3139 E-mail: kylie.l.cox2.civ@us.navy.mil

(d) Technical Point of Contact (TPOC) is the contracting officer’s representative for technical matters when a COR is not appointed. The TPOC is responsible for technical issues of contract administration, such as providing all items of Government Furnished Information (GFI), Government Furnished Material (GFM) and Government Furnished Equipment (GFE) if specified in the contract as well…