Attachment_0001_-__Performance_Work_Statement_20180130_Revised.pdf

PERFORMANCE WORK STATEMENT

FOR

ELECTRO-OPTIC / INFRARED / LASER DESIGNATOR PAYLOAD

PRODUCTION AND SYSTEM SUPPORT

BASE CONTRACT

Solicitation Number: W909MY-17-R-D008

28 AUGUST 2017

Prepared by:

Product Manager-Electro Optics / Infrared Payloads

SFAE-IEW-TE

5895 Wilson Rd, Bldg 337 Ft Belvoir, VA 22060

Table of Contents

1. General

1.1 Scope

1.2 System Description

2. Applicable Documents

2.1 Military Standards

2.2 Military Handbooks

2.3 Government Documents

2.4 Non-Government Documents

3. Requirements

3.1 Program Management Support

3.2 Production

3.3 Systems Engineering Support

3.4 Integration

3.5 Testing and Evaluation

3.6 Integrated Product Support

4. Data and Data Rights

5. OPSEC Plan

6. Travel

7. Program Protection Plan (PPP)

8. Safety Assessment Report (SAR)

Performance Work Statement for

Electro-Optic/Infrared/Laser Designator (EO/IR/LD) Payload Production and System Support

1. General

This is contract is for the procurement of Electro-Optic/Infrared/Laser Designator (EO/IR/LD) Payloads, spares and associated services. Services include program management, production, system engineering, integration, test, evaluation and logistical support services for the EO/IR/LD Payload program.

1.1 Scope

This Performance Work Statement (PWS) details the requirements for program management, production, systems engineering, integration, test, logistics, maintenance and training of the EO/IR/LD Payload, subsystems, and components.

1.2 System Description

The EO/IR/LD Payload integrates to and operates from the Tactical Unmanned Air Systems RQ-7Bv2 (RQ-7Bv2) and will be a non-developmental item that provides a robust, advanced state-of-art sensor suite to collect critical information for all members of the air-ground maneuver team. The EO/IR/LD Payload provides the maneuver commander with persistent situational awareness of the battlespace as compared to what was previously available; increase in survivability for the RQ-7Bv2; provides near real-time imagery for detection and classification of targets / threats and supports Force Application, Battlespace Awareness, Force Protection, and Net - Centric Operations.

2. Applicable Documents

The following documents are applicable to this PWS and all appendices to the extent specified herein. Table 2.1-1 contains a list of military standards referenced in this PWS.

Table 2.2-1 contains a list of military handbooks referenced in this PWS. Table 2.3-1 contains a list of Government documents to include Army Regulations (ARs), guidebooks, Department of the Army Pamphlets (DA PAMs), Department of Defense Instructions (DODIs), Department of Defense (DoD) directives, military specifications, Training and Doctrine Command (TRADOC) Regulations (TRs) referenced in this PWS.

Table 2-4-1 contains a list of non-Government documents referenced in the PWS to include commercial standards and Contractor specifications referenced in this PWS. In the event of a conflict between the text of this document and the references cited herein, the text of this document and the Performance Based Specification (PBS) for the EO/IR/LD Payload Sub-system for the RQ-7Bv2 shall take precedence. Nothing in this document, however, supersedes applicable laws and regulations unless a specific exemption has been obtained. Unless otherwise stated, the following documents may be obtained from the Document Automation and Production Service, Building 4/D, 700 Robbins Avenue, Philadelphia, PA 19111-5094 or visit https://assist.dla.mil.

2.1 Military Standards

Table 2.1-1 – Military Standards

Document ID Date Document Description

MIL-STD-129R 18 Feb 14 Military Marking for Shipment and Storage

MIL-STD-130N (1) 16 Nov 12 Identification Marking of U.S. Military Property

MIL-STD-882E 11 May 12 Standard Practice for System Safety

MIL-STD-2073-1E

(1)

07 Jan 11 DoD Standard Practice for Military Packaging

MIL-STD-40051-

2C

15 Dec 15 Preparation of Digital Technical Information for Page-Based Technical Manuals (TMs)

MIL-STD-3034A 29 April 14 DoD Reliability-Centered Maintenance (RCM) Process

2.2 Military Handbooks

Table 2.2-1 – Military Handbooks

MIL-HDBK-61A 07 Feb 01 Configuration Management Guidance

MIL-HDBK-502A 08 Mar 13 Product Support Analysis

2.3 Government Documents

Table 2.3-1 – Government Documents

PBS for the Payload Sub-system for the RQ-7Bv2 TUAS

17 Aug 17

A performance specification is a document that specifies threshold and objective technical requirements of the contract.

Shadow AV Payload Mechanical and Electrical ICD

20 Jul 15

Interface Control Document (ICD) for the

RQ-7B

AR 750-1 Army Materiel Maintenance Policy

20 Sep 07

This regulation establishes policy, responsibilities, and procedures for Army Materiel Maintenance Policy

Defense Acquisition University Guidebook

Dec 11

Integrated Product Support Element

Shadow Tactical Unmanned Aircraft System Test and Evaluation Management Plan

11 Apr 14

Common Evaluation Strategy for RQ7B

Department of Defense Risk, Issue, and Opportunity Management Guide for Defense Acquisition Programs

11 Jan 17

This guide is one of several DoD policy and guidance documents that address the Department’s focus on risk management.

AR 700-15

Packaging of Materiel

12 Jan 14

This regulation covers packaging requirements, specifications, levels of protection and project information exchange requirements.

AR 700-145 24 Sep 12 Item Unique Identification

TITLE 10 USC

21 May 17 Core Logistics Capability

AR 530-1

Operations Security

(OPSEC).

26 Sep 14

This regulation covers Operations Security (OPSEC).

