# Presentation: 319637

## NOAA Observing System Architecture (NOSA)

**Data Call Briefing Package**
**November 15, 2002**

## Change Record

_**Version**_**	**_**Date**_**	**_**Changes**_
**	****1****	****11/1/02****	****First Issue**
**	****2****	****11/15/02****	****Added survey tree example**

## Initial Tasking

**Develop an observing system architecture**
- Baseline (“state today”)
- Target architecture (“future state”—10-20 years)
**Base prospective observing systems on validated requirements**
**Investigate system consolidation and ownership transition (e.g., buoys)**
**Conduct a systemic review of all observing systems considering the following factors**
- Required system characteristics
- Number of and types of system users
- Capital asset value and recurring maintenance costs

## Initial Scope

**Focus first on baseline observing system architecture**
- Begin with systemic review of all NOAA observing systems
- Work closely with NOAA team developing the requirements-based management process
- Timeline for future observing system architecture development TBD
**Address only NOAA owned and/or operated systems**
**Include operational and research systems**

## NOSA Senior Steering Group

**NESDIS****	****Greg Withee, Rob Mairs (lead)****	**
**NMFS****	****Bill Fox**
**NOS****	****	****Steve Gill**
**NWS****	****Greg Mandt (lead), Paul Moersdorf**
**OAR****	****	****Mike Johnson**
**OMAO****	****Beth White**
**CIO****	****	****Carl Staton**

## NOSA Action Group

**NESDIS****	****Rob Mairs (lead), Howard Diamond, Lisa ****	****	****Botluk****	**
**NMFS****	****Ned Cyr, David Detlor**
**NOS****	****	****Steve Gill**
**NWS****	****Rainer Dombrowsky, Eric Meindl, Tim ****	****	****Ross**
**OAR****	****	****Sid Thurston**
**OMAO****	****Beth White**
**OCIO****	****Ira Grossman**
**IA****	****	****Michael Hales**
**Contractor Support (Aerospace Corp, Veridian)**

## Initial Action Group Focus

**Analyze purpose of observing system architecture**
**Establish framework, format and content of data call**
- Data call
- Data capture/analysis
- Follow-up interviews
**Discuss use of architecture tools (e.g., Ptech, Popkin, METIS)**
- Proper capture and visualization of various architecture views
**Assimilate data (principles, guidelines, standards, etc.)**

## NOSA Project Schedule Summary

**Data Call Finish on Monday, Dec 2nd**

## Architecture Queries

**How much is NOAA spending on observing systems?**
**What observing systems are associated with each NOAA strategic goal?**
**Display all observing systems owned by a particular line office.**
**What observing systems are supporting our ability to measure the heat content of the ocean (or other scientific query)?**
- What additional observing systems do we need to answer this particular question?
**Display all organizations that own buoys.**

## Architecture Queries(continued)

**Display all requirements not being met by current observing systems.**
**Display all observing systems that a certain stakeholder deems important.**
**Display all observing systems that measure a particular environmental parameter.**
**Display the acquisition costs of all observing systems associated with a certain strategic goal.**
**Display the geographic coverage of a particular observing system.**
- How does this coverage compare with stated requirements?

## Architecture Queries(continued)

**Display the NOAA network locations that observe a particular environmental parameter?**
- Do other US organizations operate similar systems?
- How do they compare to the NOAA system?
- Could NOAA use their data?  If so, what is the justification for this NOAA-operated system?
- How does this NOAA observing system fit within the global system for this parameter (e.g., GCOS, GOOS, World Weather Watch, etc.)?
**How much does NOAA pay to acquire data from non-NOAA sources?  What would it cost to deploy a NOAA-operated system to observe the same parameters?**

## NOAA Observing System Architecture (NOSA) Primary Information Flows

**NOAA Observing System Architecture (NOSA) Primary Information Flows**

- Element

- Element

- Element

- Element

- Element

- Element

- Modeling/Data Assimilation System (M/DAS)

- Report Generation System (RGS)

