W56HZV15R0156-_Amendment_0002.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

Cost Plus Incentive Fee (Cost Based)

0002 2017JUN27

W56HZV

U.S. ARMY CONTRACTING COMMAND

WARREN, MICHIGAN 48397-5000

CARRIE ENGLISH

EMAIL: CARRIE.L.ENGLISH.CIV@MAIL.MIL

W56HZV-15-R-0156

2017MAY16

X

X 2017AUG07 12:00pm

/SIGNED/

2 signed

SEE SECOND PAGE FOR DESCRIPTION

1 105

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: CARRIE ENGLISH

Buyer Office Symbol/Telephone Number: CCTA-HCP-D/(586)282-7404

Type of Contract 1: Cost Plus Incentive Fee (Cost Based)

Type of Contract 2: Cost Plus Fixed Fee

Kind of Contract: Research and Development Contracts

*** End of Narrative A0000 ***

The purpose of amendment 0002 to solicitation W56HZV15R0156 is as follows:

1. To extend the proposal closing date as follows:

From: 12:00PM on 2017 Jul 05

To: 12:00PM on 2017 Aug 07

2. Add Clause 252.227-7018, Rights in Noncommercial Technical Data and Computer Software - Small Business Innovative Research (SBIR)

Program (FEB 2014).

3. Add Clause 252.227-7038, Patent RightsOwnership by the Contractor (Large Business) (JUN 2012).

4. Clause 52.219-9, Small Business Subcontracting Plan is changed:

From: 52.219-9, Small Business Subcontracting Plan NOV/2016.

TO: 52.219-9, Small Business Subcontracting Plan (JAN 2017) Alternate II (Nov 2016).

5. Acronymn in Section A.1.2.3.1 is changed as follows:

From: The Government is providing the EMD and AMUC target estimates for informational purposes only. ____

To: The Government is providing the EMD and AUMC target estimates for informational purposes only. ____

6. Section A.1.3.2 subtitle is changed as follows:

From: A.1.3.2 Assertion of Restriction

To:A.1.3.2 Assertion of Restrictions and Identification of Commercial Items ______________________________________

7. Section A.1.3.2 removes a sentence as follows:

From: A.1.3.2.1 DFARS 252.227-7017 is included in the solicitation. The Offeror shall make and submit signed assertions (as to the restrictions on data rights) with Commercial Tech Data and Commercial Computer Software (SW), Attachment 0060 and Identification and

Assertion of Restrictions, Attachment 0061 to its proposal. The assertions will become an attachment to the resulting contract.

Offerors are not required, either as a condition of being responsive to a solicitation or as a condition for award, to sell or otherwise_________________________________________________________________________________________________________________________________________ relinquish to the Government any rights in technical data related to items, components or processes developed exclusively at private_____________________________________________________________________________________________________________________________________ expense, except for the data identified at DFARS 227.7103-5(a).________________________________________________________________

To: A.1.3.2.1 DFARS 252.227-7017 is included in the solicitation. The Offeror shall make and submit signed assertions (as to the restrictions on data rights) with Commercial Tech Data and Commercial Computer Software (SW), Attachment 0060 and Identification and

Assertion of Restrictions, Attachment 0061 to its proposal. The assertions will become an attachment to the resulting contract.

8. Section A.1.6.2 is changed as follows:

From: There are documents within the RFP that are marked Distribution Statement C and D. In order to obtain access to these documents an

Offeror must have a Federal Business Opportunities (FedBizOpps) account. The Offeror is responsible for obtaining the appropriate export ________________________________________________________________ licenses, or process the appropriate export license exemption, necessary for authorization to share any such information with______________________________________________________________________________________________________________________________ subcontractors that are foreign persons/entities as defined in applicable export laws and regulations, or to obtain access to the files________________________________________________________________________________________________________________________________________ themselves.___________

To: A.1.6.2 There are documents within the RFP that are marked Distribution Statement C and D. The Offeror is responsible for following _________________________________________

2 105

W56HZV-15-R-0156 0002

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

DoD Instruction - 5230.24. In order to obtain access to these documents an Offeror must have a Federal Business Opportunities___________________________

(FedBizOpps) account.

9. Section A.1.6.3 is changed as follows:

From: A.1.6.3 The pictures from the October 12-13, 2016 RCIS Type I Vehicle Viewing have a Distribution A statement. Please note that _________________ some of the RCIS HMEE CAD Models and Data Information are marked as Distribution D and contain technical data whose export is restricted_________________________________________________________________________________________________________________________________________ by the Arms Export Control Act (Title 22, U.S.C., Sec 2751, et seq.) or the Export Administration Act of 1979, as amended, (Title 50,______________________________________________________________________________________________________________________________________

U.S.C., App. 2401 et seq.).____________________________

To: A.1.6.3 The pictures from the October 12-13, 2016 RCIS Type I Vehicle Viewing have a Distribution A statement.

10. Section A.1.6.4 is changed as follows:

From: A.1.6.4 The Department of Defense and U.S. DoD Contractors wishing to receive the RCIS Vehicle Viewing Pictures and HMEE CAD

Models and Data Information must follow the instructions below. The documents will be sent to Department of Defense and U.S. DoD

Contractors upon verification and approval via U.S. mail, or Fed-Ex. Requests for these documents shall be referred to the attention of ________________________ the Contract Specialist, Carrie English.

