ATS SOW - 11 Sep 24 .docx

11 September 2024

Statement of Work (SOW) for

Ammunition Transfer System (ATS)

Prepared by

AFLCMC/WNZ SUPPORT EQUIPMENT & VEHICLES

235 BYRON STREET

BLDG 300 WEST WING, BAY D, SUITE 27A

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. DEFINITIONS

3.1 Controlled Unclassified Information (CUI)

3.2 Loss of Government property

4. REQUIREMENTS

4.1 Program management

4.1.1 Data delivery and transfer

4.1.2 Program manager

4.1.3 Plant access

4.1.4 Monthly status report

4.2 Conferences and program reviews

4.2.1 Postaward conference

4.2.2 System Engineering Technical Reviews (SETRs)

4.2.2.1 Test readiness review (TRR)

4.2.2.2 SETR documentation

4.2.3 Program Management Reviews (PMRs)

4.2.4 Production Readiness Review (PRR)

4.2.5 Conference room

4.2.6 Meeting agendas

4.2.7 Meeting minutes

4.2.8 Multi-user ECP Automated Review System (MEARS)

4.3 Systems engineering

4.3.1 Environment, Safety, and Occupational Health (ESOH)

4.3.1.1 Hazardous materials

4.4 Logistics

4.4.1 Provisioning

4.4.1.1 Provisioning Guidance Conference (PGC)

4.5 Testing and evaluation

4.5.1 First article test

4.5.1.1 First article test procedures

4.5.1.2 First article testing

4.5.1.3 First article test daily situation reports (SITREPs)

4.5.1.4 Compatibility testing

4.5.1.5 First article test report

4.5.2 Operational Test and Evaluation (OT&E)

4.5.3 Restoration

4.5.4 Disposition

4.6 Configuration management

4.6.1 Engineering Change Proposals (ECPs)

4.6.1.1 TDP

4.6.1.2 Qualification of new components

4.6.2 Request for Variance (RFV)

4.6.3 Engineering data

4.6.3.1 Engineering Data Guidance Conference

4.6.3.2 In-Process Review (IPR) of the TDP

4.6.3.3 Relationship of the contractor with subcontractors and vendors

4.6.3.4 Engineering data updates and revisions

4.6.4 Configuration audit plan and Physical Configuration Audit (PCA)

4.6.4.1 Configuration audit plan

4.6.4.2 PCA

4.7 Controlled Unclassified Information (CUI)

4.8 Government furnished equipment (GFE)

4.8.1 Contractor responsibility

4.8.2 Reporting of Government property

4.8.3 Loss of Government property

4.8.3.1 Definition of loss of Government property

4.8.3.2 Reporting loss of Government property

4.8.3.3 Return or retention of Government property

1. SCOPE

This document defines the tasks associated with the procurement of the Ammunition Transfer System (ATS) as described by Technical Data Package (TDP) Part Number 201757932-10, Commercial and Government Entity (CAGE) 98752, and is to be used in conjunction with the TDP.

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

2.1.2 Other Government documents, drawings, and publications.

DATA ITEM DESCRIPTIONS (DIDs)

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

DRAWINGS

Part Number

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

NATIONAL INSTITUTE OF STANDARDS AND TECHNOLOGY (NIST)

SP 800-171 Rev. 2 Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations [including updates as of 01-28-2021]

(Copies of this document are available online at https://nvlpubs.nist.gov/.)

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)

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

SAE International

GEIA HB-0007B Logistics Product Data Handbook

