SOW_09-Jul-2021.pdf

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

2021-07-09

Statement of Work (SOW) for

MOBILE AIRCRAFT ARRESTING SYSTEMS

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

2.3 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.1.4 Integrated master plan (IMP)

3.1.5 Integrated master schedule (IMS)

3.2 Conferences and program reviews

3.2.1 Post award conference

3.2.2 Technical reviews

3.2.2.1 Design reviews

3.2.2.1.1 Design review location and schedule

3.2.2.1.2 Design review content

3.2.2.2 Test readiness review (TRR)

3.2.2.3 Technical review documentation

3.2.3 Program Management Review support

3.2.4 Conference room

3.2.5 Meeting agendas

3.2.6 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 Corrosion control

3.3.3 Risk management

3.4 Logistics

3.4.1 Technical Order (TO) requirements

3.4.2 Provisioning

3.4.2.1 Provisioning Guidance Conference

3.4.3 Training/familiarization

3.4.3.1 Installation, operation and maintenance orientation

3.4.3.2 Installation, operation and maintenance familiarization/orientation material

3.5 Testing and evaluation

3.5.1 Design analysis

3.5.2 First article test

3.5.2.1 First article test procedures

3.5.2.2 First article testing

3.5.2.3 First article test daily situation reports (SITREPs)

3.5.2.4 First article test report

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.2 Production release

3.6.2 Engineering Change Proposals (ECPs)

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

1. SCOPE

This document defines the tasks associated with the procurement and qualification of Mobile Aircraft Arresting Systems (MAAS) as described by Technical Order 35E8-2-10-1 and the USAF data package beginning with top level drawing 201018515 and is to be used in conjunction with Technical Order 35E8-2-10-1.

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-313F 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-1568C Materials and Processes for Corrosion Prevention and

Control in Aerospace Weapons Systems

MIL-STD-3035

MIL-STD-3036

MIL-HDBK-29612-3A

Design Criteria Standard USAF Aircraft Arresting Systems Test Method Standard USAF Aircraft Arresting Systems Development of Interactive Multimedia Instruction

2.1.2 Other Government documents, drawings, and publications.

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

DATA ITEM DESCRIPTIONS (DIDs)

DI-MGMT-80004A Management Plan DI-SAFT-80101C System Safety Hazard Analysis Report

DI-MGMT-81928 Contractor's Progress, Status and Management Report DI-MISC-80508B Technical Report/Study Services 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-ILSS-80872 Training Materials DI-CMAN-81218 Product Base Line Index (PBLI) DI-ADMN-81249B Conference Agenda DI-ADMN-81250B Conference Minutes DI-MFFP-81403A Corrosion Prevention and Control Plan DI-SAFT-81626 System Safety Program Plan DI-SESS-81758A Logistics Product Data DI-MGMT-81861 Integrated Program Management Report (IPMR) DI-SESS-81874 Engineering Data for Provisioning (EDFP) DI-SESS-81000 Product Drawings/Models and Associated Lists

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

2.3 Order of precedence. In the event of a conflict between the text of this document and the references cited herein, the text of this document takes precedence. Nothing in this document, however, supersedes applicable laws and regulations unless a specific exemption has been obtained.

3. REQUIREMENTS

3.1 Program management.

3.1.1 Program manager. The contractor shall identify to the Government and maintain a single point of contact (Program Manager) for all matters under this contract. The contractor shall also ensure that all program management personnel assigned to the program shall be available, as required, to meet program objectives.

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. The current program integrated master schedule (IMS) (see 3.1.5); risk management analysis, mitigation plan, and tracking (see 3.3.3); shall be provided as attachments to the monthly status report.

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

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

3.1.5 Integrated master schedule (IMS). A baseline IMS shall be developed at the start of the program in accordance with DI-MGMT-81861, Format 6. 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.3). (DI-MGMT-81861, Integrated Program Management Report (IPMR))

3.2 Conferences and program reviews.

3.2.1 Post award conference. The Government will convene a post award conference with the contractor at a location that is mutually agreeable to both parties 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 Technical reviews.

3.2.2.1 Design reviews.

