Consumables used at the property
With Input Usage enabled, record the quantities used, wasted and returned. Usage logs connect consumption to the route, service and property, retaining actual cost context for review.
Explore input-use records →Keep the record behind the completed visit.
Connect assignment, arrival, field time, service activity and the outcome at the property. OrdexisOne gives the office a way to understand how the work happened and gives staff the controls to record it.
Order Now →Distinguish travelling, working and waiting.
Route and property controls capture the different parts of the field day. Staff can review the active state and use manual assistance when location events need correction.
- Route state
- Start, pause, resume and end the route. Retain the state of the assigned day as the team moves between properties.
- Arrival and departure
- Use supported property geobox entry and exit detection or manually confirm entry. Location updates depend on the staff member's permission and operating configuration.
- Driving, on-site and hold time
- Record travel and time at the property separately from hold time. The distinction gives the office more context than a single elapsed duration for the whole day.
- Manual timing assistance
- Use supported manual controls when automatic events need correction, helping the recorded activity reflect the visit staff actually carried out.
Keep service activity and exceptions with the stop.
The property workflow allows staff to review service status and complete the work with its operating context. Field records preserve what matters for the office's next question or action.
The same approach supports a technician callout, a cleaning visit, a treatment service or an assigned project stop. The configured service and field workflow determine what staff record.
Explore the full field workspace →Hazards and incidents
Submit hazard or accident reports in the operational context. The office can review the record when an issue affects the work or requires further attention.
General field reports
Record other field observations through the general report workflow. Preserve the context for support, follow-up arrangements and discussion of the service delivered.
A record that reaches the office
Preserve supported activity through the end of the route.
Handle a connection interruption
Supported pending field activity can be retained when connectivity is interrupted. Staff can see pending synchronization status, and supported actions synchronize when the connection returns.
Close the assigned day
Review the end-of-route state and enter an approved route-end zone when required. Reconcile route activity and materials so the operating record includes completion and the quantities that returned.
Keep scheduled service visible
The Service Schedule Operations Console presents generated service occurrences as records the office can search, filter and inspect, with timing, status, order, service and property context.
Explore scheduled-work oversight →Review performance and resolve questions with context.
Routing Metrics connects route runs, stops, inputs and financial views. Open the detail behind a result and see how staff time and service activity relate to the customer work.
Inspect the relevant stop
Review stop date, staff, customer, service, status, travel time, property time, revenue and gross result. Route details provide the broader run and input context.
Filter the operational view
Focus by employee, customer, service, route division, run kind, run or stop status and input. Review completion and outcomes alongside driving, on-site and hold time.
See where information is incomplete
GPS quality, event coverage and audit gaps identify limits in the available record. Use these indicators when interpreting time, cost and profitability views.
Connect the field record to your operation.
Staff tools run in a responsive PWA. Location-assisted events depend on device permission, browser support and configuration. Input records depend on enabled capabilities; supported pending synchronization applies to the available field actions.