Attch_0001_FINAL_TROPO_PWS_09Mar2018_Amend_0003.pdf

UNCLASSIFIED

AN/TRC-XXX

Troposcatter Transmission (TROPO) System

Performance Work Statement (PWS)

February 2018

Prepared by:

Project Manager, Tactical Network

ATTN: SFAE-CCC-TN

Aberdeen Proving Grounds, MD 21005

DISTRIBUTION A. Approved for public release: distribution unlimited. Other request for this document shall be referred to PEO C3T/PM Tactical Network, 6010 Frankford St., Aberdeen Proving Grounds, MD 21005

1. General

1.1. Scope

This Performance Work Statement (PWS) specifies the tasks and work requirements for the acquisition of all production equipment, engineering services, integration, testing, logistics, training, maintenance, configuration management and support services required to support the

Troposcatter Transmission system (TROPO). This requirement also includes the identification of spares, repairs, logistics documentation and technical refreshment proposals.

1.2. Background

The PM Tactical Network communications network provides the Army Warfighter with voice, data and full motion video imagery to enable decisive action in the tactical environment and into the Sustaining Base, utilizing primarily Commercial Off-the-Shelf (COTS) equipment. The PM

Tactical Network TROPO is part of the modernization efforts needed for the Army’s Beyond

Line of Sight (BLOS) expeditionary network communications. The modernization of the Army networks includes increasing network capacity, improving system interoperability and adding flexibility to the network for the tactical formation. PM Tactical Network has a need to procure the next generation of TROPO system by way of hardware, spares, logistics, engineering support and other services. The TROPO system is a compact, portable and rapidly deployable tactical solution that supports tactical military missions by providing a critical communications solution.

The system shall be easy to install and operate, and work in networked environments.

1.3. Order Type

1.4. The effort shall utilize delivery and/or task orders issued as Firm Fixed Price (FFP) and/or Cost Plus Fixed Fee (CPFF).

1.5. Period of Performance / Place of Performance.

The period of performance of this contract shall not exceed ten (10) years from date of award, with a five (5) year base period and a five (5) year option, against which delivery orders or task orders can be written. All equipment/material procurements, deliveries, installation, testing, training and final system acceptance shall be accomplished within the contract period of performance. It is anticipated that performance will take place at various Continental United

States (CONUS) or Outside Continental United States (OCONUS) Contractor and Government sites.

1.6. Inspection and Acceptance

1.6.1. Inspection and Acceptance shall be at Origin/Destination (based on CLIN direction) by a delegated US Government Representative from each service for all equipment and materials procured in CONUS and delivered under this contract.

1.6.2. Origin is defined as the Contractor’s facilities in CONUS and Destination shall be at a government owned facility as designated by contract.

1.6.3. Final Inspection and Acceptance at Origin will be IAW the Government approved

Acceptance Test Plan.

1.6.4. USMC Unique Requirements:

1.6.4.1 The Contractor shall forward copies of signed DD250s (all Key Supporting

Documentation KSDs) to Program Office.

1.6.4.2 Defense Contract Management Agency (DCMA) representative shall inspect for compliance with USMC “Gold Standard” marking requirement per Naval message

DTG:201546Z Dec 16.

1.7. Government Contracting Officer Representative

The Government Contracting Officer Representative (COR) for this effort:

Name: Michael Wang

Organization: PM TACTICAL NETWORK

Address: 6010 Frankford Street

Aberdeen Proving Ground, MD 21005

Email: michael.wang3.civ@mail.mil

Phone: (443) 395-6593

1.8. GOVERNMENT FURNISHED EQUIPMENT (GFE), MATERIAL (GFM),

INFORMATION (GFI), SOFTWARE (GFS)

1.8.1. The Government may furnish certain items of hardware and software for the performance of this contract. The Contractor shall provide the following report: Status of Government

Furnished Equipment (GFE), GFE Inventory List, in accordance with (IAW) Contract

Data Requirements List (CDRL) A001 and DI-MGMT-80269 as required. Submission of this report shall begin one month after receipt of GFE.

1.8.2. Access to TACTICAL NETWORK Test Bed/Lab assets located at Aberdeen Proving

Grounds (APG) and other facilities shall be available if requested and coordinated with the COR to support efforts included in this delivery order. In addition, GFE, GFM and

GFI may be provided to support future efforts.

1.8.3. The Contractor shall be accountable for all GFE IAW Federal Acquisition Regulation

(FAR) Subpart 45.5 and FAR Clause 52.245-1. Additions, deletions, or substitutions may be initiated at the direction of the Contracting Officer. These changes shall be subject to equitable adjustment under the terms of FAR Clause 52.245-1.

1.8.4. Upon discovery of defective/broken/unsatisfactory GFE equipment, notification shall be submitted to government COR within 5 business days. Return/repair/replace procedures shall be provided to the contractor once the government is notified of the issue. In some cases, authorization may be given to the contractor for limited repairs on site.

1.9. General Security

The Contractor shall be required to have a SECRET facility clearance with appropriate SECRET safeguarding capability. The Contractor will not require access to Communications Security

(COMSEC) information, Sensitive Compartmented Information (SCI) and Non-SCI, North

Atlantic Treaty Organization (NATO), Foreign Government Information, and For Official Use

Only (FOUO) information. Access to the Warfighter Information Network - Tactical Increment

1 (WIN-T Inc 1) Security Classification Guide (SCG) dated 15 Feb 2012 is required. The

Government will sponsor the Contractor with access to the Secret Internet Protocol Router

Network (SIPRNET) at Government’s facility. 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 Transmissions