(Application for copies should be addressed to SAE International, 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. DEFINITIONS

3.1 Controlled Unclassified Information (CUI). CUI is defined as unclassified information that laws, regulations, or Government-wide policies allow for, or require, safeguarding.

3.2 Loss of Government property. “Loss of Government property” means unintended loss of or damage to Government property including property that cannot be found after a reasonable search, loss due to inadequate storage, loss due to lack of security, theft, damage requiring repair to restore the item to usable condition, or damage that renders the property useless for its intended purpose or Beyond Economical Repair (BER). Loss of Government property does not include manufacturing defects, obsolescence, normal wear and tear, or purposeful destructive testing. Unless otherwise stated in the contract/order, loss of Government property does not include normal and reasonable inventory adjustments, that is, losses of low priority consumable material, such as common hardware, as agreed to by the contractor and the Government Property Administrator.

4. REQUIREMENTS

4.1 Program management.

4.1.1 Data delivery and transfer. To promote effective schedule management, email shall be utilized to the maximum extent possible for tasks identified in this SOW. 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.

4.1.2 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.

4.1.3 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.

4.1.4 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, Contractor's Progress and Status Report)

4.2 Conferences and program reviews. Throughout the period of performance (POP) of the contract, conferences, meetings, and technical or programmatic reviews may be supplemented with a virtual environment as directed by the Procuring Contracting Officer (PCO) if travel restrictions, safety measures, or other program specifics prevent or limit the number of in-person attendees. Virtual meetings can utilize, but shall not be limited to, AF365 Teams. The contractor shall adhere to any Federal, State, or local health and well-being regulations and guidelines for contractor-hosted in-person gatherings with Government personnel.

4.2.1 Postaward conference. If the Government determines that a postaward conference is necessary, the Government will convene the conference with the contractor at Robins AFB GA within sixty (60) calendar days after contract award. The PCO will coordinate the actual date and time of the conference with the contractor.

4.2.2 System Engineering Technical Reviews (SETRs).

4.2.2.1 Integrated Test Team (ITT). The contractor shall participate in recurring Government ITT meetings (cadence to be determined) to gain Air Force subject matter expertise in creation of First Article and Production Acceptance Test Plans and Procedures (from this SOW, Appendix A, and CDRL requirements). ITT participants may include Air Force IPT, test wing, command and base safety, and operational units.

4.2.2.2 Test readiness review (TRR). The contractor shall conduct a TRR 14 calendar days prior to the start of the 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 the contractor’s facility. The PCO will coordinate the actual date and time of the TRR with the contractor.

4.2.2.3 SETR documentation. The contractor shall prepare all necessary detailed status reports for the SETR meetings, Meeting Agendas, and Meeting Minutes. The contractor shall prepare formal documentation of the TRR. (DI-ADMN-81249, Meeting Agenda; DI-ADMN-81250, Meeting Minutes; DI-MISC-80508, Technical Report/Study Services)

4.2.3 Program Management Reviews (PMRs). 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 at a mutually agreeable location or via teleconferences. (DI-ADMN-81249, Meeting Agenda; DI-ADMN-81250, Meeting Minutes)

4.2.4 Production Readiness Review (PRR). A PRR shall be conducted to ensure the contractor is ready to begin production. The PRR shall include an evaluation of the contractor's manufacturing readiness processes, quality management system, production planning (that is, facilities, tooling and test equipment capacity, personnel development and certification, process documentation, inventory management, supplier management, etc.). Unless otherwise specified or directed by the PCO, the PRR shall be conducted at the contractor's facility within thirty (30) days following procuring activity approval of the test report.

4.2.5 Conference room. The contractor shall provide a conference room suitable for meetings of up to 12 Government representatives, plus contractor personnel, in support of scheduled meetings at the contractor's facility.

4.2.6 Meeting agendas. The contractor shall publish an agenda for all meetings and conferences specified in 4.2.2 - 4.2.4. 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 seven calendar days prior to any meeting. (DI-ADMN-81249, Meeting Agenda)

4.2.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. (DI-ADMN-81250, Meeting Minutes)

4.2.8 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. 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. The contractor shall obtain and possess PKI certification from an accepted Government source to access the DoD SAFE.

4.3 Systems engineering.

4.3.1 Environment, Safety, and Occupational Health (ESOH).

4.3.1.1 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 to be delivered under this contract, including locations, quantities, and special handling and disposal procedures. This information shall be documented in the monthly status report (see 4.1.4) and reviewed at the PMRs and TRR; it shall be in accordance with FED-STD-313.

4.4 Logistics.

4.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-81758, Logistics Product Data. Specific Logistics Product Data to be submitted:

i. Provisioning Parts List (PPL) Top-down sequence

ii. Design Change Notices (DCNs)

iii. Statement of Prior Submission (SPS)

iv. Long Lead Items List (LLIL)

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

(DI-SESS-81758, Logistics Product Data; DI-SESS-81874, Engineering Data For Provisioning (EDFP))

4.4.1.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 in conjunction with the postaward conference. 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-81249, Meeting Agenda; DI-ADMN-81250, Meeting Minutes)

4.5 Testing and evaluation.

4.5.1 Test support. The contractor shall ensure common repair parts are available during all phases of testing specified herein so that minor breakdowns do not delay the test beyond repair time required to return the equipment to serviceable condition. If during troubleshooting or diagnosing a compatibility test or fault is found that a replacement part(s) is required for repair, the contractor shall ship part(s) to the test location via “same day” and/or “overnight” service at the direction of the procuring activity. Additionally, copies of the latest draft TOs shall be available for Government use during logistics testing and operational testing.

4.5.2 First article testing.

4.5.2.1 First article test plan. The contractor shall develop a first article test plan within ninety (90) calendar days after contract award. A basic first article test plan outline is provided as Appendix A with the minimum testing required to demonstrate functionality of the system. The contractor shall build upon the test plan requirements defined in Appendix A to include all inspections, analyses, demonstrations, and test procedures that would be beneficial in demonstrating ATS’s physical, performance, reliability, serviceability, and maintainability requirements. The first article test plan may reference TO 35D30-4-21-1 Operation and Maintenance Instructions with Illustrated Parts Breakdown, Ammunition Transfer System (ATS) GFU-27/K PN 20118066-10 and/or compatible commercial operation and maintenance instructions to validate the first article’s Interchange Loading, Ammunition Support, Tray and Top Guide, and Download Assemblies and the Counter, Top Guide, Drive, Pawl Stop, Element, Base, Frame, and Guide Assemblies. (DI-NDTI-80566, Test Plan)

4.5.2.2 First article test procedures. The contractor shall develop detailed test procedures, which shall address all requirements identified in the TDP and this SOW, except for the compatibility testing (see 4.5.1.4). The test procedures shall include data record sheets, charts, graphs, identification of test instruments by manufacturer, model number, and serial number. The test procedures shall address modeling and simulation (M&S); if M&S is not applicable, the test procedures shall be so noted. (DI-NDTI-80603, Test Procedure)

4.5.2.3 First article testing. After Government approval of the first article test procedures, the contractor shall schedule the testing to be conducted within thirty (30) days after pre-production units are finished. 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 thirty (30) calendar days prior to the start of testing. The test will be witnessed by one or more Government representatives. All first article testing, including the compatibility testing (see 4.5.2.4), shall be completed within thirty (30) calendar days.

4.5.2.4 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.

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

4.5.2.5 First article test report. The contractor shall submit a first article test report upon completion of the first article test. The test report shall document all testing performed, including results of any unsuccessful test attempts. (DI-NDTI-80809, Test/Inspection Report)

4.5.3 Compatibility testing. Within thirty (30) calendar days after approval of the first article test plans and procedures, the first article ATS units shall be shipped to an approved Operational Testing & Evaluation (OT&E) Test Wing for compatibility testing. The contractor shall be responsible for all costs associated with shipping. The Operational Test Organization’s (OTO) Test Execution Authority (TEA) is responsible for identifying test scope, test safety, system hazards, and mitigating/approving all risks prior to test execution. The OTO will develop detailed compatibility testing procedures based on Air Force TOs, Aerospace Ground Equipment maintenance, and operational experience. See Table I below for TO references.

