W56HZV-16-R-0210_0001_v3.pdf

PDF 131 KB Posted

Attached to
Light Engineer Utility Trailer (LEUT) Type II
Solicitation number
W56HZV-16-R-0210
Issued by

About this file

W56HZV-16-R-0210 0001

View the file

Other files

File Type Posted
Attachment_0029,_Superseding_Revisions_to_ATPD-2414B.PDF PDF
W56HZV16R0210-0004.pdf PDF
W56HZV16R0210-0003.pdf PDF
Attachment_0010_LEUT_PRICING_MATRIX_V15.xlsx XLSX spreadsheet
LEUT_Type_II_RFP_W56HV-16-R-0210_Questions_Set_3,_Question_30.xlsx XLSX spreadsheet
LEUT_Type_II_RFP_W56HV-16-R-0210_Questions_Set_2_(13-32_minus_30).pdf PDF
Attachment_0029,_Superseding_Revisions_to_ATPD-2414B.PDF PDF
W56HZV16R0210-0002.pdf PDF
LEUT_Type_II_RFP_W56HV-16-R-0210_Questions_Set_1,_1-12.pdf PDF
Type_II_LEUT_CDRLs_Signed_LATEST_VERSION_25Jan2018.pdf PDF
Attachment_0025_Past_Performance_Questionnaire_v2.doc DOC document
Attachment_0030,_Consolidated_GFP.pdf PDF
Attachment_0011,_Sample_Level_Of_Repair_Analysis.docx DOCX document
Attachment_0010_LEUT_PRICING_MATRIX_V15.xlsx XLSX spreadsheet
Attachment_0030,_Consolidated_GFP.pdf PDF
Attachment_0028,_General_Mechanics_Tool_Kit.pdf PDF
Attachment_0002,_DDD_for_ECPs_and_VECPs.doc DOC document
Attachment_0018,_Trailer_Vehicle_Dynamic_Data_Sheet_20170929_edits.xlsx XLSX spreadsheet
Attachment_0006,_DI-ILSS-80134A.pdf PDF
W56HZV16R0210.pdf PDF
Attachment_0007,_DoD_Guide_UID_v3.0.pdf PDF
Attachment_0010_LEUT_PRICING_MATRIX_V14.xlsx XLSX spreadsheet
Attachment_0011,_Sample_Level_Of_Repair_Analysis.docx DOCX document
Attachment_0021,_Performance_Summary_Matrix_Revised_06_Feb_2018_edits.xlsx XLSX spreadsheet
Attachment_0029,_Superseding_Revisions_to_ATPD-2414B.pdf PDF
Attachment_0023,_Controlled_Unclassified_Information_(CUI).pdf PDF
Attachment_0001,_ATPD-2414B_-_M1269_Type_II_LEUT.pdf PDF
Attachment_0014,_MIL-STD_40051-2C.pdf PDF
Attachment_0017,_VCI_Data_Requirements_for_Trailer_20170929_edits.xlsx XLSX spreadsheet
Attachment_0027,_Request_for_use_of_Prohibited_Materials_-_LEUT.doc DOC document
Attachment_0008,_SOP_Unique_Item_Traceability_Data_Integrity.pdf PDF
Attachment_0025_Past_Performance_Questionnaire.doc DOC document
Attachment_0012,_Sample_Critical_Stockage_List.doc DOC document
Attachment_0013,_Sample_Provisioning_Requirements_Statement.doc DOC document
Attachment_0015,_Sample_DrawingTree.pdf PDF
Attachment_0022,_JPO_JLTV_OPSEC_Plan.pdf PDF
Attachment_0020,_TDP_Requirements.docx DOCX document
Attachment_0016,_GFP_Tracker.xlsx XLSX spreadsheet
Attachment_0009,_2408-9_Instructions.docx DOCX document
Attachment_0019,_Simulation_based_Design_Model_Data_CAE.doc DOC document
Attachment_0010_LEUT_PRICING_MATRIX_V14.xlsx XLSX spreadsheet
Attachment_0030,_Consolidated_GFP.pdf PDF
Attachment_0026,_LEUT_SOW_to_CLIN_Crosswalk_20180118_Clean.xlsx XLSX spreadsheet
Attachment_0011,_Sample_Level_Of_Repair_Analysis.docx DOCX document
Attachment_0010_LEUT_PRICING_MATRIX_V14.xlsx XLSX spreadsheet
Attachment_0010_LEUT_Pricing_Matrix_20180215.xlsx XLSX spreadsheet
Attachment_0021,_Performance_Summary_Matrix_Revised_06_Feb_2018_edits.xlsx XLSX spreadsheet
Attachment_0020,_TDP_Requirements.docx DOCX document
Type_II_LEUT_CDRLs_Signed_LATEST_VERSION_25Jan2018.docx DOCX document
Attachment_0017,_VCI_Data_Requirements_for_Trailer_20170929_edits.xlsx XLSX spreadsheet
Show 40 more

Latest 50 of 78 listed here. See the rest on GovTribe.

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

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

W56HZV

U.S. ARMY CONTRACTING COMMAND

WARREN, MICHIGAN 48397-5000

JAMES R. JONES III

EMAIL: JAMES.R.JONES3.CIV@MAIL.MIL

W56HZV-16-R-0210

2018FEB26

X

X 2018APR06 12:00pm

2 signed

SEE SECOND PAGE FOR DESCRIPTION

1 43

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: JAMES R. JONES III

Buyer Office Symbol/Telephone Number: CCTA-HTA-C/(586)282-3494

Type of Contract 1: Firm Fixed Price

Kind of Contract: Supply Contracts and Priced Orders

*** End of Narrative A0000 ***

The purpose of this amendment is to update Section A (Executive Summary), Section C (Statement of Work), Section E and Section M;

