SOWFInal.pdf

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

13 April 2021

Statement of Work (SOW) for

TRACTOR, AIRCRAFT TOWING, FLIGHT LINE

Prepared by

SUPPORT EQUIPMENT AND VEHICLES PROGRAM OFFICE

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 Post-award conference

3.2.2 Program Management review support

3.2.3 Meeting space

3.2.4 Meeting agendas

3.2.5 Meeting minutes

3.3 System safety

3.4 Technical Order (TO) requirements

3.5 Testing and evaluation

3.5.1 Pre-production unit test

3.5.1.1 Pre-production unit test procedures

3.5.1.2 Pre-production unit testing

3.5.1.3 Pre-production unit test report

3.6 Restoration

3.6.1 Disposition

3.7 Configuration management

3.7.1.1 Product baseline

3.7.1.2 Production release

3.7.2 Engineering Change Proposals (ECPs)

3.7.3 Request for Variance (RFV)

3.8 Service Bulletins

3.9 Cybersecurity requirements

3.9.1 Cybersecurity analysis

3.9.2 Risk Management Framework (RMF)

1. SCOPE

This document defines the tasks associated with the procurement of the Flight Line Tow Tractor (FLTT) as described by Commercial Item Description (CID) A-A-59312E and is to be used in conjunction with A-A-59312E.

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.

COMMERCIAL ITEM DESCRIPTION

A-A-59312E TRACTOR, AIRCRAFT TOWING, FLIGHT LINE

2.1.2 Other Government documents, drawings, and publications.

DATA ITEM DESCRIPTIONS (DIDs)

DI-NDTI-80603A Test Procedure DI-SESS-80639E Engineering Change Proposal (ECP) DI-SESS-80640E Request for Variance (RFV) DI-SESS-80642E Notice of Revision (NOR) DI-NDTI-80809B Test/Inspection Report DI-SESS-82019 Product Base Line Index (PBLI) DI-MISC-81618 Service Bulletins DI-MISC-80508B, Technical Report – Study/Services

DI-SAFT-80101C

DI-SAFT-81626

System Safety Hazard Analysis Report (SSHAR) System Safety Program Plan

DI-MGMT-81928

DI-MGMT-82135

Contractor’s Progress, Status and Management Report RMF A&A Products

DI-ADMN-81249B Conference Agenda DI-ADMN-81250B Conference Minutes

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

DEPARTMENT OF DEFENSE GUIDES

TM-86-01Q Air Force Technical Manual Contract Requirements

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-81928, Contractor’s Progress, Status and Management Report)

3.2 Conferences and program reviews.

3.2.1 Post-award conference. If the Government determines that a post-award conference is necessary, the Government will convene the conference with the contractor at a location that is mutually agreeable to both parties, or via teleconference, within 60 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 Program Management review support. The contractor shall participate in and support all reviews, audits, and meetings as requested by the Program Manager or the contractor. Program Management Reviews shall be conducted as required at a mutually agreeable location or via teleconferences.

3.2.3 Meeting space. The contractor shall provide a conference room or space suitable for meetings of up to 5 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 3.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)

3.3 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 program plan and system safety hazard analysis shall be provided 90 days after contract award; an updated version of the plan and analysis shall be provided with the pre-production unit test report.

(DI-SAFT-81626, System Safety Program Plan; DI-SAFT-80101, System Safety Hazard Analysis Report)

3.4 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). In addition to the requirements specified in TO CDRLs, the following information shall be included in the TO (applicable paragraphs in A-A-59312E are provided for reference):

a. The temporary CPC removal process (see 3.2.1.4)

b. The information contained on the identification data plate as it is presented on the plate (see 3.2.3.1)

c. The information contained on the transportation data plate as it is presented on the plate (see 3.2.3.2)

d. The information contained on the lubrication data plate as it is presented on the plate (see 3.2.3.3)

e. Copy of the tire manufacturer approval for over inflation and tire sidewall markings if necessary (3.2.9)