3.2.2.1.1 Design review location and schedule. The contractor shall conduct a preliminary design review (PDR) within 4 months after the contract is awarded to review any drawing discrepancies discovered. The contractor shall conduct a critical design review (CDR) within 8 months after the contract is awarded to review any additional drawing discrepancies discovered. The design reviews shall be held at a location that is mutually agreeable to both parties, or via teleconference.

The PCO will coordinate the actual date, time, and location of the reviews with the contractor.

3.2.2.1.2 Design review content. The PDR and CDR shall include formal technical reviews of the proposed design drawing package; program risks shall be reviewed on a technical and schedule basis. Each review shall include, but is not limited to, preliminary calculations; any necessary design studies or analyses including the design analysis as required in 3.5.1 and 3.6.4; preliminary drawings, including equipment layout drawings (packaging), proprietary or restricted design processes, components, and information; electrical and mechanical design; environmental control;

thermal design aspects; software design; training materials; lists of materials, parts, and processes;

human engineering elements; corrosion control; maintainability; production capability and manufacturing; and quality considerations. Final drawings, final calculations, and any mockups or any assemblies shall be made available for the Government review as well. All applicable comments from the PDR shall be incorporated into the CDR design documentation.

3.2.2.2 Test readiness review (TRR). The contractor shall conduct a test readiness review (TRR) 14 days prior to the start of the first article test. 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 at a location that is mutually agreeable to both parties, or via teleconference. The PCO will coordinate the actual date, time, and location of the reviews with the contractor.

3.2.2.3 Technical review documentation. The contractor shall prepare all necessary detailed status reports for the technical review meetings, conference agendas, and conference minutes. The contractor shall prepare formal documentation of the TRR. (DI-MISC-80508, Technical Report/Study Services; DI-ADMN-81249B, Conference Agenda; DI-ADMN-81250B, Conference Minutes)

3.2.3 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.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-81249B, Conference Agenda)

3.2.6 Meeting minutes. The contractor shall provide a written record of the discussions, decisions, and action items identified at each meeting. Minutes shall include presentation material.

