Draft_CIP_PWS_-_14_Nov_13.doc

ANNEX – A

LIST OF DOCUMENTS

Attachment X

Contract

ATTACHMENT X

PERFORMANCE WORK STATEMENT (PWS)

COMPONENT IMPROVEMENT PROGRAM (CIP)

OEM

TMS(‘s)

1 Jan 2015 – 30 Dec {2020}

Draft Version 1 Summary of Changes

PWS Applicability Matrix Table of Contents 2Summary of Changes

3PWS Applicability Matrix

4Table of Contents

61.0

SCOPE/OBJECTIVE

62.0

APPLICABLE DOCUMENTS:

73.0

CIP REQUIREMENTS

73.1

ENGINEERING REQUIREMENTS

73.1.1 Systems Engineering & Program Support

73.1.2 Interface Management

73.1.3 Development and Verification

83.1.4 Quality Assurance

83.1.5 Critical Safety Items (CSIs)

83.1.6 Reliability and Maintainability (R&M) Data Analysis

83.1.6.1 Government Industry Data Exchange Program (GIDEP)

83.1.7 Failure Modes and Effects Criticality Analysis (FMECA)

83.1.7.1 FMECA changes due to EPD/ECP

83.1.7.2 FMECA updates

93.1.8 Performance and Operability

93.1.9 Propulsion Characteristics Guide (Gray Book)

93.1.10 System Safety Program

93.1.10.1 Hazard Identification and Mitigation

93.1.10.2 System Safety Program Plan

93.1.10.3 System Safety Group Support

103.1.10.4 Hazard Tracking and Risk Resolution

103.1.10.5 Safety and Health Hazard Review of Engineering Project Description (EPDs), Engineering Change Proposals (ECPs), and Change Notices (CNs)

103.1.10.6 Health Hazard Analysis (HHA)

103.1.11 Environmental Risk Management

103.1.11.1 Hazardous Material (HAZMAT) Management Plan (HMMP)

103.1.11.2 HMMP Implementation

113.1.11.3 Ozone Depleting Substances (ODS)

113.1.12 Airworthiness Certification

113.1.12.1 Airworthiness Certification Plan

113.1.12.2 Modification Airworthiness Certification Criteria (MACC)

113.1.12.3 MACC Report

Error! Bookmark not defined.3.1.13 Nuclear Survivability Maintenance/Surveillance Plan

113.2

CIP PROGRAM MANAGEMENT INTEGRATION

123.3

CIP CONTRACTS MANAGEMENT

123.3.1 Program Security and Foreign Disclosure

123.3.2 Integrated Baseline Review

123.3.3 Long Lead Hardware Procurement

123.3.4 Government Furnished Property, Material and Equipment (GFP/GFE)

133.3.4.1 Right of Use for CIP GFP

133.3.4.2 Right of Use for Non-CIP GFP

133.3.4.3 Test Measurement and Diagnostic Equipment (TMDE)

133.4

TMS PROGRAM MANAGEMENT

133.4.1 Program Reviews

133.4.2 Integrated Engineering Design Reviews and/or Audits

143.4.3 Integrated Program Management Report (IPMR)

143.4.4 Program Progress Report

143.5

CONTRACTOR COST MANAGEMENT SYSTEM

143.5.1 Earned Value System

143.5.2 Fuels, Oils, and Lubricants

143.6

CONFIGURATION MANAGEMENT

143.6.1 Configuration/Change Management

143.6.2 Configuration Status Accounting Information

143.6.3 Specification Maintenance

153.6.4 Engineering Change Proposals (ECPs)

153.6.5 Parts Control & Standardization Program

153.6.6 Item Unique Identification (IUID)

153.7

DATA MANAGEMENT

153.7.1 Data Management Planning/Execution

153.7.2 Data Accession List (DAL)

163.7.3 Engineering Data

163.7.3.1 Engineering Data Documentation

163.7.4 Provisioning Data

163.7.5 Data Rights

163.8 ENGINEERING PROJECT DESCRIPTIONS (EPDs)

173.8.1 Permissible EPD Topics and Specific Requirements

173.8.1.1 Hardware/Software Design

183.8.1.2 Overhaul and Repair

183.8.1.3 Support Equipment/Tooling Design

183.8.1.4 Study/Analysis Tasks

183.8.1.4.1 Mission/Life Analysis

183.8.1.5 Test and Test Management

193.8.1.5.1 Support Equipment Testing

193.8.1.5.2 Software Simulation, Test, and Evaluation

193.8.1.5.3 CIP Test Article Configuration Management and Usage Tracking

203.8.1.5.4 Petroleum, Oil and Lubricant (POL)

203.8.2 Consideration of New Technology

203.8.3 EPD Requirements Process

203.8.4 Ad Hoc EPD Process

203.8.5 Cost Effectiveness Analysis (CEA)

