SOW-FlightControlSysTestSet.pdf

01 March 2011

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

Statement of Work (SOW) for

Test Set, Flight Control Systems

Prepared by

WR-ALC SUPPORT EQUIPMENT AND VEHICLE ENGINEERING DIVISION

460 RICHARD RAY BLVD STE 200

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 orientation conference (PAOC)

3.2.2 Technical reviews

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 System safety

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 verification

3.4.2 Provisioning

3.4.3 Training/familiarization

3.4.3.1 Operation and maintenance orientation

3.4.3.2 Operation and maintenance familiarization/orientation material

3.5 Testing and evaluation

3.5.1 Design analysis

3.5.2 Preproduction test

3.5.2.1 Preproduction test procedures

3.5.2.2 Preproduction testing

3.5.2.3 Preproduction test report

3.5.3 Compatibility testing

3.5.4 Restoration

3.5.5 Disposition

3.6 Configuration management and control

3.6.1 Configuration requirements

3.6.1.1 Production release

3.6.1.2 Product Base Line Index

3.6.2 Engineering Change Proposals (ECPs)

3.6.3 Request for Deviation (RFD)

1. SCOPE

This document defines the tasks associated with the procurement of Test Set, Flight Control Systems as described by PD08WRGBGBEA10 and is to be used in conjunction with

PD08WRGBGBEA10.

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

MIL-PRF-49506 Logistics Management Information

DEPARTMENT OF DEFENSE STANDARDS

MIL-STD-882D Standard Practice for System Safety

DEPARTMENT OF DEFENSE HANDBOOKS

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

MIL-HDBK-29612 Guidance for Acquisition of Training Data Products and Services

2.1.2 Other Government documents, drawings, and publications.

PURCHASE DESCRIPTIONS

PD08WRGBGBEA10 Test Set, Flight Control Systems

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-ILSS-80872 Training Materials 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’s integrated master schedule (see 3.1.5) shall be provided as an attachment 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-80004, 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 orientation conference (PAOC). If the Government determines that a PAOC is necessary, the Government will convene the PAOC with the contractor at a location that is mutually agreeable to both parties, or via teleconference, within 30 days after contract award.

The Procuring Contracting Officer (PCO) will coordinate the actual date, time, and location of the conference with the contractor.

3.2.2 Technical reviews. The Government will convene with the contractor at a location that is mutually agreeable to both parties, or via teleconference, for the test readiness review (TRR) two weeks prior to the start of the preproduction 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 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 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 at a mutually agreeable location or via teleconferences.

3.2.4 Conference room. The contractor shall provide a conference room suitable for meetings of up to 4 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.1 and 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-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 System safety. The contractor shall establish, conduct, document, and maintain a system safety program in accordance with 4.1 through 4.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 TRR; an updated version of the analysis shall be provided with the preproduction test report. (DI-SAFT-81626, System Safety Program Plan;

DI-SAFT-80101, System Safety Hazard Analysis Report)

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 TRR. (DI-MFFP-81403, Corrosion Prevention and Control Plan)

3.4 Logistics.

3.4.1 Technical Order (TO) 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.

(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.

(TM 86-01, Air Force Technical Manual Contract Requirements; DI-MGMT-80227, Contractor's Progress, Status and Management Report)

3.4.1.2 TO verification. Technical order verification shall be in accordance with TM 86-01 at the contractor’s facility. (TM 86-01, Air Force Technical Manual Contract Requirements)

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))

3.4.3 Training/familiarization.

3.4.3.1 Operation and maintenance orientation. The contractor shall plan for conducting classroom and “hands-on” operation and maintenance orientation for up to ten representatives of the using activities to familiarize the user with the Flight Control Systems Test Set, hereafter referred to as test set. The orientation shall be a minimum forty (40) formal classroom training hours. It is recommended, although not mandated, that Instructor-Led Training (ILT) development, evaluation, and documentation be in accordance with MIL-HDBK-29612, Part 2.

