Energy Sector
Global
3 source references
4 mapped control areas
Regulated SaaS, Private cloud
About this template
Control room work depends on procedures, and those procedures name systems that must stay private. A utility can still want model help with documents, reports and training material. Every check here runs at the gateway before a prompt reaches a provider.
Grid and generation teams want help reading a procedure, drafting a switching narrative or summarizing an outage report. The starter treats each of those as text. It holds no credential for a control system and no permission to call a tool. A switching order stays with the operator who is qualified to give it.
The refusal list aims at the sensitive nouns of this work. A request that names a facility blueprint, a safety interlock or a control system password does not go through. Built-in safety wording adds explosives, weapons and attacks. Each screen looks for the words themselves, so a study of a past attack on a substation is refused with them.
Ahead of those screens, injection wording is checked and then identity. An unauthenticated call is refused, and role claims are taken from verified identity rather than from a supplied header. Redaction masks operator and badge numbers, on-call maintenance numbers, and shift roster references so they do not travel to the provider.
Answers must reach 0.87 combined, 0.78 for relevance and 0.80 for accuracy. They must also cover at least 120 characters and two sentences. Text that misses a floor is refused. The review step is empty, so it is a hook for escalation rather than escalation itself.
NERC CIP, ISO 27001 and NIST CSF 2.0 stand behind the starter. What it produces is input for a compliance file rather than a finding. Rail and maritime starters run the same chain against transport references. Choose this one when the duty in question is bulk electric system reliability.
Source frameworks, standards and obligations
Control areas mapped by this template
Deployment options
Adapt the template in three steps
Review the scope
Confirm that the regions, source references, control areas and deployment options fit your use case.
Adapt the configuration
Open the template in the Verdictan console. Set its policies, thresholds, routing and review requirements for your environment.
Test before deployment
Test each policy outcome. Confirm that allowed, redacted, blocked and reviewed requests behave as expected.
Explore more Industrial & Manufacturing templates
Aerospace Manufacturing
Protect aerospace designs, limit access, screen configured terms, require engineering review and retain limited production evidence.
Chemical Industry
Protect plant and interlock data, limit access, screen configured terms, require review and retain limited evidence.
Electronics Manufacturing
Protect electronics designs, limit access, screen configured terms, check output quality, require review and keep limited records.