Reference · built on requestOperator by FibricProduction & maintenance

Backlog Priority

Ranks the open maintenance backlog by asset priority, safety flags, and tomorrow's production plan, and proposes the next-day sequence.

Request accessPricing ↗

About

A backlog sorted by age sends a technician to the wrong machine. Backlog Priority reads the open work orders in IBM Maximo Manage, Fiix, MaintainX, or UpKeep with their priority, asset, status, and target start. In Maximo it reads the work order priority, the asset or location priority, and the calculated priority that sets the respond-by date. It reads asset criticality where the CMMS keeps it, and any safety flag on the record.

Against that it reads tomorrow's production plan from NetSuite work orders or Plex jobs, and the machine state now over OPC UA, so a machine due to run is not taken down and an idle one is used. It proposes a sequence per crew and the target date changes behind it. The planner approves.

This is a reference listing. It documents what Fibric would read from Backlog Priority 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

  • Open work orders with status, priority, asset, location, and target start in Maximo Work Order Tracking, Fiix, MaintainX, or UpKeep
  • Maximo WOPRIORITY, ASSETLOCPRIORITY, and CALCPRIORITY, and the RESPONDBY date derived from them
  • Asset criticality in MaintainX, asset and location priority in Maximo, and safety flags on work orders or work requests
  • Tomorrow's production plan: NetSuite work orders with AM Planned Start Date and work center, or Plex jobs by workcenter
  • Machine state now, running, idle, or faulted, over OPC UA or from Ignition tags
  • Technician and team assignments in the CMMS, so the sequence is per crew

Proposed actions

  • Target capability: propose a next-day sequence per crew, ordered by calculated priority, safety flag, and machine idle windows, for the planner
  • Target capability: propose a target start change on each sequenced work order in the CMMS
  • Target capability: propose deferring a work order on a machine planned to run, naming the next idle window
  • Target capability: propose raising the priority of a work order whose respond-by date has passed or whose asset has faulted since it was opened
  • Target capability: propose posting the approved sequence to the crew's Microsoft Teams channel

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

What you can build

  • Respond-by first

    Maximo's calculated priority puts a work order past its respond-by date. Backlog Priority moves it to the top of tomorrow's list and checks the NetSuite plan for an idle window on that asset.

    With IBM Maximo Manage, NetSuite

  • Idle window found

    A press is faulted now and not planned tomorrow. Fiix work orders on it are pulled forward, and the target start on each is proposed for the morning.

    With Fiix, OPC UA

  • Do not take down the running line

    A MaintainX work order on a critical asset falls on a day Plex has it running all shift. The operator proposes deferring it to the next idle window and posts the sequence to Teams.

    With MaintainX, Plex, Microsoft Teams

  • Crew by crew

    UpKeep worker and team assignments split the sequence per crew, with Ignition run states marking which machines are free at shift start.

    With UpKeep, Ignition

Requirements

  • A CMMS connector with the open backlog: IBM Maximo Manage, Fiix, MaintainX, or UpKeep, with assets on the work orders
  • A priority or criticality on assets or work orders; records without one sort last
  • A production plan source: NetSuite work orders with scheduling fields, or Plex jobs
  • An OPC UA or Ignition connector with a run state per machine, if you want idle windows used
Authentication
Backlog Priority carries no credentials. Work orders come through your CMMS connector, plans through the ERP or MES connector, and machine state through OPC UA, each under that connector's scopes.

Limits

  • Rank uses the priorities on the records. A work order with no asset or priority is placed last, not guessed at.
  • An unplanned run on a machine is invisible to it; the plan it reads is the ERP or MES plan.
  • It never closes, assigns, or cancels a work order. The planner approves the sequence and every date change.
  • A safety flag is whatever your CMMS records. The operator does not decide what counts as a safety issue.

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 Backlog Priority ↗

Questions and answers

What does the planner approve?
The sequence and each target start or priority change. The proposal shows every work order with its priority, asset, safety flag, the plan for the machine tomorrow, and its state now. Approve, move an item, or dismiss. A dismissed order keeps its current date.
What record is left?
The sequence as approved, per crew and day, and a receipt per work order changed: the priority values read, the plan consulted, who approved, the field written, and the previous value for reversal.
Where does it stop without the planner?
It never changes a work order without approval, never assigns a technician, never closes or cancels work, and never edits a production plan. It reads machine state; it does not write to a PLC.
Ask about Backlog Priority

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