Software Design srl sells an airport a shared version of now only when the records moving through its operational database and integration layer remain attributable, current and recoverable. A dashboard is not the shared state. The accepted state is the agreement between live flight events, authorized changes, downstream delivery and the retained history.

The airport record is an operational control surface

Software Design's Airport Traffic Manager description presents a system that stores and exchanges real-time flight data, accepts automated and authorized manual updates, associates resources with movements and retains history for analysis and service accounting. Those functions place identity and sequence at the center of airport operations.

A revised movement time can affect a stand, gate, baggage belt, staff task, passenger display and chargeable service. The system therefore needs more than the latest value. It needs the source of the observation, when it was accepted, who or what changed it, which dependent systems received it and how conflicting inputs were resolved.

The accepted record should distinguish an airline or air-traffic message from a local manual correction. It should identify the movement and resource without relying on a screen label that can be reused. It should preserve enough history to explain why the visible state changed and which later records depended on that change.

The shared bus does not erase endpoint ownership

The AOSnice framework description places an airport operational database, core services, modules, a shared service bus and distribution channels around the operating picture. A common integration layer can reduce bespoke links, but it also becomes a continuity boundary.

Each connected endpoint still needs an owner, interface identity, expected message set, current route and failure behavior. If a baggage system stops receiving updates, a green integration service is not proof that the operational chain is intact. The operator needs delivery evidence from the intended source through the bus to the intended destination, together with an exception that names who owns recovery.

Changes to schemas, routes or endpoint credentials should be reversible. Before an interface change, the airport should capture the accepted mapping and current endpoint state, identify dependent consumers, define the cutover and rollback conditions, test representative events and preserve the result. A shared bus is useful when it makes that state legible, not when it hides dependencies behind one vendor boundary.

The legal operator boundary must remain explicit

A Software Design customer notice identifies the Naples company and its relationship to SITA. That entity record matters because contracts, support duties, data handling and recovery commitments must attach to a named operator rather than an ambiguous group brand.

Parent-company reach can add resources, but it does not by itself identify which entity hosts a service, controls an interface, retains operational history or restores the platform. Those roles should be explicit in the service record and tested before a disruption, ownership change or replacement project.

Portability requires a recoverable operating picture

An airport can keep the benefits of a shared information layer without treating dependency as permanent. It needs exportable history, documented schemas, current interface inventories, named data owners, recovery copies and a transition plan that preserves the live operating picture while endpoints move.

The practical test is whether another authorized operator can reconstruct the accepted flight and resource state, verify the active routes and restore or replace a failed component without relying on undocumented vendor memory. That is the continuity evidence behind a shared version of now.

Verdict

Software Design's useful surface is the agreement between the airport's accepted operational record and the running network of data sources, service-bus routes and destination systems. The product is credible when identity, event sequence, delivery and recovery remain traceable. This is operator continuity grounded in the live airport state, not advocacy for centralization.

Sources

  1. Software Design: Airport Traffic Manager
  2. Software Design: AOSnice Framework
  3. Software Design: Customer Information Notice