The spatial and temporal model
How on-map entities, areas, and time fit together.
SimOps is, at heart, a map of a construction site over time. Everything on it is an entity with a footprint and a lifetime.
Entities on the map
The map's first-class citizens are the Primitive entity kinds — the point, circle and polygon primitives that everything else is built from. Pointlike entities that open a properties panel rather than a footprint editor are Auxiliary pins. When you select several entities at once you get a Multi-selection, and acting on a mixed set surfaces the Bulk-action strip; if your click lands on a stack of overlapping entities the Disambiguation picker lets you choose which one you meant.
Placing one is the shortest way to see what a footprint and a lifetime mean together: a person becomes a circle that only exists for the hours they are booked, and a crane brings its own red drop zone with it.
Not every scheduled team has a place on the map. A Roving crew is a team you add from
the Add menu with S, without placing it anywhere. It still carries a contractor, a time
window, a crew type and a permit, just as a worker does, and it is counted and listed like a
worker too — in the entity browser's Roving crews section and the toolbar count badge. It
never appears on the canvas, though, and it never enters clash detection.
Buildings add a vertical axis. Floor focus narrows the map to one level and dims the rest, with an Off-floor hint for entities that live elsewhere. Every building also has a Roof above its floors, a level of its own that is open to the sky; how workers, plant and areas stand on a roof or a floor is explained in Roofs and levels.
Areas and reference geometry
Polygonal regions are ActiveAreas. Geometry that is always-on and plan-agnostic (roads, buildings, zones) is a Reference feature — and buildings and zones double as containers you can fill. Both are traced on the ground the same way; what differs is that the area carries a window and the road does not.
Fill covers a whole container without drawing: the container's own outline is snapshotted into new areas for you. A building slices into its levels, so a Floor-fill (the "Floor-fill area…" button on the building panel) makes one Whole-floor area per level you tick, the roof among them; a zone has no floors, so "Fill zone…" is the single-slice case and makes one Whole-zone area. Fill has no keyboard chord: its doors are those two buttons on the focused container's panel. One container per fill — three zones is three fills. What you get are ordinary areas on the map, clashing and rendering like anything you drew by hand; that they were filled shows only on the container's panel.
Every fill mints a Fill group, down to a group of one, and the panel lists each group under Fill with Clear (delete the whole group — every floor, every recurrence — in one go) and Regenerate. Filled polygons are frozen at fill time and never drift with the container behind your back; when the footprint or zone outline moves, a "Geometry changed since fill" chip appears and Regenerate re-snapshots the group.
Permits reach the same machinery without touching the map: when a permit's location hint resolves to a container, its detail card offers Fill {location}…, opening the fill modal pre-seeded from the permit — the container, the floor if the hint named one, occurrences from the permit's dates, and permit linkage on every area created. No resolved location, no offer: there you still draw.
Which place a token is in
Buildings and zones are also the Named places that work is counted under. The planner's reality layer, the lost-time ledger's By place view and a Work line's place all ask the same question — which place does my crew count under? — and there is one answer, the Token place. A token is in exactly one place: a building (on a floor) or a zone. Zones are meant for ground outside buildings, so where a zone has been drawn inside a building anyway, the building wins.
The answer is looked for in this order:
- What the token records. A token that records its building (with its floor) is in that building. Failing that, a token that records its zone is in that zone; a building beats a zone when it records both. A recorded building or zone that is not a place on this site is ignored, not trusted.
- Where it was drawn. A token that records no place is in the building its footprint falls in — carrying the token's own floor — and only where no building holds it does a zone answer. A point on a place's outline counts as inside, but an area laid flush against a place (sharing an edge, no ground) only touches it and is not in it. A building or zone that has a single floor holds only tokens on that floor, and a token with no floor is on the ground floor.
Where a token was drawn never overrides what it records. Each surface then adds its own policy: the Planner reads only what tokens record, a Work line needs exactly one place, and lost time keeps every place a record's work reaches.
Time
Every entity carries an Active period. Work is organised into Shifts, and a recurring booking expands into a Schedule group of individual Occurrences. The timeline Scrubber-anchored surface decides what is visible at the moment you have scrubbed to — which is not always the same window the clash engine evaluates, a subtlety the decision record covers in detail. Winding the clock is the gesture that makes the point: the whole site moves with it.