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

0006 2017AUG03

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 21

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

1. Section L.2.2.1.2 Acceptable File Formats is changed as follows:

FROM: All electronic information provided in response to the solicitation shall be provided in Microsoft (MS) Office 2013 or PDF compatible format or except as noted in instructions for individual volumes.

TO: All electronic information provided in response to the solicitation shall be provided in Microsoft (MS) Office 2013 or PDF compatible format or except as noted in instructions for individual volumes. No videos may be attached as any part of the proposal ______________________________________________________ submission media. Video files will not be accepted as any part of the proposal submission.__________________________________________________________________________________________

2. Section M.3.5.2.6 Data and Computer Software Rights in Resulting Contract is changed as follows:

FROM: The Offeror selected for award will have Attachment 0060 Commercial Tech Data and Commercial Computer SW and Attachment 0061

Identification and Assertion of Restrictionsincorporated in Section J of the contract. The contractor shall deliver a TDP and computer ________________________________________________ software with restrictive markings, if any, conforming to Attachment 0060 Commercial Tech Data and Commercial Computer SW and Attachment_________________________________________________________________________________________________________________________________________

0061 Identification and Assertion of Restrictions. In the event an Offeror does not agree to incorporate the proposed Attachment 0060_________________________________________________

Commercial Tech Data and Commercial Computer SW and Attachment 0061 Identification and Assertion of Restrictions, into the resulting contract, the Offeror will not be credited with the Data and Computer Software Rights Adjustment.

TO: The Offeror selected for award will have Attachment 0060 Commercial Tech Data and Commercial Computer SW and Attachment 0061

Identification and Assertion of Restrictions incorporated in Section J of the contract. Markings on deliverables shall be IAW DFARS ____________________________________________ clauses including 252.227-7013 and 252.227-7014. In the event an Offeror does not agree to incorporate the proposed Attachment 0060_______________________________________________

Commercial Tech Data and Commercial Computer SW and Attachment 0061 Identification and Assertion of Restrictions, into the resulting contract, the Offeror will not be credited with the Data and Computer Software Rights Adjustment.

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

*** END OF NARRATIVE A0007 ***

2 21

W56HZV-15-R-0156 0006

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

SECTION L - INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS

L.1 General Proposal Information

L.1.1 The proposal, subject to the Submission, Modification, Revision, and Withdrawal of Proposals paragraph of Instructions to

Offeror(s) Competitive Acquisitions (FAR Provision 52.215-1(c), ALT I) contained in Section L of the solicitation, shall be submitted in the format and quantities set forth below. All information necessary for the review and evaluation of a proposal is to be contained in the proposal volumes set forth below. Section M of the solicitation sets forth the evaluation criteria and delineates the Factors to be evaluated and their relative order of importance. The Offerors proposal, as required by this section, shall be evaluated as set forth in Section M of this solicitation. The Government will not assume the Offeror possesses any capability, understanding, or commitment not specified in its proposal. It is an Offerors responsibility to submit a well-written proposal, with adequately detailed information, which clearly demonstrates an understanding of and the ability to comply with the solicitation requirements to allow for a meaningful evaluation. The Government does not assume the duty to search for data to cure problems it finds in proposals.

L.2 Proposal Content, Format and Instructions

L.2.1 Proposal Content

L.2.1.1 All proposals shall be in English (American Standard) and shall be in US dollars. The proposal shall include all information specified and address all requirements outlined in Section L. The Offeror's proposal shall be submitted in five separate volumes as set forth below. The Offerors proposal shall consist of the following volumes:

Volume

Number Title Quantity

Volume 1 Design 3

Volume 2 Past Performance 3

Volume 3 Cost/Price 3

Volume 4 Small Business Participation 3

Volume 5 Terms and Conditions 3

L.2.1.2 A Proposal Executive Summary or transmittal letter is optional. It will neither be considered as part of the volumes required, nor will it be evaluated. If a Proposal Executive Summary is submitted, it shall be submitted as a separate volume from the five volumes set forth above and it should be no more than five pages in length. No videos may be attached as any part of the proposal submission media. Video files will not be accepted as any part of the proposal submission.

L.2.1.3 Offerors are not authorized to include in the proposal citations for, or linkages to websites.

L.2.2 Proposal Format and Instructions

L.2.2.1 Each volume listed above shall be submitted on a separate set of CD-ROMs or DVDs. The Offeror shall submit three identical sets of CD-ROMs or DVDs for each volume. One set of media shall be labeled as the primary copy and signed by a representative of the company authorized to submit proposals. In the case of discrepancies between the sets of media, the primary copy will take precedence.

L.2.2.1.1 Each CD-ROM or DVD shall be labeled so it is easily identifiable for evaluation purposes (example: Volume II, Cost/Price

Factor, Set 1 of 3, CD 1 of X), and shall also include the Offerors name and the solicitation number. Each volume shall include a (i) title page, (ii) table of contents, and (iii) list of tables and figures. Each page of the proposal shall be numbered, and each paragraph of the proposal shall have a reference number. Provide a list of all attachments and substantiating data in the table of contents. The table of contents shall be organized as set forth below. The table of contents shall include the following information for each Factor, attachment, and for all substantiating data listed:

(a) Cross-reference to related section L paragraph number

(b) Page number

(c) CD-ROM or DVD Volume and number

(d) File name

L.2.2.1.2 Acceptable File Formats. All electronic information provided in response to the solicitation shall be provided in Microsoft

(MS) Office 2013 or PDF compatible format or except as noted in instructions for individual volumes. No videos may be attached as any part of the proposal submission media. Video files will not be accepted as any part of the proposal submission.

L.2.2.1.3 Unless otherwise specified, proposals shall be formatted for 8.5 x 11 paper with a minimum font size of 10 pt. and with a minimum of 0.5 margins. Schedules, drawings and other documents more appropriate to larger size shall be formatted for no larger than 11 x 17 dimensions. All spreadsheets shall include all formulas, function, macros, computations, or equations used to compute the proposed amounts. For each workbook, all Rows, Columns, Cells, and Worksheets shall be visible. Zero height and zero width rows and columns in

Worksheets are not acceptable. Worksheet cells formatted with the font color equal to the fill color are unacceptable. If Workbooks or

3 21

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

Worksheets are password protected, then the passwords shall be provided. Print image files or pictures or files containing only values are not acceptable. Failure to provide fully functional excel spreadsheets in the proposal may result in your proposal being rejected.

L.2.2.2 Submission Due Date

The Offeror shall ensure its proposal, in its entirety, reaches its intended destination before the date and time set for closing of the solicitation set forth in Block 9 on the SF 33, front page of the solicitation.

L.2.2.2.1 Lateness

The lateness rules for submitted proposals are outlined in FAR 52.215-1, ALT I "Instructions to Offerors-Competitive Acquisition," and are incorporated in to this solicitation.

L.2.2.3 Proposal Submission Address

Submit the proposal to the address below. All proposals delivered in response to this solicitation, whether hand-carried or submitted via U.S. mail, shall be addressed as follows:

US Army Contracting Command Warren

Bid Room, Bldg 231, Mail Stop 303

Attn: RCIS Type I Proposal, Carrie English or Helen Smith

6501 East 11 Mile Road

Warren, MI 48397-5000

Solicitation Number: W56HZV-15-R-0156

Proposal Due Date & Time: (Refer to Standard Form 33 (pg. 1), Block 9)

TO BE DELIVERED UNOPENED

(Offerors name)

L.2.2.4 Method of Submission

Proposals may either be hand-carried or submitted via US mail. Hand-carried submissions* include proposals delivered by commercial carriers such as FedEx, UPS, or services other than the US Postal Service. Hand-carried proposals shall be delivered to the Detroit

Arsenal (DTA) Mail Handling Facility (Building 255) between the hours of 8:00AM and 1:00PM local Warren, MI time. The package(s) will be dated and time stamped at the Mail Handling Facility and the Government will be responsible for forwarding the package(s) to the appropriate personnel. Offerors should ensure that any commercial carrier it uses has a tracking system that can provide documentation that will prove the date and time of delivery to the Government. If the proposal is hand-carried by other than a commercial carrier, the delivery person (even if an employee of the Offeror) shall be a US citizen, and shall obtain a signed receipt, indicating date and time of delivery, from the Mail Handling Facility personnel. The delivery person shall provide the receipt since the Mail Handling

Facility personnel do not have them.

*Directions to DTA: From Van Dyke Avenue, travel west on East Eleven Mile road to railroad track. Immediately after crossing railroad track turn right into DTA main gate and follow security officer directions to the Mail Handling Facility (Building 255). It may be necessary for the delivery person to obtain a visitors badge prior to being allowed to enter the installation. If so, the security officer will advise the delivery person of the procedures to follow.

L.2.2.4.1 Exterior envelopes shall identify the solicitation number and date specified for receipt of proposals.

L.2.2.4.2 Offerors are cautioned that approval to enter the installation shall be obtained prior to the closing date and time for receipt of proposals. Follow the procedures outlined above for entry. It is the Offerors responsibility to plan sufficient time to clear Detroit Arsenal security.

L.2.3 Single Proposal Submission

Offerors are limited to submitting one proposal with one approach to meeting the requirements of this solicitation. An Offeror is defined as an entity competing independently that does not share a common parent, does not have a parent/subsidiary relationship with any other Offeror, and is not affiliated with any other Offeror (as defined in Federal Acquisition Regulation (FAR) 19.101).

L.2.4 All or None

Offers in response to this solicitation shall be submitted for all the requirements identified in the solicitation. Offers submitted for less than all the requirements called for by this solicitation may be rejected or ineligible for award.

L.3 Evaluation Factors:

4 21

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

Offeror proposals shall address the following four Evaluation Factors:

Factor 1: Design

Factor 2: Past Performance

Factor 3: Cost/Price

