Call_0004-_SOO_C-_Universal_Operator_Control_Unit_Platform.pdf

PDF 77 KB Posted

Attached to
First Responders Group Broad Agency Announcement
Solicitation number
HSHQDC-13-R-B0012
Issued by

About this file

SOO C- Universal Operator Control Unit Platform

View the file

Other files

File Type Posted
BAA_13-012_Call_0005_Questions_and_Answers-_Amendment_3.pdf PDF
BAA_13-012_Call_0005_Amendment_0005.pdf PDF
FRG_BAA_13-012_Version_10.pdf PDF
Amendment_00012_BAA-13-012.pdf PDF
BAA_13-012_Call_0005_Questions_and_Answers-_Amendment_2.pdf PDF
BAA_13-012_Call_0005_Amendment_0004.pdf PDF
BAA_13-012_Call_0005_Amendment_0003.pdf PDF
Amendment_00011_BAA-13-012.pdf PDF
FRG_BAA_13-012_Version_9.pdf PDF
BAA_13-012_Call_0005_Amendment_0002.pdf PDF
BAA_13-012_Call_0005_Questions_and_Answers-_Amendment_1.pdf PDF
BAA_13-012_Call_0005_Amendment_0001.pdf PDF
BAA_13-012_Call_0005_Amendment_0001.pdf PDF
BAA_13-012_Call_0005_Questions_and_Answers.pdf PDF
Call_0005-_SOO_B-_Emergency_Response_Vehicle_Warning_for_Civilians.pdf PDF
Call_0005-_SOO_C-_Emergency_Vehicle_to_Emergency_Vehicle_Warning_System.pdf PDF
Call_0005-_SOO_F-Rescue_Hoist_Protective_Glove.pdf PDF
Call_0005-_SOO_H-_Integration_of_Public_Data_Feeds.pdf PDF
Call_0005-_SOO_J-_Energy_Harvesting_Fabric.pdf PDF
Call_0005-_SOO_A-_Wildland_Fire_Respiratory_Protection.pdf PDF
Call_0005-_SOO_D-_Multi-Mission_Disrupter.pdf PDF
Call_0005-_SOO_E-_Multimeter_Wire_Attack_Kit.pdf PDF
BAA_13-012_Call_0005.pdf PDF
Call_0005-_SOO_I-_Visualization_System_for_3D_Location_and_Tracking.pdf PDF
Call_0005-_SOO_G-First_Responder_Routing_Logic_Guide.pdf PDF
DRAFT-SOO_7-_First_Responder_Routing_Logic_Guide.pdf PDF
DRAFT-SOO_4-_Multi-Mission_Disrupter.pdf PDF
DRAFT-_SOO_9-_3D_Indoor_Dynamic_Mapping_and_Visualization.pdf PDF
DRAFT-_SOO_8-_Integration_of_Public_Data_Feeds.pdf PDF
DRAFT-_SOO_3-_Emergency_Vehicle_to_Emergency_Vehicle_Warning_System.pdf PDF
DRAFT-_FRG_BAA_Call_0005_Solicitation_TTAs.pdf PDF
DRAFT-_SOO_6-_Rescue_Hoist_Protective_Glove.pdf PDF
DRAFT-_SOO_5-_Multimeter_Wire_Attack_Kit.pdf PDF
DRAFT-_SOO_10-_Energy_Harvesting_Fabric.pdf PDF
DRAFT-_SOO_2-_Emergency_Response_Vehicle_Warning_for_Civilians.pdf PDF
DRAFT-_SOO_1-Wildland_Fire_Respiratory_Protection.pdf PDF
FRG_BAA_13-012_Version_8.pdf PDF
Amendment_00010_BAA-13-012.pdf PDF
Questions_and_Answers_for_BAA_13-012_Call_0004.pdf PDF
Call_0004-_SOO_E-_Drone-Based_Wireless_360_Camera.pdf PDF
Call_0004-_SOO_B-_Rapid_VBIED_Assessment_and_Inspection.pdf PDF
Call_0004-_SOO_H-_Law_Enforcement_Capture_and_Restraining_System.pdf PDF
Call_0004-_SOO_D-_Activation_of_Body-Worn_Cameras_without_Responder_Manipulation.pdf PDF
Call_0004-_SOO_A-_Respiration_Protection_for_Firefighters_during_Overhaul.pdf PDF
Call_0004-_SOO_F-_Enhanced_Roadway_Safety_for_First_Responders.pdf PDF
Call_0004-_SOO_G-_Humanized_2-Arm_Large_3D_Robot.pdf PDF
BAA_13-012_Call_0004.pdf PDF
FRG_BAA_13-012_Version_7.pdf PDF
Amendment_00009_BAA-13-012.pdf PDF
Questions_and_Answers_for_BAA_13-012_Call_0003.pdf PDF
Show 40 more

Latest 50 of 87 listed here. See the rest on GovTribe.

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

Universal Operator Control Unit Platform Statement of Objectives BAA 13-012/Call 0004/ SOO C

October 13, 2015 Science and Technology Directorate Department of Homeland Security

