1. Kevin Gomes, SENSORS Overview and Architecture OOI Cyberinfrastructure: Sensing and Acquisition Workshop San Diego August 5-7, 2008

2. OOI-CYBERINFRASTRUCTURE SENSORS Overview and Architecture SENSORS Project Overview SIAM Model, Architecture and Interfaces SENSORS and OMF Proxy Architecture and Model

3. OOI-CYBERINFRASTRUCTURE SENSORS Project and Workshop Report Project followed ORION workshop in San Juan –Workshop to define middleware requirements for observatory infrastructure –Test Plug and Work (SIAM) on MARS –Follow on Workshop (to be done) Report on workshop (requirements) –Resource Management –Monitoring Requirements –Instrument Management –Data and Metadata

4. OOI-CYBERINFRASTRUCTURE SIAM Model “mmddyy=...” “time=...” Data logger client Time synchronizer client “acquire” getData() setClock() HydroRad instrument service Standard interface SBE-16 instrument service Standard interface SBE-16 “ts”

5. OOI-CYBERINFRASTRUCTURE SIAM Concepts Instrument PUCK Power Port Instrument Port Port Node...... Node Manager Port Manager Device Service Instrument PUCK Power Port Instrument Port Port Device Service = CI Platform Controller = CI Instrument Supervisor = CI Instrument Agent Data Sent to SSDS: -CI Observatory Data Ingest -CI Repositories Metadata Event Manager

6. OOI-CYBERINFRASTRUCTURE SIAM Model, Architecture, and Interfaces

7. OOI-CYBERINFRASTRUCTURE SIAM Node and Port Manager

8. OOI-CYBERINFRASTRUCTURE SIAM Model, Architecture, and Interfaces

9. OOI-CYBERINFRASTRUCTURE SIAM Ports

10. OOI-CYBERINFRASTRUCTURE SIAM Model, Architecture, and Interfaces

11. OOI-CYBERINFRASTRUCTURE SIAM Device and Instrument

12. OOI-CYBERINFRASTRUCTURE SIAM Model, Architecture, and Interfaces

13. OOI-CYBERINFRASTRUCTURE SIAM Device Services

14. OOI-CYBERINFRASTRUCTURE SIAM Node and Port Manager (Details)

15. OOI-CYBERINFRASTRUCTURE SIAM Ports (Details)

16. OOI-CYBERINFRASTRUCTURE SIAM Ports (Details)

17. OOI-CYBERINFRASTRUCTURE SIAM Device and Instrument (Details)

18. OOI-CYBERINFRASTRUCTURE SIAM Device and Instrument (Details)

19. OOI-CYBERINFRASTRUCTURE SIAM Device Services (Details)

20. OOI-CYBERINFRASTRUCTURE SIAM Device Services (Details)

21. OOI-CYBERINFRASTRUCTURE SIAM Device Services (Details)

22. OOI-CYBERINFRASTRUCTURE SIAM Device Services (Details)

23. OOI-CYBERINFRASTRUCTURE SENSORS Work to apply to ALOHA and MARS PUCK RS-232 to Ethernet RS-232 SSDS Interface Shore Side Data System SSDS Interface Instrument services Digi RealPort Cable Shore Node Shore-side Computer (at MBARI) SIIM CTD Shore Network (Internet) Seahurst Cable

24. OOI-CYBERINFRASTRUCTURE Extending to OMF CTD RS-232 to Ethernet RS-232 SSDS Interface SSDS Interface Instrument services Digi RealPort Cable Shore Node Digi Shore Network (Internet) ALOHA Cable Shore Side Data System MBARI Enterprise Service Bus NCSA Enterprise Service Bus Proxy & Strategy

25. OOI-CYBERINFRASTRUCTURE OMF Proxy Architecture and Model Instrument Observatory Middleware (MOM) Proxy Strategy Middleware (SIAM/ROADNet/etc.) Device Service OGC/1451/ProtocolX Queue Instrument Proxy Mediation Classes (Common Model) Translation between common Instrument Proxy interface to language d’jour Common interface specification for instrument in observatory Translation between legacy middleware and common model = CI Exchange = CI Instrument Agent = State Model

