W56HZV18R0096-0003.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT 1. Contract ID Code Page Of

2. Amendment/Modification No.

3. Effective Date

4. Requisition/Purchase Req No.

5. Project No. (If applicable)

6. Issued By Code 7. Administered By (If other than Item 6) Code

8. Name And Address Of Contractor (No., Street, City, County, State and Zip Code)

9A. Amendment Of Solicitation No.

9B. Dated (See Item 11)

10A. Modification Of Contract/Order No.

10B. Dated (See Item 13) Code Facility Code

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

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

Offers 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 ____________ copies of the amendments: (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 ONLY APPLIES TO MODIFICATIONS OF CONTRACTS/ORDERS

It Modifies The Contract/Order No. As Described In Item 14.

A. This Change Order is Issued Pursuant To: 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 data, 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.)

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)

16A. Name And Title Of Contracting Officer (Type or print)

15B. Contractor/Offeror 15C. Date Signed 16B. United States Of America 16C. Date Signed

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

NSN 7540-01-152-8070

PREVIOUS EDITIONS UNUSABLE

30-105-02 STANDARD FORM 30 (REV. 10-83)

Prescribed by GSA FAR (48 CFR) 53.243

SEE SCHEDULE

X

Firm Fixed Price

0003 2018NOV08

W56HZV

U.S. ARMY CONTRACTING COMMAND

WARREN, MICHIGAN 48397-5000

STEPHEN PEEPLES

EMAIL: STEPHEN.J.PEEPLES2.CIV@MAIL.MIL

W56HZV-18-R-0096

2018SEP24

X

X 2018NOV19 03:00pm

/SIGNED/

2 signed

SEE SECOND PAGE FOR DESCRIPTION

1 35

CONTINUATION SHEET

Reference No. of Document Being Continued Page of

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

SECTION A - SUPPLEMENTAL INFORMATION

Buyer Name: STEPHEN PEEPLES

Buyer Office Symbol/Telephone Number: CCTA-HCS-B/(586)282-6949

Type of Contract 1: Firm Fixed Price

Kind of Contract: System Acquisition Contracts

*** End of Narrative A0000 ***

1. The purpose of this Amendment 0003 to solicitation W56HZV-18-R-0096 is to clarify language, correct typographical errors, and update the Request for Waiver of First Artile Testing Requirement.

2. As a result of Amendment 0003, the following changes are hereby made to the RFP:

Section C:

The numbering of Section C.7.4.3.5.4.3.1 is corrected to reflect C.7.4.2.5.4.3.1.

Section D:

Section D.1.1 - IAW C.7.4.7 is deleted in reference to the attachments, special purpose kits, initial packages and BII requirements for

MFS-TRM units being stored at contractor facilities.

Section F:

Section F.1.3 - language is modified to include Preventative Maintenance Checks and Services (PMCS) requirement.

Section F.1.5 - referenced in Section D is deleted regarding TRM shipment and storage instructions.

Section J:

Attachment 0021 - Request for Waiver of First Article Testing Requirement:

(a) Language at subpart (i) is updated to clarify Options 2 and 3.

(b) Contractor certification language is modified.

Section M:

(a) Section M.4.2.4 - transportation costs reference corrected to reflect Section E.7.

(b) Section M.4.2.1 - Total Evaluated Price reference corrected to reflect Section M.4.2.2.

(c) Section M.2 - Rejection of Offers subpart (e) reference corrected to reflect Section M.4.2.5.

3. The contractor response deadline is extended to 19 November 2018 3:00pm local time; Warren, Michigan.

4. Except as provided herein, all other terms and conditions remain unchanged.

*** END OF NARRATIVE A0008 ***

2 35

W56HZV-18-R-0096

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

SECTION C - DESCRIPTION/SPECIFICATIONS/WORK STATEMENT

Table of contents:

1. GENERAL

2. MEETINGS/CONFERENCES/REVIEWS

3. SYSTEM REQUIREMENTS AND CHARACTERISTICS

4. CONFIGURATION MANAGEMENT (CM)

5. FIRST ARTICLE TEST (FAT)

6. PRODUCTION

7. INTEGRATED PRODUCT SUPPORT (IPS) MANAGEMENT

8. SECURITY

C.1 GENERAL

C.1.1 The contractor, as an independent contractor and not as an agent of the Government, shall provide the supplies and services required by this Statement of Work (SOW), as required by Delivery Orders and Task Orders issued by the Procurement Contracting Officer

(PCO) under this contract.

C.1.2 The Modular Fuel System (MFS)-Tank Rack Module (TRM) is a Palletized Load System (PLS) and Heavy Expanded Mobility Tactical Truck

Load Handling System (HEMTT-LHS) compatible petroleum storage and distribution system. The MFS-TRM is capable of receiving, storing, filtering, and issuing kerosene based fuels (i.e. Jet Propellant (JP) JP-5, JP-8, Jet-A, Jet-A1) and diesel fuel. The MFS-TRM is an ISO-compatible system that can be rapidly emplaced, operated, maintained, and recovered. Individual TRMs, having a 2,500-gallon minimum capacity (unless previously waived by the Government), will be used for bulk and retail distribution missions.

C.1.3 Applicable documentation: Exhibit A, Contract Data Requirements List (CDRL A001-A051), contains references to government Data