(TEMPEST) requirement at the Contractor’s facility. Additional Operations Security (OPSEC) requirements will be provided by the Government IAW AR 530-1, OPSEC. Use of the Defense

Courier Service is authorized. 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.

Foreign sub-Contractor participation will be handled IAW AR 380-10 (Technology, Transfer, Disclosure of Information & Contacts with Foreign Representatives), CECOM Regulation 380-

16 (Industrial Security), National Disclosure Policy, and affiliated regulations and/or supplements (DTM) 09-019, “Policy Guidance for Foreign Ownership, Control, or Influence

(FOCI),” 2 September 2009.

1.10. PUBLIC RELEASE

1.10.1. The Contractor is reminded that information identified as "UNCLASSIFIED" is not equivalent to "Approved for Public Release". Information covered by this contract is subject to arms control and export restrictions that may limit distribution. The Contractor must verify that proposed public releases do not contain information subject to control under the International Traffic in Arms Regulations (ITAR), the Militarily Critical

Technologies List (MCTL), the Department of Commerce Controlled Commerce List

(CCL), or other technology transfer statutes and regulations. The Contractor is reminded that DoD Regulation and US Statute impose severe criminal penalties for unauthorized transfer of controlled unclassified information (CUI). The Contractor must obtain approval for all public releases of information covered by this contract through the

Government Contracting Activity (GCA) prior to disclosure.

1.10.2. The term "information" applies to, but is not limited to, articles, speeches, photographs, brochures, advertisements, displays, and presentations on any phase of this contract.

1.10.3. It is the responsibility of the Contractors to screen all information submitted by them or to them for determination of public release to ensure that it is both unclassified and technically accurate. Letters of transmittal must contain certification to this effect.

Copies of material may not be released outside official channels until the review process is complete and approval has been granted. If information is found during the review process that is suspected of being classified, notification should be given to the holders of the document as to the degree of protection required. When doubt exists concerning the classified status of a proposed release pertinent to this contract, the Component Office of

Primary Responsibility (OPR) for the Security Classification Guide(s) associated with this contract (see DD 254) will render the final decision. The material submitted for review must include a valid suspense date, if applicable.

1.10.4. Only information that has been reviewed and approved for public release by the GCA may be released. Information for public release that is revised or developed after initial approval must be resubmitted for review and further processing as outlined above.

1.10.5. Material requiring an export license shall not be entered into Security/Policy Review channels for public release approval in order to circumvent the licensing requirements of the Departments of State and Commerce. Participants shall comply with export laws and regulations relating to the exporting of items/information under this contract.

1.10.6. Contemplated visits of public media representatives shall receive prior coordination and approval from the GCA.

2. APPLICABLE DOCUMENTS

The following documents specified form a part of this contract to the extent specified herein.

The most recent revision of the referenced document at the time of contract shall be used unless otherwise specified. The documents below, as may be updated, amended, or replaced from time to time, are some of the documents that shall apply to this order. Nothing in this document, however, supersedes applicable laws and regulations unless a specific exemption has been obtained.

2.1. Specifications, Standards, Handbooks (MIL)

2.1.1. MIL-PRF-29612B Training Data Products, dated 31 Aug 2001

2.1.2. MIL-PRF-63002L Requirements for Preparation of Modification Work Orders, 29

Apr 2013

2.1.3. MIL-STD-129R Military Marking for Shipment and Storage, 18 Feb 2014

2.1.4. MIL-STD-130N w/chg 1 Identification Marking of U.S. Military Property, dated 16 Nov 2012

2.1.5. MIL-STD-196F Joint Electronics Designation System, dated 11 Sep 2013

2.1.6. MIL-STD-882E Department of Defense Standard Practice for System Safety, dated

11 May 2012

2.1.7. MIL-STD-1472G Human Engineering, dated 11 Jan 2012

2.1.8. MIL-STD-1629A Procedures for Performing a Failure Mode Effects and Criticality

Analysis, 24 Nov 1980

2.1.9. MIL-STD-3100A Technical Data Packages, 26 Feb 2013

2.1.10. MIL-STD-40051-2C Preparation of Digital Technical Information for Page-Based

Technical Manuals (TMs), dated 15 Dec 2015

2.1.11. MIL-HDBK-61A Configuration Management Guidance, 7 Feb 01

2.1.12. MIL-HDBK-454B General Guidelines for Electronic Equipment, dated 15 Apr 2007

2.1.13. MIL-HDBK-502A Product Support Analysis, 8 Mar 2013

2.1.14. MIL-HDBK-1222F Guide to the General Style and Format of U.S. Army Work

Package TMs, dated 15 Dec 2015

2.1.15. MIL-HDBK-2155 Failure Reporting, Analysis and Corrective Action System, dated

11 Dec 1995

2.1.16. MIL-STD-188-164B Interoperability of SHF Satellite Communication Terminals, dated

23 March 2012.

2.1.17. Department of Defense Joint Software Systems Safety Engineering Handbook, dated 27

August 2010.

Above referenced documents available at http://quicksearch.dla.mil/

2.2. Other Government Documents

2.2.1. Department of Defense (DoD) Regulations

http://quicksearch.dla.mil/

DFARS 252.211-7003 Item Identification and Valuation, Jun 05, available at http://www.acq.osd.mil/dpap/dars/dfars/index.htm

2.2.2. Department of Defense Directives (DODD)

DoDD 5220.22-M National Industrial Security Program Operating Manual, dated 28 Feb 06, available at http://www.dtic.mil/whs/directives/

2.2.3. RISK MANAGEMENT FRAMEWORK

