Q&A_Tracker_12-29-16.pdf

Questi on #

Date

Received

Document Reference Title Requirement Question Government Response

#1 6/24/2015 RCIS RFI Regarding the RCIS RFI, are the Distribution D attachments 1-5 are available?

There was no attachment 0004 released with the RFI. Updated

RFI doc on 8 July 2015 to provide interested parties clarification on obtaining RCIS attachments in FBO.

#2 6/25/2015 PROCNET /RFI 2015 We would like to request access to the RCIS 2015 RFI documents that contain CUI. Can you please advise as to what additional steps if any we need to take in order to do so.

Updated RFI doc on 8 July 2015 to provide interested parties clarification on obtaining RCIS attachments in FBO.

#3 6/25/2015 PROCNET /RFI 2015 Our company is in receipt of the subject RFI on the FBO website and is hereby requesting access to the RCIS program Controlled Unclassified Information (CUI) identified, but not currently available via the Internet.

Updated RFI doc on 8 July 2015 to provide interested parties clarification on obtaining RCIS attachments in FBO.

#4 6/25/2015 PROCNET /RFI 2015 The RCIS RFI-2015.PDf document lists that there is

Controller unclassified information not available on the internet that is available upon request. I would like to request this information such that we may be able to provide a complete response. Please let me know what other documentation is required so that we might receive the information.

Updated RFI doc on 8 July 2015 to provide interested parties clarification on obtaining RCIS attachments in FBO.

#5 6/30/2015 RFI 2015 Doc The RFI-2015 document directs that requests must be made through the FBO website. However there is no methodology to request that information on the FBO opportunity page other than the listing of this email address as Primary POC and the RFI-2015 Document lists that this address should be contacted for clarifications. The direct link for the Distribution D

Controlled unclassified information on the RCIS ProcNet webpage

(https://contracting.tacom.army.mil/majoracq/RCIS.ht

m) only links back to the FBO website.

Updated RFI doc on 8 July 2015 to provide interested parties clarification on obtaining RCIS attachments in FBO.

#6 6/30/2015 RCIS 2015 RFI We are in receipt of the subject Fed Biz Ops (FBO) RFI referencing Controlled Unclassified Information (CUI) that is not available via the internet. "However, CUI will be made available to offerors upon an approved request". Per RCIS 2015 RFI, we are hereby requesting access to the RCIS program Controlled Unclassified

Information (CUI) identified, but not currently available via the Internet.

Updated RFI doc on 8 July 2015 to provide interested parties clarification on obtaining RCIS attachments in FBO.

#7 6/30/2015 RCIS Distro D

Attachments/CUI

Docs

I did see the statement in the 2015 rfi regarding requesting these cui docs over fbo but I have not been able to figure out how to achieve this within the fbo posting. I will ask around here as I am overlooking something. Not the first time :)

#8 6/30/2015 #REF! We would like to request access to the CUI documents available to prepare a response to the RFI. Please advise if the documents are available for the RFI response or will only be made available for the RFP response.

CUI will be made available to offerors upon an approved request.

Requests for CUI documents must be made through the Federal

Business Opportunities (FBO) website via Explicit Access Request.

FBO will prompt you for your firm's Marketing Partner ID

Number (MPIN). This is tied to your CAGE code. Once a request has been made, an automated email will be generated to the

Government reviewer. The Government reserves the right to request additional information to support releasing documentation. All CUI must be handled in accordance with

(IAW) the Security Classification markings on each individual document. Direct links to the CUI documents are available on the

RCIS website. The CUI docs will be avaible for the RFI if approved.

#9 7/1/2015 Attachments 1-5 Hello, I doubled checked my FBO profile status which confirms that we are verified to receive controlled information; however, there are no icons or links in the notice that I can see which reference Attachments 1-5.

If attachments 1-5 are available for request from FBO --

I can't figure it out. Have checked the FBO users guide and conferred with other FBO users. Please note I am only referring to Attachments 1-5, the others are available without issue. Any help you can provide would be greatly appreciated.

There was no attachment 0004 released with the RFI. Updated

RFI doc on 8 July 2015 to provide interested parties clarification on obtaining RCIS attachments in FBO.

#10 7/1/2015 RCIS 2015 RFI We have again read the RFI 2015 document and reviewed the opportunity postings on FBO and

PROCNET. While there are links on FBO to the EMD

SOW, CDRLs, and Distribution Statement A

Attachments, there do not appear to be either links to the Distribution Statement D Attachments, or links to request specific access under the "Notice Details" or

"Packages" tabs. Please advise.

Updated RFI doc on 8 July 2015 to provide interested parties clarification on obtaining RCIS attachments in FBO.

#11 7/1/2015 PROCNET Page Please clarify the reference to "TS3 FoC" on the

PROCNET page?

