Final W31P4Q-24-R-0024 LIDAS PWS Follow On Final 8 Nov 23.pdf

CUI

W31P4Q-24-R-0024

PERFORMANCE WORK STATEMENT (PWS)

FOR

ENGINEERING SERVICES

FOR

MULTIPLE LAUNCH ROCKET SYSTEM (MLRS)

LAUNCHER INSTRUMENTATION DATA ACQUISITION SYSTEM (LIDAS)

8 November 2023

Prepared By:

Business Management Directorate

SFAE-MSL-STB

Huntsville, AL 35808

DISTRIBUTION STATEMENT D. Distribution authorized to the Department of Defense and U.S. DoD contractors only; Administrative or Operational use and Export Controlled, Date of Determination 29 Jun 2023. Other requests for this document shall be referred to STORM Project Office, ATTN: SFAE-MSL-STB, Huntsville, AL 35808.

Export-Control Act Warning - This document contains technical data whose export is restricted by the Arms Export Control Act (Section 2751 of Title 22, United States Code) or the Export Control Reform Act of 2018 (Chapter 58 Sections 4801-4852 of Title 50, United States Code). Violations of these export laws are subject to severe criminal penalties. Disseminate in accordance with provisions of DoD Directive 5230.25 and DoD Instruction 2040.02.

Controlled by: STORM Project Office Category: Procurement & Acquisition Dissemination Controls: FEDCON POC: Shannon Kelsoe, 256-842-7177

Table of Contents

1.0 Scope

2.0 Applicable Documents

3.0 Requirements

3.1 General

3.2 Liaison

3.3 Management

3.4 Task Activation and Control of Test Equipment………………………………...……………………………………….2

3.5 Program Management Support of Test Equipment

3.6 Engineering Support of Test Equipment

3.7 FMS Support of Test Equipment

3.8 Integrated Product Support (IPS) of Test Equipment

3.9 Government Furnished Property (GFP)

3.10 Security

3.11 Hazardous Material Management……………………………………………………………………………………… 13

3.12 Safety

3.13 Contractor Manpower Reporting Application…………………………………………………………………….…15

3.14 Cybersecurity

Engineering Services for Multiple Launch Rocket System (MLRS)

Launcher Instrumentation Data Acquisition System (LIDAS) W31P4Q-23-R-0056

Performance Work Statement (PWS) 18 July 2023

1.0 SCOPE. This Performance Work Statement (PWS) delineates, in general terms, the overall requirements of the engineering services to support the MLRS LIDAS Family of Highly Specialized Test Equipment for the Strategic and Operational Rockets and Missiles (STORM) Project Office. The highly specialized test equipment includes, current and future LIDAS Family Test Equipment including the MLRS Family of Munitions (MFOM) Weapons Simulator. The purpose of this PWS is to obtain the engineering services outlined herein without duplicating efforts that have been accomplished or are required on other MLRS contracts.

2.0 APPLICABLE DOCUMENTS. The applicable top-level documents are contained in the Document Summary List (DSL), by number, title, revision, date, contract reference and Controlled Unclassified Information (CUI) category. The document versions specified on the DSL take precedence over the generic references (those without the revision letters) cited in the PWS. Unless otherwise indicated, copies of specifications, standards, and handbooks listed are available from the Document Automation and Production Service, at the Acquisition Streamlining and Standardization Information System website: https://assist.daps.dla.mil/quicksearch/.

3.0 REQUIREMENTS:

3.1 General. The LIDAS engineering services support shall include the following contractor tasks: investigations, inspections, and analyses to improve the maintainability, training, reliability, quality, operations, or logistics support of the fielded LIDAS; technical support at live firings and during tests in which the LIDAS is used both in Continental United States (CONUS) and Outside Continental United States (OCONUS) locations; improvement and modification of the LIDAS in response to changes in the MLRS Launcher or munitions supported by the launcher; interoperability support for Foreign Military Sales (FMS)/co-production countries; and other support needed to meet the instrumentation requirements of the STORM Project Office including: M270Al Launcher, M270A2 Launcher, High Mobility Artillery Rocket System (HIMARS), Extended Range MLRS (ER-MLRS), Guided MLRS (GMLRS), Army Tactical Missile System and Common Fire Control System. The contractor shall place emphasis on safety, reliability, quality, producibility, maintainability, and usability of the LIDAS Family of Highly Specialized Test Equipment. The test equipment includes the MLRS LIDAS, M270A1, M270A2, HIMARS, M270B2, M270D1, C4I, MFOM Weapon Simulator, upgrades, and future items. The specific effort to be expended, tasks to be accomplished, and documentation required shall be defined by individual Government Work Authorizations (GWAs).

The contractor's efforts under this PWS shall include planning and managing a streamlined engineering services program, accomplishing product engineering tasks, https://assist.daps.dla.mil/quicksearch/

Launcher Instrumentation Data Acquisition System (LIDAS) W31P4Q-23-R-0056 including technical representation at both CONUS and OCONUS locations, to support and modify the highly specialized equipment to meet current and future STORM and MFOM requirements. The contractor shall provide all program directives, integration and coordination of all activities as required to support the requirements of this contract.

3.2 Liaison. The contractor shall furnish representatives, when so directed, to coordinate activities in accordance with (IAW) this PWS with Government agencies including, the U.S. Army Aviation and Missile Command, the Army Contracting Command – Redstone (ACC-Redstone), and other contractors.

