How it works

Something you can use at every step.

A pilot shows the gaps between your plan and your plant. We piece the plan together from wherever it lives today and set it against how the plant really runs. Once you see the gaps, you can't unsee them.

  • Started in hoursAfter a discovery conversation, your team uploads the data package in one to two hours. No workshops, nothing to install.
  • Useful before it endsThe first gaps show up while the pilot is still running, so your team can act on them early.
  • One success testAgreed at the start, so value is judged in your terms.
  • A paid pilotA fixed scope and fee, agreed before work starts.

Why other AI pilots stall.

Many are custom builds for one site. They learn correlations from history, pick a solution before anyone has mapped how the plant runs, and end at a recommendation the plant never acts on. An Imubit pilot starts with a product: a map of your plant, based on your data. The data then leads to the solution that matches the best business outcome.

A custom pilotAn Imubit pilot
  1. Built from scratch for one site
    Built on one product, with the same method at every site
  2. Learns correlations from history
    A deterministic model of cause and effect: the same inputs give the same answer every time, and your engineers certify it
  3. Starts with a solution
    Starts with the gaps between plan and plant, ranked by value, before anything is built
  4. Ends at a recommendation
    Leads toward closed loop, inside the envelope your engineers set

Your knowledge, paired with ours.

Our builders bring the AI. Our process engineers bring what they have learned in refineries, chemical and polymer plants, cement kilns and mineral processing. Your team brings what no one else has: how your plant really runs. A pilot needs all three.

  1. How the plant runs day to day
    Build and test the models
    Models of it, built on the platform and tested on your data
  2. What the plan asks of the plant
    Find and rank the gaps
    Each recurring gap traced to the decision behind it
  3. Where the business needs to go
    Agree what to close first
    What is already being built on the platform

This is not a hands-off process. Your planners, process engineers and operations team build alongside ours, in DLPC® Builder or from the AI tools they already use, and they keep what they build.

The pilot, step by step.

Each step builds on the one before. The gaps Map finds become the models your engineers build, and those same models are what the controller learns on. Nothing is thrown away, so the value adds up step by step.

You choose the question you most want answered, and we agree one success test with you. The map then shows where it ranks among the site's gaps, and the choice can change.

What you keep.

  • A what-if simulator

    Built on your plan and plant data and tested on data it has not seen. Try a change on it before you make it on the plant.

  • A map of the gaps

    Where the plant falls short of the plan, the recurring decision behind each gap, and what each is worth.

  • A plan to close them

    Which decisions to model next, which to take to closed loop, and in what order.

All of it is yours, even if you go no further. Closing the loop on a unit is the step after the pilot, under a subscription.

What pilots are building now.

A few of the problems current pilots are working on. The same approach runs across refining, chemicals and polymers, cement, and mining and minerals.

RefiningRefining

Where does the site fall short of the plan month after month, and what is each gap worth?

The pod builds A site-wide map of the recurring gaps between plan and plant, and a what-if simulator of the whole site that planners and engineers can question.

CementCement

What will today's cement test at 28 days?

The pod builds Strength models for each curing age, from the chemistry and fineness the lab already measures.

See the application
CalciningCalcining

Which kiln should carry more of the load?

The pod builds A density target for every kiln that meets the site's blended specification with the least gas, from the models already running each kiln.

See the application
Oil productionOil production

How much chemical does the separator need?

The pod builds A model of separation efficiency against oil rate and chemical injection, built from the separator's own history.

Common questions

Questions before a pilot.

Let’s get started
What does our team need to do?

Join a discovery conversation, upload the data package, which takes one to two hours, and agree one success test. Your planners and engineers then work with Imubit's builders on your own data.

Do we need workshops or new software?

No. There are no workshops and nothing to install, so work on your data starts as soon as the package is uploaded. We discuss the findings with your planners and engineers, and what moving forward would be worth. Nothing writes to your plant.

Where does our data go?

Into the Imubit Platform, which runs on AWS and Google Cloud and encrypts all data at rest and in motion. Imubit has completed a SOC 2 Type II examination, and the report is available under NDA. When a unit later moves to closed loop, its controller runs on-premise inside your plant network.

Data security policy
What happens after the pilot?

Closing the loop on a unit is the next step, under a subscription, inside the envelope your engineers set. Everything from the pilot stays yours either way.

Imubit is for builders.

Tell us the problem you most want solved, and we will show you how a pilot gets you to value on it.