Airport Electronic Management System

Blaine Peterson Operations Director Duluth Airport Authority

Like many local airports: Small staff burdened by old paper-based

record keeping systems Preparing for FAA 139 inspections was burdensome System management was non-existent or

poorly designed Strong historical data was not easy to access

or process

History

Identified Need One database to manage all airport operations Examples: Daily 139 airfield inspections Trackable airfield / non-airfield work orders Airport signage and lighting plans Tied to the FAA’s NOTAM Manager system Airfield equipment maintenance program Tenant emergency notification and emergency system management system

Cloud based for use on the airfield and in the office No need for maintaining large on-airport server

Options

Develop own database Small staff doesn’t have the capability

Commercially available system Several available that didn’t have all the

capabilities we looked for

Selected VEOCI Cloud based Multi-functional 139 centric with expandable capabilities

DAILY 139 AIRFIELD INSPECTIONS TIME CONSUMING BUT CAN TARGET INDIVIDUAL AIRPORT

NEEDS NOT A BOILERPLATE SYSTEM THAT YOU ARE TIED TO

SENT ADMINISTRATOR TO “VEOCI BOOTCAMP” VERY COST EFFECTIVE REGARDING THE INFORMATION

GAINED (SEND A COMPUTER SAVVY PERSON) YOU CAN BUILD IT WITH AS MUCH/LITTLE INFO AS YOU

WANT INTERACTIVE GOOGLE EARTH MAP IS MOST USEFUL

Implementation

DAILY 139 AIRFIELD INSPECTIONS

Where are we at 6 months later

REPORTS FUNCTION USEFUL FOR 139 INSPECTION PREPARATION

EXPANDING CAPABILITY EMERGENCY MANAGEMENT

AIRFIELD SIGN REPLACEMENT PLAN

AIRFIELD VEHICLE MAINTENANCE PROGRAM

AIRFIELD PAINT PLAN

AIRPORT FACILITIES MANAGEMENT

139 AND OSHA TRAINING RECORDS

AIRFIELD DRIVERS TRAINING RECORDS

MORE????

QUESTIONS or COMMENTS?