SOWDeicers-2021_02_11.pdf

11 Feb 2021

Statement of Work (SOW) for

SPRAYING UNIT, CLEANING-DEICING-ANTI-ICING FLUID, TRUCK

MOUNTED (CLASS A & CLASS B)

Prepared by

Richard C. Gordon, AFLCMC/WNZ Mechanical Engineer

SUPPORT EQUIPMENT AND VEHICLES PROGRAM OFFICE 235

BYRON ST STE 19A

ROBINS AFB GA 31098-1813

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

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.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.4 Logistics

3.4.1 Technical Order (TO) requirements

3.4.2 Commissioning

3.4.2.1. CONUS

3.4.2.1.1 Installations in Zone A include but are not limited to:

3.4.2.1.2 Installations in Zone B include but are not limited to:

3.4.2.1.3 Installations in Zone C include but are not limited to:

3.4.2.2 OCONUS

3.4.2.2.1 Installations in Zone AA include but are not limited to:

3.4.2.2.2 Installations in Zone BB include but are not limited to:

3.4.2.2.3 Installations in Zone CC include but are not limited to:

3.4.2.2.4 Installations in Zone DD include but are not limited to:

3.4.2.2.5 Installations in Zone EE include but are not limited to:

3.4.2.2.6 Installations in Zone FF include but are not limited to:

3.4.3 Computer Program Identification Number (CPIN)

3.5 Testing and evaluation

3.5.1 First article test

3.5.1.1 First article test procedures

3.5.1.2 First article testing

3.5.1.3 First article 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 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 Diagnostic Software

3.7 Service bulletins

1. SCOPE

This document defines the tasks associated with the procurement of the Deicers as described by Commercial Item Description (CID) A-A-59145D, dated 8 June 2020, and revision pages (if applicable), and is to be used in conjunction with A-A-59145D.

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 STANDARDS

MIL-STD-882E System Safety

2.1.2 Other Government documents, drawings, and publications.

AIR FORCE INSTRUCTION (AFI)

AFI 32-7086 Hazardous Materials Management, dated 4 February

