A01_GTACS_II_PWS_02_November_2017.pdf

PDF 553 KB Posted

Attached to
Global Tactical Advanced Communication System II (GTACS II) and Services
Solicitation number
W15P7T18R0003
Issued by

About this file

This the Final PWS for GTACS II.

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

Performance Work Statement for

Global Tactical Advanced Communications Systems

(GTACS II)

02 November 2017

Prepared by:

PdM SATCOM, Project Manager Tactical Network, Program Executive Office, Command Control Communications –Tactical (PEO C3T), Aberdeen Proving Ground (APG), MD

Procurement Sensitive i

TABLE OF CONTENTS

Para./Section Title Page

1.0 SCOPE 1

2.0 APPLICABLE DOCUMENTS OR LATEST REVISION 2

3.0 GENERAL REQUIREMENTS 4

3.1 Contract Type

3.2 Ordering Period

3.3 Place of Performance

3.4 Facilities

3.5 Government Furnished Property (GFP)

3.6 Personnel

3.7 Government Support

3.8 Security

3.9 Organizational Conflict of Interest

3.10 Non-Developmental Items and Processes

3.11 Safety and Environmental

3.12 Travel

3.13 Quality Assurance

3.14 Contract Management

4.0 CONTRACT TASKS 13

4.1 Tasking Descriptions

4.2 Systems Engineering and Integration

4.3 Command Control and Communications (C3) Systems

4.4 Program Management

4.5 Operation and Maintenance

4.6 Integrated Logistics Support

4.7 Site Survey

4.8 Installation

4.9 Test and Evaluation

4.10 Certification

4.11 Studies, Analysis and Reporting

4.12 Requirements for Unique Identification (UID)

4.13 Data and Data Management

5.0 CONTRACT ADMINISTRATION 18

6.0 CONTRACTOR MANPOWER REPORTING APPLICATION 18

7.0 ACCEPTANCE 19

APPENDIX A - CONTRACTOR NON-DISCLOSURE AGREEMENT 20

APPENDIX B - CONTRACTOR EMPLOYEE PERSONAL FINANCIAL INTEREST/PROTECTION OF

SENSITIVE INFORMATION AGREEMENT 22

Performance Work Statement for

Global Tactical Advanced Communications Systems (GTACS II) and Services

1.0 SCOPE

The Global Tactical Advanced Communication Systems (GTACS II) and Services contract is a multiple award Indefinite Delivery Indefinite Quantity (IDIQ) contract supported by the Program

Executive Office Command, Control and Communications-Tactical (PEO C3T), and Project

Manager Tactical Network (PM Tactical Network).

This Performance Work Statement (PWS) establishes the overarching requirements for

Contractor-provided hardware, software, services and data in support of the PEO C3T Mission which is to develop or procure hardware and software that can be integrated, tested, fielded and supported as networked battle command solutions that enhance Warfighter effectiveness. C3T systems include all programs, projects and products managed within PEO C3T, its Project

Managers (PMs), Product Managers (PdMs) and Product Directors (PDs). This contract vehicle may be used by other agencies and organizations in support of their missions. During the period of performance of the GTACS II contract, it is expected that the organization and needs of PEO

C3T, its PMs, PdMs and PDs will evolve and re-organize in response to the changing needs of the

Warfighter and anticipated threats. The GTACS II program and contract will provide the flexibility and responsiveness needed to support the mission of PEO C3T, its PMs, PdMs and PDs.

The C3T systems hardware includes, but is not limited to: products, systems, and subsystems

