B08 SAM updated Solicitation Amendment 0006 30Aug2024.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. NAME AND TITLE OF SIGNER (Type or print)

30-105-04EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

STANDARD FORM 30 (Rev. 10-83) Prescribed by GSA

FAR (48 CFR) 53.243

Amendment 0006

This amendment update Section M by adding Q&A #94, w hich directs to a few edits in Section C.

1. CONTRACT ID CODE PAGE OF PAGES

S 1 38

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

16C. DATE SIGNED

BY 30-Aug-2024

16B. UNITED STATES OF AMERICA15C. DATE SIGNED15B. CONTRACTOR/OFFEROR

(Signature of Contracting Officer)(Signature of person authorized to sign)

8. NAME AND ADDRESS OF CONTRACTOR (No., Street , County, State and Zip Code) X W911QY24R0007

X 9B. DATED (SEE ITEM 11)

24-Jul-2024

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

X The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offer is extended, X is not extended.

Offer must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:

(a) By completing Items 8 and 15, and returning 1 copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN

REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE

CONTRACT ORDER NO. IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(B).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, is required to sign this document and return copies to the issuing office.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

10A. MOD. OF CONTRACT/ORDER NO.

2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO.(If applicable)

6. ISSUED BY

3. EFFECTIVE DATE

30-Aug-2024

CODE

W6QK ACC-APG NATICK DIVISION

1 GENERAL GREENE AVE

BLDG 1

NATICK MA 01760

W911QY 7. ADMINISTERED BY (If other than item 6)

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

W911QY24R0007

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION C - DESCRIPTIONS AND SPECIFICATIONS

The following have been modified:

STATEMENT OF WORK

The following attachments are incorporated herein with full force and effect as if it were included in the SOW, giving them the same preference in order of precedence as if they were in full text.

Section J Attachment 0001 Performance Purchase Description (PPD) for IECUs Section J Attachment 0002 Interface Standard for IECUs Section J Attachment 0003 Integrated Product Support SOW for IECUs

C.1 BACKGROUND

The U.S. Army's Environmental Control Units (ECUs) are required to comply with statutory restrictions dictating use of non-ozone-depleting refrigerants. Currently fielded military standard (“legacy”) ECUs use refrigerants prohibited in manufacturing of new equipment since 2010. Phase-out of ozone-depleting refrigerants occurred much earlier in some allied nations where the U.S. Army must continue to operate. Additionally, existing MIL-STD ECUs are increasingly unreliable due to age and/or are no longer supportable by the Army logistics system. Legacy ECUs do not meet domestic environmental law requirements or international agreements and require replacement with the new family of Improved Environmental Control Unit (IECU) which use non-ozone depleting refrigerants. IECUs also offer substantial benefits in terms of reduced weight, lower power consumption, and greater reliability.

C.2 GENERAL SCOPE

C.2.1 This contract is a hybrid, single award indefinite-delivery/indefinite-quantity (IDIQ) contract with firm-fixed-price (FFP), fixed price economic price adjustment (FP-EPA) and a small percentage of cost reimbursable CLINs.

C.2.2. The work to be performed by the contractor is detailed in this Statement of Work (SOW) and will be authorized by issuance of delivery orders. The contractor shall not initiate any work that is not authorized by a delivery order or modification without written direction by the Contracting Officer (KO). If the requirements of this SOW, Section J attachments, subsidiary specifications, standards, drawings, or publications are conflicting; the contractor shall refer the conflict, in writing, to the KO for resolution. The contractor shall furnish all personnel, labor, engineering, materials, supplies, logistics support, and facilities necessary to design, manufacture, and test the IECUs and provide all support in the form of hardware and software as well as all technical data products as indicated in this SOW.

C.2.3 Terms and Conventions: A list of acronyms is in contract Attachment 0004. The terms “Improved Environmental Control Units”; “ECU,”; “IECU,” and “air conditioner” may be used interchangeably in this contract.

All “days” specified in the contract are calendar days which include Saturdays, Sundays, and holidays unless specifically stated otherwise. If an item is due on any weekend day or federal holiday, the due date will be the next scheduled working day. The following terms shall be used to identify the four IECU variants:

Variant BTU/hr. Voltage Phase Hertz

IECU 9,000 115 1 50/60

18K-1 IECU 18,000 230 1 50/60

18K-3 IECU 18,000 208 3 50/60

36K IECU 36,000 208 3 50/60

The contractor shall design and build each IECU variant to meet the requirements contained in Section J, Attachment 0001 Performance Purchase Description (PPD) and Attachment 0002 Interface Standard (IS) MIL-STD- 1408D (2 Apr 2009). The Government has its own drawing package for previous iterations of each IECU variant.

The contractor may request access to the Government’s drawings for informational purposes only. The Government’s drawings are not part of the requirements of this contract, nor does the Government warrant its drawing package meets the PPD or IS. Rather the contractor shall meet the PPD and IS through its own design.

C.3. ORDERING SEQUENCE OF EVENTS

