Sect_J_Attach_A_PWS_19Apr2016.pdf

W911QY-16-R-0009 Attachment A

RQ-7B

UNMANNED AIRCRAFT SYSTEMS

(UAS)

Technical Services and Field Support (TSAFS)

Indefinite Delivery Indefinite Quantity (IDIQ)

Performance Work Statement

(PWS)

28 March 2016

Prepared By:

Unmanned Aircraft Systems (UAS) Project Office

SFAE-AV-UAS-TUAS

TABLE OF CONTENTS

1 SCOPE

1.1 Type of Contract

1.2 Period of Performance

2 APPLICABLE DOCUMENTS

3 TECHNICAL SERVICES REQUIREMENTS

3.1 General

3.1.1 Origination/Revision – TO Policy

3.1.2 Task Order Funding Expenditures

3.1.3 Task Order Completion

3.1.4 Contract Transition Plan

3.1.5 Data Requirement and Data Rights

3.1.5.1 Non-Disclosure Agreement and Transfer of Information

3.2 Task Order Functional Areas

3.2.1 Program Management

3.2.1.1 Program Management Status Review (PMSR)

3.2.1.2 Integrated Product Team (IPT) Meetings

3.2.1.3 Contractor Integrated Performance Management

3.2.1.3.1 Earned Value Management System (EVMS)

3.2.1.3.2 Cost

3.2.1.3.3 Contract Work Breakdown Structure

3.2.1.4 Integrated Baseline Review (IBR)

3.2.1.5 Contractor Manpower Reporting

3.2.1.6 Integrated Master Plan (IMP)

3.2.1.7 Contract Cost and Software Data Reporting (CSDR)

3.2.1.8 Subcontract CSDR Reporting

3.2.1.9 CSDR Post Award Conference

3.2.1.10 Integrated Performance Management Reviews

3.2.2 Configuration Management (CM)

3.2.2.1 Configuration Management Plan (CMP)

3.2.2.2 Configuration Control

3.2.2.3 Engineering Change Proposal

3.2.2.4 Request for Deviation

3.2.2.5 Configuration Auditing and Verification

3.2.2.6 Technical Data Package (TDP)

3.2.2.7 Data Accession List

3.2.2.8 RQ-7B Technical Data Package Maintenance

3.2.2.9 Data Management (DM)

3.2.3 Engineering and Integration

3.2.3.1 Engineering and Integration Processes and Deliverables

3.2.3.2 Software Requirements

3.2.3.2.1 Software Development Plan (SDP)

3.2.3.2.2 Open Source Software (OSS) Products

3.2.3.2.3 Capability Maturity Model Integration (CMMI)

3.2.3.2.4 Software Releases

3.2.3.2.5 User Interface Manual

3.2.3.2.6 Software Transition Plan

3.2.3.2.7 Acquire Software Licenses

3.2.3.3 Architecture

3.2.4 Quality System/Product Assurance

3.2.4.1 Product Acceptance System

3.2.4.1.1 Equipment Accuracy and Calibration

3.2.4.1.2 Gauge Repeatability and Reproducibility (Gauge R&R)

3.2.4.2 Subcontractor/Supplier Quality Management

3.2.4.3 Manufacturing and Quality Plan

3.2.4.4 Electrostatic Discharge (ESD)

3.2.4.5 Reliability and Maintainability

3.2.5 Test and Evaluation

3.2.6 Integrated Products Support

3.2.6.1 Hardware and Software/Firmware Design Changes

3.2.6.1.1 Logistics Management Information

3.2.6.1.1.1 Maintenance Planning

3.2.6.1.1.2 Level of Repair Analysis

3.2.6.1.1.3 Manpower and Personnel

3.2.6.1.1.4 Packaging, Handling, Storage, and Transportation (PHS&T)

3.2.6.1.1.5 Supply Support

3.2.6.1.1.6 Support Equipment

3.2.6.1.1.7 Provisioning Requirements

3.2.6.2 Modification Work Orders (MWOs)

3.2.6.3 Technical Manuals (TM)

3.2.6.3.1 Technical Manual Updates

3.2.6.3.2 Technical Manual Development Source Material

3.2.6.3.3 TM Validation

3.2.6.3.4 TM Verification

3.2.6.3.5 Acceptance/Rejection Criteria

3.2.6.3.6 Training and Training Resources Support

3.3 Cybersecurity

3.3.1 Information Assurance (IA) Testing

3.3.2 Information Assurance (IA) Continuous Monitoring

3.3.3 Contractor-Owned Information Systems

3.4 Safety

3.4.1 Hazard Tracking System

3.4.2 Hazardous Material Management

3.4.3 Airworthiness Requirements

3.5 Security

3.5.1 Antiterrorism (AT)/Operations Security Compliance

3.6 Government Furnished Equipment/Property (GFE/GFP)

4 LOGISTICS SUPPORT SERVICES

4.1 New Equipment Training (NET)

4.2 Field Activities

4.3 Equipment for Training Support

4.4 Other Training

4.5 Operations Manpower

4.5.1 Government Owned – Contractor Operated (GOCO) Personnel

4.5.2 Government Furnished Equipment (GFE) Operations and Support

4.5.3 Personnel for Enhanced Platoon Augmentation

4.5.4 Enhanced Platoon Augmentation Teams

4.5.5 Enhanced Platoon Augmentation - Synthetic Aperture Radar (SAR) Teams

4.5.6 Contractor Crew Logistics Support

4.5.7 Contractor Crew Mission Requirements

4.5.8 Contractor Crew Currency Requirements

