1 / 12

Leveraging Maritime Robotics

Leveraging Maritime Robotics. Long Term Problem/Opportunity. Chad Trytten, Founder & CEO 2011-NOV-30. Who Is This Guy?. WWW.SPARKINTEGRATION.COM. Maritime Summit 2011. Slide 1. Distrix - L ike FedEx, sort of. Exchange of information between systems

jonas-richards
Download Presentation

Leveraging Maritime Robotics

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Leveraging Maritime Robotics Long Term Problem/Opportunity Chad Trytten, Founder & CEO 2011-NOV-30

  2. Who Is This Guy? WWW.SPARKINTEGRATION.COM Maritime Summit 2011 Slide 1

  3. Distrix - Like FedEx, sort of Exchange of information between systems • FedEx deals with physical packagesDistrix deals with information packages • FedEx uses available physical transport Distrix uses available comms transport Other similarities • Content is irrelevant – data,voice or video • Logistic process is invisible to the user • Extremely fast and efficient WWW.SPARKINTEGRATION.COM Maritime Summit 2011 Slide 2

  4. Opportunity - So many uses • DoD and DHS have overseen a rapid expansion in the use of ISR over the past decade • The applications and types of data elements continue to grow rapidly as innovation continues apace in both technology and CONOPS • Over 175,000 sq miles of costal waters with potential for exploration, resource extraction, port/shipping operations, environmental management, ISR, security; less than 5,000 miles land borders • Military, First Responder, and Civilian groups are consolidating systems as an investment to reduce errors and personnel costs • Robots are platforms for information needed by the rest of operations WWW.SPARKINTEGRATION.COM Maritime Summit 2011 Slide 3

  5. Problem - So many uses • There are many different types of robots! • Currently, each ISR system (robot) is largely still operating in isolation, limiting operational capability • There is significant effort, cost, and risk of integrating vastly different technologies in ISR and other equipment into usable Situational Awareness (SA) • Ultimately, many stakeholders wants access to the same robotic platforms / sensory information • How to make it easy for other systems to use the information? WWW.SPARKINTEGRATION.COM Maritime Summit 2011 Slide 4

  6. Hurdles to Adoption • It all comes down to how easily *your* system plays with the rest • To be competitive, corporations and government must: • Simplify and speed up the development of sensor systems • Enable seamless interaction between individual components • Ensure a secure and efficient execution environment • Don’t try to do it all, do what you do best • Need a bi-directional, platform-independent communications mechanism that enables rapid integration of inter- and intra- information sharing of warfighters with sensor systems and ISR robots • Must address the technical problem of low-level technological incompatibilities without forcing a single standard or re-engineering WWW.SPARKINTEGRATION.COM Maritime Summit 2011 Slide 5

  7. What Is Distrix? Distrixstands for ‘Distributed Information Exchange’ Open software framework and tools. Enables engineers to integrate complex electronic systems and subsystems. Distrix allows systems/components built by different vendors using different standards for different purposes to work together with minimal re-engineering. WWW.SPARKINTEGRATION.COM Maritime Summit 2011 Slide 6

  8. Distrix Overview • Distrix provided the same mechanism for comms over multiple ‘networks’: • Device-to-Application (hardware) • Application-to-Application (local delivery) • Application-to-Platform (remote delivery) • Platform-to-Platform (network) • Distrix agents (components) can be developed in many languages for a variety of operating systems, hardware, and communication protocols. For example: • Windows • Linux • Android • OS X • OpenRTOS • iOS • Baremetal • TCP/IP • UDP/IP • Mixed TCP/UDP • Serial232, 422, 485, 530 • IPC/Local • Embedded • SPI and GPIO • MIL-STD-1553 • C • C++ • C# • Java • Objective-C • Python WWW.SPARKINTEGRATION.COM Maritime Summit 2011 Slide 7

  9. Distrix Implementation • Runs on legacy commercial or custom hardware • Deployed on a heterogeneous, distributed network that appears flat amidst multiple (a/sync, multi-path) connection types and operating environments • Components can run in different programming languages, using different information formats on differing operating systems and hardware WWW.SPARKINTEGRATION.COM Maritime Summit 2011 Slide 8

  10. Distrix Deployments • Foreign Comparative Test with SPAWAR: Demonstrate how unmanned systems interoperability can be used to implement autonomous security in a seaport • Border UAV Surveillance: Improve quality and security of UAS voice and data links by adding Inmarsat capability to existing UAS • Commercial Security System: Integrate existing sensors (camera, IR, keycard access, etc.) and provide sensor auto discovery and configuration for addition of new sensors • Multiple Data Links: Use centralized system to manage multi-comms paths and add encryption without modification to existing network WWW.SPARKINTEGRATION.COM Maritime Summit 2011 Slide 9

  11. Summary • Leverage existing investments and infrastructure for fast affordable assembly without re-engineering of mixed new and legacy • Use COTS and MOTS products without re-design to match existing systems; the future is time and cost sensitive • Enable cross-functional teams to work collaboratively but maintain autonomy, IP and skill sets • Support an open, modular framework with 3rd party extensions • Focus on operational need, not technical details WWW.SPARKINTEGRATION.COM Maritime Summit 2011 Slide 10

  12. Final Quotes • Wiilliam Lynn, Deputy Secretary Defense: “It takes the Pentagon 81 months to make a new computer system operational after it is first funded.” By contrast, he notes, “the iPhone was developed in 24 months [with COTS]” • Lt. General Robert Lennox’s position that the combination of a COTS computing device and a legacy radio would ultimately save money: “that pairing and the fact that we have those two together would save us hundreds of millions of dollars and will lighten the load, to get it out to soldiers faster and cheaper” • Port of Redwood City DHS Award notice: “The end product will produce a catalog of inventoried data and real time information for security and emergency response. It will create a ‘virtual Port’ and will be made available to response agencies […] in lieu of creating a new, stand alone program that would be limited to just the Port Area.” WWW.SPARKINTEGRATION.COM Maritime Summit 2011 Slide 11

More Related