This website uses cookies
Read our Privacy policy and Terms of use for more information.
Overview
This agent tells you what your facility must record and hand over before it can commission. It sets out the CII SR19-01 DR310 commissioning data requirements from the Construction Industry Institute (CII), sub-code by sub-code. It gives the totals of the Capital Facilities Information Handover Specification (CFIHOS) V2.0 handover lists for construction and commissioning. Name a discipline (electrical, mechanical, piping, instrumentation, civil, structural or HVAC) and the totals narrow to it. You use it from your IBM watsonx Orchestrate environment, and Vistergy hosts it. Code builds the assessment from the published standard, and a model writes it up. If a draft states a figure the assessment does not hold, code serves its own text instead.
Does it need IBM Maximo? No.
No system connection is needed. Unconnected, the agent answers what commissioning readiness requires, from CII SR19-01 DR310 and the CFIHOS V2.0 handover lists. Once IBM Maximo is connected, it can look up your assets, work orders, service requests and documents. It can count your work orders, assets or service requests, and check a named asset's CFIHOS attribute completeness. The readiness assessment itself reads the published standard, not your records.
What you provide, if you connect IBM Maximo
This section applies only if you choose to connect a system of record. 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 Application Suite (MAS) instance URL. The base URL of your Maximo SaaS or on-prem deployment, for example https://yourcompany.manage.suite.maximo.com.
Authentication method. Service account with a Maximo API key (the supported integration method for Maximo Manage 8.8 and later). Your Maximo administrator creates a dedicated Maximo user with the read and write entitlements the agent surfaces (see "Maximo entitlements" below), issues a long-lived API key for it, and pastes the key into the dashboard.
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 work orders, service requests, asset records, and document attachments.
Write on service request and work order creation (the actions 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?" (what DR310 and the handover lists require)
→ "What must the electrical systems hand over before commissioning?" (electrical, mechanical, piping, instrumentation, civil, structural or HVAC)
→ "What does turnover date slippage need recorded?"
→ "What must test packages record before commissioning?"
→ "What does punch list resolution need recorded?"
The agent sets out what DR310 and the handover lists require. The assessment gives no score, count or date for a facility. It reads the published standard, not your records. 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.
Integration steps
Recommended setup in watsonx Orchestrate
There are two ways to use the agent.
Chat with it directly. It works as supplied. Its standards answers are built from the published standards, and every answer has an audit bundle 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. Asked to create a service request, it proposes one and writes nothing until your operator confirms.
The agent sets out what readiness requires. The commissioning go or no-go decision stays with the engineer, operator or regulator. The agent issues no verdict.
The agent reports the system-of-record (Maximo) connection state honestly and never implies a connection that does not exist.
Service Level: see the Vistergy Support page.
Status: see the Vistergy Status page.
Terms: see the End User Licence Agreement.
Certifications: Vistergy is certified to ISO 9001:2015 (certificate 526732026) and to ISO/IEC 27001:2022 and ISO/IEC 42001:2023 (certificate 528322026). Details at vistergy.com/legal.
Last updated: 29th October 2026