Syntech Manufacturing

Syntech Manufacturing · component guide

Production scheduling

The component analyzes a production plan's load against work-center capacity over a chosen horizon and shows the takt time and the constraint work center. It then recomputes the plan's operation schedule by a chosen strategy and reports how many orders and operations were moved.

Where it lives

  • Production planning workplace → tab “Scheduling”.
  • Manufacturing home page → tab “Scheduling”.
  • Page designer → view element “Production scheduling” (it can be added to any page; the heading property sets the title).

What it needs

Package
productionschedulingsyntech (view element syn.MfgScheduling), installed together with the SynManufacturing package.
Licence
Licence operation SynManufacturing.Use. Without it the element shows a “Licence required” card and loads no data; an administrator grants it in System designer → Licence manager.
Service
SynSchedulingWebService — AnalyzeLean computes takt and the bottleneck, Reschedule and RescheduleByBottleneck move the operations.
Rights
The operation right CanScheduleProduction is checked on the server. Without it the screen opens and the analysis is visible, but rescheduling comes back refused by the service.
Settings
The component has no system settings of its own: the horizon (14 days by default), the strategy (“By bottleneck (drum-buffer-rope)” by default) and “Start from” are set on the screen itself.
Data
Production plans with their orders and operations, and work centers with a computed capacity over the horizon; without them the table stays empty.

The screen

Production scheduling on the Production planning workplace
Real screenProduction scheduling: a plan picked and the strategy “By material shortage priority”
  • “Production plan”The list of active plans by name; until a plan is picked the component answers “Select a production plan first.”.
  • “Horizon, days”How many days ahead capacity and demand are computed: from 1 to 365, 14 by default.
  • “Analyze” and “Reload”“Analyze” computes the load for the chosen plan and horizon, “Reload” re-reads the list of plans. While a call runs both buttons read “Working…”.
  • “Constraint work center”A chip with the name of the constraint work center next to the horizon of the analysis; with no constraint the chip says “none”.
  • “Work center · Load, min · Capacity, min · Utilization · Demand, units · Takt, min/unit”The columns of the analysis table: required time, available time, their ratio in percent, the demand over the horizon and the takt per unit. The constraint row is highlighted and carries a marker.
  • “Strategy”The rule that orders the ready operations: “By priority”, “By due date”, “By product type”, “By color sequence”, “Mixed”, “By bottleneck (drum-buffer-rope)” or “By material shortage priority”.
  • “Start from”The date and time the new schedule is built from; an empty field means the current moment.
  • “Reschedule”Runs the recomputation; afterwards the message “Rescheduled orders / operations:” names two numbers, followed by the server’s note when there is one (for example, that due-date order was used instead of shortage priority).

Typical actions

Analyze the load of a plan

  1. Pick a plan in “Production plan” and set “Horizon, days”.
  2. Press “Analyze” — the table per work center appears.
  3. Compare “Load, min” with “Capacity, min”: a “Utilization” above 100% means the horizon does not hold enough capacity.

Find the bottleneck and the takt

  1. After the analysis read the chip “Constraint work center” — it is the most loaded center over the horizon.
  2. Find the highlighted row and its “Takt, min/unit” — the minutes that center spends per unit of demand.
  3. Change the horizon and analyze again to see whether the constraint stays the same.

Reschedule the operations by a rule

  1. Pick a value in “Strategy” — for example “By due date” or “By priority”.
  2. Set “Start from”: the schedule is built forward from that moment.
  3. Press “Reschedule” and read the message “Rescheduled orders / operations:”.
  4. Run “Analyze” again to see the load under the new schedule.

Reschedule around the bottleneck

  1. Choose the strategy “By bottleneck (drum-buffer-rope)” — it is the default one.
  2. Set “Start from” and press “Reschedule”: the schedule is built around the constraint work center.
  3. Check the result with a new analysis: the utilization around the bottleneck should even out.

Put the orders with shortages first

  1. Pick the strategy “By material shortage priority”.
  2. Set “Start from” and press “Reschedule”: the orders with shortages go first, in the order of the shortage-priority ranking.
  3. Read the note next to the summary: if the switch “RISK: automatic reorder by shortage priority” is off, the server schedules by due date and says so.

Colour changeover matrix

For coating and paint lines, where the order of colours decides how long the equipment is washed (white after black needs a long wash, so a grey goes in between). Switch on SynColorChangeoverEnabled (default off) and fill the lookup Colour changeover (SynColorChangeover):

  • From colour or From colour group → To colour or To colour group, Changeover / wash, min, optional Intermediate colour and Work centre (empty = every work centre), Active. The most specific active row wins: a work-centre row before a general one, an exact colour before a group. Same colour = 0.
  • Scheduling adds these minutes to the setup of an operation after the previous colour on the same work centre (planned setup on the operation is not changed; the minutes only move the dates).
  • The Colour sequence strategy then orders the work along the cheapest changeover path (nearest colour next), then by due date; priority still goes first.
  • SynColorLightToDarkRule (default off): for a pair with no row, light → dark costs nothing and dark → light costs the target colour group’s wash time (lightness from the colour’s HEX); the sequence prefers light before dark.
  • The colour of an order is the plan item’s colour, else the product’s colour (Product → Colour). A suggested intermediate colour is written to the scheduling log.

Limits and known behaviour

  • With no plan selected neither the analysis nor the rescheduling starts — the component asks you to select a production plan first.
  • Rescheduling always builds the schedule forward from “Start from”; backward scheduling from a due date is not offered on this screen.
  • “Start from” and the work-center calendars are read in your own local time, the same way the operations are generated: a schedule built from 08:00 starts at 08:00 on your clock, not shifted by the server’s time zone.
  • Rescheduling does not move work that is already under way or committed: started, paused and completed operations, and operations included in a shift assignment that is not closed, keep their dates and their assignment. The server’s note under the summary lists them and warns when such an operation now starts before its predecessor ends. A paused operation stays paused.
  • Rescheduling never changes an operation’s planned setup: the shorter setup between orders of the same colour only moves the dates, so running it again gives the same setup minutes.
  • The table is a snapshot taken when “Analyze” was pressed: after operations or capacities change, analyze again — it does not refresh itself.
  • A refusal from the service is shown in the service's own words rather than hidden. When a request does not get through or fails, a short message appears — “You do not have the right for this action”, “The server could not be reached…” or “The server could not complete the request (error N)…” — and the details go to the browser console.
  • Preset mobile quick filters are unsupported: the plan, the horizon and the strategy are set on the screen itself.
  • After a package update the page needs a hard reload (Ctrl+F5) — otherwise the browser keeps the previous bundle in cache.

See also

Full Syntech Manufacturing guide — sectionProduction scheduling (takt and bottleneck)All Syntech application guideshttps://syntechcompany.github.io/appsguides/
A Syntech Manufacturing component. Section, tab and button names match the product; the component language follows your Creatio profile language.