(such as: Non-Secure Internet Protocol Router (NIPR), Secure Internet Protocol Router (SIPR), Joint Worldwide Intelligence Communications System (JWICS), CENTCOM Regional

Intelligence Exchange System (CENTRIX), Commercial and Net Equipment, Tactical

Communications Platforms, Mobile Broadband Global Area Network Access Capabilities

(MBAC), Satellite Communications (SATCOM) Terminals (Large, Very Small Aperture

Terminal (VSAT), Hand Held), Highly Mobile Communications, Very High Frequency (VHF), Ultra High Frequency (UHF), Ku-band, Ka-band, C-band, X-band, L-band, Land and Mobile

Radio (LMR) and Mobile satellite services ( e.g., Satellite Phones, Secure Personal Digital

Assistants (PDAs), Cell Service Development). Hardware and engineering services will be specified in applicable Delivery Orders/Task Orders (DOs/TOs). (Note: The terms: Delivery

Order (DO) and Task Order (TO) as used extensively throughout this document have the same meaning as specified in FAR Part 2.) Services may include: systems engineering; hardware and software engineering; development; maintenance; software development, sustainment and support; program management and analysis; logistics; supply chain management; technical field assistance; product and subsystem integration, test and evaluation; modeling and simulation;

information operations/assurance support; fielding and training; facilities management;

administrative support, Help Desks, In-house Engineering Support and On-site Engineering

Support. These services may be performed in conjunction with new and existing Government system of systems, family of systems, platforms, systems, subsystems and items and any

Government application of C3T. Also included in scope are: hardware, software, services and data associated with secure communications such as crypto security, transmission security, emission security, traffic-flow security and physical security. This will also include research, development, acquisition, fielding and sustainment of automated air and missile defense command and control systems, network infrastructure, Army Tactical Shelters, power supply requirements, cooling, heating and dehumidification equipment components, as well as any directly related equipment or integration and/or support services for items that are within scope of the PEO C3T mission. This PWS provides the general requirements. Specific and detail requirements are outlined in Attachments to be used and referenced to when applicable in individual Requests for

Task Execution Plan (RTEP) and corresponding DOs/TOs.

The GTACS II program will compete user requirements among the GTACS II Prime Contractors IAW FAR 16.505 in order to assure the best value to the Government. This will be achieved through the issuance of individual, competitive RTEPs for specific tasking, receipt of Task

Execution Plans (TEPs) in response and award of a DO/TO for each specific GTACS II requirement. As requirement for a particular system/equipment configuration arise, an RTEP will be competed among those Prime Contractors designated in accordance with (IAW) the procedures of the GTACS II contract. Each DO/TO will contain a TEP. The TEP shall provide the details necessary (e.g., hardware, software, services and data) to successfully implement the GTACS II customer requirement. Contractors shall refer to the ordering procedures of the basic contract for instructions and guidance on task orders.

2.0 APPLICABLE DOCUMENTS OR LATEST REVISION

The contractor shall comply with all Regulations and Standards applicable to the work or product provided under this contract unless otherwise stated. Some of the types of documents that are applicable in an individual DO/TO are set forth below. This list is not comprehensive and additional information will be provided within each order.

Document Number Document Title Issue Date

AR 530-1 Operations Security 26 September 2014

AR 380-10 Foreign Disclosure and Contact with

Foreign Representative

14 July 2015

DoD-Manual 5220.22, Volume 3

National Industrial Security Program:

Procedures for Government Activities

Relating to Foreign Ownership, Control or Influence (FOCI

April 2014

AR 25-2 Information ASSurance 24 October 2007

DODI 8500.01 Organization 14 March 2014

Special Publication 800-

Managing Information Security Risk

Organization, Mission, and Information

System View

March 2011

DoDD 8140.01 Cyberspace Workforce Management August 2015

DoD 8140.01-M Information Assurance Training for

Workforce Improvement December 2005

DoD 5220.22-M National Industrial Security Program

Operating Manual 28 February 2006

DoDI 5000.02 Operation of the Defense Acquisition

System.

2 February 2017 http://www.acq.osd.mil/dp ap/pdi/uid/docs/IUID_101

_The_Basics_v3_05_2010

_v2.pdf

Army’s Unique Identification (UID) policy 29 July 2003

DoDI 3020.41 Operational Contractor Support (OCS) December 2011

IEEE 15288.1-2014 IEEE Standard for Application of

Systems Engineering on Defense

Programs

15 May 2015

AR 525-13 Force Protection Program Dec 1997

MIL-PRF-29612B Specification: Training Data Products 31 August 2001

MIL-STD-40051-2C Preparation of Digital Technical

Information for Page Based Technical

Manuals

December 2015

3.0 GENERAL REQUIREMENTS

The requirements of this PWS shall be in addition to the requirements stated in other terms and conditions of the base contract and any DO/TO issued. Any inconsistency shall be brought to the attention of the Contracting Officer.

The Contractor shall provide the systems, hardware, software and services required by individual

DOs/ TOs pursuant to the requirements specified herein.

The Contractor shall monitor all performance aspects of the GTACS II contract, and as outlined in each individual DO/TO. Each individual DO/TO will provide the specifics for each requirement.

The Government Contract Officers Representitive (COR) or the Defense Contract Management

Agency (DCMA) representative, as assigned, has the right at all reasonable times, to inspect or otherwise evaluate the work performed or being performed. If any inspection or evaluation is made by the Government on the premises of the Contractor, the Contractor shall provide all reasonable facilities and assistance for the safety and convenience of the Government representative in the performance of their duties consistent with the PWS and contract clauses. All inspections and evaluations shall be performed in such a manner as will not unduly delay the work.

Note that anytime the term “contractor” or “contractor employee” is used, it includes the required performance/compliance of subcontractors and subcontractor employees.

Laws, regulations, systems, publications, or other references cited within this PWS may change, evolve, or be updated during the ordering period of this basic IDIQ. It is the intention that the contractor maintain compliance with requirements that are current.

3.1 Contract Type

This base contract is a multiple award IDIQ type contract. Individual DOs/TOs can be awarded on a Firm Fixed Price (FFP), Cost Plus Fixed Fee (CPFF) basis. Local and Federal policies covering the use of contract types will be fully implemented.

3.2 Ordering Period

The GTACS II ordering period is five (5) year base period and one (1) five (5) year option from the effective date of award. Individual DOs/TOs can be awarded at any time during this period.

Performance of an individual DO/TO awarded during the IDIQ period will not extend more than one year beyond the ordering period. Options under DOs/TOs will not be exercised outside the base contract ordering period.

3.3 Place of Performance

The place of performance shall be identified in individual DOs/TOs. Locations will be

Government or Contractor sites within the continental United States (CONUS) and/or outside the continental United States (OCONUS).

3.3.1 Technical Expert Status Accreditation (TESA)

The Government will provide TESA through Department of Defense Contractor Personnel Office

(DOCPERS) in Germany when required by the specific DO/TO.

3.3.2 Status of Forces Agreement (SOFA)

The COR in coordination with the servicing legal advisor will inform the Contractor of the existence of all relevant SOFA and other similar documents, and provide copies or provide access upon request. The Contractor is responsible for obtaining all necessary legal advice concerning the content, meaning, application, etc. of any applicable SOFAs, and similar agreements. The

Contractor shall adhere to all relevant provisions of the applicable clauses, laws, SOFAs and other similar related agreements. The Contractor shall be responsible for providing the Government with the required documentation to acquire invited Contractor or technical expert status, if required by

SOFA.

The contractor shall coordinate with the ACO and COR for theater specific reporting and contractor management issues. Specific instructions shall be presented in each T.O./D.O.

3.4 Facilities

Certain Government office or laboratory space may be made available for performance of specific

DOs/TOs. Such facilities will be specified in the corresponding RTEP provided by the

Government.

3.5 Government Furnished Property (GFP)

GFM and/or GFE may be provided to support an individual DO/TO. In such cases, the GFM and

GFE provisions at Sections H and I of this contract will be supplemented by specific delivery and disposition instructions provided in the corresponding DO/TO. See FAR Part 52.245-1, Government Property.

3.6 Personnel

The Contractor shall provide only fully trained, experienced, and technically proficient personnel having the appropriate security clearances as identified in applicable DO/TOs. Training of

Contractor personnel will be performed by the Contractor at their expense, unless otherwise authorized in writing by the Contracting Officer (KO) or identified in the contract as Government furnished.

3.6.1 Personnel Qualifications

3.7 Government Support

The Contracting Officer will provide the Contractor access to all available Government furnished information, facilities, material, equipment, services, etc., as required by the individual T.O. and on a non-interference and availability basis to accomplish each DO/TO.

3.8 Security

The security requirements for the basic IDIQ contract are defined in the attached DD Form 254.

The contractor facility shall have SECRET safeguarding capability. The Contractor shall provide personnel having security clearances up to TOP SECRET as identified in applicable

Delivery/Task Order (DO/TO). Each individual DO/TO that requires a contractor facility and

COMSEC requirements above the SECRET level will need to issue a separate DD Form 254 identifying the specific security requirements for that particular DO/TO at that time.

The highest security level that may be required by the Contractor to perform at Government or other Contractor facilities on individual DOs/TOs is TOP SECRET.

The contractor will require access to COMSEC information, Restricted Data, Critical Nuclear

Weapon Design Information (CNWDI), Formerly Restricted Data, SCI and Non SCI Intelligence information, Special Access information (SAP), NATO, Foreign Government Information and

FOUO information. The contractor will also require access to Security/Program Classification

Guide(s) (SCG), and access at Government locations to Special Access Programs such SIPRNET, CENTRIX, JWICS and NSANET.

In performing this contract, the contractor will receive and generate classified material and fabricate/modify/store classified hardware. All Contractor facilities shall provide an appropriate means of storage for classified documents, classified equipment and materials, and non-classified equipment and materials, in accordance with Operational Security (OPSEC) and

Communications Security (COMSEC) requirements. The Contractor shall obtain a COMSEC account in accordance with DD Form 254 within 120 days after contract award.

Contractor will have access to classified information overseas and will be authorized to use the

Defense Technical Information Center (DTIC). A COMSEC account will be required and there will be a TEMPEST requirement. OPSEC requirements will be provided by the Government

IAW AR 530-1. Use of the Defense Courier Service is authorized. Performance of this contract will be in CONUS and OCONUS locations as designated by the COR. Administrative duties will not require a clearance but may require investigation for IT duties.

Foreign subcontractor participation will be handled, at a minimum, in accordance with AR 380-

10 (Foreign Disclosure and Contacts with Foreign Representatives); DoD-M 5220.22, Volume 3, Each individual shall comply with and maintain the qualifications set forth in the guidelines and requirements of the contract. Due to the ever evolving nature of cybersecurity and the growing threat to Information Systems, all individuals, at the DO/TO level are expected to maintain their certifications during the life of this contract and be knowledgeable on new policies and guidance that emerge.

April 2014 National Industrial Security Program: Procedures for Government Activities Relating to Foreign Ownership, Control, or Influence (FOCI), and affiliated regulations and/or supplements.

The contractor shall ensure that their systems, personnel, supply chains, equipment, and cloud computing services at a minimum comply with the current security requirements of requirements of FAR part 4.19, DFARS Part 39, AR 25-2, DODI 8500.01 Cybersecurity DoD Instruction

8510.01 Risk Management Framework (RMF) for DoD Information Technology (IT), NIST

Special Publication 800-39 Managing Information Security Risk Organization, Mission, and

Information System View and other applicable regulations addressing IT and cyber security.

The contractor shall maintain awareness and compliance with emerging cyber security requirements applicable to DOD contractors.

3.8.1 Antiterrorism/Operational Security Requirements

The Government retains the right to request removal of Contractor personnel, regardless of prior clearance or adjudication status, whose actions while assigned to this contract conflict with the safety, security, environmental, or other critical interests of the Government.

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 30 calendar days after contract start date or effective date of incorporation of this requirement into the contract, whichever is applicable. The Contractor shall submit certificates of completion for each affected contractor employee and subcontractor employee, to the COR or to the KO if a COR is not assigned, within 10 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. Contractors 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.

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 30 calendar days of contract award and within 30 calendar days of new https://jkodirect.jten.mil/ http://jko.jten.mil/courses/atl1/launch.html employees commencing performance with the results reported to the COR NLT 60 calendar days after contract award.

Army Training Certification Tracking System (ATCTS) Registration. All Contractor employees with access to a Government information system must be registered in the ATCTS (Army

Training Certification Tracking System) at commencement of services, and must successfully complete the DOD Cybersecurity Awareness prior to access to the Information System (IS) and then annually thereafter.

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)

Cybersecurity/Information Technology (IT) Training. All Contractor employees and associated sub-contractor employees must complete the DoD Cybersecurity awareness training before issuance of network access and annually thereafter. All Contractor employees working

Cybersecurity/IT functions must comply with DoD and Army training requirements in DoDD

8140.01, DoD 8570.01-M (Ch4) and AR 25-2 within six months of appointment to

Cybersecurity/IT functions.

Cybersecurity/Information Technology (IT) 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.

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); any revisions to DOD

