Home/Workflows/Systems integration
Engineering · Integration

Performance where
your systems already are.

A server-side interface puts runway analysis and limiting weights inside the flight planning, dispatch and load systems an operation already runs, with every request and response retained.

Overview

One engine behind every system

Requests from operator systems sit above the line and platform responses below it, from the first call at plan time through to the retained record.

INTEGRATION · REQUEST TO RECORD
STARTCOMPLETEYOUR SYSTEMSPLATFORMPlan builtRequestInto the OFPChange re-runRunway analysisLimiting weightsResponseRetained

One engine behind every system

Flight planning, dispatch, load control and the flight deck resolve against the same calculation, so the systems agree by construction.

Answers at plan time

Limiting weights and runway analysis are available while the plan is still being built, where they can still change the outcome.

Every exchange retained

Requests and responses are retained with the dataset version that produced them, so an integration can be audited in full.

Step by step

From a planning request to a retained record

What the platform does with a server-side request, and what the calling system holds while it happens.

Your systemsPlatform
01Plan time

The planning system asks for performance

The operational flight plan is built and the planning system calls for performance directly, so the numbers arrive while the plan is still open.

  • Server-side call from the planning system
  • Aircraft, route and conditions passed with the request
  • Answer available while the plan can still change
PLAN TIME

Platform receives the request

Planning system waits on one call

ANALYSIS
02Analysis

Every runway comes back, not a summary

Runway and obstacle analysis is returned for the runways in question, computed for the registration in its current configuration.

  • Analysis per runway and per intersection
  • Registration-level configuration applied
  • Wet and contaminated cases returned with the dry result

Figures land inside the plan

PAYLOAD
03Payload

Limiting weights land inside the plan

Limiting weights come back in a form the planning system can act on, so payload and fuel decisions are made against real figures.

  • Limiting weights returned with the analysis
  • Structured for the calling system to consume
  • Dataset version identified in the response
04Change

A change raises a new call

When something moves that affects the answer, the calling system asks again and the platform answers on the current conditions.

  • New request on any change that moves the answer
  • Conditions resolved at the time of the call
  • Previous response retained alongside the new one
CHANGE

Platform answers on current conditions

05Downstream

The same result reaches the other systems

Dispatch, load control and the flight deck resolve against the same calculation, so the figures do not need reconciling between systems.

  • Same engine behind dispatch and the flight deck
  • Consistent results across the operator estate
  • Delivery over the channels already in use
DOWNSTREAM

Same result across the estate

RECORD
06Record

Requests and responses are retained

Every exchange is retained with the dataset version behind it, so an integration can be audited without instrumenting the calling system.

  • Request and response retained together
  • Dataset version recorded with each exchange
  • Available for audit and for support
API · TRANSACTION
REQUEST
From flight planning
RECEIVED
ANALYSIS
All runways
COMPUTED
RESPONSE
Limiting weights
RETURNED
RECORD
Request and result
RETAINED
Evidence

An integration you can audit

Requests, responses and the dataset version behind each one are retained by the platform, so an integration can be reviewed without instrumenting the calling system.

  • Every request and response retained together
  • Dataset version recorded with each exchange
  • Consistent results across dispatch, load control and the flight deck
  • Available for audit and for support

Put performance inside the systems you already run

Talk to our engineers about calling performance server-side from your flight planning, dispatch and load systems.