Attachments 0010, 0011, 0025, and 0026; as well as add Attachment 0030. This amendment will also extend the closing date and the deadline for Government receipt of Pre-Proposal questions.

1. Updates to Section A, Section C, Section E, and Section M are as follows:

- Section A.5

From:

Offerors are advised that this solicitation contains two affordability caps. Section M contains the Affordability requirements. No proposal will be considered for award if the proposed Year 1 cost is more than $2,910,647 or LEUT Affordability exceeds

$63,862,698.

To:

Offerors are advised that this solicitation contains two affordability caps. Section M contains the Affordability requirements. No proposal will be considered for award if the proposed Year 1 cost is more than $2,827,495 or LEUT Affordability exceeds

$63,862,698.

- Section C.6.2.1

From:

Topcoat shall be CARC paint per MIL-DTL-64159 Coating, Water Dispersible Aliphatic Polyurethane, and Chemical Agent Resistant.

Army Technical Bulletin 43-0209, Color, Marking, and Camouflage Painting of Military Vehicles, Construction Equipment and

Materials Handling Equipment shall be used for registration marking IAW AR 750-1, Chapter 7, Section 8, component surfaces.

Component surfaces that exceed 400\'b0F (204\'b0C) shall be coated with heat resistant paint. The Type II LEUT and its accessories shall be prepared, treated, and painted per best commercial practice. There shall be no over spray on informational components such as instruction plates. All internal and external threads shall be greaseless and free from paint before painting. The finish and quality assurance testing for all painted surfaces shall be IAW MIL-DTL-53072.

To:

Topcoat shall be CARC paint per MIL-DTL-64159 Coating, Water Dispersible Aliphatic Polyurethane, and Chemical Agent Resistant.

Army Technical Bulletin 43-0209, Color, Marking, and Camouflage Painting of Military Vehicles, Construction Equipment and

Materials Handling Equipment shall be used for registration marking IAW AR 750-1, Chapter 7, Section 8, component surfaces.

Component surfaces that exceed 400 degrees Fahrenheit (204 degrees Celsius) shall be coated with heat resistant paint. The Type II

LEUT and its accessories shall be prepared, treated, and painted per best commercial practice. There shall be no over spray on informational components such as instruction plates. All internal and external threads shall be greaseless and free from paint before painting. The finish and quality assurance testing for all painted surfaces shall be IAW MIL-DTL-53072.

- Section C.8.2.3

From:

New Test Measurement and Diagnostic Equipment (TMDE) Items. The contractor shall not introduce any new unique tools without prior written Government approval. However, those not identified in U.S. Army Supply Catalogs may require special source and calibration documentation in order to update and provide data for possible inclusion to the TMDE register (DA Pam 700-21-1). Reference web site DA PAM 700-60, ://www.apd.army.mil/epubs/DR_pubs/DR_a/pdf/web/p700_60.pdf, for more information.

To:

New Test Measurement and Diagnostic Equipment (TMDE) Items. The contractor shall not introduce any new unique tools without prior

2 43

W56HZV-16-R-0210 0001

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

written Government approval. However, those not identified in U.S. Army Supply Catalogs may require special source and calibration documentation in order to update and provide data for possible inclusion to the TMDE register (DA Pam 700-21-1). Reference web site DA PAM 700-60, http://www.apd.army.mil/epubs/DR_pubs/DR_a/pdf/web/p700_60.pdf , for more information.

- Section C.8.4

From:

The contractor shall conduct pre-procurement screening for component parts. The screening process consists of checking for existing, valid part numbers, National Stock Numbers (NSN), and current unit of measure and issue prices for provisioning purposes for these items. Drawings are not required for items which already have a valid NSN.

The contractor shall enter each LMI Data Product the Next Higher Assembly (NHA) in Genesis. The contractor shall identify, at a minimum, the immediate NHA Provisioning List Item Sequence Number Provisioning List Item Sequence Number (PLISN), the NHA, items with a recoverability code of XC (Logistics Control Number identification) and the End Item PLISN with the proper Indicator Code and overhaul quantities for each item identified as a NHA having a Source Code of P. For non-P coded items, only the NHA and

Indicator Codes are required.

To:

The contractor shall conduct pre-procurement screening for component parts. The screening process consists of checking for existing, valid part numbers, National Stock Numbers (NSN), and current unit of measure and issue prices for provisioning purposes for these items. Drawings are not required for items which already have a valid NSN.

The contractor shall enter each LMI Data Product to the Next Higher Assembly (NHA) in Power-LOG-J through the LOGSA website at https://www.logsa.army.mil/lec/powerlog/ IAW CDRL A039. The contractor shall identify, at a minimum, the immediate NHA

Provisioning List Item Sequence Number Provisioning List Item Sequence Number (PLISN), the NHA, items with a recoverability code of XC (Logistics Control Number identification) and the End Item PLISN with the proper Indicator Code and overhaul quantities for each item identified as a NHA having a Source Code of P. For non-P coded items, only the NHA and Indicator Codes are required.

- Section C.8.9.7

From:

Equipment Control Record, Department of Army Form 2408-9. The contractor shall complete and submit Equipment Control Record

Department of Army (DA) Form 2408-9, IAW Attachment 0009, within Logistics Support Agency (LOGSA) website: ://liw.logsa.army.mil for each Type II LEUT produced under this contract IAW MIL-STD-3003B. DA 2408-9 includes instructions for completing the file and printing the 2408-9 form. The Contractor shall insert the actual copy of the DA Form 2408-9 in each Type II LEUT log folder located in the Assembly Bag containing the Hand Receipt and Operators Manual. The contractor shall notate the Production database with the date (month, day, and year) the DA Form 2408-9 was submitted in LOGSA and the date (month, day, and year) the DA Form

2408-9 was securely included on the Type II LEUT.

To:

Equipment Control Record, Department of Army Form 2408-9. The contractor shall complete and submit Equipment Control Record

