TURN ASSET HEALTH
INTO RELIABLE CAPACITY.
TURN CAPACITY
INTO REVENUE CONFIDENCE.

PHOENIX connects product demand, machine condition, maintenance, operations, logistics and local AI so teams can see what is limiting production, which work protects throughput, and where capacity or revenue is at risk.

See the Deployment

Your Data. Your Models.
Your Industrial Intelligence.

Bring your people, plant data, machine evidence and local AI into one coordinated knowledge experience. Run multiple local LLMs against approved context, retain conversations and expert knowledge on-prem, and let agents select and cross-check the model best suited to each engineering, reporting or coding task.

Explore PHOENIX
AI Server Deployment PHOENIX CIP LabSource Why On Prem Architecture Industries
What PHOENIX Delivers

A Secure Industrial Intelligence Environment

PHOENIX creates a private industrial intelligence environment that connects physical asset evidence to production demand, maintenance execution and capacity. Local models, AgentSWARMS, CIP, contextual memory, reporting and app-building tools turn that context into decisions that protect throughput and revenue.

Why Put AI On Prem?

Keep your industrial intelligence where it belongs.

Your competitive advantage is not just a motor waveform. It is the combination of operations, maintenance, engineering knowledge, production context, recipes, work history and machine data. On-prem AI lets you use that combined knowledge without making the public cloud your plant's primary intelligence layer.

01

KEEP DATA LOCAL

Sensitive plant information, documents, embeddings, RAG indexes and model workloads can remain inside the customer's own network.

02

BUILD CAPACITY CONTEXT

AI can connect asset condition, maintenance, production, engineering, logistics and commercial priorities to understand what actually limits reliable capacity.

03

CONTROL ACCESS

Models do not receive unrestricted network access. CIP controls the identities, tools, credentials, sources and actions permitted for each agent.

04

GROW YOUR OWN INTELLIGENCE

Domain experts can create reusable agents, Python or HTML apps, reports, analytics and decision logic while the knowledge and history remain on-prem.

On-Prem AI Server Deployment

The hardware and software arrive as one industrial AI environment.

PHOENIX works with the customer to size and deploy the on-prem compute platform required for local model inference, plant data access, RAG, engineering agents, coding and analytics.

What the local AI server does

  • Runs multiple private/local LLMs for engineering, analysis, coding and reporting without ongoing external per-token inference charges when local models are used
  • Uses agents to select the model best suited to each task and, where required, hand results to a second model or specialist agent for verification
  • Hosts LabSource, PHOENIX CIP, local RAG indexes, contextual memory and approved agent services
  • Connects through CIP to approved internal databases, historians, DCS/PLC data, CMMS, ERP, files and APIs
  • Retains chats, prompts, retrieved context, model requests, results and expert corrections against the relevant domain, project, asset and requirement
  • Supports local reporting, contextual prompts, AI suggestions and controlled Python / HTML application development

Entry-level deployment scope

A typical starting deployment combines enterprise GPU compute, ECC memory, mirrored NVMe storage, Linux, containerized inference services, LabSource and PHOENIX CIP.

Customer infrastructure: customer provides the approved rack/location, network connection, UPS/power and suitable cooling/environment. Facility electrical work, rack changes and dedicated HVAC/cooling are excluded unless separately scoped.

Launch support: LabSource / PHOENIX can provide an on-site FTE for the first month, renewable monthly, to configure the environment, set up models/RAG/agents, optimize performance, test workflows and train users.

PHOENIX Asset Health Network

High-Resolution Sensing That Gives AI Better Evidence

The PHOENIX AI stack is strongest when it has access to high-quality physical data from the assets themselves. PHOENIX combines autonomous sensing, long-range wireless connectivity and high-resolution vibration analytics to create a continuously available asset-health data layer.

VIBE

High-Resolution Vibration Analytics

Capture machine behavior at the level required for real rotating-equipment diagnostics, not just simple threshold alarms.

  • High-resolution time waveform capture
  • FFT analysis across X / Y / Z axes
  • RMS, peak and trend analytics
  • RPM / tachometer correlation
  • Gearmesh, harmonics and sideband analysis
  • AI-assisted fault interpretation and evidence-based recommendations
AHN

Asset Health Sensor Network

Create a persistent digital health layer across critical assets so condition data becomes part of the wider operational and maintenance context.

  • Vibration, pressure, airflow, oil quality, temperature and other condition sensors
  • Autonomous collection across distributed assets
  • Asset / component / sensor hierarchy
  • Local edge collection with PHOENIX integration
  • Condition history available to reliability and AI agents
  • Supports mining, manufacturing, utilities and remote industrial environments
BLE

Long-Range Bluetooth

Extend low-power wireless sensing across industrial facilities without the cost and complexity of wiring every monitored point.

  • Long-range BLE gateways for industrial coverage
  • Multi-gateway visibility and intelligent collection paths
  • RSSI-based gateway selection and fallback logic
  • Supports distributed mobile and fixed sensors
  • Reduced installation effort versus traditional wired networks
  • Practical for hard-to-reach and geographically spread assets
