240 likes | 421 Views
Robotic Systems Joint Project Office Programs and Initiatives. LtCol David Thompson Project Manager Robotic Systems Joint Project Office 2 September 2010 Distribution Statement A: Approved for public release; distribution is unlimited. MISSION
E N D
Robotic Systems Joint Project Office Programs and Initiatives LtCol David ThompsonProject ManagerRobotic Systems Joint Project Office • 2 September 2010 • Distribution Statement A: Approved for public release; distribution is unlimited.
MISSION Lead the development, systems engineering, integration, acquisition, testing, fielding, sustainment and improvement of unmanned systems for the Joint Warfighter to ensure safe, effective and supportable capabilities are provided while meeting cost, schedule and performance. VISION Continuous improvement of unmanned system capabilities to meet current and future Joint Warfighter objectives.
RS JPO Portfolio Maneuver Maneuver Support Sustainment • IED Defeat Systems • Disarm / Disrupt • Reconnaissance • Investigation • Explosive Sniffer • Common Robotic Kit • EOD • Convoy • Log/Resupply • Area/Route Clearance • Mine Neutralization • Counter IED • CBRNE
Evolution of Ground Robotics in Combat Sustainment, Modernization, Interoperability and Modularity
Current Operations • Robotic systems have functioned properly and reliably during OIF/OEF • RS JPO has fielded over 7000 ground robotic systems since 2004 What the Soldier wants: • Extended range and robust comms • Smaller, more compact devices • Common controller • Longer battery life • Increased endurance, dexterity & agility • More capable payloads • Cameras, comms, IED detection, etc • More systems Although Soldier’s are generally satisfied with current UGSs, a common concern is the weight, size, frequency allocation, and power consumption
Robotic Modernization z RSTA Capability Equipment LOGISTICS Endurance Power/Energy 55 lbs 35 LBS Armed CBRNE Detection Arm Strength Maneuver 90 lbs EOD Route Clearance/Engineering Dexterity IED 2004 CAPABILITY Common Controller Tele-op Dedicated OCU Improved Communications for:standoff range, crew compatibility Operational Environment 2010 CAPABILITY SUPERVISED AUTONOMY INTEROPERABILITY
Short Term Strategy • Continued leveraging of Commercial Off-the-Shelf (COTS) • Add-on packages to expand capability of current robots • Stepping stone to modularity and autonomy • Maintenance strategy to maximize service life of robots • Not a cost-effective long term approach
Long Term Strategy • Field a Family of Robotic Systems • Series of platforms providing common interface, controls, and architecture • Modular payloads to provide a wide range of capabilities • Move from an in-house repair and maintenance capability to an “Army standard” maintenance structure
Family of Robotic SystemsPayload Integration and Interoperability Common payload interface across platforms by mission or class Family of unmanned ground systems Mission equipment payloads .. .. .. .. .. .. Payload A Payload B Payload C Payload D Payload E Payload Interface Standard Architecture
Modularity Common Within Platforms Common Across Platforms Common Integrating Software Mission Specific Payload Common Controller Power Supply Communications Actuator Navigational Sensors Operating Software Mobility Platform Artificial Intelligence
Emphasis on Interoperability Today:Teleoperated, dedicated control unit, COTS systems • Soon: • Joint Shared Integrated Picture • Increased Force Survivability • Increased Operational Lethality • Sensors, Shooters, Command, Control & Communications • Reconnaissance / Surveillance The Future:Interoperable, unmanned, networkedsystems working hand in hand with Soldiers
Emerging Requirements SUPPORTING IMMEDIATE WARFIGHTER NEEDS WHILE ESTABLISHING PATH FORWARD FOR FUTURE REQUIREMENTS
TRADOC Unmanned Systems ICD • ICD drafted to support all unmanned systems capabilities through 2034 • Air, Ground, and Maritime • Army Requirement with Joint Interest • Overarching capabilities to require unmanned systems: • Command & Control • Movement & Maneuver • Intelligence • Fires • Sustainment • Protection • Approved 23 August 2010
RS JPO UGS Roadmap • RS JPO Roadmap was developed to help define the desired direction and investments in UGSs based on the current and projected states of technology • July 2010 Addendum available
Interoperability Objectives • Define interoperability standards for integration across UGVs (leveraging other standards work) • Open Architecture & Interfaces • Common Control Standards • Communications (“Common” Data Link) • Payload Integration (Modularity) • (Framework consists of Four Interoperability Profiles (IOP)) • Establish Conformance and Validation Criteria to test suitability and compliance (Virtual SIL & Robotic SIL) • FY11 Version 0 (Core Capabilities) and FY12 Version 1 (Unique Capabilities) • Initial effort culminated with initial standards and concepts Tech Base and User Communities of Interest are Embedded
-SAE AS-4 implementation of IOP -Priority/Sequences -Private Messages -Transport -Interfaces -AS-4 Committee Industry/Gov’t Participation • Industry Forum – 15 June 2010 • Industry -33 Companies (52) • Gov’t – 13 Gov’t Agencies (36) • Total Participants 88 • Working IPT Structure • 5 WIPTs • Led by RSJPO and TARDEC • Aligned with IOP Framework • Industry and Gov’t Participation • -15+ Companies/11 Gov’t • Rules and process • Collaborative Meetings • IPT Meetings (Higher Level Body) • Cross Leveling of Information • Baseline and Change Control • WIPT Presentations and Concurrence • Open Dialogue -Architecture -System Functions -Mission threads -Implementation -Performance -Latency -Network -Validation - - Overarching WIPT -Logical Arch. -Interface Reqt’s -Data link -Software -C2 -WMI -Performance -Training * Senior Level * Governance * Baseline * Change Control Board SAE AS-4 WIPT Control WIPT -Waveforms -Frequencies -COMSEC & Encryption -Radio Config. -Data Rates -Latency RS JPO Interoperability IPT -Payload Arch. -Sensors -Video -Message Protocol -Emitters, Audio & Acoustic -Actuators -Performance Comms WIPT Payload WIPT Voluntary Participation by Industry
Why is interoperability important? • To provide sustainable and repeatable processes and capabilities to support the current and future Warfighter • Leverage technologies and capabilities across all UGS partner organizations • Increase Efficiency/ MaximizeLimited Resources • Reduce Logistics Footprint
Investing in Dual-Use Technologies • Obstacle detection & avoidance • Military: pedestrians, terrain and man-made obstacles • Civilian: automobile safety technologies – active cruise control • Autonomous navigation • Military: resupply, dynamic path planning • Civilian: automobile safety technologies – active cruise control • Increased communication range • Military: increased standoff • Civilian: command post (DHS/1st Responders), wireless networks • Multi-robot control • Military: one controller/many robots, manning levels • Civilian: warehousing • Interoperability • Military: agile mission response, cost effective • Civilian: standardization, “price point” • Improved battery technologies / fuel cells • Military: longer life, reduced soldier load • Civilian: fuel efficiency
Summary • RS JPO mission and roles are expanding • Robotic procurement becoming proactive vice reactive • More RDT&E and coordination required • JRRF and JRRDs providing Warfighter robotic support • CONUS and OCONUS • Pursuing synchronized UGS Acquisition Strategy and legitimacy • AAE Policy memo on robotic acquisition • USD(AT&L) Memo: Army Modernization Follow-On to Future Combat System • Army approved Unmanned Systems ICD Continuing progress and coordination in robotic acquisition, logistics, and technology is centered at the Detroit Arsenal