Item Descriptions and other documents. These documents are available at: https://assist.dla.mil/online/start/ . This web site provides an on-line registration process by which contractors may obtain a password.

C.1.4 Specifications and Standards:

To the extent that this statement of work references industry and government standards and specifications, such standards and specifications are incorporated by reference.

C.2 MEETINGS/CONFERENCES/REVIEWS

C.2.1 General Meeting Requirements: The Contractor is required to conduct meetings and reviews during the contract performance period as set forth below. The contractor shall provide an agenda prior to each meeting IAW CDRL A001 and take minutes of all the meetings IAW

CDRL A002.

C.2.2 Start of Work Meeting: The contractor shall host a Start of Work Meeting (SOWM) at its facility within thirty (30) days after issuance of first delivery order. This meeting will focus on contract terms and conditions, a review of all data requirements, required specifications, program schedule, test requirements and relevant logistics requirements to assure a complete understanding of the requirements. The meeting will also include break out meetings to support all logistic support functions. Contractor attendees shall include contract administration personnel, management, engineers, and logistics personnel.

C.2.2.1 In this meeting, the Contractor shall present detailed paths or milestone graphic presentations that defines Contractor performance necessary to meet contract requirements and contract delivery requirements as defined in the Scope of Work. The briefing shall include a full review of the contract and associated sections. The Contractor shall provide to the Government an internal list of all functional Contractor personnel involved in this contract. This list shall be updated as required to maintain accuracy. Break out meetings shall be held for the following logistic support areas: Provisioning Guidance, Publications Guidance, New Equipment Training, Maintenance Planning, Testing and Reliability, and Safety.The Contractor shall request the sequence of the government directed serial numbers from the COR at start of work meeting.

C.2.3. Contract Status Reviews: The Contractor shall host quarterly meetings, at the contractors facility, to review contract status.

These reviews shall be for one eight-hour day. Topics to be discussed shall consist of contract status, testing, production, logistics engineering, and deliverables and the government may add additional topics prior to each meeting.

C.2.4 Integrated Product Team (IPT) Meetings: The contractor shall support bi-weekly IPT meetings to discuss program issues, SOW clarifications and contract issues.

C.2.5 Internet-Based Collaboration

C.2.5.1 Collaboration tools. The following Internet-based collaboration tools shall be used to facilitate information sharing and collaboration within a secure Government server environment that provides controlled, distributed access to MFS-TRM program information.

3 35

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

The Government will host all Internet-based collaboration environments.

C.2.5.1.1 Details on specific collaboration tools, requirements for access, and approach for use will be discussed at the Start of Work

Meeting (SOWM). The Government will sponsor Army Knowledge Online (AKO) and VISION Digital Library System (VDLS) accounts. The

Government can only sponsor accounts for U.S. Citizens. The Contractor shall provide names, contact information, level of access (upload or download), and training required for personnel requiring access to these tools at the SOWM meeting (for all systems except VDLS).

C.2.5.1.2 In order to access these systems, the Contractor shall obtain External Certification Authority (ECA) Certificates and DoD

Common Access Cards (CAC) for appropriate personnel. The contractor shall designate an IA Officer to work with the Government IA Manager in order to obtain and implement usage of the ECA or CAC program in compliance with DoD Directive 8190.3 Smart Card Technology, and DoD

Instruction 8520.2, Public Key Infrastructure (PKI) and Public Key (PK) Enabling.

C.3 SYSTEM REQUIREMENTS AND CHARACTERISTICS

C.3.1 Hardware: The Contractor shall develop, test and deliver MFS-TRM hardware systems that meet the performance requirements of the product description ATPD 2336E (Attachment 0001).

C.3.2 Basic Issue Items (BII): The contractor shall include a set of BII composed of items required for operation or operator maintenance for each MFS-TRM. The BII must be stowed and integrated with each MFS-TRM system. BII stowage must meet all packing requirements and must be weathertight to effectively withstand all usual and unusual weather and terrain conditions without rapid deterioration.

C.3.3 Components of End Item (COEI): The Contractor shall include a set of COEI for each MFS-TRM. COEI are items required for operation, operator and crew maintenance. COEI includes minimum essential items required to enable an assemblage or system (referred to as the End

Item) to perform its intended operational functions. COEI are items required to be with each End Item, and is defined as various parts and equipment which are required for End Item to be "complete" and must accompany an End Item when it is issued, transferred between property accounts, retrograded, or evacuated. COEI also includes any items identified as On-board Spares (OBS.). COEI stowage must meet all packing requirements.

C.3.4 Authorized Stockage List (ASL): The contractor shall include separately packaged Government approved ASL to the locations provided in the Government Shipping Instructions.

C.4 CONFIGURATION MANAGEMENT (CM)

C.4.1 CM: The contractor shall establish a CM program for configuration management and control of the MFS-TRM IAW; Electronic Industries

Alliance (EIA) -649 and EIA-649-1. Configuration control methods and procedures shall be implemented that maintain the integrity, traceability, and history of the established production baseline. Documentation shall be maintained for all changes made to the production baseline, including all affected part numbers, assembly numbers, and equipment serial numbers.

C.4.1.1 The Contractor shall notify the Government of any changes to its established CM process, as well as any changes to its facilities that will impact the established CM process. The Contractor shall document all elements of its configuration management program in a CM Plan. The Government shall have the right to review the contractor's CM plan at any time.