DISTRIBUTION NOTICE: Further dissemination only as directed by DHS Office of Policy DESTRUCTION NOTICE: Destroy by any method that will prevent disclosure of contents or reconstruction of the document.

October 5, 2015 i

Table of Contents

1.0 Purpose

2.0 Scope (Capability Gap)

3.0 Period and Place of Performance

4.0 Background

5.0 Functional Requirements

5.1 Overall Concept of Operations

5.2 Threat

5.3 Operating Constraints (Current Technology Shortfalls)

5.4 Specific Required Capabilities

5.4.1 Operation

5.4.2 Functionality

5.4.3 System Characteristics

5.5 System Performance

5.5.1 Mission Scenarios

5.5.2 Compatibility and Interoperability

5.5.3 Human Interface Requirements

5.5.4 Logistics and Readiness

5.5.5 Durability

5.6 System Support

5.6.1 Maintenance

5.6.2 Capabilities and Limitations

5.6.3 Supply

5.6.4 Support Equipment

5.7 Training

5.8 Storage

5.9 System Affordability

5.10 Certification Requirements for Product Conformity

1.0 Purpose

The proposed solution is to develop a standardized Operator Control Unit (OCU) platform to reduce training requirements and associated costs. The solution will enable end users (i.e., bomb technicians) to operate multiple robotic platforms using a single, standardized control unit rather than allocating valuable time to learning multiple control units for different robotic platforms.

Today, manufacturers create platforms that require system-specific training, which due to lack of interoperability, lead to increased operating and maintenance (O&M) costs. An interoperable OCU would lead to more effective mutual aid.

2.0 Scope (Capability Gap)

The universal OCU platform will create a common user interface for robot operators that will lead to greater interoperability, lower training requirements, and thus will produce cost savings. The platform must be able to operate in all weather and lighting conditions.

3.0 Period and Place of Performance

A complete field functional prototype that demonstrates at least 90% of all requisite capabilities must be operational within 12-18 months of the award. All developmental activities will be performed at the contractor-designated site(s). DHS may require the contractor to perform critical design reviews and/or product presentations at DHS-specified locations.

4.0 Background

Current robotic platforms offered to the first responder community come with a variety of different control units which are rarely cross compatible with other robotic platforms, even though they may be produced by the same manufacturer. Due to the multitude of different robots in use, technicians are required to dedicate 8 hours a month to training in order to maintain their understanding and familiarity of controlling several robotic platforms. The requested solution calls for the creation of a universal control unit, capable of operating any robotic platform and effectively reduces the training time of technicians while increasing their understanding of performing more complex maneuvers and skills.

5.0 Functional Requirements

5.1 Overall Concept of Operations

This proposed solution would enable operators to have immediate control of robotic platforms deployed in the field without the need for additional training or preparation time. Additionally, because of the simplified operation, it would eliminate the need to transport multiple controllers, which take up precious space in response vehicles. A unified controller also reduces costs of new equipment by eliminating the need for purchasing separate controllers for each robotic platform, and reduces costs to repair by producing a more cost effective standardized system.

5.2 Threat

The proposed solution will address and reduce the number of man-made errors caused from operational fatigue. By producing a simplified, standardized controller which works on a wide range of robotic platforms, operators will retain a familiar competence level with the technology while also improving upon the speed in which they perform more specialized functions (i.e.

gripping objects).

5.3 Operating Constraints (Current Technology Shortfalls)

Today, robotic platform manufacturers build proprietary control units with every platform they build. These control units are typically not interchangeable between different platform models produced by the same manufacturer and are very expensive to procure. A standardized OCU would allow end users to continue utilizing their current robotic platforms without requiring them to procure a more expensive alternative.

The standard squad training for robot operators is approximately 16 hours per month and is often split amongst various pieces of equipment. Due to this constraint, technicians are at risk of losing familiarity when having to train on multiple robotic controllers. Furthermore, technicians develop muscle memory when operating robot controllers. This muscle memory can cause unwanted movements when using a less familiar controller, thus causing damage to the platform and potentially triggering an IED.

5.4 Specific Required Capabilities

5.4.1 Operation

The proposed solution will operate in a similar manner that bomb technicians currently conduct their respective duties.

5.4.2 Functionality

Key required functional characteristics for the proposed OCU platform solution include:

• Operational in all weather conditions;

• Must be portable, and easily operable from the bomb technician’s lap or on a tabletop;

• Utilize a feedback loop which alerts users when the platform wasn’t working properly, and also provide a low-power alert;

• Provides an alert when arming tools (i.e., firing circuit, disrupter, etc.);

• A removable key, required for the operator to arm the firing circuit prior to engaging the circuit;

• An adapter mechanism that joins the universal OCU to the transmitter/receiver of common robotics platforms in order to use existing radio systems (i.e. Remotec, iRobot, Talon, etc.)

for communications;

• At minimum 12”, high-definition color display, between 720p -1080p, which is easily viewed in all lighting conditions;

• Full operation of all capabilities that the original OCU allows;

• The same picture-in-picture imagery as the original dedicated OCU;

• Have the ability to wirelessly send the display output to an external device;

• Automatic calibration when necessary with minimal operator input; and