https://rmf.org/index.php/rmf-in-the-department-of-defense-dod

2.3. DoD Manuals, Documents and Memos

2.3.1. DoD 4100.39-M Federal Logistics Information System (FLIS) Procedures Manual, dated Oct 2010, available at http://www.dtic.mil/whs/directives/corres/html/410039m.html

2.3.2. DoDI 5200.39 Critical Program Information (CPI) Protection within the DoD, dated 28

May 2015

2.3.3. DoDI 8500.01 Cybersecurity, dated 14 Mar 2014

2.3.4. DoDI 8510.01 Risk Management Framework for DoD Information Technology (IT), dated 12 Mar 2014

2.3.5. DoDD 5200.01 DoD Information Security Program, dated 21 Apr 2016

2.3.6. DoDD 5220.22 National Industrial Security Program (NISP), dated 18 Mar 2011

2.3.7. DoDD 8570.01 Information Assurance Workforce Improvement Program, dated

10 Nov 2015

2.3.8. DA PAM 25-33 User’s Guide for Army Publications and Forms, dated 15 Sep 1996

2.3.9. DA PAM 700-56 Logistics Supportability Planning and Procedures in Army

Acquisition, 21 Apr 06, available at http://www.army.mil/usapa/epubs/

2.3.10. DA PAM 700-142 Instructions for Type Classification Materiel Release, Fielding and

Transfer, 1 JUL 2014

2.3.11. DA PAM 738-751 Functional User’s Manual for the Army Maintenance Management

System – Aviation, dated 28 Feb 2014

2.3.12. IUID Guide IUID: Department of Defense Guide to Item Unique Identification (IUID)

Assuring Valuation, Accountability and Control of Government Property, Version 1.6, 1

Jun 06, available at http://www.acq.osd.mil/dpap/pdi/uid/index.html

2.3.13. USMC Unique Documents:

2.3.13.1 DTG 201546Z Dec 16 Interim Guidance for Reporting and Correcting Identification

Plate Discrepancies for Accountable Property (can be provided upon request)

2.4. PEO C3T – Performance Specifications

2.4.1. Refer to Appendix A Performance Specification for the Troposcatter

Transmission system when required by the Government.

2.5. Army Regulations / Marine Corps

2.5.1. AR 25-2 Information Assurance, Rapid Action Revision (RAR) dated 23 Mar 2009 http://www.acq.osd.mil/dpap/dars/dfars/index.htm http://www.dtic.mil/whs/directives/ https://rmf.org/index.php/rmf-in-the-department-of-defense-dod http://www.acq.osd.mil/dpap/pdi/uid/index.html

2.5.2. AR 73-1 Test and Evaluation Policy, dated 1 Aug 2006

2.5.3. AR 380-40 Policy for Safeguarding and Controlling COMSEC Material, RAR dated

24 Apr 2013

2.5.4. AR 385-16 System Safety Engineering Management, dated 13 Aug 2013

2.5.5. AR 700-127 Integrated Product Support, 7 Oct 2014

2.5.6. AR 700-142 Type Classification, Materiel Release, Fielding and Transfer, 2 JUN 2015

2.5.7. AR 725-50 Requisitioning, Receipt, and Issue System, 15 Nov 1995

2.5.8. AR 750-1 Army Materiel Maintenance Policy, 12 Sep 2013

2.5.9. Above referenced documents available at http://www.army.mil/usapa/epubs/

2.5.10. USMC Unique Documents:

2.5.10.1 MCO 5215.17D Marine Corps Technical Publications Management

2.5.10.2 MCO 4790.25 Ground Equipment Maintenance Program

2.5.10.3 MCO 1553.1B The Marine Corps Training and Education System

2.5.10.4 MCO 4400.150 Consumer-Level Supply Policy.

2.5.10.5 TECHNICAL MANUAL: CARGO HANDLING MANUAL V-22 TILTROTOR

Publication A1-V22AB-CLG-000, 1 August 2015

2.5.10.6 NAVMC 1553.1A Marine Corps Instructional Systems Design/Systems Approach To

Training And Education Handbook

2.5.10.7 Above referenced documents available at:

http://www.marines.mil/News/Publications/ELECTRONIC-LIBRARY/

2.6. TRADOC Regulations

2.6.1. TRADOC Regulation 350-70 Army Learning Policy and Systems, dated 6 Dec 2011, available at http://www-tradoc.army.mil/tpubs/index.htm

2.7. Non-Government Documents

2.7.1. UL 60950-1 Safety of Information Technology Equipment, Second Edition, dated 27

Mar 2007, available at http://www.ul.com/

2.7.2. UL 969 Standard for Marking and Labeling Systems, Fourth Edition, dated 19 Sep

2014, available at http://www.ul.com/

2.7.3. ANSI/ISO 8632.1-4:1999 Computer Graphics Metafile for the Storage and Transfer of Picture Description Information Parts 1-4, available at http://www.itl.nist.gov/fipspubs/

2.7.4. ANSI/HFES 200 Human Factors Engineering (HFE) of Software User Interfaces,

2.7.5. NAS411, NAS411-1 Hazardous Materials Management Program, dated 30 Sep

2013, available at http://quicksearch.dla.mil/

2.7.6. SEI CMMI 1.3 Carnegie Mellon Software Engineering Institute, Capability

Maturity Model Integration (CMMI), Version 1.3, dated Nov 2010, available at http://www.sei.cmu.edu/reports/10tr033.pdf http://www.army.mil/usapa/epubs/ http://www.marines.mil/News/Publications/ELECTRONIC-LIBRARY/ http://www-tradoc.army.mil/tpubs/index.htm http://www.ul.com/ http://www.ul.com/ http://www.itl.nist.gov/fipspubs/ http://quicksearch.dla.mil/ http://www.sei.cmu.edu/reports/10tr033.pdf

