ATCH-01 - MAAS - Statement of Work (SOW).pdf

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

17 January 2024

Statement of Work (SOW) for

Mobile Aircraft Arresting System (MAAS)

Prepared by

SUPPORT EQUIPMENT AND VEHICLES PROGRAM OFFICE

236 MILLEDGEVILLE STREET, SUITE F30

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 Non-Government publications

2.3 Order of precedence

3. REQUIREMENTS

3.1 Program management

3.1.1 Common Access Card (CAC)

3.1.2 Access to Government systems(s)

3.1.3 Data delivery and transfer

3.1.4 Program manager

3.1.5 Plant access

3.1.6 Monthly status report

3.1.7 Integrated master plan (IMP)

3.1.8 Integrated master schedule (IMS)

3.2 Conferences and program reviews

3.2.1 Post-award conference

3.2.2 Test readiness review (TRR)

3.2.2.1 TRR documentation

3.2.3 Program Management Review (PMR) support

3.2.4 Conference room

3.2.5 Meeting agendas

3.2.6 Meeting minutes

3.2.7 Multi-user ECP Automated Review System (MEARS)

3.3 Systems engineering

3.3.1 Corrosion Control

3.3.1.1 Materials, protective coatings, and finish

3.3.1.1.1 Protective coatings

3.3.1.1.2 Surface Preparation and pretreatment

3.3.1.1.2.1 Aluminum pretreatment

3.3.1.1.2.2 Ferrous pretreatment

3.3.1.1.3 Primer

3.3.1.1.3.1 Ferrous surfaces

3.3.1.1.3.2 Aluminum surfaces

3.3.1.1.4 Topcoat

3.3.1.1.5 Dissimilar metals

3.3.1.1.6 Finish

3.3.1.1.7 Touch-up

3.4 Logistics

3.4.1 Provisioning

3.4.1.1 Provisioning Guidance Conference

3.4.2 Technical Order (T.O.) requirements

3.5 Testing and evaluation

3.5.1 Testing

3.5.1.1 Functional verification

3.5.1.2 First article test

3.5.2 Test reports

3.5.2.1 Contractor test reports

3.5.2.2 Government test reports

3.5.3 First article acceptance

3.5.4 Restoration

3.5.5 Disposition

3.6 Configuration management

3.6.1 Configuration requirements

3.6.1.1 Production release

3.6.2 Engineering Change Proposals (ECPs)

3.6.2.1 TDP

3.6.2.2 Qualification of new components

3.6.3 Request for Variance (RFV)

3.6.4 Engineering data

3.6.4.1 Engineering Data Guidance Conference

3.6.4.2 In-Process Review (IPR) of the TDP

3.6.4.3 Relationship of the contractor with subcontractors and vendors

3.6.4.4 Engineering data updates and revisions

3.6.5 Configuration audit plan and Physical Configuration Audit (PCA)

3.6.5.1 Configuration audit plan

3.6.5.2 PCA

3.7 Government furnished equipment (GFE)

1. SCOPE

This document defines the tasks associated with the procurement and qualification of the Mobile Aircraft Arresting System (MAAS) as described by Technical Orders (T.O.s) 35E8-2-10-1, 35E8- 2-10-3, 35E8-2-10-4, 35E8-2-5-1, 35E8-2-5-3, and 35E8-2-5-4 and the United States Air Force (USAF) technical data package (TDP) beginning with top level drawing 201018515, Contractor and Government Entity (CAGE) 98752 and is to be used in conjunction with the T.O.s and TPD.

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.

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 SPECIFICATIONS

TT-C-490H Chemical Conversion Coatings and Pretreatments for

Metallic Substrates (Base for Organic Coatings)

DEPARTMENT OF DEFENSE SPECIFICATIONS

MIL-DTL-5541F NOT 1 Chemical Conversion Coatings on Aluminum and Aluminum Alloys

MIL-A-8625F(2) NOT 1 Anodic Coatings for Aluminum and Aluminum Alloys MIL-C-10578D(3) NOT 4 Corrosion Removing Metal Conditioning Compound

(Phosphoric Acid Base) MIL-PRF-23377K NOT 1 Primer Coatings: Epoxy, High-Solids MIL-PRF-32550(1) Metal-Rich Primer MIL-DTL-53022F(1) Primer, Epoxy Coating, Corrosion Inhibiting Lead and

