Why MaxIron
A UK ferry operator completed its Maximo upgrade in seven months and retained the same MaxIron team for the ongoing service.
One published engagement
The upgrade combined application migration, database conversion and one production cutover. The same architects continued on the support account.
Starting release
IBM Maximo 7.6
The operator entered the programme on IBM Maximo 7.6.
Live release
IBM MAS 9.0.1
The upgrade put IBM MAS 9.0.1 into production.
Runtime
Red Hat OpenShift
The live IBM MAS estate runs on Red Hat OpenShift.
Client decisions recorded
Delivery commitments
01
The proposal identifies the delivery leads. A named architect owns configuration, integration and upgrade design; senior leadership stays involved in scope, risk and acceptance.
Leadership responsibilities and prior career experience02
Where hosting and support are in scope, delivery knowledge stays with the account. The ferry upgrade retained the architects who designed the move into its ongoing service.
Ferry upgrade and continuing support03
Inventories, supported platform design, trial loads and rehearsed cutovers turn technical decisions into acceptance evidence. Change and release records identify the approver and the scope of each change.
Airport architecture and operational controls04
Written data standards, runbooks and paired delivery preserve the decisions needed to maintain the estate. The gas-network workstream transferred standards ownership and development capability to internal roles.
Utility data and capability transferHow the work runs
The same sequence on an implementation, an upgrade or a live estate we take over. Each step produces an artefact the client keeps.
Customisation and integration inventory first. For an upgrade, that is the input to a fixed quote and a trial run in a non-production environment.
Upgrade or rebuild, MaxIron Cloud or your Azure, AWS or OCI, which MAS components are in this phase. Written down before the build starts.
Named architect, agreed release cadence, and a record of who approved each change. The products that hold that record are on the products page.
Platform operations on MaxIron Cloud or in your Azure, AWS or OCI subscription, and application support with continuity from delivery into the live service.
For a 7.6 estate, start with the upgrade quote. For an estate already in service, start with a 30-minute health-check review.
Engagement scope
MaxIron specialises in IBM Maximo and MAS. The service schedule records the people, scope, acceptance evidence and operating responsibilities for the engagement.
The proposal identifies the accountable lead and delivery roles. Named-person continuity and notice of a change can be agreed in the contract schedule.
Fixed pricing follows the customisation and integration inventory. Before assessment, an estimate states the assumptions and the factors that can change scope.
Business-role access, asset-data definitions, operating priorities and production acceptance remain with the customer’s accountable owners unless the contract assigns them differently.
Runbooks, standards ownership and knowledge transfer are agreed for the workstream. Hosting layers, support coverage and recovery objectives are written into the service schedule.
Describe the current version, hosting, interfaces and delivery requirement. A senior lead will identify the assessment needed, the responsibilities MaxIron can carry and the approvals your team will hold.
Useful to have on the call