3.3 Management. The Chief, Test Division, or Contracting Officer’s Representative (COR), as the Government Technical Manager for this engineering services contract will be authorized to request, approve, and submit GWAs to the ACC-Redstone Contracts Office for concurrence and incorporation into the contract. The COR will be authorized to cancel any GWA by coordinating with the ACC-Redstone Contracts Office for concurrence and incorporating written direction into the contract. Such written technical direction to the contractor shall be provided and confirmed at the Directorate level by GWAs which will be serialized for control and signed by the Government’s Technical Manager.

3.3.1 Government Technical Management Monitor. The Chief, Test Division, or COR, will be the designated Government Technical Management Monitor for the Program Management Engineering Support, Interoperability Support, and Product Support of Test Equipment.

3.3.2 Government Technical Monitor. The Government Technical Management Monitor, or COR, will manage specified major activity areas and serve as a technical liaison to the contractor. The authority of the Government Technical Management Monitor extends only to the activity specified in their signed and approved GWAs.

3.3.3 Contractor Technical Manager. The contractor shall appoint a Contractor Technical Manager for the duties and responsibilities commensurate with those of their Government counterpart identified in Section 3.3.

3.4 Task Activation and Control of Test Equipment. The contractor shall only perform efforts under this contract pursuant to a Government approved GWA. The Government Technical Manager will issue GWAs, including the task description and an estimate of hours required to perform the work delineated in the GWA.

3.4.1 GWA Priority. The Government Technical Management Monitor reserves the right to establish priority of the GWAs.

Launcher Instrumentation Data Acquisition System (LIDAS) W31P4Q-23-R-0056

3.4.2 Contractor GWA priority. The contactor shall redirect work on GWAs when so directed in writing by the Government Technical Manager.

3.4.3 Level of Effort for Contractor Tasks. The contractor shall submit, upon direction of the Government Technical Manager, an estimate of the level of effort necessary to accomplish all contractor required tasks in section 3 of this PWS, including the manufacture of hardware for test or checkout of designs or investigations.

3.4.4 Performance and Cost Report. The contractor shall provide expertise in the areas of program control, scheduling, cost estimating and cost reporting and shall establish time-phased technical milestones for each GWA. The contractor’s records shall be time-phased based upon the contractor’s accounting periods so that technical progress can be matched to the actual hours used for the preparation and submission of a consolidated report. The contractor shall prepare and submit the Performance and Cost Report IAW DI-FNCL-80912 (A001).

3.4.5 Contractor Control of Tasks. The contractor shall plan, coordinate, and control the tasks defined in the GWAs.

3.4.6 Management and Progress Reviews. The contractor shall participate in formal management and progress reviews on each GWA with ACC-Redstone and the STORM Project Office, as scheduled.

3.5 Program Management Support of Test Equipment. The objective of this section is to provide requirements for program management support of the LIDAS Family of Highly Specialized Test Equipment and the MFOM Weapon Simulator.

3.5.1 Contractor Support of Government’s Planning, Coordination, and Use of Highly Specialized Test Equipment. The program management efforts to be performed by the contractor shall be in support of the Government’s planning, coordination, and use of the highly specialized test equipment to meet the test objectives of the STORM Project Office and other users of the equipment. The program management support shall include review of planning documents, recommendations for use of the highly specialized equipment, and support in utilizing the equipment. The contractor shall ensure improvements and modifications to the highly specialized test equipment are implemented in a cost-effective manner. The contractor shall provide technical expertise to meet the test objectives of FMS/co-production countries through the use of the highly specialized test equipment. When directed by GWA, the contractor shall perform the program management tasks described IAW the following PWS paragraphs:

Launcher Instrumentation Data Acquisition System (LIDAS) W31P4Q-23-R-0056

3.5.1.1 Discussion of Test Objectives. Attend meetings, briefings and other functions involving the discussion of test objectives and verbally advise the Government on the technical feasibility of highly specialized test equipment to meet test objectives of the MFOM and the STORM Project Office.

3.5.1.2 Review Planning Documents. Review the planning documents and coordinate a schedule with Government agencies, activities and commands for the use of highly specialized test equipment to meet the test objectives of the MFOM and the STORM Project Office.

3.5.1.3 Resolution of MFOM Issues. Conduct analyses, prepare reports, and briefings to support the Government in making use of the highly specialized test equipment to resolve MFOM problems and to meet MFOM test objectives. The contractor shall prepare and deliver presentation material IAW DI-ADMN-81373 (A002).

3.5.1.4 Assist In Developing Plans. Assist in developing plans and provide support to the STORM Project Office in meeting the test objectives for FMS/co- production countries that use MLRS Launcher and the MFOM. The contractor shall prepare and deliver test plans IAW DI-NDTI-80566 (A003).

3.5.1.5 User Forum Support. Provide technical support to the STORM Project Office in developing and conducting a user forum to obtain ideas and feedback from users on recommended improvements and changes.

3.6 Engineering Support of Test Equipment. The objective of this section is to provide general requirements for engineering support of the LIDAS Highly Specialized Test Equipment and the MFOM Weapon Simulator.

