Compare the operating models
In this fictional example, C pays at office O while maintenance occurs at S1/S2, each with separate equipment and gate instructions. Changing C’s address for each visit loses site history.
| Business requirement | Customer address field | Service-site record |
|---|---|---|
| Billing office O | Commercial-account detail | Not necessarily maintained |
| S1 equipment and access | Mixed with billing | Site-specific context |
| S2 visit | Hard to separate from S1 | History points to S2 |
Work through the chosen model
Map C → S1/S2, with O as billing address. Sites store address, supplied operational access instructions, assets and visit links. Each job chooses a site; only capture access details needed for the task.
- Select service site
- Read that site’s context
- Attach completed visit
Sites help repeat visits but need updates when equipment/access changes. This differs from resolving which historical address a shipment used.
An S2 visit adds S2 history, leaving O’s billing address and S1 equipment unchanged.
When the other model fits
One-off delivery has no continuing site context. Always create a site?
Show the worked answer
No. An order address may suffice.