Last updated: April 2026

Airport ground operations teams manage fleets of tugs, belt loaders, air starters, ground power units, and other specialized equipment across multiple terminals and shift rotations. When that management runs on whiteboards, spreadsheets, and phone calls, maintenance cycles get missed, equipment location is unknown, and accountability gaps show up in inspection logs and incident reports. PCG built a modular GSE management platform that replaced all of it with a single system tracking every asset, every technician assignment, and every service event in real time.

At a glance

🚛 Fleet tracking for tugs, belt loaders, air starters, GPUs, and all GSE asset types

📦 Parts and maintenance inventory with automated consumption tracking

👷 Personnel management with shift assignments and certification records

📍 Real-time location and service status visibility across all terminals

🔧 Preventive maintenance scheduling with usage-based trigger logic

🔐 Role-based access for maintenance, dispatch, and operations leadership

What was the problem and what did PCG build to solve it?

Ground operations teams were managing a complex, multi-terminal fleet using tools that could not keep pace with the operational volume or the accountability requirements of airport ground operations. The gap between what those tools could track and what the operation actually needed to know was showing up as downtime, inventory discrepancies, and compliance exposure.

The Problem
  • Equipment status and location managed on whiteboards and static spreadsheets
  • Manual check-in and check-out processes with no audit trail
  • Fragmented communication between maintenance, dispatch, and shift leads
  • Missed preventive maintenance cycles causing avoidable breakdowns
  • Inventory inaccuracies including lost and duplicate parts records
  • No way to generate service history or performance reports across facilities
  • No accountability tracking for personnel assignments and inspection logs
The Solution
  • Centralized command platform tracking every GSE asset across all terminals in real time
  • QR and barcode integration for check-in, check-out, inspections, and service records
  • Usage-based maintenance triggers that fire on hours, mileage, or calendar interval
  • Automated parts consumption tied to maintenance work orders
  • Full personnel assignment and certification tracking with expiration alerts
  • Live operational dashboard with filters by terminal, equipment type, and service category
  • Exportable compliance, usage, and downtime reports for regulatory and management review

What are the five core modules in the GSE management system?

The system was built as five independent but integrated modules. Each module manages a distinct operational domain. Because the architecture is modular, changes to the inventory module do not affect the personnel module, and new modules can be added as the operation's requirements expand without requiring changes to existing functionality.

🚛 Equipment Fleet Manager
  • Real-time status tracking for every piece of ground equipment
  • Custom attributes for equipment type, condition, location, assigned gate, and availability
  • QR and barcode integration for check-in, check-out, inspections, and service record updates
  • Full service history accessible from any asset record
📦 Inventory Control
  • Parts, consumables, and tools managed by location across all terminals
  • Min and max thresholds with automatic reorder alerts before stockouts occur
  • Inventory audit logs with timestamps and user attribution
  • Automatic part consumption recorded when maintenance work orders close
🔧 Maintenance and Service Scheduler
  • Preventive maintenance logic triggered by usage hours, mileage, or calendar interval
  • Work order creation and tracking with status, assignments, and technician notes
  • Service history reports and compliance logs for each asset
  • Overdue maintenance alerts with escalation to supervisors
👷 Personnel Manager
  • Operators, technicians, and supervisors assigned by shift or equipment group
  • Credentials, certifications, and training records with expiration date tracking
  • Performance and usage logs linked to equipment assignments
  • Automated alerts when certifications approach expiration
📊 Reporting and Dashboard
  • Live operational dashboard showing active equipment, out-of-service units, and open service queues
  • Custom filters by terminal, equipment type, or service category
  • Exportable reports for compliance, usage patterns, and downtime metrics
  • Capital replacement and utilization data for management planning

What were the measurable results after deployment?

📍 100%
Real-time visibility into GSE inventory and location across all terminals
🔧 40%
Reduction in maintenance-related downtime through predictive scheduling
📋 0
Manual spreadsheet processes remaining in the tracked workflows after deployment

Beyond the headline numbers, the operation gained the ability to make capital replacement decisions from utilization data rather than from age alone, and shift transitions became faster because incoming leads could see the current state of every asset and every open work order without a verbal handoff.

What were the key technical innovations in this build?

Modular architecture with independent subsystems. Equipment, inventory, maintenance, and personnel modules share a common database but operate independently. A change to the maintenance scheduling logic does not require rebuilding the inventory or personnel modules.
Usage-based maintenance triggers. Preventive maintenance fires on actual usage data, not calendar intervals alone. A piece of equipment that runs twice the normal hours in a week gets its service event scheduled twice as fast. One running light gets it deferred without penalty.
Real-time status updating with mobile-friendly inspection workflows. Technicians update equipment status and close work orders from mobile devices on the flight line. The dashboard reflects the update within seconds without requiring a desktop session or a radio call to the operations center.
Unified data access across operational roles. Maintenance teams, dispatch, and operations leadership all access the same live data through role-filtered views. Maintenance sees work orders and service history. Dispatch sees availability and location. Leadership sees performance metrics and compliance status. One system, three views.

Technology stack

Component Technology
🖥️ FrontendRazor Pages, JavaScript, Bootstrap
⚙️ Backend.NET Core / C#
🗄️ DatabaseSQL Server
🔔 Alerts and notificationsSMTP email alerts; optional Twilio SMS integration for maintenance and certification triggers
🔐 SecurityRole-based access control with department and function-level permissions; encryption at rest
☁️ HostingIIS deployment; on-premise or cloud configuration supported depending on client infrastructure

Frequently Asked Questions

Yes. The modular architecture was designed specifically to support adaptation. The equipment types, maintenance trigger rules, personnel certification requirements, and reporting outputs are all configurable rather than hardcoded to airport GSE. PCG has built fleet and equipment management systems for municipal fleet operations, construction equipment, and industrial facilities using the same underlying architecture. The specific asset attributes, maintenance schedules, and role definitions are defined during the requirements phase for each deployment.
Each piece of equipment carries a QR code or barcode label. Technicians and operators scan the code with a mobile device to open the asset record, log a check-in or check-out, record an inspection result, or update service status. The scan creates a timestamped, user-attributed record in the database immediately. No paper form, no radio call, no end-of-shift data entry. The label itself can be printed from within the system and is replaceable if damaged without losing any associated history.
PCG audits the existing spreadsheets and databases during the requirements phase to assess what historical data is worth migrating. Service history, equipment records, and personnel certification data are typically migrated so the new system starts with a complete picture rather than a blank slate. Data that is too inconsistent or incomplete to be useful is archived rather than migrated. The migration process includes validation against the new system's data structure before any records are committed to the production database.
Maintenance alerts are delivered by email through SMTP with optional SMS via Twilio integration. Recipients are configured by role and by equipment group: the lead technician for a terminal receives alerts for equipment assigned to that terminal, the maintenance supervisor receives escalation alerts for overdue work orders, and operations leadership receives summary reports on a defined schedule. Alert thresholds, recipients, and escalation rules are all configurable without code changes.
Yes. The system supports multi-location deployment with location-scoped data views. A technician at Terminal B sees the equipment and inventory assigned to Terminal B. A regional operations manager sees all terminals simultaneously with filters to drill into any individual location. Shared equipment that moves between terminals is tracked by location in real time through the check-in and check-out workflow. Consolidated reporting across all locations is available to users with the appropriate access level.
Equipment marked out of service is excluded from availability views and dispatch assignments automatically. The system continues tracking any open work orders, parts on order, and estimated return-to-service dates associated with the asset. When the equipment returns to service, the technician closes the final work order, logs the service completion, and the asset becomes available in the fleet view again. The full out-of-service history remains attached to the equipment record for capital planning and warranty tracking purposes.
About the Author
Allison Woolbert, CEO and Senior Systems Architect, Phoenix Consultants Group

Allison has been building fleet and equipment management systems since the early 1980s, predating PCG's founding in 1995. Her work in aviation ground support, municipal fleet management, and industrial equipment tracking spans more than three decades. The GSE management system described in this case study is one of several fleet management platforms PCG has built for operations where equipment failure is measured in flight delays and regulatory exposure rather than inconvenience.

The design principle behind every PCG fleet management system is the same: the people doing the work need information at the point where decisions get made, not at a desk two hours after the fact. A system that requires a radio call to find out where a piece of equipment is, or a spreadsheet lookup to determine whether a certification is current, is a system that will be worked around rather than used. PCG builds for the flight line, not the office.