Department of Army (DA) Form 2408-9, IAW Attachment 0009, within Logistics Support Agency (LOGSA) website:

https://liw.logsa.army.mil for each Type II LEUT produced under this contract IAW MIL-STD-3003B. DA 2408-9 includes instructions for completing the file and printing the 2408-9 form. The Contractor shall insert the actual copy of the DA Form 2408-9 in each

Type II LEUT log folder located in the Assembly Bag containing the Hand Receipt and Operators Manual. The contractor shall notate the Production database with the date (month, day, and year) the DA Form 2408-9 was submitted in LOGSA and the date (month, day, and year) the DA Form 2408-9 was securely included on the Type II LEUT.

- Section C.9.1.1 - C.9.1.5

From:

C.9.1.1 Aberdeen Proving Ground for approximately 20 consecutive weeks. The contractor is responsible for providing on-site test support between the hours of 6:30 am 4:30 pm, Monday thru Friday (NTE 40 hours per week) except Federal holidays or when the

Government facility is closed due to local or national emergencies, administrative closings, or similar Government directed facility closings.

C.9.1.2 Yuma Test Center for approximately 1 week. The contractor is responsible for providing on-site test support between the hours of 6:30 am 4:30 pm, Monday thru Friday (NTE 40 hours per week) except Federal holidays or when the Government facility is closed due to local or national emergencies, administrative closings, or similar Government directed facility closings.

3 43

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

C.9.1.3 Defense Ammunition Center (DAC) for approximately 2 consecutive weeks. The contractor is responsible for providing on-site test support between the hours of 6:30 am 4:30 pm, Monday thru Friday (NTE 40 hours per week) except Federal holidays or when the

Government facility is closed due to local or national emergencies, administrative closings, or similar Government directed facility closings.

C.9.1.4 TARDEC for approximately 25 consecutive weeks. The contractor is responsible for providing on-site test support between the hours of 6:30 am 4:30 pm, Monday thru Friday (NTE 40 hours per week) except Federal holidays or when the Government facility is closed due to local or national emergencies, administrative closings, or similar Government directed facility closings.

C.9.1.5 Follow on Production Testing for approximately 4 consecutive weeks per production year at Aberdeen or Yuma Test Centers.

The contractor shall be responsible for providing on-site test support between the hours of 6:30 am 4:30 pm, Monday thru Friday

(NTE 40 hours per week) except Federal holidays or when the Government facility is closed due to local or national emergencies, administrative closings, or similar Government directed facility closings.

To:

C.9.1.1 Aberdeen Proving Ground for approximately 20 consecutive weeks. The contractor is responsible for providing on-site test support between the hours of 6:30 am - 4:30 pm, Monday thru Friday (NTE 40 hours per week) except Federal holidays or when the

Government facility is closed due to local or national emergencies, administrative closings, or similar Government directed facility closings.

C.9.1.2 Yuma Test Center for approximately 1 week. The contractor is responsible for providing on-site test support between the hours of 6:30 am - 4:30 pm, Monday thru Friday (NTE 40 hours per week) except Federal holidays or when the Government facility is closed due to local or national emergencies, administrative closings, or similar Government directed facility closings.

C.9.1.3 Defense Ammunition Center (DAC) for approximately 2 consecutive weeks. The contractor is responsible for providing on-site test support between the hours of 6:30 am - 4:30 pm, Monday thru Friday (NTE 40 hours per week) except Federal holidays or when the Government facility is closed due to local or national emergencies, administrative closings, or similar Government directed facility closings.

C.9.1.4 TARDEC for approximately 12 consecutive weeks. The contractor is responsible for providing on-site test support between the hours of 6:30 am - 4:30 pm, Monday thru Friday (NTE 40 hours per week) except Federal holidays or when the Government facility is closed due to local or national emergencies, administrative closings, or similar Government directed facility closings.

C.9.1.5 Follow on Production Testing for approximately 4 consecutive weeks per production year at Aberdeen or Yuma Test Centers.

The contractor shall be responsible for providing on-site test support between the hours of 6:30 am - 4:30 pm, Monday thru Friday

(NTE 40 hours per week) except Federal holidays or when the Government facility is closed due to local or national emergencies, administrative closings, or similar Government directed facility closings.

- Section E.5

From:

The Government will begin the PQT with the start of TARDEC testing. The expected duration of the PQT test is approximately seven months, some test events may run concurrently. The contractor shall deliver one Type II LEUT Trailer to TARDEC (Warren, MI), six

Type II LEUT Trailers to Aberdeen Test Center (ATC), one Type II LEUT Trailer to Yuma Test Center (YTC), and one Type II LEUT trailer to McAllister, OK (DAC) for testing. Asset utilization and duration shall be allocated as indicated below:

Test

Site Quantity Purpose ___ Expected Duration__________________________________________________________________________________________________________

OEM 2 Log Demonstration/Soldier Interaction Test Event/Verification 4 weeks

ATC * PMBS field data collection for TARDEC drive files 2 weeks

TARDEC 1 PMBS/VIPER/SPIDER 25 weeks

ATC 2 Endurance/RAM Testing 20 weeks

ATC 4 Performance Testing/Environmental Testing/HSL 8 weeks

YTC 1 Road Departure and Recovery Test 1 week

DAC 1 Ammunition Certification Testing 2 weeks

To:

The Government will begin the PQT with the start of TARDEC testing. The expected duration of the PQT test is approximately seven months, some test events may run concurrently. The contractor shall deliver one Type II LEUT Trailer to TARDEC (Warren, MI), six

Type II LEUT Trailers to Aberdeen Test Center (ATC), one Type II LEUT Trailer to Yuma Test Center (YTC), and one Type II LEUT trailer to McAllister, OK (DAC) for testing. Asset utilization and duration shall be allocated as indicated below:

