Attachment0001PWSRevised01Oct2015.docx

IMPROVED TURBINE ENGINE

PERFORMANCE WORK STATEMENT (PWS)

Version: 2

Prepared by:

Future Vertical Lift Project Office 5304 Patton Road Redstone Arsenal, AL 35898

TABLE OF CONTENTS

01 OCTOBER 15

vi

GENERAL INFORMATION

SCOPE

This Performance Work Statement (PWS) defines the effort required for the planning, design and development of the Improved Turbine Engine (ITE) through Preliminary Design Review (PDR) and a post-PDR analysis phase. The use of the term Government in this document references the United States Government.

BACKGROUND

The ITE will be developed as a new centerline engine using emerging technology that will result in a qualified engine replacement for the current Black Hawk and Apache aircraft which currently use a turbo-shaft engine of the T700 family of engines. The T700 engine was developed and qualified during the 1970s and provides propulsion power to the Black Hawk and Apache aircraft, as well as a number of other Department of Defense and other Government agency aircraft. Various derivative models of the engine have been subsequently developed and approved, the latest version being the T700-GE-701D engine.

The intent of the ITE is to fill the capability gap as described in the Operational Energy for Sustained Ground Operations Initial Capability Document (OEICD) in Black Hawk and Apache performance requirements by designing an affordable engine with a reduction in fuel consumption and decreased sustainment costs as compared with the legacy engine. The OEICD identifies Army aviation capability gaps as lacking sufficient endurance to conduct persistent and dispersed missions, lacking energy sources that provide sufficient power to enable operations for extended times without sustainment and that the force cannot decrease collective system energy demands without a reciprocal decrease in endurance and performance for sustained operations and an increased demand on sustainment capabilities The ITE effort is focused on developing a new turboshaft engine, incorporating advanced technology to support modernization requirements necessary to ensure the Black Hawk and Apache remain operationally effective well into the 21st century.

APPLICABLE DOCUMENTS

Applicable top level documents are contained in Attachment A, Contract Document Summary List (DSL), by number, title, and date. The document versions in the DSL take precedence over the generic references (without revision letters) cited in this PWS.

REQUIREMENTS

The Contractor shall furnish the personnel, services, facilities, equipment, software, hardware, and material to design and develop an ITE in accordance with (IAW) the requirements of the ITE System Requirements Document (SRD), Specification Development Document (SDD), and this PWS. The ITE SRD establishes overall engine performance and verification requirements for qualification and acceptance by the Government for Preliminary Flight Rating (PFR), Qualification Rating (QT), and Operational Capability Release (OCR). The SDD establishes the content and format to be used by the Contractor to prepare the proposed Engine Model Specification (EMS). The SRD and SDD contain performance, airworthiness and qualification requirements for the ITE that shall be included in the EMS. The EMS delivered at proposal will replace the SDD at contract award. The Contractor shall conduct activities necessary to mature all critical technologies for the ITE design to a Technology Readiness Level (TRL) of 6. The contract requirement is a Government approved Preliminary Design Review (PDR) substantiated with all critical technologies demonstrated to TRL 6 and approved post-PDR activities referenced in paragraph 3.3.5.

PROGRAM MANAGEMENT

The Contractor shall implement Schedule, Cost, Risk and Financial Management procedures. The procedures shall support development of a Post Award Conference, In-Process Reviews in terms of location, agenda and format. Schedule products shall be event driven Program Schedules/Networks based upon detailed schedules, with milestones having achievement criteria listed for each requirement. The Contractor shall utilize an Earned Value Management System (EVMS), as well as a systematic approach for implementing Cost as an Independent Variable (CAIV). The Contractor shall develop and implement a Risk Management Plan. Financial Management approach with its associated cost reporting procedures shall be implemented by the Contractor.

The Contractor shall develop a Program Management Plan (PMP) for the ITE Program IAW DI-MGMT-81797 and deliver IAW CDRL A001. The Contractor shall provide the management resources required to execute the ITE Program IAW the approved PMP. Monthly Technical Status Progress Reports shall be submitted IAW DI-MGMT-80555 and delivered IAW CDRL A002.

