Database-to-AirTOP integration utility PUBLIC PORTFOLIO VIEW

Data Integration

SQL Flight Plan Importer

Imports approved flight-plan records from a relational data source into AirTOP with movement pairing, mapping, validation and controlled exception handling.

ROLE Data mapping, pairing logic, validation workflow and AirTOP import engineering

DELIVERY MODEL Specialist-governed · Human-reviewed

SQL AirTOP API Java Movement Pairing Data Mapping CSV Export

SQL Flight Plan Importer public interface preview

CAPABILITY PREVIEW Public-safe interface representation

PROJECT OVERVIEW

From operational need to controlled delivery

THE CHALLENGE

Operational need

Structured data still requires careful chronology, movement relationships, field mapping and quality checks before it can be used safely in a simulation model.

ENGINEERED RESPONSE

Solution approach

A purpose-built importer retrieves an approved operating period, pairs related movements, prepares routing and model fields, and exposes exceptions for specialist review before import.

VALUE CREATED

Operational impact

Creates a repeatable database-to-AirTOP workflow, reduces manual pairing and improves visibility of unmatched or invalid records.

CONTROLLED WORKFLOW

A clear specialist-led path from source to result

Select period

Choose an operating date or approved date range

Fetch records

Read authorised movement data from SQL

Pair movements

Associate related arrival and departure activity

Map & validate

Prepare model fields, routes and classifications

Review exceptions

Inspect unmatched, duplicate or incomplete records

Import & export

Create AirTOP records and preserve a review log

DEVELOPED CAPABILITIES

Complete public-safe feature inventory

The list below describes the developed capability without exposing operational records, source-system credentials, private mappings or proprietary implementation details.

SQL data extraction

Provides a controlled entry point for approved operational datasets.

Connects to an authorised relational flight-plan data source.
Supports a selected operating date or a complete date range.
Maps the selected source period to the corresponding AirTOP model day.
Retrieves arrival and departure movement records for review.
Displays source records in a sortable specialist table.
Keeps database credentials outside the public application content.

Operational time handling

Uses movement-relevant timestamps instead of a single generic time field.

Selects the appropriate operational time for each movement type.
Normalises timestamps into the AirTOP simulation timeline.
Handles midnight crossing and multi-day source ranges.
Assigns records to the correct model day.
Flags invalid chronology before import.
Sorts the review grid using the calculated reference time.

Arrival and departure pairing

Associates related movements while retaining unmatched traffic.

Groups records using approved aircraft and chronology attributes.
Matches the nearest valid subsequent movement where relationships are consistent.
Checks reciprocal origin and destination logic.
Keeps arrival-only and departure-only records visible.
Shows paired, unpaired and excluded counts before import.
Exports a link-review report for specialist verification.

Route and procedure mapping

Converts database route fields into model-ready routing information.

Maps departure routing from available procedure and departure-fix data.
Maps arrival routing from available procedure and arrival-fix data.
Selects the strongest valid match from available model objects.
Supports local-flight and overflight treatment.
Retains usable movement data when full routing cannot be resolved.
Makes unresolved mappings visible before import.

Import controls and reporting

Gives the specialist a clear, reversible review process.

Previews every candidate record before model creation.
Supports configurable duplicate handling.
Shows validation warnings and import-blocking errors.
Uses a progress indicator for longer database operations.
Exports processed records and review results to CSV.
Separates created, skipped, unmatched and failed outcomes.

Data governance

Protects operational information while documenting the workflow.

Keeps connection strings and credentials in environment configuration.
Avoids publishing source schemas or operational records.
Uses explicit mapping and validation steps.
Preserves specialist approval before committing model data.
Supports traceable review outputs without revealing confidential values.
Separates public portfolio descriptions from production implementation details.

SOLUTION ARCHITECTURE

High-level design without sensitive implementation exposure

Authorised SQL source

Approved movement and flight-plan dataset

Extraction layer

Date filtering and controlled record retrieval

Pairing & mapping engine

Chronology, relationship, route and field preparation

Specialist review UI

Counts, exceptions, duplicate controls and approval

AirTOP & export

Model creation plus CSV review output

CAPABILITY EVIDENCE

Designed outcomes

Repeatable database-to-AirTOP preparation workflow.

Reduced manual movement pairing and field mapping.

Clear visibility of unmatched and invalid records.

Improved consistency across operating-day imports.

No public exposure of source-system details or operational data.