Manufacturing

Planr

Demand intelligence for multi-plant manufacturers.

The field report

The planner’s shortest decision is still taking hours.

Import-dependent plants run on a 45–65 day replenishment clock. Inventory, transport, and demand live in separate files. Planr stitches them and answers “can we keep the line running?” in minutes.

Network · live
8 plants
Eight plants across a network, two showing shortage/surplus state, transport lines connecting between them.NDRSTRDWDPNEHYDBGLCHNMDUSHORTAGESURPLUSTRANSFER ROUTE
Deployment
Live · 8 plants
ERP
Any · field-mapped
Engine
Operations research
Decision cycle
Days → minutes

The crisis

The decision that keeps breaking.

Tuesday morning, filter plant outside Nasik. Media 007 is down to 8 kg against a 46 kg daily burn. Coverage: two and a half days. Supplier lead time: 45–65 days. Shortage: 912 kg across a nineteen-day window.

The fix already exists in the network. The same part sits at two sister plants. A compatible substitute sits at a third. A master roll in the building can be cut to width. Planr surfaced all three within seconds of the data loading.

“From lag report to actionable shortage resolution options, in one session.”
Demand Intelligence Platform · Executive Brief

Walkthrough · Part 1 of 4

How Planr starts where spreadsheets end.

The operational reports a planner already exports — stitched into one decision-ready view before the day begins.

Walkthrough · Intro
VideoThe scattered Monday morning, compressed into one ready-to-act view.

The gap

Why planning stays manual.

The problem is cohesion, not data. The operational reports a planner needs already exist — stock and buffers, open POs and ETAs, plant-level inventory value, inter-plant transport. They arrive separately, at different cadences, owned by different teams.

Stitching them into one view eats the day. Deciding gets what’s left. Every at-risk part becomes a coordination project; the knowledge of who substituted what lives in whoever is in the room.

Five fragmented data sources drifting independently; flickering connectors never converge.LAG MASTERstock · buffersDSRopen POs · ETAsINVENTORY VALUEplant coverageTRANSPORT MASTERcost · transitERP EXPORTSnative CSV / XLSXNO CONVERGENCE
Figure IIFour reports from four teams, each alive in its own orbit. Connectors flicker; nothing converges.

Walkthrough · Part 2 of 4

Coverage across every plant, in one view.

Every plant, every part — coverage in one view. Risk surfaces the moment the data loads; one drill-down lands on the stock projection.

Walkthrough · Lag Analysis
VideoRisk surfaces before anyone has to ask.

What Planr is

Introducing Planr.

Planr ingests the operational reports, normalises them, and runs an operations-research engine across the network. Output: a ranked, costed menu of resolution options the planner can act on.

Three layers — data, analytics, decision — with an AI layer on top. Not an LLM doing the math; OR doing it, auditably.

The four layers

Planr four-layer architecture: Data layer at the foundation, then Analytics engine, Decision interface, and AI layer at the top. Click any layer to inspect it.AI LAYERDECISION INTERFACEANALYTICS ENGINEDATA LAYER
  • Accepts the operational exports your ERP already produces. Field-mapping aligns any column naming to a stable internal vocabulary. No code.

Dashboard & drill-down

Shortage intelligence.

Planr runs a shortage computation across every plant and every raw material at once — the thing a spreadsheet can’t. The dashboard shows coverage in kilograms and days. Click any at-risk part: RLT window, on-hand, material-in-transit against confirmed ETAs, exact stockout window, replenishment to restore the buffer.

The same engine runs in two planning modes. Pick whichever your data supports today. Both feed the options engine downstream.

Stock trajectory for Media 007 at Plant 1. Stock crosses the green-level buffer at day 40, opens a 12-day stockout window, and steps back up on MIT arrival.0100200300400KG STOCK0d16d32d48d64dRLT WINDOW · 65 DAYSGREEN LEVELMIT ETA · 52dSTOCKOUT · 12 DAYSSHORTAGE — 912 KG
Figure IVStock trajectory for Media 007 at Plant 1: on-hand crossing the green-level buffer, the shaded stockout window, material-in-transit stepping up on confirmed ETA.

Resolution pathways

The Options Engine.

For every at-risk part, four families of resolution. Same part at a sister plant. Compatible substitute at another plant. Substitute already at home. Master-roll cuts, LP-optimised inside the 3–12% machine-constraint window.

Each option lands in one row: source plant, source part, width and grade match, transferable quantity, cutting waste, transit days, total delivered cost. Every number visible. Every number auditable.

