StatementWork_1022377_00_1.doc

19 January 2010

19 January 2010 Statement of Work (SOW)

For

COMMON MULTI-PLATFORM BORESIGHT SYSTEM (CMBS)

Prepared by

642d COMBAT SUSTAINMENT GROUP ENGINEERING DIVISION

460 RICHARD RAY BLVD STE 200

ROBINS AFB GA 31098-1813

TABLE OF CONTENTS

1. SCOPE

1.1 Classification

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 Publication

2.3 Order of Precedence

3. REQUIREMENTS

3.1 Program management

3.1.1 Program manager

3.1.2 Plant access

3.1.3 Production release

3.1.4 Conflict of requirements

3.2 Program reviews

3.2.1 Post-award orientation conference (PAOC)

3.2.2 Technical design and program management reviews (PMRs)

3.2.2.1 Preliminary Design Review

3.2.2.2 Critical Design Review

3.2.3 Program Management Review Support

3.2.4 Conference room

3.2.5 Meeting agendas

3.2.6 Meeting minutes

3.2.7 Monthly status report

3.3 System engineering

3.3.1 System safety

3.3.2 Corrosion control

3.4 Logistics

3.4.1 Provisioning

3.4.2 Technical Order (T.O.) requirements

3.4.2.1 Technical Manual schedule and status report

3.4.2.2 T.O. verification

3.5 Training/familiarization

3.5.1 Operation and maintenance orientation

3.5.1.2 Operation and maintenance familiarization/orientation material

3.5.1.3 Government Rights

3.5.2 Software documentation and data deliverables

3.5.2.1 Executable code

3.5.2.2 Software version description document

3.5.2.3 Automated Computer Program Identification Number (ACPIN) Data and

Control Record

3.6 Testing and evaluation

3.6.1 Design analysis

3.6.2 Preproduction test procedures and reports

3.6.3 Users Operational Test and Evaluation (OT&E)

3.6.4 Refurbishment

3.6.5 Production acceptance procedure and report

3.7 Configuration management and control

3.7.1 Configuration requirements

3.7.2 Commercial parts

3.7.3 Engineering Change Proposals (ECPs)

3.7.4 Request for Deviation (RFD)

3.7.5 Production release

3.7.6 Engineering data

3.7.6.1 Engineering Data Guidance Conference

3.7.6.2 In-Process Review (IPR) of the TDP

3.7.6.3 Relationship of the contractor with subcontractors and vendors

3.7.6.4 Engineering data updates and revisions

4 Transportation

1. SCOPE

This document defines the tasks and support requirements for the procurement of the Common Multi-Platform Boresight System (CMBS), as described by PD09WRGBGBEB12 and is to be used in conjunction with PD10WRGBGBEB08.

1.1 Classification. The CMBS will be use to align the critical weapon and aircraft avionics to the aircraft reference centerline in order to harmonize the systems for peak warfighting operation. Boresighting is performed when excessive G-Loads or unusually violent maneuvers occur, where there is a hard landing, where there has been aircraft structural damage or repairs performed, where the pilot reports a discrepancy, when timed scheduled Boresight is required, or where local aircraft maintenance has determined there is a need.

2. APPLICABLE DOCUMENTS. The following documents are applicable to the SOW to the extent specified herein. NOTE: The term First Article and Preproduction Kits will be use interchangeably throughout the PD and this SOW.

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-217F (2)

Reliability Prediction of Electronic Equipment

MIL-HDBK-29612-3A

Development of Interactive Multimedia Instruction (IMI) (Parts 1-5)

MIL-HDBK-470 (A)

Designing and Developing Maintenance Products and Systems

MIL-HDBK-472

Maintenance Prediction

2.1.2 Other Government documents, drawings, and publications.

PURCHASE DESCRIPTIONS

PD09WRGBGBEB12

Common Multi-Platform Boresight System PD10WRGBGBEB08 F-15/16 Adapters

DEPARTMENT OF DEFENSE MANUALS

TM 86-01N

Air Force Technical Manual Contract Requirements DATA ITEM DESCRIPTIONS (DIDs)

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-SAFT-81626

System Safety Program Plan DI-ILSS-80872 Training Materials

DI-MCCR-80700 Computer Software Product End Item

DI-IPSC-81442A Software Version Description

DI-MISC-81454B Automated Computer Program Identification Number (ACPIN) Data and Control Record

DI-ALSS-81529/T Logistics Management Information (LMI) Data Product(s)

DI-SESS-81000D/T Product Drawings/Models and Associated List

DI-ILSS-81335 Design Review Data Package (Copies of these documents are available online at http://assist.daps.dla.mil/quicksearch/ or www.dodssp.daps.mil or from the Standardization Document Order Desk, 700 Robins Avenue, Building 4D, Philadelphia, PA 19111-5094.)

2.2 Non-Government Publications. The following documents form a part of this document to the extent specific 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)

