Attachment_0001_PWS_Design_ES_Base_23_MAR_2021.pdf

Performance Work Statement (PWS)

Engineering Services (ES) “Design & Development”

Indefinite Delivery - Indefinite Quantity (IDIQ)

Soldier Unmanned Aircraft Systems (SUAS)

23 March 2021

DISTRIBUTION STATEMENT D: Distribution authorized to the Department of Defense (DoD) and U.S. DoD Contractors only for Administrative or Operational Use, 9 April 2020. Other requests shall be referred to Project Manager, Unmanned Aircraft Systems (UAS) Project Office, SFAE-AV-UAS, 5681 Wood Road, Redstone Arsenal, AL 36898-5000.

SOURCE SELECTION SENSITIVE (See FAR 3.104)

Table of Contents

1. SCOPE AND BACKGROUND

2. APPLICABLE DOCUMENTS

3. REQUIREMENTS

4. SERVICE CONTRACT REPORTING

5. CONTRACTOR TASK ORDER MANAGER

6. COR AND SUBCONTRACT MANAGEMENT

7. CONTRACTOR PERSONNEL, DISCIPLINES, AND SPECIALTIES

8. GENERAL INFORMATION

9. GOVERNMENT-FURNISHED INFORMATION AND PROPERTY

10. WARRANTY

11. QUALITY ASSURANCE SURVEILLANCE PLAN (QASP)

12. ENVIRONMENTAL SAFETY AND OCCUPATIONAL HEALTH (ESOH)

13. COST, PERFORMANCE, AND PROGRESS REPORTING

14. EARNED VALUE MANAGEMENT SYSTEM (EVMS)

15. SECURITY

1. SCOPE AND BACKGROUND

1.1. Scope

This Soldier Unmanned Aircraft Systems (SUAS) technical support services contract includes Engineering, Test, Validation, Verification, and Maintenance Sustainment related requirements for the Rucksack Portable Unmanned Aircraft System (RPUAS) Program. United States (U.S.) Military Forces and other Governmental Agencies employ SUAS in demanding mission profiles under diverse environmental conditions.

The U.S. Army Group I Unmanned Aircraft Systems (UAS) inventory is comprised of Short Range Reconnaissance (SRR), Medium Range Reconnaissance (MRR), and Long Range Reconnaissance (LRR) aircraft as well as the Handheld Ground Control Station (H-GCS) utilizing Tactical Open Government-owned Architecture (TOGA).

Additionally, this need requires various technical, logistics, and program management to support SUAS research and development.

1.2. Background

1.2.1. The SUAS Product Office (PdO) oversees program management of Group I SUAS, the RQ-11B Raven and RQ-20A Puma, along with a Short Range Reconnaissance (SRR) Air Vehicle (i.e., quadcopter-like SUAS).

1.2.2. Modifications to RPUAS components include the frequency reallocation configuration modification to 2,485 current RQ-11B Raven Unmanned Aircraft (UA) to the MRR configuration and continued technology enhancements of the H-GCS, LRR, and SRR.

1.2.3. The SUAS PdO currently does not operate Group II UAS.

1.2.4. The SUAS PdO is actively involved with other entities and industry in order to capitalize on new capabilities and emerging technologies. Non-Standard SUAS systems loaned, leased, or acquired through such partnerships shall require support.

1.2.5. Redstone Arsenal, Alabama, 35898 is the SUAS PdO official duty station as defined in 5 Code of Federal Regulations (CFR) 550.112(j) and 551.422(d).

1.2.6. There is a need to support the existing fleet of SUAS RQ-11B Raven (legacy and upgraded MRR), RQ-20A Puma, the H-GCS systems, and maintain compatibility with new SRR and LRR systems.

2. APPLICABLE DOCUMENTS

The Contract Document Summary List (DSL), Appendix B, provides all top-level documents by number, title, and date. The document versions specified on the DSL take precedence over the generic references (without revision letters) cited in the Performance Work Statement (PWS).

3. REQUIREMENTS