4 43

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

Test

Site Quantity Purpose ___ Expected Duration__________________________________________________________________________________________________________

OEM 2 Log Demonstration/Soldier Interaction Test Event/Verification 4 weeks

ATC * PMBS field data collection for TARDEC drive files 2 weeks

TARDEC 1 PMBS/VIPER/SPIDER 12 weeks

ATC 2 Endurance/RAM Testing 20 weeks

ATC 4 Performance Testing/Environmental Testing/HSL 8 weeks

YTC 1 Road Departure and Recovery Test 1 week

DAC 1 Ammunition Certification Testing 2 weeks

- Section M.3.2.1.1

From:

Affordability based on Available Funding for Year 1 will be calculated by Attachment 0010, 'Year 1 Affordability' tab, which adds together the proposed prices for the following CLINs: 0011AA, 0021, 0031AA, 0041, 0051, 0061, 0071, 0081, 0101, 0111, 0121, 0131AA, and 0141. Proposals that exceed $2,910,647 for these CLINs will be determined unaffordable and will not be considered for award.

To:

Affordability based on Available Funding for Year 1 will be calculated by Attachment 0010, 'Year 1 Affordability' tab, which adds together the proposed prices for the following CLINs: 0011AA, 0021, 0031AA, 0041, 0051, 0061, 0071, 0081, 0101, 0111, 0121, 0131AA, and 0141. Proposals that exceed $2,827,495 for these CLINs will be determined unaffordable and will not be considered for award.

2. Update the following attachments:

Attachment 0010 LEUT PRICING MATRIX V15

- Updated version to reflect change to Year 1 affordability cost

Attachment 0011 Sample Level Of Repair Analysis

- Updated title within Attachment 0011 from Attachment 0025 to Attachment 0011

Attachment 0025 Past Performance Questionnaire

- Updated point of contact and receive date for past Performance Questionnaire

Attachment 0026 LEUT SOW to CLIN Crosswalk

- Updated to correct version

3. Add the following attachment to FBO:

- Attachment 0030 Consolidated GFP

4. As of now, Attachment 0003, DDD for NORs v1 RESERVED and Attachment 0005, Maintenance Analysis 29May14 RESERVED are reserved and not used.

5. Due to the changes made as a result of this amendment, the closing date is changed from 28 March 2018 to 6 April 2018. The deadline for Government receipt of Pre-Proposal questions is changed from March 19, 2018 to March 26, 2018.

*** END OF NARRATIVE A0003 ***

EXECUTIVE SUMMARY

Light Engineer Utility Trailer (LEUT) Type II

Low Rate Initial Production (LRIP) / Full Rate Production (FRP)

Contract REQUEST FOR PROPOSAL (RFP) W56HZV-16-R-0210

A.1 Introduction

RFP W56HZV-16-R-0210 is issued by the US Army Contracting Command Warren (ACC-WRN) for the Production Phase of the LEUT program.

The LEUTs primary mission is to provide current and future Engineer U.S Joint Forces with a dedicated light haul capability that is

5 43

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

required for the transport of key construction enablers, Steer Skid Loader (SSL) and Back Hoe Loader (BHL) that are used during construction and combat operations.

A.2 LEUT Acquisition Strategy

This RFP is a total small business set-aside. The Government intends to award one firm-fixed price contract resulting from this RFP using best value tradeoff procedures. All proposal submission requirements are located in Section L. All proposals shall clearly identify why the acceptance of the proposal would be advantageous to the Government. Any proposed deviations from or exceptions to the requirements, terms, and conditions of the solicitation shall be clearly identified and explicitly defined. Offerors are cautioned to consult the Contracting Officer IN WRITING before submitting an offer that proposes any deviations or exceptions to any of the requirements, terms, and conditions of the solicitation because it may be cause for rejection of the proposal.

A.3 Production Award

A.3.1 The Government intends to award one five-year firm-fixed price (FFP) with two option years, Indefinite Delivery Indefinite

Quantity (IDIQ) contract for hardware, test support, and logistics products. The minimum guaranteed quantity is 11 LRIP trailers. The maximum quantity under this contract is 1,505 trailers. The Government intends to order the minimum guaranteed quantity at the time of contract award under delivery order 0001. The initial order quantity will be for LRIP assets that will be taken through a formal

Government test program. Upon successful completion of the test program, full rate production may begin.

A.3.2 Offerors are advised not to provide pricing information in Section B of the solicitation. Offerors shall complete and submit prices in the Price Evaluation Worksheet (Attachment 0010). Offerors must provide prices for all items identified in Attachment 0010.

A.3.3 CLINs 0011AA, 0041, 0101, and 0131AA are subject to FOB Destination Clauses 52.247-34, 52.247-48.

A.3.4 Threshold and Objective Requirements

A.3.4.1 The Army Tank Purchase Description ATPD-2414B (Attachment 0001) and Superseding Revisions to ATPD-2414B (Attachment 0029), contains technical requirements that have both threshold (required) and objective (desired) performance levels. Offerors MUST meet all

THRESHOLD performance levels identified in Attachment 0001 and Attachment 0029, Superseding Revisions to ATPD-2414B. Offerors may propose to meet any OBJECTIVE performance levels indicated in Attachment 0001 and Attachment 0029, Superseding Revisions to ATPD-2414B.

However, evaluation credit for exceeding the threshold performance level will only be given as outlined in Section M.

A.3.4.2 The Government will incorporate the offerors proposed level of performance for the requirements list in Section L.4.1.6.2 and

L.4.1.7.2 into any resulting contract.

A.3.4.3 Attachment 0029, Superseding Revisions to ATPD-2414B, supersedes Paragraphs 3.6.2 and 3.6.5 of Attachment 0001, ATPD-2414B.

A.4 Government Furnished Equipment and Information