NPRD-95

Non-electronic Parts Reliability Data 1995

(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 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 Production release. The contractor assumes all risks in initiating production before the Government has approved the preproduction test reports, and that any deficiencies from the User Operational Test and Evaluation (OT&E) have been corrected.

3.1.4 Conflict of requirements. In the event of any conflict of requirements specified herein, the conflict shall be referred to the PCO for resolution. If a difference in interpretation of contract requirements exists as specified herein between the contractor and any Government representative, the contractor shall seek clarification from the PCO.

3.2 Program reviews.

3.2.1 Post-award orientation conference (PAOC). PAOC shall be held promptly after contract award at Robins AFB GA at a time and date mutually agreed upon by both parties.

3.2.2 Technical design and program management reviews (PMRs). 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. (DI-ADMN-81249A, Conference Agenda, DI-ADMN-81250A, Conference Minutes)

3.2.2.1 Preliminary Design Review (PDR). The contractor shall be responsible for conducting a Preliminary Design Review (PDR) on the design of the CMBS unit. The PDR shall be held at Robins AFB. The contractor shall be responsible for including but not limited to preparing the PDR agenda, submission of required documentation to the Government prior to PDR, preparation and distribution of PDR meeting minutes, and any action items resulting from the PDR event. At the conclusion of PDR, the Government will approve the contractor's design with any preliminary calculations and or models, integration, and installation information when all data has been determined to be acceptable. The contractor shall not proceed to the Critical Design Review (CDR) until the Government has approved PDR. (DI-ADMN-81249A, Conference Agenda, DI-ADMN-81250A, Conference Minutes, DI-ILSS-81335, Design Review Data Package)

3.2.2.2 Critical Design Review (CDR). The contractor shall be responsible for conducting a CDR to present the final design of the CMBS unit. The contractor shall host the CDR at its facility. The contractor shall be responsible for including but not limited to preparing the CDR agenda, submission of any required documentation to the Government before CDR, preparation and distribution of CDR meeting minutes, and any action items resulting from the CDR event. At the conclusion of CDR, the Government will approve the contractor's final design to include applicable equations, calculations and three dimensional drawings, when all data has been determined to be acceptable. (DI-ADMN-81249A, Conference Agenda, DI-ADMN-81250A, Conference Minutes, DI-ILSS-81335, Design Review Data Package)

3.2.3 Program Management Review 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 the contractor’s facility or a mutually agreeable location.

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.

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 include as directed 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. The contractor shall submit meeting minutes no later than ten days after meeting in accordance with DD from 1423. (DI-ADMN-81250A, Conference Minutes)

3.2.7 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 task, issues, actions, deliverables, and expenditure status. Problem areas shall be identified with proposed solutions and outcomes. The current program master schedule (see 3.1.2) shall be provided as an attachment to the monthly status report. (DI-MGMT-80227, Contractor’s Progress, Status and Management Report)

3.3 System 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. (DI-SAFT-81626, System Safety Program Plan; DI-SAFT-80101B, System Safety Hazard Analysis Report)

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

3.4 Logistics.

3.4.1 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). Topdown Sequence, Long Lead Items List (LLIL): LLIL-SAIP (Items recommended for Spares Acquisition Integrated with Production and not later than 165 days prior to contractor’s order need date or as determined at the PGC), Design Change Notices (DCNs): (DI-ALSS-81529/T Logistics Management Information (LMI) Data Product(s)).

3.4.2 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-01N, Air Force Technical Manual Contract Requirements.

3.4.2.1 Technical Manual schedule and status report. The Technical Manual schedule and status report shall be in accordance with TM-86-01N, Air Force Technical Manual Contract Requirements, and DI-MGMT-80227, Contractor's Progress, Status and Management Report.

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

3.5 Training/familiarization

3.5.1 Operation and maintenance orientation. The contractor shall plan for and conduct classroom and “hands-on” operation and maintenance orientation for the using F-15/16 and AFMETCAL activities (approximately 20 Government personnel), to familiarize the users with the CMBS. 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 CMBS for both corrective and preventive efforts; support/test equipment review; CMBS safety features and procedures; application of technical manual to modes and effects; troubleshooting/fault isolation, and theory of operation. This training should also cover the calibration of the CMBS and associated special tooling. 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 CMBS 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 DOD personnel during the orientation.

3.5.1.2 Operation and maintenance familiarization/orientation material. The contractor shall develop 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 CMBS 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.1.3 Government rights. The contractor shall extend to the Government unlimited usage rights for the duplication and distribution of the operation and maintenance familiarization/orientation material (CD-ROM) identified in 3.5.1.2 The contractor may identify to the Government any specific proprietary materials or items needing to be limited due to proprietary rights.