Factor 4: Small Business Participation

L.3.1 Volume I - Design Factor

The Design Factor Volume includes four Sub-factors:

Sub-factor 1: Control of Interrogation Functions

Sub-factor 2: Communications

Sub-factor 3: Teleoperation Control of Automotive Functions

Sub-factor 4: Semi-Autonomous Control of Automotive Functions

L.3.1.1 Sub-factor 1: Control of Interrogation Functions

L.3.1.1.1 The Offeror shall describe its control architecture and concept of operation to enable an operator using the Operator Control

Unit (OCU) to perform excavation and interrogation tasks using the R-HMEE. The Offeror shall describe the operators control(s) and display(s), user interface, video sensors and remote video views from the R-HMEE, Mobile Base Unit (MBU) processing and control methods for the below Performance Specification (P-spec) requirements (L.3.1.1.5).

L.3.1.1.2 The Offeror shall provide information on the system hardware architecture to perform excavation and interrogation tasks including operators control(s) and display(s), R-HMEE video sensors and Mobile Base Unit (MBU) with substantiating data in the form of hardware architecture diagram(s) and hardware specification data sheets.

L.3.1.1.3 The Offeror shall provide information on the design of system software implementing the OCU user interface, MBU processing and control methods (to include names of application code, operating system(s), middleware, third party software packages, licenses required). The Offeror shall provide substantiating data in the form of existing software to be reused as Source Lines Of Code (SLOC), new software to be developed as SLOC, and software architecture.

L.3.1.1.4 The Offeror shall provide substantiating data for the R-HMEE video cameras, in the form of camera specification data sheets, field of view analysis, quantity, type, performance during day and night, mounting location(s), and occlusions on vehicle video cameras used for day and night operation.

L.3.1.1.5 The Offeror shall provide its proposed solution to address the following requirements:

P-spec-402: Backhoe Bucket: Excavate Objects in Gravel Road

P-spec-409: Clamshell Bucket: Grasp and Lift Objects from a Hole

P-spec-410: Front Loader: Scoop, Lift, and Move Objects

P-spec-441: Rake and Spork: Interrogate Object in Dirt Road

L.3.1.2 Sub-factor 2: Communications

L.3.1.2.1 The Offeror shall describe its communications approach to include its radio communication system selection for the below P-spec requirements (L.3.1.2.5).

L.3.1.2.2 The Offeror shall provide substantiating data in the form of radio specification data sheets and proposed approach for encryption.

L.3.1.2.3 The Offeror shall provide information to include analytical calculations on round trip control loop latency and contribution of all individual system components including encryption, with substantiating data in the form of test and experimentation reports. The

Offeror shall provide information on video feedback to the OCU operator (including video processing, transmission rate, and display) with substantiating data in the form of specification sheets, test data for video throughput (megabits per second [Mbps]) and display

(resolution and frames per second [fps]).

L.3.1.2.4 The Offeror shall provide substantiating data in the form of test and experimentation reports on Line-Of-Sight (LOS) operating range.

L.3.1.2.5 The Offeror shall provide its proposed solution to address the following requirements:

5 21

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

P-spec-508: Communications Encryption

P-spec-517: Wireless Communications Latency

P-spec-695: Line of Sight (LOS) Range

L.3.1.3 Sub-factor 3: Teleoperation Control of Automotive Functions

L.3.1.3.1 The Offeror shall describe its control architecture and concept of operation to enable an operator using the OCU to control via teleoperation the automotive functions of the R-HMEE. The Offeror shall describe the operators control(s) and display(s), user interface, video sensors and remote video views from the R-HMEE, Mobile Base Unit (MBU) processing and any teleoperation assist methods.

The Offeror shall provide information on vehicle speeds attainable with substantiating data in the form of field test and experimentation reports for the below P-spec requirements (L.3.1.3.5).

L.3.1.3.2 The Offeror shall provide information on the system hardware architecture including operators control(s) and display(s), R-

HMEE video sensors and Mobile Base Unit (MBU) with substantiating data in the form of hardware architecture diagram(s) and hardware specification data sheets.

L.3.1.3.3 The Offeror shall provide information on the design of system software implementing the OCU user interface, MBU processing, and any teleoperation assist methods (to include names of application code, operating system(s), middleware, third party software packages, licenses required). The Offeror shall provide substantiating data in the form of existing software to be reused as Source

Lines Of Code (SLOC), new software to be developed as SLOC, and software architecture.

L.3.1.3.4 The Offeror shall provide substantiating data for the R-HMEE video cameras, in the form of camera specification data sheets, field of view analysis, quantity, type, performance during day and night, mounting location(s), and occlusions on vehicle video cameras used for day and night operation.

L.3.1.3.5 The Offeror shall provide its proposed solution to address the following requirement:

P-spec-3185: Teleoperation Control of Automotive Functions Forward and Reverse Directions

L.3.1.4 Sub-factor 4: Semi-Autonomous Control of Automotive Functions

