10-ospo/pda discussion copc november 4, 2015 nesdis/ospo

10-OSPO/PDA Discussion

COPC November 4, 2015

NESDIS/OSPO

CSAB F2F (Oct 7-8, 2015)

Prepared by: Chris Sisko ([email protected])

Current NDE Operational StatusNDE Operational System (PE1) is functioning as intended.NDE Operational System (PE1) is the largest single distribution system

within ESPC (legacy network).NDE I&T system (PE2) is highly utilized and supports the following:

- IDPS maintenance release cycle- New algorithm deployments (called DAPs)- Algorithm refinement and enhancements - Bug fixes- Production Rule updates (separate from DAPs).- Expansion of tailoring options- Improvements to data handling- Relational Database updates / optimization rollouts

2

NDE Operational Products

3

Application Short Name

Application Name Product Name Format Satellite

ACSPO SSTAdvanced Clear Sky Processor for Oceans (NDE) - SST

SST, Clear Sky Mask netCDF SNPP

AOT Aerosol Optical Thickness VIIRS Aerosol Optical Thickness (NDE) BUFR SNPP

ATMS-SDR ATMS SDR radiances ATMS SDR radiances 22 channels (NDE) [BUFR] SNPP

CRIS-SDR-399 CrIS SDR radiances 399CrIS IR sounder SDR radiances 399 channels for NWP data assimilation (NDE)

[BUFR] SNPP

CRIS-SDR-1305 CrIS SDR radiances 1305CrIS IR sounder SDR radiances 1305 channels for NWP data assimilation (NDE)

BUFR SNPP

NUCAPS Level 2NOAA Unique CrIS ATMS product System Level 2

CrIS/ATMS Atmos Temp Profile CrIS/ATMS Atmospheric Moisture Profile

[netCDF] SNPP

MIRS ATMSMicrowave Integrated Retrieval System (NDE) - ATMS

MIRS ATMS image products MIRS ATMS SND products

[netCDF] SNPP

OMPS-NP OMPS nadir profile Ozone nadir profile (NDE) BUFR SNPP

OMPS-TC OMPS total column Ozone total column (NDE) BUFR SNPP

VIIRS-EDR VIIRS EDR VIIRS EDR (NDE) netCDF SNPPVIIRS-SDR VIIRS SDR VIIRS SDR (NDE) netCDF SNPPVIIRS Binary Snow Cover

VIIRS Binary Snow Cover VIIRS Binary Snow Map netCDF SNPP

VPW VIIRS Polar Winds VIIRS Polar Winds[BUFR], netCDF

SNPP

GVFGreen Vegetation Fraction VIIRS Green Vegetation Fraction GRIB2 SNPP

NTCPMicrowave Tropical Cyclone Products

Microwave Tropical Cyclone Products netCDF, TXT, PNG

SNPP

Upcoming Operational Products• Vegetation Health Products• GCOM-W• Active Fire

Products for DoD currently sent from the NDE system to DAPE

Products in the queue for DoD; will eventually be sent from the NDE system to DAPE

Final Notes on NDE systemBoth systems (PE1 and PE2) have been augmented with additional Linux

processing capacity.Unix/AIX based algorithms were completely phased out. Occasional distribution issues have caused random disruptions on NDE PE1

(ops system) at times for some PULL/PUSH jobs; upgrading the middleware on the operational system has mitigated these issues.

4

Sep 2013(initial operations)

Today(Sep 2015)

Number of users (subscriptions) 3 (12) 30 (320)

Average Data Ingest* ~70 TB ~110 TB

Production Success* 99.90% 99.98%

Distribution Success* 99.50% 99.97%

Total Distributed Data Size* ~10 TB ~37 TB

5

PDA Update

Process for Fielding New Requirements

Office of Systems Architecture and Advanced PlanningEntry point for new Level 1 requirements (e.g. new non-NOAA

data)Coordinates with other organizations and other NESDIS Lines

Offices to validate requirements, understand development costs, and ensure funding is available

POC Mark Mulholland 240 678-4286

6

PDAPDA has three system strings: I&T, NSOF Ops and CBU Ops

