Project Settings

One of the first tasks to do when creating a project on Twinview is to set and configure your project specific settings.

You can amend your projects settings and information at any time in the Project Settings.

Options may vary depending on your package and your role/permissions on the project.

General Settings

In General Settings, you can change your project name, description, preview image or location. However, these settings should be repopulated as part of your onboarding process.

The beacon UUID field can be populated with your chosen bluetooth beacon UUID (iBeacon or Eddystone) that you have created for your project. All beacons on your project should be configured with this project UUID. If you are not utilising beacons on your project this can be left blank

Model Exports

Here, you can export your project data to the industry standard (BS1192:4) COBie format, or export your IOT data to a JSON object for use in 3rd party applications.

To generate a new COBie, click ‘Export Cobie’. Depending upon model size and data, this may take a few minutes. Once generated, you can download the COBie file by clicking download. You can also download previously generated files as these are kept on the system.

To export your IOT data, click 'Export IOT Data'. Depending upon model size and data, this may take a few minutes. Once generated, you can download the JSON file by clicking download. You can also download previously generated files as these are

kept on the system.

Rooms and Spaces

The Room dialogue vault has recently been updated to include the new room zoning feature realeased in V1.20. This documentation and screenshots have not yet been updated to reflect these updates.

Here you can add, and manage your rooms and spaces. Rooms are automatically extracted from your 3D model if the model format used supports Rooms. Here you can see, edit and manage rooms and the features which are associated to rooms such as beacons.

It is important to understand the relationship rooms have with other building elements such as levels and assets.

• Assets are associated with a Room/Space

• Rooms are associated to a level

• Levels are associated to a building

Rooms can also have their own dashboards, to display data about themselves and the items in them.

To Edit a Room, click the 'View' button, which will then open up the room details modal. Here you can see the rooms data and tabs for the dashboard. To edit a room, click the 'edit' button on the top right of the room data panel.

You can then edit the data in the room as well as define its Level association.

To view the Room/Space dashboard, click view to show the room/space data, then click the 'Dashboard' tab. This will show the room/space's dashboard which you can configure like any other dashboard (see Dashboards).

The 'Beacons' button opens up the beacons page, where you can view, edit and configure the bluetooth beacons on your project. See 'Bluetooth Beacons' section for more information.

Categories

If your project has ‘Twinview Manage’ enabled, you can define your default categories for assets, tickets, issues, maintenance jobs.

and tasks. These should be pre-populated and setup as part of your project’s onboarding.

Templates

If your project has ‘Twinview Manage’ enabled, the templates section is where you can add your default templates for maintenance jobs and tasks. This is a useful way to create standardised maintenance jobs or activities, that will save you time for common jobs or tasks you do often.

See Creating a Task template or Creating a Maintenance Job Template for more information.

Ticket Templates (custom fields)

One the the template types is Ticket Templates. This allows you to define any additional custom fields above and beyond the standard ones that you may want to collect when a ticket is raised.

When you add a field you can define it is mandatory or optional when a ticket is raised. These fields are added to the create ticket dialogue modal when a user raises a ticket, whether that vai the website, the app or via the API.

This field are shown in the ticket detail summary and are exposed to the API like normal Ticket fields.

This is useful if you have a 3rd party ticketing system where the mimimum data between it and twinview do not align. This means data fields between the two sepearte applications can now match withoiut any custom mapping or dats transforms been applied in node assistant.

Model Parameters

The model parameters tab is where you can define which additional paramiters you want to show on the asset detail page. This is useful if the assets have their own specific or custom data which you want to show on the asset detail page.

See showing custom asset data on the asset detail page for more information.

Query Sets

Query Sets is where you can build your custom search sets in Twinview. The query builder allows you to search for and group assets using their data. This is useful for various Twinview functionality, such as assigning a document to multiple assets or for classifying assets for capturing data in the Twinview Capture module.

See 'How to Create and manage Query Sets' for more information.

QR Codes

This is where you can generate QR codes for assigning to assets. You can also see any QR codes that have been assigned to an asset.

For more information on QR Codes see QR Codes in Twinview for more information.

Device Groups

Here you can create, view and edit you IOT device groups. Device groups are a way to group IOT devices, and assign permissions based on the device groups. Here you can see your defined device groups.

Depending on permissions you this tab may not be available or the functionality restricted to read only.