PWS_LSC_13_May_16.docx

Performance-Based Work Statement for

Lifecycle Service Support Contract

PR Number

Date QAPC signs QASP

Table of Contents

1.0 Description of Services

1.1 Objective(s)

1.2 Benefit to United States Air Force (USAF)

2.0 Services Summary

3.0 Government Property and Services

3.1 Government Property

3.2 Government Property to be Provided

3.3 Reporting of Government Property

3.4 Loss of Government Property

3.5 Return/Retention of Government Property

4.0 Technical Requirements

4.1 Place of Performance

4.1.1 Contract/Order Period of Performance

4.2 Item Unique Identification (IUID)

4.3 Packaging

4.4 Counterfeit Electronic Parts

4.5 Government-Industry Data Exchange Program (GIDEP)

4.6 Travel

4.7 Categories of Work

4.7.1.4 Airworthiness

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

4.7.1.6 Cybersecurity Implementaton

4.7.1.7 Cybersecutity Workforce

4.7.2.5 Engineering Data

4.7.3 Testing

4.7.4 Software

4.7.4.3 Software Process

4.7.4.3.1 Software Requirements and Feasibility Analysis

4.7.4.3.2 Software Design

4.7.4.3.3 Software Implementation

4.7.4.3.4 Software Test and Evaluation

4.7.4.3.5 Software Validation

4.7.4.3.6 Software Verification

4.7.4.3.7 Software Documentation

4.7.4.3.8 Software Configuration Management

4.7.4.3.9 Software Ownership and Rights

4.7.5.2 Technology Insertion and Systems Integration

4.7.5.3 Systems Installation and Integration

4.7.5.4 Standard Items

4.7.5.5 Producibility

4.7.5.6 Source Qualification

4.7.5.7 Laboratory Services

4.7.5.8 Certifications

4.7.5.9 Product Data Management

4.7.5.10 Configuration Data Management

4.8 Contractor Requirements

4.8.1 Program Management

4.8.2 Subcontractor Management

4.8.3 Associate Contractor Agreements (ACA)

4.8.4 Contractor Furnished Materials and Equipment

4.8.5 Facilities Requirement

4.8.6 Management Meetings and Reviews

4.8.7 Multi-functional Teams (MFT)

4.9 Delivery Order Requirements

4.9.1 Field Representation

4.9.2 Access to Facilities and Property

4.9.3 Delivery Order Deliverables

4.9.4 Delivery Order Data Requirements

4.9.5 Publications

4.9.6 Funds Status Report

4.9.7 Integrated Master Schedule (IMS)

4.10 Quality Control Provisions

4.10.1 Aircraft Quality Control Program

4.11 Program Protection Plan (PPP)

4.12 Non-Development Items

4.13 Commercial Processes and Technologies

4.14 Risk Management

4.15 Proposal Submission

4.16 Continuation of Essential DoD Contractor Services During Crisis

4.17 Inspection of Services Clause

4.18 Commercial Asset Visability – Air Force (CAV-AF)

5.0 General Information

5.1 Security Requirements

5.1.1 Security Regulations

5.1.2 Operations Security (OPSEC)

5.1.3 Employee Clearances

5.1.4 Security Incidents and Violations

5.1.5 Release and Removal of Documentation

5.1.6 Communications Security (COMSEC)

5.1.7 Security of Contractor System(s)

5.1.8 Access to Government Facility or Military Installation

5.2 Environmental Management System (EMS)

5.2.1 Safety and Environmental

5.2.2 System Safety and Health Hazards

5.2.3 Hazardous Materials

5.3 Green Procurement Program (GPP)

5.4 Safety Requirements

5.4.1 Safety and Health Plan

5.4.2 Contractor Compliance

5.4.3 Mishap Notification/Investigation

5.5 Inspection of Services

5.6 Trafficking in Persons

5.7 Invoicing/Payment and Receipt/Acceptance

6.0 Appendices

6.1 Appendix A: References

6.2 Appendix B: Acronyms

6.3 Appendix C: Contract Data Requirements List (CDRL)

6.4 Appendix D: Labor Categories And Qualifications

6.5 Appendix E: SOF/PR Systems Engineering Plan (SEP)

1.0 Description of Services

1.1 Objective(s): The purpose of this document is to provide modification, engineering, and sustainment support for all Special Operations Forces/Personnel Recovery (SOF/PR) and Rotary Division managed aircraft to include integrated weapon systems, subsystems, and associated support equipment. This requirement may include, but is not limited to non-recurring engineering, manufacture, integration, logistics, provisioning and installation of aircraft modification kits. The delivery orders may contain development of airworthiness documentation, aircraft integration technical data packages, trial installations, kit-proof installations, test support, technical orders, full-rate kit production, kit installations and repair/correction of Engineering Change Proposals (ECPs). Additionally, the contractor shall provide punctual delivery of all required data. This effort will not include Advisory and Assistance Services (A&AS) support.

1.1.1 The contractor shall provide support to the SOF/PR and Rotary Division Program Office, in the following categories: (1) Modification; (2) Engineering; (3) Technical Support; (4) Production; (5)Testing; (6) Logistics; (7) Sustainment; and (8) Travel in execution of Delivery Orders (DO) issued.

1.1.2 Request/Authorization for In-Scope Taskings: A Request/Authorization for In-scope Taskings will be used by the Government to direct execution of specific with-in scope taskings which are mutually agreed upon with respect to cost and schedule.

1.1.3 Quality Assurance Surveillance Plan: No Quality Assurance Surveillance Plan will be required on the basic contract. A Quality Assurance Surveillance Plan (QASP) may be required for individual DOs.

1.2 Benefit to United States Air Force (USAF): This effort will benefit the Air Force by providing timely engineering, technical and modification support and improved capability to the war-fighter. The awardee shall perform a minimum of 51 percent of the work ordered.

2.0 Services Summary:

Comply with occupational, environmental, safety, and health requirements

5.3.1 Standard is no critical defects. A critical defect occurs where there is non-compliance with OSHA, AFOSH Standards, AFIs, AFMAN, EPA, OEBGD, NFPA, S&H OI/plan, or environmental OI/plan; and a safety or environmental incident or mishap is attributed to inadequate or non-performed S&H or environmental tasks; or missed or inadequately performed duties jeopardized the S&H of environment, of personnel, or equipment.

Mishap Notification

100% compliance with the security requirements. For any compromise, the incident will be reviewed by the Government Security Office to determine the level and appropriate resolution

Appendix C All documentation shall be provided to the Government by the delivery date called out in each CDRL 90% of time and compliant with the CDRL requirements or written Government direction. The remaining 10% of the time compliant submittal must be within 3 additional calendar days.

3.0 Government Property and Services

3.1 Government Property: To the maximum practicable extent, the Government will provide available information and data on an as available/required/authorized basis to support individual 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.

3.2 Government Property to be Provided: Government Furnished Material (GFM) and Government Furnished Equipment (GFE) may be provided to support individual 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 individual DOs. Additionally, if Government facilities are provided, they will be specified in individual DOs. The designated Government Program Manager (PM) or Contracting Officer Representative (COR) for the individual DO will provide the contractor access to all GFI, facilities, material, equipment, services, etc., as required to accomplish individual DOs.

3.3 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 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).

3.4 Loss of Government Property: Reporting Loss of Government Property, the Contractor shall use the Defense Contract Management Agency (DCMA) eTools software application to report loss of Government property at the site below 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. http://www.dcma.mil/aboutetools.cfm

3.5 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 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.

4.0 Technical Requirements

4.1 Place of Performance: These services will be performed at locations specified under each Delivery Order (DO).

4.1.1 Contract/Order Period of Performance: The period of performance for the contract/order will extend __________.

4.2 Item Unique Identification (IUID): The contractor shall mark items in accordance with DFARS 211.274-2, DFARS 252-211.7003, MIL-STD-130N, Department of Defense Standard Practice/Identification Marking of U.S. Military Property, and applicable contract clauses.

4.3 Packaging: 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 ensure that classified material is packaged, marked and shipped in accordance with DoD 5220.22-M, National Industrial Security Program Operating Manual (NISPOM).

4.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 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 and applicable supplements and shall be in compliance with all applicable guidance and clauses listed in the contract.

4.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 GIDEP Operations Manual S0300-BT-PRO-010, Government-Industry Data Exchange Program

4.5.1 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 arecord of the status and disposition of all Alert/Safe-Alert reports

4.6 Travel: The contractor may be required to travel to Government installations CONUS and OCONUS or to other contractor facilities to provide SOF/PR and Rotary 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. All trips shall be documented in trip reports included in the MSRs. The contractor shall provide a list of travel requirements in the MSR.

4.7 Categories of Work: All personnel under labor categories identified in PWS Appendix C “Labor Categories and Qualifications” must meet all minimum qualifications as identified. Only those labor categories and qualifications listed in the attachment shall be used for DOs unless an exception has been granted prior to commencement of the individual DO.

4.7.1 Logistics:

4.7.1.1 Logistics Studies: The contractor shall provide logistics services as specified in assigned DOs. Contractor support shall include preparing/documenting agendas, briefing materials, minutes, and action items and documenting these actions in their monthly status reports.

4.7.1.2 Support Requirements: The contractor shall provide engineering and logistics analysis support. The contractor shall provide analyses to assist in the determination of weapon system support requirements. Analyses shall cover the full spectrum of support requirements from concept through fielding of equipment. Studies shall include, but are not limited to, levels of maintenance, support equipment, training, technical orders, site activation task force, configuration commonality of equipment, modification accountability and crisis supportability investigations. The contractor shall prepare and review support equipment requirements consistent with the maintenance concept for the SOF/PR weapons systems and the accepted system concept. Support equipment requirements shall be structured to encourage the use of existing tools and equipment. The application of commercial-off-the-shelf (COTS) equipment shall be considered for each application. The contractor shall review the aircraft or system Support Equipment Recommendation Documents (SERDs) for accuracy and completeness.

4.7.1.3 Configuration Management: 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.

4.7.1.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. The Contractor shall develop Modified Airworthiness Certification Criteria (MACC) in accordance with (IAW) MIL-HDBK-516C and 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.

4.7.1.5 Diminishing Manufacturing Sources/Material Shortages (DMS/MS): The contractor shall provide DMS/MS information as requied by each DO. The contractor shall develop and revise DMS/MS Plans and develop and maintain indentured parts lists for use in DMS/MS technical studies. The contractor shall require access to Government Information Management Systems to gain Total Asset Visibility including maintenance activity. The contractor shall be required to access Government-Industry Data Exchange Program (GIDEP) and perform DMS/MS Technical Studies to identify current and potential future part and material shortage problems. The contractor shall assess and predict long range part availability from original vendors and aftermarket sources. The contractor may obtain written letters of 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.

4.7.1.6 Cybersecurity Implementation: The contractor shall integrate DoD Instruction 8510 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, verification and validation in accordance with the specific DO.

4.7.1.7 Cybersecurity Workforce: The contractor shall implement DoD Directive 8570.1 and DoD 8570.1-M for requirements and processes necessary for information management and cybersecurity including those applicable to contractor employees and employee training.

4.7.2 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 PWS Appendix D. The contractor shall provide engineering services 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), performing studies, validation and verification, prototyping, aircraft surveys, troubleshooting activity, and testing to support systems and subsystems. Upon award of a DO requirement, the contractor shall: (1) provide effective and timely response to deficiency reports, configuration change requests, repair/maintenance actions, and items causing operational limitations; (2) support development and qualification of replacement parts; drawing, specifications, and technical data updates; training data and equipment updates; and support equipment update or replacement; (3) support mishap investigations, failure analysis, Form 107 requests, design reviews, technical interchange meetings (TIMs), PMRs, and aircraft training devices as directed; and/or (4) apply an integrated systems engineering and Operational Safety, Suitability and Effectiveness (OSS&E) approach to all tasks. The contractor may be required to provide Technical Data Documents (TRD) and Engineering Change Proposals. The contractor may be required to sign or create Maintenance Discrepancy and Work Documents (AFTO Form 781A, includes Red X authority), Physical Configuration Inspection Reports (AFMC Form 272), Configuration Control Board Directives (AFMC Form 518), and Final Release for Flight (AFMC Form 273).

4.7.2.1 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 obtain as many items or kits necessary to satisfy 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.

4.7.2.2 Prototype/Pre-Production: The contractor shall develop and provide prototypes/ preproduction/production representative items in quantities as specified to allow for testing by both the contractor and Government. When required by DO, the contractor shall build prototype, preproduction, and/or production representative units; conduct tests and evaluate the item(s) against specified requirements; and deliver a validated technical documentation package. The contractor may also be required to perform first article testing.

4.7.2.3 Reverse Engineering: The contractor shall perform reverse engineering of hardware and software. The contractor shall conduct a technical evaluation of available hardware and software technical documentation and confirm the hardware and software’s documented performance and structure matches fielded units. The contractor shall identify, to the Government, any necessary information that is missing from available documentation.

4.7.2.4 System Integration: Upon award of a DO requirement to perform system integration, the contractor will 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. Interface control documentation (ICDs) will be requested from source suppliers, and will be included as configuration control documentation for system integration technical data packages.

4.7.2.4.1 The contractor may 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 technical studies, analytical engineering, software engineering, system integration engineering, development of engineering design packages, validation and verification, and testing.

4.7.2.5 Engineering Data: The contractor shall develop/produce/maintain and deliver a Technical Data Package (TDP) that accurately depicts the final product. The TDP shall represent the 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 dictated by that DO.

4.7.2.6 Engineering Data Guidance Conference: The contractor shall support and co-chair a Guidance Conference with WR-ALC/ ENGLDC 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:

4.7.2.6.1 Understanding of all CDRL requirements, applicable DIDs, specifications and standards.

4.7.2.6.2 TDP review requirements and schedules.

4.7.2.6.3 TDP delivery requirements and schedules.

4.7.2.6.4 Contractor's drafting practices/procedures/TDP drawing formats.

4.7.2.6.5 The contractor's quality assurance procedures relating to TDP documents, including quality control of subcontractor and vendor data.

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

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

4.7.2.6.8 TDP deliverables. Note: Guidance Conference may be held in conjunction with other meetings or conferences.

4.7.2.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 included in the TDP. The IPR shall be conducted only after the contractor's quality assurance personnel have completely reviewed the data and determined that data are of sufficient quality that Government time will be effectively utilized during the review. IPR may be scheduled when data has reached the 50% percent completion point and shall be held, when possible, in conjunction with other reviews (i.e., PDR, CDR). The contractor shall notify WR-ALC/ENGLDC a minimum of 30 days prior to the anticipated date of completion point. The IPR shall focus on the contractor's progress in the preparation of the TDP. The contractor shall support and provide the necessary resources, i.e., meeting agenda, conference room, applicable data, minutes, and appropriate personnel available to answer any questions to perform the IPR effectively. The contractor shall correct all discrepancies identified in the IPR. All subcontractor/vendor data shall be made available for review. If the quantity of subcontractor/vendor data is of sufficient magnitude, the Government may schedule a separate IPR at the subcontractor's/vendor's facility.

4.7.2.8 Engineering Studies: Upon award of a DO requirement for technical studies and analyses, the contractor shall perform independent technical studies and analyses as required to support the aircraft systems and subsystems and their integration into the aircraft utilizing the applicable Joint Service Specification Guide (JSSG). The intent of these activities is to provide the Government with an assessment of potential solutions to any specified deficiency. The assessment shall provide the Government with sufficient insight to pursue the appropriate solution to resolve the identified problem. The contractor’s report shall include a description of all options reviewed, how each is applied to the problem, and ranked (include ranking rationale and methodology) according to viability for problem resolution. Studies and analyses may include, but are not limited to: stress analysis report (SAR), system safety hazard analysis (SSHA), failure modes, effects, and criticality analysis (FMECA), finite element analysis (FEA), durability and damage tolerance analysis (DADTA), electrical loads analysis (ELA), weight and balance (W&B) report, aircraft survey post reports, antenna cosite analysis, aerodynamic analysis, and engineering trade studies.

4.7.2.9 Weapon System Integrity and Aircraft Performance Characteristics: The contractor shall provide updates for Weapon System Integrity Programs (WSIP) and Technical Performance Measurements (TPMs). The contractor shall analyze and verify how a modification affects the established performance envelopes for specified aircraft. The contractor required updates include the Aircraft Structural Integrity Program (ASIP), Propulsion System Integrity Program (PSIP), Mechanical Equipment Integrity Program (MEIP), and Avionics and Electronics Integrity Program (AEIP). As required, the contractor shall calculate and update the aircraft’s Electrical Load Analysis (ELA), Weight & Balance, Electromagnetic Environmental Effects (E3), Drag Analysis, and Antenna Coupling Analysis.

4.7.3 Testing:

4.7.3.1 Ground and Flight Testing: The contractor shall conduct testing, or shall support Government test personnel, as specified by individual DOs. The contractor shall ensure that all hardware, software, test equipment, instrumentation, supplies, facilities, and personnel are available and in place to conduct or support each scheduled test as specified in individual DOs. The Contractor shall provide the necessary test planning documentation, coordination, accomplish the necessary instrumentation, and provide qualified engineering supervision and staffing.

