13820 - SOW.docx

24June2025

Statement of Work (SOW) for GTE Test Cell Rehost Upgrade

Prepared by:

COMMODITIES SUPPORT MAINTENANCE GROUP

309TH CMXG

HILL AFB UT 84056

TABLE OF CONTENTS

1. SCOPE

1.1. Scope. This Statement of Work (SOW) defines the tasks associated with Rehosting the Gas Turbine Engine (GTE) test cells with new data acquisitions systems. This tasking includes all associated hardware and software, including computer systems that serve as HMI (Human Machine Interface) and data storage and handling systems.

2. APPLICABLE DOCUMENTS

2.1. Government Documents.

2.2. Other Government Documents, Drawings, and Publications.

2.2.1. The Government will provide the current set of drawings to the contractor.

Current drawing package

2.3. General Industry Publications. All work shall conform to the following:

2.3.1. NFPA 70: National Electric Code (NEC), latest edition

2.3.2. 29 CFR 1910 Occupational and Health Administration (OSHA) General Industry Regulations

2.4. 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. Upgrade Data Acquisition System. The Contractor shall upgrade the Data Acquisition system to the latest version of software and hardware platform that they deem to be the best fit for performance, Reliability, Accessibility and Maintainability (RAM). The system will maintain all of the features and capabilities of the existing system and include new features and capabilities outlined in this SOW.

3.1.1. A new computer for each test cell shall be included and running the latest supportable versions of ProTECS and Windows.

3.1.2. The Contractor shall supply all the needed computer monitors.

3.1.3. The engine bay monitor shall be replaced with a ruggedized (20” minimum) monitor appropriate for the fuel and oil environment.

3.1.4. The contractor shall supply one spare DAQ controller if applicable.

3.1.5. The contractor shall supply one spare computer.

3.1.6. Each test cell shall be capable of running all current Test Program Sets (TPS) on ProTECS software.

3.2. Corrections and Additions. The system shall include the following corrections and additional features.

3.2.1. The contractor shall provide a channel that can accurately read a Linear Voltage Differential Transducer (LVDT). The contactor shall add this capability to the system so an Inlet Guide Vane position reading can be obtained. The accuracy must meet the requirement of ± 1.5 °.

3.2.2. The Exhaust Gas Temperature (EGT) Survey utility used in the F22 TPS) (Cell 3) has deficiencies. The purpose of this utility is to remove an exhaust EGT channel reading from the average, if the value looks unreasonable, for example an open T/C. It is allowable to have two sensor readings out of the EGT average at a time. It appears that if more than two probes read higher than the set limit it disables all channels. To reset the utility, the program must be exited and restarted to get EGT readings again. The contractor shall modify this utility so it will continue to read all EGT Channels even if more than two EGT readings are out of range but alert the operator that a requirement has not been met. This non-compliance shall be captured by the TPS and shown in the test report as a failed requirement. Comment by MCFARLAND, KENNADIE L CIV USAF AFMC 309 CMXG/MXDSR: What is this? Is this info relative? Comment by CARTER, REX M CIV USAF AFMC 309 CMXG/MXDEA: The contractor will know what this is, it is the name of a piece of code they wrote. It should be left like this so they can easily recognize it.

3.2.3. There are power requirements for generator load on the 85 series engines. Currently there is no monitoring to ensure the expected power is being applied. Since the load bank has no monitoring, the load on a phase could fail and there would be no indication. The contractor shall upgrade the system to read voltage and current on all phases, so the true kilowatt load can be calculated. An alarm condition shall notify the operator if the load value is out of range. This condition shall be captured by the TPS and reported as a failure. Comment by MCFARLAND, KENNADIE L CIV USAF AFMC 309 CMXG/MXDSR: Is this relative? Can we just put what we want them to do? Comment by CARTER, REX M CIV USAF AFMC 309 CMXG/MXDEA: Yes, it is relative, giving background so there is no doubt of the current state. The 3rd sentence defines the requirement.

3.2.4. Calibration Utility

3.2.4.1. In cases where a sensor is calibrated off the stand and correction offsets are entered by way of a table there is no capture of that event that shows the calibration dates. Examples of this are flow meters and vibration sensors. The contractor shall add a feature that allows calibration dates of sensors to be entered into the system, so technicians get a notice when the due date is approaching.