4.5.9 Individual Crew Member Certification

1 SCOPE

This Performance Work Statement (PWS) establishes overall requirements for an Indefinite

Quantity/Indefinite Delivery (IDIQ) services contract providing technical and logistics services in support of the Tactical Unmanned Aircraft System (TUAS), the Universal Ground Control

Station (UGCS), and the Universal Ground Data Terminal (UGDT), in CONUS and OCONUS, and their domestic and foreign customers, as allocated by individual Task Orders (TOs).

The Government shall not exercise any supervision or control over the contract service providers performing the services herein. Such contract service providers shall be accountable solely to the contractor who in turn is responsible to the Government. The contractor shall provide all personnel, equipment, tools, materials, supervision and non-personal services necessary to perform Technical Services and Field Support (TSAFS) as defined in this

Performance Work Statement (PWS).

The TOs will consist of the following major categories including respective data deliverables as specified therein:

Technical Services

Logistics Support Services

Individual TOs will be issued in accordance with (IAW) this PWS that contain the specific requirements for the development, integration, non-repetitive investigation, inspection, analysis and corrective action, test or evaluation efforts for the TUAS, UGCS, UGDT, their configuration variants, and components.

The TUAS, UGCS and UGDT are designed to meet the Army’s requirement for flexible, responsive near real-time Reconnaissance, Surveillance, and Target Acquisition (RSTA), Battle

Damage Assessment (BDA), and battle management support to maneuver commanders of

Combat Aviation Brigades (CAB), Brigade Combat Teams (BCT) and Armored Cavalry

Regiments (ACR) for peace operations and all levels of war.

1.1 Type of Contract

The Government anticipates award of a Multiple Award IDIQ contract. The Government intends to issue Firm-Fixed price TOs under this contract but reserves the right to issue Cost type TOs as the procurement situation requires.

1.2 Period of Performance

The anticipated ordering period will be five years. The Government reserves the right to extend the term of this contract at the prices set forth in the contract at time of award in accordance with (IAW) the terms and conditions contained in Federal Acquisition Regulation (FAR)

52.217-9, Option to Extend the Term of the Contract.

2 APPLICABLE DOCUMENTS

Applicable top level documents are contained in the Document Summary List (DSL), by number, title, and date. The document versions specified on the DSL (or amended after contract award) take precedence over the generic references (without revision letters) cited in the PWS.

3 TECHNICAL SERVICES REQUIREMENTS

3.1 General

The contractor shall perform all efforts to conduct non-repetitive development, integration, investigation, inspection, analysis and corrective action, test or evaluation efforts for the TUAS, UGCS, and UGDT, their configuration variants, and components of the TUAS, UGCS and

UGDT systems, as directed by the TOs. All efforts performed by the contractor under this contract shall be provided in accordance with (IAW) this Base PWS and its applicable issued

TOs.

The UAS Project Office will utilize this PWS and applicable TOs to satisfy requirements for development and procurement of upgrades, modifications, new payloads, and test support of same. The contractor shall provide full engineering support for development, producing, and delivering the resulting required product. Quantities procured shall be sufficient to support the development testing, operational testing, and Low Rate Initial Production (LRIP) quantities, not to exceed (NTE) 10% of the total fielding quantity. Quantities procured shall be aligned to numbers sufficient to validate the aforementioned new concepts / upgrades, IAW the direction in the TOs.

The contractor, as an independent contractor and not as an agent of the Government, shall provide all labor and materials necessary (except those furnished by the Government) to accomplish TO requirements in the performance of this PWS. The Period of Performance

(PoP) will be specified by the individual TOs.

Note: All dates/time spans specified for Data Deliverables shall be “calendar days” unless specified otherwise in the Contract Deliverable Requirements List (CDRL).

3.1.1 Origination/Revision – TO Policy

Each TO will be awarded for a specific effort(s) for requirements covered by the scope of this

Base PWS. The Government will prepare new and revised requirements which may or may not result in Contracting Officer (KO) negotiated and issued TOs. These TOs will delineate the technical direction of the respective Base PWS tasks. The Base PWS, revisions to the Base

PWS, and TOs will be incorporated only by contract modification. The explicit requirements of a TO will take precedence over the more general requirements in the Base PWS. All requirements in this PWS shall apply to the TOs unless those requirements are specifically excluded or modified within the TO.

3.1.2 Task Order Funding Expenditures

The contractor shall notify both the KO and the Government Technical Manager (GTM), in writing, when 75 percent of the funds allocated to the TO have been expended (excluding Firm

Fixed Price (FFP) TOs). The contractor shall then follow specific direction given by the KO.

In no case shall the contractor expend funds on a (cost) TO beyond the original estimated cost prior to approval of a revision establishing a new estimated cost by the KO (see FAR 52.232-22

Limitation of Funds).

3.1.3 Task Order Completion

At the completion of each TO, the contractor shall prepare an Engineering Accomplishment

Report on that TO and deliver IAW DI-MGMT-80061 (CDRL A001).

3.1.4 Contract Transition Plan

As directed by the Government, the contractor shall submit a Transition Plan describing actions required to transition support services from the current existing contract to the TOs proposed under this PWS (e.g. NET, GOCO, EPA). When directed by a TO, the Transition Plan, shall be delivered to the Government no later than 30 days after contract award IAW DI-MISC-80508B

(CDRL A029).

3.1.5 Data Requirement and Data Rights

3.1.5.1 Non-Disclosure Agreement and Transfer of Information

