Plant-floor findings. Business-wide impact.
Crucion continuously evaluates operational data across production, equipment and utilities to uncover the findings that deserve attention. Engineering establishes what is known. AI helps explain what happened, identify likely contributors and guide the investigation. Your team decides what happens next.
Two editions. One engine.
Why Crucion
Plants have more data than ever. Teams still chase the answer.
Engineering first. AI second.
Teams spend their time chasing answers across systems, spreadsheets, reports and their own department's view of the same event.
When a line stops, everyone has data. Nobody has the same answer.
Crucion was built so those teams start from the same finding, the same evidence and the same understanding of what deserves attention.
Why it matters
Operational events create business consequences.
Mechanical downtime on a capper is a maintenance event. A blocked filler and a starved palletizer are production events. Lost throughput and margin are business events. Most plants see them in different systems, owned by different teams. Crucion connects them into one finding, from where it started to what it cost, counted once.
One operational event · demonstration plant data
Line 1 Capper: mechanical downtime.
91 minutes on the latest afternoon shift, against 15 declared. Above normal on 3 of the last 3.
ComputedLine 1 Filler blocked.
The filler behind the capper cannot discharge.
ComputedLine 1 Palletizer starved.
Lost throughput across the line, traced back to the capper.
Computed$85,667/yr
Potential savings, priced from the line's own economics and counted once, at the capper.
The same capper, in Crucion
One stop, traced and priced, with the evidence for every link.
The capper stops. The filler blocks and the palletizer starves in the same moment. Crucion confirms each link against the declared line sequence, prices the 8.6 minutes once at the line's make-up cost, and shows where breaking the chain would have avoided the loss. Rejects on restart stay "not priced" until a cost is set, rather than guessed.
A utility sag that stops a line.
Voltage sag at 2:14 a.m. → compressor trips → air header below the filler's minimum → Line 2 stops 38 minutes → $4,864 lost margin
Crucion follows the chain across utilities, equipment and the line, and names a link only when your plant's layout and the measured data agree. Illustrative example.
What happened?
The chain from origin to consequence. Crucion names a link only when your plant's layout and the measured data agree.
What could it cost?
Priced from your own margin, capacity and rates, and counted once, not in three reports claiming the same downtime.
What deserves investigation?
Every finding ranked by its value to your plant, with what Crucion can and can't see.
What should happen next?
Where breaking the chain would have stopped the loss, and a decision recorded by your team.
Engineering first. AI second.
Measured. Inferred. Unknown. Always labeled.
Engineering evaluators compute every number. AI explains what they found, and every investigation keeps three things apart, so your team can check the answer before acting on it.
Computed from your data or configured by your team, and labeled that way on every fact, with the math shown.
Likely contributors, labeled hypothesized and ranked, never stated as the cause.
Listed in every investigation, with what would close the gap. An empty answer is never an all-clear.
Coater first-pass yield decline
Estimated recoverable value: $3,300 – $8,250 per yearOne finding. Multiple stakeholders.
Every team starts from the same evidence.
The same event means something different to each team. Crucion gives each of them the same finding and the same evidence, so the morning meeting starts from shared facts instead of separate reports.
Production impact
Minutes and units lost, and where the stop started.
System behavior
How the disturbance moved through the plant, link by link.
Assets to investigate
The capper that keeps going down, the chiller drifting off its baseline, and the history behind each.
Cost exposure
What each loss costs, counted once, and proof that a fix paid off.
Decision context
What is ranked, what has been decided, and what it saved.
Human in the loop
Crucion keeps those conversations connected.
Crucion never acts on your plant by itself. Every finding waits for someone who knows the equipment to record a decision. Those decisions, work orders and conversations with CrucionAI become the plant's record, and Crucion draws on them the next time a similar problem appears, so what experienced people know stays with the plant when they retire.
- Act Real and worth fixing. It moves to the work plan.
- Discuss Worth a conversation with operations, maintenance or finance first.
- Investigate Needs a closer look. Run a full investigation of the evidence.
- Watch Not yet. Crucion keeps watching and brings it back with new evidence.
- Dismiss Known or expected. Recorded, so the same question isn't asked twice.
- Acknowledge Seen and understood. No action now, and it stays on record.
- Resolve Fixed. Closed with a note on what was done.
What Crucion evaluates
Production. Equipment. Utilities.
The product comes first. Equipment makes it, and utilities run the equipment. Crucion checks all three continuously, in one place, and prices each finding the same way: production from your own capacity and margin, utilities from your own rate schedule.
Production
- Production impact events
- Throughput loss
- Downtime patterns
- First-pass yield
Equipment
- Compressor performance and sequencing
- Chiller and refrigeration drift from baseline
- Boiler and steam efficiency drift
- UPS battery aging, runtime and loading
Utilities
- Peak demand and power factor
- Harmonics
- Off-hours load and energy against baseline
- Compressed-air and water leaks
- Cooling tower water and cooling load creep
Equipment drifting from its own baseline shows up before it costs a shift. A drop in yield on a coater shows up next to the air, steam and power that coater uses, and a stop on Line 2 shows up with the compressor and the utility event behind it.
How Crucion works
Connect. Evaluate. Explain. Decide.
Connect
Meters, drives, equipment, your historian and your MES, from any vendor, over OPC UA, MQTT Sparkplug B, Modbus TCP and more.
Evaluate
Engineering evaluators find and price each condition, continuously. The same data gives the same finding every time.
Explain
CrucionAI writes briefings and investigations from evaluated findings only, with every fact labeled.
Decide
Your team records a decision on every finding. When one is closed, Crucion verifies the savings from metered data.
Your own AI
Already using ChatGPT, Copilot or Claude?
Ask it about your plant. Crucion lets the assistant your team already uses answer from trusted operational findings and the plant record, not from guesses.
- →It can answer, never change anything
- →Each person sees only what their role allows
- →Every figure quoted exactly as Crucion computed it
- →Says plainly when something isn't measured or can't be checked
For IT: Crucion connects through the Model Context Protocol (MCP), read-only.
Why plant teams trust it
Public engineering. Your plant. Your data.
Production is evaluated with standard OEE measures of availability, performance and quality. Equipment and utilities are evaluated with methods from decades of U.S. Department of Energy and national laboratory research. The engineering behind a finding is published and checkable, not invented by an AI.
Continuous evaluation
Not a once-a-year assessment. Every check runs on live data, every day, and brings a finding back when new evidence appears.
Runs on site
A virtual appliance on VMware vSphere, Stratus ztC Edge, KVM or Hyper-V. Analysis happens inside your facility, not in a vendor cloud.
Works air-gapped
A site with no outside connection still gets every finding and every dollar figure. Only CrucionAI's narrative and outside AI assistants need a network path.
Your keys, your sign-in
Every credential, including the AI account, belongs to you. Single sign-on with Active Directory or Entra ID.
Your own AI, read-only
ChatGPT, Copilot or Claude can ask Crucion through MCP. It answers from Crucion's findings and can change nothing.
Savings that are verified
When a finding is closed, Crucion measures before and after, and books savings only from metered data.
No gaps in your records
Recovers up to 90 days of missed interval data from supported meters' onboard logs after a network outage.
Every fact labeled
Computed, configured or assumed, on every number CrucionAI uses, with the methodology cited.
Who builds it
Built by Conperio Technology Solutions.
Conperio is an industrial software company in Terre Haute, Indiana. For more than 35 years we have connected the plant floor to the enterprise, and we built Crucion to turn that data into decisions a plant or data center team can trust.
See it running
Watch Crucion work on a running plant.
No slides. Crucion running live, finding and pricing problems, tracing a stop to its cause, and answering questions from your own AI. Pick the way that suits you.
Live demonstration
A screen-share of Crucion running a plant, led by the people who built it. Bring your questions and your toughest problem.
Customer Experience Center
See Crucion on a working SMC training line, plus meters and UPS units, and talk with the engineering team behind it.
A look at your own equipment
Walk us through your data, systems and the operational questions you most want answered, and explore what Crucion could evaluate in your environment.