Meters & Usage-Based Automations

A meter tracks a usage value that accrues over time on a specific asset or vehicle — engine hours on a mower, odometer miles on a truck, gallons through a sprayer, cycles on a piece of equipment. Unlike a PM schedule, which fires on a calendar date, a meter fires based on how much the asset has actually been used.

Meters exist to feed one thing: usage-based automations. Once a meter is recording readings, you can wire up an automation in CMMS > Automations that watches it and reacts the moment it crosses a threshold you set.

1. Open any asset or vehicle detail and go to the Meters tab. Click + New Meter.
2. Choose the unit — miles, hours, gallons, cycles, or whatever fits the asset — and give the meter a name (e.g. "Odometer" or "Engine Hours").
3. To log usage, click the meter and use + Add Reading. Enter the value and the date.
4. The meter's current value always reflects the latest reading — there's no separate "current value" field to keep in sync manually.

1. Go to CMMS > Automations and click + New Automation.
2. Set Trigger Type to Meter Threshold, then select the specific meter to watch.
3. Choose the operator — ≥ is the one you'll use almost always for cumulative meters like mileage or hours, since those values only go up. Enter the threshold value to compare against.
4. Pick an action type. If it's Create Work Order or Create WO Request, you can also set a Service Interval — see the worked example below for what that does.

This is the canonical use of meter automations — a recurring, mileage-based service that keeps re-scheduling itself without anyone touching the threshold by hand.

1. Truck #4 has an Odometer meter, currently at 31,200 miles from past readings.
2. An automation is configured: Trigger = Meter Threshold, Meter = Truck #4 — Odometer, Operator = ≥, Threshold = 36,000. Action = Create Work Order ("Oil Change"), Service Interval = 5,000 miles.
3. A crew member logs a new odometer reading of 36,150 miles. The automations engine runs instantly, sees 36,150 ≥ 36,000, and creates the "Oil Change" work order right then.
4. The automation's Pending Reset flag flips to true — see the next section for why. No second work order gets created no matter how many more readings come in while it's pending.
5. A tech performs the oil change and marks the work order Done. That closes the loop: Pending Reset clears, and the threshold automatically advances by the 5,000-mile interval — from 36,000 to 41,000 miles.
6. Later, another reading pushes the odometer past 41,000. The automation fires again, a new Oil Change work order is created, and the cycle repeats — 46,000 next, then 51,000, and so on — with no one ever editing the threshold by hand.

Pending Reset is the state that keeps a meter-threshold automation from firing over and over. Without it, every single reading that still satisfies the operator (e.g. every reading ≥ 36,000 miles, which is all of them once you've crossed that line) would create another work order.

Think of it as a simple two-state machine:

Every trigger type an automation can use, and every action it can take.

The Automations page also offers ready-made templates — click any template card to add it to your org instantly, no manual configuration required.

• Low Stock Alert — Fires on Part Low Stock; creates a requisition automatically.
• PM Due Reminder — Fires on PM Schedule Due; creates a work order ahead of the due date.
• WO Completed — Notify Team — Fires on Work Order Status Changed (Done); sends a notification.
• PO Approved — Fires on Purchase Order Status Changed (Approved); sends a notification.

A few related pieces are easy to conflate with meter automations. They're deliberately separate systems:

• PM Schedules are calendar-based, not usage-based — they fire on a recurring date regardless of how much an asset has actually been used. See the PM Schedules guide for how those work.
• Zapier's "Meter Threshold" trigger is a separate, per-Zap configuration that lives outside Equipt entirely — it doesn't use, share, or affect the Pending Reset state of any automation configured here. See Meter Threshold, in detail in the Zapier guide.
• Samsara (Settings > Integrations, API key) syncs vehicle odometer readings automatically once connected, updating the corresponding vehicle meter exactly as a manual reading would — which can trigger mileage-based automations the same way.