C.3.1 There are two (2) ordering periods in this contract, a five-year base ordering period with a five-year optional production ordering period.

C.3.2 The Government expects that each IECU variant will undergo their designs, builds, and tests of Production Verification Test (PVT) and First Article Test (FAT) units sometime during the ordering period. The PVT shall verify the contractor’s design for each variant meets the PPD and IS. Upon completion of production readiness reviews and successful PVT for a given IECU variant, the Government may approve proceeding to FAT and additional production units. The Integrated Product Support deliverables for each variant may also be ordered during the ordering period.

C.3.3 There is no specified ordering schedule, and the Government may award any CLIN, for any variant, and at any time. However, the Government expects to order from respective CLINs for each variant separately and in their order of priority. For example, the 18K-3 IECU variant is currently the highest priority. Therefore, the first delivery order would likely include CLINs for the 18K-3 unit, and the Government would subsequently order CLINs for other variants at other times during the contract PoP.

C.3.4 At the end of the five (5) year base period, the Government may exercise the five (5) year option to continue with production and any other option period CLINs.

C.4 PROGRAM MANAGEMENT

C.4.1 Program Manager: The contractor shall designate an individual as the contractor’s Program Manager (PM).

The PM shall be the primary Point of Contact (POC) between the Government and contractor and shall manage and coordinate all contractor activities related to the contract. The PM shall have the authority to commit the contractor to specific courses of action and accept direction from the Government KO. The PM shall coordinate all meetings between the Government and the contractor. The PM shall bring to the KO’s attention any conflicts in the contractor’s interpretation of the contract requirements (via email) or problems that could adversely affect the contractor’s ability to meet the stated quality, cost, or production/delivery schedule.

C.4.2 Monthly Status Report (MSR) and Integrated Master Schedule (IMS) (CDRL A033): The contractor shall provide MSR and monthly IMS per the CDRL. Up to four (4) separate sets of MSR/IMS monthly reports may be ordered, during both ordering periods. One set for each of the four (4) IECU variants. Individual delivery orders will specify for which IECU variants the monthly MSR/IMS reports are required.

C.4.2.1 IMS: The IMS shall be developed and submitted in Microsoft Project (MS Project). Unless otherwise specified, all verbiage specifying a number of days in this statement of work, contract attachments, and contact exhibits shall be construed as the number of calendar days. The IMS shall include detailed task/activity necessary for contract execution to include all contract deliverables, Government reviews/inspections/acceptance, events, meetings, milestones, and their discrete tasks/activities. A baseline schedule shall be established from contract award and progress shall be tracked against that baseline plan. The schedule shall show in detail the path the contractor will follow to meet the required delivery dates of all items awarded on the contract. The schedule shall track all tasks and include percentages complete. The contractor shall keep the IMS up to date and track program progress using the schedule. The contractor shall notify the Government of proposed changes to the baseline IMS that would change the baseline finish dates for contract deliverables and Contract Line-Item Numbers (CLINs). The monthly IMS updates shall include Baseline Start and Finish Dates for each task, in addition to updated Start and Finish dates.

Government concurrence with such changes is required. If the Government concurs on changes, the IMS shall be re-baselined. The IMS shall govern if a conflict exists between the IMS and submittal due dates in CDRL items or the delivery dates in Section F of delivery orders. The IMS shall contain the following additional features:

(a) Each task/activity shall be no longer than 44 workdays in duration with a threshold of no more than 5% of uncompleted activities in excess of 44 workdays. Tasks/activities exceeding 44 workdays shall instead be further broken down into tasks that do not exceed 44 workdays.

(b) Tasks/Activities shall be linked by a predecessor and successor. No greater than 5% of uncompleted activities will lack a predecessor and successor, with the exception of Level of Effort and Summary level activities.

(c) Each task/activity shall be unconstrained when applicable; no less than 95% of all activities shall possess As Soon As Possible relationship type and will allow for clear Critical Path identification and analysis.

(d) Task/Activity relationships shall be Finish to Start. No greater than 10% of alternate relationships such as Start to Start, Finish to Finish, or Start to Finish shall be utilized.

(e) There shall be 0 leads, 0 occurrences of negative lag, however a maximum of 5% of activities may utilize lag.

C.4.2.2 MSR: The monthly status reports shall clearly communicate to the Government the current status of the entire project, tasks accomplished in the previous month; tasks planned for the upcoming month; a risk assessment and identification of cost, schedule, and performance risks; results of meetings; and an issues and action items listing and status. The MSR shall contain either separate sections or separate appendices for each IECU variant. The MSR shall contain an appendix with a Technical Manual Status per Contract Attachment 0003, Integrated Product Support Statement of Work.

C.5 CONFIGURATION MANAGEMENT

C.5.1 Configuration Management: The contractor shall implement and maintain an internal configuration management program for the IECU throughout the life of the contract. EIA649, ‘National Consensus Standard for Configuration Management’, may be used as a guide for the contractor’s configuration management program.