To: A.1.6.4 The Department of Defense and U.S. DoD Contractors wishing to receive the RCIS Vehicle Viewing Pictures and HMEE CAD Models and Data Information must follow the instructions below. The documents will be sent to Department of Defense and U.S. DoD Contractors upon verification and approval via U.S. mail, Fed-Ex or AMRDEC Safe Access File Exchange (SAFE). Requests for these documents shall be __________________________________________________________________ referred to the attention of the Contract Specialist, Carrie English.

11. Section A.1.6.7 is changed as follows:

From: Offerors approved to receive the RCIS HMEE CAD Models and Data Information documents will receive two CD-ROMs: One for the RCIS

Type I Vehicle Viewing pictures - Distribution A and one RCIS HMEE CAD Models and Data Information Distribution D. Following approval, the Government will send the CD-ROMs to the address provided in the request.

To: Offerors approved to receive the RCIS HMEE CAD Models and Data Information documents will receive two CD-ROMs: One for the RCIS Type

I Vehicle Viewing pictures - Distribution A and one RCIS HMEE CAD Models and Data Information Distribution D. Following approval, the

Government will send the CD-ROMs or AMRDEC Safe Access File Exchange (SAFE) to the address provided in the request. ____________________________________________

12. Section A.1.6.10 is removed from the solicitation.

A.1.6.10 In addition, certain attachments to the RFP have limited distribution and/or export controlled statements in accordance with

DoD Directive 5230.4, Distribution Statements on Technical Documents and DoD Directive 5230.25, Withholding of Unclassified Technical

Data from Public Disclosure. The most restricted level of distribution on CUI is Distribution Statement D.

13. Section A.1.9.1 is changed as follows:

From: The Government is releasing the RFP package with sufficient detail to prepare a proposal. However, the Government will accept questions during the Request for Proposal (RFP) process via RCIS TYPE I Mailbox for 20 calendar days after the release of the RFP. _________________________________________________

To: The Government is releasing the RFP package with sufficient detail to prepare a proposal. However, the Government will accept questions during the Request for Proposal (RFP) process via RCIS TYPE I Mailbox through July 14, 2017. _____________________

14. Section C.13.2.7.6 is changed as follows:

From: The Contractor shall submit deliver all data, to include EDFP, with conforming markings as described in DFARS 252.227-7013. The ______

Government will reject any markings on data that do not conform to the markings described in DFARS 252.227-7013. The Contractor shall rework at no expense to the Government. The Government will not allow any statements or markings that claim to limit the Governments use _________________________________________________________________________________________________ of the drawing other than the limited rights restrictive legend or Government purpose rights restrictive legend and the Government___________________________________________________________________________________________________________________________________ directed distribution statement. The Contractor shall submit the EDFP IAW CDRL A046, Engineering Data For Provisioning (EDFP)._________________________________

To: The Contractor shall deliver all data, to include EDFP, with conforming markings as described in DFARS 252.227-7013. The Government _______ will reject any markings on data that do not conform to the markings described in DFARS 252.227-7013. The Contractor shall rework at no expense to the Government. The Contractor shall submit the EDFP IAW CDRL A046, Engineering Data For Provisioning (EDFP).

15. Section H.5.1 b is changed as follows:

From: The TM option may be exercised at any time but not later than 1672 calendar days after contract award. The TDP option may be exercised at any time but not later than 2037 calendar days after contract award.

3 105

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

To: This contract requires delivery of Technical Manuals, Training Material, and other data necessary for operation, maintenance, ______________________________________________________________________________________________________________________________ installation, or training (other than detailed manufacturing or process data). These items shall be delivered with Unlimited Rights and________________________________________________________________________________________________________________________________________

Unrestricted Rights IAW DFARS 252.227-7013 and 252.227-7015. The TM option may be exercised at any time but not later than 1672 calendar_____________________________________________________________ days after contract award. The TDP option may be exercised at any time but not later than 2037 calendar days after contract award.

16. Section H.14 is added to the solicitation.

H.14 commercial computer software (including Open Source Software(OSS)

Use of Open Source Software Without Delivery. The Government treats Open Source Software (OSS) as a category of commercial computer software. If the Offeror proposes to deliver OSS while performing under the Contract, the Contractor shall follow the same rules as prescribed in this provision as for commercial computer software. Additionally, if the Offeror proposes to use, but not deliver, commercial computer software (including OSS), the Contractor must ensure that such use does not: (i) create, or purport to create, any

Government distribution obligations with respect to the computer software deliverables; or (ii) grant, or purport to grant, to any third party any rights to or immunities under Government intellectual property or Government data rights to the Government computer software deliverables.

17. The Offeror's proposal quantiity in Section L.2.1.1 is changed:

From: Quantity 1

To: Quantity 3 _

18. Section L..3.5.6 is changed as follows:

From: Assertion of Restrictions. The Offeror shall include in its proposal submission, each of the following: Completed Attachment 0060

Commercial Tech Data and Commercial Computer SW and Attachment 0061 Identification and Assertion of Restrictions IAW DFARS 252.227-

7017. Omission of restrictions applicable to Attachment 0060 and 0061 will bar the Offeror from asserting such a restriction upon delivery of the data, unless the omission would analogously qualify for the allowable post-award presentations based on the conditions _______________________________________ provided in subsection (e) of either DFARS Provision 252.227-7013 or 252.227-7014.

To: Assertion of Restrictions and Identification of Commercial Items. The Offeror shall include in its proposal submission, each of the ______________________________________ following: Completed Attachment 0060 Commercial Tech Data and Commercial Computer SW and Attachment 0061 Identification and Assertion of Restrictions IAW DFARS 252.227-7017. Omission of restrictions applicable to Attachment 0060 and 0061 will bar the Offeror from asserting such a restriction upon delivery of the data, unless for the allowable post-award presentations based on the conditions provided in subsection (e) of either DFARS Provision 252.227-7013 or 252.227-7014.

19. Section M.3.4.1 Evaluation of Factor 2: Past Performance is changed as follows:

From: The Past Performance Factor evaluation will assess the expectation that the Offeror will successfully meet the RCIS Type I contract requirements based on the Offerors record of past performance on recent and relevant contract performance to the considerations listed in L.3.2.1.1.This assessment will result in the application of a Confidence Rating which will be based upon the extent to which _________ recent prior past performance is relevant to the requirements listed in L.3.2.1.1. _________

To:The Past Performance Factor evaluation will assess the expectation that the Offeror will successfully meet the RCIS Type I contract requirements based on the Offerors record of past performance on recent and relevant contract performance to the considerations listed in L.3.2.2.This assessment will result in the application of a Confidence Rating which will be based upon the extent to which _______ recent prior past performance is relevant to the requirements listed in L.3.2.2. _______

20. The "draft" watermark is removed from Attachment 0017 - RCIS Type I Test and Evaluation Master Plan (TEMP). This changes the version date as follows:

From: 22 Feb 2017 # of Pages 98

To: 13 Jun 2017 # of Pages 101

21. Attachment 0035 - Past Performance Relevancy Matrix, Relevance consideration Work Scopes Tab item b) is changed:

From: Provide Field Level Maintenance to include replacement of defective parts and preventative maintenance, returning repaired equipment to the Soldier and providing support for crew, unit and selected Direct Support (DS) maintenance tasks.

To: Provide a Logistics Support Activity (LOGSA) authenticated Operator and Maintenance Technical Manual. _____________________________________________________________________________________________

This changes the version date as follows:

From: 24 Mar 2017 # of Pages 4

To: 15 Jun 2017 # of Pages 4

4 105

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

22. The "draft" watermark is removed from Exhibit A - Contract Data Requirements List(CDRL). This changes the version date as follows:

From: 16 Dec 2015 # of Pages 141

To: 15 Jun 2017 # of Pages 140

23. All other terms and conditions of Solicitation W56HZV1R0156 remain unchanged.

*** END OF NARRATIVE A0003 ***

EXECUTIVE SUMMARY

Route Clearance Interrogation System (RCIS) Type I

REQUEST FOR PROPOSAL (RFP) # W56HZV-15-R-0156

A.1 INTRODUCTION

A.1.1 The Route Clearance Interrogation System (RCIS) capability provides a solution to mitigate gaps identified in Explosive Hazards

Defeat Initial Capabilities Document (ICD); Joint Requirements Oversight Council Memorandum (JROCM) 095-06; and Mobility Through Urban and Complex Terrain (MTUCT) ICD, Catalog of Approved Requirements Documents (CARDS) #06058. This Army requirement comes from the

Product Manager (PdM) Applique and Large Unmanned Ground Systems (ALUGS) and PdM Combat Engineer and Materiel Handling Equipment

(CE/MHE). The RCIS Type I system includes a Delta High Mobility Engineer Excavator (D-HMEE) with mounted and dismounted Operator

Control Unit (OCU) capability, assigned to the Clearance Company and Brigade Engineer Battalion (BEB) Construction Company. The RCIS

Type I Program is entering the Defense Acquisition Lifecycle at Engineering and Manufacturing Development (EMD). This acquisition includes EMD, Low Rate Initial Production (LRIP), Full Rate Production (FRP), Technical Manual (TM) - Final Reproducible Copy, Interim

Contractor Support (ICS), System Technical Support (STS), Total Package Fielding (TPF) and Technical Data Package (TDP) and Computer

Software. The resulting contract including options is for a period of up to six years and seven months (79 months total). First Article

Testing will be conducted under LRIP.

A.1.2 RCIS TYPE I PROGRAM OVERVIEW

A.1.2.1 The Government intends to award a single contract with a base period of performance of 31 months of EMD.

A.1.2.2 The Government will utilize a cost incentive during EMD as set forth in FAR clause 52.216-10 (Incentive Fee). The contractor will propose target cost, cost of money, and target fee. The Government established a 50/50 share ratio for overruns and a 70/30 share line for underruns, with a 2% minimum and 12% maximum fee. The EMD effort also includes a separately priced Contract Line Item Number

(CLIN) for Field Service Representative (FSR) support on a Cost Plus Fixed Fee (CPFF) basis.

A.1.2.3 The Government will utilize a technical incentive during EMD to incentivize technical performance based on the parameter of wireless Line of Sight (LOS) range. This requirement aligns to the Performance Specification 3.3.6.2 and to Key Performance Parameter

(KPP) 3 for Semi-Autonomous Control (SAC). The technical performance incentive will be separate from the fee associated with the cost incentive. The contractors fee will be increased by up to 2.5% of EMD CLIN 1000AA proposed price (target cost + target fee) in accordance with the Measurement scale listed in H.6.1.3 if its RCIS Type I achieves the performance IAW the criteria in Section

H.6.1.3.1.1.

A.1.2.3.1 The Government's total target estimate for the RCIS Type I Engineering and Manufacturing Development (EMD) phase is

$12,200,000 in Then-Year dollars for efforts specified in this request for proposal. The estimated funding profile for this effort in

Then Year Dollars is $3,350,000 (FY18); $4,520,000 (FY19); $4,330,000 (FY20). The Government's target estimated Average Unit

Manufacturing Cost (AUMC) for RCIS Type I is $189,520 in Base Year FY17 dollars per unit. The Government is providing the EMD and AUMC target estimates for informational purposes only. Proposals will be evaluated in accordance with Sections L and M of this request for proposal.

A.1.2.4 The contract will also include two Fixed Price Incentive Firm (FPIF) LRIP options for 12 months each and two FPIF Full Rate

Production (FRP) options for 12 months each. The Government established a 30/70 share ratio for underruns and a 30/70 share line for overruns IAW FAR clause 52.216-16 Incentive Price Revision Firm target, in no event shall the total final price of these items exceed the ceiling price of 120% of the proposed target cost. The contract will also include CPFF Level of Effort (LOE) CLINs for two Interim

Contractor Support (ICS) options, each option is for 12 months; two System Technical Support (STS) options, each option is for 12 months; two Total Package Fielding (TPF) options, each option is for 12 months and one Firm Fixed Price (FFP) Technical Manuals (TM) -

Final Reproducible Copy and one FFP Technical Data Package (TDP)and Computer Software option.

Contract QTY Deliverable CLIN CLIN Type Performance

Period

EMD 7 (6) Prototype RCIS 1000AA CPIF 31 Months

Type Is, 1 SAC (stand alone) and 1 radio set

5 105

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

EMD FSR Support 1 Field Support Rep 1100AA CPFF 31 Months

(FSR) Support

LRIP Option 1 10 LRIP RCIS Type I 2001AA FPIF 12 Months

LRIP Option 2 12 LRIP RCIS Type I 2002AA FPIF 12 Months

TM Option 1 SAC System TMs 3001AA FFP 24 Months

FRP Option 1 48 FRP RCIS Type 1 4001AA FPIF 12 Months

FRP Option 2 56 FRP RCIS Type 1 4002AA FPIF 12 Months

TFP Option 1 20,000 Man Hours Fielding Support 5001AA CPFF LOE Term 12 Months

(not-to-exceed) Services

TFP Option 2 20,000 Man Hours Fielding Support 5002AA CPFF LOE Term 12 Months

(not-to-exceed) Services

ICS Option 1 15,000 Man Hours Fielding Support 6001AA CPFF LOE Term 12 Months

(not-to-exceed) Services

ICS Option 2 15,000 Man Hours Fielding Support 6002AA CPFF LOE Term 12 Months

(not-to-exceed) Services

STS Option 1 7,500 Man Hours Fielding Support 7001AA CPFF LOE Term 12 Months

(not-to-exceed) Services

STS Option 2 7,500 Man Hours Fielding Support 7002AA CPFF LOE Term 12 Months

(not-to-exceed) Services

TDP and 1 RCIS Type I TDP 8001AA FFP 12 Months

Computer Software Option

A.1.3 PROPOSAL SUBMISSION REQUIRMENTS

A.1.3.1 Proposals shall follow all instructions in Section L.

A.1.3.2 Assertion of Restrictions and Identification of Commercial Items

A.1.3.2.1 DFARS 252.227-7017 is included in the solicitation. The Offeror shall make and submit signed assertions (as to the restrictions on data rights) with Commercial Tech Data and Commercial Computer Software (SW), Attachment 0060 and Identification and

Assertion of Restrictions, Attachment 0061 to its proposal. The assertions will become an attachment to the resulting contract.

A.1.3.2.2 RCIS Technical Data and Computer Software Rights Evaluation Spreadsheet, Attachment 0033 will be utilized for the purposes of evaluation only to identify and evaluate TDP and Computer Software Assertion of Restrictions and must contain the same assertions and restrictions listed in Attachment 0060 and Attachment 0061.

A.1.4 PRODUCTION QUANTITIES AND DELIVERY REQUIREMENTS

A.1.4.1 CLINs 1000AA, 2001AA, 2002AA, 4001AA and 4002AA of the solicitation provide EMD, LRIP and FRP quantities for the base award and options. During LRIP Option One, the Contractor shall develop the first six LRIP units by removing the six SAC systems, delivered during

EMD, upgrading these SAC systems to the Initial Product Baseline utilizing LRIP components, and re-integrate to the Government furnished

D-HMEE vehicles and MPCVs under EMD (CLIN 1000AA) as part of the 10 RCIS Type Is delivered under LRIP I (CLIN 2001AA) IAW Performance

Work Statement (PWS) C.21.15.1.1.1. See Sections B and F of the solicitation for details relating to vehicle delivery, inspection and acceptance.

A.1.5 SYSTEM ACCEPTANCE

A.1.5.1 Prior to successful completion of the First Article Approval LRIP requirements, acceptance of the LRIP RCIS Type Is shall be conditional and based off the Governments LRIP Pre-Test Readiness Review (pre-TRR) approval and TRR delivery (C.21.3.4.5.1 Contractor

Conducted Pre-Test Readiness Review). At the time of conditional acceptance, prior to first article approval, the Contractor shall invoice for 100% system unit price. The Administrative Contracting Officer (ACO) will withhold 40% (forty percent) of the total system price from the payment. The Contractor shall submit a request for final acceptance when all First Article Approval requirements IAW

C.21.16.1 are met, the contractor has refurbished the LRIP systems, and the Final Inspection Record (FIR) is complete. Upon final acceptance of the RCIS Type I, the PCO will authorize release of the payment withhold. See Section E of the solicitation for details relating to Conditional Acceptance of Test Assets, Final Acceptance Request and Manufacturing Standards.

A.1.6 ACCESS TO SOLICITATION DOCUMENTS

A.1.6.1 ACCESS TO CONTROLLED UNCLASSIFIED INFORMATION & DISTRIBUTION C and D ATTACHMENTS