(https://contracting.tacom.army.mil/majoracq/RCIS.ht m)

"TS3 FoC" was changed to "RCIS".

#12 7/7/2015 RFI 2015 Doc We have reviewed the FBO RFI and it remains unclear to us who or where we should be submitting the request to gain access to the CUI in support of the subject RFI. If written or electronic notification to the

FBO is required, please provide insight to assist so that we can better respond to the RFI. in receipt of the subject Fed Biz Ops (FBO) RFI referencing Controlled

Unclassified Information (CUI) that is not available via the internet. "However, CUI will be made available to offerors upon an approved request". Per RCIS 2015 RFI, we are hereby requesting access to the RCIS program

Controlled Unclassified Information (CUI) identified, but not currently available via the Internet.

#13 8/18/2015 RFI 2015 Doc I believe the statement "If multiple individuals in your company need access to the attachments/documents for a solicitation and an explicit access request is required" is stating that if an individual from a contractor needs explicit access to the FBO website to download controlled information (CUI in this case), each person need EXPLICT FBO website access must register. It does NOT mean that once we have the information on our contractor IT system we need to have each person with need to know register through their FBO website. Is this a correct understanding? Or, does this mean that every person from every department from every contractor thinking about bidding would need to register on the FBO website?

Every individual contractor that needs access to attachments/documents for a solicitation, whether the contractor is interested in being the prime or a subcontractor, needs to be registered in Federal Business Opportunities (FBO) and submit an explicit access request. Once a contractor obtains access to attachments/documents, one person from an individual company that has already obtained access to the drawings can disseminate to other individuals in the company in accordance with DoD Regulations. However, it is important to note that such dissemination of attachments/documents that have an Export Control Warning Notice are subject to the Arms

Export Control Act (Title 22, U.S.C., Sec 2751, et.seq.) or the

Export Administration Act of 1979, as amended, Title 50, U.S.C, App. 2401 et. seq. Further dissemination must be in accordance with provisions of DoD Directive 5230.25. This also applies to distribution of the attachments/documents to all subcontractors at every level.

#14 9/21/2015 Attachment 1 -

Performance

Specification

Can we obtain the "Performance Specification for the

Multi-Function Control And Display System For Medium

Mine Protected Vehicle Family" referenced in P-spec

3214 of Attachment 1?

It is the Government’s intent to remove the Performance

Specification for the Multi-Function Control And Display System

For Medium Mine Protected Vehicle Family referenced in P-spec

3214 of Attachment 001. This intended change would be depicted when a draft Attachment 001 – RCIS Performance

Specification, draft solicitation or the solicitation is released.

#15 8/2/2016 Pre-Solicitation

Conference Question

If a small business is certified as more than one socio-economic category, can credit be given for each of the socio-economic categories? For example, what category or categories could be claimed for a Service

Disabled Veteran Owned (SDVOSB) and Woman Owned

Small Business (WOSB)?

Yes, In accordance with the Small Business Participation Factor

Workbook Instructions - Attachment 0036, if the prime contractor or subcontractor falls into more than one category of

Small Business, include the dollars in each of those categories.

For the example contained in the question, the dollars associated with the work to be performed by the SDVOSB /

WOSB would be applied to the SB category, SDVOSB category, and to the WOSB category. (Reference "Small Business

Participation Factor Workbook Instructions" page 2 (Prime $, Prime Contractor Participation Dollars), Paragraph 2.e. "Applying

Multiple Small Business Categories" and page 3 (Sub $, Subcontractor Participation Dollars), Paragraph 2.e "Applying

Multiple Small Business Categories.")

#16 8/4/2016 Pre-Solicitation

Conference Question

This projected iteration of the RCIS is meant to be semi-autonomous only, once the operator chooses to exit the vehicle. Is there an intent to progress to more autonomy? How much? What would that ‘autonomy’ mean?

No. There is no requirement for more 'Autonomy'.

Requirements for semi-autonomous control will be clarified in

Attachment 0001 RCIS P-Spec in the final RFP.

#17 8/4/2016 Pre-Solicitation

Conference Question

Is this semi-autonomous version merely waypoint following or will it sense the road? Will it also have obstacle avoidance capability?

Semi-Autonomous control is not required to be merely waypoint following, nor is it required to sense the road. Obstacle avoidance is not a requirement. The technology is specific to each offerors' design and the responsibility of the offeror.

Please refer to P-Spec-526 in Attachment 0001 RCIS P-Spec.

#18 8/4/2016 Pre-Solicitation

Conference Question

Does the system need to work in adverse weather conditions like dust, fog?

Yes, refer to Attachment 0001 RCIS P-Spec dated 21 July 2016, Section 3.4.2 pages 103 - 106 .

#20 8/4/2016 Pre-Solicitation

Will RCIS only be expected to follow defined lanes or roadways autonomously similar to AMAS/ACO's intended capability?

No, there is no requirement to follow defined lanes or roadways autonomously similar to AMAS/ACO's intended capability.

#21 8/4/2016 Pre-Solicitation

Conference Question

What other automation has not been talked about but is necessary for RCIS?

All requirements are contained in Attachment 0001 RCIS P-Spec dated 21 July 2016. Any updates to the requirements of this procurement will be articulated in Attachment 0001 RCIS P-Spec in the final RFP.

#22 8/4/2016 Pre-Solicitation

Conference Question

Is the SAC integrated add-on kit meant to be temporary or will it be part of the base platform?

Please refer to Attachment 0001 RCIS P-Spec dated 21 July 2016.

There are requirements throughout the P-Spec addressing the integration and mounting, and those components which are required to be removable. The term 'temporary' is not used in the P-Spec. The SAC integrated add-on kit is not part of the base platform. Any updates to the requirements of this procurement will be articulated in Attachment 0001 RCIS P-Spec in the final

RFP.

#24 8/4/2016 Pre-Solicitation

Conference Question

How important will be compatibility of this system with

Leader-Follower/ACO/Autonomous Ground Resupply, IOP, and Victory?

The SAC system is required to implement IOP. Please refer to the RCIS PWS and Attachment 0001 RCIS P-Spec dated 21 July

2016. There is no requirement to be compatible with Leader-

Follower/ACO/Autonomous Ground Resupply or Victory.

#26 8/12/2016 Pre-Solicitation

Conference Question

Will any level of technical data (shop manuals, schematics, etc.) on the base vehicle be available to contractors pre- or post-award beyond what has already been published on FBO as of August 11, 2016?

Yes. Shrinkwrap CAD data for the D-HMEE will be available pre-award and provided with the final RFP release. Electrical and

Hydraulic schematics for the D-HMEE will be available post-award.

#28 8/12/2016 Pre-Solicitation

There was mention of a dismount OCU capability/requirement, but also a head-pointed capability/requirement on the OCU. It may be difficult to support these two requirements combined in a logical, safe fashion. Can the Government clarify or provide any guidance here as to what the requirement is or is not?

The head aimed control viewer is only required when operating in the MPCV Control Vehicle. It is not intended for use in the dismount mode. This will be clarified in Attachment 0001 RCIS P-

Spec, section 3.2.3.3.4, in the final RFP.

#29 8/12/2016 Pre-Solicitation

Conference Question

What level of day-to-day maintenance can the system require and still be acceptable to the mission? E.g.

wiping off sensor lenses, etc.?

Per the RCIS Operational Mode Summary/Mission Profile

(OMS/MP) (Attachment 0005), Preventive Maintenance Checks and Services (PMCS) is completed before and after missions. Per the RCIS Performance Specification (Attachment 0001), RCIS

PMCS shall be completed in 30 minutes or less Thershold (T), 10 minutes or less Objective (O), reference P-Spec 579 section

3.3.2.2.2.

#31 8/12/2016 Pre-Solicitation

Conference Question

Will the Government be handling ATEC/related validation and certification activities, or are those the responsibility of the contractor to line up and execute?

The Contractor will provide test certifications per the

Attachment 0001 RCIS P-Spec section 4. The Contractor will also support the Government with ATEC documentation deliverables per the PWS, section C.16 and C.21.16.

#32 8/12/2016 Pre-Solicitation

Conference Question

Will the Government entertain flexible terms in terms of payments and financing to accommodate larger purchases (particularly in the production phases)?

The Government has not yet made any determination regarding financing. The final RFP will reflect the Government's determination regarding financing.

#37 8/12/2016 P-spec-754 3.2.3.7.6

Non-Line of Sight

(NLOS)

Range

The RCIS Type I shall control the R-

HMEE in the unmanned mode up to a distance of

100 meters Non

Line-of-Sight

(NLOS) (T), up to

500 meters (O), from the OCU.

The definition of NLOS in section 6.2 describes line of sight obstructions such as buildings, terrain features, vegetation, etc. It will be very difficult to predict the RF path losses through all possible combinations of materials and all possible material thicknesses that may be encountered. Could this requirement be reworded to provide the maximum RF path loss through the obstructions instead, given in terms of decibels (dB)?

That would give the contractor the ability to precisely define the performance parameters for the RCIS radio transmitters and receivers, and allow the Government to perform controlled laboratory tests to verify that the requirement is met in the delivered system.

Yes. The Government will update the requirement in the RCIS P-

SPEC Attachment 0001 to be released with the final RFP.

#38 8/12/2016 P-spec-2987 3.2.3.6.4.

Integrate

Boom

Arm

Attachme nts

The RCIS Type I shall integrate the rake and spork, air spade, light and measurement attachments onto the boom arm without interfering with each other and the classification camera (T), without interfering with all attachments (O).

Is any data available for the clearance volumes between the D-HMEE unique interrogation attachments (Rake and Spork/Air Spade, Clamshell Bucket, Backhoe) and the RCIS Type I classification equipment?

Yes. Shrinkwrap CAD data will be available and provided with the final RFP release.

#47 8/15/2016 Pre-Solicitation

Conference Question

Has the HMEE ICD been validated by the government or an independent third party? If not, can HMEE delivery be moved closer to the contract award date in order to ensure that all of the appropriate IO and sensors are documented and functional?

No, the D-HMEE Robotic ICD (Attachment 0003) has not been validated by a third party. The Government will consider validating the ICD, and also consider moving the D-HMEE delivery closer to contract award.

#48 8/15/2016 Pre-Solicitation

Conference Question

Have the HMEE CAN latency and the curve of braking distance vs speed been measured? Can they be added to the HMEE ICD?

No, the D-HMEE CAN latency and the curve of braking distance vs speed has not yet been measured. The Government will consider obtaining this information and providing it with the final RFP release.

#50 8/15/2016 Pre-Solicitation

Is there a Risk Reduction Test (RRT), that allows the

Government and Army test community to learn how to test the system, scheduled prior to Government Test as part of the approved program schedule?

The Government will perform Risk Reduction Testing during the

TARDEC SIL or "Government Simuluation" (PWS C.15.2) and

"Contractor Verification Testing" (PWS C.16.3).

#51 8/15/2016 Pre-Solicitation

Conference Question

When being tele-operated, can the HMEE’s reverse speed be limited by the MBU B-Kit? This would reduce the requirements and cost of obstacle detection components on the rear side of the HMEE.

Yes. The Government will update the speed requirement for reverse in the RCIS P-SPEC Attachment 0001 to be released with the final RFP.

#52 8/15/2016 Pre-Solicitation

Conference Question

Will the IOP instantiation for the RCIS program be released with the RFP?

Yes, the Government will provide a RCIS-specific IOP instantiation with the final RFP release.

#53 8/15/2016 Pre-Solicitation

Conference Question

How will the proposals be evaluated in regards to cost and performance? LPTA? Best Value?

It is the Government’s intent to evaluate proposals using a best value tradeoff process . Please continue to check FedBizOppz

(FBO) for draft solicitation/documents or for the solicitation release.

#54 8/15/2016 Pre-Solicitation

Conference Question

What is the percentage of time in a 72 hour mission the system will be operated in unmanned mode (including tele-operated, semi-autonomous, and autonomous modes)?

Please refer to Attachment 0005 - RCIS Operational Mode

Summary - Mission Profile (OMS-MP).

#59 8/15/2016 Pre-Solicitation

Conference Question

P-spec-507 requires wireless communications be

“closed loop, point to point system which is only capable of transmitting data and video between the R-HMEE and the OCU”. Is this requirement a limitation due to safety and information security reasons or would meshing type radios be an acceptable solution.

P-spec-507 states that the communications shall be point-to-point, transmitting data and video between the R-HMEE and the

OCU. Additional radios not on the R-HMEE or OCU to establish a mesh network or act as repeaters would not meet the requirement.

#60 8/15/2016 Pre-Solicitation

Is the intent of the Head Aimed Control Viewer (P-Spec-

356): ”to view video from the R-HMEE as if they were seated in the R-HMEE driver's seat” such that the operator should see all interior items (gauges , indicator lights, physical controls) including obstructions presented by cab?

No. P-spec-356 will be revised in the final Attachment 0001

RCIS P-Spec.

#62 8/15/2016 Pre-Solicitation

Conference Question

Separation of applique kit prime contractor and JCB will increase program costs and overall program risk.

a. Example: If base D-HMEE does not meet performance requirements or has minimal factor of safety, this will incur additional risk due to separation of program this is an unknown factor.

Contractor advised that statement was only meant to express a comment. There is no question to answer.

#63 8/15/2016 Pre-Solicitation

Conference Question

There is not enough information regarding the physical interfaces to the D-HMEE. Provision of detailed Interior and Exterior CAD data for development of mechanical interfaces would drastically reduce program cost and risk.

Noted. Shrinkwrap CAD data will be available and provided with the final RFP release.

#65 8/15/2016 Pre-Solicitation

Conference Question

There is no mention of feedback sensors on the loader and backhoe joints, some of the semi-autonomous behaviors suggested would require it. Will the D-HMEE come with these sensors already provided?

No. There is no information beyond that documented in the D-

HMEE Robotic ICD (Attachment 0003). The RCIS Type I vendor is responsible for providing any equipment such as feedback sensors if required by their design.

#70 8/15/2016 Pre-Solicitation

Conference Question

Please reference Attachment 02, ICD HMEE. What are the configuration items of the Crew Protection Kit hardware and it interfaces to the HMEE?

Information regarding the CPK configuration items or interfaces is not available. However, shrinkwrap CAD data will be available for the D-HMEE and provided with the final RFP release. The

CAD data will contain both the unarmored D-HMEE cab and the armored D-HMEE cab (with the CPK).

#71 8/15/2016 Pre-Solicitation

Will CAD models of the HMEE and MPCV control vehicle be provided? If so, when? If not, will space claim be provided within which contractor can locate items?

Shrinkwrap CAD data will be available for the D-HMEE and provided with the final RFP release. The CAD data will contain both the unarmored D-HMEE cab and the armored D-HMEE cab

(with the CPK).

CAD data for the MPCV is not available. The Government is making the MPCV available to industry to inspect during RCIS

Type I vehicle vieiwing be held on 12-13 Oct 2016 in Warren, MI.

#72 8/15/2016 Pre-Solicitation

Conference Question

Will feedback from steering wheel angles of all 4 wheels on CAN bus? How about feedback on service brakes?

No, there is no feedback from steering wheel angles of all 4 wheels on CAN bus. No, there is no feedback on service brakes.

The RCIS Type I vendor is responsible for providing any equipment such as feedback sensors if required by their design.

#73 8/15/2016 Pre-Solicitation

Conference Question

Please reference Attachment 03, D-HMEE Robotic

Interface ICD. Section 4.5.3 details an emergency stop’s

(E-STOP) recommended location and indicates that provisions for one have been made. The performance specification, however, has no requirement for a physical E-Stop on the MBU. Should the MBU B-Kit provide a physical emergency stop or are the provisions solely for the purposes of testing?

In the manned mode, the D-HMEE emergency stop is provided by the OEM on the D-HMEE and as described in section 4.5.3 of

Attachment 0003.

In the unmanned mode the operator has the OCU. Attachment

0001 RCIS P-Spec-546 states the OCU shall have a dedicated physical switch to enable one operator using the OCU to initiate an emergency stop. Please refer to Attachment 0001 RCIS P-

Spec dated 21 July 2016.

#74 8/15/2016 Pre-Solicitation

Please more clearly define Semi-Autonomy requirements. For example, while maximum and average speeds are designated for Semi-Autonomous control, what exactly will the system be doing while driving at these speeds? Moving in the convoy formation? Moving from the stationary convoy formation to potential threat (on its own)? Etc. If collision avoidance is included in Semi-Autonomous capabilities it is possible that the system could initiate a specific behavior that will allow it to avoid hitting a human or object, but then this behavior inadvertently causes a vehicle-to-vehicle collision. What type of decision path protocol will be required for such scenarios? Could you provide more specific requirements around vehicle following behavior requirements? Can you provide an example of your implied Semi-autonomy definition? For example, are there industry standards that we can reference (e.g., NIST), or is it intended that the referenced TOPs define the required degrees of semi-autonomy. Also, while

TOP 2-2-540 provides limited detail on the definition of semi-autonomy, it lists the verification method for

Autonomous Navigation as “TBD.” Please clarify.

Regarding movement within formations, please refer to

Attachment 0005 - RCIS Operational Mode Summary - Mission

Profile (OMS-MP).

The Government will consider updating the Semi-Autonomy requirement in the RCIS P-SPEC Attachment 0001 to be released with the final RFP.

#75 8/15/2016 Pre-Solicitation

Conference Question

Are there any obstacle detection sensor restrictions? There are no restrictions on choice of technology. However, all sensors must be safe for use at Army test centers and within

Army units once fielded. Lasers must meet all requirements of

MIL STD 1425A.

#76 8/15/2016 Pre-Solicitation

Is road following behavior based on sensors only or on a pre-loaded map?

There are no restrictions on methods of semi-autonomous control. However, all information necessary for operation such as maps are the offeror's responsibility, no maps will be provided by the Government.

#77 8/15/2016 Pre-Solicitation

Conference Question

Please reference PSPEC – 546: Is this stop in accordance with 3.2.2.8.2 stopping distance?

No. The stopping distance in Attachment 0001 RCIS P-Spec-290 is specific to the D-HMEE. P-Spec-546 is required of the SAC system IAW the Unmanned Ground Vehicle (UGV)

Interoperability Profile (IOP).

#78 8/15/2016 Pre-Solicitation

Conference Question

Is it the Government’s intent that the RCIS Type I prime will develop the RCIS-specific IOP instantiation, or will one be provided?

Yes, the Government will provide a RCIS-specific IOP instantiation with the final RFP release.

#81 8/15/2016 Pre-Solicitation

Conference Question

Please reference PSPEC – 712: PSPEC States reliability of Host Vehicle and Control Vehicle shall not be degraded– What are the baseline reliabilities of the control and host vehicles?

This question refers to an outdated version of the RCIS P-Spec.

Please refer to P-spec-712 in Attachment 0001 RCIS P-Spec dated 21 July 2016 which contains revised language.

#82 8/15/2016 Pre-Solicitation

Conference Question

Please reference PSPEC – 2993: Interrogation Time –

How do these required times compare to the interrogation times when an operator is seated in the cab of the HMEE? The mobility requirements (PSPEC –

276, 281, 469, 2947, 301, 302, 2892, 2893, etc.) allow for up to 10% degradation in performance when performing unmanned movements. Should the same logic apply to performance associated with using the implements remotely? It would not make sense to require a remote operator to perform a task faster than an operator sitting in the vehicle’s cab.

The requirements for interrogation time were specified by the military user. Since this is a new capability, there is no documented human performance baseline. Refer to

Attachment 0001 RCIS P-Spec dated 21 July 2016; specifically P-specs 402, 403, 440, 441, 442, 2997, 443, 2998, and 444.

The 10% degradation was also specified by the military user, refer to P-specs 281, 301, 302, 2892, 2893, 2949, 291, and 309.

No, the same logic does not apply to peformance assoicatied with using the implments remotely because there is documented test results for manned HMEE automotive performance.

#84 8/15/2016 Pre-Solicitation

Will HMEE have a SASM GPS module? If so, what is the message protocol for SASM GPS? Will command vehicle have SASM GPS? If so, Will the OCU have access to that

GPS data? Will the vehicle to be followed (MPCV, etc.)

provide GPS position to the HMEE vehicle?

No, the HMEE does not have a SASM GPS module, therefore there is no message protocol for SASM GPS.

The command vehicle may or may not have SASM GPS.

Regardless, the OCU will not have access to that GPS data.

The Government is not providing GPS position from the vehicle to be followed (MPCV, etc.) to the HMEE vehicle. The offeror is responsible for providing GPS position from the vehicle to the

HMEE if needed as part of its design solution.

#85 8/15/2016 Pre-Solicitation

Conference Question

Is the HMEE vehicle position going to be on CAN bus? Is there an IMU aside from tilt sensor on base vehicle?

No, there is no HMEE vehicle position on the CAN bus.

No. There is no IMU aside from tilt sensor on base vehicle.

#86 8/15/2016 Pre-Solicitation

Conference Question

What type/format of map data will be provided for semi-autonomous operations? For example, Blue Force tracker?

No map data will be provided by the Government, nor is it a requirement of the P-spec.

#87 8/15/2016 Pre-Solicitation

Conference Question

What type/format of path data would be provided/imported, or would it only be generated locally based on operator input?

No path data will be provided by the Government. This is specific to each offerors' design and the responsibility of the offeror.

#88 8/15/2016 Pre-Solicitation

Conference Question

Please reference PSPEC – 3173: RCIS Vehicle Audio – Is there a minimum (or range) of dB sound level(s) that must be detected? It may be necessary to define ranges during while HMEE is at standstill, engine off and a different range while in motion

Yes. The Government will update this requirement to clarify a range of sound (in dB) in the RCIS P-SPEC Attachment 0001 to be released with the final RFP.

#89 8/15/2016 Pre-Solicitation

Please reference PSPEC – 356: View from Vehicle

Driver’s Seat. Do the requirements of 3.2.3.4.6.4 and

3.2.3.4.6.5 apply to this requirement. For example, if the design must account for the 5th to 95% percentile soldier, the viewing angle center lines change over that human height range and it may be required to move the center point of the camera to accommodate the entire range. Since the operator will be seated in the Buffalo viewing a camera mounted within the HMEE cab it may better to set the view point from a maximum advantage point of camera regardless of the height of the original

HMEE driver.

No, the requirements of P-spec-325 in 3.2.3.4.6.4 and P-spec-

318 in 3.2.3.4.6.5 do not apply to the P-spec-356 requirement.

#107 8/15/2016 Pre-Solicitation

Conference Question

Does the Government anticipate that additional attachments or documents will be released prior to the final RFP (e.g., Attachments 17, 25, 26, 28, 30, 33, 34, 35, 37, and 40)?

The Government will not release additional attachments prior to final RFP release.

#19 8/4/2016 Pre-Solicitation

Conference Question

Will the system be expected to operate in GPS-Denied areas?

Yes.

The Government will revise this requirement in the RCIS P-SPEC

Attachment 0001 to be released with the final RFP.

#23 8/4/2016 Pre-Solicitation

Conference Question

For LRIP and FRP, are the vehicle purchases going to be done all with the SAC/semi-autonomy kits, or split with some having with some without)?

For LRIP and FRP all vehicles (R-HMEEs and MPCVs) are required to have SAC system (MBU and OCU) kits. For LRIP and FRP the integration into MPCVs will occur as specified in PWS Sections

C.21.15 and C.22.15.

The Government will clarify these requirements in the PWS to be

#25 8/4/2016 Pre-Solicitation

When will industry have an opportunity to physically see/work with a HMEE in order to better gauge what it will take to integrate the SAC kits?

Please refer to the Vehicle Viewing Invitation on FBO. The

Vehicle Viewing occurred on October 12-13, 2016.

#27 8/4/2016 Pre-Solicitation

Conference Question

A major risk reducing activity in the development and testing of systems like RCIS is M&S. We thus have four

M&S related questions: a. What data (CAD models, location of center of gravity, etc.) on the Hemi and

Buffalo will be provided to allow contractors to simulate the systems during the engineering phase?

b. Will the government provide models or simulation capability, or support M&S activity as part of the engineering phase of the program?

c. Will there be any required deliverables in terms of models or simulations of the SAC or integrated system, and for what M&S environment?

d. Will there be any required deliverables to the

Government in terms of performance characterization demonstrated through M&S?

a. Test data of the D-HMEE will be provided post-award. This data will include center of gravity and other measured parameters related to Mobility P-spec-276. No data will be provided for the MPCV.

b. No, the Government will not provide models or simulation capability as part of the engineering phase of the program.

c. No.

d. No, there is no requirement for M&S deliverables. But, M&S activity may be proposed by the offeror to support engineering development.

#30 8/12/2016 Pre-Solicitation

Conference Question

Will the Government be willing to ship vehicles to a central point where the contractor can perform the conversion activities, or must they be done as disparate locations?

Yes, the Government will ship D-HMEE vehicles to the contractor's location for EMD, LRIP, and FRP.

However, the Government will ship MPCV Control Vehicles as

GFE to the contractor's location for EMD only. The contractor is required to integrate into MPCV Control Vehicles at disparate locations in LRIP and FRP IAW PWS Sections C.21.15 and C.22.15.

The Government will clarify these requirements in the PWS to be

#33 8/12/2016 Pre-Solicitation

Does the government envision having any sort of subcontract with the platform manufacturer (either directly or with the prime for RCIS) to answer questions, provide any support to the effort, etc.?

Please refer to JCB Organizational Conflict of Interest (OCI) notice posted to FBO on August 9, 2016.

#34 8/12/2016 P-spec-3208 3.2.3.2.3.

2 MBU

Video

Display

Spatial

Coordinat es

The OCU video display shall provide information of the three spatial coordinates in the workspace (i.e., X, Y, and Z) IAW MIL

STD 1472, Section

5.12.2.5.1 (T = O)

Can the Government provide additional details about this requirement? For example, is the {0,0,0} HOME reference point permanently fixed to a point on the vehicle or is it set by the operator? Is the point being tracked set to a fixed location on the classification equipment or is set by the operator?

Yes, In P-spec-3198 and 3208, the three spatial coordinates in the workspace represent position grid information for position location. The Government will revise this requirement in the

RCIS P-SPEC Attachment 0001 to be released with the final RFP.

#35 8/12/2016 P-spec-356 3.2.3.3.4.

1 View from

Vehicle

Driver's

Seat

The Head Aimed

Control Viewer shall cover both eyes and enable the operator in the

Control Vehicle to view video from the R-HMEE as if they were seated in the R-HMEE driver's seat (T =

O).

