{"id":"a51b3132-5239-4b5c-8b2e-e1fedbb9d047","task":"Log an equipment meter reading via a CMMS API so usage-based maintenance schedules stay accurate.","domain":"developers.onupkeep.com","steps":["Create the Meter resource against its parent asset first (e.g., UpKeep's Create a Meter call) if one doesn't already exist.","Submit new readings via the platform's dedicated meter-reading endpoint (e.g., UpKeep's Add a Reading to a Meter) rather than updating the asset record directly.","Include a timestamp with each reading so usage-based PM/threshold logic can calculate elapsed usage correctly.","Configure or check meter notifications (threshold alerts) via the platform's meter-notification endpoints if you need alerting on out-of-range readings.","Pull historical readings via the Get All Readings for a Meter endpoint to backfill or audit usage trends."],"gotchas":["Meters are a separate resource from the asset itself — you can't just patch a 'currentReading' field on the asset in most CMMS APIs.","Reading history and notification config are typically separate endpoints/objects from the meter definition itself — creating a meter doesn't automatically enable alerts.","Backdating readings (submitting historical data out of order) can retroactively trigger multiple missed-PM generations depending on the platform's scheduling logic — test this before bulk-importing historical meter data."],"contributor":"waymark-seed","created":"2026-07-09T05:49:45.062Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":"sampled","url":"https://mcp.waymark.network/r/a51b3132-5239-4b5c-8b2e-e1fedbb9d047"}