5220.22-M, notice of which has been furnished to the contractor.

AT Awareness Training for 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.

For contractors requiring Common Access Card (CAC). Before CAC issuance, the contractor employee requires, at a minimum, a favorably adjudicated National Agency Check with Inquiries

(NACI) or an equivalent or higher investigation in accordance with Army Directive 2014-05. The contractor employee will be issued a CAC only if duties involve one of the following: (1) Both physical access to a DoD facility and access, via logon, to DoD networks on-site or remotely; (2) http://cdse.edu/catalog/elearning/GS130.html https://prmsglobal.prms.af.mil/prmsconv/Profile/Survey/start.aspx

Remote access, via logon, to a DoD network using DoD-approved remote access procedures; or

(3) Physical access to multiple DoD facilities or multiple non-DoD federally controlled facilities on behalf of the DoD on a recurring basis for a period of 6 months or more. At the discretion of the sponsoring activity, an initial CAC may be issued based on a favorable review of the FBI fingerprint check and a successfully scheduled NACI at the Office of Personnel Management.

For contractors that do not require CAC, but require access to a 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.

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.

Contractors and all associated sub-contractor employees authorized to accompany U.S. Armed

Forces deployed outside the US in contingency operations, humanitarian or peacekeeping operations, or other military operations or exercises shall comply with DFARS Clause 252.225-

