HMIF Common Dismounted Controller RFI 20231221 FINAL.pdf

Category Opportunity

DoD Communities of Interest Dismounted Controllers for Robotic Systems

Subject Human-Machine Integrated Formation (H-MIF) Common Dismounted Controller

Due Date 22 January 2024

Government Organization RCCTO: U.S. Army’s Rapid Capabilities and Critical Technologies Office

NAICS 541715 - Research and Development in the Physical, Engineering, and Life Sciences (except Nanotechnology and Biotechnology)

PSC Code AC33 – National Defense R&D Services; Defense-related activities; Experimental Development

Description The Army Rapid Capabilities and Critical Technologies Office (RCCTO) seeks approaches to create a standardized dismounted controller hardware to enhance interoperability and ease of use across different robotic systems in support of the Human-Machine Integrated Formation (H-MIF).

The controller should be applicable to a wide range of robotic platforms, including unmanned ground vehicles (UGVs) with assured teleoperation, unmanned aerial vehicles (UAVs), support maneuver and lethality assured control, variety of payloads (i.e., m the Common Remotely Operated Weapons System- Javelin (CROWS-J), Smoke Obscuration Module (SOM), Tethered Unmanned Aircraft System (T-UAS), and other dismounted robotic systems.

Key Features:

Modular Design: The controller should have a modular architecture to accommodate various hardware and software components.

Safety: Critical functionality for assured control of the UGV and Weapon as well as an integrated safety assured e-stop.

User-friendly Interface: Should be Warfighter Machine Interface (WMI) compliant.

Interoperability: Ensure compatibility with different robotic systems, communication protocols, and sensor types.

Durability: Develop a rugged and durable hardware design capable of withstanding harsh environmental conditions.

The RCCTO desires to expand their awareness of this information and capability across the industry, including not only traditional defense contractors and large businesses, but also to small businesses, nontraditional defense contractors, and academic/research institutions.

This is a Request for Information (RFI) only. This request shall not be construed as a solicitation announcement, invitation for bids, request for proposals, request for quotes, or an indication that the Government will contract for the items contained in this notice. Interested contractors are invited to provide responses to the RFI. Both large and small businesses, as well as academic institutions, are encouraged to respond. The information provided may be used by the Army in developing its acquisition strategy, statement of work/performance work statements, and/or statement of objectives.

Interested parties are responsible to adequately mark proprietary, restricted or competition sensitive information contained in their response accordingly. The Government will not reimburse respondents for any cost associated with the submission of the information being requested or reimburse expenses incurred to the interested parties for responses.

This request does not constitute a solicitation for proposals or the authority to enter negotiations to award a contract. No funds have been authorized, appropriated, or received for this effort. This request is intended to serve mainly as a request for information to assist with market research purposes. However, RCCTO reserves the right to utilize it as a Request for White Paper (RFWP) without any additional notification or documentation requirements to meet changing mission requirements or schedules, and to thus award one or more prototype project OTAs under 10 USC 4022 from this Opportunity. In such event, Technical Characteristics, Schedule and ROM (in descending order of importance and as described in this document) will be considered in evaluation of any submitted response, and in determining any selection of either a full, or partial solution.

Responses should include, but are not limited to the following:

Provide an overview of your company.

Provide examples of past work performed on common dismounted controllers for robotics systems.

*Note: Experience is not limited to Department of Defense work.

Provide a Rough Order of Magnitude (ROM) (Cost) and duration (Schedule) you require to design, build/integrate, test, and deliver two (2), common dismounted controller for the Robotic Control Vehicle (RCV), and the Small Multipurpose Equipment Transport (SMET) vehicles with the assumption that the Government will provide the RCV and SMET vehicles as Government Furnished Equipment (GFE) within 30 days after the project has started.

Provide an assessment of your ability to meet the following performance objectives.

*Note: If a performance objective is not feasible or contradicts another objective, please explain why, and provide a recommendation.

• Control Capabilities: Common dismounted controller system should support all the control types listed below. Interested Vendors shall insert recommendations where applicable:

o Ground Mobility - Wheeled Steering Curvature Control Speed Control (may be independent Throttle & Brake Controls) Gear Change (may be incorporated in speed control if input from user and feedback are sufficiently intuitive) o Ground Mobility - Tracked

Steering Curvature Control Speed Control (may be independent Throttle & Brake Controls) Gear Change (may be incorporated in speed control if input from user and feedback are sufficiently intuitive) Yaw (If zero-point turn capable) o Ground Mobility - Omni-Directional Drive Omni- Direction Control (Strafe Forward, Back, Left, Right) Speed Control (If Omni- Direction Control not implemented) Yaw Control o Air Mobility - Omni-Directional flight (i.e. quadcopter) Omni- Direction Control (Strafe Forward, Back, Left, Right) Speed Control if Omni-Direction Control not implemented (Positive to negative speed range) Altitude (Up, Down) Yaw Control o Air Mobility - Plane-like Flight Speed Control or throttle (Zero and Positive speeds only) Roll Control Pitch Control o All Mobility Speed Limiter o Gimbal Azimuth and Elevation Control Slew Speed/Sensitivity

LRF

POI Adjustment (Ranging) Target Tracking / Slew-to-Cue BSO Marking (SPOT Report) o General Camera Control Zoom Focus (Image Quality) Polarity (DAY/IR/NVIS) o Weapons / RWS Control SAFE/ARM Switch Trigger Firing Rate Menu Selection o Comms Push-to-Talk Net Change o Safety Mobility Inhibit Switch VST Button o General Mode Switch (Required where hardware interfaces are used in multiple non-simultaneous functions.)

• Sensor Integration o Implement a strategy to monitor video feed latency. Note Multi-Function Assured Control (Concept)

• Sub-System Integration: Common dismounted controller system should be integrated with all of the following sub-systems:

o WMI:

Integrate computer with necessary touch interface, RAM, processing power, OS, and any other hardware and software requirements to function as a

WMI.

o KDA SSCI:

Supply necessary power and packaging to host KDA SSCI Integrate with all fire controls o VST:

Supply power to host VST Supply comms interface for VST Host VST hardware and integrate VST Stop Button into handheld device o RVMS:

Supply power to and packaging to host RVMS Route any information to or through RVMS required for it to monitor controller operation Provide interface for RVMS to use to command a Mobility Inhibit, ETOP or any other actions RVMS supports o MPU5 / Silvus Radio Link:

Provide ergonomic antenna fixture for radio transceivers Provide power and packaging space for either radio Either package both MPU5 & Silvus into one kit, or provide modular system allowing field changing of radio type o SINCGARS:

Provide headset port Provide access to voice network connection Supply power for the headset o Removable battery Maintain at least 12 hrs. of operational time with chosen power solution Ideally compatible with BB2590. Otherwise integrate ruggedized removable battery

• Communication:

o Shall support Line of sight comms with controlled vehicle up to (1000m?)

o Shall support non-Line of sight comms with controlled vehicle up to using mesh networking of radio system o Minimize control input latency to ensure responsive and timely robotic system operation.

Keep overall system latency for the operator to 250ms or less and implement method to monitor comms latency.

o IOP V5 Compliance

• Safety o Safety controls shall be verified with function test on connection with vehicle, start-up must be automatically required, and may be fully automatic or involve user action (such as test pressing and releasing VST)

• Ergonomics o Total weight not exceeding <20 lbs. T, 15 lbs. or realistic value o Total hand-held burden not exceeding <5 lbs. T, 3 lbs. or realistic value o All components must either be held or worn on body (Plate carrier mounted, backpack, sling, etc.)

o All functions assigned a priority level of 1 shall be accessible within the thumb and index finger sweep of the operator's hand in the natural grip position without repositioning of the hand.

o All functions assigned a priority level of 2 shall be accessible within the thumb and index finger sweep of the operator's hand in the natural grip position with minor repositioning of the hand.

o All functions assigned a priority level of 3 shall be accessible with repositioning of the hand from the natural grip position.

o All functions assigned a priority level of 4 shall be implemented as space allows and shall have the function implemented in the Graphical User Interface.

o All functions assigned a priority level of 5 shall be considered for implementation pending all functions of priority 1 through 4 have been met and additional space has not been allocated.

o The controller design shall accommodate for the size of the 5 - 95% adult hand size for both male and female proportions.

o The force needed to actuate a push button switch shall be continuous at a rate of <insert relevant values of the force here> and displace a distance of <insert relevant values of the distance here>.

o The force needed to move a rotary dial from the current detent position to the next detent position shall be <insert relevant values of the force here> and the rotational displacement shall be proportional to the amount of detents (i.e., 360/detents).

o The force needed to move a toggle or 4-way switch from the neutral position to another position shall be continuous at a rate of <insert relevant values of the force here>.

o The displacement of a toggle switch shall be more than 20 degrees but no more than 30 degrees.

o The displacement of a joystick shall be more than 30 degrees but no more than 60 degrees and the force required to displace from the neutral position shall be <insert relevant values of the force here>.

o The displacement of a trigger shall be more than 20 degrees but less than 45 degrees if rotationally actuated or more than 5mm but less than 20mm if linearly actuated and the force shall be continuous at a rate of <insert relevant values of the rate here>.

o Safety Critical controls shall not be repurposed in across modes.

o Safety Critical controls may me inactive only in specific modes <should reference table of what modes safety critical interface function across modes. Such as no VST when flying UAV or change VST functionality.

o The system shall be usable wearing Flame Resistant Combat Gloves LIN DA154H o All switches shall provide a detent (i.e. physical click) at the electrical activation point of the switch.

o Activation of mobility inhibit switch(es) shall be performed by grasping the control with a natural grip and squeezing with the palm, proximal phalanx, or middle phalanx of the finger.

o Mobility inhibit switch(es) shall not require repositioning of the hand from the natural grip position to be activated, nor shall they be activated with the thumb or distal phalanx.

o A variety of switch caps shall be utilized to distinguish similar switches: flat, flat textured, concave, convex, concave dimple, convex dimple, etc. A unique switch cap type shall be utilized for each switch of the same type activated by the same finger / thumb.

o Switch caps shall provide a means to distinguish grouped functions.

o For any joystick including a momentary push button, the push button shall only be activated from the neutral position of the joystick.

o Should a screen be utilized, the screen shall be no larger than 10in diagonal, maintain a 16:9 aspect ratio, and support non-gloved and gloved touch input.

o

• Haptics o Haptic Feedback shall be provided to the operator's palms and index fingers with the use of motors located within the controller body and trigger bodies.

o Haptic Feedback intensity shall be configurable in scale from any percentage from 0 to 100% in no less than 10% increments.

• Ruggedization o The controller design, development, and assembly shall be handled in accordance with MIL-STD 810G and IP68 for construction.

o All port connections shall be reinforced by tri-start screw type connections.

o The cabling to the controller shall allow for flexibility and strain relief to prevent failure of the cable after 1000 hours of use.

o The cabling to the controller shall be coiled, spooled, or any other manner of self-withdrawing to allow for stretch.

• Lighting o Any status lights or backlight switch caps utilized shall be compatible with NVIS systems and have a black-out mode.

o Black Out mode.

o NVIS compatible mode.

o Dimmable screen to support naked-eye Night Ops.

o Sufficient screen brightness for direct sunlight at max setting (>500 lux).

Development and Testing:

• Prototyping: Develop prototype versions for iterative testing and refinement based on user feedback.

• Simulation: Provide prototypes that integrate with SIL / HILSILs for testing in virtual environments before field deployment.

• Benchtop Testing: Conduct benchtop experiments of controller, verifying system communication with available robotic systems early in development (prior to achieving mobility). Emphasis on checking for various failure conditions.

Standards and Compliance:

• Standards Adherence: Ensure compliance with relevant industry standards and protocols for interoperability and safety.

Training and Documentation:

• User Training: Develop training materials and conduct training sessions to familiarize users with the controller's features and functionalities.

• Technical Documentation: Provide comprehensive technical documentation to support maintenance and troubleshooting.

Security:

• Cybersecurity: Implement robust cybersecurity measures to protect the controller and connected robotic systems from unauthorized access and potential cyber threats.

Project Timeline and Milestones:

• Phases: Outline distinct development phases, milestones, and a timeline for the successful completion of the project.

Notice: Respondents are cautioned that Government support contractors may serve as non- Government advisors providing support and/or review of any submittals in response to this RFI.

These individuals will be authorized access only to those portions of the submission that are necessary to enable them to perform their respective duties. Such firms are expressly prohibited from competing on the subject acquisition. Submissions in response to this RFI constitutes approval to release submitted information to Government support contractors. All support contractors will comply with procurement Integrity Laws.

Recommendations: Based on your system’s capabilities as sought above and your company’s understanding of the operating environment, provide any additional recommended capability requirements and performance thresholds. Please highlight unique capabilities that make your product stand out. This information will help bound the art of the possible for the effort in the timeframe we have available.

REFERENCES: None

Provide Company information to include:

Name, Mailing Address, and CAGE Code (if available). Business Size Status for the North American Industry Classification System (NAICS) code of this RFI. Technical and Business Points of Contact to include telephone Numbers and E-mail Addresses.

Indicate whether your company is a Large Business, Small Business, or Academic Institution Indicate whether your company is a non-traditional defense contractor (*see definition below).

If your company's proposed approach has been proposed to or previously funded by any federal agency. Identify each specific agency and all applicable contract/agreement numbers. All interested parties should submit a capabilities statement with a maximum of ten (10) pages.

*Non-traditional defense contractor is defined in 10 U.S.C. § 3014 as an entity that is not currently performing and has not performed, for at least the one-year period preceding this RFI, any contract or subcontract for the Department of Defense that is subject to full coverage under the cost accounting standards prescribed pursuant to section 1502 of title 41 and the regulations implementing such section.

Submissions must be submitted no later than 16:00EST on 22 January 2024 via email to Simone Brightmon at simone.l.brightmon.civ@army.mil and Jolynda Ivy at jolynda.v.ivy.civ@army.mil All mailto:simone.l.brightmon.civ@army.mil mailto:jolynda.v.ivy.civ@army.mil submissions shall be clearly marked "Capabilities Statement for Army RCCTO HMIF Common Dismounted Controller". Only UNCLASSIFIED Capabilities Statements will be accepted.