Copies of this document may be purchased at http://www.sae.org/. The Contractor shall maintain configuration management of the Technical Data Package (TDP) and shall prepare Engineering Change Proposals (ECPs) and Notices of Revision (NORs) for any changes. The Government reserves the right to inspect and review the TDP and configuration management processes at any time during the contract. The contractor shall provide TDP and configuration control documentation for review at the Government’s request.

C.5.2 Configuration Baseline (CBL): The contractor shall control the Configuration Baseline (CBL) using the change control and engineering release processes. The CBL is the documentation describing all the IECU’s characteristics. The CBL shall include, but not be limited to, the Technical Data Package (TDP); test and verification reports; engineering drawings; sources of supply, parts lists; specifications; latest IECU technical publications (e.g.

Repair Parts and Special Tools List (RPSTL)); supporting process specifications; manufacturing and testing instructions; and computer software configuration items. All baselines shall be documented in a configuration status accounting database.

C.5.3 Configuration Control: The contractor shall use configuration control to manage all proposed changes after the configuration is baselined. Configuration control shall be used to document the impact of proposed changes and to update configuration documentation.

C.5.4 Configuration Control Documents: The contractor shall not initiate changes or departures from the CBL except for changes or departures that are submitted and accepted by the Government in accordance with (IAW) Configuration Control Documents (CCDs): Changes not caused by the Government shall be considered part of the contractor’s price for IECU production units and therefore CDRL A039 Configuration Control Documents, shall not be separately priced or separately paid by the Government for such changes. In the event of Government-caused changes, the cost of CCD deliverables (CDRL A039) shall be part of the pricing of delivery orders for Technical and Engineering Support as specified in Paragraph C12. CCDs include Engineering Change Proposals (ECP);

Notices of Revision (NOR); and Requests for Deviation (RFD). All configuration changes shall be documented by the contractor and be approved in writing by the Government prior to incorporation. In exigent circumstances, to allow for continuation of ongoing testing or production, the contracting officer may at its discretion provisionally approve on a temporary basis a CBL change. In this event, the contractor shall within seven (7) working days of any provisional CBL change submit a corresponding CCD. The Government, at its own discretion, may revoke any provisional CBL changes approved in this manner.

C.5.4.1 Engineering Change Proposal (ECP): Over the course of the contract, engineering changes may be required to address changes in parts, materials, manufacturing processes or future requirements. An Engineering Change Proposal (ECP) shall be prepared for all proposed changes. ECPs shall only be integrated into the system if approved by the Government. There shall be a separate ECP with attendant support for each change to be made. All supporting data reasonably required by the Government to modify the configuration baseline, including, but not limited to, calculations, test data, sketches, and layouts shall be provided. Each ECP shall be numbered consecutively by the contractor beginning with prefix letter E for ECP, followed by a three-digit number beginning with 001. Revisions to initial submissions of an ECP, submitted either to expand the supporting information or to override the initial submission shall carry the original ECP number, with sequential revision designators R1, R2, etc.

ECPs shall be prepared in contractor format, however, shall at a minimum, include the following:

a. Date Prepared

b. ECP Number

c. Justification and Priority Code

d. System Designation (i.e. Cage Code, nomenclature, model, P/N)

e. Name of Part (or Lowest Assembly) Affected

f. Baselines Affected

g. Title of Change

h. Description of Change

i. Need for Change

j. Documented changes (red line edits) on Interfaces (i.e. ILS deliverables, Interchangeability and Interoperability)

k. Total Costs/Savings

l. Retrofit Information (if applicable)

m. Data describing the change to include any changes or additions to the drawings and Engineering Data for Provisioning (EDFP).

n. Required testing performed and evaluation of the test results.

o. Required updates to all Integrated Product Support (IPS) data required by Contract Attachment 0003

p. Applicable updates to the contractor’s Quality Assurance Plan and Safety Assessment Report.

q. Other attachments as needed to facilitate the Government’s evaluation and acceptance of the change.

C.5.4.2 The contractor shall submit an NOR for each change that must be made to technical documentation following the approval of an ECP. The NOR shall be submitted with the ECP as "cloud" NOR redline drawings or signed and submitted electronically using the fillable PDF DD Form 1695 available from https://www.esd.whs.mil/.

C.5.4.3 The contractor shall submit a Request for Deviation RFD) that describes a requested departure from configuration documentation for a specific number of units or period. The contractor shall identify the impact of the RFD on performance, operational readiness, and logistics support of the affected CI. The RFD shall be signed and submitted electronically using the fillable PDF DD Form 1694 available from https://www.esd.whs.mil/.

C.6 MEETINGS AND REVIEWS

C.6.1 Meetings and Reviews: The contractor shall participate in and make presentations to the meetings and reviews listed below. Contractor shall ensure that all personnel and subcontractors required for an adequate discussion of the contract effort attend all meetings and reviews. Scheduling of the meetings and reviews shall not change the delivery schedule of the contract. All meetings and reviews required in this section may be held at either the contractor’s facility, a Government facility, via teleconference or by video teleconference.

