W900KK-20-R-0020_SOW-FD_RevC111419.docx

STATEMENT OF WORK (SOW)

ENGINEERING SERVICES

FOR

ARMY TARGET CONTROL SYSTEMS

AND ASSOCIATED ANCILLARY EQUIPMENT

1 October 2019

Prepared By

Targets Management Office (TMO) Project Manager for Cyber, Test & Training (CT2) Program Executive Office for Simulation Training and Instrumentation Bldg. 3203 Hercules Road, Redstone Arsenal, AL 35898 -7458

Table of Contents

STATEMENT OF WORK (SOW)

ENGINEERING SERVICES

FOR

ARMY TARGET CONTROL SYSTEMS,

AND ASSOCIATED ANCILLARY EQUIPMENT

1.0 OBJECTIVE

The Targets Management Office (TMO) located at Redstone Arsenal, AL, reports to the Project Manager for Cyber, Test & Training (PM CT2), headquartered in Orlando, FL. The TMO mission is to provide all types of targets for the U.S. Army, other DOD customers and foreign clients. Efforts to conduct this mission 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 have been fielded to Army Test and Evaluation Command (ATEC) Test Centers: (White Sands Missile Range (WSMR), NM; Yuma Proving Grounds (YPG), AZ; Aberdeen Proving Grounds (APG), MD; Redstone Arsenal, AL, Dugway Proving Ground (DPG), UT) and also to TMO 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 development and integration 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 Target Control Systems (TCS) will be located at various Army, Navy, or Air Force locations.

2.0 APPLICABLE DOCUMENTS

a. All applicable documents cited in the Document Summary List (DSL) by number, title, and date.

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

3.0 REQUIREMENTS

3.1 General

3.1.1 The contractor shall, under the terms, conditions, and provisions set forth herein, furnish sufficient personnel, labor, equipment, supplies, materials, engineering and other services to accomplish work in accordance with (IAW) procedures outlined in this SOW.

3.1.2 In accomplishing the work outlined in the SOW, the contractor shall not duplicate any work required by any other government contract.

3.1.3 The contractor shall identify a Technical Manager to manage this effort and serve as a counterpart to the Government Project Director. The Government Project Director is an individual appointed to exercise overall technical management of this engineering services contract. Additionally, the contractor is required to provide points of contact for Government counterparts (e.g., contracts, budget/billing).

3.1.4 The contractor shall perform electrical and mechanical design including software, conceptual design and prototype fabrication, and prototype testing.

3.1.5 Equipment designed by the contractor shall be fabricated, integrated into the defined end item, and tested as a complete operational unit.

3.1.6 End items designed by the contractor shall be fabricated and installed as necessary for establishment of initial test and evaluation operations at test ranges.

3.1.7 The contractor shall provide training and engineering assistance to operations in support of AGATCS, TICU, and Associated Ancillary Equipment.

3.2.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, 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.

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

3.2.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.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 – COTS or GOTS. 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 subESM.

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.1 Upgrade of Army TCS applications to include software and hardware solutions to meet new target control system requirements, identification of available options (including modification of existing systems or subsystems), and design of new target control subsystems or ancillary devices to meet customer requirements. This may include system engineering, and development of engineering documents and specifications for system upgrades.

Development and fabrication of prototype equipment and proof of principle evaluation tests that include installation and integration of subsystems, environmental testing and other testing required to determine the performance and/or improve the design of the Army TCS components and other airborne/ground/maritime target equipment.

3.3.2 Software engineering development, modification, documentation, management, quality control, configuration management and deployment of software.

3.3.3 System integration for various Government agencies involving target operations. System integration shall be provided to 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.4 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.

The contractor shall provide technical support for Army TCS missions in CONUS and 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 identify efficiencies that can be gained by making updates/changes across all target platform software and shall present these to the government for inclusion in the SubESM. 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.7 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.8 Other Direct Costs

