Implementation timelines, offline and online capability, dispatch integration, logging and more. If your question is not covered here, contact us directly.
Normally an implementation is started and finished within two to three months. This is highly dependent on which features are required, so it can be both shorter and longer. We also offer an expedited on-site implementation lasting one to two weeks at an extra cost.
Yes, documentation support is included in the setup fee.
Yes. The performance data for your fleet, whether manufacturer SCAP modules, performance tables or digitised AFM data, is installed on the device, so takeoff and landing calculations run fully offline. You will still need connectivity to synchronise new configurations, airport and obstacle databases, and to upload log files.
All of them. Where the manufacturer provides a SCAP module (the IATA standard for computerised airplane performance), we use it, either as a first-principle module solving the certified performance model directly or as a second-principle module computing on pre-calculated data. Where no SCAP exists, or another basis suits your operation better, the same engine runs on RPM/RTOW table lookups, digitised AFM performance charts, supplements and custom data sources, every one validated against the certified reference.
Yes. The manufacturer corporate programmes are supported alongside the commercial types they are built on: Boeing Business Jets (BBJ, BBJ2, BBJ3, BBJ MAX, BBJ 747-8, BBJ 777 and BBJ 787), Airbus Corporate Jets (ACJ TwoTwenty, and ACJ319, ACJ320 and ACJ321 in both ceo and neo, plus ACJ330, ACJ340 and ACJ350), the Embraer Lineage 1000 and Legacy 600/650, and the Bombardier Challenger 850. A corporate version shares its airframe with the commercial aircraft, but carries different maximum weights, auxiliary fuel tanks and its own AFM, so each one is set up on its own certified data rather than inheriting the commercial figures.
Yes. Every aircraft type we support can run server-side takeoff and landing performance, and the Performance API connects it directly to your flight planning and dispatch systems. Calculations and dispatch releases remain synchronised with the crew’s EFB, so the flight deck and the back office always work from the same numbers.
Yes. The Web Performance Dispatch UI gives dispatchers full takeoff and landing performance in the browser, supporting the joint dispatcher and pilot responsibility under FAA Part 121. Releases can be delivered to the aircraft over ACARS or AIRCOM datalink, and every calculation is logged in JAWS.
DS Contingency Solution provides performance through any standard web browser, on any device, powered by the same DS Performance engine as the EFB app. If an iPad is lost, damaged or unavailable, the operation continues.
Yes. DS Analysis Tools tests and validates the calculation engine, airport & obstacle database revisions and manually engineered data such as EOSIDs. It also supports studies from citypair analysis and batch RTOW runs to airport authority assessments.
More than 40 airlines worldwide, from regional specialists to global carriers. We share references person to person rather than publishing lists, so ask us for operators relevant to your fleet and region.
Yes, we do. Currently there is no time limit: all logs are stored, always. We can easily tweak retention to suit your needs if shorter periods are required.
We offer a cloud-based solution for the back-end systems, so regardless of your scale of operation or which products you use, getting started is easy and secure. Contact us for specifics.
Contact us about implementation, integrations, certification or pricing.