2.7.7. SAE-GEIA-HB-0007-B Logistics Product Data Handbook, dated 01 Feb 2014

2.7.8. SAE-GEIA-STD-0007-B Logistics Product Data, dated 01 May 2013

2.7.9. SAE-GEIA-STD-0009 Reliability Program Standard for Systems Design, Development and Manufacturing, dated 01 Aug 2008

2.7.10. SAE TA-HB-0007-1 Logistics Product Data Reports Handbook, dated 01 May 2013

2.7.11. SAE J1739 Potential Failure Modes and Effects Analysis, 01 Jan 2009

2.7.12. ASTM D3951-15, Standard Practice for Commercial Packaging, dated 2015

3. REQUIREMENTS

This contract is to procure both hardware and services. The Contractor shall perform all tasks required and delineated in this PWS to manufacture, integrate, test, certify, document, deliver and support the systems. The Contractor shall design, produce, assemble, integrate, configure, test, certify, document, sustain and deliver Tactical Network TROPO systems per this PWS and

Performance Specification (PSPEC) as detailed in Appendix A.

3.1. Equipment

The Contractor shall produce, assemble, integrate, configure, test, and deliver all TROPO equipment per the PSPEC detailed in Appendix A and best commercial practices. The

Contractor shall ensure that the TROPO equipment, when assembled per the agreed upon architecture, meets the requirements of Specifications detailed in Appendix A and is of a design which has successfully passed Government test requirements outlined in this PWS and the

PSPEC detailed in Appendix A.

The Contractor shall provide hardware, software, initial spare parts, ancillary items (cabling, connectors), deliverable data, and applicable licenses associated with each of the TROPO equipment as described in the PSPEC detailed in Appendix A and this PWS as ordered by the

Government. All services required to provide for delivery of these systems and equipment shall be included in the firm fixed prices for these items.

The Contractor shall provide the TROPO equipment when purchased either individually or as part of a system. All TROPO deliveries shall include all hardware (including cables), software, spares, ancillary items, device configurations, operation and maintenance manuals, and applicable licenses as defined in Section B of this acquisition.

3.2. PROGRAM MANAGEMENT AND SYSTEM ENGINEERING

The Contractor shall provide for coordination and control of the overall tasks and efforts to ensure that appropriate contract requirements are met, resources are safeguarded, laws and regulations are followed, and reliable data are obtained, maintained, and fairly disclosed through applicable contract data requirements.

3.2.1. Program Management

3.2.1.1 Program Manager

The Contractor shall establish a single management focal point, the Program Manager, to accomplish the administrative, managerial and financial aspects of this contract. The Contractor shall establish and maintain program management practices throughout the period of performance. Program management practices shall provide visibility into the Contractors’ organization and techniques used in managing the program, specifically subContractor and data management. Documentation identified in this PWS shall be readily available to Government representative(s) during planned visits.

3.2.1.2 SubContractor Management

The Contractor is responsible for performance of requirements delineated in this PWS and shall institute appropriate management actions relative to subContractor performance. Requirements that are contractually specified shall apply to subContractor performance; however, the

Contractor shall be accountable for compliance from its subContractors and is responsible for ensuring all deliverable products comply with the contract requirements. Contractor will ensure subContractors meet all FAR requirements that are applicable.

3.2.1.3 Data Management

The Contractor shall utilize a single, centralized system for management of all data required under this contract. Specific data management functions shall include schedule for deliverables, maintenance of deliverables, and distribution and delivery of data products. The Contractor shall gain access to the Government designated site and use it to upload all deliverables as specified.

Government use of any data management system shall not require installation of client software on Government computer systems. The Contractor shall ensure all data is centrally available for

Government review.

3.2.1.4 Risk Management

The Contractor’s shall develop a Risk Management Plan. The Contractor shall ensure risk management is an integral part of the systems engineering process and the overall program management effort. Risks shall be presented to the Government Program Office.

3.2.1.5 Integrated Master Schedule (IMS)

The Contractor shall develop an IMS, which shall include scheduling details for material delivery, integration, testing and logistics support IAW CDRL A002, Integrated Master Schedule

(DI-MGMT-81861A). The IMS shall be used by the Government and Contractor to verify attainability of contract objectives, to evaluate progress toward meeting program objectives, and to integrate the program schedule activities with all related components. Any other schedules that may be generated during the contract shall not conflict with the IMS. The IMS shall integrate all significant events, deliverables and deliveries required. All events shall be expressed as ‘not later than’ calendar dates. The Prime Contractor’s and SubContractors’ schedules shall be fully integrated in the IMS.

The Prime Contractor is required to include significant external interfaces and critical items from suppliers, teammates, or other detailed schedules that depict significant and/or critical elements and Government furnished equipment or information dependencies for the entire contractual effort in a single integrated network. The determination of significant and critical shall be agreed to by the Government. When subContractor schedule data reflects a different status date than the prime Contractor’s schedule status date, these status dates shall be described in the analysis section of the IMS.

The IMS shall contain a monthly analysis that includes but is not limited to the changes to the schedule assumptions, schedule progress to-date, variances to the baseline schedule, causes for the variances, potential impacts and recommended corrective actions to minimize schedule delays. The analysis shall also identify potential problems and an assessment of the critical path and near-critical paths. The Contractor shall provide an explanation for any deviation that affects the critical path, as well as a description of the corrective action to be taken. Thresholds for reporting other significant variances to the baseline schedule and near-critical paths shall be specified in the CDRL. These thresholds will be mutually agreed upon by the Government and