3.2.4.2. The system shall notify an operator when a calibration due date is approaching and not allow a test to run if any calibrated channels are past their due date. This feature should be determined by log in privileges. An operator should not be allowed to run but an engineer should be allowed to run. Comment by MCFARLAND, KENNADIE L CIV USAF AFMC 309 CMXG/MXDSR: Who determines that? Who gives access? Comment by CARTER, REX M CIV USAF AFMC 309 CMXG/MXDEA: The 2nd sentence defines this.

3.2.5. Currently speed control on the 85 series engines is done by bypassing fuel, this method has not always resulted in good speed control. The Contractor shall add capability to better control speed by controlling the air pressure to the fuel control. This would consist of a voltage or current controlled air pressure regulator that would control air pressure directly to the fuel control. Comment by MCFARLAND, KENNADIE L CIV USAF AFMC 309 CMXG/MXDSR: Needs to be reworded to what we are asking for Comment by CARTER, REX M CIV USAF AFMC 309 CMXG/MXDEA: We are asking for the contractor to add capability to accomplish speed control through air pressure regulation at the fuel control. We don’t want do dictate this so tight that they can’t user a better method if they know of one. The last sentence defines the requirement. Comment by BERRETT, ERIC J CIV USAF AFMC 309 CMXG/MXDEA: Reworded this so that the requirement is in the second sentence. If this changes the meaning of the requirement you can change it back. Comment by MCFARLAND, KENNADIE L CIV USAF AFMC 309 CMXG/MXDSR: done

3.2.6. C17 load bank control is currently done by way of a serial interface utility provided by the OEM (Original Equipment Manufacturer). It is problematic because it sometimes loses communication and doesn’t seem to be very robust. The contractor shall consider integrating this feature into ProTECS. This would consist of Digital outputs to control the various loads of the load bank. However, there are other features of the load bank that would have to be considered, such as voltage and current monitoring. Voltage and current monitoring are currently done through the Loadtec (OEM) utility, if a manual interface is chosen those parameters would have to be monitored another way. The contractor shall investigate the suitability of a direct acting control and monitoring of the load bank. The contractor shall inform the government of the best solution. The contractor shall then implement the recommended solution. Comment by MCFARLAND, KENNADIE L CIV USAF AFMC 309 CMXG/MXDSR: We need to put what we are asking for. Comment by CARTER, REX M CIV USAF AFMC 309 CMXG/MXDEA: Don’t know how to tighten this up anymore, we are asking them to do some investigative work here, they have seen the SOW and didn’t have any comments on it. I tried to give as much information as I could so they know what they are getting into. Comment by MCFARLAND, KENNADIE L CIV USAF AFMC 309 CMXG/MXDSR: What are we asking them here? Is this additional to the quote we already have? Have they already done this? Comment by CARTER, REX M CIV USAF AFMC 309 CMXG/MXDEA: See above comment

3.2.7. Contractor shall add Direct Current (DC) amperage measurement capability for monitoring what the current the Unit Under Test (UUT) engine is drawing.

3.2.8. The contractor shall add the capability for an operator to type a message and have it displayed on the test cell monitor to communicate with someone in the test cell.

3.2.9. Display current configuration data:

3.2.9.1. The computer program identification number (CPIN) must be visible for operators and technicians. The ability to display the CPIN was added to our current version of ProTECS after the original installation. It is displayed on the About tab. The CPIN number field is populated from a config file. The contractor shall ensure the upgrade retains the ability to display the CPIN and populate it from a config file. The current implementation is acceptable. Comment by MCFARLAND, KENNADIE L CIV USAF AFMC 309 CMXG/MXDSR: Will the contractor know what this means? Comment by CARTER, REX M CIV USAF AFMC 309 CMXG/MXDEA: Yes, I am informing them here of a change that was made since the last baseline.

3.2.9.2. The Technical Order (TO) number for each UUT must be displayed to the operator. This could be accomplished by the same method as the CPIN or through the TPS message screens which is also acceptable. The contractor shall discuss the possible implementations with the government and implement the selected option. Comment by MCFARLAND, KENNADIE L CIV USAF AFMC 309 CMXG/MXDSR: What are we asking them here? Is this additional to the quote we already have? Have they already done this? Comment by CARTER, REX M CIV USAF AFMC 309 CMXG/MXDEA: Yeah, this is not a big deal, capability already exists, just asking them to consult with us on the method chosen.

