AIS (Airport Information Systems)

Name: AIS (Airport Information Systems)
Brand: AIS (Airport Information Systems)

Flight Information Display System, Aeronautical Billing System, Overflight Billing System

Est 1990|8 Ref Customers

LinkedIn 486|Website|FTEs 5|HQ Castle Donington, England, GB

MarketsERP Invoicing & Payment Processing

Published Oct 12, 2026

01Common complaints

- Scenarios where alternatives are better - Large hub airports with complex multi-terminal constraints and deep integration needs may find SITA or Amadeus better suited depending on ecosystem and governance. - Airports needing only digital signage or basic FIDS without billing or multi-department integration may find FIDS-only vendors more cost-effective. - Organizations with strict vendor-security prequalification requirements (for example, publicly published SOC 2/ISO documentation) may prefer vendors that publish those artifacts. - Technical requirements AIS may not meet (based on public information gaps) - If you require SSO/SAML/SCIM and formal security certifications, AIS does not publish these details publicly; buyers should validate during procurement. - Budget constraints - Quote-based, configurable suites can become more expensive compared with point solutions for a narrow use case. - Red flags in buying process - Limited public pricing and limited mainstream review coverage increases the diligence burden on the buyer. - Current limitations acknowledged by public materials - AIS marketing materials describe the need for configurability and integration but do not publish architectural limitations. - Features on the roadmap - AIS blog references product updates and modernization efforts (for example, AFIDS 2.0 updates) but does not provide a publicly dated product roadmap with commitments. - Scale limitations - Not publicly documented. - Security or compliance gaps - Security certifications and detailed security controls are not publicly documented; this is a notable gap for B2B and critical infrastructure buyers. - API limitations or integration constraints - No public developer portal or comprehensive API documentation was found; integration interfaces should be clarified during procurement.

Deal disqualifiers

Airports requiring publicly documented SOC 2 or ISO 27001 certifications as a procurement prerequisite
Airports needing published APIs, AIDX support, or modern integration toolkits without custom engagement
Airports requiring a published cloud-native deployment model with detailed architecture and security artifacts

02Why they buy

- Competitive advantages observable in public materials (with caveats) - Operations-to-revenue linkage - AIS documents integration between AFIDS (operational events), FIDSnet (display distribution), and ALDIS (aeronautical billing), indicating an integrated workflow across these modules. - Billing capabilities - ALDIS is described as supporting detailed charging configurations (discounts/surcharges, multiple tax levels, dual-currency invoicing) in vendor materials. - Regional adoption signals - Named airport upgrades and visible logos indicate real operational adoption in regional airport segments. - Where competitors have advantages - AeroCloud and Veovo emphasize cloud-native architectures and predictive operations in public materials. - Incumbents such as SITA and Amadeus have broader integration coverage and stronger visibility in global procurement processes.

03Field reports

Review-platform coverage reality check (important)

- Searches for Gartner Peer Insights, G2, and TrustRadius did not return clearly relevant product pages for this specific vendor; search results often matched unrelated "AIS" acronyms. As a result, independent review-platform coverage for this specific vendor is limited or not readily discoverable. - Publicly visible customer sentiment therefore relies more on AIS’s published customer logos, third-party airport/industry write-ups, and general practitioner discussions about FIDS and airport operational systems.

Evidence of deployments (customer logos / named airports)

AIS product pages display multiple airport logos in AFIDS and ALDIS marketing pages (for example: Glasgow Prestwick, City of Derry, Ireland West Airport Knock, Humberside).
Industry group posts describe upgrades at:
- City of Derry Airport (FIDSnet upgrade; Android Smart Boxes used as display controllers)
- Glasgow Prestwick International Airport (FIDSnet upgrade)

Community/social signal (relevant to buying)

A Reddit AMA from a practitioner responsible for airport flight information displays highlights that these systems are critical infrastructure and that go-live risk and operational impact are high.
Practitioner preference for integrating FIDS within the AODB to reduce interface issues was expressed in the AMA; these comments reflect general airport IT concerns rather than AIS-specific reviews.

Factors appearing to influence selection of AIS (inferred from vendor materials and upgrade articles)

Vendor-provided statements
- The vendor describes stability and customer support capabilities and indicates configurability in its product materials and references a user group community (AISUG).
Practical buyer appeal
- For regional airports, a modular suite integrating AFIDS, ALDIS, and FIDSnet can be an appropriate scope compared with larger enterprise suites.

Likely reasons for not selecting AIS (inferred)

Lack of publicly documented cloud and security posture can slow procurement for regulated buyers.
Airports seeking cloud-native architectures, AI/ML-enabled analytics, or broad enterprise network effects may shortlist alternative vendors that emphasize those capabilities.
Very large airports with complex, multi-terminal operations may prefer larger incumbents depending on ecosystem fit.

Direct quotes (balanced, with attribution)

From the Reddit practitioner AMA (general FIDS implementation):
- "Just hit me how critical this system is - thousands of passengers will rely on it to catch their flights."
- "Btw, personally I prefer FIDS integrated in the AODB, as many problems through interface problems are obsolete"
Note: These quotes are not about AIS; they reflect broader market/operator experience.

