This website uses cookies
Read our Privacy policy and Terms of use for more information.
Overview
The agent audits construction work packages against the canonical AWP standard. It scores each package against CII SR19-01 v2.0 (60 data requirements across 19 categories), extending CFIHOS V2.0 for construction execution. The agent runs inside the customer's IBM watsonx Orchestrate environment and reads from / writes to the customer's IBM Maximo MAS instance under the customer's own authorisation.
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 work orders, work packages, service requests, asset records, and document attachments needed for compliance scoring.
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
→ "Audit work pack [ID] against CII SR19-01 v2.0."
→ "What is the compliance status of work pack [ID]?"
→ "Which CII SR19-01 categories does this work pack address?"
→ "Create a service request to close compliance gap [GAP-ID] on work pack [ID]."
→ "List all open compliance findings on work order [ID]."
The agent supports natural-language questions about work-pack compliance. It does not advise on radiation, plant operations, or any regulated technical discipline.
Audit-bundle format
Every query produces an audit bundle with the following fields:
The audit bundle is exportable on request. Format aligns with ISO 19650-4 Clause 7 evidence requirements.
Integration steps
Behaviour and limits
The agent never auto-fires writes to Maximo. Where a query contains a write intent, the agent surfaces the exact Maximo affordance for the customer to confirm.
The agent emits structured outputs for compliance queries (scored against CII SR19-01 v2.0) and natural-language responses for explanatory queries.
Where retrieval cannot find a confident answer, the agent returns a guarded boilerplate rather than fabricating a response.
Service Level: see the .
Status: see the .
Terms: see the .
Last updated: 8th May 2026