SOW.pdf

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

17 MAY 2017

Statement of Work (SOW) for

7-1/2 TON DOLLY SET

NSN 2330-01-661-5190

Prepared by

SUPPORT EQUIPMENT AND VEHICLE 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.2 Conferences and program reviews

3.2.1 Postaward conference

3.2.2 Program Management Review support

3.2.3 Conference room

3.2.4 Meeting agendas

3.2.5 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 Risk management

3.4 Logistics

3.4.1 Technical Order (TO) requirements

3.4.1.1 Technical manual schedule and status report

3.4.2 Commissioning

3.5 Testing and evaluation

3.5.1 First production test

3.5.1.1 First production test procedures

3.5.1.2 First production testing

3.5.1.3 First production test report

3.5.2 Restoration

3.5.3 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 Variance (RFV)

3.6.4 Service bulletin

3.6.5 USAF Registration Numbers

1. SCOPE

This document defines the tasks associated with the procurement of the 7-1/2 Ton Dolly Set

Mobilizer as described by A-A-59981 and is to be used in conjunction with A-A-59981.

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 STANDARDS

MIL-STD-882E System Safety

MIL-STD-1223AC NOT1 Nontactical Wheeled Vehicles Treatment, Painting, Identification Marking and Data Plate Standards

2.1.2 Other Government documents, drawings, and publications.

DATA ITEM DESCRIPTIONS (DIDs)

DI-SAFT-80101C System Safety Hazard Analysis Report (SSHAR)

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

DI-MISC-80508B Technical Report/Study Services

DI-NDTI-80603A Test Procedure

DI-SESS-80639D Engineering Change Proposal (ECP)

DI-SESS-80640D Request for Variance (RFV)

DI-SESS-80642D Notice of Revision (NOR)

DI-NDTI-80809B NOT 1 Test/Inspection Report

DI-CMAN-81218 Product Base Line Index (PBLI)

DI-ADMN-81249B Conference Agenda

DI-ADMN-81250B Conference Minutes

DI-SAFT-81626 System Safety Program Plan (SSPP)

