Presented to Friends & Partners of Aviation Weather

1. Presented toFriends & Partners of Aviation Weather Rick Heuwinkel, ARS-100 October 8, 2003 AWTT PROCESS UPDATE

2. Outline • Users’ Concerns Re: Input to FAA Requirements Process • Map of Current User Input Points • AWTT Role • Approaches to Solutions • Roadmap • Input from Expert Users S:\1ARS100\Admin\OrgMgtProcess\AWTT\FPAW03\3AWTTupdateFPAW03v1.0.ppt

3. Requirements Process: Common Complaints • Present development process yields a patchwork of multiple, overlapping, and potentially inconsistent products • Products are introduced without consideration of regulatory impact • Providers define WHAT products are required and HOW they will look and then ask users to approve after it is too late to make changes S:\1ARS100\Admin\OrgMgtProcess\AWTT\FPAW03\3AWTTupdateFPAW03v1.0.ppt

4. Low Cost Moderate Cost Expert Input Oversight User Input to Aviation Weather Requirements ATA MetCom CAST JSC AWTT User Meetings RTCA Ad hoc (e.g., GFA) ICAO IATA Ad hoc meeting with associations FAA Direct written or voiced complaints from users FPAW MNS & Requirements AWRP PDT user teams System development teams: TDWR LLWAS ITWS CWIS UNAs CDM Wx Apps Team S:\1ARS100\Admin\OrgMgtProcess\AWTT\FPAW03\3AWTTupdateFPAW03v1.0.ppt

5. User Input Summary • Numerous groups have input to requirements, overall investment is substantial • Same representatives serve on many groups, individual commitment is substantial • Some groups provide needed oversight on a broad range of issues • Other groups provide technical expertise on design of specific products • Both types of involvement are needed and can’t be done by same group S:\1ARS100\Admin\OrgMgtProcess\AWTT\FPAW03\3AWTTupdateFPAW03v1.0.ppt

6. AWTT Flow Chart • D1 • User Needs Analysis • Initial concept of use • (ConUse) • D2 • User Needs Analysis (refined) • ConUse (refined) • D3 • Initial ConUse approval • AVR approvals or approval • plans in place • Initial approval of requirements • Enter AMS Process, if needed • D4 • Final ConUse approval • Final AVR approvals in place • Final approval of requirements • AMS Process, if needed, completed Operational Platforms Release product for operational use by selected users (AWTT Board decision) Data/Product for users Sponsorship of Users’ Needs R&D and Controlled Testing Experimental Application D1 D2 D3 D4 Assign new needs (ARS-20 coordinate ATS/AVR/NWS decision) Select/fund R&D projects to support needs (ARS-20 coordinate ATS/AVR/NWS decision) Release product for testing under FAA test plan (e.g., display on ADDS) (AWTT Board decision) ASG Decision S:\1ARS100\Admin\OrgMgtProcess\AWTT\FPAW03\3AWTTupdateFPAW03v1.0.ppt Optional Path

7. Contents of UNA & ConUse • Identify users (decision makers) • Document operational decisions requiring weather information • Describe ideal information needed to support operational decisions • Specify performance metrics (how good is good enough?) • Identify needed Rule/guidance changes • Describe needed user training • Define needed access architecture (ConUse only) S:\1ARS100\Admin\OrgMgtProcess\AWTT\FPAW03\3AWTTupdateFPAW03v1.0.ppt

8. Approaches to Solution • Systemic: Develop a roadmap to address to show plan to reduce product proliferation and manage unintended regulatory impact • Product Specific: Obtain more effective input from user experts on individual product design S:\1ARS100\Admin\OrgMgtProcess\AWTT\FPAW03\3AWTTupdateFPAW03v1.0.ppt

9. Roadmap • Shows migration path from existing products to new product suite: • Identifies product mergers and replacements • Done for each weather category and user class • Identifies regulatory impacts & develop plan for rule/guidance change, domestic & international • Identifies priorities for supporting research S:\1ARS100\Admin\OrgMgtProcess\AWTT\FPAW03\3AWTTupdateFPAW03v1.0.ppt

10. Roadmap Production • FAA/NWS draft Roadmap based on: • Mission Needs Statements • Current UNA & ConUse documents • Current research plans • AWTT Users Group review and comment • Iterate as needed S:\1ARS100\Admin\OrgMgtProcess\AWTT\FPAW03\3AWTTupdateFPAW03v1.0.ppt

11. Enhance Input from Expert User Teams for Product Design • Document/validate results from ongoing expert user teams • Document early in ConUse & update frequently • Publish ConUse early & employ systematic review • Enhance expert user teams • Employ Users Needs Analyses before R&D • Selectively add user teams during R&D & document results in ConUse for systematic review • Enhance AWTT User Meetings for oversight • Systematic web review of UNA/ConUse documents • Double meeting frequency to quarterly? S:\1ARS100\Admin\OrgMgtProcess\AWTT\FPAW03\3AWTTupdateFPAW03v1.0.ppt

12. Constraints • User input processes must adhere to Federal Advisory Committee Act and Administrative Procedures Act • Increased PBO emphasis on measured performance improvement • Reduction in accidents • Increased capacity & efficiency • Limited time & travel resources for requirements processes, both sides S:\1ARS100\Admin\OrgMgtProcess\AWTT\FPAW03\3AWTTupdateFPAW03v1.0.ppt

13. Summary • To improve requirements, FAA will develop, with user input: • A roadmap showing migration to fewer but better product suites with fewer unintended regulatory constraints • Improved users technical input to product design. • Both managed thru enhanced AWTT users meetings S:\1ARS100\Admin\OrgMgtProcess\AWTT\FPAW03\3AWTTupdateFPAW03v1.0.ppt