(Copies of this document are available online at http://www.e-publishing.af.mil/.)

DATA ITEM DESCRIPTIONS (DIDs)

DI-SAFT-80101C System Safety Hazard Analysis Report (SSHAR) DI-MGMT-81928 Contractor's Progress, Status and Management Report DI-NDTI-81307A First Article Qualification Test Plan and Procedures 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-CMAN-82019 Product Base Line Index (PBLI) DI-ADMN-81249B Conference Agenda DI-ADMN-81250B Conference Minutes DI-SAFT-81626 System Safety Program Plan (SSPP) DI-MISC-81618 Service Bulletins DI-AVCS-80700 Computer Software Product End Items DI-MISC-81454D Computer Program Identification Number Catalog

Information DI-IPSC-82249 Software Assurance Evaluation Report

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

http://www.e-publishing.af.mil/ 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-01Q Air Force Technical Manual Contract Requirements

COMMERCIAL ITEM DESCRIPTIONS

A-A-59145D SPRAYING UNIT, CLEANING-DEICING-ANTI-ICING FLUID, TRUCK

MOUNTED

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 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 Program Manager 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 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 3.2.3. 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 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 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 First Article 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 AFI 32-7086, to be delivered under this contract, including locations, quantities, and special handling and disposal procedures.

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.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 of the boom and enclosed cab; servicing and troubleshooting of all engines as well as other components of the vehicle; and over-the-shoulder instructions for operation of the vehicle and its various components such as safety shutdown systems. For all subsequent deliveries to each base location where commissioning has already taken place, the Government will be responsible for follow-on familiarization.

3.4.2.1. CONUS.

For purposes of this instant contract, commissioning in the Continental United States (CONUS) locations is designated into 3 categories: Zone A, Zone B, and Zone C.

3.4.2.1.1 Installations in Zone A include but are not limited to:

Robins AFB, GA; Moody AFB, GA; Charleston AFB, SC; Seymour Johnson AFB, NC; Pope AFB, NC;

Louisville IAP, KY; Buckley ANG, OH; Wright-Patterson AFB, OH; Langley AFB, VA; Harrisburg IAP, PA; Dover AFB, DE; Hanscom AFB, MA; Andrews AFB, MD; McGuire AFB, NJ; Niagra Falls ARS, NY;

Stewart IAP, NY, etc.

3.4.2.1.2 Installations in Zone B include but are not limited to:

Maxwell AFB, AL; Birmingham IAP, AL; Barksdale AFB, LA; Lackland AFB, TX; Little Rock AFB, AR;

Altus AFB, OK; Tinker AFB, OK; McConnell AFB, KS; Forbes Field, KS; Whiteman AFB, MO; Scott AFB, IL; Offutt AFB, NE; Grand Forks AFB, ND, Minot AFB, ND, etc.

3.4.2.1.3 Installations in Zone C include but are not limited to:

Kirtland AFB, NM; Cannon AFB, NM; Buckley AFB, CO; Ellsworth AFB, SD; Cheyenne Mountain AFS, CO; Peterson AFB, CO; Hill AFB, UT; Nellis AFB, NV; Edwards AFB, CA; Travis AFB, CA; Mountain Home AFB, ID; McChord AFB, WA;Fairchild AFB, WA, etc.

3.4.2.2 OCONUS.

For purposes of this instant contract, commissioning Outside the Continental United States (OCONUS) locations is designated into 6 categories:

3.4.2.2.1 Installations in Zone AA include but are not limited to:

Eielson AFB, AK; Elmendorf AFB, AK; and Hickam AFB, HI.

3.4.2.2.2 Installations in Zone BB include but are not limited to:

Osan AB, South Korea; Kunsan AB, South Korea; Yokota AB, Japan; Misawa AB, Japan; Kadena AB, Japan; and Andersen AFB, Guam.

3.4.2.2.3 Installations in Zone CC include but are not limited to:

Joint Base Balad, Iraq; Bagram Airfield, Afghanistan; and Manas AB, Kyrgyzstan.

3.4.2.2.4 Installations in Zone DD include but are not limited to:

RAF Lakenheath, England; RAF Mildenhall, England; Ramstein AB, Germany; Spangdahlem AB, Germany; Aviano AB, Italy; Moron AB, Spain; and Incirlik AB, Turkey.

3.4.2.2.5 Installations in Zone EE include but are not limited to:

Thule AB, Greenland

3.4.2.2.6 Installations in Zone FF include but are not limited to:

Soto Cano AB, Honduras; and Muniz ANGB, Puerto Rico

3.4.3 Computer Program Identification Number (CPIN).

The Contractor shall submit a request for CPIN assignment of all custom and/or commercial software to include, but not limited to, any utility software for firmware updates, the firmware itself, and any other support software to be delivered to the Government. CPIN assignment requests shall be accomplished by direct on-line data entry into Enhanced Technical Information Management System (ETIMS) in accordance with TO 00-5-16 guidelines. The contractor shall delivery the final Computer Software Configuration Items (CSCIs) on CD/DVD-ROM. The CPIN media label information shall match the information in ETIMS. (DI-MISC-81454D, Computer Program Identification Number Catalog Information) (DI-AVCS-80700, Computer Software Product End Items)

3.5 Testing and evaluation.

3.5.1 First article test.

3.5.1.1 First article test procedures.

The contractor shall develop detailed First Article test procedures, which shall address all requirements identified in the CID A-A-59145D 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-81307, First Article Qualification Test Plan and Procedures)

3.5.1.2 First article testing.

After Government approval of the First Article 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 Article 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 article test report.

The contractor shall submit a First Article test report upon completion of the First Article 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 Article acceptance, the First Article Deicer 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 First Article Deicer to a serviceable, “like new” condition while retaining configuration integrity. The contractor shall be responsible for all costs associated with shipping of the First Article Deicer to the contractor's facility for restoration.

3.5.3 Disposition.

The First Article Deicer 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-59145D, dated 8 June 2020, and corresponding revisions or change pages, if applicable.

3.6.1.1.2 Product baseline.

All of the documents used to produce and define the accepted First Article Deicer shall be identified in a Product Base Line Index (PBLI). The list shall identify the applicable version number as required. (DI-CMAN-82019, 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 Article 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 Diagnostic Software.

A copy of any diagnostic software required or recommended for maintaining the spraying unit shall be provided with each spraying unit on CD/DVD-ROM. Any diagnostic software must be compatible for use on Microsoft Windows 10 (64-bit) operating system. The contractor shall develop and deliver a Software Assurance (SwA) Evaluation Report to demonstrate that all delivered software functions as intended and is free of vulnerabilities (i.e. defects, bugs, malware, etc.), either intentionally or unintentionally or inserted as part of the software throughout the lifecycle. Any interface hardware/cable required to communicate between the host computer with diagnostic software and the spraying unit shall also be provided with each spraying unit. (DI- IPSC-82249, Software Assurance (SwA) Evaluation Report)

3.7 Service bulletins.

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- 81618, Service Bulletins)