Contractor. The IMS shall be analyzed and submitted with the monthly analysis. The Contractor shall perform a schedule risk assessment at major events. The assessment shall be included in the monthly analysis.

At the time of RFP submission, the Contractor shall propose the structure of the IMS, significant external interfaces, frequency of Schedule Risk Assessment (SRA), thresholds for reporting significant variances, and other details deemed necessary after contract award. The Contractor may choose the delivery format, however Microsoft Project is preferred.

3.2.1.6 Contract Work Breakdown Structure

The Contractor shall provide for a Level 3 Contract Work Breakdown Structure (CWBS) and dictionary. The Contractor shall use the CWBS as the framework for planning, budgeting, and reporting program status, cost, and schedule to the Government. SubContractor data shall be incorporated into the Contractor’s CWBS.

3.2.1.7 Contract Performance Report

3.2.1.7.1 The Contractor shall continuously monitor the technical performance of this contract, and all subcontracts, and deliver to the Government a quarterly assessment report IAW Data Item A003, Contract Performance Report (DI-

MGMT-81861A). This report shall convey the status of Contractor activity during the previous month as well as cumulative contract performance.

Technical reviews shall address all areas concerning technical status/progress, testing/plan/procedures, architecture, HFE, training, technical documentation, reliability and all else relating to technical performance. The performance report as a minimum shall discuss:

a) Significant accomplishments and issues that arose during the reporting period

b) Projected activities for the following and subsequent periods

c) SubContractor performance when applicable

d) Program risks and mitigation efforts (technical, supply chain, cost & schedule)

e) Status of performance payments, as applicable

f) Dates and quantities of any material deliveries

g) Any general meetings that occurred with the Government or End User representatives during the reporting period

3.2.1.8 Program Meetings

The Contractor shall participate in quarterly program reviews which can be held either in the

Contractor’s facility or at APG, MD. In addition, the Contractor shall participate in a weekly teleconferences to review program status with the program office.

3.2.1.9 Contractor Manpower Reporting

The Contractor shall comply with the following Manpower Reporting requirements:

The Office of the Assistant Secretary of the Army (Manpower & Reserve Affairs) operates and maintains a secure Army data collection site where the Contractor will report ALL Contractor manpower (including subContractor manpower) required for performance of this contract. The

Contractor is required to completely fill in all the information in the format using the following web address: https://cmra.army.mil.

The required information for the Manpower Reporting includes:

a) Contracting Office, Contracting Officer, Contracting Officer’s Technical

Representative;

b) Contract number, including task and delivery order number;

c) Beginning and ending dates covered by reporting period;

d) Contractor name, address, phone number, e-mail address, identity of Contractor employee entering data;

e) Estimated direct labor hours (including subContractors);

f) Estimated direct labor dollars paid this reporting period (including subContractors);

g) Total payments (including subContractors);

h) Predominant Federal Service Code (FSC) reflecting services provided by

Contractor (and separate predominant FSC for each subContractor if different);

i) Estimated data collection costs;

j) Organizational title associated with the Unit Identification Code (UIC) for the

Army Requiring Activity (the Army Requiring Activity is responsible for providing the Contractor with its UIC for the purposes of reporting this information);

k) Locations where Contractor and subContractors perform the work (specified by zip code in the United States and nearest city, country, when in an overseas location, using standardized nomenclature provided on website);

l) Presence of deployment or contingency contract language; and

m) Number of Contractor and subContractor employees deployed in theater this reporting period (by country).

As part of its submission, the Contractor will also provide the estimated total cost (if any) incurred to comply with this reporting requirement. Reporting period will be the period of performance not to exceed 12 months ending 30 September of each Government fiscal year and must be reported by 31 October of each calendar year. Contractors filing their Contractor

Manpower Reports will receive immediate e-mail confirmation that their reports have been received in the system. This should facilitate final payment to Contractors and expedite contract closeout. Administrative contracting staff should accept this confirmation as proof of completion of this contract deliverable. The Contractor Manpower Reporting Application (CMRA) web site maintains a “Frequently Asked Questions and Answers” https://cmra.army.mil/ that is updated periodically. Any technical or implementation questions not addressed on this site can be https://cmra.army.mil/ discussed and coordinated through the CMRA Help Desk at 703-377-6199, or https://cmra.army.mil.

3.2.1.10 Contractor Monthly Cost Reporting

The Contractor shall submit Monthly Cost Reports IAW the requirements outlined in CDRL

A004 Monthly Cost Reporting (DI-MGMT-81466A).

The monthly cost report shall have the following breakout of cost incurred to date:

a) Labor by Functional Area (Contractor will be required to provide Functional Area

Definitions)

b) Material (Hardware)

c) Travel

d) ODC

The contractor may report by Contractor Work Breakdown Structure (CWBS) or CLIN; however the Government reserves the right to reject any format provided. Monthly Cost Reports shall be submitted and exchanged electronically, in Microsoft ® Office 2000 (or later) product suite.

3.2.1.11 Post Award Conference

The Government intends to convene a post award conference no later than 30 days after contract award. The Contracting Officer shall notify the Contractor of the specific date, the CONUS location in the vicinity of Aberdeen Proving Ground, MD, and the agenda of the post award within 10 days of contract award.

3.2.2. System Engineering

3.2.2.1 Engineering Support

3.2.2.1.1 Systems Engineering

The Contractor shall provide Systems Engineering support for all activities performed under this