C.4.2 Engineering Changes - Contractor Initiated:

C.4.2.1 Engineering Change Proposals (ECPs) submitted by the Contractor shall be prepared and delivered IAW CDRL A003. Any Engineering

Change Proposal (ECP) that impacts packaging shall include a packaging impact statement and assessments for items requiring special handling, storage or condemnation, HAZMAT, shelf life, and transportability problem items. Any ECP that impacts safety shall be accompanied with an updated SAR.

C.4.2.2 Value Engineering Change Proposal (VECP):

The contractor shall prepare VECPs in the same manner as Class I ECPs (CDRL A003).

C.4.2.3 Requests for Variation (RFV):

The contractor shall submit RFVs from the current approved production baseline IAW CDRL A004, authorized variations are a temporary departure from the requirements and do not constitute a permanent change to the approved production baseline.

C.4.2.4 Notice of Revision:

The contractor shall generate and submit Notices of Revision (NOR) concurrently with Engineering Change Proposals (ECPs) when associated technical documentation requires change. NORs shall be prepared IAW CDRL A005.

C.4.2.5 Government Review

The Government may require the Contractor to perform additional tests to verify acceptability of any contractor-initiated change. The

Government will determine the extent of required testing, up to and including a complete PVT, for that change.

4 35

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

C.4.3. Responsibility for Data Revision:

The Contractor shall submit, at no cost to the Government within 45 business days of making any contractor-initiated configuration change, revisions to all affected contractual data deliverables.

C.4.4 Responsibility for the Cost of Changes (Excluding VECPs): The responsibility for the cost of changes is as follows:

C.4.4.1 The Government is not responsible for additional testing or software costs associated with any Contractor initiated configuration change. The Contractor shall perform such tests at no additional cost to the Government.

C.4.4.2 When a change results in reduced Contractor costs, the Government may, at the sole discretion of the Contracting Officer, require an equitable downward adjustment to the contract price.

C.4.4.3 The Government is not liable for any costs the Contractor may incur, due to delay in contract performance, as a result of a

Contractor request for change. Further, any production or delivery delays caused by additional Government-required testing and inspection will not be the basis for an excusable delay as defined in the default clause of this contract. Such delays shall not form the basis for adjustment in contract price or delivery schedule.

C.4.5 Engineering Changes - Government Initiated:

In the event the Government desires a change to the end item configuration, the Contracting Officer will request, in writing, a technical or price proposal from the contractor.

C.4.6 Configuration Status Accounting:

The contractor shall establish and maintain a Configuration Status Accounting (CSA) program that allows the configuration of the MFS-TRM system to be tracked. The CSA program shall provide serialized hardware identification that provides a clear audit trail back to documented changes, cut-in points, and other configuration-related technical documentation. A record of all configuration changes shall be maintained, whether or not the change affects form, fit, or function. CSA data shall be available for Government inspection any time during contract performance. CSA data shall be formatted and delivered IAW CDRL A006, Configuration Status Accounting.

C.4.7 Physical Configuration Audit:

C.4.7.1 A Physical Configuration Audit (PCA) shall be performed by the contractor and witnessed by the Government to verify that the production MFS-TRM systems drawings and other applicable technical and logistical documents, are fully defined and reflect the "as-designed, as-built" system previously accepted by the Government. The PCA shall also confirm that all changes or corrections resulting from Government testing have been implemented, and verify that accurate form, fit, function, and interface information is provided in the commercial off-the-shelf (COTS) items. The contractor shall provide a PCA audit plan IAW CDRL A007 and conduct the PCA at his or her facility, or sub-contractor's facility.

C.4.7.2 The PCA shall be conducted incrementally, concurrent with the fabrication and assembly of MFS-TRM sub-systems, and final assembly of a MFS-TRM unit. The Contractor's plan that provides the sub-system or MFS-TRM to be audited, facilities, personnel, documentation (including technical, and the supporting LPD), and other support as may be required, shall be provided to the Government on request. The Contractor shall document the results of each audit, including all discrepancies found, in the Configuration Audit

Report. In the event the Government or Contractor finds evidence that the technical or logistical documents do not adequately represent the material, production shall cease until all discrepancies are corrected, subject to Government review and approval, and, written permission is granted by the Government to resume production. The PCA report shall be formatted and delivered IAW CDRL A008. The

Contractor shall incorporate changes or corrections to the models, drawings and associated technical data resulting from the PCA, into the MFS-TRM.

C.5: First Article Test (FAT)

C.5.1 Production Verification Testing (PVT): If the contractor MFS-TRM system design has previously successfully completed a Government

FAT and the production line has not been dormant for 2 or more years, then the contractor shall complete PVT.

C.5.1.1 PVT shall be accomplished at the contractor's facility and consist of the following:

a) Accomplishment of the contractor's AI&T plan previously approved by the USG.

b) Physical Configuration Audit (PCA).

C.5.1.2 The contractor shall provide two TRM systems for the PVT.

C.5.1.3 AI&T inspection shall be verified 100% the by the contractor and USG.

C.5.1.4 The contractor shall perform a PCA with USG oversight IAW section C.4.7

5 35

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

C.5.2 Product Qualification Test (PQT)

C.5.2.1 PQT shall consist of Government FAT and PCA.

