What’s your Robotic OCU IQ?

0

Share | Rate this Article: (4.6 Stars | 5 Votes)   Thanks for your rating!

The days of treating the Operating Control Unit (OCU) as an afterthought to the development of unmanned systems are over. The success of any given mission may rely heavily of the interaction between the operator and the robot, so before you develop any OCU, here are a few questions you should ask.

1. What’s the OS? This may seem a bit obvious, but developing Window’s software for a Linux environment has derailed more than one project.
2. Is it JAUS compliant and truly interoperable? “Does it work on my unmanned system?” used to be the most important question that was asked about OCUs. Now, the DoD has made it clear that the most important question is, “Does it work on my robot and other unmanned systems as well?”
3. Is the OCU mobile, mounted or dismounted? Whether your OCU is handheld, man-wearable, vehicle-mounted, or located on a desk has huge consequences for the specs on power consumption, optics, displays, graphics, sunlight readability and night vision.
4. Is it sustainable? That computer you chose may be the cheapest and may meet the requirements, but are you going to be able to upgrade it in two years? Five? What about repair? Are there enough available trained technicians who have the proper security clearance? Where are the supply depots and repair centers located? The failure to think about these factors has created literally mountains of handheld mobile devices waiting for a repairman who will never come.
5. Did I forget the “H” in HMI (Human Machine Interaction)? Cool technology is not enough. It’s got to operate well in theater in the hands of the warfighter. Whenever possible, get feedback from end-users about how things work in the real world.
6. Does it comply with the RSJPO, NAVSEA, and SPAWAR roadmaps? Developing systems for future needs is one of the biggest problems facing Defense contractors today.  Are you anticipating the requirements of tomorrow’s soldiers? Is your system aligned with what the DoD wants?
7. Am I reinventing the wheel? If you don’t know the answer to Question 6 (and especially if you didn’t know enough to ask), maybe you shouldn’t develop the OCU yourself. Your robot may be great, but it may be a mistake to try to do everything. Find yourself the right set of partners who have the proven rugged computerized platform, the modularity and software for common control, and the right radio configuration.
    

Any other questions? Visit www.commoncontrolnow.com or e-mail ocupros@amrel.com.
 

Contributor: William Finn

Share |

William Finn is Senior Copywriter & Editor for American Reliance (AMREL). He writes on a variety of defense issues.

You Should Check Out:

US Demand for UAVs Rising Due to 'Unprecedented Capability'