Exhibit_A_-_TECHNICAL_REQUIREMENTS_AN-TSC-156D_PHOENIX_08-15-2019.pdf

PDF 287 KB Posted

Attached to
Spare Parts-AN/TSC-156D-Satellite Communication System (Phoenix)
Solicitation number
SPRBL1-19-R-0059
Issued by

About this file

This document provides details for a federal contract solicitation seeking spare parts to support the AN/TSC-156D Satellite Communication System (Phoenix). The solicitation will be issued by the Defense Logistics Agency Aberdeen Provisioning Center and is seeking firm-fixed-price proposals for 31 national stock numbered spare parts to support the Phoenix system over a potential 10-year period of performance. The incumbent and sole approved manufacturer for all items is L3 Technologies. Proposals must be submitted electronically through the Federal Business Opportunities website by the anticipated issuance date of September 11, 2019. The proposed contract type is firm-fixed-price for one five-year base period and one five-year option period. Estimated annual quantities for planning purposes range from one to nine units per item.

Exhibit A Technical Requirements AN/TSC-156D (Phoenix)

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

Exhibit A SPRBL1-19-R-0059 Page 1 of 11 Issue: 15 August 2019

TECHNICAL REQUIREMENTS

Hardware Spares

Satellite Communications System AN/TSC-156D (Phoenix)

Exhibit A SPRBL1-19-R-0059 Page 2 of 11

TABLE OF CONTENTS

1.0 APPLICABLE DOCUMENTS

2.0 CONFIGURATION BASELINE

CIPN Configuration Baseline

2.1 Part Revisions

2.1.1 Configuration

2.1.2 Departures from Configuration Baseline

3.0 ITEM UNIQUE IDENTIFICATION (UID)

3.1 Unique Identification Marking

3.2 Unique Identification Marking Data Submission Guidance

4.0 PACKAGING

4.1 Wood Packing Material

4.2 Preservation, Packing and Marking Instructions

4.2.1 Part Number Marking

5.0 PERFORMANCE REQUIREMENTS

5.1 Inspection and Testing

5.2 Quality

5.3 Hardware Procurement Requirements

5.4 Post Award Orientation Conference

6.0 SECURITY DETAILS

6.1 Security Requirements

6.2 AT Level I Training

6.3 Access and General Protection/Security Policy and Procedures

6.4 AT Awareness Training for Contractor Personnel Traveling Overseas

6.5 iWATCH Training

6.6 Contractor Employees Access to Government Information Systems

6.7 OPSEC Standing Operating Procedure/Plan

6.8 OPSEC Training

6.9 Information Assurance (IA)/Information Technology (IT) Training

7.0 CONTRACT DATA REQUIREMENT LIST (CDRL) DD 1423-1

CDRL A001: Configuration

Appendix A – NSNs for Procurement

Exhibit A SPRBL1-19-R-0059 Page 3 of 11

1.0 APPLICABLE DOCUMENTS

Military and Federal Standards MIL-STD-129R Military Marking for Shipment and Storage MIL-STD-130N Identification Marking of U.S. Military Property DED-STD-595 C(1) Colors used in Government Procurement

Military and Federal Specifications DFARS 252.211-7003 Item Identification and Valuation DFARS 252.211-7006 Passive Radio Frequency Identification AR 25 Information Assurance AR 381-12 Threat Awareness and Reporting Program AR 380-67 Information Management, Information Assurance AR 525-13 Antiterrorism AR 530-1 Operations Security DoD 8570.01 Baseline Certifications DoD 8570.01-M Baseline Certifications FAR 42.503 Post Award Conferences MIL-DTL-53039 C Coating, Aliphatic Polyurethane, Single Component, Chemical

Agent Resistant w/Amd 2 MIL-DTL-53072 D Chemical Agent Resistant Coating (CARC) System Application

Procedures and Quality Control Inspection

MIL-DTL-53072 D Coating, Water Dispersible Aliphatic Polyurethane, Chemical Agent Resistant

MIL-PRF-22750 F Coating, Epoxy, High-Solids MIL-DTL-287 H Waveguide Assemblies, Flexible, Twistable and Non-twistable

General Specification for

Other Documents None A 3286081 Tactical SHF Satellite Terminal (TSST) Specification, Specification

Number A3286081, dated 01 April 2003 A 3286082 Quad-Band Satellite Emulator (QBSE) Specification, Specification

Number A3286082, date 01 April 2003