The contractor shall provide supplies and services that are not immediately available through the Government supply system, and any other items needed to maintain operational capability for the AGATCS under the SOW. Prior to any purchases, the contractor shall coordinate requirements with the COR, for further approval by the PCO.

3.9 Travel

The contractor shall submit all travel requests to the COR for review and the PCO for approval. Reimbursement for rental car, lodging, and meals and incidental expenses will be reimbursed IAW Joint Travel Regulation (JTR). The contractor will be reimbursed for allowable and allocable costs with proper authority and supporting documentation.

3.10 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 A014 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 EPA’s 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 A013. 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 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 The contractor shall maintain an accident prevention program to ensure that the Government assets are protected from damage or theft. Reports of accidents/incidents shall be coordinated with the Government Project Director’s Representative, Range Safety, TMO, and the Garrison Safety Office and prepared IAW CDRL A016.

4.1.1 For all hardware, software, and personnel safety, the contractor shall manage, analyze, identify, perform risk assessment, and mitigate safety and health hazards for all configurations of the Army TCS IAW MIL-STD-882, and AMCOM Regulation 385-17.

4.1.2 For improvements or modifications that may affect the inherent level of safety of the Army TCS, the contractor shall prepare a Safety Assessment Report (SAR) IAW CDRL A002 and MIL-STD-882. The SAR shall provide a comprehensive evaluation of all software and hardware safety risks and shall identify and evaluate all identified design and procedural hazards present. The SAR shall identify all safety features of the modified hardware and software.

4.1.3 The contractor shall conduct system safety reviews as an integral part of scheduled program reviews. Ad hoc system safety reviews may be scheduled at the discretion of the Government or in response to a request by the contractor.

5.0 SECURITY

The work defined by this 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 defined by this SOW. Therefore, in accordance with the 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 this SOW.

5.1 Security Management

5.1.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, incorporated into the contract.

5.1.2 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.3 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.4 The Contractor shall 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 this SOW.

5.1.5 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 contracting officer, if a COR is not assigned, within 30 calendar days after completion of training by all employees and subcontractor personnel. AT level I awareness training is available at the following website: https://atlevel1.dtic.mil/at.

5.1.6 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, 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.7 AT Awareness Training for Contractor Personnel Traveling Overseas. This standard language text requires US-based Contractor employees and associated sub-contractor employees to make available and to 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 Antiterrorism Officer (ATO) being the local point of contact.

5.1.8 IWATCH Training. The Contractor and all associated sub-Contractors shall brief all employees on the local watch program (training standards provided by the requiring activity ATO). This local developed training will be used to inform employees of the types of behavior to watch for and instruct employees to report suspicious activity to the COR. This training shall be completed within 60 calendar days of contract award and within 30 calendar days of new employees commencing performance with the results reported to the COR NLT 60 calendar days after contract award.

5.1.9 The Contractor shall complete the DoD Information Assurance Awareness training prior to access to the IS and then annually thereafter.

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

5.1.11 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 their reporting for duty. All Contractor employees must complete annual OPSEC awareness training.

5.1.12 For Information Assurance (IA)/information technology (IT) training. All Contractor employees and associated sub-Contractor 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, DoD 8570.01-M and AR 25-2 within six months of employment.

5.1.13 For Contract Requiring Performance or Delivery in a Foreign Country, DFARS Clause 252.225-7043, Antiterrorism/Force Protection for Defense Contractors Outside the US. The clause shall be used in solicitations and contracts that require performance or delivery in a foreign country. This clause applies to both contingencies and non-contingency support. The key AT requirement is for non-local national Contractor personnel to comply with theater clearance requirements and allows the combatant commander to exercise oversight to ensure the Contractor’s compliance with combatant commander and subordinate task force commander policies and directives.