C.5.2.1.1 If the contractor MFS-TRM system design has previously successfully completed a Government FAT and the production line has been dormant for 2 or more years. The contractors system shall be tested IAW attachment 0004 Abbreviated FAT, and the contractor shall support testing events.

C.5.2.2 The Contractor shall conduct a Test Readiness Review (TRR), at the contractor's facility, for the purpose of demonstrating to the Government that the MFS-TRM is ready for FAT. The TRR shall occur 60 days after start of work meeting. The TRR shall conclude with a functional walk-through and demonstration of an MFS-TRM production representative unit. The demonstration shall provide an overview of the physical, functional, and operational characteristics of the MFS-TRM.

C.5.2.2.1 The contractor shall deliver an agenda for the TRR IAW CDRL A009 and a TRR report IAW CDRL A031

C.5.2.3 The contractor shall provide four MFS-TRMs, no later than 120 days after contract award for Government FAT testing. The testing shall be accomplished at Yuma Testing Center, Arizona.

C.5.2.4 The Contractor shall deliver System Support Packages (SSP) to support Government FAT. The contractor shall provide the SSP with a component list IAW A016 to the government test site 30 days NLT the start date of the Government FAT. The contents of each SSP shall include all parts and tools necessary to repair or replace components damage during FAT within 4 hours.

C.5.2.4.1 The Contractor shall provide at least one Field Support Representative (FSR) that is a Subject Matter Experts (SMEs) on the

MFS-TRM at the test site during testing of the MFS-TRM. The FSR shall provide operational and maintenance support of the MFS-TRM, conduct 100% of pre and post inspection and inventory of the MFS-TRM with the USG test team present.

C.5.2.4.1.1 The FSR shall participate in meetings pertaining to testing, and maintain daily log of all support provided.

C.5.2.4.1.2 The FSR shall perform an operational walk-through and demonstration of the MFS-TRM prior to the test to ensure that all parts of the MFS-TRM are functional

C.5.2.4.1.3 The FSR shall identify and correct any equipment failures that occur during testing. The FSR shall analyze test data, conduct failure analysis, and maintain a data tracking system throughout all test efforts. After completion of the effort, the contractor shall provide services including labor sufficient to prepare the MFS-TRMs for shipment.

C.5.2.4.1.4 The FSR shall coordinate with the appropriate YPG personnel to secure test site access.

C.5.2.4.1.5 De-processing: The FSR shall perform on-site preparation of equipment at the test sites, including operator and maintainer

Preventive Maintenance Checks & Services (PMCS). Upon completion of de-processing, the MFS-TRM shall be 100% fully mission capable.

C.5.2.4.2 Failure Analysis and Corrective Action Reporting System (FACARS):

The contractor shall be responsible for accessing the Army Test Incident Reporting System (ATIRS) database to obtain the Test Incident

Reports (TIRs) generated on the equipment during FAT. Information on access to ATIRS, and points of contact at ATC are available on the web at: http:// vision.atc.army.mil. The contractor's date of receipt of the TIR shall be defined as the day the TIR is posted to the database. Upon receipt of a TIR, the contractor shall assess the failure, and shall furnish a response IAW CDRL A010 FACARS, with the proposed corrective action to prevent or minimize the probability of incident recurrence. The proposed corrective action shall be submitted to the FACARS review board for approval and the contractor shall input the approved corrective action report to the ATIR database. Following the completion of FAT, the contractor shall submit a final FACAR report IAW CDRL A011.

C.5.2.4.2.3 The Contractor shall use VISION Digital Library System (VDLS) to access Test Incident Reports (TIRs), and unclassified data from Government testing. A list of Contractor personnel requiring VDLS access shall be provided to the Government (60) days prior to the

FAT.

C.5.2.5 Reliability and Maintainability (R&M) Scoring and Assessment Conference:

C.5.2.5.1 The contractor shall support Government Scoring and Assessment Conferences by briefing members about engineering changes and modifications made to the MFS-TRM as a result of failures. A minimum of two Government Scoring and Assessment Conferences shall be held, one midway through FAT and one after completion of FAT. Government Scoring and Assessment Conference will be conducted at Government test locations.

C.5.2.5.2 The contractor shall request USG approval for corrective actions before implementing the corrective action.

C.5.2.5.3 The contractor shall perform a PCA with USG oversignt IAW C.4.7 within 60 days after FAT approval.

C.5.3 Full FAT

6 35

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

C.5.3.1 If the contractor MFS-TRM system design has never successfully completed a Government FAT, then the contractors system shall be tested IAW attachment 0003 and the contractor shall support testing events.

C.5.3.2 The contractor shall complete and support PVT during Government FAT in accordance with Attachment 0003 for full FAT.

C.5.3.3 The Contractor shall conduct a TRR, at the contractor's facility, for the purpose of demonstrating to the Government that the

MFS-TRM is ready for FAT. The TRR shall occur 90 days after contract award. The TRR shall conclude with a functional walk-through and demonstration of an actual MFS-TRM production unit. The demonstration shall provide an overview of the physical, functional, and operational characteristics of the MFS-TRM.

C.5.3.3.1 The contractor shall deliver an agenda for the TRR IAW CDRL A009, and a TRR report IAW CDRL A031.

C.5.3.4 The contractor shall provide 6 MFS-TRMs, no later than 120 days after contract award for Government FAT testing. The testing shall be accomplished at Yuma Testing Center, Arizona.

