Skip to content

Work Order Management Service

Idea

“Work orders” provide a basic digital workflow for work requests (maintenance, repair, inspection and incident handling) that are essential to monitor asset health and to detect technical issues before they lead to asset failure and downtime. You can create, track and update work orders using an API.

Access

For accessing this service, you need to have the respective roles listed in Work Order Management roles and scopes.

Basics

Work Order provides a ticketing way to plan and assign audits or maintenance of assets. Detailed Work order helps the assignee to prioritize and execute the task. Timely updated work order provides the status overview of all work orders.

  • Title*: A well-defined title should summarize the task or expectation.
  • Description: A more detailed description about the work order should be added.
  • Assigned to: An assignment defines the person to work on the task. The assignee gets an email notification with the work order link, if 'Notify Assignee' flag is provided as 'true'.
  • Due Date*: This date sets the expectation about getting the task completed.
  • Status: Work order can be updated to have different statuses to reflect the progress. The following status are available:
    • OPEN: Default status of work order at the time of creation.
    • INPROGRESS: A work order is expected to be in this status as the work starts.
    • ONHOLD: A work order can be marked as on hold using this status.
    • OVERDUE: System puts the work order in overdue if it is not closed by the defined due date.
    • DONE: A work order can be moved to this status as the work gets done.
  • Priority: The following priority options are available to prioritize the work items:
    • LOW
    • MEDIUM
    • HIGH
    • EMERGENCY
  • Type: Type of a work order defines the reasoning behind the initiation of that work order
    • PLANNED: This defines that work order is a planned activity or scheduled activity to be done.
    • INCIDENT: This defines that work order is an outcome of an incident happened and it is not a planned work.
  • Association: Work orders can be associated with different entity types e.g. ASSET.
  • Attachment: Attachments can be any files supporting the work to be done or the details captured while working.

Features

  • Intuitive overview enables easy monitoring and prioritization of work orders
  • Due dates and assignments enable convenient tracking and planning
  • Details can be easily added using attachments and associations

Limitations

  • A tenant can create 1000 work orders. You may delete older/unused/Done work orders to maintain the total count within this limit.
  • A work order can have a maximum of 10 attachments. You may delete attachments to attach new ones if total has reached this limit.
  • Currently, a work order can be associated only with entity of type ASSET.

Example Scenario

Work orders could be created for the following reasons:

  • Follow-up work orders - to schedule a repair (at a later date) found during ongoing activity
  • Work orders for incidents or reported problems (non-routine work orders)
  • Planned work during scheduled plant shutdown
  • Equipment / Process modification projects
  • Work orders for compliance of regulations and audits
  • Outcome of these work requests carry insights that could optimize operations, extend asset life, improve worker safety.

Any questions left?

Ask the community


Except where otherwise noted, content on this site is licensed under the MindSphere Development License Agreement.


Last update: March 21, 2022