PWS. The Contractor shall designate a Systems Engineer who shall possess sufficient knowledge and authority to manage, direct, execute and control all engineering elements of the contract.

3.2.2.1.2 Cyber Security

The Contractor shall provide Cyber Security support for all Contractor activities performed under this PWS. The Contractor shall designate a Cyber Security Lead to manage and execute the Cyber Security related tasks in this PWS.

3.2.2.1.3 Test and Evaluation

The Contractor shall provide Test and Evaluation support for all activities performed under this

PWS. The Contractor shall support technology insertion testing relative to emerging

Current/Future Force Networks requirements/capabilities and system upgrades.

3.2.2.2 Systems Engineering Management Plan (SEMP)

The Contractor shall plan and apply a systems engineering approach that optimizes total system performance and minimizes total ownership costs. The systems engineering effort shall address systems engineering activities in the Systems Engineering Management Plan, which describes https://cmra.army.mil/ the program’s overall technical approach, including systems engineering processes, resources, and key technical tasks activities and events along with their Technical Performance Metrics.

These shall be integrated with the program management control efforts, including the IMP, IMS, technical performance measures, and the cost/schedule reporting system. The Contractor shall provide a System Engineering Management Plan that describes the Contractor’s overall technical approach, including processes, resources, and metrics for achieving the work described in this

PWS. The SEMP shall be submitted in accordance with CDRL A005 SEMP.

3.2.2.3 Technical Reviews

3.2.2.3.1 Technical Reviews

The Contractor shall support Test Readiness Reviews and System Verification Reviews by providing system subject matter expertise and respond to Requests for Information requiring technical information and analyses.

The Contractor shall prepare an agenda for each technical review.

The Contractor shall prepare minutes for each technical review.

3.2.2.4 Technical Review Materials

The Contractor shall prepare review materials as required for each technical review. The

Contractor shall deliver a complete indentured Bill of Materials representing the system’s initial

Product Baseline in accordance with CDRL A006 iBOM.

The Contractor shall deliver a Technical Data Package representing the system’s initial Product

Baseline in accordance with CDRL A007 Product Drawings/Models and Associated Lists for the

Technical Reviews.

The Contractor shall deliver Interface Control Documents to support evaluation of the system’s initial Product Baseline in accordance with CDRL A011 (DI-SESS-81248B) ICDs for the

Technical Reviews.

3.2.2.5 Physical Configuration Audit (PCA)

The developer shall facilitate Physical Configuration Audits conducted by the Government in accordance with the program schedule at a date mutually agreed upon by the Government and the Contractor. The Contractor shall provide support for the PCA in the form of facilities, tools, and technical personnel as requested by the Government audit chair, the production representative system that has successfully passed production acceptance, and at least one complete draft copy of the final drawing package, with all corrections from the In-Process

Technical Drawing Review incorporated. The Contractor shall ensure the reassembly and testing of all audited systems in compliance with performance and production requirements. The

Contractor shall provide corrective actions for all discrepancies, for Government approval. Upon approval of the discrepancies the Contractor shall correct all of the discrepancies in accordance with the Government approved corrective action.

The Contractor shall prepare a PCA Summary Report at the culmination of the PCA in accordance with CDRL A009 (DI-SESS-81022D) PCA Report for each audit.

The Contractor shall prepare an agenda for each audit.

The Contractor shall prepare minutes for each audit.

3.2.2.6 Technical Analyses

The Contractor shall conduct the following Systems Engineering Studies and Analysis if requested by the Government:

Evaluation of new technologies and perform systems engineering work to determine integration effort, viability, performance and capability gain

Trades Studies

Evaluation of software and hardware versions and updates in terms of capability and network impact

Evaluation of obsolescence issues and mitigations (Number of Occurrences based on Obsolescence and DMSMS Management Plan)

Identify/evaluate any design changes and transition of equipment that may be required as a result of changes to system configuration requirements

Conduct performance and feasibility analysis of a specific concept or technique to include the modeling of concepts and techniques with comparison to current design and performance characteristics

Assist in developing solutions to systems engineering challenges based on technology insertion and new product integration.

Each Systems Engineering Study or Analysis shall contain, at a minimum, the background of the issue being evaluated, the technical approach to the study, any initial hypothesis or theories, the technical details of the study, including any modeling, simulation, testing, test result data, quantitative and qualitative measures and data, detailed analysis performed, decision factors, decision weighting, system dependencies, cost and schedule impacts, and the final recommendation of the study based on the analytical results. The Contractor shall prepare

Systems Engineering Studies and Analysis in accordance with (DI-MISC-80508B) Technical

Report Trade Studies / Services.

3.2.2.7 System Evaluations and Lessons Learned Analyses

Conduct system evaluations and lessons learned analyses of TROPO solution end items/systems.

Anomalies identified as a result of an evaluation/analysis will be contained in a Detailed

Technical Publication (DTP) that addresses the anomaly/issue and ways to overcome or mitigate the deleterious effects of the known problem.

3.2.2.8 Requirements Verification

The Contractor shall develop, deliver, and update a Requirements Compliance Matrix (RCM) for all requirements identified in the PSPEC detailed in Appendix A.

The RCM shall include each specification identified by index number, corresponding verification method using a Verification Cross Reference Matrix, the status of the requirement (MET, NOT

MET, MET WITH EXCEPTION, or NOT YET EVALUATED), and the objective evidence supporting the verification determination. The RCM shall be submitted by the Contractor in accordance with CDRL A010 (DI-MISC-81283) RCM.

3.2.2.9 Interface Control Documentation