If performance of this contract requires access to another contractor’s proprietary information, the contractor shall (i) enter into a written agreement (Non-Disclosure Agreement (NDA) similar to DFARS 227.7103-7) with the other entities involved, as appropriate, in order to protect such proprietary information from unauthorized use or disclosure for as long as it remains proprietary; and (ii) refrain from using such proprietary information other than as agreed to, for example; to support execution of the TOs awarded under this contract. An executed copy of all proprietary information agreements by individual personnel or on a corporate basis shall be furnished to the KO within fifteen (15) calendar days of execution.

The NDA shall be enforceable throughout the life of the contract unless revoked in writing by both parties in the agreement. The NDA shall be executed and provided to the Government as an attachment to the contract. The NDA shall outline the agreed upon procedures between the two companies detailing how data shall be securely transferred between them post contract award. All awardees will be notified of the NDA status NLT 30 days ACA. Upon notification, contractors shall begin inter-party transfer of information requiring an NDA and complete the task NLT 30 days after notification.

The contractor shall promptly notify the KO, in writing, if it has been tasked to evaluate or advise the Government concerning its own products or activities or those of a competitor in order to ensure that proper safeguards exist to guarantee objectivity and to protect the

Government's interest.

The following are sample provisions that may be tailored and included at the TO level.

Nondisclosure of Sensitive and/or Proprietary Data:

The contractor recognizes that in the performance of this TO, subject to an executed NDA, it may receive or have access to certain sensitive information, including information provided on a proprietary basis by original equipment manufacturers (OEMs) and other public or private entities.

The contractor agrees to use and examine this information exclusively in the performance of this

TO and to take the necessary steps IAW Government regulations to prevent disclosure of such information to any party outside the Government or Government designated support contractors possessing appropriate proprietary agreements.

The contractor agrees to indoctrinate its personnel who have access to sensitive information regarding the management, safeguarding, limitations in use, and the relationship under which the contractor has possession of or access to the information. Contractor personnel shall not engage in any other action, venture or employment wherein sensitive information will be used for the profit of any party other than those furnishing the information. The NDA for contractor employees shall be signed by all indoctrinated personnel and forwarded to the respective contractor’s Task Monitor for retention, prior to work commencing. The contractor shall restrict access to sensitive/proprietary information to the minimum number of employees necessary for contract performance.

3.2 Task Order Functional Areas

This PWS defines the overarching functional areas and tasks to be performed under the TOs.

The TO Functional Areas are summarized below.

3.2.1 Program Management

This section details contractor activities regarding TO management, including engineering services program planning, organizing, control of hours and costs, staffing, and control and release of reports and program liaison with the Government.

3.2.1.1 Program Management Status Review (PMSR)

The contractor shall conduct a quarterly PMSR meeting to review overall program status.

These reviews shall be conducted at the contractor’s site or the Government site, with venue to be determined by the Government on a case by case basis.

3.2.1.2 Integrated Product Team (IPT) Meetings

The contractor, during the PoP for a given TO, shall conduct weekly Integrated Product Team

(IPT) meetings. The contractor shall use IPTs to provide status, to coordinate with

Government, and resolve issues, and as such, each IPT shall have an objective means to measure program success and shall identify risk areas and develop solutions to mitigate these risks. The IPTs shall have joint Government/contractor leads. Under no circumstance shall any

IPT have the authority to make contract changes. The KO is the only person authorized to make contract changes; therefore, any IPT recommendations which require contract modification shall be forwarded to the KO in writing, along with a request to modify the contract. The contractor shall coordinate an agenda and maintain minutes with action items addressed at subsequent meetings and milestone reviews.

3.2.1.3 Contractor Integrated Performance Management

TOs specify labor hours and a dollar value, and contain event phased technical milestones per the most current Government approved Systems Engineering Plan (SEP, UAS-00004) with a project schedule so as to facilitate Contractor Integrated Performance Management. The contractor shall comply with the following subparagraphs of this section (3.2.1.3) to ensure the aforementioned Performance Management.

3.2.1.3.1 Earned Value Management System (EVMS)

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

Earned Value Management System (EVMS) IAW Defense Federal Acquisition Regulation

Supplement (DFARS) 252.234-7001, DFARS 252.234-7002, 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 work breakdown structure, integrated master schedule, 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 be invoked for individual TOs on a case by case basis as determined by the Government.

The contractor shall prepare an Integrated Program Management Report (IPMR) IAW DI-

MGMT-81861 (CDRL A002) for all cost plus type or incentive TOs greater than or equal to

$20 million or deemed high risk by the Government. The contractor shall prepare an IPMR

Format 6 (Integrated Master Schedule) for Fixed Priced tasks as directed by the TO. The IPMR shall integrate cost and schedule performance data with objective technical measures of performance. The contractor shall flow down IPMR requirements to any subcontractor that has a cost or incentive contract valued at or greater than $20 million in then-year dollars.

Task

Order

Type

Value IPMR

Format

IPMR

Format

IPMR

Format

IPMR

Format

IPMR

Format

IMPR

Format 6

IPMR

Format

Cost

Plus or

Incentive

< $20M Required if directed by the TO

Not

Required

Not

Required

Not

Required

Required if directed by the TO

Required if directed by the TO

Required if directed by the TO

Cost

Plus or

Incentive

> or =

$20M and <

$50M

Required Not

Required

Not

Required

Not

Required

Required Required Required

Cost

Plus or

Incentive

> or equal to

$50M

Required Required Required Required Required Required Required

Firm

Fixed

Price

Any Not

Required

Not

Required

Not