A3329679 TACTICAL SHF SATELLITE TERMINAL (TSST)

SPECIFICATION AN/TSC-156D With Replacement FM Orderwire 23 June, 2011

SPI# AG 00000601 Special Packaging Instruction (when applicable) DLAD T/Q RP001 DLA Packaging Requirements for Procurement

Commercial Documents ASTM D 3951-15 Standard Practice for Commercial Packaging ANSI/ASQ 9001:2015 Quality Management Systems - Requirements ANSI/IEEE STD 200-1975 Electrical And Electronics Parts And Equipment Reference

Designations for electrical and electronics parts and equipment ISPM Number 15 Regulation of Wood Packaging Material in International Trade

(2009) NAS 3426 Electrical Harness-Cable Assemblies, Packaging Of'

Exhibit A SPRBL1-19-R-0059 Page 4 of 11

Security Documents None

2.0 CONFIGURATION BASELINE

This paragraph establishes contractor requirements for Configuration Management of a Part Number (PN) where the Government does not own a Performance Specification to define the Item.

CIPN Configuration Baseline. The Contractor’s Part Number (PN), as defined by the Contractor’s specifications, drawings, catalog page, etc., at the time of award of this contract, shall form the Configuration Baseline for this acquisition. The applicable Configuration Baseline (CB) for the listed Configuration Item (CI)/Computer Software Configuration Item (CSCI) is as follows:

CI/CSCI CB

AN/TSC-156

Phoenix

A3286082 Quad-Band Satellite Emulator (QBSE) Specification A3286081 Tactical SHF Satellite Terminal (TSST) Specification

Refer to Appendix A for all NSNs

2.1 Part Revisions

2.1.1 Configuration

Each CI, as developed/built and delivered, shall conform to the cited CB and (if applicable) all subsequent CB’s that will be made contractually binding by the Procuring Contracting Officer (PCO). Configuration changes not directly affecting the configuration baseline must be documented by the contractor and shall sent to the Government.

2.1.2 Departures from Configuration Baseline

No changes or departures from the CB are acceptable except for changes or departures which are submitted in accordance with CDRL A001 Configuration Management DI-MISC-80711A and are approved by the Government Configuration Manager (C Mgr.) or Configuration Management Officer (CMO) and which are made applicable to the contract by the PCO. Configuration Control shall be achieved by the Configuration Control Documents (CCDs) as follows:

The Engineering Change Proposal (ECP) describes changes to the CI and associated Government documents and data that are affected by the proposed engineering change. The ECP includes both the engineering change and the supporting documentation by which the change is described and suggested.

An ECP is required for a major change. A major change is defined as any change that will impact any of the following conditions of the PN:

A. Overall performance and Form, Fit, Function and Interface (F3I) Characteristics.

B. Reliability, Maintainability and Survivability C. Electromagnetic Interference (EMI), air worthiness certification, or other pertinent requirement.

D. Safety

Exhibit A SPRBL1-19-R-0059 Page 5 of 11

E. Support, operational and training requirements F. Impact on Technical Manuals, Repair Parts and Special Tools Lists (RPSTLs), DMWRs, Provisioning

Parts List (PPL), etc.

G. Impact on Cost and/or Schedule. Impact on test equipment, and support equipment

A Notice of Revision (NOR) shows the detailed changes that must be made to technical documentation, except specifications, (one NOR per document) following approval of an ECP. The NOR is submitted as part of the

ECP.

A Specification Change Notice (SCN) is used to delineate the exact change(s) in a specification that will be distributed to users when the ECP is approved. The SCN is submitted as part of the ECP. The SCN is not used for a military or federal document, only a Request for Variance (RFV) can be used for those documents.

The Request for Variance (RFV) describes a departure from configuration documentation for a specific number of units or period of time. Contractor shall identify the impact of the RFV on performance, operational readiness and logistics support of the affected CIs. The Government may require compensation or consideration for any approved RFV.

The Contractor shall provide all supporting program data with the CCD. The contractor shall uniquely and sequentially identify (including the use of the contract number) each ECP, NOR, SCN or RFV. The identification number should use less than 16 characters.

3.0 ITEM UNIQUE IDENTIFICATION (UID)

The contractor shall implement item Unique Identification (UID) marking, as defined in MIL-STD-130-M and DoD Guide to Uniquely Identifying Tangible Items, Assuring Valuation, Accountability and Control of Government Property, Version 3.0, December 2, 2014. The two-dimensional item UID marking shall be incorporated into existing data plates, shall be machine-readable with common optical scanning devices, and be accompanied by the corresponding human readable markings when practical.

