Turning Existing-Site Measurements into a Booth Release Basis

Direct answer: release a defined basis, not a survey file

Existing-site measurements can support a booth-layout release only when the project can identify exactly what was measured, where, when, in which physical state, from which references, by which controlled method and data record, and for which decision. The release package must close the coordinate and elevation basis, coverage boundary, obstacle identities, floor and opening conditions, measurement state, uncertainty or limitation treatment, separately owned project allowances, controlling revision, unresolved dependencies, and change or remeasurement triggers.

A point cloud, marked-up plan, model, dimension schedule, photograph, or survey report is not self-explanatory release evidence. Each can be useful, but each result supports only its named site area, feature, physical state, revision, limitations, and decision purpose. A measured column does not prove the space behind it is visible. A measured opening does not prove a module, workpiece, tool, or person can pass. A historic as-built record does not prove that the current as-found condition is unchanged. A clean digital model does not prove that concealed services, temporary items, future work, or omitted geometry are absent.

Use four bounded dispositions for every release-critical site item:

• Usable for the named layout release: the required identity, state, evidence, ownership, and dependency fields are closed for that specific use.
• Conditional input: the assumption, affected layout relationship, owner, evidence due, validation gate, and failure disposition are recorded. The affected geometry or interface remains unavailable for manufacture until the gate closes.
• Hold and remeasure or resolve: a reference, feature, condition, result, allowance decision, revision, or authority is missing, stale, conflicting, or unsuitable for the named use.
• Reference only: the information can frame questions but cannot freeze the affected layout.

These are project decision labels, not survey grades, accuracy classes, standard-defined statuses, safety approvals, or conformity results. The upstream custom-booth project brief can identify the site and intended arrangement, but it does not turn a preliminary site file into release evidence.

Most importantly, a survey record is an input to layout release. It does not by itself prove every site condition, final clearance, structural adequacy, access safety, fire or building compliance, installation feasibility, commissioning, future condition, or StelBooth capability. If a release-critical fact or owner is missing, keep that affected relationship open. Do not invent a dimension, tolerance, instrument accuracy, allowance, site fact, or supplier capability to close it.

Establish a reproducible reference basis

The site record and the proposed booth layout need a controlled way to describe the same place. Name every coordinate or elevation system that appears in the package: for example, a local project grid, building grid, equipment coordinates, or another appointed reference. Do not assume that two files use the same realization because their axes have similar names.

For the basis used by the layout, record the origin, axis directions, orientation convention, vertical or elevation reference, reference points or physical features, how those references were realized, their condition when used, and who owns the definition. If site data must be transformed into layout coordinates, identify the source and destination systems, transformation record, revision, responsible authority, and the check used to accept it. If the physical references are damaged, moved, covered, recreated, or inaccessible, the dependent relationship is open until the appointed authority resolves the effect.

ISO's public catalog record identifies ISO 5459:2024 as addressing datums and datum systems in geometrical product specifications.^[1] That public subject supports the need to identify a reference framework when the project invokes it. It does not select a booth-site origin, building grid, elevation reference, target arrangement, transformation, tolerance, measurement method, applicable edition, or conformity result.

Treat reference realization as evidence, not a label. A named benchmark without location and condition cannot be recovered reliably. A model origin without its relationship to physical references cannot control field placement. A temporary mark may be usable only while its preservation and purpose remain controlled. The package should show which layout features depend on each reference so a later disturbance can reopen the right entries instead of invalidating everything without analysis.

An adjacent large-assembly guide discusses datum continuity across shipping and reassembly. Its useful analogy is limited to preserving reference identity and state through change. It supplies no site datum, survey method, acceptance value, or booth-layout result.

Classify coverage, obstacles, and unknowns

Give every release-relevant floor region, opening, obstacle, reference, and interface a stable Site Item ID. The register should say whether the item is measured, observed only, assumed, inaccessible or concealed, temporary, planned or future, or excluded. Those labels are an editorial control for this project, not standardized survey classes.

