AGATCS SDP IDIQ DRAFT SOW Version 1.docx

STATEMENT OF WORK (SOW)

ARMY GROUND AERIAL TARGET CONTROL SYSTEM (AGATCS) SUPPORT, DEVELOPMENT & PRODUCTION (SDP)

Prepared By

Threat Systems Management Office (TSMO) Project Manager (PM) for Cyber, Test & Training (CT2) Program Executive Office (PEO) for Simulation Training and Instrumentation (STRI) Bldg. 3203 Hercules Road, Redstone Arsenal, AL 35898 -7458

Table of Contents

UNCLASSIFIED/FOUO

STATEMENT OF WORK

ARMY GROUND AERIAL TARGET CONTROL SYSTEM

SUPPORT, DEVELOPMENT & PRODUCTION

i iii

STATEMENT OF WORK (SOW)

DEVELOPMENTARMY TARGET CONTROL SYSTEMS

AND ASSOCIATED ANCILLARY EQUIPMENT

1. OBJECTIVE

The Threat Systems Management Office (TSMO) located at Redstone Arsenal, AL, reports to the Project Manager for Cyber, Test & Training (PM CT2), headquartered in Orlando, FL. The TSMO mission is to provide threat systems for testing and training in live, virtual, and constructive environments. The objectives of this effort include engineering development; acquisition of targets, target control systems and spares; target operation support; training and planning.

1.1 Background

The Army Target Control System (TCS), currently known as the Army Ground Aerial Target Control System (AGATCS), is the Army’s primary aerial (full scale, subscale, rotary wing, small unmanned aerial system (SUAS)), and surface (ground/maritime) target control system. AGATCS enables remote control of Army targets with a single control system in support of weapon system live fire testing necessary for lethality evaluation and sensor package testing for evaluation of suitability and effectiveness. AGATCS systems are fielded to Army Test and Evaluation Command (ATEC) Test Centers: (White Sands Missile Range (WSMR), NM; Yuma Proving Ground (YPG), AZ; Aberdeen Proving Ground (APG), MD; Redstone Arsenal, AL, Dugway Proving Ground (DPG), UT) and TSMO Aerial Target Flight Services (Ft. Bliss, TX). Additional development to integrate new targets and new target control capabilities continues per the Test Capabilities Requirements Document (TCRD) prepared by ATEC.

AGATCS includes other areas of target control such as target test sets, avionics, and target instrumentation.

1.2 Scope

This Statement of Work (SOW) defines the general requirements for the support, development and production of new targets and new target control capabilities into the AGATCS and associated ancillary equipment and to provide upgrades for other miscellaneous target control systems. The Army TCS will be located at various Army, Navy, Air Force or other locations.

1.0 APPLICABLE DOCUMENTS AND DEFINITIONS

2.1 Delivery Orders

Delivery Orders (DOs) will be issued to accomplish specific requirements. Each DO will have a SOW which references requirements identified at the base Indefinite Delivery/Indefinite Quantity (IDIQ) level but with order level specific requirements which provide more detail. DOs may be issued at any time during the ordering period of the base IDIQ. Additionally, each DO may contain DO specific Contract Data Requirements Lists (CDRLs).

2.2 Applicable Documents

The applicable top-level documents are contained in the Contract Document Summary List (DSL), by number, title, date, contract reference and category. The document versions specified on the DSL take precedence over the generic references (those without the revision letters) cited in the SOW.

Performance specifications, engineering specifications, drawings, software documentation, operations manuals, and other available documentation generated by previous original equipment manufacturers and engineering service contractors for the Army TCS that technically defines existing hardware and software.

All data associated with this requirement will be in accordance with (IAW) Distribution Statement D.

2.3.2 “Ancillary equipment” is defined as surface (ground/maritime) target instrumentation (STI), aerial target instrumentation (ATI) and control and monitoring equipment for aerial, ground, and maritime targets. Included are the components of a target group set such as the transponder, datalink, encoder/decoder device, TICU and associated test equipment, avionics package, ground target interface equipment, maritime target interface equipment, vehicle control module, power conditioning modules, engine interface modules, system disconnect switches, emergency stop systems, radios, Global Positioning System (GPS) receiver, antennas and antenna switch, range interface processor; simulation/visualization processor, test sets, launch control equipment; and other airborne/ground/maritime target equipment. Also included are components for control and monitoring such as laptops, computers, antennas, monitors, video systems, and cables.

2.3.3 “Other airborne/ground/maritime target equipment” is defined as auxiliary and/or add-on devices which require control from the AGATCS to include autopilots, gyros, Inertial Measurement Units (IMU), bus nodes, processors, power supplies, actuators, payloads, altimeters, sensors, brackets, and wiring/cabling connecting those devices.

