Aviation Weather - PowerPoint PPT Presentation

aviation weather n.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
Aviation Weather PowerPoint Presentation
Download Presentation
Aviation Weather

play fullscreen
1 / 27
Aviation Weather
100 Views
Download Presentation
mandar
Download Presentation

Aviation Weather

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. Aviation Weather Right Sizing 7/14/10 Bi-weekly

  2. Agenda • Introduction to FAA AMS • Requirements for SA phase  CRDR • Requirements for CRD phase  IARD • Application of ASWON and WSDS Deliverables: • ESRL • Indiana U. • MIT/Lincoln Lab • NCAR • NSSL • U. of Oklahoma

  3. Templates Used

  4. Acronyms Used

  5. Acquisition Management System Fig. 3: p. 4 of 79

  6. Motivation All FAA investment initiatives must go through a Service Analysis (SA) and CRD process. During SA and CRD, the service organization must build a legitimate and compelling case that shows how a proposed initiative fulfills an FAA service need In both SA and CRD, a set of products will be developed by the service organization that act as both milestones for progressing through the AMS lifecycle and as building blocks for creating a sound acquisition case. from p. 2 of 79

  7. Service Analysis Phase Fig. 4: p. 5 of 79

  8. Requirements: Service Analysis • Inclusion in EA Roadmap • The roadmap effort is currently in progress. • Concept of Operations (CONOPS) • CONOPS is both a stand-alone document and a sub-section within the Shortfall Analysis Report. • Shortfall Analysis Report (App. C) • This report re-states the problem being addressed by the initiative, identifies the severity of the problem, and explains the methods used to generate the shortfall estimate. • Preliminary ACAT Determination Request (App. A) • Acquisition Category (ACAT) classifies project based on dollar thresholds and appropriate qualitative factors. • The assigned ACAT Level determines the future governance of the program. • Approved CRD Plan (App. B) • The CRD plan outlines the approach the service organization will employ to complete the CRD phase of AMS.

  9. Service Analysis: Concept of Operations • The CONOPS document includes the following sections (App. K): • Executive Summary • Description of Operational Need • Service or System Justification (Description of Desired Change) • Proposed Service or System • Operational Scenarios • Impacts • References • Appendices

  10. Service Analysis: Shortfall Analysis Report • This report re-states the problem being addressed by the initiative, identifies the severity of the problem, and explains the methods used to generate the shortfall estimate. • It contains, but is not limited to, the following products.

  11. Service Analysis: Preliminary ACAT Determination Request

  12. Service Analysis: Preliminary ACAT Determination Request (cont’d)

  13. Service Analysis: CRD Plan The CRD Plan is the document that outlines the approach the service organization will employ to complete the CRD phase. Its purposes are: • Ensure agreement among all organizations providing CRD resources • Define products to be completed during the CRD phase • Establish a milestone schedule for the CRD effort

  14. Service Analysis: CRD Plan

  15. CRD Plan: Other Deliverable Activities • Conduct Safety Risk Management • Develop Preliminary Requirements (pPR) • Develop Range of Alternatives • Estimate Costs and Benefits • Create Investment Analysis Plan (IAP) • Finalize ACAT Designation Request • Prepare for Investment Analysis Readiness Decision (IARD)

  16. Service Analysis and CRD Products

  17. CRD Process

  18. CRD Phase: Concept of Use (CONUSE) • The CONUSE document is an expansion of the CONOPS: • Focus is on the user (i.e. user’s language, needs, expectations, etc.) • It describes specifically how users will employ the proposed capabilities and how they will function in the operating environment (secondary focus) • The CONUSE will be used as a foundation for performing the functional analysis and, in turn, developing the preliminary Program Requirements.

  19. CRD Phase: Concept of Use • The CONUSE document includes the following sections (App. L): • Background Information (including References) • Description of Operational Need • Service or System Justification • Proposed Service or System • Operational Scenarios • Description of Impacts • Appendices

  20. CRD Phase: Functional Analysis • The Functional Analysis product takes stakeholder needs and translates them into the functions required to satisfy the need. • Higher-level functions are decomposed into sequentially lower-level sub-functions. • A function is defined as a characteristic action or activity that needs to be performed to achieve the desired service. • Stakeholder needs are derived from the Needed Services product, the Preliminary Shortfall product, the CONOPS, and the NAS System Requirements document (SR-1000). • During Functional Analysis, focus is on what the new service will do, not how the service will be performed.

  21. CRD Phase: Functional Analysis • Through the process of decomposing and analyzing functions, a description of the system emerges and becomes the framework for developing requirements and physical architectures. • Analysis of the operating environment is also required. • Changes to an environment or multiple operating environments may require defining additional functions. • Required analysis tools: • N2 Diagram • Functional Flow Block Diagram

  22. Functional Analysis: Generic N2 Diagram • N is the number of entities • Functional or physical entities are placed on the diagonal axis • The remaining squares of N x N matrix represent the interface inputs and outputs Fig 4.7-5 : System Engineering Manual

  23. Functional Analysis: Example N2 Diagram • Blank square indicates no interface between respective functions • An ‘X’ placed in square corresponding to Row I, Column J indicates data flow from function I to function J. Fig 4.7-6 : System Engineering Manual

  24. Functional Analysis: More Diagrams Functional Flow Block Diagram Diagram Showing Functional Decomposition Fig 4.4-21 : System Engineering Manual Fig 4.4-23 : System Engineering Manual

  25. Backup Slides

  26. Service Analysis Phase Identify and define future service needs Document service needs on approved EA roadmap Clearly describe the nature, urgency, and impact of the problem Ends with a CRDR, marking transition to CRD Phase CRD Phase Define and validate any shortfalls or service gaps Identify requirements on a functional level Ensure that the investment initiative aligns with FAA strategic goals and objectives Identify different viable alternatives Ends with an IARD, marking transition to Investment Analysis Phase Motivation (cont’d)

  27. Weather Sensor Roadmap (1 of 2) CY CY 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 2025 IARD 37 FID 444 IID 443 IARD 407 FID 104 Wind Shear Det Svc Portfolio (with LIDAR & LLWAS) LLWAS TR IID 77 X Wind Shear Solutions ASR-WSP WSP TR1 WSP TR 2/3 IARD 407 IID 77 FID 104 X Wind Shear Service ASR-WSP TDWR IID 77 TDWR X TDWR SLEP 2 TDWR SLEP 1 TDWR SLEP 3 IARD 407 FID 104 ASR-8/9 WX Channel NextGen Surveillance & Weather Radar Capability IID 77 IARD 407 FID 104 ISD 408 FAASensors IID 77 FID 104 ASR-11 WX Channel X IARD 407 FID 104 IID 77 IARD 407 NEXRAD Product Improvement & Dual Pol NEXRAD X NextGen RWI Solution Set ASWON Portfolio AWOS AWSS ASOS Surface Weather Observing Service ASWON TR NextGen Surface Observing Capability FID 446 ISD 447 IARD 85 IID 445 26 ASWON TR SAWS, DASI, F420 Alaskan Wx Cameras Surface Weather Observing Solutions Non FAA Sensors Non-Fed AWOS 93 ACFT Wx Sensors 43 Auto PIREP Entry ERAM PIREPS NextGen RWI Solution Set 481 49 Lightning Data Supporting Activities Evaluate Multi-Function Phased Array Radar Technology (MPAR) IARD 407 Develop Inter-Agency Requirements for Air Domain Surveillance IARD 407 93 Wx Right Sizing study for NextGen Observing Capabilities (AJT & AJP)