Kevin Gomes SENSORS Overview and Architecture OOI Cyberinfrastructure

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

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

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

OOI-CYBERINFRASTRUCTURE ge t D at Standard interface Data logger client get. Data() Hydro. Rad instrument “acquire” service Standard interface SIAM Model SBE-16 instrument service Hydro. Rad “time=. . . ” a( Time synchronizer client se t Cl o ck ( ) ) set. Clock() SBE-16 “ts” “mmddyy=. . . ”

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

OOI-CYBERINFRASTRUCTURE SIAM Model, Architecture, and Interfaces

OOI-CYBERINFRASTRUCTURE SIAM Node and Port Manager

OOI-CYBERINFRASTRUCTURE SIAM Model, Architecture, and Interfaces

OOI-CYBERINFRASTRUCTURE SIAM Ports

OOI-CYBERINFRASTRUCTURE SIAM Model, Architecture, and Interfaces

OOI-CYBERINFRASTRUCTURE SIAM Device and Instrument

OOI-CYBERINFRASTRUCTURE SIAM Model, Architecture, and Interfaces

OOI-CYBERINFRASTRUCTURE SIAM Device Services

OOI-CYBERINFRASTRUCTURE SIAM Node and Port Manager (Details)

OOI-CYBERINFRASTRUCTURE SIAM Ports (Details)

OOI-CYBERINFRASTRUCTURE SIAM Device and Instrument (Details)

OOI-CYBERINFRASTRUCTURE SIAM Device Services (Details)

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

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

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

OOI-CYBERINFRASTRUCTURE OMF Proxy Architecture and Model Mule ESB/Active MQ OGC Queue <sps: get. Observation/> OGCStrategy get. New. Observation() Instrument Proxy Mediation Classes (Common Model) “ts” aquire. Data() SIAM Node Device Service Instrument

OOI-CYBERINFRASTRUCTURE OMF Proxy Architecture and Model Mule ESB/Active MQ OGC Queue OGCStrategy <om: Observation> <Item>32. 45</Item> <Item>121. 45</Item> <Iterm>-99. 99</Iterm> </om: Observation> convert. And. Send() Instrument Proxy add. Sample() publish. Data() Mediation Classes (Common Model) SIAM Node Metadata is tagged to data and data is parsed 32. 45, 121. 45, -99. 99 Device Service Instrument

OOI-CYBERINFRASTRUCTURE SENSORS and OMF Proxy Architecture and Model

OOI-CYBERINFRASTRUCTURE

OOI-CYBERINFRASTRUCTURE SENSORS and OMF Proxy Architecture and Model

OOI-CYBERINFRASTRUCTURE

OOI-CYBERINFRASTRUCTURE SENSORS and OMF Proxy Architecture and Model

OOI-CYBERINFRASTRUCTURE

Sample Sensor. ML from SIAM OOI-CYBERINFRASTRUCTURE

Sample OM from SIAM OOI-CYBERINFRASTRUCTURE

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

OOI-CYBERINFRASTRUCTURE Questions and Thanks

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

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

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

OOI-CYBERINFRASTRUCTURE SENSORS Report Requirements (cont. ) • Data and Metadata – – – – Up to individual PI (L 0) Automated sequencing of data (L 1) Uniform metadata form (L 1) Application interface to get static and dynamic metadata (L 1) Uniform application interface to display data (L 2) Base level of automated data quality control (L 2) Automated metadata discovery (L 3) Automated notification of metadata changes (L 3)