2.3.4 Any references to “the Government,” unless otherwise specified, shall mean the Procuring Contracting Officer (PCO), the Contracting Officer Representative (COR), or to the extent authorized by the PCO, the Government Project Director.

3.0 REQUIREMENTS

3.1 General

The requirements defined herein form the basis for all supplies and services to be delivered to the Government. This SOW defines the overarching scope of work for all DOs. The requirements to be performed as part of the engineering development shall be defined in general terms by the Base SOW with specific tasks further defined in the DO SOW. The contractor shall ensure compliance with the contract requirements and delivery of the required products and incidental services. The Government shall retain unlimited rights to all work, created, generated, or produced and required to be delivered under all DOs as defined at Defense Federal Acquisition Regulation Supplement (DFARS) clause 252.227-7020 (Rights in Special Works).

In accomplishing the work outlined in the SOW, the contractor shall not duplicate any work required by any other government contract. The contractor shall make known to the Government if duplicate work is requested by any Government agency.

3.1.1 Program Management

The contractor shall perform all management functions required to fulfill the requirements as stated in this SOW. The contractor shall designate a single point of contact (POC) to serve as the Government’s POC. The Government does not require the establishment of field offices for performance under this contract.

3.1.2 Kickoff Meetings/Post Award Conferences

The contractor shall participate in either a Kickoff Meeting or Post Award Conference after contract award and after DO award as directed by the Government. Key personnel and points of contact for both parties will be identified. The contractor shall be prepared to discuss the phase-in plan and the respective responsibilities of all parties. The purpose of the conference is to ensure that the contractor is prepared to execute the work required in the SOW. The contractor shall place emphasis on management plan implementation, agreement on metrics and measures, operating procedures, transition plan and other contract matters. The contractor shall prepare and submit Record of Meeting/Minutes in accordance with IAW CDRL A024.

3.1.3 Management Plan

The contractor shall submit a Management Plan. The management plan shall describe the contractor’s organization, assignment of functions, duties, and responsibilities, management procedures and policies, and reporting requirements for the conduct of contractually-imposed tasks, projects, or programs. The contractor shall prepare and submit Management Plan IAW CDRL A025.

3.1.4 Integrated Master Plan (IMP)

The contractor shall prepare and submit an IMP and an Integrated Master Schedule (IMS) IAW CDRL A026. The contractor shall maintain and manage to the IMP and IMS developed for each specific DO, including appropriate program milestones with corresponding entrance and exit criteria. The IMP shall include a detailed account of all tasks necessary to accomplish the goals and objectives of each specific DO.

3.1.5 Progress Reports

The contractor shall prepare and submit Monthly Progress Reports IAW CDRL A027. The report shall include schedules (proposed and actual), description of significant events (problems encountered, resolution, tests conducted, major findings), and disposition of the task(s) (cancelled, completed, carried forward to another DO).

3.1.6 Technical Reports

The contractor shall prepare Technical Study/Services Reports IAW CDRL A002 to document the work accomplished and results obtained from engineering studies and analyses or specific technical services performed as defined in appropriate DOs. The contractor shall prepare and submit Scientific and Technical Reports IAW CDRL A002.

3.1.7 Final Report

The contractor shall submit a Final Report at the conclusion of each DO IAW CDRL A027. This report shall document all work performed under each effort, and shall include all designs, analyses, test results, study findings, and recommendations.

3.1.8 Financial Reports

The contractor shall prepare the following:

· Performance and Cost Report IAW CDRLA007

· Contract Funds Status Report IAW CDRL A038

· Contract Invoicing and Payment Report IAW CDRL A012

· Contract Work Breakdown Structure IAW CDRL A037

3.1.9 Work Control

All data interchange shall be conducted in a digital environment compatible with the latest version of Microsoft Office family of products. The Contract shall query Government to ask for a designated standard naming convention for all electronic submissions as required.

3.1.10 Design Specification

The contractor shall submit a design specification for new developments or update an existing design specification for modifications to existing equipment that details hardware and software functional requirements and test and qualification requirements. The contractor shall prepare and submit Design Specification IAW CDRL A020.

3.2 Meeting and Reviews

The contractor shall conduct, attend, and participate in meetings and reviews. The specific locations, dates, and duration of the meetings will vary based on requirements. Meetings and reviews will be chaired by a government representative. The contractor shall prepare drawings and other data to aid in the presentations. The contractor shall have key personnel and support available to carry out the meeting. The contractor shall explain assumptions and methodologies in arriving at particular conclusions, recommendations, or alternatives in the accomplishment of the DOs. Subcontractors shall attend meetings and reviews when required to address key elements. The contractor shall prepare the meeting agenda, meeting minutes and presentation material appropriate for the meetings and reviews. The contractor shall prepare and submit Record of Meeting/Minutes IAW CDRL A024.

