What AssetAtlas Is

AssetAtlas is the asset registry for a project, with a position attached to every record. Each piece of equipment gets a record, and that record knows where it physically sits — on a floor plan and inside the 360° capture. The registry is unified at the project level and spans every building in the project.

It opens from Project → Apps, in the Add-Ons section. It holds one asset table for the whole project, and each asset in that table carries a location and, once placed, a coordinate.

Facility and plant managers own the registry, operation engineers keep it current and place assets in space, and QA/QC, field, and inspection roles read it.

Note: Project Member and above can add, edit, import, reposition, and delete assets. See Before You Start for what the read-only tiers can do.

This release changes four things:

• Assets attach to the new built-world structure — Project (= Facility) › { Site | Building › Level › Work Area }.
• An embedded SiteView viewer shows the registry in 3D and on a 2D floor plan, in four layouts.
• Assets can be given a coordinate by pointing at them in the viewer.
• CSV import and export carry the location columns.

AssetAtlas is where two separate setups meet. One defines what an asset is, the other defines where it can go — and neither is configured inside AssetAtlas itself. The rest of this article follows the diagram in order.

Before You Start

AssetAtlas is where two separate setups meet, and neither of them happens inside AssetAtlas. Do them in this order.

Team Settings — what an asset is

Three objects, created at team level and shared across every project. They chain together, and the order matters because each one references the one before it.

1. Status Set — the statuses an asset can move through. Created under Templates → Status Sets.

• Statuses sit in three stage groups: Initiation Stage, Execution Stage, and Finalization Stage.
• The order set here is the order the dropdown shows, and the first status becomes the default on a new asset.
• Those stage groups are also what the asset table's Status filter groups by.

2. Form Template — the property fields an asset carries. Created under Templates → Forms, and held in a shared pool.

• Whatever fields are defined here are what appears on an asset's Properties tab.
• The Status Set attaches here — to the Form, not directly to the category. The boxed line in the Live Preview below names which Status Set this Form is using.

3. Asset Category — the classification tree. Created under Asset Categories.

• Each Asset Category Type holds one tree; the types are listed on the left.
• A category references one Form Template — boxed below — and its child categories inherit it.
• The category then shows the result as its Effective Status Set.

What the chain means in practice: an asset takes its statuses and its property fields from its category, never from the project. Two assets in different categories can offer different statuses and different fields. If a category or its Status Set has no options, the Add New Asset dialog still opens, but Save is blocked.

Project setup — where an asset can go

Built in the project Skeleton, once per project.

• The built world.
  • The Site — exactly one per project, fixed, and not addable.
  • Buildings, each holding Levels, each holding Work Areas.
  • An asset attaches to either the Site or a building path.
• The names matter more than they look.
  • A CSV import matches Building, Level and Work Area by name, not by ID.
  • Whatever is typed in the Skeleton is exactly what an import file has to carry. LEVEL_01 and Level 1 are two different levels as far as the import is concerned.
  • Settle the naming before anyone builds an import file. See Import a CSV File for what a mismatch looks like.
• Captures and plans.
  • The 3D viewer needs a SiteView capture for the selected Level.
  • The 2D map needs a Reference Plan for that Level.
  • With no Level selected, the viewer reads "Select a Level to load the viewer".

Who can do what

• Project Member and above — add, edit, import, reposition, and delete.
• SiteView Member and SiteView Observer — view asset detail and status history, browse by category, filter by text, select rows, switch layouts, and navigate between the table and the viewer.
• A user without execute permission on an action sees "You do not have permission to {action} for this asset."

Pick the Asset Category Type

On a project with no Asset Category Type configured, AssetAtlas opens on a selection screen instead of the asset table. Select a type from the options configured in Team Settings and you land on the main page. Later visits skip the screen.

Once at least one asset exists under an Asset Category Type, the selector in the header becomes read-only and shows a lock icon. Hovering it explains why: "Delete all assets to change Category Type." Changing the type then means deleting every asset under it first. This is the one setup decision in AssetAtlas that cannot be walked back cheaply, so agree the customer's category taxonomy before the first import, not after.

The Add New Asset dialog inherits its Category options and its default value from whichever Asset Category Type is active in the header.

Add the Assets

There are three ways to create asset records. Add one at a time for corrections and demonstrations; import a CSV file for anything at scale. Both live in the Actions menu at the top right of the table, alongside Export Selected to CSV and Delete Selected.

Add One Asset

• Click Actions → Add New Asset.
• Complete the required fields: Category (inherited from the header Asset Category Type), Name, Status, and the location — Building, Level, and Work Area are each marked required. Description is optional.
• Leave Add another asset after saving selected to keep the dialog open for a run of entries.
• Click Save.

Status defaults to the first status in the category's Status Set. The asset appears in the table immediately, and in the viewer once it has a Level or a coordinate.

Duplicate is the quiet third path. From a row's Actions (⋮) menu, it copies the asset's properties, category, and location, but deliberately not its coordinate and not its attachments — which is also a useful way to explain why coordinates are per-asset.

Import a CSV File

CSV import is a four-step wizard: Import CSV → Category mapping → Map Properties → Review Properties.

Two things trip people up:

• File size. The upload step caps the file at 1 MB, which arrives sooner than customers expect on a several-thousand-row inventory. Split large inventories across files.
• Site and Building are separate columns in CSV, even though the interface merges them. A row carries one or the other, never both.

