Skip to content
Food processing line with stainless steel equipment in a production hall
Plant Intelligence · 06

Production Scheduling That Knows What the Line Is Doing

Metromotion Controls connects your production schedule to live line data, so schedulers see status, rates, stops and CIP as they happen, can check adherence during the shift and re-plan in real time as conditions on the floor change.

How we approach it

Engineered for your site and support model

A production schedule is a plan made with the best information available the day before. By mid-morning the line has had a long stop, a changeover ran over and a CIP took longer than planned, and the scheduler finds out by walking the floor or waiting for the shift report. Metromotion Controls connects the schedule, whether it lives in a spreadsheet, a planning tool or ERP, to the live state of each line. Schedulers see adherence and forecast finish times from actual rates, and changeover and CIP windows come from measured durations, so the next plan starts from what the line really does.

01
Live order status and rate against plan by line
02
Schedule adherence and forecast finish times from actual rates
03
Changeover and CIP durations measured by SKU pair
04
Order release to the line and confirmation back
05
Interfaces to spreadsheets, APS tools and ERP planning
06
Planned against actual history for the next plan
Delivery context

Platforms and vendors

  • Ignition
  • SQL databases
  • ERP and planning tool interfaces
  • Excel and CSV schedules
  • REST APIs
  • ISA-88 batch control

Relevant experience

  • Real Pet Food: ISA-88 batch control from production scheduling through to live plant-floor batch visibility.
  • Chobani: OEE and data analytics supporting continuous improvement work across yield, throughput, CIP duration and scheduling.
  • Chobani: live OEE and downtime captured from PLC states, giving the actual rates and stops a schedule needs.
Section 01

Why schedules drift from the floor

Schedules drift for predictable reasons, and most of them are visible in the line data long before anyone updates the plan.

  • Rates planned from nameplate speed rather than the measured rate for each SKU on each line.
  • Changeover and CIP durations planned from estimates rather than recorded times.
  • Stops and slow running known to the line but not to the scheduler until the shift report.
  • Orders started, paused or finished without the schedule being told.
Section 02

Live line status in front of the scheduler

The first step is visibility. Each order on the schedule is matched to the line running it, and the scheduler sees what the line is doing now: running, stopped, in changeover or in CIP, the rate against plan and the quantity made so far. From actual rates, the system forecasts when each order will finish, so a late finish shows up while there is still time to act on it.

  • Order status by line: not started, running, paused or complete.
  • Quantity made and rate against plan, updated live.
  • Forecast finish time from the measured rate, not the planned one.
  • Schedule adherence by order, line and shift during the shift.
Section 03

Re-planning in real time

When conditions change, the scheduler decides what to do; the data makes the decision faster and better informed. With live status, measured durations and forecast finish times on one screen, a scheduler can see the effect of moving an order, pulling a CIP forward or splitting a run before committing to it, and the updated plan goes back to the line without being retyped.

  • Changeover and CIP windows based on recorded durations for each SKU pair.
  • The knock-on effect of a long stop visible across the rest of the day.
  • Updated sequences released to the line and selected at the HMI.
  • A record of planned against actual for the next planning cycle.
Section 04

Orders released to the line and confirmed back

Retyping orders at the HMI is slow and error-prone. Orders can be released from the schedule, planning tool or ERP to the line with SKU, quantity and recipe, selected by the operator at changeover, and confirmed back with actual start, finish, output and scrap. We have built this flow from schedule to batch on ISA-88 batch control at Real Pet Food, and the same pattern applies to packing and filling lines. For the ERP side of the connection, see ERP and SAP integration.

Section 05

Working with the scheduling tool you have

Many mid-size plants schedule in a spreadsheet, and that is often fine once it is fed with real data. Others use an advanced planning and scheduling (APS) tool or the planning module of their ERP. We connect to what the site uses through a documented interface, database or file exchange, and keep the plant-floor side independent so the scheduling tool can change later without rebuilding the line integration.

Frequently Asked Questions

Common questions