strings.

PDA increment 2.5 provides full user functionality, including the user interface (recently deployed/integrated).

PDA is being deployed into a new ESPC network that will have an initial external capacity of 57 Gbps (8 Gbps inbound); infrastructure is scalable to 120 Gbps.

PDA at NSOF will support many missions, but PDA at CBU only supports JPSS.

7

PDA / DAPE• For current NDE operations (now) – ESPC feeds DAPE for DoD’s additional

SNPP data needs.

• Continue supporting/sustaining DAPE in terms of legacy data flow

• Work towards distributing DAPE through PDA

• Final Path: DAPE through PDA• Minimize potential disruptions by maintaining DDS services while DAPE functionality

is determined.• NOAA’s approach will give DoD an opportunity to build confidence with PDA

distribution.• Once the DAPE to PDA to DoD data flow is fully functional, DDS will be

decommissioned.

8

PDA ScheduleOSPO has started onboarding staff to support PDA

OSPO will determine the best approach to monitor product delivery from PDA using the tools provided.

Expect ORR to occur in the late summer of 2016 • Document preparation for ORR expected to be complete by end of Feb 2016• ORR is largely driven by new missions (JPSS B2.0 and GOES-R)

9

Transition Notes Initial planning of the transition (TTO) approach was completed -

pending approval by JPSS and other stakeholders.

Latest known JPSS Block 2.0 ORR milestone is late May 2016 (TBD).

From start to end of the user transition is 210 days:• Pre-TTO phase (120 days)• TTO=0 phase (back-orbit / In-between S-NPP SVL contact)• Post-TTO phase (90 days w/ a targeted goal of 45 days)

10

Final Summary NDE system has been operational for well over a year; ~ 85% of the new NDE

(product generation system) will be the same when NDE 2.0 and PDA become operational.

PDA utilizes common transfer protocols and the performance of the system is driven by GOES-R requirements to rapidly ingest, process and make available data to meet user’s real-time needs.

Continue to support DAPE for DoD’s existing legacy data flow purposes and to move new data requirements to the PDA enterprise system as the least disruptive approach until subject matter experts can analyze the best path forward.

PDA ORR is tentatively scheduled for late Summer of 2016 – due to inter-dependencies on both JPSS and GOES-R.

11

Questions or Comments?

12

Additional Background Material

13

CSAB F2F (Oct 7-8, 2015)


Pre-TTO

15

TTO - Event Description of Event Event Details

- 120 DaysFreeze period

No New user Onboarding

New user onboarding is prohibited. Once post TTO is complete new users may be added. Additional freeze is put on rolling out any new algorithms. An exception can be made if there is an emergency fix that would otherwise completely halt transition.

✓ Announce system freeze to all ESPC stakeholders✓ Re-schedule non-critical algorithm changes to post TTO time

frame as warranted✓ Work with new users (if authorized) to determine best time for

integration post-TTO

- 95 Days ORR Preparation JPSS ORR prep ✓ See JPSS for details on parallel operations

- 90 Days I & I StatusCoordinate with all users for training on the new system/ I&I Status check

✓ Provide all external users with training documentation✓ Offer webinar training where necessary✓ Check with ESPDS and OSPO (still in integration process)

- 60 DaysFinal Training Phase for

PDAAll users will have completed training

✓ Validate user training matrix✓ See JPSS for details on parallel operations

- 45 DaysNDE 1.0 (PE-2) System Freeze to support final

NAB phase NAB Activity - I & T Freeze

✓ NDE 1.0 to receive and process data from the NAB✓ External test users interface w/ NDE1.0 where applicable

(NCEP, EMC, etc.)

- 30 DaysFormal notification of

TTOIssuance of ESPC Notification & Mission Notice of upcoming TTO

✓ Issue notification to ESPC and Mission external list✓ Coordinate w/ RTN, Raytheon, as well as Mission Support

Team ✓ See JPSS for details on parallel operations

- 20 DaysData Flow Consistency

Check

Recheck with major stakeholders (Priorities 1 & 2) regarding their interface status (i.e. is data still flowing)