Table I. TO references for compatibility testing.

Ammunition Transfer System (ATS) GFU-27/K, PN 20118066-10

35D30-4-21-1, Operation and Maintenance Instructions with Illustrated Parts Breakdown

20-MM Universal Ammunition Loading System (UALS)

PN 212F156

TO 35D30-4-15-1, Operation and Maintenance Instructions

Operation and Maintenance Instructions With Illustrated Parts Breakdown

All compatibility testing will be complete within thirty (30) calendar days of initiation. Air Force personnel will perform all compatibility testing; contractor personnel shall available during the test event(s) to witness the testing, perform any ATS repairs that may be required, and advise Air Force personnel during the test period. If faults such as timing or jamming issues arise during compatibility testing, the contractor shall investigate the root cause and repair the first article equipment such that it does successfully interoperate with compatible ammo loading systems (ALS) including the UALS and LALS. Air Force test reports will document all testing performed, including results of any unsuccessful test attempts. Any failure reports generated, such as may occur during the compatibility testing, shall be included with results of unsuccessful test attempts.

4.5.4 Operational Test and Evaluation (OT&E). After completion of compatibility testing and approval by the Government, further necessary operational testing required by the Air Force shall be conducted (to include overall system compatibility and operational testing for ATS, ALS, and aircraft guns). Air Force operators and maintainers will conduct all OT&E. The contractor shall provide a spare parts kit with each ATS shipped for the OT&E containing all items required to conduct scheduled maintenance during the test as well as common repair parts predicted to be needed during the OT&E. Contractor's support shall be available (within 48 hours of notification exclusive of weekends and official Federal Government holidays) all times during the OT&E. All OT&E shall be completed within allocated 120 calendar days.

4.5.5 Restoration. After completion of OT&E and acceptance, the first article ATSs shall be shipped, within thirty (30) calendar days, to the contractor's facility for restoration. The contractor shall be responsible for any repairs that may be necessary to restore the ATSs to a serviceable, "like new" condition while retaining configuration integrity. The contractor shall be responsible for all costs associated with shipping of the ATSs to the contractor's facility for restoration.

4.5.6 Disposition. One approved unit shall be retained at the contractor's facility, to serve as a manufacturing standard, until the last shipment. The remaining units shall be shipped to the location(s) specified in the contract.

4.5.7 Production acceptance test. When subsequent tasks are issued beyond the base contract, the contractor shall conduct a production acceptance test to validate production unit functionality and quality. One from every contract task quantity produced shall be subjected to the production acceptance test. A basic test procedure is provided as Appendix A with the minimum testing required to demonstrate functionality and quality of the production units. Test records are to be completed, retained, and provided as requested to the procuring activity. (DI-NDTI-80603, Test Procedure; DI-NDTI-80809, Test/Inspection Report).

4.6 Configuration management.

4.6.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 TDP unless such change is submitted in writing by ECP and approved by the procuring activity.

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

4.6.1.1 TDP. The TDP (also known as the drawing package) forms a part of this SOW and constitutes the end item product drawings. The TDP is mandatory for use in design and building the ATS 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 ATS. If during the manufacturing process of first article ATSs 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 first article ATSs shall be made available, upon request, for inspection by the procuring activity. Any changes to the TDP shall be processed via approved ECP(s).

4.6.1.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 ATS 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 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.

4.6.2 Request for Variance (RFV). The contractor shall prepare an RFV whenever a departure from the contractually specified base line is proposed for a specific number of units or for a specific time. (DI-SESS-80640, Request for Variance (RFV))

4.6.3 Engineering data. The contractor shall develop, produce, maintain, and deliver a 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 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 Drawings Models 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-130, 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-82351, Acquisition and Sustainment Data Package (ASDP) Engineering Design Data and Associated Lists (EDDAL))

4.6.3.1 Engineering Data Guidance Conference. The contractor shall support and co-chair a Guidance Conference with AFLCMC/LZPEM for engineering data within sixty (60) calendar 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 Contract Data Requirements List (CDRL) requirements, applicable DIDs, specifications, and standards.