3.1 Unique Identification Marking

The contractor shall comply with DFARS 252.211-7003, Item Identification and Valuation to provide UID. UID markings shall be per the latest version of MIL-STD-130. UID markings are also required for embedded components in this contract. Guidance for UID Marking of embedded components shall be per the latest version of MIL-STD-130 and the https://www.acq.osd.mil/dpap/pdi/uid/ website. Refer to DFARS 252.211-7003 for additional requirements. The Contractor shall ensure that all delivered equipment meeting the UID criteria is marked and the applicable data is submitted to the DOD UID Repository.

The UID 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 the latest version of MIL-STD-130N.

3.2 Unique Identification Marking Data Submission Guidance

The Contractor shall submit UID data via the Wide Area Work Flow (WAWF) Paperless Contracting Environment per the latest published guidance. The latest UID Data Submission guidance may be found at http://www.acq.osd.mil/dpap/sitemap.html.

Exhibit A SPRBL1-19-R-0059 Page 6 of 11

4.0 PACKAGING

All hardware items shall be packaged and marked in accordance with (IAW) ASTM D 3951-15, Standard Practice for Commercial Packaging. Level of Protection: Commercial, Level of Pack (LPK): Commercial, Quantity Unit Pack (QUP): 001. Marking shall be IAW MIL-STD-129R with change 4. Radio Frequency Identification (RFID) requirements shall be per clause DFARS 252.211-7006 of the contract.

4.1 Wood Packing Material

Wood packaging material (WPM) includes but is not limited to pallets, skids, load boards, pallet collars, wooden boxes, reels, dunnage, crates, frames and cleats. This requirement excludes materials that have undergone a manufacturing process, such as corrugated fiberboard, plywood, particleboard, veneer, and oriented strand board (OSB). All WPM shall meet the requirements of the International Standards for Phytosanitary Measures (ISPM) Number 15, "Regulation of Wood Packaging Material in International Trade". DoD shipments inside and outside of the United States shall meet the requirements of ISPM 15 whenever WPM is used to ship DoD cargo.

All WPM shall comply with the official quality control program for heat treatment (HT) or kiln dried heat treatment (KDHT) IAW American Lumber Standard Committee (ALSC), Incorporated, Wood Packaging Material Program and WPM Enforcement Regulations (see http://www.alsc.org/).

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 diagonally 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 ALSC approved DUNNAGE stamp.

DoD Components are defined as all entities, including Contractors that engage in logistical functions supporting elements of the U.S. Armed Forces. See DLAD T/Q RP001 DLA Packaging Requirements for Procurement.

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. The Contractor shall establish, maintain, control and be responsible for the handling, storage, preservation, packaging and shipping to maintain the quality of the materials and to prevent damage from loss, deterioration, degradation, or substitution of products

4.2 Preservation, Packing and Marking Instructions

4.2.1 Part Number Marking

Each item delivered under contract, along with each assembly, subassembly, and module, shall be legibly marked with the appropriate part number and manufacturer’s identification. Hardware such as screws, nuts, bolts, need not be marked. The marking shall become permanently part of the item after it is applied, and can be applied using deformation, tag, and rubber stamp with permanent characteristics or stencil. The marking shall not interfere with proper operation of the item, and shall have no deleterious effect on the item. Any item deemed unsuitable for marking as outlined herein shall be identified to the KO for resolution as to marking requirement. This requirement may be entirely met by existing marking requirements contained within the drawings or specifications cited in this Task order.

Exhibit A SPRBL1-19-R-0059 Page 7 of 11

5.0 PERFORMANCE REQUIREMENTS

Under this Indefinite-Delivery Indefinite-Quantity (IDIQ) contract, the Contractor shall serve as the prime Contractor and shall procure all of the items as ordered by the Government in accordance with this Technical Requirements document.

5.1 Inspection and Testing

The contractor shall maintain a system for the identification of the process, inspection/test status of all NSNs. The contractor shall perform final Inspection and testing on all deliverables in accordance with the contractor's Inspection and Testing Procedures. These inspection reports shall be kept in the shipping container along with spare when shipped to all Branch of Government and depots where the terminal are repaired. A copy of these test records shall be delivered to Product Realization (PRD) Engineer assigned to the terminal and to Contracting Officer Representative (COR) when the deliverables are shipped out to the Government. Equipment and facilities required for inspection and testing shall be the Contractor’s responsibility.

5.2 Quality

The Contractor shall comply with a higher-level quality management system such as the ANSI/ASQ 9001:2015 or AS9100, Quality Management Systems - Requirements, or equivalent in all production facilities involved in this contract. The Contractor shall provide and maintain a comprehensive quality assurance program within its producing/manufacturing facility which addresses Hardware and Software/Firmware Quality. The Contractor shall flow down all quality requirements to sub-Contractors as they apply to procured material and services. The Contractor may change to an alternate Quality Management System during the term of the contract as long as a written request is submitted and approved by the Government.

The Government reserves the right to examine or audit the contractor's Quality Management System and any manufacturing/production processes. The Contractor shall provide the Government the right to make such inspections and audits while the work is in process in order to provide confidence that the project complies with contractual requirements. The Contractor shall provide personnel and facilities to support Government's inspections and audits.

5.3 Hardware Procurement Requirements

The Contractor shall supply all items in accordance with the delivery schedule. Items shall be completed, packaged, shipped, and received at the specified ship to location. Supply Turnaround Time shall be from date of delivery order to the date the item arrives at the Government depot.

5.4 Post Award Orientation Conference

Within 30 calendar days after contract award, a Post Award Orientation Conference will be convened by the PCO.

The conference shall be conducted in accordance with FAR 42.503 procedures. The purpose of the conference is to ensure mutual understanding of the contract requirements and proposed work, review general approaches, schedule and level of effort, and to provide any necessary clarification.

6.0 SECURITY DETAILS

6.1 Security Requirements

The Contractor shall be required to have a SECRET facility clearance with appropriate SECRET safeguarding capability. The contractor will require access to COMSEC information, Restricted Data, Non SCI Intelligence information, and FOUO information. Access to the Security/Program Classification Guide (SCG) is required. In performing this contract, the Contractor shall receive, process and store classified material up to the SECRET level. There will not be a Telecommunications Electronics Material Protected from Emanating Spurious

Exhibit A SPRBL1-19-R-0059 Page 8 of 11

Transmissions (TEMPEST) requirement at the Contractor’s facility. Additional Operations Security (OPSEC) requirements will be provided by the Government IAW AR 530-1, OPSEC. OCONUS performance of this contract will be defined by the Contracting Officer’s Representative (COR). Administrative duties will not require a clearance and shall require investigation for IT duties.

In performing this contract the contractor will receive, send, generate material and fabricate/modify/store classified hardware if applicable. The contractor will be authorized to use the Defense Technical Information Center (DTIC). Use of the Defense Courier Service is authorized. Contractor personnel performing IT sensitive duties are subject to investigative and assignment requirements IAW AR 25-2, AR 380-67 and affiliated regulations.

All contractor personnel who have access to classified information, hardware or software or unclassified contractor written/modified software must be a U.S. Citizen with a final SECRET clearance issued by the U.S.

Government. For all contractors with security clearances, per AR 381-12 Threat Awareness and Reporting Program (TARP), contractor employees must receive annual TARP training by a CI agent or other trainer as specified in 2-4b.

6.2 AT Level I Training

All contractor employees, to include subcontractor employees, requiring access to Army installations, facilities and controlled access areas shall complete AT Level I awareness training within sixty (60) calendar days of the 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 PCO or to the contracting officer, if a PCO is not assigned, within sixty (60) calendar days of completion of training. AT level I awareness training is available at the following website:

https://atlevel1.dtic.mil/at.

6.3 Access and General Protection/Security Policy and Procedures Contractor and all associated sub-contractors employees shall comply with applicable installation, facility and area commander installation/facility access and local security policies and procedures (provided by Government representative). The contractor shall also provide all information required for background checks to meet installation access requirements to be accomplished by installation Provost Marshal Office, Director of Emergency Services or Security Office. The contractor workforce must comply with all personal identity verification requirements as directed by DOD, HQDA and/or local policy. In addition to the changes otherwise authorized by the changes clause of this contract, should the Force Protection Condition (FPCON) at any individual facility or installation change, the Government may require changes in contractor security matters or processes.

6.4 AT Awareness Training for Contractor Personnel Traveling Overseas If applicable, contractor employees shall 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.

6.5 iWATCH Training The contractor and all associated sub-contractors shall brief all employees on the local iWATCH program (training standards provided by the requiring activity ATO). This locally 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 sixty (60) calendar days of contract award and within thirty (30) calendar days of new employees commencing performance, Exhibit A SPRBL1-19-R-0059 Page 9 of 11

6.6 Contractor Employees Access to Government Information Systems All contractor employees who require access to a Government Information System (IS) must be registered in the ATCTS (Army Training Certification Tracking System) at commencement of services and must successfully complete the DOD Information Assurance Awareness prior to access to the IS and then annually thereafter.

6.7 OPSEC Standing Operating Procedure/Plan

The contractor shall develop an OPSEC Standing Operating Procedure (SOP)/Plan within ninety (90) calendar days of contract award, to be reviewed and approved by the responsible Government OPSEC officer, per AR 530- 1, Operations Security. This SOP/Plan will include the Government's critical information, why it needs to be protected, where it is located, who is responsible for it, and how to protect it. In addition, the contractor shall identify an individual who will be an OPSEC Coordinator. The contractor will ensure that this individual becomes OPSEC Level II certified per AR 530-1.

6.8 OPSEC Training

Per AR 530-1, Operations Security, new contractor employees must complete Level I OPSEC training within thirty (30) calendar days of their reporting for duty. All contractor employees must complete annual OPSEC awareness training.

6.9 Information Assurance (IA)/Information Technology (IT) Training All contractor employees and associated sub-contractor employees must complete the DoD IA awareness training before issuance of network access and annually thereafter. All contractor employees working IA/IT functions must comply with DoD and Army training requirements in DoD 8570.01, DoD 8570.01-M and AR 25-2 within six (6) months of employment. The baseline certification as stipulated in DoD 8570.01-M must be completed upon contract award.

7.0 CONTRACT DATA REQUIREMENT LIST (CDRL) DD 1423-1

CDRL Data Line No. DID Identification Title

A001 DI-MISC 80711A Scientific and Technical Reports – Configuration Management

CDRL is on the next page.

Exhibit A SPRBL1-19-R-0059 Page 10 of 11

CDRL A001: Configuration

CONTRACT DATA REQUIREMENTS LIST

(1 Data Item) Form Approved OMB No. 0704-0188

Public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to Department of Defense, Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA. 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503. Please DO NOT RETURN your form to either of these addresses. Send completed form to the Government Issuing Contracting Officer for Contract/PR No. listed in Block E.

A. CONTRACT LINE ITEM NO. B. EXHIBIT C. CATEGORY:

A TDP TM OTHER MISC

D. SYSTEM/ITEM E. CONTRACT/PR NO. F. CONTRACTOR

AN/TSC 156D (Phoenix)

1. DATA ITEM NO. 2. TITLE OF DATA ITEM 3. SUBTITLE 17. PRICE

GROUP

A001 Scientific and Technical Reports Configuration Management

4. AUTHORITY (Data Acquisition Document No.) 5. CONTRACT REFERENCE 6. REQUIRING OFFICE 18. ESTIMATED

TOTAL PRICE

DI-MISC-80711A Tech Requirements, sec 2.1.2 AMEL-LCC-NS

7. DD 250 REQ 9.DIST STATEMENT

REQUIRED

10. FREQUENCY 12. DATE OF FIRST SUBMISSION 14. DISTRIBUTION

N/A N/A ASREQ BLOCK 16 b. COPIES

8. APP CODE 11. AS OF DATE 13. DATE OF SUBSEQUENT

SUBMISSION

a. ADDRESSEE Draft

Final

BLOCK 16

Reg

Repro

16. REMARKS:

Data Item Description DI-MISC-80711A: Delete block 10 instructions entirely and follow instructions in this Technical Requirements. AN/TSC 156D (Phoenix) Hardware Spares.

The Contractor shall prepare and submit a Request for Variance (RFV) for Government review in accordance with this Technical Requirements section for Configuration Management when there is a change or departure from a contractual baseline.

All RFVs for changes shall be submitted for Government review or notification within 5 business days of Contractor approval and prior to presentation of the product for acceptance, but not later than 30 calendar days, of any such product.

The Government shall review, accept, and/or comment on the draft submission in 30 calendar days. The Contractor shall incorporate changes and re-submit within 30 calendar days. The Government will have 30 calendar days to review, accept, or comment on the final submission.

Data shall be submitted and exchanged electronically in Microsoft Office suite of applications (MS Word, Excel, Power Point, Access, and Project). Alternate formats may be allowed subject to Government review and approval.

PCO

AMEL-LCC-NS

FCDD-ISP-CS

15. TOTAL 0 3 0

G. PREPARED BY H. DATE I. APPROVED BY J. DATE

Biruk Shiferaw

FCDD-ISP-CS

General Engineer June 26, 2019

X Kate McDevitt

12 March 2019

DD FORM 1423-1, FEB 2001 PREVIOUS EDITION MAY BE USED. Page 1 of 1 Pages

Exhibit A SPRBL1-19-R-0059 Page 11 of 11

APPENDIX A – NSNS FOR PROCUREMENT

NSN

Count NSN CAGE Mfg PN Nomenclature

1 4130-01-592-8708 06401 7192855-028 Condenser, Refrigeration 2 4130-01-602-9083 06401 7192855-031 Control, Air Conditioner 3 5895-01-521-2206 06401 7193230-003 Antenna Control Unit 4 5895-01-521-5413 06401 7192787-000 Distribution Box 5 5895-01-522-2560 06401 7192752-000 Antenna Control Unit 6 5895-01-534-3253 06401 7092954-000 Converter, Frequency 7 5895-01-534-6124 06401 7192953-000 Converter, Frequency 8 5895-01-590-9749 06401 7192753-006 Control, Communication 9 5920-01-550-5868 06401 8161952-000 Arrester, Lightning 10 5975-01-521-2187 06401 8161583-000 Panel, Electrical-El 11 5985-01-520-9792 06401 7191941-011 Remote Unit, Control 12 5985-01-521-0938 06401 7192826-000 Antenna Subassembly 13 5985-01-521-1714 06401 7192826-002 Antenna Subassembly 14 5985-01-521-1721 06401 7192826-001 Antenna Subassembly 15 5985-01-535-5663 06401 7192826-003 Antenna Subassembly 16 5985-01-535-6924 06401 7192827-001 Antenna Subassembly 17 5985-01-550-9519 06401 7191941-017 Drive, Antenna 18 5996-01-520-9564 06401 7192757-000 Amplifier 19 5996-01-521-2193 06401 7192762-002 Amplifier, Radio Frequency 20 5996-01-521-2204 06401 7192762-001 Amplifier, Radio Frequency 21 5996-01-521-2211 06401 7192762-000 Amplifier, Radio Frequency 22 5996-01-534-6853 06401 7193109-000 KA- HPA (Amplifier, Radio Freq) 23 5996-01-534-9696 06401 7192762-003 Amplifier, Radio Frequency 24 5998-01-521-2197 06401 7191941-005 Circuit Card Assembly 25 6110-01-590-9772 06401 8161646-002 Distribution Box 26 6130-01-520-9796 06401 7184752-002 Power Supply 27 6130-01-591-2301 06401 7184752-005 Power Supply 28 6625-01-668-7295 06401 1000989898 Analyzer, Spectrum 29 7021-01-647-3095 06401 1000397189 Computer, Digital 30 7025-01-600-2132 06401 40012246-000 Interface Unit, Auto 31 7025-01-679-6155 06401 1000169203 Multiplexer, Digital

1.0 APPLICABLE DOCUMENTS
2.0 CONFIGURATION BASELINE
2.1 Part Revisions
2.1.1 Configuration
2.1.2 Departures from Configuration Baseline
3.0 ITEM UNIQUE IDENTIFICATION (UID)
3.1 Unique Identification Marking
3.2 Unique Identification Marking Data Submission Guidance
4.0 PACKAGING
4.1 Wood Packing Material
4.2 Preservation, Packing and Marking Instructions
4.2.1 Part Number Marking
5.0 PERFORMANCE REQUIREMENTS
5.1 Inspection and Testing
5.2 Quality
5.3 Hardware Procurement Requirements
5.4 Post Award Orientation Conference
6.0 SECURITY DETAILS
6.1 Security Requirements
6.2 AT Level I Training
6.3 Access and General Protection/Security Policy and Procedures
6.4 AT Awareness Training for Contractor Personnel Traveling Overseas
6.5 iWATCH Training
6.6 Contractor Employees Access to Government Information Systems
6.7 OPSEC Standing Operating Procedure/Plan
6.8 OPSEC Training
6.9 Information Assurance (IA)/Information Technology (IT) Training
7.0 CONTRACT DATA REQUIREMENT LIST (CDRL) DD 1423-1
CDRL A001: Configuration

Appendix A – NSNs for Procurement

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