Systems Engineering Plan (SEP) for the Shadow RQ-7B Operations and Support Phase

5 Jan 16

Technical approach to manage system engineering activities for the Shadow

RQ-7B

DODI 5200.44

05 Nov 12

Protection of Mission Critical Functions to Achieve Trusted Systems and Networks

(TSN)

DoD 2010 Defense Acquisition

27 Aug 10

Definition of technology readiness levels.

AR 700-127 11 Oct 16 Integrated Product Support – APD Army DoD Manual 4151.22M

30 Jun 2011 Reliability-Centered-Maintenance

AR 25-400-2 2 Oct 07 Army Record Information Management System

AR 710-2 10 Oct 08 Supply Policy Below the National Level

DA PAM 710-2-1 01 Dec 16 Pamphlet to AR 710-2

AR 700-15 12 Jan 04 Packaging of Materiel

AR 735-5 09 Nov 16 Property Accountability

SD - 22 DMSMS

06 Jan 16

Best practices for Diminishing Manufacturing Sources and Material Shortages (DMSMS) Management

AR 380-5 29 Sep 00 Department of the Army Information Security Program

AR 70-77 7 Apr 14 Program Protection

AR 40-501 22 Dec 16 Standards of Medical Fitness

2.4 Non-Government Documents

Table 2.4-1 – Non-Government Documents

ISO 9001 15 Sep 15 9001:2008 Quality Management Systems- Requirements

ISO / IEC / IEEE

24748-4:2016, Systems and Software Engineering – Life Cycle Management – Part 4: Systems Engineering Planning

05 Jan 16

Defines the interdisciplinary tasks which are required throughout a system's life cycle

SAE/GEIA-STD-0007 16 Apr 14 Logistics Products Data

EIA-649B 04 Mar 15 National Consensus Standard for Configuration Management

Standardization Directory (SD) - 22 DMSMS Guidebook

06 Jan 16 DMSMS Guidebook

ANSI/EIA-649B 30 Nov 13 Configuration Management Standard

3. Requirements

The Contractor shall provide all personnel, equipment, supplies, facilities, transportation, tools, materials, supervision, and other items and non-personal services necessary in accordance with (IAW) the requirements identified in this PWS, PBS for the Payload Subsystem for the RQ-7Bv2 Tactical Unmanned Aircraft System (TUAS) and the Shadow AV Payload Mechanical and Electrical ICD except for those items specified as Government Furnished Property (GFP) and services. The payload shall be Technical Readiness Level (TRL) seven (7) IAW DoD 2010 Defense Acquisition Guidebook. Requirements identified in this base PWS may be delineated in individual orders issued during the Period of Performance (PoP).

3.1 Program Management Support