Case Studies

- Vendor-adjacent "success stories" and upgrades - City of Derry Airport upgrade (industry forum post) - Described by the post as a cost-effective solution using Android Smart Boxes as display controllers and references multiple FIDSnet v3.0 customers. - Critical view: No quantified KPI improvements (for example, reductions in misconnects, FIDS incidents, or operational workload) were provided in the public post. - Glasgow Prestwick International Airport upgrade (industry forum post) - Describes an upgrade to FIDSnet. - Critical view: The post provides limited quantitative operational impact data. - AIS blog content - AIS blog posts describe product updates and operational concepts (for example, AFIDS functioning as a backend to FIDSnet) and integration narratives. - Critical view: These materials are vendor-produced and do not contain independently verified performance metrics.

04Best fit

Company sizes

Likely best fit: small-to-mid sized airports (regional) needing multi-department operational data capture and aeronautical billing without the budget or scale for the largest enterprise suites.

Industries and verticals

Airport operators
Ground handling companies and handling agents (as stakeholders feeding data)
Airport finance teams (aeronautical billing)

Roles and personas

Decision makers
- Airport Operations Director / Head of Operations
- CIO / Head of IT / Airport Systems Manager
- Head of Finance / Revenue Assurance
End users
- ATC administration staff
- Handling agents and airline station staff
- Fuel operators and airside operations personnel
- Terminal operations staff managing passenger communications

Pain points addressed

Consolidating operational data flows to feed:
- Passenger-facing displays (FIDS)
- Airport web flight status
- Aeronautical billing and invoicing workflows

Qualification criteria

Airports that value:
- Configurable workflows with ICAO/IATA and UTC/local time support
- Linking operational events to billing workflows
- A vendor with an established operating history and documented ownership that can suggest software continuity

05The pitch

- What the product does (core value proposition in objective terms) - AIS (Airport Information Systems) provides a suite of airport operations software focused on regional/smaller-to-mid airports, centered on: - AFIDS (Airport Flight Information Display System): real-time flight data collection and processing used for operations and feeding displays and web outputs - FIDSnet: flight information display network (including web uplift capabilities referenced by AIS) - ALDIS (Airport Landing Dues Information System): aeronautical billing and invoicing engine - AIS describes its software as integrated across airport departments (air traffic administration workflows, handling agents, refuellers, apron management, billing, passenger information displays) and states the product offers configurable options and an emphasis on operational reliability. - Target market and market positioning - AIS’s public materials and customer logos indicate a core focus on regional airports and airport operators that need: - A configurable operations stack - Integration between operational data capture (AFIDS) and revenue/billing (ALDIS) - Flight information display distribution across terminal screens and web - The footprint appears concentrated in the UK/Ireland and nearby regions; AIS states it has implementations outside that region as well. - Company background (founding year, HQ, key leadership) - Founding year and HQ are not documented in a single public "About" page reviewed. - AIS states it has decades of experience supplying airport management systems; this is a vendor-provided statement and was not independently verified in the pages reviewed. - AIS provides a contact page including support channels and describes remote diagnostics via customer VPN. - Funding and growth: investment rounds, acquisitions, estimated customer count/revenue if public - Ownership / acquisition - AIS was acquired by a larger software group in 2022; this is a documented corporate event. - Customer count (vendor-stated) - AIS states it has worked with several dozen clients and airports for ALDIS implementations. - Public revenue/customer metrics - AIS does not publicly disclose revenue, ARR, or audited customer counts on the pages reviewed. - Pricing model with specific tiers and costs where available - Pricing is not publicly listed as fixed tiers; no per-airport/per-screen/per-module pricing was found. - The site uses an "Arrange a Demo" call-to-action; pricing appears to follow a quote-based enterprise engagement model. - Total cost of ownership considerations (implementation, training, hidden costs) - Likely cost drivers (inferred from product type and AIS statements) - Implementation and configuration work: AIS states its solutions are configurable and tailored to airport requirements, which commonly implies consulting and configuration effort. - Integration: AFIDS/FIDSnet/ALDIS integration with airport, airline, handling agent, and ATC flows can add cost and duration to projects. - On-prem vs hosted: AIS does not clearly state hosting models publicly; an on-premises deployment would require hardware, database, and IT overhead. - Support model: AIS states typical response times on its contact page; support SLAs and after-hours coverage may carry additional fees. - Potential hidden costs / procurement considerations - Remote diagnostics that require customer VPN access may necessitate additional security approvals, monitoring, and vendor-access controls from airport IT/security teams. - Key competitors in the space (list 4-6 direct alternatives) - SITA Airport Management - Amadeus airport operator solutions (e.g., AODB and broader airport operator stack) - AeroCloud (cloud-native airport operations platform) - Veovo (airport operations and passenger flow optimization) - FIDS-only and signage solutions (e.g., PADS4 FIDS Operator and other FIDS vendors)

Get a comprehensive analysis of AIS (Airport Information Systems) including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →