This website uses cookies
Read our Privacy policy and Terms of use for more information.
Overview
This agent tells you whether your facility is ready to commission, gate by gate, with the evidence behind every call. It reviews readiness discipline by discipline (mechanical, electrical, instrumentation, controls, safety, environmental, operational) against the canonical commissioning-completion lifecycle, CII SR19-01 DR310, and returns a readiness score with a ranked list of blockers, each tied to its source evidence. It runs inside your IBM watsonx Orchestrate environment, and reads from your IBM Maximo MAS instance under your own authorisation. It is deterministic and standards-grounded.
What you provide
To connect the agent to your environment you provide three things, all entered through your per-tenant dashboard at https://dashboard.vistergy.ai/{instance_id} (the link is returned in the IBM watsonx Orchestrate provisioning response and never exposed publicly).
Maximo MAS instance URL. The base URL of your Maximo SaaS or on-prem deployment, for example https://yourcompany.manage.suite.maximo.com.
Authentication method. Choose one:
Service account (recommended for production). A dedicated Maximo user account with the read and write entitlements scoped to the affordances the agent surfaces. See “Maximo entitlements” below.
Maximo API key. If your Maximo deployment supports long-lived API keys, paste the key value into the dashboard.
SaaS browser session. Suitable for evaluation only. The dashboard accepts the cookie set from a recent Maximo browser session.
Credential rotation cadence. Vistergy recommends 90-day rotation for service accounts and Maximo API keys. Rotation is performed by your Maximo administrator, then refreshed in the same dashboard field; no Vistergy intervention required.
Maximo entitlements (service account or API key). The Maximo administrator grants the connecting account these scopes:
Read on commissioning manifests, DR310 completion records, work orders, test packages, punch-list items, asset records, and document attachments needed for readiness assessment.
Write on service request creation and work order updates (the affordances the agent surfaces). Writes never auto-fire; the agent surfaces the proposed Maximo action for your operator to confirm.
What Vistergy never asks for. The agent does not require, and Vistergy will never request:
Your IBM Cloud account credentials.
Credentials for any system outside your Maximo deployment.
Any data for model training. Customer queries are not used to train any model, ever. See the End User Licence Agreement and Data Processing Addendum for the full data handling boundary.
Supported queries
→ "Is this facility ready to commission?" (or a named sub-system)
→ "What is blocking commissioning for the electrical systems?" (any discipline: mechanical, electrical, instrumentation, controls, safety, environmental, operational)
→ "Show me the turnover date slippage for this facility."
→ "What test packages remain incomplete before commissioning?"
→ "What is the punch list resolution rate?"
The agent answers readiness questions deterministically from DR310 completion data, discipline by discipline, with a readiness score and a ranked list of evidence-linked blockers. A question outside the commissioning-readiness scope returns a brief, agent-specific message saying so, rather than an inferred answer. Facility construction-state from satellite imagery is the Vistergy Facility Intelligence agent's domain, not this agent's. The agent does not advise on radiation, plant operations, or any regulated technical discipline.
Audit-bundle format
Every query produces a session-linked audit record capturing:
The audit bundle is exportable on request. Format aligns with ISO 19650-4 Clause 7 evidence requirements.
Integration steps
Recommended setup in watsonx Orchestrate
There are two ways to use the agent.
Chat with it directly. It works as supplied. Every answer is grounded in the published standards, carries source citations, and an audit bundle is available on request.
Add it as a collaborator inside your own Orchestrate agent. If you compose it into an agent you build, apply the tested configuration below so your agent behaves the way this one was designed to.
Agent style: select ReAct. Commissioning readiness is a high-stakes application, and ReAct is the style IBM recommends for high-stakes applications.
Paste the tested instructions below into your agent's instructions, keeping the collaborator name as it appears in your collaborator list.
Starter prompts: use the supported queries above as your starter prompts. They are written to return grounded, sourced answers first time.
Leave "Chat with documents" off for governed use. Uploaded-document answers bypass the agent's source-traced retrieval.
Tested instructions:
Route every readiness or commissioning-gap question to the Vistergy Commissioning Readiness collaborator, including questions about systems or sub-systems you do not recognise, without asking a clarifying question first. Route system-of-record questions (whether the workspace is connected to Maximo, whether records are aligned) to the same collaborator. Present its responses exactly as given, with their source attributions and any audit-bundle content. When it reports that something is not found or has no result, that is the answer: never turn a not-found into a status, score, or verdict, and never add a conclusion it did not state. It reports the system-of-record connection state honestly; surface that response verbatim and never imply a connection that does not exist. Never answer from your own knowledge. Keep responses concise.
For teams building with the watsonx Orchestrate Agent Development Kit, the same configuration as an importable agent definition:
spec_version: v1 kind: native name: my_commissioning_assistant display_name: My Commissioning Assistant llm: watsonx/ibm/granite-4-h-small # or your preferred watsonx model style: react instructions: | Route every readiness or commissioning-gap question to the Vistergy Commissioning Readiness collaborator, including questions about systems you do not recognise, without asking a clarifying question first. Route system-of-record questions to the same collaborator. Present its responses exactly as given, with their source attributions and any audit-bundle content. When it reports that something is not found or has no result, that is the answer: never turn a not-found into a status, score, or verdict, and never add a conclusion it did not state. It reports the system-of-record connection state honestly; surface that response verbatim and never imply a connection that does not exist. Never answer from your own knowledge. Keep responses concise. collaborators: - vistergy_commissioning_readiness # the agent as named in your instance
Behaviour and limits
The agent never auto-fires writes to Maximo. Where a query contains a write intent ("create an SR for..."), the agent surfaces the exact Maximo affordance for the customer to confirm.
The agent quantifies readiness and surfaces the blockers with their evidence. The commissioning go/no-go decision remains with the engineer, operator, or regulator; the agent measures the gap, it does not issue the verdict.
The agent reports the system-of-record (Maximo) connection state honestly and never implies a connection that does not exist.
Where data cannot support a confident readiness call, the agent returns a guarded response rather than fabricating one.
Service Level: see the Vistergy Support page.
Status: see the Vistergy Status page.
Terms: see the End User Licence Agreement.
Last updated: 23 June 2026