C.6.1.1 Post Award Conference: The contractor shall coordinate, schedule, and conduct a Post Award Conference with the Government within thirty (30) calendar days of contract award. The purpose of the conference shall be discussion of project orientation, transfer of background information, to provide a mutual understanding of the technical requirements/ contractual requirements and the quality assurance provisions of the contract. The Government can address any questions or issues with regards to technical matters. The contractor shall describe to the Government the management of all aspects of the program. The contractor shall ensure that all personnel and subcontractors that are required for an adequate discussion of the contract effort are in attendance. Scheduling of the Post Award Conference shall not change the delivery schedule of the contract. The contractor shall be prepared to:

a. Conduct a review of the contract and delivery schedule requirements and ensure a mutual understanding between the Government and the contractor.

b. Conduct a virtual or in-person tour of all facilities associated with the contract effort.

c. Discuss other items as deemed necessary by the Contracting Officer.

C.6.1.2 In-Process Reviews: In-Process Reviews (IPR) shall be conducted as a part of program status monitoring and control. Technical publication, provisioning, training, technical/engineering, quality assurance, and other necessary IPRs shall be conducted to clarify requirements, assure conformance to contract requirements, provide guidance, review deliverable status, and to help ensure deliverables are prepared in a manner that will satisfy contractual requirements. The contractor may request an IPR when Government assistance or clarification is desired. The Government may require IPRs regardless of the program schedule and shall notify the contractor of a Government required IPR no later than five (5) calendar days prior to the event. Discrepancies and/or deficiencies identified as the result of an IPR shall be corrected by a date mutually agreed upon between the Government and the contractor.

The schedule for IPRs will be flexible and occur on an as needed basis and as program issues dictate.

C.6.1.3 Bi-weekly meetings: At least bi-weekly meetings shall be held. Some meetings may be cancelled or postponed at Government’s discretion. Meetings shall be conducted by Government and contractor personnel to address technical progress, cost, schedule, contractual, and other programmatic issues, or concerns. The updates shall include, but are not limited to, issues involving design, development, fabrication, testing, cost, funding, quality control, production, task tracking, and scheduling. Updates shall identify any programmatic problems that may have arisen and shall identify proposed solutions.

C.6.1.4 Integrated Product Support (IPS) meetings and conferences. The contractor shall participate and/or conduct the meetings and conferences for each variant as specified in Attachment 0003, Integrated Product Support Statement of Work

C.6.2 DESIGN REVIEWS

C.6.2.1 Design Review Meetings: When ordered, the contractor shall conduct a minimum of three (3) design reviews (Concept Design Review (CoDR), Preliminary Design Review (PDR), and Critical Design Review (CDR)) with the Government for each IECU variant. Additional reviews shall be scheduled as needed. The contractor shall propose design review dates that support the IMS for meeting delivery dates of the contract. Contractor shall ensure that all personnel and subcontractors required for an adequate discussion attend all reviews.

Concept Design Review (CoDR) (CDRL A002): Up to four (4) CoDRs may be ordered during this contract, one for each of the four (4) IECU variants. Individual delivery orders will specify for which IECU variants the CoDRs are required. The purpose of the CoDR is to: assess the feasibility of the contractor’s proposed design, review concept sketches and design details and perform a systems requirements review. The presentation, format, and content shall be sufficient to support the purpose of the concept review and IAW CDRL A002.

C.6.2.2 Preliminary Design Review (PDR) (CDRL A003): Up to four (4) PDRs may be ordered during this contract, one for each of the four (4) IECU variants. Individual delivery orders will specify for which IECU variants the PDRs are required. The purpose of the PDR is to ensure that the design and basic system architecture are sufficiently complete to demonstrate confidence that the performance requirements will be satisfied with all risks mitigated. At the time of the PDR, the contractor shall have identified at least the system functions and major component functions needed to meet the requirements of the PPD and have applied performance requirements to each function. The contractor shall also present details of its findings thus far on the effectiveness of component and subcomponent hardware and software items in meeting the functional and performance requirements. The presentation format and content shall be sufficient to support the purpose of the PDR and IAW CDRL A003.

C.6.2.3 Critical Design Review (CDR) (CDRL A004): Up to four (4) CDRs may be ordered during this contract, one for each of the four (4) IECU variants. Individual delivery orders will specify for which IECU variants the CDRs are required. The purpose of the CDR is to confirm that the system design is stable and is expected to meet system performance requirements, as evidenced by the detailed design documentation and drawings and specifications. The CDRL shall also establish the system’s initial configuration baseline. Government approval of CDR results is required before proceeding to PVT unit production. The presentation format and content shall be sufficient to support the purpose of the CDR and IAW CDRL A004.

C.7 SYSTEM SAFETY