Except where noted herein, meetings and reviews shall be considered fulfilled when the following items are completed:

3.2.1 Integrated Product Team (IPT) Meetings

The contractor shall participate in scheduled IPT meetings. The IPT meetings shall be used to address development status of activities as well as discuss questions and issues in between scheduled management reviews. The contractor shall document action items and due dates, coordinate resolution, and track action items until closure. Action item closure shall require contractor and government approval. The contractor shall prepare and submit Issue Tracker IAW CDRL A024.

3.2.2 Program Management Review (PMR) Meetings

The contractor shall coordinate PMRs to review status and planned activities. Participants shall include contractor and government personnel. The contractor shall prepare and submit the PMR agenda. The contractor shall prepare and submit agenda IAW CDRL A021. At the conclusion of the PMR, the contractor shall prepare and submit Report, Record of Meeting/Minutes IAW CDRL A024 and Presentation Material IAW CDRL A022.

3.2.3 System Requirements Review-II- System Functional Review (SRR-II-SFR) The contractor shall conduct a combined SRR-II-SFR. The SRR-II-SFR is a multi-disciplined product and process assessment to ensure that the system under review can proceed into preliminary design, and that the system functional requirements, including derived and decomposed requirements, are defined and consistent with program cost, schedule, risk, and other system constraints. The SRR-II-SFR shall assess the system functional requirements and ensure that the required system performance is fully defined and is traceable to the functional baseline described in the SOW and associated specification.

The contractor shall submit the SRR-II-SFR agenda IAW CDRL A021.

3.2.3.1 SRR-II-SFR Entry/Exit Criteria

SRR-II-SFR entry and exit criteria will be identified within the DO SOW, when required.

3.2.4 Preliminary Design Review (PDR)

The contractor shall prepare and submit the PDR agenda IAW CDRL A021. The purpose of the PDR is for the Government to formally review the activities and work products generated by the contractor during the performance of the preliminary design stage in order to develop the allocated baseline, and to verify that the approach for the system design is ready to proceed into the detailed design phase. The contractor shall describe the proposed design and development schedule and submit IAW CDRL A022, Presentation Material no less than 7 business days prior to the PDR. Following the PDR, the contractor shall submit Report, and Record of Meeting/Minutes IAW CDRL A024.

3.2.4.1 PDR Entry/Exit Criteria

PDR entry and exit criteria will be identified within the DO SOW, when required.

3.2.5 Critical Design Review (CDR)

The contractor shall prepare and submit the CDR agenda IAW CDRL A021. The purpose of the CDR is for the Government to formally review the activities and work products generated by the contractor during the performance of the critical design stage in order to develop the product baseline, and to verify that the system is ready to proceed into the hardware-software coding, assembly, and integration phase. The contractor shall describe the proposed design and development schedule and submit, Presentation Material no less than 7 business days prior to the CDR IAW CDRL A022. Following the CDR, the contractor shall submit Report, Record of Meeting/Minutes IAW CDRL A021.

3.2.5.1 CDR Entry/Exit Criteria

CDR entry and exit criteria will be identified within the DO SOW, when required.

3.2.6 Technical Interchange Meeting (TIM)

The contractor shall participate in Technical Interchange Meetings (TIMs). During these meetings, the contractor shall present necessary data to enable a joint review of its various assigned efforts, along with attendant schedules, and resource expenditures. The contractor shall participate in technical discussions and inform the COR, in a timely fashion, of any problems with contract execution. The contractor shall present proposed solutions. The contractor shall conduct, attend, and participate in Verification, Validation and Accreditation (VV&A) meetings, and other meetings as scheduled by the PCO or written designee. The contractor shall submit Report, Record of Meeting/Minutes IAW CDRL A024 and submit Presentation Material IAW CDRL A022.

3.3 System Upgrades

The contractor shall develop, test, evaluate, and integrate improvements to the Army TCS software and hardware to achieve a target system capable of meeting the requirements of state-of-the-art weapons systems undergoing research, development, test and evaluation (RDT&E). These upgrades include: design, analysis, modification, fabrication of prototypes, proof of principle evaluation, test/demonstration, planning, data evaluation, troubleshooting, repair/refurbishment, simulation, system certification, training, documentation and reporting.

The contractor shall perform electrical and mechanical design including conceptual design, prototype fabrication, and prototype testing. Equipment designed by the contractor shall be fabricated, integrated into the defined end item, and tested as a complete operational unit.

The contractor shall conduct market surveillance and market investigations in order to maximize the use of commercial and non-developmental items. The hardware used shall be, to the maximum extent possible, commercial-off-the-shelf (COTS). To the maximum extent possible, all hardware shall be open architecture, modular, and non-proprietary. All computer related hardware, software, IT, or related services shall be purchased through the Army Computer Hardware, Enterprise Software and Solutions (CHESS) IT schedules in performing the requirements of each specific DO. Prior to using any commercial software, the Contractor shall provide copies of the software license agreements for the Government’s review. All software license agreements shall adhere to federal procurement law.