The orientation shall include but not be limited to: operational familiarization; maintenance of the Flight Control Systems Test Set for both corrective and preventive efforts; support/test equipment review; test set safety features and procedures; application of technical manual to modes and effects; troubleshooting/fault isolation, and theory of operation. In addition, the contractor shall provide training at their facility of at least a week in length to cover calibration of the test set and associated special tooling. Training shall be provided at the contractor facility or a mutually agreed upon site for a minimum of two AFMETCAL representatives. Upon completion of training, telephone support shall be available for six months during normal duty hours for any calibration concerns encountered. The contractor shall provide all required reference material for DOD personnel from each MDS community, to include a CD-ROM with a digital copy, in Adobe Acrobat (PDF) format for all student support materials, which shall be provided at the conclusion of training to all students (DI-ILSS-80872, Training Materials).

Copies of the latest draft effort in developing the Technical Manual (TM)/Technical Order (TO) for the test set shall also be available and shall be the primary source of data used. The contractor is not required to provide transportation to and from the site, lodging, or meals for the Government personnel during orientation.

3.4.3.2 Operation and maintenance familiarization/orientation material. Operation and maintenance familiarization/orientation material. The contractor shall develop, or facilitate the development of a training product. A master copy of all source files, regardless of authoring platform, original source graphics, and media utilized, and not identified as proprietary by the contractor, shall be provided to support further training product development by the Government.

Examples include, but are not limited to, all HTML/XHTML/DHTML/XML files, Templates, Adobe Flash (both compiled swf and FLA source files), Adobe Dream weaver source files (to include any template files), JAVA source code (to include associated linked library/class files), compiled applets, Javascript/Vbscript code, Cascading Style Sheets (CSS) and a listing of hypertext links shall be included. Furthermore, it is recommended, although not mandated, that all interactive training products be developed, evaluated and documented in accordance with MIL-HDBK-29612, parts 1-5. The interactive multimedia instruction will be used in the field for familiarization of operational and maintenance personnel at the organizational level. The contractor shall also work with the customer representative to ensure proper operation and integration of this courseware into client LMS as required. This training product shall be in sufficient detail to provide the technician adequate skills to operate and provide general maintenance for the up-keep of the test set in the field. This training product shall be subject to preliminary Government approval. The training product shall be subject to final Government approval before final delivery (DI-ILSS-80872, Training Materials).

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. An initial design analysis shall be provided two weeks prior to the TRR, and with the preproduction test report.

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

3.5.2 Preproduction test.

3.5.2.1 Preproduction test procedures. The contractor shall develop detailed preproduction 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. (DI-NDTI-80603, Test Procedure)

3.5.2.2 Preproduction testing. After Government approval of the preproduction 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 preproduction testing 30 days prior to the start of testing.

3.5.2.3 Preproduction test report. The contractor shall submit a preproduction test report upon completion of the preproduction test. (DI-NDTI-80809, Test/Inspection Report)

3.5.3 Compatibility testing. During the preproduction test, a test item shall be shipped to Edwards AFB, CA for compatibility testing in accordance with 4.6 Compatibility Test . Air Force personnel will witness the test; however, contractor personnel shall perform the test. 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.4 Restoration. After completion of preproduction and Compatibility Testing, the preproduction item 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 item to a serviceable, “like new” condition while retaining configuration integrity. The contractor shall be responsible for all costs associated with delivery of the preproduction item to the contractor's facility for restoration.

3.5.5 Disposition. The preproduction item shall be retained at the contractor’s facility, to serve as a manufacturing standard, until the last shipment.

3.6 Configuration management and control.

3.6.1 Configuration requirements.

3.6.1.1 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 preproduction test report has been delivered and approved by the procuring activity.

3.6.1.2 Product Base Line Index. After preproduction acceptance, the contractor shall establish and maintain configuration control. All of the documents used to produce and define the accepted preproduction item 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.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 after production release 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))