1.0

SCOPE/OBJECTIVE

The requirements of this PWS apply to each TMS engine as defined in Appendix 1; Applicability Matrix.

The objective of CIP is to improve system-level safety, reliability, maintainability, durability, operability, supportability, and affordability to support Major Command (MAJCOM) or Type Command (TYCOM) metrics provided in the Engine Life Management Plan (ELMP) or Propulsion System Life Management Plan (PSLMP). The Contractor shall provide and support engineering and test activities to develop solutions to engine problems. These solutions address service-related operational and support problems, increase safety of flight, correct operationally identified deficiencies, improve reliability, maintainability and durability, and reduce total ownership costs for non-CLS, Government Furnished Equipment in-service engines. Tasks include developing production-representative deliverables through Engineering Change Proposals (ECPs) that enable the achievement of MAJCOM/TYCOM ELMP/PSLMP goals.

2.0

APPLICABLE DOCUMENTS:

The latest versions of the documents specified below form a part of this document to the extent specified herein. The requirements of any document referenced within the specification, but omitted in section 2, remain applicable.

MIL-HDBK-516 B (Expanded) “Airworthiness Certification Criteria” MIL-STD-882E and MIL-STD-882D “System Safety” ANSI/ISO/ASQ QS9001:2008 “Quality Management Systems” AS-9100 “Quality Systems” “Aviation Critical Safety Item Management Handbook”, JACG (Joint Aeronautical Commander’s Group), NAVAIR Public Release 11-515, 16 March 2011

Air Force Propulsion Center of Excellence (PCoE) system safety approach, PCoE Best Practice 99-06 MIL-STD-1629A “Procedures for Performing a Failure Mode, Effects and Criticality Analysis” Federal Standard No. 313D “Material Safety Data, Transportation Data, and Disposal Data for Hazardous Materials Furnished to Government Activities DD Form 254 “Contract Security Classification Specification” AFMAN 16-101 “International Affairs and Security Assistance Management” National Industrial Security Program Operating Manual

FAR Clause 52.234-2

FAR Part 45

DFARS 252.211-7003

DFARS Clause 252.234-7002

DFARS Clause 252.242-7005

CEA User's Group “CEA Version”

Component Improvement Program (CIP) Scorecard Process Guidance (annual document)

MIL-STD-3024 Propulsion System Integrity Program (PSIP), formerly Engine Structural Integrity Program (ENSIP)

The following identify Type Model Series (TMS) current approved prime item development specifications:

Applicable Engine Specifications

RR

*Including the approved Specification Change Notices (SCN’s)

3.0

CIP REQUIREMENTS

The Component Improvement Program (CIP) shall be performed in accordance with requirements defined in this document and implemented through individually approved Engineering Project Description (EPD) proposals.

3.1

ENGINEERING REQUIREMENTS

The Contractor shall manage, maintain and conduct a continuing engineering and test program at the Contractor’s facility and Government facilities, as required in support of approved CIP tasks.

3.1.1 Systems Engineering & Program Support

The Contractor shall provide all systems engineering functions required for the execution of this program. The Contractor’s systems engineering activities shall include, as a minimum, the management and integration of requirements analysis and allocation, affordability, risk identification and management, Weapon System Contractor (WSC) interface management, engine systems and design integration, and systems engineering elements such as system safety analysis (SSA), reliability, maintainability, human factors, producibility, safety, hazardous material analysis, mass properties, and system security.

The Contractor shall provide systems engineering and program support services as required for proper integration and control of CIP activities in conjunction with other TMS program activities and as described in approved EPDs.

3.1.2 Interface Management As requested by the Government, the Contractor shall support the WSC to update and maintain Interface Control Documents (ICDs). The Contractor shall notify the Government Program Office of interface changes (A021: DI-MGMT-81453A/T).

3.1.3 Development and Verification The Contractor shall perform development and verification activities to satisfy the requirements of each EPD in accordance with applicable Prime Item Development (PID) and Prime Item Performance (PIP) specifications and applicable Integrity Programs (e.g., PSIP, ENSIP).

3.1.4 Quality Assurance The Contractor shall maintain a quality system that addresses the elements of ANSI/ISO/ASQ QS9001:2008 and AS-9100, for quality assurance in design/development, production, installation and servicing. Copies of the Contractor’s quality system documentation shall be made available to the Government upon request. (A021: DI-MGMT-81453A/T) 3.1.5 Critical Safety Items (CSIs)

For all hardware and support equipment tasks, the Contractor shall recommend criticality classifications, and identify, document, and manage critical characteristics, in accordance with the Contractor’s process using “Aviation Critical Safety Item Management Handbook”, JACG (Joint Aeronautical Commander’s Group), NAVAIR Public Release 11-515, 16 March 2011, as a guide.

