SOW - 72kw Generator Set - (20200830 - 1915).docx

<SOW DATE>

Statement of Work (SOW) for

72 kW / 90kVA GENERATOR SET

Prepared by

SUPPORT EQUIPMENT AND VEHICLES PROGRAM OFFICE

235 BYRON ST STE 19A

ROBINS AFB GA 31098-1813

THIS PAGE HAS BEEN INTENTIONALLY LEFT BLANK

TABLE OF CONTENTS

1. SCOPE 6

2. APPLICABLE DOCUMENTS 6

3. REQUIREMENTS 8

1. SCOPE

This document defines the tasks associated with the procurement of 72 kW/90 kVA Generator Set as described by <PD NUMBER TBD> and is to be used in conjunction with <PD NUMBER TBD>. The 72kW/90 kVA Generator Set is hereby referred to as the Ground Power Unit (GPU). Throughout the rest of this SOW <PD NUMBER TBD> is hereby referred to as the PD.

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 documents form a part of this SOW to the extent specified herein. Although revision letters for specifications/documents may not be cited within the text of the SOW or the PD, it shall be understood that the below listed revision letters apply to their respective specifications or documents when the specifications or documents are called out within the text. All documents cited as references in both this SOW and the PD shall be the latest revision unless specifically stated otherwise.

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.

AIR FORCE INSTRUCTION (AFI)

