← Features

Planner & region evolution

The read-only reality layer of the Work home's Plan Gantt — who is working where, on which day, read straight off the live site — plus the changepoint stepper that walks one piece of ground forward through time. The contractors' programmes sit beside it as the plan layer; SimOps never plans for you.

Planning stays in P6 or Powerproject. Each contractor's programme comes into SimOps as a file (Imports), and every activity in it becomes a Work line on the Work home's Plan Gantt — the plan layer. What a planner also needs is a legible picture of what is actually happening on the ground to hold that plan against. That is the Planner, the Gantt's reality layer: a read-only view of reality, organised the way a lookahead is organised — contractor × place × day — so the two can be read side by side, or overlaid. Reality meets the plan only through a token placed on a line; the Planner itself never asserts that anything is late. It supplies the numbers; the judgement stays with the person who owns the plan.

What it does for you

  • A lookahead shaped like your lookahead. The spine is a day-column matrix, grouped contractor-first and pivotable to place-first, so it reads against a P6 Gantt without translation. The horizon is 2, 4 or 6 weeks forward with a fixed five-day backward tail — the tail is what makes overstay visible ("still in the Turbine Hall three days after they should have moved").
  • The atom is an issued permit. An activity is an issued Permit read as a unit of scheduled work: it is the one object that carries a structured who (Contractor), what (permit categories), when (Permit window) and where. The placed workers, plant and areas linked to it are its manifestation — they supply the hard location and the human labels the permit's own free-text location lacks.
  • A Work line is the second kind of evidence. A token attached to a Work line counts under its own contractor even with no issued permit behind it. Where a token has both, the permit wins. Drilling into a cell lists the Work lines that credited it beside its permits.
  • Place, not just polygon. The location axis is the Named place — a building or a zone, treated as one axis because a planner reasons about both as named locations. Floor is a first-class drill-down, so "in the Electrical Building" and "on Level 2" are both askable.
  • Spatial contention, which P6 cannot see. A schedule encodes activity logic; it does not know that four trades are booked into the same room on Thursday. Congestion — distinct contractors per place per day — tints the place choropleth on the map, so over-subscribed ground reads at a glance.
  • Nothing hides. Work with neither a permit nor a Work line behind it is not silently dropped: unpermitted tokens surface in their own bucket, and permits whose location could not be matched to a place surface in the spine as unresolved rather than vanishing. A Roving crew is placeless by design rather than unmatched, so it reads under a band of its own, Roving — never as unresolved, which would ask you to go and fix data that is already right.

Where a token counts

Which building or zone a placed worker, machine or area is in is its Token place — the rule is stated once, in The spatial and temporal model. The reality layer and a Work line each put their own policy on top of it.

The reality layer reads what a token records, never where it was drawn. It looks at a token's recorded building, floor and zone only — not its footprint — and buildings and zones are separate grains:

  • At the building and floor grains a token counts under the building it records. A token that records a building and a zone is in the building.
  • At the zone grain a token counts under the zone it records. A token that records a building is not counted under a zone, even when it also records one.
  • A token with nothing on the current grain's axis — it records no place there, or the building or zone it records is not a place on the site — counts under its issued permit's matched location. If that permit's location matched nothing, it counts as unresolved. With no issued permit behind it (an unpermitted token, or one credited only by a Work line), it counts as outdoor.

A Work line takes its place from its first placed token. A line has no place until a token sets one, and until then it sits under No place yet in the Plan Gantt's Area order. Attaching tokens to a line with no place — directly, through a schedule group that carries the line, or by making a line from a token — gives it the place of the first token that is in exactly one place. A line that has a place keeps it; only a hand edit moves it. Unlike the reality layer, the line uses the whole rule, footprint included:

  • A token that records its building (else its zone) fills that place. A worker pinned to a zone fills the zone.
  • A token that records no place fills the building its footprint is in, on the token's floor — even where a zone is drawn inside that building — and only otherwise a zone.
  • Either way, if the building has no floor of that number, the line takes the whole building.
  • An area that records no place and reaches into two buildings — or, outside every building, two zones — is in no single place, so it fills nothing. An area laid flush against a place, sharing an edge but no ground, is not in that place.
  • A token outside every building and zone, and a Roving crew, leave the line under No place yet.

What it deliberately does not do

The Planner does not plan. It has no create, no edit and no save; there is nothing on it to submit. The in-app planning cycle — draft cycles, contractor submissions, the baseline/planned/actual fork and the planned-versus-actual compare — was removed in full (see planning-removal), and this surface is what remained standing: a live read, not a fork of the data. The plan it is read against is the contractors' own uploaded files, never one SimOps authors — a line's slip is drawn on the plan layer, from the file's dates, not computed by the reality read (every-activity-is-a-work-line). Nor does it answer history — was this firm working in that place on those dates? is the permit history lookup's question (Commercial ▸ Permit history, a bounded date-range read over the whole register), and Reality stays the now-anchored lookahead. SimOps is the reality-record; the gap between that record and the plan is the planner's to read, deliberately (see planner-analysis-reality-not-plan).

Two honest limits worth knowing before you cite a number. The view reads live, mutable rows — it is a proxy for reality, only as current as the site team keeps it, never verified actuals. And the counts are markers, not people: a worker count is "worker pins placed here", which is not the same thing as a headcount.

Region evolution — one piece of ground, forward through time

The spine reads the whole site by contractor and place. Its companion reads the opposite way: pick a piece of ground — right-click a building, a zone or a placed entity on the map and choose Scheduled changes here — and ask what is scheduled to change there. The answer is a stream of changepoints: the moments the population of that ground actually changes, each naming what entered, what exited, and how much is in scope afterwards.

The Stepper walks them one at a time, and it moves the site clock as it goes — there is one cursor, not two, so stepping scrubs the map and scrubbing the map re-highlights the row. The map door lands it as a transient, tab-less Changes here view of the Work rail; ✕ or Escape puts you back exactly where you were. (The stepper's old Work-home tab and its constructor grid retired in the fold — every door pre-anchors its region, so there is nothing left to construct by hand.)

Where to find it

Both live in the Work home (W), the domain home for scheduled work in place and time. It has no tabs: its body is one Plan Gantt, with a layer toggle — Plan · Reality · Both — drawn for a reader who may see reality:

  • Reality (the Reality layer) — the Planner spine and the map choropleth. Q opens the Work home straight onto it for that one opening — it never changes the layer the home remembers, so the next W opens on the layer you last picked on the toolbar — and a second Q closes it.
  • Both — the programmes' lines with reality on them: a tokened line's run as a strip under its row (a ghost behind its bar in the Gantt presentation), and anyone on site but not on a line shown in a foot group and on each programme header's presence strip. A run spans the days anything on the line stood, but its headcount counts crew only — so a line whose only tokens are a laydown or an exclusion zone draws a thinner, dashed run marked Activity on site — no crew. A loose laydown or exclusion is nobody on site and stays out of the foot group.
  • Changes here — the changepoint stepper, landed by the map's right-click Scheduled changes here door, transient; ✕ or Escape restores the Gantt.

The reality layer answers to planner_view (coordinator, admin, and the site-manager deputy), so the Q chord stays inert — and the layer toggle is not drawn — for a membership that can open the Work home but not see reality. The map door sits on the wider entity_view band — it is a new lens on scheduled work the membership can already see, not new data.

See it / try it

Was this page useful? Report a problem

No cookies and no third-party analytics. A verdict records this page's path — and a search that finds nothing records the words you typed — in this site's own server log.

Generated from source · SimOops living system reference