CSS - N0016727Q0001 TCS.pdf

PDF 2 MB Posted

Attached to
Tailcone Studs
Solicitation number
N0016727Q0001
Issued by

About this file

This is a combined synopsis and Request for Quotes (RFQ) issued by Naval Surface Warfare Center Carderock Division (NSWCCD) for the procurement of Tailcone Studs (96 units). The solicitation incorporates FAR Part 12 for commercial items and includes provisions and clauses effective through Federal Acquisition Circular FAC 2026-01 and DFARS DPN 20260702. The NAICS code is 336611 (Ship and Boat Building) with PSC code 2010, and this procurement is set-aside for small business. Quotes must be submitted on company letterhead by 10:00 AM on November 5, 2026, to kylie.cox3.civ@us.navy.mil. Responses must include pricing, CAGE code, FOB Destination, point of contact, GSA contract number (if applicable), business size, and lead time for delivery. The pricing arrangement is firm fixed price, and one firm-fixed price purchase order is anticipated to be issued in response.

The technical requirements specify manufacturing of eight tailcone stud shipsets (12 per shipset) in accordance with Reference 2.1 (DISTR D)_808-T01-07-260807 - ITEM 20 - TC STUD.pdf. The contractor must maintain ISO 9001:2015 quality system certification, submit material certifications demonstrating compliance with DFARS specialty metals restrictions, perform 100 percent dimensional and thread inspection, and provide final certification packages for each shipset. All studs must be manufactured from a single heat/lot of material with maintained traceability. Delivery is required to NSWCCD in West Bethesda, Maryland (9500 MacArthur Boulevard, Building 3, Room 308.03), with a three-month period of performance from contract award and one-week advance notification prior to delivery. Each individually packaged shipset must be consolidated into a single heavy-duty, watertight hard plastic storage container. The contractor must deliver a digital technical report/certification data package via email and provide all hardware to the specified address. The Procuring Contracting Officer is Sydney Mcdonald-Johnson, and the Contract Specialist is Kylie Cox.

View the file

Other files

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

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 Tailcone Studs.

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 2026-01 effective 03/13/2026 located on https://www.acquisition.gov/?q=browsefar and the Defense Federal Acquisition Regulation Supplement (DFARS) DPN 20260702 effective 07/02/2026 located at https://www.acq.osd.mil/dpap/dars/change_notices.html. SEE ATTACHED SOLICITATION FOR CLAUSES AND PROVISIONS. The NAICS code is 336611 and the associated PSC code is 2010. 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 05 November 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 05 November 2026, Eastern Standard Time (EST) to kylie.cox3.civ@us.navy.mil.

Point of Contact for this notice is Kylie Cox, kylie.cox3.civ@us.navy.mil

Solicitation/Contract Form Continuation

Tailcone Studs

N0016727Q0001

Continuation of Supplies or Services and Prices/Costs

Additional Information/Notes

Item Supplies/Service Quantity Unit Unit Price Amount

Tailcone Studs

Internal Number: 1024510100 Pricing Arrangement: Firm Fixed Price

96 Each

Continuation of Description

TC Studs

1. BACKGROUND: The Advanced Propulsor Management Office (APMO) (Code 808) in the Naval Architecture and Engineering Department (Code 80) of the Naval Surface Warfare Center, Carderock Division (NSWCCD) is responsible for managing the manufacture and delivery of United States Navy submarine propulsors. The APMO requires the fabrication of hardware to support propulsor component construction, shipment, and installation.

2. SCOPE: The objective of this requirement is to provide propulsor support hardware, including handling fixtures, shipping materials, fasteners, and miscellaneous hardware. The contractor shall provide a quantity of 96 tailcone (TC) studs. Upon completion of manufacturing and Government acceptance the contractor shall deliver all components to the NSWCCD in West Bethesda, MD.

The contractor shall furnish all labor, equipment, and materials necessary to perform the tasking in accordance with the references.

References:

2.1 Ref_2.1-(DISTR D)_808-T01-07-260807 - ITEM 20 - TC STUD.pdf

3. TECHNICAL REQUIREMENTS:

3.1 TC Studs: The contractor shall manufacture eight TC shipsets, 12 per shipset, for a total quantity of 96 in accordance with reference 2.1. The contractor shall procure material, machine, certify, package, and deliver the completed TC studs to NSWCCD.

3.1.1 Quality System: The contractor's quality system shall meet ISO 9001:2015 or later. The contractor may submit an alternative quality system subject to Government approval prior to contract award.

3.1.2 Material: The contractor shall submit material certifications for all material provided under this order. All material certifications shall show compliance with DFARS 252.225-7008 and DFARS 252.225-7009 (Restriction on Acquisition of Certain Articles Containing Specialty Metals). The contractor shall be responsible for maintaining heat/lot traceability of originating material bar stock to final TC studs during the manufacturing process. Each TC stud shipset shall be manufactured from a single heat/lot of material (CDRL A001).