3.2.10. The current version of the GTCP165 engine TPS monitors 4 EGT probes. The contractor shall add capability for the system to read an additional 4 EGT channels for a total of 8. The scope of this task is software only, hardware implementation is not required. Comment by MCFARLAND, KENNADIE L CIV USAF AFMC 309 CMXG/MXDSR: What does this stand for? Model number? Comment by CARTER, REX M CIV USAF AFMC 309 CMXG/MXDEA: It is a model number, will be very familiar to the contractor.

3.2.11. Current signal conditioning cards for measuring vibration are general purpose voltage cards, it is likely that special purpose vibration processing hardware could improve the performance of vibration signal processing. There are advantages to having all hardware on the Data Acquisition (DAQ) so upgrading computers is easier. The contractor shall investigate the best solution for vibration monitoring with an effort to host this function on the DAQ. The findings of this investigative effort shall be presented to the government, so an implementation method can be selected. The contractor shall implement the selected method. Additionally, the contractor shall retain all capabilities for vibration processing of the current systems. Comment by MCFARLAND, KENNADIE L CIV USAF AFMC 309 CMXG/MXDSR: What are we asking them here? Is this additional to the quote we already have? Have they already done this? Comment by CARTER, REX M CIV USAF AFMC 309 CMXG/MXDEA: Giving a little background in the first part of the paragraph to clarify what we are asking them to do and why, requirement is in 5th paragraph, the contractor shall… I have discussed this with the contractor, they are using this implementation in their more current systems.

3.2.12. The contractor shall review all signals read by the DAQ to ensure the hardware aligns well with sensor ranges, so calibration tolerances are easily met with suitable resolutions. Comment by MCFARLAND, KENNADIE L CIV USAF AFMC 309 CMXG/MXDSR: What are we telling them to do? When are they doing this? Comment by CARTER, REX M CIV USAF AFMC 309 CMXG/MXDEA: We are asking them to review all signals and make sure the hardware they are choosing is well suited for the application and not just replacing modules with like modules.

3.2.13. The GTCP165 engine employs a three-phase generator. It is a requirement to measure the voltage to ensure that all three phases are producing the same voltage within 10vac. It has been a challenge to make these measurements accurately through the system because of the interference of each phase on the other. These measurements are currently being accomplished with a hand help DMM. The Contractor shall incorporate a method to measure this phase-to-phase voltage accurately within the DAQ system. Comment by MCFARLAND, KENNADIE L CIV USAF AFMC 309 CMXG/MXDSR: What are we asking them here? Is this additional to the quote we already have? Have they already done this? Comment by CARTER, REX M CIV USAF AFMC 309 CMXG/MXDEA: We are asking the contractor to add capability for the specified voltage measurement so that it can be recorded through the data acquisition system instead of being done manually. This should be included in the quote we have.

3.2.14. The contractor shall provide a copy of the LabVIEW development suite of the same version used for the development of the software. (CDRL A001) This suite shall be licensed by a perpetual license and be transferable to the government. This software suite shall be installed on a computer that is identical to the ones used in the test cell. This computer will have the capability to be used as a development machine as well as a spare test cell computer. As such it should have all the software loaded to function in this capacity including ProTECS and any other needed software including any needed drivers. Comment by MCFARLAND, KENNADIE L CIV USAF AFMC 309 CMXG/MXDSR: CDRL 1

3.3. Program Management

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

3.3.2. Monthly Status Report. The contractor shall submit a monthly status report, due by the 5th of every month, which 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. (CDRL A002)

3.3.3. Conferences and Program Reviews Comment by GREEN, ALYSSA C CIV USAF AFMC 309 CMXG/MXDEA: I know we talk about Acceptance Testing and PCA in the documentation section, do we also need to talk about them in the requirements section? Only wondering since they are kind of conferences/reviews.

