What is A.D.I.B.?
ADIB (Agonistic Data and Information Broker) is an intelligent Agonistic Data and Information Brokerinformation exchange layer that sits between systems that produce information and systems that consume information.
​
Instead of creating separate integrations between every system, each system connects to ADIB once. ADIB then manages how information moves between the different systems according to defined rules, permissions and business requirements.
​
For example, an airport may have systems for flight operations, baggage, passenger processing, security, parking, billing, facilities, CCTV, airlines and ground handling.
Â
A transportation hub may have rail, bus, traffic, parking, payment and passenger information systems.
Â
A smart city may have CCTV, IoT sensors, traffic systems, environmental sensors, public safety systems and citizen applications.
​
ADIB provides a common information exchange layer across these environments.
​
The platform can receive information through APIs, REST, SOAP, Webhooks, MQTT, message queues, database change capture, secure file transfer and other supported protocols. It can then validate the information, transform it into a common structure, apply routing rules and deliver it to the appropriate destination.
Â
This approach reduces integration complexity while improving visibility, control, traceability and operational resilience.
Â
ADIB is also designed to remain independent of a particular technology supplier, programming language, database, operating system or hosting model. This gives organisations greater flexibility to adopt new technologies without creating another generation of tightly coupled integrations.
​
ADIB connects to data once and delivers information everywhere!
Agnostic Data & Information Broker
The A.D.I.B. Architecture
ADIB is built as a modular architecture with multiple layers working together to manage the complete information journey from source to destination.
1. Data Exchange and API Gateway
2. Connectors and Ingestion
3. Messaging and Event Streaming
The Data Exchange layer provides the central entry and exit point for integrations. The API Gateway manages authentication, authorisation, traffic control, API management and logging.
​
Every connection is governed through a consistent set of policies, regardless of the source system or destination.
ADIB provides connectors for different types of systems, devices and applications. Data can be received through APIs, messaging systems, databases, files, sensors and other integration mechanisms.
​
This allows existing systems to continue using their preferred technologies while ADIB provides the common exchange layer.
The messaging layer enables information to be distributed reliably without requiring systems to communicate directly with one another.
​
Events can be published once and delivered to multiple authorised consumers. Persistent queues, acknowledgement, retry mechanisms and controlled replay help ensure that information is not lost when a destination becomes temporarily unavailable.
4. Transformation and Routing
5. Storage and Persistence
6. Management and Governance
Information from different systems rarely arrives in exactly the same format. ADIB can validate, map, transform, enrich and route information according to configurable rules and a common data model.
The Persistent Store provides a controlled record of information passing through the platform, together with audit and operational records. Landing, Curated and Consumption zones can be used according to the information requirements of the organisation.
Across all layers, ADIB provides integration management, metadata, lineage, monitoring, logging, governance and security.
​
The result is an architecture that is not simply an integration engine, but a controlled information exchange platform for complex operational environments.
Connect Anything with ADIB Connectors
One of the key strengths of ADIB is its ability to connect systems using different technologies and protocols. ADIB can support common integration mechanisms such as:
​
• JSON and structured data formats
• REST APIs
• SOAP services
• Webhooks
• MQTT
• Message queues
• Database change capture
• Secure file transfer
• Scheduled file exchange
• TCP and IP based connections
• Aviation messaging formats such as AIDX and IATA Type B
• Enterprise systems such as SAP through appropriate adapters
​
The architecture allows connectors to be configured and reused rather than creating a completely new integration for every connection. This is particularly important in airports and transportation environments where legacy systems often operate alongside modern cloud applications, specialised operational systems, sensors and external platforms.
​
ADIB can therefore act as a common integration layer without requiring every system to understand every other system. A new system only needs to connect to ADIB. Once connected, it can exchange information with the systems and applications that it is authorised to communicate with. This significantly simplifies the integration landscape and makes it easier to introduce new applications, services and technologies over time.
Exchange, Transform and Deliver Information
ADIB is designed around a simple principle:
​
Receive information once. Understand it. Govern it. Deliver it where it is needed.
​
Information entering ADIB can be validated against defined schemas and business rules. It can then be mapped into a common data model before being routed to one or more destinations.
​
Routing can be based on the source, destination, information type, event, priority, business rule or other configured criteria. For example, a flight status event could be received once and distributed to an airline application, passenger information display, airport operations centre, mobile application, analytics platform and other authorised consumers. Similarly, a traffic incident detected by a smart city camera could be transformed into a standard event and distributed to a traffic management centre, emergency response application, public information service and other relevant systems.Â
This creates a loosely connected environment where systems do not need to know how every other system works. ADIB manages the complexity in the middle.
​
The platform also provides traceability across the information journey. Organisations can follow information from its source through processing and transformation to its final destinations. This provides valuable operational visibility and supports audit, troubleshooting and reconciliation.
Persistent Store, Replayability and Operational Resilience
Operational information is often time sensitive. Losing an event, transaction or message can have significant consequences. ADIB therefore incorporates persistent messaging, acknowledgement, retry, recovery and replay capabilities.
​
When information enters the platform, it can be retained within the Persistent Store rather than simply passing through memory and disappearing after delivery. The Persistent Store can contain selected information for up to N days, with the actual retention period configured according to operational, regulatory and business requirements. This provides an important capability for replayability. If a destination system is temporarily unavailable, information can be retained and delivered when the destination becomes available again. If a downstream system requires information to be resent, authorised operators can replay the required information from the retained record.
​
This also supports recovery, reconciliation and investigation. For example, if an airport system experiences an outage, relevant messages can be recovered and delivered after the system returns. If a transportation system needs to reconstruct events following an incident, historical information can be retrieved from the retained record.
​
ADIB also supports monitoring of interfaces and pipelines, with automated retry and recovery mechanisms designed to minimise disruption. The proposal describes monitoring from source through to confirmed receipt, together with retry, checkpoint recovery, backfill and reconciliation capabilities.
​
This makes resilience part of the architecture rather than an afterthought.
Security, Metadata and Data Governance
As information moves between multiple systems and organisations, security and governance become critical. ADIB applies security controls across the information exchange environment, including authentication, authorisation, access control, encryption, audit logging and traffic management. Access can be controlled according to users, applications, systems, roles and defined permissions. APIs can also be governed through appropriate authentication mechanisms and traffic policies.
​
Beyond security, ADIB provides a metadata driven approach to managing integrations. Metadata can describe the source, destination, information type, schema, transformation rules, routing rules and other characteristics of an information flow. This creates a more manageable environment where integrations can be controlled through configuration rather than extensive custom development.
​
Data governance is also supported through common data models, data dictionaries, metadata, lineage, quality rules and traceability. This is particularly important for airports, transportation hubs and smart cities because the same operational information may be consumed by many departments, applications and external stakeholders.
​
ADIB helps establish confidence that information is properly controlled, understood, protected and traceable throughout its journey.
ADIB for Airports, Transportation Hubs and Smart Cities
ADIB is particularly suited to environments where large numbers of operational systems need to exchange information continuously.
A.D.I.B. for Airports
A.D.I.B. for Transportation Hubs
A.D.I.B. for Smart Cities
Airports are among the most complex operational environments, with many systems working simultaneously across flight operations, passenger processing, baggage, security, ground handling, facilities, parking, billing, airlines and airport management.
Â
ADIB provides the information exchange backbone connecting these systems.
Â
Flight events can be received once and distributed to multiple authorised systems. Baggage information can flow between baggage systems, operational systems and relevant applications. Passenger movement information can be exchanged with authorised platforms. Operational alerts can be distributed to the appropriate teams. Data can also be delivered to enterprise data platforms for analytics and reporting.
Â
The architecture supports real time, near real time and scheduled information exchange, allowing each system to operate according to its own technical requirements while ADIB manages the information exchange layer.
Â
ADIB can also provide a foundation for future airport capabilities such as Airport Collaborative Decision Making, integrated operational dashboards and more connected airport ecosystems.
​
The result is an airport where systems become more connected without creating an increasingly complicated web of point to point interfaces.
Modern transportation hubs increasingly combine multiple modes of transportation within a single operational environment.
​
A major transportation hub may include rail, bus, taxi, ride hailing, parking, traffic management, ticketing, payment, passenger information, security, CCTV and facility management systems.
Â
Each system may have its own vendor, technology and data structure.
Â
ADIB can act as the common information broker between these systems.
Â
A train arrival event, for example, could be received from a rail system and distributed to passenger information displays, mobile applications, station management systems, traffic systems and other authorised services.
Â
Traffic incidents detected through cameras or sensors can similarly be transformed into standard operational events and distributed to traffic management, emergency response and relevant public information channels.
Â
This creates a connected transportation ecosystem where information can move across organisational and technological boundaries without requiring every system to integrate directly with every other system.
Smart cities generate enormous amounts of operational information from different sources.
Â
These may include CCTV cameras, traffic systems, environmental sensors, IoT devices, public safety systems, parking systems, public transport, utilities, mobile applications and citizen services.
​
ADIB provides the information exchange layer that allows these sources to communicate with the applications and platforms that need their information.
​
For example, a CCTV or IoT system may generate an incident event containing information such as event type, location, time and source identifier. ADIB can receive the event, validate it, apply the appropriate routing rules and distribute it to traffic management, emergency response, command centres, mobile applications or other authorised platforms.
​
The same architecture can be applied to environmental alerts, traffic congestion, public safety events, parking availability and other smart city use cases.
​
This allows a city to evolve from a collection of independent systems into a more connected operational ecosystem.
A.D.I.B., A.D.A.M. and A.I.D.A.
ADIB, ADAM and AIDA are complementary technologies within our broader data and artificial intelligence ecosystem. They address three different stages of the information and intelligence journey. ADIB connects and exchanges information across operational systems. ADAM brings that information together for data management, analytics and visualisation. AIDA builds on that governed data and analytics foundation to provide an intelligent, conversational experience through Generative AI. Together, they create a progression from connected operations, to governed data, to analytics, to intelligent interaction.
