SOW.doc

26 March 2009 26 March 2009

26 March 2009 Statement of Work (SOW) for

B-52 Drag Chute Maintenance Stand

Prepared by

642d COMBAT SUSTAINMENT GROUP ENGINEERING DIVISION

460 RICHARD RAY BLVD STE 200

ROBINS AFB GA 31098-1813

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 Non-Government publications.

2.3 Order of precedence.

3. REQUIREMENTS

3.1 Program management.

3.1.1 Program manager.

3.1.2 Integrated master plan (IMP).

3.1.3 Integrated master schedule (IMS).

3.1.4 Plant access.

3.2 Program reviews.

3.2.1 Post-award orientation conference (PAOC).

3.2.2 Technical design and program management reviews (PMRs).

3.2.3 PMR support.

3.2.4 Conference room.

3.2.5 Meeting agendas.

3.2.6 Meeting minutes.

3.3 Corrosion.

3.3.1 Corrosion control.

3.4 Logistics.

3.4.1 Technical Order (T.O.) requirements.

3.4.1.1 Technical Manual schedule and status report.

3.4.1.2 T.O. verification.

3.4.2 Provisioning.

3.4.3 Instructions/familiarization.

3.5 Testing and evaluation.

3.5.1 Engineering calculations.

3.5.2 First article test procedures and report.

3.5.3 Operational inspection.

3.6 Configuration management and control.

3.6.1 Configuration requirements.

3.6.2 Engineering Change Proposals (ECPs).

3.6.3 Request for Deviation (RFD).

3.6.4 Engineering data.

3.6.4.1 Engineering Data Guidance Conference.

3.6.4.2 In-Process Review (IPR) of the TDP.

3.6.4.3 Relationship of the contractor with subcontractors and vendors.

3.6.4.4 Engineering data updates and revisions.

3.7 Welding

3.7.1 Welding procedures

3.7 Warranty

3.7.1 Warranty program

1. SCOPE

This document defines the tasks and support requirements for the procurement of the B-52 Drag Chute Maintenance Stand as described by PD08WRGBGBEA24 and is to be used in conjunction with PD08WRGBGBEA24.

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.

DEPARTMENT OF DEFENSE SPECIFICATIONS

DEPARTMENT OF DEFENSE STANDARDS

DEPARTMENT OF DEFENSE HANDBOOKS

2.1.2 Other Government documents, drawings, and publications.

PURCHASE DESCRIPTIONS

DEPARTMENT OF DEFENSE MANUALS

DATA ITEM DESCRIPTIONS (DIDs)

DI-ALSS-81529

DI-ALSS-81530

Logistics Management Information (LMI) Data Product(s) Data Item Description Logistics Management Information (LMI) Summaries

DI-MGMT-81650

DI-MISC-80875

DI-SESS-81639

Integrated Master Schedule (IMS)

Welding Procedures Warranty Performance Report

(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 Non-Government publications. The following documents form a part of this document to the extent specified herein. Unless otherwise specified, the issues of the documents which are DOD adopted are those listed in the issue of the DODISS cited in the solicitation. Unless otherwise specified, the issues of documents not listed in the DODISS are the issues of the documents cited in the solicitation.

Reliability Information Analysis Center (RIAC)

(Application for copies should be addressed to Reliability Information Analysis Center, 201 Mill Street, Rome NY 13440.)

2.3 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. The contractor shall prepare a monthly contractor’s progress, status and management report. This report shall identify the status of all portions of the contract and shall be identified in the contractor's milestone chart. The program report shall include all events such as reviews, audits, tests, identification, and delivery of the contract line items. (DI-MGMT-80227, Contractor's Progress, Status and Management Report)

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

3.1.3 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. (DI-MGMT-81650, Integrated Master Schedule)

3.1.4 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.2 Program reviews.

3.2.1 Post-award orientation conference (PAOC). The contractor shall host a PAOC within 30 days after contract award. The Government will convene the PAOC with the contractor at Robins AFB.

3.2.2 Technical design and program management reviews (PMRs). The contractor shall host a preliminary design review (PDR) three (3) months after contract is awarded, or at the contractor’s request, as approved by the Government. The contractor shall host a critical design review (CDR) six (6) months after the contract is awarded, or at the contractor’s request as approved by the Government. The contractor shall host PMRs quarterly, or at the contractor’s request, as approved by the Government. PMRs may be held in conjunction with the technical design review meetings. The contractor shall prepare all required detailed status reports for the program and technical design review meetings.