The Contractor shall establish a single management focal point for this contract and subsequent Task Orders (TOs) / Delivery Orders (DOs). The Contractor shall manage all aspects of the EO/IR/LD Payload during the PoP, including the performance of all suppliers and SubContractors directly associated with this effort (this includes DMSMS IAW paragraph 3.6.2.5. The Contractor shall produce a Contractor’s Progress, Status, and Management Report (CPSMR) IAW Contract Data Requirements List (CDRL) B001 that shall report Contractor and SubContractor status as required in TOs/DOs.

3.1.1 Integrated Master Schedule (IMS)

The Contractor shall develop and maintain an IMS, IAW CDRL B002, IMS; for the PoP that incorporates individual orders as they are awarded in order to manage the program.

3.1.2 Post Award Meeting (PAM)

The Contractor shall host a one-time PAM no more than ten (10) days after contract award, at the Contractor’s Contiguous United States (CONUS) facility. The purpose of this meeting shall be to ensure a common understanding of contract requirements and associated schedules. The meeting shall be two (2) business days in duration at eight

(8) hours per day. The Government recommends that the Contractor’s Program Manager, Lead Engineer, Lead Manufacturing Engineer and Lead Logistician participate in the PAM. The Contractor shall prepare an Agenda IAW CDRL B003, Conference Agenda. The Contractor shall prepare and provide presentation material IAW CDRL B004, Presentation Material. The Contractor shall compile, track and distribute meeting minutes and action items to all attendees, IAW CDRL B005, Report, Record of Meeting/Minutes.

3.1.3 Program Management Review (PMR)

The Contractor shall conduct PMRs to provide a forum for review and discussion of contract performance on all active orders. The PMRs shall be conducted quarterly per year, at the Contractor’s facility or Government facility as required by the Government.

No more than 50% of the PMRs will be held at Government facilities and the other 50% at the Contractor’s CONUS facility. The agenda for each PMR shall be agreed to in advance by the Government and Contractor’s Program Manager and be provided IAW CDRL B003, Conference Agenda. The Contractor shall prepare and provide presentation material IAW CDRL B004, Presentation Material. The Contractor shall compile, track and distribute meeting minutes and action items to all attendees, IAW CDRL B005, Report, Record of Meeting/Minutes. The meeting shall be two (2) business days in duration at eight (8) hours per day. The Government recommends that the Contractor’s Program Manager, Lead Engineer, Lead Manufacturing Engineer and Lead Logistician shall participate in the PMR. The Contractor shall compile, track and distribute meeting minutes and action items to all attendees.

3.1.4 Integrated Product Teams (IPT)

The Contractor shall support IPTs and other Government meetings. All meetings shall be conducted via teleconference. Meetings shall be one (1) hour in duration. The Government recommends that the Contractor’s Program Manager, Lead Engineer, Lead Manufacturing Engineer and Lead Logistician shall participate in the IPT. The Contractor shall compile, track and distribute meeting minutes and action items to all attendees. The Contractor shall prepare an Agenda IAW CDRL B003, Conference Agenda. The Contractor shall prepare and provide presentation material IAW CDRL B004, Presentation Material. The Contractor shall compile, track and distribute meeting minutes and action items to all attendees, IAW CDRL B005, Report, Record of Meeting/Minutes.

3.1.5 Technical Interchange Meeting (TIM)

The Contractor shall travel and support an integration event lasting three (3) business days eight (8) hours per day at a CONUS integrator’s location. The Government recommends that the Contractor’s Program Manager, Lead Engineer, Lead Manufacturing Engineer and Lead Logistician shall participate in the TIM. The Contractor shall provide meeting minutes IAW CDRL B005, Report, Record of Meeting Minutes, and a trip report IAW CDRL B006, Trip Report.

3.1.6 Government Furnished Property

The Contractor shall be provided GFP in the form of EO/IR/LD Payloads that require repair or retrograde and this is the only GFP that will be provided on the contract. The Government may provide additional GFP if it is determined necessary and all GFP provided shall be managed IAW applicable Federal Acquisition Regulation (FAR) and Defense Federal Acquisition Regulation Supplement (DFARS) clauses incorporated into this contract. A GFP and Contractor Acquired Property (CAP) Master Report will be submitted, IAW CDRL B007, to describe the status and inventory data for government property accountable to the contract. The Government Report will be used to review the condition, installation, and effectiveness of government property in the Contractor’s possession.

3.1.7 Contractor Cost Data Reports

3.1.7.1 Contract Work Breakdown Structure

The Contractor shall prepare and deliver a Contract Work Breakdown Structure (CWBS) IAW CDRL B008. The Contractor shall systematically collect and report actual contract costs to provide Government cost analysts with data needed to estimate future costs.

3.1.7.2 Contractor Cost Data Reports

The Contractor shall develop a Cost Data Summary Report (DD Form 1921) IAW CDRL B009 and DFARS 215.403.5. The Contractor shall develop a Functional Cost-Hour Report (DD Form 1921-1) IAW CDRL B010. The Contractor shall develop a Contractor Business Data Report (Form DD 1921-3) IAW CDRL B011.

3.2 Production

All EO/IR/LD Payloads, Materials, Test and Support Equipment shall be delivered to a Product Manager Electro-Optic / Infrared (PdM EO/IR) Logistics Point identified in paragraph 3.6.6. Effort specifics, including quantity, schedule, and delivery locations, shall be administered through individual TOs/DOs.

The Contractor shall attain Government approval prior to any early delivery of EO/IR/LD Payloads or materials. The early delivery will not incur additional cost to the Government or void any warranty. The Contractor shall be responsible for any discrepancies and corrections of those deficiencies found during the inspection of the delivered item.

3.2.1 Payloads

The Contractor shall manufacture, test and deliver the EO/IR/LD Payloads IAW the PBS for the EO/IR/LD Payload Sub-system for the RQ-7Bv2. The Contractor shall conduct Environmental Stress Screening and Acceptance Testing on EO/IR/LD Payloads IAW paragraph 3.2.5. The EO/IR/LD Payloads shall include the shipping case, operator manual, user control interface and any other ancillary equipment needed to operate the EO/IR/LD Payload. The Contractor shall provide the EO/IR/LD payload Software Product Specification embedded in each payload in accordance with CDRL A036. In addition, one (1) additional copy shall be provided with the first delivered payload to be used by the Government in a software laboratory environment.

3.2.2 Payload Associated Deliverable Materiel

The Contractor shall provide a Part Lists that identifies maintenance parts support requirements for the field to the Lowest Replaceable Unit (LRU), CDRL D020. As required at the DO/TO level, the Contractor shall provide all spare parts, consumables, component parts, field support tooling, diagnostic tools/kits, support equipment, materials, and secondary items for the EO/IR/LD Payload.

3.2.3 Retrofits of Fielded Systems

The Government will provide a GFP-payload for the Contractor to inspect for retrofit.

This retrofit may include, but is not limited to: conversions, field fixes, retrofits, remanufactures, redesigns, upgrades, extended service programs, engineering changes, software revisions, system enhancement programs, service life extension programs, system improvement programs, product improvement programs, preplanned product improvements, Horizontal Technology Integration (HTI), Continuous Technology Refreshments (CTR), and technology insertions. The Contractor shall provide the technical requirements for the retrofit IAW CDRL A001, Retrofits of Fielded Systems. Individual TOs will be issued for the inspection and any necessary retrofits, as needed.

The Contractor shall conduct retrofits to the EO/IR/LD Payloads as required in TOs/DOs. The Contractor shall procure all of the material required to facilitate the EO/IR/LD Payloads Retrofits.

The Contractor shall ensure “A” and “F” condition EO/IR/LD Payloads parts that are removed during the retrofit process shall be tracked and managed as GFP. See DoD 4000.25-2-M Appendix 2.5 for appropriate condition codes. The Contractor shall supply a listing of serialized items and other items in “A” and “F” condition to the Government for confirmation of which items are to be transferred as GFP. A Government Furnished Property and Contractor Acquired Property Master Report will be submitted, in accordance with CDRL B007, to describe the status and supply condition data of the

GFP.

The Contractor is responsible for coordinating the activities of all suppliers and subcontracted efforts. This includes manufacture, procurement, and delivery of all equipment procured to facilitate EO/IR/LD Payloads retrofits. In addition, the Contractor shall coordinate all supplier parts deliveries and data deliveries. The Contractor is responsible for the repair of any EO/IR/LD Payloads parts that are broken during the retrofit. If the contractor consumes a Government furnished spare part, the contractor shall repair the “F” condition part on a separate Firm Fixed Priced (FFP) CLIN.

3.2.4 Engineering Change Proposal (ECP)

3.2.4.1 Class I ECP. The Contractor shall submit ECP IAW the terms and conditions identified in the FAR and DFARS clauses incorporated in this contract and Military Handbook-61A (MIL-HDBK-61A). The Contractor shall submit Class I ECPs, IAW CDRL A002, Engineering Change Proposal-Class I, Major; for system changes that affect form, fit, function, performance, reliability, logistic baseline, logistics infrastructure to include depot capability and delivered Logistics Management Information (LMI) data, and any system certifications such as but not limited to airworthiness, Information Assurance (IA), and anti-tamper. Any changes that impact cost or schedule shall be addressed as a Class I change. The Contractor shall submit all Class I ECPs for Government approval prior to implementation. The ECP shall assess the safety impact due to the software and firmware changes being made to that specific system release.

Government Configuration Management and control will extend beyond the Line Replaceable Unit (LRU) into Shop Replaceable Unit (SRU) assemblies, subassemblies, test and special equipment and components IAW the terms and conditions of the contract and the FAR and DFARS.

ECPs that are initiated by the Contractor shall be solely the Contractor’s responsibility relative to cost. This includes any updates to CDRLs affected by the change in the configuration baseline. ECPs that the Government requests or requires the Contractor to deliver as a result of a Government initiated change shall be delivered IAW Section 3.3.2, and the cost of completing those Class 1 ECPs will be separately priced and funded by the Government.

3.2.4.2 Class II ECP. ECPs not classified as Class I are Class II. Class II changes may be processed by the Contractor, IAW CDRL A003, Engineering Change Proposal- Class II, Minor. However, the local Defense Contract Management Agency (DCMA) Quality Assurance Representative (QAR) shall review all change actions/decisions. If the DCMA QAR does not agree with the classification of a specific change, they may direct the Contractor, with Government Program Office concurrence, to elevate it to Class I. Final classification decision shall be made by the Government.

3.2.4.3 Class I vs. Class II. In instances where the Contractor cannot determine the classification of the change, the change must be designated Class I and submitted IAW CDRL A002, Engineering Change Proposal-Class I, Major.

3.2.4.4 ECP Class Determination. The Contractor shall have Material Review Board Authority for deviations that are classified as Minor IAW ANSI/EIA-649B, ISO 9001 and per MIL-HDBK-61A. The Contractor shall maintain a copy of each minor deviation (i.e., Nonconforming Material Report) and make them available to the Government upon request. All other requests for deviation that are classified as Major shall be submitted to the Government for approval from the approved configuration and incorporation into the applicable individual order. Variation or exception to any Government approved test procedure (ex. acceptance test procedure, environmental stress screening) shall necessitate a Major Request for Variance (RFV), IAW CDRL A004, Request for Variance. The Contractor shall submit a Notice of Revision IAW CDRL A005 for each instance of change initiated by the Contractor, at no additional cost to the Government.

3.2.5 Environmental Stress Screening and Acceptance Testing

The Contractor shall develop Environmental Stress Screening (ESS) Procedures IAW CDRL A006 and Acceptance Test (AT) Procedures IAW CDRL A007 and provide updates as directed by task order. ESS shall be conducted on all production delivery payloads. AT shall be conducted on all production delivery payloads and all payloads that are returned to the Contractor for repair. The Contractor shall notify the Government one week prior to testing to allow for Government witnessing.

3.2.6 Quality Assurance Program

The Contractor shall meet the requirements of ISO 9001-2008 or equivalent and have a quality management system that monitors and controls critical processes; continuously improves processes; establishes mechanisms for performance feedback; and maintains an effective root cause analysis and corrective action system, the terms and conditions of the contract, and FAR Part 46. Any exclusion to the Contractor’s quality control program shall be agreed to between the Contractor and the Government. The Contractor shall make available, for review by the Government, quality system procedures, planning and all other documentation and data that comprise the Contractor's quality control program for both hardware and software. The Government may audit products and processes as well as the quality control system at any stage of contract performance. The Contractor shall also submit a Quality Control Plan (QCP), IAW CDRL A008, Quality Control Plan.

3.3 Systems Engineering Support

The Contractor shall perform Systems Engineering IAW International Organization for Standardization (ISO) / International Electro technical Commission (IEC) / Institute for Electrical and Electronics Engineers (IEEE) 24748-4:2016, Systems and Software Engineering – Life Cycle Management – Part 4: Systems Engineering Planning and provide Systems Engineering Support IAW the Systems Engineering Plan (SEP) (see Attachment 1) for the Shadow RQ-7Bv2 Operations and Support Phase dated 5 January 2016. Contractor shall develop a Specification Requirement Verification Matrix, IAW CDRL A009, to provide traceability between the test requirements and the specification requirements. Efforts under this program may require support in the area of special tools, fixtures, tooling, cables, and other miscellaneous equipment or material to accomplish the specific support effort. The Contractor shall develop a Systems Engineering Management Plan (SEMP) IAW CDRL A010 and submit the plan to the Government for review as required. The SEMP shall be updated IAW CDRL A011.

3.3.1 Product Baseline Review (PBR)

The Contractor shall host a PBR at their CONUS facility to establish and document the product baseline for the EO/IR/LD payload. The meeting shall be two (2) business days in duration at eight (8) hours per day. The Government recommends that the Contractor's Program Manager, Lead Engineer, Lead Manufacturing Engineer and Lead Logistician participate in the PBR, at a minimum. Functional leads and Subject Matter Experts (SMEs) should be available as required to provide the necessary level of detail.

The Contractor shall submit a Conference Agenda IAW CDRL B003 and Presentation Materials IAW CDRL B004 no later than three (3) business days prior to the review. At the completion of the review, the Contractor shall submit a Report, Record of the Meeting IAW CDRL B005.

3.3.1.1 PBR Entry Criteria. The Contractor shall submit drafts of the following CDRLs no later than ten (10) business days prior to PBR. The Contractor’s entry into the PBR shall be contingent upon Government concurrence that the following criteria have been met:

a) The Contractor shall provide Government access to documentation that demonstrates that the EO/IR/LD payload design and any modifications will meet the requirements of the PBS and the RQ-7Bv2 ICD. This shall include, but not be limited to drawings, software architecture, hardware architecture, and interface documentation.

b) The Contractor shall prepare a Risk Analysis IAW CDRL A011 and the

Department of Defense Risk, Issue, and Opportunity Management Guide for Defense Acquisition Programs dated January 2017.

c) The Contractor shall submit the following CDRLs:

1. The IMS IAW CDRL B002

2. The SEMP IAW CDRL A010

3. The First Article Test Plan (Pre-PBR) IAW CDRL A012

4. The Reliability Test Plan (Pre-PBR) IAW CDRL A013

5. The Specification Requirements Verification Matrix showing traceability between PBS requirements and Contractor documentation provided to the Government for review IAW CDRL A009.

3.3.1.2 PBR Exit Criteria. Completion of the PBR shall be contingent upon Government concurrence that the following criteria have been met:

a) Closure and Government approval of assigned action items.

b) Updated Risk Analysis IAW CDRL A014.

c) Product drawings, ICDs, and software design documents, reviewed in

Paragraph 3.3.1.1, are complete and under configuration management.

d) The Contractor shall submit updates of the following CDRLs no later than ten

(10) business days after the review.

1. The IMS IAW CDRL B002

2. The updated SEMP IAW CDRL A015

3. The First Article Test Plan (Post PBR) IAW CDRL A016

4. The Reliability Test Plan (Post PBR) IAW CDRL A017

A018

5. The updated Specification Requirements Verification Matrix IAW CDRL

f) Government stakeholders (PdM EO/IR, PdM TUAS, TRADOC) concur that the design addresses platform level requirements and accept the identified risks and mitigation plans.

3.3.3 Configuration Management (CM)

The Contractor shall implement and maintain a CM system IAW ANSI/EIA-649B and under the general guidance of MIL-HDBK-61A. The CM system shall ensure that each configuration item conforms to the generated documentation. The CM system shall provide for CM planning and management, configuration identification, configuration change management, configuration status accounting, and configuration data of all hardware, firmware, software, and documentation, including Commercial-Off-The-Shelf (COTS) items. The Contractor shall develop and deliver a CM Plan, IAW CDRL A019 and a Configuration Status Accounting Information-As Built Data; IAW CDRL A020.

The Contractor shall maintain the EO/IR/LD Payload Product Specification IAW CDRL A021 and ICDs IAW CDRL A022 to support each configuration and submit updated documents to the Government for approval as required.

3.3.4 Software Engineering Support

The Contractor shall provide software engineering support, as directed by the Government or with an approved ECP, to sustain and upgrade software and firmware configuration items. The Contractor shall develop and maintain a mapping of system specifications to software requirements and document it in a Software Requirements Specification (SRS), IAW CDRL A023. The Contractor shall maintain a software / firmware compatibility matrix for all software releases that shall describe the software versions and compatible firmware to all system releases. The Contractor shall provide a Software Version Description (SVD) document IAW CDRL A024, for each version of software delivered.

3.3.5 Reliability, Availability and Maintainability (RAM) Program

The Contractor shall develop, implement, and execute a RAM program to ensure achievement of the reliability requirements established for the EO/IR/LD Payload. The Contractor shall develop RAM reports and assess the reliability of EO/IR/LD Payloads throughout the life cycle using its System Reliability Model, including applying data from Catalog Ordering Logistics Tracking system (COLTS), Logistics Modernization Program (LMP), and Global Command and Control System – Army (GCSS-A), or other approved IDE. The Government will approve access to these systems. The Contractor shall provide a reliability report IAW: CDRL A025, Reliability and Maintainability Predictions Report; CDRL A026 Reliability Centered Maintenance (RCM) Analysis IAW DoD 4151.22M; and MIL-STD-3034A. These actions shall be negotiated at the task order level.

3.3.6 Failure Analysis

The Contractor shall collect and analyze failure data to determine the root cause of the failures. The Contractor shall implement a Failure, Reporting, Analysis, and Corrective Action System (FRACAS) for tracking of failures. As part of the FRACAS process, the Contractor shall analyze and identify potential patterns or trends failures and provide corrective action to the Government for approval. The Contractor shall provide a report documenting this analysis IAW CDRL A027, Failure Reporting Analysis and Corrective Action Report.

3.4 Integration

3.4.1 Technology Insertion

The Contractor shall insert new technologies into the system baseline that would allow the EO/IR/LD Payload to meet objective requirements of the PBS. The Contractor shall propose new technologies for insertion into the EO/IR//LD Payload baseline and insert them based on Government approval. This integration shall be IAW CDRL A028, Technology Insertion. Coordination and approval with the Government shall occur prior to integration of new technologies. Emphasis shall be on the demonstration of clear and definable improvements in the performance, logistics supportability, reliability, and maintainability of the EO/IR/LD Payload. The Contractor shall propose new technologies through the following process: 1) Submit proposal idea to the Government for a discussion based on requirements. 2) Government determine that the technology is mature and ready for insertion. 3) Contractor and Government mutually identify cost increases (if any), requalification, recertification, fleet retrofit, etc. 4) Contractor identify Work breakdown Structure (WBS). 5) Identify all ECPs to the EO/IR/LD Payload Baseline. 6) Government approves technology insertion. These actions will be negotiated at the TOs/DOs level.

3.4.2 Platform Integration Support

