310 likes | 489 Views
Concepts of Operations. John Graybeal Life Cycle Architecture Review La 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)
E N D
ConceptsofOperations • John Graybeal • Life Cycle Architecture Review • La 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 Laboratory, Signing up Partners, Sharing Documents
Concept of Operations: Scientist CI Science User Concept of Operations • Data Streams: Subscribe, Access, Assess, Integrate
Concept of Operations: Scientist CI Science User Concept of Operations • Pushing Data: Automated, Streaming, Notifying, Archiving, Public
Concept of Operations: Scientist CI Science User Concept of Operations • Operations: Monitoring, Troubleshooting, Communicating
Concept of Operations: Instrument CI Instrument Life Concept of Operations • Stages • Manufacture • Commissioning • Deployment • Recovery • Actors & Processes • Resource • Participant/Role • Actions or Interactions • Authentication/Authorization • Governance/Policy • Identity
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
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
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. OOI CI LCO Review, Feb 2010 12
IOOS Collaboration OOI CI LCO Review, Feb 2010 13
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 OOI CI LCO Review, Feb 2010 14
Step 4: Start Interface Tests Interface Testing OOI CI LCO Review, Feb 2010 16
Step 7: Setup, Checkout Deployed OOI CI LCO Review, Feb 2010 17
Step 8: Enable Validated • Data and metadata flow through observatory. • Users and systems can find these outputs. OOI CI LCO Review, Feb 2010 18
Thanks ! Questions ?
Product DescriptionandUse Cases • John graybeal • Life Cycle Architecture Review • La 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? • Captures capabilities • (as we wrote it) Makes them explicitly visible • Outlines functions and relations • (as we wrote it) Identifies ‘interesting’ technical points
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 ?