Chromate Free MIL-DTL-53030D(1) NOT 1 Primer Coating, Epoxy, Water Reducible, Lead and

Chromate Free MIL-DTL-81706B(1) NOT 1 Chemical Conversion Materials for Coating Aluminum and Aluminum Alloys MIL-PRF-85285F Coating: Polyurethane, Aircraft and Support Equipment

DEPARTMENT OF DEFENSE STANDARDS

MIL-STD-130N(1) NOT 1 Identification Marking of U.S. Military Property MIL-STD-889D Dissimilar Metals MIL-STD-3035 USAF Aircraft Arresting Systems Design Criteria Standard MIL-STD-3036 USAF Aircraft Arresting Systems (Test Method) Aircraft

2.1.2 Other Government documents, drawings, and publications.

DATA ITEM DESCRIPTIONS (DIDs)

DI-MGMT-80004A Management Plan DI-MISC-80508B Technical Report/Study Services DI-NDTI-80809B Test/Inspection Report DI-SESS-80639E Engineering Change Proposal (ECP) DI-SESS-80640E Request for Variance (RFV) DI-SESS-80642E Notice of Revision (NOR) DI-SESS-81000F Product Engineering Design Data and Associated Lists DI-SESS-81022E Configuration Audit Summary Report and Certification DI-ADMN-81249C Meeting Agenda DI-ADMN-81250C Meeting Minutes DI-SESS-81646C Configuration Audit Plan DI-MGMT-81861C Integrated Program Management Data and Analysis Report

(IPMDAR)

DI-SESS-81874 Engineering Data for Provisioning (EDFP) DI-MGMT-81928 NOT 2 Contractor's Progress and Status Report DI-SESS-81758A/T Logistics Product Data

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

DEPARTMENT OF DEFENSE MANUALS

35E8-2-5-1 OPR AND MAINT INSTR – ACFT ARRESTING SYS

MOD BAK-12E32A (GULF WESTERN IND)

35E8-2-5-3 Aircraft Arresting System Model BAK-12 35E8-2-5-4 Aircraft Arresting System Model BAK-12 35E8-2-10-1 Operation and Maintenance Instructions, Arresting Systems, Aircraft, Mobile Model No AM 32A-96, Part No 52-D- 8013-101, Part No 52-D-8013-103, Part No 52-D-8013-104

35E8-2-10-3 Overhaul Instructions – Mobile Aircraft Arresting Sys, PN 52-D-8013-101 (Gulf and Western)

35E8-2-10-4 Illustrated Parts Breakdown, Arresting System, Aircraft, Mobile Model No AM 32A-96, Part No 52-D-8013-101, Part No 52-D-8013-103, Part No 52-D-8013-104

TM-86-01R Technical Manual Contract Requirements (TMCR)

DRAWINGS

Part Number

CAGE Nomenclature

9579776 98752 Product Data Specification

9579777 98752 Clarification of Detailed Test Criteria for Electrical and Avionics Items

201018515 98752 Mobile Arresting Unit

(Copies of drawings will be provided with the solicitation.)

2.2 Non-Government publications. The following documents of the exact revision listed below form a part of this document to the extent specified herein.

AMERICAN SOCIETY OF MECHANICAL ENGINEERS (ASME)

Y14.24-2012 Types and Applications of Engineering Drawings Y14.34-2018 Associated Lists Y14.35-2014 Revision of Engineering Drawings and Associated Documents Y14.41-2012 Digital Product Definition Data Practices Y14.47-2019 Model Organization Practices Y14.100-2017 Engineering Drawing Practices

