Sensor layer
Sensors at every service point report real-time conditions: how full a bin is, how low a dispenser is running, the fluid level in a tank, and the location of an asset that moves. The signal is real, not an estimate based on a schedule.
Three layers. One platform. The work that needs doing gets done.
ClearPath senses real-time conditions at service points and tracks the location of assets that move. It decides which points need attention and sends the work to the team that does it. Here’s how the three layers work together.
The Three Layers
Three things make ClearPath work.
Sensors report what’s happening. The platform decides what to do about it. A partner owns the customer relationship. Each layer does one job. Together, they replace calendar-based service with demand-triggered dispatch.
Layer One: Sensors
Sensors that fit the job.
Every service point gets a sensor matched to what’s being measured, and assets that move get location tracking. How it’s measured changes by industry. The job stays the same.
In waste and recycling, sensors measure accumulation: how full the bin is. In restroom consumables and venue and course operations, they measure depletion: how much paper, soap, sand, or other supply is left. In fleet fueling, they measure fluid level across vehicles spread over many locations. For assets that move, the platform also tracks location. The pattern is the same in every case: a physical condition or position becomes a real-time signal.
The sensors do one job well: they make the invisible state of every service point visible to the platform. They report at a pace that fits how the operation runs.
Layer Two: Dispatch
Logic that turns signal into work.
The dispatch layer is where ClearPath earns its keep. It’s the difference between raw sensor readings and a real operational result.
Sensor data alone is noise. The dispatch layer reads every signal across every service point and applies threshold rules set up for the operation. It weighs priority and routing, then makes a dispatch decision: which points need service now, which can wait, and which route makes sense for the points that need attention.
The decisions update continuously. A bin that wasn’t on the list ten minutes ago is on it now if it has crossed the threshold. A route in progress can be reordered if a higher-priority point comes in. The signal sets the pace, not the schedule.
This is work calendar-based service can’t do. A calendar can’t see which bin is full. The dispatch layer can.
Layer Three: Partners
Always under the partner's brand. Always the partner's own.
Every ClearPath deployment runs under the partner’s brand. The platform underneath is the same, and the customer-facing experience belongs to the partner.
That means the mobile view the custodian opens, the dashboard the supervisor checks, and the connection to the partner’s billing and operational systems all run under the partner’s name. The customer buys from the partner, with the partner’s relationship and support behind the sale.
ObjectSpectrum runs the platform. Partners sell it under their own brand. The two roles stay separate.
The Workflow
Four steps, on a loop.
The cycle runs continuously, and every signal starts the next dispatch.
Calendar-based service runs in fixed cycles set in advance. ClearPath runs in cycles set by what is happening in the operation. The schedule used to be the input. Now the signal is.
Four Paths From Here
Pick your next move.
See the ROI engines
Three ways the math comes back: labor, coverage, and capacity.
See the capabilities
What the platform does today, including sensor types, dispatch logic, and integration support.
Get ClearPath in your operation
Tell us about your operation. We’ll connect you with the right way to deploy ClearPath.
Become a Partner
Equipment manufacturers and service operators sell ClearPath under their own brand.