Reference · built on requestOperator by FibricProduction & maintenance

Changeover Plan

Reads the released work order queue and the recipe on the line, and proposes an order sequence and changeover window that cuts setup time.

Request accessPricing ↗

About

Every recipe switch costs setup time that the routing already states. Changeover Plan reads the released work orders for one line from NetSuite, Katana Cloud Inventory, Plex, or Fulcrum, with due dates and planning priority, and the routing's operation steps, work centers, and setup times. From the PLC it reads the recipe loaded now and the quantity left on the running order, so it knows when the line will free up.

It proposes a sequence that runs orders sharing a setup back to back, with the minutes saved per swap and the due dates checked, and a changeover window placed where the current order ends. The proposal goes to the planner in Microsoft Teams. On approval it proposes the date and queue changes on the work orders themselves.

This is a reference listing. It documents what Fibric would read from Changeover Plan and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Work orders in NetSuite with status Planned or Released, AM Planned Start Date, Planning Priority Code, and OK to Release
  • Manufacturing orders in Katana with queue rank and ingredient_availability, jobs in Plex, and jobs with operations in Fulcrum
  • The manufacturing routing per assembly: operation steps, work centers, setup time, and run rate
  • The recipe or product number loaded on the line and the quantity remaining, read from PLC tags over OPC UA or Ignition
  • Component commitment on each work order, so an order whose member items are not committed is not sequenced ahead
  • Replies on the Adaptive Card it posts to the planner's Microsoft Teams channel

Proposed actions

  • Target capability: propose a run sequence for one line that groups orders sharing a setup, with minutes saved per swap and due dates checked
  • Target capability: propose a changeover window, start and end, placed where the running order's remaining quantity runs out
  • Target capability: propose the AM Planned Start Date or queue rank changes on the sequenced work orders, for the planner
  • Target capability: propose a Microsoft Teams card to the line's channel with the sequence and window, and take the planner's answer
  • Target capability: propose holding an order whose components are not committed, instead of placing it in the sequence

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Same setup, back to back

    Several released orders share a setup, split by a different one in the queue. Changeover Plan proposes running them together, shows the minutes saved, and confirms no due date slips.

    With NetSuite, OPC UA, Microsoft Teams

  • Window on the remaining count

    The PLC shows the running order will finish mid-afternoon. The operator proposes the changeover window there and the queue rank changes in Katana.

    With Katana Cloud Inventory, Ignition

  • Hold what cannot start

    A job's components are not committed. Rather than sequence it, the operator proposes a hold, and the planner sees why in the Teams card beside the Plex job.

    With Plex, Microsoft Teams

  • Job-shop sequence

    Fulcrum jobs with operations on the same work center are grouped by tooling and posted to the planner, with the recipe the S7-1500 reports as the starting point.

    With Fulcrum, SIMATIC S7-1500

Requirements

  • An ERP or MES connector with work orders and routings: NetSuite, Katana Cloud Inventory, Plex, or Fulcrum
  • Setup time per operation step on the routing; without it there is nothing to save
  • An OPC UA or Ignition connector exposing the loaded recipe and remaining count per line
  • A Microsoft Teams channel per line where the planner answers, with ChannelMessage.Send granted to the posting account
Authentication
Changeover Plan has no credentials of its own. It reads orders and routings through your ERP or MES connector, line state through OPC UA or Ignition, and posts through the Microsoft Teams connector under a delegated account that is a member of the channel.

Limits

  • It sequences within one line. It does not move an order to another line or plant.
  • Due dates win. It will not push an order past its due date to save a changeover unless you allow that for the line.
  • A routing with no setup time is sequenced by due date and priority only.
  • Microsoft Graph allows application permissions for channel messages only in migration; posting uses a delegated account, so a person's account owns the message.

Access and pricing

Reference listing. Fibric builds the operator under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Changeover Plan ↗

Questions and answers

What does the planner approve?
The sequence, the changeover window, and each date or queue change on a work order. The Teams card shows the order of runs, the setup minutes saved per swap, and any due date at risk. Approve, reorder, or dismiss. A dismissed sequence is not re-proposed until the queue changes.
What record is left?
A receipt per sequence: the orders as read, the routing values used, the recipe on the line at the time, who approved in Teams, the fields written on each work order, and the previous values so the change can be reversed.
What will it not do without the planner?
It never changes a work order, releases an order to the floor, or writes to the PLC. It never posts to Teams except as a proposal. It never sends anything to a customer.
Ask about Changeover Plan

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This operator is developed, published, and supported by Fibric. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy