K4-B-VAA_PWS_27 Aug 2026.pdf
PDF 606 KB Posted
- Solicitation number
- W91CRB-26-R-5013
About this file
This is a Performance Work Statement (PWS) for a Foreign Military Sales (FMS) Case K4-B-VAA covering the procurement of Ultra-High Frequency (UHF) Tactical Satellite (TACSAT) Type 1 Radios - Advanced Multiband Multichannel Man-pack Terminals (AM3Ts), associated ancillaries, services, and training for NATO Communications and Information Agency (NCIA). The contract requires delivery of equipment across three batches over a 36-month period, with Batch 1 (150 AM3T Kits, 75 Man Portable Kits, 60 Mobile Kits, and 6 Deployed HQ Kits) due within 12 months; Batch 2 due within 24 months; and Batch 3 due within 36 months. Equipment must comply with specified STANAG military standards, MIL-STD specifications, and perform dual-channel simultaneous operations across multiple waveforms including UHF SATCOM (Dedicated, DAMA, and Integrated Waveform), VHF/UHF Line of Sight, SINCGARS, HAVEQUICK II, and SATURN modes with NATO SECRET-level encryption capability.
The contractor must provide comprehensive Integrated Product Support including technical manuals, training materials, operator and maintenance manuals, and four training sessions (two CONUS and two OCONUS at NCI Academy, Portugal) for up to 12 students each. Additional deliverables include a Project Implementation Plan, System Design Specification, System Test and Acceptance Plan, First Article System Test (FAST) at contractor facilities within six months of contract award, Batch Delivery Acceptance testing at NCIA facilities, and Final System Acceptance within 39 months. The contractor shall provide a two-year warranty covering workmanship and materials, with 90-day repair turnaround for warranty claims. All hardware must be new production certified for latest configuration, marked with Item Unique Identification (IUID) per MIL-STD-130N, and packaged per ASTM D 3951-10 standards with ISPM 15-compliant wood packaging materials. Configuration Management, Quality Assurance per STANAG 4107 and AQAP standards, and security requirements including NATO SECRET facility clearance, AT/OPSEC training, and CMMC Level 2 certification are mandated throughout the contract lifecycle.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| K4-B-VAA_RTM_27 Aug 2026.xlsx | XLSX spreadsheet | |
| W91CRB-26-R-5013 Amd 0003_01SEP2026.pdf | ||
| W91CRB-26-R-5013 Amd 002_26AUG2026.pdf | ||
| K4-B-VAA_RTM_13 AUG 2026.xlsx | XLSX spreadsheet | |
| Price Summary Workbook_14AUG2026.xlsx | XLSX spreadsheet | |
| K4-B-VAA_PWS_13 Aug2026.pdf | ||
| K4-B-VAA_DD Form 254_ 2026 April 09.pdf | ||
| W91CRB-26-R-5013 Amd 001_18AUG2026.pdf | ||
| Price Summary Workbook_30JUL2026.xlsx | XLSX spreadsheet | |
| RTM_K4-B-VAA_30JUL2026.xlsx | XLSX spreadsheet | |
| K4-B-VAA_PWS_30JULY2026.pdf | ||
| K4-B-VAA_CDRLs_30JUL2026.pdf | ||
| W91CRB-26-R-5013_30JUL2026.pdf |
Show all 13
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
Performance Work Statement (PWS)
Ultra-High Frequency (UHF) Tactical Satellite (TACSAT) Type 1 Radios - Advanced Multiband Multichannel Man-pack Terminals (AM3Ts), Associated Ancillaries, Services and Training
Foreign Military Sales (FMS) Case K4-B-VAA
27 August 2026
Prepared by:
The Security Assistance Management Directorate (SAMD), AMSEL-LCS-RE
Aberdeen Proving Ground, MD
1.0 Scope.
This document defines the efforts required to provide the Ultra-High Frequency (UHF) Tactical Satellite (TACSAT) Type 1 Radios - Advanced Multiband Multichannel Man-pack Terminals (AM3Ts), associated ancillaries, services and training for North Atlantic Treaty Organization (NATO) Communications and Information Agency (NCIA) under Foreign Military Sales (FMS) case K4-B-VAA. The word Government in this document refers to the United States Government. The word Purchaser in this document refers to the FMS Customer(s) or NATO NCIA.
2.0 Applicable Documents.
2.1 Military Standards
MIL-STD-130N with Change 1 Identification Marking of U.S. Military Property MIL-STD-882E System Safety DoD Directive 5230.11 Disclosure of Classified Military Information to Foreign Governments and International Organizations AR 525-13 Antiterrorism AR 530-1 Operations Security AR 381-12 Threat Awareness and Reporting Program (TARP)
2.2 Commercial Standards
ISPM 15 Guidelines for Regulating Wood Packaging Material in International Trade ASTM D 3951-18 Standard Practice for Commercial Packaging
3.0 Requirements. The contractor shall provide all the hardware, software, services and training as specified in PWS. Items shall be presented as new or updated and shall meet the performance criteria and characteristics as specified in the manufacturer’s drawings and specifications. Required hardware, software, and services are described in below paragraphs. Detailed requirements, technical specifications, operational and performance characteristics are provided in Appendix A.
3.1 Requirements for Hardware and Software. The contractor shall provide hardware and software in accordance with and shall meet the technical specifications, operational and performance criteria stated in this PWS. The contractor shall notify, and receive approval from, the Government of any component or system substitutions due to obsolescence or other issues, prior to packing for shipment.
The overall requirements for the Ultra-High Frequency (UHF) Tactical Satellite (TACSAT) Type 1 Radios - Advanced Multiband Multichannel Man-pack Terminals (AM3Ts), associated ancillaries, services and training are outlined in Appendix A, Scope Summary.
3.1.1 AM3T Kit (Batch 1). The contractor shall deliver one-hundred fifty (150) AM3T Kits (Batch 1) within twelve (12) months of contract award (or as soon as the contractor is able.)
The equipment shall be provided in accordance with and shall meet the technical specifications, operational and performance criteria listed in Appendix A, Section 1, Paragraph A. Waveform Licenses (if required) with each batch delivery.
3.1.2 Man Portable Kit (Ancillary Set for OTP Operations) (Batch 1). The contractor shall deliver seventy-five (75) Man Portable Kits (Ancillary Sets for OTP Operations) (Batch 1) within twelve (12) months of contract award (or as soon as the contractor is able.) The equipment shall be provided in accordance with and shall meet the technical specifications, operational and performance criteria listed in Appendix A, Section 1, Paragraph B.
3.1.3 Mobile Kit (Ancillary Set for OTM Operations) (Batch 1). The contractor shall deliver sixty (60) Mobile Kits (Ancillary Sets for OTM Operations) (Batch 1) within twelve (12) months of contract award (or as soon as the contractor is able.) The equipment shall be provided in accordance with and shall meet the technical specifications, operational and performance criteria listed in Appendix A, Section 1, Paragraph C.
3.1.4 Deployed HQ Kit (Ancillary Set) (Batch 1). The contractor shall deliver six (6) Deployed HQ Kits (Ancillary Sets) (Batch 1) within twelve (12) months of contract award (or as soon as the contractor is able.) The equipment shall be provided in accordance with and shall meet the technical specifications, operational and performance criteria listed in Appendix A, Section 1, Paragraph D.
3.1.5 AM3T Kit (Batch 2). The contractor shall deliver one hundred eighty-four (184) AM3T Kits (Batch 2) within twelve (12) months but no later than twenty-four (24) months of contract award (or as soon as the contractor is able.) The equipment shall be provided in accordance with and shall meet the technical specifications, operational and performance criteria listed in Appendix A, Section 1, Paragraph A. Waveform Licenses (if required) with each batch delivery.
3.1.6 Man Portable Kits (Ancillary Set for OTP Operations) (Batch 2). The contractor shall deliver eighty-six (86) Man Portable Kits (Ancillary Sets for OTP Operations) (Batch 2) within fifteen (15) months but no later than twenty-four (24) months of contract award (or as soon as the contractor is able.) The equipment shall be provided in accordance with and shall meet the technical specifications, operational and performance criteria listed in Appendix A, Section 1, Paragraph B.
3.1.7 Mobile Kit (Ancillary Set for OTM Operations) (Batch 2). The contractor shall deliver seventy-eight (78) Mobile Kits (Ancillary Sets for OTM Operations) (Batch 2) within fifteen
(15) months but no later than twenty-four (24) months of contract award (or as soon as the contractor is able.) The equipment shall be provided in accordance with and shall meet the technical specifications, operational and performance criteria listed in Appendix A, Section 1, Paragraph C.
3.1.8 Deployed HQ Kit (Ancillary Set) (Batch 2). The contractor shall deliver six (6) Deployed HQ Kits (Ancillary Sets) (Batch 2) within fifteen (15) months but no later than twenty-four (24) months of contract award (or as soon as the contractor is able.) The equipment shall be provided in accordance with and shall meet the technical specifications, operational and performance criteria listed in Appendix A, Section 1, Paragraph D.
3.1.9 AM3T Kit (Batch 3). The contractor shall deliver one-hundred eighty-three (183) AM3T Kits (Batch 3) within twelve (12) months but no later than thirty-six (36) months of contract award (or as soon as the contractor is able.) The equipment shall be provided in accordance with and shall meet the technical specifications, operational and performance criteria listed in Appendix A, Section 1, Paragraph A. Waveform Licenses (if required) with each batch delivery.
3.1.10 Man Portable Kits (Ancillary Set for OTP Operations) (Batch 3). The contractor shall deliver eighty-seven (87) Man Portable Kits (Ancillary Sets for OTP Operations) (Batch 3) within eighteen (18) months but no later than thirty-six (36) months of contract award (or as soon as the contractor is able.) The equipment shall be provided in accordance with and shall meet the technical specifications, operational and performance criteria listed in Appendix A, Section 1, Paragraph B.
3.1.11 Mobile Kit (Ancillary Set for OTM Operations) (Batch 3). The contractor shall deliver seventy-eight (78) Mobile Kits (Ancillary Sets for OTM Operations) (Batch 3) within eighteen
(18) months but no later than thirty-six (36) months of contract award (or as soon as the contractor is able). The equipment shall be provided in accordance with and shall meet the technical specifications, operational and performance criteria listed in Appendix A, Section 1, Paragraph C.
3.1.12 Deployed HQ Kit (Ancillary Set) (Batch 3). The contractor shall deliver six (6) Deployed HQ Kits (Ancillary Sets) (Batch 3) within eighteen (18) months but no later than thirty-six (36) months of contract award (or as soon as the contractor is able.) The equipment shall be provided in accordance with and shall meet the technical specifications, operational and performance criteria listed in Appendix A, Section 1, Paragraph D.
3.2 Requirements for Services and Training. The contractor shall provide services and training in accordance with and shall meet the specifications and performance criteria stated in this PWS.
3.2.1 CONUS Radio Operator Training. The contractor shall provide one (1) session of Continental United States (CONUS) Radio Operator Training at the contractor’s facility. One
(1) instructor, one (1) week, up to twelve (12) students.
3.2.2 CONUS Radio Maintenance Training. The contractor shall provide one (1) session of CONUS Radio Maintenance Training at the contractor’s facility. One (1) instructor, one (1) week, up to twelve (12) students.
3.2.3 OCONUS Radio Operator Training. The contractor shall provide one (1) session of Outside the Continental United States (OCONUS) Radio Operator Training at the NCI Academy, Portugal with one (1) instructor, one (1) week, up to twelve (12) students.
3.2.4 OCONUS Radio Maintenance Training. The contractor shall provide one (1) session of Outside the Continental United States (OCONUS) Radio Levels I and II Maintenance Training at the NCI Academy, Portugal with one (1) instructor, one (1) week, up to twelve
(12) students.
3.3 Other Requirements.
3.3.1 Project Implementation Plan (PIP). The Contractor shall deliver a Project Implementation Plan (PIP) (Draft and Final) to NCIA, Effective Date of Contract (EDC) plus 2 weeks (Draft) and EDC plus 8 weeks (Final). The detailed requirements of the PIP are listed in Appendix A, Section 2 (CDRL B001).
3.3.2 Project Review Meetings (PRMs). The contractor shall coordinate and hold seven (7) Project Review Meetings (PRMs) with NCIA. The detailed requirements and schedule of PRMs are listed in Appendix A, Section 2. (CDRLs B002, B003)
3.3.3 System Design Specification. The contractor shall deliver a System Design Specification (SDS) (Draft and Final) to NCIA, EDC plus 6 weeks (Draft) and EDC plus 12 weeks (Final). The detailed requirements of System Design are listed in Appendix A, Section 3 (CDRL B004).
3.3.4 System Test and Acceptance. The contractor shall perform testing activities to verify that the hardware and software meets requirements, characteristics, and performance criteria listed in Appendix A, Section 4.
3.3.4.1 System Test and Acceptance Plan (STAP) (Draft and Final). The contractor shall provide the System Test and Acceptance Plan (STAP) within four (4) weeks (draft) and six
(6) weeks of EDC (Final). The detailed requirements of STAP are listed in Appendix A, Section 4. (CDRL B005)
3.3.4.2 Test Readiness Review (TRR). The contractor shall conduct a Test Readiness Review (TRR) one (1) week before FAST. The detailed requirements of the TRR are listed in Appendix A, Section 4.
3.3.4.3 First Article System Test (FAST). The contractor shall conduct First Article System Test (FAST) six (6) months from EDC. The procedures for FAST (CDRL B006) shall be provided three (3) weeks before FAST; the FAST Report (CDRL B007, including Test Results Sheets) shall be delivered two (2) weeks after the conclusion of FAST. The detailed FAST requirements are listed in Appendix A, Section 4.
3.3.4.4 BATCH Delivery Acceptance (BDA). The contractor shall provide a representative to support the BDA IAW with the following schedule. The detailed requirements of BDA are listed in Appendix A, Section 4 (CDRL B002).
3.3.4.4.1 BDA – Batch 1. EDC in accordance with the delivery schedule for batch one (1) in paragraphs 3.1.1 to 3.1.4.
3.3.4.4.2 BDA – Batch 2. EDC in accordance with the delivery schedule for batch two (2) in paragraphs 3.1.5 to 3.1.8.
3.3.4.4.3 BDA – Batch 3. EDC in accordance with the delivery schedule for batch two (2) in paragraphs 3.1.11 to 3.1.12.
3.3.4.5 Final System Acceptance (FSA). The contractor shall conduct Final System Acceptance (FSA) within thirty-nine (39) months from EDC (or earlier if the contractor delivers sooner.) The contractor shall also provide FSA Reports (CDRL B007) within thirty-nine (39) months from EDC. The detailed requirements of FSA (CDRL B006) are listed in Appendix A, Section 4.
3.3.5 Integrated Product Support (IPS) Deliveries. The contractor shall provide Integrated Product Support (IPS) deliveries (documents, data and activities) IAW with the following schedule. The detailed IPS deliveries are listed in Appendix A, Section 5 and Section 6.
3.3.5.1 Integrated Product Support Plan (IPSP) (Draft and Final) required by EDC plus 8 weeks (Draft) and EDC plus 6 months (Final) (CDRL C001).
3.3.5.2 Product Support Data Package (Draft and Final) required by EDC plus 6 months (Draft) and EDC plus 12 months (Final + Revisions) (CDRLs C002 and C003).
3.3.5.3 Obsolescence Report (Draft and Final + Revisions) required by EDC plus 6 months (Draft) and EDC plus 12/18/24/30/36 months (Final) (CDRL C004).
3.3.5.4 Operators Manuals (Draft and Final + Revisions) required by EDC+12 months (Draft) and within 2 months after each batch delivery (Final + Revisions). Commercial Off-the-Shelf (COTS) Operator Manuals shall be provided, supplemented as necessary to reflect unique AM3T, Man Portable, Mobile, and Deployed HQ Kit configurations.
Supplemental information shall be provided IAW DI-TMSS-80527D and DI-TMSS-81816.
The Operators Manual shall also include as a separable document a Quick Setup Pocket Guide (CDRL C005).
3.3.5.5 Maintenance Manuals (Draft and Final + Revisions) required by EDC plus 12 months (Draft) and within 2 months after each batch delivery (Final + Revisions). (COTS) Maintenance Manuals shall be provided, supplemented as necessary to reflect unique AM3T, Man Portable, Mobile, and Deployed HQ Kit configurations. Supplemental information shall be provided IAW DI-TMSS-80527D and DI-TMSS-81816 (CDRL C005).
3.3.5.6 Training Material (Draft and Final) required two (2) months before 1st training (Draft) and 2 weeks before 1st training (Final). Training Material shall include presentation slides, accompanying notes, handouts, and visual aids required to conduct operator and maintenance training of the AM3T, Man Portable, Mobile, and Deployed HQ kit configurations. Training instructors shall provide one (1) hard copy of training handouts for each student (CDRL C006).
3.3.5.7 In Service Support and Warranty shall be valid for each batch two (2) years after U.S. Government acceptance.
3.3.5.8 Warranty Report (Final) required at the end of the warranty period (CDRL C012).
3.3.5.9 Configuration Management Plan required by EDC plus eight (8) weeks (CDRL C007).
3.3.5.10 Configuration Baseline required with each batch after approved engineering change proposals (ECPs) (CDRL C008).
3.4 Requirements for Item Unique Identification (IUID). The contractor shall mark all contract deliverables In Accordance With (IAW) DFARS clause 252.211-7003 in Section F of this contract and the following requirements.
3.4.1 IUID Marking.
3.4.1.1 New items: The contractor shall provide IUID, or DoD recognized unique identification equivalent as detailed in DFARS 252.211-7003, for all items delivered with an acquisition cost of $5,000.00 or more and Government serial numbered items. For long term contracts, the Contractor shall implement IUID markings IAW MIL-STD-130N w/Ch1, dated 16 Nov 2012 for any item that will exceed the $5,000.00 unit price for any range quantity or contract year. This requirement is effective throughout the life of this contract.
3.4.1.2 Repair items: Items received for repair shall be inspected for IUID markings. For items where the marking is damaged or missing the contractor shall mark the equipment with the appropriate IUID markings. For previously acquired items where the IUID markings were not required the contractor shall follow the procedures as if the item was a new item.
3.4.1.3 Commercial Markings. All other items shall have acceptable commercial markings that meet the guidelines in Department of Defense (DoD) Guide to Uniquely Identifying Items http://www.acq.osd.mil/dpap/pdi/uid/index.html.
3.4.1.4 Permanency and Legibility. The IUID marking and identification plates, tags, etching, or labels when used on equipment, parts, assemblies, subassemblies, units, sets, groups, or kits shall be as permanent as the normal life expectancy of the item and be capable of withstanding the environment, test, cleaning, repair, and rebuild procedures specified for the item. Legibility shall be as required and verified for ready readability per MIL-STD-130N w/Ch1, dated 16 Nov 2012.
3.4.1.5 Deleterious Effect. Marking of items shall be accomplished in a manner that will not adversely affect the life and utility of the item. Marking materials creating hazardous conditions shall not be used. Placement and choice of the marking shall not create hazardous conditions.
3.4.1.6 Mandatory Information Reporting for all items requiring IUID marking. The contractor shall include the National Stock Number (NSN), if the item has a NSN, the Serial Number marked on the item, if a Serial Number is marked on the item, the original part number, the current part number (only if not the same as the original part number), the current part number effective date (only if the current part number is used) and the US ARMY as the SERVICE /AGENCY/COMMAND data element in the information reported to the IUID Registry, in addition to the information required to be reported to the IUID Registry by DFARS clause 252.211-7003.
3.4.1.6.1 Wide Area Workflow (WAWF) users shall report this mandatory information to the IUID Registry by Direct submission via an X12 Ship Notice/Shipment and Billing Notice (856/857) transaction, an IUID XML transaction, an IUID flat file transaction or a WAWF IUID Material Inspection and Receiving Report/Combo UDF through the Global Exchange http://www.acq.osd.mil/dpap/pdi/uid/index.html
(GEX) Service, or manually, via the IUID Web Entry Site at http://www.bpn.gov/iuid. For WAWF users, these methods do not replace the current WAWF interaction but are performed in addition to it after the shipment has been accepted to provide IUID data that cannot be provided via WAWF.
3.4.2 IUID Coding. IUID markings and readability requirements shall comply with MIL-STD- 130N w/Ch1, dated 16 Nov 2012.
3.4.2.1 Symbology markings and the order of priority for marking the hardware shall be in accordance with MIL-STD-130N w/Ch1, dated 16 Nov 12. Priority is the 2D data matrix symbol (machine readable) IUID is the minimum requirement when there are severe space limitations. The second priority is the human readable characters. The third priority is the Linear Bar Code.
3.4.2.2 If technical data has not specified the marking location, markings shall be located such that they are visible during item use, provided that sufficient space is available, and does not interfere with equipment operations.
3.4.2.3 If items are not described by Government Product Technical Data (i.e. Commercial Items), the contractor shall maintain diagrams showing placement and description of the IUID marking and applicable installation and processing instructions for government review.
3.4.2.4 The contractor shall maintain an accurate, current list of IUIDs for all manufactured items on this contract. Dates of manufacture, substitutions, shop changes, etc. shall be included on this list. The list shall be available for inspection by the PCO or other Government representative at any time during the life of this contract. The contractor shall provide this list to the government at the end of the contract.
3.4.3 Correction of Noncompliant Equipment and Technical Data.
3.4.3.1 The contractor shall initiate the appropriate configuration control document to correct all affected drawings/specifications which conflict with or omit the marking requirements stipulated above.
3.4.3.2 The contractor shall advise the COR if any configuration control requirements do not apply or when the equipment on order is defined by technical data which conflicts with or omits the marking requirements stated above. Such advice shall list the number of each deficient drawing/specification and a brief description of the deficiency.
3.4.3.3 If the item on order is defined by existing Government technical documentation and such documentation conflicts with the requirements of this PWS, production of equipment with revised markings shall not proceed until Government approval is received by email from the PCO.
3.4.4 Government Purchase of Product/Technical Data.
3.4.4.1 Specifications. Any equipment specification(s) on this contract procured by the Government shall include a requirement to mark the appropriate items with IUID.
http://www.bpn.gov/iuid
3.4.4.2 Drawings. If the Government is procuring engineering drawings or drawing revisions on this contract, the contractor shall include IUID marking requirements on each applicable drawing. Location shall be depicted on the pictorial and other details presented in the notes.
3.4.5 Pricing of IUID Requirements. All efforts required by this PWS and contract, including, but not limited to, the preparation of ECPs or notification of marking deficiencies, serial number data reporting at end of contract and the actual marking of hardware, will be included in the base contract price.
3.5 Security Requirements. The contractor shall meet requirements for Security stated below:
3.5.1 Anti-Terrorism (AT)/ Operations Security
3.5.1.1. AT Level 1 Training: This standard language is for contractor employees with an area of performance within a controlled installation, facility or area: All contractor employees, to include subcontractor employees, requiring access to installations, facilities and controlled access areas shall complete AT Level I Awareness Training within 30 calendar days after contract start date or effective date of incorporation of this requirement into the contract, whichever is applicable. The contractor shall submit certificates of completion for each affected contractor employee and subcontractor employee, to the COR or to the contracting officer, if a COR is not assigned, within 60 calendar days after completion of training by all employees and subcontractor personnel. AT Level I Awareness Training is available at the following website: http://jko.jten.mil (course number “- US007”).
(CDRL A001)
3.5.1.2. AT Awareness Training for Personnel Traveling Overseas: This standard language required U.S. based contractor employees and associated subcontractor employees to make available and to receive Government provided area of responsibility (AOR)-specific AT awareness training as directed by AR 525‐13. Specific AOR training content is directed by the combatant commander, with the unit ATO being the local point of contact.
3.5.2. iWATCH Training: This standard language is for contractor employees with an area of performance within a controlled installation, facility or area: The contractor and all associated subcontractors shall brief all employees on the local iWATCH program (training standards provided by the requiring activity ATO). This local developed training will be used to inform employees of the types of behavior to watch for and instruct employees to report suspicious activity to the COR. This training shall be completed within 30 calendar days of contract award and within 30 calendar days of new employees commencing performance with the results reported to the COR NLT 60 calendar days after contract award. (CDRL A001) https://www.dhs.gov/see-something-say-something
3.5.3 Operations Security (OPSEC)
http://jko.jten.mil/ https://www.dhs.gov/see-something-say-something
3.5.3.1 OPSEC Plan: For contracts that require a formal OPSEC program: The contractor shall develop an OPSEC Standing Operating Procedure (SOP)/Plan within 90 calendar days of contract award, to be reviewed and approved by the responsible Government OPSEC officer. This plan shall include a process to identify critical information, where it is located, who is responsible for it, how to protect it and why it needs to be protected. The contractor shall implement OPSEC measures as ordered by the commander. In addition, the contractor shall have an identified certified Level II OPSEC coordinator per AR 530-1.
(CDRL A002)
3.5.3.2 OPSEC Training: Per AR-530-1 Operations Security, the contractor employees must complete Level I OPSEC Awareness training. New employees must be trained within 30 calendar days of their reporting for duty and annually thereafter. (CDRL A001)
3.5.4 Cybersecurity.
3.5.4.1 Cybersecurity/Information Technology (IT) Training. All contractor employees and associated sub-contractor employees must complete the DoD Cybersecurity awareness training before issuance of network access and annually thereafter. All contractor employees working Cybersecurity/IT functions must comply with DoD and Army training requirements in DoDD 8570.01, DoD 8570.01-M and AR 25-2 within six months of appointment to Cybersecurity/IT functions (CDRL A001).
3.5.4.2 Cybersecurity/Information Technology (IT) Certification. Per DoD 8570.01-M, DFARS 252.239.7001 and AR 25-2, the contractor employees supporting Cybersecurity/IT functions shall be appropriately certified upon contract award.
3.5.5 Information Security
3.5.5.1 For contracts that require handling or access to classified information. Contractor shall comply with FAR 52.204-2, Security Requirements. This clause involves access to information classified “Confidential,” “Secret,” or “Top Secret” and requires contractors to comply with— (1) The Security Agreement (DD Form 441), including the National Industrial Security Program Operating Manual (DoD 5220.22-M); (2) any revisions to DoD 5220.22-M, notice of which has been furnished to the contractor.
a. If secure telecommunication requirements apply, include clause 252.239-7016 and follow guidance at 239.74.
b. If covered system support requirements apply, include provision 252.239-7017 into the solicitation, clause 252.239-7018 into the contract, and follow guidance at 239.73
3.5.5.2 Controlled Unclassified Information (CUI). Include DFARS clause 252.204-7012, which requires the contractor to comply with NIST 800-171. Also include DFARS provision 252.204-2019 into solicitations. Acquisition officials should follow procedures outlined in DFARS 204.73 and verify vendors have an adequate NIST SP 800-171 summary assessment score within the Supplier Performance Risk System (within PIEE). If the score doesn't show a medium- or high-level assessment with a score of 110 or better (as described in the "NIST SP 800-171 DoD Assessment Methodology"), include clause
252.204-7020 and obtain the vendor's "system security plan" and "plan of action" for NIST SP 800-171 verification and assurance by Army security officials.
a. The contractor is required to receive, handle, store, process, and deliver information addressing designs and capabilities of military command, control, and communications technology. As such, the contractor’s Information Technology (IT) shall be Cybersecurity Maturity Model Certification (CMMC) certified as Level 2 (self-assessment) for CUI Basic information. While the contractor is not required to be CMMC certified at Level 2 Third-Party Assessor Organization (C3PAO) until 10 November 2026, the contractor’s IT must satisfy requirements to receive, handle, store, process, and deliver CUI Specified information.
3.5.5.3 Security Training: Several training requirements exist for contractor personnel per DoD and Army regulation/ directives. On-site contractors may receive training briefs from the government appointed Security Manager; however, contracting companies will be required to provide training to offsite contractor employees. Training is tailored to the organization’s requirements as well as local policy. Some examples of Security training provided to integrated/embedded contractors may include, but is not limited to, the following:
• Threat Awareness Reporting Program (required for all contractors with security clearances) - Per AR 381-12 Threat Awareness and Reporting Program (TARP), cleared contractor employees must receive annual TARP training by a CI agent or other trainer as specified in 2-4b. (CDRL A001)
• Initial Security Orientation: Online training available on the Army Training Information System (ATIS) at https://learn.atis.army.mil/.
• Annual Security Orientation: Online training available on the Training Information System (ATIS) at https://learn.atis.army.mil/.
• Derivative Classification Training: Online training available via CDSE STEP, DoD
5200.01 and memo for Chief Management Officer of the Department of Defense dated 31 January 2019 - annual requirement reference.
• DA, AMC, and/or commander directed security stand-downs, e.g., ad-hoc refresher training.
3.5.5.4 For Contract Requiring Performance or Delivery in a Foreign Country: DFARS Clause 252.225-7043 Antiterrorism/ Force Protection for Defense Contractors Outside the US. The clause shall be used in solicitations and contracts that require performance or delivery in a foreign country. This clause applies to both contingencies and non-contingency support. The key AT requirement is for non-local national contractor personnel to comply with theater clearance requirements and allows the combatant commander to exercise oversight to ensure the contractors compliance with combatant commander and subordinate task force commander policies and directives.
3.6 Procurement New Production. The contractor shall provide email verification to the COR that all delivered hardware is supplied from new production and is of the latest configuration at time of production. The email shall include model/configuration number, date of production, and serial number of major end items delivered.
https://learn.atis.army.mil/
3.7 Requirements for Packaging. Packaging/packing shall be in accordance with ASTM D 3951-10, Standard Practice for Commercial Packaging, Level of Protection (LOP):
Commercial, Level of Pack (LPK): Commercial, Quantity Unit Pack (QUP): 001. Marking shall be in accordance with MIL-STD-129R.
3.7.1. Wood Packaging Material (WPM) includes but is not limited to pallets, skids, load boards, pallet collars, wooden boxes, reels, dunnage, crates, frame and cleats. This requirement excludes materials that have undergone a manufacturing process, such as corrugated fiberboard, plywood, particleboard, veneer, and oriented strand board (OSD).
3.7.2. All WPM shall meet the requirements of International Standards for Phytosanitary Measures (ISPM) Number 15, “Regulations in Wood Packaging Material in International Trade (2009)”. DoD shipments inside and outside of the United States shall meet the requirements of ISPM 15 whenever WPM is used to ship DoD cargo.
3.7.3. All WPM shall comply with the official quality control program for heat treatment (HT) or kiln dried heat treatment (KD HT) (IAW) American Lumber Standard Committee (ALSC), Incorporated, Wood Packaging Material Program and WPM Enforcement Regulations (see
ALSC WPM).
3.7.4. All WPM shall include certification/quality markings IAW the ALSC standard.
Markings shall be placed in an unobstructed area that will be readily visible to inspectors.
Pallet markings shall be applied to the stringer or block on opposite sides of the pallet and be contrasting and clearly visible. All containers shall be marked on a side other than the top or bottom, contrasting and clearly visible. All dunnage used in configuring and/or securing the load shall also comply with ISPM 15 and be marked with an ASLC approved DUNNAGE stamp.
3.7.5. Failure to comply with these requirements may result in refusal, destruction, or treatment of materials at the point of entry. The Government reserves the right to recoup from the contractor any remediation costs incurred by the Government.
3.7.6 Handling, Storage, Preservation, Packaging and Shipping. The Contractor shall establish, maintain, control and be responsible for the handling, storage, preservation, packaging and shipping to protect the quality of the materials and to prevent damage from loss, deterioration, degradation, or substitution of products.
3.8 Requirements for Quality, Final Inspection and Test. The contractor shall comply with the following requirements:
3.8.1. Sites for Inspection, Testing, and Acceptance. Inspection, testing, and acceptance of all equipment shall be at Origin. Inspection and testing shall be performed by the contractor. Acceptance shall be by the cognizant DCMA office/POC identified in the Wide Area Work Flow (WAWF) clause 252.232-7006.
3.8.2 Quality System. The contractor shall establish/maintain a system for the final inspection and test of all purchased items to comply with contract requirements. The http://www.alsc.org/WPM_summary_mod.htm
Government has the right to review the contractor’s quality system and require correction whenever it, or any portion thereof, fails to meet the requirements set forth in the contract (see Appendix A, Section 7).
3.8.3 Inspection and Testing. The contractor shall ensure that all necessary inspections and tests are performed on completed products, and this shall include all inspections and tests which are normally performed for the equipment on order. The contractor shall at a minimum perform any inspections and tests (including visual/mechanical inspections and functional tests) required to satisfy the form, fit, and function requirements of the contract.
The form, fit, and function requirements are defined by the contractor’s drawings and literature (specification documents, data sheets, acceptance test procedures, host component assembly checklist, remote antenna assembly checklist, and laptop configuration checklist.) System functional and performance testing shall be performed IAW the System Requirements listed in Appendix A, Section 1 and System Testing and Acceptance listed in Appendix A, Section 4.
3.8.4 Responsibility. The requirements of this PWS do not relieve the contractor of the responsibility to perform any additional tests or inspections required to assure product quality and compliance with drawings and specification requirements.
3.8.5 Records. The contractor shall maintain adequate records of inspections and tests to demonstrate that the final product satisfies contract requirements. The Government has the right to review these records at any time.
3.9 Requirements for Safety Engineering.
The contractor shall identify and document all real and potential hazards associated with the equipment ordered in this contract. This shall include any toxic substance exposure concerns to personnel during operation or maintenance to include transportation or resulting from damage to the equipment. The contractor shall also identify and document any special disposal procedures. The identified hazards and special disposal procedures shall be described either in the applicable Technical Manual shipped with each hardware item, or alternatively as a separate insert (in English) included with each hardware item if no Technical Manual is available for the item. All hazards that cannot be eliminated shall be reduced to the lowest risk possible. Those hazards that cannot be eliminated must be presented to the COR via email, providing at a minimum the post and pre-fix hazard severity and hazard probability levels, corrective action and status, prior to government acceptance of the equipment. MIL-STD-882E shall be used in assessing system safety.
The contractor shall affix applicable safety/hazardous precautionary warnings on hardware in English.
3.10 Requirements for Warranty. The contractor shall provide a no-cost warranty IAW below paragraphs, 3.3.5.7, REQ-90, and from IPS-75 to IPS-80.
3.10.1 The Contractor shall provide a no-cost warranty covering workmanship and materials for all items furnished in accordance with this contract or any modification thereof. If the warranty is a commercial warranty and states that the warranty is not in effect outside the continental United States, then the wording of the warranty shall be amended so that the warranty is extended to the customer country. The warranty shall be for a minimum of two
(2) years following the date of acceptance by the U.S. Government.
3.10.2. Warranty Procedures. The FMS customer will notify The US Army Security Assistance Command (USASAC) New Cumberland (NC) of an equipment failure using a Supply Deficiency Report (SDR). USASAC NC will forward the SDR to the CECOM SAMD SDR action officer, and the contractor will be notified of an equipment failure. Exercising of the warranty shall commence upon contractor receipt of failure notification, at which point the warranty clock shall be stopped relative to the unit in question. Upon receipt of the failed item, the contractor shall determine if the item and failure are covered by the warranty. Upon confirmation that the contractor has repaired/replaced the item under warranty, the warranty clock shall be restarted. The FMS Customer shall be responsible for the established contractual price for items tested and found to be a "False Pull" or "No Evidence of Failure (NEOF)". The contractor shall meet or exceed a 90-day turn-around time for repairs. This time shall be from the date of receipt of the failed item by the contractor at the Contractor’s facility, to shipment from the contractor's facility. The contractor shall be responsible for the transportation cost of repaired items under warranty from the contractor’s facilities to the partner nation base in the customer country.
Transportation costs of repair items determined not to be under warranty shall be borne by the customer country.
3.11 Requirements for Meetings and Reports.
3.11.1 Program Management
a. Program Manager. The contractor shall designate a Program Manager who has overall responsibility for the program, and the control and coordination of work performed.
The Program Manager shall continue to act as the single point of contact within the contractor’s activity for all required program status information, including program cost, schedule, and performance. The contractor shall prepare for, conduct, and present required information needed to support management, design, and status reviews. In addition to meetings described in paragraph 3.3.2, the contractor shall conduct the following review meetings:
1) Monthly Status Reviews. Monthly status review meetings shall be conducted with the US Government team via phone to discuss progress against open actions, address potential risks and plan for upcoming milestones.
2) Quarterly In-Progress Reviews. Quarterly In-Progress Review meetings shall be held in person at the US Government facility to discuss overall program progress to date and request feedback regarding performance, schedule and adherence to contractual requirements to date
b. Monthly Status Report. In the Monthly Status Report, the Contractor shall document the status of efforts towards achieving contract hardware deliverables, installation, acceptance tests and training objectives. The Contractor shall identify accomplishments and challenges encountered, and compare the status achieved to planned goals. The Government shall use the document to monitor and evaluate Contractor performance. The Contractor shall provide this report to the Government monthly IAW CDRL B003. The document shall be titled Status Report and subtitled Monthly Status Report.
1) The contractor shall submit a digital copy of the first Monthly Status Report 30 days after contract award. Subsequent reports shall be submitted by the 5th day of each month.
2) The layout and form of the report shall be in the contractor’s format. Any diagrams and drawings provided shall be in accordance with the contractor’s standard engineering drawing practices. Any illustrations and graphs, e.g., charts, graphs, photographs, sketches, shall be in accordance with the contractor’s normal methods for such data.
3) Alternative delivery media may be discussed with the Contracting Officer prior to delivery.
4) The report, including appendices, attachments, illustrations, graphics, shall be clear, legible and reproducible.
5) Contents of the Monthly Status Report shall include the following:
a) A monthly Milestone/Timeline Chart providing a chronological resume estimating the start and completion times of events from the time of contract award to the end of the contract’s period of performance. An event is defined as a concise, complete and clearly identifiable work effort to be accomplished.
Each event shall be sequentially numbered. A description of the purpose of each event shall be included with the Chart.
b) In each report, the contractor shall provide a report summary with a brief statement of the overall contract status, complete Milestone events, whether the event was accomplished within the estimated time for completion, reason for task/schedule variances, and scheduling impacts on any other events or on the Milestone/Timeline Chart in its entirety.
c) The contractor shall identify all major problems and deficiencies with impact and recommended solutions narrative.
d) The contractor shall summarize the status of tickets and incidents submitted.
e) A revised Milestone/Timeline Chart shall be included with the report when major problems and deficiencies result in changes to the contract scheduling of events.
f) The name of the person(s) preparing report and contact telephone number(s).
c. At a minimum, the contractor shall conduct monthly meetings to monitor contract execution and status IAW reference Appendix A, Section 2. Meetings shall be conducted with the customer and key contract management and technical personnel selected by the contractor. The contractor shall deliver a meeting report describing topics discussed, project status, problem areas/concerns, proposed solutions, and customer feedback. The meeting report shall be IAW CDRL B002.
3.11.2 Status Report – Certificate of Completion.
The Contractor shall attach a completed Certificate of Completion to each DD Form 250 submitted for any and all services in the WAWF system in accordance with CDRL B008, and this PWS. At a minimum, the Contractor shall provide the following to include but not limited to (see attached template in Appendix B):
a. Contract number
b. Delivery Order Number
c. Contract CLIN
d. FMS Case designator
e. Period/service being invoiced
f. Contractor Point of contact for certificate of completion to include, printed name, position/title/rank, phone number, email and signature certifying completion.
g. Class Roster when training is provided.
h. Certifying person’s information that can verify the services have been completed to include but not limited to Country/customer/US Government Personnel, point of contact for certificate of completion to include, printed name, position/title/rank, phone number, email address and signature verifying completion. Failure to provide all the information as indicated in this paragraph could result in payment delays.
4.0 Data and Data Rights. The Government’s rights in non-commercial technical data and software deliverables shall be governed by RFO DFARS 252.227-7989. The Government's rights in commercial technical data deliverables shall be governed by RFO DFARS 252.227-7990. All technical data (e.g. documents, drawings, computer aided design models, simulation and modeling) and software deliverables shall be properly marked in accordance with the marking requirements set forth in RFO DFARS 252.227- 7989(g). Technical data and software deliverables with non-conforming restrictive markings shall be rejected and corrected by the Contractor at the Contractor's expense, in accordance with RFO DFARS 252.227-7989(i). A Data Rights Assertion List IAW RFO DFARS 252.227-7992 for all Prime and sub-Contractors (including sub-contractors from previous Task Orders) shall be included in the proposal.
No other marking regarding the license rights is allowed in the data deliverables. For example, Notice or Disclaimer to the Third party, Proprietary markings, and any other related statements regarding the rights are strictly prohibited.
The contractor shall submit the corresponding commercial software license agreements which will be reviewed and approved by the Contracting Officer for the Government. IAW FAR 12.212 and RFO DFARS 227.7202-1, the contractor shall not submit any commercial software license terms that conflict with federal procurement law or do not satisfy the Government’s needs. Commercial Software License terms that are unacceptable to the Government include (but are not limited to) indemnification provisions (and other types of provisions that include unauthorized or unbudgeted funding obligations), attorney's fees provision, state or foreign choice of law/jurisdiction provisions, binding arbitration provisions, and injunctive relief provisions.
In order to assert that the Government will only have limited rights to non-commercial technical data and restricted rights to non-commercial computer software, the Contractor must be prepared to show evidence that (1) all components/parts of the product were developed exclusively with private funds; and (2) the Government was not entitled to Government Purpose Rights or Unlimited Rights IAW RFO DFARS 252.227-7989.
5.0 Procurement Contracting Officer. The ACC-APG Procurement Contracting Officer (PCO) is the single point of contact within the government for funds, program direction or approval of progress payments. Only the PCO can approve or direct changes or additions to the contract.
APPENDIX A
NCIA intends to replace the AN/PRC-117F and AN/PRC-117G with UHF TACSAT Type 1 Radios - Advanced Multiband Multichannel Man-pack Terminals (AM3Ts) which are designed in Man Portable, Mobile Vehicular, and Deployable HQ configurations. The AM3T Kits which include UHF TACSAT Type 1 Radio - Advanced Multiband Multichannel Man-pack Terminal (AM3T) are configured in Dismount/Man Portable, Vehicular/Mobile, and Deployable HQ configurations. The Man Portable Kit is used for On-the Pause (OTP) operations. The Mobile Kit is used for On-the-Move (OTM) operations while the Deployable Headquarter (HQ) Kit is for deployed sites. The following summaries describe the four (4) specified kits and three (3) deployment use cases.
KIT SUMMARY:
• AM3T KIT: Each AM3T Kit consists of an AM3T Hard Side Transit and Storage Case (UHF TACSAT Type 1 Radios, basic accessories and Operator’s Manual, CDRL C005) and an AM3T Kit Standard Packaging (configuration software and technical manual).
• MAN PORTABLE KIT: Each Man Portable Kit consists of a Man Portable Hard Side Wheeled Ancillary Case (Ancillary set OTP Operations) and one (1) 8-Bay Battery Charging System for every eight (8) Man Portable Kits rounded to the highest whole number.
• MOBILE KIT: Each Mobile Kit consists of a Mobile Kit Integrated Hard Side Mount Storage and Transit Case (RF amplifier, power supply, shock mount and other accessories) and a Mobil Kit Standard Packaging (vehicular antennas, cables and connectors). (Note that rugged shock mounts are required for end item components within the transit case.)
• DEPLOYABLE HQ KIT: Each Deployable HQ Kit consists of a Deployable HQ Kit Integrated Deployable Transit, Storage, and Operations Case (Ancillary Set for deployed sites), Deployable HQ Kit Standard Packaging (deployable antennas, switch, etc.) and one (1) 8-Bay Battery Charging System for every eight (8) Deployable HQ Kits rounded to the highest whole number. (Note that rugged shock mounts are required for end item components within the transit case.)
DEPLOYMENT USE CASE SUMMARY: All Development Use Cases for Dismount/Man Portable, Vehicular/Mobile, and Deployable HQ Configurations will require the AM3T Kit since it is the only kit that contains the UHF TACSAT Type 1 Radio.
• MAN PORTABLE (OTP) DEPLOYMENT USE CASE: Each Man Portable (OTP) Deployment Use Case consists of an AM3T Kit and Man Portable Kit.
• MOBILE (OTM) DEPLOYMENT USE CASE: Each Mobile (OTM) Deployment Use Case consists of an AM3T Kit, and Mobile Kit.
• DEPLOYABLE HQ DEPLOYMENT USE CASE: Each Deployable HQ Deployment Use Case consists of an AM3T Kit, and Deployable HQ Kit.
The required equipment, associated ancillaries, services and training are summarized in the table below:
Type of Equipment /Service Total Qty Batch 1 Batch 2 Batch 3
AM3T Kits (Waveform Licenses (if required)) 517 150 184 183 Man Portable Kit (Ancillary Set for OTP Operations) 248 75 86 87 Mobile Kit (Ancillary Set for OTM Operations) 216 60 78 78 Deployable HQ Kit (Ancillary Set) 18 6 6 6 Eight (8) Bay Battery Charging System 35 11 12 12 CONUS Radio Operator Training 1 CONUS Radio Maintenance Training 1 OCONUS Radio Operator Training 1 OCONUS Radio Maintenance Training 1 Project Implementation Plan (PIP) 2 [Draft (1) + Final(1) ] (Draft and Final) (CDRL B001) Project Review Meetings (PRMs) (CDRLs B002, B003) 7 System Design Specification (SDS) 2 [Draft (1) + Final(1) ] (Draft and Final) (CDRL B004) System Test and Acceptance System Test and Acceptance Plan Qty: 2 [Draft (1) + Final(1)] (Draft and Final) (CDRL B005) Test Readiness Review (TRR) 1 First Article System Test (FAST) and FAST procedure (CDRL B006) and FAST report 3 [Test Execution (1) + Procedure (1) + Report (1)] (CDRL B007, including Test Results Sheets) BATCH Delivery Acceptance (BDA) (CDRL B002) 3 1 1 1 Final System Acceptance (FSA) (CDRL B006) and 2 [Test Execution(1) +Report(1)] Report (CDRL B007) Integrated Product Support (IPS) Deliveries (Documents, Data and Activities) Integrated Product Support Plan (IPSP) As many as required (Draft and Final+ Revisions) (CDRL C001) Product Support Data Package As many as required (Draft and Final + Revisions) (CDRLs C002 and C003) Obsolescence Report (Draft and Final + Revisions) As many as required
(CDRL C004)
Operators Manuals (Draft and Final+ Revisions) As many as required
(CDRL C005)
Maintenance Manuals (Draft and Final+ Revisions) As many as required
(CDRL C005)
Training Material (Draft and Final) (CDRL C006) As many as required In Service Support and Warranty (Each batch 1 two (2) years after U.S.
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 .