The contractor shall perform software design, modification, prototype generation and prototype testing. Software created by the contractor shall be integrated into the defined end item and tested as a complete operational unit.

End items designed by the contractor shall be fabricated and installed for establishment of developmental and operational test and evaluation at test ranges.

Commercial practices shall be employed for all system operation and maintenance procedures similar to those used by commercial industry and for aerial, ground and maritime manned and unmanned systems.

Items to be considered for Army TCS development shall include the following:

3.3.4 System integration for various Government agencies involving target operations. System integration shall be provided to Department of Defense (DOD) and inter-service initiatives to increase interoperability of target control systems especially with the Navy and Air Force target control systems. In accomplishing these requirements, the contractor shall coordinate and interface with the supported activities.

3.3.5 Development to improve the capabilities of the Army TCS and other airborne/ground/maritime target equipment, and their components. The need for improvements may be caused by obsolescence of components and subsystems or may be required to meet future operational requirements. Upgrades, modifications, and technology updates shall be designed and prototypes developed which are compatible with the existing equipment and functions of the control system elements.

3.4 Initial Equipment Development, Delivery, and Integration

The contractor shall engineer, acquire materials, and provide initial low rate fabrication of Army TCS systems, subsystems, and components required for the fielding of Army TCS at defined test ranges and other test locations as defined by the customer mission. The contractor shall provide training for fielding of all new equipment.

3.4.1 The contractor shall develop and deliver Army TCS systems, subsystems, and components. These materials may be required to be directly delivered to locations specified by the Government or used by the contractor for integration into higher level assemblies that are fabricated by the contractor.

3.4.4 The contractor shall submit training materials, user manuals and associated supplemental data/technical information published by the manufacturer on the assembly IAW CDRL A017 to support installation, operation, parts, and maintenance of each system. The contractor shall provide training to Government and contractor personnel on the installation and operations and maintenance of hardware procured. The contractor shall provide training to personnel on software developed under this contract.

3.5 Production Parts

The contractor shall provide essential part numbered components and repair of part numbered components to support the operation and maintenance of the Army TCS.

3.5.1 The contractor shall provide to the government the identity of changes (either additions or deletions) to part numbered components contained on the contractual components list to support the operation and maintenance of the Army TCS IAW CDRL A002. This approach will enable continued system support in the event of Army TCS changes affected via engineering services during the life cycle of the system.

3.5.2 The contractor shall ensure that hardware components manufactured (either manufactured by the contractor or procured from another manufacturer) and hardware components repaired are IAW the system's latest configuration management documentation and also compatible with specific Army TCS system software.

3.5.3 The contractor shall define economic order breakpoints and permit incremental coverage to include usage of maximum range quantity as requirements occur.

3.5.4 The contractor shall perform teardown and inspection (T&I) of identified unserviceable Army TCS components and furnish an estimate of repair and estimated delivery date of repaired serviceable item for Government review.

3.5.5 The contractor shall complete the repair/rebuild (R/R) action upon notification from the Contracting Officer's Technical Representative (COTR).

3.5.6 The contractor shall fabricate, obtain and test new part numbered components that are ordered by the Government and certify that they are form, fit and function equivalent to the same part numbered items that are in the Government inventory.

3.6 Field Support of the Army TCS

The contractor shall provide technical support for Army TCS missions in Continental United States (CONUS) and Outside Continental United States (OCONUS) locations. Contractor personnel should have subject matter specific knowledge and experience to support peculiar installation requirements, engineering testing, target operations, reprogramming, setup of TMO special projects, configuration of nonstandard targets, diagnostic and trouble-shooting of Army TCS failures, test equipment malfunctions, and other Army TCS related problems that require immediate resolution. Contractor personnel shall be capable of successfully providing onsite, immediate resolution for failures and malfunctions.

The contractor shall provide personnel with sufficient working knowledge on all airborne/ground/maritime targets controlled with Army TCS. The contractor shall be responsible for establishing and maintaining cohesiveness and consistency within/across AGATCS software. This will be an ongoing requirement. The contractor shall provide technical advice and recommend software upgrades and/or solutions that have the potential for transferability across various target types.

The contractor shall maintain/update all existing AGATCS software and identify commonalities to avoid duplicate efforts on various targets. Specific tasks may include software code updates/modifications/additions, system change requests (SCRs), participation in development/operational testing, troubleshooting in the field, completing cyber updates and completing field software updates. The contractor shall track SCRs and the Government will determine the priority of the SCRs and the contractor shall address the SCRs based on the priority given by the Government.

3.8 Field Service Engineer

