Frequently Asked QuestionsHow can you have a standard robot for urban search and rescue? Can I participate in the standards process? Where can I learn more about the urban search and rescue robot standards program? What is the goal of these Responder/Robot Evaluation Exercises and how will they lead toward sales of my robot? Are you grading my robots at the Responder/Robot Evaluation Exercises? Who gets to attend these events? I want to demo my new whizbang gadget but I don't want it to get damaged. Can I bring it and just show it? I have a new whizbang technology that responders should know about, but it's doesn't really have anything to do with robots? Can I bring it? Will this event produce purchase decisions for my robot? What Personal Protective Equipment (PPE) is needed to participate in this event? How can you have a standard robot for urban search and rescue? Can I participate in the standards process? Where can I learn more about the urban search and rescue robot standards program? What is the goal of these Responder/Robot Evaluation Exercises and how will they lead toward sales of my robot? 0. Emergency responders on our advisory panel produced an initial set of performance requirements for robots which could improve/augment their existing capabilities based on their experiences performing urban search and rescue. This was prior to much exposure, if any, to robotic technologies, so the emphasis was on gaps in their current capabilities that could potentially be addressed with robotic technologies. The 100 or so initial requirements can be found at www.isd.mel.nist.gov/US&R_Robot_Standards (Preliminary Report). 1. Responder/Robot Evaluation Exercises are being conducted to introduce emerging robotic technologies to responders within relevant training environments. The scenarios used in these exercises are opportunities to highlight the utility or unique advantages that particular technologies may provide, and how they must be deployed to be useful. 2. Responders will augment their defined set of requirements with additional needed capabilities, adding requirements for particularly helpful robotic technologies, such as 3-D mapping of confined space voids for example, based on their assessment of these emerging technologies within their training environments. Prior to these events, they either didn't know about that particular technology, or never saw it working in their environments. 3. Particularly "ripe" technologies demonstrated to be useful and survivable within responder training environments will get performance thresholds and objectives assigned by the responders as a group after each event, giving technology providers an envelope in which to provide solutions -- since differing levels of cost/performance may appeal to different response organizations or support specific roles/tasks (i.e. initial reconnaissance vs. structural assessment). Less "ripe" technologies that are considered on the path toward fieldable will get more general requirements written to help guide development. Both technologies will benefit from ongoing participation in these responder/robot evaluation exercises to guide development . 4. Performance test methods will be developed for these "ripe" technologies to capture key performance criteria necessary to quantify/compare implementations. These test methods will not identify good/bad performance, rather they will objectively capture actual performance in a known (and practiced) test method to help guide applicability and purchasing decisions, etc. These performance test methods will ultimately be standardized in waves within ASTM International's Homeland Security portfolio. The first wave of standard test methods covering "ripe" technologies is due to be published in 2006. 5. Robots and technologies that use these performance test methods to quantify their capabilities will be considered available for purchase with DHS funds. They will be included in a compendium which captures their performance test results and disseminated to FEMA and other response organizations to help guide trade-off and applicability decisions for purchasing. Note, however, that NIST cannot represent DHS's intent regarding the timing or funding of any grants to purchase robotic equipment. Are you grading my robots at the Responder/Robot Evaluation Exercises? That said, video of successful robots in challenging responder training scenarios is captured at these events so that responders everywhere can start to envision how these assets might work for them. Who gets to attend these events? I want to demo my new whizbang gadget but I don't want it to get damaged. Can I bring it and just show it? I have a new whizbang technology that responders should know about, but it's doesn't really have anything to do with robots? Can I bring it? Will this event produce purchase decisions for my robot? We understand that many robot developers hope for or need an imminent purchase decision to hang on every outing. Unfortunately, we can't say with confidence that this event will necessary lead directly to a purchase. This event is intended to close the loop on your technologies and their intended applications, to identify necessary changes in your approach to be maximally useful to responders, and to provide exposure of your technology to the people who guide purchasing decisions for this community. See questions above for addition discussion regarding the envisioned path to procurement. What Personal Protective Equipment (PPE) is needed to participate in this event? On Site Safety Comes First Safety of all personnel participating in this event is our first concern. The fact that we have robotics personnel on site, generally unaccustomed to working within hazardous scenarios, is particularly problematic. First, all appropriate personal protective equipment (PPE) must be worn at all times while on site (see associated page on PPE) -- which means wear all of it when you are working in/near a scenario. People in street clothes or without helmets, gloves, etc., are limited to paved roads only. Compliance with these personal protective equipment rules are mandatory.
|