(Application for copies should be addressed to ASME, Two Park Avenue, New York NY 10016- 5990, http://www.asme.org/.)

SAE International

GEIA HB-0007-B Logistics Product Data Handbook AMS-STD-595A Colors Used in Government Procurement

(Application for copies should be addressed to SAE International, Inc., 400 Commonwealth Drive, Warrendale PA 15096, http://www.sae.org/.)

NACE INTERNATIONAL

SSPC-SP10/NACE No.2 Near-White Metal Blast Cleaning SSPC-Vis 1 Guide and Reference Photographs for Steel Surfaces

Prepared by Dry Abrasive Blast Cleaning

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.

http://www.asme.org/ http://www.sae.org/

3.1.1 Common Access Card (CAC). The contractor shall ensure a CAC is obtained by all contractor/subcontractor personnel who require access to DoD computer networks/systems, for DoD facility entry control, and/or for physical access to facilities and buildings to perform tasks under the contract/order. The contractor shall provide a list of contractor/subcontractor personnel who require a CAC to the Procuring Contracting Officer (PCO). The Government will provide the contractor instructions on how to complete a Contractor Verification System (CVS) application and notify the contractor of approval/disapproval of contractor/subcontractor personnel application.

Contractor/subcontractor personnel shall obtain the CAC from the local Real Time Automated Personnel Identification Documentation System (RAPIDS) issuing facility (usually the Military Personnel Flight (MPF)).

The contractor shall notify the PCO of any change to the list of contractor/subcontractor personnel who require a CAC and provide an updated list within five business days. The contractor shall immediately (within same day) report a lost or stolen CAC to the PCO. The contractor shall return any issued CAC to the PCO within five business days once contractor personnel no longer require computer network/system access. The contractor shall return any and all CACs to the PCO within five business days after completion/termination of the contract.

3.1.2 Access to Government system(s). The procuring activity will provide and/or arrange contractor personnel access to system(s) necessary to perform tasks under the contract/order. The contractor shall ensure contractor personnel who require access to an unclassified Government AIS have the appropriate background check or security investigation conducted. The procuring activity will provide and/or arrange system access subject to approval of the DD Form 2875, System Authorization Access Request (SAAR). Upon completion/termination of the contract/order or transfer/termination of contractor personnel, the contractor shall ensure the system account(s) are closed.

3.1.3 Data delivery and transfer. To promote effective schedule management, electronic data exchanges shall be utilized to the maximum extent possible for tasks identified in this SOW.

Contractor personnel having CACs will be granted access to Air Force Cloud Hosted Enterprise Services Teams (AF365 Teams), a collaborative workspace product of Microsoft, to send/receive/upload/download/view data for tasks identified in the SOW. Air Force OneDrive, accessible through AF365 Teams to CAC holders, shall be the Cloud hosted data storage repository. Department of Defense (DoD) Secure Access File Exchange (SAFE) shall be the secondary (backup) electronic data exchange, located at https://safe.apps.mil, and utilized when temporary circumstances do not permit use of AF365 Teams.

3.1.4 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.5 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.

https://safe.apps.mil/

3.1.6 Monthly status report. The contractor shall submit a monthly status report that shall cover actions to date 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 NOT 2, Contractor's Progress and Status Report)

3.1.7 Integrated master plan (IMP). The contractor shall implement and maintain the proposed IMP for this program. (DI-MGMT-80004A, Management Plan)

3.1.8 Integrated master schedule (IMS). A baseline IMS shall be developed at the start of the program in accordance with 1.2.2 of DI-MGMT-81861C. The contractor shall implement and maintain the IMS using the original baseline schedule as an unchanging reference. The IMS shall be provided in both Microsoft Project and PDF formats as an attachment to the monthly status report (see 3.1.6). (DI-MGMT-81861C, Integrated Program Management Data and Analysis Report (IPMDAR))

3.2 Conferences and program reviews.

3.2.1 Postaward conference. The Government will convene a postaward conference with the contractor at the contractor’s facility within 60 days after contract award. The Procuring Contracting Officer (PCO) will coordinate the actual date and time of the conference with the contractor.

3.2.2 Test readiness review (TRR). The contractor shall conduct a test readiness review (TRR) 14 days prior to the start of the functional verification (see 3.5.1.1). 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 TRR shall be held via AF365 Teams. The PCO will coordinate the actual date and time with the contractor.

3.2.2.1 TRR documentation. The contractor shall prepare all necessary detailed status reports for the TRR meeting, conference agenda, and conference minute. The contractor shall prepare formal documentation of the TRR. (DI-ADMN-81249C, Meeting Agenda; DI-ADMN-81250C, Meeting Minutes; DI-MISC-80508B, Technical Report/Study Services)

3.2.3 Program Management Review (PMR) support. The contractor shall participate in and support all reviews, audits, and meetings as requested by the PCO or the contractor. PMRs shall be conducted quarterly or as required via AF365 Teams.

3.2.4 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.5 Meeting agendas. The contractor shall publish an agenda for all meetings and conferences specified in 3.2.2 and 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-81249C, Meeting Agenda)

3.2.6 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-81250C, Meeting Minutes)

