MaxIron Blueprint
Start Maximo design from a working configuration.
MaxIron Blueprint is an IBM Maximo and MAS foundation add-on, installed and registered before the first workshop. It includes applications, workflows, statuses, domains, security groups, escalations, start centres and reports. Your process owners review the baseline and agree the changes their operation needs.
Blueprint is licensed and introduced as part of a MaxIron implementation or upgrade scope. Price depends on the estate, modules and agreed baseline. Quote on request.
The choice
Every Maximo foundation arrives by one of three routes
They differ in who makes the standard decisions, when, and whether the reasons outlive the people who made them.
Configure from a blank sheet
Operating context
A design phase is running with nothing installed, and hierarchies, statuses and failure codes are boxes on a wall.
Planning consideration
Senior specialist months on capability standard in every asset-intensive estate, then trimmed under the go-live date. The trims survive to year eight.
Document an existing configuration
Re-base during an upgrade →Operating context
Maximo has run for years, the configuration works, and whoever chose the domains has moved on.
Planning consideration
Leaving configuration decisions undocumented, so each upgrade has to establish their purpose and whether they should be retained.
Start from a curated baseline
See implementation services →Operating context
A working environment sits in front of planners in week one, and design starts from the gap.
Planning consideration
Accepting it wholesale. A foundation nobody argues with is an operating model written for somebody else.
What is in the baseline
Configured and running when you log in on day one
Blueprint is registered against Maximo as one versioned add-on, with its configuration changes recorded.
- Applications and screens
- Set up for asset-intensive operations, so a week-one planner opens something recognisable.
- Hierarchy, classification and domains
- Hierarchy shapes, classification and the domains that hold values consistent once records arrive through MaxIron Data Loader.
- Work types, statuses and lifecycle
- Approval paths and status transitions as mature operators run them, with the failure code structure behind them.
- Security groups and roles
- Access split across planners, supervisors, technicians, contractors and auditors.
- Escalations and automation scripts
- Overdue work, missed approvals, unassigned jobs, expiring certification.
- Start centres, reports and integration keys
- Start centres and KPIs usable in week one, plus the keys your interfaces need.
What you change afterwards
Five steps from an installed baseline to your operating model
Process owners review a running environment and agree the configuration changes needed for their operation.
- 01
Install and register
Installed on the Maximo or MAS environment and registered as a product, with a version and a change record.
Owner MaxIron delivery lead Typically Day one
- 02
Walk it with your people
The first session raises, approves and closes a job with three supervisors, a planner and the stores lead.
Owner Your process owners Typically Week one
- 03
Agree the changes
Record each difference between the baseline and the agreed operating process as a specific configuration change.
Owner Solution architect Typically Weeks two to three
- 04
Configure on top
Deltas released with author, sequence and date, through MaxIron Pipelines where the estate runs it.
Owner MaxIron configuration team Typically Weeks three to six
- 05
Carry it forward
Baseline plus deltas moves through environments as one known shape and follows MAS releases.
Owner You, with MaxIron support Typically Ongoing
One delta, all the way through
A shutdown status the baseline did not have
In the week-one walkthrough a maintenance supervisor says the baseline status path will not survive the annual shutdown: shutdown jobs sit in a personal spreadsheet, invisible to planning and reporting.
Deployed from the outset on every MaxIron-led Maximo and MAS implementation, and the standard foundation for estates we operate and support across utilities, transport, manufacturing, oil and gas and public sector.
The maintenance manager asks for a held-for-shutdown status, visible in the planner view. It is released as a delta on the baseline, so seven months later a MAS release lands cleanly and the status still has a name against it.
Only the customer makes that call. MaxIron configures it, releases it, records who asked.
Scope and boundaries
Your process decisions and data work remain
Blueprint supplies a starting configuration. Process ownership, data preparation and acceptance remain part of the implementation.
It does not make your process decisions
How you approve work, who owns a shutdown and what the failure taxonomy means stay with your process owners.
Your data still has to be brought in
Cleansing and proving asset and location data is the larger half of most programmes, and MaxIron Data Loader is where it lands. Blueprint means it lands in agreed structures.
A baseline nobody adapts becomes debt
The week-one walkthrough is not optional. Accepted wholesale, the baseline belongs to another operator.
MaxIron Blueprint, frequently asked questions
- What exactly is MaxIron Blueprint?
- An IBM Maximo and MAS foundation add-on installed at engagement start: applications, workflows, security groups, domains, automation, start centres and reports as one version-controlled baseline.
- How is this different from a starter pack or a template?
- A template is a document. Blueprint is a registered Maximo product with a version, an upgrade path and a change history.
- How much of the baseline survives contact with our operation?
- Most of it. Hierarchy shapes, security patterns, domains and escalations tend to stay; approval thresholds, shutdown handling and status naming are where deltas sit.
- Will Blueprint slow down our upgrades to MAS?
- No. It is configuration and supported scripting delivered as a registered product, so it follows MAS releases.
- Who owns the configuration we add on top?
- You do. Deltas carry author, sequence and date, so the change record travels with the estate rather than a supplier relationship.
Review Blueprint against your implementation plan
We install Blueprint in a clean MAS environment, walk what it ships with, then work through your list. You leave knowing which route you are on and which decisions stay yours.
Bring this to the walkthrough
- The programme plan, with the date foundation design is due to finish
- The work types and statuses your operation really uses
- Asset and location hierarchy as it stands, spreadsheet included
- The systems Maximo will exchange data with, awkward one included