3.1.3 Dimensional Inspection: The contractor shall perform a 100 percent dimensional and thread inspection of all TC studs and shall provide certificates of conformance to comply with reference 2.1 note 302. The contractor, per Note 301 of reference 2.1, shall determine acceptability of all threads based on System 21, ASME B1.3.

3.1.4 Final Certification Package: The contractor shall provide a final certification package/technical report in accordance with reference 2.1, note 302 for each TC stud shipset delivered to the Government

(CDRL A001).

3.1.5 Packaging: The contractor shall provide packaging that protects each of the eight TC stud shipsets from damage, maintains material traceability, and ensures secure transport. Each shipset shall be packaged individually, and each individual package shall contain a hardcopy of the corresponding certification package in accordance with Section 3.1.2.

The contractor shall then consolidate all eight individually packaged shipsets into a single heavyduty, watertight hard plastic storage container (e.g., Pelican Case or equivalent) that provides adequate protection during handling and shipment.

All packaging solutions shall be sized and configured to minimize internal movement and ensure the shipsets remain secure throughout transportation.

3.2 Delivery: Upon completion of tasking in 3.1, the contractor shall deliver all hardware to NSWCCD in West Bethesda, MD. The contractor shall notify the Government Point of Contact (POC) one week (calendar days) prior to delivery.

4. DELIVERABLES: The contractor shall deliver the following Contract Data Requirements Lists (CDRL) for this order.

CDRL Title Data Item Description

A001 Technical

Report

DI-MISC-80508B

The contractor shall prepare a digital copy of the final certification data package/technical report and deliver via email to:

The contractor shall deliver all hardware and spare parts to:

NSWC, Carderock Division

9500 MacArthur Boulevard, Bldg 3, Room 308.03

West Bethesda, MD 20817-5700

POC:

5. PERIOD OF PERFORMANCE

The Period of Performance (PoP) for tasks detailed in Section 3 shall be three months after contract award.

6. TRAVEL

No travel is required.

Requirements Tailcone Studs

Continuation of Packaging and Marking

Continuation of Inspection and Acceptance

Continuation of Deliveries or Performance

Line Item Delivery Schedule Quantity Address and POC

Delivery Schedule From date of lead time event to delivery 3 Month Date of Award

96 Each Ship To DoDAAC: N00167 CountryCode: USA

NSWC CARDEROCK

CARDEROCK DIVISION BLDG 3, Room 308.03, 9500 MACARTHUR

BOULEVARD

BETHESDA, MD 20817-5700

UNITED STATES

Continuation of Accounting and Appropriation Data

Contract Clauses

FAR Clauses Incorporated by Reference

Number Title Effective Date

Alternate/ Deviation

Variation Effective Date

52.204-13 System for Award Management-Maintenance. (Deviation 2026-O0038) Feb 2026 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 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

DFARS Clauses Incorporated by Reference

Number Title Effective Date

Alternate/ Deviation

Variation Effective Date

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.232-7010 Levies on Contract Payments. Dec 2006 252.247-7023 Transportation of Supplies by Sea. Oct 2024 252.204-7015 Notice of Authorized Disclosure of Information for Litigation Support. Jan 2023 252.223-7008 Prohibition of Hexavalent Chromium. Jan 2023 252.232-7003 Electronic Submission of Payment Requests and Receiving Reports. Dec 2018

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) Destination/Destination (D/D)

(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) Destination/Destination (D/D)

(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 N00167

Ship To Code N00167

Ship From Code

Mark For Code

Service Approver (DoDAAC)

Service Acceptor (DoDAAC)

Accept at Other DoDAAC ____

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)

Additional Regulation or Supplemental Clauses Incorporated by Full Text

G-242-H002 HOURS OF OPERATION AND HOLIDAY SCHEDULE (NAVSEA) (JUL 2021) (Jul 2021)

(a) The policy of this activity is to schedule periods of reduced operations or shutdown during holiday periods. Deliveries will not be accepted on Saturdays, Sundays or Holidays except as specifically requested by the [insert activity name]. All goods or services attempted to be delivered on a Saturday, Sunday or Holiday without specific instructions from the Contracting Officer or his duly appointed representative will be returned to the contractor at the contractor's expense with no cost or liability to the U.

S. Government.

(b) The federal Government observes public Holidays that have been established under 5 U.S.C. 6103. The actual date of observance for each of the holidays, for a specific calendar year, may be obtained from the OPM website at OPM.GOV or by using the following direct link: https://www.opm.gov/policy-data-oversight/pay-leave/federal-holidays/.

