15 September 2010 Balanced Capabilities & Proven Past Performance INDUS Technology, Inc.

215 September 2010 INDUS At-A-Glance Company Profile Began Government Services: 1998 CY09 Revenue: $31M  Service Disabled Veteran Owned Small Business (SDVOSB)  Seaport-e, GSA various, VETS  HQ in San Diego, CA and Field Offices: Silverdale, WA (2006) Oahu, HI (2009) Phoenix, AZ (2003) Norfolk, & Crystal City, VA (2004) Washington D.C. Metro (2004) Charleston, SC (2004) Colorado Springs, CO (2005) Port Hueneme, CA (2008) Newport, RI (2009)  ISO 9001:2008 Registered and Certified (*)Numbers above the bars represents the amount of employees for that year. 307 employees as of 1 April 2010.

315 September 2010 Our Robotics Mentor-Protégé efforts  Rhetorical question – what is Interoperability for unmanned systems? Many answers and solutions – JAUS, etc. This is a good, valuable, and even a required capability But, this type of interoperability only provides the infrastructure for communication much like the English language or phones provide for us  However, effective communication requires much more than simply the ability to communicate

415 September 2010 Our Robotics Mentor-Protégé efforts  In order to achieve the battlefield of the future vision, we need Interfunctioning unmanned systems Interfunctioning = multiple units (UVs, AUVs, manned units, etc.) functioning together to complete a mission or set of task(s) A “swarm” is a very specific subset of this problem space where multiple similar or like UVs function together effectively as 1 unit INDUS and Lockheed Martin (our Mentor) are working towards a general solution to allow multiple dissimilar units function together

515 September 2010 Our Robotics Mentor-Protégé efforts  INDUS and Lockheed Martin (our Mentor) are working together on a different perspective on the problem View UVs not as discrete vehicles to be applied to a single mission/task but view them in terms of the services they can provide  Example: UAV may carry both sensors and weapons – may provide both surveillance and offensive services. You can gain the most effectiveness by being able to multiply task it even in flight to accomplish multiple missions/tasks at the same time Requires a paradigm shift in asset tasking (CONOPS change) and a mechanism for intelligent multi-tasking

615 September 2010 Notional Approach Service Consumers C2 systems/personnel “Complete a task” Directory (Yellow Pages) Services Providers Status of task Completed task Wrappers Hybrid reasoning module based on multiple Artificial Intelligence technologies Status/completion monitoring No need to do all at once – add in 1 at a time as completed Reasoning Component

715 September 2010 Dynamic Task allocation to UVs Each Unit (manned and unmanned) defined as Service Provider Defined Parameters – operating parameters, payload capability, etc. Defined constraints – range, sensor limitations, etc. Can go in and out of availability Regional Directory Provider Regions can be nested up to theater and global levels “Regions” can be Service Providers to higher-level regions C2 and planning systems/personnel at regional headquarters are Service Consumers Leverage GIG as communications network infrastructure Service Providers can also be Service Consumers Human units on the field can task UVs to provide battlefield awareness