1) Is there a preferred location for the Head Aimed

Control Viewer camera when the HMEE is in the automotive mode?

2) Is there a preferred location for the camera when the

HMEE is in the classification mode?

3) Does the same camera need to see both forward and backwards?

4) If the camera needs to point forward and backwards, is there a requirement for the user wearing the Head

Aimed Control Viewer to be able remotely control the camera to rotate 180 degrees?

1) No. There is not a preferred location for the position for the vehicle camera(s), but the design is required to meet P-spec-757

Field of View.

2) No. There is not a preferred location for the classification camera on the HMEE other than being integrated on the boom arm (P-spec-373).

3) No. The same camera is not required to see both forward and backwards.

4) No, see the answer to #3 above.

#36 8/12/2016 P-spec-330

P-spec-2914

P-spec-333

P-spec-2915

P-spec-335

P-spec-2916

P-spec-336

P-spec-2917

3.2.3.4.4.

3 through

3.2.3.4.4.

Identify and

Recognize

The SAC System shall enable an operator using the

OCU to recognize …

The SAC System shall enable an operator using the

OCU to identify ...

The Government has taken great care to provide separate requirements for “recognize” and “identify”.

The two terms have nearly identical meanings. What is the significance of the separate requirements?

After review there is no difference between the two separate requirements. The Government will revise the RCIS P-SPEC

