Project Types and Workflow - Federal Aviation Administration · 2 3 Federal Aviation Administration...
Transcript of Project Types and Workflow - Federal Aviation Administration · 2 3 Federal Aviation Administration...
1
1 Federal AviationAdministration
Regional Workshop - AAL
Oct 19-20, 2011
Project Types and Workflow
Airports GIS
Presented to | FAA Regions | Alaskan
By | Gil Neumann, APP-400 | Thomas Wade, ASW-611
Date | October 19-20, 2011
2 Federal AviationAdministration
Regional Workshop - AAL
Oct 19-20, 2011
Agenda
Robust Data Collection – “eALP”(10 min)
Runway Extension/NewRunway with New InstrumentApproach Procedures (10)
No Safety Critical Data -Apron/Taxiway (5)
Establish Geodetic Control (5)
Other – Land Acquisition,Boundary Survey, Noise,Planned Development (5)
2
3 Federal AviationAdministration
Regional Workshop - AAL
Oct 19-20, 2011
Robust Data Collection (eg., eALP project) Critically evaluate features and attributes to include in project
Some attributes, for non safety-critical features, may be omittedfrom original project, then collected during a future initiative
Evaluate which runways need AS/AAA to support IAPdevelopment in the near term (5-7 years)
Consider 65 DNL contour and limits of noise program
Two Airports GIS projects:
‣ Airport Airspace Analysis: VG (data includes all existing data)
‣ Airport Layout Plan: airport design or planning (planning &design data)
SOW, Plan(s), NGS review and approval
If “Triggering Event,” the airport must incorporate contractrequirements and processes for upcoming projects to ensureAirports GIS deliverables
4 Federal AviationAdministration
Regional Workshop - AAL
Oct 19-20, 2011
Robust Data Collection Project | Getting Started
Consultant Selection
‣ Reference APP-1/AAS-1 working guidance: 06/24/2010-Attachment A
Scoping Meeting with airport/consultant team/FAA
‣ Working guidance, Attachment B
‣ Scoping meeting guide/agenda (handout)
Negotiate scope/fee and issue NTP
Create two Airports GIS “Survey” projects
‣ Project 1 | New Survey: Obstruction Survey (or similar)
‣ Project 2 | Planned and Design Data (ALP, eALP)
SOW (Project 1)‣ Develop, Submit, and Approve (FAA | Region/HQ (Contractor))
Plans‣ Develop and Submit for NGS Review and approval
3
5 Federal AviationAdministration
Regional Workshop - AAL
Oct 19-20, 2011
6 Federal AviationAdministration
Regional Workshop - AAL
Oct 19-20, 2011
Creation of an electronic ALP (current) in Airports GIS
Create
Project
Upload
Planning Data
Data
Acceptance
Assemble
eALP
Electronic ALP
“Survey” Projects Create eALP
“Project”
eALP Projects
Upload
Data
Create ALP
Project
Aeronautical Survey (s)
Planning/ALP Update (s)Data Sets
4
7 Federal AviationAdministration
Regional Workshop - AAL
Oct 19-20, 2011
New instrument approach with runway extension
Timing: usually must collect imagerybefore extension/new runway is in place
Recommend collecting low-level (high-resolution) imagery for entire airportproperty, not just in runway environment
After Construction: may re-fly runwayflight line (new tiles) for orthoimagery andmay wish to use to extract new features(e.g. lights, marking) rather than usingCADD/survey data
Airports GIS Project Type: AAA/VG
SOW, Plan(s), NGS review and approval
8 Federal AviationAdministration
Regional Workshop - AAL
Oct 19-20, 2011
Workflow - IAP Development with Design Values
FAA/FPO
IAP DesignFAA/NGS
Data
Acceptance
Determine
Design Values
(Runways ends/ CL Profile)
Conduct AAA
Using Design
Values
Submit Data
Status =
Under Construction
Flight Check
and Publish
Survey As-Built
Features
Submit Data
Status = As Built
Design
~
As-Built
Yes
Yes
No
5
9 Federal AviationAdministration
Regional Workshop - AAL
Oct 19-20, 2011
10 Federal AviationAdministration
Regional Workshop - AAL
Oct 19-20, 2011
6
11 Federal AviationAdministration
Regional Workshop - AAL
Oct 19-20, 2011
How to treat obstacles or NAVAIDS shownin the imagery, but scheduled for removalor relocation
Use Status Attribute to differentiate
NAVAID/Obstacle scheduled for removal/relocation
‣ Status = “Temporary”
‣ Recommend additional information in UserFlag
After Removal
‣ Status = “Demolished”
‣ Provide Documentation
12 Federal AviationAdministration
Regional Workshop - AAL
Oct 19-20, 2011
7
13 Federal AviationAdministration
Regional Workshop - AAL
Oct 19-20, 2011
Instrument Approach Procedure Development –Survey and Data Approval Timeline
Develop Scope,Select Consultant &
Negotiate Fee
Prepare SOW, Survey& QC Plans
NGS DataReview &
Acceptance
Conduct Aeronautical Survey &Airport Airspace Analysis
NT
P1 - 3 Months
FA
AS
OW
Ap
pro
va
l
Wait to Fly –Full Foliage,
Weather,SatelliteVisibility
Procedure Development/Publication
NG
SIm
ag
ery
Pla
nA
pp
rova
l
NG
SD
ata
Ap
pro
va
l
Co
lle
ct
Ima
ge
ry
?? 6 - 8 Months2 - 4
Months
Airport Development Office Support
Fin
al
Re
po
rt&
Da
taU
plo
ad
Minimum Time 10-12 Months Maximum Time 18-24 Months
Regional-610 (Planning) Support Regional-620 (Procedure Coordination) Support
Fli
gh
tC
he
ck
Va
lid
ate
De
sig
nD
ata
Su
bm
itta
l
NG
SD
ata
Ap
pro
va
l
Pu
bli
sh
Ap
pro
ach
Pro
ce
du
re
Data Available for use by ATO and Others
10 - 12 Months
NG
SS
urv
ey
&Q
CP
lan
Ap
pro
va
l
Ima
ge
ryS
ub
mit
tal
NG
SIm
ag
ery
Ap
pro
va
l
> 65days
AirportConsultant TeamMother NatureNGSFAA
- Activity
- Submittal, Action or Approval
1 - 4 Months
Re
qu
est
Pro
ce
du
reD
eve
lop
me
nt
14 Federal AviationAdministration
Regional Workshop - AAL
Oct 19-20, 2011
No Safety-Critical data project (new taxiway/apron)
Determine how Airports GIS Will be incorporated into both design andconstruction phases of project.
Determine who is responsible to QC and upload Airports GIS data
Planned Major Feature (RW/TW) should be in Airports GIS with statuscode as near-term, eventually feature will be refined and status changedduring airspace and or SMS review
Identify as-built features to be included in the upload before the projectcan be closed (e.g. – Taxiway, Shoulder, Lights, Signage, Marking andUtilities)
Collect all attributes
Airports GIS Project Type – Construction/Airside (or Landside)
SOW, Plans with Airport Review and QC of Data
QC and Upload Data near end of project
Close project
8
15 Federal AviationAdministration
Regional Workshop - AAL
Oct 19-20, 2011
Establish Geodetic Control
Recommendations
‣ Separate Airports GIS project
‣ Not in Planning Project (e.g. – Robust Data Collection)
Project Type – Construction – Landside
SOW, Geodetic Control Plan (only), NGS Reviewand Approval
SOW Review (FAA) Focal Point
‣ Proposed Location of PACS/SACS
16 Federal AviationAdministration
Regional Workshop - AAL
Oct 19-20, 2011
Land Acquisition, Noise (Contours or Mitigation),Environmental or Planned Development Determine how Airports GIS will be incorporated into
the project
Determine features to be included and reviewattributes (expect all are included in the project)
Determine who is responsible to QC and uploadAirports GIS data
Determine Airports GIS Project Type
Airport has responsibility for data
Upload data and close project
Planning Data – SOW?, Plans?
9
17 Federal AviationAdministration
Regional Workshop - AAL
Oct 19-20, 2011
Airports GIS – SOW and Plan Requirements
Statement-
of-Work
Plans
Project GoalAirports GIS
Project Type
GeodeticControl
ImagerySurvey &
Quality Control
New Approach1
RW - Extension/New1
AAA-VG or
Non VG
Robust Data Collection -“eALP”2
AAA-VG or
Non VG
Runway ReconstructionConstruction -
Airside
Taxiway/ApronConstruction
Construction –Airside
Noise Contours, PlanningData3
ALP – AirportDesign / Planning
Install PACS/SACSConstruction -
Airside3 Land Acq./Wetlands/
Environmental MappingConstruction -
Landside3 1 – No Installation of PACS/SACS
2 –VG Approach Analysis
3 – Including eALP Planned data (non Surveyed)
4 – Temporarily
18 Federal AviationAdministration
Regional Workshop - AAL
Oct 19-20, 2011
G. Thomas Wade, P.E.
Senior Planner | ASW-610
Office: 817.222.5613
Gil Neumann
Senior Airport Planner | APP-400
Office: 202.267.5840