3.3.3.1. Kick Off Meeting. The kickoff meeting shall take place within 7 business days of the contract award. This can take place via telecom. Comment by MCFARLAND, KENNADIE L CIV USAF AFMC 309 CMXG/MXDSR: Can we combine these into one meeting? Comment by CARTER, REX M CIV USAF AFMC 309 CMXG/MXDEA: Well I would rather keep them separate, the kick off meeting is intended to discuss the format of and schedule the Post Award Conference. The Kick off is just intended to be a phone call. There is nothing magic about the 72 hours if you want to change that. Comment by MCFARLAND, KENNADIE L CIV USAF AFMC 309 CMXG/MXDSR: Changing to 7 business days Comment by CARTER, REX M CIV USAF AFMC 309 CMXG/MXDEA: That’s fine

3.3.3.2. Post Award Conference. The Government will convene a post-award conference with the contractor within 30 days after contract award. The Government will coordinate the actual date and time of the conference with the contractor. It is up to the discretion of the contractor if they want to make an onsite visit or participate by way of a telecom. The purpose of this conference will be to review the requirements of this SOW, CDRLs (to include DIDs), milestones and provide the opportunity to ask questions. This conference also allows the contractor to present possible design options. Comment by MCFARLAND, KENNADIE L CIV USAF AFMC 309 CMXG/MXDSR: What do you mean by this? Comment by CARTER, REX M CIV USAF AFMC 309 CMXG/MXDEA: This is in reference to some of the items in section 3.2 Corrections and Additions where we are tasking the contractor with coming up with a solution.

3.3.3.5. Technical Data Exchanges. Technical data exchanges may occur whenever needed by either party. These exchanges may be accomplished by way of DoD SAFE, email or CD/DVD depending on what is needed for file size and suitability.

3.4. Removal of Existing Equipment and Installation of New Equipment

3.4.1. Equipment Removal. The Contractor shall disassemble, remove, and palletize the existing equipment listed in Table 31. The palletized components shall be placed in a designated location within building 240. The contractor shall remove all unused equipment when replacing the existing equipment.

Table 31 Equipment to be removed

Data Acquisition units

Associated computers and monitors Comment by MCFARLAND, KENNADIE L CIV USAF AFMC 309 CMXG/MXDSR: Are these stand alone computers or are they connected to the NIPR? Comment by CARTER, REX M CIV USAF AFMC 309 CMXG/MXDEA: Stand alone

All applicable wire and cables

3.4.2. Equipment Installation. The Contractor shall install the equipment listed in the table below.

4 New Data Acquisition units

4 New Computers and monitors

All applicable wire and cable

3.4.3. Equipment Provided by Contractor.

Table 34 Equipment Provided by Contractor

4 New Data Acquisition Systems

4 Computer Systems including monitors

Associated cables and interfaces

1 Spare computer with monitors

3.4.4. Equipment Provided by Government.

Printers

The government will provide the OS and office software

3.4.5. Facility Modifications. The Contractor shall not make any facility structural modifications without prior written approval from the Government’s technical representative.

3.4.6. Tools and Equipment. The Contractor shall be responsible to furnish all tools required to remove existing equipment and install new equipment.

3.5. Training. The Contractor shall provide the trainings listed in Table 36.

Table 36

3.6. Information Assurance (IA). The following paragraphs layout the IA Management Plan.

3.6.1. IA Management. The contractor shall maintain appropriate IA management and incorporate tools into system software that provide DoD-approved malware protection/prevention and tracking in accordance with 115 AFI 33-115_YOKOTAABSUP dated 6 May 2015.

3.6.2. IA Program. The contractor shall maintain a robust information assurance program that is detailed in a written Contractor’s Information Assurance Plan. (CDRL A006) The contractor shall perform a virus scan prior to all shipments addressing most current virus scanning software. A signed and dated certification from the virus scanning official that this action has been taken shall be shipped with the asset.

3.6.3. IA Reporting/Tracking. The Contracting Officer (CO) shall be notified upon discovery of any virus or malware associated with the equipment being procured. Be aware that an IA reporting/tracking process is mandatory for subject procurement. Ensure the following:

3.6.3.1. Malicious Logic. In accordance with 115 AFI 33-115_YOKOTAABSUP dated 6 May 2015, the contractor and 309 CMXG/EN shall promptly report any incident meeting the requirements as defined in paragraph 5.4, Incidents Defined, to the USAF and cooperate with USAF investigations. Affected assets shall be immediately quarantined. The contractor shall notify the CO by telephone within 24 hours upon verification of a virus. The contractor shall not perform any remedial action of affected USAF equipment without direction from the CO.

