W56HZV17R0065-0001_RFP_Amendment_1.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 Fixed Fee

0001 2017JUN21

W56HZV

U.S. ARMY CONTRACTING COMMAND

WARREN, MICHIGAN 48397-5000

PAMELA SREBERNAK

EMAIL: PAMELA.A.SREBERNAK.CIV@MAIL.MIL

W56HZV-17-R-0065

2017MAY17

X

X 2017JUL18 01:00pm

/SIGNED/

2 signed

SEE SECOND PAGE FOR DESCRIPTION

1 64

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: PAMELA SREBERNAK

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

Type of Contract 1: Cost Plus Fixed Fee

Type of Contract 2: Firm Fixed Price

Kind of Contract: Research and Development Contracts

*** End of Narrative A0000 ***

EXECUTIVE SUMMARY

Common Robotics System-Individual (CRS(I))

A.1 INTRODUCTION

A.1.1 Request for Proposal (RFP) W56HZV-17-R-0065 is hereby issued by Army Contracting Command-Warren (ACC-WRN) for the CRS(I) program.

The CRS(I) is entering the Defense Acquisition Lifecycle at a Milestone B. The contemplated contract is an award of up to two Indefinite

Delivery, Indefinite Quantity (IDIQ) contracts that will have an initial Engineering and Manufacturing Development (EMD) Phase of approximately 18 months (EMD1), during which the contractor(s) will deliver two prototypes that will be tested and evaluated IAW

Attachment 0029, Run0Off Test Plan. The Government will evaluate the results of the Run-Off Test along with revised price proposals to determine which contractor will be awarded a Task Order (TO) for EMD phase (EMD2). The successful contractor will further mature the

CRS(I) during the second phase EMD2, which is approximately 18 months in length. Once EMD is complete, and the CRS(I) design is to a production-ready state, the contract will move into Low Rate Initial Production (LRIP) for two ordering years, followed by Full Rate

Production (FRP) for three ordering years.

A.1.1.1 The Government reserves the right, if only one award is made, to eliminate the requirement for the Run-Off Test. The Government may require submission of a revised price proposal even if the technical portion of the testing is not performed.

A.1.2 This IDIQ has a Minimum Guaranteed Quantity of the initial EMD phase (EMD1), under CLIN 1001. The Maximum quantity on the contract will be established by the Total Evaluated Price (ref. Section M.4.3.2) of an offeror's proposal.

A.1.3 This RFP represents the Army's sole request for this requirement.

A.2 EMD AFFORDABILITY

A.2.1 Any proposal received in response to this RFP that proposes a Cost Plus Fixed Fee in excess of $17,200,000 for EMD Phase 1 will be considered unaffordable and will not be considered for award.

A.2.2 Any proposal received in response to this RFP that proposes a Cost Plus Fixed Fee in excess of $24,000,000 for EMD Phase 2 will be considered unaffordable and will not be considered for award.

A.3 TARGET AVERAGE UNIT MANUFACTURING COST

The CRS(I) production target Average Unit Manufacturing Cost (AUMC) for a CRS(I) System is a maximum $121,000 per unit. The Government is providing the target AUMC for informational purposes only. The CRS(I) System is defined in C.1.2.1, and is a combination of CLIN prices using the ordering approach developed for this requirement (ref. Sec B.1).

A.4 CONTRACT DATA REQUIREMENT LIST (CDRLs)

Contract Data Requirements are contained within Exhibit A. All Exhibit A data items are not separately priced, and will be required throughout the period of performance, in accordance with requirements of individual CDRLs. No separate delivery order will be placed for CDRLs.

A.5 CONTROLLED UNCLASSIFIED INFORMATION

A.5.1 Controlled Unclassified Information (CUI) Request Procedures: This RFP contains CUI that will only be sent to offerors upon an approved request.

A.5.2 Any CUI material held by an offeror not awarded a CRS(I) contract shall be destroyed in accordance with the Controlled

Unclassified Information document provided with the CUI information within 30 days after award of the CRS(I) contract or cancellation of this RFP, and destruction receipts certifying destruction will be provided to the Contracting Officer IAW Section C.4 and 52.211-4072.

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

2 64

W56HZV-17-R-0065 0001

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

with DoD Directive, Distribution Statements on Technical Documents. Attachment 0071 is Classified and must be handled as such (ref:

C.17).

A.5.4 Offerors must also state in their request that the offeror in possession of the documents will comply with the handling requirements of DoDD 5230.24 and DoDD 5230.25.

A.5.5 Requests for CUI documents must made via e-mail to usarmy.detroit.acc.mbx.wrn-crsi@mail.mil with the Subject [Name of Requesting

Firm-Request for CRS(I) CUI Documentation] requests must completely address all information identified below in A.5.6. Incomplete requests will not be considered. The Government reserves the right to request additional information.

A.5.6 Requests for any CUI must clearly state:

- The Company Name and Electronic Mailing Address (must match CAGE code address) where the information is to be sent

- CAGE Code

- Point of Contact (POC) with Telephone Number(s), Datafax Number, and electronic mail Address

- CAGE Code(s) and Address(es) of the Company Facility (Facilities) that will participate in Proposal Preparation and Performance of the

CRS(I)

-In the event an offeror does not possess a CAGE code, the Certification of Proposal Preparation and Performance Facility (Facilities) identifying qualification in accordance with paragraph 3.2 of DoDD 5230.25, Withholding of Unclassified Technical Data from Public

Disclosure for those companies that do not have a CAGE Code assigned must be completed.

