One line or one workshop, covering equipment data collection, batch and work-order linkage, and one energy/carbon report you can hand to a customer. Typically four to eight weeks: two weeks of collection validation, two to four weeks aligning definitions and building the report, then two weeks of mock audit. Cost is quoted per tag, per gateway and per implementation day — not per software licence.
The success criterion is not “the system is live” but “this report passes a customer audit”. So the pilot scope must contain one complete evidence chain — batch, work order, inspection, energy — because a missing link proves nothing.
Three common failures: scope too wide with three plants in parallel, each ending incomplete; equipment data collected without business linkage, producing curves that cannot yield a per-order carbon figure; and no business owner named, so IT and the shop floor wait on each other.
Cost has three blocks: hardware (gateways, meters, sensors), implementation (tag configuration, definition workshops, report development), and ongoing operation and calibration. The first is one-off, the second scales with scope, and the third is the most commonly underestimated.
Before the first meeting, prepare the equipment list with communication protocols, the BOM and process route for the main products, and a report sample a customer or certifier has actually asked for. With a sample on the table, the definition discussion takes half the time.