Government-Furnished Equipment (GFE) and Government Furnished Information (GFI), will be tracked on Attachment 0016. All GFE provided to the contractor for use shall be maintained in accordance with (IAW) the applicable Technical Manual (TM) applicable to the GFE. All

GFE shall be only used with trained and licensed operators.

A.5 Affordability

Offerors are advised that this solicitation contains two affordability caps. Section M contains the Affordability requirements. No proposal will be considered for award if the proposed Year 1 cost is more than $2,827,495 or LEUT Affordability exceeds $63,862,698.

A.6 Basis of Award

Award will be made on a Best Value Trade-Off (FAR 15.101-1) basis. Offerors must carefully review Sections L and M of the solicitation and understand the evaluation criteria that will be used in the Government's selection of the Best Value offer for award.

A.7 Formal Communication

A.7.1 All questions regarding this RFP shall be submitted IN WRITING ONLY to the Contract Specialist, via email at

"mailto:usarmy.detroit.acc.mbx.wrn-leut@mail.mil " All questions and correspondence related to this RFP shall reference the RFP number

W56HZV-16-R-0210 in the email subject line.

A.7.2 The deadline for Government receipt of Pre-Proposal questions is March 26, 2018, 1:00PM, Local Time, Warren, MI. Any questions received after this date and time may not be addressed before the RFP closes, and shall not be a cause for extension of the closing date. Therefore, offerors are advised to submit questions as soon as possible.

A.7.3 The RFP and synopsis are posted on the FEDBIZOPPS website. The Government will post amendments to the RFP on the same website.

6 43

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

The Government will post answers to industry-generated questions to the same website. Offerors shall note that questions submitted containing proprietary information shall be considered a waiver of any protection of that information as the question and the Government response will be posted to the FEDBIZOPPS website. Responses to industry-generated questions are not considered changes to the RFP.

The only way the RFP can be changed is through an amendment.

A.7.4 Offerors are responsible for periodically reviewing the FEDBIZOPPS website for the most current information pertaining to this

RFP. If an offeror experiences connectivity issues with the website, the offeror shall submit a request via email to the Contract

Specialist at usarmy.detroit.acc.mbx.wrn-leut@mail.mil for the most recent information published on the site.

*** END OF NARRATIVE A0001 ***

7 43

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

SECTION C - DESCRIPTION/SPECIFICATIONS/WORK STATEMENT

DESCRIPTION/SPECIFICATION INDEX

C.1 General

C.2 Hardware and Material

C.3 Meetings, Reviews and Conferences

C.4 Integrated Master Schedule

C.5 Configuration Management

C.6 Corrosion

C.7 Environmental, Safety and Occupational Health (ESOH)

C.8 Integrated Product Support (IPS)

C.9 Test Service Representative (TSR)

C.10 Modeling and Simulation (M&S)

C.11 Government Furnished Equipment and Information

C.12 Warranty

C.13 Transportability Report

C.14 Production Database

C.15 Federal Retail Excise Tax (FRET) Expenses

C.16 Security Requirements

C.17 Program Protection Plan (PPP)

C.18 Contractor Manpower Reporting

C.1 GENERAL

C.1.1 INTRODUCTION. This scope of work (SOW) is for the production of the Light Engineer Utility Trailer (LEUT), M1269, Type II.

C.1.2 System Requirements. The contractor shall be responsible for the overall component selection, integration, design, development, fabrication, contractor testing, logistics product development, configuration management to meet the requirements of the Automotive

Tank Purchase Description (ATPD) 2414B (Attachment 0001) and Superseding Revisions to ATPD-2414B (Attachment 0029), providing test support for Government conducted production qualification, logistics demonstration, technical manual validation/verification, and special test events.

C.1.3 Data. The contractor shall prepare deliverable program data IAW the format and content specified in the Data Item Descriptions

(DID) and deliver data IAW the Contract Data Requirements List (CDRL) (Exhibit A). Data submitted by e-mail shall not exceed 10 megabytes (MB) in file size. The contractor shall transmit Data over 10 MB on a CD via regular mail or AMRDEC Secure Access File

Exchange (SAFE) Web application.

C.1.3.1 Applicable Documents. The contractor shall utilize the most recent versions of all DIDs, regulations, specifications, and standards listed throughout this contract. The DIDs, Military specifications, and Military standards are located at:

https://assist.dla.mil .

C.2 HARDWARE AND MATERIAL

C.2.1 Type II LEUT. The contractor shall manufacture the Type II LEUT IAW the requirements of Attachment 0001 and Attachment 0029, Superseding Revisions to ATPD-2414B. The Government will maintain Attachment 0001 and Attachment 0029, Superseding Revisions to ATPD-

2414B.

8 43

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

C.2.2 Product Support Package (PSP). The contractor shall deliver a PSP (as detailed in Section C.8.7) for PQT, Logistics Demonstration

(LD) and TM verification site support no later than 30 days prior to testing. The contractor shall package the PSP IAW packaging and preservation requirements in Section D of this document. A PSP shall be delivered to the following locations:

C.2.2.1 Aberdeen Proving Ground IAW section C.9.1.1.

C.2.2.2 Reserved.

C.2.2.3 U.S. Army Tank Automotive Research Development and Engineering Center (TARDEC) IAW section C.9.1.4.

C.2.2.4 Original Equipment Manufacturer (OEM) IAW Section C.8.5.1.

C.2.2.5 Follow-on Production Testing sites IAW section C.9.1.5 and E.9.1.

C.2.3 Basic Issue Items (BII). The contractor shall procure and over-pack the BII and inventory list IAW Attachment 0001 and Attachment

0029, Superseding Revisions to ATPD-2414B, with each Type II LEUT produced under this contract.

C.2.4 Authorized Stockage List (ASL). The contractor shall package and deliver ASL.