Measured means a retrievable result exists for a defined feature or measurand in a recorded state. It does not mean that every surface of the object was visible, that the result is current forever, or that it is suitable for a different decision. Observed only can establish that something was seen, but it cannot silently become a release dimension. Assumed needs an owner and validation gate. Inaccessible or concealed records a known evidence gap instead of inferring empty space. Temporary and planned or future preserve the difference between what existed during measurement and what the layout will encounter. Excluded prevents a survey boundary from being mistaken for complete site coverage.

Large-scale dimensional-metrology literature reviews multiple technologies and application conditions rather than identifying one universally best method.^[2] Its bounded relevance here is planning: the appointed measurement authority should relate the task, measurement volume, access, environment, reference realization, selected method, data identity, and traceability or uncertainty treatment. The review does not rank an instrument for this site or provide a scan density, accuracy, target layout, coverage, fitting rule, or acceptance value.

For obstacles, record the stable identity and the physical portion that the evidence covers. Depending on the named layout relationship, relevant items can include columns, beams, walls, bracing, ducts, pipes, cable routes, trays, panels, equipment, platforms, guards, trenches, covers, plinths, rails, projections, lights, signs, or temporary works. This is a prompt list, not a claim that any item exists at a particular site.

Also record what the evidence does not establish. Geometry does not identify service contents, isolation state, ownership, hidden routing, relocation permission, structural function, required separation, or future position. A modeled object may be based on a nominal drawing rather than a current observation. A point on one face does not define an entire surface or the space behind it. The site-utilities and interface-responsibility guide can help name owners and prepared-on-site inputs, but it does not verify utility identity, condition, route, or measured geometry.

Close floor, opening, and approach conditions

A floor input needs more context than one elevation. Define the surface that existed during measurement and the area for which the evidence applies. Where they affect the named layout, record the relevant elevation or profile relationship, changes of level, slopes, edges, thresholds, joints, recesses, pits, trenches, covers, plinths, rails, coatings, toppings, unfinished areas, temporary protection, or future layers. State whether an item was present, removed, planned, inaccessible, or outside the measured boundary.

That record still does not prove slab capacity, anchor suitability, structural condition, flatness compliance, drainage performance, final finish acceptance, or an installation adjustment. Those decisions require their own criteria, evidence, and responsible authorities. Do not convert unused geometric space into an unnamed erection or levelling allowance.

For each opening, identify the frame, sill or threshold, leaf or panel, track, guides, seals, guards, handles or other hardware that affects the named use. Record the operating state in which the clear geometry was defined, along with the approach and withdrawal zones and any adjacent obstruction. Distinguish an existing opening from a proposed alteration, temporary removal, or future finished condition.

The phrase clear opening is incomplete until the project defines what is clear, in which state, and for which moving object and route. A door may have a different occupied envelope while moving than when held open. A nominal frame dimension does not include every approach constraint. A static check does not establish lifting behavior, dynamic movement, safe handling, or compliance.

The maintenance-clearance guide shows why a named task, door state, removable item, tool, and approach can define a different envelope. The module shipping and local-assembly guide addresses another route with its own packed items and installation sequence. Neither page provides a B6 site dimension, allowance, passage result, lifting method, or safe-work decision. Production workpiece movement, module delivery, and maintenance access remain separate checks even when they share an opening.

Bind every result to its measurement state

For each release-critical result, record the date, physical and operational state, access and visibility, temporary works, movable objects, relevant site or environmental conditions identified by the measurement authority, and the current reference realization. Add the method category, instrument or data identity, setup or observation-network reference, covered extent, processing or fitting rule when it affects interpretation, raw-data or report identity, and the person or organization responsible for the measurement conclusion.

