Today's Operations

Aircraft on Ground
1

Currently at the FBO

Upcoming Arrivals
+3

Scheduled for today

Scheduled Departures
+1

Departed or scheduled

At-Risk Trips
1

Require immediate attention

Upcoming Movements
A list of scheduled arrivals and departures for today.
FlightItineraryStatus
OPS-104
G650
Northern Hub → Coastal Gateway
Scheduled
OPS-221
Global 7500
Metro Capital → Coastal Gateway
Arrived
OPS-332
Falcon 8X
Regional East → Coastal Gateway
Scheduled
OPS-404
Challenger 350
Island Hub → Coastal Gateway
At Risk
Task Workload
Manage and assign operational tasks.

Prepare for G650 arrival (location-configured SOP)

Unassigned
Marshalling

Catering delivery for Global 7500

Maria GarciaMMaria Garcia
Catering

Refuel Global 7500 (volume per contract)

Unassigned
Fueling

Tow Falcon 8X to assigned hangar bay

Unassigned
Towing

GPU connect for Challenger 350

Unassigned
GPU Service

Lavatory service for G650

Maria GarciaMMaria Garcia
Lavatory Service

Platform Blueprint

A modular FBO operations platform designed for global, multi-tenant business aviation operations.

1. High-Level Architecture
Global multi-tenant model optimized for operators running multiple airports, regions, and service lines.
  • Multi-tenant hierarchy — FBO organization → locations → facilities (stands, hangars, fuel farms) with shared services and local overrides.
  • Customer org model — company → teams → aircraft with delegated access, billing profiles, and service preferences.
  • Domain separation — customer portal, ops execution, billing, and admin/config are independently scalable modules.
  • Event-driven updates — trip status, task changes, and approvals emit events for notifications, audits, and integrations.
2. Core Data Models (Conceptual Schema)
Auditable, versioned entities with soft deletes and explicit UTC/local timestamps.
  • User — id, orgId, roleIds[], locale, timezone, MFA status, lastLoginAt.
  • Organization — type (FBO or customer), parentOrgId, billingProfiles, defaultTimezone, regionRuleset.
  • Role & Permission — roleId, scope, permissionSet, approvalMatrix, effectiveDates.
  • Aircraft — tailNumber, operatorOrgId, MTOW, equipment, documents, alerts.
  • Trip — itinerary legs, ETA/ETD planned vs actual, local/UTC stamps, status, services, approvals.
  • Service Request — catalogItemId, inputs, dependencies, SLAs, visibility flags.
  • Task — generatedFromServiceId, assignee/team, checklist, start/stop, exception codes.
  • Slot — resourceId, windowStart/ windowEnd, conflictRules, bufferMinutes.
  • Parking/Stand & Hangar Bay — capacity, constraints, location mapping, availability status.
  • Equipment (GSE) — type, status, location, maintenance schedule.
  • Quote — versioned line items, approvals, expiry, currencyCode, taxProfile.
  • Invoice & Payment — invoice schedule, payment terms, partial/recurring support.
  • Document — type, storageRef, visibility, retention policy.
  • Message/Note — trip-linked, visibility (customer/internal), channel.
  • Audit Log — entity snapshots, diff, actor, timestamp, reason.
3. Trip Object Design (System Backbone)
Trip is the single source of truth for arrival, turn, and departure workflows.
  • Lifecycle — draft → quoted → confirmed → in-progress → complete → closed (cancelled/at-risk variants).
  • ETA/ETD — planned vs actual, each stored in UTC + site-local timestamps.
  • Multi-leg — linked legs with turnaround buffers and shared services.
  • Attachments & notes — role-based visibility flags, customer-friendly notes vs internal ops notes.
  • Composable services — each service request is a line item with its own approval and SLA tracking.
  • Approval chain — status, approver, timestamp, and versioned snapshots.
4. Service Catalog & Availability Engine
Configuration-first catalog with rule-based availability and pricing flexibility.
  • Pricing models — flat, hourly, MTOW-based, per pax, per unit, and custom formulas.
  • Dependencies — required inputs (pax count, MTOW), prerequisite services, bundled options.
  • Lead times & cutoffs — per service, per location, with configurable overrides.
  • Availability — aircraft limits, equipment and staff constraints, plus conflict detection.
  • Manual overrides — supervisor approvals with audit trail and reason codes.