• Use of open source and industry standard software and control systems for future upgradability purposes.

5.4.3 System Characteristics

The functional and operational physical characteristic requirements for the proposed solution are:

• Must have an ergonomic interface similar to the HDT Global Hardened Operator Control Unit (HOCU);

• Able to withstand the shock associated with a 5’ drop;

• Must be operable in all weather conditions, including resistance to rain and all International

Protection Rating (IP) Code 65 enclosure requirements;

• Shall be Advanced Explosive Ordnance Disposal Robotic System (AEODRS) compliant;

• Provide common communication interface for sensors and other input devices for multi-platform use; and

• Must come with a manufacturer’s general warranty to include accessibility to spare parts.

5.5 System Performance

5.5.1 Mission Scenarios

Bomb technicians are unable to administrator mutual aid or assist in operations across disparate bomb squads due to the difference in OCU’s. If an operator is unfamiliar with a specific robot OCU, he or she is unable to take over the task from the previous operator. Additionally, a fatigued operator is more likely to commit errors during an active incident, potentially resulting in serious consequences.

5.5.2 Compatibility and Interoperability

The device must have an adapter mechanism(s) which enables the Universal OCU to connect to the proprietary radio control systems used for operating various other robotics platforms while maintaining full operational capability of the robotic platforms.

5.5.3 Human Interface Requirements

The OCU must have a high-definition color display and have the ability to send the display output to an external device. Use of a control unit similar to the HDT Global HOCU would reduce the learning curve and memory requirements when operating the gripper mechanism versus the traditional multi-switch method currently in use.

5.5.4 Logistics and Readiness

This proposed platform shall operate multiple manufacturers’ robotic platforms for bomb technicians without requiring additional training.

5.5.5 Durability

This device must be:

• Meet all IP Code 65 enclosure characteristics to ensure ruggedness, so that bomb technicians can use in all weather and other operational conditions; and

• It shall be AEODRS compliant.

5.6 System Support

5.6.1 Maintenance

All maintenance for the item(s) and related equipment shall be defined by the contractor, including: the required maintenance schedule, identification of the specific components of the ensemble that requires the maintenance, the type of maintenance required, and whether the maintenance can be performed in the field or must be returned to the manufacturer for maintenance. The equipment must come with a manufacturer’s general warranty, to include accessibility to spare parts. Additionally, the device shall automatically calibrate itself when necessary with minimal operator input. All systems must use open source and industry standard software and control systems for future upgradability purposes.

5.6.2 Capabilities and Limitations

The proposed solution must be capable of integrating with current radio systems, which are used to link OCU’s to robotic platforms. Since each manufacturer uses dedicated R/C systems, an adapter will be needed to go from the Universal OCU to the transmitter/receiver system. Adapters for the most common platforms will be included in this project. Additionally, the proposed solution must allow for full operational capability of the robotic platform as when using the original OCU.

5.6.3 Supply

Supply shall be determined by the individual departments based upon cost, quantity needed, and effectiveness of the solution.

5.6.4 Support Equipment

The Universal OCU will be able to control existing robotic platforms without loss of performance.

This includes the various arm configurations, various number of simultaneous cameras in use, bi-directional audio (if the platform has this capability), assorted numbers of firing/tool circuits (from zero to ten) based on the different platforms’ capabilities etc. Additionally, depending upon the final product there may be a need for cabling or plugs to connect the OCU to the current robotic platform operating systems.

5.7 Training

Training information shall be provided on any specialized equipment, and shall include instructions on how to properly store, clean, deploy, and maintain the basic ensemble. Any specialty requirements for personnel conducting maintenance, storage, extraction, or delivery will be identified including certification requirements. Training material shall be available initially in hard copy, and subsequently in soft copy format.

5.8 Storage

The manufacturer shall identify all storage requirements for the proposed solution.

5.9 System Affordability

The DHS S&T First Responder Resource Group, a national subject matter expert body that has representation from all major responder disciplines, recommend that the unit cost for this technology be no greater than existing robotic control technology.

5.10 Certification Requirements for Product Conformity

• Meet US Federal Communications Commission (FCC) wireless standards;

• Meet all IP Code 65 enclosure requirements; and

• AEODRS compliant.

1.0 Purpose
2.0 Scope (Capability Gap)
3.0 Period and Place of Performance
4.0 Background
5.0 Functional Requirements
5.1 Overall Concept of Operations
5.2 Threat
5.3 Operating Constraints (Current Technology Shortfalls)
5.4 Specific Required Capabilities
5.4.1 Operation
5.4.2 Functionality
5.4.3 System Characteristics
5.5 System Performance
5.5.1 Mission Scenarios
5.5.2 Compatibility and Interoperability
5.5.3 Human Interface Requirements
5.5.4 Logistics and Readiness
5.5.5 Durability
5.6 System Support
5.6.1 Maintenance
5.6.2 Capabilities and Limitations
5.6.3 Supply
5.6.4 Support Equipment
5.7 Training
5.8 Storage
5.9 System Affordability
5.10 Certification Requirements for Product Conformity

File details come from the government source that posted it. Updated .