Product · Intelligence · In IBM MAS Manage
One work order, four desks, a confirmation at each.
MaxIron AI Crew supports work-order and asset steps inside IBM MAS Manage, one role at a time. Each crew member works under the signed-in user's own Maximo authorisation, prepares the step rather than taking it, and stops where the next role begins.
Two jobs, one procurement decision
Advice to one person, and work that crosses four desks
Two MaxIron products, sold separately because the governance question differs.
MaxIron Assist
Advice at the moment of the task, answered from your own written procedure.
MaxIron AI Crew
Scoped work inside IBM MAS Manage, one role at a time, each step confirmed by the person who holds it.
The question it answers
How is this task done here? One user, one question.
Which role holds this step, what it needs in front of it, and who holds the next one?
Whose authorisation it uses
The signed-in user's own. No elevated account behind the reply.
The signed-in user's own, per role. Audit names a person, never a service account.
What it may change
A record the user could change themselves, prepared, shown, then confirmed.
The same, one role at a time. Higher-impact execution goes to a governed workflow.
Where it stops
At the answer. What the user does next follows their procedure.
At the role boundary, naming the role that holds the next step.
Four desks, one work order
A gearbox change, desk to desk, over three days
Read the stop at the end of each role: that is where the crew member hands back.
Work order 41-2288, illustrative
- Planner, Tuesday 09:10
- The last two failures, both long-lead spares on site, and this site’s job plan.
- Planner confirms
- Applies the job plan, adds a coupling check line, schedules it. Releasing belongs to the approver.
- Approver, Tuesday 16:40
- The estimate, two jobs it displaces this week, two prior interventions in nine months.
- Approver confirms
- Approves with one line on displacement, on the work order rather than in sent items.
- Stores confirms, Wednesday 08:20
- Reserves the site-store line, flags the line on order outstanding. The requisition belongs to purchasing.
- Supervisor, Thursday 15:05
- Corrects the failure code on the drafted completion and closes the job.
- On the work order
- Who did what, in order, what it waited on and which role held it.
Reading the trace
- Assembled
- Gathered under that role holder's own authorisation.
- Confirmed
- The role holder confirms. Nothing is applied without this.
- Written
- What landed on the work order in IBM MAS Manage.
Before security review asks
Six answers a security review will test
- Identity used
- The signed-in user's
- Service accounts
- None
- Reads
- On request
- Record changes
- Prepared, shown, confirmed
- Role boundary
- A hard stop
- IBM application images
- Unchanged
Every read and change runs under that person’s Maximo authorisation.
No shared privileged identity, so audit names a person.
Where the user cannot see a record, neither can the crew member.
Retained with the user, the change and the time.
Where the next step belongs to a role the user does not hold, it names it.
AI Crew runs beside IBM MAS Manage and complements it.
What this needs from your side
- Security groups tight enough that a role boundary exists to inherit
- A named approver per job type, including the informal steps
- Managed browser rollout to approved desktops
Run this on one work order
Four statements, taken in order
Take a job from last month that crossed three roles. Stop at the first false statement.
- 1
The security groups let each role see what it needs and no more.
- 2
Every step had a named person accountable, including the informal ones.
- 3
The work order shows what the job waited on, and which role held it.
- 4
Somebody could tell you today who approved it and what they saw.
If you stopped early
The statement you stopped at is Maximo configuration or delegation work, and it precedes rollout.
If every statement held
The handoffs are governed already, so AI Crew removes the assembling around each decision.
Scope and boundaries
Three limits that decide whether this is worth doing yet
Where one of these matches your estate, address it first.
It inherits your authorisation model, gaps included
Part of MaxIron Enterprise AI for IBM MAS Manage, alongside AI Engine: what a Maximo user meets while AI Engine coordinates delivery, operations and governance agents. Broad security groups mean a broad crew, so the boundary you hoped to buy may not exist yet; tightening them is Maximo configuration work that precedes rollout.
It cannot shorten a decision waiting on a person
Where the approver is on leave, the work order waits. The wait becomes visible on the record, but shorter cycles come from delegation change.
On-screen action needs a managed rollout you control
Acting on screen inside Manage needs managed browser deployment to approved desktops. Until then AI Crew assembles, guides and navigates. Execution across roles sits with MaxIron AI Engine.
MaxIron AI Crew, frequently asked questions
- Does it act as the user, or as a service account?
- As the user, under their own Maximo authorisation. It cannot read or act beyond what that person could.
- What is recorded when a crew member is used?
- The user, the time, the proposal and the confirmation. Retention and access are agreed with your security team before deployment.
- How is this different from MaxIron Assist?
- MaxIron Assist answers one user’s question in context. AI Crew handles work crossing roles, and how each step hands back.
- Is MaxIron AI Crew an IBM product?
- No. It is a MaxIron product for IBM MAS Manage environments and complements the IBM platform. See enterprise AI governance.
Bring one work order that crossed four desks.
Pick a real job from last month that took longer in the gaps than in the work. We map it desk by desk: what each crew member assembles, what each person confirms, where it stops, and where Assist is the cheaper answer.
Bring this to the first call
- One work order crossing at least three roles, slower than it should have been
- Security groups for those roles, so we can be specific about visibility
- Approval routing for that job type, including the informal steps