(c) Delayed Opening, Early Dismissal and Closure of Government Facilities. When a Government facility has a delayed opening, is closed or Federal employees are dismissed early (due to severe weather, security threat, security exercise, or a facility related problem) that prevents personnel from working, onsite contractor personnel regularly assigned to work at that facility shall follow the same reporting and/or departure directions given to Government personnel. The contractor shall not direct charge to the contract for such time off, but shall follow parent company policies regarding taking leave (administrative or other). Non-essential contractor personnel, who are not required to remain at or report to the facility, shall follow their parent company policy regarding whether they should go/stay home or report to another company facility. Subsequent to an early dismissal, delayed opening, or during periods of inclement weather, onsite contractors should monitor the OPM website as well as radio and television announcements before departing for work to determine if the facility is closed or operating on a delayed arrival basis.

(d) When Federal employees are excused from work due to a holiday or a special event (that is unrelated to severe weather, a security threat, or a facility related problem), on site contractors shall continue working established work hours or take leave in accordance with parent company policy. Those contractor employees who take leave shall not direct charge the non-working hours to the contract. Contractors are responsible for predetermining and disclosing their charging practices for early dismissal, delayed openings, or closings in accordance with the FAR, applicable cost accounting standards, and the company's established policy and procedures. Contractors shall follow their disclosed charging practices during the contract period of performance, and shall not follow any verbal directions to the contrary. The Contracting Officer will make the determination of cost allowability for time lost due to facility closure in accordance with FAR, applicable Cost Accounting Standards, and the Contractor's established accounting policy and procedures.

(e) If you intend to visit the Contracts Office, it is advised that you call for an appointment at least 24 hours in advance.

(f) The hours of operation are as follows:

AREA FROM TO

West Bethesda, MD 0800 1400

Norfolk, VA 0800 1400

Virginia Beach, VA 0800 1400

(g) All deliveries to the Receiving Officer or Technical Point of Contact address are identified in Box 15, shall be made Monday through Friday from to , local time. Deliveries will not be accepted after . No deliveries will be accepted on federal 0800 1400 1400 government holidays.