C.5.3.5 The Contractor shall deliver System Support Packages (SSP) to support Government FAT testing. The contractor shall deliver the

SSP with a component list IAW A016 to the government test site 30 days prior to the Government FAT. The contents of each SSP shall include all parts and tools necessary to repair or replace components damage during FAT within 4 hours.

C.5.3.5.1 The Contractor shall provide at least one Field Support Representative (FSR) that is a Subject Matter Experts (SMEs) on the

MFS- TRM at the test site during testing of the MFS-TRM. The FSR shall provide operational and maintenance support of the MFS-TRM, providing repair parts, conduct 100% pre and post inspection and inventory of the MFS-TRM with the test team present.

C.5.3.5.2 The FSR shall participate in meetings pertaining to testing, and maintain daily log of all support provided. All cost for additional contractor service support during retest due to failure or disapproval of test shall be borne by the contractor.

C.5.3.5.3 The FSR shall perform an operational walk-through and demonstration of the MFS-TRM prior to the test to ensure that all parts of the MFS-TRM are functional

C.5.3.5.4 The FSR shall identify and correct any equipment failures that occur during testing. The FSR shall analyze test data, conduct failure analysis, and maintain a data tracking system throughout all test efforts. After completion of the effort, the contractor shall provide services including labor sufficient to prepare the MFS-TRMs for shipment.

C.5.3.5.5 The FSR shall coordinate with the appropriate YPG personnel to secure test site access.

C.5.3.5.6 De-processing: The FSR shall perform on-site preparation of equipment at the test sites, including operator and maintainer

Preventive Maintenance Checks & Services (PMCS). Upon completion of de-processing, the MFS-TRM shall be 100% fully mission capable.

C.5.3.6 Failure Analysis and Corrective Action Reporting System (FACARS): The contractor shall be responsible for accessing the Army

Test Incident Reporting System (ATIRS) database to obtain the Test Incident Reports (TIRs) generated on the equipment during FAT.

Information on access to ATIRS, and points of contact at ATC are available on the web at: http:// vision.atc.army.mil. The contractor's date of receipt of the TIR shall be defined as the day the TIR is posted to the database. Upon receipt of a TIR, the contractor shall assess the failure, and shall furnish a response IAW CDRL A010 FACARS, with the proposed corrective action to prevent or minimize the probability of incident recurrence. The proposed corrective action shall be submitted to the FACARS review board for approval and the contractor shall input the approved corrective action report to the ATIR database. Following the completion of FAT, the contractor shall submit a final FACAR report IAW CDRL A011.

C.5.3.6.1 The Contractor shall use VISION Digital Library System (VDLS) to access Test Incident Reports (TIRs), and unclassified data from Government testing. A list of Contractor personnel requiring VDLS access shall be provided to the Government (60) days prior to the

FAT.

C.5.3.7 Reliability and Maintainability (R&M) Scoring and Assessment Conference:

C.5.3.7.1 The contractor shall support Government Scoring and Conferences by briefing members about engineering changes and modifications made to the MFS-TRM as a result of failures. A minimum of two Government Scoring and Assessment Conferences shall be held, one midway through FAT and one after completion of FAT. Government Scoring and Assessment Conference will be conducted at Government test locations.

C.5.3.7.2 The contractor shall request USG approval for corrective actions before implementing the corrective action.

C.5.3.7.3 The contractor 60 days after FAT approval shall perform a PCA with USG oversight IAW section C.4.7

C.5.3.8 Human Factors Engineering Analysis (HFEA). For HFE requirements not specifically defined in the ATPD, the Contractor shall use the design standards contained in MIL-STD-1472 and MIL-STD-1474 for application of human factors engineering practices during the design

7 35

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

of the MFS-TRM and applicable components. The Contractor shall perform and deliver a HFEA IAW CDRL A047, Human Factors Engineering

Analysis". The information used to create this CDRL shall be available to the Government and discussed at SIPT meetings as well as major reviews IAW the Government provided IMP.

C.5.3.9 Safety Engineering and Health Hazard

C.5.3.9.1 Safety Engineering System Safety Program. The contractor shall establish and implement a System Safety Program to identify, assess, and manage safety, health and environmental hazards IAW MIL-STD-882E; to ensure the safety-related requirements specified in

ATPD 2336E for the MFS-TRM are met.

C.5.3.9.2 System Safety Program Plan. The contractor shall develop, implement and maintain a System Safety Program Plan (SSPP) IAW MIL-

STD-882E Task 102, details of the software system safety program shall be included within the SSPP. The program shall entail a planned approach to the performance of safety tasks. The SSPP shall be developed in accordance with CDRL A048 (System Safety Program Plan).

CFE with limited data must be assessed by the contractor for system integration, the SSPP shall document the contractor's process for its integration into the system.

C.5.3.9.3 Hazard Tracking System (HTS). The contractor shall develop and maintain a process to identify, document and track