The Contractor shall develop, deliver, and update Interface Control Documents (ICD) that identify the interface requirements between: Hardware Configuration Items (HWCI) and hardware devices (HWCI to HWCI); Computer Software Configuration Items (CSCI) and hardware devices (CSCI to HWCI); and HWCI and CSCI to systems external to TROPO system.

The ICDs shall be submitted by the Contractor in accordance with CDRL A011 (DI-SESS-

81248B) ICD.

3.2.2.10 Provide support related to reliability, maintainability, operational availability and HFE.

3.2.3. Frequency and Spectrum

3.2.3.1 The Contractor shall perform a study of frequencies at the location specified by the

Government in order to identify available TROPO operating frequencies and bandwidths respective levels to fulfill the capacity requested for each of the links.

3.2.3.2 The Contractor shall obtain Special Temporary Authority (STA) from the Federal

Communications Commission (FCC) for the dates and durations identified by the

Government.

3.2.3.3 The Contractor shall negotiate spectrum usage terms with the license holder(s) of the requested frequency bands.

3.2.3.4 The Contractor shall obtain spectrum usage through subcontracts, as required.

3.2.3.5 The Contractor shall submit completed DD1494 forms (Application for Equipment

Frequency Allocation) required by the Government according to CDRL A012 (DI-

MISC-80711A) Scientific and Technical Reports.

3.2.4. Field Testing Support

3.2.4.1 As required, the Contractor shall provide technical and engineering support to the

Government for testing efforts as set forth below.

3.2.4.2 Validation Testing Support

The Contractor shall provide technical support for Government Validation Exercise (Valex)

Testing of fielded equipment. The efforts required for Valex support include the following.

3.2.4.3 Field Engineering Support

Validators shall arrive on site under the direction of PM Tactical Network Field Engineering and

Test Lead to ensure all equipment is properly staged in preparation for configuration. All testing shall be IAW PM approved test plans and procedures. Validators to support field testing efforts as required at both CONUS and OCONUS locations. Additionally they shall support and attend weekly mission planning teleconferences in preparation of this support. The number of personnel needed and disciplines will be determined by the PM Tactical Network Field

Engineering Manager prior to mission execution.

3.2.4.4 Configuration Updates

Field engineers shall perform Internet Protocol (IP) loading, update baselines, install software updates, and perform new hardware integration and other efforts to ensure Full Mission

Capability.

3.2.4.5 Other Testing Support

The Contractor shall plan and participate in testing and events involving PM Tactical Network as directed by the COR. Such activities may include:

a) Support events at various Government facilities. Events may include testing, training, logistics demonstration or other related activities.

b) Plan and develop test plans and procedures, conduct tests associated with new requirements and equipment modifications and upgrades.

c) Plan to support Engineering Tests, Unit Validation Exercises and Unit Field Exercises to include Combat Training Center (CTC) rotations. The types and numbers of engineering personnel required for these events shall be coordinated in advance with the COR.

d) New equipment/systems/software that may be developed during the term of this acquisition may in the future require Valex support.

e) Develop system check-out procedures to determine if end-items and/or component parts held by PM Tactical Network in storage are Fully Mission Capable (FMC).

f) Conduct technical inspections of TROPO end items or component parts as directed.

3.3. Integrated Logistics Support (ILS)

3.3.1. The Contractor shall develop an integrated product support strategy for the TROPO system with the following elements, using AR 700-127 as a guide.

3.3.2. Miscellaneous (no deliverables)

3.3.2.1 Maintenance and Supply Support Concepts

Using AR-750-1 as a guide, the Contractor shall develop a maintenance and supply concept for the TROPO equipment. The Contractor shall define all Line Replaceable Units (LRUs) and make a repair versus discard decision for each identified LRU. An LRU is defined as all of the

Field Replaceable Components that are required to be replaced in order to bring an inoperable

TROPO Solution to a FMC status. LRUs include items such as control modules, power supplies, radios and cables. The Contractor shall utilize the two-level maintenance concept which consists of Field-level and Sustainment-level maintenance. The Contractor shall ensure that all maintenance actions required to bring an inoperable TROPO system to a FMC condition are accomplished at the Field level of maintenance by the crew or maintenance personnel organic to military units assigned support responsibilities (Organizational and Direct Support).

3.3.2.2 Field level maintenance is characterized as on-system maintenance and shall consist of replacing LRUs. LRUs will either be returned to the Sustainment level of maintenance for repair or will be discarded. The Contractor shall support the Government’s re-supply of failed LRUs through the standard Army supply system.

3.3.2.3 Interim Contractor Support (ICS)

The Government may order ICS to allow sufficient time for the Government to determine and implement the Product Support Strategy.

3.3.2.3.1 Supply Support Services

During ICS, the Contractor shall provide supply support services as ordered by the Government.

These services can be ordered for Continental United States (CONUS) and Outside Continental

United States (OCONUS) locations, for forward deployed locations world-wide, and into areas of conflict.

3.3.2.3.2 Repair and Return

Unserviceable equipment shall be shipped to the Contractor for Contractor Logistics Support

(CLS) repair and return. The Contractor shall establish a depot support process, on a repair and return basis, for equipment the Government does not have support capability. The Contractor shall be responsible for assessing the condition of incoming equipment and for establishing control procedures for all equipment to be repaired by the Contractor or by the Original

Equipment Manufacturer (OEM).

Upon completion of the repair actions, the repaired item shall be inspected by the Defense

Contract Management Agency (DCMA) representative to ensure proper functionality. If a test or inspection failure occurs, the contractor shall immediately investigate the cause of failure and implement the corrective action necessary to restore the failed unit to a serviceable condition.

