1. Friends / Partners in Aviation Weather
October 8, 2008
Process Improvements
Paul Fiduccia, Facilitator

2. Changes From 2002 FPAW Format Changes More time for discussion:
Observations: 1 hr >> 1 hr 25 min
Product Generation: 1 hr >> 1 hr 50 min
Ground-Based Dissemination: 1 hr >> 1 hr 5 min
Cockpit-Based Dissemination: 1 hr >> 1 hr 10 minutes
User Issues:
User Issues developed & submitted to Providers further in advance of the meeting to help focus presentations.
User Issues allocated to each Segment, with a short initial segment on Over-Arching Issues and Action Items

3. Action Item Process
Compile requested Action Items in writing during panel discussions: What-Who-When
Submit to Executive Committee:
Segment 1 – 3 items at end of Segment 3
Segment 4 – 5 items at end of Segment 5
Development of Action Items in Segment 6; Part of Conclusions and Recommendations

4. Friends / Partners in Aviation Weather
User Issues
Overview and Over-Arching Issues
Paul Fiduccia, SAMA

5. Criteria For Coordinated User Issues
Important – A high priority user need of many members of an association
Broad-based – important to multiple associations and segments of civil aviation
High-level – An issue appropriate for senior FAA, NWS, and NASA managers
Strategic – Typically 1 year for completion

6. FPAW 2003 User Panel Associations Agencies Airlines Unions Others: ADF
AOPA
AOPA/ASF
ATA
SAMA
Agencies
DOD
FAA (FSSs)
NASA Ames
Airlines
Continental
Northwest
Southwest
United
Unions
ALPA
NAATS
NATCA
Others:
WeatherNews
Global Insurance

7. Over-Arching User Issues
User-Driven aviation weather requirements process.
Systems Engineering Type Approach to aviation weather products development: Users – What; Developers – How.
Coordinated development of “suites” of products for each type of user and weather phenomena.
Real user inclusion in AWTT – semi-annual consultative meetings have proven inadequate.
FAA, NWS, airlines and GA group to make recommendations, provide technical input, and work on Conuses for all initiatives.