NWS RFC SERVICE BACKUP DISCUSSION HIC CONFERENCE 31 July 2008. Billy G. Olsen, PE Hydrologist In Charge NWS – ABRFC – Tulsa, OK. POINT OF DISCUSSION. Current circumstances in AWIPS-II & CHPS planning activities provide a refreshing opportunity to address
Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.
Billy G. Olsen, PE
Hydrologist In Charge
NWS – ABRFC – Tulsa, OK
Current circumstances in AWIPS-II &
CHPS planning activities provide a
refreshing opportunity to address
NWS RFC Service Backup
Potential for RFC service backup to finally go mainstream with national support
How do we take advantage
of this opportunity?
Various unique local/regional hardware
and data ingest/dissemination configurations
One commonality is RFC self-backup
Systems are not supported nationally
RFC BACKUP OPERATIONS NATIONALPLANNING TEAM
Chartered May 2006 (Feb 07, Mar 07, Jan 08)
Currently on hold based on AWIPS-II
TEAM CHARTER FOR RFC BACKUP OPERATIONS
Vision: A robust operational scheme which supports operational backup of River Forecast Centers (RFC)
in time scales of hours to weeks.
Mission: Review current national and regional policies and procedures for RFC backup operations. Define
necessary operational concepts for RFC backup. Identify operational and system requirements to
implement the operational concepts. Develop the OSIP Stage 2 Concept of Operations (ConOps)
and Operational Requirements Document (ORD).
Scope of Authority/Limitations:
Team will review NWSI 10-2201, Backup Operations, and appropriate Regional Supplements.
Team will review the Hurricane Katrina Service Assessment, especially the findings and recommendations
related to RFC Backup, as well as the report on LMRFC backup operations compiled by a sub-team.
Team should consider lessons learned and past practices from previous RFC backup operations, as well
as various operational concepts, including Service Backup, Computational Backup, Local Backup, and
others as appropriate, in developing an RFC Backup ConOps
Team will consult with internal and external partners and customers, as needed
Organizational allegiances among the team members must not be allowed to influence either the
evaluation or the recommendations
The team will make decisions by consensus
The team will solicit/incorporate minority opinions if decisions are not reached by consensus
No travel expenses will be authorized
Team membership will be comprised of representation from OHD, OCWWS/HSD, NWS Regions,
Termination Date: The team will complete its work within 6 months of its formation.
Success Criteria/Deliverables: Deliver a Concept of Operations (ConOps) and Operational
Requirements Document (ORD) which will constitute the OSIP Stage 2 documentation
Commencement & Termination Date:
• The team will be formed and commence activities by March 9, 2007 and deliver its final report and briefing by September 31, 2007
Team Membership – Representatives From:
SR – Eric Jones, Senior Forecaster, LMRFC, Team Leader
CR – John Halquist, DOH, NCRFC
WR – Harold Opitz, HIC, NWRFC
AR – Dave Streubel, Senior Hydrologist, APRFC
ER – Joe Heim, Senior Forecaster, OHRFC
OCWWS – Randy Rieman, Senior Support Hydrologist
OHD – Jon Roe, Chief, OHD Software Engineering Branch, or designee
OST – TBD
FEWS design offers local high availability
system as well as on/off site backup capability
Experience with UK & European systems
Flexible system allows working within a budget
Synchronization relates to IHFS & OFS “type” data
At first glance…bandwidth appears manageable
CHPS AND RFC BACKUP
Concept of Operations
AWIPS Thin Client
OSIP Number: 08012
July 21, 2008
Steve Schotz - NWS/OST/PPD/SPB - Team Lead Ronla Henry - NWS/OST/SEC/DB Bill Ward - NWS/PR/ES&SD Duane Carpenter - NWS/AR/ESSD Heath Hockenberry - NWS/OCWWS/MSD/FPWSB Cyndie Abelman - NWS/OCWWS/MSD/AWSB Scott Jacobs - NWS/NCEP/NCO/SIB Richard Jesuroga - OAR/GSD Sher Schranz - OAR/GSD Eric Howieson - NWS/SR/SOD/SIB Mark Mollner - NWS/WR/SSD Josh Watson - NWS/ER/SSD Michael Graf - NWS/OCWWS/MSD/AWSB Gregory Noonan - NWS/CR/MSD
AWIPS-II THIN CLIENT Client
The Advance Weather Interactive Processing System-II (AWIPS-II) will provide a robust and flexible infrastructure for NWS forecast operations. Upon deployment, AWIPS-II will provide the functional equivalent of today's baseline software through AWIPS-I Operational Build (OB) 9. Currently, AWIPS-I does not include integrated enterprise solution to support the following missions:
Center Weather Service Units (CWSUs)
Weather Service Offices (WSOs)
Incident Support Specialists (ISS) including Incident Meteorologists (IMET)
NCEP Centers to partially support their Continuity of Operations (COOP) requirements and remote
These program areas require remote access to AWIPS capabilities to support their mission requirements.
The purpose of this AWIPS Thin Client project is to develop and deploy an integrated thin client solution that will satisfy the NWS enterprise requirements for remote access to AWIPS-II capabilities. The thin client capabilities must support the operational needs of the mission areas defined above.
NWS has an existing thin client capability provided by FX-Net. However, FX-NET only partially addresses NWS AWIPS remote access requirements. In addition, FX-Net is built on the original AWIPS-I architecture. Without an integrated thin client capability, NWS would be forced to maintain and enhance the original AWIPS-I baseline or enhance FX-NET to interface with the AWIPS-II baseline. This would duplicate software O&M efforts.
The Thin Client project planning and development will be led by the NWS in partnership with the NOAA Earth System Research Laboratory, Global Systems Division (GSD) and Raytheon Technical Services (RTS), the AWIPS-II prime contractor. Once developed, the thin client will become part of the AWIPS-II baseline and supported by RTS, accordingly.
The Thin Client project is part of the second phase of the AWIPS Technology Infusion project (OSIP 04-005) that extends the AWIPS-II architecture to all levels of NWS operations.
AWIPS-II THIN CLIENT Client
NCEP plans to use for backup (COOP)
4.3 NCEP Scenarios
User: All NCEP forecasters
Action: Continuity of Operations Plan (COOP) Implementation
The National Centers have requirements to maintain the level of product creation during a COOP event. The Centers would use the Thin Client during the transition period from the main site to the backup site. In some short-lived situations, the use of the Thin Client may be preferable to fully activating the backup site.
AWIPS-II THIN CLIENT Client
SCHEDULE – OSIP 08-012
AWIPS-II THIN CLIENT Client
From Wikipedia, the free encyclopedia
A thin client (sometimes also called a lean or slim client) is a client computer or client software in
client-server architecture networks which depends primarily on the central server for processing activities,
and mainly focuses on conveying input and output between the user and the remote server.
In contrast, a thick or fat client does as much processing as possible and passes only data for communications and storage to the server.
Many thin client devices run only web browsers or remote desktop software, meaning that all significant
processing occurs on the server. However, recent devices marketed as thin clients can run complete
operating systems such as Debian GNU/Linux, qualifying them as diskless nodes or hybrid clients.
As a consequence, the term "thin client", in terms of hardware, has come to encompass any device
marketed as, or used as, a thin client in the original definition – even if its actual capabilities are much
greater. The term is also sometimes used in an even broader sense which includes diskless nodes.
WHERE DO WE GO FROM HERE?
WHERE DO WE GO FROM HERE? Client
SOME OPTIONS ARE…
A) Sort out bureaucracy (teams / projects)
B) Re-Start National RFC Backup Team (liaison w/CAT & Thin Client Teams)
1) Same team as previously (National RFC Bkup)
2) Same team as OSIP IWT 07-056 (RFC Bkup)
3) Add new team member(s) from CAT RFC(s)
4) Form new team
C) CAT becomes responsible for RFC Backup planning
(liaison w/Thin Client Team & RFCs/Regions)
D) Add an RFC Rep to Thin Client Team
(liaison w/CAT & RFCs/Regions)
E) Other ideas