Required

Not

Required

Not

Required

Required if directed by the TO

Not

Required

3.2.1.3.2 Cost

The contractor shall prepare and submit a Contract Funds Status Report (CFSR) IAW DI-

MGMT-81468 (CDRL A003) for all cost plus or incentive fee TOs. A CFSR is not required for each individual TO.

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

80165A (CDRL A004) for all cost plus or incentive TOs less than $20 million and EVMS not required.

3.2.1.3.3 Contract Work Breakdown Structure

The contractor shall prepare the CWBS and dictionary IAW the CAPE approved contract

CSDR plan (Section J Attachment F) and IAW DI-MGMT-81334 (CDRL A005). The contractor CSDR reporting requirements shall be based on the CAPE-approved CSDR Plan and these requirements. The contractor may further extend the CWBS for its own reporting purposes. The contractor shall maintain and update the WBS and dictionaries during contract execution.

3.2.1.4 Integrated Baseline Review (IBR)

The contractor shall support an Integrated Baseline Review (conducted by the Government) whenever the value of a cost plus or incentive type TO is equal to or exceeds $20 million, or if

EVMS is required on the TO. 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 IBR shall be held NLT 75 calendar days after the TO award. The contractor shall perform formal rebaselining/reprogramming (OTB/OTS, or single point adjustment) of its contract budget baseline only after receiving authorization in writing from the Government KO. Each IBR shall verify that 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. 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.

3.2.1.5 Contractor Manpower Reporting

The contractor shall report all contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract for the Unmanned Aircraft

Systems Project Office via a secure data collection site. The contractor is required to completely fill in all required data fields using the following web address:

http://www.ecmra.mil/, and then click on “Department of the Army CMRA” or the icon of the

DoD organization that is receiving or benefitting from the contracted services.

Reporting inputs will be for the labor executed during the period of performance during each

Government fiscal year (FY) which runs October 1 through September 30. While inputs may be reported any time during the FY, all data shall be reported no later than October 31 of each calendar year, beginning with 2017. Contractors may direct questions to the help desk by clicking on “Send an email” which is located under the Help Resources ribbon on the right side of the login page of the applicable Service/Component’s CMR website”.

3.2.1.6 Integrated Master Plan (IMP)

The contractor shall develop and submit an Integrated Master Plan (IMP) for all TOs which require an IPMR, IAW DI-MISC-80508 (CDRL A006), and maintain the IMP using the DoD http://www.ecmra.mil/

Integrated Master Plan and Integrated Master Schedule Preparation and User Guide as a guide.

The IMP shall be the foundation of the program schedule and shall provide a hierarchy for schedule traceability and summarization. The IMP shall be submitted for review at the IBR.

The IMP shall describe the contractor’s organization, assignment of function, duties and responsibilities, management procedures and policies, and reporting requirements for the conduct of contractually-imposed tasks, projects, or programs. IMPs shall be generated and maintained at the TO level.

3.2.1.7 Contract Cost and Software Data Reporting (CSDR)

The contractor shall prepare and provide the following Contractor Cost and Software Data

Reports (CSDRs) IAW the OSD Deputy Director, Cost Assessment (DDCA) - approved Cost and Software Data Reporting (CSDR) Plan provisions.

Cost Data Summary Report prepared IAW DI-FNCL-81565 (CDRL A007), Functional Cost- Hour Report prepared IAW DI-FNCL-81566 (CDRL A008), Reserved (CDRL A009), and

Contractor Business Data Report prepared IAW DI-FNCL-81765 (CDRL A010), Sustainment Functional Cost-Hour Report prepared IAW DI-FNCL-81992 (CDRL A011).

The contractor shall submit a Software Resources Data Reporting: Initial Developer Report and

Data Dictionary IAW DI-MGMT-81739 (CDRL A012) and Software Resources Data

Reporting: Final Developer Report and Data Dictionary IAW DI-MGMT-81740 (CDRL A013) for all software TOs that total $20 million or more.

3.2.1.8 Subcontract CSDR Reporting

The contractor shall, with the assistance of the Government, prepare and submit to the KO or designee, proposed CSDR plans, IAW DOD 5000.04-M-1, within 60 days of subcontract award for any subcontracts exceeding $50 million or any subcontracts valued at between $20 million and $50 million that the Department of Defense Cost and Resource Center (DCARC) designates as being high risk, high value, or high technical interest. The contractor shall flow down the CSDR requirements, IAW DoD 5000.04-M-1, to any contractor that has a contract valued at over $50 million or any contracts valued at between $20 million and $50 million that are designated by DCARC as being high risk or high technical interest.

3.2.1.9 CSDR Post Award Conference

The contractor shall participate with the Government in a CSDR conference, IAW DoD

5000.04-M-1, in order to determine the final contract CWBS elements, recurring and nonrecurring classifications, and to resolve any other CSDR issues. The Government will schedule the CSDR Conference to be conducted after contract award. Conference deliverables by the contractor shall include any accepted CSDR Plans or a resolved revised CSDR Plan ready for approval submission. This conference may be held via teleconference, virtually or face-to-face as determined by the DoD Program Office and the Defense Cost and Resource

Center (DCARC).

3.2.1.10 Integrated Performance Management Reviews

The contractor shall participate in a monthly Government-conducted review of cost, schedule and technical status as reported on the prior month's IPMR.

3.2.2 Configuration Management (CM)

The contractor shall serve as the configuration management activity for TOs and shall be responsible for all functions related to the configuration management of engineering documentation to include change management of the functional, allocated, and product configuration baselines for all systems, subsystems, assemblies, components and parts developed or produced under awarded TOs. The contractor shall define and control all interface requirements and ensure compatibility and interoperability for hardware and software components. The contractor shall designate a single Configuration Manager (CM) to manage the TOs configuration.

3.2.2.1 Configuration Management Plan (CMP)

The contractor shall develop and implement a Configuration and Data Management (DM) program to include configuration management planning, configuration identification, configuration control, and configuration verification and auditing. The contractor shall use

MIL-HDBK-61A as a guide in developing the CM/DM program and plan. The contractor shall prepare a program unique CMP IAW DI-CMAN-80858 (CDRL A014). The CMP shall document the contractor’s configuration and data management organization, methodologies, and processes utilized to prepare, distribute, review, approve, release, and control the revision and status of hardware, software and firmware engineering documentation developed under the

TOs. The CMP shall identify the contractor’s configuration and data management tools. The

CMP shall identify the contractor’s configuration change tracking systems, the contractor

Configuration Control Boards, to include material review boards, software review boards and engineering review boards used to review and evaluate requirements and materials before the engineering proposals/request for deviation are presented for Government approval. The CMP shall identify the participants, interactions, relationships and authorities for each of these boards. The CMP shall identify auditing and verification processes and procedures. The

Government may attend and participate at review boards identified within the CMP as part of the CM process.

3.2.2.2 Configuration Control

The contractor shall participate in Configuration Control Boards (CCBs), as identified in the

TO, to present to the Government the proposed configuration changes and limited departures

(Sections 3.2.2.3 and 3.2.2.4) to the approved configuration baseline documentation prior to adjudication by the PM. All changes to a Universal Product shall be presented to the Integrated

Joint CCB (I-JCCB) for concurrence prior to submittal and final adjudication by the Product

Office JCCB. Any changes that impact ICDs, or other controlled documentation shall not be implemented by the contractor without prior contractual authorization. Any proposed changes that impact current or future production or operational support costs shall contain life cycle cost justification.

JCCB – The contractor shall contribute to the JCCB’s review of ECP packages submitted to change the TUAS Shadow (Functional, Allocated, or Product) baseline, regardless of change originator. The contractor’s participation shall be limited to evaluating the submitted ECP package for completeness and adequacy for incorporation into the appropriate database used by the contractor to maintain the affected baseline. (e.g., DOORS, eMatrix, NX Models).

The contractor shall participate in design reviews to assist PdM TUAS in recognizing and resolving potential baseline change conflicts between changes in-work, whether or not the contractor is developing the design change. An expected output from Design Reviews, shall be a decision on whether or not the ECP is to be incorporated into the product baseline.

The contractor shall provide a proposal appropriate for each approved ECP (i.e., full cut in, or limited effectivity) to incorporate into the contractor’s PLM system after approval by the JCCB.

3.2.2.3 Engineering Change Proposal

Pursuant to a Government directed TO, the contractor shall prepare an Engineering Change

Proposal (ECP) IAW DI-SESS-80639 (CDRL A015) to propose Class I changes to the

Government approved configuration documentation. Proposals that have the potential to influence / impact any of the Universal products must first be approved by the I-JCCB. The contractor shall prepare Notices of Revision (NORs) IAW DI-SESS-80642 (CDRL A016), and

Engineering Release Records (ERRs) prepared IAW DI-SESS-80463 (CDRL A017). The contractor shall prepare Specification Change Notices (SCN) IAW DI-SESS-80643 (CDRL

A018), when the respective baseline specification is impacted. NORs and SCNs shall be included with an ECP to document the current and proposed configuration changes to the impacted configuration documentation.

CHANGE CLASSIFICATION

The contractor shall classify all proposed configuration changes as a Class I or Class II change.

A configuration change shall be classified as a Class I change if the proposed change:

1. Affects any physical or functional requirement in the controlled functional or allocated configuration documentation, or

2. Affects any controlled functional, allocated or product configuration documentation, and costs, warranties, or contract milestones/deliveries, or

3. Affects controlled product configuration documentation, and one or more of the following:

a. Government furnished equipment

b. Safety,

c. Compatibility, interoperability, or logistics support,

d. Delivered technical manuals (operations and maintenance),

e. Will require retrofit of delivered units,

f. Impacts to performance.

g. Interchangeability, substitutability, or replaceability or any items down to non-repairable subassemblies,

h. Source on a source control drawing,

i. Skills, manning, training, biomedical factors or human engineering design,

j. Reliability, maintainability, survivability,

k. Weight, balance, moment of inertia, interface and electromagnetic characteristics

l. Information Assurance: Changes that impact Information Technology (IT) systems (e.g. IT Hardware (HW), Operating Systems (OS), Web Engines, and

Database changes), and network configuration or network boundary protection

(e.g. firewall modifications).

m. Rights in data

n. Form, fit and function

Class II engineering changes shall be submitted and dispositioned in contractor format, as

Engineering Change Notices (ECNs) to the Defense Contracts Management Agency (DCMA) for approval as Class II (vice Class I) changes. DCMA will review the Class I check list (see previous paragraph) and validate that no Class I criteria are included. DCMA will be the approval authority for Class II changes.

3.2.2.4 Request for Deviation

The contractor shall prepare a Request for Deviation (RFD) IAW DI-SESS-80640 (CDRL

A019) to solicit Government acceptance of nonconforming material.

3.2.2.5 Configuration Auditing and Verification

FUNCTIONAL CONFIGURATION AUDIT (FCA):