C.7.1 System Safety Requirements: The contractor shall establish system safety processes and procedures to integrate hazard identification, assessment, and elimination or control into the product design and production effort required by this contract. Standards, specifications, regulations, design handbooks, safety design checklists, and other sources of design guidance shall be reviewed for pertinent safety design requirements applicable to the IECU.

The contractor shall incorporate safety design criteria for developing system specification safety requirements. The contractor shall comply with the System Safety Statement of Work in Section C.SS.

C.7.1.1 Safety Assessment Report (SAR) (CDRL A001): Up to four (4) SARs may be ordered during this contract, one for each of the four (4) IECU variants. Individual delivery orders will specify for which IECU variants the SARs are required. The contractor shall conduct a Safety Assessment of each IECU variant in accordance with MIL- STD-882E and CDRL A001. The SAR is a comprehensive evaluation of the safety risks to the operator, user, maintainer, and the equipment prior to test or operation of the system. The SAR shall identify, analyze and document all safety features of the system design and potential hazards that may be present and specific procedural controls that should be followed to prevent or minimize any hazard exposure.

C.7.1.2 Health Hazard Assessment Report (HHAR): An HHAR shall be delivered as an appendix or attachment to the SAR.

C.7.1.3 hazardous Material Management Plan (HMMP): The contractor shall prepare and deliver an HMMP as an appendix or attachment to the SAR.

C.8 SYSTEM SUPPORT PACKAGES

C.8.1 System Support Package Component Listing (SSPCL) (CDRL A040): Up to four (4) SSPCLs may be ordered during this contract, one for each of the four (4) IECU variants. Individual delivery orders will specify for which IECU variants the SSPCLs are required. The contractor shall provide a S S P C L IAW. CDRL A040 System Support Package Components Listing. The SSPCL shall be updated as needed through the completion of the events cited in C8.2 below and at no additional cost to the Government.

C.8.2 System Support Package (SSP): The contractor shall provide a SSP for each IECU variant. The SSP shall contain the type and quantity of support items to sustain the IECU through Production Verification Test, First Article Test, Technical Manual (TM) Validation, Maintenance Evaluation, and TM Verification. The SSP shall contain items including, but not limited to, spare parts, expendable and durable items, special tools, mandatory replacement parts, refrigerant. and bulk items. The SSP shall be replenished and updated as needed until the completion of the aforementioned events and at no additional cost to the Government.

C.9 PRODUCTION VERIFICATION TEST (PVT)

C.9.1 PVT Units: The contractor shall deliver PVT Units for each IECU variant. PVT units shall meet the requirements contained in Section J, Attachment 0001 Performance Purchase Description (PPD)) and Attachment

0002 Interface Standard (IS) MIL-STD-1408D (2 Apr 2009).

C.9.2 Contractor Test Authorization: The contractor is authorized to receive DoD test rates at a Major Range Test Facility Base (MRTFB) for PVT.

C.9.3 PVT Plan (CDRL A034): Up to four (4) PVT Plans may be ordered during this contract, one for each of the four (4) IECU variants. Individual delivery orders will specify for which IECU variants the PVT Plans are required.

The PVT Plan shall include, but is not limited to: System description, schedule and test sequence, test objectives, test witnesses, test criterion, test procedures, test equipment/tools/facilities, test photos, pass/fail criteria, planned technical analysis, data to be processed, raw data to be collected, data collection format. Evidence that planned test facilities, equipment, and personnel are qualified for their assigned verifications shall be provided in the plan. Each requirement/verification outlined in the performance purchase description shall be addressed in the plan. The plan shall also include any tests or verifications required by the Design Review Information Packages (DRIP). The plan shall specify the PPD and DRIP-required verifications to which each PVT unit will be subjected. The plan shall be submitted and approved by the Government prior to the start of testing.

C.9.4 PVT Readiness Review: A PVT readiness review shall be held for each IECU variant. Testing shall not begin without the Government’s approval of test readiness. Prior to the PVT Readiness Review, the contractor shall conduct the Quality Conformance (QC) tests specified in Table III of section 4 of the PPD on all PVT units.

Successful QC tests shall be a precursor to both test readiness and the Government's acceptance of the PVT units.

The contractor shall conduct a Readiness Review no later than fourteen (14) calendar days prior to the planned start of PVT. The PVT Readiness Review shall present results of the PVT unit and support package manufacture, the results of conformance QC testing, SOW requirements, demonstration that safety has been adequately addressed, review of PVT Plan, test resources to be utilized, test coordination efforts, and methods used to reduce risk to an acceptable level. The exact date, location, and administrative arrangements for this meeting shall be made between the contractor and the Government. The presentation format and content shall be sufficient to support the purpose of the review and CDRL requirement.

