End to end: from the forwarder truck at the gate to the consignee signature on import — RFC acceptance, ULD build-up, a 640-position ASRS, aircraft loading, and IATA Cargo-IMP EDI. Open it in a browser and start playing; nothing to install.
Every image on this page is captured from the running application — no mock-ups.
None of these are fixed by more training, because they depend on memory and eyesight for a whole shift. They are fixed by a system that blocks at the point of failure.
A DGR declaration that does not match the cargo passes a visual check
Fines · seizure · flight safety risk
A piece is scanned into the wrong ULD and nobody knows until the load sheet disagrees
Six figures per event, plus offloaded cargo
Nobody can see which unit has been idle for how long
Runaway ULD rental · spoiled perishables and pharma
FSU / FFM not sent, or sent late, because they are still typed one by one
Customers cannot track · airline SLA penalties
The same data is typed 3–4 times between acceptance and flight close
Compounding errors · no audit trail
This is the same file we carry on a thumb drive to on-site presentations. The whole system is one file, fully functional with no internet connection.
This application is designed for 1920×1080. On a phone it will be tiny — open it on a computer, or tap "New tab" and rotate to landscape.
The question customers really ask is not what features exist, but where the daily job gets easier.
| Daily task | Before | With ACTS |
|---|---|---|
| Acceptance (RFC) | Documents checked by eye and memory; a miss is found when the fine arrives | All four gates checked — Data / DGR / Security / Airworthiness. Fail means you cannot accept it at all |
| ULD planning | Segregation table looked up in a manual, or remembered; a mistake shows up as a rejection at destination | Conflicting SHCs are caught and split into a new ULD automatically, with the rule quoted |
| Scanning into a ULD | Wrong ULD still closes; discovered when the load sheet disagrees | The wrong scan locks the ULD immediately and names the correct one; fixing it unlocks automatically |
| Finding a ULD | Walk the floor, make calls, open several systems | A 3D map of all 640 positions — hover for flight, weight, temperature and dwell time |
| Idle stock | Discovered when the ULD rental invoice arrives, or when the perishables have spoiled | Heatmap turns red past 8 hours of dwell, so the supervisor clears it before it costs anything |
| Closing a flight | FSU typed one AWB at a time, regularly missed, no proof of sending | One button fires FSU-DEP for every AWB plus FFM and UCM, each with a recorded timestamp |
| "Where is my shipment?" | Ask around several departments; sometimes the answer is tomorrow | Open the AWB and read its whole timeline with every FSU attached — answered in ten seconds |
| Flight delay | Rebuild the whole build-up plan by hand, slowly and error-prone | The system re-plans automatically, shifts cut-off, re-queues work and pulls in cargo that would have missed |
| Payload overrun | The supervisor picks what to cut, then argues with sales | The system proposes the least damaging set with full reasoning, and books the next flight for the customer |
| Disputes | Evidence hunted across paper and multiple systems for a day | Everything on one screen, from the first FWB to the consignee signature, each with a timestamp |
| Training new staff | Weeks, with a buddy alongside | Every screen explains itself via the ? button, with a running narration bar — up to speed within one shift |
| Data entry | The same record typed 3–4 times between acceptance and flight close | Entered once; every screen, KPI and EDI message reads from the same state |
One system, a different win for each role.
Acceptance · Build-up · Loading
Shift control
Management
Forwarder · Airline
Every image below is captured from the same application you can play with above.
The top lane is export (gate → acceptance → build-up → ASRS → dolly → aircraft); the bottom lane is import running back the other way. Cargo boxes move along the lines only when the system actually changes that shipment's status.
Five KPIs counting up from the live simulation, a six-flight timeline with cut-off markers, a 24-hour throughput chart against plan, and three occupancy donuts.
Eight truck docks with timers, and an acceptance queue with four RFC lights (Data / DGR / Security / Airworthiness) — one AWB deliberately fails DGR so you can see the block work.
Per-ULD build plans with weight bars, IATA DGR segregation warnings, three workstations, and a job queue ordered by priority with the reason shown.
4 aisles × 2 sides × 16 bays × 5 levels = 640 positions, with four ETVs travelling horizontally and vertically in separate aisles simultaneously. Orbit it with the mouse.
Six dolly docks, a checklist following the loading sequence, and an aircraft hold diagram that fills position by position as the team ticks each unit off.
Flight and shipment tables you can sort, search and filter on any column; click a row to open the full lifetime timeline of that AWB.
An EDI log in Cargo-IMP format (FWB / FHL / FFM / FSU / UCM). Expand any line for the real raw message with a line-by-line explanation.
The core of the proposal — each one quotes a standard the industry actually uses, and tells the operator how to fix it.
| Event | What the system does | Loss prevented | Standard |
|---|---|---|---|
| DGR declaration mismatch | Blocks the change to ACCEPTED and withholds FSU-RCS · moves to DG hold · notifies the forwarder | Dangerous goods on the aircraft: fines, seizure, safety risk | IATA DGR 62nd Ed. |
| Conflicting SHCs in a ULD | Warns with the rule cited, then splits into a new ULD automatically | Contamination, damage and rejection at destination | IATA DGR 9.3.A |
| Wrong ULD scan (misload) | Locks the ULD until the piece is moved and re-scanned · logged to shift quality report | Six-figure misloads and offloaded cargo | IATA ULD Regulations |
| Damaged ULD | Issues a damage report, reserves a spare and triggers a rebuild immediately | Unserviceable ULD on the aircraft and damage claims | IATA ULDR |
| Weighed vs declared mismatch | Flags for re-check when the difference exceeds the set threshold, before acceptance | Wrong rating and a load sheet that disagrees with reality | IATA TACT |
| Payload exceeded | Computes the least damaging offload set with full reasoning and books the next flight | Overweight aircraft and unloading at the ramp | IATA AHM — Load Control |
| Approaching cut-off | Counts down per flight, raises job priority automatically and warns ahead of time | Missed flights and airline SLA penalties | Service level agreement |
| Flight delay | Re-plans the whole build-up, shifts cut-off and re-queues the work | A dead plan rebuilt by hand — slow and error-prone | — |
| Found cargo (FDCA) | Opens a discrepancy case with a reference number and fires FSU-DIS back to origin | Untracked cargo and customs problems | IATA Cargo-IMP FSU |
| Long-dwelling ULD | Occupancy heatmap by dwell time shows which position is over the threshold | Runaway ULD rental and spoiled perishables/pharma | IATA CEIV (cold chain) |
Pick Scenario B in the demo above and press Auto; all four play out for real.
The airline reschedules mid-shift and the whole build-up plan is void
→ Cut-off shifted automatically, a new plan computed, and cargo that would have missed pulled back in
Load control reduces payload for extra fuel on a diverted routing
→ The least damaging offload set is proposed with full reasoning, and the next flight is booked for the customer
A collapsed base and torn net make the unit unserviceable
→ Damage report issued automatically, a spare reserved, and a rebuild started without stopping the flight
Breaking down an import ULD turns up three pieces not on the manifest
→ A discrepancy case is opened with a reference number and FSU-DIS is sent back to the origin station
Nothing invented here — every rule the system enforces comes from a standard airlines and ground handlers already work to.
Tested at two levels: logic in a headless runner, and rendering in a real browser at 1920×1080.
The whole state engine sits apart from the interface — screens can change without touching the rules, and the same logic carries into production
Every screen reads from the same central state, so two screens can never disagree
Seed data comes from a seeded PRNG; Reset gives the identical world every time — ideal for demos and regression testing
Works with no internet and sends nothing off the machine — safe to present inside operational areas
Integration points for ETVs, airline systems, customs and weighbridges were designed as separate modules from day one
Book a free consultation with our engineering team.
