Usage-based Actions
Equipment doesn't age by the calendar; it ages by how hard it works. Most maintenance schedules are still based on fixed dates, resulting in machines being serviced either too early or, worse, too late, increasing the risk of breakdowns.
Usage-based Actions lets you trigger maintenance tasks automatically based on real consumption data: operating hours, units produced, liters dispensed, whatever metric actually reflects the wear on your products.
When a threshold is reached, the right action automatically fires at the right time.
By completing the action, the counter is automatically reset, even if the action is done earlier than expected.
In the Console, when defining actions, you can now specify the metric and threshold to activate the action, without the need to define any extra computed metric.
Work Order Management
We've introduced the Work Order, a dedicated tool for technicians to organize and track all actions to be performed at a customer's facility, to improve traceability and accountability.
Technicians completing Actions can now add Notes and Attachments (e.g., photos of damaged or broken parts) to better document the work they performed.
While completing the physical work, Actions can be marked (individual or multiple) as done (fully or partially) or discarded, with the option to provide a reason when needed.
For each Action, its execution history can be inspected to search for past performed actions at any time.
Work Order management is embedded in a new section of the Action List widget you are already using, so the configuration is quite easy; just set permissions without the need for any extra effort.
Ticket Management
The DPS has been enriched with a Ticketing system to help end-users create and manage support requests in a consistent, structured process, ensuring quick access to product data, faster response times, and no risk of lost or duplicated work.
Here are the main Ticket features:
Ticket creation: DPS users can open new tickets to request support for any issue, directly from the platform.
Ticket context: When a ticket is created, the relevant context is automatically attached, including the associated product, the customer, and the triggering event (e.g., failure, anomaly).
In this way, support teams always have the full picture without any manual lookup, reducing the time to respond.Ticket search and visualization: Browse and search through both open and closed tickets, making it easy to find any request at a glance.
Ticket management: Service providers (Organization or Partners) can fully manage tickets. This includes: updating statuses (e.g., Open, Closed), setting priority, assigning users, and monitoring progress throughout the support lifecycle.
Notes and attachments: All parties can exchange information directly on the ticket using notes and attachments, gathering all required information in one place.
The ticket management feature is ready to use; all you need to do is set the permissions for who can view the tickets and add a predefined page to the desired views with a single click.
Bug fixes (DPS)
The thing list did not take into account the
latestMetricValueTimestamp > 0query condition.Clicking the shift button multiple times in the Period Field resulted in an inconsistent period being selected.
In some cases, the SSO login did not complete if done after a previous console login.
Bug fixes (Console)
The Test Algorithm button did not include the URL of the CSV file of work sessions within the script’s JSON input.