A.5.7 Offerors approved to receive the CUI documents will receive an electronic mail from the Government confirming approval of the request. Following approval, the Government will send, via postal mail or an overnight carrier (e.g. FedEx, USPS), the CUI information on a CD-ROM to the address provided in the request, or access to CUI documents through FBO will be granted. Instructions are included in Attachments for requesting materials that must be provided other than through FBO.

A.6 CLASSIFIED INFORMATION

A.6.1 Classified Information Request Procedures: The RFP includes an annex, Attachment 0071, classified at the SECRET level. This annex 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 0034; Continuation sheets are Attachment 0025).

A.6.2 Requests for the classified portion of this RFP must be made by the offeror's Facility Security Officer (FSO) via electronic mail to matthew.g.curis.civ@mail.mil with the subject line "Request for CRSI RFP Classified Annex".

A.6.3 Requests made by persons other than the FSO will not be processed.

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

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

A.6.5 See Section L of this RFP for proposal submission instructions.

A.7 QUESTIONS AND ANSWERS

The Government will accept questions and clarification requests from potential offerors, related to this RFP, through 1500 hours on 27

June 2017 and will post the responses on the Federal Business Opportunities (FBO) website.

*** END OF NARRATIVE A0001 ***

3 64

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

1. The purpose of Amendment 0001 to Solicitation W56HZV-17-R-0065 is to incorporate the following changes:

A. Updated Section A to include: A.6.2 contact information updated, A.7 to extend date to 27 June 2017 to accept questions and clarification requests.

B. Added Section B.4 Contract Phases and Ordering Years language to include B.4.1, B.4.2, B.4.3, B.4.3.1, B.4.3.2, B.4.4, B.4.4.1, B.4.4.2, B.4.4.3, and B.4.4.4.

C. Updated Section C to include: Changed C.7.2.2 to include Key & Certification Management Architecture, added C.7.2.2.1 - Key &

Certification Management Plan, C.7.2.2.2 - Key Certificate specification, C.20.3.1.3 and C.20.3.1.4. Updated Sections C.7.2.5

Cybersecurity Testing, C.18.3 CRS(I) System Fabrication, C.19.1 EMD2, C.19.2.3 User Jury, C.19.3.1 CRS(I) EMD2 Test CRS(I) Systems, C.19.4 EMD Testing & Evaluation (PPQT), C.20.2.3.2 Government Operational Test Readiness Reviews (OTRR), C.20.3.1 Production

Qualification Test (PQGT)/Limited User Test (LUT) Assets, C.20.10.3 CPVT, C.20.10.3.1 Contractor Production Verificaiton Test Plan, C.20.10.4.4.

D. CLIN 2001 - Changed narrative

E. Added CLINs 4008 - LRIP Contractor Manpower Reporting, and 7008 FRP Contractor Manpower Reporting.

F. Changed CDRL A008 to change EMD1 to EMD2 in Block 13.

G. Updated CDRLs Exhibit A to include: A116, A117, and A118.

H. Changed Attachments 0001, 0003, 0005, and 0026 to include the following:

Attachment 0001 - PSPEC to update the definition of Chemical, Biological, Radiation and Nuclear (CBRN) Payload in Section 1.1, JCAUS ICD reference updated in Section 2.2, Updated the following paragraphs: 3.5.2.2, 3.5.2.8.2, CRS-I-PSPEC-1004 at Level 5, 3.5.3.2.1.1.1, 3.5.3.2.1.1.1.1.1, 3.5.3.3.1.1, 3.5.3.3.1.2, 3.5.3.4.4 and 3.5.7.2.1.1.1.

Attachment 0003 - Statement of Work Applicable Documents updated additional standards, starting at DoDI 5200.44, sections added under

"other documents" to include: DoD Cyber Security, CNSS requirements, Cybersecurity control description and assessment, and Army specific requirements for Cyber and INFOSEC.

Attachment 0005 - Integrated Master Plan updated to move IOC after FUE and removes EUA as well as provides test specific changes.

Attachment 0026 - TOGA Partial TDP to update instructions for companies to request the TOGA Partial TDP.

I. Added Attachment 0073 JCAUS ICD CRSI and Attachment 0074 JCAUS ADD 2.0.

J. Added FAR clause 52.237-4000 Contractor Manpower Reporting.

K. Extended the RFP due date until 18 July 2017 at 1300 hours.

*** END OF NARRATIVE A0002 ***

4 64

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

SECTION B - SUPPLIES OR SERVICES AND PRICES/COSTS

Section B narrative

B.1 During Engineering and Manufacturing Development Phase I, the two (2) contractors awarded a Multiple Award IDIQ CRS(I) contract will each be issued a Task Order (TO) for EMD1 requiring the manufacture and delivery of two (2) prototype CRS(I) systems. Each of these TOs constitute the guaranteed minimum quantity, for each contractor, required to satisfy the Government's obligation under the Multiple

Award IDIQ CRS(I) contract in accordance with FAR 16.501-2(b)(3).

Ordering CLINs established for the Low Rate Initial Production (LRIP) and Full Rate Production (FRP) periods will allow the Government to procure different configurations of CRS(I) units and other supporting requirements. The Government has created CLINs based on the requirements of this action, but LRIP and FRP CLINs are structured for an ordering approach based on potential Government needs.

B.1.1 The Government intends to order configurations of CRS(I) units by a combination of the ordering CLINs defined in B.1.2.1 through

B.1.2.7 below. When a combination of CLINs including the Shipping Container defined at B.1.2.6 are simultaneously ordered, the other components ordered under CLINs defined by B.1.2.1 through B.1.2.5, and B.1.2.7, shall be packed in the Shipping Container to create a

