How we deliver
We operate your estate from one console, and you read the same records.
The MaxIron Portal runs delivery and operations on the IBM Maximo and MAS estates we host and support. Your service owners read health, your change authority signs production change, and the monthly service report comes off the same records.
What you see when you sign in
Your estates, their state, and anything waiting on you
One row per estate and environment, scoped to the groups your administrator granted. Every row carries its last sync time, so a stale row says so.
| Estate | Environment | State | Alerts | Waiting on you | Synced |
|---|---|---|---|---|---|
| Water utility | Production | Healthy | None active | Nothing awaiting you | 2 min ago |
| Water utility | Test | Healthy | None active | 1 change awaiting your approval | 2 min ago |
| Rail operator | Production | Watching | 1 warning, interface queue | Nothing awaiting you | 1 min ago |
| Rail operator | Training | Stopped | Suppressed while stopped | Nothing awaiting you | 1 min ago |
Live markup rather than a screenshot. Names, counts and timings are illustrative; the columns are the ones a customer signs in to.
Reading the state column
- Healthy
- No alert open, and the last sync is inside the refresh interval.
- Watching
- An alert is open with its source and start time, and an engineer is on it.
- Stopped
- Stopped to schedule, so alerting is suppressed by design.
What a service owner does in it
Four actions, and who holds each one
- 01
Sign in and take your scope
Corporate SSO, with no separate MaxIron account. Visibility follows the group your administrator assigns, so an owner of two regions sees two estates and nothing else.
Owner Your administrator Typically Once, at onboarding
- 02
Read the state
Service health, open alerts with source and start time, environments and clusters, open tickets and month-to-date cost. Every card is stamped with its last sync.
Owner IT service owner Typically Daily, under five minutes
- 03
Decide on a change
Changes arrive in the approval queue with parameters, requester and test evidence. Approve and the promotion submits; reject and it stops.
Owner Your change authority Typically Per production change
- 04
Take the record away
Incidents, availability and response times download as a monthly service report, measured from the same records rather than assembled for the meeting.
Owner Internal audit Typically Monthly
One production change, start to finish
A person decides, and the record keeps the decision beside the outcome
Automation validates, packages and promotes. Promotion waits on the approver you named, however long that takes, and MaxIron approves nothing on your behalf.
- 01 Configuration validated in a non-production environment Done
- 02 Release packaged and versioned Done
- 03 Customer approval recorded Done
- 04 Promotion to production Running
- 05 Post-change checks Pending
Log, streaming while it runs
- 10:31:02 approval recorded by named approver, promotion started
- 10:31:47 configuration applied, release version tagged
- 10:32:10 post-change checks queued
Approver, comment, timestamp and outcome stay on the change record and in the monthly service report. A rejection is recorded in the same place.
Reading the run
- Done
- Completed, with its output on the change record.
- Running
- In progress, with the log streaming.
- Pending
- Queued behind the step above it.
Who signs in to which system
The Portal serves service owners; IBM Maximo serves the workforce
Portal access is sized at the first conversation, because the right-hand column is a named list rather than a user population.
Your Maximo users
Planners, supervisors and technicians. Most will never open the Portal.
Your service owners
IT service owner, change authority, programme owner, internal audit.
Where the work happens
In IBM Maximo, on the work order, the asset and the record.
In the Portal, on the estate around them.
What it replaces
Nothing. IBM Maximo stays the system of record.
The weekly status email, the environment spreadsheet and the pre-audit evidence hunt.
Training required
None. The working day is unchanged.
One session. An approval queue that needs a course is built wrong.
Access
What Portal access involves
- Sign-in
- Your SSO
- Named users
- 4 to 10
- Licence
- Included
- Data shown
- Your estates
- Onboarding
- One session
- Reporting
- Monthly
OpenID Connect against your own identity provider.
Service owners and approvers, not the Maximo user population.
Bundled with MaxIron Cloud and with support contracts.
The same records the MaxIron engineer on shift is reading.
Groups configured, then one walkthrough with your service owner.
Availability and response times measured, not self-reported.
What this needs from you
- A named change authority, because the approval queue waits on a person.
- An administrator of yours to grant groups and decide who sees which estate.
Scope of this offer
Four boundaries on the Portal
Stated here so they can be assessed during evaluation.
Delivered on estates MaxIron operates
The Portal is the operator console for estates we run under MaxIron Cloud and support. Deployment into your own data centre for your team to operate sits outside the offer.
IBM Maximo remains the system of record
Maximo and MAS hold the work orders, assets and history. The Portal holds the estate around them: environments, health, change, approvals and cost.
Coverage follows what we operate
Infrastructure run by another supplier keeps whatever monitoring its operator uses. The board names it as out of scope rather than showing an empty row.
Governance ownership stays with your organisation
Where production change has no named approver, requests queue. The queue makes that visible on day one, and appointing the person is yours to settle.
Questions buyers ask about the Portal
- Do our Maximo users have to learn it?
- Planners, supervisors and technicians work in IBM Maximo unchanged. The Portal is for the IT service owner, the change authority, the programme owner and internal audit.
- Do we see the same data MaxIron sees?
- The same records, scoped to your estates. Health, incident and change records match what the engineer on shift reads, with a last-sync time on every card.
- Who decides what each of our people can see?
- Your administrator, by group: pages, actions and estates, per person. MaxIron does not decide who in your organisation approves production change.
- Can we use the Portal on an estate MaxIron does not operate?
- The Portal shows what we run, so it belongs with MaxIron Cloud and the estates we support. For an estate in your own tenancy, the route is support and partnership.
Walk through the approval queue on a live estate.
Ninety minutes on one screen share: the health board, one approval end to end, and last month's service report.
What to bring to the walkthrough
- The person who approves production Maximo change today
- Your last production change, and how you would prove who approved it and when
- Your current environment list, and when it was last confirmed complete
- The most recent internal audit request, and how long the evidence took to assemble