3.1.6 Reliability and Maintainability (R&M) Data Analysis The Contractor shall collect and analyze development and operational R&M data. R&M Data Analysis which results in CIP activity shall be a traceable part of any resulting task and documented within the applicable EPD, ECP, and associated documentation. Engine Program TMS R&M definitions shall be used when reporting status. (A021: DI-MGMT-81453A/T) 3.1.6.1

Government Industry Data Exchange Program (GIDEP)

The Contractor shall participate in the GIDEP in order to promote exchange of information pertaining to engineering, failure experience, metrology, product information, and reliability-maintain ability data on products, components (including construction materials), manufacturing processes, environmental issues associated with those manufacturing processes, recycling and waste prevention.

3.1.7 Failure Modes and Effects Criticality Analysis (FMECA) 3.1.7.1

FMECA changes due to EPD/ECP

The Contractor shall perform a FMECA for all design changes using the methodology of MIL-STD-1629A or the Contractor’s equivalent process. The Contractor shall consider all assemblies, subassemblies, applicable components, and interfaces affected by the design change, and document the FMECA-driven results in the ECP.

3.1.7.2

FMECA updates

The Contractor shall update the FMECA database with any new failure modes discovered during testing or operational usage. The preferred database access is via a web-based means, accessible from the Government Program Offices. (A021: DI-MGMT-81453A/T) 3.1.8 Performance and Operability

The Contractor shall conduct performance and operability assessments as described in EPDs, including performance and operability support of development and qualification tests.

The Contractor shall update and maintain engine steady state and transient performance and operability computer programs (models) that reflect the engine hardware and software configuration in accordance with the Prime Item Development (PID) or Prime Item Performance (PIP) Specification. The Contractor shall deliver engine computer models and user's manuals per CDRL {XYZ}. (A025: DI-MISC-80672/T) 3.1.9 Propulsion Characteristics Guide (Gray Book)

The Contractor shall provide a Propulsion Characteristic Summary of baseline performance, characteristics, and pictorial presentations for each engine TMS listed in paragraph 2.0 of this PWS. The Contractor shall update the Propulsion Characteristics Summaries when a hardware or software improvement task results in a change to a reported characteristic.

This deliverable will be used to maintain a current Propulsion Characteristics Guide (Gray Book) which provides a single reference source of comparable data of USAF propulsion systems. ({A036: DI-XXXX-GRAYBK}) 3.1.10 System Safety Program The Contractor shall conduct a System Safety Program in accordance with MIL-STD-882E (excluding Paragraph 4.4 and sub-paragraphs), as tailored below. Software shall be in accordance with Paragraph 4.3 and sub-paragraphs of MIL-STD-882E.

3.1.10.1

Hazard Identification and Mitigation

The Contractor shall identify and mitigate hazards using the System Safety Methodology of MIL-STD-882E Task 101.

3.1.10.2

System Safety Program Plan The Contractor shall develop, maintain, and utilize TMS System Safety Program Plans (SSPPs) in accordance with MIL-STD-882E Task 102. In addition, the SSPP shall document the Contractor’s methodology for accomplishing Flight Safety Risk Management in accordance with the Air Force Propulsion Center of Excellence (PCoE) system safety approach, PCoE Best Practice 99-06. The SSPP shall be reviewed annually and updated as required. (A033: DI-SAFT-81626) 3.1.10.3

System Safety Group Support The Contractor shall participate as a member of the System Safety Group (SSG). The Contractor shall also participate in System Safety Working Group (SSWG) meetings as directed by the SSG chair person. SSG meetings will normally be held semi-annually with the location alternating between Contractor and Government facilities. The Contractor shall document all such meetings with agendas, meeting minutes, action items, and presentation materials. All minutes and action items shall be monitored, tracked, comments incorporated, and updates distributed on a routine basis. (A002: DI-ADMN-81373, A001: DI-ADMN-81250A) 3.1.10.4

Hazard Tracking and Risk Resolution The Contractor shall maintain the hazard tracking system as required by MIL-STD-882E Task 106, the SSPP, and the Air Force Propulsion Center of Excellence (PCoE) system safety approach, PCoE Best Practice 99-06. The preferred database access is via an existing, web-based means, accessible from the Government Program Offices. (A021: DI-MGMT-81453A/T) 3.1.10.5

Safety and Health Hazard Review of Engineering Project Description (EPDs), Engineering Change Proposals (ECPs), and Change Notices (CNs) The Contractor shall provide a safety and health hazard review (in accordance with MIL-STD-882E, Task 304) as part of the initial submittal of each EPD, and shall update that review as the EPD task progresses. The Contractor shall analyze each Class I design change (ECP) in accordance with MIL-STD-882E, Task 304. The conclusion of the analysis shall be incorporated into the ECP or CN as part of the supporting documentation. Contractor format is acceptable. (A032: DI-SAFT-80103B/T) 3.1.10.6