Can the schedule reschedule itself?

The scheduler stays in charge of the plan. What changes is the information: live status, measured durations and forecast finish times, so the scheduler can re-plan in real time instead of the next morning. Automatic optimisation can be added later through a dedicated scheduling tool if a site needs it.

Do we need scheduling software?

Not always. Many single-site plants schedule well in a spreadsheet once it is fed with actual rates and durations. A dedicated APS tool earns its cost when many lines share constrained equipment or labour.

Where do changeover times come from?

From the line data. The PLC and SCADA layer record when a line stops for changeover or CIP and when it restarts, so each SKU pair builds its own measured changeover time.

Can orders come from our ERP?

Yes. Orders can be released from ERP or a planning tool to the line and results confirmed back. We scope that interface with the ERP team at the start of a project.

Related Work

Connected services, industries and proof

Service

Plant Intelligence: factory data and OEE

OEE, reports, quality, CIP, maintenance and energy data from the team that builds and programs the lines.

Service

OEE and production monitoring

Live OEE, line status and stop reasons read directly from the PLCs on food and beverage lines.

Service

ERP and SAP integration

Orders down to the line and counts, consumption, scrap and batch results back to ERPs such as SAP and Pronto Xi.

Service

MES for mid-size food plants

The MES functions a mid-size food plant uses, what it can skip, and whether to build on Ignition or buy enterprise MES.

Project

Real Pet Food raw materials handling

Pet food raw materials automation covering batching, handling and production control requirements.

Project

Chobani OEE data platform

OEE and downtime reporting from PLC states, with shift and weekly management reports for an Australian yoghurt plant.

Project

Chobani greenfield yoghurt plant

Large capital project delivery across process automation, electrical engineering and commissioning.

Service

Ignition SCADA integrator Melbourne

Ignition Gold Certified System Integrator for Ignition SCADA, historian, reporting and MES functions.

Insight

MES and SCADA integration in food plants

The ISA-95 levels, the SCADA-to-MES boundary, production tracking and genealogy, B2MML and ERP integration for food manufacturers.

Insight

OEE for Australian food and beverage lines

OEE meaning and calculation under ISO 22400-2, with a worked two-SKU example and the booking rules that move the figure.

Industry

Food and beverage automation Australia

Automation, traceability, CIP, SCADA and production data for Australian food and beverage plants.

Industry

Pet food automation

Batch, recipe, work order, CCP and OEE systems for pet food manufacturing environments.

Related work

Related project proof

Project

Real Pet Food Company

Real Pet Food Company needed automated raw materials handling with stronger batch traceability and scheduling, across a plant where mechanical, electrical and automation scope all had to be brought together by one team before startup. Metromotion Controls structured the batch control to ISA-88, breaking each product into recipe phases and validating the transfer route and ingredient at each step so material moved against a confirmed path rather than an assumed one. The team supplied, installed and commissioned the system, coordinating mechanical, electrical and automation scope through simulation, FAT and startup.

Project

Chobani

Building on the greenfield automation delivered at Chobani's Australian facility, Metromotion Controls was engaged to develop an OEE data platform that gave the operations team structured visibility of line performance, availability losses, and production output. The project connected existing PLC infrastructure to a centralised reporting environment, establishing consistent downtime reason codes, shift-level OEE calculation, and management dashboards aligned to how the site teams already ran daily reviews.

Project

Chobani

Chobani needed a controls partner to help establish its Australian manufacturing operation with new production lines and site infrastructure, and the relationship has had to keep adding and optimising lines without disturbing production already running on site. Metromotion Controls supported the initial setup and has continued to add, optimise and support production lines over the years, bringing process, packaging and site services onto common control and data interfaces so each addition extends one operating environment rather than a separate island. The scope spans plant services including boilers, refrigeration, trade waste, power monitoring and water usage monitoring, plus OEE, site data analytics and contextualised production data from lab equipment and other external sources.

Related pages

Want a schedule that keeps up with the line?

Speak directly with an engineer about scope, timing and technical constraints.