The security and governance layer protecting the LabSource on-prem AI server, its credentials, models, tools, data connections and outbound communications.
PHOENIX CIP creates a controlled security boundary between plant and enterprise systems and the local AI environment, giving agents governed access to the context they need without making the AI server an unrestricted control path.
DCS, PLC, historians, CMMS, ERP, databases, engineering files, Git, APIs, SSH and approved internal services.
Identity, role permissions, secrets, network rules, approved tools, egress control and full audit govern every connection.
Local LLMs, RAG, engineering agents, analytics and coding remain inside the customer-controlled environment.
PHOENIX CIP — Critical Infrastructure Protection — is the hardened IT security and governance layer surrounding the LabSource on-prem AI server. It protects the server, its models, credentials, data sources and connected tools by controlling identity, secrets, network access, permissions, data movement and every agent action that crosses the security boundary.
CIP is the security envelope around LabSource.
LabSource can reason, code, analyze and connect to plant systems — but CIP decides exactly what the on-prem server and its agents are allowed to touch.
The Vault is the protected credential layer for LabSource. Database passwords, API keys, SSH credentials, certificates, Git tokens and service accounts are centrally controlled, encrypted and only released to approved tools at runtime. Engineers and agents do not need to copy secrets into code, configuration files or prompts.
The objective is not to isolate AI from the plant. It is to give LabSource useful access through controlled, auditable pathways. CIP allows local AI to work across approved databases, historians, files, Git repositories, APIs, SSH, PowerShell and engineering systems without turning the AI server into an unrestricted privileged user.
LabSource does the thinking. PHOENIX CIP controls the trust. The LabSource server remains inside the customer environment while CIP governs identity, credentials, tools, data access, network communication and outbound exchange around it.
PHOENIX CIP provides governed, auditable access to approved plant and enterprise information while approved external exchanges remain customer-initiated outbound over HTTPS / port 443. It supplies the production, maintenance, logistics and engineering context needed to reason about reliable capacity and revenue exposure without unrestricted equipment control.
Vault, identity, RBAC, secrets, network segmentation, audit and egress controls protect the AI environment.
Approved access to PHOENIX, CMMS, ERP, historians, databases, engineering files, APIs, Git and other internal information sources.
Define who and what can read each source, which tools may be used and what information may leave the site.
Power generation is a priority use case for CIP because AI needs useful plant context without becoming an uncontrolled path into critical systems. CIP provides the governed boundary: approved data sources, Vault-managed credentials, role and facility scope, read/write restrictions, agent/tool permissions, auditability and controlled outbound data exchange.
Expose historian, condition, maintenance and operating information without granting shutdown-capable or unrestricted control access.
Approved external exchanges can remain initiated from inside the facility over HTTPS / port 443, preserving a simple and defensible network boundary.
Use local and approved cloud AI to explain risk, support outage and maintenance decisions, and protect generation capacity while operators retain plant authority.
