noaa weather wire service project
DESCRIPTION
NOAA WEATHER WIRE SERVICE PROJECT. Presented to: NWS Partners August 5, 2013 Jim McNitt Project Manager Office of Science and Technology National Weather Service National Oceanic and Atmospheric Administration Department Of Commerce 1325 East-West Highway - PowerPoint PPT PresentationTRANSCRIPT
1
NOAA WEATHER WIRE SERVICE PROJECT
Presented to:
NWS PartnersAugust 5, 2013
Jim McNittProject Manager
Office of Science and TechnologyNational Weather Service
National Oceanic and Atmospheric Administration Department Of Commerce1325 East-West Highway
Silver Spring, MD 20910-3283
2
BackgroundWeather Radio Improvement Program (WRIP)
established as a NWS program (2006)Phase 1 - System Design and Prototype (2007 –
2008)Phase 2 - System Development and Deployment
(2009 – 2012)Final detailed designSystem Acceptance TestPre-Operational Test and Evaluation (OT&E)
In April 2012, WRIP-2 was established to move NOAA Weather Wire Service (NWWS) to the NWS dissemination architecture
In May 2013, Office of Science and Technology separated NWWS from NOAA Weather Radio/Broadcast Message Handler (NWR/BMH) and moved the NWWS Project under the Integrated Dissemination Program (IDP)
3
Project Components
NWWS-Sat: Satellite broadcast through AWIPS Satellite Broadcast Network (SBN) to end users
End User Client (EUC): EUC software to reside on satellite users’ systems. Functions are: message collection, message archiving, message visualization, and product filtering
Open Interface (OI): Data “push” via internet. Low-cost option for users without stringent delivery requirements . Being developed using existing NWS-Chat capability, and integrated within NWS Internet Dissemination System (NIDS)
National Law Enforcement Telecommunications Systems (NLETS): New software to handle message collection, message transformation based on user profile configurations, and dissemination to NLETS center to support 34 state entities, who redistribute to other state/local emergency managers
4
Systems Architecture
NOAA Weather Wire Current System Configuration
5
6
Milestone Schedule
ID2013 2014
Jun OctApr JanMar
1 12/19/201210/15/2012
Jul Nov Apr
6
2 9/17/20124/3/2012
3/18/20132/19/2013
8 7/24/20136/11/2013
11 12/18/20139/12/2013
2012
Oct
7 7/10/20135/2/2012
9 9/9/20136/3/2013
JunMayFeb
13
12 1/30/20141/30/2014
5/2/20142/3/2014
Task Name
Install ground terminals at OT&E sites
NWWS SAT (SBN Channel 201)
NWWS Sat and EUC Interface Control Document (ICD)
Develop NWWS End User Client (EUC)
SIT and SAT forNWWS Sat
Implement Operational Support (Tier 1/2/3) for OT&E
IOT&E (Ph 1)
Deployment Readiness Review (DRR) for NWWS SAT and NWWS EUC
Concurrent Ops CSC
18
14 10/11/201310/8/2012Develop Nlets Release 1
11/29/20136/3/2013Develop Nlets Release 2
23
22 3/3/20143/3/2014IOT&E (Ph 2) TRR
6/9/20143/4/2014IOT&E (Ph 2)
27
25
26
10/1/201410/1/2014DRR
12/30/201410/1/2014Concurrent OPS with CSC
12/30/201412/30/2014CSC services end
5 4/17/20134/16/2013NWWS SAT, EUC, and Nlets CDR
17 8/9/20134/22/2013NWWS Nlets and OI ICD
19 2/18/201412/2/2013Schedule Reserve
Jan Aug FebSep Dec MarFeb OctAug NovJanMarMay SepJul JanDecMay Aug SepDec JulNov
2015
Apr Jun
3 5/22/20134/25/2013NWWS MS-3
4 4/17/20134/17/2013NWWS OI and MMS PDR
15 8/30/20134/22/2013Develop Open Interface push
Feb Mar
24 9/29/20146/10/2014Schedule Reserve
21 2/28/20142/19/2014NLETS SIT and SAT
10 8/1/20137/31/2013Delta CDR
20 1/22/20141/21/2014Delta CDR
16 10/1/20137/2/2013Stage OI inNIDS
NOAA Weather Wire Future System Configuration
7
NWWS End User Terminal (current compared to new)
8
Calypso (current) Novra (new)
RS232 Data Output Ethernet 10/100 Base T Data Output
Product filtering included within receiver
No product filtering within the receiver - Filtering needs to be provided by end user-developed external application.
Data product format is WMO message
Data product format is WMO message wrapped in NOAAPort Transport layer protocol
9
Tier 2 Tier 3
User Tier I
START 1. NOVRA blue LOCKED light ON?
2. NOVRA data light FLASHING?
YES
3. Are NWWS products flowing through
EUC client
YES
No
No
4. Is the EUC client malfunctioning?
YES
Yes
5. Is the EUC tracking messages OK?
No
No
Yes
SAT OT&E USER NEEDS TO VERIFY THESE 5 CHECKLIST ITEMS BEFORE
CALLING HELP DESK
NWWS OT&E SBN Test User Help Data FlowJuly 18, 2013
Problems in test site local system/
infrastructure?
NO
Test site needs to fix their local system/
infrastructure
YES
END
There are no apparent problems. If other problems or issues persists, call Help Desk
Yes
Call NWWS Help Desk
301-713-0864 x 173Or
Provide results of 5 point checklist and
likely cause
This is likely a “No Data”
issue
This is likely an “EUC
Client” issue
This is likely a “garbled or missing message”
issue
No
IsNCF experiencing an
SBN issue?
Assign the ticket to NCF as Tier 2.
· Open a ticket.· Use NWWS-Test ticket
category· Use NWWS-Test
distribution list· Include email of user(s)· Include checklist results· Include any symptoms
Assign the ticket to OPS23 as Tier 2.
Yes
No
Assign the ticket to DRS as Tier 2.
Tier 2 / 3 investigates and fixes the problem, providing periodic
updates and progress status to Tier 1
Tier 2 / 3 reports resolved status with
fix action/resolutuion to Tier 1
Yes
Contactuser. Do they confirm that the problem has
been fixed?
No
Problem has been
fixed.
Close the ticket
Is this a hardware issue? No
Don’t Know
10
Questions?