Attachment_5.pdf

PR: FD2060- 19 -31706 SOW REVISION: 1

AIR FORCE LIFE CYCLE MANAGEMENT CENTER

ROBINS AIR FORCE BASE, GEORGIA 31098-1670

STATEMENT OF WORK (SOW)

FOR

SPECIAL OPERATIONS FORCES/PERSONNEL RECOVERY (SOF/PR)

& ROTARY DIVISION

MULTIPLE AWARD CONTRACT FOR MODIFICATIONS (MACM)

FD2060-19-31706

PR Number

January 2019

Date

Prepared by:

AFLCMC/WIU

235 Byron Street, Suite 19A

Robins AFB, GA 31098-1670

DISTRIBUTION STATEMENT C: Distribution authorized to U.S. Government agencies and their contractors (Administrative or Operational Use; 15-07-01). Other requests for this document shall be referred to AFLCMC/WIU, Robins AFB, GA 31098-1670.

PR: FD2060- 19 -31706 SOW REVISION: 2

TABLE OF CONTENTS

1.0 Description of Supplies/Services

1.1 Objective(s)

1.1.1 Support:

1.1.2 Quality Assurance Surveillance Plan (QASP)

1.2 Benefit to United States Air Force (USAF)

2.0 Government Property and Services

2.1 Government Property

2.2 Government Property to be Provided

2.3 Government Furnished Information (GFI)

2.4 Reporting of Government Property

2.5 Loss of Government Property

2.6 Return/Retention of Government Property

2.7 Government Systems

3.0 Technical Requirements

3.1 Period and Place of Performance

3.1.1 Contract/Order Period of Performance

3.1.2 Place of Performance

3.2 Item Unique Identification (IUID)

3.3 Kit Packaging, Handling, Shipping, and Transportation

3.3.1 Packaging and Handling

3.3.2 Shipping/Transportation

3.4 Counterfeit Electronic Parts

3.5 Government-Industry Data Exchange Program (GIDEP)

3.6 Travel

3.7 Diminishing Manufacturing Sources/Material Shortages (DMS/MS)

3.8 Cybersecurity Implementation

3.8.1 Cybersecurity Workforce

3.9 Engineering

3.9.1 Engineering Data

3.9.1.1 Restrictions on use of Propriety Material

PR: FD2060- 19 -31706 SOW REVISION: 3

3.9.2 System Integration

3.9.3 Proof of Concept Fabrication

3.9.4 Airworthiness

3.9.5 Validation and Verification

3.9.6 Trial Installation (TI) Kit

3.9.7 Kit Proof (KP)/Production Kits

3.9.8 Production Installation

3.9.9 Test Procedures

3.9.9.1 Ground and Flight Testing

3.9.9.2 System and Component Testing

3.9.10 Software

3.9.10.1 Software Requirements and Feasibility Analysis

3.9.10.2 Software Process

3.9.10.3 Software Design

3.9.10.4 Software Implementation

3.9.10.5 Software Test and Evaluation

3.9.10.6 Software Validation

3.9.10.7 Software Verification

3.9.10.8 Software Documentation

3.9.10.9 Software Configuration Management

3.9.10.10 Software Ownership and Rights

3.9.10.11 Development of New Software

3.9.10.12 Modification of Existing Software

3.9.11 Systems Engineering

3.9.12 Human Factors Engineering

3.10 Technology Insertion and Systems Integration

3.11 Systems Installation and Integration

3.12 Standard Items

3.13 Producibility

3.14 Source Qualification

3.15 Laboratory Services

3.16 Certifications

3.17 Product Data Management

3.18 Configuration Management (MIL-STD-973)

3.19 Configuration Data Management

3.20 Contractor Requirements

3.21 Program Management

3.22 Subcontractor Management

PR: FD2060- 19 -31706 SOW REVISION: 4

3.23 Multi-functional Team (MFT)

3.24 Contractor Furnished Materials and Equipment

3.25 Facilities Requirement

3.26 Management Meetings and Reviews

3.26.1 Post Contract Award Conferences

3.26.2 Technical Interchange Meetings (TIM)

3.26.3 Design Reviews/Audits

3.26.4 Performance Reviews

3.26.5 Provisioning

3.26.6 Engineering Data Guidance Conference

3.26.7 In-Process Review (IPR) of the TDP

3.27 Delivery Order Requirements

3.27.1 Conflicting Requirements

3.27.2 Administration

3.28 Delivery Order Deliverables

3.28.1 Data Requirements

3.28.2 Funds Status Report

3.28.3 Integrated Master Schedule (IMS)

3.29 Risk Management

3.30 Field Representation

3.30.1 Interim Contract Support/Contractor Logistics Support (ICS/CLS)

3.31 Publications

3.32 Quality Control Provisions

3.33 Program Protection Plan (PPP)

3.34 Non-Development Items (NDIs)

3.35 Commercial Processes and Technologies

3.36 Commercial Asset Visibility-Air Force (CAV-AF)

3.37 Over and Above (O&A)

4.0 General Information

4.1 Continuation of Mission-Essential Services During a Crisis

4.2 Security Requirements

PR: FD2060- 19 -31706 SOW REVISION: 5

4.2.1 Security Regulations

4.2.2 Operations Security (OPSEC)

4.2.3 Communications Security (COMSEC)

4.2.4 Security Clearances

4.2.5 Security Incidents and Violations

4.2.6 Security of Contractor System(s)