CRS(I) unit in a configuration that is defined in Section C.1.2.

B.1.1.1 Except for Section B, the definition of a CRS(I) System in Section C.1.2 applies.

B.1.1.2 When a component of the CRS(I) System references the Performance Specification (PSpec) (Attachment 0001), the definition in the

PSpec takes precedence when a conflict exists.

B.1.2 LRIP and FRP CRS(I) ordering CLINs definitions:

B.1.2.1 The "Mobility Base Platform (MBP)" (CLINs 3001, 4001, 5001, 6001, and 7001) is as stated in the MBP discussion in Section 1.1 of the PSpec. The MBP includes the basic robot/chassis integrated with the audio subsystem, controls, drive cameras, and interfaces for payloads. This is also known as the Mobile Base Platform.

NOTE: Basic Issue Items (BII), the Electronic Technical Manual Digital Video Disk (ETM DVD), the Initial Service Package (ISP) list, and Authorized Stockage List (ASL) shall be included when the MBP is ordered. The MBP CLINs do not include the OCU, Shipping Container, Standard Payload, or other payload capabilities.

B.1.2.2 The "Standard Payload" (CLINs 3002, 4002, 5002, 6002, and 7002) is as stated in the Standard Payload discussion in Section 1.1 of the PSpec. The Standard Payload CLIN includes the Manipulator Arm and other items listed in the Standard Payload discussion in

Section 1.1 of the PSpec.

Note: The Standard Payload CLINs do not include the MBP, OCU, Shipping Container, or other payload capabilities.

B.1.2.3 The "Engineering and Explosive Ordinance Disposal (EOD) Payload" (CLINs 3003, 4003, 5003, 6003, and 7003) includes a scraping/hooking device as stated in the Engineer Payload discussion in Section 1.1 of the PSpec.

NOTE: For this ordering approach, the secondary display will be ordered separately, depending on the requirement of the Government

(ref: B.1.2.7 below). The EOD Payload CLINs do not include the MBP, OCU, Shipping Container, Standard Payload, or other payload capabilities.

B.1.2.4 The "Chemical, Biological, Radiation, and Nuclear (CBRN) Payload" (CLINs 3004, 4004, 5004, 6004, and 7004) includes a universal mounting bracket and other provisions to integrate the CBRN sensors onto the system as stated in the CBRN discussion in Section 1.1 of the PSpec.

NOTE: For this ordering approach, the secondary display will be ordered separately, depending on the requirement of the Government

(ref: B.1.2.7 below). The CBRN Payload CLINs do not include the MBP, OCU, Shipping Container, Standard Payload, or other payload capabilities.

B.1.2.5 The "Operator Control Unit (OCU) " configuration (CLINs 3005, 4005, 5005, 6005, and 7005) includes a hand controller and accessories stated in the OCU and Hand Controller discussion in Section 1.1 of the PSpec.

NOTE: The OCU CLINs do not include the MBP, Shipping Container, Standard Payload, or other payload capabilities.

B.1.2.6 The "Shipping Container" (CLINs 3006, 4006, 5006, 6006, and 7006) is discussed in Section 5 of the PSpec. This shipping container shall be configured to hold a complete CRS(I) System as defined at Section C.1.2.1, including BII, ETM DVD, ISP list, and ASL.

NOTE: The Shipping Container CLINs do not include the MBP, OCU, Standard Payload, or other payload capabilities.

B.1.2.7 The "Secondary Display" (CLINs 3007, 4007, 5007, 6007, and 7007) is discussed in the EOD and CBRN Payloads portions of Section

5 64

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

1.1 of the PSpec. This is ordered separately, as needed, from those payloads to avoid duplicate secondary displays when both EOD and

CBRN payloads are ordered for a CRS(I).

NOTE: Only the Secondary Display is included under these CLINs.

B.1.2.8 The "OCU Configuration Kit" (CLINs 3100 and 5100) includes the OCU (defined in Section 1.1 of the PSpec); a Secondary Display;

BII (this is the same BII as included with B.1.2.1 above); ETM DVD (this is the same as included with B.1.2.1 above); ISP list (this is the same as included with B.1.2.1 above); ASL (this is the same as included with B.1.2.1 above); and, a shipping container that meets the Section 5 PSpec requirements and is sized for the components of the OCU Configuration Kit. The OCU Configuration Kit only contains the items mentioned in this paragraph B.1.2.8.

B.2 CLIN CONTRACT TYPE: Due to contract administration system requirements, the 'CLIN CONTRACT TYPE' is 'Firm Fixed Price' for LRIP and

FRP, but the task orders issued for EMD 1 (CLIN 0001) and EMD 2 (CLIN 0002) are Cost Plus Fixed Fee (CPFF), as noted in those CLIN narratives.

B.3 Cost/Price Worksheet Attachment 0069 will establish cost/price for the CLINs within this section, and will be used by the Government to place orders against an awarded contract.

B.4 Contract Phases and Ordering Years

