SOW_GPM_2021-05-20.docx

20 MAY 2021

Statement of Work (SOW) for

72 kW / 90 kVA GROUND POWER UNIT 144 kW / 180 kVA GROUND POWER UNIT 144 kW UNIVERSAL LOAD BANK

Prepared by

SUPPORT EQUIPMENT AND VEHICLES PROGRAM OFFICE

235 BYRON ST STE 19A

ROBINS AFB GA 31098-1813

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

THIS PAGE HAS BEEN INTENTIONALLY LEFT BLANK

TABLE OF CONTENTS

1. SCOPE 6

2. APPLICABLE DOCUMENTS 6

3. REQUIREMENTS 9

1. SCOPE

This Statement of Work (SOW) defines the tasks associated with the integration, testing, and production of a 144 kilo-watt (kW)/180 kilovolt-ampere (kVA) Ground Power Unit (GPU), a 72 kW/90 kVA GPU, and a 144 kW Universal Load Bank (ULB) as described by Purchase Description (PD) numbers PD21WRWNZEA007, PD21WRWNZEA008, and PD21WRWNZEA009, respectively.

The Government intends to issue one solicitation resulting in two contracts, each having a two year basic period of performance (POP). The two contracts will be issued to procure the items above: the Group A contract will include a single award consolidating for six each first article 72 kW GPUs, six each 144 kW GPUs, and eight each first article 144 kW ULBs. The Group B contract will be a small business (SB) set-aside for six each 72 kW first article GPUs. Following testing and acceptance of the first articles by the Government for both contracts, the Government intends to exercise multiple 12-month options periods for both the Group A and Group B efforts.

Throughout this SOW, explicit references to terms such as “Group A” and/or “Group A contractor” shall be assumed to include the 72 kW/90 kVA GPU, the 144 kW/180 kVA GPU, and the 144 kW ULB. Similarly, explicit references to terms such as “Group B” and/or “Group B contractor” shall be assumed to include only the 72 kW/90 kVA GPU. If not otherwise specified, the term “contractor” shall be assumed to apply to both the Group A AND the Group B awardees. The terminology denoted above applies equally to tasks denoted within the SOW and any accompanying contract deliverable requirements list (CDRL) item.

NOTE: Unless otherwise specified herein, the term “days” denotes calendar days.

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

DEPARTMENT OF DEFENSE STANDARDS

DEPARTMENT OF DEFENSE HANDBOOKS

2.1.2 Other Government documents, drawings, and publications.

NATIONAL INSTITUTE OF STANDARDS AND TECHNOLOGY (NIST)

DEPARTMENT OF DEFENSE MANUALS

DEPARTMENT OF DEFENSE DIRECTIVES

DEPARTMENT OF DEFENSE INSTRUCTIONS (DODI)

AIR FORCE INSTRUCTIONS (AFI)

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

DATA ITEM DESCRIPTIONS (DIDs)

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

DEPARTMENT OF DEFENSE GUIDES

(A copy of the Risk Management Guide can be obtained at the following internet address: https://www.sebokwiki.org/wiki/Risk_Management_Guide_for_DOD_Acquisition.)

PURCHASE DESCRIPTIONS

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)

