Lynxby DOMINION
← Back to modules

PRODUCTION ORDERS MODULE What each order produced, and the energy it took.

Production goes one way and energy the other. Cross-checking them is somebody's job, every month.

Production orders is the Lynx module that cross-checks the manufacturing orders arriving from the ERP against the electrical consumption the platform already records on the line. The screen answers two questions: how a period went, and what happened to one specific order.

ERP orders × consumption measured on the line

Request a demo →

Add to the platform →

lynxplatform.cloud/produccion/ordenes

Product screens with sample data: no figure on these screens comes from a plant.

Nothing new to instrument Your ERP already knows what it made. Your meter already knows what it cost.

The module does not re-instrument a line that already meters: it takes the orders from the ERP and the consumption the equipment already publishes to Lynx, and crosses them over each order interval.

  • Orders from the ERPEach order arrives from SAP with its line, its schedule, its part numbers and the declared downtime. The source document is kept intact.
  • Consumption measured on the lineConsumption for the interval is how much the line energy meter grows between the start and the end of the order. It is not estimated: it is measured.
  • The ratio between themProcessed quantity and energy give each order its ratio —Wh/kg and equivalents—, which is what makes one order comparable with another.

Work orders One row per order, grouped by day

Line, schedule, duration, processed quantity, consumption, the ratio between them, downtime and part numbers worked. The ratio column places each order against the median for the period, so the ones that deviate stand out at a glance.

lynxplatform.cloud/produccion/ordenes · órdenes de trabajo
  • Against the period median

    Every ratio is marked above or below the median, and those outside the whiskers are flagged: they are the ones worth looking at one by one.

  • Filtered before calculating

    Plant, lines, process quantity, consumption quantity and date range. Order and part number accept an exact match.

  • Export to Excel

    Everything queried comes out in a spreadsheet, with the same columns and the same filter shown on screen.

That table is the spreadsheet somebody rebuilds every month, cross-checking two exports by hand.

A demo with your orders →

Order detail What happened to this order

Clicking a row —or its point in the distribution— opens its indicators, its downtime with the reason, and the full document exactly as it arrived from ingestion. Without leaving the query.

  • The order's indicatorsDuration, processed quantity, consumption, ratio, number of stops and downtime for that order, not for the period.
  • Downtime with its reasonStart, end and duration of every stop, with the code and description from the plant downtime-reason catalogue.
  • The source documentThe complete ingestion record, to check what the screen shows against what came in from the ERP.
lynxplatform.cloud/produccion/ordenes · detalle

Downtime in range Where the time goes

A breakdown of all downtime in the filter by reason, ordered by time lost. It goes by sum of durations, not by percentage of the shift: one order can have overlapping stops, so the total can exceed the range.

lynxplatform.cloud/produccion/ordenes · paradas
Lynx by Dominion

Your orders, with their consumption

We prepare a demo with the orders and the consumption of one of your lines, and work out with you which quantity matters on each.

Request a demo →

Or write to us directly at support.dt@dominion-global.com

← Back to modules