Enginero User Guide

Terms and Definitions

Description

Site

Site is the entire company/organization which manages the Enginero application.

Hub

A part of the company/organization that operates as a separate unit which can be either based on geographic location or profit center.

Project

A project in Enginero is an aggregation of 3D models, 2D drawings, Assets, Documents and more Information etc. related to a single construction project. It acts as a package for users to collaboratively work to meet specific objectives.

Teams

Teams is a virtual partition of a project where a user can be added to a “Team” where they can access specific sections dedicated to that team 

Business Unit 

Business units acts as tags to add labels while in project creation and categorize projects across the hubs 

BIM

Building Information Modeling (BIM) is a digital representation of physical and functional characteristics of a facility.

Files

Project Data Management will enable the project team to store, maintain and control all information pertaining to the project. Documents, Drawings, Models and Assets are collectively termed as Files.

Model Coordination

Model Coordination, as functionality of Coordination Sets to manage, publish, and detect clashes between selected models related to the project in Enginero

Permissions

The ability to do actions in Enginero (including viewing content, editing content, and changing configuration) is governed by permissions. Each permission has a name and covers one action or a small subset of actions. A user must be granted a permission to perform actions

Roles

A role can be defined as a set of permissions that determines a user access to the modules within Enginero

Assets

Assets can be termed as reusable and quantifiable item which is used in a project. E.g. Furniture, equipment, etc.

Asset Libraries

Asset libraries are virtual grouping of similar assets to efficiently manage assets derived from various sources. A single asset can belong to multiple libraries.

Breadcrumbs

Breadcrumbs can be termed as a navigation panel that allows users to keep track of the current location within the application.

RFI

RFI stands for Request for Information. It is commonly used to obtain more information where there is less information provided

Issues

Issue can be defined as problem that has been encountered in executing project activities.

Clashes

Clashes are like issues but run between models or views to find out if any criteria is out of the match defined. Users can view the clashes published from Navisworks as well as the Enginero Clash Engine.

Type

Types and Sub-types are created to segregate the Project/Issues/Document/RFI based on custom-defined terms to effectively categorize them. Each type can have a workflow associated with it.

Status

Status represents the state of an Issue/RFI/Document/Clash at a specific point in the workflow. It is an indicator of where a particular Issue/RFI/Document/Clash stands in its process of resolution.

Board View

A Board view represents the state of an Issue/RFI at a specific point in the workflow. It is an indicator of where a particular Issue/RFI stands in its process of resolution

Enginero Category

Classify the elements in models based on applied ruler condition within the Hub 

BOQ Template

Create a Global Template for the Properties by setting unique Rules and Conditions

Workflows

A workflow is an automated process in which a series of sequential tasks are carried out from beginning to the end to execute a business process based on user-defined rules or conditions.

Reports

Reports are used to export all the BOQ, RFI, Clashes, and issues information as PDF, CSV and BCF format