Environmental, Safety, and Occupational Health (ESOH) hazards until they are eliminated or the associated risk is reduced to a level acceptable to the Government. The contractor shall identify ESOH hazards associated with the system to include any modifications as described in C.4. The HTS shall contain the fields identified in MIL-STD-882 Task 106 for each potential or actual ESOH hazard of the system and when the hazard may be expected to occur under both usual and unusual operating and maintenance conditions. The contractor shall categorize the risk before and after mitigation in accordance with MIL-STD-882. The contractor shall identify if the hazard is hardware, software or environmental related. Mitigation actions include redesign, recommended engineering controls, safety features or devices, warning devices and procedures and training. Hazards to be identified in the HTS include, but are not limited to: sharp edges/moving parts hazards, physical hazards (e.g. extreme temperatures, acoustical energy, ionizing and non-ionizing radiation), chemical hazards (e.g. flammables, corrosives, carcinogens), toxic fumes (exhaust emissions), electrical hazards, whole-body vibration, compliance issues with regulatory organizations, generation of hazardous wastes, air, water, and soil pollution hazards, biological hazards, fire prevention issues, and ergonomic hazards. The HTS shall be delivered as part of the SAR (CDRL A049).

C.5.3.9.4 Safety Assessment Report (SAR). The contractor shall develop and maintain a SAR for the system in accordance with MIL-STD-882E

Task 301 CDRL A049. The SAR shall include the results of a Software System Safety Assessment (SSSA). The SSSA shall be executed IAW MIL-

STD-882E terms, definitions and risk matrices, unless tailored alternative matrices are formally approved in accordance with DOD

Component policy, to assess the Software contribution to system risk. Additional guidance on how to conduct required SSSAs are provided in the Joint Software System Safety Engineering Handbook and Software System Safety Implementation Process and Tasks Supporting MIL-STD-

882E. The SAR shall address safety impacts to maintenance, operation, installation, and removal. Safety Data Sheets (SDS) shall be included in each assessment. As an appendix to the SAR, the contractor shall identify and incorporate health hazards associated with each action. The contractor shall provide a description and discussion of each potential or actual health hazard of concern for each subsystem/component/item/etc. The SAR, including the health hazards, shall identify all known safety and health features of the hardware, firmware, software, system design, and inherent hazards and shall establish operational and maintenance procedures and precautions to be observed by Government test agencies and system users.

C.5.3.9.4.1 The following are examples of some areas of concern that may contain safety and health hazards, (the list in not all inclusive: a) automotive issues (i.e., stability, braking, and handling), b) fire protection issues, c) toxic fumes (i.e., engine exhaust, weapons firing), d) noise levels (i.e., steady-state, drive-by, impulse), e) electrical issues, f) weapons characteristics

(i.e., blast overpressure, misfire procedures, hangfire procedures, cook off, breech or barrel life, safety mechanisms, weapon/vehicle integration), g) ammunition storage, h) autoloader performance (for MGS as applicable), i) operators devices and procedures to ensure safe operation, and j) analyses and tests conducted, with quantities involved, to demonstrate safety.

C.5.3.9.5 Functional Hazard Analysis (FHA). The contractor shall conduct a Functional Hazard analysis (FHA) IAW MIL-STD-882E Task 208 to assess all the system and subsystem functions (safety and non-safety) to determine the criticality of hardware, firmware, and software components. The FHA shall identify failure conditions of each function (loss of function, malfunction, or degraded function), identify the effects of that failure condition, and identify the severity of the effects. The FHAs shall also identify the Software

Criticality Indices (SwCI) associated with each function and each Computer Software Configuration Item (CSCI) and each Computer Software

Unit (CSU) and each Package, software contributions to the system level hazards, and safety-critical software requirements to mitigate the identified hazards. The contractor shall document the results of the FHA in the Hazards Report (contractor hazard log) of the SAR

CDRL A049. The contractor shall provide the Government access to their hazard log and make available any hazard log related documentation for inspection upon request.

C.5.3.9.6 Software System Safety (SSS)

C.5.3.9.6.1 The contractor shall conduct a Software System Safety Program IAW MIL-STD-882E, the Joint Software System Safety Engineering

Handbook, and the Software System Safety Implementation Process and Tasks Supporting MIL-STD 882E. The Contractor shall include SSS as an integral part of the system safety program. Contractor software technical specialists, to include system safety and SSS specialists, shall support the software system safety effort during the development of the SSS Assessment and shall participate in System Safety

Working Group. The plan for all SSS activities and Level of Rigor (LOR) tasks shall be included in the System Safety Program Plan

8 35

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

(SSPP) (CDRL A048). Results, evidence, and residual safety risk from SSS shall be included in the SAR (CDRL A049).

C.5.3.9.6.2 Non-developmental item (NDI), commercial-off-the-shelf (COTS), Re-use, and Government furnished Software contribution to system risk. The contractor shall conduct a complete SSS assessment to define, evaluate and test the safety-significant functionality associated with the integration of the NDI, COTS, re-used, and Government furnished (GF) software and firmware. The SSS assessment shall list both safety-critical and safety-related functions that the proposed COTS, GF and reuse application will perform, list of safety requirements to be included in the specifications and level of rigor required. The contractor shall employ techniques to reduce the risk of NDI, COTS, GF, and reuse software and firmware in safety-significant applications. Results, evidence, and residual safety risk from

NDI, COTS, GF, and reuse software and firmware shall be included in the SAR (CDRL A049).

C.5.3.9.6.3 Software System Safety (SSS) Testing. The contractor shall provide software test evidence that the software does not pose an unacceptable or undesirable risk. The contractor shall conduct safety-specific testing and provide the results in the SAR (CDRL A049) to verify that the design and implementation of the software mitigates all of the identified software related hazards. Level of Rigor