3.2.7 Multi-user ECP Automated Review System (MEARS). The contractor shall electronically deliver all contractual data specified herein using the Government-controlled method of delivery, MEARS, http://mears1.redstone.army.mil/mears/Default.aspx. The contractor shall work with the Government to ensure that an adequate number of contractor personnel obtain and possess Public Key Infrastructure (PKI) certification from an accepted Government source. The contractor shall be receptive to the training offered by the Government on the MEARS system. The contractor shall prepare, maintain, and track the contract data status, schedule and ensure timely data deliveries. If MEARS is down for maintenance, the contractor shall use an alternative method of the contractual data deliverables utilizing Defense Information Systems Agency (DISA), known as Department of Defense (DoD) SAFE, via http://safe.apps.mil/. The contractor shall obtain and possess PKI certification from an accepted Government source to access the DoD SAFE.

3.3 Systems engineering.

3.3.1 Corrosion control.

3.3.1.1 Materials, protective coatings, and finish.

3.3.1.1.1 Protective coatings. Surface treatments, pre-treatments and coatings shall be applied to all components and surfaces that are not corrosion resistant. Surface treatments include electroplated coatings, thermal sprayed coatings, and hard anodize coatings. Surface pre-treatments include thin film anodize, conversion coatings, zinc phosphate, and other coatings used to enhance subsequent corrosion protective coating adhesion and performance. Corrosion protective coatings include corrosion inhibited epoxy primers and polyurethane topcoats. Exposed surfaces of fasteners, handles, and fittings shall also be primed and painted. All coating properties such as, but not limited to, ultra-violet (UV) resistance, hardness, adhesion, chip-resistance, salt-spray resistance, etc. shall be consistent with the world-wide climactic, environmental, and operational conditions experienced by the MAAS.

3.3.1.1.2 Surface preparation and pretreatment. Components and surfaces shall be cleaned, degreased, and prepped prior to any scuffing, sanding, blasting, or application of any pretreatment.

Surface preparation and pretreatment shall be in accordance with the respective primer and topcoat specifications. All corrosion protection steps, regardless of material, shall be applied before any new oxidation or rusting occurs post-treatment and shall be completed prior to application of any respective coating used as either primer or topcoat. Surfaces shall be scuffed, sanded, and/or blasted, depending upon material type and thickness, to remove any existing surface impurities (for example, primer/paint/topcoat, corrosion, welding/grinding/cutting slag, etc.) that may prevent adhesion and protection of further corrosion control measure. Any surface undergoing a media blasting process shall have the blasting pressure, blasting material type, and blasting material grit suitably chosen to prevent warpage or other structural damage. Coatings requiring a

“near-white” ferrous metal finish shall have the surface(s) prepared in accordance with SSPC-SP 10/NACE No. 2. General surface finish and cleanliness shall conform to SSPC-Vis 1.

3.3.1.1.2.1 Aluminum pretreatment. Aluminum components and surfaces used in construction of the MAAS shall be treated with a suitable conversion coating prior to application of any other corrosion prevention coating. Anodizing or a MIL-DTL-81706 conversion coating process may be utilized, at the discretion of the MAAS’ manufacturer. Any anodizing shall be applied in accordance with MIL-A-8625, Type II, Class 1; no further conversion coating is required on anodized aluminum surfaces. Alternatively, aluminum surfaces shall have MIL-DTL-81706, Type I, Class 1A, Form I, Method C chemical conversion coating applied in accordance with MIL-DTL- 5541, Type I, Class 1A. In areas and locals where use of hexavalent chrome is not permitted by regulatory authority, aluminum surfaces shall have MIL-DTL-81706, Type II, Class 1A, Form I, Method C chemical conversion coating applied in accordance with MIL-DTL-5541, Type II, Class 1A.

3.3.1.1.2.2 Ferrous pretreatment. Ferrous components and surfaces used in construction of the MAAS shall be treated with a metal etching compound in accordance with MIL-C-10578 prior to application of any further pretreatment process(es). Ferrous surfaces with iron or zinc phosphate coatings/etches do not require further pretreatment. Ferrous surfaces without an iron or zinc phosphate coating/etch shall be treated with a wash primer in accordance with TT-C-490 to seal out flash rust.

3.3.1.1.3 Primer. Raw metal edges, to include fastener and drain holes, shall be coated with primer prior to applying the topcoat. Any surfaces where primer and/or topcoat is not required or intended to be applied, shall be masked off using materials and processes suitable for use with applied primer and/or topcoat system. A primer color shall be chosen that is compatible with the color of the topcoat used such that scratches in the topcoat do not yield an obtrusive contrast with any exposed primer (tone-down primer in a similar shade/color family as the topcoat).

3.3.1.1.3.1 Ferrous surfaces. Ferrous structures and surfaces shall be primed with a non-water reducible zinc rich primer in accordance with MIL-PRF-32550, Type I, Form A, Class S. The zinc rich primer shall be followed, within four hours, by a coat of MIL-DTL-53030 intermediate primer in a wet-to-wet primer application. The primer system shall yield a dry-film thickness (dft) of 2.0-

2.5 mils for the zinc rich primer and 0.9 to 1.1 mils for the intermediate primer. The primer system shall be allowed to dry and fully cure in accordance with the primer manufacturer's directions prior to applying the topcoat.

3.3.1.1.3.2 Aluminum surfaces. Aluminum and mixed aluminum and ferrous structures and surfaces shall be primed with an epoxy primer in accordance with MIL-PRF-23377, Type I, Class N. This single part primer system shall yield a dft of 0.6 to 0.8 mils.

3.3.1.1.4 Topcoat. All components shall be top coated with polyurethane in accordance with MIL- PRF-85285, Type IV, Class H. Upon request of the contractor, and approval of the procuring activity, MIL-PRF-85285 Type II or Type III coatings may be applied in lieu of MIL-PRF-85285 Type IV coatings in areas and locals where regulatory authority prohibit the use of 420g/l VOC.

Neither Chemical Agent Resistant Coating (CARC) nor powder coating shall be used. Topcoat shall be applied to a dft of 1.6 to 2.4 mils in all instances, regardless of the primer system utilized.

The coating shall be free from runs, sags, orange peel, or other defects. The contractor shall utilize the topcoat material manufacturer's specifications to accomplish application of the coating system in accordance with the manufacturer's directions to the minimum dft required herein. If a conflict arises between the minimum dft required herein, and the topcoat material manufacturer's specification, the topcoat material manufacturer's specification shall take precedence.

3.3.1.1.5 Dissimilar metals. Dissimilar metals, as defined in MIL-STD-889, shall not be in contact with each other. Metal plating or metal spraying of dissimilar base metals to provide electromotively-compatible abutting surfaces is acceptable. The use of dissimilar metals only when separated by suitable insulating material is permitted, except in systems where bridging of insulation materials by an electrically conductive fluid can occur. Sealants or gel type gasket materials shall be used between faying surfaces and butt joints.

3.3.1.1.6 Finish. The exterior finish color of the MAAS shall be Color Number 14052 of SAE

AMS-STD-595.

3.3.1.1.7 Touch-up. Any minor dings, scuffs, or scratches that may occur during the assembly process shall be cleaned, scuffed (as required), primed (thin tie coat), and painted in accordance with the corrosion prevention requirements stated herein, using the same products as applied to the surface(s) prior to assembly.

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). GEIA-HB-0007B (Logistics Product Data Handbook) should be used as a guide. The format shall be consistent with existing Government Provisioning data system (D220). The following DIDs apply:

a. DI-SESS-81758A/T, Logistics Product Data.

Specific Logistics Product Data to be submitted:

(1) Provisioning Parts List (PPL)

(2) Design Change Notices (DCNs)

(3) Statement of Prior Submission (SPS)

b. DI-SESS-81874, Engineering Data For Provisioning (EDFP).

3.4.1.1 Provisioning Guidance Conference. A Provisioning Guidance Conference (PGC) shall be scheduled by the Prime Provisioning Activity (PPA) and should be held within 45 days after receipt of contract. The PGC is normally held at AFGLSC PPA for approximately two days to ensure both the contractor and the Government understand the provisioning requirements on contract. If a PGC is not desired, the contractor shall submit a written request for waiver of the PGC to the PPA. In the event a waiver is approved, a mutual understanding of the Provisioning requirements shall be communicated in some forum in which the AFMC Form 718 (Provisioning

Performance Schedule (PPS)) shall be documented/completed, signed by both the Government and contractor, and a contract modification issued, if required. (DI-ADMN-81249C, Meeting Agenda; DI-ADMN-81250C, Meeting Minutes)

3.4.2 Technical Order (T.O.) requirements. The contractor shall update and deliver all applicable technical manuals in accordance with TM-86-01. No production unit of the MAAS will be accepted prior to Government approval of the updated technical manuals. (TM-86-01, Air Force Technical Manual Contract Requirements)

3.5 Testing and evaluation.

3.5.1 Testing.

3.5.1.1 Functional verification. The contractor shall have one system (two MAAS Units) available for functional verification at the contractor’s facility within 240 days after contract award. The functional verification of the system and each subsystem shall be performed to verify compliance with this SOW, applicable T.O.s and each applicable requirement of MIL-STD-3035 and MIL- STD-3036. MIL-STD-3035 Sections 3.3, 5.1.2.1-5.1.2.4 shall not apply. Also, in MIL-STD-3035 section 5.1.2 the phrase “Intelligent or computerized” shall be disregarded, however the other requirements of 5.1.2 shall apply. All other sections are applicable. The test will be performed by Government personnel in accordance with T.O. 35E8-2-10-3 Sections 8.1-8.3 to ensure the system is complete and functional prior to start of first article testing (3.5.1.2). The functional verification shall be completed within five days. Immediately after successful completion of the functional testing, the system shall be shipped to NAVAIR Lakehurst.

3.5.1.2 First article test. The first article test will be performed by Government personnel at NAVAIR Lakehurst, using detailed test procedures developed by the Government in accordance with MIL-STD-3036 and this SOW. The test matrix currently consists of 148 test events ranging from approximate weights of 25,000 lbs up to 80,000 lbs, and speeds from 77 to 167 knots.

Contractor’s support shall be available (within 48 hours of notification exclusive of weekends and official Federal Government holidays) all times during the test. All testing shall be completed within an allocated 120 calendar days, with up to 30 calendar days allocated within that time frame for the contractor to make any needed repairs, adjustments, etc. to the first article item. The contractor shall be responsible for all costs associated with the shipment to and from the test site and all repairs to the first article item. The contractor shall also supply all hazardous materials to be used in and/or consumed during the test. The first article item shall match within +/- 5% the documented performance of the fielded USAF BAK-12 system in terms of all performance parameters, to include end-of-arrestment stored energy, off-center engagement tendencies, and end-of-arrestment hook loads; failure to achieve this performance will result in disapproval of the first article.

3.5.2 Test reports.

3.5.2.1 Contractor test reports. The contractor shall submit a test report upon completion of the functional verification and another upon completion of the first article test. The test reports shall document all testing performed, including results of any unsuccessful test attempts, based upon data collected by the Government test team. (DI‑NDTI‑80809B, Test/Inspection Report)

3.5.2.2 Government test reports. The procuring activity will provide the contractor the Government generated test reports for the testing completed at the contractor’s facility and at NAVAIR Lakehurst. Any deficiencies identified in the test reports shall be satisfactorily corrected and any resulting changes shall be successfully implemented by the contractor into the MAAS first article test unit before proceeding with the PCA activities.

3.5.3 First article acceptance. Successful implementation of corrective actions for all deficiencies identified in the first article test report, the resulting changes being implemented in the first article test unit, and successful completion of the PCA constitutes first article acceptance.

3.5.4 Restoration. After first article acceptance, the contractor shall be responsible for any repairs necessary to restore the first article MAAS to a serviceable, “like new” condition while retaining configuration integrity.

3.5.5 Disposition. The approved first article MAAS 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 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 approval of the first article test report, PCA Configuration Audit Summary Report, and the TDP (see 3.6.4) 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 TDP 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. A Notice of Revision (NOR) shall be submitted with each ECP. Should the Government approve an ECP, the contractor shall be responsible for submitting changes to the T.O.s to reflect the changes made in the ECP. (DI-SESS-80639E, Engineering Change Proposal (ECP); DI-SESS-80642E, Notice of Revision (NOR))

3.6.2.1 TDP. The TDP 201018515, CAGE 98752 forms a part of this SOW and constitutes the end item product drawings. The TDP is mandatory for use in design and building the MAAS and no deviation from the drawings is permissible without prior approval of the procuring activity. Where tolerances could cumulatively result in incorrect fits, the contractor shall provide tolerances within those prescribed on the drawings to ensure correct fit, assembly, and operation of the MAAS. If during the manufacturing process of first article MAAS discrepancies are noted with the TDP, the contractor shall notify the procuring activity of such discrepancies. Any data prepared by the contractor or obtained from a vendor to support fabrication and manufacture of the MAAS shall be made available, upon request, for inspection by the procuring activity. Any changes to the TDP shall be processed via approved ECP(s).

3.6.2.2 Qualification of new components. In the event that the contractor desires to qualify components which are form, fit, and functionally interchangeable as substitute components for those specified on the drawings, the first article tests shall be conducted on the first article MAAS with the proposed components installed. Failure to meet any requirements specified herein during or as a result of the test shall be cause for rejection of the proposed changes. Successful performance of the first article tests does not preclude performance of any other tests deemed necessary by the procuring activity to verify form, fit, and functional interchangeability of the substitute components.

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-80640E, Request for Variance (RFV))

3.6.4 Engineering data. The contractor shall develop/produce/maintain and deliver a Technical Data Package (TDP) that accurately depicts the final product. TDP data includes, but is not limited to, Computer Aided Design (CAD) data, CAD models, model-based definition data sets, Gerber data, and Master Bill of Materials (BOM). 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 or any third party. The TDP shall represent the approved, tested, and accepted configuration of the defined delivered item(s). This shall include software and all test requirement documentation data required to test systems, subsystems, and/or components.

Vendor Item Control Drawings shall be used to specify the requirements for purchased items when such items have been approved for use in the design and are used without alteration, selection, or source qualification (testing of an item prior to procurement action to ensure that it satisfies the specified requirements). All engineering product definition data created using Government funding as a result of this contract shall be considered a part of the TDP and shall be delivered to the Government with unlimited rights. The TDP shall be created in accordance with the following American Society of Mechanical Engineers (ASME) standards: ASME Y14.100-2017, Appendix B, sections B6 through B9.1 and Appendices C, D, E, and F in conjunction with ASME Y14.24- 2012, ASME Y14.34, ASME Y14.35, ASME Y14.41, and ASME Y14.47 and as defined in the corresponding CDRL for this task to create and deliver Product Engineering Design Data and Associated Lists (Engineering Data) under this contract. Data set classification code marking in accordance with Appendix F of ASME Y14.100-2017 is required. CAD model file name and extension identification is required on drawing graphic sheets. TDP data shall specify parts marking requirements for item identification in accordance with MIL-STD-130N, other applicable documents referenced therein, and as specified in this contract. Test Criteria for Electrical and Avionics Items shall be in accordance with data set identifier 9579777 Revision B (CAGE 98752).

The TDP shall be delivered in accordance with Air Force Product Data Specification data set identifier 9579776 Revision N (CAGE 98752) referenced in attached DD Form 1423 Block 16.

(DI-SESS-81000F/T Product Engineering Design Data and Associated Lists)

3.6.4.1 Engineering Data Guidance Conference. The contractor shall support and co-chair a Guidance Conference with AFLCMC/LZPEM 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: (DI-ADMN-81249C Meeting Agenda, DI-ADMN-81250C Meeting Minutes)

a. Understanding of all CDRL requirements, applicable DIDs, specifications, and standards.

b. TDP review requirements and schedules.

c. TDP delivery requirements and schedules.

d. Contractor's drafting practices/procedures/TDP drawing formats/CAD programs.

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 Technical Data Package (TDP) deliverables.

Note: The Guidance Conference may be held in conjunction with other meetings or conferences.

3.6.4.2 In-process review (IPR) of the TDP. The contractor shall host, support, and co-chair an IPR of the engineering data, 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% completion point and shall be held, when possible, in conjunction with other reviews. Concurrent with the IPR, the contractor shall submit four (4) representative samples of each digital format of data for this project in accordance with Air Force data set identifier 9579776 (CAGE 98752).

