FINAL SRC SOW (05 JAN 2021) V.pdf

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

05 January 2021

Statement of Work (SOW) for

Strategic Replenishment Contract (SRC) for Support Equipment and Vehicles (SE&V) Division

Prepared by

SUPPORT EQUIPMENT AND VEHICLES 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 SRC nature…………………………………………………………………………….7

3.2 Data management, access, and reporting

3.2.1 Multi-user ECP Automated Review System (MEARS)

3.2.2 Joint Engineering Data Management Information and Control System

(JEDMICS)

3.2.3 Electronic Data Exchange (EDE) system

3.3 Program management

3.3.1 Program manager

3.3.2 Plant access

3.3.3 Monthly status report

3.4 Conferences and program reviews

3.4.1 Postaward conference

3.4.2 Test readiness review (TRR)

3.4.3 Technical review documentation

3.4.4 Program Management Review support

3.4.5 Conference room

3.4.6 Meeting agendas

3.4.7 Meeting minutes

3.5 Systems engineering

3.5.1. Hazardous materials

3.5.2 Recycled, recovered, environmentally preferable, or bio-based materials

3.5.3 Counterfeit Prevention Plan (CPP)

3.5.3.1 Applicability

3.5.3.2 Definitions

3.5.3.3 Parts availability and use of parts brokers

3.5.3.4 Procurement policies

3.5.3.4.1 Risk assessment

3.5.3.5 Detection and avoidance responsibilities

3.5.3.6 Testing and verification

3.5.3.7 Configuration identification and traceability

3.5.3.8 Counterfeit notification and reporting

3.5.3.9 Counterfeit protection training

3.5.4 Risk management…………………………………………………………………..13

3.6 Logistics

3.6.1 Technical Order (TO) requirements

3.6.2 Provisioning requirements………………………………………………………….13

3.6.2.1 Provisioning Guidance Conference………………………………………………14

3.7 Testing and evaluation

3.7.1 First article (FA) CSE qualification/acceptance

3.7.1.1 FA test plan

3.7.1.2 FA test procedures

3.7.1.3 FA testing

3.7.1.4 FA test report

3.7.1.5 Production release

3.7.2 Restoration

3.7.3 Disposition

3.7.4 Production acceptance testing……………………………………………………...15

3.7.4.1 Production acceptance test procedure……………………………………………15

3.7.4.2 Production acceptance test report………………………………………………..16

3.8 Configuration management and control

3.8.1 Product baseline

3.8.1.1 Engineering Data List (EDL)

3.8.1.1.1 Engineering Change Proposals (ECPs)

3.8.1.1.2 TDP

3.8.1.1.3 Qualification of new components

3.8.1.1.4 Request for Variance (RFV)

3.8.1.2 Approved sources of supply list

3.8.1.2.1 CSE item obsolescence/Diminishing Manufacturing Sources and Material Shortages (DMSMS)

3.8.1.2.2 Technical Support Request (TSR)

3.8.1.2.2.1 Surplus CSE items……………………………………………………………17

3.9 Government furnished information (GFI)

3.10 CSE item unique identification

4 QUALITY ASSURANCE (QA)

4.1 Responsibility for inspection

4.2 Warranty………………………………………………………………………………18

5 PACKAGING

1. SCOPE