A.1.6.2 There are documents within the RFP that are marked Distribution Statement C and D. The Offeror is responsible for following DoD

Instruction - 5230.24. In order to obtain access to these documents an Offeror must have a Federal Business Opportunities (FedBizOpps) account.

A.1.6.3 The pictures from the October 12-13, 2016 RCIS Type I Vehicle Viewing have a Distribution A statement.

6 105

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

A.1.6.4 The Department of Defense and U.S. DoD Contractors wishing to receive the RCIS Vehicle Viewing Pictures and HMEE CAD Models and

Data Information must follow the instructions below. The documents will be sent to Department of Defense and U.S. DoD Contractors upon verification and approval via U.S. mail, Fed-Ex or AMRDEC Safe Access File Exchange (SAFE). Requests for these documents shall be referred to the attention of the Contract Specialist, Carrie English.

A.1.6.5 Offerors must submit the following information via email to Mrs. Carrie English at carrie.l.english.civ@mail.mil. One individual per company CAGE code will be permitted to receive the requested RCIS Vehicle Viewing Pictures and HMEE CAD Models and Data Information.

Telephone requests will not be accepted.

1. Individuals full name

2. Company name

3. Company CAGE Code

4. Physical Address

5. Identify if your company is a U.S. based firm or a non-U.S. based firm and identify the country location.

6. Are you a Department of Defense employee or a U.S. DoD Contractor?

A.1.6.6 Offerors must indicate RCIS Vehicle Pictures and HMEE CAD Models and Data Info Request in the email subject line when submitting a RCIS Vehicle Viewing Pictures and HMEE CAD Models and Data Information request.

A.1.6.7 Offerors approved to receive the RCIS HMEE CAD Models and Data Information documents will receive two CD-ROMs: One for the RCIS

Type I Vehicle Viewing pictures - Distribution A and one RCIS HMEE CAD Models and Data Information Distribution D. Following approval, the Government will send the CD-ROMs or AMRDEC Safe Access File Exchange (SAFE) to the address provided in the request.

A.1.6.8 Controlled Unclassified Information (CUI) Request Procedures: This RFP contains CUI that can only be viewed from the sensitive/secured side of FedBiz Opps. The below Attachments contain CUI:

Attachment 0001: RCIS Performance Specification

Attachment 0002: D-HMEE Physical Interface Control Document (ICD)

Attachment 0003: D-HMEE Robotic Interface ICD

Attachment 0004: RCIS Control Vehicle ICD (MPCV)

Attachment 0005: RCIS Operational Mode Summary - Mission Profile (OMS-MP)

Attachment 0010: RCIS Pre-TRR Checklist

Attachment 0013: RCIS Type I Failure Definition Scoring Criteria (FDSC)

Attachment 0017: RCIS Test Evaluation Master Plan

Attachment 0018: RCIS Type I Test Summary

Attachment 0019: RCIS STRAP

Attachment 0026: RCIS IOP Instantiation

Attachment 0027: Robotic and Automated Systems - Ground Security Classification Guide (RAS-G SCG) Attachment 0029: Fielding Location and

Schedule

Attachment 0031: SSv PAL w References

Attachment 0041: PEO CSCSS Armoring Systems Security Classification Guide

Attachment 0042: PEO CSCSS OPSEC Plan

* RCIS HMEE CAD Models and Data Information are Distribution D statements

A.1.6.9. Any CUI material held by an Offeror not awarded an RCIS Type I contract shall be destroyed in accordance with Department of

Defense Manual (DoDM) 5200.01-V4. The unsuccessful Offeror shall use DA Form 3964 to document destruction and shall provide this to the

Contracting Officer.

A.1.7 CLASSIFIED INFORMATION

A .1.7.1 Classified Information Request Procedures: The RFP includes, Preliminary System Analysis Attachment 0059, classified at the

SECRET level. The Preliminary System Analysis will only be released to Offerors holding the appropriate Facility Clearance (FCL). All classified material must be handled in accordance with the National Industrial Security Program Operating Manual (NISPOM), DoD 5220.22-M and the DD-254 for this RFP (Attachment 0024).

A.1.7.2 Requests for the classified portion of this RFP must be made by the Offeror's Facility Security Officer (FSO) via electronic mail to carrie.l.english.civ@mail.mil with the subject line "Request for RCIS Type I RFP Classified Document". Requests made by persons other than the FSO will not be processed.

The following information must be provided in the request and must match the Offeror's information in the Industrial Security Facilities

Database (ISFD):

-The Company Name and Classified Mailing Address

-CAGE Code

-Name of FSO with Telephone Number, Datafax Number, and Electronic Mail Address and Secret Internet Protocol Router Network (SIPRNet)

7 105

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

Electronic Mail Address

-CAGE Code(s) and Address(es) of the Company Facility (Facilities) intended to participate in Proposal Preparation and Performance of the RCIS Type I Program where classified information will be utilized.

A.1.7.3 All classified material held shall be handled and destroyed in accordance with the DD-254 (Attachment 0024).

A.1.8 ORGANIZATIONAL CONFLICTS OF INTEREST (OCI)

A.1.8.1 A potential OCI as defined in FAR Subpart 9.5 has been identified and is anticipated to occur if the performance of work under contract W56HZV-14-C-0154 is not completed prior to the release of the RFP for the Route Clearance Interrogation System (RCIS) Type I

Vehicle.

A .1.8.2 In order to eliminate an actual OCI, J C Bamford Excavators LTC (JCB) is prohibited from participating as a prime or subcontractor, or as a consultant to any third party in the RCIS Type I RFP W56HZV-15-R-0156 or the resultant contract. JCB is the

