W56HZV15R0156-0003.pdf

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

2. Amendment/Modification No.

3. Effective Date

4. Requisition/Purchase Req No.

5. Project No. (If applicable)

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

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

9A. Amendment Of Solicitation No.

9B. Dated (See Item 11)

10A. Modification Of Contract/Order No.

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

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

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

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

(a) By completing items 8 and 15, and returning ____________ copies of the amendments: (b) By acknowledging receipt of this amendment on each copy of the offer submitted; or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. Accounting And Appropriation Data (If required)

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

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

A. This Change Order is Issued Pursuant To: The Changes Set Forth In Item 14 Are Made In

The Contract/Order No. In Item 10A.

B. The Above Numbered Contract/Order Is Modified To Reflect The Administrative Changes (such as changes in paying office, appropriation data, etc.) Set

Forth In Item 14, Pursuant To The Authority of FAR 43.103(b).

C. This Supplemental Agreement Is Entered Into Pursuant To Authority Of:

D. Other (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, is required to sign this document and return _______________ copies to the Issuing Office.

14. Description Of Amendment/Modification (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

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

15A. Name And Title Of Signer (Type or print)

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

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

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

NSN 7540-01-152-8070

PREVIOUS EDITIONS UNUSABLE

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

Prescribed by GSA FAR (48 CFR) 53.243

SEE SCHEDULE

X

Cost Plus Incentive Fee (Cost Based)

0003 2017JUL10

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

/SIGNED/

2 signed

SEE SECOND PAGE FOR DESCRIPTION

1 92

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 0003 to solicitation W56HZV15R0156 is as follows:

1. Section A.1.2.3 is revised as follows:

From: 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.

To: The Government will utilize a technical incentive during EMD to incentivize technical performance based on the parameter of wireless

Line of Sight (LOS) range. 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.

2. Section C.6.11 Key Management is added to the Solicitation as follows:

C.6.11.1 Key and Certificate Management Architecture (KCMA)

The contractor shall deliver a Key and Certificate Management Architecture (KCMA) IAW CDRL A133.

C.6.11.2 Key and Certificate Management Plan (KCMP)

The contractor shall deliver a Key and Certificate Management Plan (KCMP) IAW CDRL A134.

3. Section C. 13.3.4 is revised as follows:

From: Upon determining that the required support equipment and tools are within the sources (C.11.2.5.2) Selection Criteria, the __________

Contractor shall list those items IAW CDRL A123 Maintenance, Test, and Support Equipment Requirements List (MTSERL).

To: Upon determining that the required support equipment and tools are within the sources (C.13.3.3) Selection Criteria, the Contractor ________ shall list those items IAW CDRL A123 Maintenance, Test, and Support Equipment Requirements List (MTSERL).

4. Section C.21.15.2 is revised as follows:

From: The Contractor shall update the SAC system delivered in EMD for Government Modeling & Simulation to the initial and final product baselines at the Government laboratory located in Warren, Michigan.

To: The Contractor shall update the SAC system delivered in EMD for Government Modeling & Simulation to the initial and final product baselines at the Government laboratory located in Warren, Michigan. For the initial product baseline, the Contractor shall update the ___________________________________________________________________

SAC system in the first LRIP Option. For the final product baseline, the Contractor shall update the SAC system in the second LRIP____________________________________________________________________________________________________________________________________

Option._______

5. Section L.3.3.4. is revised to add "The Offeror shall provide"

6. CDRL A133 Key and Certificate Management Architecture (KCMA)is added to Exhibit A Contract Data Requirements List (CDRLs).

2 92

W56HZV-15-R-0156 0003

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

7. CDRL A134 Key and Certificate Management Plan (KCMP)is added to Exhibit A Contract Data Requirements List (CDRLs).

8. The following Attachment 0001 - Performance Specification P-Specs contain changes to:

Section 3:

P-Spec-3245

P-spec-540

P-Spec-517

P-Spec-315

P-Spec-374

P-Spec-351

P-Spec-358

P-Spec-3196

P-Spec-3225

P-Spec-3226

P-Spec-889

P-Spec-587

P-Spec-603

P-Spec-2856

P-Spec-2612

P-Spec-3186

P-Spec-598

P-Spec-366

P-Spec-496

P-Spec-650

P-Spec-651

P-Spec-2920

P-Spec-3290 (a new requirement)

Section 4:

P-Spec-643

P-Spec-2938

9. Attachment 0008 is revised to include the scheduled delivery of Government Furnished Property (GFP).

10. Attachment 0015 is revised to include the scheduled delivery of Government Furnished Property (GFP).

11.Amendment 0002 contained the following addition in Attachment 0017 - RCIS Type I Test and Evaluation Master Plan (TEMP) Section

1.2.3. Based on the threat, the RCIS Type I may be required to be operated in the unmanned mode during route clearance movements. __________________________________________________________________________________________________________________________

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

*** END OF NARRATIVE A0004 ***

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

3 92

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

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

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

4 92

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

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.

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:

5 92

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

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)

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

6 92

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

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 ***

7 92

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).