Health Hazard Analysis (HHA) When the 3.1.10.5 review indicates a health hazard exists, the Contractor shall perform a Health Hazard Analysis (HHA). The Contractor shall use MIL-STD-882E, Task 207 paragraphs 207.1 and 207.2 methodologies to perform and document a HHA to identify human health hazards, to evaluate proposed hazardous materials and processes using such materials, and to propose measures to eliminate the hazards or reduce the associated risks when the hazards cannot be eliminated. These hazards shall include those associated with normal operations, as well as system failures. Additionally, the Contractor’s assessments shall address the effectiveness of mitigation efforts.

3.1.11 Environmental Risk Management 3.1.11.1

Hazardous Material (HAZMAT) Management Plan (HMMP) The Contractor shall develop, implement, and maintain a HMMP in accordance with MIL-STD-882E, Task 108. HAZMAT is defined based on MIL-STD-882E and Federal Standard No. 313D. The HMMP shall address all processes as they pertain to CIP. The Contractor shall identify the materials to be prohibited, restricted, and tracked based on the definitions of these categories in Task 108, paragraph 108.2.2. The preferred access to the HMMP data is via a web-based means, accessible from the Government Program Offices. (A021: DI-MGMT-81453A/T) 3.1.11.2

HMMP Implementation The Contractor shall employ its HMMP to screen alternative materials for the work to be performed under this contract in modifying engines and components or required for subsequent operations and maintenance activities to reduce the use or release of HAZMAT and prevent pollution.

3.1.11.3

Ozone Depleting Substances (ODS)

The Contractor shall not incorporate into nor use any Class I or Class II ODS in the manufacture of items provided for in this contract, unless specifically approved by the Government’s representative. If an EPD potentially requires use of an ODS for mission critical requirements for which economically and technically feasible substitutes are not available, it will be evaluated by the Government and considered for approval.

3.1.12

Airworthiness Certification Airworthiness Certification shall comply with MIL-HDBK-516B Expanded.

3.1.12.1

Airworthiness Certification Plan The Contractor shall develop, document, maintain, and deliver an Airworthiness Certification Plan. The Airworthiness Certification Plan shall define the overall program approach to achieving and maintaining airworthiness and create the framework within which detailed airworthiness planning and execution is accomplished. The Airworthiness Certification Plan shall contain a timeline that includes major airworthiness activities and critical deliverable milestones. Existing design reviews, Configuration Management (CM) processes and verification planning processes should be used to the greatest extent possible to minimize cost. (A018: DI-MGMT-80004A) 3.1.12.2

Modification Airworthiness Certification Criteria (MACC) For each modification that impacts Airworthiness Certification Criteria (as defined in Section 7 of MIL-HDBK-516B Expanded), the Contractor shall develop and maintain a Modification Airworthiness Certification Criteria (MACC) document that defines the Certification Basis (Airworthiness Specification). The preliminary Certification Basis shall be delivered with each hardware or software design change EPD at proposal. The final Certification Basis shall be delivered prior to the start of certification testing. (A034: DI-SESS-81766).

3.1.12.3

MACC Report

The Contractor shall deliver a MACC Report in accordance with the Airworthiness Certification Plan for each modification that impacts Airworthiness Certification Criteria, to demonstrate compliance to the defined Certification Basis. The preferred access to all substantiating data referenced in the MACC report shall be via a web-based means, accessible from the Government Program Offices. (A027: DI-SESS-81768) 3.2

CIP PROGRAM MANAGEMENT INTEGRATION

The contractor shall plan, present, coordinate, and support an integrated CIP Corporate program. This includes overarching, contract management, cost management, program and test management, configuration/data management, Senior level meetings, reviews and planning activities necessary to execute CIP at a corporate level.

3.3

CIP CONTRACTS MANAGEMENT

The Contractor shall provide contract management and administration in support of CIP contractual actions. This shall include subcontract management and support of the Corporate Small Business Subcontracting Plan goals.

3.3.1 Program Security and Foreign Disclosure The Contractor shall comply with the requirements of DD Form 254, Contract Security Classification Specification. The Contractor shall also comply with Air Force foreign disclosure and international security requirements. Engine participation efforts are outlined in AFMAN 16-101. The Contractor shall maintain a security program that complies with the guidance reflected in the TMS system level Program Protection Plan and the National Industrial Security Program Operating Manual. The Contractor shall also provide Operations Security (OPSEC), Communications Security (COMSEC) and Information Assurance (IA) Training as part of its overall training requirements. OPSEC, COMSEC, and IA Training outline specific actions to protect classified and sensitive unclassified information, activities and operations during the course of the contract.