(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 as the inspection and acceptance of all contract deliverables.

The Technical Point of Contact (TPOC) is:

Name: [ *] Phone: (Area Code) xxx- [xxxx] E-mail: [ *]

(e) The Alternate Technical Point of Contact (ATPOC) is responsible for TPOC responsibilities and functions in the event that the TPOC is unavailable due to leave, illness, or other official business.

The Alternate Technical Point of Contact (ATPOC) is:

Name: [*]

Phone: (Area Code) xxx- [xxxx]

E-mail: [*]

[ *] To be completed at contract award

(End of Text)

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.203-19 Prohibition on Requiring Certain Internal Confidentiality Agreements or Statements. Jan 2017 52.240-91 Security Prohibitions and Exclusions. (Deviation 2026-O0038) Feb 2026 52.240-92 Security Requirements. (Deviation 2026-O0038) Feb 2026

52.244-6 Subcontracts for Commercial Products and Commercial Services. (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 52.222-90 Addressing DEI Discrimination by Federal Contractors. (Deviation 2026-O0038) Apr 2026

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.204-7022 Expediting Contract Closeout. May 2021 252.225-7012 Preference for Certain Domestic Commodities. Apr 2022 252.225-7048 Export-Controlled Items. Jun 2013 252.237-7010 Prohibition on Interrogation of Detainees by Contractor Personnel. Jan 2023

252.204-7012 Safeguarding Covered Defense Information and Cyber Incident Reporting.

(DEVIATION 2024-O0013 REVISION 1)

May 2024 Deviation 2024-O0013 May 2024

252.225-7972 Prohibition on the Procurement of Foreign-Made Unmanned Aircraft Systems. (DEVIATION 2024-O0014)

Aug 2024 Deviation 2024-O0014 Aug 2024

DFARS Clauses Incorporated by Full Text

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 for all information systems used in performance of the contract, task order, or delivery order that process, store, or transmit FCI Level 2 (Self) or CUI; and

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

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)

List of Contract Documents, Exhibits, or Attachments

Exhibits:

Id Exhibit Name Exhibit Description Reference Identifier

Date Line Item

A CDRL A001 Technical Report TC Studs - Signed

Contract Data Requirements List (CDRL) 22 Oct

B A001 DID Contract Data Requirements List (CDRL) 22 Oct

Attachments:

Number Attachment Name Attachment Description Reference Identifier

Date

Ref_2.1-(DISTR D)_808-T01-07-

260807 - ITEM 20

- TC STUD (1)

Drawings 22 Oct

Solicitation Provisions

FAR Clauses Incorporated by Reference

Number Title Effective Date

Alternate/ Deviation

Variation Effective Date

52.212-1 Instructions to Offerors-Commercial Products and Commercial Services. (Deviation 2026- O0038)

Feb 2026

DFARS Clauses Incorporated by Reference

Number Title Effective Date

Alternate/ Deviation

Variation Effective Date

252.203-7005 Representation Relating to Compensation of Former DoD Officials. Sep 2022 252.204-7008 Compliance with Safeguarding Covered Defense Information Controls. Oct 2016 252.225-7055 Representation Regarding Business Operations with the Maduro Regime. May 2022

252.225-7059 Prohibition on Certain Procurements from the Xinjiang Uyghur Autonomous Region- Representation.

Jun 2023

DFARS Clauses Incorporated by Full Text

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

(May 2021)

PROHIBITION ON THE ACQUISITION OF COVERED DEFENSE TELECOMMUNICATIONS EQUIPMENT OR SERVICES-

REPRESENTATION (MAY 2021)

The Offeror is not required to complete the representation in this provision if the Offeror has represented in the provision at 252.204-7016, Covered Defense Telecommunications Equipment or Services-Representation, that it "does not provide covered defense telecommunications equipment or services as a part of its offered products or services to the Government in the performance of any contract, subcontract, or other contractual instrument."

(a) . "Covered defense telecommunications equipment or services," "covered mission," "critical technology," and "substantial or Definitions essential component," as used in this provision, have the meanings given in the 252.204-7018 clause, Prohibition on the Acquisition of Covered Defense Telecommunications Equipment or Services, of this solicitation.

(b) . Section 1656 of the National Defense Authorization Act for Fiscal Year 2018 (Pub. L. 115-91) prohibits agencies from Prohibition procuring or obtaining, or extending or renewing a contract to procure or obtain, any equipment, system, or service to carry out covered missions that uses covered defense telecommunications equipment or services as a substantial or essential component of any system, or as critical technology as part of any system.

(c) . The Offeror shall review the list of excluded parties in the System for Award Management (SAM) at for Procedures https://www.sam.gov entities that are excluded when providing any equipment, system, or service to carry out covered missions that uses covered defense telecommunications equipment or services as a substantial or essential component of any system, or as critical technology as part of any system, unless a waiver is granted.

(d) . If in its annual representations and certifications in SAM the Offeror has represented in paragraph (c) of the provision at Representation 252.204-7016, Covered Defense Telecommunications Equipment or Services-Representation, that it "does" provide covered defense telecommunications equipment or services as a part of its offered products or services to the Government in the performance of any contract, subcontract, or other contractual instrument, then the Offeror shall complete the following additional representation:

The Offeror represents that it will will not provide covered defense telecommunications equipment or services as a part of its offered products or services to DoD in the performance of any award resulting from this solicitation.

(e) . If the Offeror has represented in paragraph (d) of this provision that it "will provide covered defense telecommunications Disclosures equipment or services," the Offeror shall provide the following information as part of the offer:

(1) A description of all covered defense telecommunications equipment and services offered (include brand or manufacturer; product, such as model number, original equipment manufacturer (OEM) number, manufacturer part number, or wholesaler number; and item description, as applicable).

(2) An explanation of the proposed use of covered defense telecommunications equipment and services and any factors relevant to determining if such use would be permissible under the prohibition referenced in paragraph (b) of this provision.

(3) For services, the entity providing the covered defense telecommunications services (include entity name, unique entity identifier, and Commercial and Government Entity (CAGE) code, if known).

(4) For equipment, the entity that produced or provided the covered defense telecommunications equipment (include entity name, unique entity identifier, CAGE code, and whether the entity was the OEM or a distributor, if known).

(End of provision)

Addendum to 52.212-1, Instructions to Offerors - Commercial Products and Commercial Services

Evaluation - Commercial Products and Commercial Services

FAR Clauses Incorporated by Full Text

52.212-2 Evaluation-Commercial Products and Commercial Services. (Deviation 2026-O0038) (Tailored)

(Feb 2026)

Evaluation-Commercial Products and Commercial Services (Feb 2026) (Deviation 2026-O0038)

EVALUATION FACTORS FOR AWARD

The Government has determined that an award will be made to the responsible Quoter whose technically acceptable quote is considered to be the most advantageous to the Government, past performance and price considered

1. Technical Acceptability: All quotations will be evaluated on a pass/fail basis to determine if the proposed product(s) clearly meet the technical requirements outlined in the solicitation's Performance Work Statement / salient characteristics. Quotations that do not meet the minimum requirements detailed in the solicitation will be rated "Unacceptable" and will not be considered further.

2. Past Performance: The Government reserves the right to consider past performance information for the lowest-priced, technically acceptable vendor prior to award. The Government may use information available in the Supplier Performance Risk System (SPRS) and other sources. A neutral past performance rating will be assigned if no relevant past performance information is available.

3. Price: The price of all technically acceptable…

This is the start of the file's text. The full file is on GovTribe.

File details come from the government source that posted it. Updated .