StatementOfWork.pdf

DISTRIBUTION STATEMENT A. Approved for public release: Distribution is unlimited.

10 June 2013

Statement of Work (SOW) for

ETU-8/E and ETU-9/E Engine Trailers

Prepared by

AFLCMC SUPPORT EQUIPMENT AND VEHICLE ENGINEERING DIVISION

235 BYRON ST, STE 19A

ROBINS AFB GA 31098-1813

THIS PAGE HAS BEEN INTENTIONALLY LEFT BLANK

TABLE OF CONTENTS

1. SCOPE

2. APPLICABLE DOCUMENTS

2.1 Government documents

2.1.1 Specifications, standards, and handbooks

2.1.2 Other Government documents, drawings, and publications

2.2 Order of precedence

3. REQUIREMENTS

3.1 Program management

3.1.1 Program manager

3.1.2 Plant access

3.1.3 Monthly status report

3.1.4 Integrated master plan (IMP)

3.1.5 Integrated master schedule (IMS)

3.2 Program reviews

3.2.1 Post-award conference (PAC)

3.2.2 Technical reviews

3.2.2.1 Design reviews

3.2.2.1.1 Design review location and schedule

3.2.2.1.2 Design review content

3.2.2.2 Test readiness review

3.2.2.3 Technical review documentation

3.2.3 Program Management Review support

3.2.4 Conference room

3.2.5 Meeting agendas

3.2.6 Meeting minutes

3.3 Systems engineering

3.3.1 Environment, Safety, and Occupational Health (ESOH)

3.3.1.1 System safety

3.3.1.2 Hazardous materials

3.3.2 Corrosion control

3.4 Logistics

3.4.1 Technical Order (TO) requirements

3.4.1.1 Technical Manual schedule and status report

3.4.1.2 TO Guidance Conference

3.4.1.3 TO verification

3.4.2 Provisioning

3.4.2.1 Provisioning Guidance Conference……………………………………………..9

3.5 Testing and evaluation

3.5.1 Design analysis

3.5.2 First article test

3.5.2.1 First article test procedures

3.5.2.2 First article testing

3.5.2.3 First article test daily situation reports (SITREPs)

3.5.2.4 Compatibility testing

3.5.2.5 First article test report

3.5.3 Restoration

3.5.4 Disposition

3.6 Configuration management

3.6.1 Configuration requirements

3.6.1.1 Baselines

3.6.1.1.1 Functional baseline

3.6.1.1.2 Allocated baseline

3.6.1.1.3 Product baseline

3.6.1.2 Production release

3.6.2 Engineering Change Proposals (ECPs)

3.6.3 Request for Deviation (RFD)

1. SCOPE

This document defines the tasks and support requirements for the procurement of the ETU-8/E and ETU-9/E engine trailers as described by PD08WRGBGBEB16 and is to be used in conjunction with PD08WRGBGBEB16.

2. APPLICABLE DOCUMENTS

The following documents are applicable to the SOW to the extent specified herein.

2.1 Government documents.

2.1.1 Specifications, standards, and handbooks. The following specifications, standards, and handbooks of the exact revision listed below form a part of this SOW to the extent specified herein.

FEDERAL STANDARDS

FED-STD-313D(1) Material Safety Data, Transportation Data, and Disposal Data for Hazardous Materials Furnished to Government Activities

DEPARTMENT OF DEFENSE SPECIFICATIONS

MIL-PRF-49506 Logistics Management Information

DEPARTMENT OF DEFENSE STANDARDS

MIL-STD-882E System Safety

DEPARTMENT OF DEFENSE HANDBOOKS

MIL-HDBK-1568 Material and Processes for Corrosion Prevention and Control in Aerospace Weapons Systems

2.1.2 Other Government documents, drawings, and publications.

PURCHASE DESCRIPTIONS

PD08WRGBGBEB16,

Rev. B

Aircraft and missile engine lift trailers

DEPARTMENT OF DEFENSE GUIDES

(no identifier) Risk Management Guide for DoD Acquisition, Sixth Edition, Version 1.0

DEPARTMENT OF DEFENSE MANUALS

TM-86-01N Air Force Technical Manual Contract Requirements

DATA ITEM DESCRIPTIONS (DIDs)

DI-MGMT-80004A Management Plan DI-SAFT-80101B System Safety Hazard Analysis Report DI-MGMT-80227 Contractor's Progress, Status and Management Report DI-MISC-80508B Technical Report/Study Services DI-NDTI-80603A Test Procedure DI-CMAN-80639C Engineering Change Proposal (ECP) DI-CMAN-80640C Request for Deviation (RFD) DI-CMAN-80642C Notice of Revision (NOR) DI-NDTI-80809B Test/Inspection Report DI-CMAN-81218 Product Base Line Index (PBLI) DI-ADMN-81249A Conference Agenda DI-ADMN-81250A Conference Minutes DI-MFFP-81403 Corrosion Prevention and Control Plan DI-ALSS-81529 Logistics Management Information (LMI) Data

