LBMS — Location-Based Management System
LBMS is the modern mathematical descendant of Line of Balance. Formalised by Olli Seppänen and colleagues at Helsinki University of Technology in the early 2000s, it organises construction work by location — a project is broken into zones, floors or spans, and every activity is assigned to the location where it happens. Flowline charts then show trades moving through locations over time, with learning-curve adjustments, risk analysis around production variability, and native integration into CPM programmes.
What is LBMS?
LBMS (Location-Based Management System) is a scheduling methodology that organises construction activities by the location where they happen rather than by activity logic alone. The project is decomposed into a location-breakdown structure (LBS) — zones, floors, wings, spans — and the schedule tracks each trade's flow through those locations as a continuous production system, visualised as flowlines.
Also known as: location-based scheduling, flowline method, flowline scheduling, line-of-balance scheduling (modern). The acronym LBMS is standard across the Seppänen-era literature; older terminology sometimes just says “flowline”.
Four concepts that make LBMS different from CPM
LBMS extends CPM rather than replacing it. These four additions are what make flowline planning quantitatively different from a Gantt view.
- 1
Location-breakdown structure (LBS)
The project is formally broken into locations before any scheduling starts. For a tower: tower / wing / floor / zone. For a highway: section / kilometre / lane. Every quantity-takeoff item is tagged to a location, so work content per location is explicit.
- 2
Production rates per trade per location
Each trade's production rate is calculated from crew size, work content and productivity factor at the location level. A single trade can have different production rates in different parts of the project (ground-floor podium vs typical floor), which flat Gantt rows cannot represent.
- 3
Learning curves
Crews typically speed up as they repeat identical work. LBMS applies a learning-curve coefficient (often based on Wright's learning curve or the 90% / 80% construction learning rates found in practice) so that production rates for later floors are faster than for the first floor — matching what actually happens on site.
- 4
Production-rate risk analysis
Because flowline charts expose the rate at which crews flow through locations, LBMS tools can run risk analysis on rate variability: if the structure crew is 10% slower than planned, where does the next trade get starved and by how many days? This is a dimension CPM float analysis does not naturally produce.
Worked example: location-breakdown on a mid-rise office
A 12-storey office with a podium and typical floors. Breaking the project into an LBS before scheduling makes visible the structural reason why many mid-rise projects lose time at the podium handover and never catch up.
| Level | Example locations | What it enables |
|---|---|---|
| L1 — Project | Office tower | Overall programme target |
| L2 — Phase | Substructure / Podium / Typical / Roof | Different production rates per phase |
| L3 — Floor | Floor -2, Floor -1, Floor 0, Floor 1–10, Floor 11, Roof | Trade flow visible per floor |
| L4 — Zone | North / Core / South per floor | Multi-crew allocation possible |
| L5 — Room / span (optional) | Per-office fit-out units | Takt-ready granularity for fit-out |
What the LBS reveals that a flat Gantt hides
The podium and the typical floors are different production systems. The podium has one-off structure (bigger spans, heavier reinforcement, more MEP density) which runs at ~0.5 floors per week, slower than the typical floors (1.0 floor per week once the crew is trained on the detail). CPM shows one row per activity and hides this; LBMS makes it structural — the podium is its own phase in the LBS and the production rates are calculated separately. The result: the master reflects reality from day one, and the trades flowing through the typical floors are not held up by the podium's slower cycle.
Where LBMS falls short in practice
LBMS is a mathematically strong scheduling framework but needs a reliable operational layer to deliver on site. Four failure modes come up repeatedly.
Steep setup curve
Building an accurate LBS and tagging every quantity-takeoff item to a location is weeks of work on a first project. Teams that skimp on the LBS get flowline charts that look pretty but are structurally wrong.
Learning-curve estimates are judgement calls
The 90% / 80% construction learning rates come from empirical studies but vary wildly by trade, country and crew. A pessimistic estimate hides capacity; an optimistic one promises impossible rates. Mature LBMS teams measure their own learning rates per trade and update the model as the project progresses.
No weekly commitment layer
LBMS tells you the balanced plan but not whether this week's commitments will hold. Without the Last Planner lookahead and PPC feedback on top, the chart stays optimistic as real site failures accumulate.
Software lock-in
Flowline views need specialist software such as Trimble Vico Office — teams used to Primavera P6 or Microsoft Project cannot read a flowline chart without training. The method's biggest practical cost is often the shift in planner skill, not the licence fee.
How VisiLean supports location-based scheduling
VisiLean Planner runs CPM as the master and supports Takt zones for repetitive portions — the operational cousin of LBMS. The location-based planning approach is treated as a layer on top of the master schedule, not as a replacement for it, which matches how most mature teams actually run LBMS in production.
- CPM master imported directly from Primavera P6, Microsoft Project or Asta Powerproject — the same source of truth across location-based and activity-based work.
- Takt zones layer on top of the CPM master for repetitive work, giving each trade a defined rhythm through the zones — the operational equivalent of a balanced LBMS flowline.
- The six-week lookahead screens upcoming zone handoffs for the constraints (design, materials, prerequisites, access) that typically break flow in location-based plans.
- Field progress captured through LiveSite feeds planned-vs-actual back into the schedule continuously, so the location-based plan reflects what is actually happening on site rather than what was drawn in week one.
Related methods
Line of Balance
The 1941 ancestor of LBMS. Sloped lines for trades through units — same conceptual idea, less mathematical rigour than the LBMS successor.
Read moreTakt Planning
The production-control cousin of LBMS. Fixed Takt time, sized zones and rhythmic trade wagons rather than calculated production rates.
Read moreCritical Path Method
The master-schedule method LBMS sits alongside in modern practice. CPM for the frame, LBMS for the repetitive portions.
Read moreVisiLean Planner
The product that runs CPM and Takt as views of the same schedule — supporting the balanced-flow discipline LBMS visualises.
Read moreFrequently asked questions
What is LBMS in construction?
LBMS (Location-Based Management System) is a scheduling methodology that organises construction work by location rather than by activity. The project is broken into a location-breakdown structure (LBS) — zones, floors, wings, rooms, spans — and every activity is assigned to the location where it happens. Flowline charts then show trades moving through locations over time, with production rates visible as slopes. LBMS was formalised by Olli Seppänen and the research group at Helsinki University of Technology in the early 2000s, building on Line of Balance (1941) and the Russian cyclogram methods of the 1930s.
How is LBMS different from CPM?
CPM organises work by activity logic — a network of task relationships that produces a critical path through the project. LBMS organises work by location — the same activities grouped by where they happen, visualised as trades flowing through zones. CPM is better for one-off scope with complex interdependencies; LBMS is better for repetitive work where production rates and crew flow are the primary planning concern. On modern projects they are usually complementary — CPM for the master, LBMS for the repetitive portions, both feeding the same programme.
How is LBMS different from Line of Balance?
Line of Balance is the 1941 ancestor; LBMS is the modern descendant. LOB used sloped straight lines to represent trades through units — simple to draw by hand but assumes constant production rates. LBMS extends the idea with a formal location-breakdown structure, mathematical risk analysis around production rate variability, learning-curve adjustments, and native integration into CPM-based tools. LBMS is what most lean construction practitioners mean when they talk about flowline methods today.
How is LBMS different from Takt planning?
Both are location-based and both target balanced flow across repetitive units. The difference is directionality: LBMS calculates optimal production rates from crew capacity and work content, then charts the resulting flow. Takt imposes a fixed rhythm (the Takt time) and sizes crews and work content to meet it. LBMS asks “what production rate can we achieve?”; Takt asks “what production rate must we hit, and how do we structure the work to hit it?”. Many mature programmes use both — LBMS as the diagnostic view, Takt as the operational discipline.
Which markets have adopted LBMS most strongly?
The Nordics — Finland, Sweden, Norway — are the strongest LBMS adopters, driven partly by the methodology's academic origins in Helsinki and partly by the region's lean construction maturity. Germany, Austria and Switzerland use LBMS alongside Taktplanung on larger projects. The UK and US have slower adoption, with LBMS more common on infrastructure (highways, rail) than on building work, where CPM remains dominant. Vico Office (now part of Trimble) is the platform most associated with practical LBMS implementation outside academic research.
See location-based planning on a live schedule
VisiLean runs CPM and Takt as views of the same schedule, with field updates from LiveSite feeding the location-based plan continuously.