The Contractor shall be responsible for providing real-time database access to the following:

a. Integrated Master Schedule

b. Dynamic Object Oriented Requirements Management System (DOORS) or equivalent

c. Risk

d. Drawings

e. Models

f. Earned Value Management

g. Configuration Management engine/software/programmable hardware

h. Quality Management System

i. Critical Safety Items

j. Configuration Status Accounting (CSA) The Contractor shall provide up to two (2) seats with read only access for each of the above databases to facilitate program execution. The Contractor shall provide real-time database access to the databases a-j of paragraph 3.1 of this PWS IAW DI-MISC-80508 and deliver IAW CDRL A018. A centralized file, computer data base, or document called a “Hazard Log” shall be maintained by the Contractor and made available to the Government upon request.

Coordination and Reviews Post Award Conference The Contractor shall conduct a Post Award Conference within 30 days of contract award at the Contractor’s facility, to include contract personnel, management, and IPTs with U.S. Government participation. The Contractor, in conjunction with the Government, shall develop a detailed agenda prior to the meeting. In this meeting, the Contractor shall discuss the PWS and how they intend to accomplish all aspects of the PWS, discuss any gaps, issues and concerns, and identify and address any potential risks. The Contractor shall identify the critical technologies of their ITE preliminary design, their present Technology Readiness Level (TRL), and their plan to achieve TRL 6. The Contractor shall describe how the project will be run and managed; discuss expectations and the deliverables, and technical and management reviews. The Contractor shall introduce the project team, and roles and responsibilities for each role. The Contractor shall discuss risks, issues and change management, how risks will be handled and mitigated, and how changes and change orders will be handled and executed. The Contractor shall discuss trade studies to explore opportunities to increase system performance while implementing Cost as an Independent Variable (CAIV) principles for the ITE design. The Contractor shall prepare Post Award Conference agenda and briefing charts IAW DI-MGMT-81605 and deliver IAW CDRL A003-001. The Contractor shall prepare Post Award Conference minutes and action items IAW DI-ADMN-81505 and deliver IAW CDRL A003-002.

Integrated Program Reviews The Contractor shall conduct quarterly Integrated Program Reviews (IPR) that address cost, schedule, technical progress, product assurance and program progress assessments. The Contractor shall conduct two (2) meetings per year at the Contractor’s facility and two (2) meetings per year at the Government’s facility. The Contractor shall provide in-depth information on program progress and status to include cost, schedule (with milestones), integrated logistics support, technical performance, and risk management. The Contractor shall describe those accomplishments and issues that have occurred since last review. Data regarding the monthly personnel loading together with cost projections and actual performance against those projections shall be included. The review shall include the current status of their major Subcontractors. In addition an executive summary shall present the status of cost, schedule, integrated logistics support, product support, and technical performance. The Contractor, in conjunction with the Government, shall develop a detailed agenda prior to the IPR. Action items stemming from each review shall be recorded in the minutes and will be reported on at subsequent reviews. The initial IPR shall be conducted NLT 60 days following the Post Award Conference. Technical/System level reviews (see Section 3.2.6) will be in lieu of IPRs. The Contractor shall prepare an IPR agenda and briefing charts IAW DI-MGMT-81605 and deliver IAW CDRL A003-003. The Contractor shall prepare IPR minutes and action items IAW DI-ADMN-81505 and deliver IAW CDRL A003-004.

Integrated Baseline Review The Contractor shall host an Integrated Baseline Review (IBR), NLT 90 days after contract award for the purpose of joint (Government/Contractor) approval of the Performance Measurement Baseline (PMB). Additional IBRs may be conducted if the Contractor is unable to demonstrate performance management competency IAW EVM guidelines or if events significantly change the project's baseline. The PMB shall be the basis for the Integrated Program Management Report (IPMR), as described in paragraph 3.1.5, against which the entire contract effort shall be measured. This includes Contractor/Subcontractor award schedules/status, resource assignments, integrated master schedules, budgets and work authorization documents sufficient to account for all technical scope, schedule and budget. The Contractor, in conjunction with the Government, shall develop a detailed agenda NLT thirty (30) days prior to all IBR sessions and prepare IBR agenda and briefing materials IAW DI-MGMT-81605 and deliver IAW CDRL A003-005. The Contractor shall prepare IBR minutes and action items IAW DI-ADMN-81505 and deliver IAW CDRL A003-006. The IBR is considered approved by the Government when all of the associated CDRLs and action items have been approved and resolved. The Government retains the rights to allow for specific exceptions and will provide such exceptions to the Contractor at time of Government approval of all associated CDRLs and action items.

