Customer Portals are now available!Get Started
API Documentation was updated!Learn more
Usage-Based Strategies
Usage-based strategies create work orders when a device reaches a certain usage threshold — for example, after a number of missions or operating hours. This performs maintenance on demand, based on actual load.
When to use usage-based strategies
Section titled “When to use usage-based strategies”When wear depends on actual usage rather than calendar time:
- Wear parts that degrade with every mission
- Components serviced after defined operating hours
- Consumables replaced after a number of cycles
Example scenarios:
- Maintenance after every 1,000 robot missions
- Service after every 500 operating hours
- Inspection after a defined number of production cycles
Configuration
Section titled “Configuration”Define the trigger using:
- Metric — Which usage metric to track (e.g. number of missions, operating hours)
- Threshold — The value at which a work order should be created
After each triggered work order the count restarts, so maintenance recurs every time the threshold is reached.
Practical tips
Section titled “Practical tips”- Pick a metric that truly reflects wear (missions rather than mere power-on time).
- Combine with baseline scheduled maintenance if servicing is needed even without usage.