The contractor shall, when directed by a TO, prepare a Functional Configuration Audit (FCA)

Plan IAW DI-SESS-81646 (CDRL A020). The contractor shall conduct, in conjunction with the Government, Functional Configuration Audits (FCAs) when directed by a TO. The contractor shall make available for Government review, at least 30 days in advance of the FCA, all documentation required for the conduct of the FCA. The contractor shall prepare and deliver a Configuration Audit Summary Report IAW DI-SESS-81022 (CDRL A021).

PHYSICAL CONFIGURATION AUDIT (PCA):

The contractor shall prepare a Physical Configuration Audit (PCA) Plan, when directed by a

TO, IAW DI-SESS-81646 (CDRL A020). The contractor shall conduct, in conjunction with the Government, Physical Configuration Audits (PCAs) when directed by a TO. The contractor shall make available for Government review, at least 30 days in advance of the PCA, all documentation required for the conduct of the PCA. The contractor shall prepare and deliver a

Configuration Audit Summary Report IAW DI-SESS-81022 (CDRL A021).

3.2.2.6 Technical Data Package (TDP)

The contractor shall deliver Product Drawings, Models, and Associated Lists IAW DI-SESS-

81000 (CDRL A022) and the associated TDP Option Selection Worksheet, as required by the efforts associated with individual TOs. 3D Models shall only be required when specifically called out in the TO and shall be delivered by the contractor IAW DI-SESS-81000 (CDRL

A023). The TDP shall include all product configuration documentation, resulting from the modification effected by the respective TO, such as product performance specifications, interface documents, drawings, assembly drawings, parts lists, schematics, printed circuit board designs, detail specifications, software source code, executable code, integration procedures, associated Operating Procedures, Acceptance Test Procedures (ATPs) unless otherwise identified as a separate deliverable. The contractor shall identify all interchangeable end item level interface requirements and prepare an Interface Control Document (ICD) list IAW DI-

SESS-81248 (CDRL A024), if not separately tasked. All TDP and associated list documentation shall be provided in a format consistent with MIS-STD-52406-IS. The TUAS is defined as the Aircraft, GCS, GDT, PGCS, PGDT, all configuration variants and components, Data Link Suite, Automatic Take-Off and Landing Ground Unit, Ground Support Equipment, and all ancillary equipment required to support the operation and maintenance of the system.

Delivery of the Technical Data Package shall include components and design activities accomplished by subcontractors.

3.2.2.7 Data Accession List

The contractor shall provide a Data Accession List (DAL) IAW DI-MGMT-81453 (CDRL

A025) of all documentation developed as part of a respective TO. The contractor shall ensure documents on the DAL are available upon request.

3.2.2.8 RQ-7B Technical Data Package Maintenance

As required by a specific TO, the contractor shall maintain the complete Technical Data

Package (TDP) of the TUAS Shadow system. This maintenance shall be for any configuration changes (Class I or II) to the product baseline. The contractor shall continue to maintain the

TDP in the contractor’s Product Lifecycle Management (PLM) system.

The contractor shall:

Attend design reviews for task orders in work to assess impact to the product baseline.

Provide input and review draft ECPs to assess impact to the product baseline.

Review the completed task order ECP prior to JCCB and provide feedback / input / recommendations to PdM TUAS relative to product baseline impact.

Attend the task order JCCB to support approval of the task order ECP.

Provide a proposal appropriate for each approved ECP (i.e., full cut in, or limited effectivity) to incorporate into the contractor’s PLM system.

The contractor shall provide a full RQ-7B TDP to the Government on an annual basis IAW DI-

SESS-81000 (CDRL A022) in the event of change from the previous annual submittal.

3.2.2.9 Data Management (DM)

The contactor shall maintain a DM program to control and track the delivery of data items required by the Contract Data Requirements List (CDRL), DD Form 1423. The Government review cycle will be initiated when the deliverable is receipted by the Government

Configuration/Data Manager.

3.2.3 Engineering and Integration

This section details contractor engineering activities to include systems engineering functions, integration, interoperability, product engineering, and problem resolution throughout the program lifecycle.

Engineering and integration efforts to be executed by the contractor, as required by the TO(s), shall include the design, development, hardware fabrication, software modification to include source code, integration, test, and technical development or modification to drawings, design documents, security documents, Command, Control, Communications, Computers and

Intelligence (C4I), and logistics documentation (i.e., Modification Work Orders (MWOs), plans, reports, and engineering input for technical manuals). The contractor shall establish a program liaison with the Government via an overarching System Engineering, Integration, and

Test (SEIT) Integrated Product Team (IPT) and subIPTs.

3.2.3.1 Engineering and Integration Processes and Deliverables

As directed by the Government, the contractor shall prepare a System Engineering Management

Plan (SEMP) IAW DI-SESS-81785 (CDRL A026). The SEMP shall comply with the latest approved System Engineering Plan (SEP), (UAS-00004) and incorporate a crosswalk of its methodology, processes, criteria, and content to the SEP. The contractor shall ensure that its subcontractor's System Engineering practices and processes are in compliance with and traceable to the Government approved SEMP for efforts performed in support of TOs of this contract. The contractor shall implement the Government approved SEMP to execute all systems engineering required under this contract and its TOs.

The contractor shall maintain compliance with the System/Subsystem Performance

Specification for Tactical Unmanned Aerial Vehicle (TUAV) (R38431-00003), the