C.9.5 Production Verification Testing: The contractor shall conduct all the verifications specified for PVT in Section 4 of the PPD on each IECU variant. The contractor shall also conduct any testing or inspections required by the Design Review Information Packages. Unless specified otherwise in the PPD, not all verifications required by Section 4 of the PPD need to be accomplished on multiple PVT Units of the same variant during PVT. The contractor may utilize multiple PVT units of the same variant as needed to complete all verifications within the required schedule. Facilities, equipment, and personnel used for PVT shall be qualified for their assigned verifications. If Government facilities are utilized, the contractor shall train Government personnel and/or soldiers how to set up, operate, and maintain the IECU to the extent required of the Government. The contractor shall provide reimbursement directly to the Government testing activity (e.g., Aberdeen Test Center) for all direct and indirect costs incurred related to the test conduct. Throughout PVT conduct, the contractor shall provide to the Government immediate access to test related information, including the test plans, test schedule, test results, and each Test Incident Report (TIR). The Government shall have the right to attend any portion of, or all the PVT. In addition to conducting PVT, the contractor shall provide continuous support including, but not limited to, training Government test personnel (if used), addressing TIRs, and performing any required maintenance and repairs during testing. The contractor shall include the Contracting Officer’s Representative (COR) in all contractor communications with Government test and certification agencies. The Government intends to conduct its Maintainability Evaluation (ME) by using one of the PVT units. ME requirements are contained in Attachment 0003, Integrated Product Support Statement of Work. The Government will provide its ME Report to the contractor as an input for the Post-PVT Production Readiness Review.

C.9.6 PVT failures and deficiencies: When a test failure occurs, the contractor shall determine the cause and corrective action needed. Retest requirements shall be determined by the Government through consideration of the nature and extent of the failure and the risk to the program. The contractor shall address all TIRs, and deficiencies identified during PVT and refurbish hardware at no cost to the Government if required for retest or for a subsequently scheduled test or evaluation. During testing, if the PVT Systems require repair to resume and successfully pass testing, the contractor shall repair or refurbish the units to support the continuation of testing at no cost to the Government.

Failures or deficiencies not caused by the contractor’s design or manufacture may still require repair by the contractor, but those such repairs will be optional and priced at the time of requirement.

C.9.7 PVT Report (CDRL A005): Up to four (4) PVT Reports may be ordered during this contract, one for each of the four (4) IECU variants. Individual delivery orders will specify for which IECU variants the PVT Reports are required. The contractor shall prepare and submit a PVT Report for each IECU variant. The PVT report shall include, but is not limited to system description, Table of contents, list of figures and tables, test verifications, test photos, pass/fail results, processed data, test results, raw data and signatures. Every requirement/verification outlined in the performance purchase description and the approved PVT plan shall be addressed.

C.9.8 Post-PVT Production Readiness Review (PRR): The contractor shall not proceed to further IECU production of a given IECU variant without written approval from the Government. A successful completion of PVT, acceptable resolution of all outstanding design issues, and a successful PRR is needed for approval to proceed with additional production units of a given variant. The contractor shall present the variant’s PVT results, resolution of design and test issues from both the ME and PVT, Technical Data Package (TDP), and Quality Assurance plan. The presentation format and content shall be sufficient to support the purpose of the PRR.

C.10 FIRST ARTICLE TEST (FAT)

C.10.1 First Article Test (FAT) Units: The contractor shall deliver FAT units for each IECU variant. FAT units shall meet the requirements contained in Section J, Attachment 0001, Performance Purchase Description (PPD) and Attachment 0002, Interface Standard (IS) MIL-STD-1408D (2 Apr 2009). The FAT units shall also incorporate any changes necessitated by the PVT phase. The First Article units shall be completely representative of production units including, but not limited to, design, manufacturing processes, sources of supply, and quality assurance processes. Prior to delivery of the First Article Units to the Government, the contractor shall, at no extra cost to the Government, replace or repair to original condition of any units or subcomponents that sustained any damage or were otherwise non-compliant during FAT. Normal wear and tear resulting from the testing shall be acceptable;

however, damage resulting from material deficiencies or inadequate design must be corrected on the FAT unit by the contractor at their own expense. Changes to FAT units resulting from material deficiencies or inadequate design shall be incorporated into the design through the ECP process to include updating the FAT units and proving out all requisite design fixes/modifications.

C.10.2 Contractor Test Authorization: The contractor is authorized to receive DoD test rates at a Major Range Test Facility Base (MRTFB).

C.10.3 First Article Test (FAT) Plan (CDRL A035): Up to four (4) FAT Plans may be ordered during this contract, one for each of the four (4) IECU variants. Individual delivery orders will specify for which IECU variants the FAT Plans are required. The FAT Plan shall include, but is not limited to: System description, schedule and test sequence, test objectives, test witnesses, test criterion, test procedures, test equipment/tools/facilities, test photos, pass/fail criteria, planned technical analysis, data to be processed, raw data to be collected, data collection format. Evidence that planned test facilities, equipment, and personnel are qualified for their assigned verifications shall be provided in the plan. Each requirement/verification outlined in the performance purchase description shall be addressed in the plan along with any other tests or inspections required by Post-PVT Production Readiness Review (PRR).

The plan shall specify the PPD and the PRR-required verifications to which each FAT unit will be subjected.