3.2.3 PMR support. The contractor shall participate in and support all reviews, audits, and meetings as requested by the Procuring Contracting Officer (PCO). Reviews shall be held at Robins AFB.

3.2.4 Conference room. A conference room shall provide that is suitable for meetings of up to 5 Government representatives, plus contractor personnel in support of scheduled meetings.

3.2.5 Meeting agendas. The contractor shall publish an agenda for all meetings and conferences specified in 3.2.2. 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-81249A, 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-81250A, Conference Minutes)

3.3 Corrosion.

3.3.1 Corrosion control. The contractor shall establish, conduct, document, and maintain corrosion prevention and control program using MIL-HDBK-1568 for guidance. A corrosion prevention and control plan shall be developed. (DI-MFFP-81403, Corrosion Prevention and Control Plan)

3.4 Logistics.

3.4.1 Technical Order (T.O.) requirements. The contractor shall submit Operation and Operator Maintenance Instruction; Maintenance and Overhaul; and Illustrated Parts Breakdown (IPB) manuals in accordance with 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, Air Force Technical Manual Contract Requirements, and DI-MGMT-80227, Contractor's Progress, Status and Management Report.

3.4.1.2 T.O. verification. Technical order verification shall be in accordance with TM 86-01 at the contractor’s facility.

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 should 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) Topdown Sequence; Design Change Notices (DCNs): DI-ALSS-81557, Supplemental Data For Provisioning (SDFP): DI-ALSS-81530, Data Item Description Logistics Management Information (LMI) Summaries)

3.4.3 Instructions/familiarization. The contractor shall provide instructional courses on the servicing, operational usage, adjustments, and troubleshooting for this unit. (DI-SESS-81526B, Instructional Media Package)

3.5 Testing and evaluation.

3.5.1 Engineering calculations. The contractor shall complete all supporting engineering calculations for the design, development, and production of this unit. All supporting engineering calculations, both formal and informal, shall be provided to the Government. (DI-GDRQ-80650, Design Data and Calculations)

3.5.2 First article test procedures and report. The contractor shall develop detailed first article test procedures which must be approved by the Government. The test procedures shall address all test requirements identified in PD08WRGBGBEA24 and this SOW. The test procedures shall include data record sheets, charts, graphs, identification of test instruments by manufacturer, model number, and serial number. After approval of the first article test procedures, the contractor shall schedule the testing to be conducted. The contractor shall notify the Government of the date, time, and location of the first article testing 30 days prior to the start of testing. The contractor shall submit a first article test report upon completion of the first article test. (DI-NDTI-80603A, Test Procedure; DI-NDTI-80809B, Test/Inspection Report)

3.5.3 Operational inspection. After completion of the first article testing and approval by the Government for the first article test report, the first article test unit shall be shipped to Barksdale AFB for an operational inspection. The operational inspection shall be completed prior to the first article acceptance. Air Force users will conduct all operational inspections which includes Validation/Verification of the T.O.s. The contractor shall provide all manuals and any additional items required for the users to complete the operational inspection. Contractor’s support must be available within 48 hours of notification (exclusive of weekends and official Government holidays) any time during the user OT&E. All operational inspections shall be completed within the allocated five (5) days.

3.6 Configuration management and control.

3.6.1 Configuration requirements. After the first article item acceptance, the contractor shall establish and maintain configuration control. The accepted first article items shall not serve as the manufacturing standard. All of the documents used to produce and define the accepted first article items shall be identified in a Product Base Line Index. The list shall identify the applicable version number as required. (DI-CMAN-81218, Product Base Line Index (PBLI))

3.6.2 Engineering Change Proposals (ECPs). After the Product Baseline is released, the contractor shall incorporate all changes to master drawing baseline via approved ECPs. A Notice of Revision (NOR) shall be submitted with each ECP. (DI-CMAN-80639C, Engineering Change Proposal (ECP); DI-CMAN-80642C, Notice of Revision (NOR)).

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