4.7.3.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. The contractor shall perform all testing required for full qualification (e.g., Electromagnetic Interference (EMI), Electromagnetic Compatibility (EMC), environmental, etc).

4.7.3.3 Validation and Verification: Upon award of a DO requirement the contractor shall provide engineering support in the validation and verification of all avionics, hardware, and software systems and subsystems installations and associated technical manuals. 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.

4.7.3.4 Test Support: The contractor shall provide aircraft integration support and check-out during current and continuing /developmental 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.

4.7.3.5 Prototyping: When required by the DO, the contractor shall develop prototype hardware as required to validate and test alternative designs, integrate equipment into the aircraft, and conduct qualification testing. This may include support for T-1 and T-2 test requirements, proof of concept, and trial installation/kit proof installation. Prototype hardware shall be production representative documented by engineering drawings and specifications. The contractor shall obtain design concept approval of all assembly and installation drawings and ECPs prior to the prototype installation. Prototype installation will be accomplished for the purpose of proving the validity of the contractor’s design, verification of the kit component design, completeness of kit contents, checking electromagnetic effects (EME), testing of system performance, and verification of the preliminary TCTO. The contractor shall furnish the prototype installation kit and installation labor unless otherwise directed.

4.7.3.6 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 prototyping 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.

4.7.4 Software: The contractor shall apply effective software engineering processes to all software requirements. Software certification shall be IAW ISO-STD-12207 or equivalent processes approved by other Department of Defense (DoD) services or agencies may be specified for individual DOs.

4.7.4.1 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 4.7.4.3 to the degree specified in the DO.

4.7.4.2 Maintenance of Existing Software: When a requirement is established to modify existing software, the contractor shall accomplish all or part of the efforts in paragraph 4.1.4.3 to the degree specified in the DO.

4.7.4.3 Software Process:

4.7.4.3.1 Software Requirements and Feasibility Analysis: The contractor shall analyze operational requirements and/or deficiencies and determine the feasibility of developing new software or modifying existing software to resolve them.

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

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

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

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

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

4.7.4.3.7 Software Documentation: Upon award of a DO requirement for software engineering services or software maintenance support the contractor shall create or update documentation to include Automated Computer Product Identification Number (ACPIN) and other processes as specified in the DO.

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

4.7.4.3.9 Software Ownership and Rights: The contractor shall obtain and grant the Government the right to use and distribute computer software developed or obtained under this effort. Any inability to grant rights to the software will be discussed with the Government on a case-by-case basis. This includes software residing in 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 contractor shall provide unlimited rights for all non-commercial computer software products and software documentation that are developed solely with Government funds. The contractor shall seek unlimited rights to all non-commercial computer software and related documentation that was developed using both Government and private funds. The Government PCO 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 AFLCMC/WIU.

4.7.5 Systems Engineering: The contractor shall apply an integrated systems engineering and Operational Safety, Suitability and Effectiveness (OSS&E) approach to all DOs that is consistent with the SOF/PR and Rotary Systems Engineering Plan.

4.7.5.1 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 by individual DOs.

4.7.5.4 Standard Items: All designs shall use Commercial-Off-The-Shelf (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.

4.7.5.5 Producibility: The contractor may be required to establish a program that assures all designs are producible and that 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 Air Force and as specified by individual DOs.

4.7.5.6 Source Qualification: The contractor shall be required to assist in the qualification of sources as specified by individual DOs.

4.7.5.7 Laboratory Services: As specified by individual 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.

4.7.5.8 Certifications: The contractor shall obtain commercial and/or military certifications /authorizations as specified by individual DOs.

4.7.5.9 Product Data Management: The contractor shall review and/or develop and submit Product Data in accordance with individual DOs. Product Data may define one or more configuration items, associated manufacturing processes, and associated test procedures. Various types of Product Data, including engineering drawings, specifications, quality assurance requirements, and/or commercial item descriptions may be required. Furthermore, Product Data may include complete design disclosure, form/fit/function requirements, performance specifications, Interface Control Data, market surveys.

4.7.5.10 Configuration Data Management: The contractor shall provide configuration management support in accordance with individual DOs, including but not limited to:

4.7.5.10.1 Collection, review, tracking and archiving of Configuration Control Documents

4.7.5.10.2 Development of automated databases to track hierarchical components

4.7.5.10.3 Maintenance of Product Data

4.7.5.10.4 Support to Configuration Control Boards (CCBs)

4.7.5.10.5 Performance of FCAs and PCAs

4.7.5.10.6 Evaluation of Configuration Management Single Process Initiative (CMSPI) Concept Papers

4.8 Contractor Requirements: The contractor shall provide the services specified herein in accordance with this PWS and the applicable individual DO. General conditions applicable to all DO requirements appear in paragraph 4.7. Unique requirements may be specified in individual DOs.

4.8.1 Program Management: The contractor shall designate a single program management point of contact. The contractor shall develop management plans as necessary to ensure that all elements of this effort are successfully executed within the program budgets and schedule. The contractor shall also ensure that complete financial accountability is maintained by contract line item and that all 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 PWS. The contractor shall conduct program meetings and reviews as required by this PWS 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), etc. Where feasible, meetings should be combined. The contractor and the government will mutually agree upon locations and dates of program meetings and reviews.

4.8.2 Subcontractor Management: The contractor shall maintain a current Subcontractor Management Plan IAW the individual DO. 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 contract and its proposed subcontractors. The contractor shall levy on sub-contractors and sub-vendors the same requirements for Technical Data Packages (TDPs) as are levied on them by this contract. This requirement shall apply at all tiers of sub-contractor/vendor levels associated with the program.

4.8.3 Associate Contractor Agreements (ACA): If the contractor shall enter into ACAs for any portion of the contract requiring joint participation in the accomplishment of the Government’s requirement, the agreements shall include the basis for sharing information, data, technical knowledge, expertise, and/or resources essential to the integration of the Lifecycle Support Contract, which shall ensure the greatest degree of cooperation for the development of the program to meet the terms of the contract.

4.8.3.1 ACAs shall include the following general information:

4.8.3.1.1 Identify the associate contractors and their relationships

4.8.3.1.2 Identify the program involved and the relevant Government contracts of the associate contractors.

4.8.3.1.3 Describe the associate contractor interfaces by general subject matter.

4.8.3.1.4 Specify the categories of information to be exchanged or support to be provided.

4.8.3.1.5 Include the expiration date (or event) of the ACA.

4.8.3.1.6 Identify potential conflicts between relevant Government contracts and the ACA; include agreements on protection of proprietary data and restrictions on employees.

4.8.3.1.7 A copy of such agreement shall be provided to the contracting officer for review before execution of the document by the cooperating contractors.

4.8.3.1.8 The contractor is not relieved of any contract requirements or entitled to any adjustments to the contract terms because of a failure to resolve a disagreement with an associate contractor.

4.8.3.1.9 Liability for the improper disclosure of any proprietary data contained in or referenced by any agreement shall rest with the parties to the agreement, and not the Government.

4.8.3.1.10 All costs associated with the agreements are included in the negotiated cost of this contract.

4.8.4 Contractor Furnished Materials and Equipment: The contractor shall acquire any additional hardware and software not provided by the Government as required to accomplish individual DOs. Ownership will be established in accordance with terms and conditions specified within individual 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 individual DOs. Required data types, formats, and transmission media will be specified by individual DOs.

4.8.5 Facilities Requirement: Facilities required for some requirements may include an enclosed climate-controlled hangar of sufficient size to accommodate any fully mission-configured HH-60 helicopter or C-130 aircraft variant. This hangar shall be located near an airstrip capable of receiving and servicing helicopters and C-130 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, 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, scaffolds, and ladders typically used for depot level aircraft maintenance.

4.8.6 Management Meetings and Reviews: The Contractor shall be required to support various meetings as identified in individual DOs. The Contractor shall maintain a schedule of events for 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 submission of AIs with identity of Office of Primary Responsibility (OPR).

4.8.6.1 Post Award Conferences: The Government will host a Post-Award Orientation Conference at a Government designated facility within 30 days after contract award. A Post Award Confrence may be required after award of a DO. The DO will specify if a Post Award Conference is required. All key contract participants (Government and contractor) shall attend.

4.8.6.2 Technical Interchange Meetings (TIM): The contractor shall participate in TIMs as required by Government’s DO Managers for individual DOs. The Government DO Manager will specify agenda and attendance requirements, with specific dates and locations, at least 10 calendar days prior to the meeting.

4.8.6.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),…