This document defines the tasks associated with sourcing; acquiring; in certain instances, qualifying; and delivering approximately 500 National Stock Numbers (NSNs) from a subset of approximately 60 Federal Stock Classes (FSCs) within the Support Equipment and Vehicles (SE&V) portfolio via the following capability–aligned, multiple award, indefinite delivery, indefinite quantity (IDIQ) Strategic Replenishment Contracts (SRCs): Base Support SRC, Flightline Maintenance Testing and Tooling (FMT&T) SRC, and Aerospace Ground Equipment (AGE) and Munitions Material Handling Equipment (MMHE) SRC. The contractor shall perform these functions from the currently approved/qualified sources of supply as provided by the Government. NSNs with one or multiple approved sources of supply as well as those not procured in the recent years are included in the SRCs. The Base Support SRC includes, but not limited to, Basic Expeditionary Airfield Resources (BEAR), Base and Aircraft Arresting Systems (B&AAS), and Fuels Support Equipment (FSE). The FMT&T SRC includes, but not limited to, electronic and mechanical aircraft maintenance testers, aircraft engine trailers, specialized tooling, and various backshop equipment. The AGE and MMHE SRC includes, but not limited to, aerial stores lift trucks, maintenance stands, air conditioners and heaters, secondary power, and miscellaneous AGE equipment (cranes, dollies, lift adapters). All NSNs included are comprised of ground and aircraft common support equipment (CSE) end items with Economic Repair and Recoverability Code (ERRC) codes of S and U with initial Government estimated costs of greater than $40,000 per asset. These assets support the United States Air Force (USAF), Foreign Military Sales (FMS), Air National Guard (ANG) and other Department of Defense (DoD) customers. All NSNs included are replenishments for existing capabilities and do not constitute new start programs. For NSNs where the Government is in possession of complete technical data packages (TDPs), the tasks defined in this document are to be used in conjunction with the requirements outlined in the solicited TDPs. After award of the basic contract, any further ordering and resultant delivery shall take place via a delivery order process.

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-130N(1) NOT1 Identification Marking of U.S. Military Property

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-MGMT-81928 Contractor's Progress and Status Report

DI-MISC-80508B

DI-NDTI-80566A

Technical Report/Study Services Test Plan

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 NOT 2 Test/Inspection Report DI-ADMN-81249B Conference Agenda

DI-ADMN-81250B

DI-SESS-81758A/T NOT1

Conference Minutes Logistics Product Data

DI-MISC-81832

DI-SESS-81874

Counterfeit Protection Plan Engineering Data for Provisioning (EDFP)

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

DEPARTMENT OF DEFENSE GUIDES

(no identifier) Risk Management Guide for DoD Acquisition, Sixth Edition, Version 1.0

DEPARTMENT OF DEFENSE MANUALS

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

DRAWINGS

Part Number

CAGE

Code

Nomenclature multiple multiple multiple

(Copies of drawings are available from JEDMICS.)

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.

SOCIETY OF AUTOMOTIVE ENGINEERS (SAE)

AS5553 Aerospace Standard, Counterfeit Electronics Parts;

Avoidance, Detection, Mitigation, and Disposition

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

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 SRC nature. Due to the unique nature of this effort, which encompasses approximately 500 NSNs from approximately 60 FSCs within three capability–aligned, multiple award, IDIQ basic contract vehicles, with deliverable items procured via award of individual delivery orders, every requirement denoted herein is not necessarily applicable to each delivery order. For acquisition purposes, requirements herein with the phrasing “when required by a delivery order”, or other similar phrasing, may be considered as only required when explicitly stated by the Government procuring activity in an individual delivery order. Requirements contained herein without the phrasing “when required by a delivery order”, or other similar phrasing, may be considered to always be applicable to the SRC contractor. Any misunderstanding, conflict, or confusion by the SRC contractor regarding applicability of any requirements contained within this document shall be referred to the Procuring Contracting Officer (PCO) for resolution. The term “contract” contained herein applies to any of the SRC contracts awarded.

3.2 Data management, access, and reporting.

3.2.1 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 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.2.2 Joint Engineering Data Management Information and Control System (JEDMICS). The contractor shall have access to the Government JEDMICS in order to receive the technical and electronic data necessary to fulfill the requirements for the NSNs solicited with the Government TDPs. The contractor shall maintain access to JEDMICS for the entire duration of the contract performance. Upon contract award and no later than the post award conference (PAC), the contractor shall contact the Government program manager to request access to JEDMICS. The contractor shall ensure at all times that there are two or more contractor’s personnel with access to JEDMICS. If for any reason, outside of the Government’s responsibility, the contractor doesn’t have or lost access to JEDMICS, the contractor shall immediately notify the Government. The contractor will not be allowed to bid on any CSE items via the delivery order process until the access to JEDMICS is established.

