MaxIron Portal
Manage Maximo environments, support and releases in one place
Operators sign in through Microsoft single sign-on to see their authorised tenants, or customer environments. They can review service health, investigate an alert and follow an agreed recovery workflow through approval to confirmed resolution. Engineers and service managers work from the same run history and decisions.
IBM Maximo and MAS remain the systems of record for assets, work orders and maintenance history.
Arrange a Portal demonstrationDashboard
Open menu · Dashboard
Administrator view · scroll menu
Cloud, service and delivery position across the selected tenants
Tenant-scoped operating view
Cloud Health Status
Healthy
0 alarms · 2 alerts
Ticket priority summary
14
Open / WIP
31
Unresolved
Alerts & Alarms
0
Alarms
2
Alerts
Uptime · Grafana · Alertmanager
Cloud Costs (Selected Tenants)
£18,426
Projected month end: £27,910
Next ticket to attend
NSU-184 · P2
In Progress · SLA 3.6h
Last ticket touched by customer
NSU-179 · P3
Waiting for Support
Choose by need
Choose Portal for operations and Assist for Maximo user tasks
Portal brings Cloud Manager, Support Management, DevOps Management and AI Workflows together. Assist helps users query Maximo data, prepare actions and carry out role-specific work.
Manage environments, service incidents, releases and AI investigations
MaxIron PortalA shared workspace for operators, engineers and service managers, with access controls for each customer environment.
Ask questions about Maximo records and prepare actions for approval
MaxIron AssistAn assistant in Manage and authorised AI tools, with confirmation before consequential actions.
Key capabilities
See the issue, follow the work and review the outcome
- Review environments and service health
- Cloud Manager and Support Management bring environment inventory, cloud costs, service health, alerts and priority tickets together. Operators see the customer environments their permissions allow them to manage.
- Follow a release from request to outcome
- DevOps Management brings workflows, schedules, logs and approvals into one workspace. Engineers can see who started a run, which parameters were used, where it stopped and whether it completed successfully.
- Supervise AI investigations and tasks
- The AI agent orchestrator assigns work to specialist roles and shows their progress. Operators can follow delegated tasks, respond to requests for human input and review results before publishing. Learning entries remain subject to management controls.
Agent workflow
Follow each AI task and review the result
A support investigation moves through confidence triage, planning, specialist tasks and human review. The role hierarchy shows who is coordinating and which specialist is working. The mission tree connects the original request to delegated tasks, while the operator can see progress and requests for input. Publishing and learn stages follow configured review controls.
AI Workflows
Open menu · AI Workflows
Administrator view · scroll menu
Role assignment, stage history, delegated work and human input
Synthetic support investigation
Recurring integration failures
Stage 6 of 11 · Execute
- Lobby Completed
- Ingest Completed
- Triage Completed
- Plan Completed
- Hierarchy Completed
- 6 Execute In progress
- 7 Post-Exec Pending
- 8 Review Pending
- 9 Publish Pending
- 10 Learn Pending
- 11 Complete Pending
Role hierarchy
3 active rolesMission evidence
WorkingMaximo Specialist · completed
Correlated failed integration records with affected work-order updates.
Platform Engineer · active
Comparing endpoint health with the last approved deployment.
Human input required
Confirm whether the maintenance window includes a controlled service restart.
Demonstration scenario
Investigate an integration failure and approve the recovery
Using illustrative data, we show how an operator investigates an alert in one customer environment, follows the delivery workflow and asks a specialist agent to review the evidence.
This is a qualification demonstration against representative work, not a named customer result. Anonymised customer engagements and reference conversations under NDA sit in the case studies.
What we walk through
- Sign in as an operator with access to one selected tenant.
- Open an integration alert and start the agreed recovery workflow.
- Hold the protected step for a named approval, then follow an agent task through human review.
Pass condition
The demonstration checks that the operator stays within the authorised environment and that the protected step waits for its named approver.
Evidence retained: Workflow parameters, initiator, live and historical logs, approval decision, timestamps and final state.
Boundary that remains: IBM Maximo retains the maintenance record. The designated approver decides whether the recovery can proceed.
Buying information
How MaxIron Portal is sold and introduced
Pricing is agreed against your environments, operating responsibilities and required workflows. A demonstration covers one customer environment, a delivery workflow and an AI task before we confirm scope.
Arrange a Portal demonstration- Price
- Quote on request.
- Included tools
- Cloud, Support, DevOps and AI tools within Portal, configured for the agreed scope.
- Deployment
- A browser workspace configured for your customer environments, identity provider, permissions and workflows.
- Compatibility
- IBM Maximo and MAS estates, with Microsoft single sign-on for user identity.
Questions about MaxIron Portal
- What is MaxIron Portal?
- MaxIron Portal brings Cloud Manager, Support Management, DevOps Management and AI Workflows into one browser workspace. These tools share customer environment access, user identity and permissions.
- Is MaxIron Assist the same as Portal?
- Assist helps users work with IBM Maximo data in Manage and through authorised AI tools. Portal is the workspace for managing environments, support, delivery workflows and supervised agent runs. Assist can perform role-specific work within Portal.
- How is access controlled?
- Users sign in through Microsoft single sign-on. Permissions determine which customer environments, pages and actions each group can access. The illustrative menu shows the administrator view; the live menu follows the signed-in user’s permissions.
Defined scope
System ownership, access and approvals
Portal supports operating work around IBM Maximo. These responsibilities are agreed for each deployment.
Maximo remains authoritative
IBM Maximo and MAS remain the systems of record for assets, work orders and maintenance history. Portal operates the technology and processes around them.
Access follows configured policy
Microsoft single sign-on identifies the user. Authorisation checks the page, action and customer environment against configured groups and policies.
Approval responsibilities are agreed upfront
Configured workflows identify the person who can approve a protected step. Requests for input and review decisions remain visible to the operating team.
See how Portal would support your operating team
Bring one customer environment, a recurring delivery task and the approval it requires. We will demonstrate the operating workflow and confirm which Portal capabilities fit.
Bring this to the first call
- The cloud and MAS environments one operator is responsible for
- A repeat delivery workflow and its named approver
- An agent task that needs a visible human review point