Build the model. Verify the change.

1. Collect legitimate sources. Register the drawing revision, capture date, rights, coordinate frame and coverage. Keep private files in the authorized project system.
2. Align what can be aligned. Match fixed features between plan, section, photo and 3D. Record camera assumptions, scale, control and residuals. A nominal door size or a published object diameter is a candidate constraint until the same feature is positively identified.
3. Reconstruct and classify. Keep observed surfaces, interpreted geometry and missing information visible. Extract features where source quality supports them; do not fill hidden systems with plausible guesses.
4. Define the requested output. Select features and a region, confirm the output format and intended use, and review the scope, estimate and verification needs.
5. Generate, then check. The intended service automates extraction and packaging with human QC and oversight. Each result needs source checks, coverage/error review and an accepted release.
6. Verify revisions in the field. Target the uncertain or changed regions. Compare capture dates, geometry and evidence; retain the prior revision and record the accepted changes.

Current proof of concept: model review and reconstruction studies are available. Selected existing-model geometry can be packaged automatically as IFC4 after project sign-in, with a recorded human QC step. Automatic feature detection from raw scans is not connected. A local selection or draft quote is not a submitted or accepted order.

Start with a clear specification and usable evidence. A BIM model can begin with dimensioned plans, sections, schedules and photographs. Whether it meets the specification depends on the required elements, information, tolerance and checks.

1. Agree the finish. List required parts by zone, their intended use, LOD 250 requirements, formats, tolerance and acceptance checks. Identify which sources describe design intent and which document existing conditions.
2. Check the starting information. Confirm the building, level, revision, units and dimensions. Use known dimensions or control to establish scale. Public photos help identify visible features; they do not establish a complete measured interior.
3. Build and connect. Model the supported elements, keep source IDs, and generate the plans, sections and reflected ceiling plan from that same revision. Record estimated and unobserved parts.
4. Use Eddie's support. GO3D can guide the crew remotely, check source coverage, manage revisions and review the model. If a gap needs a site visit, use agreed dimensions, a suitable 360 walk or targeted capture. No scan is required where sufficient reliable evidence already exists.
5. Check, then accept. Compare the required elements with the agreed references and independent checks. A named reviewer records the basis for acceptance. Update only the parts that pass; keep remaining gaps visible.

Jambo today: the review model, drawings and CAD exports demonstrate this workflow. Zero regions are accepted as LOD 250. The controlling plan/levels, agreed element matrix and tolerance, metric scale checks, current lighting/ceiling evidence and receiving-software review remain open.

See the model's verification tasks · USIBD accuracy guidance · Procurement reference page

IFC is the BIM exchange format provided here. Editable DXF is CAD interchange. Native RVT/DWG authoring and receiving-application acceptance have not been demonstrated.

Build a useful BIM baseline from usable plans and other reliable information. A scan is not a prerequisite for every model: use it to check uncertain conditions and update the baseline when the project needs it.

If scope changes, reuse the information already captured or sufficiently documented. Add verified detail as needed, keep gaps visible, and retain earlier versions. More detailed appearance never upgrades an unverified dimension.

Requested delivery target: LOD 250. Agree the required parts by area, tolerance, source/control and checks before acceptance. The current study has not demonstrated that target. The VDC Forum / BIMForum Global description is a reference, not an automatic project accuracy assignment.

Marc sets Woolpert's client price and margin. Earlier suggested figures are source-based planning references, not a GO3D quotation. The current agreed flexible-schedule demonstration remains $0; ongoing service terms are agreed separately.

Choose direct on-site delivery, project support that trains/equips the team and manages data/direction, or remote delivery from suitable provided sources. These support plans are separate from the point-cloud/BIM/coordination deliverable options.

Scale the agreed work to the budget. A practical path starts with on-site help to deliver the project and train the team, then shifts to remote support as the team is ready. Define data, access, field and review responsibilities in the work agreement.

Open LOD 250 guide in the 2D scope or 3D model. Amber means modeled but needing verification; grey means missing evidence; purple means conditional scope. Green requires current-source evidence, agreed checks and named acceptance. The current study has zero accepted regions.

Select a represented part to see the checks it needs. Use Previous/Next for area tasks, then save a local task or add its checks to the local field recap. Notes and downloads do not submit work or approve the model. The marked plan and model are not a verified registration.

The tour includes the field guide. Start with reliable plans and observations; scan only the gaps or revisions that the intended use requires. Keep Z03 lighting-only: no flooring.

Open the existing 3D field guide

Compare client revenue with processing cost, human QC time and targeted field-revision cost. Leave unknown inputs blank. Use measured processing time and reviewed output yield as evidence; a planning scenario is not actual margin. The current $0 demonstration is separate from the customer bid. Automatic extraction is a capability developed and measured together, with human QC and oversight.

