The Machine Came Back. The ERP Missed It.
A lift returns at 4:47 PM. The contract still shows it rented. The meter photo is on a phone. Service does not know whether it is available. One physical asset now has four administrative lives.
A forward deployed AI engineer follows the return through inspection, service, availability, and billing. The goal is a reliable event path, not a heroic employee with a good memory.
Record the Return Once
The agent reads a return ticket, meter photo, and damage note. It proposes the asset, contract, return time, fuel level, and inspection status. Rules verify identifiers and evidence. A person approves damage findings and charges.
Use one event envelope across the yard, service queue, and ERP. CloudEvents version 1.0.2 defines a common event format across systems. Each system receives the same identity, source, type, time, and business data.
Time matters. RFC 3339 defines a consistent Internet timestamp format. Store the time zone, or closing time becomes tomorrow’s argument.
Use five states: rented, returning, inspection, service, available. Only approved transitions reach the ERP. A unique key stops retries from closing the contract twice.
Reuse the Boring Machinery
The reusable asset is the connector, schema, extraction prompt, rules, approval queue, audit log, and evaluation set. Over the past eight months, these parts have become easier to package and test. Rental policy remains specific. Generic magic is specific bullshit waiting to happen.
The ERP stays authoritative for asset status, billing, and accounting. AI proposes messy details. Code checks state and totals. People approve costly exceptions.
Measure the Queue
Illustrative calculation: 70 returns each week at eight minutes of reconciliation require 9.3 hours. At two minutes each, they require 2.3 hours. At an assumed loaded labor cost of $42 per hour, seven recovered hours equal $294 of weekly capacity, not guaranteed profit or payroll savings.
Track delayed availability, duplicate receipts, disputed charges, missing evidence, and assets reopened after inspection. Any utilization or revenue improvement must be proven from actual rental and collection records.
If the yard sees the lift and the ERP does not, the machine is not in two realities. The integration is broken.