3.2.3 Electronic Data Exchange (EDE) system. The contractor shall use an internal EDE system to provide delivery order management, tracking, financial transactions, and customer management for the entire duration of the contract performance. The contractor’s existing EDE system shall be utilized with the minimum changes necessary to conform to the requirements specified herein;

Government access to the contractor’s EDE system is not required. The contractor shall generate a status report from the EDE system in Excel spreadsheet format (or similar) and provide it to the Government as an attachment to the monthly status report (see 3.3.3). The information included shall be the latest information available at the time of submission to the Government and at a minimum include the following:

a. Contract data: CLIN data, delivery order number and date, and contract ARO.

b. Ordering data: NSN, noun, part number, quantity ordered, requisition number, and unit price.

c. Shipping data and delivery information: delivery order due date, quantity shipped, ship date, trackable shipping document number, delivery date, and delivery location.

d. Configuration control data: Changes to TDPs, Engineering Change Order number, Request for Variations number.

e. Vendor information data: vendor name, CAGE code, and vendor business type (i.e., small business or large business).

f. Quality control data: detection of quality problems and defects, identification of root causes and implementation of corrective actions.

3.3 Program management.

3.3.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.3.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. In the event of discrepancies identified during the Government inspection and acceptance of the CSE end item NSN, during testing of individual items, during the investigation of Product Quality Deficiency Reports (PQDRs), during Engineering Investigations (formally known as Material Deficiency Report

(MDR)), or other similar activities, the contractor shall facilitate Government access to their subcontractor(s) facility(s) where the item was manufactured.

