kevin gomes, sensors overview and architecture ooi cyberinfrastructure: sensing and acquisition...

Kevin Gomes, SENSORS Overview and Architecture

OOI Cyberinfrastructure:Sensing and Acquisition Workshop

San DiegoAugust 5-7, 2008

OOI-CYBERINFRASTRUCTURE

SENSORS Overview and Architecture

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


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


SIAM Model

“mmddyy=...”

“time=...”

Data loggerclient

Time synchronizer

client

“acquire”getData()

getData()

setC

lock

()

setClock()

HydroRadHydroRadinstrument

serviceSta

nd

ard

inte

rfac

e

SBE-16instrument

serviceSta

nd

ard

inte

rfac

e SBE-16“ts”


SIAM Concepts

Instrument

PU

CK

Power Port

Instrument Port

Port

Node

.

.

.

Node Manager

Port Manager

Device Service

Instrument

PU

CK

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


SIAM Model, Architecture, and Interfaces


SIAM Node and Port Manager


SIAM Ports


SIAM Device and Instrument


SIAM Device Services


SIAM Node and Port Manager (Details)


SIAM Ports (Details)


SIAM Device and Instrument (Details)


SIAM Device Services (Details)


SENSORS Work to apply to ALOHA and MARS

PUCK

RS-232 to Ethernet

Ethernet

RS-232SSDSInterface

Shore SideData

System SSDSInterface

Instrumentservices

Dig

i Rea

lPor

t

Cable ShoreNode

Shore-side ComputerShore-side Computer(at MBARI)(at MBARI)

SIIM

CTD

Shore Network (Internet) Seahurst Cable


Extending to OMF

CTD

RS-232 to Ethernet

Ethernet

RS-232SSDSInterface

SSDSInterface

Instrumentservices

Dig

i Rea

lPor

t

Cable ShoreNode

Digi

Shore Network (Internet) ALOHA Cable

Shore SideData

System

MBARIEnterprise

ServiceBus

NCSAEnterprise

ServiceBus

Proxy &Strategy


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

Translation between common Instrument Proxy interface to language d’jour

Common interface specification for instrument in observatory

Common interface specification for instrument in observatory Translation

between legacy middleware and common model

Translation between legacy middleware and common model

= CI Exchange

= CI Instrument Agent

= State Model



Instrument

Mule ESB/Active MQ

OGCStrategy

SIAM Node Device Service

OGC

Queue

Instrument Proxy


<sps:getObservation/><sps:getObservation/>

getNewObservation()getNewObservation()

aquireData()aquireData()

“ts”“ts”



Instrument

Mule ESB/Active MQ

OGCStrategy

SIAM Node Device Service

OGC

Queue

Instrument Proxy


<om:Observation> <Item>32.45</Item> <Item>121.45</Item> <Iterm>-99.99</Iterm></om:Observation>

<om:Observation> <Item>32.45</Item> <Item>121.45</Item> <Iterm>-99.99</Iterm></om:Observation>

convertAndSend()convertAndSend()

addSample()publishData()

addSample()publishData()

32.45, 121.45, -99.9932.45, 121.45, -99.99

Metadata is tagged to data and data is parsed

Metadata is tagged to data and data is parsed


SENSORS and OMF Proxy Architecture and Model

QuickTime™ and a decompressor

are needed to see this picture.

OOI-CYBERINFRASTRUCTURESample SensorML from

SIAM



OOI-CYBERINFRASTRUCTURESample OM from

SIAM




Integration ofIEEE 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 Transducer

1451.0 TEDS

STWSConsumer

STWS SOAP/HTTP

IEEE 1451.0 HTTP

IEEE 1451.0 HTTP Client

IEEE 1451.0 HTTP Server

RS 232 C

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


Questions and Thanks


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)


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)



• 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)



• 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)

kevin gomes, sensors overview and architecture ooi cyberinfrastructure: sensing and acquisition...

Documents

workshop reportproject

orion workshop

middleware requirements

legacy middleware

work siam

san juanworkshop

acquisition workshopsan

kevin gomes