3.6.3.2. Malicious Logic Protection. The contractor shall ensure incoming and outgoing non-volatile storage devices, via utilization of human and technological preventative measures such as good cyber hygiene and virus scanning, are free of malicious logic. (AFMAN 17-1301, 10 February 2017, pp 5.4)

3.6.3.3. Removable Media. The contractor shall ensure all removable media devices (hard drives, thumb drives, CDs, etc.) are free of malicious logic before and after use. (AFMAN 17-1301, pp 5.12)

3.7. Life Cycle Sustainment. The overall system design (e.g. components, hardware, software, etc.) shall be reliable, accessible, and maintainable and allow the Government to competitively select service providers for all future repairs without involving the original manufacturer of the system. Wherever possible, the contractor shall use components that are commercially available, commonly used in comparable industry equipment, interchangeable with other brands, and competitively priced. The system design shall not require the Government or a Government contractor to perform any reverse engineering to make system repairs.

4. DOCUMENTATION

The Contractor shall provide the following documentation:

4.1. Operation and Maintenance Manual for Test Stands. Operation and Maintenance manuals shall be delivered for operation, maintenance, and any needed setup for the system. A 33K series TO is currently used for calibration of the stands. It is not anticipated that a commercial manual for calibration will be needed, but if there are enough changes that one is warranted, they shall provide this or consult with the government to update the existing TO to accomplish calibration.

4.2. Engineering Data. The contractor shall update all applicable items in the Technical Data Package (TDP) to reflect changes to the system. 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, Master Bill of Materials (BOM) and parts list, schematics, wiring diagrams, assembly drawings, functional block diagrams and flowcharts, and equipment layout. The TDP shall provide the necessary design, engineering, manufacturing, testing and quality assurance requirements information necessary to enable the procurement and 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. For any third-party items procured for this effort, the contractor shall provide the OEM’s original nomenclature, key characteristics, and data sheets as part of the TDP. 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). (CDRL A007) Comment by MCFARLAND, KENNADIE L CIV USAF AFMC 309 CMXG/MXDSR: CDRL DI-SESS-81000F, Product Drawings/Models and Associated Lists)

4.5. Acceptance Test Plan and Report. The contractor shall provide an Acceptance Test Plan (ATP) that includes an Acceptance Test Report (ATR) provided in the contractor’s format in accordance with CDRL A004 and CDRL A005. This plan shall outline procedures for providing objective evidence that the new test equipment meets each requirement outlined in this purchase specification. This plan shall be provided to the Government representative 30 days in advance of the scheduled tests to allow opportunity for review and feedback. (CDRL A009) Comment by MCFARLAND, KENNADIE L CIV USAF AFMC 309 CMXG/MXDSR: CDRL Test Plan (CDRL A004, DI-NDTI-80566A, Test Plan) Test Report (CDRL A005, DI-NDTI-80809B, Test Report) Reference A-10 Nacelles

4.6. Physical Configuration Audit. The contractor shall conduct a Physical Configuration Audit jointly with the Government chairing the audit. The Physical Configuration Audit shall verify the drawings reflect the “as built” configuration of all developed or modified portions of the hardware. A product baseline shall be established upon completion of and Government acceptance of the Physical Configuration Audit Plan. A complete preliminary copy of the drawing package (section 4.2) shall be delivered 15 business days prior to the Physical Configuration Audit (CDRL A0010)

4.7. Computer Program Identification Number (CPIN). The contractor shall request a CPIN number and implement it in the executive software such that the CPIN number and revision are visible to an operator or calibration technician. The contractor shall provide two copies of the install disk for the executive software. Each disc (CD or DVD) shall be labeled with the following information: CPIN number, Revision, Date, Classification, Units (e.g. 1 of 1, 1 of 2, etc.) and the Title. (CDRL A011) Comment by MCFARLAND, KENNADIE L CIV USAF AFMC 309 CMXG/MXDSR: CDRL DI-MISC-81454C

5. DATA DELIVERABLES

The contractor shall provide a technical data package as stated in the table below.

Monthly Status Report

6. AVAILABLE FACILITY SERVICES. The following facility services will be made available to the Contractor. It shall be the responsibility of the Contractor to route new piping, cables, conduit, hangers, insulation, etc. from the existing facility connection points. If insufficient facility services are available, it shall be the responsibility of the Contractor to install and modify the facility after written approval from, and coordination with, the Government’s technical representative.