NIST Technical Note 1297 addresses reporting measurement results with uncertainty, keeping referenced measurement-process documents current, and the relationship between a measurand and the method used to define it; it also cautions that changed use conditions can introduce effects not present in the original measurement context.^[3] This article transfers only that disciplined record relationship. The guidance does not supply a booth-site uncertainty budget, coverage factor, tolerance, decision rule, calibration interval, instrument, remeasurement period, or acceptance result.

Ask the appointed measurement authority to provide the uncertainty or limitation statement needed for the decision. Do not substitute a catalog instrument specification, display resolution, repeat reading, rounded coordinate, or file precision for that statement. Do not compare results from different references, physical states, coverage, processing rules, or methods as though they were automatically equivalent. The authority may decide they are comparable, require a controlled transformation, limit the use, or request new evidence; this article does not make that decision.

Keep measurement uncertainty separate from project allowances. They answer different questions:

If a required value is absent, mark it open. An unexplained allowance, contingency, or residual gap cannot close an unknown because no reviewer can tell which effect it was intended to cover, whether effects are being counted twice, or who accepted the remaining risk.

Use the Site Measurement Release Register

Use two linked text tables. Part A records what the site evidence means. Part B records how the project proposes to use it. A stable Site Item ID joins the rows so an allowance, revision, disposition, or trigger cannot drift onto a different feature.

The tables below are a project-defined editorial tool. They are not a survey standard, accuracy specification, inspection plan, conformity scheme, building approval, or proof that any entry is correct. Keep cells blank or explicitly open until the named authority supplies controlled information.

Part A: basis and condition record

Read the middle cell as the answer to what physical condition and reference did the result describe? Read the last cell as the answer to what retrievable evidence and limitation make that description usable? A row is incomplete if it contains a coordinate with no feature definition, a feature with no coverage, a report with no state, or a state with no responsible owner.

Part B: release and change record

The shared ID is mandatory for using the tool, but the article does not prescribe the project's naming syntax. One physical item may need several rows when different surfaces, states, or decision purposes have different evidence. Conversely, do not split one source into artificial rows merely to make an incomplete record appear detailed.

Use usable for the named layout release only when the required chain is closed: identity, reference, coverage, physical state, measurement evidence, relevant uncertainty/limitation, allowance decisions, controlling revision, dependencies, and release authority. This status freezes only the named layout relationship. It does not release every booth feature or authorize structural, safety, compliance, installation, procurement, or manufacture decisions outside the recorded scope.

A conditional row must identify the assumption and keep the affected geometry or interface unavailable for manufacture until the validation gate closes. Verify on site, allow enough clearance, coordinate later, or field adjust does not qualify without an owner, evidence due, decision gate, and failure disposition.

Control revisions and remeasurement triggers

Identify which site plan, measurement report, point or surface data set, model, redline, photograph register, and layout revision controls each information type. Preserve the issuer, date, status, revision, and superseded record. ISO's public catalog identifies ISO 16792:2021 as addressing digital product-definition data practices.^[4] That subject supports controlled identity when a project invokes the framework; it does not prescribe this register, a file format, source hierarchy, approval route, revision syntax, applicability, or conformity.

When two sources conflict, do not choose the more convenient geometry. Record the conflict, affected Site Item IDs and layout relationships, source owners, interim hold, evidence required, and authorized disposition. A newer date does not automatically make one source technically controlling if it covers a different state or purpose.

Changes can propagate through connected design relationships; engineering-design research provides a bounded general basis for reviewing dependencies instead of considering only the changed item.^[5] The cited rotorcraft case does not predict a booth impact, assign responsibility, or require a full survey after every change. For B6, it supports asking which released entries relied on the changed condition.

Trigger an impact review when a reference is disturbed or recreated; construction, demolition, repair, damage, settlement, floor work, or finish work changes a relied-upon condition; an opening, service, platform, guard, or equipment item moves; temporary works change; a concealed or excluded area becomes decision-critical; sources conflict or become untraceable; or the booth footprint, height, route, selected equipment, installation method, maintenance task, or evidence purpose changes.