C.2.5 Technical Manuals (TM). The contractor shall over-pack a GFI TM with each trailer produced during FRP in accordance with section

C.8.5.6.

C.3 MEETINGS, REVIEWS, AND CONFERENCES

C.3.1 Participation and Administration. The contractor shall participate in all meetings, reviews, audits, and assessments required in this scope of work. Where possible, the contractor shall schedule face to face meetings in tandem, or groups, to minimize personnel resources and travel expenses. The contractor shall submit an agenda and read-ahead package in contractor format for all meetings, audits, assessments, and reviews IAW CDRL A024. The contractor shall record and provide minutes for all meetings, audits, assessments, and reviews called out in this contract IAW CDRL A025. The contractor shall identify the recorder at the beginning of each event. The contractor shall coordinate arrangements for all meetings with the Contracting Officer Representative (COR) no later than 10 days in advance of all meetings. Arrangements shall include meeting date, time, in person, or via teleconference and location.

C.3.1.1 Meeting and Conferences. The contractor shall make the following available for the Governments use when meetings or conferences take place at the contractors facility

a. Required technical, logistical or other documentation (including drawings, computer data bases, publications, and other required data).

b. Restrooms.

c. Access to standard office equipment including copy, fax machines and internet access.

C.3.2 Start of Work Meeting (SOWM). The contractor shall conduct a SOWM with Government attendees within 20 business days after contract award, at the contractors production facility. At the SOWM, the contractor shall identify to the Government how they will manage all design, integration, fabrication, supportability, and risk throughout the production phase. The SOWM will consist of a scope of work and CDRL review, an Integrated Product Support In-Process Review (reference C.3.8), an Integrated Master Schedule (IMS) review

(reference C.4), and a System Requirements Review (SRR). The SRR will be a line by line review of Attachment 0001 and Attachment 0029, Superseding Revisions to ATPD-2414B. The contractor shall also conduct a Preliminary Design Review (PDR) (See Section C.3.2.2) at the

SOWM. For planning purposes, the SOWM meeting is anticipated to be a five day event.

C.3.2.1 SOWM Presentation. At the SOWM, the contractor shall provide a detailed description of the procedures, actions, events and organization the contractor intends to employ to accomplish the mission.

C.3.2.2 Preliminary Design Review. The contractor shall host the PDR during the SOWM. The purpose of this PDR is to ensure the preliminary design and basic system architecture are complete, and that there is technical confidence in the designs ability to meet the requirements of the ATPD. The PDR shall be determined to be complete by the Government Technical Review Chair.

C.3.2.2.1 PDR Completion Criteria:

a) Technical data for the allocated baseline are complete, satisfy the system specification, and provide a sufficient foundation for detailed design to proceed

b) Risks have been balanced and are acceptable with any risk mitigation plans

c) Feasibility and schedule are determined to be within acceptable risk margins

9 43

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

d) IMS is updated (including systems and software critical path drivers) and includes all activities required to complete Critical

Design Review (CDR) (assuming same developer responsible for PDR and CDR)

e) Corrective action plans for issues in the PDR have been identified or resolved

f) Quality management system has been deemed acceptable by the Government Technical Review Chair or COR

C.3.3 Critical Design Review. The contractor shall host a CDR no later than 30 days after start of the PDR. The primary purpose of the meeting is to formalize the initial product baseline, assess design maturity and evaluate risks. The contractor shall present their configuration design and meet all completion criteria identified by the Government for this review. This meeting serves as the decision point for the Government to allow the contractor to begin assembly of the LRIP test trailers upon approval of CDR. The CDR shall be determined to be complete by the Government Technical Review Chair.

C.3.3.1 CDR Completion Criteria:

a) An established system initial product baseline

b) Acceptable risks with mitigation plans approved

c) The program development schedule has been updated to include; fabrication, test and evaluation, software coding (if applicable), and critical path drivers

d) The program sustainment development efforts and schedules have been updated based on current budgets, test evaluation results and firm supportability design features

e) Quality management system has been updated to include changes post-PDR and deemed acceptable by the Government Technical Review

Chair or PCO

C.3.4 Test Readiness Review (TRR). The contractor shall attend and provide supporting information related to the Government conducted

TRR at Aberdeen Proving Ground, MD, which shall be held no more than 30 days after delivery of the first LRIP. The purpose of the TRR is to verify that all required resources and plans are ready so that the Government can commence test activities.

C.3.5 Production Readiness Review (PRR). Following the completion of PQT, the contractor shall conduct a PRR to allow the Government to determine if the design is ready for full rate production and if the contractor and major subcontractors have accomplished adequate production planning without incurring unacceptable risks that will breach thresholds of schedule or performance. The PRR shall be conducted no later than 45 days after PQT completion.

C.3.6 Program Management Integrated Product Team (IPT) Meetings. The contractor shall conduct a weekly teleconference Program

Management IPT meeting. The primary purpose of this meeting is to review the contract performance plan, provide progress assessments, review technical and other specialty area status, and review open action items.

C.3.7 Program Management Reviews (PMR). The contractor shall conduct quarterly PMRs at the contractors facility with the Government.

The exact date of each meeting shall be mutually agreed upon by the contractor and the Government. The first PMR is estimated to occur

90 days after the SOWM. At a minimum, the topics shall include: schedule, performance, production status, logistics, engineering, quality, contracting, risk status, and corrective actions. The contractor shall prepare meeting minutes and include identification of items requiring specific actions, response dates and responsible organization. Other Government agencies and contractors may be in attendance which will be coordinated prior to the PMR.