L.3.1.4.1 The Offeror shall describe its control architecture and concept of operation to enable an operator using the OCU to semi-autonomously control the automotive functions of the R-HMEE. The Offeror shall describe the operators control(s) and display(s), user interface, Mobile Base Unit (MBU) processing and semi-autonomous control methods, and all R-HMEE sensors. The Offeror shall provide information on vehicle speeds attainable with substantiating data in the form of field test and experimentation reports, for the below P-spec requirements (L.3.1.4.5)

L.3.1.4.2 The Offeror shall provide information on the SAC system hardware architecture including the operators control(s) and display(s), Mobile Base Unit (MBU) processing, and all R-HMEE sensors with substantiating data in the form of hardware architecture diagram(s) and hardware specification data sheets.

L.3.1.4.3 The Offeror shall provide information on the design of system software implementing the OCU user interface, MBU processing and semi-autonomous control methods (to include names of application code, operating system(s), middleware, third party software packages, licenses required). The Offeror shall provide substantiating data in the form of existing software to be reused as Source Lines Of Code

(SLOC), new software to be developed as SLOC, and software architecture.

L.3.1.4.4 The Offeror shall provide information and substantiating data, in the form of sensor specification data sheets, on sensors

(quantity, type, performance during day and night).

L.3.1.4.5 The Offeror shall provide its proposed solution to address the following requirement:

P-spec-526: Semi-Autonomous Control of Automotive Functions Forward Direction

Semi-autonomous control in the reverse direction is not required.

Semi-autonomous control that employs a tether, cable, or other physical connection between the R-HMEE and Control Vehicle (or OCU when dismounted) is not permitted.

L.3.2 Volume II: Past Performance Factor

L.3.2.1 The Offeror shall provide information for a total of up to four recent and relevant contracts. These may include foreign, federal, state, local municipality, and private industry contracts. The Government will not consider the past performance of subcontractors or any individuals or key personnel; only corporate past performance will be considered.

6 21

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

L.3.2.1.2 Recent contracts are those performed within three years preceding the date of issuance of this solicitation.

For the purposes of this volume, contract shall be defined as:

a. a single task or delivery order placed under a single-award or multiple-award IDIQ task order contract (FAR 16.501-1) that does not contain multiple work directives or similar instruments which contain separate statements of work; or,

b. a single work directive or similar instrument which contains a separate statement of work issued under a broader contract; or

c. a single order placed under a Basic Ordering Agreement (BOA) (FAR 16.703); or

d. a single task order placed under a Federal Supply Schedule (FSS)(FAR 8.405-2); or

e. a single task order placed under a single-award or multiple-award blanket purchase agreement (BPA) (FAR 8.405-3 or FAR 13.303); or

f. a single Government or Commercial contract which does not include any of the types of instruments derived in (a)-(e) above.

L.3.2.2 Relevant contracts are those that are comparable in scope, magnitude of effort, and complexity to the following requirements:

a. Production and full integration of a SAC system or comparable robotics kit to a High Mobility Engineering Excavator (HMEE) vehicle, or other vehicle platform similar to a HMEE, along with Operator Control Units and all components for operation of the end system.

b. Provide a Logistics Support Activity (LOGSA) authenticated Operator and Maintenance Technical Manual.

L.3.2.3 The Offeror shall submit a completed Attachment 0035 Past Performance Relevance Matrix.

L.3.2.4 Contract Information: For each of the up to four recent and relevant contracts submitted, provide the following information:

a. Contract Number (and delivery order number if applicable);

b. Contract Type;

c. Total Value of the Contract (beginning & ending value);

d. Delivery or Performance Schedule:

e. Government or commercial contracting activity address, telephone number and email;

f. Procuring Contracting Officer (PCO) and Contract Specialists name or point of contact (for commercial customer), as well as their telephone number and email addresses:

g. Government or commercial Administrative Contracting Officer (ACO), Contracting Officers Representative (COR), Performance Certifier, and Quality Assurance Representatives (QAR) names, as well as their telephone numbers and email addresses;

h. A description of scope of work requirements and a discussion of the similarities between the cited contract scope and the relevant standards identified above in L.3.2.2.

i. A description of the work performed by the Offeror;

j. Percentage of effort performed as a prime or subcontractor;

k. For each of the contracts listed, provide a brief self-assessment of contract performance.

l. Copies of Statements of Work from each of the submitted contracts to establish the relevance of the contract to the scope of work activities listed in L.3.2.2 above.

L.3.2.5 Performance Approach. To support the Past Performance assessment of the relevance of prior contracts to the RCIS Type I contract, Offerors shall describe the similarities between their proposed performance approach and the contracts they are presenting.

L.3.2.5.1 For any contracts that did not or will not meet original schedule or technical performance requirements, provide a brief explanation of the reason(s) for the variance and any corrective action(s) taken. The Offerors shall list each time the delivery schedule was revised and provide an explanation of why the revision was necessary. All Requests for Deviation and Requests for Waiver shall be addressed with respect to causes and corrective actions. The Offeror shall also provide a copy of any Cure Notices or Show