The LRU/SRU shall then be retested. The Contractor shall provide notification of the inspection results to the PCO and return the item to the Government. The items shall be packaged and shipped per instructions as directed by the Government.

3.3.2.3.3 Repair Requirements

Under this acquisition, the Contractor shall serve as the prime Contractor and shall produce or repair all of the items as ordered by the Government IAW documents listed above and this PWS.

3.3.2.3.4 Repair vs. Evaluation

Upon receipt of an item for repair, the Contractor shall first conduct an evaluation to determine if the item is either No Evidence of Failure (NEOF) or Beyond Economic Repair (BER). IAW sections 3.3.2.3.9 and 3.3.2.3.10 the Contractor shall notify the Government of those items that are determined to be NEOF or BER, and shall follow the additional instructions set forth in those sections. No repair of any NEOF or BER item will be completed and the schedule will be adjusted by the Government to reflect “Evaluation” only, as set forth in 3.3.2.3.5

3.3.2.3.5 Removed

3.3.2.3.6 Repair Baseline

The Contractor shall repair each component so that the performance meets all of the form, fit and function requirements, interface requirements, and drawing requirements. All items shall be repaired to supply condition code “A” (Ready For Issue). Supply Condition Codes are identified in AR 725-50.

3.3.2.3.7 Start-Up

The Contractor shall furnish all facilities, parts, materials, data, personnel, equipment and any other effort, needed to fully provide the repair services required by this PWS within 45 days after

Government notification. The Contractor shall provide the shipping address of this facility to the

Government Procurement Contracting Officer (PCO), in writing, within 10 days after issuance of repair task/delivery order.

3.3.2.3.8 Use of Tobyhanna Army Depot (TYAD)

The Contractor shall acknowledge that TYAD is not a source of supply for this contract. The

Contractor shall leverage TYAD as a source for screening of returned assets to determine applicability of warranty coverage through the use of a Public Private Partnership (PPP).

Additionally, the contractor shall pursue the opportunity to leverage TYAD as a source for Out of Warranty (OOW) or Other Than Fair Wear and Tear (OTFWT) repair through the use of a

Public Private Partnership (PPP) with the understanding that TYAD does not currently have repair capability for the TROPO systems. It is expected that, through this partnership, TYAD would be used to accomplish a level of repairs that would incrementally increase their sustainment capabilities in support of TROPO. This PPP effort shall involve such activities as, but not limited to, training, documentation on repair and test procedures, test equipment and associated source code, supply support, along with any special requirements.

The intent of including TYAD in sustainment activities under this contract is to both familiarize the organic depot with the TROPO system in preparation for future assumption of sustainment activities as well as to provide soldiers in the field with a centralized organic source of supply support. PM Tactical Network seeks to limit the need for soldiers to pursue sustainment support outside of Army channels.

The contractor shall prepare and submit a Hardware Sustainment Transition Plan per CDRL

A063 (DI-MISC-80508B) outlining how Depot-level sustainment tasks (e.g. repair, reset, overhaul) will be transitioned to TYAD or any other organic facility. The plan shall include but may not be limited to:

a. Test Procedures

b. Test Equipment

c. Special tooling

d. Special facilities

e. Training requirements

f. Skill sets

g. DMWR information

h. Schedule to complete full transition

The contractor shall ensure all tooling and equipment specified in this plan shall adhere to all government certification requirements. In accordance with the Hardware Transition Plan, the contractor shall provide a Technical Data Package (CDRL A077) and Technical Data Package

Index (CDRL A078) that will facilitate efforts to provide an organic depot level capability at

TYAD.

3.3.2.3.9 No Evidence of Failure (NEOF)

Upon receipt of an item to be repaired, the Contractor shall evaluate the returned item to determine if it is NEOF. If the item is found to be operational, and NEOF is confirmed by the

Defense Contract Management Agency (DCMA) representative, the Contractor shall provide notification of this determination to the PCO and return the item to the Government. All return transportation costs shall be borne by the Contractor as part of the Evaluation CLIN price.

3.3.2.3.10 Beyond Economical Repair (BER)

Upon receipt of an item to be repaired, the Contractor shall evaluate the item to determine if it is

BER. A component shall be considered BER when the total repair cost exceeds 65% of the contract acquisition cost for that item. The BER determination shall be confirmed by the onsite

DCMA representative. Upon DCMA confirmation, the Contractor shall notify the PCO of the item’s BER determination and request disposal instructions which will be carried out by the

Contractor. All transportation costs shall be borne by the Contractor.

3.3.2.3.11 Confirmation of NEOF or BER by DCMA Representative

As part of DCMA confirmation of an item’s NEOF or BER determination, the DCMA representative shall verify the following:

a) Property identity

b) Damaged or mishandled items

c) Actual item failures

d) Determine completeness of the items

3.3.2.3.12 Repair Turn Around Time (RTAT)

The work required varies based upon the complexity of the repair and the Contractor shall provide estimated repair times in their proposal for each item being repaired. Contractor shall inspect/evaluate each item as a goal within 5 business days of receipt, provision of funding and authorization to proceed with the repair and provide the status to the COR. Acceptance for repairs shall be rendered upon execution of the DD Form 250 or DD Form 1149.

The Government will assess the Contractor’s RTAT performance based on the estimated repair times listed in the Offeror’s Proposal. RTAT will be reviewed quarterly as part of the Quality

Assurance Surveillance Plan (QASP).

3.3.2.3.13 The Contractor (or partner) shall repair returned assets and ship-back to government CONUS and OCONUS locations in accordance with estimated repair times from their proposal and allowing for reasonable shipping durations to respective sites.