✓ Confirm data flow consistency for:✓ NWS AWIPS/ NCEP/ ROCs✓ DOD ( 557th, FNMOC and NAVO)✓ EUMETSAT✓ CLASS✓ Remaining Priority 1 Users

- 7 Days 7 Day Notice from TTO Issue ESPC Notification ✓ RTN/ MST notification

- 5 DaysOperation Readiness

Review (ORR)ORR prep period ends and the formal ORR occurs

✓ Conduct formal ORR

CSAB F2F (Oct 7-8, 2015)


Pre-TTO and TTO=0

16

TTO - Event Event Description Event Details

- 2 Days Timing CoordinationCoordinate exact times during back orbit for the switch to occur

✓ Coordinate timing with internal stakeholders✓ Issue ESPC Notice and Mission Notice to respective distribution

list

- 0 Days TTO = 0Switch to NDE 2. 0 & New Ground System

Note: An initial “Prime group” consisting of 7 users will be brought on at this time; however, time permitting should allow an additional 6 users will be brought online. Following the initial on-boarding of the prime group there will follow up 48 hour monitoring period to ensure that data is flowing reliably. During this monitoring period no other users will be on-boarded.

✓ Activate the following prime group users, in order as listed:1. NWS/AWIPS 2. NCEP/WCOSS (NCO-OPS) 3. EUMETSAT 4. 557th

5. CLASS6. GRAVITE7. SDS

✓ Additional prime group users may be brought on-line during this time in the following sequence:

1. NCEP/EMC2. NCEP/NCO-IDP A/B (NPDS)3. FNMOC 4. NAVO5. ESPC/NIC 6. NECEI SS 7. ESPC/IMS

While on-boarding these users is a top priority, it may not be feasible at TTO=0. Therefore, any users of these users that do not make it on will be automatically bumped into User Group 1 and given 1st priority.

✓ Analyze product generation / distribution performance using available log information and RDBMS (Oracle) records

CSAB F2F (Oct 7-8, 2015)


Post-TTO

17

TTO + Event Description of Event Event Details

On-boarding ProcessThe following is a general description of the transition process. These general steps will be utilized in each phase for the transition of each user group. • User will be deactivated from NDE (PE1)• User will be activated in PDA• User logs and database will be monitored for 48 hours to ensure data is being actively received from the new ops data feed• Troubleshooting will occur as necessary. If problem(s) persist user will be moved back to NDE 1.0 (PE1)

+ 2 DaysOn-boarding

process begins (User Group 1)

Users are organized into groups based on priority. Each group is allotted 5 days to complete on-boarding. Any user that cannot complete on-boarding during this 5 day period will be automatically bumped in the next group.

✓ De-activate STAR-NCWCP on NDE 1.0 and activate distribution on PDA to STAR-NCWCP

✓ Monitor new PDA distribution to STAR-NCWCP and notify user of the transition to the PDA interface

✓ De-activate NASA-JPL on NDE 1.0 and activate distribution on PDA to NASA-JPL

✓ Monitor new PDA distribution to NASA-JPL and notify user of the transition to the PDA interface

✓ De-activate NOAA-AOML on NDE 1.0 and activate distribution on PDA to NOAA-AOML

✓ Monitor new PDA distribution to NOAA-AOML and notify user of the transition to the PDA interface

+ 7 Days48 hour

monitoring periodEnsure that data is flowing reliably to Users in Group 1.


+ 9 Days On-boarding (User Group 2)


✓ De-activate JMA on NDE 1.0 and activate distribution on PDA to JMA✓ Monitor new PDA distribution to JMA and notify user of the transition to the PDA

interface✓ De-activate CMC on NDE 1.0 and activate distribution on PDA to CMC✓ Monitor new PDA distribution to CMC and notify user of the transition to the PDA

interface✓ De-activate India-NC on NDE 1.0 and activate distribution on PDA to India-NC✓ Monitor new PDA distribution to India-NC and notify user of the transition to the

PDA interface

CSAB F2F (Oct 7-8, 2015)


Post-TTO

18

TTO + Event Description of Event Event Details

+ 14 Days48 hour

monitoring period

Ensure that data is flowing reliably to Users in Group 2.