7040 and DFARS Clause 252-225-7995 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.

Contractors and all associated sub-contractor employees requiring performance or delivery in a

Foreign Country shall comply with DFARS Clause 252.225-7043, Antiterrorism/Force Protection for Defense Contractors outside the US. All non-local national contractor personnel shall comply with theater clearance requirements and shall allow the combatant commander to exercise oversight to ensure the contractor’s compliance with combatant commander and subordinate task force commander policies and directives.

Threat Awareness Reporting Program. 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.

3.8.2 Controlled Unclassified Informaiton (CUI)

In accordance with the stated intent of Exceutive order 13556 and as applicable, all CUI information shall be handled in accordance with DOD policy. In the absence of DOD policy all

CUI documentation shall be protected and not released by the Contractor.

3.9 Organizational Conflict of Interest

The Contractor agrees to accept and to complete all awarded DOs/TOs and not to establish relationships with other GTACS II Contractors, Subcontractor or Vendors in a manner as to create an actual or perceived organizational conflict of interest consistent with FAR Part 9.505 and all relationships shall be designed to avoid, neutralize, or mitigate organizational conflicts of interest that might otherwise exist in situations related to individual orders.. To avoid an organizational or financial conflict of interest and to avoid prejudicing the best interests of the Government, the KO may place restrictions on the Contractor, its affiliates, chief executives, directors, subsidiaries at any tier when placing orders. Examples of situations, which may require restrictions, are provided at FAR Part 9.508. All Contractor personnel directly associated with this contract will be required to sign a non-disclosure statement that will be furnished at time of award of this contract. Subject non-disclosure statements, once signed, shall be furnished to the designated COR and KO.

