Location-Based Management System (LBMS)

Location-Based Management System (LBMS)

1. What Is Location-Based Management System (LBMS)?

The Location-Based Management System (LBMS) is a construction planning and production-control framework that organizes work around physical locations and the movement of crews through them. “Location-based” identifies where work happens; “management system” means that planning, measurement, forecasting, and corrective action operate together. Its central question is: can each crew complete its work and move to the next location without interruption or interference?

For general contractors, this provides a practical way to evaluate trade sequencing, crew deployment, and handoffs across floors, wings, apartments, or infrastructure sections. Executives should use it to test whether a delivery plan is operationally credible—not simply whether its milestone dates look acceptable.

2. Origin and Background

The modern integrated LBMS was developed by Russell Kenley and Olli Seppänen and codified in their 2010 book, Location-Based Management for Construction: Planning, Scheduling and Control. Their published research on flowline planning and control predates the book, including a 2005 paper. LBMS builds on earlier line-of-balance and flowline approaches while incorporating critical-path scheduling logic. It did not originate the broader idea of location-based scheduling.

The objective was to connect construction schedules with how production actually proceeds: crews working through physical areas with different quantities, dependencies, and resource requirements. Its original construction context remains directly relevant; the important distinction is between drawing a location-based schedule and actively managing production through it.

3. How Location-Based Management System (LBMS) Works

LBMS connects three questions: what must be built in each location, how quickly available crews can build it, and when that location becomes available to subsequent trades. Locations need not contain identical work, and some tasks may occur in only one location.

The core elements

  • Location Breakdown Structure (LBS): A hierarchy of physical areas—for example, project, building, floor, and zone. Different tasks can be managed at appropriate hierarchy levels while retaining consistent location references.
  • Location-based quantities: Work quantities are assigned to locations, rather than remaining only in project-wide totals. Relevant measures might include wall area, duct length, or concrete volume.
  • Tasks and crews: A task collects related work performed across locations. Quantities, labor requirements, crew composition, and working calendars determine realistic local durations.
  • Dependencies and buffers: Technical sequencing, crew movement, and location-specific relationships are modeled. Planned time separation between trades protects flow against variability.
  • Production control: Actual quantities, resources, and progress update forecasts, allowing intervention before a local shortfall disrupts downstream work.

These elements connect the physical scope with production planning and control; the location hierarchy is more than a labeling convention.

The principal visual artifact is a flowline chart, typically displaying time horizontally and ordered locations vertically. Task lines show progression through locations. Their slopes indicate location-completion rates—not labor productivity by themselves. Where quantities differ, the underlying quantity and resource data remain essential.

Converging lines can reveal a faster successor approaching a slower predecessor. The response may be to improve the predecessor’s method, adjust resources, change location sequencing, or delay successor mobilization to preserve continuous work. LBMS therefore challenges the assumption that starting every trade as early as possible produces the best production plan.

4. When to Use Location-Based Management System (LBMS)

LBMS is especially useful when multiple crews progress through identifiable work areas and their production rates must be coordinated. Suitable applications include multistory interiors, residential developments, phased commercial fit-outs, and linear civil works. Exact repetition is helpful but not necessary; location-specific quantities accommodate differences between areas.

Useful executive questions include:

  • Will accelerated ceiling installation catch unfinished overhead services?
  • Should a subcontractor mobilize later rather than repeatedly stop and restart?
  • Which location or trade threatens the next handover milestone?
  • Does a recovery proposal improve overall flow or merely relocate congestion?

The minimum useful inputs are location-based scope, quantities, production assumptions, resources, dependencies, and actual progress. Planning should involve the superintendent, scheduler, estimators, and trade representatives—not remain a desktop exercise.

Use a limited pilot before extending the system. Setup effort depends on quantity availability and subcontractor participation; ongoing control requires a recurring field-data routine. Do not make LBMS the dominant tool for an isolated equipment installation or an investment appraisal. It can also mislead when unresolved design or access conditions make apparently available locations unworkable.

5. How to Apply Location-Based Management System (LBMS): Step-by-Step

The following sequence is a practical implementation guide. Agree on the production decision before choosing software or designing dashboards.

  1. Clarify the decision and scope. Define the milestone being protected, the construction phase, and the delivery horizon. Distinguish structural completion, interior completion, system commissioning, and owner handover.

  2. Define workable locations. Agree on a location hierarchy using drawings and trade input. Choose boundaries where work can genuinely be completed and released. Check access, staging space, and differences between structural and finishing work.

  3. Gather quantities and production inputs. Allocate scope to locations. Obtain crew composition, working calendars, achievable output, deliveries, and prerequisite information. Separate measured inputs from estimates, and record who owns each assumption.

  4. Construct the production model. Create tasks across applicable locations, calculate local durations, and establish technical and crew-flow relationships. Build the flowline view and connect it to project milestones and non-location-driven activities.

  5. Balance flow collaboratively. Review interruptions, converging trades, resource peaks, and oversized locations. Test changes to methods, sequencing, crew numbers, and mobilization dates. Do not assume additional labor produces proportional output.

  6. Establish measurement and forecasting. Record installed quantities, crew resources, actual dates, and release status by location. Use observed performance to forecast remaining work. Keep the approved baseline separate from the current forecast.

  7. Translate warnings into decisions. Assign an owner and deadline to each corrective action. Evaluate downstream consequences before resequencing work. Preserve design acceptance, inspection, quality, and safety gates when assessing acceleration.

  8. Test sensitivities and iterate. Challenge optimistic output assumptions, late deliveries, and unavailable areas. Review forecasts with trade supervisors, reconcile disagreements, and update assumptions without erasing the history of deviations.