Users that have not been integrated at this point will be reactivated and receive additional transition support at a later time.

+ 16 Days On-boarding(User Group 3)


✓ De-activate NASA-GPM on NDE 1.0 and activate distribution on PDA to NASA-GPM

✓ Monitor new PDA distribution to NASA-GPM and notify user of the transition to the PDA interface

✓ De-activate JTWC on NDE 1.0 and activate distribution on PDA to JWTC

✓ Monitor new PDA distribution to JTWC and notify user of the transition to the PDA interface

✓ De-activate STAR-CIRA on NDE 1.0 and activate distribution on PDA to STAR-CIRA

✓ Monitor new PDA distribution to STAR-CIRA and notify user of the transition to the PDA interface

+ 21 Days48 hour

monitoring period

Ensure that data is flowing reliably to Users in Group 3.


+ 23 - 44 DaysUsers groups 4, 5, and 6 contain only internal ESPC users. The only internal users that will be integrated into Block 2.0 will be the ones that cannot access the shared file system. If internal ESPC users must be integrated into Block 2.0 they will follow in the same fashion as the external users. A detailed view of internals integration can be seen in the TTO Timeline (page 11).

+ 45 DaysGoal:

End of User Transition

Goal of OSPO to have all necessary ESPC users integrated into Block 2.0.

✓ Any users still need to be integrated at this point there is another 45 day margin for them to become fully integrated

+ 90 Days Decommission Decommissioning of the old Block 1.2 systems✓ Block 2.0 will become the sole ground system for ESPC

users to obtain their data

CSAB F2F (Oct 7-8, 2015)


Internal and External NDE Users

19

Internal Users (ESPC) Description

MiRS Microwave Integrated Retrieval System

CW ESPC Coast Watch systems

VIIRSDIST VIIRS Mcidas system - SAB

NUCAPS NOAA Unique CrIS/ATMS Processing System

GCOM GCOM -> npds

IMS Interactive Multi-sensor Snow and Ice Mapping System – NIC/ESPC (X)

TOAST Ozone

PRODMON NDE PG Product Monitoring

TCP Tropical Cyclone Product systems

NIC National/Naval Ice Center

BSST Blended Sea Surface Temperature

Okeanos Ocean Color systems

GVF Global vegetation systems

External Users Description

NWS/AWIPS National Weather Service/ Advanced Weather Interactive Processing System

EUMETSAT European Organisation for the Exploitation of Meteorological Satellites

NCEP/WCOSS (NCO-OPS)

NCEP Super Computers (Tide/Gyre)

557th United States Air Force (USAF) 557th Weather Wing (formerly Air Force Weather Agency (AFWA))

STAR-NCWCP STAR – Central Distribution System

STAR-CIRA Colorado State – Cooperative

NASA-GPM Global Precipitation Mission

NASA-JPL Jet Propulsion Laboratory – NASA DAAC (archive)

NOAA-AOML Coast Watch nodes (GOMEX & Caribbean)

NCEP/NCO-IDP A/B (NPDS)

NCEP College Park/Boulder Systems

CLASS/NCEI NOAA Archive

JMA Japanese Meteorological Association

CMC Environment Canada – Met Centre

India-NC India Medium Range Forecast Center

GRAVITEGovernment Resource for Algorithm Verification, Independent Testing, and Evaluation

SDS NASA Science Data Segment

NCEP/EMC Environmental Modelling Center (Dev)

FNMOC Fleet Numerical Meteorology and Oceanography Center

NAVO Naval Oceanographic Office

JTWC U.S. Navy – Joint Typhoon Warning Center

NWSTG OPS NWS Telecommunications Operations Center

ESPC/DAPE – provides specialized data access to DoD today; however, all new mission data will be provided by PDA once operational

CSAB F2F (Oct 7-8, 2015)


CBU Data Flow

20

CSAB F2F (Oct 7-8, 2015)


N-WAVEN-Wave is a program of Federal and contract staff that

manage the NOAA Science Network known as N-Wave, and also supports projects outlined in the NOAA Strategic Plan for Network Optimization and Transport Services.