Attachment 0001 to be released with the final RFP.

#39 8/12/2016 P-spec-3272 3.2.3.7.12

Spectrum

Agile

Radio

The RCIS Type I wireless communications shall be spectrum agile, capable of changing channels in the frequency spectrum to be mutually compatible with other electronic equipment operating in its area of operation without degrading performance, to include multi-national forces, and comply with spectrum regulations of other nations.

Is any additional information available for the existing

RF equipment on the D-HMEE and MPCV vehicles, such as the DUKE V2/V3, SINCGARS, GPS receiver, and MT-

2011 transceiver? To determine compatibility with the

RCIS RF equipment, the contractor will need to know the frequency, power, and bandwidth of the other emitters and the frequency, bandwidth, and selectivity of the other receivers.

No. All available information is contained in Attachment 0002

HMEE ICD and Attachment 0004 Control Vehicle ICD.

#40 8/12/2016 P-spec-3159 3.3.2.2.4

Provide

Built-In

Test (BIT)

In manned and unmanned mode, the RCIS Type I shall include Built-

In Test (BIT) to automatically identify faults to a single component and alert the operator (T = O).

Can the Government confirm that the BIT needs to identify failures to the field replaceable modular level;

i.e. the OCU, MBU, computer systems, radios, cameras, etc.? Is that what is meant by the term “component”?

