sun sess 2.acc workflow final - kansas city[1] · • geodetic control plans required only...

Overall WorkflowOverall Workflow

Kevin Carlson

Getting Started and Participating in the Program

David Barron Kevin CarlsonAssociate Vice President, AECOM

[email protected]

David BarronVice President, Cisneros Inc.

[email protected]

Overall Work Flow of Participating in the Program

INTRODUCTION

Airports GIS Project FlowAirports GIS Project Flow• Project Creation – Airport

A i t f R t ti Ai t• Assignment of Representatives – Airport• Upload Statement of Work – Airport (Consultant)

SOW Concurrence FAA (HQ or Region)• SOW Concurrence – FAA (HQ or Region)• Plan Submittal(s) – Consultant• Plan Approval(s) NGS• Plan Approval(s) – NGS• Project Execution – Consultant Team• Deliverables – Consultant AirportDeliverables Consultant• Data Verification/Validation – NGS• Data Use – FAA/Others

AirportFAA / NGSConsultant

Submit a Statement of Work

Submit Geodetic Control Plan

Submit Imagery Control Plan

Submit Survey Conduct Aerial & Submit Control Plan Ground Surveyto NGS

Prepare OrthorectifiedAerial Photography

Planimetrics and Airport Airspace

Analysis

Submit to NGS

Convert PlanimetricsConvert Planimetrics to GIS data with correct topology

Attribute Data Upload Data to AGIS


AIRPORTS INITIATE THE PROJECT

Project Creation in Airports GISProject Creation in Airports GIS

• Airport Sponsor/ Operator Responsibility

• Can be delegated to State• Can be delegated to State Agency through Letter of Authorization

• Reference to Online Help

Create an Airports GIS

Project

O li H lOnline Help


PROJECT TYPES

Project Types

• Category II or III Operations• Navigation Aid Siting – Non-Precision / Precision / Visual• Airport Layout PlanAirport Layout Plan• Airport Obstruction Chart• Construction – Airside / Landside• Instrument Procedure Development• Pavement Design / Construction / Rehabilitation / Roughness• Airport Mapping Databasep pp g

Project Types


A-GIS / e-ALP Pilot Program Projects

Project Types


Construction Projects

Project Types


Approach Procedures and Navaids

Project Types


PROJECT SCOPING

Project Scoping• Reference -18B Table 2-1Reference -18B, Table 2-1

– Safety Critical Features?– Imagery Required? Photo Scale(s)?– Contour intervals?– Contour intervals?– Aeronautical Survey and Airspace

Analysis Required? Which Runway(s)?

– Design and As-Built Data?– ALP Follow-on Project?

• Identify Responsible Party/Data S f h F t /Att ib tSource for each Feature/Attribute

• Statement-of-Work/ Implementation Plans

• Most Projects Require Some GIS Expertise

AC 150/5300-18B | Table 2-1AC 150/5300 18B | Table 2 1

Example Table 2.1 Use – Taxiway Construction

Scope of Work – Practical ExperienceScope of Work Practical Experience

Review each feature and all associated attributes– What is the intended source– Who is responsible for obtaining it– Does it need data conversion

Scope of Work Review

WhoWho handles

submittals?

Will reports be produced?

Scope of Work ReviewAddress geodeticgeodetic control

Leaf-on or leaf-off

imagery?imagery? What scale and extent?

Scope of Work ReviewWhat will be

produced fromproduced from each orthophoto

… resolution, planimetrics, off-airport data, etc.

Are there any existing construction projects or other airfield issues that p j

might impact the timing of the imagery collection?

Scope of Work ReviewWhat

survey issurvey is included?

Identify not-applicable

taskstasks explicitly


What runways a u ayswill be treated as vertically-

guided?

Include maps and graphics to clearly communicate the areas of interestareas of interest


Define e etopographic deliverables

Topographic data is expensive – clearly delineate

the expected coverage


Address dd essplanimetrics –and include an

attached spreadsheetspreadsheet

for all features and attributes

Consider phasing the project and providing interimand providing interim

deliverables


Do not ignore attribution and conversion to GIS f tGIS format

