Getting Started and Participating in the Program

Overall Workflow Getting Started and Participating in the Program David Barron Vice President, Cisneros Inc. david.barron@cisneros-si.com Kevin Carlson Associate Vice President, AECOM kevin.carlson@aecom.com

Overall Work Flow of Participating in the Program INTRODUCTION

Airports GIS Project Flow Project Creation Airport Assignment of Representatives ti Airport Upload Statement of Work Airport (Consultant) SOW Concurrence FAA (HQ or Region) Plan Submittal(s) Consultant Plan Approval(s) NGS Project Execution Consultant Team Deliverables Consultant Airport FAA / NGS Data Verification/Validation NGS Consultant Data Use FAA/Others

Submit a Statement of Work Submit Geodetic Control Plan Submit Imagery Control Plan Submit Survey Control Plan Submit to NGS Conduct Aerial & Ground Survey Prepare Orthorectified Aerial Photography Submit to NGS Planimetrics and Airport Airspace Analysis Convert Planimetrics to GIS data with correct topology Attribute Data Upload Data to AGIS

Overall Work Flow of Participating in the Program AIRPORTS INITIATE THE PROJECT

Project Creation in Airports GIS Airport Sponsor/ Operator Responsibility Can be delegated to State Agency through Letter of Authorization Reference to Online Help

Create an Airports GIS Project

Online Help

Overall Work Flow of Participating in the Program PROJECT TYPES

Project Types Category II or III Operations Navigation Aid Siting Non-Precision / Precision / Visual Airport Layout Plan Airport Obstruction Chart Construction Airside / Landside Instrument Procedure Development Pavement Design / Construction / Rehabilitation / Roughness Airport Mapping Database

Project Types

Overall Work Flow of Participating in the Program PROJECT SCOPING

Project Scoping Reference -18B, Table 2-1 Safety Critical Features? Imagery Required? Photo Scale(s)? Contour intervals? Aeronautical Survey and Airspace Analysis Required? Which Runway(s)? Design and As-Built Data? ALP Follow-on Project? Identify Responsible Party/Data Source for each Feature/Attribute t Statement-of-Work/ Implementation Plans Most Projects Require Some GIS Expertise

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

Example Table 2.1 Use Taxiway Construction

Scope 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 Who handles submittals? Will reports be produced?

Scope of Work Review Address geodetic control Leaf-on or leaf-off imagery? What scale and extent?

Scope of Work Review What will be produced from each orthophoto resolution, planimetrics, offairport data, etc. Are there any existing construction projects or other airfield issues that might impact the timing of the imagery collection?

Scope of Work Review What survey is included? Identify notapplicable tasks explicitly

Scope of Work Review Include maps and graphics to clearly communicate the areas of interest What runways will be treated as verticallyguided?

Scope of Work Review Define e topographic deliverables Topographic data is expensive clearly delineate the expected coverage

Scope of Work Review Address planimetrics and include an attached spreadsheet for all features and attributes Consider phasing the project and providing interim deliverables

Scope of Work Review Do not ignore attribution and conversion to GIS format Attribute details covered in the attached spreadsheet

Scope of Work Review Utilities data might be limited, and be sure to identify the expected quality (most likely SUE Level D ) Manage expectations on collecting surrounding cadastral data if there are desired datasets, identify them clearly

Scope of Work Review Identify data that might be lessaccurate Phased Deliverables

Scope of Work Review Final phase for the planning work (surfaces) and proposed development no survey required here If hardcopies are If hardcopies are desired, be sure to address them

Scope of Work Review Important assumptions: HW / SW Website Mgmt Boundary Survey Training AC Changes Others!

Overall Work Flow of Participating in the Program PROJECT IMPLEMENTATION

Setting Roles and Responsibilities Who is Creating the Project? Responsible for Interacting with the FAA Website? Creating the Statement of Work and Other Plans? Conducting Surveys? Collecting Aerial Photography, If Necessary? Converting and Preparing Data? Uploading Deliverables to the FAA? Managing g the Grant?

Statement-of-Work Framework Components FAA/Airport Agreement Background & Objective Written from Airport Perspective Safety-Critical Data Not Consultant Scope of Requirements Services Plans NGS Compares Plans to Geodetic Control SOW Imagery See Online Help Survey & QC Templates Features Pre Coordinate with As-Built Data ADO Graphic RW Extension, with or w/o

Existing Data Airports GIS If Accepted by NGS (Sponsor Download) NGS/UDDF If Surveyed (NGS Website) FAA/AVN If Approach exists (FAA/AVN Website Airport Data -

Overall Work Flow of Participating in the Program FAA / NGS VALIDATION

VALIDATION / VERIFICATION

Review, Verification, Validation and Acceptance Expectations Task Statement-of-Work Plans Stereo Imagery Data Expectations 1 Week 2 Weeks 1 Month 1 Month NGS Independently Verifies Safety-Critical Data (Runway Coordinates, Profile, 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 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 ADO representative on preferred locations Separate Airports GIS Project Airside Construction Geodetic Control Plans required only when establishing PACS/SACS

Temporary Geodetic Control Meets accuracy requirements Utilize in Planning project if permanent control does not exist Identify as Plan B in Statement- of-work if existing permanent Control cannot be recovered

FAA Airports GIS Program FAA 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 Program FAA 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 17B Imagery Required for ALP Updates and Instrument Procedure Development (AC 150/5300-18, Table 2-1) Not Required for general airside/landside construction projects

Requirements 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 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 Verification

Waivers FAA Approves any Waiver request Pre Coordinate with Regional FAA Representatives Region must Coordinate all waivers with AAS-100 Have waived Full Foliage with Airport provided documentation Included Airport documentation in Statement-of-Work

LiDAR LiDAR is not acceptable for obstacle analysis Airborne LiDAR may be used to develop a Digital Terrain 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 AAS-100)

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

Quality Control and Data Model 480 Pages! Chapter 1-4: 105 pages Chapter 5 (Data Model): 315 pages Appendices Safety-Critical Data Table 4-1 Runways, NAVAIDS, Obstacles, Geospatial (Profiles, Elevation, ARP), Verification vs. Validation Accuracy and Reporting Criteria i Table 2-1 Object Identification Surfaces Vertically Guided Approaches Non VG Approaches Statement-of-Work, Implementation Plans Data Translation, Use of Existing Data & Data Migration Tool GIS Schema (Data Model)

Vertically Guided Object Identification Surfaces LPV and ILS Approaches require use of Vertically Guided Object Identification Surfaces (-18B, Sect. 2.7.1.1) 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 information about all other runways.

FAA Airports GIS Program FAA Requirements AC 150/5300 18b Deliverables -18B is not a graphic version of a Hardcopy ALP Which Version is correct?

FAA Airports GIS Program FAA Requirements AC 150/5300 18b Deliverables -18B is not a graphic version of a Hardcopy ALP Which Version is correct? None Line 18B graphics make a terrible Hardcopy ALP

Airport GIS Website https://airports-gis.faa.gov GS G Controls Workflow Project Statemement-of-Workt t Plans Data Reports Approvals Airport Operator Must Create Project (can be delegate State Agency though Letter-of-Authorization May (usually) assign Representatives (Consultants) to act in their behalf

Overall Work Flow of Participating in the Program MAINTAINING DATA

Data Maintenance Requirements and Best Practices Grant/PFC AC List Require Airports GIS as-builts datasets for most projects Request GIS Data for tenants t prior to issuing a Certificate of Occupancy 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!) Conditional Payment Clauses Contractor Upload-to-FAA Requirements Not just for as-builts ex: Pavement Design