Yes. To clarify, component in P-spec-3159 means a field replaceable piece of equipment (OCU, MBU, computer systems, radios, cameras, etc.). The Government will revise this requirement in the RCIS P-SPEC Attachment 0001 to be released with the final RFP.

#41 8/12/2016 RCIS Program

General Question

The TRADOC requirement developer includes rationales and operational significance in the originating requirements document. This information could be valuable for the offeror to gain further understanding of the requirements driving the Performance Specification.

Other programs, to include most recently Mobile

Protected Firepower (MPF), have released their requirements document to industry. Given this, will the

RCIS program release the base requirements document to industry? And, if so, when would this document be released?

No. PdM ALUGS coordinated with the user who decided not to provide the User Requirements Document with the final RFP.

Please refer to the RCIS Operational Mode Summary/Mission

Profile (OMS/MP) (Attachment 0005).

#42 8/12/2016 RCIS Program

General Question

The offerors were unable to inspect an actual HMEE or

Buffalo MPCV during the RCIS Industry Day on 1 August

2016. Will the RCIS program office arrange for offerors to inspect a HMEE and Buffalo MPCV prior to the release of the final RFP?

The Vehicle Viewing occurred on October 12-13, 2016. Please refer to the RCIS Vehicle Viewing Pictures and HMEE CAD Models and Data Information Notice posted 12 DEC.

