Transcript Document

Aviation Weather
Right Sizing 7/14/10
Bi-weekly
Presented to: Right Sizing Team
By: Ken Hamm, AJP-6830
Aviation Weather Office
Date: July 14, 2010
v0.1
Federal Aviation
Administration
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
Right Sizing Bi-Weekly – v0.1
July 14, 2010
Federal Aviation
Administration
2
Templates Used
Type of Product
Preliminary ACAT Determination
Request
A
CRD Plan
B
Shortfall Analysis Report
C
Service Analysis Approval Matrix
H
CRD Approval Matrix
I
Concept of Operations
K
Concept of Use
L
Right Sizing Bi-Weekly – v0.1
July 14, 2010
Appendix
Federal Aviation
Administration
3
Acronyms Used
Acronym
Full Name
ACAT
Acquisition Category
AMS
Acquisition Management System
CONOPS
Concept of Operations
CONUSE
Concept of Use
CRD
Concept and Requirements Definition
CRDR
Concept and Requirements Definition Readiness Decision
EA
Enterprise Architecture
IARD
Investment Analysis Readiness Decision
pPR
preliminary Program Requirements
Right Sizing Bi-Weekly – v0.1
July 14, 2010
Federal Aviation
Administration
4
Acquisition Management System
Fig. 3: p. 4 of 79
Right Sizing Bi-Weekly – v0.1
July 14, 2010
Federal Aviation
Administration
5
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
Right Sizing Bi-Weekly – v0.1
July 14, 2010
Federal Aviation
Administration
6
Service Analysis Phase
Fig. 4: p. 5 of 79
Right Sizing Bi-Weekly – v0.1
July 14, 2010
Federal Aviation
Administration
7
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.
Right Sizing Bi-Weekly – v0.1
July 14, 2010
Federal Aviation
Administration
8
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
Right Sizing Bi-Weekly – v0.1
July 14, 2010
Federal Aviation
Administration
9
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.
Required Product
Description
Needed Service or Capability
Identifies the new or updated capability
required to meet FAA strategic
objectives
Legacy Case Definition
Identifies existing operational and
technical environment and planned
near-term capability
Preliminary Shortfall
Detailed description of shortfall
Concept of Operations
Describes what initiative will do from a
physical or operational perspective
Right Sizing Bi-Weekly – v0.1
July 14, 2010
Federal Aviation
Administration
10
Service Analysis: Preliminary ACAT
Determination Request
Right Sizing Bi-Weekly – v0.1
July 14, 2010
Federal Aviation
Administration
11
Service Analysis: Preliminary ACAT
Determination Request (cont’d)
Right Sizing Bi-Weekly – v0.1
July 14, 2010
Federal Aviation
Administration
12
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
Right Sizing Bi-Weekly – v0.1
July 14, 2010
Federal Aviation
Administration
13
Service Analysis: CRD Plan
Deliverable
Activity
Responsible
Agent
Reviewing
Agents
Review
Period
Target Date
Develop
Concept(s) of
Use
Develop
Functional
Analysis
Quantify
Shortfall
Develop EA
Products and
Amendments
Right Sizing Bi-Weekly – v0.1
July 14, 2010
Federal Aviation
Administration
14
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)
Right Sizing Bi-Weekly – v0.1
July 14, 2010
Federal Aviation
Administration
15
Service Analysis and CRD Products
Right Sizing Bi-Weekly – v0.1
July 14, 2010
Federal Aviation
Administration
16
CRD Process
Right Sizing Bi-Weekly – v0.1
July 14, 2010
Federal Aviation
Administration
17
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.
Right Sizing Bi-Weekly – v0.1
July 14, 2010
Federal Aviation
Administration
18
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
Right Sizing Bi-Weekly – v0.1
July 14, 2010
Federal Aviation
Administration
19
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.
Right Sizing Bi-Weekly – v0.1
July 14, 2010
Federal Aviation
Administration
20
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
Right Sizing Bi-Weekly – v0.1
July 14, 2010
Federal Aviation
Administration
21
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
Right Sizing Bi-Weekly – v0.1
July 14, 2010
Federal Aviation
Administration
22
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
Right Sizing Bi-Weekly – v0.1
July 14, 2010
Federal Aviation
Administration
23
Functional Analysis: More Diagrams
Diagram Showing Functional Decomposition
Fig 4.4-21 : System Engineering Manual
Right Sizing Bi-Weekly – v0.1
July 14, 2010
Functional Flow Block Diagram
Fig 4.4-23 : System Engineering Manual
Federal Aviation
Administration
24
Backup Slides
Right Sizing Bi-Weekly – v0.1
July 14, 2010
Federal Aviation
Administration
25
Motivation (cont’d)
Service Analysis Phase
CRD 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
• 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
Right Sizing Bi-Weekly – v0.1
July 14, 2010
Federal Aviation
Administration
26
Weather Sensor Roadmap (1 of 2)
2009
Wind Shear Det Svc
Portfolio
2010
IARD
37
2011
IID
443
2012
2013
2014
FID
444
IARD
WSP
IARD TR
407
2015
407 LLWAS
TR
(with LIDAR & LLWAS)
FAA Sensors
Wind Shear Service
CY
CY
ASR-WSP
ASR-WSP
WSP TR1
TDWR
TDWR
TDWR SLEP 1
IID
77
IID
77
2/3
IARD TDWR
407
2016
SLEP 2 IID
2017
FID
104
77
FID
104
IARD
407
IID
77
FID
104
ASR-11
WX Channel
IARD
407
IID
77
FID
104
IARD
407
IID
77
FID
104
NEXRAD Product
Improvement & Dual Pol
2019
2020
FID
104
ASR-8/9
WX Channel
NEXRAD
2018
2021
2022
2023
2024
2025
X
Wind Shear
Solutions
X
X
TDWR SLEP 3
NextGen Surveillance & Weather ISD
Radar Capability
408
X
X
Surface Weather
Observing Service
NextGen RWI Solution Set
ASWON Portfolio
AWOS
AWSS
ASOS
ASWON
IARD
85
ASWON TR 26
TR
IID
FID
445
446
NextGen
Surface Observing Capability
ISD
447
SAWS, DASI, F420
Alaskan Wx Cameras
Surface Weather Observing Solutions
Non-Fed
Non FAA
Sensors
AWOS
ACFT Wx
93
Sensors
PIREPS
Lightning
Data
Supporting
Activities
Auto PIREP
Entry ERAM
43
49
Evaluate Multi-Function Phased Array Radar
Technology (MPAR)
Develop Inter-Agency Requirements
for Air Domain Surveillance
NextGen RWI Solution Set
481
IARD
407
Wx Right Sizing study for NextGen
Observing Capabilities (AJT & AJP)
Right Sizing Bi-Weekly – v0.1
July 14, 2010
IARD
407
93
Federal Aviation
Administration
27