Skip to content

Manufacturing

The work around the ERP in your plant

Your ERP holds the work orders, the purchase orders and the invoices. Getting them in, checked and out again happens at the order desk, in purchasing, in accounts payable and at the scheduling board. That is where our engineers sit.

Where our engineers sit in week one

Day 2
The order desk and customer service
Day 3
Purchasing and accounts payable
Day 4
The scheduling board
Day 5
Your IT manager or ERP administrator

01 Workflows

Five workflows in a plant, today and after

Each one is fully digital work that sits around the ERP. The level on a card is the highest one that workflow should reach, not where it starts: a workflow typically starts at Level 0 (Recorded) and moves up one level at a time, after a promotion review.

Illustrative example

Each card describes a typical case, not a specific client.

  • 01 / Order desk

    Sales order entry

    Today

    Customers email purchase orders as PDFs, scans and spreadsheets. Someone on the order desk keys every line into the ERP and translates the customer's part numbers from a spreadsheet, or from memory.

    After

    An agent reads the purchase order, translates the part numbers and enters the orders that match the price list and the credit limit. The order desk sets the rules, takes the mismatches and reviews a sample.

    Some orders always go to a person: a first order from a new customer, a part with a new drawing revision, anything above the amount limit.

  • 02 / Inside sales and estimating

    Quoting

    Today

    A request for quote arrives with a drawing and a quantity. An estimator builds the cost from material, the operations in the routing, setup and outside processing, often starting from an old quote in Excel.

    After

    An agent finds the past quotes for similar parts and prepares the quote for a repeat part in full. The estimator reviews and approves every one before it is sent.

    That is the ceiling for made-to-order parts: an agent does not read a drawing and decide how to make the part. Quotes for stocked items at list or contract price can reach Level 3 (Supervised).

  • 03 / Purchasing

    Supplier follow-up

    Today

    Supplier acknowledgments pile up unread, so the ERP keeps showing the date you asked for. Your buyers export the open purchase order report to Excel and chase suppliers one by one.

    After

    An agent reads each acknowledgment, asks suppliers for confirmed dates and keeps the promise dates in the ERP true. A slip that puts a job at risk goes to a buyer.

    The level is for follow-up and keeping dates current. Releasing a purchase order commits money, so it stops at Level 3 with tight limits, or at Level 2 (Prepared).

  • 04 / Scheduling board

    Production scheduling support

    Today

    The ERP has a schedule. The one the plant runs to is on a board or in a spreadsheet, rebuilt by the scheduler each morning from late purchase orders, jobs that fell behind and machines that are down.

    After

    An agent keeps the list of jobs at risk current and prepares each schedule change in full, showing what moves and why. The scheduler approves every change.

    Schedule changes stay at Level 2 for good, because the schedule decides what machines and people do. The jobs-at-risk list and the dates customer service sees can run at Level 3.

  • 05 / Accounts payable

    AP invoice matching

    Today

    An AP clerk keys each supplier invoice, then chases the mismatches: a price that changed, a partial receipt, freight that is not on the purchase order.

    After

    An agent enters the invoices that match the purchase order and the receipt within your controller's tolerances. Mismatches go to a person, routed by reason: price to the buyer, quantity to receiving.

    Level 4 (Autonomous) is possible for the same invoices. Invoices with no purchase order stay at Level 2 for good: the agent proposes the coding and a person approves every one. Matching an invoice does not approve it for payment: releasing payment stays with people at every level.

  • 06 / The ladder

    Where each one stops

    The highest level each workflow should reach, not where it starts.

    1. Sales order entry Level 4
    2. Quoting, made-to-order parts Level 2
    3. Supplier follow-up and keeping dates current Level 4
    4. Production schedule changes Level 2, for good
    5. AP matching, invoices backed by a purchase order Level 3

Two more we look for in a plant front office: inventory and cycle counts, and customer order-status questions. The playbooks in the docs take each workflow level by level.

02 Where it stops

What stays with people in a plant

Agents work on the digital part: the email, the document, the ERP transaction. The rest stays where it is.

  • Running machines and moving material. Agents do not do physical work and do not operate machinery.
  • Deciding the schedule. The agent prepares a change and the scheduler decides. The supervisor knows a machine is running rough before any system does.
  • Estimating a new part. The estimator estimates, with the history the agent found.
  • Choosing suppliers. Sourcing, negotiating and deciding to pay for expedited freight stay with your buyers.
  • Paying suppliers. An agent never releases a payment and never changes a supplier's bank details.
  • Counting. People count. An agent can issue the count list and post small adjustments that a recount confirmed.
  • The phone. Calls stay with your people.

03 How it starts

It starts on your floor

Two engineers spend two weeks on your floor and in your front office. They map how the work really gets done and show the first automation working on your own data.

A Discovery Sprint in a plant

  • Safety first. Before anyone walks the floor, our engineers take your safety orientation and wear what each area requires. They do not touch machines, material or product.
  • A day at the scheduling board. They stand with the scheduler through the morning rebuild: which purchase orders are late, which jobs fell behind, which machine is down.
  • A ranked list of what to fix. The Automation Backlog ranks your workflows by hours spent, cost of errors and how feasible they are to automate.
  • A prototype on your data. At the readout the top workflow runs on your own purchase orders, invoices or work orders. It reads your data and writes nothing to your ERP.

Stage 01

Discovery Sprint

Two engineers spend two weeks on your floor and in your front office. They map how the work really gets done and show the first automation working on your own data.

$25,000 fixed fee

Duration
2 weeks on site
Team
2 forward-deployed engineers

You get

  • Operations Map
  • Systems and Data Audit
  • Automation Backlog, ranked
  • Working Prototype of the top workflow, on your real data

Next step

Start with a call with an engineer.

Tell us which ERP you run and the three workflows that hurt most. That is the whole first conversation.