How it works

On top of your ERP, never inside it

Your ERP stays the system of record. Unbrick reads a nightly copy of its reports, checks it, and plans the shop forward from today.

Your plant

Your ERP

Scheduled CSV reports it already knows how to make: items, jobs, routings, labor, orders.

Your plant

Plant connector

A small program next to the exports. It checks each night’s files and pushes them out over HTTPS.

Hosted or yours

Unbrick

Refuses stale or partial data, then plans finite capacity forward and keeps every result traceable.

Your people

Your team

Planner, approver, supervisors and the floor, each with their own sign-in and role.

Every night

What happens between the export and the morning

1

Export

The ERP writes its scheduled reports to a folder, as it does today.

2

Check at the plant

The connector maps the files, checks every table, count and checksum, and stops if anything is broken.

3

Check again, then plan

Unbrick refuses stale, partial or repeated loads. A good load is planned forward with finite capacity.

4

Ready by morning

Today’s plan, the brief for each role, and any customer review in progress, all from last night’s data.

If the export breaks, nothing half-loaded is ever shown. Yesterday’s plan stays current, every screen says the data is not from today, and Data health says why.

What the plan models

We tell you what the model doesn’t know

The plan schedules labor by department, from the hours your people actually log. It treats outside processing as calendar days, plans component supply from stock, finished lots and open lots, and keeps held and stalled lots out until a person acts.

What it doesn’t model is listed on screen: individual machines and tooling, raw material beyond stock on hand, inspection capacity and shipping capacity. Each delivery date shows how much of it rests on recorded facts and how much on assumptions.

Data health: what the delivery dates rest on, and what the plan models and does not model
Synthetic demo plant.
Where it runs

Hosted by us, or on your server

The same software either way. Moving between them later is a backup and a restore.

Hosted by us

  • Your own isolated deployment and database
  • Backups, health checks and updates are ours to run
  • Your address: yourplant.unbrick.ai

On your server

  • Runs in containers on a server at your plant
  • Your IT holds the keys and the backups
  • Nothing leaves your network