Opsynth

Every slot below just changed.
Your quarter doesn't have to.

ATP reads your ERP, explodes every bill of material, and answers what MRP can't: which builds clear, what they're worth, and who owns the fix.

Build readiness · next 7 weeks44 slots
4
Role views, one dataset
8
Decisions computed nightly
21
Source tables in scope
0
Changes to your ERP

Opsynth Innovations, Inc.

Built at the desk,
not the whiteboard.

We were the buyers and planners pulling the same reports every Monday to answer one question our systems couldn't: are we going to make it? Opsynth exists to close that gap. ATP is our first product line. It won't be the last.

Principles

Four convictions that
shape everything we ship.

Compute the decision, not the dashboard.

MRP will tell you a part is short. It won't tell you the shortage stops four instruments, puts eight figures in play this quarter, and clears in a day by releasing a lot already sitting in your building. A chart restates the problem. ATP works out the answer, then shows its reasoning.

Every number carries its receipts.

Open the lineage on any figure and you'll find the source tables, the filters, and the derivation behind it. The same number means the same thing in every view, and a reconciliation suite runs against the product to keep it that way.

Go past the purchase order.

Most inventory tools stop at open POs and on-hand balances. Readiness lives a level below, in the bill of material, the work order, and the dependent reservation. That's where we extract — and it's why ATP can score a build rather than flag a part.

One dataset, four jobs.

Planning, purchasing, quality, and the executive team don't need four tools and four versions of the truth. They need one set of numbers pointed at four different decisions, each in the language of the person making it.

The product

Every build in the window,
ranked by how close it is to clearing.

ATP takes a plant's open work orders and walks each one down to the component: what the build needs, what's on hand, what's on the water, and what's held in quality.

Command Center showing eight in-window builds ranked by clear-to-build readiness
Command Center. Revenue at risk and revenue already missed at the top, clear-to-build readiness per assembly, and the function that owns the next action in the right-hand column. Not a status report — a work queue.

Blast radius

One part. Four instruments.
Now you know which meeting to call.

A shortage list ranks parts by how short they are. That's rarely the same as how much they matter. Select a constraint and the plant filters to its consequences.

Build readiness filtered to a single constrained component and the four assemblies it affects
Plant view, filtered to one constraint. Eleven slots of thirty-nine, four assemblies, eight of them not ready — with the fan tracing each constrained component to the instruments waiting on it.

Honest verdicts

Including the answer
nobody wants to hear.

Where a gap can't close inside the remaining lead time, ATP says so — with the arithmetic in the open — rather than producing a recovery plan that quietly fails three weeks later.

Production slot detail showing a ready build with all components covered
Ready. All components covered against the commit date. No reason for this build to take up anyone's morning.
Production slot detail showing a blocker that will not recover in time
Won't recover in time. Zero projected on hand and the next delivery landing ninety-seven days past the build date. Decide now, not in November.

From signal to action

Each shortage arrives with a way out, and a name on it.

Open a build and ATP lists which parts are short, by how much, against what the build needs — then stacks the recommended actions underneath, each labelled with its owner, how many shortages it closes, and how long it takes to execute.

Cross-plant pulls are checked against real unrestricted stock at the donor plant. Quality dispositions are tied to specific lots, quantities, and suppliers. The build itself carries a primary owner, so the daily stand-up stops being a negotiation about whose problem it is.

Build detail listing five short parts and five recommended actions with owners
Recommended actions. Five parts short, five actions, two owners, one order of operations.

Four views

Same numbers.
Four different questions.

Planning

Which slots are ready, at risk, or not ready — and which constraint is doing the most damage across the most assemblies.

Purchasing

Spend at risk, past-due lines, expedite and cancel candidates, and measured lead-time variance by vendor.

Executive

Protected, at-risk, and missed revenue across the quarter, with close pace against elapsed time.

Quality

Held material valued and aged, filtered to the lots actually blocking a build.

Build readiness showing production slots by week, constraint impact and top constraints
Planning · Build readiness. Thirty-nine slots across seventeen assemblies, scored week by week, with every constraint traced to the instruments waiting on it.
Supply exposure showing supply versus demand projection, lead time variance by vendor and past-due items
Purchasing · Supply exposure. Cumulative supply against cumulative demand per part, with the date the gap opens and lead-time variance measured from goods receipt history.
Revenue exposure showing protected, at-risk and missed revenue
Executive · Revenue exposure. The quarter split into protected, at risk, and missed, with the assemblies ranked by dollar exposure.
MRB value showing disposition mix, aging and supplier defects
Quality · MRB value. Held inventory by disposition and age, valued and tied to demand, with the suppliers blocking the most builds.

Capabilities

What ATP computes
that your ERP does not.

Clear-to-build score

The share of a build's component lines covered at its commit date, from a full BOM explosion against unrestricted stock and scheduled receipts.

Blast radius

How many builds a single shortage touches, and what those builds are worth. The small part on the shortage report is often the one holding the quarter.

Recovery complexity

Whether a gap can close inside the remaining lead time, by which lever, and at what cost in days.

Lead time variance

Actual days late per vendor, measured from goods receipt history rather than the number stored on the material master.

Supply vs demand projection

Cumulative on-hand plus scheduled receipts against cumulative reservations, per part, with the date the gap opens.

MRB value tied to demand

Held lots valued, aged, and matched to the builds they're blocking, so quality work is sequenced by what it releases.

Cancel and delay candidates

Open purchase orders with no demand behind them in the horizon — capital you can stop spending before it lands.

Written brief

A plain-language summary of the window, generated for the role reading it and ready to paste into the message you were going to write anyway.

Deployment

No transports. No production changes.
Read-only throughout.

We start with the smallest possible footprint in your landscape, prove the numbers against what your team already knows, and only then talk about deeper integration.

Phase one · Nightly extract

Scheduled job, flat files, done by morning.

A background job writes the required tables on a nightly schedule. ATP loads, models, and publishes before the first shift meeting. Nothing is written back.

Phase two · Direct integration

API connection, once the value is obvious.

When the plant runs on ATP daily and the numbers have earned their trust, we move to a live connection — on your security team's terms and timeline.

Tables in scope · materials, BOMs, work orders, purchasing, stock, sales
  • MARA
  • MAKT
  • MARC
  • MARD
  • MAST
  • STKO
  • STPO
  • LFA1
  • EINE
  • EKKO
  • EKPO
  • EKET
  • EKBE
  • EBAN
  • AUFK
  • AFKO
  • RESB
  • JEST
  • VBAK
  • VBAP
  • VBEP

Craft

Made for people who live in it all day.

Planners and buyers don't visit this software. They sit in it from the morning stand-up until the last expedite call. So it loads fast, reads clearly under fluorescent light, and lets people set it up the way they work.

Dense tables that stay legible, lineage on every card, plain language in every empty state, and ten palettes — because a screen you stare at for nine hours should be one you can stand.

Appearance settings showing five light and five dark palettes
Appearance. Ten palettes, applied instantly across every view.

Next step

Bring us one plant
and a nightly extract.

We'll stand ATP up against your own data and walk your planners through the first window. If the numbers don't match what your team already knows, that's a finding worth having.

Email
sales@opsynth.coDemo and design partner enquiries
Web
opsynth.coProduct overview and demo request

Design partner program. We are taking on three design partners. They help shape the roadmap in exchange for a first-year discount and every future upgrade free for the life of the product. Integration is scoped per environment.