The plan shall be submitted and approved by the Government prior to the start of FAT.

C.10.4 First Article Test Readiness Review: A First Article Test (FAT) readiness review shall be held for each IECU variant. Testing shall not begin without the Government’s approval of test readiness. Prior to the FAT Readiness Review, the contractor shall conduct the Quality Conformance (QC) tests specified in Table III in Section 4 of the PPD on all FAT Units. Successful QC tests shall be a precursor to both test readiness and the Government's acceptance of the FAT units. The contractor shall conduct a Readiness Review no later than fourteen (14) calendar days prior to the planned start of FAT. The FAT Readiness Review shall include, but is not limited to, results of the FAT unit and support package manufacture, the results of conformance QC testing, SOW requirements, demonstration that safety has been adequately addressed, review of FAT Plan, test resources to be utilized, test coordination efforts, and methods used to reduce risk to an acceptable level. The exact date, location, and administrative arrangements for this meeting shall be made between the contractor and the Government. The presentation format and content will be of the contractor’s choosing but must be sufficient to support the purpose of the review.

C.10.5 First Article Test: The contractor shall conduct all the verifications specified for FAT in Section 4 of the PPD on each IECU variant and any other tests or inspections required by the Post-PVT Production Readiness Review (PRR). Unless specified otherwise in the PPD, not all verifications required by Section 4 of the PPD need to be accomplished on multiple FAT Units of the same variant during FAT. The contractor may utilize multiple FAT units of the same variant as needed to complete all verifications within the required schedule. Facilities, equipment, and personnel used for PVT shall be qualified for their assigned verifications. If Government facilities are utilized, the contractor shall train Government personnel and/or soldiers how to set up, operate, and maintain IECU to the extent required of the Government. The contractor shall provide reimbursement directly to the Government testing activity (e.g., Aberdeen Test Center) for all direct and indirect costs incurred related to the testing. Throughout FAT conduct, the contractor shall provide to the Government immediate access to test related information including the test plans, test schedule, test results, and each Test Incident Report (TIR). The Government shall have the right to attend any portion or all the FAT. In addition to conducting FAT, the contractor shall provide continuous support including, but not limited to, training Government test personnel (if used), addressing TIRs, and performing any required maintenance and repairs during testing. The contractor shall include the Contracting Officer’s Representative (COR) in all contractor communications with Government test and certification agencies.

C.10.6 First Article Test (FAT) failures and deficiencies: When a test failure occurs, the contractor shall determine the cause and corrective action needed. Retest requirements shall be determined by the Government through consideration of the nature and extent of the failure and the risk to the program. The contractor shall address all TIRs, and deficiencies identified during FAT and refurbish hardware at no cost to the Government if required for retest or a subsequently scheduled test. During testing, if the FAT Systems require repair to resume and successfully pass testing, the contractor shall repair or refurbish the units to support the continuation of testing at no cost to the Government. Failures or deficiencies not caused by the contractor’s design or manufacture may still require repair by the contractor. But those such repairs will be optional and priced at the time of requirement.

C.10.7 First Article Test Report (CDRL A006): Up to four (4) FAT Reports may be ordered during this contract, one for each of the four (4) IECU variants. Individual delivery orders will specify for which IECU variants the FAT Reports are required. The contractor shall prepare and submit a FAT Report for each IECU variant in accordance with the CDRLs. The FAT report shall include, but is not limited to system description, Table of contents, list of figures and tables, test verifications, test photos, pass/fail results, processed data, test results, raw data and signatures. Every requirement/verification outlined in the performance purchase description and the approved FAT plan shall be addressed.

C.10.8 Physical Configuration Audits (PCA): The contractor shall conduct PCAs for each IECU. The PCAs shall be conducted in accordance with Attachment 0003, the Integrated Product Support (IPS) Statement of Work (SOW).

C.10.9 Post- First Article Test Production Readiness Reviews (PRR): The contractor shall not proceed to further IECU production of a given IECU variant without written approval from the Government. A successful completion of FAT, acceptable resolution of all outstanding design issues, and a successful post-FAT PRR is needed for approval to proceed with additional production units of a given variant. The contractor shall present the variant’s FAT results, resolution of design and test issues, PCA results, updated Technical Data Package (TDP), and updated Quality Assurance plan. The presentation format and content shall be sufficient to support the purpose of the PRR.

C.11 PRODUCTION

C.11.1 IECU Production Units: The contractor shall provide IECU production units for each IECU variant in accordance with the requirements set forth herein and in accordance with Attachment 0001 PPD and Attachment 0002 IS Interface Standard MIL-STD-1408D 2APR2009.

The Government will not inspect/accept production units until after acceptance of FAT and after corrective actions for FAT issues are implemented in production. Paint color shall be specified in delivery orders.