3.10 Non-Developmental Items and Processes

Non-Developmental Items (NDI) and Commercial items shall be used to the maximum practicable extent. Modified COTS items and ruggedized equipment may be required. The Contractor shall apply commercially available processes and technologies to the maximum practicable extent.

3.11 Safety and Environmental

The Contractor shall comply with all applicable federal, state and local safety, health and environmental regulations, including the National Environmental Policy Act (NEPA). In addition, when performing OCONUS, the contractor shall ensure they comply with all applicable environmental provisions of the host country IAW the terms and conditions of the contract.

The Contractor shall identify and evaluate system safety and health hazards, define risk levels, and establish a program that manages the probability and severity of all hazards in accordance with requirements listed in RTEPs. Safety and health hazards shall be managed consistently with mission requirements. All inherent hazards shall be identified, evaluated and either eliminated or controlled to ensure minimum risk to the environment and personnel. The contractor shall keep records for the life of the contract plus two years. These records shall be made available to the

Government upon request.

When required by the specific DO/TO, the Contractor shall provide a Safety Assessment Report

(SAR) that will address hazardous material in its hazardous material section of System Safety

Verification Checklist, SEL Form 1183. The DO/TO will require a Material Safety Data Sheet

(MSDS) for hazardous materials that are required to be incorporated into the system.

3.12 Travel

The Joint Travel Regulations (JTR) shall provide the basis for determining allocable and allowable travel expenses. The Contractor shall not be reimbursed for travel to and from their normal place of business within CONUS. All travel requests must be approved in writing by the Government.

3.13 Quality Assurance

The quality assurance requirements set forth herein are the minimum allowable under the contract.

Individual DOs/TOs and RTEPs may include additional quality assurance requirements appropriate for the goods and services being ordered. The Contractor shall maintain a quality assurance system to ensure product integrity. Sections B, E and I of the contract specify the requirements for inspection and acceptance of the items delivered under this contact. The prime

Contractor shall possess either ISO 9000 or Capability Maturity Model Integration (CMMI) Level

2 certification.

3.13.1 Services

When services are acquired under this contract, the Government will require a Quality Assurance

Surveillance Plan (QASP) to assess the Contractor’s performance.

3.14 Contract Management

The Contractor shall establish a single management focal point to accomplish the administrative, managerial and financial aspects of this contract.

3.14.1 Work Control

All program requirements, contract actions and data interchange shall be conducted in a digital environment using electronic and web-based applications. At a minimum, such data shall be compatible with the latest ARMY CIO G-6 authorized Microsoft Office family.

3.14.2 Contract Performance Report

The Contractor shall submit a monthly Contract Performance Report in accordance with DI-

MGMT-81861 Integrated Program Management Report and CDRL.

These reports convey the status of all DOs/TOs awarded as of contract inception as well as cumulative contract performance. These reports shall be a roll up of monthly cost data and other relevant information at the base contract level.

3.14.2.1 Small Business Utilization Report

The Contractor shall provide the Small Business Utilization Report semi-annually in accordance with CDRL for DI-MGMT-82041. The Contractor shall include summary data for all Delivery

Orders awarded under the base GTACS II contract.

3.14.3 Post Award Conference

The Government will convene a Post-Award Conference at Contractor facility with each Prime

Contractor within 60 days after contract award. The Post-Award Conference discussion should focus on acquisition process improvement. A summary presentation of the Contractor’s capability to support the GTACS II requirements will also be presented by the Contractor. The Contractor shall document post award conference discussion to include contractor internal working session and submit Conference Report in accordance with CDRL for DI-ADMIN-81308A. The

Conference Report shall outline the suggestions for acquisition process improvement at DO/TO level with the goal of reducing the time to award.

3.14.4 Data Rights

The Government’s rights in non-commercial technical data and software deliverables shall be governed by DFARS 252.227-7013 and DFARS 252.227-7014, respectively. The Government's rights in commercial technical data deliverables shall be governed by DFARS 252.227-7015. All non-commercial technical data and software deliverables shall be properly marked in accordance with the marking requirements set forth in DFARS 252.227-7013(f) and DFARS 252.227-7014(f).

Technical data and software deliverables with non-conforming restrictive markings may be rejected and corrected by the Contractor at the Contractor's expense, in accordance with DFARS

252.227-7014(h)(2).

3.14.5 Commercial Software Purchases

The Contractor shall not purchase commercial software on behalf of the Government (where the

Government is a licensee or end user) unless the corresponding commercial software license agreement has been reviewed and approved by the Contracting Officer. The Government shall not accept any commercial software license terms that conflict with federal procurement law or do not satisfy user needs. Commercial Software License terms that are unacceptable to the Government include (but are not limited to) indemnification provisions (and other types of provisions that include unauthorized or unbudgeted funding obligations), attorney's fees provision, state or foreign choice of law/jurisdiction provisions, binding arbitration provisions, and injunctive relief provisions.

3.14.6 Theatre Business Clearance (TBC)

The Contractor shall comply with DoD Theatre Business Clearance directives for DOs/TOs requiring contractor personnel in Iraq, Afghanistan, Kuwait and Pakistan or areas otherwise noted by current TBC instructions. These requirements will be provided as an attachment to the contract.

The requirements associated with each TBC will be provided as required per DO/TO.

Contractors shall check the applicable theater guidance for specific requirements for performance within that theater. For example, check the CENTCOM Contracting website http://www2.centcom.mil/sites/contracts/Pages/Default.aspx for the most up to date directives for performance within the CENTCOM area of operations.

3.14.7 Synchronized Pre-deployment and Operational Tracking

Contractor Personnel Authorized to Accompany the U.S. Armed Forces, are required to maintain by-name contractor accountability within the Synchronized Pre-deployment and Operational

Tracker (SPOT), designated as the Joint Enterprise contractor management and accountability system to provide a central source of contingency contractor information and a summary of contract services IAW DoDI 3020.41. All contractor data must be entered into the SPOT database for all contractors traveling to the National Training Center (NTC), Joint Readiness Training

Center (JRTC) and to any AMC CONUS or OCONUS locations. They are further required to http://www2.centcom.mil/sites/contracts/Pages/Default.aspx coordinate in person with the respective AMC Forward Commanders, Logistic Support Elements, or Logistic Assistance Offices

4.0 CONTRACT TASKS

Each RTEP shall provide a detailed description of the technical requirements for the command control and communication (C3) system or equipment, services, personnel, location(s), and schedule for a given DO/TO. The work to be performed requires a broad range of technical solutions associated with command control communications and intelligence technologies to include transmission media; communications systems that typically provide turn-key solutions;

hardware and software; and support services. Contract tasks can include work in relationship to any aspect of the Operation of the Defense Acquisition System as described in DoDI 5000.02 to incluude new materiel requirements, the engineering and manufacturing development; production and deployment and operation and support processes for C3 defense acquisition programs.

Furthermore, work may be required in responding to diverse and varied special projects with challenging schedules and restrictive budgets. The task areas below may include the acquisition of complex Systems of Systems, subsystems, nodes, equipment, components, software, hardware, technical or logistic documentation and services required during a system/equipment life cycle phase. These Task Areas apply to Programs of Record weapons systems falling under DoDD

5000.01 and DoDI 5000.02 and Non-Programs of Record , as may be required.

4.1 Tasking Descriptions

4.1.1 Functional Area 1- Research and Development

This functional area includes design, development, fabrication, and testing of developmental systems covering the complete range of C3 systems. It includes the following; engineering development, modeling and prototyping, hardware, software, program management, engineering services, test and evaluation, and logistics solutions required for C3 systems. It includes activities and tasks required of a systems/equipment developer during an Engineering and Manufacturing

Development phase within the scope of DoDI 5000.02 “Operation of the Defense Acquisition

System.”

4.1.2 Functional Area 2 - Production and Deployment

This Functional Area includes system development, design and integration of COTS/GOTS items, newly developed items to satisfy system requirements and includes Low Rate Initial Production

(LRIP), Full Rate Production (FRP), manufacturing and deployment/fielding of C3 equipment or systems. It includes equipment, associated hardware and software, program management, software support, engineering services, test and evaluation, spare and repair parts, warranties, new equipment training, support centers (facilities and equipment), Field Service Representatives

(FSR), support equipment, logistics support activities to include provisioning, technical manuals, training materials and depot support. It includes activities and tasks required of a systems/equipment producer/manufacturer during a Production and Deployment phase within the scope of DoDI 5000.02 “Operation of the Defense Acquisition System.”

4.1.3 Functional Area 3 – Sustainment through Disposal

This Functional Area supports all operations and maintenance activities, including the acquisition of spare and repair parts, ancillary items, support equipment, depot support, technical support, repair services, overhaul, provisioning, leasing, storage, training, extended field support operation and maintenance activities, reporting, record keeping, engineering changes, logistic material updates, software maintenance, engineering services and data preparation, studies and analysis to sustain fielded C3 systems and disposal of systems/equipment. It includes reset of equipment for the repair/refurbishment of the item. It includes activities and tasks required of a contractor during an Operation and Support phase within the scope of DoDI 5000.02 “Operation of the Defense

Acquisition System.”

4.2 Systems Engineering and Integration

The Contractor shall design, develop, perform research, integrate, test and provide C3 systems in accordance with IEEE 15288.1-2014. The Contractor shall perform engineering disciplines for the design, development and production of new and modified C3 systems and IT capabilities.

Contractor support shall include scientific analytical and engineering efforts necessary to transform operational needs into unique system performance parameters for evolution into improved system capabilities. The Contractor shall, when required, provide modeling, simulation and prototyping. The Contractor shall perform hardware design and prototyping that includes requirements for well-engineered breadboard, brass board, rack, chassis, or transit case mounted hardware prototypes, capable of operation under field conditions.

Design concepts shall, when feasible, include provisions for continuous technological improvement to maximize opportunities for product improvement available from emerging technological advances in the market place. Proven technologies, products and processes shall be utilized wherever possible.

The Contractor shall have a thorough knowledge of the existing C3 systems operations, components, and subsystems; and the interoperability of proposed systems to existing networks.

The Contractor shall, when required, provide engineering documentation, Configuration

Management and Control, maintenance and service manuals, procedural and operator manuals, and other engineering related manuals, policies, procedures, guides and reference material to include drawings and associated parts lists

4.3 Command Control and Communications (C3) Systems

C3 systems and hardware to be procured per the GTACS II contract include but are not limited to:

(i) Baseband components/systems such as: Non-Secure Internet Protocol Router (NIPR), Secure Internet Protocol Router (SIPR), Joint Worldwide Intelligence Communications

System (JWICS), CENTCOM Regional Intelligence Exchange System (CENTRIX), computers and network equipment.

(ii) Communication/Control Systems and Tactical Platforms such as: Mobile Broadband

Global Area Network Access Capabilities (MBAC), Satellite Communications

(SATCOM) terminals, Very Small Aperture Terminal (VSAT), Hand Held Highly

Mobile Communications, Tactical Network (TN) systems, subsystems, nodes, Point of

Presence (PoPs), amplifiers, radio, C3 hardware components, converters, modems, receivers, antenna, power supplies/generators, communication vehicles, radomes, enclosures, control systems and software.

(iii) Ancillary Items such as: mounting/installation hardware, phones, secure personal digital assistants (PDAs), shelters, facilities, spare parts, tools, test equipment, materials, consumables, related services and any item required to provide a turn-key system/solution to GTACS II customers.

4.4 Program Management

The Contractor shall provide program management and administration services as required per each DO/TO.

4.5 Operation and Maintenance

The Contractor shall, when required, configure, operate, maintain, provide network management and advisory services for the C3 systems and associated equipment as defined in the specific

DO/TO.

4.6 Integrated Logistics Support

The Contractor shall provide Integrated Logistics Support services and data in all areas of Life

Cycle Management (LCM) for all GTACS II items, as defined in the DO/TO

The contractor shall implement ILS as a multi-functional technical management discipline associated with the design, development, test, production, fielding, sustainment, and improvement modifications of cost effective C3 systems that achieve the warfighters' peacetime and wartime readiness requirements. The principal objectives of ILS are to ensure that support considerations are an integral part of the system's design requirements, that the system can be cost effectively supported through its life-cycle (from program initiation to system retirement), and that the infrastructure elements necessary to the initial fielding, operation and maintenance support of the system are identified, developed and acquired.

The Contractor shall provide any or all of the following publications: systems level operations and maintenance technical manual, quick reference guide, and electronic formatted manuals to include but not limited to, Electronic Technical Manual (ETM), Interactive Electronic Technical Manual

(IETM), Modification Work Orders, Field or Technical Bulletins, Repair Parts and Special Tools technical manuals, Provisioning Parts Lists, and other such items in the format specified in the

DO/TO. Unsless specifically identified in the DO/TO, the Contractor shall develop and provide manuals per MIL-STD-40051-2C.

The contractor shall review, develop, update, and modify training programs for platforms, systems, subsystems or components as specified in the DO/TO. All courses shall be developed using MIL-

PRF-29612B and TRADOC Regulation 350-70 as guidance. The courses shall adhere to the

TRADOC Army Learning Policy and Systems (ALPS) emphasis on analysis, design, development, implementation, and evaluation (ADDIE) process and Training Development

