top of page
TECHNOLOGY AND DATA CAPTURE · METHODOLOGY

How field evidence becomes usable building information

Capture methods support the Building Condition & Capital Planning Assessment. Field evidence shows what is present, spatial context helps locate it, and engineering review makes the information usable for repair, replacement and capital planning. Methods depend on the agreed scope; not every asset receives every measurement, and no universal accuracy is implied.

CURRENT · STANDARD IN EVERY ENGAGEMENT

Core capture methods

    Walkthrough video and photographs document accessible spaces, systems, equipment, nameplates and visible conditions. AI-assisted extraction can help identify manufacturer, model, serial and capacity from captured images, subject to engineer review. Spatial organization links agreed records to building, floor, room or zone so owners can find them later.

Scoped methods such as 3D/LiDAR capture and condition-specific measurements are added only when confirmed during scoping. The actual methods, coverage and limitations are stated in the engagement.

SCOPED · PARTNER-DEPENDENT · CONFIRMED AT SCOPING

Specialty measurement

3D/LiDAR scanning and certain condition-specific measurements depend on partners or specialized equipment. Availability is confirmed during scoping before any of these methods is included in an engagement.

FUTURE · DIRECTION ONLY, NOT A CURRENT SERVICE

Infrastructure-specific AI agent

Future or unvalidated methods, such as an infrastructure-specific AI agent that could reason over an owner's model, are a direction, not an operational product, and are not part of current scoped services.

SCOPE BOUNDARY · NO ACCURACY CLAIMS

What capture does not imply

We make no accuracy or completeness claims for any capture method. Coverage reflects the agreed scope, site access, and equipment for each engagement, and findings are subject to engineering review.

WHERE THIS FITS

A technical detail page within the assessment journey

This page supports Methodology and Portfolio Assessment. It explains how field data is captured; those pages explain how the assessment is run and what it covers across a portfolio.

NEXT STEPS

  • Asset Data and Deliverables → See what the captured data becomes: the validated model and its outputs.
  • Request Assessment → Start scoping, including which capture methods fit your portfolio.
SPATIAL INTELLIGENCE ENGINE

Every asset and deficiency, linked to a place you can find in the field

The model is spatially organized. Where included in scope, each asset and deficiency can be linked to its site, building, floor, room or mechanical space, column grid, coordinates, photographs, and 3D references. Spatial evidence supports three tasks: identifying the asset, reviewing its observed condition in context, and informing capital and maintenance decisions—with engineers, not software, making the judgments.

The coordinate reference system and measurement methods are defined for each engagement, and expected accuracy depends on the method used and site conditions. Locations are validated during engineering review, and limitations—such as inaccessible spaces or references not captured—are documented rather than assumed.

The intended result: field-identifiable records that a technician, engineer, or contractor can use to locate the item, confirm its condition, and plan the work.

Location vocabulary

Spatial information supports field identification and work planning only. It does not replace a survey by a licensed land surveyor or support uses requiring certified dimensional precision.

Site

The campus, property, or facility address the record belongs to. Recorded from owner-provided information and site documents; accuracy is limited to the identifiers the owner supplies.

Building

The named or numbered structure on the site. Confirmed by field observation against owner building lists; mismatched or legacy names are flagged for owner confirmation.

Floor

The level within the building, including basements, mezzanines, and roofs. Taken from drawings and signage where available; levels without clear labeling are described as observed.

Room

The room number or name where the item is found. Matched to posted room signage and available floor plans; accuracy depends on how current the owner's room numbering is.

Mechanical space

Mechanical rooms, penthouses, chases, roof areas, and ceiling spaces. Recorded where access is provided; spaces not accessed during the visit are listed as limitations.

Grid

The structural column grid reference (for example, C-4). Read from drawings and field-marked columns; accuracy is to the nearest grid bay, not a measured offset from a grid line.

Coordinates

X/Y (and where captured, Z) values in the coordinate reference system defined for the engagement. Accuracy depends on the capture method and site conditions and is stated per project.

Asset / component location

Where a piece of equipment or a component of it sits. Documented through observation, tags, and photos so it can be found again in the field.

Deficiency location

The specific point on or near an asset where a condition was observed. Described relative to the asset and supported by photographs; it is not a measured survey point.

Elevation

Height relative to the floor or a stated datum, such as ceiling-mounted or roof-level. Typically estimated or taken from drawings unless a measured method is included in scope.

Spatial relationships

How items relate to each other—what an asset serves, what feeds it, and what is adjacent. Based on observation and available documents; unverified connections are marked as such.

Photographic position

Where and in which direction a photo was taken, so the view can be repeated. Positions are approximate and tied to the room or grid reference.

3D model reference

A link from the record to a 3D model, scan, or virtual tour, where one is included in scope. Model accuracy depends on the capture method and is not survey-grade.

Coordinate reference system

Defined for each engagement—typically a local building system tied to drawings or the column grid. The system used is documented with the data so others can interpret it.

Measurement method

Field observation, drawing reference, photographs, and, where in scope, reality-capture tools. The method used for each location is recorded with it.

Expected accuracy, validation & limitations

Expected accuracy is stated per method and is intended to be sufficient to locate the item in the field. Locations are checked during engineering review; inaccessible spaces, outdated drawings, and uncaptured references are recorded as limitations rather than assumed.

Technical Boundaries

What is current, what is scoped, and what is future

Our core product is a continuously usable, spatially organized, engineering-validated model of an owner's physical infrastructure. To describe it accurately, we separate what the service delivers within an agreed scope, the conditions that govern it, and the opportunities that remain on our roadmap.

Claims Discipline

What we do not claim unless separately verified

  • No universal sensor suite.
  • No universal accuracy claims.
  • No survey-grade location.
  • No automated condition ratings without approved rules and engineering review.
  • No comprehensive coverage beyond the agreed taxonomy, physical access, and engagement scope.
  • No universal integrations; integrations depend on the client's system.
  • No measured savings.
  • No guaranteed timelines.
  • No predictive failure dates.
  • No ISO certification.
  • No BUILDER endorsement.
  • No currently operational client-facing AI.

Roadmap label: future opportunities are not current operational products unless separately confirmed for a specific engagement.

01 — Scoped Capabilities

  • The assessment creates and populates a spatially organized, engineering-validated model of the owner's physical infrastructure from comprehensive field data.
  • The model is designed to support maintenance, repair, replacement, and capital decisions, including work orders, cost planning, portfolio prioritization, project scoping, and owner-side engineering.
  • Comprehensive means comprehensive within the agreed taxonomy, coverage, access, and scope of each engagement.

02 — Limitations

  • AI-assisted extraction requires human engineering review.
  • Condition ratings require defined and validated rules.
  • Location accuracy depends on the capture method and its validation.
  • Integrations depend on the client's system.
  • Coverage is limited to the agreed taxonomy, physical access, and engagement scope.

03 — Future Roadmap (Not Current)

A client-facing infrastructure AI assistant is a future roadmap opportunity, not part of the current assessment.

bottom of page