Original Equipment Manufacturer (OEM) of the High Mobility Engineer Excavator (HMEE). See Section H of this RFP for the full OCI information.

A.1.9 MANAGING RESPONSES AND QUESTIONS IN RCIS TYPE I MAILBOX

A.1.9.1 The Government is releasing the RFP package with sufficient detail to prepare a proposal. However, the Government will accept questions during the Request for Proposal (RFP) process via RCIS TYPE I Mailbox through July 14, 2017.

A.1.9.2 RCIS TYPE I Mailbox is: usarmy.detroit.acc.mbx.wrn-rcis@mail.mil

A.1.10 EXTENSION REQUESTS

A.1.10.1 Contractors shall ensure that they allocate enough time in their proposal preparation schedules for requesting Government documents before proposals are due. Lack of planning does not constitute a reason for extending the solicitation or accepting late proposals.

A.1.11 POST RFP CONFERENCE

A.1.11.1 A Post RFP Proposal Conference is NOT going to occur following solicitation release.

*** END OF NARRATIVE A0001 ***

8 105

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

SECTION C - DESCRIPTION/SPECIFICATIONS/WORK STATEMENT

Performance Work Statement (PWS)

C.1 RCIS Type I

C.1.1 Introduction

This Performance Work Statement (PWS) encompasses the Engineering and Manufacturing Development (EMD) (C.1.2-C.20), Low Rate Initial

Production (LRIP) Options (C.21), Full Rate Production (FRP) Options (C.22), Total Package Fielding Options (C.23), Technical Data

Package (TDP) Option (C.24), the System Technical Support (STS) Options (C.25) and Interim Contractor Support Options (C.26), of the

Route Clearance & Interrogation System (RCIS) Type I program.

C.1.1.1 Definitions

C.1.1.1.1 High Mobility Engineer Excavator (HMEE): a 15-ton construction tractor capable of high speed with a front loader and backhoe bucket on a boom arm, able to self-deploy with military convoys.

C.1.1.1.2 Delta HMEE (D-HMEE): a HMEE modified with electronic control of automotive and interrogation functions to enable unmanned operation; also includes additional interrogation attachments (air spade, rake and spork, and clamshell bucket).

C.1.1.1.3 Buffalo Mine Protected Clearance Vehicle (MPCV): a 24 ton wheeled armored vehicle in the Mine-Resistant Ambush-Protected

(MRAP) Family of Vehicles (FoV) used for route clearance missions.

C.1.1.1.4 RCIS HMEE (R-HMEE): a D-HMEE integrated with Semi-autonomous Control (SAC) system components capable of manned and unmanned operation.

C.1.1.1.5 SAC System: a robotics applique kit consisting of a Mobile Base Unit (MBU) integrated on the D-HMEE and Operator Control Unit

(OCU) integrated on the MPCV enabling unmanned control of the R-HMEE by an operator in the MPCV. The operator can remove the OCU from the MPCV and control the R-HMEE while dismounted.

C.1.1.1.6 Control Vehicle: a Buffalo MPCV integrated with SAC system components enabling an operator to control the R-HMEE in the unmanned mode.

C.1.1.1.7 RCIS Type I: a system consisting of an R-HMEE and Control Vehicle used during route clearance missions.

C.1.1.1.8 Commercial Item: As defined by Federal Acquisition Regulation (FAR) Subpart 2.1 Definitions.

C.1.1.1.9 Commercially available off-the-shelf (COTS): As defined by FAR Subpart 2.1 Definitions.

C.1.1.2 Applicable Documents

C.1.1.2.1 A list of the documents applicable to this PWS is contained in Attachment 11, Performance Work Statement Applicable Documents.

C.1.1.3 System Overview

C.1.1.3.1 The RCIS Type I shall enable a Soldier to excavate, interrogate, and classify deep buried explosive hazards, Improvised

Explosive Devices (IEDs), and caches in a wide range of road surfaces and soil conditions, as well as clear routes by moving explosive hazards, debris and rubble, and filling potholes. The RCIS Type I shall operate in two different modes: a manned mode operated by a

Soldier in the R-HMEE and an unmanned mode operated by a Soldier in a separate Control Vehicle or in a dismounted position.

C.1.1.3.2 The RCIS Type I shall employ two R-HMEE vehicle configurations: an unarmored configuration and, an armored configuration with its Crew Protective Kit (CPK). The RCIS Type I shall provide various attachments including a front loader, backhoe bucket, clamshell bucket, rake and spork, air spade, classification camera, light and measurement devices to enable a Soldier to perform interrogation tasks.

C.1.1.3.3 The RCIS Type I shall include a SAC system that provides the capability to control the R-HMEE and attachments in the unmanned mode. The SAC system shall also be capable of providing control of classification capabilities in the manned mode.

C.1.2 Engineering Manufacturing and Design (EMD):

C.1.2.1 For EMD, the Contractor shall design, develop, and deliver RCIS Type Is and all associated deliverables in accordance with (IAW) the Performance Specification for RCIS Type I (Attachment 0001), hereafter referred to as the RCIS P-Spec, and sections C.2 through C.20 of the PWS. For information regarding RCIS Type I missions refer to the Operational Mode Summary / Mission Profile (OMS/MP) (Attachment

0005).

9 105

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

C.1.2.1.1 The Contractor shall integrate SAC system components onto six D-HMEE vehicles IAW the D-HMEE Physical Interface Control

Document (ICD) (Attachment 0002) and D-HMEE Robotic Interface ICD (Attachment 0003).