3.3.2 Integrated Baseline Review The Contractor shall co-lead an Integrated Baseline Review (IBR) that focuses on the Contractor's integrated Performance Measurement Baseline (PMB) and the appropriate measure of earned value performance. In accordance with FAR Clause 52.234-2, a pre-award IBR shall be performed jointly with the Government and Contractor for this contract and any subsequent issued delivery orders. The Contractor shall manage Control Accounts in accordance with best practices for Earned Value Management (EVM), including a review of the contract period of performance schedule, performance measurement baseline, actuals to date and performance evaluation techniques and measurements. The Contractor shall document all such reviews as appropriate, such as agendas, meeting minutes and action items. All minutes and action items shall be monitored, tracked, comments incorporated and updates distributed on a routine basis. (A002: DI-ADMN-81373, A001: DI-ADMN-81250A) 3.3.3 Long Lead Hardware Procurement The Contractor is authorized to propose procurement of limited long lead hardware in order to accomplish approved EPDs.

3.3.4 Government Furnished Property, Material and Equipment (GFP/GFE) The Contractor shall manage U.S. Government furnished property and equipment according to FAR Part 45. The Contractor shall provide an inventory report at the end of each calendar year (A021: DI-MGMT-81453A/T).

3.3.4.1

Right of Use for CIP GFP The Contractor shall submit a written request to the Government to use CIP GFP in the performance of non-CIP related tasks on other contracts. All requests shall be approved by the Government Contracting Officer prior to using requested GFP. The Contractor shall address non-interference, benefits, cost considerations, period of performance, and consideration for use through Government Contracting Officer approval.

3.3.4.2

Right of Use for Non-CIP GFP The Contractor shall submit a written request to the Government to use non-CIP GFP in the performance of CIP related tasks. The Contractor shall address non-interference, benefits, cost considerations, period of performance, and consideration for use through Government Contracting Officer approval.

3.3.4.3

Test Measurement and Diagnostic Equipment (TMDE)

The Contractor shall ensure all Government furnished TMDE is calibrated and documented to assure traceability to national standards.

3.4

TMS PROGRAM MANAGEMENT

The Contractor shall conduct formal and informal program and technical reviews as required by the Government. The Contractor shall support CIP working groups, including but not limited to, Program Management Reviews, Requirements Reviews, Maintenance Planning, and Test Planning with the TMS stakeholders to promote efficient and effective communications. The Contractor shall document all such reviews as appropriate, such as agendas, meeting minutes and action items. All minutes and action items shall be monitored, tracked, comments incorporated and updates distributed on a routine basis. (A002: DI-ADMN-81373, A001: DI-ADMN-81250A) 3.4.1 Program Reviews The Contractor shall present program status reviews as requested by the Government. The Contractor shall provide formal agendas and briefing materials; track action items; and provide formal minutes of program reviews as requested by the Government. Reviews may vary by TMS, worldwide activities, maintenance planning and field operations. Meetings shall include, but not limited to, Program Management Reviews and Roadmap Reviews. (A002: DI-ADMN-81373, A001: DI-ADMN-81250A)

3.4.2 Integrated Engineering Design Reviews and/or Audits The Contractor shall present engineering technical reviews as requested by the Government. The Contractor shall recommend the types of reviews, including the review schedule, format and agenda. Reviews shall be tailored to the specific needs of the particular development activity. The Contractor shall provide formal agendas and briefing materials; track action items; and provide formal minutes of program reviews and audits as requested by the Government. Reviews shall include, but not be limited to, Director of Propulsion (DoP) Safety and Technical Reviews, support to Engineering Independent Review Teams and CIP Engineering Technical Reviews. (A002: DI-ADMN-81373, A001: DI-ADMN-81250A) 3.4.3 Integrated Program Management Report (IPMR) The Contractor shall deliver an IPMR to measure cost and schedule performance. The IPMR will be structured around seven formats that contain content and relationships required for electronic submission. (A023: DI-MGMT-81861) 3.4.4 Program Progress Report

The Contractor shall deliver a Program Progress Report that provides the Government with the means to evaluate and monitor the progress made by the contractor of tasks in accomplishing the goals established for CIP. (A019: DI-MGMT-80555/T) 3.5

CONTRACTOR COST MANAGEMENT SYSTEM

3.5.1 Earned Value System Contractor shall establish, maintain, and use a certified Earned Value System in accordance with DFARS Clause 252.234-7002 and DFARS Clause 252.242-7005. This system shall be capable of providing a budget baseline, actual costs against budgeted costs, and an estimate of schedule completion versus planned. The Contractor shall perform financial and earned value analysis and reporting, to include a Contract Funds Status Reports (CFSR) detailing the integrated cost status of work in progress, projected work and accrued work on the contract (A022: DI-MGMT-81468/T).

3.5.2 Fuels, Oils, and Lubricants