(LOR) activities shall be conducted to ensure that the software will perform as specified in software requirements, while reducing the number of contributors to hazards that may exist. The plan for LOR tasks shall be included in the SSPP (CDRL A048). Evidence of test

LOR task completion shall be included in the Software Test Plan and Description/Report. If the software design does not provide evidence as defined by the LOR activities that it meets safety requirements, IAW MIL-STD-882E, an assessment must be conducted to determine the risk associated with inadequately verified and satisfied LOR activities.

C.5.3.10 Environmental Compliance. The Contractor shall ensure that all aspects of contract execution are in compliance with applicable

International, United States Federal, State, and Local environmental regulations and requirements; including activities associated with design, prototype build, test, storage, and disposal. The Contractor shall immediately notify the Contracting Officer if the Government gives any direction that may result in violation of law or regulation.

C.5.3.11 Hazardous Materials Management.

For the purposes of this contract, hazardous materials shall be defined by FED-STD-313. A Radioactive material is defined as any source material, as defined by Title 10, Code of Federal Regulations, Part 40, "Domestic Licensing of Source Material", in excess of 0.05 percent by weight. Specific prohibited hazardous materials for the MFS are identified SECTION 3.3.4 of the MFS Purchase Description

(Attachment 0001). Hazardous materials restrictions shall apply to all components, parts, and materials provided under this contract, including items purchased through a subcontractor or supplier, COTS components, OEM parts, and manufactured parts.

C.5.3.11.1 Exceptions to the Hazardous Materials Requirements.

Waivers from the hazardous materials requirements shall not be permissible except where a suitable alternative does not exist. The

Contractor shall provide a list of anticipated waiver requests no later than the SOWM. The Contractor shall submit waiver requests to the COR no later than the SOWM using the, Request for Use of Prohibited Materials (Attachment 0006). Waiver requests shall include detailed technical justification for the use of prohibited hazardous materials. The Contractor shall not deliver any items containing prohibited materials without the Government approval of the waiver request.

C.5.3.11.2 Hazardous Materials Management Report (HMMR).

The Contractor shall prepare an Hazardous Materials Management Report (HMMR) IAW National Aerospace Standard (NAS) 411 REV 2 (dated

April 29, 1994), section 4.4. (Exception to NAS 411 REV 2 Section 4.4.1: In addition to those hazardous materials delivered on the system and required for operation and maintenance, the HMMR shall identify: all hazardous materials used in final system manufacture and assembly, specifying the process(es) utilizing the materials; any hazardous materials created by the system; and any anticipated hazardous wastes created during operation and maintenance of the system.) The HMMR shall specify which phase (manufacture, operation, and Sustainment) that each material is required for or created in.

For the life of the contract, the Contractor shall discuss status, changes or issues with the HMMR as part of the technical reviews ESOH

WG meetings. (CDRL A050, HMMR).

C.5.4 Refurbishment: The Government will request individual proposals from the contractor to refurbish system(s) used during FAT or that have sustained other damages. Refurbishment shall be completed within ninety (90) days after receiving Government authorization to do

so. Refurbishment includes complete cleaning and touch-up repainting of the systems, repair and replacement of any worn or damaged parts to bring the units to a 10/20 condition IAW AR750-1. Parts removed from refurbished systems shall be disposed of by the contractor IAW local, state, and federal regulations at no additional cost to the Government.

C.6 PRODUCTION

Full Rate Production (FRP) shall not begin until the requirements in section C.5 are successfully completed and a signed delivery order is granted by the PCO.

C.6.1 TRM Serialized Tracking

The following data shall be part of the serialized Information, and required USG approval.

a. Serial Number (sequence will be provided by the USG)

b. System Designation or Model Number

c. Contract Number

9 35

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

d. Contractor

e. Date of Manufacturing

C.6.2 Welding Requirements

C.6.2.1 The contractor shall ensure that the all welds shall be free from defects indicative of poor workmanship or material. All welding shall be IAW the American Welding Society (AWS) welding codes. The TRM tank shall be constructed IAW American Society of

Mechanical Engineers (ASME) BPVC Sec. VIII, Div. 1 and Sec. IX.

C.6.2.2 Welding Procedures: Prior to production or repair welding operations the contractor is responsible for developing and preparing fusion and or resistance welding procedures. Resistance welding procedures shall be prepared and validated as recommended by the ASME and the AWS.

C.6.2.3 Alternate Welding Standards: The contractor may request from the PCO to utilize alternate standards or codes once the contractor have demonstrated that equivalent or better finish quality and performance can be obtained by its use. The contractor shall demonstrate such equivalence to the USG prior to fabrication of any production weldment. If the contractor cannot release the specific or proprietary information, the Government reserves the right to conduct an on-site review of the contractors quality system and weld processes to verify its capability of producing acceptable welds. The Government reserves the right to approve or disapprove the use of any and all such alternative weld standards and specifications.

C.6.2.4 Previously Qualified Procedures: The contractor may request to use previously qualified welding procedures under another

Department of Defense (DOD) contract, which the contractor qualified procedures that produced acceptable workmanship specimens, the contractor may use previously qualified weld procedures provided all the following requirements are met:

a. The weld procedure was qualified and approved on a previous DOD contract

b. The contractor has certified welders and equipment

c. There was no break in production for more than three months

d. No outstanding welding Product Quality Deficiency Reports