The Options Engine. A central shortage on Media 007 branches into four resolution pathways — transfer of the same part, substitute at another plant, substitute at the same plant, and master-roller cutting.SAME PART · DIFF PLANTCOST₹ 12,800WASTETRANSIT2 daysVIABLESUBSTITUTE · DIFF PLANTCOST₹ 9,400WASTE4.8%TRANSIT3 daysVIABLESUBSTITUTE · SAME PLANTCOST₹ 2,100WASTE7.1%TRANSIT0 daysVIABLEMASTER ROLLER CUTCOST₹ 3,300WASTE5.4%TRANSIT0 daysVIABLESHORTAGEMedia 007 · Plant 1–912 KG · 19d window
Figure VFor a single at-risk part, the engine computes all four families of pathway at once — ranked by delivered cost, material waste, and transit time.

Same part · different plant

Sister plants with surplus above their own green level. Transferable quantity, transport cost, transit days.

Substitute · different plant

Compatible substitute at another plant. Width-mismatch wastage plus transfer cost and transit.

Substitute · same plant

Parts already in-house that can be converted or reallocated. Zero transport. Cutting waste traded for it.

Master roller cutting

Cutting combinations from available master rolls. LP-optimised inside the 3–12% waste window.

Walkthrough · Part 3 of 4

Every shortage, every feasible path.

Transfer, substitute, reallocate, or cut from a master roll. Each row arrives with rolls needed, wastage percentage, and transit already solved — through OR, not heuristics.

Walkthrough · Resolution paths
VideoThe whole menu, with the math already done.

AI decisioning

From options to plans.

The options engine handles feasibility — every pathway the network allows. The AI layer handles optimisation — picking the right subset across every plant and every part in a single pass.

Three plans, three goals. Lowest cost leans on transfers. Fastest leans on shortest transit. Balanced trades cost, speed, and waste. Cross-plant dependencies are honoured: surplus committed to Plant 3 isn’t available to Plant 5. Drill into any action and the underlying combination opens with the same tables and tooltips from the options view.

Hundreds of feasible options condense into three ranked plans — lowest cost, fastest resolution, balanced.PLAN 01LOWEST COSTMinimise total spendCOSTTIMEWASTEPLAN 02FASTESTMinimise time to resolveCOSTTIMEWASTEPLAN 03BALANCEDBest trade-offCOSTTIMEWASTE~288+ feasible options → 3 ranked plans
Figure VIThe OR engine computes every feasible pathway across every part and every plant. The AI layer then composes three globally-optimal plans from that structured set.
“Hundreds of unranked options to three plans with reasoning, in a minute instead of a morning.”

Walkthrough · Part 4 of 4

Hundreds of options collapse into one plan.

OR produces every valid resolution. The AI layer ranks, sequences, and explains them — lowest cost, fastest, minimum waste — on demand.

Walkthrough · AI layer
VideoThree ranked plans with per-action reasoning.

For commercial teams

What-If, a decision layer for sales.

The other person living inside a shortage is the sales owner — the face of every customer commitment, with no view into the plant. “Can you deliver 2,500 units by the 18th?” shouldn’t need a callback.

Sales describes the order in free text. What-If runs the same cross-plant analysis a planner would: BOM, inventory, open POs, transfer availability, air-freight feasibility. Out: a feasibility answer, a timeline, BOM blockers, an action plan to take back to the customer.

Feature · What-If Analysis
VideoFeature walkthrough: What-If Analysis, by Planr.
A customer promise branches into five feasibility checks — inventory, lead time, BOM risk, cross-plant availability, and air freight — each resolving to a pass, warning or fail state.CUSTOMERPROMISEInventoryLead timeBOM riskCross-plantAir freight
Figure VIIOne customer promise triggers five downstream checks. Each resolves to a pass, a warning, or a blocker — before the commitment goes out.

Commit with options, not guesswork.

In production

Proof & deployment.

Planr is live at a top-tier automotive filter manufacturer — eight plants, all import-dependent raw-material planning. Today: manual file upload. Phase 2: direct ERP integration, Oracle first.

No plant-count limit, no industry lock-in. The same OR engine fits pharma, specialty chemicals, and any multi-plant operation running on import-dependent raw materials. New verticals start with a discovery call — we sit with your planning team, map your reports and constraints, and fit the resolution families to your bottleneck before a single file moves.

8
Plants, live
Any
ERP supported
OR
Engine, not LLM
45–65d
RLT window handled

Bring the clock back under control

Bring the decision back under a clock you control.

Planr runs at an eight-plant operation today. It adapts to your ERP via configuration, not a rebuild. Start with the lag report you already produce.