(DI-ADMN-81250B, 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 shall be provided 14 days prior to the PDR; updated versions of the analysis shall be provided 14 days prior to the CDR, 14 days prior to the TRR, and with the first article test report.

(DI-SAFT-81626, System Safety Program Plan; DI-SAFT-80101C, 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. This information shall be documented in the design analysis (see 3.5.1) and reviewed at the technical reviews.

3.3.2 Corrosion control. The contractor shall establish, conduct, document, and maintain a corrosion prevention control program using 5.1.1 of MIL-STD-1568C for guidance. An initial corrosion prevention and control plan shall be provided 14 days prior to the PDR; the second submission of the plan shall be provided 14 days prior to the CDR. (DI-MFFP-81403A, Corrosion Prevention and Control Plan)

3.3.3 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 update existing USAF technical manuals in accordance with TM-86-01. (TM-86-01, Air Force Technical Manual Contract Requirements)

3.4.2 Provisioning. The contractor shall identify and recommend logical spare and repair parts sufficient to meet system and equipment operation and supportability in accordance with the Air Force Initial Provisioning Performance Specification (IPPS). GEIA-HB-0007 (Logistics Product Data Handbook) shall be used as a guide. Format shall be consistent with existing Government Provisioning data system (D220). The following Data Item Descriptions (DIDs) apply:

DI-SESS-81758A/T Logistics Product Data Specific Logistics Product Data to be submitted:

- Provisioning Parts List (PPL)

- Common and Bulk Items List (CBIL)

- Short Form Provisioning Parts List (SFPPL)

- Design Change Notices (DCNs)

- Statement of Prior Submission (SPS)

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

3.4.2.1 Provisioning Guidance Conference (PGC). A 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 must be communicated in some forum in which the AFMC Form 718 (Provisioning Performance Schedule (PPS)) must be documented/completed, signed by both the Government and contractor, and a contract modification issued, if required. (DI-ADMN-81249B, Conference Agenda;

DI-ADMN-81250B, Conference Minutes)

3.4.3 Training/familiarization.

3.4.3.1 Installation, operation and maintenance orientation. The contractor shall plan for and conduct a one-time classroom and “hands-on” installation, operation and maintenance orientation for the United States Air Force (USAF) to familiarize the users with the MAAS system. The orientation shall include but not be limited to: operational familiarization, ease of maintaining the unit for both corrective and preventative efforts, support equipment review, application of the technical manual in regards to the various MAAS types, troubleshooting/fault isolation, theory of operation, consumable item clean up requirements and methods post aircraft engagement, MAAS equipment reset guidance and procedures, and scheduled or required concrete pad and anchor Non- Destructing Inspection (NDI) requirements. This orientation shall take place at the first installation site where a MAAS system (resulting from this effort) is to be installed within USAF. The MAAS installation/storage locations that relate to this effort will be at one of the following Air Force Bases (AFBs) or airfields: Abu Dhabi UAE, Al Udeid AB, Anderson AFB, Aviano AB, Elmendorf AFB, Holloman AFB, Nellis AFB and Thumrait AB. Testing will take place at Naval Air System Command (NAVAIR), Lakehurst, NJ. The Government will notify the contractor of the first installation schedule/date(s) and the location (to be at one of the aforementioned airfields) no later than 45 days prior to the scheduled installation occurrence. The contractor shall provide all required reference material in accordance with 3.4.3.2 herein for up to 30 Government personnel, and training should be no longer than three days in length. Copies of the latest draft effort in developing the T.O. for the MAAS shall also be available (the T.O. must have at a minimum passed the 70 percent review). The contractor is not required to provide transportation to and from the site, lodging, or meals for the approximately 30 Government personnel during the orientation. (DI-ILSS-80872, Training Materials). Travel for training will be unit funded for US Government personnel. Contractor labor and travel cost to conduct training is estimated at $5,400.00.

3.4.3.2 Installation, operation, and maintenance familiarization/orientation material. The contractor shall develop an interactive multimedia system (program media) on CD ROM or DVD to be used during the installation, operation, and maintenance orientation and for use in the field for familiarization of installation, operational and maintenance personnel at the organizational level. MIL-HDBK-29612-3A shall be used as a general guide, although contractor format is acceptable. This program media shall be in sufficient detail to provide the technician the required skills to operate and provide general maintenance for the up-keep and resetting of the MAAS as described within the technical order 35E8-2-10-1. The program media shall also be in sufficient detail to allow the Air Education and Training Command (AETC) to formulate a training course for future use. The program media shall be compatible with existing USAF personal computers (Microsoft Windows based operating systems) and consist of all materials (e.g., software, firmware) necessary to execute the material. Approximately 30 copies of the draft version program media shall be available for use at the installation, operation and maintenance orientation for Government personnel. Feedback from the Government personnel attending the operation and maintenance orientation shall be gathered and used to develop the final version of the program media to be used for organizational level familiarization. The program media shall be subject to final Government approval before final delivery. Final delivery of two copies of the program media shall be made to AFLCMC/WNZEC. One copy of the program media shall be sent with each MAAS as pack up data. Note: Excluding the first article MAASs, no MAAS delivery acceptance will occur without completed and Government accepted orientation material. (DI- ILSS-80872, Training Materials, MIL-HDBK-29612-3A)

3.5 Testing and evaluation.

3.5.1 Design analysis. A design analysis of the system and each subsystem shall be performed to verify compliance with this SOW and each applicable requirement of MIL-STD-3035 and MI:- STD 3036. MIL-STD-3035 Sections 3.3, 5.1.2.1-5.1.2.4 shall not apply. Also, in 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 analysis shall include, but is not limited to, environmental and hazardous material management (see 3.3.1.2 a service life analysis). A Material Safety Data Sheet (MSDS) shall be provided for each hazardous material identified for use in the program (see 3.3.1.2). (Note that the system safety hazard analysis is addressed in 3.3.3.1.). An initial design analysis shall be provided 14 days prior to the PDR; updated versions of the analysis shall be provided 14 days prior to the CDR, 14 days prior to the TRR, and with the first article test report. (DI-MISC-80508, Technical Report/Study Services)

3.5.2 First article test.

3.5.2.1 First article test procedures. The Government shall work directly with NAVAIR, Lakehurst, NJ testing facility to develop detailed first article test procedures, which shall address all requirements identified in the 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. 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-80603A, Test Procedure)

3.5.2.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. The contractor shall have a system available for first article testing 300 days After Receipt of Order (ARO).

3.5.2.3 First article test daily situation reports (SITREPs). Throughout the first article test, the contractor shall submit a daily situation report (SITREP) that shall cover all monitored daily test activities. Examples are:

a. Test logs.

b. Observed data to include: Observations, comments, anomalous conditions, or other items completed for each first article unit.

c. Recorded data as applicable to the type of equipment.

d. Records of preventive maintenance activities performed.

e. Daily Failure Reporting and Corrective Action System (FRACAS) status updates to include total number of failures occurred. Resolutions of previous failures and implementation of corrective actions applicable to the Reliability Growth Test (RGT)

FRACAS.

f. For RGT, tracking of reliability growth to include the reliability growth curve for the number of hours completed.

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

3.5.2.4 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. Failure reports generated as a result of the process shall be included with results of unsuccessful test attempts. (DI-NDTI-80809B, Test/Inspection Report)

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 Technical Order 35E8-2-10-1.

3.6.1.1.2 Allocated baseline. All of the documents used to produce and define the accepted CDR configuration shall constitute the allocated baseline. (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 article test report and TOs have been delivered and approved by the procuring activity. The contractor shall deliver production units 210 days ARO.

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-80639E, Engineering Change Proposal (ECP); DI-SESS-80642E, Notice of Revision (NOR)).

3.6.3 Request for Variance (RFV). The contractor shall prepare a 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 provide USAF with all necessary engineering drawings to allow complete and unassisted construction and installation of the MAAS onto USAF airfields. Specifically, the contractor shall provide the Government with one engineering/installation drawing package for each of the types of MAAS installations. This data shall also include information related to pass/fail criteria for non-destructive tensile testing of concrete anchors and epoxy-repaired anchors at the time of new installation and at the time of 10 year overhauls. This data includes, but is not limited to, AutoCAD data (i.e., dwg files). (DI-

SESS-81000)

Such engineering/installation drawings shall convey all the required information necessary to allow surface-type concrete slab construction (for installment of the MAAS systems) at runway widths ranging from 150-feet to 300-feet. At a minimum, the contractor-generated engineering/installation drawings shall contain the following:

a. MAAS concrete slab locations (distance to the runway edge),

b. MAAS concrete slab orientations (with respect to the runway),

c. Concrete slab dimensions,

d. Concrete slab geometry (front, side and top views),

e. Module anchor details and locations,

f. Rebar size(s) and locations (within the concrete slabs),

g. Tolerances,

h. Finish,

i. Materials (and their callout locations), and

j. Other miscellaneous requirements (i.e., jet blast deflector locations and bolt hole patterns, etc.)

Such engineering/installation drawings shall accurately and unambiguously detail the MAAS system and components. This information shall be provided in accordance with DI-SESS-81000 and prior to operational inspection, if applicable. Further, the contractor shall develop these drawings with USAF Commercial and Government Entity (CAGE) Code 98752 and title block information in accordance with the drawing template shown in Appendix A. The drawings are subject to WNZEC (technical) and AFLCMC/ENGE (format) approvals. The Government shall own all rights to the drawings provided.

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:

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.

i. Number of discrepancies or problems discovered with the USAF owned data package, specified by the top level drawing 201018515, including parts availability, tolerance issues, dimensional interference, typos and other data problems. The contractor shall perform full due diligence of the USAF data package in preparing for this discussion so that all technical issues can be addressed to the maximum extent possible prior to PDR, CDR and FAT.

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

(DI-ADMN-81249B, Conference Agenda; DI-ADMN-81250B Conference Minutes)

3.6.4.2 In-process review (IPR) of the TDP. The contractor shall host, support, and co-chair an IPR of the engineering drawings and associated lists and other documentation to be included in the TDP. The IPR shall be conducted only after the contractor's quality assurance personnel have completely reviewed the data and determined that data are of sufficient quality that Government time will be effectively utilized during the review. IPR may be scheduled when data has reached the 50 percent completion point and shall be held, when possible, in conjunction with other reviews (for example, PDR or CDR). 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 TDP. 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-81249B, Conference Agenda; DI-ADMN-81250B, Conference 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.