Attribute details covered in the attached spreadsheet


Manage expectations on

collecting disurrounding

cadastral data –if there are

desired datasets, identify

them clearlyUtilities data might be limited, and be sure to ,

identify the expected quality (most likely SUE “Level D”)


Identify data that might be less-

accurate

Phased Deliverables


Final phase for the planning

work (surfaces) d dand proposed

development –no survey

required hereq

If hardcopies areIf hardcopies are desired, be sure to address them


Important assumptions:

HW / SW•HW / SW•Website Mgmt•Boundary Survey•Training•AC Changes

Others!


PROJECT IMPLEMENTATION

Setting Roles and Setting Roles and Responsibilities• Who is…

– Creating the Project?– Responsible for Interacting with the FAA Website?– Creating the Statement of Work and Other Plans?

C d ti S ?– Conducting Surveys?– Collecting Aerial Photography, If Necessary?– Converting and Preparing Data?– Converting and Preparing Data?– Uploading Deliverables to the FAA?– Managing the Grant?g g

Statement-of-Work

• FAA/Airport Agreement• Written from Airport

• Background & ObjectiveRW Extension with or w/o

ComponentsFramework

• Written from Airport Perspective

• Not Consultant Scope of Services

– RW Extension, with or w/o Safety-Critical Data

• Requirements– PlansServices

• NGS Compares Plans to SOWS O li H l

– Plans• Geodetic Control• Imagery

S & QC• See Online Help Templates

• Pre Coordinate with ADO

• Survey & QC– Features– As-Built DataG hiADO • Graphic

Existing DataExisting Data

Ai GIS If• Airports GIS – If Accepted by NGS (Sponsor Download)( p )

• NGS/UDDF – If Surveyed (NGS W b it )Website)

• FAA/AVN – If Approach exists pp(FAA/AVN Website

• Airport Data -


FAA / NGS VALIDATION

VALIDATION / VERIFICATIONVALIDATION / VERIFICATION

Review Verification Validation Review, Verification, Validation and Acceptance Expectations

Statement-of-Work 1 WeekTask Expectations

Plans 2 WeeksStereo Imagery 1 MonthData 1 Month

NGS Independently Verifies Safety CriticalNGS Independently Verifies Safety-Critical Data (Runway Coordinates, Profile,

NAVAIDS, Obstacles, etc.)NAVAIDS, Obstacles, etc.)

Establishing Geodetic Control• PACS/SACS

– 1 PACS/2 SACS - Standard Configuration– 1 PACS – Minimum Configuration– Can support Multiple PACS/SACS systems

at large airports - if justifiedat large airports - if justified.– Evaluate installation benefits if unusual

geological conditions exist– Usually cost beneficial

• Recommendations– Establish PACS/SACS in “Development”

project/grant as additional scope– Coordinate with Regional ADOCoordinate with Regional ADO

representative on preferred locations– Separate Airports GIS Project – Airside

Construction• Geodetic Control Plans required only when• Geodetic Control Plans required only when

establishing PACS/SACS

Temporary Geodetic ControlTemporary Geodetic Control

• Meets accuracy requirements• Utilize in Planning project if

permanent control does not exist• Identify as “Plan B” in Statement-Identify as Plan B in Statement

of-Work if existing permanent Control cannot be recovered

FAA Ai t GIS PFAA Airports GIS ProgramFAA Survey Requirements AC 150/5300 –18b

Preparation of required descriptions, sketches, photographs, and other documentation.

PENCIL RUBBINGS. Rubbings are not required during the recovery of a survey mark. However, rubbings are required at the time of each observation at that station See sample Below

FAA Airports GIS Programp gFAA Survey sample Form AC 150/5300 –18b

3) photograph type three should be taken horizontally with the station approximately 10 to 30 feet in the distance

AC 150/5300 17B | IAC 150/5300-17B | Imagery

• Required for ALP Updates and Instrument Procedure Development (AC 150/5300-18, T bl 2 1)Table 2-1)

• Not Required for general airside/landside construction projects

RequirementsRequirements• The imagery should be flown at an altitude providing for usability of

the imagery beyond the scope of the current project, such as future engineering or planningengineering or planning.

• Flying height less that 12,000 feet Above Ground Level (AGL)• Ground Sample Distance (GSD) – 10-30 cm (4-12 in./pixel)• Generally, Multiple flight levels if project includes off-airport obstacle y, p g p j p

analysis

Flightline and Control Diagram• Recommend to Include

Imagery Area(s) in Statement-of-Work

NGS VerificationNGS Verification

W iWaivers

• FAA Approves any Waiver request– Pre Coordinate with Regional FAA Representatives

Region must Coordinate all waivers with AAS 100– Region must Coordinate all waivers with AAS-100

• Have waived Full Foliage with Airport provided g p pdocumentation

Included Airport documentation in Statement of Work• Included Airport documentation in Statement-of-Work

LiDARLiDAR

LiDAR i bl f b l l i• LiDAR is not acceptable for obstacle analysis• Airborne LiDAR may be used to develop a Digital

Terrain Model (DTM) to cost effectively developTerrain Model (DTM) to cost effectively develop ground contours after coordination with Regional Office and AAS-100

• Ground based (stationary or mobile) is being evaluated to capture runway surface and other terrain data (Coordinate with Regional Office and ( gAAS-100)

AC 150/5300 18B | Survey AC 150/5300-18B | Survey Requirements and GIS Schema

Quality Control and Data Modely• 480 Pages!

– Chapter 1-4: 105 pagesChapter 5 (Data Model): 315 pages– Chapter 5 (Data Model): 315 pages

– Appendices• Safety-Critical Data

– Table 4-1– Runways, NAVAIDS, Obstacles,

Geospatial (Profiles, Elevation, ARP),…

• Verification vs. ValidationA d R ti C it i• Accuracy and Reporting Criteria

• Table 2-1• Object Identification Surfaces

– Vertically Guided Approachesy pp– Non VG Approaches

• Statement-of-Work, Implementation Plans

• Data Translation, Use of Existing Data &Data Translation, Use of Existing Data & Data Migration Tool

• GIS Schema (Data Model)

Vertically Guided Object Identification S f

• LPV and ILS Approaches require use of Vertically Guided Object

Surfaces

use of Vertically Guided Object Identification Surfaces (-18B, Sect. 2.7.1.1)

O t f bj t id tifi ti• One set of object identification surfaces per runway -– not approach-end dependent

and – Horizontal and Conical Surfaces

not combined into an Airport surface

• Airport Airspace Analysis (object identification) requires Airport Elevation and ARP, therefore AAA for a runway requires i f ti b t ll thinformation about all other runways.

FAA Airports GIS Programp gFAA Requirements AC 150/5300 –18bDeliverables -18B is not a graphic version of a Hardcopy ALPWhich Version is correct?

FAA Airports GIS Programp gFAA Requirements AC 150/5300 –18bDeliverables -18B is not a graphic version of a Hardcopy ALPWhich Version is correct? None

Line

18B graphics make a terrible Hardcopy ALP

Airport GIS Website

// G S G• https://Airports-GIS.FAA.Gov• Controls Workflow

– ProjectSt t t f W k– Statemement-of-Work

– Plans– Data– ReportsReports– Approvals

• Airport Operator– Must Create Project (can be j (

delegate State Agency though Letter-of-Authorization

– May (usually) assign Representatives (Consultants) to act i th i b h lfin their behalf


MAINTAINING DATA

Data Maintenance – Requirements Data Maintenance – Requirements and Best Practices

Grant/PFC | AC List

• Require Airports GIS as-builts datasets for most projectsR t GIS D t f t t• Request GIS Data for tenants prior to issuing a Certificate of Occupancyp y

Grant Assurance 29

Deliverables must go through a procedure

Maintaining Data

• Tools for Maintaining Data– Data Submittal Standards– Data QC / QA Procedures– Contract Language for Deliverables (GIS!)

C diti l P t Cl– Conditional Payment Clauses– Contractor Upload-to-FAA Requirements

Not just for as-builts … ex: Pavement Design

sun sess 2.acc workflow final - kansas city[1] · • geodetic control plans required only...

Documents