The wizard treats two kinds of error differently. Mapping problems at Map Properties block progress to Review Properties. Row-level validation problems at Review Properties do not: invalid rows are excluded, the validation summary counts the valid ones, and you can go back to fix the file or proceed.

Note: The Building, Level and Work Area values in the CSV are matched by name against the project Skeleton. A row whose level reads Level 1 against a Skeleton that says LEVEL_01 is rejected as an unrecognised level. Rejected rows are listed at Review and Confirm and are left out of the import — the rest still import, so it is easy to miss. Export the Skeleton names, or copy them straight out of the project, before building the file.

Export to CSV

Select the rows to export, then choose Actions → Export Selected to CSV; the menu shows the selected count beside it. The export carries the asset fields together with Building, Level, and Work Area.

See the Registry in Space

The layout picker is the grid icon at the top right of the header — its tooltip reads Change layout. It opens a LAYOUT menu with four options: Table Only (the default), 3D View + Table, 2D Map + Table, and 3D + 2D + Table. In the combined layout the 2D Reference Plan sits on the left and the 3D viewer on the right, split 65/35 in the 3D viewer's favour, with a drag handle to rebalance them.

The 3D viewer is a SiteView you choose. Switching into a 3D layout with no SiteView selected opens a Choose a SiteView dialog listing the project's SiteViews. Inside the viewer, a chip shows the capture date with a See other dates link, and the context bar above the viewer carries the project name with Building and Level selectors. The 2D map shows the Reference Plan for the selected Level.

Pins in the viewer are Status Markers: colour encodes the asset's status, the pin shape is common to every asset, and the asset name appears on hover. Pins also survive a re-capture — coordinates are bound to the Level rather than to a capture version, so when the site is captured again the pins land in the same places. This is the reassurance owners want before they commit to placing a few thousand assets.

Navigation runs both ways between the table and the viewer. Click a row and the detail panel opens while the viewer navigates to that asset's pin. Click a pin and the matching row highlights, scrolls into view, and opens the same panel. Filtering is one-directional: changing the Level inside the embedded SiteView filters the table to that Level, but the table does not drive the viewer.

Filters are embedded in the table column headers, on Name/Description, Status, Building, Level, Work Area, and Last Updated. The Status filter groups its options by the three stage groups defined on the Status Set. Filters combine with category browse and text search, and when nothing matches, the table shows "No assets found" with "Try adjusting your search or filter criteria."

Place Each Asset

Placing an asset gives it a coordinate, so it shows at its actual point in the viewer rather than at a representative point for its Work Area. You place an asset by clicking its position in the viewer. The article does not cover typing coordinate values or importing them, for the reason given in the flag below.

• Open the asset's detail panel and click Reposition (the crosshair icon in the panel header).
• A focus overlay fades the surrounding interface and a small panel appears over the viewer: "Click a point in the viewer to reposition this asset." with "Press ESC to cancel." below it.
• Click the asset's position in the 3D or the 2D viewer. In the 3D + 2D + Table layout, whichever viewer you click first commits the coordinate. From Table Only, the app switches to 3D + Table and gives you a navigate-then-Ready step first.

The click commits immediately — there is no separate confirm step — and the new coordinate appears in the Overview tab. ESC or closing the detail panel ends the placement without committing, and the previous coordinate is retained.

The asset model carries a coordinate only — there is no rotation field.

What Sits on the Asset Record

Clicking a row opens a slide-in detail panel with three tabs: Overview, Properties, and Attachments.

• Overview holds a thumbnail, Status, the Location group (Building, Level, Work Area, with their own Edit control), the Coordinate, and Status History. On an asset with no transitions yet, Status History reads "No status changes recorded yet."
• Properties holds the Form Template fields for that asset's category, under a FORM FIELDS heading. Unset fields show an em dash.
• Attachments takes photos and PDFs by drag and drop or Add File, with a stated limit of 100 MB per file.

Three details come up often:

• Status is always directly editable. It is not behind the Edit control that governs the Location group and the form fields.
• Status History records every transition per asset, with timestamp, user, and old and new value — the audit trail QA/QC customers ask for.
• Concurrent edits resolve last-write-wins. There is no lock and no conflict dialog in this release.
• Comments sit at the bottom of the panel and are available from every tab, on the web and in the mobile app.

For the full tour of the record — position, provenance, and condition — refer to the Asset Records article.

What AssetAtlas Does Not Do

Two boundaries, stated plainly.

• No observation linkage yet. Linking an observation to a specific asset is deferred to the SiteNote scope. Status History and comments are what exists today.
• No automation. Rules driven by observation status or asset condition are a separate future project.

Setup Checklist

Work through this on a demo project.

1. In Team Settings → Templates, confirm the Status Sets and Forms the categories will reference.
2. In Team Settings → Asset Categories, confirm an Asset Category Type with a category structure — or import one from CSV.
3. In the project, confirm the Site exists and add the Buildings, Levels, and Work Areas the assets will reference.
4. Confirm a SiteView capture and a Reference Plan exist for at least one Level.
5. Open Project → Apps → AssetAtlas and select the Asset Category Type.
6. Add one asset by hand to see the merged Building dropdown and the required fields.
7. Import a small CSV file and read the validation summary.
8. Reposition one asset in the viewer and watch the coordinate update in the panel.
9. Switch to 3D + 2D + Table, pick a SiteView, click a row, then click a pin.
10. Filter by Status, then clear the filter.
11. Export the selected rows to CSV and open the file.

At the end of this you have a placed registry on a demo project and have seen every surface a customer will ask about in a first session.