C.3.8 Integrated Product Support In-Process Reviews (IPSIPRs). The contractor shall host, at their facility, IPSIPRs. IPSIPRs commence in conjunction with the SOWM and will repeat on a monthly basis for the duration of Logistics Demonstration. IPSIPRs shall consist of reporting progress on logistics products development to include schedule, present logistics products for review, discuss, and track issues and actions items for resolution. The contractor shall have available supportive material and maintenance rationale for all logistics data presented for the Governments review. The contractor shall provide a meeting place, administrative support and office equipment as required until all required data is delivered and approved. The contractor shall brief the Integrated Product Support Team a provisioning performance schedule IAW CDRL A048 at the Initial Logistics IPSIPR.

C.3.8.1 Provisioning Conference. The contractor shall host, at their facility, Provisioning Conferences. Provisioning Conferences shall be included as part of CDR, and will repeat on a monthly basis until the end of product verification. The contractor shall brief the

Integrated Product Support Team a provisioning performance schedule with updates IAW CDRL A048 at every Provisioning Conference.

C.3.9 Test Meetings. Test meetings shall be held IAW section E.7.3.

C.3.10 System Safety and Environmental Working Group. System Safety and Environmental Working Group meetings shall be held IAW section

C.7.7.

10 43

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

C.4 INTEGRATED MASTER SCHEDULE. The contractor shall develop, maintain, and deliver an IMS (CDRL A013) throughout the life of the contract. The contractor shall maintain the IMS, present the IMS at the SOWM and at each PMR, explain all delays in meeting contract requirements, and provide get-well plans within 30 days of discovery.

C.5 CONFIGURATION MANAGEMENT

C.5.1 Configuration Management (CM). The contractor shall implement a CM program for configuration planning, identification, control, status accounting, verification, audit, and data management of the Type II LEUT and document the CM program in a CM Plan. To maximize return on investment and reduce life cycle costs, the contractor shall use best practices to implement the technical and program management principles fundamental to CM detailed in C.5.1.1 below. The contractor shall deliver the CM Plan IAW CDRL A005.

C.5.1.1 Configuration Management Standards. The contractor shall perform CM as required by this contract and as extracted from the SAE-

EIA-649-1, Configuration Management Requirements for Defense Contracts. SAE GEIA-HB-649, Implementation Guide for CM, may be used for guidance.

C.5.2 Configuration Identification and Data Management (DM). The contractor shall perform data management, provide the configuration documentation to document the physical and functional characteristics of the Type II LEUT, establish baselines for configuration control, and assign product and document identifiers as required by sections C.3.3, C. 5.2.1, C.5.2.2, C.5.2.3, C.5.2.4, and C.5.2.3.1.

The contractor is responsible for all original data in its possession, including drawings, models, and associated documents. The contractor shall flow down CM and DM requirements to subcontractors and suppliers to provide an appropriate application of CM and DM functions and principles to the entire supply chain.

C.5.2.1 Data Management. The contractor shall possess an authoritative product data, engineering or configuration management system and the processes to effectively manage, securely store, release, validate, and track multiple versions and iterations of the Type II LEUT:

as-designed, as-integrated, as-built, and as-delivered configuration baselines; this includes management of product structures, product definition documents and data, contractor test and analysis data, GFI and other related technical documents.

C.5.2.2 Version Control and Traceability. The contractor shall assign a unique identifier to product data and utilize disciplined version control in managing digital data. Each revision (version) shall be a new master, and the contractor shall retain all approved revisions of each document and model representation to provide a traceable history in order to access the correct revision when needed.

Numerical revisions are not allowed. The contractor shall ensure that all representations (i.e., Adobe PDF, CAD, etc.) of a single version or revision of data, delivered to the Government for approval and subsequently maintained by the contractor for the term of this contract, are identical. The content of a document and model revision is fixed once approved by PD LTV.

C.5.2.3 Configuration Baseline and Release. The contractor shall have a process in place for initial release of design information, release of approved changes to the design information, and delivery of released data to the Government. The contractor shall be responsible for creating and maintaining the design release configuration (e.g., developmental baseline, design release baseline) up to date, by incrementally releasing new design data and incorporating approved engineering changes to the Type II LEUT design as they occur. The contractor shall maintain an up to date incremental developmental baseline for the Type II LEUT. At completion of the CDR, the contractor shall establish and maintain the Initial Product Baseline (IPBL) (e.g., initial production configuration baseline). This

IPBL shall identify and document the functional and physical characteristics of the Type II LEUT. The design release configuration shall then be incrementally updated to incorporate approved changes resulting in a Final Product Baseline (FPBL) as an output of PQT approval, Logistics Demonstration, PRR, and Physical Configuration Audit (PCA). The contractor shall maintain an updated product baseline for the entire period of performance and submit the IBOM IAW CDRL A047.

C.5.2.3.1 Design Freeze for Test. The Type II LEUT design shall be frozen upon delivery of the first test asset(s) to the test site; all test assets delivered shall be identical in configuration. The contractor shall not incorporate changes without prior Government approval.

C.5.2.4 Product and Enterprise identifiers. The Part or Identifying Number (PIN), in combination with the Commercial and Government

Entity (CAGE), establishes unique item identification of products. A PIN and CAGE shall be used to uniquely identify all Type II LEUT products. The Government is the design activity (i.e., design authority, customer, procuring activity) for all products (e.g., hardware, software, models, drawings, associated documents) newly developed, or altered or modified from already developed products. The contractor shall assign a Government PIN for the product identifier when TACOM is the design activity, assigning CAGE 19207 as the enterprise identifier. Design documents (e.g., CAD models, drawings) for new or modified or altered items shall be numbered the same as, or included within, the part number.

C.5.2.5 Existing Products. Already developed products used in the Type II LEUT, including commercial products, products defined by

Government or non-Government standards, and products for which a Government organization is the design activity, shall retain the existing identifiers (document number, PIN and CAGE), unless modified to the extent that interchangeability is affected. Already developed Army items having a Government PIN and CAGE that are modified for the Type II LEUT Trailer shall not be re-identified with the contractor's or other vendor PINs. The item and its product data shall reflect a new Government PIN with CAGE 19207. The contractor shall maintain configuration records that link or otherwise retain history of the original Government PIN-CAGE to the new Government PIN-