Performance Specification for the Tactical Common Data Link (TCDL) System (R39489-

00064), the Performance Specification for the Universal Ground Data Terminals (R39278-

30003), and the Performance Specification for the Universal Ground Control Station (R39593-

00036), as applicable, for efforts under this contract and its TOs. The contractor shall prepare/revise the following deliverables as tasked by the individual TOs:

Revisions to Existing Government Documents IAW DI-ADMN-80925

(CDRL A027)

Engineering Studies, Reports, and Analyses

2 versions – (review only and approval required) IAW DI-MISC-80508

(CDRLs A028, A029)

Contractor Evaluation of Technical Publications and Recommended Changes IAW DI-TMSS-81670

(CDRL A030)

First Article Qualification Test Plan and Procedures IAW DI-NDTI-81307

(CDRL A031)

Reliability Centered Maintenance (RCM) Failure Modes and Effects Analysis (FMEA) Report IAW DI-SESS-80980

(CDRL A032)

Frequency Allocation Data IAW DI-MISC-81174

(CDRL A033)

Specification Requirements Verification Matrix IAW DI-MISC-81283

(CDRL A034)

System/Subsystem Performance Specification (SSS) IAW DI-IPSC-81431

(CDRL A035)

System/Subsystem Design Description (SSDD) IAW DI-IPSC-81432

(CDRL A036)

3.2.3.2 Software Requirements

The contractor shall manage all software requirements IAW the Product Office approved SEP

(UAS-00004). The contractor shall manage all safety critical software IAW the SEP (UAS-

00004). The contractor shall develop software IAW AMCOM Regulation 385-17 and the SEP.

The contractor shall prepare and deliver Computer Software Products to the Government IAW

DI-IPSC-81488 (CDRL A037). Computer Software Products shall include all software for the system, test and maintenance software.

The contractor shall prepare software configuration item qualification test plans IAW DI-IPSC-

81438 (CDRL A038), and document software qualification test reports IAW DI-IPSC-

81440(CDRL A039). The contractor shall prepare Software Test Descriptions (STDs) IAW

DI-IPSC-81439 (CDRL A040). The STDs shall document software test configuration, test set configuration, and software test cases for integration and regression testing. Any hardware or software integration facility used to verify contract requirements shall be described in and comply with the approved System/Software Integration Laboratory (SIL) Development &

Management Plan to be delivered by the contractor IAW DI-SESS-81770 (CDRL A041).

3.2.3.2.1 Software Development Plan (SDP)

As required by individual TOs, the contractor shall define a model based software development approach appropriate for the software effort to be performed IAW each TO. This approach shall be documented in a Government approved Software Development Plan IAW DI-IPSC-

81427 (CDRL A042).

The SDP shall define the contractor’s proposed life cycle model and the processes used as a part of that model. In this context, the term "life cycle model" shall be as defined in

IEEE/EIA 12207-2008, Standard for Information Technology. The SDP shall describe the overall life cycle and shall include primary, supporting, and organizational processes based on the work content of the TO. The SDP shall define the processes, the activities to be performed as a part of the processes, the tasks that support the activities, and the techniques and tools to be used to perform the tasks. The contractor shall ensure that full access to any deficiency reporting database is provided to the Government and shall be documented as part of the SDP.

As required by the individual TOs, the contractor shall include in the SDP a software metrics collection methodology, including a description of planned approach for software measurement and rationale for the metrics selection. The contractor shall determine how the metrics shall be collected, recommend when they shall be reported, and document them in the SDP. The SDP shall provide an estimated Source Lines of Code (SLOC) that is composed of new, modified, and reuse for the planned CSCIs.

The contractor’s SDP shall define, develop, and implement the following minimum set of core metrics specific to their program:

Software Size/Stability

Software organization including: manpower requirements (including staffing profile metrics, skills and certification required, training plan), training metrics (actual training

vs. required by plan, and required experience), and staff turnover metrics.

Software cost/schedule against an approved baseline, including cost and schedule variances and cost and schedule performance indices. Provide the basis for software cost estimation, (e.g. historical productivity, and parametrics).

Percentage of total system functionality to be provided by software, percentage of total system functionality to be provided by software estimate, and justification of the percentage of total software that shall be new development vs. Commercial Off-the-Shelf

(COTS)/Government Off the Shelf (GOTS)/Non Developmental Item (NDI)/OSS baseline requirements (including expected growth and trend metrics for software stability, and the use of metrics for forecasting)

Metrics for software quality, including defect density metrics and trends (e.g. defects per

SLOC, defects per unit, defects per interface).

As required by the individual TO, the contractor shall include in the SDP an automated unit test plan and process that exercises at a minimum the open and public interfaces, data exchange requirements, functional requirements and provides measured code coverage for the software being developed. The contractor shall run automated unit tests as part of every build of software. Software subject to automated unit testing shall not be checked into a source control system without passing the relevant automated unit tests. The contractor shall maintain automated unit testing source code under configuration management. Delivery shall include any related dependencies including build scripts, mock objects, stubs and Runtime Callable Wrappers used in building and executing the automated unit tests.

3.2.3.2.2 Open Source Software (OSS) Products

As required by individual TOs, the contractor shall compile and deliver a list of Open Source

Software (OSS) products that are planned for use in the software delivery and submit to the

Government for approval IAW DI-MISC-80711 (Scientific and Technical Reports-OSS

Products - CDRL A043). The list shall document the Identification of OSS Use and

Modifications that include the following:

OSS Title and Version number

License and Version number

Name of Contractor Asserting Restrictions

Possible Modification of OSS by contractor

If modified, was OSS modified by incorporation into a third party’s software.

