Industrial as-built surveys: order data the next team can use

Start with the decision. Is the goal to check a clearance, plan a tie-in, produce drawings, author a model or deliver a record of existing conditions? That answer defines the survey boundary, reference system, required detail and handover format.

What “as-built” means in an industrial facility

• Name the required output
• Separate capture from modelling
• Link each format to its recipient

Design drawings record intent. An as-built survey records observed conditions at capture time. A plant can change again soon after delivery, so the date and limits of the record are part of the deliverable.

A point cloud represents visible surfaces as 3D points. A 2D drawing interprets that geometry for a plan or section. A BIM model organizes interpreted objects and the properties required by the brief. None automatically identifies concealed pipes, materials or an asset's operational state.

Scope capture around the job

• Describe the decisions the survey supports
• Define boundaries and interfaces
• Plan survey control

Set boundaries and interfaces

Name the areas, levels, lines, plant rooms and access routes to cover. Include the interfaces with proposed work, even when they fall outside the immediate footprint. A survey that ends before a tie-in location may not serve the design team.

In an operating plant, document safety rules, access windows and equipment that cannot be approached during production. Ask the capture provider to identify occluded and inaccessible areas. ATIS.cloud does not perform field capture; it supports later inspection and handover of the delivered data.

Define references and useful quality

Specify coordinates, levels and control points. “Maximum accuracy” is not a usable requirement without a task. State the tolerances relevant to the proposed equipment or design and ask how registration and control will be checked.

Choose point density and views around the objects people must examine. If a flange, valve or opening matters, name it in the brief. If equipment hides a connection, record that gap and decide whether another capture position or inspection method is needed.

Select deliverables before the survey

Check which formats each recipient can use. An E57, LAS or LAZ cloud may suit inspection or reuse in another tool, subject to preserved attributes and referencing. IFC serves a different need: model-object exchange. Request an early sample when several teams or applications will consume the output.

ATIS.cloud supports browser-based inspection and sharing of surveys. ATIS.cad can support drawing and building-object production from a scan with human review. Its early access requires a request and activation by the team, separate from the ATIS.cloud trial. Detailed industrial piping models are not an automatic output and must be scoped and checked as a distinct job.

A brief that can be tested

• State capture exclusions
• Specify formats and versions
• Set acceptance criteria

Consider an illustrative installation in a plant that must keep operating. The engineering team needs evidence for the machine footprint, lifting route, maintenance clearance and visible utility tie-ins. Attach a marked-up site plan identifying the decision-critical locations before asking a surveyor to capture anything. “Scan the workshop” does not define a checkable output.

The engineering team must set numerical tolerances for this machine and decision; no universal figure belongs in the brief. The survey provider should state how it will meet and verify those requirements, then report deviations. A concealed interface is still unresolved even when the rest of the cloud is accurate.

For a piping modification, the critical checks shift to tie-ins, centre lines, supports and access. Sections, isometrics or a model belong in the order only when their scope and detail are specified. The next section turns the brief into an acceptance task for the actual recipient.

Accept the handover with the end user

Have the recipient complete a real task before signing off:

1. Coverage: are required areas and interfaces visible, and are gaps listed?
2. Reference: do coordinates, levels, orientation and units match the project?
3. Quality: can critical objects be located and measured within agreed tolerances?
4. Formats: can each recipient open the intended output and find needed properties?
5. Traceability: are date, version, assumptions and revisions linked to the files?
6. Access: do sharing rights and expiry fit the handover?

When a check fails, distinguish recapture from registration correction, missing documentation or a modelling assumption. These are different remedies and often different responsibilities.

Work around an operating plant

Survey scope depends on the operator's access rules, safety procedures, shutdown windows, traffic and restrictions on imagery. A capture team cannot promise to see a pipe hidden behind running equipment. If that pipe affects the design, arrange another evidence source, a safe access window or an explicit reservation in the deliverable.

Before the site visit, confirm:

• accessible zones and the people who may accompany the survey team;
• critical elements to measure and likely occlusions;
• existing plans and control references to check, without assuming they are current;
• safety, authorization and distribution restrictions;
• recipients and required format for each output.

After capture, distinguish a data gap from a physical difference between drawing and plant. A pipe missing from the cloud may simply be concealed. An apparent offset may reflect a registration problem. Each finding needs a different check before the design changes. The acceptance record should state what was verified on site and what remains unresolved.

Example: a production-line change

Suppose a team plans to move a conveyor and add a maintenance route. The scope covers the affected bay, adjacent equipment and circulation, tied to the project's control reference. A practical minimum handover might include a checked point cloud, control information, an occlusion register and contextual views. Drawings or BIM objects, if needed, require their own scope and level of detail.

During acceptance, the engineering team loads the proposed design alongside the survey, checks alignment, then tests clearances and interfaces. The site operator reviews access. If a critical opening was not captured, the team records a reservation and orders a targeted supplement. A point cloud cannot turn a design assumption into approval by itself.

Keep delivery and revisions accountable

The supplier may provide both source files and a browser-based review project. The latter lets recipients inspect the record without installing every authoring tool. It does not replace contractual archiving or a file-level quality check. Show the version, date and access window on the handover. If a subsequent survey corrects the earlier one, retain the reason and notify anyone who relied on the superseded version.

Plan the delivery: explore ATIS.cloud for manufacturing, supported formats, project sharing and the Scan-to-BIM workflow guide. Use a demo to test a representative captured project.

If the survey will later feed an operations reference, our industrial digital twin guide explains how to connect the point cloud, the model and equipment data.

Compare survey proposals on the work they will support

The query “industrial 3D scanning” can lead to scanner hardware, a capture contractor or software for using the result. Choose the supplier against the intended handover, not the device name alone. The buyer should supply the same scope, access constraints and acceptance tasks to each provider. Otherwise two bids can appear comparable while one covers the full production bay and another excludes its service routes.

Ask each bidder to state its assumptions:

• whether the plant can remain in operation during capture and how moving objects will be handled;
• which areas need escorts, permits or a shutdown window;
• how the point cloud will be registered to project control;
• what will be recorded when a critical surface is concealed;
• which original and derived files will be handed over, in what coordinate system;
• how corrections will be documented after the client's review.

These questions help the buyer distinguish survey quality from model detail. A provider may deliver an accurate registered cloud without producing BIM objects. Another may create drawings and a model but need a longer period to resolve hidden or ambiguous equipment. Put each output and its acceptance condition in the scope of work. Do not assume that a marketing image of a detailed model describes the files you will receive.

Make the acceptance test part of procurement

Include one representative test area in the contract or purchase order. Ask the provider to show its capture boundary, control report, registration method and unresolved gaps there. Have the engineering team load the delivered format into its own workflow and locate a known interface. Have the site operator check whether the context is recognizable and current. This reveals a coordinate mismatch or missing corridor while there is still time to correct the delivery.

If the plant imposes confidentiality or distribution rules, agree on the approved transfer and review route before fieldwork. Browser access can make review easier, but the legal source files, project archive and rights to reuse the survey need their own explicit terms. ATIS.cloud is relevant after capture when a checked dataset must be inspected and shared. It is not the contractor that performs the field survey or certifies the survey's engineering accuracy.