From Sensor to Intelligence

AI That Understands What the Machine Is Doing — and Why

The value is not the sensor alone and it is not the LLM alone. The advantage comes from binding physical asset evidence to maintenance, operations, production and engineering context, then letting local AI reason across the combined picture.

01 · Sense

Capture Physical Evidence

High-resolution vibration, airflow, pressure, oil quality, temperature, speed and other asset-health signals create a trusted machine-state record.

02 · Context

Connect the Plant Reality

PHOENIX CIP securely connects approved maintenance, process, production, historian, controls, CMMS, ERP and engineering sources to that asset evidence.

03 · Reason

Use Local LLMs

LabSource runs local models and specialized agents that can correlate machine behavior with operating state, work history, procedures, drawings and other approved context.

04 · Build

Create Your Own Intelligence

Engineers can turn recurring analysis into reusable agents, dashboards, calculations, reports, alerts and local applications without sending the plant's full knowledge base to the cloud.

Build intelligence around your own machines, your own data and your own engineering methods.

Local AI can learn the operating context

Instead of asking a generic model “what does this vibration peak mean?”, LabSource can evaluate the vibration against actual RPM, load, VFD frequency, maintenance history, oil condition, machine geometry, process state and recent operating changes.

Engineers can code on top of that context

Use local coding agents to build plant-specific calculations, workflows, connectors, dashboards, reports and decision modules. The code can work directly with approved internal data sources through CIP-controlled tools.

Industries

Industrial intelligence built around the way your plant creates capacity.

PHOENIX connects machine evidence, maintenance, operations, planning and local AI differently for each industry — with the same goal: protect reliable capacity, production commitments and revenue.

Explore Industries
PHOENIX Industrial Intelligence Expanded

Access a complete suite of plant intelligence across your entire operation.

PHOENIX already connects physical assets to digital intelligence. The new on-prem AI architecture adds the missing layer: a local AI server that can reason across machine condition, maintenance history, operations, production and engineering knowledge while keeping access under plant control.

1

Connect Plant + Asset Data

High-resolution vibration, asset-health sensors, long-range BLE, PLC, DCS, historian, CMMS, ERP, databases and engineering files.

2

PHOENIX CIP

Control identity, vaults, tools, permissions, facility scope and data routing.

3

Local AI Server

LabSource runs local models, industrial RAG, engineering agents, coding and analytics on customer-controlled compute.

4

Engineer Decisions

Turn cross-system plant context into explanations, recommended actions, reports, code and applications.

5

PHOENIX UI

Turn approved plant context into work-execution visibility, lifecycle economics and operating / capital decisions.

How The Platform Works

PHOENIX CIP + LabSource

Two different on-prem layers with two very different jobs: CIP controls access to the plant. LabSource is where the AI reasons, analyzes and builds.

What is PHOENIX CIP?

PHOENIX CIP — Critical Infrastructure Protection — is the secure industrial access and governance layer between AI and your plant systems.

It controls what AI can see, which systems and tools it can use, which credentials it can access, whether an action is read-only or write-enabled, and what information is allowed to leave the facility.

In simple terms: CIP is the security and control boundary for industrial AI.

  • Connects to PLC, DCS, SCADA and historians
  • Connects to CMMS / EAM, ERP, databases and APIs
  • Controls Git, SSH, PowerShell and server access
  • Manages secrets and credentials through a vault
  • Applies facility, user, role and agent permissions
  • Enforces read / write boundaries
  • Records requests, context, tools and responses for audit

What is LabSource?

LabSource is the customer’s private AI Factory — the on-prem workspace where local LLMs, agents, RAG, coding and analytics run.

LabSource uses the approved context CIP makes available and helps engineers analyze problems, ask questions of plant data, generate reports, write code, build agents and create new industrial applications.

In simple terms: LabSource is where the AI thinks, analyzes and builds.

  • Runs local and private LLMs
  • Industrial RAG over approved plant knowledge
  • Engineering, reliability and operations agents
  • Multi-agent workflows and orchestration
  • On-prem coding and application development
  • Datasets, training, evaluation and model comparison
  • Build custom plant intelligence using approved local data and tools

What is the On-Prem AI Server?

The AI server is the physical compute platform that runs LabSource, PHOENIX CIP and the local models. It provides the GPU, memory and storage needed to keep industrial AI inference and plant intelligence inside the customer environment.

The server is the engine room.

How does the sensor network fit?

The Asset Health Sensor Network provides the physical evidence: high-resolution vibration, pressure, airflow, oil quality, temperature, speed and other machine-health data. Long-range Bluetooth and gateways move that evidence into the PHOENIX environment.

The sensor network tells the AI what the machines are actually doing.