C.1.2.1.2 The Contractor shall integrate SAC system components onto six Control Vehicles, specifically the Buffalo MPCV, IAW the RCIS

Control Vehicle ICD (MPCV) (Attachment 0004).

C.2 PROGRAM STRUCTURE AND MANAGEMENT

C.2.1 The Contractor shall present its organizational key roles at the Start of Work Meeting (SOWM). When the Contractor intends to change the personnel working in key roles, the Contractor shall provide ten business days notice via email to the Contracting Officer

Representative (COR).

C.2.2 Integrated Product Teams (IPTs)

For purposes of this contract, any joint deliberative or task-focused body, regardless of its formal or informal title will be considered an Integrated Product (or Process) Team, or "IPT". The Contractor shall establish IPTs to serve as a tool to manage performance under this PWS and as a key method of communication for this contract.

C.2.3 Integrated Master Schedule (IMS)

The Contractor shall develop and maintain the projects Integrated Master Schedule (IMS) detailing program activities using the

Government provided RCIS Program Plan (Attachment 0015) as a guide. The IMS shall be delivered IAW Contract Data Requirements List

(CDRL) Integrated Master Schedule (IMS) (CDRL A001).

C.2.4 Work Breakdown Structure (WBS)

The Contractor shall use the RCIS Type I Work Breakdown Structure (WBS) (Attachment 0006) for preparation of the Contract Work Breakdown

Structure (CWBS). The CWBS shall be developed using the latest version of MIL-STD-881, Work Breakdown Structures for Defense Materiel

Items, as guidance and continue the WBS numbering scheme to decompose the CWBS to level 5 or lower. The Contractor shall deliver its

CWBS IAW Contract Work Breakdown Structure (CWBS), CDRL A002.

C.2.5 Contract Funds Status Report

The Contractor shall prepare, update and submit the Contract Funds Status Report (CFSR) IAW CDRL A003.

C.2.6 Internet-Based Collaboration

C.2.6.1 The Contractor shall notify the COR via email within 24 hours of submission of new or updated documents being posted to the RCIS

Integrated Data Environment (IDE) (C.8.2). The notification email shall include a web address or link to the location of the posted content.

C.2.6.2 The Contractor shall use Versatile Information Systems Integrated On-Line Nationwide (VISION), VISION Digital Library System

(VDLS) to access data from Government testing. Details on specific tools, requirements for access, and approach for use will be discussed at the Start of Work Meeting (SOWM) (reference C.16.6.1 VISION).

C.2.6.3 The Government will sponsor Contractor personnel access to Army Knowledge Online (AKO), Product Manager (PdM) Applique and Large

Unmanned Ground Systems (ALUGS) Portal, Defense Collaboration Services (DCS), and VDLS. The Government can only sponsor accounts for

U.S. Citizens.

C.2.6.4 To access the Government information systems cited in this contract, the Contractor shall have or obtain a DoD approved Public

Key Infrastructure credential for all personnel who require access. Credentials include External Certification Authority (ECA)

Certificates and Department of Defense (DoD) Common Access Cards (CAC). The Contractor shall designate an Information Assurance (IA)

Officer to work with PdM ALUGS and the Government Information Systems Security Manager (ISSM) to implement usage of the ECA and 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. Details on the ECA program and authorized ECA vendors can be found at: http://iase.disa.mil/pki/eca/.

C.2.6.5 Earned Value Management System (EVMS)

In the performance of this contract, the Contractor shall use an EVMS that complies with DFARS 252.234-7002, Earned Value Management

System, Table 8 (EVM Requirements) in DoDI 5000.02 (Operation of the Defense Acquisition System) and the Contractors own documented EVMS

Description. The Contractor shall deliver a monthly Integrated Program Management Report (IPMR), IAW CDRL A110.

C.3 MEETINGS/AUDITS/ASSESSMENTS/REVIEWS

C.3.1 Participation/Administration

The Contractor shall host, unless otherwise specified in the paragraphs below, all meetings, audits, assessments, and reviews. The

Contractor's hosting duties and responsibilities shall include sending invitations and providing the necessary facilities, media resources, security, minutes, and hard copy materials related to the preparation and execution of the meetings, audits, assessments, and

10 105

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

reviews. The Contractor shall provide teleconference and Defense Collaboration Services (DCS) access to the Government for all meetings, audits, assessments, and reviews. When agreed upon by the Government, the Contractor shall schedule face-to-face meetings for multiple topics to minimize personnel resources and travel expenses.

C.3.1.1 Agenda and Read-Ahead Packages

The Contractor shall submit an agenda and read-ahead package, IAW Conference Agenda (CDRL A071), prior to all meetings, audits, assessments, and reviews in Section C.3.

C.3.1.2 Minutes

The Contractor shall record and submit minutes IAW Meeting Minutes (CDRL A070) for all meetings, audits, assessments, and reviews in

Section C.3 and as otherwise called out in this contract. The Contractor shall identify its recorder at the beginning of each event.

C.3.1.3 Program Information

Information developed on this contract shall be made available by the Contractor electronically to the COR for discussion during all meetings including program reviews and meetings, technical reviews and audits, and IPT meetings IAW C.3.

C.3.2 Start of Work Meeting (SOWM)

The Contractor shall conduct a SOWM at the Contractors facility within 20 business days after contract award. This meeting will introduce and align the Government and Contractor teams. The SOWM will consist of a Contractual Obligations review, a System

Requirements Review (SRR), an IMS Review, and a Logistics Guidance Review. For planning purposes, the participants should anticipate this SOWM to be a consecutive two-day event.