The Contractor shall provide platform integration support related to integration of the EO/IR/LD Payload onto RQ-7Bv2. The Contractor shall enter into a Non-disclosure Agreement (NDA) with RQ-7Bv2 Platform Integrator Contractor. The Contractor shall share information necessary for EO/IR/LD Payloads to be integrated onto the RQ-7Bv2 with the Platform Integrator Contractor. The Contractor shall provide logistics, maintenance, training, engineering, and program management support to meetings with the platform integrator, to include Program Kickoff, System Requirements Review (SRR), System Functional Review (SFR), Preliminary Design Review (PDR), and Critical Design Review (CDR). Such support shall be sufficient to coordinate payload / platform interfaces, performance specifications, and functional capabilities per the EO/IR/LD PBS and ICD. The Government anticipates that these meetings will collectively require 15 business days, to include travel. The Contractor shall provide integration support that includes but is not limited to: support of host platform surveys to identify optimum placement of EO/IR/LD Payload, analysis of concepts and alternatives, and recommendations on integration kit design, (leveraging lessons learned from testing and previous system integration kit efforts). Platform integration support shall include on-site engineering support and telephonic / electronic support for integration and test activities to ensure payload functionality and performance on the RQ-7Bv2 platform. The Government anticipates that these activities will take approximately four

(4) weeks. The Contractor shall provide trip reports for all on-site integration activities IAW B006, Trip Report.

3.4.3 Cybersecurity

The Contractor shall provide the payload cybersecurity information required to support the Government’s RQ-7Bv2 DoD Risk Management Framework (RMF) Accreditation package IAW CDRL A029, Payload Cybersecurity Posture.

3.4.4 Cybersecurity Hardware Capability Documentation

The Contractor shall provide a Certificate of Volatility, if applicable, for any memory component installed in the system and delivery to the Government IAW CDRL A030, Certificate of Volatility. The Contractor shall identify if the payload requires the use of Universal Serial Bus, Flash Media, or any other forms of removable media to transfer data.

3.4.5 Remediation of Cybersecurity Vulnerabilities

Based on the results of the Shadow RMF Accreditation process, the Contractor shall configure the payload to be compliant with Defense Information System Agency (DISA) Security Technical Implementation Guides (STIGs) and Nessus Vulnerability Scans as well as conduct patch management, Information Assurance Vulnerability Management, and cyclical support to remediate or mitigate known critical issues, and other Cybersecurity Engineering functions. These actions will be negotiated at the task order level.

3.5 Testing and Evaluation

3.5.1 Test and Evaluation Support

The Contractor shall provide test and evaluation support on the RQ-7Bv2 platform IAW the Shadow Tactical Unmanned Aircraft System Test and Evaluation Management

Plan, dated April11, 2014 and subsequent revisions. Testing and evaluation support shall include on-site maintenance, training, engineering and telephonic / electronic support to ensure payload functionality and performance on the RQ-7Bv2 platform.

Platform test is anticipated to be conducted at Dugway Proving Ground, Utah for two (2) trips of two (2) weeks each for a total of four (4) weeks.

3.5.2 Test Readiness Review (TRR)

The Contractor shall conduct a TRR to determine if the EO/IR/LD Payload is ready to proceed into First Article Testing (FAT) by providing verification to the Government that includes, but not limited to, established test objectives, test methods and procedures, scope of tests, safety and confirms the required test resources have been properly identified and coordinated to support planned tests. The TRR shall be conducted at the Contractor’s facility. The agenda for the TRR shall be agreed to in advance by the Government and Contractor’s Program Manager. The meeting shall be two (2) business days in duration at eight (8) hours per day. The Government recommends that the Contractor’s Program Manager, Lead Engineer, Lead Manufacturing Engineer, Lead Test Engineer and Lead Logistician shall participate in the TRR. The Contractor shall compile, track and distribute meeting minutes and action items to all attendees.

The Contractor shall prepare an Agenda IAW CDRL B003, Conference Agenda. The Contractor shall prepare and provide presentation material IAW CDRL B004, Presentation Material. The Contractor shall compile, track and distribute meeting minutes and action items to all attendees, IAW CDRL B005, Report, Record of Meeting/Minutes.

3.5.3 First Article Test

The Contractor shall conduct FAT on the first three (3) payloads, as directed by the Government. These payloads will be ordered under a separate CLIN, delivered on Delivery Order 0001. FAT shall also be conducted for new or modified products, including products with changes to a qualified baseline, as directed by the Government.

Requirements to be tested in FAT shall be IAW Section 4.1.1 and Appendix A of the PBS. The FAT will occur at the Contractor's facility or at another capable facility at the Contractor's expense. The Government shall be given the opportunity to participate in the test activity. The Contractor shall ensure that first article items are produced using production representative processes, procedures, and tooling (i.e., not "soft" pre-production tooling) and meet all requirements of the PBS for the Payload Sub-system for the RQ-7Bv2. The Government can request a FAT at any time during the duration of this contract and on a recurring basis as needed, as negotiated in the individual task order. The Contractor shall develop / update the First Article Test Plans IAW CDRLs A012/A016, First Article Test Procedures IAW CDRL A031, Specification Requirement Verification Matrix Update IAW CDRL A018, and First Article Test Report IAW CDRL A032.

3.5.4 Reliability Testing (RT)

The Contractor shall conduct reliability growth testing to verify compliance with the reliability requirements of PBS paragraph 3.11.1. A joint Government/Contractor Test Review Board (TRB) shall provide oversight for the RT. Three (3) EO/IR/LD payloads shall be used for the RT. These systems shall have first successfully passed factory Environmental Stress Screening (ESS) and Acceptance Test (AT) prior to start of the RT. The Government will provide operational environment profiles to the Contractor which the Contractor shall incorporate into detailed test plans to be delivered IAW Reliability Test Plans CDRL A013/A017 and procedures IAW Reliability Test Procedures CDRL A033. At the conclusion of the RT the Contractor shall be required to institute all necessary corrective actions to bring the systems into reliability compliance at no additional cost to the Government, to include all units previously delivered to the Government.

