This website uses cookies
Read our Privacy policy and Terms of use for more information.
Overview
This agent confirms whether your facility handover package is complete enough to sign off before an asset enters operations. It gives you an overall status per package: pass, partial, fail or not assessed. You also get a completeness score and the missing documents named, with document-level evidence. It checks each package against the documents its handover event requires, mapped to ISO 19650-4 Clause 7.3 (Continuity). The requirements come from the Capital Facilities Information Handover Specification (CFIHOS) V2.0 reference. That reference holds over 6,500 document requirements, six contract-scenario templates spanning over 140 entities, and five handover events. You use it from your IBM watsonx Orchestrate environment, and Vistergy hosts it.
Does it need IBM Maximo? No.
No system connection is needed. Ask the agent what the standards require, or give it a handover package record in the conversation. It returns the completeness score with the gaps and the evidence. Connecting IBM Maximo is optional. Connect it when you want the agent to read your live records. Once writes are enabled, it can also raise the service request that closes a gap, after you confirm it.
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 handover packages, asset records, document attachments, and document-status records needed for completeness scoring.
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
→ "Validate handover package [ID] against CFIHOS V2.0 for its handover event."
→ "What is the completeness score for handover event [ID]?"
→ "Which required documents is handover package [ID] missing?"
→ "List the missing CFIHOS V2.0 document requirements for asset [ID]."
→ "Create a service request to close handover gap [GAP-ID] on package [ID]."
The agent supports natural-language questions about facility-handover completeness and compliance. It 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, scoped per handover event as well as per tenant. The handover event is the unit at which findings carry regulator meaning.
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. Compliance 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 question in this agent's domain to the Vistergy Facility Handover Compliance collaborator, including questions about items you do not recognise, without asking a clarifying question first. 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_handover_assistant display_name: My Handover Assistant llm: watsonx/ibm/granite-4-h-small # or your preferred watsonx model style: react instructions: | Route every question in this agent's domain to the Vistergy Facility Handover Compliance collaborator, including questions about items you do not recognise, without asking a clarifying question first. 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_facility_handover_compliance # 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 action for the customer to confirm.
The agent emits a structured completeness score per handover package, scored against CFIHOS V2.0 and mapped to ISO 19650-4 Clause 7.3. Each document's status is compared as a CFIHOS document status code, and only the same code meets it. A status that is not a CFIHOS code is reported as not assessed, never as complete. Explanatory questions get natural-language responses.
Where retrieval cannot find a confident answer, the agent returns a guarded boilerplate rather than fabricating a response. The package check's results are written by code, never by a model. A model writes answers to general standards questions from the structured standards data, and checks run before release. Queries outside its scope return a deterministic refusal.
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