B.4.1 EMD1, CLIN 1001, is from Contract award through 18 months after Contract award (Days after Contract (DAC)0-546.

B.4.2 EMD2, CLIN 2001, is from 18 months after Contract award through 36 months after contract award (DAC)547-1096.

B.4.3 LRIP will be from 36 months after Contract Award through 60 months after contract award. No LRIP quantities will be ordered until

Milestone C approval is received from the Milestone Decision Authority (MDA).

B.4.3.1 LRIP Ordering Year 1 is the first year after EMD2 ends, and is the fourth year of the contract (DAC 1097-1461).

B.4.3.2 LRIP Ordering Year 2 is the fifth year of the contract (DAC 1462-1826).

B.4.4 FRP will be from 61 months after contract award thru 96 months after contract award. No FRP quantities will be ordered until a

FRP approval is received from the MDA.

B.4.4.1 FRP Ordering Year 1 is the first year after LRIP Ordering Year 2, and is the sixth year of the contract (DAC 1827-2191).

B.4.4.2 FRP Ordering Year 2 is the seventh year of the contract (DAC 2192-2557).

B.4.4.3 FRP Ordering Year 3 is the eighth, and final, year of the contract (DAC 2558-2922).

B.4.4.4 Leap year may impact the DACs for FRP Ordering Years 2 and 3, depending on the actual date of contract award.

*** END OF NARRATIVE B0001 ***

6 64

PIIN/SIIN

Page of

Name of Offeror or Contractor:

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

Reference No. of Document Being Continued

MOD/AMD

2001 EMD 2 _____

Contract Type: Cost Plus Fixed Fee

Reference C.19

Anticipated Quantities as detailed in Cost/Price

Worksheet (Attachment 0069)

PPQT Test Articles = Qty 15 ea

EMD SW (SPAWAR) Assets - SSC Pacific, San Diego, CA =

Qty 1 ea

EMD M/S (TARDEC) Assets - Warren, MI = Qty 1 ea

EMD LOG Assets - Ft. Leonard Wood, MO = Qty 2 ea

EMD Facility Asset-Deliver in Place (Contractor

Facility) = Qty 1 ea

Refurbishment of all EMD 1&2 test assets = Qty 22 ea

Shipment of Test Assets = Qty 22 ea

Engineering & Mfg Development = Qty 1 LO

PPQT(FSR) Test Support = Qty 1 LO

All Other = Qty 1 LO

Inspection/Acceptance = Destination

FOB: Destination

(End of narrative B001)

4008 LRIP - CONTRACTOR MANPOWER REPORTING (CMR) __________________________________________

Ref. FAR 52.237-4000

(End of narrative B001)

7008 FRP - CONTRACTOR MANPOWER REPORTING (CMR) _________________________________________

Ref. FAR 52.237-4000

7 64

PIIN/SIIN

Page of

Name of Offeror or Contractor:

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

Reference No. of Document Being Continued

MOD/AMD

(End of narrative B001)

8 64

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

SECTION C - DESCRIPTION/SPECIFICATIONS/WORK STATEMENT

C.1 General

The Common Robotic System (Individual) (CRS(I)) is a modular system that consists of a robotic platform and a universal controller that provides a multitude of standoff capabilities (in accordance with (IAW) the Performance Specification, (ref. Attachment 0001) to support current and future missions through use of modular payloads and sensor suites for the Army. The universal controller is the Army solution to provide active and passive control for ground and air unmanned systems. The CRS(I) System will support current and future payload missions for the Engineer's area clearance and route clearance platoons, Special Operational Forces (SOF) detachments, and CBRN

(Chemical, Biological, Radiological, or Nuclear) units.

C.1.1 Introduction

This CRS(I) Statement of Work (SOW) includes Engineering, Manufacturing and Development (EMD1, Section C.18 and EMD2, Section C.19), Low

Rate Initial Production (LRIP, Section C.20), and Full Rate Production (FRP, Section C.21) IAW Integrated Master Plan (IMP) (ref.

Attachment 0005). The requirements contained within sections C.1.2 through C.17 describe an overview of the SOW for the overall effort, followed by each SOW for the overall individual phase (EMD1, EMD2, LRIP, and FRP).

C.1.1.1 The EMD1 phase applies to the start of the Engineering and Manufacturing Development at Contract Award through the completion of the Government Run-Off Test (ref. C.18).

C.1.1.2 The EMD2 phase will begin after the down select is completed thru the completion of Pre-Production Qualification Testing (ref.

C.19).

C.1.1.3 The LRIP Phase starts after the completion of EMD2 and include the Production Qualification Test (PQT), Limited User Training

(LUT), and LRIP Production (ref. C.20) which will be for two ordering years.

C.1.1.4 The Full Rate Production (FRP) starts after the completion of LRIP and will include three ordering years for production (ref.

C.21).

C.1.2 Definitions (these definitions come from DoDI 5200.39, which is publically available).

C.1.2.1 The CRS(I) performance requirements are described in the Performance Specification (ref. Attachment 0001). In this SOW, the term CRS(I) System will refer to the Mobile Base Platform (MBP), the Operator Control Unit (OCU), and the module-based payloads to support a variety of missions.

C.1.2.2 The CRS(I) Base configuration includes MBP, OCU, Basic Issue Items (BII), Electronic Technical Manual Digital Video Disk (ETM

DVD), and the shipping container.

C.1.2.2.1 The Standard Payload configuration includes CRS(I) Base plus the Manipulator Arm (MA), integrated end effector, sensors, tether (to assist with subterranean operations), lanyard, integrated illuminator and additional mission specific cameras.

C.1.2.2.2 The Engineer and Explosive Ordnance Disposal (EOD) Payload configuration includes the CRS(I) Base plus the Standard Payload plus the Scraper/Hook and the Secondary Display.

C.1.2.2.3 The Chemical, Biological, Radiation and Nuclear (CBRN) Payload configuration includes the CRS(I) Base plus the Standard

Payload plus a Universal Mounting Bracket and other provisions to integrate the CBRN sensors onto the system.

C.1.2.3 OCU Configuration Kit includes the OCU (consisting of a hand controller, processor, memory, Power Source, Cables and associated items, Radio Subsystem, an interface to an external headset and an interface to an attachable/detachable secondary display), a Secondary

Display, BII, ETM DVD and a shipping container that meets the PSpec and are only for the components for the OCU Configuration Kit.

C.1.2.4 During the LRIP Phase, the Government will perform Production Qualification Test (PQT), which is equivalent to a First Article

Test (FAT). The PQT and FAT nomenclature are interchangeable.

C.1.2.5 Task Order and Delivery Order nomenclature are used interchangeably in the CRS(I) documents. There is no change to the function performed due to the naming convention used under this contract.

C.1.2.6 CRS(I) Aspects

C.1.2.6.1 The term vehicle, as identified throughout this document and support attachments and CDRLs, also means system.

C.1.2.6.2 Mobile Base Platform (MBP). The MBP consists of the basic robot/chassis integrated with the audio subsystem, controls, drive cameras and interfaces for payloads. Mission specific modular payloads are additions to the MBP. The term mobile base platform, as identified throughout this document, the Performance Specification and support attachments and CDRLs, also means mobility base platform.

9 64

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

C.1.2.6.3 Operator Control Unit (OCU). The OCU consists of a computational module, hand controller, display device, power sources and radio subsystems. The OCU shall have the capability to passively receive communications from CRS(I), non-CRS(I) robotic ground and air vehicles, actively control both ground and air vehicle types, and be a modular solution in accordance with Robotics and Autonomous

Systems- Ground (RAS-G) Interoperablity Profile (IOP) (ref. Attachments 0035 - 0044) (ref C.8.1).

C.1.2.6.4 Mission Payloads. Mission specific payloads include Standard, Engineer and Explosive Ordnance Disposal (EOD), and CBRN which are based on the mission profile as described in the Operational Mode Summary/Mission Profile (OMS/MP) (ref. Attachment 0030).

C.1.2.7 Calendar Days. References to days are in calendar days unless otherwise specified. The Government defines business days as

Monday thru Friday except Federal Holidays.

C.1.2.8 Government Approval. Government Approval means approval by the Procuring Contracting Officer (PCO) unless otherwise specified.

C.1.2.9 Handheld-Ground Control Station (H-GCS). H-GCS is defined as the hardware, software, and associated components required to operate a RQ-20B Raven and RQ-11B Puma. The H-GCS will be provided as Government Furnished Property (GFP) (ref. Attachment 0028).

C.1.2.10 Component. A component is a subsystem, assembly, subassembly, or other major element of an end item.

C.1.2.11 Inter-Component Dependancy. An inter-component dependency occurs when components whose behavior or outputs are dependent on the behavior or output of another component.

C.1.2.12 Portability. Portability is the usability of the same software in different computing environments.

C.1.2.13 Scalability. Scalability is the capability of the software program, in whole or in part, to expand over time to support increasing workloads or requirements.

C.1.2.14 Interface. An Interface is the software languages and codes that the application or applications of the overall software solution uses to communicate with each other and with the hardware. It is the shared boundary across which two separate components of a computer system exchange information. Standards-Based Interfaces are those Interfaces defined by Standards-Based organizations.

C.1.2.15 Service-Oriented Architecture. Service-Oriented Architecture is a software design pattern wherein services are provided to the other components by application components, through a communication protocol over a network. The Unmanned Aircraft System (UAS) Control

Segment (UCS) Architecture is an example of a service-based architecture. The World Wide Web (WWW) also operates on a service-based architecture.

C.1.2.16 Refurbishment. An upgrade to a newly improved model, with full remaining or extended lifespan and enhanced capabilities. It is a return to near zero-time maintenance level with incorporation of configuration changes that are included in the configuration, or the intended configuration, of any production items.

C.1.2.17 Critical Program Information (CPI).

C.1.2.17.1 Organic CPI - Unique CPI that is owned and generated by a program.

C.1.2.17.2 Inherited CPI - CPI that is owned and generated by one program, subsystem, or project that is incorporated into and used by another program.

C.1.2.18 The terms "software" and "computer software" are equivalent terms within this contract.

C.1.3 Reserved

C.1.4 Applicable Documents

The Applicable Documents List is available in the SOW Applicable Documents (ref. Attachment 0003).

C.1.5 Requirements

C.1.5.1 CRS(I) System. The contractor shall deliver a CRS(I) System that meets all the performance requirements of the CRS(I)

Performance Specification (ref. Attachment 0001) and this SOW. The contractor shall over-pack a Digital Video Disc (DVD) of the technical manual (ref. C.15.4.1.3.2) with each CRS(I) System.

C.1.5.1.1 Basic Issue Items (BII). The contractor shall provide BII for each production CRS(I) System. The contractor shall over-pack the BII with the CRS(I) System. The BII shall consist of all items essential for an operator or crew to place the CRS(I) System into operation and to accomplish its intended functions as defined in AR 700-18 paragraph 8-5. The contractor shall list BII IAW MIL-STD

40051-2 in the technical manual. The contractor shall deliver the BII List IAW (ref. CDRL A091).

10 64

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

C.1.5.1.2 Initial Service Package (ISP). The contractor shall provide an ISP (ref. CDRL A098) for each CRS(I) System. The contractor shall over-pack the ISP List and components with the production system. The ISP shall consist of all service parts required to perform the first scheduled maintenance. The contractor shall mark each item with nomenclature, part number, and, if applicable, national stock number (NSN) . The NSNs will be provided to the contractor by the Government when marking of the NSN is required.

C.1.5.1.3 Mobile Base Platform (MBP). The contractor shall provide the Mobile Base Platform (MBP), as part of the CRS(I) System, which consists of the basic robot/chassis integrated with the audio subsystem, controls, drive cameras, and interfaces for payloads per the requirements of the CRS(I) Performance Specification (ref. Attachment 0001). Mission specific modular payloads are additions to the

MBP.

C.1.5.1.4 Operator Control Unit (OCU). The contractor shall provide the OCU, as part of the CRS(I) System, which consists of a computational module, hand controller, display device, power sources and radio subsystems in the quantities specified in the task order and per the requirements of the CRS(I) Performance Specification (ref. Attachment 0001).

C.1.5.2 Payload Integration. The contractor shall manufacture and deliver the following Payload Integration:

C.1.5.2.1 Standard Payload. The contractor shall deliver Standard Payload that include all brackets, screws, cables, and other hardware necessary to install the Standard Payload Mission Equipment on the CRS(I) System in the quantities specified in the task order and per the requirements of the CRS(I) Performance Specification (ref. Attachment 0001).

C.1.5.2.2 Engineer and Explosive Ordnance Disposal (EOD) Payload. The contractor shall deliver EOD Payload that include all brackets, screws, cables, and other hardware necessary to install the EOD Payload Mission Equipment on the CRS(I) System in the quantities specified in the task order and per the requirements of the CRS(I) Performance Specification (ref. Attachment 0001).

C.1.5.2.3 Chemical Biological Radiological Nuclear (CBRN) Payload. The contractor shall deliver CBRN Payload that include all brackets, screws, cables, and other hardware necessary to install the below listed CBRN Sensors on the CRS(I) System in the quantities specified in the task order and per the requirements of the CRS(I) Performance Specification (ref. Attachment 0001).

The CBRN Sensors are listed below:

JCAD, M4A1 NSN 6665-01-586-8286

TIC Vapor Detector, Part Number MCB3-0RC178E-DS1

Gas Monitor (CWA), Part Number MCB3-A3C136E-DS1

Radiac Dosimeter GY, Part Number RGU-100-GO

C.1.5.3 Authorized Stockage List (ASL). The contractor shall provide an ASL (ref. CDRL A103) for each production CRS(I) System, unless otherwise specified in the task order. The contractor shall over-pack the ASL with each production system. The ASL shall be comprised of parts that have a production lead time of at least eight months, or are mission essential, to keep the system operational for three months. The contractor shall provide ASL packages in the quantities specified in the task order. The contractor shall mark each item with nomenclature, part number, and NSN.

C.1.5.4 Special Tools Kit. The contractor shall provide a Special Tools Kit in the quantities specified in the task order. The Special

Tools Kit shall contain all Government approved special tools for the CRS(I) System (ref. CDRL A098). The contractor shall provide a unique part number for each part of the overall kit that encompasses all tools within the Special Tools Kit.

C.2 Program Management and Structure

The contractor shall define and ensure Key Roles (e.g. Program Management (PM) and Integrated Product Team (IPT) leads) are staffed with personnel of commensurate education, training, work experience, and technical training necessary to effectively and efficiently perform required tasks. The contractor shall present their organizational Key Roles at the Start of Work Meetings (SOWM1 (C.18) and

SOWM2 (C.19)) and shall discuss the plan for communicating and transitioning personnel changes. When the contractor intends to change the personnel working in Key Roles, the contractor shall provide 14 days notice to the Contracting Officer Representative (COR) prior to the personnel transition unless otherwise authorized. The contractor shall conduct a transition meeting with the Government within seven days of the anticipated transition date to discuss all key issues related to such a transition unless otherwise authorized. The contractor shall provide Minutes (ref. CDRL A002) reporting on any Government concerns or issues discussed in the transition meeting, and providing analysis of actions that the contractor will take to ensure a seamless transition.

C.2.1 Integrated Product Teams (IPTs)

For purposes of this contract, any formal or informal title, (e.g., "Working Group," "Integrated Design Team", etc.) shall be considered an Integrated Product (or Process) Team, or "IPT". IPTs shall be established to serve as the primary contract management tool and key method of communication with the Government for this contract. The first IPT meetings shall be held concurrently with the SOWM.

Subsequent IPT meetings shall be held monthly or as mutually agreed between the Government and contractor. The contractor shall be responsible for developing all IPT agendas (ref. CDRL A001, Conference Agenda) and meeting minutes (ref. CDRL A002). The IPT meeting

11 64

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

minutes shall be made available to the Government and discussed at subsequent IPT meetings. The contractor shall allow physical and dial-in access to the Government for all contractor IPT meetings and any contractor design reviews following the SOWMs.

C.2.1.1 IPT Structure. The IPT structure may include the following teams: Program Management, Business Management, Acquisition, Systems

Engineering, and Supportability & Logistics. Systems Engineering IPT should incorporate the following disciplines: Environmental, Safety, and Occupational Health (ESOH); Human Systems Integration (HSI); Reliability, Availability, Maintainability, and Test (RAM-T);

Risk; Transportability; Corrosion; Software; Quality Assurance; Cybersecurity; and Information Assurance. IPT Leaders shall be identified no later than the SOWMs. The contractor may propose new or modified IPT or changes to the number, composition, functionality, and responsibilities of IPTs at the SOWMs for Government consideration. Proposed changes will be jointly determined thereafter. Throughout the life of this contract, the contractor IPT members shall have the responsibility to participate in new or modified IPTs when needed to focus efforts or improve effectiveness.

C.2.2 Integrated Master Schedule (IMS)

The contractor shall develop and maintain an Integrated Master Schedule (ref. CDRL A003) interoperable with Microsoft Project v2013 by logically networking detailed program activities using the Government provided IMP (ref. Attachment 0005). The IMP outlines the program's major reviews that shall be satisfied to accomplish the work under this contract. The contractor shall report on program progress at each Program Management Review (PMR), Technical Review, and Audit. The contractor shall utilize the IMP and contract deliverable dates to develop their IMS baseline.

C.2.3 Internet-Based Collaboration

The CRS(I) Integrated Data Environment (IDE) is the PdM UGV SharePoint portal, that consists of internet-based collaboration tools

(defined below) that shall be used to facilitate information sharing and collaboration within a secure Government server environment that provides controlled, distributed access to CRS(I) program information, both released and in-work. Types of information that shall be processed and maintained within the IDE will include CRS(I) program documents, reports, program management data, meeting-related information, modeling and simulation/analysis data, manufacturing information, and test data, consistent with the Unmanned Ground

Vehicle Security Classification Guide (ref. Attachment 0006). Any posting to the IDE is considered a data deliverable in the context of

DFARS Data Rights clauses including 252.227-7013 and 252.227-7014. The IDE shall only be used for sharing unclassified/FOUO information. Information regarding the handling of all classified information will be provided at the SOWM1. To access the CRS(I) IDE, contractor associates shall have a DoD approved Public Key Infrastructure credential, obtainable through the DoD External Certification

Authority (ECA) program: http://iase.disa.mil/pki/eca/Pages/certificate.aspx.

C.2.3.1 IDE Notification. The contractor shall notify appropriate Government personnel, Contracting Officer Representative (COR) via e-mail when new or updated documents are posted to the IDE or Sharepoint site. The notification email shall include a hyperlink to the location of the posted content.

C.2.3.2 IDE Collaboration Tools. The contractor shall use the CRS(I) SharePoint server to facilitate unclassified, secure internet-based information sharing between CRS(I) program participants. SharePoint will also serve as the primary means of submitting unclassified/FOUO CDRL items, unless otherwise stated within a specific CDRL item. The contractor shall conduct contractor-Government internet conferencing (web meetings) using Government approved systems such as the Defense Connect Online (DCO) conferencing tool.

Details on specific IDE tools, requirements for access, and approach for use will be discussed at the SOWM1.

C.2.3.3 AKO Sponsor. The contractor shall request Government sponsorship for use of the Army Knowledge Online (AKO), SharePoint, DCO and other required accounts. Details will be provided at the SOWM1. The contractor personnel must be US Citizens in order to obtain sponsorship. The contractor shall provide names, contact information, level of access (upload or download), and training required for personnel requiring access to these tools no later than (NLT) SOWM1 meeting. A signed Non-Disclosure Agreement must also be provided

(ref. Attachment 0002).

C.2.3.4 VISION Digital Library System (VDLS). 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 SOWM1. The contractor shall provide all names, contact information, and level of access (upload or download) IAW VDLS Account Access (ref. Attachment 0004). The list of contractor personnel requiring VDLS access shall be provided to the Government no later than 50 calendar days prior to the Run-Off Test Readiness Review (TRR).

C.2.3.5 External Certification Authority (ECA) Certificates. In order to access these systems, the contractor shall have or obtain

External Certification Authority (ECA) Certificates or DoD Common Access Cards (CAC) as defined in Section C.7.2.1.3.

C.2.4 Data Accessions

The contractor shall identify internal data, which the contractor generates in compliance with the work effort described in this SOW IAW

Data Accessions List (ref. CDRL A029).

C.2.5 Earned Value Management System (EVMS)

12 64

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

In the performance of this contract, the contractor shall use an Earned Value Management System (EVMS) that complies with Table 8, EVM

Application Requirements and Table 9, EVM Report Requirements (Earned Value Management (EVM) Implementation Policy, Enclosure 1) in DoDI

5000.02 (Operation of the Defense Acquisition System), the American National Standards Institute/Electronic Industries Alliance Standard

748 (ANSI/EIA-748), DFARS Clauses 252.234-7001, 252.234-7002, 252.234-7003, and 252.234-7004, and the contractors own documented EVMS

Description. The contractor shall deliver a monthly Integrated Program Management Report (IPMR) (ref. CDRL A085) which shall be directly traceable to the Cost and Software Data Reporting (CSDR), and Bill of Materials (BOM) and be consistent with the Contract Work Breakdown

Structure (CWBS) (ref. CDRL A008).

C.2.5.1 Over-Target Baseline (OTB) or Over-Target Schedule (OTS). In exceptional circumstances indicated by contract performance (per the Contractor's EVMS Description), the contractor shall submit a written request to the PCO for approval to initiate an Over-Target

Baseline (OTB) or Over-Target Schedule (OTS). The request shall include a top-level projection of cost or schedule growth, a recommendation of whether or not performance variances should be retained on record, and a schedule for implementing a new baseline. The contractor shall not implement the OTB or OTS restructuring prior to receiving written approval from the PCO.

C.2.5.2 Application to Subcontractors. The contractor shall flow-down EVM requirements to subcontractors meeting the applicable thresholds per DFARS clauses 252.234-7001, 252.234-7002, 252.234-7003, and 252.234-7004. The performance information reported by the subcontractors shall be incorporated and integrated into the contractor's management system. The contractor shall conduct Integrated

Baseline Reviews (IBRs) on any subcontractors with contracts requiring EVM. Although the Government may attend these IBRs, the actual event shall be the contractor's responsibility.

C.2.6 Bill of Materials (BOM)

The contractor shall deliver a CRS(I) System Bill of Material (BOM) (ref. CDRL A007) which shall be directly traceable to the IPMR and

Cost and Software Data Reporting (CSDR) and be consistent with the Contract Work Breakdown Structure (CWBS) (ref. CDRL A008). The information used to create this CDRL shall be available to the Government and discussed at IPT meetings as well as major reviews IAW the

Government provided IMP (ref. Attachment 0005).

C.2.7 Contract Work Breakdown Structure (CWBS) Index and Dictionary

The contractor shall produce, deliver, and maintain a product oriented Contract Work Breakdown Structure (CWBS) Index and Dictionary IAW the CSDR Plan (ref. Attachment 0032). The CWBS Index and Dictionary shall be completed to the level specified by the CSDR Plan (ref.

Attachment 0032 and CDRL A008). The contractor may tailor the CSDR Plan WBS by additional lower level elements. The information used to create CWBS (ref. CDRL A008) shall be available to the Government and discussed at IPT meetings as well as major reviews IAW the

Government provided IMP (ref. Attachment 0005).

C.2.8 Contract Funds Status Report (CFSR)

The contractor shall prepare, update, and submit the Contract Funds Status Report (CFSR) (ref. CDRL A006).

C.2.9 Cost and Software Data Reporting (CSDR)

The contractor shall prepare and submit Cost and Software Data Reporting (CSDR) Reports IAW CDRL A008, CDRL A114 (DD Form 1921), CDRL

A115 (DD Form1921-1), Attachment 0032 (DD Form 2794), the CSDR Manual (DoDM 5000.04-M-1), and DoDI 5000.02. CSDR reporting is required to include reporting against any and all costs expended by the contractor during the execution of this contract.

C.2.9.1 CSDR Readiness Review

The contractor shall host a CSDR Readiness Review meeting during the Start of Work Meeting with the Government prior to the CSDR Post

Award Meeting. The purpose of the CSDR Readiness Review meeting is to prepare for the CSDR Post Award Meeting. At the CSDR Readiness

Review meeting, the contractor shall present its plan for implementing the CSDR requirements. The contractor shall: (1) describe the process to be used to satisfy the requirements of the CSDR Manual (DoD 5000.04-M-1), the CSDR Plan (ref. Attachment 0032), and the CDRLs listed in Exhibit A along with their associated data item descriptions (DIDs); (2) demonstrate how contractor cost and data reporting

(CCDR) will be based, to the maximum extent possible, upon actual cost transactions and not cost allocations; (3) demonstrate how the data from its accounting system will be mapped into the CWBS included in the CSDR Plan (ref. Attachment 0032) and into the standard reporting categories required in the CCDR data item descriptions; (4) describe how recurring and nonrecurring costs will be segregated;

(5) explain the methodology for reporting completed units on the DD Form 1921 reports; and (6) explain the traceability of data reported on CSDR, IPMR and BOM CDRLs (ref. CDRL A008, CDRL A114 (DD Form 1921), CDRL A115 (DD Form1921-1), Attachment 0032 (DD Form 2794), CDRL

A085, and CDRL A007).

C.2.9.2 CSDR Post Award Meeting

The contractor shall participate in the CSDR Post Award Meeting with the Government Cost Working Group Integrated Product Team (CWIPT).

Prior to this meeting, the contractor shall make any adjustments or corrections identified during the CSDR Readiness Review meeting. The

CSDR Post Award meeting shall be held NLT 75 calendar days after contract award. At this meeting, the contractor shall present its plan for implementing the CSDR requirements. The contractor shall: (1) describe the process to be used to satisfy the requirements of the

13 64

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

CSDR Manual (DoD 5000.04-M-1), the CSDR Plan (ref. Attachment 0032) and the CDRLs listed in Exhibit A and associated data item descriptions (DIDs); demonstrate how contractor cost and data reporting (CCDR) will be based, to the maximum extent possible, upon actual cost transactions and not cost allocations; (2) demonstrate how the data from its accounting system will be mapped into the WBS included in the CSDR Plan (ref. Attachment 0032) and into the standard reporting categories required in the CCDR data item descriptions;

(3) describe how recurring and nonrecurring costs will be segregated; (4) explain the methodology for reporting completed units on the

DD Form 1921 reports; and (5) explain the traceability of data reported on CSDR, IPMR and BOM CDRLs (ref. CDRL A008, CDRL A114(DD Form

1921), CDRL A115 (DD Form1921-1), Attachment 0032 (DD Form 2794), CDRL A085, and CDRL A007). For planning purposes, the CSDR Post Award meeting is anticipated to be a one day and will likely be held in the in the Metropolitan Detroit area.

C.2.9.3 Cost Data Summary Report

The contractor shall prepare and submit the Cost Data Summary Report (DD Form 1921) which reports direct and indirect actual cost data on both a recurring and non-recurring basis by CWBS level as specified in the CSDR Plan (ref. Attachment 0032). (CDRL A114, DD Form

1921)

C.2.9.4 Functional Cost-Hour Report

The contractor shall prepare and submit a Functional Cost-Hour Report (DD Form 1921-1) which reports resources including labor hours, overhead costs, material costs, and other direct and indirect cost data on both a recurring and non-recurring basis by CWBS level as specified in the CSDR Plan (Attachment 0032). (CDRL A115, DD Form 1921-1.

C.3 Meetings, Audits, Assessments, and Reviews

C.3.1 Participation/Administration

The contractor shall host, unless otherwise specified in the paragraphs below, all…