7. ACCESS TO FACILITIES AND PROPERTY. The contractor shall ensure the pass and identification items required for contract performance on Hill AFB are obtained for employees and non-Government owned vehicles. Contractor employees requiring escorted access will coordinate with the government. The contractor shall provide a list to the process engineer (PE) not less than 7 business days prior to the date access to the base is required.(CDRL A012) The list will be computer generated or typed and organized alphabetically by the visitor’s last name. The list will include last name, first name, driver’s license number, and state listed on license of all guests that will need access. Comment by MCFARLAND, KENNADIE L CIV USAF AFMC 309 CMXG/MXDSR: CDRL

8. SAFETY. While performing work under this contract on Government Installations, the Contractor shall comply with the specific health and safety requirements established by this contract. Comply with the health and safety rules of the Government installation that concern related activities not directly addressed in this contract. Take all reasonable steps and precautions to prevent accidents and preserve the health and safety of contractor and Government personnel performing or in any way coming in contact with the performance of this contract.

The contractor shall implement a safety program plan that ensures protection of Government personnel and property as defined in appendix B. (Attached) (CDRL A013) Comment by MCFARLAND, KENNADIE L CIV USAF AFMC 309 CMXG/MXDSR: CDRL In the event of an accident/mishap on a Government Installation, the Contractor shall take reasonable and prudent action to establish control of the accident/mishap scene, prevent further damage to persons or property, and preserve evidence. A written or email copy of the Mishap Report shall be sent within 48 hours to the PE, who will forward it to Ogden Air Logistics Complex (OO-ALC) safety office. (CDRL A007) The Contractor shall create an Incident/Mishap report in the event of any of the following:

· A condition or material fault that is a hazard to personnel, equipment, and missions.

· Conditions which prevent proper operation of the equipment.

· When equipment does not perform to published, operational or maintain standards.

· When a contract employee causes damage to equipment.

· When a contract employee is involved in an accident or injury.

9. DATA RIGHTS. The contractor shall provide at least Government Purpose Rights for all software used in the test stands as part of this contract as asserted in any Data Rights Assertion Table, or if none, as described in the Statement of Work or elsewhere in the contract. The delivery of data and software as described in the Technical Data Package (TDP) and deliverables (CDRLs) shall include, but are not limited to all software, source code, CAD files, CAD models, schematics, wiring diagrams, Gerber files, and equipment layout. The contractor shall comply with those contract clauses and definitions with respect to the government rights in technical data and software and CDRLs shall conform with DFARS 252.227-7013 and DFARS 252.227-7014, including any other applicable contact clause referenced or intended to be referenced in the contract. Comment by MCFARLAND, KENNADIE L CIV USAF AFMC 309 CMXG/MXDSR: Not sure if we can do this. Comment by CARTER, REX M CIV USAF AFMC 309 CMXG/MXDEA: Not delivery software before award. This is just saying any software they own and developed before this contract. This is kind of a general statement and may not really apply well to this particular contract but I think still makes sense because they may give us more rights for software created for this project.

10. WARRANTY.

10.1. Warranty period. The contractor shall provide a written warranty certificate for each individual test cell. The warranty period shall commence at the date of final acceptance for each test cell. The warranty shall consist of two parts.

10.1.1. A warranty for parts and systems is equal to the OEM warranty length and terms.

10.1.2. A warranty from the prime contractor should cover software functionality and troubleshooting support for a minimum length of 2 years.

10.2. Replacement of defective parts or software. During each respective warranty period, the contractor shall be responsible for the replacement of any defective parts, systems or software, the failure of which is due to faulty materials, workmanship, design or inadequate service life. Components normally consumed during this period, e.g. filters, shall be excluded from this requirement. The contractor is not expected to come on site to replace a part or make a repair that could easily be done by government personnel through off-site support.

10.3. Warranty certificate. The warranty certificate shall describe in detail the terms and timeline of the warranty, as well as outline the process of making warranty claims and contain at a minimum, the following information:

1. Part numbers/serial numbers of the new components of the test systems

1. Contract number

1. Warranty starts and end date

1. The contractor’s contact information

1. Explanation of warranty coverage

Appendix A. ACRONYMNS AND ABBREVIATIONS

SOW 1

image1.png