Document library

Client brief

Terminal and airside maintenance brought onto one MAS estate

Transport & airports · United Kingdom · 9 months to go-live

Download two-page PDF

Situation

A regional airport held airside assets in Maximo 7.x and terminal building services in a separate facilities tool. Maintenance had to continue within airside closure slots and the live safety case.

MaxIron responsibility

MaxIron designed and implemented a single MAS estate, including its multizone OpenShift architecture in the airport’s Azure subscription. Airport authorities retained permit approval, safety decisions and acceptance.

Asset register, regulatory tagging, MAS Manage, Maximo Mobile, Azure platform, integrations and ongoing service

Delivery

The programme built the asset register and regulatory tagging, configured work controls, connected agreed BMS and SCADA event classes, and introduced Maximo Mobile for field evidence.

Airside work orders carry a valid permit reference and closure slot before dispatch. The airside supervisor releases the job. The permit authority signs in the permit system. Engineers attach field evidence to the asset and work record, including offline capture where coverage is poor.

Platform and connections

IBM MAS 9 on Red Hat OpenShift in Microsoft Azure; corporate identity; BMS/SCADA; permit references; finance

Outcome

Terminal and airside operations went live on MAS 9 in nine months. Engineers use one asset estate with corporate single sign-on, while the permit system remains the authority for issuing and approving permits.

Scope and decisions

Permit issuance and approval remain in the permit system. The HSE and compliance functions retain the safety case. Integration accepts agreed event classes and priorities. The architecture serves this airport’s boundaries and requires review against another operator’s safety rules.

Delivery lessons

Bring compliance into the first hierarchy workshop, pilot the order of permit checks with supervisors, and give duplicate-tool retirement a named owner and date at mobilisation.

Next conversation

Bring the current asset-system boundaries, permit process, critical-asset register, closure calendar and compliance reporting requirements to an airport programme assessment.

Evidence basis

This brief summarises the published anonymised engagement. Client-identifying names, sites and records are withheld. Reference discussions are subject to client permission and NDA where required. Published durations and outcomes relate to this estate; another programme requires assessment of its scope and operating constraints.

Explore the full source page →