Capstone: a BIM execution plan and digital toolkit

This capstone brings the course together in one realistic planning exercise. You are the project manager for a general contractor that has just been awarded a construction management contract for an invented project, Riverbend Commons. Your task is to prepare the key parts of a BIM execution plan and a digital toolkit for the project: goals and BIM uses, the model element table, the CDE and naming rules, the coordination process, field and reality-capture workflows, data and dashboards, handover information, contract and security provisions, and a budget with an expected return. The worked examples show how each part might be developed; your own plan for an assignment should be adapted to the project you choose.

The project

Riverbend Commons is an eight-storey mixed-use building in a mid-sized Canadian city: a cast-in-place concrete podium with ground-floor retail and two levels of underground parking, and six storeys of rental apartments above, framed in concrete with a flat-plate structure. Gross floor area is about 14,800 m², with 132 apartments. The owner is a non-profit housing developer that will own and operate the building for at least 40 years. The construction budget is $68 million and the schedule is 26 months. The site is tight, bounded by a street, a lane and an occupied neighbouring building, with no laydown space beyond the footprint.

The owner's request for proposals asks for "BIM coordination, a record model and asset data for our maintenance system" but gives no further detail. The architect and engineers model in a common authoring platform; the mechanical, electrical, plumbing and fire protection trades will be engaged during design development as part of the construction management arrangement.

Step 1: goals and BIM uses

Start from the project's risks and the owner's long-term needs, not from software. For Riverbend Commons the main risks are a tight site with an occupied neighbour, dense MEP in the parking levels and corridor ceilings, repetitive residential floors where errors multiply, and an owner who needs reliable data to run the building for decades.

Some uses are deliberately left out. Energy and carbon analysis is the design team's responsibility and already in their scope. Generative design adds little on a conventional residential plan. A full digital twin connected to building automation is beyond the owner's current capability; the record model and asset data will make one possible later.

Step 2: clarify the owner's requirements

The owner's single sentence must be turned into checkable requirements (Lesson 4). A meeting with the owner's property manager establishes that its maintenance system needs a list of maintainable equipment with location, type, manufacturer, model, serial number, installation date, warranty end date and planned maintenance tasks, and that its leasing team needs accurate unit areas and room lists. The owner does not need a fabrication-level model for operations.

Step 3: model element table

The model element table sets the LOD (or information requirement) and author for each element at each milestone. An excerpt for Riverbend Commons is shown below; the full table would cover every UniFormat group.

Small conduit, branch wiring and in-wall plumbing in the suites are not modelled; they are installed from typical details and documented by 360-degree capture before drywall. This keeps modelling effort where coordination risk is highest.

Step 4: CDE, naming and exchange

The project will use one CDE for models, drawings and documents, with work-in-progress, shared, published and archived states, and status codes for coordination, information, construction and record use. File names follow the convention project-originator-zone-level-type-role-number (for example RBC-MECH-P1-L02-M3-M-0001). All models share the project base point and survey point established by the land surveyor and tied to site control (CON-250). Native files are exchanged weekly during coordination; IFC 4 Reference View files are produced at each milestone and for the record model, with the owner's required property sets checked against an IDS file.

A test exchange at kickoff checks alignment, units, IFC classes and property sets for every model before coordination starts (Lesson 3).

Step 5: coordination plan

Coordination runs weekly by zone: the two parking levels, the podium retail level, the transfer level and a typical residential floor (coordinated once, then checked for variations on each floor). Trades upload models on Monday; the BIM coordinator runs clash tests on Tuesday using the clash matrix and tolerances in the plan; issues are grouped and issued as BCF on Wednesday; the coordination meeting is on Thursday; and trades update by the following Monday. A zone is signed off when no issues beyond tolerance remain, clearance zones are clear, sleeves and openings are confirmed with structure, and hangers are modelled.

Step 6: field, reality capture and progress