3.3.3 Monthly status report. The contractor shall submit a monthly status report. The monthly status report 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. Any hazardous materials, as defined in AFI 32-7086, to be delivered under this contract, including locations, quantities, and special handling and disposal shall be identified in the monthly status report. The contractor’s status report from the EDE system (see 3.2.3) and risk management analysis, mitigation plan, and tracking (see 3.5.4) shall be provided as attachments to the monthly status report. (A007, DI-MGMT-81928, Contractor's Progress and Status Report)

3.4 Conferences and program reviews.

3.4.1 Post award conference (PAC). The Government will convene a PAC with the contractor within 30 days after contract award. The PAC shall be held virtually using an electronic communication venue mutually agreeable by both the Procuring Contracting Officer (PCO) and the contractor. The number of contractor attendees shall be limited to a maximum of four persons and the PAC duration shall not exceed four hours. The PCO will coordinate the actual date and time of the PAC with the contractor after contract award.

3.4.2 Test readiness review (TRR). When a first article test is required by a delivery order, 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 as specified in a delivery order. The PCO will coordinate the actual date, time, and location of the reviews with the contractor.

3.4.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. (A017, DI-MISC-80508, Technical Report/Study Services; A002, DI-ADMN-81249, Conference Agenda; A006, DI-ADMN-81250, Conference Minutes)

3.4.4 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 via teleconference quarterly or as specified in a delivery order.

3.4.5 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.4.6 Meeting agendas. With exception to the PAC agenda, the contractor shall publish an agenda for all meetings and conferences specified herein. 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. (A001, DI-ADMN-81249, Conference Agenda)

3.4.7 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. (A005, DI-ADMN-81250, Conference Minutes)

3.5 Systems engineering.

3.5.1 Hazardous materials. The contractor shall manage hazardous materials, including those embedded in the CSE item or used during operation or maintenance, as an element of the Systems Engineering process. The CSE shall not generate or use Class I or Class II Ozone Depleting Compounds/Substances (ODC/ODS) during operation, maintenance, or disposal. The use of hexavalent chromium is also prohibited, unless explicitly authorized within the TDP for a CSE item. 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. The information shall be documented and submitted with the monthly status report (see 3.3.3).

3.5.2 Recycled, recovered, environmentally preferable, or bio-based materials. Recycled, recovered, or environmentally preferable, or bio-based materials should be used to the maximum extent possible provided that the material meets or exceeds the operational and maintenance requirements, and promotes economically advantageous life-cycle costs. Used, rebuilt, refurbished, or surplus parts, components, sub-assemblies, or end items shall not be provided except as explicitly authorized by the PCO on a case-by-case basis. Magnesium alloys, wood products, polyvinyl chloride (PVC) products, polyester, any materials containing asbestos, or room-temperature vulcanization (RTV) which yields acetic acid, shall not be used unless explicitly authorized within the TDP for an item.

3.5.3 Counterfeit Prevention Plan (CPP). Contractors that supply electronic parts or CSE items that contain electronic parts shall establish policies and procedures to avoid, detect, mitigate and disposition counterfeit electronic parts to prevent such parts from entering the USAF/DoD supply chain. These policies and procedures shall be documented in a CPP for submission and approval in accordance with Data Item Description (DID) DI-MISC-81832 and accomplished for all specified contract items. DI-MISC-81832 is applicable to Parts, Material, and Processes Selection (PMPS) associated with delivery of systems and assemblies to the USAF and DoD. The requirements established by DI-MISC-81832 also apply to electronics components procured in sustainment of such systems and assemblies. The requirements of the DoD-adopted SAE AS5553, Aerospace Standard, Counterfeit Electronics Parts; Avoidance, Detection, Mitigation, and Disposition shall also apply. (A011, DI-MISC-81832, Counterfeit Protection Plan)

3.5.3.1 Applicability. The contractor shall identify all business locations and programs to which the CPP applies. The CPP shall address materials, hardware, electronic parts, and procured assemblies.

3.5.3.2 Definitions. The contractor shall utilize definitions in accordance with AS5553 to ensure consistency. Any contractor-derived definitions must be included in an appropriate CPP appendix or annex. (Ref. 3, 3.1, 3.2, 3.3, and Appendix H of AS5553)

3.5.3.3 Parts availability and use of parts brokers. The contractor shall not procure materials, systems, assemblies, subassemblies, or parts from parts brokers when available from Original Manufacturers (OM) or their Authorized Distributors. In cases where materials, systems, assemblies, subassemblies, or parts are no longer available from the OM or their Authorized Distributors, procurement from brokers may be authorized as defined by the contractor’s policy and their CPP. (Ref. 4.1.1, 4.1.2.e., and Appendix A of AS5553)

3.5.3.4 Procurement policies. The contractor shall provide and implement policy directing development and implementation of business practices, procedures, and processes to prevent procurement of Counterfeit materials and parts. The contractor shall identify the appropriate office(s), business units, functional organizations, and programs, who shall have responsibility for development, maintenance, and implementation of the CPP. The CPP shall identify the specific roles and responsibility for each. (Ref. 4.1.2, 4.1.3, and Appendices B, C, and D of AS5553)

3.5.3.4.1 Risk assessment. The contractor shall address the risk of using unknown sources and/or unauthorized suppliers in the CPP. Application or technical risk assessments shall establish the effect that counterfeit parts may have on in accordance with performance. Vendor or source of supply risk assessments shall establish the potential for obtaining counterfeit parts. Using any risk analysis tool acceptable to the Government, the contractor shall conduct a risk assessment based upon item characteristics and how likely it is that a counterfeit part will be received. The contractor shall identify and describe in the CPP how parts are selected for assessment and what risk is acceptable based upon the parts design, construction, material, and functional requirements. As a minimum, analysis shall be completed for flagging high risk items, such as items that are obsolete, discontinued, rare, etc. The contractor shall require completion of a trade study, documented within the CPP that shall facilitate determining whether 100% testing of parts procured from after-market sources is more cost effective than qualification or requalification of a manufacturer. (Ref. 4.1.2,

4.1.3 and Appendices B, C, and D of AS5553)

3.5.3.5 Detection and avoidance responsibilities. The contractor shall establish processes for the review and approval of contractor and applicable subcontractor systems for the detection and avoidance of counterfeit electronic parts and suspect counterfeit electronic parts, which processes shall be comparable to the processes established for contractor business systems under section 893 of the Ike Skelton National Defense Authorization Act for Fiscal Year 2011 (Public Law 111–383;

124 Stat. 4311; 10 U.S.C. 2302 note). The contractor shall flow down such requirements and processes to their subcontractors in accordance with ODASD Memo titled “Overarching DoD Counterfeit Prevention Guidance”, dated 16 March 2012. (Ref. AS5553, 4.1.4, 4.1.5, Appendix E)

3.5.3.6 Testing and verification. The contractor shall establish and accomplish testing and verification processes for items not received from an original equipment manufacturer, original component manufacturer, or authorized distributor that are identified as having high risk for counterfeit potential. These processes apply to prime contracts, and to subcontracts or suppliers below the prime contracts. The contractor shall provide a list of acceptable test facilities if the subcontractor or supplier does not have the capability to in accordance with form required testing.

Submittal of Certificates of Compliance indicating the parts are not counterfeit shall be acceptable for verification of testing. (Ref. 4.1.4 and Appendix E of AS5553)

3.5.3.7 Configuration identification and traceability. The contractor shall identify and control the configurations of all systems, assemblies, subassemblies, and parts, and enable mechanisms to provide traceability of parts. The contractor shall report to the Government when control of the configurations of all systems, assemblies, subassemblies, and parts, and mechanisms to provide traceability of parts are not possible. The contractor shall identify the specific systems, assemblies, subassemblies, and parts beyond the contractors’ control. The contractor shall be responsible for detecting and avoiding the use or inclusion of counterfeit materials and parts, to include procured assemblies and subassemblies, in such products and shall be responsible for the rework or corrective action that may be required to resolve the use or inclusion of counterfeit materials and parts. The cost of counterfeit electronic parts and suspect counterfeit electronic parts and the cost of rework or corrective action that may be required to remedy the use or inclusion of such parts are not allowable costs under Department contracts, unless:

a. the contractor has established a counterfeit avoidance/detection system approved by the DoD,

b. the counterfeit parts were procured from a DoD-accredited trusted supplier or provided as Government property, and

c. the contractor has provide timely notification to the Government. (Ref. 4.1.6 and

Appendix F of AS5553)

3.5.3.8 Counterfeit notification and reporting. The contractor shall report in writing to the Government procuring activity within 30 days of determining any end item, component, part, or material contained in supplies purchased by the Department of Defense, or purchased by a contractor or subcontractor for delivery to, or on behalf of, the Department, contains counterfeit electronic parts or suspect counterfeit electronic parts for the purpose of investigation and notification of the Air Force Office of Special Investigations (AFOSI). The PCO will coordinate reporting to the appropriate Program Management/Item Management, System Engineering Management, the AFMC Discrepant Materiel Reporting Program (DMRP) Office in 406 SCMS/GULAB, and the AFOSI. Additionally, the contractor shall within the same 30 day period ensure all suspected or confirmed counterfeit items are entered into the Government-Industry Data Exchange Program (GIDEP) system, which will serve as the DoD central reporting repository.

(Ref. 4.1.7 and Appendix G of AS5553)

3.5.3.9 Counterfeit prevention training. The contractor shall provide appropriate training and shall require all in accordance with personnel working procurement within their company, to include at a minimum their supply chain management specialists, receiving inspectors, and engineers, to complete said training. The contractor shall determine the appropriate training required. Training may be developed in-house or may be other Industry accepted training. The CPP shall describe and list the training provided by the contractor to their in accordance with personnel.

3.5.4 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.3.3).

