Manage Asset Inventory (Client/Server)

Optionally you may want to create a new separated database to use for a specific data production project.
If you do so, establish the EOS database connection to the newly created database via EOS Console > Resources > Database Connection.

Optionally you may want to add available GIS resources for this project.
Add the required resources via EOS Console > Resources > Datasets.

Create a new workspace or copy an existing workspace and add the necessary extensions, resources and define the accessibility.
EOS Console > User and Permissions > Workspace

Start the Orbit Client with administrator permissions on the inventory extensions and create the required themes.
Be careful to create these new themes in the required database and workspace (last step of the procedure).
Orbit Client > Procedures > Administration > Asset Inventory > Create New Theme

Restrictions for operators can be set via EOS console > Users and Permissions.
Enjoy data production from Mobile Mapping in Orbit.

Any server side available database connection can be used as inventory database. No restrictions nor conditions.
Define the database connections in the EOS console > Resources > Databases.

Datasets available for asset inventory are named as “Themes”. Only a well defined list of datasets can be used by the asset inventory add, edit and remove item procedures. These conditions are met automatically when using the asset inventory administration procedure “Create new theme”.
If you are building your inventory database manually, take these conditions into account :

• Required dataset attributes :
  OG_ObBJ_ID (integer), AIM_CREATE_DATE_TIME (string), AIM_CREATE_USER (string), AIM_LAST_MOD_DATE_TIME (string), AIM_LAST_MOD_USER (string), AIM_REF_ID (string), AIM_ANNOTATION (string)
• Themes.xml
  Configure the dataset as inventory theme by adding its internal EOS registry name into the themes.xml configuration file :
  <Orbit installation directory>/server/data/datasets/inventories/themes.xml
  <THEME><DATASET>registry name of the theme</DATASET></THEME>
• Adding attributes to theme:
  To add an attribute to an inventory theme in Orbit, open the database management tool (Navicat, Toad,..) and go the table design > add field. Any added field will appear inside the attribute tabel in Orbit. To define specific descriptions for the attributes in Orbit, you need to update the Orbit Resource Descriptor of the theme.
• Editing the legend of a theme:
  Open the inventory theme locally in Orbit and open Dataset Legend Editor to edit the legend.
  The legend editor is only available for local resources. Read Local vs EOS resources.
  To import the inventory theme locally, drag and drop the Orbit DataBase File inside Orbit Client:
  • The file location: <Orbit installation directory>/server/data/datasets/inventories
  • The Database connection in the Orbit Client

While adding inventory items, Orbit automatically creates and stores a snapshot of all opened mobile mapping views. When using the “Add inventory item” procedure it is also possible to add and manage snapshots and documents.

These files are stored by the Orbit client in an open file structure, organized by theme and object id.
The default configuration is : <Orbit installation directory>/client/data/inventories/<theme>/<object id>/

The spatial information of snapshots and the link of snapshots and documents with the inventory object is saved in a separated database table.
Up to Orbit version 10.5 all inventory themes used the same “link_photos” and “link_documents” table. From version 11.0 each theme has its own link tables : “<theme>_link_photos” and “<theme>_link_documents”.
The default configuration stores these link tables within the same database connection of the inventory theme. If required it is possible to use one central database for all link_photos and link_documents tables. However each inventory theme will have its own link tables within this central database connection. This is required to guarantee database performance on doing inventory on large scale.

Default configurations can be adjusted via the service configuration file. Changing any service properties requires an Orbit service restart.
<Orbit installation directory>/server/program/services/ext_inventory_suite/properties.ini

On doing asset inventory on large scale (+ 100,000 objects for one theme) the snapshot table will become very large. Indexing the fields “Name”, “Obj_id” and “Theme” is advised when an inventory insert takes increasingly more time.

The roles on extensions are managed in the EOS Console.
When opening a workspace in the Orbit Client the extension roles for user and workspace will be loaded.

Administrator
With this role, Asset Inventory themes can be created, imported, exported and removed.
Access to procedures Administration > Asset Inventory and Asset Inventory. Also Access to the Asset Inventory Search Tab.

Operator
With this roles, Inventory items can be added, edited or removed.
Access to procedures for Asset Inventory. Also Access to the Asset Inventory Search Tab.

User
With this roles, Inventory items can be consulted.
Access to Asset Inventory Search Tab.

A newly created inventory theme is be by default a 3D dataset. All objects will be saved with X,Y and Z.
If required it is possible to set the theme to a 2D dataset :

Edit and adjust the coordinate model tag in the appropriated .odb file from “3D” to “2D” using a text editor.
<Orbit Installation>/server/data/datasets/inventories/<inventory database>/<theme>.odb

Only possible for point datasets.
Existing 3D points can be converted into 2D objects by updating their Z values using a database query :

Update <table_name>
Set OG_COORD_Z = 0

Unload the EOS dataset to take advantage of the updated dataset structure : Resources > Datasets > Dataset Setup