Integrated Product Teams (IPTs) The Contractor shall utilize the Integrated Product Teams (IPT) process in the management of this effort. The Contractor shall provide the services of a Project Manager and IPT to interface with the Government Product Manager and shall designate co-leads for all ITE system IPTs. IPTs shall be made an integral part of all aspects of this effort and, as such, shall identify associated achievement criteria and detailed descriptions of procedures to be used to satisfy requirements. It is the Government’s intent that working level issues be coordinated through the IPT co-leads.

The Contractor shall participate in IPT teleconference calls with the Government at least once a week. The Contractor and Subcontractor project leads and subject matter experts shall discuss cost and performance, program progress, schedule status, program requirements, program risks, programmatic and technical issues/concerns, and project execution.

The Product Management Working Group (PMWG) The Contractor shall participate in the ITE PMWG. The PMWG shall be responsible for developing, on schedule, an affordable (in terms of lifecycle costs) system that meets the requirements outlined in this PWS and the SRD. The PMWG co-leads are the Government and Contractor Product Managers. The primary IPT co-leads shall participate in the PMWG as team members. The team shall work together to manage the ITE Program. This includes management oversight of all program and milestone decision review documentation, schedules, contracting activities and progress throughout the system’s lifecycle. Its principal objectives are:

· Ensuring and supporting an acquisition strategy that defines program objectives. Prioritizing activities and resource requirements. Team members shall identify activities and required resources. The IPT co-leads are responsible for prioritizing activities and resourcing them in a manner consistent with the acquisition strategy, program plans and this contract.

· Identifying and reducing risk related to management, technical, cost, schedule, and product support. This objective shall be met through an integrated approach across the IPTs to identify and assess risk and develop courses of action to mitigate that risk.

· Resolving issues and questions at the system level, monitoring program status, progress, and issues, and maintaining an open dialogue with Government PM and Contractor management and other ITE program stakeholders as needed.

Associate Contractor Agreements The Contractor shall establish and maintain Associate Contractor Agreements (ACA) with the H-60 and AH-64 Original Equipment Manufacturer (OEM)s and other contractor sources to facilitate the integration with the engine system. Each ACA shall define the specific areas of responsibility for the Contractors and shall be the basis for ensuring that the technical, hardware, and software interfaces between the ITE system are established and maintained. The Contractor shall integrate IAW interface and integration requirements as documented by the ACA unless otherwise agreed to through the IPT process. Representative ACAs and schedules/status for completion shall be presented as part of the Post Award Conference IAW paragraph 3.1.1.1. Final signed ACAs shall be presented at the initial IPR for Product Management Working Group (PMWG) IPT concurrence. The Contractor shall notify the PMWG IPT of any changes or modifications to the ACAs.

Contract Work Breakdown Structure Indexes and Dictionaries The Contractor, and any subcontractors who meet the reporting thresholds, shall utilize the draft Contract Work Breakdown Structure (CWBS) shown on the Cost and Software Data Reporting (CSDR) Plan, DD Form 2794 (Appendix C, Attachment B). Currently this is in draft format but will be approved by the Office of the Secretary of Defense (OSD) Cost Assessment and Program Evaluation (CAPE) for the ITE. This CWBS shall be used as the reporting structure for planning, estimating, monitoring, reporting, of cost, schedule, and technical performance. Unless lower levels are needed due to risks the Contract CSDR Plans shall identify WBSs to Level 4. The Contractor, and any subcontractors who meet the reporting thresholds, shall provide CWBS indexes and dictionaries prepared IAW DI-MGMT-81334 and delivered IAW CDRL A004. The Contractor may extend the CWBSs to lower levels for its own internal purposes. The extended CWBS shall include an index and dictionary prepared IAW DI-MGMT-81334 and delivered IAW CDRL A004.