3.6 Logistics.

3.6.1 Technical Order (TO) requirements. When required by a delivery order, the contractor shall deliver technical manual(s) in accordance with TM-86-01. (B001, TM-86-01, Air Force Technical Manual Contract Requirements (TMCR))

3.6.2 Provisioning requirements. When required by a delivery order, 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 Data Item Descriptions (DIDs) may apply, as specified in the delivery order:

a. C001, DI-SESS-81758/T, Logistics Product Data. Specific Logistics Product Data to be submitted:

(1) Provisioning Parts List (PPL) Top Down Sequence

(2) Common and Bulk Items List (CBIL)

(3) Short Form Provisioning Parts List (SFPPL)

(4) Design Change Notices (DCNs)

(5) Statement of Prior Submission (SPS)

(6) Long Lead Items List (LLIL)

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

3.6.2.1 Provisioning Guidance Conference. When required by a delivery order, 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 1 day 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. (A003, DI-ADMN-81249, Conference Agenda; A004, DI-ADMN-81250, Conference Minutes)

3.7 Testing and evaluation.

3.7.1 First article (FA) CSE qualification/acceptance. When required by a delivery order, the contractor shall prepare one or more of each CSE items for the FA testing to be conducted. All FA tests shall be conducted at the contractor’s facility and/or subcontractor’s facility in accordance with the Government provided TDP and/or approved FA test plan and/or test procedure. Testing shall not occur, except whereas specified within an individual item’s TDP, without Government approved test plans and test procedures, as specified within individual delivery order.

