Applications, workflows, escalations, automation scripts and BIRT reports configured to how your organisation actually works. Configuration first, customisation only where it earns the cost of carrying it through every future upgrade.
Review your Maximo configurationMaximo is a COTS platform, and the fastest way to make it expensive is to write code where configuration would have done. Custom automation scripts and custom Java have to be inventoried, re-tested and frequently rewritten at every version move, which is why a heavily customised 7.6 estate is so much harder to migrate to Maximo Application Suite than a well-configured one.
Valueztech configures first. That means the Maximo data model, organisations, sites and security groups designed properly, then applications, workflows, escalations and BIRT reports built on top of them. Custom code is proposed only where a genuine operational requirement justifies it, and each one is documented so it can be reassessed rather than inherited blindly.
The same discipline applies in reverse. When we are asked to look at an existing estate, the first deliverable is usually an inventory of custom Java and automation scripts, BIRT reports, MIF and REST integrations, security groups, mobile usage and ERP touchpoints, followed by a keep, refactor or retire recommendation for each.
Maximo data model, organisations, sites and security groups, set up so the estate can add a site or a business unit later without a restructure.
Application configuration against the processes agreed in design, so planners, supervisors, technicians and storeroom staff each see a Maximo shaped to their job rather than to the default.
Approval routing, work assignment and escalation rules configured to your delegations, including the escalations that quietly do most of the operational work.
Scripted behaviour where standard configuration genuinely cannot deliver the requirement, written to be readable and re-testable at the next upgrade.
BIRT and custom report development, including the compliance and regulatory reporting that asset operators in water, energy and government are measured on.
Keep, refactor or retire recommendations for every existing customisation, based on actual usage data rather than on who asked for it originally.
Current-state analysis across customisations, integrations, reports and licensing. On existing estates this covers custom Java and automation scripts, BIRT reports, MIF and REST integrations, security groups, mobile usage and ERP touchpoints.
Before anything is built, we check whether the outcome is already achievable with shipped capability. A surprising amount of legacy customisation exists because a product feature was not known about at the time.
Requirements are proven with prototypes and approved by stakeholders one sprint ahead of the build stream, so what gets configured is what was actually wanted.
Changes are delivered in two to three week sprints with automated tests written before the code and a showcase of tested software at the end of each sprint.
For each existing customisation, a documented recommendation based on real usage. Rationalising early reduces migration scope, testing effort and ongoing support cost.
Configuration, customisation and workflow changes continue under a Support Hours subscription, so the people who built the configuration are the ones who evolve it.
Full configuration stack
Organisations, sites, security, workflows, escalations, automation scripts, BIRT reports and integrations delivered by one practice.
Upgrade-aware decisions
Customisation rationalisation is standard practice on Valueztech upgrade programmes, including a Maximo 7.6 to MAS 9 delivery for a Victorian water utility.
Certified practitioners
IBM Maximo Manage v9 Functional Deployment Professional credentials within an IBM Silver Business Partner practice.
Covered by Support Hours
Configuration, customisation and workflow changes plus BIRT development are included in the Support Hours subscription.
Common questions about configuring IBM Maximo, when customisation is justified and what happens to custom code at upgrade.
Book a free thirty-minute call to walk through your customisation inventory and what a keep, refactor or retire assessment would change about your upgrade scope.
Review your Maximo configuration