BOAST RFOP_Diffuser Assembly Amendment 001.xlsx

RFOP

BASIC ORDERING AGREEMENT SUSTAINMENT TRACK (BOAST): Request for Order Proposal (RFOP)

NOTICE ID: PANDTA-26-P-0000 032936 - Amendment 001 DATE ISSUED: 7/22/2026 REV 8/21/2026 RESPONSE DUE: 28 August 2026, 1600 EST

GENERAL INFORMATION I. This Request for Order Proposal (RFOP) is a competitive action to solicit proposals for the supplies/services detailed below. While all responsible sources may submit a proposal, award is contingent upon the mandatory eligibility requirements detailed below. The resulting order will be a firm-fixed-price contract placed under the BOAST program.

II. Information regarding the program's continuous on-ramp process can be found in the standing BOAST program notice on SAM.gov under ID W912CH-26-R-0001. Vendors are encouraged to proactively establish a BOA to ensure eligibility for future requirements.

III. All questions regarding this RFOP must be submitted in writing to the Point of Contact no later than 30 July 2026, 1300 EST

DLA Distribution Anniston.

7 Frankford Ave 362 Anniston, AL 36201-4199

PROPOSAL SUBMISSION INSTRUCTIONS Proposal Content:

Submission shall consist of a completed and signed Pricing Sheet contained in this RFOP. No separate technical proposal is required. The Government intends to evaluate proposals and award an order without discussions.

ERROR:#NAME?

EVALUATION FOR AWARD Price Only The Government intends to award a Firm-Fixed-Price Order to the responsible BOA holder who submits the lowest-priced proposal. Price will be evaluated for reasonableness. Award will be made to the offeror with the lowest evaluated price.

Evaluation: Price will be evaluated for reasonableness. Award will be made to the offeror with the lowest evaluated price.

In accordance with FAR Subpart 9.1, the Government will make a determination of contractor responsibility for the apparent successful awardee prior to placing the order.

NAME: DATE:

mailto:BOAST@army.mil Applicable Clauses-Provisions

(FEB 2026)

(DEVIATION 2026-O0025)(FEB 2026)

QMS Requirements: ISO 9001:2015 (21 Oct 2015) or equivalent. Tailored by excluding paragraph 8.3

(b) The contractor shall include applicable requirements of the higher-level quality standard(s) listed in paragraph (a) of this clause and the requirement to flow down such standards, as applicable, to lower-tier subcontracts in--

(1) Any subcontract for critical and complex items (see 46.203(b) and (c)); or

(2) When the technical requirements of a subcontract require--

(i) Control of such things as design, work operations, in-process control, testing and inspection; or

(ii) Attention to such factors as organization, planning, work instructions, documentation control, and advanced metrology.

this contract.

(b) The Contractor shall label the item package (unit container) of any hazardous material to be delivered under this contract in accordance with the Hazard Communication Standard (29 CFR 1910.1200 et seq). The Standard requires that the hazard warning label conform to the requirements of the standard unless the material is otherwise subject to the labeling requirements of one of the following statutes:

(1) Federal Insecticide, Fungicide and Rodenticide Act;

(2) Federal Food, Drug and Cosmetics Act;

(3) Consumer Product Safety Act;

(4) Federal Hazardous Substances Act; or

(5) Federal Alcohol Administration Act.

(c) The Offeror shall list which hazardous material listed in the Hazardous Material Identification and Material Safety Data clause of this contract will be labeled in accordance with one of the Acts in paragraphs (b)(1) through (5) of this clause instead of the Hazard Communication Standard. Any hazardous material not listed will be interpreted to mean that a label is required in accordance with the Hazard Communication Standard.

MATERIAL (If None, Insert None.) ACT

(d) The apparently successful Offeror agrees to submit, before award, a copy of the hazard warning label for all hazardous materials not listed in paragraph (c) of this clause. The Offeror shall submit the label with the Material Safety Data Sheet being furnished under the Hazardous Material Identification and Material Safety Data clause of this contract.

(e) The Contractor shall also comply with MIL-STD-129, Marking for Shipment and Storage (including revisions adopted during the term of this contract).

(b) The Offeror must list any hazardous material, as defined in paragraph (a) of this clause, to be delivered under this contract. The hazardous material shall be properly identified and include any applicable identification number, such as National Stock Number or Special Item Number. This information shall also be included on the Safety Data Sheet submitted under this contract.

Material (If none, insert None): Identification No.:

(c) This list must be updated during performance of the contract whenever the Contractor determines that any other material to be delivered under this contract is hazardous.

(d) The apparently successful offeror agrees to submit, for each item as required prior to award, a Safety Data Sheet, meeting the requirements of 29 CFR 1910.1200(g) and the latest version of Federal Standard No. 313, for all hazardous material identified in paragraph (b) of this clause. Data shall be submitted in accordance with Federal Standard No. 313, whether or not the apparently successful offeror is the actual manufacturer of these items. Failure to submit the Safety Data Sheet prior to award may result in the apparently successful offeror being considered nonresponsible and ineligible for award.

(e) If, after award, there is a change in the composition of the item(s) or a revision to Federal Standard No. 313, which renders incomplete or inaccurate the data submitted under paragraph (d) of this clause, the Contractor shall promptly notify the Contracting Officer and resubmit the data.

(f) Neither the requirements of this clause nor any act or failure to act by the Government shall relieve the Contractor of any responsibility or liability for the safety of Government, Contractor, or subcontractor personnel or property.

(g) Nothing contained in this clause shall relieve the Contractor from complying with applicable Federal, State, and local laws, codes, ordinances, and regulations (including the obtaining of licenses and permits) in connection with hazardous material.

(h) The Government’s rights in data furnished under this contract with respect to hazardous material are as follows:

(1) To use, duplicate and disclose any data to which this clause is applicable. The purposes of this right are to—

(i) Apprise personnel of the hazards to which they may be exposed in using, handling, packaging, transporting, or disposing of hazardous materials;

(ii) Obtain medical treatment for those affected by the material; and

(iii) Have others use, duplicate, and disclose the data for the Government for these purposes.

(2) To use, duplicate, and disclose data furnished under this clause, in accordance with subparagraph (h)(1) of this clause, in precedence over any other clause of this contract providing for rights in data.

(3) The Government is not precluded from using similar or identical data acquired from other sources.

Technical & Quality Requirement

(b) To be eligible to gain access to this export controlled TDP (via SAM.gov) an offeror must have a current DD 2345, “Militarily Critical Technical Data Agreement” certification on file with the Defense Logistics Information Service (DLIS). To obtain certification, contractors must submit a DD Form 2345 to the United States (U.S.)/Canada Joint Certification Office (JCO), along with a copy of supporting documentation. DD Form 2345 and instructions can be found on the Joint Certification Program website at: http://www.dla.mil/HQ/InformationOperations/Offers/Products/LogisticsApplications/JCP.aspx Processing time is estimated at six (6) to ten (10) weeks after receipt. Upon receipt of certification, an offeror may request the TDP in accordance with the solicitation's Section C “Technical Data Package” instructions.

(c) Upon completion of the purposes for which Government Technical Data has been provided, the offeror, and all subcontractors, vendors, and sub-vendors of the offeror, are required to destroy all documents, including all reproductions, duplications, or copies thereof as may have been further distributed.

(d) Destruction of this technical data shall be accomplished by: shredding, pulping, burning, or melting any physical copies of the TDP and/or deletion or removal of downloaded TDP files from computer drives and electronic devices, and any copies of those files.

CONFIGURATION MANAGEMENT DOCUMENTATION

The Contractor may submit Engineering Change Proposals (ECPs), Requests for Variance (RFVs), and Notices of Revision (NORs) for the requirements in the Government-provided Technical Data Package (TDP).

a. The Configuration Change Management section of SAE EIA-649-1(current revision) Configuration Management Requirement for Defense Contracts, Paragraph 3.3, shall be used for configuration control of material with the following exclusions: paragraph 3.3(3); the second sentence of paragraph 3.3.1.8.1(1).

b. Furnished item(s) shall conform to the approved configuration requirements/revision, unless a Request for Variance (RFV) is processed and approved as provided by Paragraph E. below. The term "Request for Variance" includes Requests for Deviations and Waivers.

c. Value Engineering Change Proposals (VECPs) for cost saving improvements to the TDP should not be processed per SAE EIA-649-1 and should be referred to Section I FAR Clause 52.248-1 - Value Engineering.

d. All ECPs submitted will be deemed routine. If an ECP is considered as an emergency or urgent; that justification for the rationale shall be included in the ECP submittal with all applicable supporting documentation.

e. For ECPs, RFVs, or NORs, the Contractor must submit the documentation listed in sub-paragraphs e (i) through e (iii). Failure to submit a complete legible package may result in return of the ECP/RFV/SCN/NOR without processing.