3.5.2 Software documentation and data deliverables.

3.5.2.1 Executable code. The executable code shall be compatible with a standard PC running the existing Air Force Standard Desktop Configuration (SDC). The contractor shall own the executable code and shall manage and make in-house revisions/updates as necessary including updates to training materials. The contractor shall notify the Government of any and all revisions/updates. The Government pledges to protect the contractor proprietary information embodied in the code and will not disclose this information to a third party contractor without the contractor’s approval. The Government shall have the right to reproduce and distribute the software to users as necessary. (DI-MCCR-80700, Computer Software Product End Items)

3.5.2.2 Software version description document. The contractor shall submit a software version description document. (DI-IPSC-81442A, Software Version Description)

3.5.2.3 Automated Computer Program Identification Number (ACPIN) Data and Control Record. The contractor shall request a Computer Program Identification Number (CPIN) for any software configuration entity to be delivered to the Government to support the CMBS. To request a CPIN from the Government all custom and/or commercial software packages shall be labeled independently and described thoroughly on AF Forms 1243 in accordance with TO 00-5-16 guidelines. (DI-MISC-81454B, Automated Computer Program Identification Number (ACPIN) Data and Control Record)

3.6 Testing and evaluation.

3.6.1 Design analysis. A design analysis of the system and each subsystem shall be performed to verify compliance with this SOW and the PD. The initial design analysis shall be provided at the PDR; updated versions of the analysis shall be provided at the CDR, at the start of preproduction testing, and with the preproduction test report. The contractor shall be responsible for the transportation and cost associated with the transportation of the preproduction unit to Nellis AFB. (DI-MISC-80508B, Technical Report/Study Services)

3.6.2 Preproduction test procedures and report. The contractor shall develop detailed preproduction test procedures which must be approved by the Government. The test procedures 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. After completion of the contractor in-plant testing of the preproduction unit, the contractor shall submit a preliminary test report to the Government due ten (10) days after contractor testing, government will have thirty (30) days to approve/disapprove test report. Upon receipt of the Government’s written approval to proceed to OT&E, the contractor shall ship the preproduction Boresight unit to Nellis AFB for user OT&E. Subsequent to testing at Nellis AFB, the contractor shall submit a final test report to the Government. (DI-NDTI-80603, Test Procedure; DI-NDTI-80809B, Test/Inspection Report)

3.6.3 User Operational Test and Evaluation (OT&E). Testing of the CMBS will be conducted at Nellis AFB, NV. After completion of preproduction test and approval by the Government of the preliminary preproduction test report, all preproduction items shall be shipped for the user OT&E. Air Force users will conduct all tests. The contractor shall provide a spare parts kit with each item shipped for the user OT&E containing all items required to conduct scheduled maintenance during the test as well as common repair parts predicted to be needed during the OT&E. Contractor’s support must be available (within 48 hours of notification exclusive of weekends and official Government holidays) all time during the user OT&E. All user OT&E shall be completed within allocated ninety (90) days. All tests shall be completed prior to the preproduction acceptance. Subsequent to OT&E, the contractor shall prepare a final test report for government review and approval.

3.6.4 Refurbishment. After completion of preproduction and users OT&E acceptance, the preproduction items shall shipped, within 30 days, to the contractor’s facility for refurbishment/calibration and certification. One preproduction item shall be retained at the contractor’s facility until the last shipment. The remaining preproduction items shall be shipped to the location 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 the transportation and costs associated with the transportation of the preproduction unit from Nellis AFB back to the contractor's facility for refurbishment.

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

3.7 Configuration management and control.

3.7.1 Configuration requirements. After the preproduction system acceptance, the contractor shall establish and maintain configuration control. The accepted preproduction items shall serve as the manufacturing standard. All of the documents used to produce and define the accepted preproduction 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.7.2 Commercial parts. The contractor shall use standard common commercial parts in the design and fabrication of the CMBS to the maximum extent possible without adversely affecting performance.

3.7.3 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.7.4 Request for Deviation (RFD). Notwithstanding any other provisions 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 approved in writing by ECP or request for deviation/waiver submitted to the Government Program Manager. Any request for change shall be accompanied by complete documentation supporting the need for change. (DI-CMAN-80640C, Request for Deviation (RFD))

3.7.5 Production release. Production release is acknowledgment by the Government that the contractor has satisfied all requisites to proceed with delivery of hardware to be furnished under the contract. Production release is contingent upon successful completion of all preproduction testing, examination and approval of the preproduction test report.

3.7.6 Engineering data. The contractor shall develop/produce/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 product definition 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-81000D/T, Product Drawings/Models and Associated List]

3.7.6.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 a site 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:

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.7.6.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, 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 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.7.6.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.7.6.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).

4 TRANSPORTATION. For acquisition purposes, the transportation requirements shall be specified in the contract or order.

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