b. TDP review requirements and schedules.

c. TDP delivery requirements and schedules.

d. Contractor's modeling/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 for both Model-based and non-Model-based.

Note that the Guidance Conference may be held in conjunction with other meetings or conferences. (DI-ADMN-81249, Meeting Agenda; DI-ADMN-81250, Meeting Minutes)

4.6.3.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. The IPR may be scheduled when data has reached the 50 percent 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 201646959 (CAGE 98752) for Model-based TDPs and data set identifier 9579776 (CAGE 98752) for non-Model-based TDPs. The contractor shall notify AFLCMC/LZPEM a minimum of thirty (30) calendar 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-81249, Meeting Agenda; DI-ADMN-81250, Meeting Minutes)

4.6.3.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.

4.6.3.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 ninety (90) calendar 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.

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

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

4.6.4.2 PCA. During the manufacture and assembly of the first unit, the contractor shall host a PCA at the contractor's facility in accordance with the approved IMS and Configuration Audit Plan to verify that the configuration of the ATS conforms to the TDP. The PCA shall be conducted in three increments, the first when the unit is approximately 50 percent assembled, the second when it is approximately 75 percent assembled, and the final when it is approximately 90 percent assembled. At a minimum, the PCA shall include a detailed audit of engineering drawings, specifications, technical data, quality control records, and tests. The PCA shall be accomplished in a non-destructive manner and will not require disassembly of the unit or any of its assemblies, subassemblies, components, or parts. 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. Complete set of drawings, procedures, specifications, and inspection/acceptance procedures.

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

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

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 that 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-81022, Configuration Audit Summary Report; DI-ADMIN-81249, Meeting Agenda; DI-ADMIN-81250, Meeting Minutes)

4.7 Controlled Unclassified Information (CUI). CUI is defined as unclassified information that laws, regulations, or Government-wide policies allow for, or require, safeguarding. Knowledge and/or generation of CUI is required for performance of the contract/order. This SOW governs work that contains the development and transfer of CUI between contractors and the United States (U.S.) Government. All CUI shall be controlled until authorized for public release. The contractor shall ensure personnel, information, system, property, and facility security requirements are met. The contractor shall comply with Government security regulations including, but not limited to, Department of Defense (DoD) 5200.2-R, Personnel Security Program; DoD 5220.22-M; DoD Directive (DoDD) 5205.02E, DoD Operations Security (OPSEC) Program; and DoD Manual 5205.02-M, DoD Operations Security (OPSEC) Program Manual to protect Government interests. Determine if Cybersecurity Maturity Model Certification (CMMC) is required and what level. The contractor shall ensure the security of any Information Technology (IT) environment at the contractor's facility that hosts CUI. The contractor shall maintain a cyber-secure environment for all components of a non-federal IT system that processes, stores, and/or transmits CUI as defined in NIST SP 800-171 to preclude potential security incidents or violations including potential unauthorized disclosure or compromise of CUI. Contractors shall ensure their employees have been trained in the proper marking of CUI; authorized and approved training material will be provided to the contractor prior to contract award. The contractor shall ensure that all personnel handling CUI associated with this contract: have been properly trained, have been approved to handle CUI, have a valid need to handle CUI, and shall safeguard any CUI in their possession at all times. The contractor shall maintain a cyber-secure IT environment that reduces and manages risk by meeting the intent of Cybersecurity Maturity Model Certification (CMMC) Level I. The contractor shall also take necessary precautions and actions to ensure that the IT environment for any software development is secure and free of malware and malicious code. The contractor shall report any cyber incidents to the Government in accordance with DFARS Clause 252.204-7012 (Safeguarding Covered Defense Information and Cyber Incident Reporting) as applicable.

4.8 Government furnished equipment (GFE).

