Featured image for The Existing-Conditions Clause Your BEP Is Missing - Best Practices article
    Best Practices

    The Existing-Conditions Clause Your BEP Is Missing

    Maxwell Seay8 min read

    TL;DR

    TL;DR: Add an existing-conditions clause to your BIM execution plan that fixes capture method, measured and represented LOA with a confidence level, LOD per discipline, coordinate system and survey control, formats, deliverable dates, acceptance testing and data ownership. Under ISO 19650 it answers the level of information need, acceptance criteria and delivery dates in the EIR. Our published figures (±5mm registered accuracy, ±10mm at LOD 300, ±6mm at LOD 400) show the level of detail to ask any provider for.

    The clause most BIM execution plans are missing is one that governs the existing building itself: how it will be captured, how accurate the point cloud and the model must be, what gets modeled for each discipline, which coordinate system and control it ties to, what formats arrive and when, how the data is tested before anyone accepts it, and who owns it afterward. Many plans spend pages on authoring software and naming conventions, then reduce existing conditions to "survey by others." Every renovation model is drawn on top of that background, so leaving it unspecified leaves the project's foundation unspecified. Below is why the gap exists, where the clause fits in the ISO 19650 framework, and a fill-in template you can paste into your BEP.

    Why do BIM execution plans skip existing conditions?

    Because each standard the plan relies on points back at the plan. The BIMForum LOD Specification says it "does not replace a project BIM Execution Plan (BIMXP), but rather is intended to be used in conjunction with such a plan," and it defines what is modeled, not how closely it matches the building. The USIBD C120 Level of Accuracy guide defines accuracy but deliberately does not prescribe methods, and states that "a well-defined execution plan is key to obtaining the required LOA."

    So LOD defers to the plan, LOA defers to the plan, and the plan often defers to whoever shows up with a scanner. The result is a design team modeling against a point cloud nobody specified, with no agreed test for whether it is good enough.

    Where does the clause fit under ISO 19650?

    ISO 19650 works with a set of information requirements: organizational, asset and project information requirements (OIR, AIR, PIR), and exchange information requirements (EIR) set for each appointment. Part 2 introduces the BIM execution plan, the master information delivery plan and task information delivery plans.

    The UK BIM Framework's Guidance Part 2 describes the sequence. The appointing party develops appointment-specific EIR and issues them with the tender; the prospective lead appointed party returns a pre-appointment BEP that works through each requirement and responds "to the level of information need, acceptance criteria and delivery dates set by the appointing party." The guidance defines the level of information need as a framework for "the quality, quantity and granularity of information," and says an information exchange "is completed when the information receiver accepts the information."

    That gives the existing-conditions clause a clear home:

    Clause itemISO 19650 concept it answersReference to cite
    Capture method and coverageInformation production methods and proceduresProvider's method statement
    Registered accuracy and LOALevel of information need (quality)USIBD LOA
    LOD per disciplineLevel of information need (granularity)BIMForum LOD Specification
    Coordinate system and survey controlProject information standardSurvey control report
    FormatsProject information standardNamed file formats and versions
    Deliverable scheduleDelivery dates and information delivery milestonesMIDP / TIDP
    Acceptance testingAcceptance criteriaUSIBD LOA validation methods
    Data ownershipAppointment termsContract and project information protocol

    If the owner issues no EIR, the guidance advises the prospective lead appointed party to consider developing a BEP "which anticipates the EIR." The same logic applies when the EIR is silent on existing conditions: the design team writes the clause itself rather than waiting for one.

    What should each part of the clause say?

    Capture method. Name the method, the areas in and out of scope, and how inaccessible areas are handled. Leave the equipment to the provider; the LOA guide says "the decision of which means and methods shall be used to achieve a specified LOA should remain with the building documentation professional." You control the result.

    Registered accuracy and LOA. The USIBD LOA framework splits accuracy into measured accuracy (the point cloud) and represented accuracy (the model), and the C120 guide says both should be specified when measurements are processed into a deliverable. State each level, whether it is absolute or relative, and the confidence level; the guide uses 95 percent, which it ties to 2 sigma. USIBD has since released a newer LOA specification than the C120 guide quoted here, so name the version in the clause. Our ±5mm accuracy guide explains what an accuracy figure does and does not cover.

    LOD per discipline. Set LOD by element group, not for the whole model. Our LOD 200 vs 300 vs 400 comparison shows how to split levels by area.

    Coordinate system and survey control. Say who establishes control, which datums or project grid apply, and whether the model origin must match the survey. A cloud registered to an arbitrary origin is internally consistent and useless for tying new work to site.

    Formats and schedule. Name the point cloud formats (our file formats guide compares E57, RCP, LAS and PTS), the modeling platform and version, and tie each deliverable to a date or MIDP milestone so the background arrives before design needs it.

    Acceptance and ownership. Choose the validation method and pass condition before capture starts, and decide who owns and may use each part of the data. Both are covered below.

    What does the clause look like as a template?

    Paste this into the existing-conditions section of the BEP, or into the EIR if you are the owner. Brackets are blanks to fill; nothing in it is a recommended value for your building.

    EXISTING CONDITIONS INFORMATION
    
    1. CAPTURE METHOD AND COVERAGE
       Capture method: [ ] Mobile  [ ] Terrestrial (tripod)  [ ] Both
       Areas in scope: ______________________
       Areas excluded: ______________________
       Inaccessible areas: documented with photos and listed in the
         registration report; not modeled unless listed in Table EC-1.
    
    2. ACCURACY (USIBD LOA, version: ______)
       Measured accuracy (registered point cloud): LOA____
       Represented accuracy (model): per Table EC-1
       [ ] Absolute  [ ] Relative, relative to: ______________________
       Confidence level: stated at 95 percent (2 sigma) unless noted
       Provider's stated registered accuracy: ______ at ______ sigma
    
    3. LEVEL OF DEVELOPMENT (BIMForum LOD Specification, edition: ______)
       Table EC-1: element group | LOD | measured LOA | represented LOA
       Elements not listed in Table EC-1 shall not be modeled.
       Concealed elements, where modeled, shall be flagged as not
       field-verified.
    
    4. COORDINATE SYSTEM AND SURVEY CONTROL
       Control established by: [ ] Owner's surveyor  [ ] Provider
       Horizontal datum / projection: ______________________
       Vertical datum: ______________________
       Project base point and survey point: ______________________
       Control report delivered with: control point list, residuals,
         photos of control points.
    
    5. FORMATS
       Point cloud: [ ] E57  [ ] RCP  [ ] LAS  [ ] PTS
       Model: ______________ (platform), version ______
       2D: [ ] DWG  [ ] PDF
       Registration and QC report: [ ] PDF
    
    6. DELIVERABLE SCHEDULE
       Capture window: ______________________
       Registered point cloud due: ______ after capture
       Model due: ______ after capture, or by MIDP milestone ______
    
    7. ACCEPTANCE TESTING
       Measured validation: [ ] A no data check  [ ] B overlapping data
         sets  [ ] C independent measurements or methods
       Represented validation: [ ] A no check  [ ] B double check
         [ ] C triple check
       Check locations and number: ______________________
       Pass condition: ______________________
       Review period: ______ after delivery
       Failure: provider corrects at ______ cost within ______
    
    8. DATA OWNERSHIP AND USE
       Owner of raw scan data: ______________________
       Owner of registered point cloud and model: ______________________
       Licence to design team and contractors: ______________________
       Provider retention period: ______________________
       Hosting and access after close-out: ______________________

    For a fuller scope around this clause, see our scope of work template for scan to BIM, the complete guide to a 3D laser scanning scope of work and how to write a 3D scan deliverable spec.

    How would ZEALOT's published figures fill the blanks?

    Here is how our published numbers land in the template, as an example of the detail to ask any provider for:

    Template lineWhat we state
    Provider's stated registered accuracy±5mm registered accuracy; the manufacturer states 5 mm at 1 sigma (NavVis VLX3)
    Represented accuracyModel faces within ±10mm of the registered cloud at LOD 300, ±6mm at LOD 400
    Point cloud formatsE57, RCP, LAS or PTS
    Registered point cloud due3 to 5 business days after capture for a typical single building
    Model dueLOD 200 in 10 to 15 business days for ~100,000 sq ft; LOD 300 in 3 to 5 weeks

    Note the confidence levels. The manufacturer statement behind our scanner is given at 1 sigma, while LOA ranges are specified at 2 sigma. Line 2 of the template asks for the sigma so nobody reads a 1-sigma number straight into a 2-sigma table, ours included.

    How should acceptance testing work?

    The LOA framework gives three choices for validating measured accuracy: no data check, check by overlapping data sets, or check by independent measurements or methods. Represented accuracy has its own three: no check, double check, or triple check. If the clause does not choose, "no check" is a legitimate reading.

    Two further points from the UK BIM Framework guidance are worth writing in. Acceptance criteria should be checkable, including that "any definition for a value, either precisely or by a range, is satisfied." And the exchange is not complete until the receiver accepts the information, so name who reviews the delivery, how long they have, and what happens on a failure. Our point cloud QA guide lists the checks worth running on the cloud before modeling starts.

    Who should own the existing-conditions data?

    Whoever the contract says, which is why the contract has to say it. Separate ownership from licence: an owner may own the registered cloud and model while the design team and trade contractors hold a licence to use them for this project. Treat the raw scans, the registered cloud, the model and the control data as four separate items, because they are often held by different parties and needed at different times. Keep the registered cloud and control report with the project's shared information, so the next renovation starts from them. If the data needs to stay accessible after close-out, name the hosting arrangement; see our point cloud hosting service for one option.

    What should you do before the next BEP goes out?

    Fill in the template with your engineers, attach Table EC-1, and send it with the tender so every provider prices the same thing. If you want a second read, send us the scope. We return scan-to-BIM quotes within one business day, and if you are unsure where LOD should change across the building, we will mark up a floor plan with recommended LOD zones. Contact us to start.

    Sources

    Frequently Asked Questions

    What should the existing-conditions section of a BIM execution plan include?
    Eight items: the capture method and coverage, measured and represented accuracy under the USIBD LOA framework with a confidence level, LOD per discipline under the BIMForum LOD Specification, the coordinate system and who sets survey control, file formats and versions, a deliverable schedule tied to dates or MIDP milestones, an acceptance test with a validation method and pass condition, and who owns and may use the raw scans, registered point cloud, model and control data.
    Where do existing-conditions requirements belong under ISO 19650?
    The owner, as appointing party, states them in the exchange information requirements (EIR) for the appointment, and the delivery team answers them in its BIM execution plan, responding to the level of information need, acceptance criteria and delivery dates. UK BIM Framework guidance notes that when no EIR is issued, the prospective lead appointed party can write a BEP that anticipates it, so the design team can draft the clause itself.
    How should a BIM execution plan state point cloud accuracy?
    State measured accuracy for the point cloud and represented accuracy for the model separately, say whether each is absolute or relative, name the confidence level and choose a validation method. USIBD LOA ranges are specified at the 95 percent confidence level (2 sigma), so ask each provider at what sigma its figure is stated. Our ±5mm registered accuracy rests on a manufacturer statement of 5 mm at 1 sigma.

    Ready to See What Scanning Can Do for Your Project?

    Whether you're planning a renovation, documenting existing conditions, or exploring adaptive reuse — our team can help you understand what's possible with reality capture.

    Get a Free Consultation

    Stay Updated

    Subscribe to our newsletter for the latest insights on 3D scanning technology, industry trends, and project highlights.

    No spam, unsubscribe anytime. We respect your privacy.