26. OOI-CYBERINFRASTRUCTURE OMF Proxy Architecture and Model Instrument Mule ESB/Active MQ OGCStrategy SIAM Node Device Service OGC Queue Instrument Proxy Mediation Classes (Common Model) getNewObservation() aquireData() “ts”

27. OOI-CYBERINFRASTRUCTURE OMF Proxy Architecture and Model Instrument Mule ESB/Active MQ OGCStrategy SIAM Node Device Service OGC Queue Instrument Proxy Mediation Classes (Common Model) 32.45 121.45 -99.99 32.45 121.45 -99.99 convertAndSend() addSample() publishData() addSample() publishData() 32.45, 121.45, -99.99 Metadata is tagged to data and data is parsed

28. OOI-CYBERINFRASTRUCTURE SENSORS and OMF Proxy Architecture and Model

29. OOI-CYBERINFRASTRUCTURE

31. SENSORS and OMF Proxy Architecture and Model

32. OOI-CYBERINFRASTRUCTURE

33. SENSORS and OMF Proxy Architecture and Model

34. OOI-CYBERINFRASTRUCTURE

35. Sample SensorML from SIAM

36. OOI-CYBERINFRASTRUCTURE Sample OM from SIAM

37. OOI-CYBERINFRASTRUCTURE Integration of IEEE 1451 with OGC-SWE and Ocean Instruments Signal Conditioning and Conversion Transducer 1451.2 PHY TEDS IEEE-1451.0- based STWS on NCAP Smart Transducer Web Service (STWS) Transducer 1451.0 TEDS STWS Consumer STWS SOAP/HTTP IEEE 1451.0 HTTP IEEE 1451.0 HTTP Client IEEE 1451.0 HTTP Server RS 232 C PUCK Adaptor TIM (ocean instrument) NCAP Kang Lee/NIST: July 29, 2008 Tom O’Reilly: Aug 1, 2008 OGC –SWE SOS SOAP/HTTP SOS Service STWS Client Application SOS Client SOS Consumer Extracts TEDS and servlet-driver code from instrument via PUCK protocol Servlet-driver maps between IEEE 1451.0 and instrument-specific serial protocol MBARI-developed component PUCK-enabled instrument stores TEDS and servlet-driver code

38. OOI-CYBERINFRASTRUCTURE Questions and Thanks

39. OOI-CYBERINFRASTRUCTURE SENSORS Report Requirements Observatory Levels (0-3) –Resource Management Static resource allocations (L0) “Soft start” for high powered instruments (L0) Manual notification to users of resource changes (L0) Automated storage buffering of data (L1) Scheduled, preplanned resource allocation (L2) Programmed scheduling of instruments, sampling (L2) Automated resource allocation for storage, bandwidth and power (L3) Programmed mission planning (L3) Automated resource leveling (L3) Automated recovery from faults and conflicts (L3)

40. OOI-CYBERINFRASTRUCTURE SENSORS Report Requirements (cont.) Monitoring requirements –No requirement, based on hardware capability (L0) –Ground fault detection (L0) –Basic display and logging of resource utilization (L1) –Uniform application interface to display instrument status (L2) –Display and logging of real-time events (L2) –Basic diagnostic tools (L2) –Automated notification of resource conflicts (L3) –Automated notification of reconfigurations (L3) –Advanced diagnostic tools (L3)

41. OOI-CYBERINFRASTRUCTURE SENSORS Report Requirements (cont.) Instrument Management –Individual PI (L0) –NTP like time distribution (L1) –Unique OOI instrument ID (L1) –Manual lifecycle management (L1) –Pre-deployment qualification and validation of instruments (L1) –Uniform application to control and schedule instruments (L2) –Instruments can create and respond to events (L2) –IEEE 1588-like time distribution (L3) –Plug and work instrument (L3) –Automated instrument service discovery (L3) –Automated event detection and response (L3)

42. OOI-CYBERINFRASTRUCTURE SENSORS Report Requirements (cont.) Data and Metadata –Up to individual PI (L0) –Automated sequencing of data (L1) –Uniform metadata form (L1) –Application interface to get static and dynamic metadata (L1) –Uniform application interface to display data (L2) –Base level of automated data quality control (L2) –Automated metadata discovery (L3) –Automated notification of metadata changes (L3)