Locate
Find assets across floors and zones using live spatial context. The plan is the default reading surface. The stacked 3D view is there when vertical relationship matters.
SiteThread
SiteThread
Know where things are. Understand what happened. Move work forward.
SiteThread explores how live asset positioning can become an operational workspace rather than simply a collection of dots on a map. It connects current location, movement history, exceptions, and handoff workflows so operators can understand what is happening and decide what to do next.
Independent product exploration using synthetic data.
Beyond the dot on the map
A marker says where something was observed. An operation needs more than that.
A location marker can tell someone where an asset was observed. The people coordinating the work also need to know whether that observation is current, what happened before it arrived, whether movement is behind plan, whether telemetry has disappeared, whether intervention is required, who should act next, and whether a handoff has actually been confirmed.
SiteThread is the layer that connects spatial evidence with that operational workflow. The demo is a fictional site, Northworks. The question is the same in a yard, a ward, or a jobsite: do not let a map pin stand in for finished work.
Core concepts
Locate, investigate, coordinate, and replay without mixing those jobs together.
Investigate
Inspect movement history, dwell, stale observations, and the evidence behind a status. A gap in the track stays a gap. The path is not drawn across the hole.
Coordinate
Turn an expectation into a watch, a task, and a handoff. The watch is the job: these assets, this destination, this time. People still assign and confirm.
Replay
Move backward through time without confusing historical state with the live system. Replay can explain. It cannot assign or confirm.
The handoff
Five assets. One destination. Three different facts.
The seeded shift is small on purpose. Five tagged assets need to move from Ground Loading to Level 2 Staging by 10:30. At the moment the prototype opens, three are confirmed present, Cart 14 is still at Ground Loading, and Cart 15 has stopped reporting.
Present is not elsewhere. Elsewhere is not unknown.
The watch is the operational expectation: get these five assets to this destination by this time. SiteThread collects evidence, surfaces the two exceptions, and keeps human confirmation separate from machine-observed presence. It does not invent a location when telemetry disappears, and it does not offer Confirm receipt while the group is incomplete.
3 present
Level 2 Staging
1 elsewhere
Cart 14, Ground Loading
1 unknown
Cart 15, signal stopped
Uncertainty
Missing data stays visible. A stale marker never pretends to be current presence.
SiteThread distinguishes kinds of knowledge that a single green dot would collapse. Color is paired with words. Unknown is a status, not an error style, and it is not eligible to count as arrived.
Live observation
Fresh enough to treat as current.
Delayed observation
Still usable, and labeled as behind.
Stale, last-known
The last fix remains on the plan, marked as last seen.
Unknown current location
Telemetry stopped. The product does not guess.
Historical observation
Replay shows where it was, not where it is.
Confirmed handoff
A person accepted the group. Presence alone does not.
Time, not only place
Replay explains the shift. It is not the live system.
Spatial operations are temporal. The prototype keeps movement history, an event chronology, and a timeline that can be scrubbed. Observation gaps stay visible. Returning to live is an explicit step.
The amber replay banner names the mode and disables historical task and rule creation. The point is to keep someone from acting on a state that is no longer true.
Human confirmation
The system can observe presence. A person confirms the handoff.
Those are different statements. Sensor evidence can support a decision without silently replacing accountability. Confirm receipt appears only when every member of the watch qualifies. Acknowledgement of an alert is not the same as resolving it.
In the seeded shift, confirmation stays closed. That is the correct end state for the story: three present, one delayed, one unknown.
What I was exploring
Product questions, answered in a working shift rather than a slide.
Spatial context
When does a 3D view improve understanding over a plan or a list?
Temporal context
How can history explain the current state without taking over the live experience?
Uncertainty
How should stale or missing positioning data be shown without creating false certainty?
Operational workflow
How can raw location events become a watch, a task, and a handoff?
Evidence
What should support an alert, a delay, or a handoff state?
Human control
Which states can be derived, and which require an explicit confirmation?
Role
Nicholas Pulido
Concept · Product strategy · Systems thinking · Interaction model · UX/UI · Functional prototype
A solo product exploration from 2026. Not a customer deployment, and not a measured study. Positioning, sites, people, and events in the prototype are fictional.
See the handoff unfold.
Launch the working prototype and inspect a live equipment handoff across three floors. Find the delayed cart, distinguish a stale signal from a known location, inspect recent movement, and see how SiteThread turns positioning data into an operational workflow.
Launch prototype