(Copies of this document 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

DEPARTMENT OF DEFENSE MANUALS

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 Program Management.

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

3.1.2 Plant Access. The contractor shall arrange for full access to applicable contractor facilities and offices by Government representatives conducting any business, making observations, or performing inspections required by public law or by this contract.

3.1.3 Monthly Status Report. The contractor shall track program progress and document such via monthly status reports. The contractor shall submit a monthly status report that shall cover the engineering and technical development of the system and subsystems as well as a projection of planned work for the remaining effort. Reports shall document tasks, issues, actions, and deliverables. Problem areas shall be identified with proposed solutions and outcomes. The current program integrated master schedule (IMS) (see 3.1.5); and risk management analysis, mitigation plan, and tracking (see 3.3.4) shall be provided as attachments to the monthly status report. (DIMGMT80227, Contractor's Progress, Status and Management Report)

3.1.4 Reserved.

3.1.5 Integrated master schedule (IMS). A baseline IMS shall be developed at the start of the program in accordance with DIMGMT81861, Format 6. The contractor shall implement and maintain the IMS using the original baseline schedule as an unchanging reference. The IMS shall be provided in both Microsoft Project and PDF formats as an attachment to the monthly status report (see 3.1.3). (DIMGMT81861, Integrated Program Management Report (IPMR))

3.2 Conferences and Program Reviews.

3.2.1 Post-Award conference. The Government will convene a post-award conference with the contractor at a location that is mutually agreeable to both parties within 30 days after contract award. The Procuring Contracting Officer (PCO) will coordinate the actual date, time, and location of the conference with the contractor.

3.2.2 Technical reviews.

3.2.2.1 Design reviews.

3.2.2.1.1 Design review location and schedule. The contractor shall host a preliminary design review (PDR) within 60 days after the contract is awarded. The contractor shall host a critical design review (CDR) within 180 days after the contract is awarded.

3.2.2.1.2 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.5.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; training materials; lists of materials, parts, and processes; human engineering elements; corrosion control; maintainability; production capability and manufacturing; and quality considerations. Final drawings, final calculations, and any mockups or any assemblies shall be made available for the Government review as well. All applicable comments from the PDR shall be incorporated into the CDR design documentation.

3.2.2.2 Test readiness review (TRR). The contractor shall host 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.

3.2.2.3 Technical review documentation. The contractor shall prepare all necessary detailed status reports for the technical review meetings, conference agendas, and conference minutes. The contractor shall prepare formal documentation of the PDR, CDR, and TRR. (DIMISC80508, Technical Report/Study Services)

3.2.3 Program Management Review support. The contractor shall participate in and support all reviews, audits, and meetings as requested by the PCO or the contractor. Program Management Reviews shall be conducted quarterly or as required at a mutually agreeable location or via teleconferences.

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

3.2.5 Meeting agendas. The contractor shall publish an agenda for all meetings and conferences specified in 3.2.2 and 3.2.3. The contractor shall request from the Government any items or issues to be discussed or presented at the meetings, and shall include such items in the agenda. Agendas shall be submitted not less than five working days prior to any meeting. (DIADMN81249, Conference Agenda)

3.2.6 Meeting minutes. The contractor shall provide a written record of the discussions, decisions, and action items identified at each meeting. Minutes shall include presentation material. (DIADMN81250, Conference Minutes). The contractor shall submit meeting minutes no later than 10 days after the meeting. (DI-ADMN-81250A, Conference Minutes)

3.3 Systems engineering.

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

3.3.1.1 System safety. The contractor shall establish, conduct, document, and maintain a system safety program in accordance with MILSTD882. The contractor shall document their approach for analyzing, eliminating, or minimizing ESOH hazards during all phases of the program. The contractor shall initiate changes in the system design based on safety analysis results such that the associated risk is reduced to a level acceptable to the Government. An initial system safety hazard analysis shall be provided 14 days prior to the PDR; updated versions of the analysis shall be provided 14 days prior to the CDR, 14 days prior to the TRR, and with the first article test report. (DISAFT81626, System Safety Program Plan (SSPP); DISAFT80101, System Safety Hazard Analysis Report (SSHAR))

3.3.1.2 Hazardous materials. The contractor shall manage hazardous materials, including those embedded in the system or used during operation or maintenance, as an element of the Systems Engineering process. The system shall not generate or use Class I or Class II Ozone Depleting Substances (ODS) during manufacture, operation, maintenance, or disposal. The use of hexavalent chromium is also prohibited. The contractor shall list any hazardous materials, as defined in AFI 327086, to be delivered under this contract, including locations, quantities, and special handling and disposal procedures. This information shall be documented in the design analysis (see 3.5.1) and reviewed at the technical reviews; it shall be in accordance with FEDSTD313.

3.3.2 Corrosion control. The contractor shall establish, conduct, document, and maintain a corrosion prevention control program; it shall be documented in a corrosion prevention and control plan in accordance with 4.1 of MILSTD1568. The initial corrosion prevention and control plan shall be provided 14 days prior to the PDR; the second submission of the plan shall be provided 14 days prior to the CDR. (DIMFFP81403, Corrosion Prevention and Control Plan)

3.3.3 Reliability and maintainability.

3.3.3.1 Reliability.

3.3.3.1.1 Basic reliability model. The contractor shall develop and maintain a basic reliability model for the system in accordance with A.4.1 of the PD. The basic reliability model shall be documented in the design analysis (see 3.5.1) and reviewed at the technical reviews.

3.3.3.1.2 Basic reliability prediction. The contractor shall prepare and maintain a basic reliability prediction for the system in accordance with A.4.2 of the PD; it shall be based upon the associated basic reliability model (see 3.3.3.1.1). The basic reliability prediction shall be documented in the design analysis (see 3.5.1) and reviewed at the technical reviews.

3.3.3.1.3 Failure Modes, Effects, and Criticality Analysis (FMECA). The contractor shall prepare and maintain a FMECA for the system in accordance with A.4.3 of the PD; it shall be based upon the associated basic reliability model (see 3.3.3.1.1). The FMECA shall be documented in the design analysis (see 3.5.1) and reviewed at the technical reviews.

3.3.3.2 Maintainability.

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

3.3.3.2.2 Reliability-Centered Maintenance (RCM) analysis. The contractor shall perform RCM analysis in accordance with A.4.4 of the PD in order to develop preventive maintenance tasks and intervals. The RCM analysis and the preventive maintenance tasks and intervals shall be documented in the design analysis (see 3.5.1) and reviewed at the technical reviews.

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

3.3.5 Reserved.

3.3.6 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 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. The initial CPP shall be provided 90 days prior to the PDR. (DIMISC81832, Counterfeit Protection Plan)

3.3.6.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.3.6.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.3.6.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.3.6.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.3.6.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.3.6.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.3.6.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.3.6.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.3.6.8 Counterfeit notification and reporting. The contractor shall report in writing to the 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.3.6.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.4 Logistics.

3.4.1 Technical Order (TO) requirements. The contractor shall develop and deliver technical manuals in accordance with TM-86-01. (TM-86-01, Air Force Technical Manual Contract Requirements) Note: excluding the first article GPU's, no generator set delivery acceptance will occur without completed and Government accepted technical manuals. The Technical Manuals shall include complete rebuild/overhaul procedures for the engine and generator, to include generator rewind data. The program equipment specialist and the program engineer shall attend the technical order verification at the contractor's facility.

3.4.2 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-0007A (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) apply:

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

(1) Provisioning Parts List (PPL)

(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)

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

c. DI-SESS-81759A/T Logistics Product Data Summaries

(1) Support Equipment Recommendation Data (SERD)

(2) Standard Modified Hand Tools List

3.4.2.1 Provisioning Guidance Conference. A Provisioning Guidance Conference (PGC) shall be scheduled by the Prime Provisioning Activity (PPA) and should be held within 45 days after receipt of contract. The PGC is normally held at AFGLSC PPA for approximately two days to ensure both the contractor and the Government understand the provisioning requirements on contract. If a PGC is not desired, the contractor shall submit a written request for waiver of the PGC to the PPA. In the event a waiver is approved, a mutual understanding of the Provisioning requirements shall be communicated in some forum in which the AFMC Form 718 (Provisioning Performance Schedule (PPS)) shall be documented/completed, signed by both the Government and contractor, and a contract modification issued, if required. (DIADMN81249, Conference Agenda; DIADMN81250, Conference Minutes)

3.4.3 Reserved.

3.4.4. Training/familiarization. Operation and Maintenance Orientation. The contractor shall plan for and conduct a onetime classroom and “hands-on” operation and maintenance orientation for the using activities to familiarize the users with the GPU. The orientation 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 orientation shall take place at the contractor facility (within CONUS) within 90 days prior to shipment of the GPUs to the OT&E locations. The contractor shall provide all required reference material in accordance with paragraph 3.4.2 herein for up to 15 DOD personnel. Copies of the latest draft effort in developing the Technical Manual (TM)/ Technical Order (TO) for the GPU shall also be available. The contractor is not required to provide transportation to and from the site, lodging, or meals for the approximately 15 DOD personnel during the orientation. The orientation shall be attended (at a minimum) by the Government program engineer, program equipment specialist, and USAF military personnel (DI-ILSS-80872/T)

3.4.4.1 Operation and Maintenance Familiarization/Orientation Material. The contractor shall develop an interactive multimedia system (program media) on CD ROM or DVD to be used during the Operation and Maintenance Orientation and for use in the field for familiarization of operational and maintenance personnel at the organizational level. MIL-HDBK-29612-3A should be used as a general guide, although contractor format is acceptable. This program media shall be in sufficient detail to provide the technician adequate skills to operate and provide general maintenance for the up-keep of the GPU in the field. The program media shall also be in sufficient detail to allow the Air Education and Training Command (AETC) to formulate a training course for future use. The program media shall be compatible with existing Air Force personal computers (Microsoft Windows based operating systems) and consist of all materials (e.g., software, firmware) necessary to execute the Familiarization/Orientation Material. Approximately fifteen copies of the draft version program media shall be available for use at the Operation and Maintenance Orientation for DOD personnel. Feedback from the 15 DOD personnel attending the Operation and Maintenance Orientation shall be gathered and used to develop the final version of the program media to be used for organizational level familiarization. The program media shall be subject to final Government approval before final delivery. Final delivery of 2 copies of the program media shall be made to WR-ALC IAW DD Form 1423. One copy of the program media shall sent with each GPU as pack up data. Note: excluding the first article GPU's, no generator set delivery acceptance will occur without completed and Government accepted Orientation Material. (DI-ILSS-80872/T and MIL-HDBK-29612-3A) (DIILSS80872, Training Materials)

3.4.4.2 Government Rights. The contractor shall extend to the Government unlimited usage rights for the duplication and distribution of the Operation and Maintenance Familiarization /Orientation Material (program media) identified in 3.4.2.3

3.5 Testing and evaluation. Testing and evaluation shall be done in parallel as much as possible.

3.5.1 Design analysis. A design analysis of the system and each subsystem shall be performed to verify compliance with this SOW and each applicable requirement of the PD. The analysis shall include, but is not limited to, environmental and hazardous material management (see 3.3.1.2); a basic reliability model (see 3.3.3.1.1) and prediction (see 3.3.3.1.2); a FMECA (see 3.3.3.1.3); a corrective maintenance prediction (see 3.3.3.2.1); an RCM analysis and preventive maintenance tasks and intervals (see 3.3.3.2.2); and the PD paragraphs listed in PD TABLE IX – Required Analyses. A Material Safety Data Sheet (MSDS) shall be provided for each hazardous material identified for use in the program (see 3.3.1.2). (Note that the system safety hazard analysis is addressed in 3.3.1.1) An initial design analysis shall be provided 14 days prior to the PDR; updated versions of the analysis shall be provided 14 days prior to the CDR, 14 days prior to the TRR, and with the first article test report. (DIMISC80508, Technical Report/Study Services)

3.5.2 First article test.

3.5.2.1 First article test procedures. The contractor shall develop detailed first article test procedures, which shall address all requirements identified in the PD and this SOW. 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. (DINDTI80603, Test Procedure)

3.5.2.2 First article testing. After Government approval of the first article test procedures, the contractor shall schedule the testing to be conducted. If shipping is required to move the item(s) to and from a test site away from the contractor’s facility, the contractor shall be responsible for all costs associated with the shipment. The contractor shall notify the Government of the date, time, and location of first article testing 30 days prior to the start of testing. The test will be witnessed by one or more Government representatives.

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

a. Test logs.

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

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

d. Records of preventive maintenance activities performed.

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

(DIMGMT80227, Contractor's Progress, Status and Management Report)

3.5.2.4 Compatibility testing. During the first article test, a test item shall be shipped to <COMPATIBILITY TEST LOCATIONS> for compatibility testing in accordance with PD 4.6.14. Air Force personnel will perform the test and any required maintenance; contractor personnel shall witness the test and maintenance and advise the Air Force personnel. At the conclusion of the compatibility test, the test item shall be shipped to the contractor’s facility. The contractor shall be responsible for all costs associated with shipping the item to the compatibility test location and returning it to the contractor’s facility.

3.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 include the following MIL-STD-705 test results from the generator sub-contractor:

1. Open circuit saturation curve (Method 410.1c)

1. Synchronous impedance curve (Method 411.1c)

1. Zero power factor curve (Method 412.1c)

1. Rated load current saturation curve (Method 413.1c)

1. Direct axis transient reactance (Method 425.1c)

1. Negative sequence reactance (Method 422.1c)

1. Efficiency (Method 415.1d) shall be measured at 25, 50, 75, 100, and 125% balanced rated load at both 0.8 pf and 1.0 pf.

The test report shall document all testing performed, including results of any unsuccessful test attempts. Failure reports generated as a result of the FRACAS process (see PD 4.5.4) shall be included with results of unsuccessful test attempts. (DINDTI80809, Test/Inspection Report)

3.5.2.6 Transportation/Shipping. The contractor's shipping responsibility shall be as specified in the contract and shall include at a minimum: all liability and costs incurred to move all equipment to/from and between locations for testing and/or demonstration purposes.

3.5.2.7 Aircraft Transportability Certifications. The contractor is responsible to provide all required data to the procuring activity in order to obtain all necessary transportability certifications. This data shall be provided with the preliminary first article in-plant test data. (Need DID)

3.5.3 Operational Test and Evaluation (OT&E). After completion of first article testing and approval by the Government of the first article test report, # first article GPUs shall be shipped to <OT&E LOCATIONS> for OT&E. The contractor shall be responsible for all costs associated with shipping. Air Force operators and maintainers will conduct all OT&E. The contractor shall provide a spare parts kit with each first article GPU 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 Government holidays) all times during the OT&E. All OT&E shall be completed within allocated <OT&E DAYS> days.

3.5.4 Restoration. After completion of first article and OT&E acceptance, the first article GPUs shall be shipped, within 30 days, to the contractor’s facility for restoration. The contractor shall be responsible for any repairs that may be necessary to restore the first article GPUs to a serviceable, “like new” condition while retaining configuration integrity. The contractor shall be responsible for all costs associated with shipping of the first article GPUs to the contractor's facility for restoration. The Government intends use the same first article GPU for the worst part of mobility testing and salt fog testing. The GPU used for these two test is not required to be restored. The GPU used for the sand and dust testing is not required to be restored.

3.5.5 Disposition. One first article GPU shall be retained at the contractor’s facility, to serve as a manufacturing standard, until the last shipment. The remaining first article GPUs shall be shipped to the location(s) specified in the contract.

3.5.6 Conformance inspection procedure and report. The contractor shall test each production item in accordance with the PD paragraphs listed in PD TABLE X Conformance Inspection Verification Paragraphs, which lists a subset of the first article test requirements.

3.6 Configuration management.

3.6.1 Configuration requirements. After First Article (FA) acceptance, the contractor shall establish and maintain configuration control. The accepted First Article units shall serve as the manufacturing standard. All further units shall be produced to the same design and using the same parts as the First Article unit.

3.6.1.1 Baselines.

3.6.1.1.1 Functional baseline. The PD is the functional baseline.

3.6.1.1.2 Allocated baseline. All of the documents used to produce and define the accepted CDR configuration shall constitute the allocated baseline.

3.6.1.1.3 Product baseline. All of the documents used to produce and define the accepted first article GPUs shall be identified in a Product Base Line Index (PBLI). The list shall identify the applicable version number as required. (DICMAN81218, Product Base Line Index (PBLI))

3.6.1.2 Production release. Production release is acknowledgment by the procuring activity that the contractor has satisfied all requirements to proceed with delivery of hardware to be furnished under the contract. The contractor assumes all risks in initiating production before the first article test report and TOs have been delivered and approved by the procuring activity.

3.6.2 Engineering Change Proposals (ECPs). Notwithstanding any other provision in the contract, no contractor or subcontractor's change in design, fabrication, assembly, part, material, process, or source of supply shall be made to the allocated or product baseline unless such change is submitted in writing by ECP and approved by the procuring activity. Any request for change shall be accompanied by complete documentation supporting the need for the change. A system safety impact statement shall be provided as part of the submittal; it shall quantify and qualify the system safety risk identified and how it impacts the system safety risk already identified for the system. A Notice of Revision (NOR) shall be submitted with each ECP. Should the Government approve an ECP, the contractor shall be responsible for submitting updated TOs and the system safety hazard analysis report (see 3.3.1.1) to reflect the changes made in the ECP. (DISESS80639, Engineering Change Proposal (ECP); DISESS80642, Notice of Revision (NOR)).

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

3.6.4 Engineering data. The contractor shall develop/produce/maintain and deliver a Technical Data Package (TDP) that accurately depicts the final product. The TDP shall represent the approved, tested, and accepted configuration of the defined delivered item(s). 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. 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 delivered in accordance with Air Force Product Data Specification drawing 9579776 Revision L (CAGE Code 98752), reference attached DD Form 1423 Block 16. (DI-SESS-81000, Product Drawings/Models and Associated Lists)

3.6.4.1 Engineering Data Guidance Conference. The contractor shall support and co-chair a Guidance Conference with AFLCMC/LZPEM for engineering data within 60 days after contract award. The Conference shall be convened at a site and on a date agreed upon by the Government contracting officer and the contractor. The contractor shall prepare an agenda and record the minutes of the Guidance Conference. The contractor shall address, discuss, and provide status on the following:

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 drafting practices/procedures/TDP drawing formats/CAD programs.

e. The contractor's quality assurance procedures relating to TDP documents, including quality control of subcontractor and vendor data.

f. The role of subcontractors and vendors who may deliver TDP documents under this contract.

g. The contractor's configuration management system, including methods for releasing documents, approving documents, and incorporating changes into documents.

h. Digital Technical Data Package (TDP) deliverables.

Note: The Guidance Conference may be held in conjunction with other meetings or conferences. (DIADMN81249, Conference Agenda; DIADMN81250, Conference Minutes)

3.6.4.2 In-process review (IPR) of the TDP. The contractor shall host, support, and co-chair an IPR of the engineering drawings and associated lists and other documentation to be included in the TDP. The IPR shall be conducted only after the contractor's quality assurance personnel have completely reviewed the data and determined that data are of sufficient quality that Government time will be effectively utilized during the review. IPR may be scheduled when data has reached the 50 percent completion point and shall be held, when possible, in conjunction with other reviews (for example, PDR or CDR). The contractor shall notify AFLCMC/LZPEM a minimum of 30 days prior to the anticipated date of completion point. The IPR shall focus on the contractor's progress in the preparation of the TDP. The contractor shall support and provide the necessary resources, that is, meeting agenda, conference room, applicable data, minutes, and appropriate personnel available to answer any questions to perform the IPR effectively. The contractor shall correct all discrepancies identified in the IPR. All subcontractor/vendor data shall be made available for review. If the quantity of subcontractor/vendor data is of sufficient magnitude, the Government may schedule a separate IPR at the subcontractor's/vendor's facility. (DIADMN81249, Conference Agenda; DIADMN81250, Conference Minutes)

3.6.4.3 Relationship of the contractor with subcontractors and vendors. The contractor shall levy on sub-contractors and sub-vendors the same requirements for TDPs as are levied on them by this contract. This requirement shall apply at all tiers of sub-contractor/vendor levels associated with the program.

3.6.4.4 Engineering data updates and revisions. The contractor shall (and shall cause subcontractors and vendors to) update and maintain engineering data for the item(s) designed/developed/modified/produced and funded by this contract for the life of this contract and shall incorporate all changes in accordance with the following:

a. All engineering changes shall be incorporated into the applicable engineering data within 90 days after engineering release/Air Force concurrence or at intervals of five changes, whichever occurs first, except a change involving safety, which shall be incorporated immediately.

b. All engineering changes shall be incorporated into the applicable engineering data prior to delivery of data for review.

c. All engineering changes shall be incorporated into the applicable engineering data prior to delivery of final media.

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

3.7 Warranty. The contractor shall provide a warranty on each GPU for 24 months or 2400 operating hours, whichever comes first. The warranty shall cover all parts, labor, and technical data to include the Government specified engine and Government specified generator sub-system. For CONUS warranty failures, the contractor shall have # days from notification to return a replacement part to the unit, and # days for OCONUS warranty failures.

3.7.1 Warranty focal points. 30 days prior to the first production unit delivery, the contractor shall the provide the Government with warranty focal point(s) name(s), phone number(s), and email address(es). The contractor shall notify the Government program manager whenever any information on the warranty focal point(s) change, within 1 day of any changes.

3.7.2 Warranty shipping costs. The contractor shall be responsible for all shipping costs of warranted items to and from the user’s location both CONUS and OCONUS.

3.7.3 Warranty failure database. The contractor shall maintain a database of all warranty failures. For each warranty failure, this database shall include the failed component, probable cause of the failure, recommended corrective action, location of the GPU at the time of the failure, date of failure, GPU operating hours at the time of the failure. The contractor shall provide a summary report of the warranty failures every # months. (DIMISC80508, Technical Report/Study Services) DISTRIBUTION STATEMENT A. Approved for public release: Distribution is unlimited.