Product(s) DI-ALSS-81557 Supplemental Data for Provisioning (SDFP) DI-SAFT-81626 System Safety Program Plan DI-MGMT-81650 Integrated Master Schedule (IMS)

(Unless otherwise indicated, copies of the above specifications, standards, and handbooks are available from the Standardization Document Order Desk, 700 Robbins Avenue, Building 4D, Philadelphia PA 19111-5094.)

2.2 Order of precedence. In the event of a conflict between the text of this document and the references cited herein, the text of this document takes precedence. Nothing in this document, however, supersedes applicable laws and regulations unless a specific exemption has been obtained.

3. REQUIREMENTS

3.1 Program management.

3.1.1 Program manager. The contractor shall identify to the Government and maintain a single point of contact (Program Manager) for all matters under this contract. The contractor shall also ensure that all program management personnel assigned to the program shall be available, as required, to meet program objectives.

3.1.2 Plant access. The contractor shall arrange for full access to applicable contractor facilities and offices by Government representatives conducting any business, making observations, or performing inspections required by public law or by this contract.

3.1.3 Monthly status report. The contractor shall submit a monthly status report that shall cover the engineering and technical development of the system and subsystems as well as a projection of planned work for the remaining effort. Reports shall document tasks, issues, actions, deliverables, and expenditure status. Problem areas shall be identified with proposed solutions and outcomes. The current program integrated master schedule (IMS) (see 3.1.5) shall be provided as attachments to the monthly status report. (DI-MGMT-80227, Contractor's Progress, Status and Management Report)

3.1.4 Integrated master plan (IMP). The contractor shall implement and maintain the proposed IMP for this program. (DI-MGMT-80004A, Management Plan)

3.1.5 Integrated master schedule (IMS). The contractor shall implement and maintain the proposed IMS for this program. A baseline IMS shall be developed at the start of the program.

A current IMS shall be developed and maintained throughout the program, using the original baseline schedule as an unchanging reference. The IMS shall be provided in Microsoft Project format as an attachment to the monthly status report (see 3.1.3). (DI-MGMT-81650, Integrated Master Schedule)

3.2 Program reviews.

3.2.1 Post-award conference (PAC). The Government will convene a PAC with the contractor at Robins AFB within 30 days after contract award. The Procuring Contracting Officer (PCO) will coordinate the actual date and time of the conference with the contractor.

3.2.2 Technical reviews.

3.2.2.1 Design reviews.

3.2.2.1.1 Design review location and schedule. The contractor shall conduct a preliminary design review (PDR) 90 days after the contract is awarded. The PDR review shall be held via teleconference. The contractor shall conduct a critical design review (CDR) 150 days after the contract is awarded, that shall be held at the contractor’s facility. The PCO will coordinate the actual date and time of the reviews with the contractor.

3.2.2.1.2 Design review content. The PDR and CDR shall include formal technical reviews of the proposed design; program risks shall be reviewed on a technical and schedule basis. Each review shall include, but is not limited to, preliminary calculations; any necessary design studies or analyses including the design analysis as required in 3.5.1; preliminary drawings, including equipment layout drawings (packaging), proprietary or restricted design processes, components, and information; electrical and mechanical design; environmental control; thermal design aspects; software design; training materials; lists of materials, parts, and processes; human engineering elements; corrosion control; maintainability; production capability and manufacturing; and quality considerations. Final drawings, final calculations, and any mockups or any assemblies shall be made available for the Government review as well. All applicable comments from the PDR shall be incorporated into the CDR design documentation.

3.2.2.2 Test readiness review (TRR). The contractor shall conduct a test readiness review (TRR) two weeks prior to the start of the first article test. The TRR shall assess test objectives, test methods and procedures, scope of tests, and determine if required test resources have been properly identified and coordinated to support planned tests. The TRR shall be held via teleconference. The PCO will coordinate the actual date and time of the reviews with the contractor.

3.2.2.3 Technical review documentation. The contractor shall prepare all necessary detailed status reports for the technical review meetings, conference agendas, and conference minutes.

The contractor shall prepare formal documentation of the PDR, CDR, and TRR.

(DI-MISC-80508, Technical Report/Study Services)

3.2.3 Program Management Review support. The contractor shall participate in and support all reviews, audits, and meetings as requested by the PCO or the contractor. Program Management Reviews shall be conducted quarterly or as required via teleconferences.

3.2.4 Conference room. The contractor shall provide a conference room suitable for meetings of up to 15 Government representatives, plus contractor personnel, in support of scheduled meetings at the contractor’s facility.

3.2.5 Meeting agendas. The contractor shall publish an agenda for all meetings and conferences specified in 3.2.2 and 3.2.3. The contractor shall request from the Government any items or issues to be discussed or presented at the meetings, and shall include such items in the agenda.

Agendas shall be submitted not less than five working days prior to any meeting.

(DI-ADMN-81249, Conference Agenda)

3.2.6 Meeting minutes. The contractor shall provide a written record of the discussions, decisions and action items identified at each meeting. (DI-ADMN-81250, Conference Minutes)

3.3 Systems engineering.

3.3.1 Environment, Safety, and Occupational Health (ESOH).

3.3.1.1 System safety. The contractor shall establish, conduct, document, and maintain a system safety program in accordance with 4.3.1 through 4.3.8 of MIL-STD-882. The contractor shall initiate changes in the system design based on safety analysis results such that the associated risk is reduced to a level acceptable to the Government. An initial system safety hazard analysis shall be provided two weeks prior to the CDR; updated versions of the analysis shall be provided two weeks prior to the TRR and with the first article test report. (DI-SAFT-81626, System Safety Program Plan; DI-SAFT-80101, System Safety Hazard Analysis Report).

3.3.1.2 Hazardous materials. The contractor shall manage hazardous materials, including those embedded in the system or used during operation or maintenance, as an element of the Systems Engineering process. The contractor shall list any hazardous materials, as defined in FED-STD-313, to be delivered under this contract, including locations, quantities, and special handling and disposal procedures.

3.3.2 Corrosion control. The contractor shall establish, conduct, document, and maintain a corrosion prevention control program using MIL-HDBK-1568 for guidance. An initial corrosion prevention and control plan shall be provided two weeks prior to the PDR; the second submission of the plan shall be provided two weeks prior to the CDR. (DI-MFFP-81403, Corrosion Prevention and Control Plan)

3.4 Logistics.

3.4.1 Technical Order (TO) requirements. The contractor shall develop and deliver technical manuals in accordance with TM-86-01, Air Force Technical Manual Contract Requirements.

(TM-86-01, Air Force Technical Manual Contract Requirements)

3.4.1.1 Technical Manual schedule and status report. The Technical Manual schedule and status report shall be in accordance with TM-86-01.

3.4.1.2 TO Guidance Conference. The contractor shall support and co-chair a TO Guidance Conference within 30 days after contract award. The PCO will coordinate the actual date and time of the Guidance Conference with the contractor. The contractor shall prepare an agenda and record the minutes of the Guidance Conference. Note: The Guidance Conference may be held in conjunction with other meetings or conferences or via teleconference.

(DI-ADMN-81249, Conference Agenda; DI-ADMN-81250 Conference Minutes)

3.4.1.3 TO verification. Technical order verification shall be in accordance with TM-86-01 at the contractor’s facility or compatibility test location.

3.4.2 Provisioning. The contractor shall identify and recommend logical spare/repair parts sufficient to meet system/equipment operation and supportability in accordance with the Air Force Initial Provisioning Performance Specification (IPPS). MIL-PRF-49506 shall be used as a guide. Format shall be consistent with existing Government Provisioning data system (D220).

(DI-ALSS-81529, Provisioning Technical Documentation: Provisioning Parts List (PPL) Top down Sequence; Design Change Notices (DCNs): DI-ALSS-81557, Supplemental Data For Provisioning (SDFP).

3.4.2.1 Provisioning Guidance Conference. The contractor shall support and co-chair a Provisioning Guidance Conference at Robins AFB, GA or via teleconference at a date and time mutually agreeable to both parties. The PCO will coordinate the actual date, time, and location of the Guidance Conference with the contractor. The contractor shall prepare an agenda and record the minutes of the Guidance Conference. (DI ADMN 81249, Conference Agenda; DI ADMN 81250 Conference Minutes)

3.5 Testing and evaluation.

3.5.1 Design analysis. A design analysis of the system and each subsystem shall be performed to verify compliance with this SOW and each applicable requirement of the PD. The analysis shall include, but is not limited to, a service life analysis (see 4.5.3 of the PD, a snow load analysis (see 4.5.4.6 of the PD, a surface transportability analysis (see 4.5.6.1.1 of the PD), an air transportability analysis (see 4.5.17 of the PD), and a tie down provision analysis (see 4.5.19 of the PD). (Note that the system safety hazard analysis is addressed in 3.3.1). An initial design analysis shall be provided two weeks prior to the PDR; updated versions of the analysis shall be provided two weeks prior to the CDR, two weeks prior to the TRR, and with the first article test report. (DI-MISC-80508, Technical Report/Study Services)

3.5.2 First article test.

3.5.2.1 First article test procedures. The contractor shall develop detailed first article test procedures, which shall address all requirements identified in the PD and this SOW. The test procedures shall include data record sheets, charts, graphs, identification of test instruments by manufacturer, model number, and serial number. The test procedures shall address modeling and simulation (M&S); if M&S is not applicable, the test procedures shall be so noted.

(DI-NDTI-80603, Test Procedure)

3.5.2.2 First article testing. After Government approval of the first article test procedures, the contractor shall schedule the testing to be conducted. If shipping is required to move the item(s) to and from a test site away from the contractor’s facility, the contractor shall be responsible for all costs associated with the shipment. The contractor shall notify the Government of the date, time, and location of first article testing 30 days prior to the start of testing. The test will be witnessed by one or more Government representatives.

3.5.2.3 First article test daily situation reports (SITREPs). Throughout the first article test, the contractor shall submit a daily situation report (SITREP) that shall cover all monitored daily test activities. Examples are:

a. Test logs.

b. Observed data to include: Observations, comments, anomalous conditions, or other items completed for each first article unit.

c. Recorded data as applicable to the type of equipment.

d. Records of preventive maintenance activities performed.

(DI-MGMT-80227, Contractor's Progress, Status and Management Report)

3.5.2.4 Compatibility testing. During the first article test, a test item (one of each type) shall be shipped to Seymour Johnson AFB for compatibility testing in accordance with PD compatibility test (see 4.5.21 of the PD). The duration of this test will be 5 days. Air Force personnel will perform the test and any required maintenance; contractor personnel shall witness the test and maintenance and advise the Air Force personnel. At the conclusion of the compatibility test, the test item shall be shipped to the contractor’s facility. The contractor shall be responsible for all costs associated with shipping the item to the compatibility test location and returning it to the contractor’s facility.

3.5.2.5 First article test report. The contractor shall submit a first article test report upon completion of the first article test. The test report shall document all testing performed, including results of any unsuccessful test attempts. Failure reports generated as a result of the FRACAS process (see 4.4.4 of the PD shall be included with results of unsuccessful test attempts. (DI-NDTI-80809, Test/Inspection Report).

3.5.3 Restoration. After completion of first article acceptance, the first article engine trailers shall be shipped, within 30 days, to the contractor’s facility for restoration. The contractor shall be responsible for any repairs that may be necessary to restore the engine trailers to a serviceable, “like new” condition while retaining configuration integrity. The contractor shall be responsible for all costs associated with shipping of the first article engine trailers to the contractor's facility for restoration.

3.5.4 Disposition. The first article engine trailers shall be shipped to the location(s) specified in the contract.

3.6 Configuration management.

3.6.1 Configuration requirements.

3.6.1.1 Baselines.

3.6.1.1.1 Functional baseline. The functional baseline is the Purchase Description.

3.6.1.1.2 Allocated baseline. All of the documents used to produce and define configuration at the conclusion of the TRR shall constitute the allocated baseline.

3.6.1.1.3 Product baseline. All of the documents used to produce and define the accepted first article engine trailers shall be identified in a Product Base Line Index (PBLI). The list shall identify the applicable version number as required. (DI-CMAN-81218, Product Base Line Index

(PBLI))

3.6.1.2 Production release. Production release is acknowledgment by the procuring activity that the contractor has satisfied all requirements to proceed with delivery of hardware to be furnished under the contract. The contractor assumes all risks in initiating production before the first article test report has been delivered and approved by the procuring activity.

3.6.2 Engineering Change Proposals (ECPs). Notwithstanding any other provision in the contract, no contractor or subcontractor's change in design, fabrication, assembly, part, material, process, or source of supply shall be made to the allocated or product baseline unless such change is submitted in writing by ECP and approved by the procuring activity. Any request for change shall be accompanied by complete documentation supporting the need for the change. A Notice of Revision (NOR) shall be submitted with each ECP. (DI-CMAN-80639, Engineering Change Proposal (ECP); DI-CMAN-80642, Notice of Revision (NOR)).

3.6.3 Request for Deviation (RFD). The contractor shall prepare an RFD whenever a departure from the contractually-specified base line is proposed for a specific number of units or for a specific time. (DI-CMAN-80640, Request for Deviation (RFD)).