f. Any requirements for towing in low ambient temperatures, for example, recommended coolant ratios, oil types and viscosities, etc., for various temperature ranges (see 3.3.1).

g. User-specific instructions for the daily inspection and operations of the pintle hooks, and maintainer-specific instructions for the interim inspection and replacement of the pintle hook (see 3.6.6)

h. A description of the pintle hook fastener type and the fastening torque (see 3.6.6).

i. Note regarding nuclear towing (3.6.6.3)

j. For each winterization package, a breakdown of the winterization components and requirements, for example, recommended coolant ratios, oil types and viscosities, etc., for the various temperature ranges (see 3.7.6).

3.5 Testing and evaluation.

3.5.1 Pre-production unit test.

3.5.1.1 Pre-production unit test procedures. The contractor shall develop detailed pre-production unit test procedures, which shall address all requirements identified in the A-A-59312E 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 Pre-production unit testing. After Government approval of the pre-production unit 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 pre-production unit testing 30 days prior to the start of testing.

The test will be witnessed by one or more Government representatives.

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

3.6 Restoration. After completion of pre-production unit acceptance, the pre-production FLTT 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 pre-production FLTT to a serviceable, “like new” condition while retaining configuration integrity. The contractor shall be responsible for all costs associated with shipping of the pre-production FLTT to the contractor's facility for restoration.

3.6.1 Disposition. The pre-production FLTT shall be shipped to the location(s) specified in the contract.

3.7 Configuration management.

3.7.1 Configuration requirements.

3.7.1.1 Product baseline. All of the documents used to produce and define the accepted pre-production FLTT shall be identified in a Product Base Line Index (PBLI). The list shall identify the applicable version number as required. (DI-SESS-82019, Product Base Line Index (PBLI))

3.7.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 pre-production unit test report, and TOs have been delivered and approved by the procuring activity.

3.7.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) to reflect the changes made in the ECP. (DI-SESS-80639, Engineering Change Proposal (ECP); DI-SESS-80642, Notice of Revision (NOR)).

3.7.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.8 Service bulletins. The contractor shall prepare service bulletins as required, to be issued by Air Force Registration Number, 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. (DI-MISC-81618, Service Bulletins)

3.9 Cybersecurity requirements. The contractor shall implement cybersecurity in accordance with DoDI 8500.01, DoDI 8510.01, and AFI 17-101. Commercial policy and standards, such as ASE J3061, ASE J3101, and various ISO/IEC standards may be used in lieu of DODI/AFI, as applicable. The contractor shall provide cybersecurity support to include, but not limited to, engineering and technical analysis and security and risk assessment of system cybersecurity. The contractor shall include cybersecurity activities and events on the monthly status report (3.1.3).

3.9.1 Cybersecurity analysis. The contractor shall perform engineering analysis and risk and technical assessment of system cybersecurity. The engineering analysis shall include, but is not limited to, system hardware and software architecture, I/O data flow, supply chain integrity, and operational conditions as it relates to system cybersecurity. The contractor shall perform a comprehensive risk assessment based on the system cyber vulnerabilities and threats. The contractor shall conduct analysis for any COTS and/or non-developmental items to ensure that they are appropriately configured, software/hardware/firmware is controlled, and any unique risks they pose are mitigated. (DI-MISC-80508B, Technical Report – Study/Services)

3.9.2 Risk Management Framework (RMF). The contractor shall develop and deliver the required artifacts for Platform Information Technology (PIT) Assessment and Authorization (A&A) package to meet the intent and requirements of DoDI 8510.01 and AFI 17-101 for RMF implementation. The contractor shall utilize National Institute of Standards and Technology (NIST) Special Publication (SP) 800-37, NIST SP 800-53, and applicable overlays in addressing the security controls associated with the various artifacts. The contractor shall include cybersecurity risk management framework activities and events on the monthly status report (3.1.3). (DI-MGMT-82135, RMF A&A Products)