(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 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 must 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.

The contractor shall ensure the security of Automated Information System(s) (AIS) at the contractor’s facility to preclude potential security incidents or violations including potential unauthorized disclosure or compromise of CUI. 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. 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 safeguard any CUI in their possession at all times.

The contractor shall immediately notify the Procurement Contracting officer (PCO) of any potential or actual security incident or violation including potential or actual unauthorized disclosure or compromise of CUI.

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

Contractor/subcontractor personnel shall obtain the CAC from the local Real Time Automated Personnel Identification Documentation System (RAPIDS) issuing facility [usually the Military Personnel Flight (MPF)]. The contractor may plan to obtain CACs while at Robins Air Force Base (AFB) during their visit for the postaward conference.

The contractor shall notify the PCO of any change to the list of contractor/subcontractor personnel who require a CAC and provide an updated list within 5 business days. The contractor shall immediately (within same day) report a lost or stolen CAC to the PCO. The contractor shall return any issued CAC to the PCO within 5 business days once contractor personnel no longer require computer network/system access. The contractor shall return any and all CACs to the PCO within 5 business days after completion/termination of the contract. The Group A contractor shall be issued a minimum of two (Primary and Alternate) and maximum of four CACs; the Group B contractor shall be issued two CACs (Primary and Alternate).

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

3.1.3 Data delivery and transfer. To promote effective schedule management, electronic data exchanges shall be utilized to the maximum extent possible for tasks identified in this SOW. Contractor personnel having CACs will be granted access to Air Force Network Teams (AFNet Teams), a collaborative workspace product of Microsoft, to send/receive/upload/download/view data for tasks identified in the SOW. Air Force OneDrive, accessible through AFNet Teams to CAC holders, shall be the Cloud hosted data storage repository. Department of Defense (DoD) Secure Access File Exchange (SAFE) shall be the secondary (backup) electronic data exchange, located at https://safe.apps.mil, and utilized when temporary circumstances do not permit use of AFNet Teams.

3.2 Program management.

3.2.1 Program manager. The contractor shall identify to the Government and maintain a single Program Manager (PM) point of contact 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.2.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 SOW.

3.2.3 Access to Government facility or military installation. The Government will facilitate access to Government facilities and military installations as required. The contractor shall ensure contractor personnel who require access to a Government facility or military installation comply with the security requirements of the facility or installation.

3.2.4 Monthly status report (MSR). The contractor shall track program progress and document such via MSRs. The contractor shall deliver an MSR that covers the engineering and technical development of the system and subsystems for each end item, 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 expected outcomes. The current risk management analysis, mitigation plan, and tracking (see 3.4.4) shall be provided as attachments to the MSR. The contractor shall deliver the initial report on the 5th day of the first month after receipt of order (ARO).

The contractor shall develop and maintain an Integrated Master Schedule (IMS) using the original baseline schedule as an unchanging reference. The contractor shall show all activity for all end items on the IMS. The IMS shall be attached to the MSR and delivered in both Microsoft Project and PDF formats. (DI-MGMT81928, Contractor's Progress and Status Report, A001)

3.3 Conferences and program reviews. Throughout the POP, conferences, meetings, and technical or programmatic reviews may be supplemented with a virtual environment as directed by the 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, GPM AFNet Teams or Zoom. 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.

3.3.1 Travel. Travel requests for contractor/subcontractor personnel shall be submitted for approval to the PCO prior to costs being incurred and a minimum of 1 working day in advance of departure, with the exception of 2 working days in advance during Phase three operational test and evaluation (OT&E), exclusive of weekends and official Government holidays. Receipts must be presented with the invoice for reimbursement of actual travel costs.

3.3.2 Postaward conference. The Government will convene separate postaward conferences with each contractor at Robins AFB within 30 days ARO. The PCO will coordinate the actual date, time, and location of the conference with the contractor.

3.3.3 Technical reviews.

3.3.3.1 Design reviews.

3.3.3.2 Design reviews location and schedule. The contractor shall host a preliminary design review (PDR) no later than 90 days ARO. The contractor shall also host a critical design review (CDR) no later than 210 days ARO. The Group A contractor shall schedule and conduct all design review events such that all applicable information and activity is both consolidated and combined, while still clearly and effectively delineated between each end item. Refer to 3.3.3.3, herein, for design review content. All design reviews shall be held at the contractor’s location/facilities.

3.3.3.3 Design review content. The PDR and CDR shall include formal technical reviews of the proposed design; program risks shall be reviewed on a technical and schedule basis. Each review shall include, but is not limited to: preliminary calculations; any necessary design studies or analyses including the design analysis as required in 3.6.1; preliminary drawings, including equipment layout drawings (packaging); proprietary or restricted design processes, components, and information; electrical and mechanical design; environmental control; thermal design aspects; software design; cybersecurity; training materials; lists of materials, parts, and processes; human engineering elements; corrosion control; maintainability; production capability and manufacturing; and quality considerations. Final drawings, final calculations, and any mockups or any assemblies shall be made available for the Government review as well. The contractor shall provide the equipment layout drawings as Computer-aided Design/Computer Aided Manufacturing (CAD/CAM) native files at the overall assembly and major subassembly level, as well as interactive 3-dimensional (3D) .pdf files of the overall assembly and subassemblies. Further, the contractor shall provide exploded views of all assemblies and subassemblies comprising the end items to show how components fit together when assembled. All applicable comments from the PDR shall be incorporated into the CDR design documentation.

3.3.3.4 Test readiness review (TRR). The contractor shall host a formal test readiness review (TRR) 30 days prior to the start of Phase one developmental test and evaluation (DT&E) contractor inspection and 20 days prior to the start of Phase two DT&E equipment/aircraft compatibility inspection. The Government will conduct informal TRRs for Phase three OT&E, and the contractor shall provide support for these TRRs as required. First article testing includes the following phases:

a. Phase one DT&E: contractor inspection

b. Phase two A DT&E: air vehicle systems integration laboratories (SILs) (applies only to 270 volts direct current (VDC) systems)

c. Phase two B DT&E: equipment/aircraft compatibility inspection

d. Phase three: OT&E

The contractor shall only proceed to Phase two DT&E testing (and applicable Phase three OT&E testing), to include shipment of first articles, after receiving written approval from the PCO. All TRRs 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.

3.3.3.5 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 TRRs. (DIMISC80508, Technical Report/Study Services, TRR; DI-ADMN-81249, B001, Conference Agenda, A002; DI-ADMN-81250, Conference Minutes, A003)

3.3.4 Program management review support. The contractor shall host all reviews, audits, and meetings as requested by the PCO or the contractor. Similarly, the Government will make every effort to participate in and support reviews, audits, and meetings requested by the contractor.

During the basic contract period, a minimum of eight formal Program Management Reviews (PMRs) shall be conducted quarterly, at a minimum, at a mutually agreeable location or via teleconference. The Government prefers that the Group A contractor combine all end items in PMRs. PMRs shall be scheduled as directed by the PCO during the option ordering periods.

3.3.4.1 Government/contractor meetings. Informal Government and contractor virtual meetings or teleconferences shall be held weekly during the basic period; meeting agenda and minutes are not required.

3.3.5 Conference room. The contractor shall provide a conference room suitable for meetings of up to 15 Government representatives (25 personnel for training), plus contractor personnel, in support of scheduled meetings at the contractor’s facility (see 3.3 for teleconference requirements).

3.3.6 Meeting agendas. The contractor shall publish an agenda for all meetings, technical reviews and conferences specified herein, with the exception of the postaward conference in 3.3.2. The contractor shall request from the Government any items or issues to be discussed or presented and shall include such items in the agenda. Agendas shall be delivered not less than 5 working days prior to any meeting. (DI-ADMN-81249, Conference Agenda, A002)

3.3.7 Meeting minutes. The contractor shall provide a written record of the discussions, decisions, and action items identified at each conference, technical review or meeting, with the exception of the postaward conference. Minutes shall include the relevant presentation material as applicable. The contractor shall deliver meeting minutes no later than 5 days after the meeting. (DI-ADMN-81250, Conference Minutes, A003)

3.4 Systems engineering.

3.4.1 Environment, safety, and occupational health (ESOH).

3.4.1.1 System safety. The contractor shall establish, conduct, document, and maintain a system safety program for each end item in accordance with MILSTD882. The contractor shall document their approach for analyzing, eliminating, or minimizing ESOH hazards during all phases of the program for each end item. The contractor shall initiate changes in the system design based on safety analysis results, such that the associated risk is reduced to a level acceptable to the Government. A System Safety Program Plan (SSPP) for each end item shall be delivered 30 days prior to the PDR.

An initial system safety hazard analysis report (SSHAR) for each end item shall be delivered 30 days prior to the PDR. (DISAFT81626, SSPP, C001; DISAFT80101, System Safety Hazard Analysis Report (SSHAR), C002)

3.4.1.2 Hazardous materials. The contractor shall manage hazardous materials, including those embedded in the system or used during operation or maintenance, as an element of the Systems Engineering process. This information shall be documented in the design analysis (see 3.6.1) and reviewed at the technical reviews; it shall be documented in accordance with FED-STD-313.

3.4.2 Corrosion control. The contractor shall establish, conduct, document, and maintain a corrosion prevention control program for each end item, which shall be documented in a corrosion prevention and control plan deliverable in accordance with 4.1 of MILSTD1568. The Group A contractor shall present the data for each end item in its own volume within a consolidated corrosion prevention and control plan. The Government reserves the right to approve or disapprove any or all volumes of the Group A contractor’s deliverable. The initial corrosion prevention and control plan shall be delivered 30 days prior to the PDR. (DIMFFP-81403, Corrosion Prevention and Control Plan, C003)

3.4.3 Reliability and maintainability. Note: For the entirety of 3.4.3, including all sub-paragraphs herein, the PD paragraph appendix references are the same. Individual PD numbers and paragraph repetitions have been omitted for clarity.

3.4.3.1 Reliability.

3.4.3.1.1 Basic reliability model. The contractor shall develop and maintain a basic reliability model for each end item in accordance with A.4.1 of the PD(s). The basic reliability model for each end item shall be documented in the consolidated design analysis (see 3.6.1) and reviewed at the technical reviews.

3.4.3.1.2 Basic reliability prediction. The contractor shall prepare and maintain a basic reliability prediction for each end item in accordance with A.4.2 of the PD(s); it shall be based upon the associated basic reliability model (see 3.4.3.1.1). The basic reliability prediction for each end item shall be documented in the consolidated design analysis (see 3.6.1) and reviewed at the technical reviews.

3.4.3.1.3 Failure modes, effects, and criticality analysis (FMECA). The contractor shall prepare and maintain a FMECA for each end item in accordance with A.4.3 of the PD(s); it shall be based upon the associated basic reliability model (see 3.4.3.1.1). The FMECA shall be documented for each end item in the consolidated design analysis (see 3.6.1) and reviewed at the technical reviews.

3.4.3.2 Maintainability.

3.4.3.2.1 Corrective maintenance prediction. The contractor shall prepare and maintain a corrective maintainability prediction for mean time to repair (MTTR) for each end item in accordance with A.4.5 of the PD(s). The model and failure rate data shall be consistent with that of the basic reliability prediction (see 3.4.3.1.2). The corrective maintenance prediction shall be documented for each end item in the consolidated design analysis (see 3.6.1) and reviewed at the technical reviews.

3.4.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 for each end item as an attachment to the MSR (see 3.2.3).

3.4.5 Counterfeit prevention plan (CPP). Contractors that supply electronic parts or systems that contain electronic parts shall establish policies and procedures to avoid, detect, mitigate, and dispose of counterfeit electronic parts to prevent such parts from entering the United States Air Force (USAF)/DoD supply chain. These policies and procedures shall be documented in a CPP for submission and approval in accordance with 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.

The initial CPP shall be delivered 30 days prior to the PDR. The CPP shall be updated as counterfeiting methods evolve to include any new indicators, as well as new prevention processes needed (either discovered directly or provided by the Government). (DIMISC81832, Counterfeit Protection Plan, C004)

3.4.5.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.4.5.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.4.5.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 Equipment Manufacturers (OEM) or their Authorized Distributors. In cases where materials, systems, assemblies, subassemblies, or parts are no longer available from the OEM 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.4.5.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 that 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.4.5.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 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-percent 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.4.5.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.4.5.6 Testing and verification. The contractor shall establish and accomplish testing and verification processes for items not received from an OEM, 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.4.5.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 provided timely notification to the Government. (Ref. 4.1.6 and Appendix F of AS5553)

3.4.5.8 Counterfeit notification and reporting. The contractor shall report in writing to the PCO within 30 days of determining any end item, component, part, or material contained in supplies purchased by the DoD 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 Air Force Material Command (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.4.5.9 Counterfeit prevention training. The contractor shall provide appropriate training to all personnel working procurement within their company, to include, at a minimum, their supply chain management specialists, receiving inspectors, and engineers, and shall require all such personnel 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 personnel.

3.4.6 Cybersecurity requirements. The contractor shall implement cybersecurity in accordance with Department of Defense Instruction (DODI) 8500.01, DODI 8510.01, and AFI 17-101. The contractor shall provide cybersecurity support to include, but not limited to, engineering and technical analysis and assessment of system cybersecurity, development and delivery of Risk Management Framework (RMF) artifacts, and design, integration, testing, and documentation of implemented cybersecurity controls. The contractor shall include cybersecurity activities and events on the IMS. The contractor shall address technical details of cybersecurity requirements as part of the PDR and CDR.

3.4.6.1 Cybersecurity analysis. The contractor shall perform an engineering analysis and risk and technical assessment of system cybersecurity for each end item. The engineering analysis shall include, but not be limited to, system hardware and software architecture, I/O data flow, supply chain integrity, and operational conditions as it relates to system cybersecurity. The contractor shall perform a comprehensive risk assessment based on the system cyber vulnerabilities and threats. The contractor shall also conduct analysis for any commercial-off-the-shelf and/or non-developmental items to ensure that they are appropriately configured, software, hardware and firmware is controlled, and any unique risks they pose are mitigated. The initial report shall be delivered 30 days prior to PDR. (DI-MISC-80508, Technical Report – Study/Services, Cybersecurity Analysis, C005)

3.4.6.2 Risk management framework (RMF). The contractor shall develop and deliver the required artifacts for the Platform Information Technology (PIT) Assessment and Authorization (A&A) package to meet the intent and requirements of DODI 8510.01 and AFI 17-101 for RMF implementation. The contractor shall utilize National Institute of Standards and Technology (NIST) Special Publication (SP) 800-37, NIST SP 800-53, and applicable overlays in addressing the security controls associated with the various artifacts. The contractor shall include cybersecurity RMF activities and events on the IMS. The contractor shall deliver the initial RMF for each end item (Group A contractor shall consolidate the report) 30 days following PDR. (DI-MGMT-82135, RMF A&A Products, C006)

3.4.6.3 Cyber-secure development environment. The contractor shall take necessary precautions and actions to ensure that the information technology environment for any software/firmware development is secure and free of malware and malicious code. The contractor shall maintain a cyber-secure development environment that reduces and manages risk by meeting the intent of the controls as defined in NIST SP 800-53: CM-1, SA-3, and AT-2. 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.

3.4.6.4 Software. The contractor shall develop and deliver a Software Assurance Evaluation Report (SAER) to demonstrate that all delivered software functions as intended and is pending free of vulnerabilities (i.e. defects, bugs, malware, etc.) either intentionally or unintentionally inserted as part of the software throughout the development lifecycle. The contractor shall deliver the initial report 30 days prior to the Phase one TRR. (DI-IPSC-82249, Software Assurance Evaluation Report (SAER), C007)

3.4.6.5 Computer program identification number (CPIN). The contractor shall submit a request for CPIN assignment of all custom and/or commercial software to include, but not limited to, any diagnostic software, any utility software for firmware updates, the firmware itself, and any other support software to be delivered to the Government. CPIN assignment requests shall be accomplished by direct on-line data entry into Enhanced Technical Information Management System (ETIMS) in accordance with TO 00-5-16 guidelines. The contractor shall deliver the final Computer Software Configuration Items (CSCIs) on CD-DVD-ROM. The CPIN media label information shall match the information in ETIMS. The contractor shall deliver the CPIN catalog information 30 days after PDR. The contractor shall deliver the computer software product end items within 30 days after Government approval of the final first article test report. (DI-MISC-81454, Computer Program Identification Number Catalog Information, C008); (DI-AVCS-80700, Computer Software Product End Items, C009)

3.5 Logistics.

3.5.1 Technical Order (TO) requirements. The contractor shall participate in an Initial Guidance Conference (IGC) within 30 days ARO to ensure mutual understanding of TO contract requirements, schedules, points of contact, etc. The IGC shall be held in conjunction with the postaward conference at Robins AFB and/or via virtual environment as required. Note: excluding the first article GPUs and ULB, no GPUs or ULB delivery acceptance shall occur without completed and Government-accepted technical manuals.

3.5.1.1 TO content. In addition to the TO content required in accordance with the TM-86-01, the following special data shall also be included:

a. The information as it is presented on the data plates in the following PD paragraphs: 3.12.12.1, Identification plate; 3.12.12.2, Unique Identification (UID); 3.12.12.3, Transportation data plate; 3.12.12.4, Operating procedures plate; and 3.12.12.5, Corrosion treatment data plate.

b. A list of all non-standard torque values for fastening hardware used throughout the end item, to include items such as generator to coupling to engine hardware, vibration isolation hardware, suspension mounting hardware, etc.

c. Complete wiring information, such as wire running lists (size, type, designation, to/from, each end’s connectors, etc.), wiring diagram, wiring schematic for the GPUs and ULB.

d. Complete description of the warranty process.

e. For the GPUs, remove and replace procedures for only the engine, only the generator, and both at the same time. These procedures shall include directions on how to build temporary supports required for the engine or the generator when the other item is removed.

f. Complete software identification information, to include the Government-assigned CPIN(s) and the OEM’s identification code(s) for any unique software for the end item(s), such as the engine control module.

3.5.1.2 Group A TO requirements. The contractor shall develop and deliver a series of Air Force technical manuals for the 72 kW GPU, the 144 kW GPU, and the 144 kW ULB. Each end item shall have its own distinct series of technical manuals in accordance with TM-86-01. (TM-86-01, Air Force TMCR, D001)

3.5.1.3 Group B TO requirements. The contractor shall develop and deliver a series of Air Force technical manuals for the 72 kW GPU. The end item shall have its own distinct series of technical manuals in accordance with TM-86-01. (TM-86-01, Air Force TMCR, D001)

3.5.1.4 TO access. The contractor shall contact the TO Management Agency (TOMA) office located at Robins AFB (406/SCMS/GULAC) to be placed on “Initial Distribution” for TO(s) listed in the Technical Manual Contract Requirements (TMCR) (TM-86-01). This process will allow the contractor to obtain the most recent copy and any updates to these TO(s) for the duration of the contract.

3.5.2 Provisioning. The contractor shall identify all parts in a top-down break down format to meet system and equipment operation and supportability in accordance with the Air Force Initial Provisioning Performance Specification (IPPS). GEIAHB0007 shall be used as a guide. Format shall be consistent with existing Government Provisioning data system (D220). (DI-SESS-81758, Logistics Product Data, Provisioning Parts List (PPL), Design Change Notices (DCNs), Statement of Prior Submission (SPS)); DI-SESS-81874, Engineering Data for Provisioning (EDFP). The following Data Item Descriptions (DIDs) shall apply:

a. C010, 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. C011, DI-SESS-81874, Engineering Data for Provisioning (EDFP).

3.5.2.1 Provisioning guidance conference. A Provisioning Guidance Conference (PGC) will be scheduled by the Prime Provisioning Activity (PPA) and shall be held in conjunction with the postaward conference. The PGC is normally held at Air Force Global Logistics Support Center 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. (DIADMN81249, Conference Agenda, A002; DIADMN81250, Conference Minutes, A003)

3.5.3 Training. The contractor shall plan for and conduct training on each end item. This training shall be scheduled to take place at the contractor’s facility within the continental United States (CONUS) not less than 30 days prior to the shipment of any end item for compatibility testing, whether Group A or Group B. The Government prefers the Group A contractor conduct a combined “hands-on” operation and maintenance training for all end items. The training shall include, but not be limited to operational familiarization, ease of maintaining the unit for both corrective and preventative efforts, support/test equipment review, unit safety features, application of technical manual to modes and effects, troubleshooting/fault isolation, and theory of operation. This training shall provide aircraft ground equipment technicians with adequate skills to operate and provide general maintenance for the up-keep of the GPUs and ULB in the field. The contractor is not required to provide transportation to and from the site, lodging, or meals for DoD personnel during the training.

3.5.3.1 Training material. The contractor shall develop training material to be provided for up to 25 DoD personnel attending the training, using MIL-HDBK-29612-3 as a general guide, although contractor format is acceptable. This training material shall include, but not be limited to, all required training identified in 3.5.3. The contractor shall deliver the training material 30 days prior to the scheduled training. (DI-ILSS-80872, Training Material, D002)

3.5.3.2 Pack Up Data. The contractor shall develop interactive training on CD-ROM or DVD-ROM illustrating the hands on operational and maintenance familiarization training for field users. The media shall be compatible with Microsoft Windows 10 operating system. Feedback from the DoD personnel attending the hands on operational and maintenance familiarization training shall be gathered and used to develop a final version of interactive training material to be used for organizational level familiarization.