Cause Letters received on each contract listed and a description of any corrective action implemented by the Offeror. The Offerors shall indicate if any of the contracts listed were terminated and the type and reasons for the termination.

L.3.2.6 Past Performance Questionnaire. A Past Performance Questionnaire is provided in Attachment 0034. For each of the four recent and relevant contracts submitted by the Offeror, the Offeror shall send a copy of the past performance questionnaire directly to the appropriate PCO and, if applicable, COR or other appropriate technical and contracting individuals. The Offeror shall request that these individuals complete the questionnaire and forward it electronically directly to the Contract Specialist listed on the front page of the SF33 block ten as soon as possible, but no later than the solicitation closing date (See Block nine of the SF33 cover page to the solicitation) with the subject heading PAST PERFORMANCE INFORMATION FOR [Offeror name].

L.3.2.7 Corporate Entities. If any contract submitted as part of the Past Performance Factor Volume was performed by a corporate entity or division other than the corporate entity or division that would perform work under this solicitation, the Offeror shall identify the entity, and explain how the resources of the other entity will be utilized in the performance of this effort.

L.3.2.8 Predecessor Companies. If the Offeror only has recent and relevant performance history as part of a predecessor company, the

Government may consider that past performance in its evaluation of past performance. The Offeror shall provide the information for those recent and relevant contracts of that predecessor company. Offerors shall also briefly document the history of the evolution of the offering company from the predecessor company.

7 21

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

L.3.2.9 Contacting References. The Government may contact any of the references the Offeror provides, may contact other third parties for performance information, and the Government reserves the right to use any information received as part of its evaluation.

L.3.2.10 Past Performance Information. The Government does not assume the duty to search for data to cure problems it finds in proposals. The burden of providing thorough and complete past performance information remains with the Offeror. The Offeror may also be evaluated based on other internal Government or private source information. In this regard, the Government may utilize the Contract

Performance and Rating System (CPARS), the Past Performance Information Retrieval System (PPIRS) and any other available internal

Government sources to search for recent and relevant Offeror performance and ratings. While the Government may elect to consider data obtained from external sources other than the proposal, the burden on providing thorough and complete past performance information rests with the Offeror. Failure to provide the information requested in L.3.2.4 may result in an assessment that the referenced past performance record lacks relevance or is not recent.

L.3.3 Volume III: Cost/Price Factor

L.3.3.1 The Offerors Cost/Price Volume shall include substantiating information: either pricing, sales or cost information as described below, supporting the reasonableness of the proposed Fixed Price Incentive Firm (FPIF) and Firm Fixed Price (FFP) Contract Line Item

Number (CLINS) and reasonableness and realism of the proposed costs and fees for the Cost Plus Incentive Fee (CPIF) and Cost Plus Fixed

Fee (CPFF) CLINS in sufficient detail for the Government to evaluate the proposal. The Offeror shall submit its proposed price for each

CLIN in the separate Pricing Attachment (see Attachment 0055) in Microsoft Excel format, print image is not acceptable. The Offeror shall fill out all required fields in the Pricing Attachment. Partial proposals will not be considered.

L.3.3.2 Presentation of Cost/Price Data. Electronic spreadsheet format is Microsoft Excel. Files shall contain formulas used in the calculation. Files should not contain hidden rows or columns. All prices shall be stated in United States dollars (USD) only, for both the prime contractor and any potential subcontractors. The Offeror shall state the exchange rate used to convert any currency to USD, if applicable.

L.3.3.3 Cost Accounting System: In order to be considered for award as part of the responsibility determination, the Offeror shall provide evidence that it has adequate financial management and fund tracking procedures to accommodate a cost-reimbursement type contract. This evidence may include a letter from either DCMA or DCAA that states that the Offeror has an acceptable accounting system for this type of contract. If an accounting system has not been determined to be adequate by DCMA or DCAA, the Offeror shall coordinate with the PCO to obtain an accounting system review prior to submitting a proposal.

Section L.3.3.4. The Offeror shall provide:

L.3.3.4.1 The Offeror shall provide the target cost and target fee dollars for each CPIF CLINs in Attachment 0055. The Offeror shall not propose alternative share ratios, or an alternative minimum fee or maximum fee percentage, other than what the RFP requires.

L.3.3.4.2 The Offeror shall submit a Target Cost and Target Profit for each FPIF CLIN as stated in Attachment 0055 of the RFP. The

Offeror shall not propose an alternative share ratio or Ceiling Price percentage (defined as percent of target cost).

L.3.3.5 For each CLIN, include a top-level spreadsheet, time-phased by year, and organized by cost element (i.e. Direct Labor, Subcontracts, Material, Other Direct Costs, Overhead and Indirect, Fee, etc.) which supports the Offeror's proposed price. The cost breakdown shall be consistent with your cost accounting system. Provide the following information in support of each top level spreadsheet:

L.3.3.5.1 Direct labor. Support for costs related to direct labor shall include the following:

a) For all CLINs, provide a time-phased breakout of the direct labor hours, by labor category, appropriate to the Offeror's accounting system.

b) For all CLINs, provide the labor rate for each category of direct labor, including the basis for the rate and any escalation used.

Provide the basis of the proposed base direct labor rates (for instance actual rates, payroll records, Bureau of Labor Statistics data, etc.). Indicate whether any of the proposed rates are included in the current Forward Pricing Rate Agreement (FPRA), Forward Pricing

Rate Recommendation(FPRR) or Forward Pricing Rate Proposal (FPRP). Indicate whether any rates have been audited by Defense Contract

Audit Agency (DCAA) and the outcome of the audit.

c) In addition to the information required above in L.3.3.5.1(a) and L.3.3.5.1(b), for Cost Reimbursable CLINs only, the Offeror shall provide Basis of Estimate (BOE)s that include the following:

i) A narrative description of the tasks to be performed;

ii) A description of the method used to estimate the hours (identifying assumptions used and any Cost Estimating Relationships);

iii) The calculations showing the computation of the direct labor hours for each specific task;

iv) PWS Paragraph and Work Breakout Structure (WBS); and

v) A description of each labor category used in the BOE

8 21

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

L.3.3.5.2 Material

For all CLINs, the Offeror shall provide a narrative, which explains the method used to develop proposed cost, including information about the extent to which the cost is based on vendor quotes, purchase order history, estimates, or any other information necessary to substantiate the proposal.

The Offeror shall provide a complete Bill of Material (BOM) with the following information:

(a) National Stock Number (NSN), as applicable

(b) Part Number(s)

(c) Item Name and Description

(d) Vendor

(e) Unit Cost (purchase price to Offeror)

(f) Quantity used

(g) Extended Cost (unit cost multiplied by quantity used)

(h) Basis for cost (engineering estimate, vendor quote, purchase history, etc.)

(i) For material costs based on engineering estimates, please provide rationale and methodology for how the estimate was developed

(j) Indicate whether component is sole-source, competitive, or commercial

L.3.3.5.3 Travel. For all CLINs, the Offeror shall provide proposed travel costs (number of travelers, duration, airfare, lodging, per diem and rental car) and basis for projected costs as well as the Section C reference for each trip. All travel proposed shall be IAW

Joint Travel Regulations (JTR).

L.3.3.5.4 Other Direct Costs (ODC). For all CLINs, the Offeror shall provide the proposed cost and detailed basis of estimates for all proposed ODCs. Also the Offeror shall indicate if any indirect cost or profit and fee is applied to the proposed ODCs.

L.3.3.5.5 Indirect costs. For all CLINs, the Offeror shall provide a list of direct and indirect rates (e.g. Direct Labor rates, Material Overhead, Direct Labor Overhead and General & Administrative), by category and by year, used by the Offeror to develop its proposal. These rates shall be consistent with the Offerors accounting system. Identify the proposal allocation base and calculation.

The Offeror shall identify the impact the award of this contract will have on its business volume, including the effects upon the rate pools and bases. The Offeror shall include the following:

(a) The date of the current Cost Accounting Standards Board (CASB) Disclosure Statement.

(b) The effective date of the rates and other data that formed the basis for the rates (the date of the burden study analysis or payroll run, etc.), and state whether or not the rate package has been submitted to Defense Contract Audit Agency (DCAA) for review.

(c) The ending month for the Offeror's fiscal year.

(d) A narrative explaining the basis for the estimated rates. Specifically identify any escalation factors used.

(e) State whether these rates represent a Forward Pricing Rate Proposal (FPRP) or a Forward Pricing Rate Agreement (FPRA) and note the date of the agreement.

(f) State whether or not the business volume that would be generated if a contract was awarded to your firm as a result of this RFP has been included in the proposed rate package.

(g) For each of the rate categories, provide both the prior and current fiscal year's Incurred Cost rates. Indicate if the prior year rates have been audited. For the current year's Incurred Cost rates, provide the month ending for those rates.

L.3.3.5.6 Profit and Fee. For all CLINs, the Offeror shall include the proposed profit and fee rate.

L.3.3.5.7 Facilities Capital Cost of Money (FCCM). For all CLINs, if FCCM is proposed, the Offeror shall detail the total amount estimated for FCCM by category and provide its method of calculation for any proposed FCCM.

L.3.3.5.8 Escalation. The Offeror shall identify and explain in a narrative format any escalation proposed throughout the contract performance. The Offeror shall also identify any assumptions made in determining the basis for escalation rates in the out years.

L.3.3.5.9 Non-Major Subcontracts (<$10M). For all CLINs, for each subcontractor with a total proposed cost under $10M, the Offeror shall provide the subcontractor's name, the proposed cost, a brief description of work to be performed, the contract type, and the method used for determining the prices fair and reasonable.

L.3.3.6 Major Subcontractor (>$10M for the entire contract), see sections L.3.3.6.1 - 2.