Resolution, point spacing and detailed-looking geometry do not establish project accuracy. A model dimension can be exact within the model while still being wrong for the real building. LOD 250 is requested as the delivery target; current acceptance and a USIBD LOA remain unassigned.

Obtain permission and follow site access rules. Keep the camera level, move steadily, avoid abrupt rotations, retain the original files and capture times, and repeat fixed features from several positions. Capture people only within the site's permitted practice.

1. Start at the lobby entry. Record an identifying view and a slow overview. Include floor, column bases, ceiling and the first visible lighting pair.
2. Walk a loop through the main lobby. Move along one side, cross at an accessible end and return along the other. Keep the same fixed columns and lights visible across overlapping viewpoints.
3. Pause at each lighting pair. Capture oblique views from both sides plus upward detail of shields, suspension and adjacent framing. Add sharp still photographs for thin members and dim areas.
4. Record the bridge and galleries where access is permitted. Connect upper and lower observations through the same fixed supports. Do not enter restricted areas or lean outside guards.
5. Continue to the savanna glazing. Include glass-frame intersections, floor transitions and bridge relationships. Avoid relying on reflections as matching geometry.
6. Close the interior loop. Return to the starting fixed features. Log interruptions, occlusions, moving objects and any fixture or surface not covered.
7. Capture an exterior loop separately. Connect entry, accessible elevations and site paths through repeated fixed features. Record which roofs and upper facades remain occluded.

A steady 360 walk is a low-friction coverage and visual-context starting point. It does not by itself establish scale, hidden geometry, surveyed coordinates or survey-grade accuracy. Add verified dimensions/control and targeted scans where the intended use requires them.

Multi-view photogrammetry can recover camera positions and geometry when the images contain enough stable overlap, texture, parallax and calibration information. Repeated rails, patterned shields, glass reflections, motion blur and changing furnishings can create false matches.

NeRF and 3D Gaussian Splatting can help synthesize views and communicate the space. Treat them primarily as visual aids until geometry, scale and dimensions are independently constrained and validated. An attractive fly-through is not evidence of measured accuracy.

Keep image registration status, tie-point quality, camera assumptions and independent check dimensions with each result. The present Jambo photo audit has candidate matches, with no accepted metric photo reconstruction.

“I need an LOD 250 BIM model of this area.” A marked drawing, selected elements or a limit box can define a request. The platform should check the available sources and identify what is missing.

• Suitable scan coverage exists: scope and run supported extraction, followed by human QC.
• Scan coverage is missing: prepare a capture bid for the selected area, with access, required accuracy, deliverables and deadline. Review returned coverage and integrate accepted data.
• The customer has more information: contribute plans, photos, video, dimensions or corrections against the area or element. Preserve source rights, dates, private access and revision history; review changes before acceptance.

Reliable plans and imagery may support a model without a new scan. Target capture at the gaps and required checks. A drawing and request can start scoping; they do not establish metric accuracy or LOD acceptance.

Planned connected workflow. Voice-to-extraction, customer uploads and automatic bid dispatch are not operating integrations in this review. No bid, external message, payment or automatic acceptance is triggered by this guide.

The requested customer workflow is select region → choose features → confirm scope and price → automatic extraction → human QC → accepted release. The BOM should carry each element ID, classification, quantity basis, source revision and verification status.

Use field scanning as a revision and verification tool: capture the uncertain areas, changed surfaces or failed checks identified by the model. A field recap should say what needs checking, why it matters and what evidence will close it.

The agreed GO3D demonstration stays $0 to Woolpert within the agreed scope. Earlier planning prices are references, not an automatic charge or Woolpert's client bid. Unconfigured processing, external systems and payments must not be shown as completed.

For every file or modeled region, retain the original source ID and hash; provider/author and rights; capture date separately from publication/download date; coordinate frame and units; coverage; measurement or inference method; alignment assumptions; validation evidence; reviewer; release status; and the changes from the preceding revision.

Drawings should identify the model revision, sheet/plot scale, units, source hashes and estimated-versus-measured status. Field verification should update the affected elements and preserve the earlier model and drawings.

Disney D23, April 2016: eight-shield chandeliers and nominal medallion dimensions ↗

The largest Africa-map medallion is described as 8 ft (2.4384 m) across; the other four as 4 ft (1.2192 m). Confirm identity and perspective before using either as a scale constraint. A published nominal dimension is not survey control.

Catalog check: 29 October 2026. Acquisition date is shown separately from catalog publication. Footprints were tested against the Jambo reference point and working search envelope. The envelope is not a surveyed boundary.