visibility.cloud

Where it happened.

Every event has a place: the read point where the scan happened and the business location responsible for it. The seam between two custodians is not only a moment, it is a dock, a lane, a bay, and the place is part of the record, not an annotation on it.

Read point and business location.

The standard separates where a thing was read from the location responsible for it, and the spine keeps both. A carton read at a specific dock door, at a facility owned by a named party: two facts, recorded distinctly, because a dispute about custody is usually a dispute about which of the two you mean.

Your scope, and nothing outside it.

You see the places inside your own scope. What is outside it is absent, not grayed out and not redacted: there is no shape left behind to argue about. A location you were never granted simply is not in the answer.

The standard gives you this dimension. Here is what it still can't tell you.

EPCIS 2.0 §7.2.2 defines five event dimensions — and no performer is among them. The record can say a company did a process. It cannot say who observed the event. That answer has its own door.

where: answered — readPoint: dock 9 · bizLocation: dc-west who: (no field exists in the standard)

Who held it →

See your first trace.

Your capture workspace is provisioned from the seat list — we write when your seat is ready.