3.7.1.1 FA test plan. When required by a delivery order, the contractor shall develop and submit for Government review and approval a detailed FA test plan. (A012, DI-NDTI-80566, Test Plan)

3.7.1.2 FA test procedure. When required by a delivery order, the contractor shall develop detailed FA test procedure and submit it for Government review and approval. The test procedure shall address all requirements identified in applicable TDPs, specifications, and this SOW. The test procedure shall include data record sheets, charts, graphs, identification of test instruments by manufacturer, model number, and serial number. (A013, DI-NDTI-80603, Test Procedure)

3.7.1.3 FA testing. After Government approval of the FA 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 and/or subcontractor’s facility, the contractor shall be responsible for all costs associated with the shipment. The contractor and/or subcontractor shall provide or arrange for all test equipment, special tools, and facilities required for the FA testing. The contractor shall notify the Government of the date, time, and location of the FA testing 30 days prior to the start of testing. The Government reserves the right to witness any of the FA testing conducted. Failure of the CSE item to meet the FA test requirements shall be cause for rejection.

Testing shall not be conducted without occurrence and Government approval of the TRR as specified in 3.4.2.

3.7.1.4 FA test report. When FA testing is required by a delivery order, the contractor shall submit a FA test report upon completion of the FA testing for Government review and approval. The test report shall document all testing performed, including results of any unsuccessful test attempts.

Failure reports shall be included with results of unsuccessful test attempts. CSE items shall not be submitted for inspection and acceptance without a Government approved FA test report, if FA testing is required by a delivery order. (A014, DI-NDTI-80809, Test/Inspection Report)

3.7.1.5 Production release. Production release is acknowledgment by the Government procuring activity that the contractor has satisfied all requirements to proceed with delivery of the CSE item(s) to be furnished under the contract. The contractor assumes all risks in initiating CSE item(s) production before the PCO has determined that the first article CSE (when required by a delivery order) has met all requirements, and the FA test report has been delivered and approved/accepted by the Government procuring activity. Delivery of production CSE item(s) to the Government shall not occur prior to Government acceptance/approval of T.O. (when required by a delivery order) and provisioning data (when required by a delivery order).

3.7.2 Restoration. When FA testing is required by a delivery order, the contractor shall be responsible for any repairs that may be necessary to restore the FA CSE item to a serviceable, “like new” condition while retaining configuration integrity after completion of the FA qualification/acceptance. CSE items shall not be submitted for inspection and acceptance prior to restoration to a serviceable, “like new” condition.

3.7.3 Disposition. When FA testing is required by a delivery order, the refurbished FA CSE item(s) shall be shipped to the location(s) specified in the contract.