The appointed authorities decide the response. It may be a document reconciliation, targeted field check, transformation validation, partial remeasurement, or another controlled action. B6 supplies no calendar interval and does not require full remeasurement when an impact review shows that a bounded record remains valid.

Use the adjacent controlled drawing-handoff discipline to see how identity, revision, unresolved inputs, and approval records can remain connected in another equipment context. It does not define this site's source priority, survey status, or booth release.

Assign owners and hand off one controlled package

Name actual parties in the project record. Do not leave responsible authority as a shared placeholder.

• Customer or appointed design authority: owns functional layout requirements, accepted source precedence, project clearance and allowance decisions within its role, and authority to release or hold the affected geometry.
• Site or building authority: owns site access, current-condition disclosure, records of relevant change, concealed-condition information, and structural or local compliance decisions within its appointment.
• Survey or measurement authority: owns the measurand, reference realization, method, equipment/data status, coverage, processing, uncertainty or limitation statement, report identity, and conditions under which the result remains usable.
• Installer and selected-equipment authorities: own installation or erection method, equipment geometry, adjustment needs, temporary works, movement states, and interface evidence within their scopes.
• StelBooth, only where the written project scope assigns it: may use controlled inputs to coordinate affected booth geometry, identify conflicts, and maintain open-item records. This article and its external references do not prove that surveying, design, manufacture, installation, compliance work, or any project result is included or achieved.

Issue one retrievable package containing the reference-basis record, coverage and evidence-state map, completed two-part register, controlled source index, raw-data/report references, conflicts, separately owned allowance decisions, conditional and held entries, dependency/reopen register, and named approval record. The package should let a later reviewer determine what was known, what was not known, which state was measured, what decision was made, and what change invalidates or reopens it.

The final release test is deliberately narrow: can the team trace every release-critical site relationship from the current physical feature and reference basis through measurement evidence, limitations, separately owned allowances, controlling revision, dependencies, and a named decision authority? If not, hold that relationship. If yes, the package can support the named layout release, but it still does not prove all site conditions, all clearances, structural adequacy, safe access, building compliance, future state, installation acceptance, or supplier capability.

References

1. International Organization for Standardization, ISO 5459:2024, Geometrical product specifications (GPS) - Geometrical tolerancing - Datums and datum systems. Official ISO catalog record. Public title and subject only; no clause, site datum, method, tolerance, applicability, or conformity is supplied. Back to citation
2. G. N. Peggs et al., "Recent Developments in Large-Scale Dimensional Metrology," Proceedings of the Institution of Mechanical Engineers, Part B: Journal of Engineering Manufacture, 223(6), 571-595, 2009. DOI. Review and public-abstract context only; no site instrument, accuracy, coverage, uncertainty, or acceptance rule follows. Back to citation
3. Barry N. Taylor and Chris E. Kuyatt, Guidelines for Evaluating and Expressing the Uncertainty of NIST Measurement Results, NIST Technical Note 1297, 1994 edition, sections 7.1, 7.2, 7.6, and Appendix D.4.1. Official NIST landing page. Guidance only; it supplies no project uncertainty budget, allowance, tolerance, decision rule, instrument, or remeasurement interval. Back to citation
4. International Organization for Standardization, ISO 16792:2021, Technical product documentation - Digital product definition data practices. Official ISO catalog record. Public title and subject only; no B6 workflow, file format, source hierarchy, project applicability, or conformity is supplied. Back to citation
5. P. John Clarkson, Caroline Simons, and Claudia Eckert, "Predicting Change Propagation in Complex Design," Journal of Mechanical Design, 126(5), 788-797, 2004. DOI. Abstract-level connected-change caution only; the rotorcraft case does not predict a booth impact, require a full resurvey, or prove project capability. Back to citation