L.3.3.6.1 Fixed-Price CLINs: For each Major Subcontractor, the Offeror shall provide the subcontractors name, the proposed cost, a brief description of work to be performed, the contract type, and the method used for determining the prices fair and reasonable.

L.3.3.6.2 Cost Reimbursement CLINs: For each Major Subcontractor, the Offeror shall provide data as described above in L.3.3.5

(itemized by subcontract, to include the subcontractor name, subcontract price, and the Offerors narrative description of each subcontractors effort). The Offeror shall include the evaluation of the subcontractor's submission required by FAR 15.404-3 (b), and rationale for determining that the subcontract price is reasonable. Also, state the type of subcontract the Offeror anticipates (e.g.

9 21

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

firm-fixed price, cost-plus-fixed-fee, etc.). If the Major Subcontractor declines to provide complete cost proposals to the Offeror or higher-tier subcontractor, then those subcontract proposals may be submitted by the subcontractor directly to the PCO using the same submission instructions noted in L.2.

L.3.3.7 Interdivisional Transfers (if applicable). Provide the same data as for the Prime Offeror (excludes commercial or competitive transfers).

L.3.3.8 In accordance with FAR 15.306, the Government reserves the right to request additional or more detailed information to support its evaluation.

L.3.3.9 Technical Data Package (TDP) Data and Computer Software Rights

The Government requires a priced option to procure a Government Format TDP and computer software in accordance with C.24.. It is the

Governments objective to maximize competitive utility by acquiring rights in technical data, computer software and computer software documentation to permit the Government to use, modify, reproduce, release, perform, display, or disclose technical data to support future competitive acquisitions of the Semi-Autonomous Control (SAC) System as defined in C.1.1.1 including their assembly and integration to the Delta High Mobility Engineering Excavator (DHMEE) and Buffalo Mine Protected Clearance Vehicle (MPCV) as defined in

C.1.1.1.

In addition to the assertion of restrictions required to be provided in response to the applicable DFARS clauses referenced above, the

Offeror shall identify the rights in it is proposing under the Government Format TDP and computer software that will offer competitive utility.

L.3.3.9.1 The Offeror shall complete the RCIS Technical Data And Computer Software Rights Evaluation Spreadsheet, Attachment 0033, for its proposed SAC System Government Technical Data Package and computer software and submit it in Microsoft Excel 2013 format as described in Sections L.3.3.9.1.1 and L.3.3.9.1.2 below. The Offeror shall list all deliverable technical data and computer software items for which they are asserting restrictions in the Governments rights. Submission of this table is necessary for the evaluation of this factor and shall reflect the information provided by the Offeror in Attachment 0060 Commercial Tech Data and Commercial Computer

Software and Attachment 0061 Identification and Assertion of Restrictions referenced in L.3.5.6. Attachment 0060 Commercial Tech Data and Commercial Computer Sofware (SW) and Attachment 0061 Identification and Assertion of Restrictions which represent the response required by DFARS 252.227-7017 for all deliverables, including CDRL data items (SAC System Software (CDRL A023); EMD Technical Data

Package (TDP) (CDRL A028); LRIP Technical Data Package (TDP) (CDRL A075); Option Technical Data Package (TDP) (CDRL A076)).

L.3.3.9.1.1 Definitions. The following definitions will be used for Offerors proposed data rights and the Governments evaluation:

(a) Commercially Available A component or computer software which is available for public sale and has a published list price.

(b) Competitive Rights A component or computer software which is proposed to be delivered and released into the Government Format TDP and computer software with Unlimited or Government Purpose Rights as defined in DFARS 252.227-7013, 252.227-7014, and 252.227-7015, which can be openly and competitively procured by the Government for Government purposes without restriction (except that a proper Non-

Disclosure Agreement will be executed before Government Purpose Rights material is distributed to a non-Government party).

L.3.3.9.1.2 The Offeror shall provide a listing of each data item in the TDP and each computer software deliverable in which they are asserting restrictions. (Reference DFARS 252.227-7017), Instructions are as follows:

(a) ATTACHMENT 0060 CROSS-REFERENCE ITEM ID #: The contractor shall enter the item ID number in column B from Attachment 0060 for the same TDP data and computer software element as listed in Attachment 0060.

(b) ATTACHMENT 0061 CROSS-REFERENCE ITEM ID #: The contractor shall enter the item ID number in column B from Attachment 0061 for the same TDP data and computer software element as listed in Attachment 0061.

(c) DATA ITEM NUMBER: The contractor shall enter the data item number for each TDP data and computer software element, as defined in MIL-

STD-31000A 4.4, to be delivered. If multiple elements will be delivered for the same item, component, process, or computer software the contractor shall use one Data Item Number and one line of entry unless the responses for the columns differ by element.

(d) HARDWARE OR COMPUTER SOFTWARE: The offeror shall identify if the item is hardware or computer software. If computer software, the offeror must identify if it is object code/executable software or source code. If both, enter under two separate Data Item Numbers and on two separate rows. If a computer software item contains embedded software item(s) with different assertions, enter under separate