These samples shall consist of the Native, Neutral, and Viewable formats as defined in data set identifier 9579776 (CAGE 98752) for Model-based TDPs. The contractor shall notify AFLCMC/LZPEM 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 TDPs. The contractor shall support and provide the necessary resources, that is, 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/vendor data shall be made available for review. If the quantity of subcontractor/vendor data is of sufficient magnitude, the Government may schedule a separate IPR at the subcontractor's/vendor's facility. (DI-ADMN-81249C Meeting Agenda, DI-ADMN-81250C Meeting Minutes)

3.6.4.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.6.4.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/produced and funded 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/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.

d. Revisions to existing engineering drawings/models and associated lists and other documentation to be included in the TDP for which the contractor is the current design activity shall result in the delivery of the entire revised document and associated data file. For example, when a portion of a document is revised the entire document shall be delivered.

3.6.5 Configuration audit plan and Physical Configuration Audit (PCA).

3.6.5.1 Configuration audit plan. The contractor shall develop a Configuration Audit Plan to be used in performance of the PCA. (DI-SESS-81646C, Configuration Audit Plan)

3.6.5.2 PCA. After successful completion of all first article testing and Government approval of the first article test report, the contractor shall host a Physical Configuration Audit (PCA) at the contractor’s facility in accordance with the approved IMS and Configuration Audit Plan to verify that the as-built, as-tested configuration of the MAAS first article test unit conforms to its technical documentation which defines the final product baseline and that the accuracy of the TDP documentation reflects the MAAS production design. At a minimum, the PCA shall include a detailed audit of engineering drawings, specifications, technical data, quality control records, and tests utilized in production of the as-built, as-tested configuration of the MAAS first article test unit. The PCA shall be accomplished in a non-destructive manner.

A team of up to five Government personnel will conduct the PCA at the contractor’s facility with contractor’s assistance. The contractor shall be responsible for determining the extent that subcontractors, vendors, and suppliers participate in the PCA audit. At a minimum, the contractor shall provide the following support during the PCA unless otherwise agreed upon by the Government prior to the PCA:

a. PCA support staff comprised of configuration management, engineering, technicians, etc.

(as required).

b. Safe and secure working area for Government personnel in accordance with current Occupational Safety and Health Administration (OSHA) regulations.

c. Material handling equipment, tooling, other pertinent hardware, shop stock, waste disposal, any relevant operation or safety conformation, and measurement equipment, which shall be laboratory precision type, calibrated at proper intervals to ensure laboratory accuracy.

d. Disassemble and assemble hardware items as necessary to complete the PCA. (NOTE: The item shall be disassembled by the contractor to the lowest component level as defined by the TDP, except that parts that are joined by a method that is intended to be permanent, such as welding, brazing, soldering, swaging, or crimping, are not required to be separated from each other. After the item is disassembled, a team of the Government personnel will conduct the PCA for up to five workdays.)

e. Complete set of drawings, procedures, specifications, and inspection/acceptance procedures.

f. Perform all measurements and non-destructive tests as directed by the Government representatives to ensure that the audited items conform to the TDP.

g. Ensure all data and artifacts tie, trace, and link from the top-level to the lowest component and document any identified non-conformances.

h. Reassemble the item in accordance with applicable drawings, procedures, specifications, inspection/acceptance procedures, and T.O. upon conclusion of the PCA.

At the conclusion of the PCA, the contractor shall generate a configuration audit summary report with all non-conformances identified as traceable action items within the report. The contractor shall also generate the audit minutes. Note: The Government will not provide configuration audit summary report approval until all action items are complete and accepted to the satisfaction of the Government PCA team. (DI-SESS-81022E, Configuration Audit Summary Report; DI-ADMIN- 81249C, Meeting Agenda; DI-ADMIN-81250C, Meeting Minutes)

3.7 Government furnished equipment (GFE). At the request of the contractor, the Government will furnish or provide access to a complete MAAS located at Civil Engineer Maintenance Inspection and Repair Team (CEMIRT), Tyndall AFB FL within 60 days after contractor’s request for the GFE. The contractor shall have use of the GFE until the first article test unit is approved by the Government. After that, the GFE shall be returned to CEMIRT in the same condition as it was received by the contractor. The contractor shall be responsible for all costs associated with shipping the GFE to and from the contractor’s facility as well as for any repairs that may be necessary to restore the GFE to a serviceable condition while retaining configuration integrity. If instead the contractor prefers visiting CEMIRT to access a MAAS, the contractor shall notify the procuring activity within 30 days prior to visit.