Maximo Configuration
Configuration first. Customisation only when it is genuinely justified.
Most of what customers think needs customisation is actually configuration done well. Our delivery teams default to configuration-first because it is cheaper, safer, upgrade-friendly and fully supported. The result is a Maximo estate that does what the business needs without becoming a maintenance liability.
Configuration is a discipline. Done well, it removes most of the case for customisation. Done badly — or skipped because the team was unfamiliar — it leaves the estate with bespoke code that should never have been written, and a long-term cost that compounds at every upgrade. We treat configuration as the default and the discipline.
What we deliver
- Applications, security groups, signature options and conditional UI configured to the business
- Workflow, escalations and communication templates that reflect how work actually flows
- Domains, classifications, item assemblies and asset hierarchies designed for clarity, not convenience
- Start centres and KPIs that give people the information their role needs
- Reports and screens shaped through configuration before any code is written
- Configuration audit and uplift on existing estates that have drifted
How it fits with the rest of the programme
Configuration runs through every implementation and MAS upgrade we deliver. It is the natural counterpart to customisation modernisation, where existing Java customisations are reviewed and the ones that should be configuration are moved back to configuration. It is also the foundation of business process optimisation: the process changes have to land in a Maximo that is actually shaped to support them.
Sectors we have done configuration uplifts in
Related capabilities
Related capabilities you might also need
MaxIron products
MaxIron products that hold Maximo configuration in shape
Maximo configuration — frequently asked questions
- What does configuration cover in IBM Maximo?
- Configuration covers everything you can shape in Maximo without writing code: applications, security groups and signature options, domains, workflow, escalations, communication templates, KPIs, start centres, conditional UI, classifications, item assemblies, scheduling, reporting and more. In a properly configured Maximo, this covers the vast majority of what most enterprises actually need.
- Why does this matter for the buyer?
- Configuration is cheaper, safer and upgrade-friendly. Customisation that should have been configuration is the single biggest reason older Maximo estates are hard to upgrade and expensive to support. Defaulting to configuration protects the long-term value of the investment.
- When is customisation actually justified?
- When a real business requirement genuinely cannot be met through configuration. We are happy to write Automation Scripts and integrations where they are warranted; we just refuse to write them where configuration would do the job better. Customisation modernisation is the partner offer when historical custom code needs to be revisited.
- Do you do configuration on its own, or only as part of bigger projects?
- Both. Configuration runs through every implementation and upgrade we do, and we are also engaged for standalone configuration uplifts where an estate has accumulated drift, inconsistencies or under-used capability.
A Maximo that does what the business needs without becoming a liability.
Tell us where your estate is today and what it is being asked to do. We will tell you what should be configuration, what should be customisation, and what should be neither.
Start a conversation