5. Operations Execution Layer
Tasking engine connects services to real-world execution with SLAs and proofs.
  • Task generation — service requests create tasks, checklists, and equipment reservations.
  • SLA timers — auto alerts, at-risk escalation, and delay reasons.
  • Assignments — staff/team assignment with equipment requirements and coverage rules.
  • Execution proof — start/stop timestamps, photos, signatures, and checklists.
  • Exceptions — delay handling, incident tags, and post-mortem reporting.
6. Fuel Module (Extensible)
Fuel is modeled as a specialized, extensible service with abstract integrations.
  • Requests — uplift/top-off, target volume, priority and timing requirements.
  • Pricing logic — retail vs contract, tiered volume discounts, and location overrides.
  • Queueing — truck/equipment assignment and priority rules.
  • Receipts & tickets — digital ticket storage, signature capture, and audit links.
  • Status tracking — requested → scheduled → in-progress → completed with integrations abstracted.
7. Pricing, Quoting & Billing Engine
Flexible, region-aware billing with versioned quotes and multi-currency support.
  • Rate cards — effective dates, service-level rules, and locality overrides.
  • Customer overrides — negotiated pricing, contract terms, and approval routing.
  • Surcharges — after-hours, holiday, and capacity-based premiums.
  • Taxes — VAT/GST configurable by jurisdiction with exemption handling.
  • Quote lifecycle — versioning, expiry, conversion to booking and invoice.
  • Billing — partial, recurring, and multi-trip invoicing with payment plans.
8. Communication & Notifications
Trip-centric communications with configurable channels and preferences.
  • In-app messaging — threaded conversations tied to trip timeline.
  • Notes — visibility controls for internal vs customer-facing updates.
  • Automations — event-based alerts for status changes, approvals, delays.
  • Channel abstraction — email, SMS, WhatsApp, push notifications, with provider-agnostic adapters.
  • Preferences — per role, per org, per location notification rules.
9. Dashboards & Views
Role-aware dashboards for staff and customers with real-time transparency.
  • Staff boards — today board, occupancy, fuel queue, at-risk alerts, task workload.
  • Customer views — trip timeline, service status, documents, invoices/payments.
  • Mobile-ready layouts — optimized for ramp use, quick actions, and touch inputs.
10. Admin & Configuration Tools
Configuration over code: every operational and commercial rule is editable.
  • Service catalog editor — create, version, and retire services with dependencies.
  • Rate card editor — region-aware pricing, effective dates, and overrides.
  • Capacity management — stands, bays, equipment, and staffing limits.
  • Rules engine — buffers, lead times, approvals, SLA thresholds.
  • User management — RBAC, teams, access provisioning, announcement banners.
11. Security, Compliance & Reliability
Enterprise-grade protections for multi-tenant aviation operations.
  • Tenant isolation — data partition controls, scoped access tokens.
  • RBAC + MFA — least privilege, approval gating, strong authentication.
  • Audit logs — immutable logs, tamper detection, exportable trails.
  • Encryption — at rest and in transit, key rotation.
  • Reliability — rate limiting, observability, monitoring, retention controls.
12. Integration Strategy
Open integration points with no vendor lock-in for data exchange.
  • Flight data — tracking, weather, NOTAM ingestion via adapters.
  • Accounting — ERP and AR/AP integrations with webhook triggers.
  • Payments — configurable payment processors and token vaults.
  • Fuel systems — ticketing, inventory, truck dispatch abstractions.
  • Public API — API-first design with webhooks and scoped keys.
13. Mobile-First Considerations
Designed for ramp staff and on-the-go teams with offline support.
  • Offline mode — cached tasks, queued updates, sync conflict handling.
  • Push notifications — critical status changes and SLA alerts.
  • Capture tools — photo evidence, signature capture, quick status updates.
14. Phased Build Strategy
A rollout plan that scales from MVP to enterprise operations.
  • MVP — trip lifecycle, core service catalog, booking, tasking, and basic billing.
  • Ops automation — SLA automation, equipment scheduling, advanced approvals, audits.
  • Advanced — integrations, predictive analytics, multi-location optimization.
  • Design principles — configuration over code, no hardcoded currency/timezone/tax, everything auditable and permissioned, Trip as source of truth.