The Government will provide GFE as identified in Appendix A. All GFE will be provided to the contractor in proper working order, with all maintenance actions, inspections, lubrication, and maintenance history available for review and acceptance prior to shipment. Upon notice from the contractor, GFE will be provided no later than thirty (30) days after pre-production units are finished. The Government will deliver the GFE to the contractor's facility. The contractor shall have use of the GFE for the duration of the testing and return it to the Government at the conclusion of the testing. The Government will be responsible for all costs associated with shipping of the GFE to the contractor, and the contractor shall be responsible for all costs associated with shipping of the GFE to the Government.

If available, the Government will provide GFE ATS prototype unit(s). The contractor shall conduct an initial physical configuration audit using a Configuration Audit Plan and Physical Configuration Audit (PCA), 4.6.4, and associated CDRLs comparing the physical components of the prototype(s) to the TDP and denoting any differences to the procuring activity via ECPs.

If GFE ATS unit(s) are unavailable, the contractor shall be limited to auditing and evaluating the Government’s ATS TDP. Therefore, the contractor shall provide an initial examination of the TDP suitability against Government drawing standards for producibility, provisioning, and sustainment purposes and denote any discrepancies to the procuring activity via ECPs. The TDP shall conform to Engineering Data, 4.6.3 and associated CDRLs. (DI-SESS-81646, Configuration Audit Plan, DI-SESS-81022, Configuration Audit Summary Report).

4.8.1 Contractor responsibility. The contractor shall be responsible for Government property in accordance with the Federal Acquisition Regulation (FAR) and as specified in the contract.

4.8.2 Reporting of Government property. The contractor shall have a system of internal controls to manage (control, use, preserve, protect, repair, and maintain) Government property in its possession in accordance with FAR 52.245-1, and its property management system shall be adequate to satisfy the requirements of this clause. The contractor shall record receipt and return of all Government Furnished Property (GFP), as well as the reporting of shipment, consumption, disposal, or transfer to another contract, in the GFP Module in Procurement Integrated Enterprise Environment (PIEE), https://piee.eb.mil, as stipulated by DFARS 252.245-7005. This reporting requirement does not change any liability provisions or other reporting requirements that may exist under the contract. GFP training and guidance is located at the DoD Procurement Toolbox at https://dodprocurementtoolbox.com/.

4.8.3 Loss of Government property.

4.8.3.1 Definition of “loss of Government property”. “Loss of Government property” means unintended loss of or damage to Government property including property that cannot be found after a reasonable search, loss due to inadequate storage, loss due to lack of security, theft, damage requiring repair to restore the item to usable condition, or damage that renders the property useless for its intended purpose or Beyond Economical Repair (BER). Loss of Government property does not include manufacturing defects, obsolescence, normal wear and tear, or purposeful destructive testing. Unless otherwise stated in the contract/order, loss of Government property does not include normal and reasonable inventory adjustments, that is, losses of low priority consumable material, such as common hardware, as agreed to by the contractor and the Government Property Administrator.

4.8.3.2 Reporting loss of Government property. The contractor shall report loss of Government property in the GFP Module located in PIEE, https://piee.eb.mil/piee-landing/.

4.8.3.3 Return or retention of Government property. All property provided by the Government remains the property of the Government and shall be returned to the Government as directed, but no later than completion of the contract/order, unless the PCO directs the contractor to retain the property for continued use under a successor contract. All Government property shall be returned to the Government in the condition provided unless approved in advance by the PCO. All material generated under the contract/order becomes the property of the Government and shall be returned to the Government as directed, but no later than completion of the contract/order, unless the PCO directs the contractor to retain the material for continued use under a successor contract.

APPENDIX A

FIRST ARTICLE AND PRODUCTION ACCEPTANCE TESTING

A.1. SCOPE

A.1.1 Scope. This appendix defines the minimum first article testing provisions to ensure the ATS is in accordance with the TDP, exhibits good workmanship, and meets all performance requirements.

A.2 TESTING PROVISIONS