Specific deliverable requirements will be defined in the Task Orders (TOs) with applicable Contract Data Requirements List (CDRL). The Contractor shall submit all deliverables in electronic format unless otherwise identified by the Contracting Officer’s Representative (COR), in Microsoft Products or Adobe PDF. All CDRL deliveries shall be made electronically to the SUAS Data Management system. The Contractor’s data manager(s) shall utilize a Department of Defense (DoD) Primary Public Key Infrastructure (PKI) or External Certificate Authority (ECA) card to enable access to the SUAS Data Management system. The Contractor shall request account(s) via the TopVue site (https://topvue.peoavn.army.mil/Topvue-UAS/FixedNav.aspx) or through the Contracting Officer.

3.1. General Requirements

This section describes general requirements for this effort. The following subsections provide details of various considerations on this effort.

3.1.1. Non-Personal Services

The Contractor shall manage their employees and guard against any actions that are of the nature of personal services or give the perception of personal services. If the Contractor believes that any actions constitute, or are perceived to constitute personal services, the Contractor shall immediately notify the Contracting Officer (KO).

3.1.2. Business Relations

The Contractor shall successfully integrate and coordinate all activity to execute the requirements of this Performance Work Statement. The Contractor shall manage the timeliness, completeness, and quality of problem identification. The Contractor shall provide corrective action plans, proposal submittals, timely identification of issues, and effective management of Subcontractors.

3.1.3. Contract Administration

3.1.3.1. The Contractor shall have a single Point of Contact (POC) between the U.S.

Government (USG) and Contractor personnel assigned to support contracts or TOs.

3.1.3.2. Contractor personnel utilizing Army Knowledge Online (AKO) e-mail shall include the Contractor company name following their name in signature block in all e-mail correspondence.

3.1.3.3. The Contractor shall not release any information or data to third parties without the express written approval of the Procuring Contract Officer (PCO).

3.2. Program Management (PM)

3.2.1. The Contractor shall perform all aspects of SUAS Program Management and Administrative support at the Continental United States (CONUS) sites as required in support of the SUAS PdO.

https://topvue.peoavn.army.mil/Topvue-UAS/FixedNav.aspx

3.2.2. The Contractor shall conduct Program Management Reviews (PMR) to review overall program status at the Contractor’s site. The Contractor shall create charts for presentations, video productions, briefing drafts, and brochures and provide both hardcopy and softcopy presentations for PMRs.

3.2.3. The Contractor shall coordinate Video Teleconferencing (VTC) activities.

3.2.4. The Contractor shall attend meetings, reviews, and cross-functional Integrated Product Teams (IPT). The Contractor shall generate program summaries, information papers, and decision papers in accordance with (IAW) DI-ADMN-81313 (CDRL A022);

progress reports IAW DI-MGMT-80555 (CDRL A012); -reviews, analyses, and meeting minutes IAW DI-ADMN-81505 (CDRL A034); trip reports IAW DI-MISC-81943 (CDRL A007); and accomplishment reports IAW DI-ADMN-81313 (CDRL A022).

3.2.5. The Contractor shall develop and deliver a Work Breakdown Structure IAW DI- MGMT-81334 (WBS) (CDRL A023), an Integrated Master Schedule (IMS) IAW DI-

MISC-80508 (CDRL A032).

3.3. Systems Engineering

3.3.1. The Contractor shall develop and deliver the Contractor’s Systems Engineering Management Plan (SEMP) IAW DI-SESS-81785 (CDRL A039) in accordance with (IAW) the SUAS Systems Engineering Plan (SEP). The Contractor shall perform systems engineering IAW the Contractor’s Government approved SEMP.

3.3.2. The Contractor shall review and/or prepare plans, requirements, summaries, agreements, objectives, policies, strategies, justifications, memorandums, models, criteria, assessments and/or procedures to support program and mission area management and deliver IAW DI-MISC-80508 (CDRL A009).

3.3.3. The Contractor shall attend and support SUAS meetings and IPTs and provide recommendations regarding product development, system safety, system / software development, formal and informal reviews, technical status meetings, and integration and testing activities IAW DI-MISC-80508 (CDRL A009).

3.3.4. The Contractor shall conduct and support System Requirements Reviews (SRR), System Functional Reviews, Preliminary Design Reviews (PDR), and Critical Design Reviews (CDR) IAW DI-ADMN-81505 (CDRL A034).

3.3.5. The Contractor shall produce Performance Specifications IAW DI-IPSC-81431 (CDRL A028), System / Subsystem Design Descriptions IAW DI-IPSC-81432 (CDRL A029), Interface Design Descriptions IAW DI-IPSC-81436 (CDRL A061), Detailed Specification Documents IAW DI-SDMP-81464 (CDRL A030), and Interface Control Documents IAW DI-SESS-81248 (CDRL A020).

3.3.6. The Contractor shall produce Software Version Descriptions (SVD) IAW DI- IPSC-81442 (CDRL A059), Software Requirements Specifications (SRS) IAW DI-IPSC- 81433 (CDRL A060), and Software Design Descriptions (SDD) IAW DI-IPSC-81435

(CDRL A063).

3.3.7. The Contractor shall document software plans, executable files, as built information, modification procedures, build procedures, and maintenance information for software related SUAS products and deliver Software Development Plans (SDP) IAW DI-IPSC-81427 (CDRL A026), Computer Software Products IAW DI-IPSC-81488 (CDRL A053), Software Test Descriptions IAW DI-IPSC-81439 (CDRL A056), SVD IAW DI-IPSC-81442 (CDRL A059), Interface Design Descriptions (IDD) IAW DI-IPSC-81436 (CDRL A061), Interface Requirements Specification IAW DI-IPSC-81434 (CDRL A062), SDD IAW DI-IPSC-81435 (CDRL A063), Software Product Specifications IAW DI-IPSC- 81441 (CDRL A064), Software Development Files IAW DI-MISC-80508 (CDRL A076), and Computer Software Product End Items IAW DI-MCCR-80700 (CDRL A078).

3.3.8. The Contractor shall use Model-Based Systems Engineering (MBSE) development design tools to support Object-Oriented Systems Engineering Method (OOSEM) in the development and support of SUAS architecture, specifications, interfaces, etc. The Contractor shall use the PM SUAS Cameo Enterprise Architecture (EA) suite of modeling software, requiring a Common Access Card (CAC), External Certification Authority (ECA) or other Government approved means, to support SUAS system requirements, design, analysis, and verification / validation activities.

3.3.9. The Contractor shall apply systems engineering methods to map user (operational) needs to system requirements, functions, and conceptual system designs;

develop a Concept of Operations (CONOPS) to communicate user needs and system characteristics to developers, integrators, sponsors, and the SUAS PdO; and develop test requirements that are traceable to system requirements and SUAS needs IAW DI-

IPSC-81430 (CDRL A027).

3.4. Configuration Management / Data Management (CM/DM)

3.4.1. The Contractor shall develop and deliver the Contractor’s Configuration Management Plan (CMP) IAW DI-SESS-80858 (CDRL A041) IAW the SUAS CMP, to be furnished as Government-Furnished Information (GFI). The Contractor shall perform configuration management IAW the Contractor’s Government approved CMP and shall use MIL-HDBK-61 and EIA 649 as guides.

3.4.2. The Contractor shall conduct Functional and Physical Configuration Audits (FCA/PCA) and deliver plans IAW DI-SESS-81646 (CDRL A047) and reports DI-SESS-

81022 (CDRL A048).

3.4.3. The Contractor shall develop / maintain / update and deliver 2-Dimensional / 3- Dimensional (2D/3D) Drawing Technical Data Packages (TDP) IAW MIL-STD-31000 and selection worksheets DI-SESS-81000 (CDRLs A049 and A050).Source Control Drawing (SCD) approval requests shall be submitted IAW DI-SESS-81010 (CDRL A035). The Contractor shall manage and deliver Configuration Status Accounting (CSA)

IAW DI-SESS-81253 (CDRL A021).

3.4.4. The Contractor shall develop and deliver Engineering Change Proposals (ECP) IAW DI-SESS-80639 (CDRL A013), Engineering Release Records (ERR) IAW DI- SESS-80463 (CDRL A044), Notice of Revisions (NOR) IAW DI-SESS-80642 (CDRL A042), and Specification Change Notices (SCN) IAW DI-SESS-80643 (CDRL A045).

3.4.5. The Contractor shall submit a Request for Variance (RFV) per MIL-HDBK-61 to resolve the inaccuracy IAW DI-SESS-80640 (CDRL A046).

3.4.6. The Contractor shall support Unique Identification (UID) and Radio Frequency Identification (RFID) marking designs IAW DI-MGMT-81803 (CDRL A043). Items repaired and delivered as part of this contract will be marked IAW MIL-STD-130. The Baseline Description document delivered as part of this effort will include identification of items designated for UID / RFID marking. All items designated for UID / RFID marking including embedded items will be reported upon completion of contract delivery

IAW DI-MGMT-81803 (CDRL A043).

3.5. Technical Assessment and Support

3.5.1. The Contractor shall verify concept and prototype designs meet SUAS requirements IAW DI-MISC-80508 (CDRL A009).

3.5.2. The Contractor shall perform an assessment of the system architecture on current and future SUAS programs and conduct a preliminary assessment of components, special tools, and training devices for SUAS programs and provide recommendations as to the impact to SUAS and deliver Technical Reports IAW DI- MISC-80508 (CDRL A009), Baseline Description Documents IAW DI-SESS-81121 (CDRL A019), Software Development Plans IAW DI-IPSC-81427 (CDRL A026), and Contractor Evaluation of Technical Publications and Recommended Changes IAW DI-

TMSS-81670 (CDRL A051).

3.5.3. The Contractor shall determine the performance and physical characteristics of a system and document the characteristics and deliver Technical Reports IAW DI- MISC-80508 (CDRL A009) and Baseline Description Documents DI-SESS-81121

(CDRL A019).

3.5.4. The Contractor shall develop Computer Aided Design (CAD) drawings of systems, subsystems, and components for SUAS products and deliver Product Drawings / Models and Associated Lists IAW DI-SESS-81000—2D Models (CDRL A049) and 3D Models (CDRL A050).

3.5.5. The Contractor shall utilize the developed and/or USG-provided specifications to create prototype hardware and software solutions for SUAS products and deliver Technical Reports IAW DI-MISC-80508 (CDRL A009).

3.5.6. The Contractor shall develop and maintain Hardware-In-the-Loop (HWIL) and system simulation tools for SUAS products and deliver System / Software Integration Laboratory (SIL) Development and Management Plans IAW DI-IPSC-81438 (CDRL A054) and DI-SESS-81770 (CDRL A057).

3.5.7. The Contractor shall generate design information documentation for SUAS and/or Commercial Off-The-Shelf (COTS) systems IAW DI-TMSS-80527 (CDRL A015).

3.5.8. The Contractor shall design, code, test, debug, and modify systems’ models for SUAS programs.

3.5.9. The Contractor shall develop, modify, maintain, and utilize analysis tools to simulate systems and to analyze test results IAW DI-SESS-81770 (CDRL A057) and DI-

MISC-80711 (CDRL A058).

3.5.10. The Contractor shall develop and review mathematical models to describe and predict threat, environment, and defensive posture on the battlefield as a means of simulation testing IAW DI-SESS-81770 (CDRL A057) and DI-MISC-80711 (CDRL A058).

3.5.11. The Contractor shall identify the effectiveness of the system through the use of mathematical models and systems analysis techniques IAW DI-SESS-81770 (CDRL A057) and DI-MISC-80711 (CDRL A058).

3.5.12. The Contractor shall identify any and all software licenses required to execute contract and provide list and cost IAW DI-PSSS-82046 (CDRL A074).

3.5.13. The Contractor shall research and provide recommendations on ways to maximize the use of standard / common technologies and/or parts to find commonalities across SUAS systems IAW DI-MISC-80508 (CDRLs A008 and A009).

3.6. Test and Evaluation (T&E)

3.6.1. The Contractor shall develop and support Developmental, Functional, and Performance Testing activities to include developing and executing a Test and Evaluation Project Plan (TEPP) IAW DI-NDTI-81284 (CDRL A070).

3.6.2. The Contractor shall produce test requirements, test plans, test procedures for engineering, developmental, prototype, qualification / verification testing, and integration testing of own hardware, software, and third party components IAW DI-NDTI-80809 (CDRL A014) and DI-SESS-81704 (CDRL A036).

3.6.3. The Contractor shall develop and produce test / special test equipment and test fixtures for engineering, developmental, prototype, qualification / verification testing, and integration testing of own hardware, software, and third party components IAW DI- MISC-80508 (CDRLs A008, A009) and DI-NDTI-80809 (CDRL A014), and DI-SESS-

81785 (CDRL A039).

3.6.4. The Contractor shall provide test coordination, data acquisition control, and frequency management information for engineering, developmental, prototype, qualification / verification testing, and integration testing IAW DI-MISC-81174 (CDRL A018).

3.6.5. The Contractor shall conduct and/or support the following types of testing and evaluation activities and deliver test results. The Contractor shall notify the Government in advance (no less than 15 days) via Contract Letter and make available all testing for observation at the Contractor’s or Subcontractor’s facilities. The Contractor shall obtain Government approval prior to initiation of all testing conducted under this paragraph.

3.6.5.1. The Contractor shall perform product verification tests and deliver reports on SUAS assets IAW DI-NDTI-80809 (CDRL A014) and the approved Test Plan IAW DI-SESS-81704 (CDRL A036).

3.6.5.2. The Contractor shall perform Reliability, Availability, and Maintainability (RAM) tests and deliver test results IAW DI-NDTI-80809 (CDRL A014) and the approved Test Plan IAW DI-SESS-81704 (CDRL A036).

3.6.5.3. The Contractor shall support and conduct non-destructive and destructive tests and deliver test results IAW DI-NDTI-80809 (CDRL A014) and DI-SESS-81704 (CDRL A036).

3.6.5.4. The Contractor shall conduct and/or support Test and Flight Readiness Reviews (TRR/FRR) IAW DI-MISC-80508 (CDRL A009).

The reviews may be conducted at the Contractor test site or a Government test site and shall include teleconference and web conference capabilities.

3.6.5.5. The Contractor shall perform flight and operation support at CONUS sites as required in support of the SUAS PdO and its customers as defined in individual TOs.

3.6.5.6. The Contractor shall provide Government Flight Representative (GFR) certified operators as required per organization regulation IAW Army Regulation (AR) 95-20, and maintain a GFR-approved certification process to ensure operators remain current.

3.7. Production Readiness and Quality Assurance

3.7.1. The Contractor shall conduct Production Readiness Reviews (PRR) IAW DI- MGMT-80797 (CDRL A011), and produce production plans, manufacturing readiness, and quality management IAW DI-MGMT-81889 (CDRL A017) and DI-QCIC-81722

(CDRL A037).

3.7.2. The Contractor shall support production and manufacturing technology assessments at the vendor’s site and deliver findings IAW DI-MISC-80508 (CDRL A068).

3.7.3. The Contractor shall provide a Certificate of Compliance IAW DI-MISC-81356

(CDRL A067).

3.7.4. The Contractor shall deliver a First Article Inspection Report (FAIR) IAW DI-

NDTI-81307 (CDRL A052).

3.8. Engineering Sustainment

3.8.1. The Contractor shall review TDPs, and other SUAS platform documentation to deliver Engineering Data for Provisioning (EDFP) IAW DI-SESS-81874 (CDRL A073).

3.8.2. The Contractor shall provide recommendations for the integration of technologies and components into SUAS products to improve performance, reduce costs, and improve sustainability IAW DI-MISC-80508 (CDRLs A008 and A009).

3.8.3. The Contractor shall provide support for updating user training manuals and user desktop guides for acquisitions, modifications, and upgrades to SUAS products

IAW DI-IPSC-81443 (CDRL A065).

3.8.4. The Contractor shall submit a Modification Work Order (MWO) IAW MIL-PRF-

63002 (CDRL A010).

3.8.5. The Contractor shall provide a Corrosion Prevention Control Plan IAW DI-MISC-

80508 (CDRL A009).

3.9. Software Sustainment

3.9.1. The Contractor shall document the resources needed for life-cycle support of delivered software, including licenses, etc., and plans for transitioning the software to sustaining organization IAW DI-ADMN-80925 (CDRL A016), IAW DI-IPSC-81429 (CDRL A066), and DI-PSSS-82046 (CDRL A074).

3.9.2. The Contractor shall submit a Software Development Plan (SDP) IAW DI-IPSC- 81427 (CDRL A026) and shall develop software IAW this plan.

3.9.3. The Contractor shall submit an SDD IAW DI-IPSC-81435 (CDRL A063).

3.9.4. The Contractor shall submit modifications to the provided SRS IAW DI-IPSC-

81433 (CDRL A060).

3.9.5. When required by TO and when software modifications require platform interface changes, the Contractor shall submit applicable modifications to the Interface Control Document (ICD) IAW DI-SESS-81248 (CDRL A020).

3.9.6. The Contractor shall submit an SVD IAW DI-IPSC-81442 (CDRL A059).

3.9.7. The Contractor shall submit the Computer Software Product End Item (CSPEI) which includes the install files IAW DI-MCCR-80700 (CDRL A078).

3.9.8. The Contractor shall submit a Software Test Plan (STP) IAW DI-IPSC-81438

(CDRL A054).

3.9.9. The Contractor shall submit a Software Test Description (STD) IAW DI-IPSC-

81439 (CDRL A056).

3.9.10. The Contractor shall conduct a Formal Qualification Test (FQT) IAW an approved STP and STD for each software build.

3.9.11. The Contractor shall submit a Software Test Report (STR) IAW DI-IPSC-81440 (CDRL A055) to document FQT.

3.9.12. The Contractor shall create a reuse plan for products IAW DI-IPSC-81429

(CDRL A066).

3.9.13. The Contractor shall perform Independent Verification and Validation (IV&V) on Software (SW) programs of third party SW IAW DI-IPSC-81438 (CDRL A054) and DI-

IPSC-81440 (CDRL A055).

3.10. Cybersecurity

3.10.1. The Contractor shall perform cybersecurity engineering functions including Risk Management Framework (RMF) verification events and develop RMF documentation IAW DI-MISC-80508 (CDRLs A008 and A009).

3.10.2. The Contractor shall develop security into SUAS systems and secure the systems according to operational requirements, as specified within the TO.

3.10.3. The Contractor shall participate in RMF and USG-led cybersecurity events.

3.10.4. The Contractor shall conduct Security Impact Analysis on proposed changes to SUAS systems and provide results as required IAW DI-MGMT-81845 (CDRL A072).

3.10.5. The Contractor shall conduct vulnerability scans on SUAS systems on a quarterly basis utilizing the latest Nessus® plugins and Defense Information Systems Agency (DISA) scanning tools including Security Content Automation Protocol (SCAP) benchmarks and Security Technical Implementation Guides (STIGs) and deliver IAW DI-MISC-80508 (CDRLs A008 and A009).

3.10.6. The Contractor shall conduct engineering system cyber vulnerability analysis based on the system scans and prepare a Design Review Information Package (DRIP) on results from scan events IAW DI-MGMT-81845 (CDRL A072). The Contractor shall provide recommended solutions and mitigations to resolve each action.

3.10.7. The Contractor shall provide assistance to the Government in updating the existing Plan of Actions and Milestones (POA&M) Documentation in support of obtaining or maintaining the Authority to Operate (ATO).

3.10.8. The Contractor shall submit Information Systems Accreditation Documentation IAW DI-ADMN-80239 (CDRL A071) to obtain or maintain an RMF ATO on SUAS programs.

3.10.9. The Contractor shall incorporate cybersecurity related and RMF related events into the system IMS IAW DI- MISC-80508 (CDRL A032).

3.10.10. The Contractor shall conduct supply chain analysis of components incorporated into the SUAS system IAW DI-MISC-80711 (CDRL A058).

3.10.11. The Contractor shall require access to threat-related data to create a cyber resilient system to reduce the risk throughout the system lifecycle. This may require access to Non-Sensitive Compartmented Information. Contractor may require access to Foreign Government Information included in the threat data.

3.10.12. All technical information for SUAS programs is Controlled Unclassified Information (CUI).The Contractor shall require access to information marked CUI.

3.11. Obsolescence / Diminishing Manufacturing Sources (DMS) Risk Management

3.11.1. The Contractor shall provide obsolescence Subject Matter Expert (SME) support to obsolescence management and Diminishing Manufacturing Sources (DMS) Risk Management activities and deliver any findings IAW DI-MISC-80508 (CDRL A009). The Contractor shall be responsible for all DMS / obsolescence issues occurring during the period of performance of this contract. Obsolescence / DMS is defined as occurring when a supplier elects to no longer offer a specific component / subcomponent / part utilized in production or support / sustainment.

3.11.2. The Contractor shall research and provide recommendations of alternate sources for components of SUAS products IAW DI-MISC-80508 (CDRLs A008 and A009).

3.11.3. The Contractor shall submit a Bill of Material (BOM) IAW DI-MISC-80508 (CDRL A009) that includes system breakdown to the piece part level for electronic and COTS parts. The BOM will contain the following information, contained within a single tab on one Excel Spreadsheet:

a. Line Replaceable Unit (LRU) Number and Nomenclature.

b. Next Higher Assembly (NHA) Number and Nomenclature (optional).

c. OEM Part Number.

d. Manufacturer Part Number (manufacturer’s orderable part number).

e. Manufacturers Name and/or Cage Code.

f. Item Description.

g. Alternate Manufacturer Part Number.

h. Alternate Manufacturer Name and/or Cage Code.

i. Find Number.

j. Quantity and Unit of Measure.

k. Make / Buy.

3.11.4. The Contractor shall participate in Obsolescence Working Groups (OWG).

a. The OWG shall meet annually at Redstone Arsenal.

b. The Contractor shall participate in a monthly telecom.

c. The Contractor shall reconcile all obsolescence / DMS risk identified by the OWG to an agreed to closure date.

d. The Contractor shall work action items as a result of OWG meetings to a

Government and Contractor agreed to closure date.

3.11.5. Obsolescence / DMS Notification: The Contractor shall notify the Government if it determined a product or component required in the delivery of the system is unavailable due to obsolescence within ten days of discovery.

3.11.6. Obsolescence / DMS Event Summary: The Contractor shall provide the Government an obsolescence event summary for components that become obsolete on deliverable equipment IAW DI-MISC-80508 (CDRL A009) including a description of the problem-solving process and recommendations that lead to the resolution. Content shall include the following:

a. LRU Number and Nomenclature.

b. NHA Number and Nomenclature (optional).

c. OEM Part Number.

d. Manufacturer Part Number (manufacturer’s orderable part number) of obsolete item.

e. Manufacturers Name and/or Cage Code.

f. Item Description.

g. Date Contractor identified the obsolescence event.

h. Preliminary resolution recommendation.

i. Date the final resolution was identified.

j. Final resolution implemented.

k. Part number of new / replacement piece part (if applicable).

3.11.7. The Contractor shall provide an Obsolescence Risk Analysis / Roadmap detailing the supportability of each LRU IAW DI-MISC-80508 (CDRL A009). The obsolescence sustainment roadmap shall identify trigger points for when a refresh needs to occur and the order in which systems / subsystems need to be refreshed. The content of this data shall be presented in a table with each LRU showing duration in years of production and/or sustainment supportability. The Contractor shall utilize most current data available and include the following:

a. LRU Number and Nomenclature.

b. Support Years (present-ten years).

c. Major Constraints (to include OEM Part Number, Manufacturer Part Number and

Item Description).

d. Quantities Per.

e. Mitigation Required.

f. Date Mitigation Work MUST Begin.

g. Last Time Buy / Existing Stock Quantities.

3.12. SAFETY

3.12.1. System Safety Management

The Contractor shall establish a System Safety Program IAW AR 385-10, MIL-STD-882, AMCOM Regulation 385-17 and the Project Manager for Unmanned Aircraft Systems (PM UAS) System Safety Management Plan (SSMP). The Contractor shall perform safety analysis to verify safe system operation, integration, storage, transport, and maintenance. The Contractor shall perform safety analysis IAW applicable tasks listed in MIL-STD-882. The Contractor shall, identify and track hazards, identify and manage flight critical items, and identify and resolve safety issues. The Contractor shall identify and manage all safety critical software IAW MIL-STD-882 and AMCOM Regulation 385-

17. The Contractor shall participate fully in an IPT format with the USG to review and assess on-going program flight and field operations regarding safety issues to include reviews of operations, maintenance, and training procedures / documents.

3.12.2. System Safety Program Plan (SSPP)

The Contractor shall develop and deliver a System Safety Program Plan (SSPP) to the USG, IAW MIL-STD-882 Task 102 and DI-SAFT-81626 (CDRL A031). The SSPP shall fully describe the planned safety tasks and activities required to meet the System Safety Program requirements, and shall include the Software System Safety Program Plan (SwSSPP). The SSPP shall trace to the PM UAS SSMP and include a plan to satisfy the minimum requirements contained in that plan. The SSPP and its requirements shall be flowed to Subcontractors. A SwSSPP, as part of the SSPP, shall address integration of software safety within the overall system safety effort to include the software development process. The SwSSPP shall comply with MIL-STD-882 and AMCOM Regulation 385-17. The tables and matrices contained in MIL-STD-882 and the PM

UAS SSMP will take precedence over those in AMCOM Regulation 385-17. A Software Criticality Index (SwCI) will be assigned for all hazards affecting safety-significant functions.

3.12.3. Functional Hazard Analysis

The Contractor shall generate a Functional Hazard Analysis (FHA) that identifies potential functional failures IAW MIL-STD-882 Task 208 and DI-MISC-80508 (CDRL A009). Flight and Safety critical hazards from the FHA will be tracked during development and updated in the System Safety Hazard Analysis (SSHA).

3.12.4. Preliminary Hazard Analysis and Preliminary Hazard List

The Contractor shall deliver a Preliminary Hazard Analysis (PHA) to the USG IAW MIL- STD-882 Task 202 and DI-MISC-80508 (CDRL A009). The Contractor shall perform and document a PHA to determine initial risk assessments of identified hazards.

3.12.5. Subsystem Hazard Analysis

The Contractor shall prepare and deliver a Sub-System Hazard Analysis (SSHA) IAW MIL-STD-882 Task 204 and DI-SAFT-80101 (CDRL A001). Flight and Safety critical hazards that require further updating after CDR or other reviews shall be updated in the Safety Assessment Report (SAR).

3.12.6. Safety Assessment Report

The Contractor shall prepare and submit a Safety Assessment Report (SAR) IAW MIL- STD-882 Task 301 and DI-SAFT-80102 (CDRL A002). The report shall document the status of the system with regard to safety hazards, associated risk and mitigation measures. The Risk Assessment matrix in the PM UAS SSMP shall be used to assess risk.

3.12.7. Health Hazard Assessment Report

The Contractor shall deliver a Health Hazard Assessment Report IAW DI-SAFT-80106

(CDRL A003).

3.12.8. 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 ensure that design, integration, maintenance, operation, manufacturing, programmatic decisions and trade-off studies strive to eliminate or reduce hazardous materials and waste.

The Contractor shall implement a Hazardous Material Management Program (HMMP) IAW 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 PWS unless a waiver is obtained from the Army Acquisition Executive.

Any ODC/ODS refrigerant alternatives used must appear in the Environmental Protection Agency’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 HMMP shall provide the following information:

(1) Any of the following materials that are contained within a user end item:

Environmental Protection Agency (EPA) 17 List materials (identified at (http://www.epa.gov/opptintr/3350/33finb1.htm) beryllium, coatings (identified by MIL SPEC), functional fluids (e.g., coolant, hydraulic fluid, petroleum products), energetics / solid rocket motor components (including Explosives Class Number), advanced composite materials (e.g., fabricated from silica, graphite, carbon, boron, fiberglass), batteries, Class I / Class II ODS/ODC materials, and asbestos;

(2) A general description (to include a graphic or drawing) of where these materials are located within the end item;

(3) Required maintenance / repair / support materials to include: EPA 17 List materials, sealants, adhesives, coatings (identified by MIL SPEC), and Class I / Class II ODS/ODC materials; and

(4) Any Emergency Planning and Community Right to Know (EPCRA) 302 / 313 materials (identified at http://www.epa.gov/emergencies/docs/chem/title3_Oct_2006.pdf) utilized in the manufacturing process.

The Contractor shall provide immediate notification of any proposed hazardous material mitigation / elimination efforts that may adversely impact schedules, cost and/or performance IAW DI-MISC-81397 (CDRL A024) and DI-MGMT-81398 (CDRL A025).

3.12.9. Software Safety Compliance Evaluation Artifact Review

The Contractor shall host a Software Safety Compliance Evaluation (SSCE) prior to any Formal Flight TRR to allow the USG adequate time, documentation, and resources to review the Contractor and/or Subcontractor’s supporting Software Safety artifacts to assist the USG in determining if additional risk or hazards are being introduced. The Contractor shall host an SSCE NLT five days prior to any Formal Flight TRR to allow the USG adequate time, documentation, and resources to review the Contractor and/or Subcontractor’s supporting Software Safety artifacts (i.e., Software Safety Level of Rigor (LoR) Table activities and objectives, problem change details, System Integration and Test (Sys I&T) Test Plan, Sys I&T Test Logs, Sys I&T Test Report and Artifacts, Software Lifecycle tool artifacts, Software Unit Test Plans, Software Unit Test Procedures, Software Unit Test Reports, “As Run” Scan Reports, Ground Test Plan, http://www.epa.gov/ozone/ods.html http://www.epa.gov/ozone/snap/lists/index.html http://www.epa.gov/ozone/snap/lists/index.html http://www.epa.gov/opptintr/3350/33finb1.htm http://www.epa.gov/emergencies/docs/chem/title3_Oct_2006.pdf

Flight Test Plan, Daily Reports, etc.) for traceability, completeness (metric collection), robustness, and quality (craftsmanship), to assist the USG in determining if additional risk acceptance or hazards are being introduced. The SSCE will consist of a focus on those artifacts that substantiate the completion of activities and objectives associated with the highest safety and airworthiness concern. If the Contractor cannot host Subcontractor(s) for a review, additional on-site SSCEs must be coordinated at the Subcontractor facility.

3.12.10. Hazard Tracking System

The Contractor shall implement a PM UAS-approved Hazard Tracking System (HTS) Database to document, track, and manage all hazards identified during design, development, and test activities. All identified hazards shall be tracked in the HTS Database. The HTS shall also address software’s contributions to potential system level (including system of systems) hazard occurrence, or have references to the documented detailed description of software’s contributions to hazards and how those contributions are mitigated. Acceptance of hazards, mitigation, verification, and potential residual risk shall be IAW the SSMP. The content of hazard logs, procedures and process for review, concurrence, and closure of hazard logs shall be IAW the

SSMP.

3.12.11. Mishaps and Accidents

For any mishap, the Contractor shall conduct root-cause analysis, prepare a Corrective Action Report IAW DI-SESS-80255 (CDRL A069). The Contractor shall comply with AR 385-10, the Army Safety Program, and DA PAM 385-40 (Army Accident Investigations and Reporting) for mishap and accident investigation reporting. The Contractor shall report all incidents and accidents, meeting the reporting criteria of AR 385-10 and DA PAM 385-40, to the PM UAS or the SUAS PdO System Safety Manager.

3.12.12. System Safety Working Group

The Contractor shall support System Safety Working Group (SSWG) and semi-annual SSWG meetings. The Contractor shall support Software System Safety Technical Review Panel (SSSTRP) activities when required for system or software material release. The Contractor shall provide a SSSTRP TDP IAW DI-MISC-80508 (CDRL A009) NLT 30 days prior to a formal SSSTRP event. The Contractor shall comply with the GFR’s requirements IAW AR 95-20.

3.13. Airworthiness Support

3.13.1. The Contractor shall provide requirements and/or systems modeling support for requirements analysis IAW DI-MISC-80508 (CDRLs A008 and A009).

3.13.2. The Contractor shall provide documentation necessary to achieve and/or maintain an Airworthiness Release (AWR) IAW AR 70-62 IAW DI-MISC-80508 (CDRLs A008 and A009).

3.13.3. The Contractor shall comply with Critical Safety Item requirements IAW AMCOM Regulation 702-7 and deliver IAW DI-MISC-80508 (CDRLs A008 and A009).

3.13.4. The Contractor shall verify and validate, should any physical modifications occur, that the structural integrity has not been compromised (i.e., preserve positive margin of safety) IAW DI-SAFT-81932 (CDRL A079).

4. SERVICE CONTRACT REPORTING

The contractor shall report ALL contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract for technical support for the UAS Project Office, SUAS Product Office. The contractor is required to completely fill in all required data fields using the following web address: www.sam.gov.

Contractors may direct questions pertaining to the website to the help desk at the aforementioned web site.

5. CONTRACTOR TASK ORDER MANAGER

The Contractor shall designate in writing to the PCO a TO Manager and an alternate to act as the Contractor’s principal POC on all TOs. The TO Manager need not be physically located at the SUAS Contractor facility, but shall have the full authority to act on behalf of the Contractor on all contractual matters in connection with TOs.

6. COR AND SUBCONTRACT MANAGEMENT

6.1. The Contracting Officer’s Representative (COR)

The COR is an individual designated IAW Defense Federal Acquisition Regulation Supplement and is authorized in writing by the KO to perform specific technical functions. The USG will supply a COR to serve as the single POC for all (non-financial liability creating) questions related to the specific administration of the contract. The COR is not authorized to make any commitments or changes that will affect cost/price, quantity, delivery, or any other term or condition of this contract. The Contractor will receive a copy of the COR Appointment Letter after TO award specifying the extent of the COR’s authority to act on behalf of the PCO.

6.2. Subcontract Management

The Contractor shall be responsible for any subcontract management necessary to integrate work performed on this requirement and shall be responsible and accountable for any Subcontractor performance on this requirement. The prime Contractor shall manage work distribution to ensure there are no Organizational Conflict of Interest (OCI) considerations. Contractors may add Subcontractors to their team after notification to the PCO and/or COR. Cross teaming shall be permitted at USG discretion.

http://www.sam.gov/

7. CONTRACTOR PERSONNEL, DISCIPLINES, AND SPECIALTIES

7.1. Contractor Employees

7.1.1. The USG will specify the minimum qualifications of certain Contractor employees in order to satisfy Federal Law, DoD, or U.S. Army regulations.

7.1.2. The Contractor shall accomplish the assigned work by employing and utilizing qualified personnel with appropriate combinations of education, training, and experience.

7.1.3. The Contractor shall match personnel skills to the work or task with a minimum of under / over employment of resources.

7.1.4. The Contractor shall ensure the labor categories defined in the Labor Categories Document (Appendix D), labor rates, and man-hours utilized in the performance of any TO issued hereafter shall be the minimum necessary to accomplish the task.

7.2. Location and Hours of Work

7.2.1. Accomplishment of the results contained in this PWS requires work to mainly be performed at the Contractor facilities. Contractor employees shall also perform infrequent work at various Contractor, Subcontractor, or USG facilities. Most facilities are located in CONUS.

7.2.2. Core hours of work shall be from 0800 to 1700 CST / CDT daily in order to match the business hours of the SUAS PdO. Sufficient employees to perform work tasks are expected to be available during core hours.

7.2.3. On occasion, unexpected tactical or other situations may require work performance in excess of eight hours per day, 40 hours per week. All excess hour requirements shall be pre-approved by the USG.

7.2.4. Normal workdays are Monday through Friday.

7.3. Travel and Temporary Duty (TDY)

7.3.1. Travel shall be required on this contract. All travel shall be conducted using the Joint Travel Regulations (JTR) as a guide. No profit or fee is authorized. Only General and Administrative fees are authorized. All Other Direct Costs (ODCs) and material are reimbursed at cost with no profit or fee.

7.3.2. When the Contractor is required to travel to other USG facilities and/or other Contractor facilities, the travel shall be pre-approved by the COR. Within seven days after return from travel, the Contractor shall submit a Trip Report summarizing the trip to the COR. The Trip Report shall include the purpose, discussions, resolutions, actions, and the cost of the trip.

7.3.3. All Contractor travel, including plans, agenda, itinerary, or dates shall be USG pre-approved.

7.4. Transition

7.4.1. The Contractor may interface with the existing SUAS Contractor and continue to interface with them if the current contract is extended.

7.4.2. The USG will host a Kick-Off Meeting with the Contractor within 30 business days of contract award. The purpose of the meeting is to establish requirements for program reviews, discuss contractual requirements, schedules, and other pertinent contract data.

7.4.3. The Contractor shall develop a transition plan in conjunction with the USG covering the Program Management, engineering, and test support programs to ensure smooth, timely, and complete contract start up to be submitted to the USG within 20 days of contract award and discussed at the Contract Kick-Off Meeting.

7.4.4. Upon contract award, the USG will conduct technical orientation training for selected Contractor employees relative to overall knowledge of the SUAS systems.

7.5. Place of Performance

The place of performance for this contract shall be CONUS (onsite / offsite) only.

Specific places of performance will be detailed in individual TOs.

7.6. USG Equipment Furnished in USG Facilities

Contractor personnel may support tasks at a combination of offsite and onsite locations.

When the assigned place of work is in a USG facility, the USG will provide all telecommunication, information technology, and workplace-related equipment and furniture necessary to accomplish the assigned tasks.

8. GENERAL INFORMATION

8.1. Release of Information or Data to Third Parties

The Contractor shall not release any information or data to third parties without the express written approval of the PCO.

8.2. Risk Management Process

The Contractor shall establish, implement, and maintain a proactive, on-going Risk Management Process that identifies, assesses, mitigates, and appropriately reports technical, cost, and schedule risk on this contract. The Contractor and USG will use program reviews, reports, and IPT meetings to track risks and mitigation progress across the entire program.

8.3. Wide Area Work Flow (WAWF)

The Contractor shall have access to and support the Wide Area Work Flow (WAWF) website, Procurement Integrated Enterprise Environment (PIEE), found at:

https://wawf.eb.mil/piee-landing/.

https://wawf.eb.mil/piee-landing/

9. GOVERNMENT-FURNISHED INFORMATION AND PROPERTY

These items may be provided to support efforts defined in individual TOs. Specific details of GFI or Government-Furnished Property (GFP) (to include equipment) will be defined in each individual TO IAW DI-MGMT-80441 (CDRL A077). The Contractor’s COR shall return all GFI/GFP to the USG upon TO completion or request. The primary computer based supply management system currently used is the Catalog Ordering Logistics Tracking System (COLTS); however, future TOs may call for utilization of any computer based supply management system. The USG will coordinate for and provide access to USG and non-USG facilities and installations as required to allow Contractor personnel access required to complete tasks detailed in individual TOs.

10. WARRANTY

If material is used and has a shelf and/or service life, the Contractor shall provide warranty expiration dates based on shelf and/or service life. COTS equipment, systems, and materials purchased by the Contractor and provided to the USG without modification must be warranted IAW the original manufacturer’s / COTS warranty.

11. QUALITY ASSURANCE SURVEILLANCE PLAN (QASP)

The USG will use the Quality Assurance Surveillance Plan (QASP) for SUAS support to monitor the Contractor’s quality system. The USG will evaluate the Contractor performance IAW the QASP. This plan is primarily focused on what the USG must do to ensure that the Contractor has performed IAW the performance standards. It defines how the performance standards will be applied, the frequency of surveillance, and the maximum acceptable performance rate(s).

12. ENVIRONMENTAL SAFETY AND OCCUPATIONAL HEALTH (ESOH)

The Contractor shall establish an Environment, Safety and Occupational Health (ESOH) Program to minimize risk throughout the SUAS system life cycle. The Contractor shall perform ESOH analyses and provide data to support evaluation of environmental impacts IAW the National Environmental Policy Act (NEPA) (PL 91-190). The program will address environmental compliance, system safety and health, hazardous materials, pollution prevention, and explosive safety. The ESOH analyses will be used to integrate environmental considerations into the systems engineering process. Resolution, reporting, and tracking of environmental issues will be accomplished through the systems engineering process. The Contractor shall prepare a Health Hazard Assessment Report IAW DI-SAFT-80106 (CDRL A003).

13. COST, PERFORMANCE, AND PROGRESS REPORTING

The Contractor shall prepare Status Reports IAW DI-MGMT-80368 covering the program progress and status on technical, cost and schedule performance, tradeoffs, and risk reduction activity IAW DI-MGMT-80368 (CDRL A004).

14. EARNED VALUE MANAGEMENT SYSTEM (EVMS)

14.1. Integrated Performance Management System

14.1.1. The Contractor shall establish, maintain, and use in the performance of this contract, an integrated performance management system. Central to this integrated system shall be an EVMS and the EVMS guidelines contained in ANSI/EIA 748. To establish the integrated performance management system, the EVMS shall be linked to and supported by the Contractor’s management processes and systems, to include the contract WBS, IMS, change management, material management, procurement, cost estimating, and accounting. The correlation and integration of these systems and processes shall provide for early indication of cost and schedule problems, and their relation to technical achievement. EVMS will also be invoked for individual TOs on a case-by-case basis as determined by the Government.

14.1.2. The Contractor shall prepare an Integrated Program Management Data and Analysis Report (IPMDAR) IAW DI-MGMT-81861 (CDRL A038). The IPMDAR shall integrate cost and schedule performance data with objective technical measures of performance. The Contractor shall flow down IPMDAR requirements to any Subcontractor that has a cost or incentive contract valued at or greater than $20 million in then-year dollars.

The Contractor shall participate in a monthly Government-conducted review of cost, schedule and technical status as reported on the prior month’s IPMDAR.Cost The Contractor shall prepare and submit a Contract Funds Status Report (CFSR) IAW

DI-MGMT-81468 (CDRL A033).

The Contractor shall provide a Cost Breakdown Structure Summary Report IAW DI-

FNCL-80165 (CDRL A005).

14.2. Integrated Baseline Review (IBR)

The Contractor shall support an Integrated Baseline Reviews (conducted by the Government). The Contractor shall engage jointly with the Government’s Program Manager in an IBR to evaluate the risks inherent in the contract’s planned performance measurement baseline. The first IBR shall be held NLT 75 calendar days after the contract award. The Contractor shall perform formal re-baselining / reprogramming (Over Target Baseline/Over Target Schedule, or single point adjustment) of its contract budget baseline only after receiving authorization in writing from the Government KO.

Each IBR shall verify the Contractor is using a reliable performance measurement baseline which includes the entire contract scope of work, is consistent with contract schedule requirements, and has adequate resources assigned. The IBRs shall be conducted on subcontracts that meet or exceed the EVM application threshold. The prime Contractor shall lead the Subcontractor IBRs, with active participation by the Government.

14.3. Integrated Master…