3.7.4 Production acceptance testing. When required by a delivery order, the contractor shall test production CSE items to ensure proper operation prior to submission of the item(s) for Government inspection and acceptance. All production acceptance testing shall be conducted at the contractor’s facility and/or subcontractor’s facility in accordance with the Government provided TDP and/or approved production acceptance test procedure. Production acceptance testing shall not occur, except whereas specified within an individual items TDP, without Government approved production acceptance test procedures, as specified within individual delivery orders. The contractor and/or subcontractor shall provide or arrange for all test equipment, special tools, and facilities required for production acceptance testing. The Government reserves the right to witness any of the production acceptance testing conducted. Failure of the CSE item to meet the production acceptance test requirements shall be cause for rejection.

3.7.4.1 Production acceptance test procedure. When required by a delivery order, the contractor shall develop a production acceptance test procedure and submit it for Government review and approval. The test procedure shall address all requirements identified in applicable TDPs, specifications, and this SOW. The test procedure shall include data record sheets, charts, graphs, identification of test instruments by manufacturer, model number, and serial number. (A015, DI-NDTI-80603, Test Procedure)

3.7.4.2 Production acceptance test report. When production acceptance testing is required by a delivery order, the production acceptance test report for each production CSE item shall be included with the item’s documentation prior to submission for DCMA inspection and acceptance;

see 4.1 herein. (A016, DI-NDTI-80809, Test/Inspection Report)

3.8 Configuration management and control.

3.8.1 Product baseline. The CSE item product baseline is defined in the Government TDP (see 3.8.1.1.2) and/or as defined by part number (P/N) and Commercial and Government Entity (CAGE) code in the approved sources of supply list (see 3.8.1.2).

3.8.1.1. Engineering Data List (EDL). The Government will provide an EDL for the CSE end item NSNs where the Government has a complete TDP. The contractor shall have and maintain access to JEDMICS (see 3.2.2) to receive the technical and electronic data listed in the EDL to fulfill the contract requirements.

3.8.1.1.1 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 CSE item product baseline documented in the Government TDP unless such change is submitted in writing by ECP and approved by the Government procuring activity. Any request for change shall be accompanied by complete documentation supporting the need for the change. A Notice of Revision (NOR) shall be submitted with each ECP. (A008, DI-SESS-80639, Engineering Change Proposal (ECP); A009, DI-SESS-80642, Notice of Revision (NOR)).

3.8.1.1.2 TDP. The TDP (also known as the drawing package) forms a part of the contract and constitutes the CSE end item product drawings. When provided as part of a delivery order, the TDP is mandatory for use in design and building the CSE item and no deviation from the TDP is permissible without prior approval of the Government 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 CSE item. If during the manufacturing process, item discrepancies are noted with the Government provided TDP, the contractor shall notify the Government procuring activity of such discrepancies. Any data prepared by the contractor or obtained from a vendor to support fabrication and manufacture of the CSE item shall be made available, upon request, for inspection by the Government procuring activity.

Any changes to the Government TDP shall be processed via approved ECP(s).

3.8.1.1.3 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 TDP, any specified FA tests shall be conducted on the FA CSE item 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 FA tests does not preclude performance of any other tests deemed necessary by the Government procuring activity to verify form, fit, and functional interchangeability of the substitute components.

3.8.1.1.4 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 the CSE units or for a specific time. (A010, DI-SESS-80640, Request for Variance (RFV))

3.8.1.2 Approved sources of supply list. The contractor shall utilize the Government-supplied list of the currently approved/qualified sources of supply for each CSE NSN solicited to obtain any CSE item. No deviation from this list is permissible without prior approval of the Government procuring activity.