3.6.4 Engineering data. The contractor shall develop, produce, and maintain a Technical Data Package (TDP) that accurately depicts the final product. The TDP shall provide the necessary design, engineering, manufacturing, testing and quality assurance requirements information necessary to enable the procurement or manufacture of an interchangeable item that duplicates the physical and performance characteristics of the original product, without additional design engineering effort or recourse to the original design activity. Product data shall reflect the approved, tested, and accepted configuration of the defined delivered item. All engineering data created as a result of this contract shall be considered a part of the TDP. This data includes, but is not limited to CAD data, models and model based definition data sets, and Gerber data. (DI-SESS-81000C/T)

3.6.4.1 Engineering Data Guidance Conference. The contractor shall support and co-chair a Guidance Conference for engineering data within 60 days after contract award. The Conference shall be convened at Robins AFB on a date agreed upon by the Government contracting officer and the contractor. The contractor shall prepare an agenda and record the minutes of the Guidance Conference. The contractor shall address, discuss, and provide status on the following:

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

b. TDP review requirements and schedules.

c. TDP delivery requirements and schedules.

d. The contractor's drafting practices, procedures, and TDP drawing formats.

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

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

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

h. Digital TDP deliverables.

Note: The Guidance Conference may be held in conjunction with other meetings or conferences. (DI-ADMN-81249A, Conference Agenda; DI-ADMN-81250A Conference Minutes)

3.6.4.2 In-Process Review (IPR) of the TDP. The contractor shall host, support, and co-chair an IPR of the engineering drawings and associated lists and other documentation to be included in the TDP. The IPR shall be conducted only after the contractor's quality assurance personnel have completely reviewed the data and determined that data are of sufficient quality that Government time will be effectively utilized during the review. IPR may be scheduled when data has reached the 50 percent completion point and shall be held, when possible, in conjunction with other reviews (e.g., PDR or CDR). The contractor shall notify 584 CBSS/GBHCC a minimum of 30 days prior to the anticipated date of completion point. The IPR shall focus on the contractor's progress in the preparation of the TDP. The contractor shall support and provide the necessary resources: meeting agenda, conference room, applicable data, minutes, and appropriate personnel available to answer any questions to perform the IPR effectively. The contractor shall correct all discrepancies identified in the IPR. All subcontractor and vendor data shall be made available for review. If the quantity of subcontractor or vendor data is of sufficient magnitude, the Government may schedule a separate IPR at the subcontractor's or vendor's facility. (DI-ADMN-81249A, Conference Agenda; DI-ADMN-81250A, Conference Minutes)

3.6.4.3 Relationship of the contractor with subcontractors and vendors. The contractor shall levy on sub-contractors and sub-vendors the same requirements for TDPs as are levied on them by this contract. This requirement shall apply at all tiers of sub-contractor/vendor levels associated with the program.

3.6.4.4 Engineering data updates and revisions. The contractor shall (and shall cause subcontractors and vendors to) update and maintain engineering data for the item(s) designed, developed, modified, and produced by this contract for the life of this contract and shall incorporate all changes in accordance with the following:

a. All engineering changes shall be incorporated into the applicable engineering data within 90 days after engineering release and Air Force concurrence or at intervals of five changes, whichever occurs first, except a change involving safety, which shall be incorporated immediately.

b. All engineering changes shall be incorporated into the applicable engineering data prior to delivery of data for review.

c. All engineering changes shall be incorporated into the applicable engineering data prior to delivery of final media (this includes all Engineering Orders (EOs) generated as a result of the preliminary data review).

3.7 Welding.

3.7.1 Welding procedures. The contractor shall establish, conduct, document, and maintain all welding procedures using AWS D1.1 and AWS D1.2 for guidance. All welding procedures utilized on the stand shall be submitted to the Government for approval. (DI-MISC-80875, Welding Procedures)

3.8 Warranty.

3.8.1 Warranty program. The contractor shall supply a one-year standard material and workmanship warranty for this program. The contractor shall provided all information (including but not limited to the telephone numbers, addresses, electronic mail addresses and the points of contact) for warranty issues, technical assistance and any routine and/or emergency services. (DI-SESS-81639, Warranty Performance Report) DISTRIBUTION STATEMENT A. Approved for public release: Distribution is unlimited.