The network roadmap comprises four main goals:

1. Deliver Enterprise Transport Services

2. Enhance NOAA’s Network Security

3. Scale Network Capabilities

4. Optimize Network Services.

21

CSAB F2F (Oct 7-8, 2015)


N-WAVE Core

22

CSAB F2F (Oct 7-8, 2015)


NOAA Resilient TICAPs

CSAB F2F (Oct 7-8, 2015)


Internet 2 Partner

24

CSAB F2F (Oct 7-8, 2015)


Trusted Internet Connection• Agency-wide, NOAA networking is going through

a fundamental transition

• NOAA is implementing Trusted Internet Connection Access Points (TICAPS) to meet the OMB/DHS mandates

• All external connections to non-Federal or DoD networks MUST be routed through a TIC

CSAB F2F (Oct 7-8, 2015)


NOAA TIC ArchitectureEngineering Resilient TICAP Networks - Large Sites

The Denver and DC Metro large NOAA TICAPs will complement each other in resiliency, capacity and redundancy (Denver and DC Metro TICAPs will back each other up for failover) with the following attributes:

• TICAP Network equipment components will be housed at key Telecom Colocation facilities where fiber optic, commodity and R&E transport providers exists

• Network designed for geographic diversity - TICAP Network equipment installed across two separate physical colocation facilities providing

-Hardware redundancy (External Routers, Internal routers) -Internet/R&E peering redundancy

• Diverse, redundant fiber connectivity (dual homed) from NOAA sites to resilient TICAPs

CSAB F2F (Oct 7-8, 2015)


Traffic Symmetry SolutionsA given office or location connects to all external resources and the

Internet through a single TIC stack. Simplest solution. Poor availability due to outages and routine maintenance. Difficulty growing and scaling.

A given office or location maintains connections to multiple TIC sites, but only one may be in use at any given time.

“Warm spare” concept; backup pipe is unused until primary breaks. Inefficient use of resources; expensive. Difficult to ensure backup will always work properly when needed.

An office or location connects via an entity that controls traffic routing on both sides of the TIC stacks, ensuring symmetry.

High availability; automatically resilient under failures. Easy to scale and add additional connections. Efficient use of resources; allows load-balancing. X-Wave/ N-Wave solution

CSAB F2F (Oct 7-8, 2015)


X-Wave• Provide a peering infrastructure for network redundancy and

failover between TICAP sites• Enforce symmetrical IP traffic routing through the TIC• Consolidate and share ISP connections and R&E network

connectivity• External networks (providers, cloud, other direct partners) can

land in X-Wave, for routing to NOAA via TIC• X-Wave can provide locations for Science DMZs and low-risk

public data delivery • X-Wave and N-Wave need to be operated in a tightly

coordinated manner to ensure policy and configuration synchronization.

Internet Provider A Internet2

Regional Provider

Internet Provider B

Other External

X-Wave

WEB PROXY

CONTENT FILTERING

PACKET FILTERING

NCPS MONITORING

internalinternal

Seattle Denver Dallas DC Metro

WEB PROXY

CONTENT FILTERING

PACKET FILTERING

NCPS MONITORING

internal


Regional Provider

Internet Provider B

Other External

internal


Without X-Wave, Internet2 independently chooses it’s own best path back to the NOAA customer, breaking symmetry.

WEB PROXY

CONTENT FILTERING

PACKET FILTERING

NCPS MONITORING

internal


Regional Provider

Internet Provider B

Other External

X-Wave

internal


Internet VRF B

Internet VRF A

Preferred path is via Seattle



With X-Wave, Internet2 chooses it’s own best path back to X-Wave, and X-Wave sends it to the correct symmetric return TIC site.

WEB PROXY

CONTENT FILTERING

PACKET FILTERING

NCPS MONITORING

internal


Regional Provider

Internet Provider B

Other External

X-Wave

internal


internal

10-ospo/pda discussion copc november 4, 2015 nesdis/ospo

Documents

system pe2

cris sdr radiances

nde pe1 ops system

system strings

channels ndebufrsnppcrissdr

cris ir sounder sdr

nde systemboth systems

new level