SOW Hydraulic Scissor Lift Type I II 2011.doc

7 Dec 2011

7 Dec 2011

7 Dec 2011 Statement of Work (SOW) for

Hydraulic Scissor Lift 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 Conference .

3.2.1.1 Post-award conference

3.2.1.2 Guidance conference.

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. Guidance Conference.

3.4.1.3 T.O. verification.

3.4.2 Provisioning.

3.4.3 Training/familiarization.

3.5 Testing and evaluation.

3.5.1 Engineering calculations.

3.5.2 First Article Test (FAT) procedures and report.

3.5.3 User Operational Inspection

3.5.4 Restoration.

3.5.5 Production acceptance procedure and report.

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.8 Human Factors

3.8.1 Human Engineering Simulation Concept

3.8.2 Human Engineering Program Plan

3.8.3 Human Systems Integration Program Plan

3.8.4 Human Engineering Design Approach

3.8.4.1 Analysis Report

3.8.4.2 Operator

3.8.4.3 Maintainer

3.8.5 Human Engineering Tests

3.8.5.1 Test Plan

3.8.5.2 Test Report

1. SCOPE

This document defines the tasks and support requirements for the procurement of Hydraulic Scissor Lift Maintenance Stand as described by PD09WRGBGBEA08 for all Types (Type I – Low Reach and Type II – Medium Reach) of the Scissor Lift Maintenance Platform and is to be used in conjunction with PD09WRGBGBEA08.

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-HFAC-80742B

DI-HFAC-80743B

DI-HFAC-80744B

DI-HFAC-80745B

DI-HFAC-80746B

DI-HFAC-80747B

DI-HFAC-81742

DI-HFAC-81743

Human Engineering Simulation Concept

Human Engineering Test Plan

Human Engineering Test Report

Human Engineering System Analysis Report

Human Engineering Design Approach Document - Operator

Human Engineering Design Approach Document - Maintainer

Human Engineering Program Plan

Human System Integration Program Plan

DI-MFFP-81403

Corrosion Prevention and Control Plan

DI-MGMT-81650

DI-NDTI-80603A

DI-NDTI-80809B

DI-SESS-81000D

DI-SESS-81526B

Integrated Master Schedule (IMS)

Test Procedure

Test/Inspection Report

Product Drawings/Models and Associated Lists

Instructional Media Package