The field platform holds the current drawings, RFIs, submittals, daily logs, inspections, safety forms, punch lists and asset-tag capture. RFIs and submittals are tracked against contract response times and the submittal register is back-scheduled from need dates (Lesson 7). Reality capture combines a weekly 360-degree walk of every active floor, terrestrial scans of slabs and sleeves before each pour, a scan of above-ceiling MEP in corridors before ceilings close, and drone flights every two weeks during excavation and structure for progress and stockpiles.

Step 7: data and dashboards

The project dashboard serves three audiences (Lesson 9). The superintendent's weekly view shows look-ahead constraints, inspections due, first-time pass rate and safety observations. The project manager's monthly view shows SPI and CPI from the cost-loaded schedule, RFI and submittal turnaround, open coordination issues by trade, change events pending and percent plan complete. The owner's monthly report shows progress against milestones, cost to date and forecast, and handover readiness, including the percentage of asset records complete.

# Riverbend Commons: monthly KPI check against thresholds (illustrative data)
kpis = {
    # name: (value, threshold, higher_is_better)
    "SPI":                       (0.97, 0.95, True),
    "CPI":                       (1.01, 0.98, True),
    "RFI avg turnaround (days)": (8.4,  7.0,  False),
    "Submittals on time (%)":    (88,   90,   True),
    "First-time pass rate (%)":  (84,   85,   True),
    "Percent plan complete (%)": (78,   75,   True),
    "Asset records complete (%)": (41,  40,   True),
}
for name, (value, limit, higher) in kpis.items():
    ok = value >= limit if higher else value <= limit
    flag = "ok" if ok else "ATTENTION"
    print(f"{name:28s} {value:>6}  threshold {limit:>5}  {flag}")

SPI                            0.97  threshold  0.95  ok
CPI                            1.01  threshold  0.98  ok
RFI avg turnaround (days)       8.4  threshold   7.0  ATTENTION
Submittals on time (%)           88  threshold    90  ATTENTION
First-time pass rate (%)         84  threshold    85  ATTENTION
Percent plan complete (%)        78  threshold    75  ok
Asset records complete (%)       41  threshold    40  ok

The check flags three measures for discussion: RFI turnaround, submittals and first-time pass rate. Each would be explained by the responsible person at the monthly review, with actions and dates. The point of a simple threshold check is focus: most measures are fine, and attention goes to the few that are not.

Step 8: contract and security provisions

Because the contract is construction management, the CM can write BIM requirements into each trade contract: modelling to LOD 350 and 400 where listed, participation in coordination, use of the CDE and field platform, asset data capture and record model updates. The owner–CM contract should attach the BIM execution plan, state that drawings govern unless model versions are designated, grant the owner a licence to use models and data for operation, maintenance and future alterations, and require export of all records at completion. Security provisions include multi-factor authentication on all platforms, removal of access when people leave, tested backups, verification of any change in payment details and a privacy notice for workers covering site cameras and 360-degree capture.

Step 9: budget and expected return

Finally, the toolkit needs a budget and a realistic case for it. The table lists the main costs over the 26-month project; licence costs are illustrative and depend on the firm's existing enterprise agreements.

Step 10: risks to the plan

A good plan also names what could make it fail and how to respond.

Presenting the plan

For the assignment, assemble the steps into a concise BIM execution plan of 15 to 25 pages with appendices: the model element table, clash matrix, naming convention, dashboard definitions and budget. A good plan is specific (names, dates, numbers), proportionate (effort where risk is highest), checkable (every requirement can be verified) and owned (every task has a person). It should read as a working document that a coordinator, superintendent and trade foreman could each pick up and use, not as a sales brochure.

This course began by asking how digital tools can keep information structured, trusted and connected. Riverbend Commons shows that the answer is less about any particular technology than about disciplined planning: knowing what information is needed, who produces it, how it is checked, where it lives and how it is protected. Those habits will outlast every product named in today's market.