The contractor shall provide on-site field service of Army TCS equipment for operations and deployments. Services may include set up equipment for test events and operational missions; aid in performing pre-mission checkouts; troubleshooting issues arising during target testing; monitoring the system controller for telemetry quality to maintain target communications during tests to ensure successful missions and recovery; recording mission command and telemetry data and preparing/providing to the customer; applying, verifying and validating software, hardware, firmware, and cybersecurity updates to fielded equipment or units under test; supporting field tests of new hardware or software; and assisting in integration of Army TCS into existing and future sites.

3.9 Other Direct Costs

The Government may require the Contractor to purchase hardware, software, firmware, maintenance, insurance, related supplies and other direct costs (ODCs) that are integral and necessary in support work as outlined in the SOW and subsequent orders. Such requirements will be identified at the time an order is issued or may be identified during the course of an order, by the Government or the Contractor.

ODCs, for material necessary for performance of this contract, shall be specified in individual orders and shall be reimbursed in accordance with the billing and payment clauses of this contract. The Contracting Officer will establish the maximum allowable amount of and determine the fair and reasonableness of the proposed price/prices. Proposed supplies and/or materials must be itemized and priced in the cost proposal. Prior to any purchases, the contractor shall coordinate requirements with the Contracting Officer’s Representative (COR), for further approval by the PCO.

3.10 Travel

Travel may be required to fulfill the requirements of the SOW. It is anticipated that contractor support may require travel both CONUS and OCONUS. Contractors shall be required to have a valid passport and current immunizations for OCONUS travel. The contractor shall be responsible for obtaining passports, immunizations, and/or visas for traveling contractor personnel. The contractor shall be responsible for funding and processing these requirements. Since the anticipated travel costs cannot be accurately forecasted, it shall be awarded on a reimbursable basis for actual allowable costs (supporting documentation required). All travel shall be in accordance with the Federal Travel Regulations (FTR) and the Joint Travel Regulations (JTR) and adhere to Federal Acquisition Regulation (FAR) 31.205-46. The contractor shall ensure that the requested travel costs will not exceed the amount authorized in this task order. Travel must be submitted for COR approval.

All travel must be authorized by the COR or other authorized approving official and be in compliance with the task order and all other applicable requirements. The contractor shall use only the minimum number of travelers and rental cars needed to accomplish the trip purpose. Travel shall be scheduled during normal duty hours whenever possible. Airfare will be reimbursed for actual common carrier fares which are obtained by the most reasonable and economical means. The contractor shall provide a Trip Report for each trip associated with a travel approval. The contractor shall maintain a summary of all approved travel, to include at a minimum, the name of the traveler, location of travel, duration of trip, total cost of trip.

3.11 Environmental

All contractor and subcontractor activities shall be in compliance with applicable federal, state, and local environmental laws and regulations. The Contractor shall ensure that design, maintenance, operation, manufacturing, programmatic decisions, and trade-off studies strive to eliminate or reduce hazardous materials and wastes. For systems, subsystems, ancillary devices, or other items developed or modified under this contract, the contractor shall prepare a Hazardous Materials Management Program (HMMP) Plan IAW CDRL A010 and National Aerospace Standard (NAS) 411. The contractor shall not use any Class I Ozone Depleting Chemical/Ozone Depleting Substance (ODC/ODS) (identified at http://www.epa.gov/ozone/ods.html) or any ODC/ODS solvents (identified at http://www.epa.gov/ozone/snap/lists/index.html in the manufacture or support of items required by this SOW unless a waiver is obtained from the Army Acquisition Executive. Any ODC/ODS refrigerant alternatives used must appear in the Environmental Protection Agency’s (EPA) Significant New Alternatives Policy (SNAP) list (identified at http://www.epa.gov/ozone/snap/lists/index.html and have received a toxicity clearance from the U.S. Army Public Health Command (USAPHC). The contractor shall prepare annual HMMP Reports IAW CDRL A009. The HMMP Reports shall provide the following information: (1) Any of the following materials that are contained within a user end item: EPA 17 List materials (identified at http://www.epa.gov/opptintr/3350/33finb1.htm), beryllium, coatings (identified by MIL SPEC), functional fluids (e.g. coolant, hydraulic fluid, petroleum products), energetics/solid rocket motor components (including Explosives Class Number), advanced composite materials (e.g. fabricated from silica, graphite, carbon, boron, fiberglass), batteries, Class I/Class II ODS/ODC materials, and asbestos; (2) A general description (to include a graphic or drawing) of where these materials are located within the end item; (3) Required maintenance/repair/support materials to include: EPA 17 List materials, sealants, adhesives, coatings (identified by MIL SPEC), and Class I/Class II ODS/ODC materials; and (4) any Emergency Planning and Community Right-to-Know Act (EPCRA) 302/313 materials utilized in the manufacturing process (identified in EPA 550-B-19-003 / June 2019 and found at https://www.epa.gov/sites/production/files/2015-03/documents/list_of_lists.pdf). The contractor shall provide immediate notification of any proposed hazardous material mitigation/elimination efforts that may adversely impact schedules, cost and/or performance.

4.0 SAFETY

4.1 Safety Program Plan

The contractor shall prepare and submit a Safety Program Plan IAW CDRL A023 covering operations and activities to be performed. The Safety Program Plan shall incorporate the controls for the safety of personnel and property and shall assure compliance with applicable Federal, State, Department of the Army and local safety and environmental requirements.

4.2 Safety Assessment Report (SAR)

The contractor shall submit a Safety Assessment Report IAW CDRL A001.

4.3 Accidents/Incidents

The contractor shall maintain an accident prevention program to ensure the Government assets are protected from damage and theft. The contractor shall prepare and report any accidents/incidents in the Accident/Incident Report IAW CDRL A011.

4.4 Operations Safety

The contractor shall comply with all safety procedures and practices set out during mission support activities at host installation/ranges. The contractor shall be responsible for the safety of their personnel and provide contractor personnel with any required personal protective items such as safety shoes, protective eyewear, hearing protection and other personal protective items.

5.0 SECURITY MANAGEMENT

The general scope of the work defined by the SOW is unclassified. However, the contractor may be required to be at a location where other classified work is being conducted or classified material may be disclosed to the contractor in the normal conduct of work. Therefore, in accordance with the Defense Department (DD) Form 254, Contract Security Classification Specification, the contractor shall provide personnel with the necessary security clearances and shall provide the appropriate protection for classified or sensitive information normally acquired in the performance of the SOW. Should a DO SOW require classification above the level of the base IDIQ DD254, a separate DD254 will be issued for that DO.

5.1 Classified information provided by the Government in support of the Army TCS, or developed or acquired by the contractor in accomplishing this contract, shall be handled in accordance with the procedures established in DOD 5220.22-M, National Industrial Security Program Operating Manual, and in accordance with the DOD Form 254, DOD Contract Security Classification Specification.

5.1.1 For Official Use Only (FOUO) information provided by the Government in support of the Army TCS, or developed or acquired by the Contractor in accomplishing this contract, shall be handled in accordance with the procedures established in DOD 5200.1-R, DOD Information Security Program.

5.1.2 The Contractor shall provide any request for release of information on the Army TCS from persons or organizations outside of the Government. All request will be referred to the Contracting Officer for consideration in accordance with DOD 5400.7-R, DOD Freedom of Information Act (FOIA) Program.

5.1.3 The contractor may provide release of general business reports or product information to the general public, including media representatives, pertaining to the contractor’s organization, finances, or publicly available products if not restricted in any way by the SOW.

5.1.4 Contractor employees, to include subcontractor employees, requiring access to Army installations, facilities and controlled access areas shall complete Anti-Terrorism (AT) Level I awareness training within 30 calendar days after DO award date. The contractor shall submit certificates of completion for each affected contractor employee and subcontractor employee, to the PCO or COR, if assigned. AT level I awareness training is available at the following website: https://atlevel1.dtic.mil/at.

5.1.5 Access and General Protection/Security Policy and Procedures. Contractor and all associated subcontractors employees shall comply with applicable installation, facility and area commander installation/facility access and local security policies and procedures (provided by Government representative). The contractor shall also provide all information required for background checks to meet installation access requirements to be accomplished by installation Provost Marshal Office, Director of Emergency Services or Security Office. Contractor workforce must comply with all personal identity verification requirements as directed by DOD, Headquarters, United States Department of the Army (HQDA) and 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.

5.1.6 AT Awareness Training for Contractor Personnel Traveling Overseas. This standard language text requires US-based contractor employees and associated subcontractor employees to receive Government provided Area of Responsibility (AOR) specific AT awareness training as directed by Army Regulation (AR) 525-13. Specific AOR training content is directed by the combatant commander with the unit Antiterrorism Officer (ATO) being the local point of contact.

5.1.7 IWATCH Training. The contractor and all associated subcontractors shall brief all employees on the local watch program (training standards provided by the requiring activity ATO). This local developed training shall be used to inform employees of the types of behavior to watch for and instruct employees to report suspicious activity to the COR. This training shall be completed within 60 calendar days of award and within 30 calendar days of new employees commencing performance with the results reported to the PCO or COR no later than 60 calendar days after award.

5.1.8 The contractor shall complete the DOD Information Assurance Awareness training prior to accessing the Information System (IS) and then annually thereafter.

5.1.9 The contractor shall develop an Operations Security (OPSEC) Standing Operating Procedure (SOP)/Plan IAW CDRL A019 to be reviewed and approved by the responsible Government OPSEC officer, per AR 530-1, Operations Security. This is required for contracts that require an OPSEC standing Operating Procedure/Plan This SOP/Plan shall include the Government's critical information, why it needs to be protected, where it is located, who is responsible for it, and how to protect it. In addition, the contractor shall identify an individual who shall be an OPSEC Coordinator. The contractor shall ensure this individual becomes OPSEC Level II certified per AR 530-1.

5.1.10 For Contracts that Require OPSEC Training. Per AR 530-1, Operations Security, new contractor employees must complete Level I OPSEC training within 30 calendar days of reporting for duty. All contractor employees must complete annual OPSEC awareness training.

5.1.11 For Information Assurance (IA)/information technology (IT) training all contractor employees and associated subcontractor employees shall complete the DOD IA awareness training before issuance of network access and annually thereafter. All contractor employees working IA/IT functions shall comply with DOD and Army training requirements in DOD 8570.01-M and AR 25-2 within six months of employment.

5.1.12 For Contract Requiring Performance or Delivery in a Foreign Country, DFARS 252.225-7043, Antiterrorism/Force Protection for Defense Contractors Outside the US. This clause applies to both contingencies and non-contingency support. The key AT requirement is for non-local national contractor personnel to comply with theater clearance requirements and allows the combatant commander to exercise oversight to ensure the contractor’s compliance with combatant commander and subordinate task force commander policies and directives.

5.1.13 For contracts that require handling or access to Classified Information. Contractor shall comply with FAR 52.204-2, Security Requirements. This clause involves access to information classified “Confidential,” “Secret,” or “Top Secret” and requires contractors to comply with The Security Agreement (DD Form 441), including the National Industrial Security Program Operating Manual (DOD 5220.22-M) and any revisions to DOD 5220.22-M, notice of which has been furnished to the contractor.

6.0 CYBERSECURITY

The contractor shall provide IA system-level support functions IAW provisions in the following documentation and references in Special Provisions (Appendix A of the SOW):

The contractor shall implement and/or be compliant with the following:

· Army Best Business Practices Federal Information System Management Act (FISMA) security requirements, Appendix II of OMB A-130

· Security Technical Implementation Guides (STIGs) compliance, patch management, Information Assurance Vulnerability Management (IAVM), AR 380-5

· National Security Telecommunications and Information Systems Security Policy (NSTISSP), No. 11 with revisions

· Department of Defense Instruction 8500.1: Cybersecurity, DODI 8500.01

· Network Enterprise Technology Command (NETCOM) Tactics Techniques and Procedures (TTPs)

· Department of Defense Instruction 8510.01: Risk Management Framework (RMF) for DOD Information Technology (IT), DODI 8510.01

· The Federal Information Processing Standard (FIPS) Publication 140-2, (FIPS PUB 140-2)

· National Institute of Standards and Technology (NIST), Special Publications (SP) 800-53 and 800-53A Security and Privacy Controls for Federal Information Systems and Organizations

· NIST SP 800-39

· FIPS 200-Minimum Security Requirements for Federal Information and Information Systems

6.1 Cybersecurity Training

The contractor shall require that lead and support personnel performing IA-enabled job functions possess the Information Assurance Management (IAM) or Information Assurance Technical (IAT) certification relevant to their role within the execution of this contract and IAW DOD 8140.01, DOD 8570.01-M and AR 25-2 (4-3 Information Assurance Training) engineers, analysts, and technicians shall complete the required DOD Cybersecurity Training on an Annual basis. Method of training for "DOD CyberAwareness Training" is https://cs.signal.army.mil/courses.asp, titled "DOD Cyber Awareness Training.” The contractor’s CybersecurityTeam shall complete the required "Cyber Security Fundamentals (CSF) formerly known as the IAF" every two years.

6.2 Cyber Documentation

The contractor shall establish a program cybersecurity liaison with the Government or designee to provide and maintain up-to-date status of cybersecurity accreditation/remediation efforts IAW CDRL A003. The contractor shall assist in the upkeep of the System Security Plan (SSP), System Contingency Plan (SCP), System Configuration Management Plan (SCMP), systems Plan of Action and Milestones (POA&M), STIG Deviation Reports, Accreditation Boundaries, Software and Hardware Lists for each system configuration.

6.3 Cyber Tools and Reports

The contractor shall configure the system to maintain an Authority to Operate (ATO) certification to the RMF Confidentiality Integrity and Availability (CIA) and Certification Level (CL). The contractor shall coordinate with the Government to maintain the system accreditation by incorporating STIG compliance updates and mitigating the results of penetration testing into all software baseline release activities. The contractor shall perform automated and manual IAVM scans per the latest STIG requirements and incorporate the updates into each subsystem/system software revision. In the event that Defense Information Systems Agency (DISA) ceases support for the current, Information Assurance toolset (For example: Assured Compliance Assessment Solution (ACAS)/Nessus and Security Configuration Automation Protocol (SCAP) is required for Vulnerability Testing, and for Security Coding Tool an example is Fortify), the contractor shall migrate to an alternative toolset, an action that will be directed by the Government. This data shall be incorporated into the appropriate System POA&M in order to maintain the ATO. The contractor shall fix or mitigate items from the POA&M per Government direction and shall update. The contractor shall incorporate IAVM updates for each system configuration into the system software development process, to include sub-systems, IAW the POA&M; IAVM updates shall be integrated into the fielded system software release IAW approved SSP and NETCOM TTP or in each software revision, whichever comes first.

The contractor shall prepare and submit a schedule for IA activities including system cybersecurity updates for insertion into system software releases, the update cycle for STIG review, implementation, and compliance, mitigations, technical reports, and any other pertinent IA activities IAW CDRL A003.

The contractor shall support the annual review of each accredited system/sub-system's IA controls according to FISMA guidance in conjunction with the TSMO Information System Security Manager (ISSM) and or PEO STRI IA designee. The contractor shall conduct cybersecurity scans on GFE.

The contractor shall follow production specification and evaluation requirements of the NIST SP 800.53 Security and Privacy Controls for Federal Information Systems and Organizations, Committee on National Security Systems Instruction (CNSSI) 4009, CNSS Glossary, Common Criteria, and National Information Assurance Partnership (NIAP) Approved Product List (APL). All incorporated IT products, and IA-enabled IT products that require use of the product's cybersecurity capabilities, acquired under the contract, shall comply with the National Security Telecommunications and Information Systems Security Policy (NSTISSP) No. 11 "National Policy Governing the Acquisition of Information Assurance (IA) and IA-enabled Information Technology Product." All contractor developed products shall be secured IAW STIG’s and tested with a Software Code Security Tool in order to make sure contract develop software is secure prior to be applied to baseline of system.

6.3.1 Cyber Reports and Tasks Schedules

The contractor shall provide technical support on developing the following reporting requirements IAW CDRL A003.

· Assistant Secretary of the Army for Acquisition, Logistics & Technology ASA (ALT), Department Chief Information Officer (CIO)-G6 Headquarters, and PEO STRI Tasks

· Quarterly IAVA Reports

· IAVA Reports could be more than quarterly if a tasker requires PEO STRI, ASA (ALT) or Department CIO-G6 Headquarters requests an update.

· FISMA Annual Review Reports

· ACAS/Nessus Scan Reports

· SCAP Scan Reports on all COTS software

· Database Scan Reports

· Software Security Reports

· Updated NETCOM Software and Hardware Lists

· STIG Deviation Reports

· STIG Checklists

· IAVA Reports

· Ports, Protocols and Services (PPS) Lists

· STIG Lists (by type, version and release)

· Updated Configuration Drawings

· POA&M

· RMF Re-accreditation Reports

· ACAS/Nessus Scan Reports

· SCAP Scan Reports on all COTS software

· Database Scan Reports

· Software Security Reports

· Updated Software and Hardware Lists

· STIG Deviation Reports

· STIG Checklists

· IAVA Reports

· PPS Lists

· STIG Lists (by type, version and release

· Updated Configuration Drawings

· POA&M

· Vulnerability Scan Reports Bi-Annually

· ACAS/Nessus Scans

· SCAP Scan Reports on all COTS software

· Database Scan Reports

· Software Security Reports

· STIG Deviation Reports

· Updated Configuration Drawings

· POA&M

· Cybersecurity Posture Analysis Checklist (CPAC)

· ACAS/Nessus Scan Reports

· SCAP Scan Reports on all COTS software

· Database Scan Reports

· Software Security Reports

· Updated Software and Hardware Lists

· STIG Deviation Reports

· STIG Checklists

· IAVA Reports

· PPS Lists

· STIG Lists (by type, version and release

· Updated Configuration Drawings

· POA&M

· Training Reports Monthly

· Acceptable Use Policy (AUP)

· Privileged Access Agreements (PAA)

· RMF Monthly Report

· Annual Cyber DOD Certificates

· Cyber Security Fundamentals

· MISC Cyber Training/Certification (Security +, Other Cyber Training)

6.3.2 Computer Hardware Enterprise Software Solutions Program (CHESS)

The Contractor shall comply with the Army's CHESS program, under PEO Enterprise Information System. CHESS is the mandatory source for commercial IT purchases. CHESS contracts provide IT products and services that comply with NETCOM, Army and DOD policy and standards. The Contractor shall procure commercial hardware and software IT requirements by utilizing CHESS contracts and DOD Enterprise Software Initiative agreements first, regardless of dollar value.