For a contractor introducing these routines, project controls improvement is a natural follow-on engagement: consistent location coding, trustworthy progress measurement, forecast rules, and an actionable exception report.

Collaborative location definition and quantity-based planning are established features of LBMS implementation; forecasting research also emphasizes incorporating resource availability rather than merely extrapolating dates.

6. Example: Location-Based Management System (LBMS) in Action

Fictional scenario: Harbor Court Development is delivering an eight-floor apartment building. Its contractor’s schedule shows interiors finishing on time, but the superintendent sees crews moving between unfinished areas. The developer asks whether the planned handover remains credible.

The team divides each residential floor into two independently releasable zones, creating 16 locations. It allocates quantities for overhead services, ceiling installation, and finishes, then validates production assumptions with subcontractors.

Illustratively, the services sequence—including its release checks—takes four working days per zone, while ceiling installation takes three. If ceiling installation begins two working days after the first zone is released, that separation disappears by the third zone. The ceiling crew must wait at the fourth unless the plan changes. A project-wide percentage-complete report had obscured this developing interruption.

The team delays ceiling mobilization to create a workable continuous sequence, then recalculates the completion forecast. It evaluates services improvements before adding labor, models the amenity area separately, and agrees daily release checks. It does not claim that later mobilization automatically accelerates handover.

For multifamily rental developers, the recommended management output is a forecast of completed, accepted areas tied to handover requirements—not a count of zones with some work underway. Harbor Court keeps commissioning and occupancy prerequisites explicit.

7. Strengths and Limitations

Strengths

  • Physical clarity: Locations make sequencing and handoffs easier to discuss with field teams.
  • Resource continuity: The model exposes repeated mobilization, waiting, and production-rate mismatches.
  • Earlier intervention: Quantity-based forecasts can identify downstream disruption before milestone slippage becomes visible.

These strengths follow from combining location-based production planning with active forecasting and control.

Limitations

Forecast quality depends on credible quantities, productivity assumptions, and resource information. Historical performance does not guarantee that future locations will remain accessible or equally difficult. Research also shows that production problems can cascade even where the overall finish date is protected by substantial end-of-project buffers.

Do not treat spatial progress as proof of building readiness. Shared systems, testing, defects, and owner acceptance require explicit integration. Nor should a clean flowline override technical sequencing or become a substitute for contractual records.

8. Common Pitfalls and How to Avoid Them

  • Choosing convenient rather than workable zones: Administrative boundaries may not support complete handoffs. Validate boundaries with the trades that must use them.
  • Assuming equal work per floor: Similar-looking areas can contain different quantities. Measure scope locally and explain unusually difficult locations.
  • Reporting subjective percentages: “Nearly complete” does not establish downstream readiness. Track measurable quantities and agreed release conditions separately.
  • Adding labor mechanically: Extra crews may compete for access or equipment. Test the proposed method and working space before assuming faster output.
  • Redrawing instead of controlling: Updating dates without resolving causes perpetuates disruption. Maintain corrective-action owners, deadlines, and forecast comparisons.

Large locations can conceal separation between trades, while very small locations can create staging and coordination difficulties. Treat location sizing as a production-design decision.

When unresolved actions span several contractors, program management support can help establish meeting cadence, decision logs, and follow-through without transferring production accountability away from the site team.

9. How Location-Based Management System (LBMS) Relates to Other Frameworks

Critical Path Method

The Critical Path Method (CPM) emphasizes activity dependencies and project completion timing. LBMS incorporates CPM logic while adding location relationships and crew-flow considerations. Use an integrated view: location-based control for field production and dependency analysis for the broader delivery network.

Last Planner System

The Last Planner System provides collaborative planning, constraint removal, and reliable commitments. LBMS supplies quantity-based production rates and forecasts. Combine them: establish flow, make upcoming work ready, secure commitments, and compare execution with the production forecast.

Takt Planning

Takt planning organizes work around a common production rhythm across zones. LBMS can represent different task rates and unequal quantities while seeking continuity. Prefer takt when a regular rhythm is practical; consider LBMS when variable work content requires more flexible production modeling. They can be combined rather than treated as competing doctrines.

Line of Balance

Line of Balance is an important predecessor, but the terms are not interchangeable. Its cumulative production emphasis differs from LBMS’s detailed treatment of individual physical locations and their associated data.

10. Key Takeaways

  • LBMS manages production through physical locations, not merely scheduled activities.
  • Use quantities and feasible crew output to test continuity.
  • Different locations need not contain identical work.
  • Convert forecast warnings into owned corrective actions.
  • Keep commissioning, acceptance, and broader project dependencies explicit.

11. FAQs About Location-Based Management System (LBMS)

Is LBMS only suitable for repetitive buildings?

No. Repetition helps, but LBMS accommodates different quantities and tasks across locations. The essential requirement is a useful physical breakdown of the work.

Does LBMS require building information modeling?

No. Quantity inputs can come from conventional takeoffs or building information modeling (BIM). The important requirement is reliable assignment of quantities to locations, not a particular technology.

What should executives monitor?

Request remaining quantities, actual versus planned output, crew availability, location-release status, and forecast milestone exposure. Ask which corrective actions have changed the forecast—not just how many activities were completed.

How long does implementation take?

There is no universal duration. Assess quantity readiness, location complexity, trade participation, and reporting discipline. Begin with one phase; expand only when the team can maintain reliable inputs and act on the resulting forecasts.

How to get started

1

arrow-down-blue

Tell us about your project

2

arrow-down-blue

Interview candidates

(We’ll provide bios within 48 hours on average)

3

Select your consultant and start work

Find a Consultant

or email us at: [email protected]