Transcript TDWRData Supplemental Product Generator Preliminary Design Review October 14, 2004

TDWRData
Supplemental Product Generator
Preliminary Design Review
October 14, 2004
Pete Pickard
Office of Science and Technology
Systems Engineering Center
Purpose
• This review is conducted to:
– Present the plan and preliminary progress on the project to
implement the TDWR Supplemental Product Generator
– Evaluate the progress, technical adequacy, and risk
resolution (on a technical, cost, and schedule basis) of the
selected design approach,
– Determine its compatibility with requirements specifications,
– Evaluate the degree of definition and assess the technical
risk associated with the selected approach, and
– Establish the existence and compatibility of the physical and
functional interfaces among the configuration item and other
items of equipment, facilities, computer software, and
personnel
TDWRData PDR
14 October 2004
2
Agenda
•
•
•
•
Project Scope
Project Background
Team Organization
Plan for Stage 4 (Operational Development)
and Stage 5 (Deploy, Maintain, Assess)
• Requirements Overview
• Preliminary Design
TDWRData PDR
14 October 2004
3
Agenda (concluded)
•
•
•
•
•
•
•
Security Planning
Test Planning
Acquisition/Procurement Planning
Deployment Planning
Support Planning
Responsibility Transfer Planning
Next Steps
TDWRData PDR
14 October 2004
4
Project Scope - Phases
• Proof of Concept
– Four WFO-TDWR sites; WEB server images; completed
successfully
• Limited Production System
– Development of Supplemental Product Generator, modeled on
RPG
– Standalone initially with SEC O&M
– Field test (OAT) concludes in Q3 FY2005 at Proof of Concept sites
• Full Scale Deployment
–
–
–
–
–
Begin Q3 FY2005
Forecaster training through WDTB
Site and NRC ElTech training through NWSTC
O&M ultimately under NEXRAD program (Beginning FY2007)
MOA with FAA for TDWR access and O&M support
TDWRData PDR
14 October 2004
5
NWS/FAA MOA
• This Agreement covers the following work:
– Implementation of telecommunications links between TDWR
units and NWS sites, or links between the high impedance
taps of the TDWR to ITWS link to NWS sites.
– Internal FAA coordination of approvals for TDWR-NWS
connections.
– NWS coordination of, and funding for, installation of TDWRNWS telecommunications links.
– FAA technician assistance to NWS in maintaining NWS
telecommunications equipment at TDWR sites.
– Informal sharing of information between local FAA and NWS
contacts for TDWR outages and other issues.
– NWS use and re-distribution of TDWR weather data.
TDWRData PDR
14 October 2004
6
Project Scope - CONOPS
• General concept
– Enable WFO forecasters to use TDWR products to support
forecasts and warnings in a manner similar to the way they use
WSR-88D products.
– Use AWIPS radar product request tools and D2D display tools
– Complementary rather than primary operational data
• Principal users
– WFO forecasters initially; wide range of NWS and other users
potentially
• Operational availability
– Similar to WSR-88D, 96% of time that TDWR is operating
– TDWR operating status a function of FAA O&M priorities and
procedures
TDWRData PDR
14 October 2004
7
Project Scope – CONOPS
(concluded)
•
Operational impacts
– More radar data to analyze, with 5 cm wavelength increase in attenuation &
range/velocity folding
– Improved warning accuracy and reduced false alarms for tornadoes and
other severe weather
– Potential use for numerical model data assimilation
•
Organizational impacts
– Deployment dependent on AWIPS DX implementation to avoid data server
capacity issue
– NWS-FAA MOA to enable NWS access to TDWR units
– Training
– Maintenance concept will include site ElTech support
– Potential need for NWS infrastructure capacity enhancements to meet
future requirements
• Product distribution beyond local WFO
• Central collection of products and base data
• NCDC archiving
TDWRData PDR
14 October 2004
8
Project Scope – TDWR Sites
MSP
NEXRAD
TDWR
ORD
MDW
SLC
MCI
DIA
LAS
ICT
STL
TUL
PHX
OKC
BOS
DTW
MKE
JFK/LGA
CLE
PIT PHL
CMH
EWR
BWI
DAY
DCA
IND
CVG IAD
ADW
SDF
RDU
BNA
CLT
MEM
ATL
DFW
DAL
IAH
HOU
MSY
MCO
TPA
PBI
FLL
MIA
SJU
Guam
TDWRData PDR
14 October 2004
9
Project Background - Mission
• Addresses NWS mission needs and NOAA Strategic
Goals.
• The NWS requires the best possible information on
developing thunderstorms to support tornado, severe
thunderstorm and flash flood warnings.
• TDWR data would complement WSR-88D data with:
– Coverage: data for cone of silence and longer ranges of
WSR-88D
– Timeliness: base elevation update every minute; volume
updates every 3 minutes
– Spatial resolution: 150 meter linear resolution; potential for ½
degree angular resolution
TDWRData PDR
14 October 2004
10
Project Background - Benefits
• By using FAA weather radar data to complement
WSR-88D data, benefits can be realized in the
following areas:
–
–
–
–
–
–
–
–
–
–
Long-range low-level phenomena
Different viewing perspectives for a given storm
Potential mitigation of range folding obscuration
Backup during outages
Data in areas of incomplete coverage
Multiple Doppler analysis
Improved “best info” mosaics
Improved quality control of WSR-88D data
Improved precipitation estimates
Alleviate effects of the WSR-88D cone of silence
TDWRData PDR
14 October 2004
11
Operations and Services
Improvement Process
G1
G2
Stage 1
Stage 2
Need/Opportunity
Collection
Validation
G1 Core Documents
1) Need
Identification
Document
TDWRData PDR
Stage 3
Research
&
Analysis
G2 Core Documents
2) Statement of Need
3) Operations Concept
4) Operational Reqs.
5) Program Plan
14 October 2004
G4
G3
Stage 4
Operational
Development
G3 Core Documents
6) Business Case
7) Requirements
Document
8) Operational
Development
Project Plan
Stage 5
Deploy,
Maintain, &
Assess
G4 Core Documents
9) Deployment Decision
Document
10) Deployment,
Maintenance &
Assessment Plan
12
OSIP Status
• Stage 2 and Stage 3 documentation
completed
• Stage 3 (Research and Analysis) completed
• Gate 3 held on 17 August 2004 approved
proceeding with Stage 4
TDWRData PDR
14 October 2004
13
Team Organization
•
•
•
•
•
•
•
•
•
•
•
Program Management (OST)
Project Lead (OST)
Project Engineer (OST)
Requirements (OCWWS, OST)
Design, Development (OST)
Maintenance and Logistics (OST, OPS)
Operational Assessment Testing (OST, OPS)
Integration Testing (OST, FSL, NGIT)
Training (NWSTC, WDTB, OST)
Deployment Planning (OST, OPS)
Contracts (OFA)
TDWRData PDR
14 October 2004
14
Plan for Stage 4 and Stage 5
• Other Key Milestones
– CDR
– Deployment begins
TDWRData PDR
14 October 2004
Q1 FY2005
Q3 FY2005
15
NWS Requirements Overview
Operational Requirements
• TDWRData Operational Requirements Document
describes the operational capability, technical
support, and performance parameters
• Continuous operations, 96% availability when TDWR
operational
• Receive highest spatial and temporal resolution
available from TDWR unit
– Deploy with spatial resolution consistent with existing
product formats
• Base reflectivity, velocity and spectrum width product
generation for all elevation angles
TDWRData PDR
14 October 2004
16
NWS Requirements Overview
Operational Requirements
(concluded)
• Product formatting compliant with WSR-88D RPG
ICDs
• Product request, display and manipulation with same
AWIPS tools used for WSR-88D products
• Design includes support for implementing additional
products
• Initial archiving through existing local AWIPS 7-day
product archiving capability
• Additional NWS archiving requirement is TBD
• Level 2 data logging is available on SPG
– Requirement for storage to physical media is TBD
TDWRData PDR
14 October 2004
17
SPG Requirements Overview
Introduction
• TDWR SPG Definition - all HW & SW for
–
–
–
–
base data ingest from the TDWR
real-time generation, storage, and distribution of products
control, status monitoring, and error detection
display and data entry by operational user (as required)
• For the purpose of system specification requirements definition,
the TDWR SPG is viewed as a subset of the functionality of the
WSR-88D RPG.
• Only those requirements identified for IOC are presented.
TDWRData PDR
14 October 2004
18
SPG Requirements Overview
Introduction
• High Level Requirements
– base data ingest directly from the TDWR
– produce products formatted the same as corresponding
WSR-88D products
– initial product set to include base data products
– initially support NWS primary users (AWIPS)
– distribute products to AWIPS leveraging the existing radar
product request/distribution interface (RPS lists and one-time
requests)
– products designed and formatted to facilitate operational
display via D2D on AWIPS
TDWRData PDR
14 October 2004
19
SPG Requirements Overview
Introduction
• Design Goals
– The SPG design should reuse as much of the WSR-88D
RPG software as possible.
– Design should facilitate adding derived products to the
product set
– Design should facilitate expansion to include ingest of other
FAA radars (ARSR-4, ASR-9, ASR-11)
TDWRData PDR
14 October 2004
20
SPG Requirements Overview
Introduction
• RPG requirements contained in the WSR-88D
System Specification served as a guide in developing
derived SPG requirements.
– RDA, PUP, RMS, MLOS, and BDDS related requirements
were not included.
– Functional and performance requirements were based upon
the initial TDWR product list and a reduced set of product
distribution interfaces.
– Generally requirements were stated in a manner to be
similar to but not more restrictive than corresponding RPG
requirements. TDWR data are 'complementary' data.
TDWRData PDR
14 October 2004
21
SPG Requirements Overview
Interface Requirements
• External Interfaces
– TDWR
• Based upon the Terminal Doppler Weather Radar (TDWR)
Interface Control Document - NAS-IC-31058603-01
– Product Distribution - limited to AWIPS LAN connection
• Interface Control Document for the RPG to Class 1 User 2620001H
• Interface Control Document for the RPG to Class 2 User 2620007A
• Internal Interface
– TDWR data to be converted to WSR-88D radial data
messages and WSR-88D status messages
TDWRData PDR
14 October 2004
22
SPG Requirements Overview
Functional Requirements
• Data Quality
– Range Unfolding - Only requirement is to identify areas
contaminated with clutter or overlaid echoes
• Data Processing
– Transform TDWR data into WSR-88D radial data messages
& WSR-88D status messages
– Convert azimuth in degrees magnetic to degrees true North
– Handle the hazardous mode scan in such a way that
• AWIPS can step through the two sequences of increasing
elevation angles during product display
• AWIPS can step through the redundant base elevation scans
TDWRData PDR
14 October 2004
23
SPG Requirements Overview
Functional Requirements
• Monitor & Control - Status Information
– TDWR Status Parameters - monitor available parameters:
Average Transmitter power, PRF, Radar Data Output, & TDWR
Mode Operability Status
– SPG Status Monitoring - same as RPG status except no
requirement for printing
TDWRData PDR
14 October 2004
24
SPG Requirements Overview
Functional Requirements
• Monitor & Control - SPG Control
– Startup, Restart, & Controlled shutdown - in addition to no
requirement for radar control, there are no requirements
related to a distributed architecture
– Product Generation Control - no requirements relating to
alert category
– SPG Reconfiguration - manual reconfiguration capability. No
requirements relating to multiple processors / redundant
sites.
NOTE: there are no TDWR control functions including control of
VCP and clutter suppression.
TDWRData PDR
14 October 2004
25
SPG Requirements Overview
Functional Requirements
• Product Generation - All products conform with WSR88D product format IAW the RPG to Class 1 User
ICD and the WSR-88D Product Specification
• Initial Product Suite
– Base Products (truncated to 70,000 feet MSL)
• Reflectivity (16 level RLE & 8-bit to 90 km and 276 km)
• Velocity (16 level RLE & 8-bit to 90 km)
• Spectrum Width (8 level RLE to 90 km)
– Alphanumeric Products - Free Text Message
• Product Storage - Capability identical to the RPG.
TDWRData PDR
14 October 2004
26
SPG Requirements Overview
Functional Requirements
• Product Distribution
– Limited to AWIPS LAN connection
– Class 1 User - RPS list and one-time request capability. No
requirement for alert product distribution.
– Class 2 User - One-time request capability
• Product Archive (Archive III) - no requirement on
SPG
• Archive Level II Data – no operational requirement.
SPG tool exists for logging TDWR data for research
purposes.
TDWRData PDR
14 October 2004
27
SPG Requirements Overview
Functional Requirements
• Adaptation Data & Control - no RDA / PUP related data
• Comm Interface & Control - limited to Class 1 and 2 with
no requirement for dial-up connectivity
• Power Failure Recovery & Overload Control - same as
RPG
• Security Requirements - similar to RPG (differences related
to the subset of interfaces implemented)
TDWRData PDR
14 October 2004
28
SPG Requirements Overview
System Characteristics
• Performance Requirements
– SPG Full Load Definition - reduced product and external
interface set
– Response Time Requirements - only requirements relating to
SPG functions.
• System Configuration
– 1 TDWR base data interface
– Class 1 interface: 1 - minimum, 4 - full load
– Class 2 interface: 4 - minimum, 8 - full load
TDWRData PDR
14 October 2004
29
SPG Requirements Overview
System Characteristics
• Reliability / Maintainability / Availability (RMA)
– same as the RPG
– Total Preventive Maintenance (TPM) factor pertaining to the
SPG has not been established.
• Environmental Conditions - SPG to be operated within an
office environment of an NWS WFO.
TDWRData PDR
14 October 2004
30
SPG Requirements Overview
System Characteristics
• Hardware Design and Construction
– COTS requirements and standards apply
• Software Design
– Portability - POSIX and use of standard languages
– Extensibility - defined API interface for applications
• Data Processing Reserve - same as RPG
• Expandability - same as RPG except no requirements
relating to archive devices, additional communication lines, and
BDDS interfaces.
TDWRData PDR
14 October 2004
31
Preliminary Design – System
Overview – Option A
Direct TDWR Connectivity
TDWRData PDR
14 October 2004
32
Preliminary Design - System
Overview – Option B
FAA Comms Circuit Tap
TDWRData PDR
14 October 2004
33
Prelimnary Design - System
Overview - WFO Configuration
Multiple TDWRs
TDWRData PDR
14 October 2004
34
Preliminary Design – Hardware
Rack Elevations
TDWRData PDR
14 October 2004
35
Preliminary Design – System
Overview – Summary
•
•
•
•
•
•
•
TDWR data flow to WFO is transmit only (UDP).
TDWR data flows to one WFO only.
A WFO may have up to four associated TDWRs
A firewall at WFO protects AWIPS from FAA network.
The SPG processes data for display by AWIPS D2D.
A KVM controls and configures the SPG.
All procured hardware will be consistent with ORPG
and ORDA baseline equipment.
• TDWR to use surplus AWIPS racks.
TDWRData PDR
14 October 2004
36
Preliminary Design – System
Overview – Summary Cont.
• Option A
– BCA and costing based on Option A.
– Pro - Benefit from competitive pricing from communication
carriers.
– Con – NWS equipment is located in FAA shelters. Possible
FAA coordination issues with maintenance.
• Option B
– Costing for Option B is being processed.
– Con – NWS forced to use FAA communications carrier.
– Pro – No NWS equipment located in FAA shelters.
TDWRData PDR
14 October 2004
37
Supplemental Product Generator
Preliminary Design - Software
SPG Software
Development Team
Warren Blanchard (NWS) - Communications
Andy Stern (Mitretek) - Pre-Processor
Ning Shen (RSIS) - Products, Tools
TDWRData PDR
14 October 2004
38
Supplemental Product Generator
Software Overview
• SPG Software
–
–
–
–
Built from CODE ORPG Build 6 Linux system
Implements existing TCP/IP radar product user ICDs
Adds TDWR specific components
Removes/disables unused ORPG components
• AWIPS Software
– Changes minimized by duplicating WSR-88D interfaces
– New radar added by configuration/localization changes
– TDWR specific radar products added as just new radar
products
TDWRData PDR
14 October 2004
39
Supplemental Product Generator
Software Overview
• The Supplemental Product Generator (SPG)
– Processes TDWR base data
– Leverages the ORPG infrastructure for
algorithm/development environment
– Creates and distributes 88D-Like products
• Advantages of this approach:
– Same user capabilities as the WSR-88D
– Maximum reuse of ORPG and AWIPS software
• Reduce the amount of new software to develop
• Reduce risk, cost, schedule and maintenance
• Increase return on investment
– Linux being embraced by AWIPS & ORPG
– ORPG is a proven operational system with a full support
organization
TDWRData PDR
14 October 2004
40
Supplemental Product Generator
System Design
• SPG-specific new software modules
– TDWR communications manager
– TDWR radial data pre-processor
– TDWR product generation algorithms
• Modifications to baseline ORPG
– System & external communications configuration
– Site adaptation data definitions
– TDWR Volume Coverage Patterns (VCP)
– Human Computer Interface (HCI) modifications
• New supporting tools
– Data logging, data pump, data simulator
– Documentation, metrics
TDWRData PDR
14 October 2004
41
Supplemental Product Generator
Communications Manager
The communications manager is a daemon that:
• Receives UDP data packets or command packets
• Controls communications line status & handles exceptions
• Builds a complete TDWR base data radial
• Forwards the completed Data Structure to a Linear Buffer
High Level Data Flow – Communications Manager
TDWR
Comm
Manager
UDP
Data
TDWRData PDR
RESP.1
TDWR Raw
Data LB
14 October 2004
TDWR
Pre-proc.
RESP.0
TDWR Data
Translated to
88D Radial
Messages
Process
Base
Data
42
Supplemental Product Generator
Radial Data Pre-Processor
The radial data pre-processor is a daemon that:
• Receives TDWR radial, status & supplemental messages
• Handles needed administrative functions
– Internal sequence numbers, status messages, QC
•Translates data into complete RDA radial messages
High Level Data Flow – Radial Data Pre-Processor
TDWR
Comm
Manager
UDP
Data
TDWRData PDR
RESP.1
TDWR Raw
Data LB
14 October 2004
TDWR
Pre-proc.
RESP.0
Process
Base
Data
TDWR Data
Translated to
88D Radial
Messages
43
Supplemental Product Generator
Algorithm Generation
The SPG algorithm generation routines:
• Receives 88D-formatted messages from Base Data LB
• Uses the ORPG infrastructure and CODE services
• Controls some VCP fields to enable looping in AWIPS
• Generates ICD-compliant products for Class I users
High Level Data Flow – Algorithm Generation
RESP.0
TDWR Data
Translated to
88D Radial
Messages
TDWRData PDR
PBD
BD LB
Algorithms
Prod LB
Process
Base
Data
Base
Data
LBs
88D-Like
Algorithms
Product
LB
14 October 2004
44
Supplemental Product Generator
SPG Base Products
Task
Input
Output (Product ID)
Trigger
Frequency
Task 10
REFLDATA (79)
Short range 8-bits refl (180)
Start of Elev
Per Elev
Task 10
REFLDATA (79)
Short range 4-bits refl (181)
Start of Elev
Per Elev
Task 10
REFLDATA (79)
Long range 8-bits refl (186)
Start of Vol
Per Vol
Task 10
REFLDATA (79)
Long range 4-bits refl (187)
Start of Vol
Per Vol
Task 11
COMBBASE (96)
Short range 8-bits vel (182)
Start of Elev
Per Elev
Task 11
COMBBASE (96)
Short range 4-bits vel (183)
Start of Elev
Per Elev
Task 12
COMBBASE (96)
Short range 4-bits spw (185)
Start of Elev
Per Elev
TDWRData PDR
14 October 2004
45
Supplemental Product Generator
System & External Comms Config.
• Un-configure extraneous WSR-88D RPG components
with SPG unique versions of configuration files
• Comms_link.conf - reduce number and type of
communications lines & communications managers
to TDWR and TCP/IP users
• Tcp.conf – reduce # of TCM user connections to 16
• User_profiles – reduce classes to class 98 (AWIPS)
and class 2 (OTR)
• Site_info.dea – define site specific configuration,
(MLOS, RMS, BDDS, Archive III, radar name, Lat.,
Long., elevation, etc. of TDWR radar sites)
TDWRData PDR
14 October 2004
46
Supplemental Product Generator
System & External Comms Config.
• Modify configuration files
• Data_tables – remove extraneous data store
definitions; add SPG unique data stores
• Product_generation_tables – remove WSR-88D
specific products; add SPG unique products
• Product_tables – remove WSR-88D product attributes;
add SPG product attributes.
• Task_table – remove WSR-88D specific tasks &
operational processes, extraneous startup & restart
commands; add SPG tasks & operational processes,
SPG specific startup & restart commands
TDWRData PDR
14 October 2004
47
Supplemental Product Generator
Scan Strategies – Monitor Mode
TDWR Monitor Mode
•17 elevations
•Max elev angle 60 deg
•1 long range (refl only)
•Elev 2 & 3–same angle
•Duration ~6 min
TDWRData PDR
14 October 2004
48
Supplemental Product Generator
Monitor Mode Comparisons
TDWRData PDR
14 October 2004
49
Supplemental Product Generator
Monitor Mode (BWI)
SPG
VCP 90
TDWRData PDR
14 October 2004
50
Supplemental Product Generator
Scan Strategies – Hazardous Mode
TDWR Hazardous Mode
•23 elevations
•Max elev angle is
different for almost every
radar
•1 long range (refl only)
•Elev 2 & 3–same angle
•2 redundant patterns/vol.
•Base elev scan each min.
•Duration ~6 min
TDWRData PDR
14 October 2004
51
Supplemental Product Generator
Hazardous Mode Comparisons
TDWRData PDR
14 October 2004
52
Supplemental Product Generator
Hazardous Mode (BWI)
SPG
VCP 80
TDWRData PDR
14 October 2004
53
Supplemental Product Generator
Timestamp Methodology (BWI)
TDWRData PDR
14 October 2004
54
Supplemental Product Generator
SPG HCI Capability Modifications
• Add “button insensitive” calls to HCI control module
to:
– Disable RDA Control selection
– Disable Clutter Regions Editor.
– Disable Bypass Map Editor.
– Disable PRF Selection.
– Disable RDA Performance Data Display.
– Disable Environmental Data Editor.
TDWRData PDR
14 October 2004
55
Supplemental Product Generator
Modified SPG HCI
TDWRData PDR
14 October 2004
56
Supplemental Product Generator
SPG HCI Capability Modifications
• Base Data Display, Console Messages, & HCI Properties
unchanged.
• Add “non-selective” flags to HCI controls to:
– Disable Precip Cat:, VAD Update:, Auto PRF: Calib:, Load
Shed:, & RDA Messages: switches.
• Add “button insensitive” calls to HCI products button to:
– Disable RPG Products - Adaptation Data: Alert/Threshold,
Selectable Parameters & Algorithms selection.
– Generation List, Load Shed Products, & Products in Database
displays contain SPG product IDs only.
• RDA/RPG Interface Control/Status set to Disconnected.
• Add TDWR line Control/Status.
TDWRData PDR
14 October 2004
57
Supplemental Product Generator
SPG System Tools
• Data Logger – allows for logging all base data for 3
days
• Data Metrics Analyzer – performs analysis of product
transmission and data sizes
• Linear Buffer Data Pump – allows for playback of
logged data
• CVG (Codeview Graphics) – modified to decode and
display all TDWR base products
• Test Pattern Simulator – allows for specific test patterns
to be placed into the ingest linear buffer for diagnostic
testing
TDWRData PDR
14 October 2004
58
Supplemental Product Generator
SPG Product Size Statistics
Product ID
Size Range (Bytes)
VCPs
180
31918 - 109172
80 & 90 mixed
181
4482 - 38772
80 & 90 mixed
182
61520 - 216028
80 & 90 mixed
183
8724 - 115274
80 & 90 mixed
185
9068 - 140490
80 & 90 mixed
186
168376
80 & 90 mixed
187
14450 - 49318
80 & 90 mixed
Note: The statistics were collected Sept. 17 to Sept 20, 2004 for the
BWI TDWR. The products were not compressed.
TDWRData PDR
14 October 2004
59
Supplemental Product Generator
SPG Test Pattern Simulator
The black ring
represents No
Data beginning
at 32.1 KM.
These edges are
at 90 and 180
degree before
the magnetic
north adjustment
Short range
8-bit reflectivity
Product (180)
at 0.5 degree
elevation
TDWRData PDR
14 October 2004
60
Supplemental Product Generator
Base Product Example using CVG
4-bit Reflectivity
48 NM Range
150 m resolution
TDWRData PDR
14 October 2004
61
Supplemental Product Generator
Distribution of SPG Products
• Since base elevation scans repeat during
hazardous mode, a new routine request feature
provides all scans of a specific elevation angle
• Products provided using conventional WSR-88D
Class 98 routine and one-time product requests
• Products will be available via AWIPS WAN-based
Class 2 one-time request
• The General Status Message will provide the user
both SPG and TDWR status
TDWRData PDR
14 October 2004
62
AWIPS OB5 SPG Software
Overview
• Connect to SPG with existing LAN ORPG TCP/IP
communications software.
• Use standard AWIPS D2D RPS List, RMR(OB6),
Routine and One-Time Request tools to request
products.
• Use standard D2D tools to display, loop & manipulate
SPG products & general status display.
• Support multi-radar mosaic(WSR-88D & SPG TDWR).
• Use SPG products within AWIPS integration processes
such as SCAN & WES.
TDWRData PDR
14 October 2004
63
AWIPS OB5 SPG Configuration Changes
• Add TDWR radar site information for radar files.
• Add TDWR radar IDs (3001-3005) & ICAOs. (Txxx,
e.g. TBWI)
• Add SPG network addresses & ports for
communications managers.
• Add SPG base products & product IDs for data base,
RPS & OTR product requests.
• Add TDWR unique elevation angles to lists for OTR
and RPS D2D applications & menus.
TDWRData PDR
14 October 2004
64
AWIPS OB5 SPG Software Modifications
• Modify D2D to support TDWR reflectivity product
spatial resolution of 300 m for long range & 150 m
short range.
• Present only local SPG TDWR VCP angles in GUI
menus for OTR, RMR(OB6), RPS & display
selection.
• Modify RPS list & list editor to support “all scans”
request feature.
• Modify D2D to support TDWR general status
message.
TDWRData PDR
14 October 2004
65
AWIPS D2D TDWR
Product Display Example
TDWRData PDR
14 October 2004
66
Supplemental Product Generator
Security
• Security Documentation
– Based on WSR-88D security documentation.
– Required certification and accreditation process:
• National Information Assurance Certification and Accreditation
Process
• National Security Telecommunications and Information
Systems Security Instruction.
–
–
–
–
Identify required security.
Develop System Security Authorization Agreement (ITSO).
Memorandum of Agreement (FAA).
Interconnection Security Agreements (FAA, AWIPS).
TDWRData PDR
14 October 2004
67
Supplemental Product Generator
System Security
• Security Implementation Detail
– Leverage ORPG security test plans & procedures.
– TDWR connectivity at physical level is receive
only.
– Firewall appliance between SPG and TDWR.
– Harris Scan vulnerability patches for OS.
– OS firewall configuration.
– Standard service TCP wrappers & filters.
– ORPG TCM log-on authorization & exclusive port
access.
TDWRData PDR
14 October 2004
68
Test Phases for TDWR Data
•
•
•
•
•
Integration Testing
AWIPS OB5 SWIT
SPG System Test
SPG Operations Test
Beta Test (OAT)
TDWRData PDR
14 October 2004
69
SPG and AWIPS OB5 Schedule
TDWRData PDR
14 October 2004
70
Integration Testing
• Environment - NPI development lab 12349
– SPG (spg2 & 8) and AWIPS-lite (orpg22) integration platforms
• Objectives
–
–
–
–
–
–
Establish full thread live data for evaluation
Debug SPG and D2D software
Analyze TDWR data flow exceptions
Evaluate SPG and D2D stability
Provide products to FSL and OHD
Measure products sizes to validate load estimates
• Validate test tools
– Base data logging and data pump
– Product size statistics
– TDWR data simulator
TDWRData PDR
14 October 2004
71
AWIPS OB5 SWIT
• Environment – NMT SPG (nhqd) & NGIT OB5
– NMT SPG w/product distribution interface to NGIT
• Objectives – OB5 and Interoperability w/SPG
–
–
–
–
–
–
–
–
Configuration of TDWR radar site and VCP angles
RPS and OTR product requests
Single site and mosaic with WSR-88D displays
Spatial registration, moment presentation, sampling
Time loops, All-tilts, 8bit-SRM, VR shear
GSM, PRM, and PLM
SPG unit status and alarms
Archive and WES ingest
TDWRData PDR
14 October 2004
72
SPG System Test
• Environment – NMT SPG and NHDA OB5
– First article SPG and baseline AWIPS platforms
• Objectives – SPG and performance tests
– TDWR site and VCP configuration
– State transitions
• Power fail recovery, startup/shutdown/restart, communications
– Functionality
• SPG status & control, TDWR data & interface status, HCI, TDWR data
translation, product generation, exception processing
–
–
–
–
–
Expanded communications configurations
System security and access control
Validate TDWR/SPG and SPG/AWIPS Interfaces
Combined SPG and AWIPS Performance Test
Stability
TDWRData PDR
14 October 2004
73
SPG Operations Test
• Environment – NMT SPG and NHDA
– First article SPG and baseline AWIPS platforms
• Objectives
– In-house validation of beta test (OAT) plans and
procedures
TDWRData PDR
14 October 2004
74
Beta Test - OAT
• Environment – Operational systems
– Candidate sites: LWX(bwi), SLC(slc), OUN(okc), LOT(ord).
Alternates: PSR(phx), VEF(las), GSP(clt)
– Constraints: OB5 sites with T1 communications to TDWR
• Objectives
–
–
–
–
–
–
–
–
Verify deployment procedures
Verify SPG and AWIPS configurable data is correct
Verify basic functionality is behaving as expected
Verify operator training materials are satisfactory
Verify operator and maintenance documentation is satisfactory
Verify overall stability of the SPG and communications
Verify AWIPS local archive of TDWR data functions properly
Verify that site personnel find the SPG and AWIPS perform
satisfactorily for conducting their normal operational mission.
TDWRData PDR
14 October 2004
75
Acquisition/Procurement
Planning
• Communications Leasing
– TDWR MOA with FAA before any new links
ordered
– 1-4 month lead time (risk)
– CIO14
• Hardware Procurement
–
–
–
–
Prototype/kit development
CD-435 purchase all servers to ensure identical
CD-435 purchase firewalls, routers, rack equip.
OS&T
TDWRData PDR
14 October 2004
76
Deployment Planning
• Resolve floor space question
• Kit development – SEC/Contr.
– Instruction development
• Deployment Schedule – SEC/Contr.
– AWIPS DX/OB5 tie-in
– Funding
• Deployment – SEC/Contr./SET
–
–
–
–
Kit shipping
Mod note
On-site installation/testing
Site sign-off
TDWRData PDR
14 October 2004
77
Support Planning - Training
•
•
•
•
Forecaster training - WDTB
NRC personnel training
NWSTC personnel training
Hot Line/NCF training
TDWRData PDR
14 October 2004
78
Support Planning - O&M
• Maintenance concept will be developed
• Support Systems
–
–
–
–
–
–
–
–
–
NWSTC (National Weather Service Training Center)
NGIT (Northrop Grumman IT)
NWSHQ (12th floor)
AWIPS Test Bed (NWSHQ 7th floor)
FSL (Forecast Systems Lab)
ROC (KCRI, KJIM, KREX, test beds)
WDTB (Warning Decision Training Branch)
NRC (National Reconditioning Center)
OHD (Office of Hydrologic Development)
TDWRData PDR
14 October 2004
79
Responsibility Transfer
Planning
• PMRT Plan will be developed
• Transition to NEXRAD O&M near the end of
deployment (October 2006)
–
–
–
–
Transfer test bed
Provide data logging & playback capability
Drawings & other documents in proper format
Managed by Program Management Responsibility
Transfer plan
– Out year funding provided by NWS
TDWRData PDR
14 October 2004
80
Supplemental Product
Generator
PMRT Delivered Documentation
• Requirements
– Supplemental Product Generator System Specification
• Design & Development
–
–
–
–
–
TDWR Engineering Specification
TDWR Interface Control Document
TDWR Product Specification ICDs
Software Design Description Document
Software Entities
• Sources, makefiles, scripts, man pages, etc.
– Test Procedures, Data, Reports
• Technical Manuals
• Drawings
• Testing
TDWRData PDR
14 October 2004
81
Next Steps
• Critical Design Review
– Currently scheduled for week of 15 November
2004
TDWRData PDR
14 October 2004
82