8 92

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

9 92

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

10 92

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. The Contractor shall present technical issues in terms of performance goals, exit criteria, schedule progress, risks and mitigation, and cost impact.

C.3.5.2 Systems Engineering IPT Meetings

The Contractor shall conduct System Engineering (SE) IPT meetings every two weeks beginning after the SOWM to discuss the technical planning and execution of SAC system analysis, design, development, and integration activities. The Contractor shall address specialty topics at SE IPT meetings to include corrosion prevention and control, program protection, and cybersecurity. The Contractor shall complete assigned action items and discuss information related to the development of technical documentation.

C.3.5.3 Logistics Guidance Review

The Contractor shall conduct a Logistics Guidance Review to address Logistics Management data and products. The conference shall be in conjunction with the SOWM.

C.3.5.4 Software IPT Meetings

The Contractor shall conduct Software IPT meetings every two weeks beginning after the SOWM to discuss the design and development of the

SAC System computer software. The Contractor shall address all software-related topics at Software IPT meetings to include software metrics, software quality, software configuration management, software testing, Interoperability Profile (IOP) and software stress testing, cybersecurity, and software system safety. The Contractor shall discuss information related to the development of software documentation and complete assigned action items identified at the meetings.

C.3.5.5 System Safety IPT Meetings

The Contractor shall conduct monthly System Safety IPT meetings beginning after the SOWM to ensure all Environment, Safety, and

Occupational Health (ESOH) issues and hazards are identified and addressed. The Contractor shall present ESOH program status and updates, safety and design data, Hazard Tracking System (HTS) status and updates, software system safety, and other relevant ESOH data.

The Contractor shall discuss information related to the development of ESOH documentation and complete assigned action items identified at the meetings.

C.3.5.6 Human Systems Integration (HSI) IPT Meetings

The Contractor shall conduct monthly HSI IPT meetings jointly with the System Safety IPT meetings (IAW C.3.5.5) providing HSI integration system status, HSI event findings, discuss any updates to the HSI issues database, recommendations and design data. The

Contractor shall be prepared for detailed discussion of these topics. The meetings shall include Contractor HSI personnel and working level IPT personnel. The Contractor shall address HSI domains of safety, health hazards, human factors engineering, soldier survivability, manpower, personnel and training. The Contractor shall address HSI database issues in terms of risk assessment, mitigation, cost, and identification of organization and personnel responsible for a resource schedule to resolve issues (Ref Section

C.12.3 HSI Issue Database).

11 92

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

C.3.5.7 Corrosion Prevention Advisory Team (CPAT) Meetings

The Contractor shall conduct CPAT meetings, complete assigned action items, and inform the CPAT of corrosion issues and their impact on the corrosion prevention and control of the SAC system. CPAT meetings will be held as part of System Engineering IPT meetings.

C.3.5.8 Test and Evaluation Working-level Integrated Product Team (T&E WIPT)

The Contractor shall provide an engineering representative to the Government-led T&E WIPT to plan and support Contractor and Government test activities. The primary purpose of the RCIS Type I T&E WIPT is to optimize the use of T&E expertise, instrumentation, facilities, Modeling and Simulation (M&S), and the collected resources of the represented agencies and organizations to integrate the collective T&E efforts. The primary product of the T&E WIPT is the program test strategy, which is captured in the RCIS Type I Test and Evaluation

Master Plan (TEMP), Attachment 0017. The T&E WIPT shall meet every two weeks beginning after the SOWM and be the instrument that will tailor the T&E tools and strategy to maximize effectiveness and efficiency of the test procedures, while determining which specific tests are required to support the RCIS Type I assessment for approval and systems safety certification.

C.3.5.9 Program Protection Meetings

The Contractor shall conduct Program Protection meetings, complete action items as assigned in the Program Protection Meetings, and inform the Government of issues and their impact on the SAC system. The Contractor shall ensure any updated assumptions, rationale, and results related to criticality analysis, vulnerability assessments and risk evaluations, as well as supply chain risk information and mitigation are made available for Government review at the program protection meetings. The meetings will be held as part of System

Engineering IPT meetings.

C.3.5.10 System Safety and Environmental Working Group (SSEWG)

The Contractor shall participate via teleconference in the Government RCIS Type I SSEWG IAW Task 105 of MIL-STD-882E, which is comprised of SMEs from the Contractor and Government communities whose primary focus is to ensure all ESOH issues and hazards are identified and addressed. The Contractor shall support the SSEWG by attending meetings, completing assigned action items identified at the meetings, and discussing information related to the development of ESOH documentation. Virtual or telecommunication or both attendance is acceptable. During SSEWG meetings, the Contractor shall present ESOH program status and updates, safety and design data, Hazard Tracking

System (HTS) status and updates, and other relevant ESOH data. SSEWG meetings will be held on a quarterly basis.

C.3.5.11 Corrective Action Review Team (CART) Meetings

The Corrective Action Review Team (CART), is the Government group responsible for reviewing the Contractors corrective actions on Test

Deficiencies or Failures (C.16.6), and providing approval for Failure Analysis and Corrective Action Reports (FACARs) IAW CDRL A066. The

Government will chair the CART meetings. The CART meetings will be bi-weekly, one-day events. The Government will provide official notification on all CART Meeting schedules at the inception of each test project. The Contractor's corrective action team shall attend the CART meetings and directly correlate with the Government CART members, to reflect all relevant CART functions including Quality, Reliability and Maintainability (R&M), Logistics, Maintenance, Systems Engineering, Safety, Transportability and HSI/Human Factors.The

Contractor shall present root cause analysis, Corrective Actions and FACARs for discussion at the CART meetings.

C.4 SYSTEMS ENGINEERING

C.4.1 Systems Engineering Management Plan (SEMP)

The Contractor shall prepare and execute a SEMP detailing the systems engineering process for developing the SAC system. The SEMP shall also include the approach for Open Systems Architecture (C.4.6), and plans for Cybersecurity (C.6.1), Configuration Management (C.7.2) and Risk Management (C.9.1). The Contractor shall describe in its SEMP the internal processes that it will use to prepare for and conduct the technical reviews and audits. The Contractor shall prepare and deliver the SEMP IAW CDRL A004 Systems Engineering

Management Plan (SEMP).

C.4.2 System/Subsystem/Component Specification (SSS)

The Contractor shall develop and deliver system, subsystem, and component specifications IAW CDRL A005 System/Subsystem/Component

Specification for the SAC system. The System, Subsystem and Component Specifications shall be derived from and trace to the RCIS P-Spec

(Attachment 0001). The System, Subsystem and Component Specifications shall represent performance requirements of the RCIS Type I at the end of the EMD phase.

C.4.3 Requirements Compliance Matrix (RCM)

The Contractor shall develop, deliver and update a Requirements Compliance Matrix (RCM) IAW CDRL A006 Requirements Compliance Matrix

(RCM) that assesses compliance towards achieving all RCIS Performance Specification (Attachment 0001) requirements. The RCM shall trace to the RCIS Performance Specification (Attachment 0001) and include information supporting each requirements assessment. The RCM shall include P-Spec ID, P-Spec Requirement, Compliance Assessment (Meets Requirement, Partially Meets Requirement, Does Not Meet

Requirement), and Compliance Rationale to include supporting data that describes the analysis that has been done to support the assessment. The RCM shall include all related data including analysis, simulation, drawings, schematics, functional diagrams, and test results and describe how the data supports the assessed compliance.

C.4.4 System/Subsystem Design Description (SSDD)

The Contractor shall develop and deliver a System/Subsystem Design Description (SSDD) IAW CDRL A007 System/Subsystem Design Description

(SSDD) for the SAC system. The SSDD shall break down the system into Hardware/Software Configuration Items and how those components

12 92

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

interface with each other to meet the system level requirements as defined in the SSS IAW C.4.2.

C.4.5 Interface Control Documents (ICDs)

The Contractor shall prepare, deliver and update Interface Control Documents (ICDs) IAW CDRL A008 Interface Control Documents (ICDs) that identify the interface requirements between: Hardware Configuration Items (HWCI) (HWCI to HWCI); Computer Software Configuration

Items (CSCI) and hardware configuration items (CSCI to HWCI); and HWCI and CSCI to systems external to the SAC system.

C.4.6 Open Systems Architecture

The Contractor shall define and follow an open systems architecture for using modular designs with open standards and published interfaces while limiting the use of proprietary solutions. The Contractor shall document its open systems approach in its SEMP (C.4.1).

The Contractor shall demonstrate compliance with its open systems architecture during formal technical reviews and audits per Section

C.3.4.

C.4.7 Robotics and Autonomous Systems - Ground (RAS-G) Interoperability Profile (IOP)

The Contractor shall utilize the Robotics and Autonomous Systems - Ground (RAS-G) Interoperability Profile (IOP) v2 (Attachment 0014) and RCIS IOP Instantiation (Attachment 0026) in the design and build of the SAC system for RCIS Type I. If the use of the RAS-G IOP, in whole or in part, does not support the Contractor's implementation, the Contractor shall provide a non-proprietary interface description with electrical, signal, mechanical, connector, and digital message…