C.3.3 Program Management Reviews (PMR)

The Contractor shall conduct quarterly PMRs, beginning with the first quarter after contract award. The PMRs shall include Contractor senior-level program management personnel. The Contractor shall present cost, schedule, performance, and risk status at each PMR and be prepared for detailed discussion with the Government. The Contractor shall present issues in terms of performance goals, exit criteria, schedule progress, risks and mitigation, and cost impact. For planning purposes, the participants should anticipate these meetings to be a one-day event.

C.3.4 Technical Reviews and Audits

C.3.4.1 The Contractor shall conduct program technical reviews and audits IAW the IMS (CDRL A001). The Technical Review Criteria

(Attachment 0009) provides high-level entrance and exit criteria for each technical review and audits. For the System Requirements

Review (SRR) detailed in C.3.4.4, the Contractor shall finalize entrance and exit criteria jointly with the COR at least 10 business days prior to the SOWM. For all other technical reviews and audits, the Contractor shall finalize entrance and exit criteria jointly with the COR at least 20 business days prior to the associated technical review or audit. The Contractor shall remedy all unsatisfactory entrance criteria prior to entry into each technical review and audit.

C.3.4.2 The Contractor shall document the proceedings of all technical reviews and audits IAW Meeting Minutes CDRL A070. The Contractor shall document all action items that result from the technical reviews and audits in the Meeting Minutes.

C.3.4.3 The Procurement Contracting Officer (PCO) has the sole authority to certify, through written authorization, the successful completion of each technical review or audit. Successful completion of a technical review or audit is required to proceed to the next technical review or audit.

C.3.4.4 System Requirements Review (SRR)

The Contractor shall conduct the SRR in conjunction with the SOWM (Section C.3.2). The SRR shall be conducted IAW the Defense

Acquisition Guidebook (DAG) dated 15 May 2013, Section 4.2.10 System Requirements Review. The SRR shall be a line-by-line review of the

RCIS P-Spec (Attachment 0001).

C.3.4.5 Preliminary Design Review (PDR)

The Contractor shall conduct a PDR at the Contractors site no later than 3 months after contract award. The PDR shall be conducted IAW the DAG dated 15 May 2013, Section 4.2.12 Preliminary Design Review. The Contractor shall establish the SAC system allocated baseline as defined in DAG Section 4.2.12. For planning purposes, participants should anticipate this meeting to be a consecutive two-day event.

C.3.4.6 Critical Design Review (CDR)

The Contractor shall conduct a CDR at the Contractors site no later than 9 months after contract award. The CDR shall be conducted IAW the DAG dated 15 May 2013, Section 4.2.13 Critical Design Review. The Contractor shall establish the initial product baseline as defined in DAG Section 4.2.13. For planning purposes, participants should anticipate this meeting to be a consecutive two-day event.

C.3.4.7 Test Readiness Reviews (TRR)

C.3.4.7.1 Contractor Conducted Pre-Test Readiness Review (pre-TRR)

The Contractor shall conduct a Pre-TRR to present to the Government the readiness of the RCIS Type Is to enter into Government system level testing. The Pre-TRR shall be held at the Contractors site no later than -15 months after contract award. The Pre-TRR shall

11 105

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

address the content detailed in the Technical Review Criteria (Attachment 0009) and the RCIS Pre-TRR Checklist (Attachment 0010). For planning purposes, participants should anticipate this meeting to be a consecutive two-day event.

C.3.4.7.2 Government Conducted Test Readiness Reviews (TRR)

The Contractor shall attend the Government TRR to be conducted at Aberdeen Proving Ground (APG). The Government TRR is anticipated to be held no more than 15.5 months after contract award. The Contractor shall be prepared to brief and display all of the information the

Contractor prepared for the Pre-TRR to the Government. The Government TRR will assess both the Contractor's and the Government's test readiness. For planning purposes, participants should anticipate this meeting to be a one-day event.

C.3.4.7.3 Operational Test Readiness Review

The Contractor shall attend the Government Operational Test Readiness Review (OTRR), conducted at or in the vicinity of Operational Test and Evaluation site and be prepared to brief and display all of the information the Contractor prepared for the Pre-TRR and TRR. The

Government OTRR is anticipated to be a one day event and held no less than seven days prior to entering Limited User Test (LUT) and will assess readiness to enter LUT.

C.3.4.8 System Verification Review (SVR) and Functional Configuration Audit (FCA)

The Contractor shall conduct a SVR/FCA at the Contractor site after completion of all EMD testing. The SVR/FCA shall be conducted IAW the DAG dated 15 May 2013, Section 4.2.14 System Verification Review/ Functional Configuration Audit. For planning purposes, participants should anticipate this meeting to be a consecutive two-day event.

C.3.4.9 Production Readiness Review (PRR)

The Contractor shall conduct a PRR at the Contractor site after completion of SVR/FCA IAW the Contractors IMS (CDRL A001). The PRR shall be conducted IAW the DAG dated 15 May 2013, Section 4.2.15 Production Readiness Review. For planning purposes, participants should anticipate this meeting to be a one-day event.

C.3.5 Integrated Product Team (IPT) Meetings

C.3.5.1 Program Management Integrated Product Team (PM IPT) Meetings

The Contractor shall conduct monthly PM IPT meetings at the Program Officer level and below. If mutually agreed to by the parties, the

Contractor may conduct additional PM IPT meetings. The PM IPT meetings shall commence the month following the SOWM. The Contractor shall be prepared for detailed discussion on cost, schedule, performance, and risk status.