A.2.1 Examination of product. Each first article ATS shall be examined to verify compliance with the requirements herein prior to accomplishing any other demonstrations or tests listed herein. A contractor-generated, Government-approved checklist (part of the test procedure) shall be used to identify each requirement not verified by an analysis, certification, demonstration, or test, and shall be used to document the examination results. Particular attention shall be given to materials, workmanship, dimensions, surface finishes, protective coatings and sealants and their application, welding, fastening, and markings. Proper operation of each function shall be verified.

a. TDP. Ensure the ATS is in accordance with the TDP.

b. Interfaces. Ensure the ATS complies with the interface requirements for the UALS and LALS; see Table I.

c. Gears and rotors. Ensure smooth meshing of gears and rotors in ATS conveyor assembly.

d. Conveyor elements. Utilize the GFE checking fixture to check and ensure a smooth sliding motion of the conveyor elements in the ATS.

e. Drive assemblies. Inspect ATS drive assemblies and ensure no broken, chipped, or worn teeth.

f. Timing marks. Ensure all timing marks are visible and align properly.

g. Panel fitment. Check panels for fit. Ensure no gaps or interference exists.

h. Latches. Ensure latches secure properly.

i. Caster wheels. Ensure freedom of movement and proper rolling and braking operation.

j. Trays, extractor guides, tensioners, plungers, and download assemblies. Ensure proper alignment, fit up, and operation.

k. Hand crank and rounds counter assemblies. Ensure proper operation.

l. Tiedown rings. Ensure proper location and operation.

m. Grounding reel. Ensure proper operation, ground resistance, and continuity.

A.2.2 First article testing general requirements. The contractor shall perform testing of the ATS and the GFE ALS using the contractor generated, Air Force approved first article test plan and test procedures. Follow Table I Applicable TOs and any commercial operations and setup manuals for ATS and ALS units, particularly WP 004 00 thru 007 00 and equivalent Use, Shipment, Operating, and Maintenance Sections.

A.2.3 Test provisions.

A.2.3.1 Test conditions.

a. Pneumatic operating pressure of the ALS and ATS shall be between 35-40 psi: no deviations.

b. Ensure all the ATS and UALS or LALS combinations are properly timed prior to operation.

A.2.3.2 Test performance. A minimum of 2,900 20MM dummy rounds shall be transferred from ammunition cans through the ATS and into the GFE UALS or LALS.

a. Hand crank two complete revolutions with large speed handle prior to applying pneumatic air to ensure proper slack and no binding.

b. In the Bypass mode, 2,900 dummy rounds shall pass through the Interface Unit and ATS and no more than two (2) jams shall occur.

c. Return the ATS Interface Unit to Load mode, where 2,900 rounds will exit out of the ATS into UALS or LALS. Note: When 2,900 rounds are cycled through the system with less than two jammed conditions and no equipment failure, the result will satisfy successful in-plant testing procedure.

d. More than two (2) jammed conditions shall result in all testing procedures be halted. Note:

· For FAT, the contractor shall refer to the SOW and procuring activity for instructions to proceed after jammed conditions have been corrected.

· For production acceptance testing, the contractor shall provide and document corrective actions for the procuring activity per Test Records of Production Acceptance Testing 4.5.7.

e. Procedures, results, any issues, and/or corrective actions shall be recorded.

A.3 GOVERNMENT FURNISHED EQUIPMENT (GFE)||

A.3.1 GFE. The following GFE shall be provided upon request.

Table A.I. GFE

Cage: 98752

8RSQ53G1

TO 35DA15-9-1

A.4 TEST EQUIPMENT

A.4.1 Required test equipment. Table A.II lists the equipment and materials required to perform the test herein.

Table A.II Required test equipment, Nomenclature

20 Millimeter (MM), Dummy, M51A2/M51A3 Testing

Cartridge, 20MM, Dummy, PGU-39/B

19200 Shipping and Storage Container, M548

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