#43 8/15/2016 Pre-Solicitation

Conference Question

Will the D-HMEE's for LRIP be released to the successful bidder in a single delivery or will they be received IAW a delivery schedule?

The Government will detail the delivery schedule in the Section B

CLIN narratives of the final RFP.

#44 8/15/2016 Pre-Solicitation

The proposed timeline shows PQT starting immediately after receipt of the LRIP D-HMEE's. How much time will be allowed to convert the vehicles to R-HMEE configuration?

The Government will detail the delivery schedule in the Section B

CLIN narratives of the final RFP.

#45 8/15/2016 Pre-Solicitation

Conference Question

What schedule does the Government anticipate that the FRP D-HMEE's will be released to the successful offeror for conversion to the R-HMEE configuration?

The Government will detail the delivery schedule in the Section B

CLIN narratives of the final RFP.

#46 8/15/2016 Pre-Solicitation

Conference Question

With the latest release of information regarding the OCI imposed on the HMEE OEM, how does the Government anticipate offerors will receive any requested support from the OEM during the RFP stage?

The Government intends to release a final RFP package with sufficient detail to prepare a proposal. Questions during the RFP process will be accepted by the Government through FBO.

#49 8/15/2016 Pre-Solicitation

Conference Question

What kind of measurement capability, accuracy, and distance does the government envision for the classification sensors?