- Info Dissemination System (IDS)

- Users

- Data/Info Archival System (D/IAS)

- Environmental Phenomena

## Entity Relationship Diagram (ERD)

**Entity Relationship Diagram (ERD)**

- Larger System

- Observing System

- Data Handling System

- Human

- Environmental Phenomenon

- Environmental Parameter

- Sensing Element

- Sensor

- Platform / Station

- part of

- measures

- is a

- contains

- characterizes

- provides data to

- Observation Control System

- is controlled by

- Location

- located at

- Mobile

- Fixed

- is

- Space

- Air

- Ground

- Ocean

- Space

- Air

- Ground

- Ocean

- Basic Service Requirement

- < drives

- provides data directly to

- User

- provides info to

- is type of

- Stake-holder

- has

- Operator

- operated by

- situated on

- Support

- supported by

- Owner

- owned by

- Stakeholder Requirement

- < drives

- < drives

- Processing Element

- Remote

- In Situ

- is type

## NMFS Observing Systems

## NOS Observing Systems

## NESDIS Observing Systems

## NWS Observing Systems

## OAR Observing SystemsClimate Atmospheric Systems

## OAR Observing SystemsClimate Ocean Systems

## OAR Observing SystemsWeather & Air Quality Observing Systems

## OAR Observing SystemsOcean Observing Systems

## NOSA Data Flow

- NOAA
- Forge

- EA
- TOOL

**LO**
**1**

**LO**
**2**

**LO**
**N**

**. . . . . **

**SURVEYS**

- ARCH
- DESC

- GIS TOOL

- DOORS

**Requirements**

**System Characteristics**

- DOORS	Dynamic Object Oriented Requirements System
- EA	Enterprise Architecture
- GIS	Geospatial Information System

## Survey Forms in NOAA Forge

**Observing System Form ****(one per Observing System type)**

**Platform/Station Form ****(one or more per OS)**

**Sensing Element Form ****(one or more per OS)**

**Environmental Parameter Form ****(one or more per SE)**

**Geospatial Database**

**Processing Element Form ****(one or more per OS)**

**Data Handling System Form ****(one or more per OS)**

***NOTE:  At least ***_***one of each***_*** survey form type is required to be filled out for each Observing System.  See example on next slide.***

## Survey Tree Example

**Survey Tree Example**

**XYZ Observing System (XOS)**

**PT105 Floating Buoy Platform **

**Temperature Sensing Gage**

**Dry Bulb Temp**

**Geospatial Database**

**Observation Processor Unit**

**XYZ Data Handling System**

**Wet Bulb Temp**

**XYZ Weather Station **

**Geospatial Database**

**Anemometer**

**Wind Speed**

**Wind Direction**

**Forward Scatter Meter**

**Visibility**

***Environmental Parameter Surveys***

***Sensing Element Surveys***

## NOAA Forge Collaboration Environment

**https://class1.nesdis-hq.noaa.gov/**
**Login here (or add new users)**

**NOSA will use this tool to collect basic information about each Observing System**

## Adding NOSA Project Members

**Adding NOSA Project Members**

**One account per individual**
**Preferred name is last name only**
**Name with **_**no spaces**_
**Identify the organization **

**Hit Register button to complete New User setup**

## Starting NOSA Project

**Your personal page will look like this**

**Click here to enter the NOSA project**
**That is where you will start filling out survey forms**

**Click on “Survey” to start working on your surveys**

## Creating New Survey Templates

**Currently existing survey documents**

**Survey templates**

## Survey Document Administration

**Identify as Active, Inactive, Deleted, or Completed**

**Add members to survey document (allows editing)**

**Survey Questions**

**Survey Page (most surveys have more than one page)**

## Asking for Clarification

**Don’t forget to hit this button to submit your question or comment**

**Enter your question or comment here**

## NOSA Project Schedule Summary

## NOSA Project Details – Page 1

## NOSA Project Details – Page 2

## Expanded NOSA Project Schedule