Capabilities (TDC) process (http://TDC.army.mil/). The Contractor shall, when required, develop training manuals to include Computer Based Training (CBT), Computer Based Interactive

Training (CBIT), and simulation. Electronic training applications such as video teleconferencing and computer-based training shall be employed to enhance the effectiveness of training materials and courses when cost-effective. The Contractor shall, when required, conduct training for

Government personnel as directed by the Government. All deliverables shall be provided in the format specified in the DO/TO.

4.7 Site Survey

The Contractor shall, when required, perform or participate in site surveys worldwide as specified in the DO/TO, to determine site requirements affecting installation and operational feasibility.

4.8 Installation

The Contractor shall, when required, provide system installation efforts as specified in the DO/TO.

System installation include site preparation activities.

4.9 Test and Evaluation

The Contractor shall, when required, provide test and evaluation management services, test equipment and facilities, and data as specified in the DO/TO. Testing may include but not limited to:

a. Hardware and software component testing.

b. Subsystem and system level development testing.

c. System compatibility testing.

d. Acceptance testing to include certification testing.

e. Functional testing.

f. Integration and verification testing.

g. Field-testing and evaluation.

h. Environmental tests and stress screening.

i. Reliability and maintainability analysis and testing.

http://tdc.army.mil/

j. Transportability analysis and testing.

The Contractor shall ensure that all hardware, software, test equipment, instrumentation, supplies, facilities, and personnel are available and in place to conduct or support each scheduled test.

4.10 Certification

The Contractor shall, when required, obtain commercial and military certifications and authorizations for systems, subsystems, platforms, designs, equipment or installations in accordance with applicable commercial and DoD standards as specified in the DO/TO.

4.11 Studies, Analysis and Reporting

The Contractor shall, when required, perform studies, analyses and document the results of tasking required by a DO/TO.These may include but are not limited to subject areas such as: logistics, engineering, testing, financial, and operational studies and analyses. The Contractor shall document the results of assigned tasks as specified in the DO/TO.

4.12 Requirements for Unique Identification (UID)

The Contractor shall, when required, mark equipment using Unique Identifier (UID) and register

UID’s as specified in the DO/TO. The Contractor shall document UID in accordance with Bar

Code Identification Report and as specified in the DO/TO. Specific guidance for implementation for UID’s can be found at http://www.acq.osd.mil/dpap/pdi/uid/.

The Contractor shall comply with the Army’s Unique Identification (UID) policy signed on July

29, 2003, updated February 6, 2007 (or latest policy/policy update in effect as of the date of the

Task Order), for all contract deliverables. The DFARS rule 211.274 titled "Item Identification and

Valuation" and MIL-STD-130 titled "Identification Marking of U.S. Military Property" have been updated to reflect the UID policy.

The Contractor shall comply with the Department of Defense’s Radio Frequency Identification

(RFID) policy signed on July 30, 2004 (or latest policy/policy update in effect as of the date of the

Task Order). Business Rules for RFID can be found as attachments to this solicitation as well as the RFID web site www.dodrfid.org

4.13 Data and Data Management

Data is defined in other provisions of this contract, and in regulation. Requests for data under the

GTACS II contract will typically be specified on a DD Form 1423 “Contract Data Requirements

List” (CDRL). However, the Contractor shall provide data specified under the GTACS II contract and DOs/ TOs whether or not the DD Form 1423 is used.

All non-classified data identified in this PWS will be submitted to the Government as specified on the Contract Data Requirements Lists (DD Form 1423), or via e-mail if not so specified.

http://www.acq.osd.mil/dpap/pdi/uid/ https://r2csr.monmouth.army.mil/downloads/templates/AppData/Local/Microsoft/Windows/dwayne.k.terry/Local%20Settings/Bryan.McGann/Local%20Settings/sandra.rogan/Local%20Settings/Temporary%20Internet%20Files/Local%20Settings/Temporary%20Internet%20Files/Local%20Settings/Temporary%20Internet%20Files/OLKD7/Documents%20and%20Settings/suzanne.l.tilton/Local%20Settings/Temporary%20Internet%20Files/OLK3C6/www.dodrfid.org

The Contractor shall implement data management procedures during the GTACS II contract and each DO/TO as specified by the Government. All Contractor data shall be maintained up to date.

The Contractor shall archive all data developed during this contract. The Contractor shall maintain configuration management revision control for all versions of data prepared under this contract.

The Contractor shall allow the Government access to all data required by this contract. All data prepared for delivery to the Government shall be in a form and format specified in the contract and

DO/TO. When the Government does not specify the form or format for a data product it shall be assumed to be in “Contractor Format”.

Data submitted under the GTACS II contract shall be submitted using Microsoft Office suite of applications (MS Word, Excel, Access, Power Point, etc.) unless otherwise directed in the DO/TO.

All data shall be prepared in accordance with the applicable Contract Data Requirements List

(CDRLs) DD Form 1423 or as otherwise required by the FAR/DFARS and as required by the

DO/TO. Inspection and acceptance of data shall be as indicated on the DD Form 1423 and the

DO/TO. DFARS 252.246-7001 Warranty of Data applies to data ordered by the DD Form 1423s.

All DOD data and information provided to the contractor shall be considered “covered Defense information” for purposes of DFARs 204.72 unless otherwise stated.

4.13.1 PWS Data Requirements

Additional CDRLs will be specified in individual Task Orders.

5.0 Contract Administration

The contractor shall assign a technical single point of contact, also known as the Program Manager

(PM) who shall work closely with the Government DO/TO KO and COR as required. The PM shall be ultimately responsible for ensuring that the contractor’s performance meets all government contracting requirements within cost and schedule. PM shall have the requisite authority for full control over all company resources necessary for contract performance. Responsibilities shall also include, but not be limited to: personnel management, management of government material and assets, and security.

This is the start of the file's text. The full file is on GovTribe.

File details come from the government source that posted it.