1

NOAA Observing Systems Architecture (NOSA)

Program Review Team Recommendation #32 & #40

Rob Mairs, Jim Barkley and the NOSA Team

October 21, 2003

2

Initial Scope of Task Team

• 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, but ensure expansion to international systems

• Include operational and research systems

3

Methodology used for NOSA Baseline or ‘as is’ Architecture

1. Determine purpose of architecture effort

2. Diagram all relevant components of architecture

3. Determine what you need to know about each component

4. Build data collection methodology

5. Gather data

6. Publish and use

7. Establish method for maintaining

4

Enterprise Architecture: Very short and short definitions:

• The explicit description and documentation of the current and desired relationships among business and management processes and supporting infrastructure.

or• An enterprise architecture is a tool to help individuals

think about their organization as a whole. An enterprise architecture captures a wide variety of information, establishes relationships among the various documents and diagrams and stores all of the information together in a single repository, so that managers can then see relationships, ask questions, identify problems, or run simulations to help make decisions about changes they are considering.

5

‘as-is’ NOAA Enterprise

RESEARCH

BUSINESS PROCESSES

STRATEGIC PLANNING

PARTNERS

PROJECTS

PROGRAMS

PEOPLE

MANAGE

HR

BUDGET

FACILITIES

IT INFRASTRUCTURE

COMMS

SOFTWARE

STAKE-HOLDERS

USERS

OBSERVING

SYSTEMSPRODUCTS

& SERVICES

6

RESEARCH

BUSINESS PROCESSES

M&O A&P

U&D E,A&IHR

MANAGE

PEOPLE

PROJECTSPARTNERS

OBSERVING

SYSTEMS

STRATEGIC PLANNING BUDGET

PRODUCTS &

SERVICES

COMMS

SOFTWARE

IT INFRASTRUCTURE

STAKE-HOLDERS

USERSFACILITIES

M&O – Monitor & Observe

U&D – Understand & Describe

A&P – Assess & Predict

E,A&I – Engage, Advise & Inform

PROGRAMS

‘to-be’ NOAA Enterprise Architecture

7

Step 2. Observing System Architecture Relationship Diagram

Larger System

Observing System

Data Management System

(CLASS)

Human

Environmental Phenomenon

Environmental Parameter

Sensing Element

Sensor

Platform / Station

part of

senses

is a

contains

characterizes

provides data to

Observation Control System

is controlled by

Location

located at

MobileFixed

is

Space

Air

Ground

Ocean

Space

Air

Ground

Ocean

Basic Service Requirement

< drives

provides data directly to

Userprovides info to

is type of

Stake-holder

has

Operator operated by

situated on

Support

supported by

Owner

owned by

Stakeholder Requirement

< drives< drives

8

Metis Architecture Modeling Tool

Objects & Relationships

9

NOSA In the Big Picture

10

NOSA Target or ‘to be’ Architecture Method

1. Assess observing systems effectiveness in meeting NOAA strategic goals

2. Prioritize observations or capabilities and validate requirements

3. Analyze alternatives to reach desired effectiveness

4. Select target that achieves most capability within cost and other constraints

11

NOSA Geospatial Database

Maximizing utilization of NOSA data!

12

Internet Map Portal

Metadata and Station Data Links

13

Connecting Satellite and In-situ Observations

A

B

C

Satellite footprints & in-situ observatories

Zoom in and select a footprint

Get a list of in-situ observatories that are in the selected satellite footprint.

14

AVHRR and DMSP Footprints

POES (AVHRR)

DMSP

15

NOSA + Significant Events

Integrating in-situ observatories with NESDIS Operational Significant Event Image Geotiffs to create a “Map of the Day”

16

NOSA Geospatial Partners?

NOS NowCoast:http://nauticalcharts.noaa.gov/csdl/op/nowcoast.htm

NWS MIRS:http://gisias.mirs.nws.noaa.gov/mirsweb/index.cfm