(i) for ECPs, the Contractor shall prepare and deliver the ECP in accordance with (IAW) CDRL A001.

(ii) for RFVs, the Contactor shall prepare and deliver the RFV IAW CDRL A002.

(iii) for NORs, the Contractor shall prepare and deliver the NOR IAW CDRL A003.

f. The Government’s acceptance of the data deliverable required by CDRL/DD Form 1423 in e(i)-(iii) above signifies only that the data satisfies the requirements of the DID and is considered acceptable for Government processing. Acceptance of the data deliverable does not signify "technical approval" of the change proposed by the deliverable and should not be interpreted as authorizing the Contractor to proceed with the work proposed by the change. Disposition of the change (approval/disapproval) will follow acceptance of the CDRL at the Government’s sole discretion. Incorporation of an approved RFV or ECP will require execution of a contract modification.

g. The Contractor should direct questions regarding the status of an ECP or RFV to the Procuring Contracting Officer (PCO) and copy the Administrative Contracting Officer (ACO).

The submission of an ECP/RFV/SCN/NOR does not affect the required delivery date of the contract.

(b) The contractor will receive a copy of the Plan at time of award. Local form STA Form 7114 (or similar) will be used to document and record security OPSEC reviews which are conducted by TACOM G3/G2 or individual organizations supporting AT/OPSEC Officers.

(c) The contractor shall identify an individual who will be an OPSEC Coordinator. The contractor will ensure that this individual is OPSEC Level I.

Counterintelligence Awareness and Reporting (CIAR); formerly known as Threat Awareness Reporting Program (TARP) Per AR 381-12, all Department of the Army (DA) personnel (Military/Civilian/Contractor) must complete CIAR training within 30 days of assignment or employment to an organization/contract, and then once every 12 months thereafter pursuant to DoDD 5240.06. DA personnel will complete “Counterintelligence Awareness and Reporting for DoD Employees” – CI116.16, located at https://www.cdse.edu/, to satisfy most Army annual training requirements.

In addition, per AR 381-12 Chapter 5, the following individual(s) must receive an in-person CIAR briefing directly from an ACI Special Agent or a CI-experienced person in addition to the annual training requirement:

• DA personnel scheduled to travel (official, unofficial, permanent change of station) to or through countries with a high foreign intelligence or terrorist threat level as identified by Defense Intelligence Agency or the Department of State, will receive a special CIAR briefing prior to the travel and will be debriefed upon return. AR 381–12 • 13 June 2025 11

• DA personnel who have security clearances travelling to foreign locations in any duty status must fulfill pre-and-post travel security briefing and debriefing requirements in accordance with the DoD Foreign Clearance Guide and DoDD 4500.54E.

• DA personnel deploying in support of military exercises or contingency operations will receive a special CIAR briefing prior to departure.

• DA personnel taking part in bilateral or multilateral engagements with foreign governments or international organizations will receive a CIAR briefing prior to the event.

• Foreign visitors, personnel, and personal connections. Commanders will coordinate with unit security managers to identify personnel potentially vulnerable to FIE exploitation and ensure they are referred to ACI to receive specialized CIAR briefing.

• Such personnel will receive foreign intelligence threat briefings prior to foreign travel or event.

• Personnel with access to Sensitive Compartmented Information and Special Access Programs.

• Personnel assigned to or supporting defense critical infrastructure or associated assets, pursuant to DoDD 3020.40 and DoDI 5240.19, will receive an in-person special CIAR briefing on an annual basis. Such personnel will notify their local ACI office of all projected foreign travel or foreign visits.

• Foreign government employment. Current and retired DA personnel seeking employment with foreign government entities will have CIAR training and support made available.

• Information technology professionals System administrators, privileged users, and those with privileged access that provides an individual capability to alter the properties, behavior, or control of a DoD information system will receive in-person special CIAR briefings on an annual basis.

• Professional and educational exchange programs with foreign governments.

These briefings will be tailored to the particular risk or threat involved, including methods the person may use to minimize the risk, and will place special emphasis on reporting responsibilities. Debriefings will be conducted as soon as feasible following completion of travel, duty, or visit to a foreign country, or attendance at a conference with foreign personnel by an ACI Special Agent. Failure to receive training does not relieve individuals from their reporting responsibilities in chapter 4 of this regulation.

TECHNICAL DATA PACKAGE INFORMATION The following Xd item applies to this solicitation:

[ ] 1. There is no Technical Data Package (TDP) included with this solicitation.

[ X ] 2. The TDP for this solicitation resides within the System for Award Management (SAM) (https://SAM.gov ) associated with this solicitation number: PANDTA-26-P-0000 036569

To access the data through SAM:

a. Log on to the SAM web site: https://SAM.gov .

b. Search for the solicitation number.

c. Click on the attachment you would like to view.

d. If the attachment is restricted, request access to the document.

a. The Configuration Change Management section of SAE EIA-649-1(current revision) Configuration Management Requirement for Defense Contracts, Paragraph 3.3, shall be used for configuration control of material with the following exclusions: paragraph 3.3(3); the second sentence of paragraph 3.3.1.8.1(1).

b. Furnished item(s) shall conform to the approved configuration requirements/revision, unless a Request for Variance (RFV) is processed and approved as provided by Paragraph E. below. The term "Request for Variance" includes Requests for Deviations and Waivers.

c. Value Engineering Change Proposals (VECPs) for cost saving improvements to the TDP should not be processed per SAE EIA-649-1 and should be referred to Section I FAR Clause 52.248-1 - Value Engineering.

d. All ECPs submitted will be deemed routine. If an ECP is considered as an emergency or urgent; that justification for the rationale shall be included in the ECP submittal with all applicable supporting documentation.

e. For ECPs, RFVs, or NORs, the Contractor must submit the documentation listed in sub-paragraphs e (i) through e (iii). Failure to submit a complete legible package may result in return of the ECP/RFV/SCN/NOR without processing.

(i) for ECPs, the Contractor shall prepare and deliver the ECP in accordance with (IAW) CDRL A001.

(ii) for RFVs, the Contactor shall prepare and deliver the RFV IAW CDRL A002.

(iii) for NORs, the Contractor shall prepare and deliver the NOR IAW CDRL A003.

f. The Government’s acceptance of the data deliverable required by CDRL/DD Form 1423 in e(i)-(iii) above signifies only that the data satisfies the requirements of the DID and is considered acceptable for Government processing. Acceptance of the data deliverable does not signify "technical approval" of the change proposed by the deliverable and should not be interpreted as authorizing the Contractor to proceed with the work proposed by the change. Disposition of the change (approval/disapproval) will follow acceptance of the CDRL at the Government’s sole discretion. Incorporation of an approved RFV or ECP will require execution of a contract modification.

g. The Contractor should direct questions regarding the status of an ECP or RFV to the Procuring Contracting Officer (PCO) and copy the Administrative Contracting Officer (ACO).

The submission of an ECP/RFV/SCN/NOR does not affect the required delivery date of the contract.

CONTROLLED UNCLASSIFIED INFORMATION General: There are types of information that are not classified but that require application of access and distribution controls and protective measures for a variety of reasons. This information is known as controlled unclassified information (CUI). The types of information considered CUI are U.S. Government technical information and information listed at the CUI registry (https://www.archives.gov/cui/registry/category-list ). When handling CUI material, all personnel are to comply with these requirements and follow their company policy and/or applicable Non-Disclosure Agreement (NDA) concerning the protection of proprietary information in situations not clearly stated herein.

• Technical Information Description: Any recorded information related to experimental, developmental, or engineering works that can be used to define an engineering or manufacturing process, or can be used to design, procure, produce, support, maintain, operate, repair, or overhaul program material. The data may be graphic or pictorial delineations in media (e.g., computer software, drawings, or photographs), text in specifications, related performance or design documents, or computer printouts. Examples of technical information include research and engineering data, engineering drawings, and associated lists, specifications, standards, process sheets, manuals, technical reports, catalog-item identifications, and related information, and computer software documentation.

• CUI Information Description: Unclassified Information that requires safeguarding or dissemination controls pursuant to and consistent with applicable law, regulations, and government-wide or LRGWP policies but is not classified under EO 13526, (Classified National Security Information).C.8.4 CUI Markings All documents containing CUI will carry the CUI markings in accordance with DoDI 5200.48. Discontinue all use of legacy or other markings not permitted or included in either the CUI Registry or DoDI 5200.48. Marking of Technical Information will include the statement provided in the Security Classification Guide. If the contents of the technical document require more than one Distribution Statement, apply the most restrictive statement. This does not preclude additional mandated markings as may be required by the contract.

• Protection of CUI Information Access: In accordance with (IAW) DoDI 5200.48, Controlled Unclassified Information (CUI), 6 MAR 2020, all contractors supporting this contract who receive, store, or generate CUI are required to take the DoD Mandatory CUI training available on the Security Awareness Hub at : https://securityawareness.usalearning.gov/cui/index.html . Per DoDI 5200.48 and pursuant to all contractual requirements, DoD contractors require initial CUI training and annual CUI refresher training. CUI may be released only to an individual who has a valid need for such access in connection with the accomplishment of a lawful and authorized Government purpose. Further dissemination of such information will be at the discretion of the Government Security Manager. All personnel supporting this contract shall sign a CUI Non-disclosure Agreement prior to gaining access to the information. Personnel no longer requiring access to CUI must dispose (see Disposal below) or surrender any in their possession and terminate future access to it.

• Storing/Handling: During working hours, take reasonable steps to minimize risk of access to CUI by unauthorized personnel. After working hours, when not in physical possession of the owner, all CUI (whether hardcopy or optical media (e.g., DVDs, CDs) that contain CUI) must be afforded a reasonable degree of physical protection to prevent theft of program information (e.g., store CUI information in locked desks or file cabinets, locked rooms, cable lock laptops, storing in a trunk, storing out of site or similar means). Do not display CUI in public places (e.g., airports, airplanes, restaurants). Electronic storing and processing of CUI shall be in accordance with DFARS 252.204-7012 Safeguarding Controlled Defense Information and Cyber Incident Reporting. Do not process CUI on public computers (e.g., those available for use by the general public in kiosks, hotel business centers), public wireless networks or computers that do not have access control. Personally owned computers and personally owned devices are not authorized to process CUI. Portable electronic devices (e.g., smartphones, laptop computers, tablets), non-portable computers, and removable media (e.g., external hard drives, flash drives, USB drives; not including optical media) must be physically and electronically protected as described in this instruction, DFARS 252.204-7012 and DoDI 8582.01.

• Dissemination: CUI printed documents and material may be transmitted through mail channels, commercial carrier or hand-carried without formal courier orders. CUI information may be disseminated to DoD personnel and DoD contractors to conduct official business for the program. If dissemination is required outside of DoD personnel or DoD contractors, contact the Government Security Manager for approval. Technical information will follow the release instructions identified in the Distribution Statement. Use secure communications whenever possible; however, land-line telephones are more secure than cellular telephones and should be used whenever available for discussions involving CUI. Transmit voice and facsimile transmissions only when you have a reasonable assurance that only authorized recipients will have access to the transmission. Digital transmission shall comply with the below: All transmission and/or dissemination of CUI (i.e., email and file transfers) must use NIST/NIAP-approved cryptographic products/algorithms, e.g., DoD-approved Public Key Infrastructure Certification or DoD Safe Exchange at https://safe.apps.mil/ . These are available at http://iase.disa.mil/pki/eca or http://csrc.nist.gov/groups/STM/cmvp/documents/140-1/140val-all.htm . This encryption requirement includes communications that contain passcodes to teleconferences or web conferences where there is a reasonable expectation that CUI may be discussed. When encryption is not available, a government collaborative suite (aka Integrated Digital Environment [IDE]) must be used to transmit CUI.

• Contractor-hosted collaborative suites may be used for digital transmission and/or dissemination of CUI bypersonnel not located on a government backbone (e.g., NIPRNET), provided the following conditions apply: 1) Useonly NIST/NIAP-approved cryptographic products/algorithms. The latest validation lists may be obtained athttp://iase.disa.mil/pki/eca or http://csrc.nist.gov/groups/STM/cmvp/documents/140-1/140val-all.htm ; and, 2) Use aninternally hosted service that does not use a third-party collaborative suite service provider.

• Do not post CUI to web pages that are publicly available or have access limited only by domain/IP restrictions.As permitted by other contract provisions, CUI may be posted to web pages that control access through the use of aDoD approved Public Key Infrastructure Certification and that provide protection via use of secure sockets, or otherequivalent technologies. These are available at http://iase.disa.mil/pki/eca .

• As new technologies become available in the electronics arena, care should be given to providing a reasonabledegree of protection from known vulnerabilities.

• The Internet is Public Access. CUI must be reviewed and officially approved by the TACOM Public AffairsOfficer for public release before placing on the Internet. This is not applicable when the Internet is used for e-mailtransmissions and encryption is used as noted above.

• Disposal: The contractor shall ensure any covered defense information provided by the Government under this contract is destroyed or sanitized from contractor-owned media and reported in accordance with (IAW) National Institute of Standards and Technology (NIST) Special Publication (SP) 800-88, Revision 1: Guidelines for Media Sanitization (December 2014) (NIST SP 800-88, rev 1), destruction methods, or any destruction method approved for Classified National Security Information (32 CFR 2001.47) unless the CUI category's authority mandates other destruction methods (CUI Specified categories). Agencies must also use destruction methods specifically required by law, regulation, or Government-wide policy for CUI Specified categories. Destroy CUI documents in a manner that makes it unreadable, indecipherable, and irrecoverable (32 CFR 2002.14(f)(2)). For paper documents, Reference CUI Notice 2019-03:

Destroying of Controlled Unclassified Information (CUI) in paper form.

• Report of Loss of CUI: Report any loss of CUI to the Government Security Manager. Initial reports shall be made as expeditiously as possible in all cases within 72 hours of discovery. If additional information is required after submission and review of the initial report, guidance will be provided at that time. Initial report content shall include the following information as available.

- Applicable dates, including dates of compromise and dates of discovery.

- Threat methodology, including all known resources used (e.g. IP addresses, domain names, software tools).

- Account of what actions the threat(s) may have taken on victim system/network.

- What information may have been compromised or lost, and its potential impact on government programs.

PACKAGING REQUIREMENTS (SPECIAL PACKAGING INSTRUCTIONS) Military preservation, packing, and marking for the item identified above shall be accomplished in accordance with the specific requirements identified below, all the applicable requirements of, MIL-STD-2073-1 and the Special Packaging Instruction (SPI) contained in the TDP.

(1) LEVEL OF PRESERVATION: Military

(2) LEVEL OF PACKING: B

(3) QUANTITY PER UNIT PACKAGE: 001

(4) SPECIAL PACKAGING INSTRUCTION NUMBER. AK12005821

(a) REVISION C

(b) DATE OF REVISION 10 Sept 2002

(c) THE REQUIRED SPECIAL PACKAGING INSTRUCTION (SPI) IS AVAILABLE ON THE WEB AT THE FOLLOWING URL: See Attachment 0002

(d) SUPPLEMENTAL INSTRUCTIONS: SEE SECTION C FOR CHANGES/UPDATES TO SPI.

INSPECTION AND ACCEPTANCE POINTS: ORIGIN The Government's inspection and acceptance of the supplies offered under this contract/purchase order shall take place at ORIGIN. Offeror must specify below the exact name, address, and CAGE of the facility where supplies to be furnished under this contract/purchase order will be available for inspection/acceptance.

INSPECTION POINT: __________________________________________

(Name) (CAGE)

(Address) (City) (State) (Zip)

ACCEPTANCE POINT: __________________________________________

(Name) (CAGE)

(Address) (City) (State) (Zip)

MIL-STD-1916 E.__ USE OF MIL-STD 1916

(a) The Government will not accept lots whose samples submitted for acceptance contain non-conformances unless appropriately documented and approved by the contracting officer. The contractor shall use MIL-STD 1916, DOD Preferred Methods of Acceptance of Product. The Verification Level (VL) shall be VL -IV- for major characteristics and VL -II- for minor characteristics.

(b) MIL-STD HDBK-1916 provides guidance on the use of MIL-STD 1916. This handbook is not contractually binding.

(1) This clause applies to contracts requiring Chemical Conversion Coatings and Pretreatments for Metallic Substrates, Chemical Agent Resistant Coating (CARC), and their related materials. The requirements in this clause clarify and supplement those in the contract, unless nullified elsewhere in the contract or through an approved Request for Deviation.

(2) Coating qualification, spot paint repair, and MIL-DTL-16232 Phosphate Coating, Heavy, Manganese or Zinc Base coatings are not within the scope of this clause.

(b) Definitions

(1) The “contracting agency,” “appropriate agency,” “procuring authority,” “engineering authority,” “procuring agency,” and “procuring activity” is the PCO or designee.

(2) The “prime contractor” is the company awarded this contract, and the “subcontractors” comprise all companies involved in providing coated parts to the prime contractor, including companies that apply the coatings.

(c) General Requirements Clarifications

(1) The government retains the right for onsite verification of the prime contractors’ and its subcontractors’ products, processes, procedures, and test reports.

(2) The prime contractor shall be responsible for itself and its subcontractors to produce and maintain detailed process control plans, process control data, pre-production approval testing, ongoing quality control & quality control testing, and test reports.