4.2.7 Release and Removal of Documentation

4.2.8 Access to Government Facility or Military Installation

4.2.9 Prohibitions against Unauthorized Disclosures

4.3 Environmental Management System (EMS)

4.3.1 Safety and Environmental

4.3.2 System Safety and Health Hazards

4.3.3 Hazardous Materials

4.4 Affirmative Procurement Programs (APP)

4.4.1 Contractor’s Purchasing Systems

4.5 Safety Requirements

4.5.1 Contractor Compliance

4.5.2 Mishap Notification/Investigation

4.5.3 Safety and Health Plan

4.6 Inspection of Services

4.7 Trafficking in Persons

4.8 Invoicing/Payment and Receipt/Acceptance

4.9 Earned Value Management (EVM)

5.0 Appendices

5.1 Appendix A: References

5.2 Appendix B: Acronyms

5.3 Appendix C: Sample Contract Data Requirements List (CDRL)

5.4 Appendix D: SOF/PR and Rotary Systems Engineering Plan (SEP)

5.5 Appendix E: SOF/PR and Rotary Technical Manual Contract Requirements (TMCR) . 39

PR: FD2060- 19 -31706 SOW REVISION: 6

1.0 Description of Supplies/Services

1.1 Objective(s): The purpose of this document is to provide modification and sustainment support for all Special Operations Forces/Personnel Recovery (SOF/PR) and Rotary Division managed C-130, H-1, and H-60 aircraft, to include integrated weapon systems, subsystems, and associated support equipment. Specific requirements will be determined for each delivery order (DO). These requirements may include, but are not limited to, non-recurring engineering, integration, trial installations, kit proof installations, aircraft technical data packages, technical orders, provisioning, test procedures, development of airworthiness documentation, cybersecurity documentation and installation of aircraft modification kits. The DO may also contain Interim

Contractor Support (ICS), Contractor Logistics Support, Manufacturing, and full-rate kit production. This effort will not include Advisory and Assistance Services (A&AS) support.

Modifications are not inherently services, but may contain services CLINs exceeding the

Simplified Acquisition Threshold (SAT). In accordance with AFI 63-138, para. 1.2.1.6, “…embedded services are those services with an aggregate Contract Line Item Number

(CLIN) value greater than or equal to the SAT placed on a supply, FFRDC, weapons systems/Major Automated Information Systems (MAIS) contract or any contract that is otherwise exempt but contains services with a separately priced services CLIN.”

Therefore, orders anticipating the inclusion of services CLINs in excess of the SAT shall include a Services Summary and QASP.

1.1.1 Support: The Contractor shall provide support to the SOF/PR and Rotary

Division Program Office, in the following categories: (1) Modification; (2)

Technical Support; (3) Production; (4) Testing; (5) Logistics; (6) Sustainment; and

(7) Travel in execution of Delivery Orders (DO) issued.

1.1.2 Quality Assurance Surveillance Plan (QASP): No QASP will be required for the basic contract. A QASP will be required for each DOs that include stand-alone services CLINs in excess of the simplified acquisition threshold (SAT).

1.2 Benefit to United States Air Force (USAF): This effort will benefit the Air Force by providing timely support to deliver improved capability to the SOF/PR and Rotary

Division customers and warfighters. The awardee must abide by the FAR 52.219-14

Limitations on Subcontracting.

2.0 Government Property and Services

2.1 Government Property: Government Furnished Material (GFM), Government

Furnished Equipment (GFE), and Government Furnished Information (GFI) are authorized. GFM, GFE and GFI will be identified in each specific DO, as needed.

During the period of performance, the Government may provide contractor access to

Government equipment for the accomplishment of required tasks. Access will be provided on an as-available basis and unless otherwise specified, all equipment will

PR: FD2060- 19 -31706 SOW REVISION: 7

remain at its current location. Equipment may include aircraft and/or components, maintenance test equipment, jigs, fixtures, etc. If equipment is available to be transported to and used at the contractor’s facility, then it must be returned to its original location as soon as it is no longer needed at the contractor’s facility. All equipment, regardless of location, remains the property of the US Government and must be returned to the Government upon completion of the task requiring the equipment or at the completion of the contract unless a follow-on effort is coordinated, whichever comes first.

2.2 Government Property to be Provided: GFM and GFE may be provided to support

DOs on an “as available” basis. In such cases, the GFM and GFE clauses of the contract will be supplemented by specific delivery and disposition instructions provided in the corresponding DOs. The designated Government Program Manager (PM) or

Contracting Officer Representative (COR) for the DO will provide the Contractor access to all GFI, facilities, material, equipment, services, etc., as required to accomplish DOs.

2.3 Government Furnished Information (GFI): To the maximum practicable extent, the Government will provide available information and data on an “as available/required/authorized” basis to support DO performance in digital format via

Integrated Digital Environment (IDE). Each DO will identify the GFI to be provided.

The Government Program Manager will provide disposition instructions for the GFI upon completion of the contract. The Contractor shall provide the necessary documentation to gain access to sensitive or proprietary data.

2.4 Reporting of Government Property: The Contractor shall create and maintain records of all Government property accountable to the contract, including Government-

Furnished Property (GFP) and Contractor-Acquired Property (CAP) in accordance with the Federal Acquisition Regulation (FAR) and applicable supplements and shall be in compliance with all applicable guidance and clauses listed in the contract. GFP records shall be updated on a monthly basis and submitted as an attachment to the Monthly

Status Report (MSR).

2.5 Loss of Government Property: Reporting Loss of Government Property, the

Contractor shall use the Defense Contract Management Agency (DCMA) eTools software application (http://www.dcma.mil/aboutetools.cfm) to report loss of

Government property in accordance with the FAR and applicable supplements and shall be in compliance with all applicable guidance and clauses listed in the contract. The reporting requirement does not change any liability provisions or other reporting requirements that may exist under the contract/order.

2.6 Return/Retention of Government Property: All property provided by the

Government remains the property of the Government and shall be returned to the

Government upon completion of the contract/order unless the Procuring Contracting

Officer (PCO) directs the Contractor to retain the property for continued use under a successor contract. Retention of the property by the Contractor will require modification of both losing and gaining contracts in accordance with the FAR and http://www.dcma.mil/aboutetools.cfm

PR: FD2060- 19 -31706 SOW REVISION: 8

applicable supplements and shall be in compliance with all applicable guidance and clauses listed in the contract. All Government property shall be returned to the

Government in the condition provided unless approved in advance by the PCO.

2.7 Government Systems: The Government will provide contractor personnel access to system(s) necessary to perform tasks under the contract DO. The Contractor shall ensure contractor personnel who require access to a U.S. Government Automated

Information System (AIS) have a Department of Defense National Agency Check Plus

Written Inquiries (DNACI) conducted in accordance with Department of Defense

Instruction (DoDI) 5200.2-R, Personnel Security Program. The Government will provide system access subject to approval of the DD Form 2875, System Authorization

Access Request (SAAR). Upon completion/termination of the contract/order or transfer/termination of contractor personnel, the system account will be closed.

3.0 Technical Requirements:

3.1 Period and Place of Performance:

3.1.1 Contract/Order Period of Performance: The will consist of seven (7) years and include a three (3) year basic period with two (2) option periods consisting of two (2) years each. The PoP will be determined on each order, however no order may exceed seven (7) years. Orders may be placed from date of award through 24 months after exercise of the last option. The PoP will be determined on each order. Orders may be placed from ___ to ___. No order may exceed 7 years PoP.

3.1.2 Place of Performance: These services will be performed at various locations both CONUS and OCONUS depending on the specific DO and Government requirements.

3.2 Item Unique Identification (IUID): The Contractor shall mark items in accordance with DFARS 211.274-2, Policy for Unique Item Identification, Defense Federal

Acquisition Regulation Supplement (DFARS) 252-211.7003, Item Identification and

Valuation/ Definitions, MIL-STD-130N, Department of Defense Standard

Practice/Identification Marking of U.S. Military Property, and applicable contract clauses.

3.3 Kit Packaging, Handling, Shipping, and Transportation: Contractor shall be responsible for the kit packaging, handling, shipping, and transportation IAW the

Following paragraphs.

3.3.1 Packaging and Handling: The Contractor shall package and mark end items and components in accordance with each DO’s Air Force Materiel Command

(AFMC) Form 158 and IAW MIL-STD-129R, Department of Defense Standard

Practice/Military Marking for Shipment, MIL-STD-130N, Department of Defense

Standard Practice/Identification Marking of U.S. Military Property, and MIL-

STD-2073-1E, Standard Practice for Military Packaging. The Contractor shall

PR: FD2060- 19 -31706 SOW REVISION: 9

ensure classified material is packaged, marked and shipped in accordance with DoD

5220.22-M, National Industrial Security Program Operating Manual (NISPOM).

3.3.2 Shipping/Transportation: Contractor shall ship kits by traceable means to location(s) provided by the Governments Production Management Office.

3.4 Counterfeit Electronic Parts: The Contractor shall establish and maintain a counterfeit electronic part detection and avoidance system to mitigate the risk of counterfeit electronics parts being installed in end items or otherwise entering the

USAF/DoD inventory. The system shall incorporate processes/procedures to address the requirements listed in accordance with the FAR (e.g., DFAR 231.205-71;

252.242.7008) and applicable supplements and shall be in compliance with all applicable guidance and clauses listed in the contract. The Government's review of the

Contractor’s system will be accomplished as part of the evaluation of the Contractor’s purchasing system in accordance with the FAR (DFAR 252.244-7001) and applicable supplements and shall be in compliance with all applicable guidance and clauses listed in the contract.

3.5 Government-Industry Data Exchange Program (GIDEP): The Contractor shall participate in GIDEP in accordance with Air Force Joint Instruction (AFJI) 63-108, Government-Industry Data Exchange Program (GIDEP), and S0300-BT-PRO-010, Operations Manual for GIDEP. The Contractor shall review each Alert/Safe-Alert report received from GIDEP to determine if the item or process for which the Alert/Safe

Alert report is issued is applicable to the contract/order and take appropriate action.

Upon the determination that an Alert/Safe-Alert report is applicable, the Contractor shall inform the impacted organizations and subcontractors and record of the status and disposition of all Alert/Safe-Alert reports

3.6 Travel: The Contractor may be required to travel to Government installations

(CONUS and OCONUS) or to other contractor facilities to provide support. The number of trips, types and number of personnel shall be limited to the minimum required to accomplish work requirements. The Contractor shall be responsible for arranging all contractor personnel travel during the program effort in accordance with the Department of Defense (DoD) Joint Travel Regulations (JTR). The Contractor shall use the lowest cost mode of transportation commensurate with mission requirements and good traffic management principles. All travel requests shall include the number of personnel, destination, purpose, number of days, and the cost estimate of required travel.

All travel must be approved by the PCO in advance in accordance with the specific DO.

All trips shall be documented in trip reports and submitted to the PM within timelines specified in the specific DO. The Contractor shall provide a list of all upcoming travel requirements in the MSR.

3.7 Diminishing Manufacturing Sources/Material Shortages (DMS/MS): The

Contractor shall provide DMS/MS information related to each modification as required by each DO. The Contractor shall assess and predict long range part availability from original vendors and aftermarket sources. The Contractor may obtain written letters of

PR: FD2060- 19 -31706 SOW REVISION: 10

intent from part vendors and materials sources documenting current part support plans.

The Contractor shall identify and perform a technical assessment of potential sources of supply for suitable substitute parts and materials and make recommendations to mitigate program risk from DMS/MS causes and prevent DMS/MS impacting overall system availability.

3.8 Cybersecurity Implementation: The Contractor shall integrate DoDI 8510, Risk

Management Framework (RMF) for DoD Information Technology (IT), procedures into all architecture, design, development, integration, and test processes and products. The

Contractor shall implement the applicable cybersecurity controls through the systems engineering technical processes: stakeholder requirements definition; requirements analysis; architecture design; implementation; integration; risk management; and verification and validation in accordance with the specific DO. The Contractor shall develop/design cybersecurity strategies and analyze existing security strategies, help define strategic security posture, ATO roadmaps, and implementation plans. The

Contractor shall assess the current systems integration against existing sytem security strategies and conduct analysis of alternatives in response to the Governments requirements.

3.8.1 Cybersecurity Workforce: The Contractor shall implement DoDI 8500.01, Cybersecurity, and DoD 8570.1-M, Information Assurance Workforce

Improvement Program, for requirements and processes necessary for information management and cybersecurity including those applicable to contractor employees and employee training. The Contractor shall provide technical, managerial, and administrative direction for problem definition, analysis, requirements development, and implementation for the sytems the Contractor is integrating. The

Contractor shall make recommendations and advise the Government on system improvements, optimization or maintenance efforts for the systems installed.

3.9 Engineering: The Contractor shall apply the systems engineering processes for

SOF/PR and Rotary aircraft systems in accordance with the SOF/PR and Rotary

Division (AFLCMC/WIU) Systems Engineering Plan (SEP) identified in SOW

Appendix D. The Contractor shall provide engineering as specified in the specific DO to support systems and subsystems, their integration into the aircraft, associated interfaces, trainers, and support equipment. These services may include, but are not limited to, Non-Recurring Engineering (NRE), Technical Data Packages (TDP), validation and verification, prototyping, aircraft surveys, troubleshooting activity, and testing to support systems and subsystems. Depending upon the specific DO requirement, the Contractor may be required to conduct various engineering analyses in support of a modification. These analyses may include, but are not limited to, determining the effects on aircraft weight and balance, electrical power distribution, aircraft structural integrity, and radio frequency spectrum management. The Contractor shall perform an aircraft survey identifying the proposed system hardware location, wire/cable routing, aircraft power sources, etc.

3.9.1 Engineering Data: The Contractor shall develop, produce, maintain and deliver a TDP accurately depicting the final product. The TDP shall represent the

PR: FD2060- 19 -31706 SOW REVISION: 11

approved, tested, and accepted configuration of the defined delivered item(s).

TDP data includes, but is not limited to, Computer Aided Design (CAD) data, CAD models, model based definition data sets, Gerber data and Master Bill of

Materials (BOM). The TDP shall provide the necessary design, engineering, manufacturing, testing, and quality assurance requirements information necessary to enable the procurement or manufacture of an interchangeable item that duplicates the physical and performance characteristics of the original product without additional design and engineering effort or recourse to the original design activity or any third party. Drawings shall be compatible with Joint Engineering

Data Management Information Control System (JEDMICS) and shall follow the specified requirements of that system. All engineering product definition data created as a result of this contract shall be considered part of the TDP and shall become property of the Government unless specifically outlined within the DO.

3.9.1.1 Restrictions on use of Propriety Material: The Government will have unlimited or unrestricted rights to all technical data and drawings developed exclusively with Government funding for this contract. The

Government will have Government Purpose License Rights if any proprietary hardware, drawings or data developed at private expense is used.

The contractor shall receive written Government approval prior to use of any proprietary hardware, drawings or data. An index of all drawings and data developed under the contract shall be maintained and shall be made available to the procuring agency upon request.

3.9.2 System Integration: Upon award of a DO requirement to perform system integration, the Contractor shall establish the baseline system design; allocate system requirements; establish measures of effectiveness for ranking alternative designs (if readily available); and integrate the preliminary design among the design disciplines. The Contractor shall obtain Interface Control Documentation

(ICD) from source suppliers for inclusion in configuration Control Documentation for system integration technical data packages. The Contractor shall develop and provide training and training material (operational and maintenance) to support the system being integrated as outlined within the DO. The training materials shall be delivered to the Government in hard copy and digital formats for the appropriate aviation Air Force Specialty Codes (AFSC). The Contractor shall also be required to support the definition, analysis, and resolutions of special integration issues associated with SOF/PR and Rotary aircraft for existing systems and subsystems and provide support to resolve special integration problems and deficiencies associated with recently installed systems and subsystems which have not yet reached a maturity level to provide a reliable discrepancy history. This support may entail analytical engineering, software engineering, system integration engineering, training (operational and maintenance), development of engineering design packages, validation and verification, and testing.

3.9.3 Proof of Concept Fabrication: The fabrication of “Proof of Concept” items or kits, when required, shall normally follow the completion of engineering efforts.

The Contractor shall fabricate or procure as many items or kits necessary to satisfy

PR: FD2060- 19 -31706 SOW REVISION: 12

the requirements of the contract. Proof of concept items or kits shall meet the requirements necessary to provide adequate performance for parameters to be measured. Proof of concept items may be utilized by the Contractor in conjunction with the specific work requirements of tasks. These items shall be furnished to and become the property of the Government unless specifically dictated under the DO.

3.9.4 Airworthiness: The Contractor shall utilize an approach to airworthiness certification of the final aircraft configuration that complies with the intent of

AFPD 62-6, USAF Airworthiness Certification. The Contractor shall develop

Modified Airworthiness Certification Criteria (MACC) in accordance with (IAW)

MIL-HDBK-516C, Airworthiness Certification Criteria, and the Government provided template to identify the specific certification criteria that apply to the modified aircraft. The Contractor shall deliver the MACC, along with all referenced documentation in order to support USAF certification of the Aircraft in accordance with the IMS. The Government will approve or reject the draft documents in accordance with the criteria in the specific DO. A copy of the report shall be submitted as an attachment to the Final Report.

3.9.5 Validation and Verification: Upon award of a DO requirement, the

Contractor shall provide engineering and technical support in the validation and verification of all avionics, hardware, and software systems and subsystems installations and technical manuals associated with the specific DO. The

Contractor shall review generated documents, drawings, and engineering/technical data and test reports to resolve system and subsystem integration deficiencies and provide written recommendations for the suitability of the submitted data to support the weapon systems. This support shall include development of any

Engineering Change Orders (ECO) required to update existing drawings as specified in the DO.

3.9.6 Trial Installation (TI) Kit: When required by the DO, the Contractor shall be responsible for the procurement, manufacture, inspection, and installation of the trial installation kit. The Contractor shall provide on-site engineering and technical support for the installation and testing of the TI kit. The Contractor shall be responsible to provide the installation team, kits, tools and equipment, and

AFTO 781/95 forms documentation, as applicable, in accordance with TO 00-20-

1, Aerospace Equipment Maintenance Inspection, Documentation, Policies, and

Procedures, and AFI 21-101, Aircraft and Equipment Maintenance Management, for this effort.

3.9.7 Kit Proof (KP)/Production Kits: When required by the DO, the Contractor shall be responsible for the procurement, manufacture, inspection, and installation of the kit proof kit and all production kits. This includes retrofitting the trial install kit to the production configuration upon completion of the kit proof. The first production kit will be used for the kit proof and the Contractor shall support the installation of the kit proof kit. The Contractor shall be responsible for completion of aircraft AFTO 781 forms documentation in accordance with TO 00-20-1, PR: FD2060- 19 -31706 SOW REVISION: 13

Aerospace Equipment Maintenance Inspection, Documentation, Policies, and

Procedures, and AFI 21-101, Aircraft and Equipment Maintenance Management, for the kit proof and subsequent production kits as defined in this SOW.

3.9.8 Production Installation: Upon award of a DO requirement, the Contractor shall manufacture and/or procure the items necessary to install the items that have undergone trial install and kit proof install onto SOF/PR and Rotary aircraft. In addition, the Contractor shall support the installation of the production kits onto the aircraft as required by the specific DO.

3.9.9 Test Procedures: The Contractor shall provide aircraft integration support and check-out during current and continuing /developmental and operational test activities as required. The Contractor shall provide test plans, test procedures, and appropriate test reports in support of system testing in accordance with the specific

DO.

3.9.9.1 Ground and Flight Testing: The Contractor shall conduct testing, or shall support Government test personnel, as specified by the DOs. The

Contractor shall ensure all hardware, software, test equipment, instrumentation, supplies, facilities, and personnel are available and in place to conduct or support each scheduled test as specified within the DOs. The

Contractor shall provide the necessary test planning documentation, coordination, accomplish the necessary instrumentation, and provide qualified engineering supervision and staffing.

3.9.9.2 System and Component Testing: Upon award of a DO

requirement for system or component testing, the Contractor shall provide the necessary test planning documentation, coordination, instrumentation, and the qualified engineering supervision and staffing documented in a Test and Evaluation Master Plan (TEMP) IAW Memorandum for Users of the

Director, Operational Test & Evaluation (DOT&E) TEMP Guidebook. The

Contractor shall perform all testing required for full qualification (e.g., Electromagnetic Interference (EMI); Electromagnetic Compatibility (EMC)

(MIL-STD 460G); Environmental (MIL-STD-810G)). The Contractor shall perform integration testing to verify all changes comply with requirements at the system and subsystem level.

3.9.10 Software: The Contractor shall design, develop, code, integrate, test, document, and deliver new or modified system and subsystem software in accordance with each DO requirement. The Contractor shall apply effective software engineering processes to all software requirements. Software certification shall be IAW ISO-STD-12207, Information Technology-Software

Lifecycle Processes, or equivalent processes approved by other DoD services or agencies may be specified within the DOs.

3.9.10.1 Software Requirements and Feasibility Analysis: The

Contractor shall analyze operational requirements and/or deficiencies and

PR: FD2060- 19 -31706 SOW REVISION: 14

determine the feasibility of developing new software or modifying existing software to resolve them.

3.9.10.2 Software Process: A repeatable software development process, IAW ISO-STD-12207, Information Technology-Software Lifecycle

Processes, or equivalent processes approved by other DoD services or agencies shall be utilized in combination with an integrated systems analysis approach with respect to all interfaces specified in the DO.

3.9.10.3 Software Design: The Contractor shall design new software or changes to existing software to fulfill operational requirements or correct operational deficiencies.

3.9.10.4 Software Implementation: The Contractor shall develop new software or modify existing software using the programming concepts specified in the DO.

3.9.10.5 Software Test and Evaluation: The Contractor shall test and evaluate the new or modified software in accordance with approved test plans/procedures and TEMP.

3.9.10.6 Software Validation: The Contractor shall validate the new or modified software provides the specified function(s), and does not impact other functional areas in the software.

3.9.10.7 Software Verification: The Contractor shall verify the new or modified software performs the functions within the limitations and criteria of the design specifications.

3.9.10.8 Software Documentation: Upon award of a DO related to development or modification, the Contractor shall create or update technical software documentation. The technical documentation shall include applicable requirements, design, and verification documentation as specified by the DO. The Contractor shall create or update additional documentation to include Automated Computer Product Identification Number (ACPIN) and other processes as specified in the DO.

3.9.10.9 Software Configuration Management: The Contractor shall be responsible for documenting and maintaining configuration control for any item affected by new or modified software. The Contractor shall update existing technical data (e.g., drawings) affected by the new or modified software. Configuration control is defined as any change to form, fit, and function of hardware or software. The Contractor shall conduct a physical configuration audit prior to final drawing review.

PR: FD2060- 19 -31706 SOW REVISION: 15

3.9.10.10 Software Ownership and Rights: The Government requires unlimited rights in any material first produced in the performance of this contract and subsequent delivery orders, in accordance with the FAR clause at 52.217-14. In addition, for any material first produced in the performance of this contract and subsequent delivery orders, the materials may be shared with other agencies or contractors during the period of performance, or after its termination. The Contractor shall seek unlimited rights to all non-commercial computer software and related documentation developed using both Government and private funds. The Contractor shall provide unlimited rights for all non-commercial computer software products and software documentation that are developed solely with Government funds. For any subcontractors or teaming partners, the Contractor shall ensure at proposal submission that the subcontractors and/or teaming partners are willing to provide the unlimited data rights required. Any inability to grant rights to the software will be discussed with the Government on a case-by-case basis.

This includes software residing within computer devices, microelectronic devices, microcircuits and firmware. The Contractor shall obtain and deliver to the Government commercial licenses for all commercial software products developed, purchased or provided under this effort after coordination with the Government. The Government contracting officer will have the right to direct negotiate with subcontractors for less than unlimited rights when unlimited rights are not available. The Contractor shall identify any special software, computer hardware and tools needed to view, edit and compile delivered software products. The Contractor shall furnish at least one copy of any unique software, computer hardware and tools not already available to the SOF/PR and Rotary Division.

3.9.10.11 Development of New Software: When a requirement is

established to develop new software, the Contractor shall accomplish all or part of the efforts in paragraph 3.9.10 to the degree specified in the DO.

3.9.10.12 Modification of Existing Software: When a requirement is established to modify existing software, the Contractor shall accomplish all or part of the efforts in paragraph 3.9.10 to the degree specified within the

DO.

3.9.10.13 Software Sustainment: The Contractor shall create or update a software sustainment and transition plan which documents the entire software process. Specifically, the plan shall include all necessary source code, tools, licenses, and applications required to successfully sustain the software. The plan shall include long term planning for obsolescence of software and tool sets. The plan shall conform to the process or documentation standard specified by the DO.

3.9.11 Systems Engineering: The Contractor shall apply an integrated systems engineering and Operational Safety, Suitability and Effectiveness (OSS&E)

PR: FD2060- 19 -31706 SOW REVISION: 16

approach to all DOs consistent with the SOF/PR and Rotary Systems Engineering

Plan (SEP) (Appendix D).

3.9.12 Human Factors Engineering: The Contractor shall apply human factors engineering design criteria, principles, practices, and standards to the design process to achieve ergonomics, effectiveness, simplicity, efficiency, reliability, and safety of system operation, training, and maintenance; as specified within the DOs.

3.10 Technology Insertion and Systems Integration: The Contractor shall integrate new technologies into current system architectures as specified within the DOs. The

Contractor shall apply a systems design approach to ensure mission objectives and system criteria requirements are fulfilled. Emphasis shall be on open systems architecture and the demonstration of clear and definable improvements in the performance, logistics supportability, reliability, and maintainability of the item. All efforts shall employ the latest technology in consonance with economic considerations.

If applicable, design concepts shall include provisions for continuous technological upgrade to maximize opportunities for product improvement available from emerging technological advances in the commercial marketplace. Commercial-Off-The-Shelf

(COTS) equipment and software meeting the requirements of the DOs shall be used whenever possible. If directed by the DOs, the Contractor shall evaluate technology applications and identify potential risks. Such analyses shall be conducted and documented as specified by the DOs. Where analysis is notfeasible, the Contractor shall apply proven engineering design concepts necessary to achieve required performance.

The Contractor shall develop and maintain a systems integration and insertion plan to assist in identifying opportunities for the integration of new equipment technologies into existing architectures, as specified by the DOs. As applicable, this plan shall describe the management of the integration and insertion process when moving from one hardware platform to another, updates of system software and the use of software developed by other sources.

3.11 Systems Installation and Integration: The Contractor shall install and integrate equipment or software into systems or modify existing systems as specified by the DOs.

As required, the Contractor shall fabricate or obtain integration hardware, installation kits, and acquire associated software. The Contractor shall identify all equipment and utilities required for installation at the installation site, including GFM/GFE. The

Contractor shall ensure the required equipment, utilities, and resources are available at the installation site.

3.12 Standard Items: All designs shall use COTS, standard parts, materials, and processes, whenever practical. The requirements for installation, operation, maintenance, removal, and repair shall be satisfied by the use of common hand tools.

Any deviations from this requirement must have advanced written approval from the contracting officer.

PR: FD2060- 19 -31706 SOW REVISION: 17

3.13 Producibility: The Contractor shall be required to establish a program that ensures all designs are producible and producibility enhancements are considered in the design process, consider long-term logistics support analysis concerns and life cycle cost impacts. The Contractor shall provide for the limited production of parts, components, systems, support equipment, test equipment, etc, as necessary to meet mission critical functions as determined by the Government and as specified by the DOs.

3.14 Source Qualification: The Contractor shall be required to assist in the qualification of sources as specified by the DOs.

3.15 Laboratory Services: As specified within the DOs, the Contractor shall be required to obtain independent laboratory services to analyze test and inspect materials, component parts, and sample specimens. These may include third party analysis, testing, validation, verification and inspection of metallurgical, chemical, or other samples. This may include Non-Destructive Inspection or destructive testing (e.g., T.O.

33B-1-2; ASTM-E1417; ASTM-E1444; MIL-STD-461G; MIL-STD-750; MIL-STD-

810G; MIL STD-2035A).

3.16 Certifications: The Contractor shall obtain commercial and/or military certifications/ authorizations as specified by the DOs.

3.17 Product Data Management: The Contractor shall review and/or develop and submit Product Data in accordance with the DOs. Product Data may define one or more configuration items, associated manufacturing processes, and associated test procedures.

Various types of Product Data may be required (e.g., engineering drawings, specifications, quality assurance requirements, and/or commercial item descriptions, complete design disclosure, form/fit/function requirements, performance specifications, Interface Control Data, market surveys).

3.18 Configuration Management (MIL-STD-973): The Contractor shall provide configuration management related to each DO. The Contractor shall develop and revise configuration management plans and procedures, perform configuration identification of items, and participate in configuration change management activities. The Contractor shall prepare and review configuration change management and document formal events and activities identified by the Government and perform configuration status accounting.

The Contractor shall assist in software version release management and archiving and participate in third-party and Government configuration verifications and audits.

3.19 Configuration Data Management: The Contractor shall provide configuration management support (ref: MIL-HDBK-61A(AE)) in accordance with the DOs, including but not limited to:

3.19.1 Collecting, reviewing, tracking and archiving of Configuration Control

Documents

3.19.2 Development of automated databases to track hierarchical components

PR: FD2060- 19 -31706 SOW REVISION: 18

3.19.3 Maintenance of Product Data

3.19.4 Support to Configuration Control Boards (CCBs)

3.19.5 Performance of Functional Configuration Audit (FCA) and Physical

Configuration Audit (PCA)

3.19.6 Evaluation of Configuration Management Single Process Initiative

(CMSPI) Concept Papers

3.20 Contractor Requirements: The Contractor shall provide the services specified herein in accordance with this SOW and the applicable DO. Unique requirements will be specified within the DOs.

3.21 Program Management: The Contractor shall designate a single program management point of contact. The Contractor shall develop management plans as necessary to ensure all elements of this effort are successfully executed within the program budgets and schedule. The Contractor shall also ensure complete financial accountability is maintained by contract line item and all Contract Data Requirements

List (CDRL) actions are delivered to the Government in accordance with the CDRL requirements. The Contractor shall notify the Government of any program issues that may impact the execution of this SOW. The Contractor shall conduct program meetings and reviews as required by this SOW and provide logistics/program management services to support all reviews; e.g., program audits, Program

Management Reviews (PMRs), Weapon System Review (WSR), In Process Reviews

(IPRs). When feasible, meetings should be combined. The Contractor and the

Government will mutually agree upon locations and dates of program meetings and reviews.

3.22 Subcontractor Management: The Contractor shall maintain a current

Subcontractor Management Plan. The Contractor may disseminate portions of DOs to subcontractors based upon areas of expertise. The Contractor may subcontract with other companies to establish a strong technical capability to meet diverse DO requirements. The Contractor shall be held fully responsible for all aspects of each DO performance and oversight, regardless of any arrangement between the contractor and its proposed subcontractors. This requirement shall apply at all tiers of subcontractor/vendor levels associated with the program.

3.22.1 Associated Contractor Agreement (ACA): The Contractor shall establish and maintain an ACA(s) with major subcontractors as required to flow down allocated and derived SOW requirements. The ACA(s) shall define the specific areas of responsibility for the contractor and its major subcontractors, ensuring the interfaces between the aircraft, systems, subsystems, and the mission kits identified within the SOWs are established and maintained.

PR: FD2060- 19 -31706 SOW REVISION: 19

Representatives, effort updates/status, schedules and completion dates shall be addressed and agreed to as part of the ACA. The final, signed ACAs shall be presented at the kickoff meeting for Government concurrence. The contractor shall notify the Government of any changes and modifications to the ACAs as soon as practicable but no later than five (5) working days after they occur.

(Reference: AFSPCFARS 5352.217-9500, and Informational Guide 5317.9000)

3.23 Multi-functional Team (MFT): The Contractor shall participate in Government

MFT to facilitate an Integrated Product and Process Development (IPPD) environment as specified within the DOs. The Contractor’s MFT members shall represent the required functions for the performance of applicable DO and possess the authority to implement MFT objectives and decisions.

3.24 Contractor Furnished Materials and Equipment: The Contractor shall acquire any additional hardware and software not provided by the Government as required to accomplish the DOs. Ownership will be established in accordance with terms and conditions specified within the DOs. The Contractor is required to maintain software integrity in accordance with the licensing agreement of the vendor. The

Contractor is responsible to assure the completeness and correctness of the data before performance and completion of the DOs. Required data types, formats, and transmission media will be specified within the DOs.

3.25 Facilities Requirement: Facilities may be Contractor or Government provided, depending upon the DO requirements. The facilities required shall include an enclosed hangar of sufficient size to accommodate the SOF/PR and Rotary Division aircraft being modified. This hangar shall be located near an airstrip capable of receiving and servicing SOF/PR and Rotary Division aircraft. Adequate storage facilities must exist for removed equipment prior to it being reinstalled, returned to the

Government, or disposed of. Aircraft ground handling equipment will be required to support C-130 variants, HH-60, UH-1N, and TH-1H aircraft. Support equipment required includes, but is not limited to, aircraft jacks, shoring material, aircraft power generator(s), overhead hoist or crane, maintenance stands, scaffolding, and ladders typically used for depot level aircraft maintenance. While the Government prefers on-site DCMA support, space must be provided to accommodate Government inspection teams (e.g., DCMA, acceptance inspection teams).

3.26 Management Meetings and Reviews: The Contractor shall be required to support various meetings as identified in the DOs. The Contractor shall maintain a schedule of events for all meetings (e.g., Configuration Control Boards (CCBs), Crew

Station Working Groups (CSWGs), Technical Interchange Meetings (TIMs), Technical Order, Flight Manual, and Maintenance Manual reviews, Provisioning reviews) and due dates for the submission of AIs with the Office of Primary

Responsibility (OPR) identified.

PR: FD2060- 19 -31706 SOW REVISION: 20

3.26.1 Post Contract Award Conferences: A post award conference will be required after award of a DO. The post-award orientation conference will be hosted at a mutually agreed upon location within 30 days after contract award.

All key participants (Government and Contractor) shall attend.

3.26.2 Technical Interchange Meetings (TIM): The Contractor shall participate in TIMs as required by Government Program Manager for the DOs.

The Government Program Manager will specify agenda and attendance requirements, with specific dates and locations, in accordance with the DO.

3.26.3 Design Reviews/Audits: The Contractor shall prepare for and participate in formally scheduled reviews/audits (e.g., Software Specification Review

(SSR), System Requirements Review (SRR), Preliminary Design Review (PDR), Critical Design Review (CDR), Functional Configuration Audit (FCA)/Physical

Configuration Audit (PCA), Test Readiness Review (TRR)), to be conducted in accordance with requirements of the DO.

3.26.4 Performance Reviews: The Contractor shall attend Contract

Performance Reviews as required. These meetings will focus on overall contract performance. Specific dates, locations, agenda and attendance requirements will be specified by the PCO at least 30 days prior to each meeting.

3.26.5 Provisioning: Contractor shall identify and recommend logical spare/repair parts sufficient to meet the system/equipment operation and supportability in accordance with the Air Force intital Provisioning Performance

Specification (IPPS). SAE GEIA-STD-0007 should be used as a guide. The format must be consistent with the existing Government D220 provisioning data system. The contractor shall conduct Integrated Process Reviews (IPR) at intervals outlined within each DO.

3.26.6 Engineering Data Guidance Conference: The Contractor shall support, and co-chair a guidance conference with AFLCMC/LZPEM for engineering data within 60 days after contract award. The conference shall be convened at a site and on a date agreed upon by the Government contracting officer and the

Contractor. The Contractor shall prepare an agenda and record the minutes of the guidance conference. The Contractor shall address, discuss, and provide status on the following:

3.26.6.1 Understanding of all CDRL requirements, applicable Data Item

Descriptions (DIDs), specifications and standards.

3.26.6.2 TDP review requirements and schedules.

3.26.6.3 TDP delivery requirements and schedules.

3.26.6.4 Contractor’s drafting practices/procedures/TDP drawing formats.

PR: FD2060- 19 -31706 SOW REVISION: 21

3.26.6.5 The Contractor’s quality assurance procedures relating to TDP documents, including quality control of subcontractor and vendor data.

3.26.6.6 The role of subcontractors and vendors who may deliver TDP documents under this contract.

3.26.6.7 The Contractor's configuration management system, including methods for releasing documents, approving documents, and incorporating changes into documents.

3.26.6.8 Digital TDP deliverables.

3.26.7 In-Process Review (IPR) of the TDP: The Contractor shall host, support, and co- chair an IPR of the engineering drawings and associated lists and other documentation to be…