3.8.1.2.1 CSE item obsolescence/Diminishing Manufacturing Sources and Material Shortages (DMSMS). The contractor shall maintain market awareness of existing or impending obsolescence or diminishing manufacturing issues with the CSE items required by the contract. The contractor shall notify the Government procuring activity in writing if such issues arise during any time of contract performance. The contractor shall receive written approval from the Government procuring activity before proceeding with any activities to resolve obsolescence or diminishing manufacturing issues. Upon approval from the Government procuring activity, the contractor shall make necessary recommendations via Technical Support Request (TSR) form in accordance with

3.8.1.2.2. Any required ECPs, NORs, or RFV’s shall be submitted with the TSR as attachments.

3.8.1.2.2 Technical Support Request (TSR). The contractor shall utilize the TSR form (see Attachment 1) to recommend any changes to the CSE item product baseline as defined in 3.8.1 herein or propose a surplus CSE item (see 3.8.1.2.2) and submit it to the Government procuring activity for evaluation. The contractor shall receive approval from the Government procuring activity before proceeding with the recommended action proposed in the TSR. The contractor assumes all risks in initiating sourcing and delivery of the CSE item before contractor’s TSR form has been submitted and approved by the Government procuring activity.

3.8.1.2.2.1 Surplus CSE items. The Government procuring activity may consider approving new surplus CSE items; used surplus shall not be proposed. If the new surplus item is offered, the contractor shall provide all supporting documentation along with the TSR form to enable evaluation by the Government procuring activity. The supporting surplus documentation shall include, but not to be limited to, the condition and location of the surplus item, photos, the age of the item, remaining shelf life, available test data, surplus provider certifications, visual inspection results, etc.

3.9 Government furnished information (GFI). The Government will furnish the following information as identified in Appendix B of the solicitation and resultant contract: EDL (see 3.8.1.1) and approved sources of supply list (see 3.8.1.2).

3.10 CSE item unique identification. The CSE item and any of its components, for which the Government unit cost is more than $5,000 or the procuring agency determines is mission essential, is serially managed by the Government and shall have Unique Identification (UID) (also known as Item Unique Identification (IUID)) information marked in accordance with MIL-STD-130.

Unless otherwise specified, the UID shall be permanently affixed on or near the respective identification plate(s). Unless otherwise specified, the CSE item UID information shall include serial number, part number, and CAGE code, and shall be included as both a bar code and human-readable markings.

4. QUALITY ASSURANCE (QA)

4.1 Responsibility for inspection. For acquisition purposes, the inspection requirements shall be as specified in the contract or delivery order. The SRC contractor shall ensure that quality CSE items are provided to the Government. The SRC contractor shall be responsible for resolving any quality issues associated with the CSE items delivered under the contract. The SRC contractor shall inspect CSE items for compliance to the contract requirements (i.e., condition, quantity, configuration, documentation, traceability, etc.) prior to presentation to Defense Contract Management Agency (DCMA) for inspection and acceptance. All inspection and acceptance activities shall be performed at the SRC contractor’s facility. Inspection and acceptance shall not be performed at a subcontractor’s facility. The Government procuring activity reserves the right to perform any of the inspections it deems necessary to ensure supplies and services conform to the requirements specified herein.

4.2 Warranty. The warranty period for any CSE item delivered on the SRC shall be 12 months or 1,200 hours of operation, whichever occurs first, unless otherwise specified in the delivery order.

The warranty period shall start on the date of the Government acceptance, unless otherwise specified in the delivery order.

5. PACKAGING

For acquisition purposes, the packaging requirements shall be as specified in the contract or delivery order. When specified in the delivery order, the contractor shall be responsible for ensuring all packaging requirements are met, including those for Continental United States (CONUS), Outside Continental United States (OCONUS), and any unique FMS. When actual packaging of materiel is to be performed by DoD personnel, these personnel need to contact the responsible packaging activity to ascertain requisite packaging requirements. Packaging requirements are maintained by the Inventory Control Point's packaging activity within the Military Department or Defense Agency, or within the Military Department's System Command.

Packaging data retrieval is available from the managing Military Department's or Defense Agency's automated packaging files, CD-ROM products, or by contacting the responsible packaging activity.