The contractor shall furnish all necessary petroleum, oil and lubricant (POL) of the appropriate type for the tests to be conducted by the contractor. The contractor shall include POL estimates in the Engineering Program Description (EPD). The contractor is authorized to purchase POL from government sources at the government fixed rate for the Calendar Year. The Contractor shall forecast, manage, and report the usage of fuels, oils, and lubricants used in the performance of this contract. (A020: DI-MGMT-80791/T)

3.6

CONFIGURATION MANAGEMENT

3.6.1 Configuration/Change Management The Contractor shall accomplish all CIP CM tasks in accordance with each TMS-specific Configuration Management Plan (CMP). (A021: DI-MGMT-81453A/T) 3.6.2 Configuration Status Accounting Information The Contractor shall update and maintain traceability information on developed tasks from initiation to ECP submittal. (A008: DI-CMAN-81253C/T) 3.6.3 Specification Maintenance The Contractor shall maintain all Specifications for the applicable CIP contract. Submission of PID and PIP specification revision requests shall be submitted to the Government for approval under the applicable CIP contract per contract data requirements. The applicable PID/PIP specification shall be revised and delivered in accordance with approved program processes at Government request. (A007: DI-CMAN-80643C, A021: DI-MGMT-81453A/T) 3.6.4 Engineering Change Proposals (ECPs)

The Contractor shall submit ECPs to implement changes resulting from CIP EPDs. For approved ECPs, the Contractor shall process the change in accordance with the approved CMP. Submitted ECPs must contain an updated Cost Effectiveness Analysis (CEA). (A006: DI-CMAN-80639C/T)

3.6.5 Parts Control & Standardization Program The Contractor shall establish and implement a parts control and standardization program to minimize the number and type of parts used on the engine programs. The Contractor shall utilize industry standard parts to the maximum extent possible without compromising design or performance of the engine. This program shall apply to all new and modified parts of the engine and for new and modified support equipment (SE).

3.6.6 Item Unique Identification (IUID)

All items designed, developed, or delivered to the Government as part of the CIP that are subject to DFARS mandated IUID shall specify or contain (for delivered items) a machine readable data matrix symbol. Markings shall be legible with human and machine-readable information per MIL-STD-130N, “Identification Marking of U.S. Military Property”. The identification markings shall be visible during normal handling, shall be readable, shall withstand the specified environment and cleaning processes, and shall be as permanent as the service life of the unit or at least to the unit’s point of rebuild. For delivered items, the contractor shall upload the IUID assigned numbers and information into the Government IUID Registry following the applicable service’s guidance and procedures. The barcode shall contain, at a minimum: (1) Applicable Enterprise Identifier (2) Serial Number (3) Part Identification Number.

3.7

DATA MANAGEMENT

3.7.1 Data Management Planning/Execution The Contractor shall prepare, maintain, and track the contract data status and schedule. The Contractor shall submit all CDRL documentation through electronic media. The Contractor shall ensure that contractual electronic data are delivered using Secure Web-based Electronic Acquisition Program (SWEAP) (or Joint Enterprise Network for F135), unless waived by the Government Contracting Officer. The Contractor shall ensure that adequate numbers of personnel possess and utilize SWEAP accounts to ensure timely data delivery.

3.7.2 Data Accession List (DAL) The Contractor shall prepare, update, and maintain a Data Accession List (DAL). Any data developed in support of CIP and not otherwise deliverable shall be added to the DAL. The Contractor shall submit any data on the DAL upon formal Government request. (A021: DI-MGMT-81453A/T) 3.7.3 Engineering Data The Contractor shall develop and maintain (and shall require all vendors to develop and maintain) engineering data to support CIP Tasks under this contract.

3.7.3.1

Engineering Data Documentation The Contractor shall document engineering design, material identifications, manufacturing processes, fabrication and assembly sequences, test procedures, acceptance test parameters, quality control procedures and acceptance parameters, and source data for purchased material with engineering data, for the life of the contract. (A021: DI-MGMT-81453A/T) 3.7.4 Provisioning Data The Contractor shall provide Engineering Data for Provisioning (EDFP) and Provisioning Technical Documentation (PTD) which identify changes resulting from approved ECPs. (A005: DI-ALSS-81557, A003: DI-ALSS-81529/T, A004: DI-ALSS-81530/T) 3.7.5 Data Rights

The Contractor shall agree that the Government owns the data rights to any and all designs or procedures developed under this contract, with exception of any Contractor proprietary data approved to be incorporated by the Government. The Contractor shall make all assertions of less than unlimited rights prior to beginning activities which contain proprietary data. Data rights to designs or procedures developed utilizing Contractor proprietary data shall be subject to negotiations between the Government and the Contractor. Such data shall be identified by appropriate data legends. Acceptable data rights markings are (1) Unlimited rights, (2) Limited rights, and (3) Government-purpose rights. For software, an additional acceptable marking is (4) Restricted rights.