3.6.1 Engineering Support. The engineering support efforts to be performed by the contractor shall include the following: systems engineering tasks to support live fires, development and operational testing, and other activities requiring the use of the highly specialized test equipment; engineering tasks to improve and modify the highly specialized test equipment to meet current and future needs of the STORM Project Office for instrumentation and in response to changes in the basic MLRS Missile System; and engineering tasks to support the resolution of current and future MLRS Missile System hardware, software, training, maintenance, product assurance and test problems using the highly specialized test equipment. Utilize global positioning system keys, when necessary, to verify operation of the highly specialized test equipment.

When directed by GWA, the contactor shall perform the engineering tasks described in the following paragraphs:

3.6.1.1 Technical Support of MLRS Launcher Pool Instrumentation. Provide technical support for the MLRS Launcher Pool Instrumentation, including the mobile

Launcher Instrumentation Data Acquisition System (LIDAS) W31P4Q-23-R-0056 laboratory/test equipment, to troubleshoot and resolve problems with system instrumentation.

3.6.1.2 Technical Support for MFOM Development or Integration. Provide technical support for live fires, development and operational testing, and Government and contractor/subcontractor laboratories that are involved with MFOM development or integration.

3.6.1.3 Technical Support of Field Investigations. Provide technical support of field investigations of the highly specialized test equipment to assess current and future requirements of the STORM Project Office and FMS/co-production countries.

3.6.1.5 Product Drawings. Provide product drawings and associated lists IAW DI- SESS-81000 (A004) to document LIDAS highly specialized test equipment.

3.6.1.6 Contract Data Requirements List (CDRL) to Support Engineering Changes. The contractor shall prepare and submit estimates to support any engineering changes to the highly specialized test equipment, as well as, coordination of technical changes, with the STORM Project Office. The estimate shall include a dollar estimate, the amount of time required to complete the change, and a list of associated hardware delivered IAW DI-MISC-80508 (A005).

3.6.1.7 Technical Inputs. The contractor shall review and provide technical inputs on investigations, inspections, analyses, and test or evaluation efforts which could impact system hardware, firmware, or software of the instrumentation via telecom.

3.6.1.8 CDRL to Deliver Technical Reports, Software, and System Documentation. The contractor shall prepare and deliver technical reports, software, and system documentation IAW DI-MISC-80508 (A005).

3.6.1.9 Technical Support for MFOM. Provide technical support for MFOM tests, demonstrations or live fires to other Department of Defense service branches and to FMS/co-production countries.

3.6.1.10 Interoperability of MLRS. Support interoperability of the MLRS with FMS/co-production countries to include demonstrations of the highly specialized test equipment to resolve interoperability problems.

3.6.1.11 Support Testing. Support testing of the MLRS Missile System to include hardware and software testing.

3.6.1.12 Technical Input for Future MFOM Instrumentation. Provide technical input for planning of future MFOM instrumentation.

Launcher Instrumentation Data Acquisition System (LIDAS) W31P4Q-23-R-0056

3.6.1.13 Modeling and Simulation. Conduct modeling and simulation in support of MFOM instrumentation improvements.

3.7 FMS Support of Test Equipment. The objective of this section is to provide requirements for international interoperability engineering services support of highly specialized test equipment for other countries using the MLRS Launcher.

3.7.1 Contractor Support of Interoperability. The engineering services effort to be performed by the contractor is in support of interoperability and shall include the following: systems engineering tasks to support FMS/co-production country live fires, FMS/co-production country development and operational testing, and other FMS/co-production country activities requiring the use of highly specialized test equipment; and engineering tasks to support the STORM Project Office resolution of current and future FMS/co-production country MLRS Missile System hardware, software, training, maintenance, product assurance, and test problems using the highly specialized test equipment. When directed by GWA, the contractor shall perform the engineering tasks described in the following PWS paragraphs:

3.7.1.1 Technical Support for Live Fires. Provide technical support for live fires and testing at FMS/co-production country firing ranges and test facilities where the highly specialized test equipment is used.

3.7.1.2 Interface and Interoperability Support. Provide interface and interoperability support during engineering field investigations and evaluations for the MLRS Launcher and MFOM.

3.8 Integrated Product Support (IPS) of Test Equipment. The objective of this section is to provide the general requirements for IPS fielding support of the highly specialized test equipment.

3.8.1 Logistics Support. The logistics support efforts to be performed by the contractor include the following: maintenance and repair of the components of the highly specialized test equipment and any associated equipment; development of calibration procedures and equipment; periodic calibration of the highly specialized test equipment;

on-site trouble shooting, maintenance, repair, and provisioning of the highly specialized test equipment using a contractor furnished property mobile laboratory and equipment at both CONUS and OCONUS locations; and analysis, investigations, and technical support to resolve reliability, availability, and maintainability problems and issues associated with the highly specialized test equipment.

3.8.2 GWA Direction. When directed by GWA, the contractor shall perform the tasks described in the following paragraphs:

Launcher Instrumentation Data Acquisition System (LIDAS) W31P4Q-23-R-0056

3.8.2.1 Product Support, Engineering, Investigations, and Evaluations. Provide product support, engineering investigations, and evaluations for MFOM systems and sub-systems for the U.S. and other countries that use the current and future MLRS Launcher and MFOM.

3.8.2.2 Product Support and Training. Provide product support and training for fielding of improved highly specialized test equipment.