C.11.2 Production Units’ Acceptance Test and Inspection: The contractor shall subject production units to a production test and inspection prior to Government acceptance of the units. Each IECU of each production lot shall be subjected to the test and inspection unless a smaller sample size is approved by the Government and based on evidence that a smaller sample size is warranted. Conversely, the sample size shall be increased when evidence indicates an increase is necessary or immediately after ECPs or other types of changes prompt a change in sample size. The acceptance test and inspection shall include all examinations and tests in the QC column in Table III of the PPD and all other inspections and tests required by the Production Test And Inspection Plan of C11.3 below

C.11.3 Production Acceptance Test and Inspection Plans and Production Acceptance Test and Inspection Reports:

The contractor shall prepare and deliver the test and inspection plan as a stand-alone appendix in the Contractor’s Quality Assurance Plans (CDRL A037). The plan shall be updated as required by the CDRL. If variants’ test and inspection requirements differ from each other, the plan shall have separate sections for each variant. The plan shall include the inspections and tests required to substantiate product conformance to drawings and contract requirements; and the inspections and tests needed to verify resolution of PVT and FAT incidents. Test and inspection procedures shall include applicable test reference, required equipment to perform the test/inspection, location of the test/inspection, step by step instructions and checklists; data to be recorded, and pass/fail criteria.

The contractor shall deliver a Production Acceptance Test and Inspection Report for each production unit, by serial number, or production lot sample in accordance with CDRL A038. CDRL A038 shall not be separately priced or paid by the Government. Costs for the reports shall be part of the contractor’s pricing for IECU production units (e.g. CLINs 0030-0033 and Option period CLINs 2005-2008).

C.11.4 Standard Repair Procedures: The contractor shall take measures to ensure damage does not occur to an IECU during manufacturing, material handling activities, and storage. If there are any damages to an IECU, the contractor shall propose a repair procedure to the KO and the IECU COR. The proposed repair procedure shall be agreed upon by the Government and executed by the contractor.

C.11.5 Spare and Repair Parts: When ordered, the contractor shall furnish spare and repair parts from the Provisioning Parts Lists (PPL) and the TDP. As needs arise, the Government may request proposals from the contractor to furnish, package and deliver the required spare and repair parts. The Government will review each proposal and issue delivery orders on a case-by-case basis. The requirements will be defined at the delivery order level and awarded based on the level of effort, required parts, and the labor rates contained in the contractor’s Price Proposal. Spare parts delivery orders for cables shall utilize the cable pricing provided in the contractor’s Price Proposal under Attachment 0005 Spare Parts Pricing. Cables shall comply with Contract attachment 0010 Cable Assembly Drawings.

C.12 CONTRACTOR TECHNICAL AND ENGINEERING SUPPORT: When specified in a delivery order, the contractor shall perform engineering and technical tasks to address issues including, but not limited to, parts obsolescence; design and developing Government-requested ECPs; developing solutions for Foreign Military Sales (FMS); developing solutions for Pre-Planned Product Improvements (See C.18). The engineering requirements will be defined at the delivery order level and awarded based on the level of effort and the awarded labor rates. As needs arise, the Government may request proposals from the contractor to provide the required support. The Government will review each proposal and issue delivery orders on a case- by-case basis. Configuration Control Documents (CDRL A039) shall be furnished as required by delivery orders for technical and engineering support.

C.13 CONTRACTOR LOGISTICS SUPPORT: The Contractor Logistics Support are separate requirements from the work specified by Contract Attachment 0003, Integrated Product Support Statement of Work. When specified in a delivery order, the contractor shall provide logistics support for the production and fielding phase of the program.

As needs arise, the Government may request proposals from the contractor to provide the required support. The logistics support requirements will be defined at the delivery order level and awarded based on the level of effort and the awarded labor rates.

The Government will review each proposal and issue delivery orders on a case-by-case basis. Logistical support may include but is not limited to fielding support; conducting training, non-warranty repairs; performing Care of Supplies in Storage (COSIS) checks; maintenance and repairs; refurbishing damaged IECUs; troubleshooting; and root cause analyses. The contractor shall perform Logistics Support activities in the Continental United States (CONUS), and if required, Outside CONUS (OCONUS). The contractor shall, when required, provide logistics support for delivery orders related to FMS.

C.14 SHIPPING:

C.14.1 General: The contractor shall provide all shipping for PVT and FAT units and supporting hardware required for completion of PVT, FAT, and the Maintenance Evaluation (ME). When testing is complete, the contractor shall provide shipping and bear the costs thereof to return test units and all test related hardware to the contractor’s facility. The cost for shipping PVT and FAT Units for testing and ME shall be part of the contractor’s pricing for conducting PVT and FAT tests. Shipping costs incidental to manufacturing shall be incorporated into the contractor’s prices for PVT Units, FAT Units and Production Units.

C.14.2 Use of Shipping shall apply to contract related shipping not covered by C.14.1 above. For example, this CLIN applies to shipping Government-accepted IECU production units to their first destination. The Government expects to obligate funds the shipping CLIN, for a Not to Exceed dollar amount commensurate with the quantity of units ordered. The Government will request the required shipments from the contractor as needs arise.