Please refer to Attachment 0001 RCIS P-Spec dated 21 July 2016.

P-spec-400 requires measuring the dimensions [depth and width] of excavated holes and suspected hazards. The measurement attachment is used with the classification camera

(both are mounted on the boom arm) to determine the dimensions of hazards. Please refer to the objects in Attachment

0001 Appendix A.

Accuracy: This capability is required to allow the operator to discern the objects in Attachment 0001 Appendix A.

Distance: Per P-spec-400, the capability is required to measure the depth of the excavated holes.

#55 8/15/2016 Pre-Solicitation

What are D-HMEE performance characteristics in regards to the RCIS P-SPEC? (as applicable)

a. Will D-HMEE verification and validation testing EE be available to bidders for RFP? If not will they be available to prime Contractor after award?

The Government will provide some D-HMEE performance characteristics in regards to the RCIS P-SPEC based on proof-of-concept test results.

The test results will address mobility, center of gravity, electromagnetic compatibility (EMC), human factors, and reliability.

The test results will be made available to the contractor after contract award.

#56 8/15/2016 Pre-Solicitation

Conference Question

It is understood that JCB OCI will preclude bidders from directly engaging JCB support during the RFP period of the program. Will the prime contractor be able to engage JCB after contract award for program support?

A potential OCI, as defined in FAR Subpart 9.5, has been identified and is anticipated to occur if the performance of work under contract, W56HZV-14-C-0154, is not completed prior to the release of the Request for Proposal (RFP) for the Route

Clearance Interrogation System (RCIS) Type I Vehicle. JCB is prohibited from participating as a prime or sub-contractor, or as a consultant to any third party in the RCIS Type I RFP W56HZV-15-

R-0156 or the resultant contract.

Refer to JCB Organizational Conflict of Interest notice posted to

FBO:

https://www.fbo.gov/utils/view?id=5db1e189f0e2f6b00e0ec10e

3e3b9c94

#57 8/15/2016 Pre-Solicitation

Conference Question

Prime contractor is to provide overall system safety documentation for the RCIS system (which by definition includes the D-HMEE). In light of the OCI, how will the prime contractor be responsible for obtaining the necessary support from JCB?

This requirement has been changed. The Prime Contractor shall only be responsible for the system safety approach for the SAC system in the manned and unmanned modes. This will be reflected in the PWS to be released with the final RFP.

#58 8/15/2016 Pre-Solicitation

Will the Applique Kit Prime Contractor be involved in an overall system configuration control board after CDR to ensure changes made to the D-HMEE do not cause adverse effects to the RCIS system?

No. The Government will engage with the RCIS Type I vendor upon any proposed configuration changes to the D-HMEE at the regularly scheduled IPTs in accordance with the PWS Section

C.3.5.

#61 8/12/2016 Pre-Solicitation

Conference Question

It is understood that the D-HMEE to applique kit interface will not be IOP compliant.

a. Is this the only non-IOP compliant interface on the

RCIS Type I system?

b. What are the threshold and objective IOP attributes required for compliance?

c. How will IOP compliance be verified? Will system need to complete 3rd party testing

(TARDEC IOP CVT)?

a. All interfaces (IOP and non-IOP) are contained in ICD

Attachments 0002, 0003, and 0004, and the RCIS P-spec

Attachment 0001.

b. Refer to P-spec Section 3.2.3.7.8 Interoperability Profiles.

