Specialist augmentation
Experienced Maximo specialists inside your programme.
MaxIron supplies named architects, functional consultants, developers, data specialists and platform engineers for defined work packages. Your programme lead sets priorities and accepts the work; the engagement records deliverables, governance, an end date and a named handover receiver.
Delivery responsibility
Direction, risk and acceptance define the engagement
A work package sits inside your programme and governance. A delivery engagement gives MaxIron the complete scope, sequence and delivery risk.
A defined part of your delivery
Your programme continues. MaxIron is responsible for one named part of it, inside your governance, against a written scope.
A MaxIron delivery engagement
Our team, our sequence, acceptance criteria you signed, a price and a date. We carry the delivery risk.
Who directs the work
You direct the programme. MaxIron directs the part it holds, and brings that work through your change board and your sequence.
We do, against a scope and acceptance criteria you signed. We come back to you at gates rather than at stand-ups, and a change of priority is a change of scope.
Who carries the delivery risk
MaxIron, for the agreed part. Whether the wider programme lands stays with you.
We are, against the acceptance criteria. If the integration does not pass its test, that is ours to fix inside the agreed price and date.
What it is priced on
Professional services for that part, with the scope, the people and the end condition in the engagement letter.
The outcome, as a fixed price or a capped estimate against a defined scope, with a change mechanism for anything outside it.
When it is the right call
The programme is live, your team owns the estate, and one part of the delivery needs a team that will finish it. The window can be a quarter or several years.
The work is a defined block with an acceptance test: an upgrade, a migration, an integration rebuild. You want a price and a date rather than a rate and a rota.
Accountable route
Three routes for the work
The estate needs a named owner and working governance before either delivery route can succeed.
A defined part of your delivery
Talk about a delivery part →Operating context
Your programme is already running. A named part of it needs a team that will own that part through to acceptance, inside your governance, for a quarter or for several years.
Planning consideration
Asking for a role with no named deliverable. A request for a Maximo developer for six months, with nothing they are responsible for finishing, drifts into permanent staffing.
MaxIron delivery engagement
See how delivery is scoped →Operating context
The work is describable end to end and testable at the end: a MAS upgrade, a data migration, an integration rebuild. You want the risk on our side of the table.
Planning consideration
Fixing the price before the scope is testable. Where the scope is still moving, run a short paid discovery and price the delivery afterwards.
Neither, yet
See a managed arrangement →Operating context
Nobody owns the estate. No design authority, no functioning change control, no named platform owner, so any senior person you insert absorbs decisions that should be yours.
Planning consideration
Handing MaxIron a part of the delivery when nobody on your side owns the estate. The gap is still there when that part is finished, so settle accountability first.
How the exit is tested
Four checks, agreed at kick-off rather than in the final fortnight
The handover test is written at the start, so the part MaxIron holds has an end. Every check is witnessed by someone on your side.
- X1
Your named receiver runs the runbook unaided
- Passes when
- The person named at kick-off performs the procedure end to end, on a real change rather than a rehearsal, with our specialist watching and not intervening.
- Witnessed by
- Your platform owner
- X2
Every non-obvious decision has a record
- Passes when
- One decision record per rejected alternative, filed where your team already keeps them rather than in our tooling.
- Witnessed by
- Your design authority or technical lead
- X3
Open items and known risks are listed, not tidied away
- Passes when
- A written list of what is unfinished, what we found and did not fix, and what we would do next.
- Witnessed by
- Your project sponsor
- X4
The end date holds
- Passes when
- The date agreed at kick-off is met, or an extension is proposed in writing with a reason and a new end date. Not a rolling renewal.
- Witnessed by
- Your sponsor and the MaxIron engagement owner
The shape of the workstream
What you are actually buying
The engagement letter names the work package, individual, governance, notice period, end date and client-side receiver.
-
Typical length
One to two quarters
Scoped around a named outcome with a date, and extended only in writing against a new one.
-
Seniority
Senior only
The people on the workstream have held the same responsibility on a live estate.
-
Priced on
A day rate per named individual
With a notice period and an end date in the engagement letter.
-
Named before contract
Yes, with CVs
You interview the individual. A substitution is proposed, not made.
-
Governance
Yours
Your stand-ups, change board, architecture review and service management. We do not import a parallel process.
-
Assurance
MaxIron delivery standards
Certificates and the Trust Centre are on the recognition and security pages.
What this needs from you
- A named person with real time in their week to receive the handover and do the work at least once
- A working change board, or a decision on who signs a production change while we are there
- Access on day one. A specialist waiting three weeks for a login is a specialist you are paying to wait
- The last four weeks of the engagement protected for handover rather than backfilled with new scope
Specialist roles
The specialist holds a work package inside your programme
Your programme lead retains priorities, governance and acceptance. MaxIron names the specialist, their deliverables and the client-side receiver before the engagement starts.
Client programme lead
Direction and approval
Named MaxIron specialist
Delivery and evidence
Client-side receiver
Acceptance and handover
- Solution architects
- Design authority through a defined phase: upgrade decisions, cross-suite sequencing, and whether a request belongs in configuration or in code. Where a decision should sit with your own architect, they say so rather than quietly taking it.
- Functional consultants
- Work management, inventory, procurement, mobile and reliability processes. Where the constraint is the process itself rather than the build, that is business process optimisation.
- Developers
- Automation scripts, the Maximo Integration Framework, REST integrations and reports. Where the estate cannot build, test and promote at all, that is customisation modernisation.
- Data specialists
- Migration, cleansing, hierarchy and criticality design. A defined migration is usually better bought as data migration with an acceptance test.
- MAS platform engineers
- OpenShift, environment hygiene, deployment and operational readiness, including in your Azure, AWS or OCI subscription. Where you want a productised platform instead, that is MaxIron Cloud.
- Application support specialists
- Incident, change, release and runbook discipline inside your service management, including the handover that lets your team hold the rota afterwards.
Fit assessment
Three conditions for a clean exit
The estate needs an owner, a receiver needs time for handover, and the final four weeks need protection from new scope.
The estate needs a named owner
With no design authority, no change control and no named platform owner, a senior specialist absorbs decisions that should sit with you. The accountability-first route settles those roles before a work package starts.
Knowledge transfer needs somebody to transfer it to
Acceptance check X1 requires your named receiver to run the procedure unaided. Where your team has no capacity to absorb the handover, we plan a support relationship with an explicit operating boundary.
The exit costs you something in the last four weeks
Reading, running the runbooks and taking ownership of open risks all take your people away from other work. The engagement reserves that time so the agreed end date can hold.
Specialist augmentation, frequently asked questions
- How does a defined part of a programme differ from a MaxIron delivery engagement?
- Direction, delivery risk, pricing and acceptance separate the two. For a work package, your programme continues and MaxIron is responsible for one named part inside your governance. For a delivery engagement, MaxIron runs the complete scope against acceptance criteria at a fixed price or capped estimate.
- Which roles can you provide, and do we choose the individual?
- Six shapes, all senior: solution architects, functional consultants, developers covering the Maximo Integration Framework and automation scripts, data specialists, MAS platform engineers and application support specialists. You see CVs and interview the individual before contract, and a substitution is proposed rather than made.
- Is knowledge transfer part of it, or an extra?
- Part of it, during the work: pairing on real change, runbooks written while the reasoning is fresh, and a decision record for every rejected alternative. Acceptance check X1 requires a named person on your side with time to receive it.
- When is augmentation the wrong answer?
- When nobody owns the estate. With no design authority, no change control and no named platform owner, a senior specialist absorbs decisions that should be yours. In that shape we propose application support with an explicit boundary, or a managed arrangement where accountability is written down.
Define the work package and specialist role.
Bring the backlog, acceptance criteria and required dates. We will identify the discipline, named deliverables and receiver needed for a scoped engagement.
Bring this to the first call
- The named outcome and the date it has to be finished by
- The backlog itself, however rough, and which items are blocked on depth rather than on time
- Your governance: change board cadence, design authority, and who signs a production change today
- The named person who would receive the handover, and how much of their week is realistically free
- Whether the estate has an owner today, and who your team would go to if we were not there