5.1.14 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 Information Assurance (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

· NETCOM Tactics Techniques Plans (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 DoDD 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 A005. 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 Risk Management Framework (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 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 Information Assurance 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 A005.

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

The contractor shall follow production specification and evaluation requirements of the National Institute of Standards and Technology (NIST), Special Publications (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 A005.

· ASA(ALT), Department 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

· Ports, Protocols and Services (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

· Ports, Protocols and Services (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)

7.0 Product/Quality Assurance

The contractor shall provide Product Assurance (PA) technical expertise to include the utilization of PA management and technical principals, inspection techniques and other analytical and empirical tools during the development and production of systems/subsystems/components developed.

The contractor shall implement and maintain a quality system that meets the requirements of ANSI/ASQC/Q9001/ISO/Q9001/Q10012-1 or propose an equivalent system. The contractor's quality procedures, planning and all other documentation and data that comprise the quality system (for both hardware and software) shall be made available for Government review throughout the contract.

7.1 Quality System Plan (QSP)

The contractor shall provide its QSP IAW CDRL A004. The contractor’s QSP shall describe in detail the approach to implement and maintain a basic quality system that meets the requirements of ANSI/ISO/Q9001 or equivalent. The QSP shall provide for controls of process and product characteristics and include criteria and methodology that are used to validate conformance to performance specifications and to achieve functional areas in the design, test, production, and management processes. If the contractor proposes to use a quality system that has not been approved under the Department of Defense Common Process (or Standard Process) Initiatives for DOD contracts, the description shall address at least the following twenty elements: management responsibility; quality system; contract review; design control; document and data control; purchasing; control of customer supplied product; product identification and traceability; process control; inspection and testing; control of inspection, measuring and test equipment; inspection and test status; control of nonconforming product; corrective and preventive action; handling, storage, packaging, preservation, and delivery; control of quality records; internal quality audits; training; servicing; and statistical techniques.

The QSP shall include a description of the contractor’s:

- Electrostatic Discharge Protection.

- Quality Assurance Provisions.

- Product Acceptance System and validation methodology.

- Environmental Stress Screening.

- Special Test/Inspection Equipment and validation methodology.

7.2 Parts, Materials, and Processes (PMP) Control Program

The contractor shall submit a PMP Control Program Plan as part of the QSP. The PMP Control Program Plan shall include a description of the methods of process controls, documentation, and verification of continued process improvement, and the controls and policies for the following subjects as applicable:

· COTS Selection and Qualification

· Obsolete Parts/Diminishing Manufacturing Sources and Material Shortages

· Test/analysis requirements to assure piece parts/materials specification compliance for parts procured non-compliant to Government or DOD-adopted industry standards, including custom parts.

· Printed Wiring assembly (PWA) design and component mounting processes

· Electrostatic Discharge (ESD) control

· Maintenance and equipment used for electronic manufacturing processes

· Process controls, workmanship methodologies and procedures

· Training/proficiency of the workforce

· Rework and repair of PWAs and cable assemblies

7.3 Electronics Fabrication Procedures

Processes utilized for the manufacture and repair of electronic hardware will produce assemblies and equipment that meet the system performance requirements. The contractor’s electronic fabrication plan shall describe the materials, methods, and verification criteria for producing quality electrical interconnections and assemblies and shall utilize process control methodologies for the planning, implementation, and evaluation of the fabrication process. The contractor shall use IPC/EIA J-STD-001, Class 3 as guidance in developing this plan.

7.4 Test Plans

The contractor shall prepare and submit acceptance test plans IAW CDRL A007. The contractor shall prepare and submit acceptance test reports IAW CDRL A009. For any product or service provided under this contract, the contractor shall make all test plans and/or reports available for Government Review and verification.

7.5 Validation of Special Inspection/Test Equipment

Inspection and test equipment used to verify acceptance criteria specified in the controlling document shall require validation. The contractor shall verify that the Special Inspection Equipment will perform the function for which it has been designed and shall perform an equipment validation/proofing. The validation/proofing shall be in accordance with contractor developed instructions and shall assure acceptance of known good hardware and the rejection of hardware with known faults. The government reserves the right to witness the validation/proofing activities. Any change that invalidates the original criteria may require revalidation.

7.6 Quality Accreditation Programs

A contractor with an ANSI/ASQC Q9000 or ISO Q9001 third party registration (through a registrar accredited by the Registrar's Accreditation Board (RAB)) may submit the scope of the registration as evidence of the contractor’s compliance to the basic quality system requirements or a contractor may submit evidence of DOD approval of a Common Process or Standard Process Initiative for its basic quality system. If the contractor furnishes either of the cited documents as evidence of meeting the basic quality requirements, the overall QSP shall address the requirements of the PMP Control Program and the Electronic Fabrication Procedures sections of this document.

7.7 Latent Defects

The Government will accept any commercial warranty provided by the original product manufacturer. Additionally, the contractor will be responsible for any latent defects discovered during the life of the product. A latent defect is defined as a flaw, weakness, imperfection or defect which adversely affects critical performance requirements of the delivered product that is not apparent and cannot be discovered by observation or a reasonably careful inspection at the time of acceptance by the Government.

8.0 REVIEWS AND REPORTS

8.1 Software/Hardware Reviews

The contractor shall provide technical input and analysis for Government conducted reviews of the software/hardware work under this SOW. Adequate documentation shall be prepared IAW CDRL A006 in contractor format to facilitate the Government review.

8.2 Conferences

Conferences may be requested by the contractor or called by the Government to coordinate activities required by this SOW. The Government will consult with the contractor prior to establishing the conference date(s) and proposed agenda. The Government plans to hold monthly discussions and quarterly review meetings.

8.3 Engineering Accomplishment Reports

The contractor shall prepare Engineering Accomplishment Reports IAW CDRL A001 that describes the work performed under each Sub-ESM.

8.4 Technical Study Reports

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

8.5 Performance and Cost Reports

The contractor shall prepare a Performance and Cost Report IAW CDRL A010 and Contract Funds Status Report IAW CDRL A023. The reports shall address the cost status of each Sub-ESM, identify cost problems within each Sub-ESM effort and address the work status of each Sub-ESM.

9.0 CONFIGURATION MANAGEMENT/TECHNICAL DATA

9.1 Technical Data

The contractor shall prepare a variety of technical data sets. Those data sets may include the following:

· Product drawings (product baselines) IAW CDRL A012

· Interface Control Drawings or Documents IAW CDRL A017

· Manuals (technical, user, operations) IAW CDRL A022

· Engineering IAW MIL-STD-31000

· Drawing Trees IAW CDRL A018

· Computer Software Product IAW CDRL A019

· Software Version Description IAW CDRL A020

· Software Product Package IAW CDRL A021

9.1.1 The contractor shall maintain technical documentation of hardware and software changes to the Army TCS for changes resulting from engineering work performed under this contract. The contractor shall update existing technical documentation and prepare new drawings IAW CDRL A012 using best commercial practices. The contractor shall prepare or update performance-based product/process specifications IAW CDRL A015 in contractor format using best commercial practices to the lowest level of the work breakdown structure to adequately define the system/equipment. The contractor shall prepare performance-based specifications for all items designated as spares/repair parts. The contractor shall prepare engineering drawings and associated lists IAW CDRL A012 using industry standards to the depth of information required to fully define an item of hardware.

The contractor shall submit all technical data created or updated to the Government. The contractor shall provide reproductions of existing technical data applicable to work performed IAW CDRL A011.

9.2 Technical Data Package (TDP)

The contractor shall maintain a Technical Data Package (TDP) in sufficient detail using best commercial practices IAW CDRL A012 to allow for full and open competitions for the Army TCS systems or subsystems. The contractor shall certify that all TDP documentation prepared as a result of this SOW contains sufficient information with which the Government can procure from other sources identical items, components, and software products without additional design effort or recourse to the original design activity.

The contractor shall prepare and provide all documentation, drawings, and software to the Government in native format with all necessary files and shall provide all software/firmware in executable form to properly operate the system under development.

9.3 Configuration Control

The contractor shall maintain configuration control of the development baseline documentation IAW the contractor’s established CM procedures for the duration of this contract or until Government approval of the Engineering Release Record (ERR) establishing the Product Baseline. No changes to the baseline documentation shall be made without coordination and agreement with the Government. The contractor data management program shall provide visibility of contract data requirements and all significant contractual events and assure the currency and timeliness of all contractually required data. The contractors Technical Data Package shall be accessible to the Government through electronic access. Classified material shall not be delivered electronically.

10.0 ENGINEERING SERVICES MEMORANDA (ESM)

10.1 General.

10.1.1 All efforts performed under this SOW shall be provided in accordance with the ESMs and this SOW.

10.1.2 ESMs shall contain both man-hour and dollar value limitations. Sub-ESMs will specify man-hours, a dollar value, and contain time phased technical milestones. Man-hours and dollar limitations in the Sub-ESMs shall not be exceeded.

10.2 ESM Structure

10.2.1 The contractor shall perform the Engineering Services IAW the Base ESMs. The contractor shall allocate to each Base ESM the total contract funds needed to support the ESM to completion. The cumulative allocation under the Base ESMs shall at no time exceed the total contract funds.

10.2.1.1 A Sub-ESM shall describe each specific effort under the Base ESM.

10.2.1.2 Funding required for a Sub-ESM shall be obtained from the Base ESM. The total of all specific expenditures under all Sub-ESMs shall at no time exceed the total funds allocated under the Base ESM.

10.2.1.3 At the completion of each Sub-ESM, the contractor shall prepare a Final Report on that Sub-ESM IAW CDRL A003.

10.3 Origination of ESMs.

The Government Project Director may originate new Base ESMs or Sub-ESMs IAW CDRL A008 at any time during the performance of this contract.

10.3.1 Revision of ESMs. In the event it becomes necessary to make any additions, deletions, or revisions to a Base ESM or a Sub-ESM, the Government Project Director shall prepare a revised Base ESM or Sub-ESM IAW CDRL A008.

10.3.2 In no case shall the contractor expend funds on a Sub-ESM beyond the original estimated cost prior to review, concurrence, and approval by the Government of a revision establishing a new estimated cost and delivery schedule. The contractor shall notify the Government when 75 percent of the funds allocated to the Sub-ESM have been expended.

10.3.3 The Contracting Officer’s Representative (COR) may authorize the shifting of effort from one Sub-ESM to another Sub-ESM or new Sub-ESM (within the same Base ESM and CLIN). This shall be accomplished by official revision and/or preparation of the Sub-ESMs affected. This does not authorize the redirection of effort outside the contract scope.

10.3.4 The contractor shall prepare, upon request by the Government, a Sub-ESM IAW CDRL A008 to provide the necessary effort to accomplish any related task required by the Government Project Director. The explicit requirements of a Sub-ESM shall take precedence over the more general requirements in the Base ESMs.

10.4 Priority of ESMs and Sub-ESMs.

The Government reserves the right to establish priority of all tasks under this contract.

10.5 Duplication.

Sub-ESMs shall not be submitted for tasks where any portion has previously been submitted on a Sub-ESM and disapproved, unless specifically requested by the Government.

10.6 Sub-ESM Preparation.

A Sub-ESM shall not be submitted to cover the preparation of Sub-ESMs.

10.6.1 Numbers assigned to disapproved Sub-ESMs shall not be reassigned to subsequent Sub-ESMs.

10.6.2 Duplication of work covered by a previous Sub-ESM shall be sufficient basis for disapproval of a proposed Sub-ESM. The cost of duplication of work under this contract for effort performed under this or any other contract with the Government will not be reimbursable.

10.6.3 Content of Each Sub-ESM. Each Sub-ESM prepared for submittal shall be complete and shall include a statement as to the related effect(s) of the effort on any other Sub-ESM under this contract. Each Sub-ESM shall define all associated costs such as the man-hours, materials cost, and other costs (e.g., travel cost).

10.7 Receipt of Base ESMs or Sub-ESMs.

The COR will review each…