Your machines create the evidence. Your plant systems provide the context. LabSource applies local AI. CIP keeps it controlled. PHOENIX turns it into action.
PHOENIX Unified Intelligence

From Plant Reality to Operating and Capital Decisions

PHOENIX UI is the enterprise decision layer that connects the truth of what is happening in the plant with work execution, energy burden, lifecycle cost and capital planning.

What PHOENIX UI Adds

LabSource and PHOENIX CIP create the secure on-prem intelligence foundation. PHOENIX UI turns that intelligence into an operating and capital decision framework that plant managers, reliability teams, maintenance leaders and executives can use together.

  • Connect ERP assumptions and production commitments to actual plant performance
  • Bring CMMS / EAM work orders, PM status and assignment into the same decision context
  • Monitor control-system performance and process deviation against expected outcomes
  • Include energy burden, lifecycle cost and reliability exposure in asset decisions
  • Support repair, defer, optimize, renew or replace decisions with a visible performance matrix
  • Connect operational risk to work ownership and capital timing
Decision Layer

One clearer operating answer.

PHOENIX UI helps answer three practical questions:

Can the plant execute? Compare production commitments against current asset, process and execution reality.
Is the work moving? Connect risk to work orders, PM status, assignment, response and ownership.
Repair or replace? Use reliability exposure, energy burden and lifecycle cost to improve the decision.
When should capital move? Use operating burden and capital urgency to support defer, optimize, repair or renew decisions.
Industry Focus

Mining and Pulp & Paper

PHOENIX connects asset sensing, plant context and local AI around the operating realities of heavy industry.

Mining

Drills, Draglines, Haul Trucks & Leach Pads

Condition intelligence, long-range BLE and local AI across distributed mining assets and operations.

Pulp & Paper

Paper Machines, Drives, Gearboxes, Fans & Pumps

Asset-health and AI intelligence built against production process, operations, logistics constraints and available mill capacity.

Industrial Capacity Intelligence

Reliable capacity is the bridge between asset health and revenue.

PHOENIX is designed to answer a bigger question than “is this machine healthy?” It connects what the business must produce, the condition of the assets required to produce it, the work needed to keep them available, and the operational constraints that determine how much capacity can actually be committed with confidence.

01 — Product

What Must Be Produced?

Product mix, grade, orders, production schedule, throughput targets and required capacity define the business demand on the plant.

02 — Asset Health

Can the Assets Deliver?

Condition data, vibration, oil, pressure, temperature, alarms and operating history show which equipment threatens the production plan.

03 — Context

Why Is Capacity Constrained?

Process state, operating conditions, changeovers, recipes, historian data, staffing, outages and other context explain what is happening around the asset.

04 — Maintenance

What Work Is Required?

PMs, work orders, inspections, maintenance history, spare parts and engineering recommendations show what intervention is needed and when.

05 — Logistics

Can the Work Be Executed?

Parts, labor, contractor access, materials, transport, inventory, crane access, shutdown windows and other constraints determine whether the plan is practical.

06 — Capacity & Revenue

What Can We Reliably Commit?

PHOENIX connects the evidence so teams can prioritize work, protect throughput, estimate reliable capacity and focus attention where production commitments or revenue are most exposed.

Asset health is not the end point. Product demand sets the requirement. Condition shows the risk. Maintenance and logistics define what can be done. Context determines reliable capacity. Reliable capacity protects production and revenue.
Contextual AI

AI that understands the production and maintenance problem around the asset.

LabSource builds the context for each question from approved internal information. The intelligence is used to support planning, engineering, reliability and maintenance integration — not to directly control equipment.

Production Context

Product, grade, throughput, line speed, schedule, orders, operating targets and capacity requirements.

Asset Context

Condition monitoring, sensor evidence, operating state, failure history and asset hierarchy.

Maintenance Context

PM schedules, CMMS work orders, inspections, repair history, labor requirements and maintenance backlog.

Logistics Context

Parts availability, inventory, supplier lead time, material movement, access, contractors and execution constraints.

Engineering Context

Drawings, manuals, BOMs, SOPs, prior investigations, code, calculations and engineering decisions.

Contextual Memory

Past events, chats, retrieved evidence, model requests, expert corrections, decisions, production losses and maintenance outcomes remain attached to the work and strengthen future reasoning.

Resources

Asset Health to Capacity

How high-resolution machine evidence becomes capacity intelligence when it is connected to maintenance, operating context and the production requirement.

Learn More

PHOENIX CIP Architecture

How CIP governs tools, credentials, data access and controlled cloud exchange.

Learn More

LabSource for Engineers

Local LLMs, RAG, engineering agents, coding and application development.

Learn More

Take the Next Step

Deploy a private industrial intelligence environment that connects machine evidence, plant systems, domain expertise and local AI to the production plan — so reliability, operations, maintenance and management can work from the same view of reliable capacity and revenue at risk.