c. The Contractor shall perform IOP Compliance verification for the SAC System prior to PDR and CDR. Government IOP compliance validation will occur via TARDEC SIL using the

TARDEC IOP CVT prior to TRR. This will be reflected in the Final

RFP.

#67 8/15/2016 Pre-Solicitation

Conference Question

Please reference Attachment 04, ICD MPCV. Please provide all mechanical interfaces in and around seat 6.

CAD data for mechanical interfaces in and around seat #6 will be provided by the Government as part of the RCIS RFP.

Also, please refer to the Vehicle Viewing Invitation on FBO. The

Vehicle Viewing occurred on October 12-13, 2016.

#68 8/15/2016 Pre-Solicitation

Conference Question

Please reference Attachment 04, ICD MPCV. Only limited data on power was provided; many other standard power data items should be made available.

For example, is the power AC or DC; what cycle; 400

HZ? What is the quality of the amperage and voltage?

Are there any spurious voltages?

The MPCV has a 400amp alternator that provides 28 VDC IAW

MIL-STD-1275. The contractor shall integrate to this vehicle power through the Power Distribution Module as specified in

Attachment 04, Control Vehicle ICD.

The Government will clarify this information in Attachment 04, Control Vehicle ICD, to be released with the final RFP.

#69 8/15/2016 Pre-Solicitation

Please reference Attachment 04, ICD MPCV. How much weight can the Digi rack handle?

The Digi Rack can hold 30 pounds.

The Government will clarify this information in Attachment 04, Control Vehicle ICD, to be released with the final RFP.

#79 8/12/2016 Pre-Solicitation

Conference Question

Please reference Attachments 24, 27 and 41. Is it anticipated that classified information will be released to bidders during the RFP phase, or only upon contract award?

Attachments 24, 27 and 41 have been posted to Federal

Business Opportunities (FBO) . CUI will be made available to offerors upon an approved request. Requests for CUI documents must be made through the FBO website via Explicit Access

Request. FBO will prompt you for your firm's Marketing Partner

ID Number (MPIN) which is tied to a contractor CAGE code. Once a request has been made, an automated email will be generated to the Government reviewer. The Government reserves the right to request additional information to support releasing documentation. All CUI must be handled in accordance with

(IAW) the Security Classification markings on each individual document. Direct links to the CUI documents are available on the

RCIS FBO webpage.

#80 8/12/2016 Pre-Solicitation

Conference Question

Please reference PSPEC 2946: The PSPEC states that no degradation is allowed in manned mode. Will the original HMEE PSPEC be tested with the SAC disabled to verify original operation capabilities?

Yes, with respect to P-spec-2946 the Government will conduct demonstration(s) during the RCIS PPQT to verify the R-HMEE operator is able to manually operate the R-HMEE with no degradation.

However, the entire original HMEE PSPEC will not be tested with the SAC disabled to verify original operation capabilities.

#83 8/12/2016 Pre-Solicitation

Please reference PSPEC – 572: SAC MTBEFF –Will the failure of a GFE vehicle during RAM testing be scored against the contractor? For example, during the RAM test, the SAC will brake speed. The brakes may fail one

(1) time and not be repeatable. The failure may have been with the HMEE brakes or the SAC interface with the brakes. In this instance, how will that brake function failure be scored?

Please refer to the RCIS Failure Definition and Scoring Criteria

(FDSC) (Attachment 0013) for details on scoring test incidents.

Whether or not the failure of a GFE vehicle is scored against the contractor depends on the cause of the failure. For example, if the HMEE brakes fail and this failure is not related to the SAC kit, then the failure will be scored as GFE and not scored against the

SAC contractor. However, if the HMEE brakes fail and this failure is related to the SAC kit, then the failure will be scored as

GFE/Integration and will be scored against the SAC contractor

(PSPEC 712 - shall not degrade reliability of the HMEE base platform). The SAC contractor may provide information, evidence, or opinions on the scoring of test incidents, however the Government will determine the final scoring of test incidents at Government Scoring Conferences.

#90 8/15/2016 Pre-Solicitation

Conference Question

Please reference PSPEC – 699: RCIS Vehicle Video –

How many video streams should be viewable simultaneously? Are cameras required to be HD?

P-spec-699 requires one or more video streams. The number of video streams to be viewable simultaneously is not restricted.

P-spec-315 requires high quality, high resolution video. There is no requirement for the cameras to be HD. The RCIS Type I vendor may propose HD cameras as part of their design.

#91 8/15/2016 Pre-Solicitation

Conference Question

DRI related Requirements: What lighting conditions are detection/recognition/identification requirements going to be tested under?

Per P-spec-335, Lighting Conditions for testing will be during daylight, clear conditions.

The Government will clarify these conditions for all P-specs in

Section 3.2.3.4.4 in the RCIS P-SPEC Attachment 0001 to be released with the final RFP.

#92 8/15/2016 Pre-Solicitation

Conference Question

What are the minimum acceptable frame rates for the

RCIS video cameras?

Please refer to Attachment 0001 RCIS P-Spec dated 21 July 2016.

P-spec-516 requires streaming video from the R-HMEE to the

OCU at a minimum frame rate of 24 frames per second (fps).

#93 8/15/2016 Pre-Solicitation

PSPEC – 2923: Classification Camera – Under what lighting and environmental conditions are the cameras required to classify objects?

P-spec-626 requires the Environmental Conditions.

P-spec-433 requires during daylight, hours of darkness, low light conditions, and times of limited visibility (smoke, haze, fog, rain).

#94 8/15/2016 Pre-Solicitation

Conference Question

PSPEC – 374: High Quality Continuous Frame Digital

Video Stream - What is the definition of a “high quality” video stream in the context of RCIS? Are cameras required to be HD? What are the minimum acceptable frame rates of the classification cameras?