Not Used.

Earned Value Management The Contractor shall manage the entire budgeted scope of the contract (both Government and Contractor shares, and identified as such) IAW DoD 5000.02 requirements for Earned Value Management (EVM). The Contractor shall collect cost performance data including; Budgeted Cost of Work Scheduled (BCWS), Budgeted Cost of Work Performed (BCWP), and Actual Cost of Work Performed (ACWP) at the CWBS levels at the direction of the Government and flow down applicable requirements to all Subcontractors. The Contractor shall establish, maintain, and utilize in the execution of this contract an Earned Value Management System (EVMS) that meets the requirements of DoD 5000.02, Due to the EVMS requirement, an Integrated Baseline Review (IBR) is required. The Contractor shall submit electronic copies of all Control Account Manager (CAM) Notebooks IAW DI-MISC-80508 and deliver IAW CDRL A006. Additionally, the Contractor shall prepare an Integrated Program Management Report (IPMR) IAW DI-MGMT-81861 and deliver IAW CDRL A007.

Cost as an Independent Variable (CAIV) The Contractor shall implement CAIV as an integral part of managing and decision making for the total ITE effort. The Contractor shall implement a CAIV process which models the relationship between cost and requirements, in order to define potential trade space. Contractor shall describe how CAIV related activities shall be included in all decision making. The Contractor shall participate with the Government through the IPT process to implement the best practices and methodologies in order to minimize total life cycle ownership costs while meeting the technical requirements of the program.

Cost Forecasting The Contractor shall provide cost forecasting data associated with the production and direct maintenance costs of the ITE IAW DI-MISC-80508 and delivered IAW CDRL A008. Cost forecasting shall be determined at the module component level, and then further detailed down to the component level. Cost reduction initiatives and design to cost activities shall be fully explained. Components obtained from suppliers should reflect the supplier proposal costs to the greatest extent possible. Direct maintenance costs shall be based upon preliminary design impact on previously calculated component reliability and condition based maintenance implementation.

Financial Management/Reports Contract Funds Status Reports The Contractor shall prepare Contract Funds Status Reports (CFSR) IAW DI-MGMT-81468 and deliver IAW CDRL A009. This deliverable is in addition to the EVM IPMR requirement.

Contractor Cost Data Reports The Contractor shall systematically collect and report actual contract costs (both Government and Contractor shares and identified as such) to provide Government cost analysts with data needed to estimate future costs. Contractor reports shall be prepared IAW the CWBSs defined in the CAPE approved Cost and Software Data Reporting (CSDR) Plans (Appendix C, Attachment B). The Contractor shall develop a Cost Data Summary Report (DD Form 1921) IAW DI-FNCL-81565 and deliver IAW CDRL A010. The Contractor shall develop a Functional Cost-Hour Report (DD Form 1921-1) IAW DI-FNCL-81566 and deliver IAW CDRL A011.

Contractor Business Data Report The Contractor shall prepare a Contractor Business Data Report (DD Form 1921-3) IAW DI-FNCL-81765 and deliver IAW CDRL A013. The Contractor shall flow down requirements for the DD Form 1921-3 to Subcontractors performing work on contracts which contain CDSR requirements. Only one DD Form 1921-3 submission is required per business entity, independent of the number of contracts with CSDR requirements held by the business entity.

Contractor Cost and Software Data Reporting Conference A Contractor Cost and Software Data Reporting (CSDR) Conference between the Contractor and the Government shall be held within ninety (90) days of contract award to review all CCDR content to include any need for mapping from the Contractor’s accounting system into the required CCDR functional categories, the recurring and nonrecurring classifications, delivery dates, electronic reporting requirements, Subcontractor flow-down requirements, and the process for addressing any reports from the prime and Subcontractors that might be rejected. The Conference shall be held at the Contractor’s facility. Any agreements made during the CSDR Conference will be made by the Government in a revised OSD CAPE approved Contract CSDR Plan(s), approved by OSD CAPE and placed on contract in a subsequent contract modification. The Contractor shall provide the following representation:

· Contractor Financial Manager

