Skip to content
  • There are no suggestions because the search field is empty.

How to Create a Setup Expiry (with variations)

The ‘Setup Expiry’ solution allows you to track when a job ‘Setup’ exceeds a set target time. Once a setup time has expired, OFS automatically transitions to a predefined unplanned downtime reason.

Note: If a new shift or job is started during a setup, the counter will reset.
When OFS transitions out of setup into another downtime or running, the counter will also reset.

Create a New User

Step 1 - Navigate to the ‘Users & Operators’ tab and fill in the following:

  • Name - Alert Expiry

  • Login e.g. Alert

  • Password

  • Role: Analytics User

Create the Downtime Reason

Step 2 - Create the Unplanned Downtime reason in your Reason List in Fusion Manager. 

  • Name the downtime reason e.g. Overdue Setup

  • Downtime Type = Unplanned

  • Group = Setup & Hidden

  • Reason Code - Rename (optional)
    • Click the pencil icon to copy the code for Step 5.

 

Step 3 - Assign your new reason to a line in ‘Reasons Assignment’

Create a Web ‘Service’

Step 4 - Navigate to the ‘Services’ tab

  • Click ‘Web’
  • Create a 'New Service'

 

Step 5 - In the URL, enter the following with your OFS information:

http://localhost//server/control/downtime/allocate/@reasoncode

  • Change the reason code to the unplanned downtime code as per Step 2.

Step 6 - Navigate to ‘Authentication’ tab and fill in the details from Step 1.

Step 7 - Update & Test

  • To test the  API works, you must specify a workcentre ID in the URL e.g. OFS001. 

  • Change it back to once the testing is done.

Creating the Alert Trigger

Step 8 - Navigate to ‘Alerts & Flow’

  • Create a dedicated 'Alert Group' e.g. Alert Expiries

  • In that Alert Group, create a new 'Alert' and name it

  • Click the expand icon to edit the alert

Step 9 - In the Alert, navigate to the 'Triggers' tab

  • Click 'Machine State'

  • Click the + to add a new trigger

Step 10 - Fill in the following:

  • In Machine State, tick ‘Setup’

  • Toggle on ‘Group Adjacent Spans within Jobs’

  • Toggle on ‘Offset’ and enter in target time. e.g. minutes

  • Set the units i.e. minutes, hours or counts

  • Select the Lines

  • Select the ‘Service’ as per Step 4.

 

If there are variations of Setup Expiry times at SKU level

Step 11 - In the products list, fill in the column 'targetSetupTime'

If the targetSetupTime is not pre-determined and operators must enter the value, ensure 'Client Editable is toggled on for the 'targetSetupTime' field

  • Navigate to Products

  • Tick the Line

  • Click the pencil icon

  • In 'Default Product List Data':

    • Toggle ON 'targetSetupTime'

    • Toggle ON 'Client Editable'


Step 12 - In the alert Trigger, navigate to Conditional Expression

  • Toggle ON

  • Enter the code and change the value as per the setup target time
jobmeta["targetSetupTime"]==30

Note: You must create a new trigger for every variation of Setup time e.g. 30mins, 60mins and 90mins. Follow Step 9 onwards.