(Unless otherwise specified, 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 Department of Defense (DOD) adopted are those listed in the issue of the Department Of Defense Index of Specifications & Standards (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 quarterly 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 managed in Microsoft Project format and presented to the Government as a PDF 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 Conference.

3.2.1. 1 Post-award conference. The contractor shall host a post award conference within 30 days after contract award. The conference will be between the contractor and Government representatives at Robins Air Force Base facility.

3.2.1. 2 Guidance conference. The contractor shall host a guidance conference within 60 days after contract award. The conference will be between the contractor and Government representatives at Robins Air Force Base facility.

3.2.2 Technical design and program management reviews (PMRs). The contractor shall present information for the preliminary design review (PDR) three (3) months after contract is awarded or at the contractor’s request and as approved by the Government. The contractor shall present information for the critical design review (CDR) six (6) months after the contract is awarded or at the contractor’s request and as approved by the Government. The contractor shall present information for the PMRs quarterly or at the contractor’s request and 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’s facility.

3.2.4 Conference room. The contractor shall provide a conference room suitable for meetings of up to five (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 (5) 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 a 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 (TO) requirements. The contractor shall develop and deliver technical 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.

3.4.1.2 TO Guidance Conference. The contractor shall support and co-chair a TO Guidance Conference within 60 days after contract award. 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. Note: The Guidance Conference may be held in conjunction with other meetings or conferences. (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.

3.4.2 Provisioning. 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 must be consistent with existing government Provisioning data system (D220). The following Data Item Descriptions (DIDs) apply: (DI-ALSS-81529, Provisioning Technical Documentation (PTD): Provisioning Parts List (PPL), Design Change Notices (DCNs), Long Lead Items List (LLIL); DI-ALSS-81557, Supplemental Data For Provisioning (SDFP))

3.4.3 Training/familiarization. The contractor shall provide training courses on the servicing, operational useage, 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 (FAT) procedures and report. The contractor shall develop detailed FAT procedures which must be approved by the Government. The test procedures shall address all requirements identified in the PD09WRGBGBEA08 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 FAT procedures, the contractor shall schedule the testing to be conducted. The contractor shall notify the Government of the date, time, and location of the FAT 30 days prior to the start of testing. The contractor shall submit a FAT report upon completion of the FAT. (DI-NDTI-80603A, Test Procedure; DI-NDTI-80809B, Test/Inspection Report)

3.5.3 User Operational Inspection. After completion of the FAT and approval by the Government of the FAT report, all First Article items shall be shipped for the user operational inspection. All tests shall be completed prior to First Article acceptance. Air Force users will conduct all operaitional inspections at Edwards AFB and Travis AFB, both located in CA. The contractor shall provide a spare parts kit with each item shipped for the user inspection containing all items required to conduct scheduled maintenance during the test as well as common repair parts predicted to be needed during 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 inspection. All user operational inspection shall be completed within the allocated ninety (90) days. The contractor shall be responsible for all costs associated with delivery of the First Article items to and from the contractor's facility and the operational inspection locations.

3.5.4 Restoration. After completion of the First Article and users operational inspection acceptance, the First Article items shall be shipped, within 30 days, to the contractor’s facility for refurbishment. The First Article items shall be shipped to the location(s) specified in the contract. The contractor shall be responsible for any repairs that may be necessary to restore the items to a serviceable condition while retaining configuration integrity. The contractor shall be responsible for all costs associated with delivery of the First Article items to the contractor's facility for refurbishment.

3.5.5 Production acceptance procedure and report. The contractor shall test each production item in accordance with Section 4.4 (Conformance Inspection) of the PD09WRGBGBEA08 utilizing a subset of the FAT procedures. The contractor shall enclose an acceptance test report for each production item. (DI-NDTI-80809B, Test/Inspection Report)

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. 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/maintain and delivers a Technical Data Package (TDP) that accurately depicts the final product. The TDP shall represent the approved, tested, and accepted configuration of the defined delivered item(s). TDP data includes, but is not limited to, Computer Aided Design (CAD) data, CAD models, model based definition data sets, Gerber data and Master Bill of Materials (BOM). The TDP shall provide the necessary design, engineering, manufacturing, testing and quality assurance requirements information necessary to enable the procurement or manufacture of an interchangeable item that duplicates the physical and performance characteristics of the original product without additional design engineering effort or recourse to the original design activity or any third party. All engineering product definition data created as a result of this contract shall be considered a part of the TDP. The TDP shall be delivered in accordance with Air Force Product Data Specification drawing 9579776 (CAGE 98752), reference attached DD Form 1423 Block 16. (DI-SESS-81000D/T)

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

(DI-ADMN-81249A, DI-ADMN-81250A)

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

b. TDP review requirements and schedules.

c. TDP delivery requirements and schedules.

d. Contractor's drafting practices/procedures/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 Technical Data Package (TDP) deliverables.

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

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 (i.e., PDR, CDR). The contractor shall notify WR-ALC/ENGLDC a minimum of 30 days prior to the anticipated date of completion point. The IPR shall focus on the contractor's progress in the preparation of the TDP. The contractor shall support and provide the necessary resources, i.e., meeting agenda, conference room, applicable data, minutes, and appropriate personnel available to answer any questions to perform the IPR effectively. The contractor shall correct all discrepancies identified in the IPR. All subcontractor/vendor data shall be made available for review. If the quantity of subcontractor/vendor data is of sufficient magnitude, the Government may schedule a separate IPR at the subcontractor's/vendor's facility. (DI-ADMN-81249A, DI-ADMN-81250A)

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

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/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/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 EO’s 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 and welding certificates 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 Human factors

3.8.1 Human engineering simulation concept. The contractor shall use mockups and simulators to support any human engineering analysis, design, and test and evaluations. (DI-HFAC-80742B, Human Engineering Simulation Concept)

3.8.2 Human engineering program plan. The contractor shall prepare a program plan for human engineering and explains how the elements are managed. (DI-HFAC-81742, Human Engineering Program Plan)

3.8.3 Human systems integration program plan. The contractor shall manage and incorporate the human systems integration elements with othe r program elements. The contractor will be required to describe the approach and propcedures used to integrate human engineering into the program. (DI-HFAC-81743, Human Systems Integration Program Plan)

3.8.4 Human engineering design approach

3.8.4.1 Analysis report. The contractor shall create a report for all analysis that is used to describe human engineering efforts. (Di-HFAC- 80745B, Human Engineering System Analysis Report)

3.8.4.2 Operator. The contractor shall describe all equipment wihich will require interaction with the operator and how this meets the human engineering criteria. (DI-HFAC-80746B, Human Engineering Design Approach Document-Operator)

3.8.4.3 Maintainer. The contractor shall describe all equipment wihich will require interaction with the maintainer and how this meets the human engineering criteria. (DI-HFAC-80747B, Human Engineering Design Approach Document-Maintainer)

3.8.5 Human engineering tests

3.8.5.1 Test plan. The contractor shall plan for validating the human engineering requirements in support of the operation, maintenance, and support of the system. (DI-HFAC-80743B, Human Engineering Test Plan)

3.8.5.2 Test report. The contractor shall report the findings from the human engineering requirements in support of the operation, maintenance, and support of the system. (DI-HFAC-80744B, Human Engineering Test Report)

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