Data Item Numbers and on separate rows until the assertion for the entire software item is uniform.

(e) NOMENCLATURE: The Offeror shall enter the nomenclature of each data item.

(f) DESCRIPTION: The offerors shall provide a description of the part which conveys the usage, function, and location of the part.

(g) NEXT HIGHER ASSEMBLY: The Offeror shall enter the data item number of the next higher assembly, if applicable.

10 21

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

(h) COMMERCIALLY AVAILABLE (Yes or No): For each item identified, indicate whether it is commercially available or not. Note that even if a data item is commercially available, it is to be listed on Attachment 0033, if it is to be delivered with less than Unlimited

Rights.

(i) BASIS FOR ASSERTION: For each item identified with other than Unlimited Rights, the Offeror shall specify the Basis for the Asserted

Restriction. Generally, development at private expense, either exclusively or partially, is the only basis for asserting restrictions.

For each item identified with Government Purpose Rights, the Offeror shall also provide the expiration date of the Government Purpose

Rights restriction. For technical data, other than computer software documentation, development refers to development of the item, component, or process to which the data pertain. The Governments right in computer software documentation generally may not be restricted. For computer software, development refers to the software, not to the development of computer software documentation.

Indicate whether development was accomplished exclusively or partially at private expense. If development was not accomplished exclusively or partially at private expense, or for computer software documentation, enter the specific basis for asserting restrictions.

(j) ASSERTED RIGHTS CATEGORY: The Offeror shall describe the restrictions in Government rights they are asserting on each data or software item. Enter asserted rights category (Unlimited, Government Purpose Rights, Limited, Restricted, Specifically Negotiated

License Rights, or Rights in derivative computer software or computer software documentation).

(k) NAME OF PERSON ASSERTING RESTRICTIONS: For each data item identified with other than Unlimited Rights, the Offeror shall insert the name of the corporation, individual, or other person, as appropriate.

The Offeror is encouraged to maximize competitive utility to the Government by offering rights in Part 2 that are no less restrictive than Government Purpose Rights.

L.3.3.9.1.3 Signature. The RCIS Technical Data And Software Rights Evaluation Spreadsheet, Attachment 0033 shall be dated and signed by an official authorized to contractually obligate the Offeror.

L.3.4 Volume IV Small Business Participation Factor

L.3.4.1 Application: The Small Business Participation proposal submission instructions apply to every Offeror (U.S. and non-U.S.), regardless of size, socioeconomic status, or locations of working facilities or headquarters.

L.3.4.2 Definitions:

a. Affiliate is defined in FAR 19.101. For more detailed information see 13 CFR 121.103.

b. Alaskan Native Corporation is defined in FAR 19.701 and FAR Clause 52.219-9 in Section I of this solicitation.

c. Contractor Team Arrangement (CTA) is defined in FAR 9.601.

d. Indian Tribe is defined in FAR 19.701 and FAR Clause 52.219-9 in Section I of this solicitation.

e. Other Than Small Business is any entity that is not a U.S. small business concern, including, but not limited to large businesses, educational institutions, non-profits, Government entities, and foreign firms.

f. Small Business (SB) and each of the small business subcategories - small disadvantaged business (SDB), woman-owned small business

(WOSB), historically underutilized business zone small business (HUBZone SB), veteran-owned small business (VOSB), and service-disabled veteran-owned small business (SDVOSB), are defined in FAR 2.101 and in FAR Clause 52.219-8 in Section I of this solicitation.

g. Small Business Subcontractor is defined in FAR 2.101.

h. Small Business Teaming Arrangement (SBTA) is defined in FAR 2.101.

i. Subcontract is defined in FAR 19.701 and FAR Clause 52.219-9 in Section I of this solicitation. For more detailed information, see

13 CFR 125.3.

L.3.4.3 Small Business Participation Factor Workbook (Attachment 0037) and Small Business Participation Factor Workbook Instructions

(Attachment 0036):

a. All Offerors, including Offerors who are themselves U.S. small business concerns for the NAICS code assigned to this requirement, are required to complete the Small Business Participation Factor Workbook (Attachment 0037), using the detailed Small Business Participation

Factor Workbook Instructions (Attachment 0036).

b. An Offeror shall fill out the Small Business Participation Factor Workbook (Attachment 0037) with goals for this solicitation specifically, even if it is an Other-Than-Small-Business (OTSB) submitting a Comprehensive Subcontracting Plan.

c. The Small Business Participation Factor Workbook (Attachment 0037) shall be submitted in the Microsoft Excel workbook format with all tabs, formulas, and functions that are built into the template in the solicitation. Print image files or pictures (for example, a picture of an Excel spreadsheet embedded in a Word document) or files containing only values are not acceptable. Offerors shall not add formulas or links to any cells that do not already contain them, nor shall the Offeror remove or change any existing formulas or links.

11 21

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

d. Small Business Participation Factor…