---
title: "IMS 3D Upload Requirements"
slug: "ims-3d-upload-requirements"
tags: ["3D"]
updated: 2026-10-27T23:11:38Z
published: 2026-10-27T23:11:38Z
canonical: "ims-handbook.cenosco.com/ims-3d-upload-requirements"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://ims-handbook.cenosco.com/llms.txt
> Use this file to discover all available pages before exploring further.

# IMS 3D Upload Requirements

3D models can be uploaded via [Settings](/v414/docs/uploading-3d-models).

This document describes what information needs to be supplied to enable a 3D Model upload:

- Alignment data
- 3D Model in correct format
- 2D Site map in correct format
- Tagged Flocs

## Alignment Data

For the onshore sites, the following data is required for model alignment:

| What is needed | Description |
| --- | --- |
| Reference point | A point in the 3D model (x, y, z), together with GPS coordinates (longitude, latitude, altitude). The reference point should be as close as possible to the center of the site. |
| Angle | An angle between the y-axis in the 3D model and the real North. |

## 3D Model Required Format

IMS is able to natively import NavisWorks (NWD) format files 3D models. To import 3D Models created in other software, it is necessary to import them into NavisWorks and save them in NWD format.

> [!NOTE]
> **3D Model Limitations**
> 
> In general, the fewer objects in a 3D model that are rendered, the faster the rendering process will be. Loading a large number of objects can cause stuttering in the display, slow performance, and can even exceed browser RAM usage limits, causing crashes and instability.
> 
> To avoid these issues, large 3D Models should be divided into multiple smaller model areas, with each model area containing at most 25,000 objects.

## 2D Site Map Required Format

The 2D site map can be either in “DWG" or “NWD” format.

## FLOC Tagging

There are two ways for tagging FLOCs:

- Special properties, or
- Node names.

### Tagging with Special Properties

The model Node should have a special property that corresponds to the FLOC name.

### Tagged with Node Names (less accurate)

Tagging using Node Names is less accurate than tagging using Special Properties.

When tagging with Node names, the following are required:

- The Node should contain sub-Nodes that define the FLOC, and
- The Node’s name should contain the IMS FLOC name (e.g., "N012-CR6-R3010").