(Copies of these documents are available online at http://quicksearch.dla.mil.)

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

COMMERCIAL ITEM DESCRIPTIONS

A-A-59981 DOLLY SET MOBILIZER, 7-1/2 TON

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 track program progress and document such via monthly status reports. 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, and deliverables. Problem areas shall be identified with proposed solutions and outcomes.

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

3.2 Conferences and program reviews.

3.2.1 Postaward conference. The Government will convene a postaward conference with the contractor at a location that is mutually agreeable to both parties 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. (DI-ADMN-81249, Conference Agenda, DID DI-

ADMN-81250, Conference Minutes)

3.2.2 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.3 Conference room. The contractor shall provide a conference room suitable for meetings of up to 10 Government representatives, plus contractor personnel, in support of scheduled meetings at the contractor’s facility.

3.2.4 Meeting agendas. The contractor shall publish an agenda for all meetings and conferences specified in 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.5 Meeting minutes. The contractor shall provide a written record of the discussions, decisions, and action items identified at each meeting. Minutes shall include presentation material.

(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 MIL-STD-882. The contractor shall document their approach for analyzing, eliminating, or minimizing ESOH hazards during all phases of the program. 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 and an initial system safety program plan shall be provided 14 days after contract award;

an updated version of the analysis shall be provided 14 days prior to the first production 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 system shall not generate or use Class I or Class II Ozone Depleting

Substances (ODS) during operation, maintenance, or disposal. The use of hexavalent chromium is also prohibited. 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 Risk management. The contractor shall develop, implement, and conduct a risk management program; criteria can be found in the Risk Management Guide for DoD Acquisition.

Risk is defined as:

A measure of future uncertainties in achieving program performance goals within defined cost and schedule constraints. It has three components: a future root cause, a likelihood assessed at the present time of that future root cause occurring, and the consequence of that future occurrence.

A future root cause is defined as, “The reason, which, if eliminated or corrected, would prevent a potential consequence from occurring. It is the most basic reason for the presence of a risk.” A consequence is defined as, “The outcome of a future occurrence expressed qualitatively or quantitatively, being a loss, injury, disadvantage, or gain.” A related term is an issue, defined as, “A problem or consequence which has occurred due to the realization of a root cause. A current issue was likely a risk in the past that was ignored or not successfully mitigated.” The risk management process deals with identifying and mitigating risks so that they do not become issues.

The risk management process model includes the following activities, performed on a continuous basis:

a. Risk Identification,

b. Risk Analysis,

c. Risk Mitigation Planning,

d. Risk Mitigation Plan Implementation, and

e. Risk Tracking.

Risk identification, risk analysis, risk mitigation planning, risk mitigation plan implementation, and risk tracking shall be included as an attachment to the monthly status report (see 3.1.3).

3.4 Logistics.

3.4.1 Technical Order (TO) requirements. The contractor shall develop and deliver technical manuals in accordance with TM-86-01. (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. (DI-MGMT-80227, Contractor’s Progress, Status and Management Report)

3.4.2 Commissioning. The Government will order commissioning in delivery orders issued against the contract. Commissioning may or may not be required in every delivery order. When commissioning is ordered, the contractor shall provide a minimum of two days of vehicle orientation, user familiarization, and general maintenance information at the Government base identified in the delivery order – subsequent to first delivery of the vehicle to that location.

Commissioning may include, but is not limited to, a walk around of the vehicle noting the component layout and operational function, structure, design, capacity, and safety features, servicing and troubleshooting of the engine as well as other components of the vehicle, and over-the-shoulder instructions for operation of the vehicle and its various components.

3.5 Testing and evaluation.

3.5.1 First production test.

3.5.1.1 First production test procedures. The contractor shall develop detailed first production test procedures, which shall address all requirements identified in the A-A-59981 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.1.2 First production testing. After Government approval of the first production 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 production testing 30 days prior to the start of testing. The test will be witnessed by one or more Government representatives.

3.5.1.3 First production test report. The contractor shall submit a first production test report upon completion of the first production test. The test report shall document all testing performed, including results of any unsuccessful test attempts. (DI-NDTI-80809, Test/Inspection Report)

3.5.2 Restoration. After completion of First production acceptance, the contractor shall be responsible for any repairs that may be necessary to restore the first production mobilizers to a serviceable, “like new” condition while retaining configuration integrity.

3.5.3 Disposition. The first production mobilizer shall be retained at the contractor’s facility, to serve as a manufacturing standard, until the last shipment.

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 A-A-59981.

3.6.1.1.2 Allocated baseline. All of the documents used to produce and define the accepted CID configuration shall constitute the allocated baseline.

3.6.1.1.3 Product baseline. All of the documents used to produce and define the accepted first production mobilizers 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 production test report and TOs have 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 system safety impact statement shall be provided as part of the submittal; it shall quantify and qualify the system safety risk identified and how it impacts the system safety risk already identified for the system.

A Notice of Revision (NOR) shall be submitted with each ECP. Should the Government approve an ECP, the contractor shall be responsible for submitting updated TOs and the system safety hazard analysis report (see 3.3.1.1) to reflect the changes made in the ECP. (DI-SESS-80639, Engineering Change Proposal (ECP); DI-SESS-80642, Notice of Revision (NOR)).

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

3.6.4 Service bulletin. The contractor shall prepare service bulletins as required to notify the

Government of new maintenance problems and/or procedures to be implemented on the contractor’s equipment prior to issuance of permanent changes to the technical manuals. The service bulletins shall also identify any potential safety hazards previously identified. (DI-

MISC-80508, Technical Report/Study Services)

3.6.5 USAF Registration Numbers. Contractor will request Air Force registration numbers no later than 90 days and at least 60 days prior to delivery of vehicles. "US Air Force," "Vehicle

Registration Number" and "For Official Use Only" are not required on the side or the rear of the vehicle. However, the vehicle registration numbers and contract numbers are still required on the vehicle data plate in accordance with MIL-STD-1223. Also, vehicle registration numbers and contract number must be shown on the invoice/receiving reports.