C.6.2.5 Welder Qualification: The contractor shall ensure that any welder or welding operator performing manual, semi-automatic welds shall have passed qualification testing, . The contractor shall ensure that all welding equipment used in the performance of this contract has been certified.

C.6.2.6 Visual Weld Inspection: The contractor shall verify weld quality and workmanship to AWS weld inspection and is performed using qualified inspectors trained to perform these inspection functions. Acceptable qualification of the contractor inspectors may be based on:

a. Current or previous certification as an AWS Certified Welding Inspector; or

b. Current or previous certification by the Canadian Welding Bureau (CWB); or

c. Inspection performed by an engineer or technician who is competent in the use of weld inspection techniques and equipment, on the basis of formal training or experience, or both, in metals fabrication, inspection, and testing.

C.6.3 Chemical Agent Resistant Coating (CARC)

C.6.3.1 The contractor shall perform CARC painting IAW TACOM CARC Paint drawing 1285018 (MIL-DTL-53072F) (Attachment 0005). Paint color shall be Tan 686A, Number 33446 meeting FED-STD-585 and AR 750-1.

C.6.3.2 The contractor shall use a commercial high heat paint or paint meeting MIL-B-14105 (in lieu of CARC) for surfaces exceeding 400 degrees F. Adhesion testing shall be performed on a completely cured or painted finish. In addition, external compartments shall have the interiors completely cleaned and painted as necessary.

C.6.3.3 Surfaces not requiring paint; Fabrics, plastics, rubber, working parts of machinery, lubrication fittings and other surfaces not normally painted shall not be painted unless required by the specification for the end item. Such surfaces shall be masked or protected during treatment and painting to prevent damage to them.

C.6.3.4 The contractor shall ensure that CARC paint touch up or the application of CARC topcoat to an existing CARC topcoat shall be IAW

MIL-DTL-53072F. The procedure to be followed depends upon the type and condition of the existing finish. Items previously coated with alkyds, lacquers or vinyl must be stripped down to the epoxy primer if present, or to the substrate if an epoxy primer is not present.

For rework, polyurethane and epoxy topcoats can only be applied over previously painted epoxy or polyurethane topcoats.

C.6.4 Acceptance Inspection and Test Plan: The contractor shall develop the AI&T Plan and submit, electronically, for approval by the procuring contracting officer (PCO), IAW CDRL A012 AI&T. once approved; major changes to the AI&T shall be approved by the procuring activities Product Quality Manager (PQM). Minor changes may be approved at the PQMs discretion, by the Government QAR.

10 35

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

C.7 INTEGRATED PRODUCT SUPPORT (IPS) MANAGEMENT.

The Contractor shall plan, manage, and execute an IPS Program for the MFS-TRM program.

C.7.1 IPS Program Information

1) The Contractor shall conduct a IPS program that:

a. Ensures that the supportability characteristics for the MFS-TRM, signified through the System Support Package (SSP), represent the USG accepted/approved production system.

b. Ensures the SSP represents section C of the contract, which is proven through testing, the Logistics Demonstration (Log

Demo), provisioning, and verification activities.

c. Ensures the SSP is updated and validated for the MFS program ensuring any changes resulting from testing or ECPs are incorporated into the Logistics Product Data (LPD) to support initial fielding and the future sustainability of the MFS-TRM.

d. Ensure the logistics efforts are on schedule according to the contract and outlined in an IPS Integrated Master Schedule

(IMS).

2) The Contractor's IPS program shall focus on the development of a validated SSP that maintains currency with the MFS-TRM product configuration identification and serves as the baseline to be verified using the USG accepted/approved production system.

3) The Contractor shall maintain facility MFS-TRM systems to ensure they are available and in the proper configuration and condition to support, the logistics and testing activities required for its use under this contract.

C.7.1.2 The Contractor shall develop, implement, perform, update, and manage the SSP and Logistics Support Analysis (LSA) IAW section C of this contract.

C.7.1.3 IPS Program Management. The Contractor shall establish and maintain the management processes and controls to ensure the MFS-TRM

IPS program. The contractor shall establish a Supportability IPT (SIPT) to support the MFS-TRM IPS program.

C.7.1.4 IPS Management Plan. The Contractor shall present its plan for managing and executing the IPS program IAW CDRL A014. The plan shall describe the Contractor's organization, lines of communication, schedule of activities, with associated resources, and management controls.

C.7.1.5 IPS Integrated Master Schedule (IMS). The Contractor shall develop and maintain an IPS IMS to manage the MFS-TRM IPS program through completion of this contract. The IPS master schedule shall reflect the details of section C in this contract. The Contractor shall present the IPS IMS at each SIPT meeting and incorporate any SIPT approved changes into the MFS-TRM IPS IMS IAW CDRL A015.

C.7.1.6 Supportability IPT (SIPT). The Contractor shall support SIPT meetings to enhance communication between the Contractor and the

Government. The Contractor's IPS manager shall serve as vice chairperson of the SIPT. For planning purposes, the SIPT meetings shall be conducted in accordance with key IPS program events, or at a minimum, on a quarterly basis.

C.7.1.7 Supportability IPT Support. The Contractor shall conduct SIPT meeting and address agenda issues, topics and schedules IAW CDRL

A001 and record meeting minutes IAW with CDRL A002. The action items shall be assigned prior to the close of the…