ooi ci lca review august 2010 ocean observatories initiative concepts of operations john graybeal...

OOI CI LCA REVIEW August 2010

Ocean Observatories Initiative

Conceptsof

Operations

John Graybeal

Life Cycle Architecture ReviewLa Jolla, CA


Agenda

•Concepts of Operations for Entire System (Day in

the Life)

•Scientist

• Instrument

•Data

•Concept of Operations: Release 1 LCA ‘end to end’

•Data Life Cycle: Ingest and Transfer (External)

•Sensor Control and Data Acquisition (internal only)


Concept of Operations: Scientist

CI Science User Concept of Operations

• Virtual LaboratoryVirtual Laboratory, Signing up Partners, Sharing

Documents




• Data StreamsData Streams: Subscribe, Access, Assess,

Integrate




• Pushing DataPushing Data: Automated, Streaming, Notifying,

Archiving, Public




•Operations: Monitoring, Troubleshooting,

CommunicatingCommunicating


Concept of Operations: Instrument

CI Instrument Life Concept of Operations

Stages

• ManufactureManufacture

• CommissioninCommissionin

gg

• DeploymentDeployment

• RecoveryRecovery

Actors & Processes

• ResourceResource

• Participant/RoleParticipant/Role

• Actions or InteractionsActions or Interactions

• Authentication/Authentication/

AuthorizationAuthorization

• Governance/PolicyGovernance/Policy

• IdentityIdentity


Concept of Operations: Data

CI Data Life Cycle Concept of Operations

•Transformations and tribulations of data streams

in OOI CI


Release 1 End-to-End Scenarios

•Scenario 1: Data Life Cycle: Ingest and

Transformation

• Illustrating a scenario we worked with NOAA to

define

•Scenario 2: Sensor Control and Data Acquisition

• (Some) Stages of the sensor life cycle

•Viewed with human perspective, particularly of

marine IOs


Release 1 End-to-End Scenario: Data Life Cycle


An OOI-IOOS Collaboration: Features• Ingest of data

•Converting data to canonical (described) form

•Converting data to common (known) model

•Publication of data in near real time

•Subscription to data that meets user contract

•Notification of arrival of new data

•New data set

•New message in data stream

•Presentation of data in multiple formats


12

OOI CI LCO Review, Feb 2010

The Plan•1/28/2010

•“Improve the process by which researchers get data to drive models.”

•OOI-CI & IOOS-DMAC Intersection Development Project-FY2010

•Arthur Taylor, Charles Alexander, Matthew Arrott, Jeff deLaBeaujardiere,

•John Graybeal, Steve Hankin, Roy Mendelssohn, John Orcutt, Bill Pritchett,

Rich Signell, David Stuebe, Sam Walker, John Wilkin

•1. Executive Summary:

•Overview: This project is intended to improve the automated processing and transfer of

data needed by regional models for forcing and assimilation.

12


13


IOOS Collaboration

13


14


Stress Case for Release 1

•This is the stress case for the R-1 release

•ambitious set of capabilities required

•challenging data sets (large, complex)

•wide mix of provider and user communities

• fairly unforgiving schedule

•Schedule

•Ready at end of Release I

•coordinated with IOOS DMAC activities

•More to come in the External Observatories presentation

14


Release 1 End-to-End Scenario: Sensor Life Cycle


16


Interface TestingInterface Testing

16

Step 4: Start Interface Tests


17


DeployedDeployed

17

Step 7: Setup, Checkout


18


ValidatedValidated

18

Step 8: Enable

•Data and metadata flow through observatory.

•Users and systems can find these outputs.


Thanks !

Questions ?


Ocean Observatories Initiative

Product Descriptionand

Use Cases

John graybeal

Life Cycle Architecture ReviewLa Jolla, CA


Agenda

•What is the Release 1 Product Description?

•What are the Product Description Use Cases?

•How to Navigate and Read the Product Description

•R1 Product Description Use Cases (basic to

advanced)

•Applying the Product Description

• In this review

• In our development


What is the Release 1 Product Description?


What is the Release 1 Product Description?

•Captures capabilities

• (as we wrote it) Makes them explicitly visible

•Outlines functions and relations

• (as we wrote it) Identifies ‘interesting’ technical

points


What are the Product Description Use Cases?


R1 Product Description Use Cases

Moving and Saving Data

UC.R1.05 Synchronize State Data Synchronize state in distributed data store

UC.R1.06 Distribute Data Product Data made available to many consumers

UC.R1.07 Subscribe To Data User finds data, asks for update notifications

UC.R1.08 Persist Streamed Data Store streamed data for given period of time

Basic Connection and CommandsUC.R1.01 Hello User User gets an ID and logs inUC.R1.02 Hello Instrument Instrument gets ID and is hooked upUC.R1.03 Hello Data Source Data source registered and

connectedUC.R1.18 Command An InstrumentSend typical commands to specific

instrumentUC.R1.19 Direct Instrument AccessDirectly communicate with

instrumentUC.R1.20 Command A Resource Send typical commands to specific

resource


R1 Product Description Use CasesData Manipulation and Presentation

UC.R1.04 Ingest and Describe Data

Externally provided data read and distributed

UC.R1.12 Annotate Data Information or description is added to resource

UC.R1.13 Transform Data Data process produces new data from old

UC.R1.21 Derive Data Product Externally (Merge Data)

Provide data unified from many sources

UC.R1.22 Present as Catalog Present organized set of resources externally.

UC.R1.24 Version A Resource Resource is supplanted by changed version

UC.R1.09 Discover Resource User searches for resources meeting criteria


R1 Product Description Use CasesServices and Scaling: Elastic ComputingUC.R1.11 Define New Service Add new service to system capabilitiesUC.R1.14 Use Service Anywhere Messages go to services wherever they

areUC.R1.15 Put Services AnywhereAllocate services where need is

greatest

UC.R1.16 Scale the ProcessingIncrease processing quickly to meet demand

UC.R1.17 Replicate ServiceConfigure service once, deploy many times

Interact, Operate, and Maintain

UC.R1.25 Assure Reliability Computer fails, messages resent, work resumes

UC.R1.27 Configure Access Page Configure user's web page that accesses ION

UC.R1.28 Operate System Configure system and respond to requests

UC.R1.29 Monitor System Anticipate issues using monitoring toolsUC.R1.30 Troubleshoot System Diagnose issues using logs, feeds, tools


R1 Product Description Use Cases

Interactions, Policies, and AgreementsUC.R1.31 Assert Access Policy Define access policy for given resourceUC.R1.32 Conduct Negotiation Negotiate agreement (or not) between

agentsUC.R1.33 Enroll in an Org Enter as a member into an Organization

(Org)UC.R1.34 Share an Org

ResourceCollaborate with Org member offering a resource

UC.R1.35 Share Affiliated Orgs' Resources

Orgs form a contract to allow resource sharing

UC.R1.36 Create an Org Create an Organization (Org) with defined characteristics

UC.R1.10 Define Interaction Describe pattern of interaction between actors


Applying the Product Description

• In this review

•Define progress and activities in terms of these use

cases

•Demonstrate key parts of many use cases

•During development

•Organize work among the teams

•Negotiate understanding of detailed processes

•Provide context for specific tasks

•Assess progress


Thanks !

Questions ?