The service people actually experience
A dated examination of delay propagation in field and asset coordination software, and the operating choices that shape coordination. The subject is easiest to see in a work order passing between an asset register, an offline field device and a supervisor review queue. A small error at that point does not stay small: it creates another message, another check, another journey or another version. Across 2,050 monthly records, even a single unnecessary return step becomes material operating work.
The 2016 files linked to this note are Alder Civic Logistics, Bramwell Street Works. They are used as operating context, not as evidence for a market-wide claim. The purpose of the article is to ask how delay propagation can improve coordination when work orders, asset records and intervention evidence have to remain usable despite uneven source data and offline conditions.
PTD takes a deliberately strong position. Waiting that can be identified, classified and routed should be engineered out. Repeated judgment should be converted into a rule when the evidence is stable. Machines should inspect, reconcile, forecast and prepare the next action at a scale no small operating team can sustain manually. People should retain authority over safety, rights, capital and exceptions whose cost is genuinely asymmetric.
Useful facts and their limits
Google's SRE work separates useful automation from uncontrolled complexity. Service-level objectives, monitoring, testing and post-incident learning remain in place while repetitive toil is removed.
NIST's interoperability work treats a connected physical system as a system of systems. A field application should therefore expose stable identities and interfaces rather than hide the operation inside one vendor's database.
The useful software measure is not screen activity. It is a change in elapsed time, first-pass completion, error severity or capacity at a defined service level. Those measures can be compared before and after a release.
A base case in numbers
Consider an illustrative operation processing 2,050 items a month. This is a model, not a PTD company result. At a return rate of 9%, approximately 184 items re-enter the queue. If clearer data, automatic validation and guided decisions reduce the rate to 6%, the queue avoids about 61 returns each month.
At 29 minutes for each returned item, that change releases roughly 354 staff hours a year. At an illustrative loaded cost of €67 per hour, the direct capacity value is approximately €23,718. The more important gain may be outside payroll: shorter customer delay, fewer repeat visits, earlier rights clearance or less time with a physical asset unavailable.
The arithmetic is intentionally transparent: volume × change in return rate × handling time. It can be challenged line by line. A project should not be approved because the result sounds large. It should proceed only if a baseline sample of at least 260 records confirms the volume, return reason and time per return, and if quality or safety does not deteriorate when the step is removed.
From record to automation
The product should combine an asset graph, a versioned work-order state machine, offline-first capture, role-based permissions, an event log and a rules layer that can recommend but not silently change a controlled record. Every automated action needs a source, confidence level and reversible event.
The data model should be smaller than the organisation chart. Identity, state, evidence, owner and next action are the core. Everything else must justify its collection cost. A field that does not change a decision, satisfy a legal requirement or improve later learning should not be mandatory merely because software can store it.
Automation then operates in layers. First, validate format and completeness. Second, reconcile the item with the current master record. Third, propose a classification or next action. Fourth, execute low-risk routing inside a defined permission. Fifth, measure the result against the accepted baseline. This sequence prevents an automated recommendation from becoming an unexplained fact in the operating ledger.
A time-boxed pilot
A credible deployment can begin in 12 weeks. Weeks one and two freeze definitions and sample the current process. Weeks three and four instrument waiting, rework and error states without changing the workflow. The next four weeks run the new rule on a limited cohort while keeping a control group or the preceding comparable period.
The release decision should use five measures: first-pass completion, elapsed time, staff time, error severity and the share of records requiring manual override. A faster system that creates more severe errors fails. A slower pilot can still pass if it exposes hidden work and produces a baseline the organisation did not previously have.
Scaling requires a second gate. The system must show that performance survives a different team, location or catalogue; that its fallback works during disconnection or source failure; and that operators can explain why an automated recommendation was accepted. Only then should the same architecture receive more volume.
The investment question
For an owner, a program built around delay propagation becomes investable when it changes repeat economics rather than creating a one-off presentation. The relevant evidence is a sustained reduction in avoidable work, a shorter asset or catalogue cycle, more capacity at the same fixed cost, or a lower requirement for corrective capital. Revenue growth is useful, but operating leverage is the stronger test.
Capital should be staged around proof. The first amount buys measurement and integration. The second buys deployment to a wider operating perimeter. The third buys automation or physical capacity only after the constraint has moved. This avoids installing technology around an unexamined process and then calling the resulting complexity transformation.
The same logic explains why PTD holds companies for several years. Data quality, work design and maintenance intervals improve through repeated cycles. The value is cumulative: each corrected identifier, accepted definition and captured exception reduces the cost of the next decision. A short ownership horizon can harvest a software launch; it is less suited to building an operating memory.
Working conclusion
Small Delays, Large Coordination Surfaces argues for a narrow but forceful conclusion. Everyday efficiency is not an abstract social objective. It is the sum of queue length, elapsed time, first-pass completion, asset availability, energy and material consumed, and the number of decisions that reach the right person with enough evidence.
Technology should be expected to improve those quantities. The burden of proof belongs in the implementation: a frozen denominator, a dated baseline, a visible error budget and a comparison that survives a change of team. When the result is weak, the system should say so. When it is strong, the organisation should scale it quickly and redirect people toward work that requires judgment rather than repetition.
This position is recorded at 2016-08-16. The next review should replace the illustrative figures with an accepted cohort, retain the original model and show which assumption changed. That is how a technosolutionist thesis becomes an operating record instead of a slogan.
Sources and data notes
- Google — Site Reliability Engineering2016 · Reference for service-level objectives, eliminating repetitive toil, monitoring, automation, testing and learning from failure.
- International Telecommunication Union — ITU-T Y.4901 — KPIs related to ICT use in smart sustainable cities2016 · Reference for early city-service indicator design across infrastructure, transport, public services and operational efficiency.
- Library of Congress — PREMIS Data Dictionary for Preservation Metadata, Version 2.22012 · Reference for a practical preservation record built around objects, events, rights, agents and the intellectual entity being preserved. This 2012 version is used for issues published before PREMIS 3.0.
- National Institute of Standards and Technology — Framework and Roadmap for Smart Grid Interoperability Standards, Release 3.02014 · Reference for technology-neutral architecture, interoperability, testing and certification in a networked physical system.