If modified, was the OSS modified IAW the applicable DISA Application Security

Technical Implementation Guides (STIGs) (use of the OSS in the list shall be registered in the DoD Application & Management Database System (DADMS) and have an approved disposition).

When the contractor uses OSS in the performance of a Government contract, the contractor shall ensure that such use does not: (i) create, or intend to create, any

Government distribution obligations with respect to the computer software deliverables;

or (ii) grant, or intend to grant, to any third party any rights to or immunities under

Government intellectual property or Government data rights to the Government computer software deliverables.

When the contractor uses OSS in the performance of a Government contract, the contractor shall ensure that such use does not create or introduce system vulnerabilities into the System that would affect the System's accreditation, confidentiality, integrity, availability, authentication, or non-repudiation.

3.2.3.2.3 Capability Maturity Model Integration (CMMI)

At a minimum, the contractor’s processes shall comply with the CMMI Institute Software

Capability Maturity Model Integration (CMMI-DEV) Level 3 certification or equivalent. The

CMMI-DEV Level 3 certification or equivalent must be maintained for the duration of the contract. The contractor shall flow down the CMMI-DEV Level 3 requirement to subcontractors, as well as other divisions or groups of the contractor’s company performing independent software development or integration.

3.2.3.2.4 Software Releases

As required by individual TOs, the contractor shall deliver software releases to include associated checklists IAW DI-IPSC-81442 (CDRL A044), Software Version Description

(SVD). SVDs shall include:

Identification of all Computer Software Product End Items (CSPEIs)

Installation procedures

Release notes

Identification of any issues that impact use or performance with other components or workarounds

For releases that address defects found in a previous release, the SVD shall provide a cross-reference of contractor defect tracking identifier to Government tracking identifier

The above deliverable shall also include a full identification of any firmware devices, including as applicable, identification number(s), title(s), abbreviation(s), version number(s), release number(s), manufacturer's name and model number for each firmware device.

With each release, as required by the TO, the contractor shall update all documentation to reflect the executable delivered product to include:

Technical Report-Study/Services - Deficiency Report Data IAW DI-MISC-80508

(CDRL A045)

Software Requirements Specification (SRS) IAW DI-IPSC-81433 (CDRL A046)

Interface Design Description (IDD) IAW DI-IPSC-81436 (CDRL A047)

Interface Requirements Specification (IRS) IAW DI-IPSC-81434 (CDRL A048)

Software Design Description (SDD) IAW DI-IPSC-81435 (CDRL A049)

As required by the individual TO, the contractor shall provide to the Government a Software

Product Specification (SPS), IAW DI-IPSC-81441 (CDRL A050).

3.2.3.2.5 User Interface Manual

As required by the individual TOs, the contractor shall generate a Software User Manual IAW

DI-IPSC-81443 (CDRL A051), to document how the software interacts with its external and human interfaces.

3.2.3.2.6 Software Transition Plan

As required by the individual TOs, the contractor shall generate a Software Transition Plan, IAW DI-IPSC-81429 (CDRL A052), to identify the hardware, software, and other resources needed for life cycle support of deliverable software and to describe the plans for transitioning deliverable items.

3.2.3.2.7 Acquire Software Licenses

As required by applicable TO, the contractor shall acquire software licenses for products such as operating systems, middleware, applications/services, COTS, and any associated data (e.g.

maps) for software not available through U.S. Army Computer Hardware Enterprise Software and Solutions (CHESS). The contractor shall only acquire software licenses if provided a statement of non-availability from CHESS.

3.2.3.3 Architecture

The contractor shall develop a DOD Architecture Framework

(http://dodcio.defense.gov/Portals/0/Documents/DODAF/DoDAF_v2-02_web.pdf) as required by TOs calling for said Architecture. The contractor shall provide architecture framework product documentation that describes characteristics pertinent to the purpose of the architecture and shall be generated and delivered to the Government IAW DI-MGMT-81644 (CDRL A053), or portions thereof, as specified in the individual TOs.

http://dodcio.defense.gov/Portals/0/Documents/DODAF/DoDAF_v2-02_web.pdf

3.2.4 Quality System/Product Assurance

As directed by the Government, the contractor shall submit a Quality Program Plan (QPP) IAW

DI-QCIC-81722 (CDRL A054) that satisfies the requirements of AS 9100.

The QPP shall address all processes and dimensions or measurements that affect Critical Safety

Items (CSI), critical characteristics/processes, and Critical Reliability Components. The objective of the plan shall be to define and document what, where, and how to procure, fabricate, assemble, inspect, test and deliver only those units and other end products that conform to quality standards.

The contractor shall implement, or if already in place maintain, a quality system IAW AS 9100 or equivalent system as agreed between the contractor and the Government.

3.2.4.1 Product Acceptance System

The contractor shall provide the Government access to all new or modified end item acceptance test procedures (ATPs) generated by an individual TO, including those from lower tier subcontractors and suppliers (in the absence of a Prime Contractor ATP for the end item).

An end item is defined as the final combination of end products, component parts, and materials that is ready for its intended use and is used by the Soldier (e.g., Universal Ground Control

Station and Electronic Fuel Transfer Pump). The ATPs shall be submitted by the contractor for

Government approval IAW DI-NDTI-80603 (CDRL A055). If the contractor does not have access to an end item ATP from a lower tier subcontractor or supplier, the contractor shall generate an ATP and submit for Government approval. ATPs and equipment, including Special

Inspection Equipment (SIE) and Special Test Equipment (STE), shall be validated by the contractor prior to use for delivery…