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

How to make a state transition to a downtime at a scheduled time?

This article explains how to configure OFS to automatically allocate a downtime reason e.g. lunch break — at a set time each day.

Step 1 — Create the downtime reason

  1. Open Fusion Manager and navigate to the Reason tab.

  2. Create a new reason — e.g. Lunch — and set the type to Planned Downtime.

  3. Note the Reason Code assigned to this reason. You will need it in Step 3


1d) Navigate to Reason Assignment and assign the reason to the relevant line(s).

Screenshot 2026-06-19 at 3.43.57 pm

Step 2 — Create a dedicated user account

This account is used to authenticate the web service call. Create one account and reuse it across all scheduled downtime services.

  1. Navigate to the Users & Operators tab in Fusion Manager.
  2. Click Add User and complete the following fields:
      • Name — e.g. Alerts
      • Login — e.g. alerts
      • Password — set a strong password and record it; you will need it in Step 3
      • Role — set to Analytics User

Screenshot 2026-06-19 at 3.45.06 pm

 

 

Step 3 — Create a web service

NOTE: You will need one web service for each downtime reason you want to schedule.

  1. Navigate to the Services tab in Fusion Manager.
  2. Click Web to create a new web service.
  3. Give the service a clear name — e.g. Lunch Start.
    Screenshot 2026-06-19 at 3.47.32 pm
  4. In the URL field, enter the downtime allocation endpoint for your line: https://customer.ofsxpress.com/WorkcentreID/server/control/downtime/allocate/@reasoncode
    1. customer — your organisation's OFS subdomain (e.g. demo)
    2. If OFS is hosted on a local server, use localhost instead of a subdomain: https://localhost/WorkcentreID/server/control/downtime/allocate/@reasoncode
    3. WorkcentreID — the OFS line identifier (e.g. OFS001). Find this in Fusion Manager or in the console page URL.
      For multiple lines, use the code below in place of a fixed WorkcentreID. 

    4. @reasoncode — replace with the Reason Code from Step 1 (e.g. @Administration::Lunch1). The Reason Code is found in the reason created in Step 1.
    5. Example:






  5. Open the Authentication tab and enter the login credentials for the user created in Step 2.

 

Step 4 — Create an alert and alert group

Alerts organise the triggers that fire your web services. Create a dedicated alert group for scheduled downtime alerts, then add an alert inside it.

  1. Navigate to the Alerts & Flow tab in Fusion Manager.
  2. Click Add Alert Group and give it a name — e.g. Scheduled Downtime.
  3. Inside the new group, click Add Alert.
  4. Complete the alert fields:
  5. Click Save.


Screenshot 2026-06-19 at 3.57.56 pm


Step 5 — Create the scheduled trigger

  1. Within the alert created in Step 4, navigate to the Total Time or Count trigger type and create a new trigger.

  2. Configure the trigger as follows:
    1. Select the line(s) this trigger applies to
    2. Select the web service created in Step 3 (e.g. Lunch Start)
    3. Toggle on 'On Schedule'
    4. Enter the time the downtime should start (e.g. 12:00)
    5. Select the date from which the schedule should begin
    6. Select the repeat frequency (e.g. Daily, Weekly)
    7. Select the days of the week the trigger should fire
    8. Click Update to save the trigger.