Exhibit_A_-_TECHNICAL_REQUIREMENTS.docx

TECHNICAL REQUIREMENTS

Spot Buy of NSN 5985-01-522-2560 Antenna Control Unit

APPLICABLE DOCUMENTS

Military and Federal Standards

Military and Federal Specifications

Component, Chemical Agent Resistant w/Amd 2

System Application Procedures and Quality Control Inspection

Polyurethane, Chemical Agent Resistant

Non-twistable General Specification for

Other Documents

Specification, Specification Number A3286081, dated 01 April 2003

Specification, Specification Number A3286082, date 01 April 2003

Commercial Documents

Reference Designations for

International Trade

Systems-Requirements

Security Documents

CONFIGURATION BASELINE

The applicable Configuration Baselines (CB), for the listed Configuration Item (CI) and/or Computer Software Configuration Item (CSCI), are as listed in the table below.

Obsolescence Reporting

The contractor shall develop the forecasting source data that will enable the identification, forecasting and management of piece part obsolescence impacts and mitigations as a part of the Department of Defense (DoD) Program Managers’ Total System Life Cycle Management responsibilities. This data is planned for use in DMSMS forecasting tools using a common data standard that enhances efficiency across programs that may share the data on common items. The data may be obtained during any program life cycle phase using sources such as the preferred parts list, build-of materials, vendor surveys, inspections, etc. The DMSMS data shall be developed in accordance with this requirement and the CDRL A001 (DD Form 1423) for DI-SESS-81656.

Part Revisions Requirements for Configuration Management.

Product Definition Information. The Product Definition Information describes a product’s performance, functional and physical attributes, including the requirements and design information (specifications, drawings, design descriptions and software). Interfaces, including interfaces with other products, are also documented in the Product Definition Information. The Product Definition Information shall be specified by the Contractor’s Commercial Item Part Number (CIPN).

Configuration Change Process. The contractor shall establish a system for managing the configuration changes to the CIPN baseline.

CIPN Configuration Baseline. The Contractor’s Commercial Item Part Number (CIPN), 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 A3286081 Tactical SHF Satellite Terminal (TSST) Specification A3286082 Quad-Band Satellite Emulator (QBSE) Specification

Configuration. Each CI/CSCI, as developed/built and delivered, shall conform to the cited CB and (if applicable) and any subsequent CB’s that will be made contractually binding by the Procuring Contracting Officer (PCO).

Application Management.

Application Management. In performing Application Management, the Government must assess the impact of design changes to the Configuration Item. The Government is the Configuration Management authority on application management for all external applications and for all Major changes that affect the Commercial Item Part Number (CIPN) specified in paragraph 3.9.3.1. A Major change is defined as any change that will impact any of the following conditions of the CIPN:

(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

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

(h) Impact on test equipment, support equipment and associated software.

(i) Software.

Application Activity. The Government is an Application Activity (AA) for changes that affect the Contractor’s CIPN. The Government does not possess document change authority over the changes affecting the CIPN. As part of the Government’s Application Management process, the Government as AA does have a right to review or be notified of changes made by the Contractor that will affect any of the conditions identified in paragraph 3.9.3.5.1. Any changes that affect these conditions shall be submitted for Government review or notification IAW the procedures outlined below (para 3.9.3.5.3). Configuration changes not directly affecting the configuration baseline conditions identified in paragraph 3.9.3. 5.1 do not require Government review or notification.

Departures from CB. Changes that affect the CIPN conditions cited in paragraph 3.9.3.5.1 shall be submitted for Government review or notification in accordance with this requirement and the B001 DD Form 1423 for DIMISC-80711A. Upon receipt of notification, the Government will review the impact of the change.

CHEMICAL AGENT RESISTANT COATING (CARC) N/A

Paint Colors

Other

Special Instructions

X = Applicable

Antenna Elements, including protective covers, i.e. fiberglass shields.

PACKAGING

Wood Packing Material applicable Wood packing material includes pallets. See DLAD 52.247-9012 Requirements for Treatment of Wood Packaging Material (WPM).

Military Packaging applicable DS7029 and/or DS7033 Preservation, Packing and Marking Instructions

DS7029 - DS7033 LEGEND

The below codes are for special markings:

DS7029 - DS7033

Special Markings

SPRBL1-18-Q-0032 Technical Requirements Exhibit ATEMPLATE

Exhibit A SPRBL1-18-Q-0032 Page 12 of 16 Issued: 24 June 2015

Requirements for Item Unique Identification (IUID). This paragraph prescribes procedures for marking electronic/mechanical items (see Appendix A) with Item Unique Identification (IUID) for all Contractor Repair. This includes both the end item and spare/repair parts that meet the below requirements and the requirements in Section F (PADDS# FA60001) of the contract.

IUID Marking.

Repair items: The contractor shall mark those items as identified by the Government as listed in Appendix A. Items received for repair shall be inspected for IUID markings. Those items where the marking is damaged or missing the contractor shall mark the equipment. When marking requirements are not clearly specified then the contractor shall advise the PCO. 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.

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.

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.

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.

IUID Coding. IUID markings and readability requirements shall comply with MIL-STD-130N.

Symbology markings and the order of priority for marking the hardware shall be in accordance with MIL-STD 130N. First 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.

If the 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.

If items are not described by Government Product Technical Data (i.e. Commercial Items), the contractor shall submit diagrams showing placement and description of the IUID marking and applicable installation and processing instructions for government review and approval IAW with CDRL for DI-MISC-80711A and this PWS.

Per the Department of Defense, Item Unique Identification of Government Property Guidebook, Reporting Government Property In the Possession of the Contractor (PIPC), and Guidance for: Defense Federal Acquisition Regulation (DFARS) 252.211-7007, Item Unique Identification of Government Property, Version 1.0, September 21, 2007.

For new contracts issued after September 13, 2007, DoD will include an Interim Rule, DFARS 252.211-7007, Item Unique Identification of Government Property (DFARS Case 2005-D015), which permanently revises requirements for reporting of PIPC. The interim rule permanently replaces the DD Form 1662 reporting requirements with requirements for DoD contractors to electronically submit, to the IUID registry, the IUID data applicable to PIPC.

It should be understood that in accordance with DFARS 211.274-5, Contract clauses, the clause at DFARS 252.211-7003, Item Identification and Valuation, must be included in any contract that incorporates the clause at DFARS 252.211-7007, Item Unique Identification of Government Property. This is essential to assure there is no ambiguity in the requirements for assigning, registering, reporting and marking PIPC.

The contractor shall maintain an accurate, current list of IUIDs for all repaired items on this contract. Dates of repair, 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 term of this contract.

Correction of Noncompliant Equipment and Technical Data.

Should a conflict exist with existing government technical documentation and the requirements of this PWS, the contractor shall not proceed with the IUID marking until PCO approval is received for the revision.

Government Purchase of IUID Product/Technical Data.

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.

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, PIPC reporting, serial number data reporting at end of contract and the actual marking of hardware, will be included in the base contract price.

SPECIALIZED TESTING

N/A

CONTRACT SECURITY REQUIREMENTS

Anti-Terrorism (AT)/OPSEC

AT Level 1 Training

All contractor employees, to include subcontractor employees, requiring access Army installations, facilities and controlled access areas shall complete AT Level I awareness training within 60 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: https://Jkodirect.jten.mil/ for CAC holders. Non-CAC-holders may go to: http://jko.jten.mil/courses/atl1/launch.html.

Access and General Protection/Security Policy and Procedures

Contractor and all associated sub-contractors employees shall 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. Contractor workforce must comply with all personal identity verification requirements (FAR clause 52.204-9, Personal Identity Verification of Contractor Personnel) 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.

AT Awareness Training for Contractor Personnel Traveling Overseas

US based contractor employees and associated sub-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. US based contractor employees and associated sub-contractor employees will submit an Isolated Personnel Report (ISOPREP) prior to deployment, in accordance with AR 525-28, Personnel Recovery. The contractor is required to fill out the survey on NIPRNET at https://prmsglobal.prms.af.mil/prmsconv/Profile/Survey/start.aspx prior to deployment.

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 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 60 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.

For Contractors 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 contractor’s compliance with combatant commander and subordinate task force commander policies and directives.

OPSEC Standing Operating Procedure/Plan

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 will 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.

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. Level I OPSEC training is available at the following website: http://cdse.edu/catalog/elearning/GS130.html (Duration: 45 minutes).

Threat Awareness and Reporting Program (TARP)

Per AR 381-12. Contractor employees must receive annual TARP training by a CI agent or other trainer as specified in 2-4b

Handling/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.

IT/IA Training Certification

Per DoD 8570.01-M (Ch4) , DFARS 252.239.7001 and AR 25-2, the contractor employees supporting Cybersecurity/IT functions shall be appropriately certified upon contract award. The baseline certification as stipulated in DoD 8570.01-M (Ch4) must be completed upon contract award.

For Contractor Not Eligible for CAC, but Requires Access to DoD Facility or Installation

Contractor and all associated sub-contractors employees shall comply with adjudication standards and procedures using the National Crime Information Center Interstate Identification Index (NCIC-III) and Terrorist Screening Database (TSDB) (Army Directive 2014-05/AR 190-13), applicable installation, facility and area commander installation/facility access and local security policies and procedures (provided by government representative), or, at OCONUS locations, in accordance with status of forces agreements and other theater regulations.

For Contractors Authorized to Accompany the Force

DFARS Clause 252.225-7040 (DFARS Clause 252-225-7995 for CENTCOM), Contractor Personnel Authorized to Accompany U.S. Armed Forces Deployed Outside the United States. The clause shall be used in solicitations and contracts that authorize contractor personnel to accompany US Armed Forces deployed outside the US in contingency operations; humanitarian or peacekeeping operations; or other military operations or exercises, when designated by the combatant commander. The clause discusses the following AT/OPSEC related topics: required compliance with laws and regulations, pre-deployment requirements, required training (per combatant command guidance), and personnel data required.

In the event of a discrepancy between the signed DD 254 Contract Security Classification Specification, included as an attachment to the solicitation/contract, and the language in this section, the signed DD 254 information shall take precedence.

CONTRACT DATA REQUIREMENT LIST (CDRL) DD 1423-1

CDRL List

Individual CDRLs

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.

TDP TM OTHER SESS

AN/TSC-156 Phoenix

17. PRICE GROUP

A001

18. ESTIMATED TOTAL PRICE

INSERT

IN

LT

b. COPIES

SECT. B

8. APP CODE

SUBMISSION

a. ADDRESSEE

Draft Final

Reg

Repro

16. REMARKS:

Item 12: Delivery of DMSMS Data shall be within TBD days after award of contract. Subsequent reports to be submitted semiannually (every 180 days) until conclusion of contract. Government has 60 days to review and determine acceptance.

See DI-SESS-81656 for DMSMS Data Format and Content requirements.

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

If the CDRL Data Deliverable is priced and is not NSP (Not Separately Priced), then an electronic DD Form 250 will be required via the Wide Area Workflow website in order for the contractor to receive payment for the data deliverable (see section G of the Contract). E-mail notification is required with any electronic submission.

AMSEL-RDER-PRC-CM

AMSEL-LC-LEO-EIE

15. TOTAL

James Allen /s/ Electronics Engineer 443-395-6162

Chief, Comm Systems Branch 443-395-8153 01 Aug 2017

CONTRACT DATA REQUIREMENTS LIST

(1 Data Item) Original Form Approved

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.

TDP X TM OTHER

AN/TSC-156 Phoenix

17. PRICE GROUP

18. ESTIMATED TOTAL PRICE

INSERT

IN

LT

b. COPIES

SECT. B

SUBMISSION

a. ADDRESSEE

Final

SEE ITEM 16

16. REMARKS: Data Item Description DI-MISC-80711A: Delete block 10 instructions entirely and follow instructions in (Request For Change documents (RFCs)).

The contractor shall prepare and submit RFCs for Government review in accordance with the PWS section for Configuration Management when there is a Major change to or departure from a contractual baseline. All RFCs for Major changes shall be submitted for Government review or notification within 5 working days of Contractor approval and prior to presentation for acceptance, but not later than 30 days, of any such product.

All deliveries shall be in digital format. All digital files shall be provided both by electronic submission, e.g., e-mail, FTP, etc., as arranged with the requiring office, and also by CD ROM readable by computers running Microsoft Office 2000 and Office XP suite of applications (MS Word, MS Excel, MS PowerPoint, and MS Project, etc.).

Alternative delivery media may be discussed with the Contracting Officer prior to delivery.

AMSEL-RDER-PRC-CM

PCO

ACO

QAR

James Allen /s/ Electronics Engineer 443-395-6162

Chief, Comm Systems Branch 443-395-8153 01 Aug 2017

Based upon DD Form 1423-1, 1 Jun 90

CONTRACT DATA REQUIREMENTS LIST

(1 Data Item) Original Form Approved

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 Advise 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.

TDP TM OTHER MISC

AN/TSC-156 Phoenix

17. PRICE GROUP

18. ESTIMATED TOTAL PRICE

DI-MISC-80711A

(see Block 16)

INSERT

IN

LT

b. COPIES

SECT. B

SUBMISSION

a. ADDRESSEE

Final

16. REMARKS:

Item 4: Delete Block 10.2 of Data Item Description (DID) and prepare in accordance with this CDRL & the Statement of Work.

Item 12: Delivery of draft shall be 120 DAC. Government has 30 days to review/comment.

Item 13: Delivery of final shall be 30 days after receipt of Government comments. Government has 60 days to determine acceptance. Contractor to submit DD250 upon acceptance of IUID Marking Diagram/Instructions.

Item 14: All digital files will be provided both by electronic submission, e.g., e-mail, FTP, etc., as arranged with the requiring office, and also by CD ROM, readable by computers running Microsoft Windows.

If the CDRL Data Deliverable is priced and is not NSP (Not Separately Priced), then an electronic DD Form 250 will be required via the Wide Area Workflow website in order for the contractor to receive payment for the data deliverable (see section G of the Contract). E-mail notification is required with any electronic submission.

AMSEL-RDER-PRC-CM

James H Allen /s/ Electronics Engineer 443-395-6162

Chief, Communications Systems Branch 443-395-8153 01 Aug 2017 image1.wmf image2.wmf