Esc

↑↓ move↵ openIndex · Pagefind
Scheduling / Location-based planning: Line of Balance and takt plans

Location-based planning: Line of Balance and takt plans

Read the plan as a flowline of trades moving through floors, units and zones, with conflicts, buffers and crossings marked, then generate a takt train with the engine's takt module, review it, apply it to the draft and track zone-by-zone adherence.

On this page

A Gantt chart shows activities against time. On repetitive work, such as floors of a tower, units of a housing scheme or bays of a warehouse, the question is different: where is each trade, and when do two trades end up in the same place? The Planner answers it with a Line of Balance display mode and a takt plan generator. Both read the same location breakdown, and neither changes a date by itself.

The location breakdown

A flowline needs two things for each activity: its location and its trade. In the Planner, choose the Line of Balance display mode, then set where each comes from.

Locations from

Source How an activity is placed
Activity location field The activity’s location text. A path written with > (for example Level 2 > Unit 4) becomes a hierarchy.
Project locations The project’s Locations, matched by location ID, else by the full path or a unique location name (case doesn’t matter). Names that match several locations are counted and reported; use the full path. Up to 5,000 locations are read.
Activity code: name An activity code type you flag as the Location code. Its hierarchical values are the hierarchy, in their code sequence.

If you haven’t chosen, the Planner suggests one: a code type named like Location, Floor, Level, Zone, Area or Unit, else project locations when activities carry a location ID, else the location field.

Trades from is the activity’s trade field, an activity code (such as Trade or Responsibility), or the activity name without its location: Drywall — Level 2 becomes Drywall.

Siblings are ordered by code sequence, else naturally (Level 2 before Level 10). That order is the direction the work flows. Your choice of sources is stored in the plan as one undoable edit, so the next scheduler sees the same breakdown. The engine ignores it.

Use Level to roll deep locations up, for example rooms to floors. As assigned draws each activity where it was placed.

Reading the flowline

Locations run up the vertical axis, first location at the bottom (tick First location at top to reverse it). Time runs across, on the layout’s timescale. Each trade is one coloured line. In each location, its segment runs from the earliest start to the latest finish of that trade’s activities there, using actual start once work has started. Dotted joins show the crew waiting between locations.

The legend lists each trade in handover order, with the number of locations, its rate in locations per week and its waiting days. Three kinds of finding are marked, and each can be switched off:

  • Conflicts: two trades in the same location at the same time. Shaded red, with the overlap in days.
  • Buffers: the gap between one trade leaving a location and the next one entering. Set Minimum buffer (days); gaps shorter than it are labelled tight.
  • Crossings: two trades swap order between neighbouring locations, so their lines cross. Marked ×.

Conflicts and crossings lists the findings. Click one, or click a line segment (or press Enter on it), to select that activity in the grid and Gantt. Zoom with +, − or Ctrl+wheel, and drag to pan. Export flowline SVG saves the chart, and Print flowline opens the browser print dialog.

A footnote counts what was left off: activities with no location, placed activities with no trade, and activities with no calculated dates. WBS summaries and level-of-effort activities are never drawn. Findings stop at 1,000 of each kind, with a note when they’re truncated, and the list shows the first 200.

Generate a takt plan

Takt planning gives every trade the same fixed time in each zone, the takt time, so the trades move through the building like the carriages of a train. Choose Takt plan above the flowline.

  1. Name the plan and set the takt. Give a takt time in working days (1 to 60) and a start date.
  2. Choose the zones. Pick locations from the breakdown at the chosen level, or type them one per line, in flow order. Up to 200 zones.
  3. Build the trade sequence. Add trades in handover order, each with its work in crew-days per zone (0 to 10,000) and a crew ceiling (1 to 50). You can override the work for one zone. Up to 60 trades, and at most 6,000 zone × trade slots.
  4. Choose the links. The zone chain (one trade moving on) and the trade handover (the next trade entering a zone) are each FS 0, or SS + takt, which keeps the rhythm when one slot runs long. Optionally put the activities under a WBS node.
  5. Preview. The engine’s takt module plans the train on the project’s default calendar. The preview lists each trade’s crews, utilisation and whether it’s overloaded, plus the idle crew-days, the finish and the minimum feasible takt with the trade that sets it.
  6. Apply to draft. Apply the reviewed preview, then save and calculate as usual.

Applying adds one activity per slot, named Trade — Zone, with IDs such as TK1-DRYWALL-01. Each lasts one takt, carries a start on or after constraint at its takt, is placed in its location with your breakdown’s source (typed zones go into the location field), and has a note with its crews and crew-days. The relationships follow your link choices. All of it is one undo step, so Undo removes the whole plan. The plan itself is kept so its adherence can be measured.

If a trade can’t fit into the takt within its crew ceiling, the preview warns that the plan isn’t buildable and marks the trade Overloaded. Apply is still allowed, so read the warning first: lengthen the takt, raise the ceiling or split zones.

Takt adherence

Each generated plan shows a zone-by-zone table: planned completion (the plan’s last takt in the zone), actual completion (the latest actual finish, once every trade in the zone has finished), the calculated forecast, the variance in calendar days and the zone’s state. A summary counts complete zones and zones finished on takt, and warns when generated activities have since been deleted.

Who can use it

The Planner, the flowline and takt planning need Schedule admin, because they show the full network. The same flowline and the adherence of every takt plan are available read-only over the Schedule API.

Limits

  • The takt calendar is the plan’s default calendar at day level: working weekdays and non-working exceptions. Part-day shifts aren’t used.
  • The takt module puts every trade in exactly one zone for exactly one takt. It doesn’t model trades that need two takts in a zone, or work content that varies by crew size.
  • Takt previews are proposals. Nothing is stored until you apply the preview and save.
  • The flowline groups activities by the trade text exactly as written. Drywall and Dry wall are two lines.
  • Adherence uses calendar days and needs actual finishes. A zone with progress but no actual finishes shows its forecast.
  • Mistake: Reading a conflict as an error in the schedule

    In the app: A conflict is two trades in one location at once. Sometimes that is planned. Check the activities before changing logic.

  • Mistake: Expecting the flowline to show unsaved edits

    In the app: Save and calculate. The flowline draws the last calculation only.

  • Mistake: Applying a takt plan that the preview marks as overloaded

    In the app: The overloaded trade can’t finish a zone in one takt, so the train won’t hold. Change the takt, crews or zones until the preview is buildable.

  • Mistake: Naming trades inconsistently across floors

    In the app: Use a trade field or activity code. Inferring trades from names only works when names are consistent.

Keep exploring

Related across os.construction

Run it on your own project.

Start a 14-day free trial. Want a say in what ships next? Join the founding program.

Your role (optional)

14-day free trial. Pricing for paid plans isn't set yet. Talk to us. Already have an account? Sign in →

Ask the OS

Reading this page

Ask anything about this page. Answers use what you're reading as context.

Suggested

    AI · may be imperfect · sample data where shown

    Open file