· Contractor Financial Analyst responsible for completion of reports

· Contractor Engineer/Technical Representative

· Major Subcontractors’ representatives

· Attendance by the Contractor Program Manager is required Contractor Manpower Reporting The Office of the Assistant Secretary of the Army (Manpower & Reserve Affairs) operates and maintains a secure Army data collection site where the Contractor shall report all Contractor manpower required for performance of this contract.

The Contractor shall report ALL Contractor labor hours (including Subcontractor labor hours) required for performance of services provided under this contract for the planning, design and development of the ITE via a secure data collection site. The Contractor is required to completely fill in all required data fields using the following web address: http://www.ecmra.mil/, and then click on “Department of the Army CMRA” or the icon of the DoD organization that is receiving or benefitting from the contracted services.

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

The required information includes:

a. Contracting Office, Contracting Officer, Contracting Officer’s Technical Representative;

b. Contract number, including task and delivery order number;

c. Beginning and ending dates covered by reporting period;

d. Contractor name, address, phone number, e-mail address, identity of Contractor employee entering data;

e. Estimated direct labor hours (including Subcontractors);

f. Estimated direct labor dollars paid this reporting period (including Subcontractors;

g. Total payments (including Subcontractors):

h. Predominant Federal Service Code (FSC) reflecting services provided by Contractor (and separate predominant FSC for each Subcontractor if different);

i. Estimated data collection cost;

j. Organizational title associated with the Unit Identification Code (UIC) for the Army Requiring Activity (the Army Requiring Activity is responsible for providing the Contractor with its UIC for the purposes of reporting this information);

k. Locations where Contractor and Subcontractors perform the work (specified by zip code in the United States and nearest city, country, when in an overseas location, using standardized nomenclature provided on website);

l. Presence of deployment of contingency contract language; and

m. Number of Contractor and Subcontractor employees deployed in theater this reporting period (by country).

The Contractor Manpower Reporting shall be IAW DI-MISC-80508 and delivered IAW CDRL A021.

Project Risk Management Plan The ITEP system Product Manager has established risk management as an integral part of the program management concept. The Contractor shall use risk abatement and management as a continuous, pro-active process that concentrates on early identification and control of program risk areas. Program areas are evaluated in terms of technical performance, cost and schedule to address the total system and considering lifecycle impacts.

The Contractor shall implement and execute Risk Management to identify and mitigate program risks in the areas of cost, schedule, performance and supportability to include definition of risk measurements and objectives, identification, classification, and reporting for all cost, schedule, and technical performance risks. Risk management shall be implemented at all program and system levels. The Contractor shall execute the Risk Management Program and identify risk mitigation activities for all moderate and high-risk areas. The Contractor shall make available risk assessments and risk mitigation status through the IPT process. Risk management shall be an integral part of all reviews, meetings, and IPTs.

The Contractor shall develop an ITE Risk Management Plan (RMP) that details the risk management approach; describes any prior risk reduction activities; quantifies the known and potential risk areas within the program; and documents continuous risk control, handling, and reduction efforts. The integrated risk management approach defined within the RMP shall address four major areas planning, assessment, handling, and monitoring. The RMP shall serve as a “guidance tool” to enhance the IPT structured approach to integration, qualification and test, production, and fielding activities in their efforts to reduce the inherent risks of system integration, producibility, and supportability. The Contractor shall develop the ITE Risk Management Plan IAW DI-MGMT-81808 and deliver IAW CDRL A017.

Patent Application The Contractor shall submit all related patent applications to the Government Contracting Activity (GCA) for security review and proper coordination. Prior to submission to the Patent and Trademark office, the Contractor shall submit all ITE related patent applications through the Contracting Officer for review and determination of the appropriate classification level and data rights. Patent applications shall be classified and submitted to the Patent and Trademark Office as appropriate. The Government will receive a license for use of any and all patents and trademarks.

Engineering, Manufacturing and Development Phase Proposal The Contractor shall prepare and deliver a proposal to execute the Engineering and Manufacturing Development (EMD) phase for the ITEP. The proposal shall address all labor, materials, facilities, equipment, supplies, and travel necessary to meet the requirements of the ITEP EMD PWS. The proposal shall be submitted IAW DI-FNCL-81116 and delivered IAW CDRL A019.

Long Lead Items For EMD planning purposes, the Contractor shall prepare a report IAW DI-MISC-80508 and deliver IAW CDRL C005 that identifies a preliminary list of long lead items based upon the final preliminary design.

SYSTEM ENGINEERING

System Engineering Process The Contractor shall apply a Systems Engineering (SE) process to produce the supportable and affordable design baselines that are verifiable from functional baselines for the engine system, as described herein. The Contractor shall document, implement, control, and maintain a collection of technical plans, processes, and schedules to guide the project toward accomplishment of its objectives and proper conclusion.

System Engineering Management Plan The Contractor shall develop a System Engineering Management Plan (SEMP) that describes the technical approach and proposed plan for the conduct, management, and control of the integrated SE effort.

The Contractor shall describe the planned SE approach to meeting the program’s contract, requirements, and overall technical and management approach. The Contractor shall describe the detailed operational plan for executing SE down to the Subcontractor and supplier level. The Contractor shall use the Office of the Deputy Assistant Secretary of Defense for Systems Engineering (ODASD(SE)) Systems Engineering Plan (SEP) Preparation Guide to prepare the SEMP using the following website: http://www.acq.osd.mil/se/pg/guidance.html. The Contractor shall include the following in the SEMP:

The Contractor shall include other areas not mentioned above as deemed necessary to execute SE to meet the program’s contract, objectives and overall technical and management approach.

The SEMP shall be developed IAW DI-SESS-81785 and delivered IAW CDRL B001.

Configuration Management Program The Contractor shall establish and implement a Configuration Management (CM) program to manage the configurations produced under this contract, using EIA-649, ISO 10007, and MIL-HDBK-61 as guides. A CM IPT, with the Government as chair, shall be utilized for resolving CM issues and in the performance of change management activities. The Contractor shall implement a Configuration Data Management (CDM) system that shall control the configuration of all components and interfaces of the ITE. The Contractor's CDM system shall address the following elements: administration; configuration identification, change control; configuration status accounting (CSA); interface management; data management; and, subcontractor CM for all hardware, software, firmware and documentation for the duration of this contract.

Configuration Management Plan The Contractor shall develop a Configuration Management Plan (CMP). The CMP shall identify the procedures, tools, methods, standards, and interfaces to be used in conjunction with configuration items. The CMP shall describe the organization, procedures and methodology employed by the Contractor for the lifecycle of the ITE Program. Process and lifecycle objective evidence shall be recorded and made available to support contractual requirements and be available for review by the Government during all phases of the Contractor’s performance. The CMP shall include methods for identifying configurations, schedules for identifying configuration, baseline configuration establishment methods, baseline traceability, and methods for writing and closing associated problem reports. The CMP shall identify methods for change control, methods for change review, methods for approval/disapproval and other status, and methods for recording, reporting, and retrieving configuration status. The CMP shall identify the integrity controls, release methods, release authority, and data retention for configurations. The CMP shall define the process by which software is transferred from its configuration managed repository and embedded into its target computer. The Control System hardware shall be an integral part of the Engine System CMP. The Contractor’s data management system and plan shall be an integral part of the Configuration Management system and shall be documented in the CMP. The Contractor shall develop a data management plan that describes the organization, procedures and methodology employed by the Contractor for the lifecycle of the ITE Program. The Contractor shall address Interface Management within the CMP. The Contractor shall develop a CMP for the ITE program IAW DI-CMAN-80858 and deliver IAW CDRL B002. The Programmable Hardware Configuration Management Plan (HCMP) shall be included in the Software Configuration Management Plan (SCMP) (3.4.7).

Configuration Item List The Contractor shall, with Government participation, select the Configuration Items (CIs), including hardware CIs (HWCIs) and computer software CIs (CSCIs), to be identified and assign hierarchical identifiers to each CI, select the configuration documentation to be used to identify each CI and define and document interfaces between CIs. A specific CSCI embedded in a specific HWCI shall result in a unique CI. The Contractor shall maintain on a current basis the CI list. The Contractor shall develop the CI List IAW DI-SESS-81879 and deliver IAW CDRL B003.

Configuration Identification and Documentation The configuration identification for the ITE program shall be the configuration of hardware, software and firmware which allows for provisioning and procurement of spare parts, manufacturing, retrofit, installation, test, inspection, qualification, and acceptance of the ITE program and its components defined in the Functional Baseline (FBL), and Allocated Baseline (ABL).

Functional Baseline Functional Baseline Documentation The Engine Model Specification (EMS) delivered with the proposal shall become the functional baseline.

Functional Baseline Control The Contractor shall maintain the EMS and shall submit specification change notices to communicate changes to the Government. The Government will have change control authority of the EMS and shall review and approve the Specification Change Notices SCNs accordingly. The Contractor shall develop (SCNs) for proposed changes to the EMS IAW DI-CMAN-80643 and deliver IAW CDRL B005.

Allocated Baseline Allocated Configuration Documentation The Contractor shall prepare the Allocated Configuration Documentation (ACD) for each CI previously agreed upon jointly by the Government and Contractor. The Contractor shall prepare separate configuration documentation, shall have separate formal control of the changes; have separate configuration status accounting records and separate configuration audits for each of the CI’s. The ACD documentation shall consist of product specifications, interface control documentation and software requirements documentation as described in paragraph 3.2.6.5, 3.2.4.1 and 3.4.1.2. The ABL specifications shall be IAW DI-IPSC-81431 and delivered IAW CDRL B004.

Allocated Baseline Control The Contractor shall maintain the ACD and shall submit specification change notices (SCNs) to communicate changes to the Government. The Government will have change control authority of the ACD and will review and approve the SCNs accordingly. The Contractor shall develop SCNs for proposed changes to the EMS IAW DI-CMAN-80643 and deliver IAW CDRL B005.

Change Control Process The Contractor shall develop a change control process that manages the preparation, justification, evaluation, coordination, disposition and implementation of proposed engineering changes and deviations to affected configuration items (CIs) and baselined configuration documentation on the ITE program.

Configuration Status Accounting All baselines, Engineering Change Proposals (ECPs), and deviations shall be documented in the Contractor’s configuration status accounting database. Configuration Status Accounting (CSA) Database shall include the ability for the Government user to perform programmed and ad-hoc queries of the database to retrieve the required data, to view the retrieved data, and to download the retrieved data for local storage and printing. The Contractor shall develop Configuration Status Accounting (CSA) Information IAW DI-CMAN-81253 and deliver IAW CDRL B006.

Interface Management The Contractor shall ensure interface definition and compliance among the elements of the ITE system, as well as with H-60M and AH-64E Platforms. The Contractor shall ensure that all internal and external interface requirement changes are properly documented IAW the configuration management plan and aligned with all affected configuration items. The Contractor shall document the interface requirements in Interface Control Documentation including Interface Control Drawings, Interface Requirements Specifications and other documentation that depicts the physical and functional interfaces of related or co-functioning systems or components. The Contractor shall ensure compliance of the ITE interfaces with the H-60 and AH-64E platform envelope and mechanical interface drawing requirements described in Appendix A of the SRD.

Airframe/Engine Interface Control Document The Contractor shall prepare an Airframe/Engine Interface Control Document (ICD) IAW DI-CMAN-81248 and SAE AIR6181 and deliver IAW CDRL B007 for each of the proposed airframe integrations (H-60M and AH-64E). The Airframe/Engine ICD shall detail the mechanical and electrical interfaces (including data buses) between the engine and the aircraft. This document shall also provide the Installation Drawing which will include vibration and temperature limits.

Control System Interface Control Document The Contractor shall prepare a Control System Interface Control Document (CS-ICD) IAW DI- CMAN-81248 and deliver IAW CDRL B008. The control system ICD (CS-ICD) shall detail all hardware, software, and communication bus interfaces between all engine control system components.

Interface Control Working Group The Contractor shall participate in the Interface Control Working Group (ICWG). The ICWG is a specialized technical working group composed of subject matter experts (SME) from the interfacing activities and other interested participating organizations. The ICWG serves as a forum to develop and provide interface requirements, as well as to focus on interface detail definition and resolution of issues.

Not Used Not Used Classified Information The contractor shall mark and handle all CD’s containing classified information IAW DODI 5220.22.

Data Accession List The Contractor shall prepare a Data Accession List (DAL) IAW DI-MGMT-81453 and deliver IAW CDRL B009. The DAL shall segment hardware and software items for clarity purposes. Upon notification from the Procuring Contracting Officer (PCO), the Contractor shall furnish a copy of any requested documentation contained in this list IAW DI-MISC-80508 and deliver IAW CDRL B010.

Technical/System Level Reviews The Contractor shall conduct ITE system level reviews/meetings that address: IPT progress, program status, performance of Subcontractors, CAIV, trade studies, cost and schedule goals, resource loading, technical performance, Technical Performance Measures (TPMs), software progress, risk management, configuration management, process validation, producibility, corrosion prevention, path ahead to meeting objective requirements, and entrance/exit criteria for each system level review. System level reviews are described in the paragraphs below with entrance and exit criteria listed in Appendix A.

Engine System Requirements Review The Contractor shall conduct the System Requirements Review (SRR) to demonstrate the system requirements are identified and that both the Government and the Contractor are in mutual agreement. The Contractor shall demonstrate the system requirements are suitable and achievable to guide a Preliminary Design that it is balanced with cost, schedule, risks and technology readiness. The Contractor shall demonstrate that the system requirements satisfy the operational and suitability requirements and the system architecture and allocation of system requirements to architectural elements (CIs, subsystems).

The Contractor shall schedule the Engine SRR once the lower level SRRs (ECSC SRR, SWRR) are completed unless the Government approves combining lower level SRRs. The Engine SRR shall be scheduled once the actions are adjudicated and the CDRLs shall be approved or deemed acceptable by the Government for entering the review. The Contractor shall hold the Engine SRR at the Contractors facility or some other Government approved venue that is beneficial to the program.

Engine System Requirements Review Entrance Criteria The Contractor shall meet the entrance criteria IAW Appendix A.1 and the associated CDRLs. The Contractor shall coordinate the agenda for the Engine SRR with the project lead at the IPT meetings NLT thirty (30) days prior to the review. The Contractor shall prepare SRR briefing materials IAW DI-MGMT-81605 and deliver IAW CDRL B011-001. The presentation shall address all of the items listed in the SRR entrance criteria per Appendix A.1.

Engine System Requirements Review Exit Criteria The SRR shall be concluded when the exit criteria IAW Appendix A.1 is met, as approved by the Government. The Contractor shall prepare SRR minutes and action items IAW DI-ADMN-81505 and deliver IAW CDRL B012-001. The SRR briefing material shall be updated IAW DI-MGMT-81605 and delivered IAW CDRL B011-001.

Engine Control System Component System Requirements Review The Contractor shall conduct the Engine Control System Component System Requirements Review (ECSC SRR) at the Contactors or Sub-Contractors facility. The Contractor shall ensure the engine control system requirements, the system requirement relationships, and the qualification approach of the system requirements are all defined and approved by the Government. The ECSC SRR shall demonstrate progress in converging on viable, traceable system requirements that are balanced with cost, schedule, risks and technology readiness.

The Contractor shall conduct the ECSC SRR with the objective of reviewing and approving the ECSC technical description, including its requirements and architecture to establish the system controls requirements. The Contractor shall demonstrate the control system requirements are suitable and achievable to guide Preliminary Design. The Contractor shall demonstrate that the system requirements satisfy the operational and suitability requirements. The Contractor shall also demonstrate that the system architecture and allocation of system requirements are in compliance with the architectural elements (CIs, subsystems).

The Contractor in the ECSC SRR shall cover all control system and subsystem elements, at the Contractors or Sub-Contractors facility, after the SRR entrance criteria have been satisfied. The ECSC SRR may be conducted at the same time as the Engine SRR.

Engine Control System Component System Requirements Review Entrance Criteria Prior to conducting ECSC SRR, the Contractor shall submit technical products for hardware and software systems IAW this PWS as stated in Appendix A.3 and…