CAGE and include this information IAW CDRL A002, Configuration Status Accounting (CSA) Information reports.

11 43

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

C.5.2.6 Re-identification. The contractor shall not re-identify or re-mark supplier or purchased parts or related product data with its own PIN and CAGE. The contractor shall not use supplier PINs for items that can be defined by Government or industry standards or specifications. The only parts reflecting the prime contractor's PINs and CAGE shall be those items for which the contractor is the design activity. The contractor's product data, including Bill of Material (BOM), drawings, models, parts lists, and reports, shall be consistent in identifying the correct design activity PIN and CAGE.

C.5.2.7 Military and Industry Standard Parts. In lieu of contractor, Original Equipment Manufacturer (OEM), supplier, or other commercial and vendor PINs, the contractor shall use the military, industry, or specification-identified PINs in the product data for all fasteners, standard hardware, bulk material, and other items that can be defined by Government and non-Government standardization documents, and international or foreign standardization documents adopted by the American National Standards Institute (ANSI) for use in the U.S., paired with the CAGE of the corresponding standardization document.

C.5.2.7.1 The contractor shall use the part-numbering convention defined by these Government, non-Government, or adopted international or foreign standardization documents in all product data prepared under this contract. The product data shall cite the PIN established by the standardization document as the part call out, in the parts list, etc. The standardization document number shall also be shown on the product data (in the parts list, notes, etc.) if it is not discernible from the PIN.

C.5.2.7.2 The contractor shall investigate and convert any Contractor, Supplier, Vendor, or other PINs to the above required standardization document PIN-CAGE format. The contractor can download the Public Logistics Data (PUB LOG) Federal Logistics Information

Services (FLIS) Search at: http://www.dla.mil/HQ/InformationOperations/LogisticsInformationServices/FOIAReading.aspx , for researching part numbers, or contact the Defense Logistics Agency (DLA) customer service at: http://www.dla.mil/CustomerSupport.aspx , for assistance with web access, accounts, or assistance in finding part numbers for products defined by standardization documents.

C.5.2.8 National Stock Numbers (NSNs) and Part or Identifying Numbers (PINs)

C.5.2.8.1 The NSN for items may be cited in the product data in addition to the PIN-CAGE; however, NSNs do not establish unique item identification and shall not be cited within the product data in lieu of the PIN-CAGE.

C.5.2.8.2 NSNs placed within the product data either in lieu of a PIN-CAGE or that conflict with the PIN/CAGE data found in WEBFLIS will be reason for Government rejection of the product data containing the conflicting data, and will be returned to the contractor for correction and re-submittal.

C.5.2.9 Indentured Bill Of Material (IBOM). The contractor shall deliver IBOMs to the Government IAW CDRL A047. The IBOM reflects the parent-child relationship of levels of assembly. A numeric indenture level defines each part's place relative to the top of the structure, i.e., level 0 is the end item system, level 1 is all the first level parts and assemblies, level 2 items are the parts and assemblies under each separate level 1 assembly. IBOMs shall reflect the PIN not the NSN. IBOMs shall include the enterprise identifier

(CAGE) of the design activity for each item in the IBOM.

C.5.3 Configuration Status Accounting. The contractor shall provide CSA reports to the Government IAW CDRL A002. This information shall be recorded and maintained by the contractor for the term of this contract. CSA reports shall provide an audit trail for engineering changes, drawings, associated lists, quality data, logistics data and other technical documentation. CSA reports shall include status of changes and deviations, status of resulting action items, effectivity and incorporation status of approved changes and deviations. As part of the contractors design release configuration process, approved changes shall not be reported to the Government as completed or closed until the new or revised documentation (incorporating the approved change) has been incorporated into the baseline documentation and delivered to the Government IAW CDRL A004.

C.5.4 Change Management/Configuration Control

C.5.4.1 Configuration Control. The Government assumes configuration control of the Type II LEUT at Design Freeze for test in accordance with section C.5.2.3.1. All changes after CDR shall be submitted to the Government for informational purposes only. The contractor shall propose configuration changes to the Type II LEUT via the submission of Engineering Change Proposals (ECPs) or Requests for

Variance (RFVs) IAW the below requirements.

C.5.4.2 Engineering Changes. The contractor shall prepare and submit ECPs for changes to the approved configuration immediately upon determination of a need for such changes. The contractor shall deliver a Notice of Revision (NOR) for each document affected by a change. Specification changes shall also be described on a NOR. Alternatively, a NOR form is not necessary if the documentation (all sheets or pages) is provided and electronically red-lined or otherwise marked-up to clearly show original information and proposed changes IAW CDRL A004 and Attachment 0002 (Data Delivery Description (DDD)).

C.5.4.2.1 Value Engineering Change Proposal. For the life of the contract, when the contractor is interested in proposing a Value

Engineering Change Proposal (VECP), the contractor shall submit a VECP Request to the PCO. The VECP shall be prepared and executed IAW

Attachment 0002 with the additional information required in FAR 52.248-1(c). In accordance with FAR 52.248-1(f), the PCO will consider cost reductions proposed by the contractor and will consider increasing the contractors sharing rate up to 75% on a case by case basis.

(CDRL A004).

12 43

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

C.5.4.2.2 Supporting Data. Sufficient supporting data to evaluate each proposed change shall be submitted with each request. Each change request shall assign a change identifier, justify the need for change, identify the test incident or other event or action that prompted the engineering change, identify proposed effectivity, and all affected impacts (e.g., cost, schedule, requirements, documentation generated to date, tooling design, material orders, quality, provisioning, maintenance, packaging, training).

This is the start of the file's text. The full file is on GovTribe.

File details come from the government source that posted it.