Work Orders 2.0
Overview
The Work Orders module has been redesigned and simplified. This page shows the key changes between 1.0 and 2.0.
To see all the designs, go to https://zpl.io/VK865nE.
Key Navigation / Functional Changes
Type of Change | Field / Subject | Description |
|---|---|---|
Enhancement | Sidepanel Tabs | The new sidepanel has now been split into 2 distinct tabs which include information that was previously stored in row actions in FSE 1.0 (See below for more details). |
Enhancement | Work Order Dates | |
Removed | Workflow Approval & Task Approval | Only Tasks require approval; there is no approval on the WO level. Approval happens in Task Scheduling (previously Scheduling and Dispatch). We have removed those two modules from Work Orders. |
Removed | Spare Parts, Consumables, Tools | No option to add Inventory to tasks in MVP. This is on the roadmap to add back into FSE in Q2 and will include integration with actual Inventory to ensure the inventory required is actually on hand. |
Removed | Task Dependency | This feature was not fully functioning in FSE 1.0. Will will introduce this feature in a later release. |
Active Work Orders
This section describes the changes with accompanying screenshots between FSE 1.0 and FSE 2.0.
Main Page (Active Work Orders)
The fields in the datagrid were updated as seen below.
FSE 1.0 | FSE 2.0 |
|---|---|
 |  |
Work Orders (Side Panel)
Type of Change | Field / Subject | Description |
|---|---|---|
Enhancement | Sidepanel Tabs | The new side panel has now been split into 2 distinct tabs which include information that was previously stored on a single side panel page in FSE 1.0:
|
Enhancement | Simplified dates on WOs | There are only two dates on the WO itself and they now include date and time:
|
Enhancement | Publishing Tasks vs. Work Orders | Work Orders no longer need to be published and instead are simply saved. Instead, the save as draft and publish functionality has been moved to the Tasks within a Work Order. This enables you to publish Tasks individually, which sends the task to the Task Scheduling module. You can also add Tasks to Work Orders at a later date if needed. |
Enhancement | Effect of Contracts on WOs and how they impact other fields | In FSE 1.0, users select the Contract first which then pre-fills the Customer. Contracts and SLAs were required, leading to less overall flexibility. In FSE 2.0, SLAs are optional on the Contract level. There’s also been a change in UX when creating WOs where Customer is selected first and the Customer may or may not have a contract associated with their account. When creating a WO, a user first selects a Customer. This Customer may have four different Contract scenarios that now impact related fields.
|
Enhancement | Priority | FSE 1.0: Independent Priority fields on both the WO and Task. WOs could be given a priority which determined the SLA, but a Task could have its own priority that was used only for scheduling purposes; it had no effect on the SLA clock. FSE 2.0: Priority is now ONLY on the Work Order level and not on the Task, which inherits the priority of the Work Order. *Note that this could change in later versions depending on feedback from Solutions, Sales, and Customers. |
Enhancement | Work Order Statuses | Work Order Statuses have changed.
|
Removed | Spare Parts, Consumables, Tools | No option to add Inventory to tasks in MVP. This is on the roadmap to add back into FSE in Q2 and will include integration with actual Inventory to ensure the inventory required is actually on hand. |
Removed | Escalation Hierarchy | This feature was not fully functioning in FSE 1.0. We will introduce this feature in a later release. |
FSE 1.0 | FSE 2.0 |
|---|---|
Old Work Orders Sidepanel | Work Orders Information Tab Tasks Tab |
Add Tasks to Work Orders (Side Panel)
Type of Change | Field / Subject | Description |
|---|---|---|
Enhancement | Publishing Tasks vs. Work Orders | Work Orders no longer need to be published and instead are simply saved. Instead, the save as draft and publish functionality has been moved to the Tasks within a Work Order. This enables you to publish Tasks individually, which sends the task to the Task Scheduling module. You can also add Tasks to Work Orders at a later date if needed. |
Enhancement | Notes | Now you can capture Task-specific notes in this new field and pass the information on to Technicians. This field will get passed to the dispatcher when scheduling a task and then to the Technician if this field is enabled in the Mobile Workflow. |
Enhancement | Dates | Dates have been simplified. The Scheduled Start Date (Optional) is a field that gets passed to the Dispatcher when scheduling a task. It can be edited here and also in Scheduling and Dispatch. |
Enhancement | Customer Site and Info | We are now displaying the customer address/map and other Customer details in this side panel. This gets pre-populated based on which customer site you select in the Work Orders Side Panel. |
Removed | Task Dependency | This feature was not fully functioning in FSE 1.0. We will introduce this feature in a later release. |
Removed | Link Task to an Asset | We have removed the ability to add an Asset to Tasks for purposes of corrective or preventive maintenance. This is also on the Q2 roadmap along with Asset Logs to show the Task history of work performed on the Asset. |
Removed | Zone | This was a holder-over from the Singtel demo and has been removed. |
Removed | Deploy task when work order status is… | As the “save as draft” and “publish” functionality has been moved from Work Orders to the Task level, this functionality is no longer required. |
FSE 1.0 | FSE 2.0 |
|---|---|
Old Tasks Sidepanel | New Tasks Sidepanel |
Roadmap / Future Enhancements
Release | Feature | Description |
|---|---|---|
20.3 | Spare Parts, Consumables, Tools | We will be adding these back to FSE in Q2. They will each show up as a separate tab in the WO side panel. |
20.4 | Task Dependency | We will introduce a fully-functional version of Task Dependency in this release. |
TBD | Assign Task to an Asset | Ability to link Tasks to an Asset for purposes of corrective or preventive maintenance. |
TBD | Escalation Hierarchy | This feature was not fully functional in FSE 1.0. We will look to add this feature back in a future release. |