3.8.2.3 MFOM Support. Provide mobile lab/test equipment, repair parts, supplies, and other product support for live firings, and operational and developmental tests involving the MFOM.

3.8.2.4 Product Support. Provide product support to include the transportation, tools, equipment spares and mobile laboratory to accomplish the echelons of maintenance and repair of the highly specialized test equipment at the field locations in CONUS and

OCONUS.

3.8.2.5 On-Site Support. Provide on-site product support in trouble shooting, maintenance and repair, and provisioning of the highly specialized test equipment at both CONUS and OCONUS locations.

3.8.2.6 Calibration. Provide calibration procedures and equipment, and conduct calibration of the highly specialized test equipment.

3.8.2.7 Inventory Control. Maintain inventory control of the highly specialized test equipment.

3.9 Government Furnished Property (GFP).

3.9.1 GFP Inventory Report. The contractor shall prepare and deliver a Government Property Inventory Report IAW DI-MGMT-80441 (A006).

3.9.2 Government Furnished Materiel (GFM). The contractor shall prepare and deliver a GFM by National Stock Number Report IAW DI-PSSS-80727 (A007).

3.9.3 Government Furnished Materiel Consumption Report. The contractor shall prepare and submit a Government Furnished Materiel Consumption Report IAW DI-

MGMT-80438 (A008).

3.9.4 GFP Audit. The contractor shall support Government on-site property audit efforts (limited to one time annually) by providing the Government with access to a sampling of GFP during the contractor's normal business hours (i.e., sample size less than 40, Launcher Instrumentation Data Acquisition System (LIDAS) W31P4Q-23-R-0056 located at the prime contractor’s facility). The contractor shall make their property records available to the Government to support on-site property audits. The Government may apply other Government tags or property identification labels to unmarked GFP assets found. The contractor shall make the GFP and/or their property records, including the documentation repository, available to the Government to support a 100% inventory during Close-Out of contract. The contractor shall provide photos for up to 20 assets in support of sample audits per year.

3.9.5 GFP Record Reconciliation. The contractor shall participate in annual reconciliations with the Government to review and provide status on changes to property records executed since the preceding meeting. Reconciliations will be held via teleconference and will be scheduled by the Government. The contractor shall make their property records available to the Government to support all reconciliations. The contractor shall resolve errors in the contractor’s accountable property management system.

3.9.6 GFP Attachment. For new procurements initiated under this contract with a Unit of Measure of “lot” (such as procurement of tooling) the contractor shall separately identify each item contained within the lot. DD Forms 250 or DD Forms 1149 for lots shall include an attachment which identified and incorporates the following information for each item within the lot prior to signature/release of the DD Form 250/DD Form 1149, and delivery:

· Manufacturer Commercial and Government Entity Code **(if provided, for new property only)

· Item Description

· Manufacturer Name **(if provided, for new property only)

· Manufacturer Part Number

· Manufacturer Model Number

· Material Control Number (if applicable)

· Unit of Measure

· Unit Acquisition Cost

· Location

Launcher Instrumentation Data Acquisition System (LIDAS) W31P4Q-23-R-0056

· Sub Location (if applicable)

· Unique Item Identifier (UID) (as registered in the IUID Registry) (if available and necessary for individual item tracking and management)

· Type of Government Property (i.e., Government Furnished Property (GFP) or Contractor Acquired

· Property (CAP)

· Classification of Government Property Equipment

Material, Special Test Equipment, or Special Tooling

· Posting Reference

· Date of Transaction / Date of Acquisition

· Date Placed in Service

· Date of Last Physical Inventory

3.10 Security.

3.10.1 General. Security requirements will be based upon the latest Security Classification Guide. The contractor and all associated sub-contractors shall develop internal security procedures to protect classified, sensitive, unclassified, high dollar value, and hazardous items. The contractor and all associated sub-contractors shall comply with Federal Acquisition Regulation (FAR) 52.204-2, Security Requirements.

The contractor shall comply with all security classification requirements IAW the DD Form 254, DoD Contract Security Classification Specification.

3.10.2 Contracts Requiring Performance or Delivery in a Foreign Country. The contractor and all associated sub-contractors shall comply with Defense Federal Acquisition Regulation Supplement (DFARS) Clause 252.225-7043, Antiterrorism/Force Protection for Defense Contractors Outside the U.S. This clause will be used in solicitations and contracts that require performance or delivery in a foreign country and applies to both contingency and non-contingency support. Non-local national contractor personnel shall comply with theater clearance requirements. The combatant commander will exercise oversight to ensure the contractor’s compliance with combatant commander and subordinate task force commander policies and directives.

Launcher Instrumentation Data Acquisition System (LIDAS) W31P4Q-23-R-0056

3.10.3 Access and General Protection/Security Policy and Procedures. Contractors and all associated sub-contractors’ employees shall provide all information required for background checks to meet installation access requirements to be accomplished by installation Provost Marshal Office, Director of Emergency Services or Security Office.

The contractor workforce shall comply with all personal identity verification requirements (FAR clause 52.204-9, Personal Identity Verification of Contractor Personnel) as directed by DoD, Headquarters, Department of Army (HQDA) and/or local policy. In addition to the changes otherwise authorized by the changes clause of this contract, should the Force Protection Condition (FPCON) at any individual facility or installation change, the Government may require changes in contractor security matters or processes.

3.10.4 Contractors not Eligible for a Common Access Card (CAC), but Requires Access to a DoD Facility or Installation. The contractor and all associated sub-contractors employees shall comply with adjudication standards and procedures using the National Crime Information Center Interstate Identification Index and Terrorist Screening Database (Army Directive 2014-05/AR 190-13), applicable installation, facility and area commander installation/facility access and local security policies and procedures (provided by government representative), or, at OCONUS locations, IAW status of forces agreements and other theater regulations.

3.10.5 Contractors Requiring a CAC. Before CAC issuance, the contractor employee requires, at a minimum, a favorably adjudicated National Agency Check with Inquiries (NACI) or an equivalent or higher investigation IAW Army Directive 2014-05. The contractor employee will be issued a CAC only if duties involve one of the following: (1) Both physical access to a DoD facility and access, via logon, to DoD networks on-site or remotely; (2) Remote access, via logon, to a DoD network using DoD-approved remote access procedures; or (3) Physical access to multiple DoD facilities or multiple non-DoD federally controlled facilities on behalf of the DoD on a recurring basis for a period of 6 months or more. At the discretion of the sponsoring activity, an initial CAC may be issued based on a favorable review of the Federal Bureau of Investigation (FBI) fingerprint check and a successfully scheduled NACI at the Office of Personnel Management.

3.10.6 Anti-Terrorism (AT) Level 1 Training. All dedicated contractor employees, to include subcontractor employees, assigned 30 days or more to government installations, facilities and controlled access areas as their primary duty station shall complete AT Level I Awareness Training within 30 calendar days of contract definitization and within 30 calendar days of new employees commencing performance.

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, No Later Than (NLT) 30 calendar days after contract definitization

Launcher Instrumentation Data Acquisition System (LIDAS) W31P4Q-23-R-0056 and annually thereafter. AT Level I Awareness Training is available at the following website: https://jko.jten.mil.

3.10.7 Operations Security (OPSEC) Program. The contractor shall develop an OPSEC Standing Operating Procedure (SOP)/Plan within 90 calendar days of contract award, for the responsible Government OPSEC officer to review and approve IAW DI- MGMT-80934 (A014). This plan shall include a process to identify critical information, where it is located, who is responsible for it, how to protect it and why it needs to be protected. The contractor shall implement OPSEC measures as ordered by the commander. In addition, the contractor shall have an identified certified Level II OPSEC coordinator per Army Regulation (AR) 530-1.

3.10.8 OPSEC Training. Per AR 530-1 Operations Security, the contractor employees shall complete Level I OPSEC Awareness Training. New employees shall complete training within 30 calendar days of their reporting for duty and annually thereafter.

OPSEC Training is available at the following website: OPSEC Awareness for Military Members, DOD Employees, and Contractors (usalearning.gov).

3.10.9 Communications Security (COMSEC). The contractor shall follow National Security Agency (NSA) / Central Security Service Policy Manual 3-16 Control of COMSEC Material, 32 CFR Part 117, National Industrial Security Program Operating Manual (NISPOM) and AR 380-40 Safeguarding and Controlling Communications Security Material, as they apply to this contract. Government Contracting Agency approval is required prior to granting COMSEC access to a sub-contractor (NISPOM Chapter 9, Section 4, Paragraph 9-407).

3.10.10 Controlled Unclassified Information. Contractor shall comply with the requirements of Department of Defense Instruction (DoDI) 5200.48, Controlled Unclassified Information. Apply For Official Use Only to legacy information only. For current or future information, apply CUI guidance.

a. Controlled Unclassified Information shall follow the guidance outlined in DoDI 5200.48, the NIST SP 800-171 identifies the baseline CUI system security requirements for industry established by Part 2002 of Title 32, Code of Federal Regulations (CFR).

Additionally, Section 252.204-7012 of the DFARS specifies a waiver process for defense contractors IAW NIST SP 800-171 for contractor Information Technology (IT) or networks.

b. CUI with the potential to impact national security (e.g., information related to critical programs and technology information) may require enhanced protection. These enhanced measures would address both physical and logical procedures. Enhanced protection methods for systems hosting CUI include:

https://jko.jten.mil/ https://securityawareness.usalearning.gov/opsec/story.html https://securityawareness.usalearning.gov/opsec/story.html

Launcher Instrumentation Data Acquisition System (LIDAS) W31P4Q-23-R-0056

(1) Access control (e.g., restricting both physical and logical access to the systems).

(2) Audit and accountability (e.g., review and monitor system usage).

(3) Configuration management (e.g., restrict system connection to only approved resources).

(4) Identification and authentication (e.g., control issuance of end-user certificates).

(5) Incident response (e.g., ensure corrective measures are implemented in a timely manner and validate effectiveness).

(6) System and communication protection (e.g., application of encryption for data at rest and restriction of connections to uncertified, unsecured, non-organizational systems). DoD Components may implement stricter CUI encryption requirements based on a law, regulation, or government-wide policy (Defense Health Policy Procedural Instruction 8140, requires workforce encrypt emailed protected health information).

(7) System and information integrity (e.g., provide network detection tools throughout the system to identify attempted intrusions).

c. Non-DoD processing, storing, or transmitting CUI will be safeguarded IAW contractual requirements identified for the particular CUI contained in the contract, DoDI

8582.01 and Section 252.204-7012 of the DFARS or their subsequent revisions.

d. When established by contract, contractors, sub-contractors, and consultants must comply with safeguarding requirements identified in the contract for all types of CUI.

e. Contractors shall monitor CUI for aggregation and compilation based on the potential to generate classified information pursuant to security classification guidance addressing the accumulation of unclassified data or information.

3.10.11 AT Awareness Training for Contractor Personnel Traveling Overseas. The contractor employees and associated sub-contractor employees shall receive government provided Area of Responsibility (AOR) specific AT awareness training as directed by AR 525-13. The combatant commander, with the unit Anti-Terrorism Officer (ATO) being the local point of contact, directs the specific AOR training content.

3.10.12 iWATCH Training. All dedicated contractor employees, to include subcontractor employees, assigned 30 days or more to government installations, facilities and controlled access areas as their primary duty station shall complete iWATCH Training within 30 calendar days of contract definitization and within 30 calendar days of new employees commencing performance. The training results shall be reported to the COR NLT 30 calendar days after contract definitization and annually thereafter. This locally 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.

Launcher Instrumentation Data Acquisition System (LIDAS) W31P4Q-23-R-0056

An iWATCH training brief will be provided or training is available at the following website: USMEPCOM > Home > Contractors (army.mil)

3.10.13 Access and General Protection/Security Policy and Procedures. The contractor employees and all associated sub-contractor employees shall provide all information required for background checks to meet installation access requirements to be accomplished by installation Provost Marshal Office, Director of Emergency Services or Security Office. Contractor employees and all sub-contractor employees shall comply with all personal identity verification requirements (FAR clause 52.204-9, Personal Identity Verification of Contractor Personnel) as directed by DoD, HQDA and/or local policy. In addition to the changes otherwise authorized by the changes clause of this contract, should the FPCON at any individual facility or installation change, the Government may require changes in contractor security matters or processes.

3.10.14 Threat Awareness Reporting Program (TARP). IAW AR 381-12, TARP, For all contractors with security clearances, contractor employees shall receive and complete annual TARP training per AR 381-12, TARP by a Counter Intelligence (CI) agent or other trainer as specified in 2-4b. Contractors shall report threat-related incidents, behavioral indicators and other matters of CI interest specified in Chapter 3, to the Facility Security Officer (FSO), the nearest military CI office, the FBI, or the DCSA. Contractor employees working as an integral part of the Army organization ARE REQUIRED TO COMPLETE ANNUAL Threat Awareness training. Contractor FSOs will ensure that all applicable AR 381-12 requirements are implemented for personnel who work at contractor facilities. If CI agent is not available, a waiver request for the using computer based training may be presented to the STORM Project Manager for consideration.

3.11 Hazardous Material Management. All contractor and subcontractor activities shall be in compliance with applicable federal, state and local environmental laws and regulations.

The contractor shall develop and deliver a Hazardous Materials Management Program (HMMP) Plan IAW DI-MGMT-81398 (A009). In addition, the contractor shall prepare and deliver a HMMP Report IAW DI-MISC-81397 (A010). The HMMP Reports shall identify via graphic or drawing of the specific location of each hazardous material contained in the final end item(s).

For this contract, “Tracked Hazardous Materials (HAZMATs)” in NAS 411 should be defined as Emergency Planning and Community Right-To-Know Act 302/313 listed chemicals. The contractor shall report the data elements found in MIL-STD-882, Task 108, section 108.2.4 a, b, and d for Tracked HAZMATs. The contractor shall report coatings (identified by MIL SPEC), functional fluids (e.g. coolant, hydraulic fluid, lubricants, etc), and energetics/solid rocket motor components (including Explosives https://www.mepcom.army.mil/Home/Contractors/

Launcher Instrumentation Data Acquisition System (LIDAS) W31P4Q-23-R-0056

Class Number) with the same 108.2.4 a, b, and d data elements. The contractor shall provide Material Safety Data Sheets or Safety Data Sheets for all reported materials.

The contractor shall not use any Class I or Class II Ozone Depleting Chemical/Ozone Depleting Substance (ODC/ODS), identified by the lists at https://www.epa.gov/ozone-layer-protection/ozone-depleting-substances, in the manufacture or support of items required by this PWS unless approved IAW Army ODS policy and/or Title 10 United States Code section 2402. All ODS alternatives must be IAW the U.S. Environmental Protection Agency Significant New Alternatives Policy program and identified as approved – per the specific application – in the lists at http://www.epa.gov/ozone/snap/lists/. All ODS alternatives must also receive a Toxicity Clearance for the specific application from the US Army Public Health Center.

The contractor shall list any hazardous material, as defined in NAS 411-1, The National Aerospace Standard, Hazardous Materials Target List to be used for the maintenance, sustainment, and demilitarization of the end item under this contract. The hazardous material shall be properly identified and include any applicable identification number, such as National Stock Number or Special Item Number. The contractor hazardous materials list shall be updated during performance of the contract whenever the contractor determines that any other material to be used in the maintenance, sustainment, and demilitarization of the end item under this contract is hazardous.

3.12 Safety. The contractor shall adhere to all local, state, and federal laws and regulations required in order to maintain a safe and non-hazardous occupational environment throughout the duration of this contract. The contractor shall report any major accident/incident (including fire) resulting in any one or more of the following:

causing one or more fatalities or one or more disabling injuries; damage of Government property exceeding $10,000; affecting program planning or manufacturing schedules;

degrading the safety of equipment under contract, such as personnel injury or property damage may be involved; identifying a potential hazard requiring corrective action. The contractor shall prepare and deliver the report IAW DI-SAFT-81563 (A011) for each incident. The contractor shall, in the event an unsafe or hazardous condition is discovered or occurs during the performance of this contract, take immediate precautions to protect personnel and property. The contractor shall notify the Contracting Officer and the STORM Project Manager within twenty-four hours by telephone or email of such conditions.

3.12.1 System Safety Program. The contractor shall maintain a safety engineering effort to ensure system safety design criteria, the system safety design order of precedence, and safety verification processes are addressed. The contractor shall execute the system safety program IAW MIL-STD-882 (to include Task 101). The contractor shall prepare, deliver and execute the System Safety Program Plan (SSPP) IAW DI-SAFT-81626 (A012) and Task 102 of MIL-STD-882. The SSPP shall https://www.epa.gov/ozone-layer-protection/ozone-depleting-substances https://www.epa.gov/ozone-layer-protection/ozone-depleting-substances https://global.ihs.com/search_res.cfm?&rid=AIA&input_doc_number=411-1&input_doc_title=&org_code=AIA/NAS https://global.ihs.com/search_res.cfm?&rid=AIA&input_doc_number=411-1&input_doc_title=&org_code=AIA/NAS

Launcher Instrumentation Data Acquisition System (LIDAS) W31P4Q-23-R-0056 demonstrate compliance with, and traceability to the Government System Safety Management Plan.

3.12.2 Safety Assessment Report. The contractor shall prepare and deliver a Safety Assessment Report (SAR), utilizing guidance in Task 301 of MIL-STD-882 with results documented IAW DI-SAFT-80102 (A013). The SAR shall include an assessment of hazards, risk mitigation measures, and risks associated with the design, use, testing, maintenance, and training with the highly specialized test equipment covered under this contract. The SAR shall include a safety statement that the system is considered safe for the level of development and testing it is applicable to, with the final SAR stating that the system is considered safe for fielding.

3.12.3 Hazard Tracking. Hazard Tracking should be called out to support the SAR:

The contractor shall maintain a Hazard Tracking System (HTS) IAW Task 106 of MIL- STD-882 and DI-SAFT-82085 as a risk resolution system to document, track, and manage all hazards identified during design, development, manufacturing, testing, fielding, use, maintenance, surveillance, training, and disposal activities. The Government shall have access to the HTS and data. Hazard tracking worksheets or summaries shall be included as a separate section or as an appendix of the SAR.

3.12.4 Safety Reviews. The contractor shall attend and support Government conducted System Safety Working Group(s) (SSWG) prior to Design/Technical Reviews. The SSWG’s charter is to ensure that the contractor and Government have a mutual and clear understanding of the identified hardware and software such that the potential safety hazards can be stated in the SAR. Furthermore, the contractor safety personnel shall attend the program design Integrated Product Team (IPTs), System Safety IPTs, Software System Safety Working Group meetings, reviews, telecoms, and other meetings as needed.

3.13 Contractor Manpower Reporting Application. The Office of the Assistant Secretary of the Army (Manpower & Reserve Affairs) operates and maintains a secure Army data collection site to capture all direct labor hours and direct labor dollars incurred by prime contractors and subcontractors required for performance of this contract. The prime contractor shall provide the information addressed in Contractor User Guide at the following web address: https://www.ecmra.mil. Subcontractors shall provide the information addressed in the subcontractor user guide at the web address provided above.

3.13.1 Information to Include for contractor Manpower Reporting Application. The required information shall include the Contract Number, Delivery or Task Order Number (if applicable), Direct Labor Hours, Direct Labor Dollars, Country, State, Zip Code, City or Installation of Service, Total Obligated Dollars, Total Invoiced Amount, contractor

Launcher Instrumentation Data Acquisition System (LIDAS) W31P4Q-23-R-0056

Company Name, contractor Point of Contact First and Last Name, Phone Number and Email Address.

3.13.2 Inclusion in Subcontracts. The contractor shall include and require inclusion of this term in subcontracts at any tier under this contract (except to vendors providing goods and no services other than incidental services). NOTE: Subcontractors shall not enter any contract level information, only location data to include direct labor hours, direct labor dollars and location where provided.

3.13.3 Contract Record Establishment. The prime contractor shall establish the contract record at the web address referenced in PWS paragraph 3.13.

3.14 Cybersecurity. The contractor shall maintain a Cybersecurity program. The contractor shall adhere to Cybersecurity regulations and security policies including:

National Security Act; AR 25-1 Army Information Technology; AR 25-2 Army Cybersecurity; DoDI 8500.01 Cybersecurity; DoDI 8510.01 Risk Management Framework (RMF) for DoD IT, NIST SP 800-53 Security and Privacy Controls for Information Systems and Organizations; CNSSI No. 1253 Security Categorization and Control Selection for National Security Systems; DoD Directive 8140.01 IA Training, Certification, and Workforce Management; DoDI 8580.1 IA in the Defense Acquisition System; DoDI 8582.01 Security of Non-DoD Information Systems Processing Unclassified Nonpublic DoD Information; National Institute of Standards and Technology (NIST) 800 Series; DFARS Clauses 252.204-7008 (Compliance with Safeguarding Covered Defense Information Controls), 252.204-7012 (Safeguarding Covered Defense Information and Cyber Incident Reporting), 252.204-7018 (Prohibition of the Acquisition of Covered Defense Telecommunications Equipment or Services), 252.204-7019 (Notice of NIST SP 800-171 DoD Assessment Requirements), 252.204- 7020 (NIST SP 800-171 DoD Assessment Requirements), and 252.204-7021 (Cybersecurity Maturity Model Certification Requirements). Additional implementation guidance can be found in the applicable NSA Guides, Defense Information System Agency Security Technical Implementation Guides (STIGs), DoD Cybersecurity Test and Evaluation Guidebook version 2.0, and Army Best Business Practices.

3.14.1 Cybersecurity Training. All contractor employees and associated sub-contractor employees must complete the DoD Information Awareness (IA) training before issuance of network access and annually thereafter. All contractor employees working Cybersecurity functions must comply with DoD and Army training requirements in DoD Manual 8140.03 Cyberspace Workforce Qualifications and Management Program, and AR 25-2 before employment.

Launcher Instrumentation Data Acquisition System (LIDAS) W31P4Q-23-R-0056

3.14.2 Authority (sometimes called Authorization) to Operate (ATO) Support. The contractor shall support the Government obtaining an ATO of the LIDAS test equipment under the Department of Defense RMF process. Contractor support is defined as:

• Software Development Plan (SDP) / Project Plan – Project Level – (family of NIST controls) o SDP documents the details required to execute/produce the project/system o This document specifies:

Tools, methods, and processes used during the development of software Descriptions of the life cycle model, development phases, and software development environment

• System/Software Design Document – Project Level o Provides a detailed description of the design of the software to include:

System/software architecture Data flows Cybersecurity safeguards

• For example: If the software is hashed prior to fielding Safety risk mitigations o Network and data flow diagrams

• Configuration Management Plan (CMP) – Project Level (CMP family of NIST controls; SA-10) o The purpose of the Configuration Management Plan is to describe how the system/software developer accommodates change and maintains integrity in the products by applying:

A closed-loop change management process Full life-cycle control of configuration items Electronic data management A physical media repository

• Test Plan / Test Description – Project Level - (SA-11) o These documents describe the test preparations and test procedures for the system/software

• Software Version Description (SVD) (for the final SW delivery) – Project Level o The SVD document identifies and describes the referenced software version and includes:

An inventory of materials released

Launcher Instrumentation Data Acquisition System (LIDAS) W31P4Q-23-R-0056

Software contents Changes installed since the previous release

• Software Requirements Specification – Project Level o This document details the requirements for the system and includes:

Operational concept for the system/software Service requirements Software requirements Communications interface message processing information

• Version Description Document (for each engineering release) – Project Level o This document identifies and describes the software version and details the hardware components that have changed in the new version o This document includes:

An inventory of released materials and software information Installation procedures Any known problems with the system/software and workarounds (if available) relevant to this release

• Contingency Plan – Facility Level / Project Level (family of NIST controls) o This document addresses maintaining essential missions and business functions despite an information system disruption, compromise, or failure, and addresses eventual, full information system restoration without deterioration of the security safeguards originally planned and implemented o Further information contained within this document includes:

Essential missions and business functions and associated contingency requirements Recovery objectives in the event of information system disruption, compromise, or failure Restoration priorities and metrics in the event of information system disruption, compromise, or failure Contingency roles, responsibilities, and assigned individuals and their corresponding contact information

• Incident Response Plan – Project Level (family of NIST controls; SA-15(10)) o A document detailing the incident response policy and procedures. This document should include incident response training procedures required for users of the system, incident handling, monitoring, and reporting procedures. Reportable incidents must be defined in the plan – to include information spillage.

Launcher Instrumentation Data Acquisition System (LIDAS) W31P4Q-23-R-0056

• Security Concept of Operation – Project Level o Information to be processed o Operating environment (logical and physical) o Data transfer to/from the system o Types of users on the system (privileged/regular users) o Expected number of users o Vulnerability scanning that is conducted on the system and the reporting plan for when vulnerabilities are discovered o Public Key Infrastructure / Multifactor Authentication Plan o Other Special Security Considerations o Explanation of Risk Mitigations

• Security Architecture Guide – Project Level (PL) – (PL-8 and PL-8(1)) o Describes the overall philosophy, requirements, and approach to be taken with regard to protecting the confidentiality, integrity, and availability of organizational information.

o The document describes:

How the information security architecture is integrated into and supports the enterprise/overall system architecture Any information security assumptions about, and dependencies on, external services or systems

• Hardware / Software / Firmware list – Project Level o Includes component type, manufacturer/vendor, model#, serial#, License or contract, licenses/licenses used, OS/SW/FW version (see HW/SW/FW template in eMASS or the RMF Knowledge Service) o List of installed programs and applications o List of applicable STIGs

• Any memorandums, agreements, or waivers/risk acceptance regarding the system o This includes system specific Acceptable Use Policy and user agreements

• Ports, Protocols and Services Document/List – (System Specific)

• SOP (System…