Verification shall be at an 80% confidence by analysis of test data collected in a mission environment and scoring of test events. The standard Chi-squared one-sided, lower-confidence bound distribution calculation (Equation 1) will be used for calculating the Mean Time Between Failure (MTBF) with 80% confidence. Allowing two (2) relevant / chargeable failure occurrences during the test, the test length shall be a minimum of 471 total operating hours to demonstrate the threshold requirement. The test length and failure count is compliant with MIL-HDBK-781A, test plan 20 - 3. Testing shall be considered complete when the Contractor has implemented all corrective action identified to address any failures during the test, and completed all subsequent re-test needed to demonstrate the reliability requirement. The Contractor shall deliver a Reliability Test Report IAW CDRL A034.

Equation 1: MTBF ≥ 2T/ 2 (, 2r+2)

Where: T is total cumulative operating time 2 (, 2r+2) is the Chi-squared distribution is the probability indicated by 1- confidence level (i.e., 1 – 80% confidence = 0.2) r is the total number of chargeable failures

3.5.5 Failed Item Analysis Report

The Contract shall ensure for each failure that occurs during Contractor testing and/or Government conducted testing the Contractor shall notify the Government (via email or letter) within 48 hours and shall provide a Failed Item Analysis Report (FIAR) IAW CDRL A035. The status of all FIARs shall be maintained within a Contractor database accessible to the Government.

3.6 Integrated Product Support

The Contractor shall provide integrated product support for the EO/IR/LD payload IAW AR 700-127 Chapter 2, Framework. The logistics integrated product support requirements shall include but, not be limited to, supportability analysis, supply support, maintenance, training, computer resources, support equipment, property accountability, packaging, handling, storage and transportation.

3.6.1 Supportability Analysis

The Contractor shall develop and support the development of supportability analyses, IAW MIL-HDBK-502A, such as level of repair analysis, core logistics analysis, core depot assessment, business case analysis, cost benefit analysis, analysis of alternatives and sensitivity analysis by participating in IPTs or providing required data to complete analysis.

3.6.1.1 Level of Repair Analysis. The Contractor shall use the Government approved model, Customized Optimization Model for Predicting and Analyzing Support Structure (COMPASS) and submit a Level of Repair Analysis (LORA) Input Data IAW CDRL D001. The Contractor shall support updating the LORA as the system matures. All files shall be maintained IAW AR 25-400-2 and submitted to the Government upon request.

3.6.1.2 Depot Analysis. The Contractor shall support the Government in the development of Core Logistics Capability analysis to determine the core depot level maintenance and repair capability for EO/IR/LD Payloads, IAW Title 10 USC 2464. The Contractor shall deliver a Depot Maintenance Study IAW CDRL D002.

3.6.2 Supply Support

The Contractor shall identify and manage parts and supplies necessary to establish or maintain equipment and replenish stocks used to operate, maintain, and repair the EO/IR/LD payload. This includes spares, repair parts, and consumables.

3.6.2.1 Bill of Materials. The Contractor shall submit a Bill of Materials (BOM) IAW CDRL D003, which includes system breakdown to the piece part level and Production Lead Time.

3.6.2.2 Inventory Report. The Contractor shall provide stock supply reports that include demand forecast reports to the Government to enable sufficient repair part stock availability. The Contractor shall provide this data within Inventory Reports as required by individual orders IAW CDRL D004, Inventory Reports.

3.6.2.3 Provisioning. The Contractor shall submit Provisioning Parts Data, IAW CDRL D005, Engineering Data for Provisioning and SAE/GEIA-STD-0007. The Contractor shall provide updates to any provisioning data due to design changes.

3.6.2.4 Maintenance Allocation Chart (MAC). The Contractor shall maintain, update, and submit the Maintenance Allocation Chart (MAC) IAW MIL-STD-40051-2C and deliver IAW CDRL D006, as configuration and/or maintenance concepts changes.

3.6.2.5 Diminishing Manufacturing Sources and Material Shortages. The Contractor shall minimize materiel readiness risks by developing the DMSMS Management and Implementation Plans, based on Standardization Directory (SD) - 22 DMSMS Guidebook (January 2016), IAW CDRL D007, DMSMS Management Plan and CDRL D008, DMSMS Implementation Plan. The Contractor shall ensure that DMSMS is applied to all current and future Production Payloads as well as spares and repair parts.

The Contractor shall provide notification to the Government no less than 12 months prior to the component becoming obsolete. This notification shall be made through submission of an Obsolescence Alert Notice IAW CDRL D009 within ten (10) days of learning of components that will become obsolete on deliverable equipment or diminishing manufacturing sources but no less than 12 months prior to obsolescence.

This requirement shall be included in all subcontracts at all levels.

3.6.3 Disposal

For items requiring disposal the Contractor shall request COR approval. The Contractor shall perform disposition of excess government property in accordance with FAR and DFARS requirements. Subsequently the Contractor shall plan the disposal of equipment and materials to an approved disposition location and provide a turn in receipt copy to the COR.

3.6.4 Hardware Transition

The Contractor shall provide information to the Government on the EO/IR/LD payload, in accordance with the Integrated Logistics Support Plan, CDRL D010. The plan shall include all twelve (12) Integrated Product Support Elements as identified in the Integrated Product Support Handbook.

3.6.5 Software Transition

The Contractor shall support the software sustainment transition of the EO/IR/LD IAW CDRL D011, Software Transition Plan.

3.6.6 Packing, Handling, Storage, Transportation, and Marking

The contractor shall label and pack all hardware deliverables IAW AR 700-15, chapter 2 or best commercial practices to prevent physical damage during shipment to CONUS destinations. Container markings shall be in accordance with MIL-STD-129R. A packing list containing the contract number, serial numbers and part number for each system/component shall be enclosed in each container listing all items packed therein.

A DD Form 1149 indicating Government initial Inspection signed by DCMA or Government personnel shall also be included in the individual pack. All packed items, whether at the system level or consolidated, shall have human readable serial numbers as well as scanner readable bar-coded serial number information permanently affixed to the outer wrap, ship to/mark for information and serial numbers to aid in asset tracking.

The contractor shall comply with MIL-STD-130N (1), for all contract deliverables. The contractor shall establish appropriate export and logistics support to ensure minimized delays in product shipments and or logistics delays due to export.

Unless otherwise directed by the Government, the Contractor shall label all items for delivery to the following shipping address:

DoDAAC: W91QX7

PdM EO/IR Attn: Warehouse POC, 256-313-0813 Bldg: 7425 Warehouse Rd.

Redstone Arsenal, AL. 35898

3.6.6.1 Item Unique Identification. The Contractor shall comply with the DFARS clause 252.211-7003 for all items that meet the IUID criteria. IUID markings shall IAW MIL-STD-130N (1) with Change 1, for all contract deliverables. The Contractor will submit and update the IUID Marking Plan, IAW CDRL D012, Item Unique Identification Marking Plan, and the IUID Marking and Verification Report, IAW CDRL D013, Item Unique Identification Marking and Verification Report. DFARS clause 252.211-7003, IUID requirements also apply to the EO/IR/LD Payload, and shall be implemented under this contract. The Contractor shall enter the IUID data submittals into the Wide Area Work Flow (WAWF) system and when IUID markings are required for embedded items, the Contractor shall supply the data required. Further guidance and information about IUID, including the DoD Guide to Uniquely Identifying Items, is available at the IUID website: http://www.acq.osd.mil/dpap/pdi/uid/index.html.

3.6.6.1.2 Bar-coding of System, Subsystem, and Parts. The Contractor shall obtain and utilize Automated Information Technology (AIT) equipment and software capable of decoding, encoding, and printing bar-code symbology that complies with industry commercial standards. Contractor label content should be IAW MIL-STD-130N (1) with Change 1. Two-dimensional symbol bar-codes shall be used for all parts identified to receive bar-coding labels. The Contractor’s equipment and software should support the creation of bar-code labels and the decoding of the data printed on the bar-code labels in line with Government systems.

3.6.7 Maintenance Planning/Monitoring

The Contractor shall plan and develop maintenance plans for the EO/IR/LD payload IAW CDRL D014, Maintenance Plan. Updates to the maintenance plan initiated by the Government will be negotiated at TO level. Contractor required updates shall be Not Separately Priced. To include monitoring, addressing, and developing get well maintenance plans in order to maintain an 85% or better operational readiness at the platform level. The formula for Operational Availability is as follows:

Ao = (Operational Time + Standby Time)/Total Time

The Contractor shall use a Government approved information system such as Catalog Ordering Logistics Tracking System (COLTS), Logistics Modernization Program (LMP) or Global Command and Control System – Army (GCCS-A) to track maintenance actions.

The current approved IDEs for this program is Catalog Ordering Logistics Tracking System (COLTS). The contractor shall transfer its tracking efforts to another IDE, such as Logistics Modernization Program (LMP) and/or Global Command and Control System – Army (GCCS-A), when it becomes available for use and at the direction of the Government.

As negotiated at task order level the contractor shall migrate historical payload data to a future IDE.

Maintenance actions include but, not limited to return material authorization, operational status, failure, corrective action, parts required to repair, and status of parts required for repair.

3.6.7.1 Maintenance Concept. The maintenance concept for the EO/IR/LD Payload is IAW the Army’s two levels which are field and sustainment. When an EO/IR/LD Payload is non-mission capable (NMC) beyond the repair level, the unit will send the system to the Field Service Representative (FSR) for analyses. If the FSR cannot perform the repair, they will send the system to the Depot / Original Equipment Manufacturer (OEM). The FSR shall notify the Government Designated Representative that a spare system is required. The Depot/OEM will assess, test and repair the system. The Depot/OEM will ensure the system meets all operating requirements.

3.6.7.1.1 Repairs

3.6.7.1.1.1 Repair Turn Around Times (RTAT). The Contractor shall meet the RTAT for repairs and Major Repairs/Non-standard Depot Repair Inspection Report per Table 3.6.7.1.1.1-1 Maintenance Requirements.

Table 3.6.7.1.1.1-1. Maintenance Requirements

Category

Level of Repair

Description of Off-Platform Corrective

Maintenance to be Performed

Maintenance Details

Repair Turn

Around Time

(RTAT)

Government

Approval Prior to Repair

Required?

(Yes/No)

1 Basic Includes repair of LRUs by removing and replacing some SRUs due to standard operations.

Examine humidity indicators Change desiccant Examine and clean payload Conduct boresight

14 Days (w/ FSR) * 30 Days (w/o FSR) **

No calibration BIT error code diagnostics

Intermediate

Includes repair of LRUs by removing and replacing some SRUs due to standard operations.

Image processing CCA repair

GBSM repair

14 Days (w/ FSR) * 30 Days (w/o FSR) **

No

3 Standard Depot Level Repair

Includes repair of LRUs by removing and replacing most SRUs due to standard operations.

Gimbal drive motors Temperature sensor repair Hand controller repair

Gimbal processor repair

Yoke assembly repair

30 days No

4 Depot Level 01

Repairs that are resultant from non-standard operations such as; hard landings, impact (with ground or other object) or excessive loading that results in damage to the…