MaxIron Cloud
Managed IBM Maximo hosting, operated by MaxIron.
A fully managed service for dedicated IBM Maximo Application Suite environments on AWS, Microsoft Azure or Oracle Cloud Infrastructure. MaxIron operates Red Hat OpenShift, databases, monitoring, patching, backups, recovery and the MAS release path.
Service overview
One team operates the complete MAS platform
-
Dedicated
Customer environments
Each customer estate is isolated and operated by named MaxIron engineers.
-
Hours
Typical non-production provisioning
After commercial, network and identity prerequisites are complete.
-
2× yearly
Minimum restore-test cadence
Each production environment is restored into a scratch environment and the result is retained.
-
12 months
Cloud audit-log retention
The standard retention period for cloud audit records.
Architecture and responsibility
A managed platform with defined business control
The hosting scope covers the layers required to run MAS. Region, connectivity, recovery objectives, service hours and application support are agreed in the service description.
Keep the platform ready for the operation it supports.
Maintenance teams depend on Maximo being available when work needs to be planned, dispatched or recorded. We connect platform monitoring, maintenance and recovery preparation in an agreed managed service, giving your team a named operating partner and a clear view of responsibilities.
Explore a group-wide Maximo programmeMaxIron operates
IBM Maximo Application Suite
Manage and agreed MAS applications · production and non-production · controlled release path
Red Hat OpenShift and database
Clusters · database administration · storage · certificates · capacity
AWS, Microsoft Azure or Oracle Cloud
Agreed region · network connectivity · dedicated customer environments
Monitoring, patching, backups, restore tests and incident response span the platform layers.
Your organisation owns
- Business data and process
- Asset definitions, process policy, data stewardship and regulatory acceptance.
- Identity and connected systems
- User approval, identity policy and ownership of ERP, GIS and other counterpart systems.
- Production decisions
- Business acceptance, change windows and approval of service scope and recovery objectives.
Service specification
Platforms, regions, operations and recovery
Platform
- Cloud providers
- AWS, Microsoft Azure and Oracle Cloud Infrastructure.
- Environment model
- Dedicated customer environments operated by named MaxIron engineers.
- Versions
- IBM MAS 8 and MAS 9, plus Maximo 7.6 on the extended support track.
- Provisioning
- Non-production is typically available within hours after the agreed prerequisites. Production follows the approved security and connectivity runbook.
Regions and residency
- Default residency
- United Kingdom and Ireland.
- AWS
- eu-west-2 London, eu-west-1 Ireland.
- Azure
- UK South, North Europe.
- Oracle Cloud
- UK South, EU Frankfurt.
- Other regions
- Agreed per customer and named in the service description.
Operations and visibility
- Monitoring
- Availability, response times, interface queues, scheduled jobs and capacity, with thresholds agreed for each environment.
- Incident management
- P1 to P4 incident classes. The standard P1 acknowledgement target is one hour.
- Service records
- Health, incidents, changes, approvals and monthly reporting are available in the MaxIron Portal.
- Operations team
- Named MaxIron engineers working within the certified management system.
Recovery and assurance
- Recovery objectives
- The standard production starting point is a 15-minute recovery point and a 4-hour recovery time. Contracted objectives are set for each environment.
- Restore testing
- At least twice a year for each production environment, with the result retained.
- Audit logs
- Cloud audit records retained for 12 months.
- Certification
- ISO/IEC 27001:2022 and ISO 9001:2015, ISOQAR certificate 27274.
- Threat detection
- AWS GuardDuty, Microsoft Defender for Cloud or OCI Cloud Guard on every active environment.
- Sub-processors
- Published by name and region on the Trust Centre. Approval, change notification and objection rights follow the data processing agreement for the engagement.
The recovery figures shown here are standard production starting points. Final objectives, regions, retention and incident targets are agreed against your environment list and written into the service description. Current assurance information is published on the Trust Centre.
Working relationship
A managed platform with clear business control
MaxIron operates the service
MaxIron is responsible for the cloud platform, Red Hat OpenShift, databases, MAS runtime, monitoring, patching, backups, recovery testing and release process described in the service agreement.
Named engineers work from the same incident, change and approval records that your service team sees in the MaxIron Portal. Platform break-fix follows agreed standing authority. Planned production changes follow the approved maintenance window.
Your team controls the business decisions
Your team decides who can use Maximo, how the estate supports the operation, which maintenance windows apply and which tested changes are approved for production.
Business validation remains part of every release. Connected systems such as SAP, finance, GIS and field applications keep their own owners and change windows, with MaxIron managing the Maximo side of each interface.
Onboarding
From your current estate to a managed service
The programme is planned around the estate you already have, the controls it must meet and the business validation required before production.
- 01
Review the estate
We confirm the environment list, MAS or Maximo version, modules, integrations, residency requirement and service objectives.
Owner MaxIron and your service owner Typically Initial working session
- 02
Agree the service design
The architecture, regions, connectivity, identity integration, recovery objectives, maintenance windows and migration approach are written into the service design.
Owner MaxIron with your architecture and security teams Typically During mobilisation
- 03
Build and connect the environments
MaxIron provisions the dedicated platform, connects corporate identity and networks, applies the agreed security controls and prepares non-production for validation.
Owner MaxIron Typically Non-production typically within hours after prerequisites
- 04
Migrate and validate
Configuration, data and integrations are moved through rehearsed runs. Your team validates the business process before production cutover.
Owner MaxIron and your business leads Typically Set by estate size and migration scope
- 05
Operate and improve
Monitoring, incidents, patching, backups, releases and service reporting continue under the agreed monthly service.
Owner MaxIron Typically Ongoing
Service scope
What is scoped alongside the hosting service
These areas affect the platform but require their own business decisions, owners or commercial scope.
Business process and asset decisions
Asset hierarchy, criticality, work management process and planning discipline remain customer decisions. MaxIron can support that work through business process optimisation.
Application support
Operation of the hosted platform is included. Support for Maximo configuration, workflows and user issues can be added and is scoped against the live estate.
Connected systems
SAP, finance, GIS, historians and field systems retain their own owners and maintenance windows. MaxIron manages and monitors the Maximo side under Maximo integrations.
Custom code and licensing
Custom code must build, test and promote through the release path. Modernisation and MAS AppPoints licensing are sized separately.
Questions about MaxIron Cloud
- What is MaxIron Cloud?
- MaxIron Cloud is a fully managed hosting service for IBM Maximo Application Suite. MaxIron provides and operates the dedicated cloud platform, Red Hat OpenShift, databases, MAS runtime, monitoring, patching, backups, recovery and release process for a monthly service charge.
- Which cloud providers and MAS versions are supported?
- MaxIron Cloud runs on AWS, Microsoft Azure and Oracle Cloud Infrastructure. We operate IBM MAS 8 and MAS 9, plus Maximo 7.6 estates on the extended support track.
- Who operates the service?
- Named MaxIron engineers operate the platform within our ISO/IEC 27001:2022 management system. Monitoring, incidents, changes and approvals are managed through the same records available to your service team in the MaxIron Portal.
- Where can our data be hosted?
- The standard regions are the United Kingdom and Ireland, with AWS London and Ireland, Azure UK South and North Europe, and Oracle Cloud UK South and EU Frankfurt available. Other regions can be agreed and are recorded in the service description.
- What are the recovery objectives?
- The standard production starting point is a 15-minute recovery point and a 4-hour recovery time. Final objectives are agreed for each environment and written into the service description. Every production environment is restore-tested at least twice a year.
- How quickly can a MAS environment be provisioned?
- A non-production environment is typically available within hours after commercial, network and identity prerequisites are complete. Production follows the agreed security, connectivity and validation runbook.
- How do we see service health, incidents and changes?
- The MaxIron Portal provides service health, incident and change records, production approval queues and monthly service reporting. Your service team sees the same active records used by MaxIron engineers.
- Is application support included?
- MaxIron Cloud includes operation of the hosted platform. Application support for Maximo configuration, workflows, integrations and user issues can be added and is scoped against the estate.
- Are MAS licences included?
- MAS entitlement is sized separately. MaxIron is an IBM Gold Partner and MAS reseller, and can supply licences or work with your existing entitlement under MAS AppPoints licensing.
Start with your environment list.
We will review the estate, confirm the likely service shape and identify the information needed for architecture, migration and pricing.
Useful information for the first conversation
- The production and non-production environment list
- MAS version, or the Maximo version you are moving from, and the modules in scope
- Key integrations and any fixed maintenance windows
- Data residency, recovery and assurance requirements