3.8 ENGINEERING PROJECT DESCRIPTIONS (EPDs) The Contractor shall develop EPDs in accordance with the contract, A035: DI-XXXX-EPD, and the requirements in this PWS. The details for each EPD shall be established and refined with participation of appropriate Government representatives. (DID Number for EPD) During the performance period of each EPD, either the Government or Contractor may initiate, or the Government may direct, changes to EPDs IAW the reviews and procedures set forth herein and in Section H, Special Contract Requirements.

3.8.1 Permissible EPD Topics and Specific Requirements All EPDs and revisions to EPDs will be vetted and approved by the Government. The following lists are not exhaustive but delineate typical allowable/non-allowable EPD topics (tasks). Requirements applicable to specific task types follow below:

Allowable Tasks: hardware/software design, overhaul and repair development (depot, intermediate, and organizational levels), support equipment/tooling design (common and peculiar), study/analysis (including mission analysis and component life analysis), electronic part/component obsolescence improvement, life-cycle-cost reductions, Analytical Condition Inspections (ACI), inspection development, test and test management (including engine maturation testing), and management/integration.

Non-allowable Tasks: work covered under warranty from production contracts, and manufacturing process changes authorized under engine Engineering Assistance to Production and Service (EAPS).

3.8.1.1

Hardware/Software Design

The Contractor shall design and develop the hardware and software necessary to complete the requirements of each approved EPD.

As part of each hardware or software design task the contractor shall generate updates to the relevant TMS’s integrity reports (e.g. PSIP Report, DAR, SOLAR, etc.) in order to maintain currency of these reports with the new configuration. The contractor shall only incorporate these updates into the integrity reports following ECP approval. The preferred access to the integrity reports is via a web-based means, accessible from the Government Program Offices. (A021: DI-MGMT-81453A/T) 3.8.1.1.1 Software Development

The Contractor shall update and implement, as necessary, software in accordance with the Software Development Plan (SDP) (if applicable), to ensure requirements set forth in the PID or PIP specification and the WSC ICD are achieved, or as necessary to support an approved EPD. The Government shall assist in setting the content priority prior to each software release. (A016: DI-IPSC-81442A, A026: DI-MISC-81454B, A017: DI-MCCR-80700)

3.8.1.1.1.1

Software Development Plan

The Contractor shall update and maintain a SDP that satisfies the PID or PIP specification and is coordinated, as necessary, with the WSC. (A009: DI-IPSC-81427/T) 3.8.1.1.1.2

Software Requirement Specification

The Contractor shall develop or update a Software Requirement Specification (SRS) for each software product. Each SRS shall include an Interface Requirement Specification or data required to facilitate interfaces with other systems and applications and identify the appropriate document(s) further defining those interfaces. (A010: DI-IPSC-81433A, A011: DI-IPSC-81434A) 3.8.1.1.1.3

Software Design Description The Contractor shall develop or update a Software Design Description (SDD) for each software application. (A012: DI-IPSC-81435A) 3.8.1.1.1.4

Software Product Delivery

The Contractor shall deliver all software products as execution-ready code to the USAF on digital media. The software products shall be delivered to the Government Software Control Center (SCC) for storage and configuration control. (A017: DI-MCCR-80700, A026: DI-MISC-81454B) 3.8.1.2

Overhaul and Repair

The Contractor shall design, develop, establish and refine organizational, intermediate and depot or heavy maintenance center overhaul/repair methods, procedures and tooling as defined in the EPD.

3.8.1.3

Support Equipment/Tooling Design

The Contractor shall design and develop SE/tooling as defined in the EPD. The contractor shall identify each piece of SE proposed to be developed or modified under this contract and obtain Government approval prior to task initiation. The Contractor shall fabricate, qualify and deliver the first-article of complex and non-complex SE in order to support engine related changes, support equipment improvements, concept changes and overall improvements. The Contractor shall revise, maintain, and deliver support equipment data, including engine model applicability. The Government is the final authority on classification of SE as complex or non-complex. The Contractor shall ensure all Test Measurement Diagnostic Equipment (TMDE) is calibrated and documented to assure traceability to national standards. (A004: DI-ALSS-81530/T, A031: DI-QCIC-80278A) 3.8.1.4 Study/Analysis Tasks

The Contractor shall develop, manage and document analysis and methodology necessary to complete the requirements of each approved EPD. The contractor shall report methods used and results of study/analysis tasks in a technical report. (A024: DI-MISC-80508B/T) 3.8.1.4.1 Mission/Life Analysis The contractor shall analyze engine operational usage/mission data, update duty cycles (used for design, test, and analysis) to represent operational usage, and update part lives per the new duty cycle consistent with requirements and timing defined in each TMS Life Management Plan (e.g. ELMP, PSLMP) and integrity program (e.g. PSIP, ENSIP) or as otherwise directed by the U.S. Government.

