CENTRE FOR MARITIME RESEARCH AND EXPERIMENTATION

Transcription

1 CENTRE FOR MARITIME RESEARCH AND EXPERIMENTATION Gabriel Grenon, Dr.Alain Maguer presented by Per Arne Sletner Head, Autonomous Unmanned Vehicles Section Slide 1

2 Mission CMRE organises and conducts scientific research and technology development, and delivers innovative and field-tested S&T solutions to address the defence and security needs of the Alliance in the maritime domain. Slide 2

3 Highly-skilled, international, interdisciplinary professionals Visiting Scientists Collaborative Research Program Over 50 years preparing instrumentation and performing controlled measurements at sea Slide 3

4 Slide 4

5 Challenges - Commercial and Science Slide 5

6 Challenges - Defense environment Slide 6

7 Interoperability From - Stovepipes To - Collaborative / interchangeable pool of service providers Affordability - Procurement - Operations & maintenance - TLMP Open Architecture - Modularity - Configurability - Scalability AUV Challenges A Global Approach Safety - L&R capability - Remote operations Persistence - Endurance (energy) - System robustness (HW & SW) Decision-Making - Onboard intelligence - Limited & intermittent communications Slide 7

8 AUVs with their specific capabilities (size, range, speed, functionalities, payloads) Some capability enhancements delegated to supporting systems Universal CS System of Systems - Coordinated multi-domain efforts - Minimize negative impact on individual system capabilities - Maximize benefits of supporting systems - Provide means for future enhancements Slide 8

9 Subsea Service Node Slide 9

10 Surface Service Node Slide 10

11 Interoperability INTER- OPERABILITY OPEN ARCHITECTURE PERSISTENCE DECISION MAKING SAFETY CO$T Slide 11

12 INTER- OPERABILITY OPEN ARCHITECTURE PERSISTENCE - Legacy Vehicles: Frontseat/Backseat middleware provides a means to interface all legacy onboard control systems with a common high-level and user interface - New Vehicles: Born interoperable DECISION MAKING - Use and further development of interface and communications standards (STANAG 4586, NATO STO IST) - Use de-facto standard software suites (MOOS, ROS) Common language with all operators/c 2 (MDCS) Means to collaborate as a Federation Test/Validate through simulation, SIL, HIL Code re-use SAFETY CO$T - Extend to UW communications (JANUS) - Extend to hardware interoperability? Slide 12

13 Open Architecture INTER- OPERABILITY OPEN ARCHITECTURE PERSISTENCE DECISION MAKING SAFETY CO$T Slide 13

14 Persistence INTER- OPERABILITY Ep Pf() n OPEN ARCHITECTURE PERSISTENCE DECISION MAKING SAFETY CO$T Slide 14

15 INTER- OPERABILITY OPEN ARCHITECTURE PERSISTENCE DECISION MAKING SAFETY CO$T Slide 15

16 INTER- OPERABILITY OPEN ARCHITECTURE PERSISTENCE DECISION MAKING SAFETY CO$T Slide 16

17 1- Keep personnel out of harm s way 2- Safe (launch and) recovery of deployed assets remote-piloted robotic operations (1) minimize personnel involvement in L&R (1) minimize impact of sea conditions (1-2) DS = long term parking Postpone recovery to next safe weather window INTER- OPERABILITY OPEN ARCHITECTURE PERSISTENCE DECISION MAKING SAFETY CO$T Slide 17

18 Tom Swean, NATO SCI ET-012 Affordable Robotics Status of Fielded UxS Systems United States Costs driven by unique requirements Fielded unmanned systems are almost without exception developed for Servicespecific needs driven by rapid fielding timelines in support of immediate operational requirements (specific unit needs rather than Big-Service needs). Industry has become comfortable with producing a completely new unmanned platform/system when an improvement or new capability is needed. Very little is backward compatible. Opportunities for realizing cost savings Limited to NO interoperability with other unmanned (or manned) systems in all domains (ground, air, maritime) Payloads, sensors, software & computing technology are anticipated to evolve much faster than base platforms requiring modularity within a system. Open architectures (OA), nonproprietary interfaces, government owned data rights, and standard interoperability profiles (IOP) are required for broader, more affordable, net-centric military applications. INTER- OPERABILITY OPEN ARCHITECTURE PERSISTENCE DECISION MAKING SAFETY SoS as a framework to implement better cost practices CO$T Slide 18

19 Interoperability From - Stovepipes To - Collaborative / interchangeable pool of service providers Open Architecture - Modularity - Configurability - Scalability Persistence - Endurance (energy) - System robustness (HW & SW) Affordability - Procurement - Operations & maintenance - TLMP Safety - L&R capability - Remote operations Decision-Making - Onboard intelligence - Limited & intermittent communications Slide 19

20 Slide 20

21 Slide 21