3.8.1.5

Test and Test Management The Contractor shall conduct and document full-scale engine testing, component testing, and other appropriate testing to support the applicable CIP EPDs. The Contractor shall provide support for engine ground and flight test, including maintenance, required for conducting testing at Arnold Engineering Development Complex (AEDC) or other Government or Contractor facilities. When testing at government test facilities the contractor shall be responsible for coordinating all test conduct/support requirements with the Government Program Office and the Government Responsible Test Organization (RTO). The Contractor shall support test planning and reviews with the USAF; report final results and recommendations; and forecast test location needs and costs looking forward for 5 years. Full-scale propulsion system testing common to many EPDs shall be described in a separate test EPD. Testing unique to a specific EPD shall be described in that EPD. The contractor shall investigate and document ground and flight test failures using the Contractor’s internal Failure Reporting, Analysis, and Corrective Action System (FRACAS). The Contractor shall prepare and submit Test Plans, Test Procedures, and Test Reports as required by individual EPDs. (A028: DI-NDTI-80566A, A029: DI-NDTI-80603A, A030: DI-NDTI-80809B/T) 3.8.1.5.1 Support Equipment Testing Unless otherwise directed, the Contractor shall perform first article qualification tests on all support equipment modified, revised, or developed under the approved EPD. Qualification testing of support equipment shall include performance, serviceability, reliability and maintainability, and workmanship evaluations. (A028: DI-NDTI-80566A, A029: DI-NDTI-80603A, A030: DI-NDTI-80809B/T) 3.8.1.5.2 Software Simulation, Test, and Evaluation

The Contractor shall test software in accordance with processes described in the SDP unless otherwise authorized by the Government. The Contractor shall support WSC software integration and verification testing, as necessary. The Contractor shall support government requests for software and system integration test data. The Contractor shall support test planning and reviews with the Government, and shall report final results and recommendations. The Contractor shall accommodate government (and WSC if necessary) attendance at internal software reviews. The Contractor shall accommodate government witnessing of software and systems integration testing upon request. The Contractor shall prove all simulation bench and stand-alone models are validated against engine test data. The Contractor shall develop and maintain a software test plan, software test description, and software test report for each Computer Software Configuration Item (CSCI). (A013: DI-IPSC-81438/T, A014: DI-IPSC-81439A, A015: DI-IPSC-81440/T) 3.8.1.5.3 CIP Test Article Configuration Management and Usage Tracking

The Contractor shall perform configuration management and usage tracking of all contractually-designated CIP test articles, including non-CIP-accountable articles supporting a CIP testing initiative. The data shall be available to DCMA property management and the Government program office. (A021: DI-MGMT-81453A/T) 3.8.1.5.4 Petroleum, Oil and Lubricant (POL)

The contractor shall furnish all necessary petroleum, oil and lubricant (POL) of the appropriate type for contractor tests to be conducted in the Engineering Program Description (EPD) budget proposed where POL will be required. The contractor is authorized to purchase POL from government sources at the government fixed rate for the Calendar Year.

3.8.2 Consideration of New Technology

The Contractor shall conduct an evaluation of the technology base and provide an assessment of potential new technology solutions, including manufacturing technologies, to address each EPD. The technology base shall include technologies developed by industry as well as those developed by the Government. The assessment shall include Technology Readiness Level (TRL), Manufacturing Readiness Level (MRL), and risk (technical, schedule, cost, implementation), and shall include supporting rationale. The Contractor shall document proposed new technologies in the EPD. Data rights assertions shall be in accordance with {section 3.7.5} of this PWS. ( {A035: DI-XXXX-EPD} ) 3.8.3 EPD Requirements Process The Contractor shall support the annual Government EPD requirements review process. The Contractor shall propose new candidate EPD tasks and revisions to existing EPDs, if required. New candidate tasks shall include planning and scoring elements of an EPD in accordance with DID (A035: DI-XXXX-EPD).

3.8.4 Ad Hoc EPD Process

When required by Immediate Flight Safety, Serious Mission Degradation, or Safety-Related, the Contractor shall develop EPDs out-of-cycle (outside the normal EPD requirements process), IAW the reviews and procedures set forth herein and in Section H, Special Contract Requirements.

3.8.5 Cost Effectiveness Analysis (CEA) The Contractor shall develop and submit a Cost Effectiveness Analysis (CEA) for all hardware improvement EPDs excluding support equipment and EPDs valued at less than $100K, unless the CEA requirement is waived by the program office. Costs contained in the CEA are Rough Order of Magnitude (ROM) estimates and are provided for planning and budgeting purposes only. For funded tasks, the Contractor shall update CEAs annually. The Contractor shall format the CEA IAW the latest CEA version as established by the CEA User's Group or as approved by the TMS Program Manager for unique efforts that cannot be accomplished by standard processes.