How is the data structure?
Vision presents all your groups (or locations) and assets (or equipments) contained into your domain. The machines are positioned in a linear hierarchical structure - ie: database, group, sub groups ... and asset.
1 database contains 1 or more assets or groups. 1 group can contain 1 or more assets or sub groups. there is no level limitation in the tree structure.
Vision and NESTi4 presents the same data but not with the same presentation. NESTi4 is expert oriented (configuration, analysis, report) and Vision is supervision oriented. Both applications share the same technical databases and are fully synchronized:
all existing groups and assets defined into NESTi4 databases with exactly the same data hierarchy
all changes applied by users into NESTi4 are automatically displayed into Vision
all changes applied by users into Vision are automatically displayed into NESTi4.
How to manage groups and assets (or location) ?
Only autorized users can open "asset group & inbox" module to manage all his groups and assets:
Groups (or locations) can be created, renamed or removed
Assets (or equipments) can be removed only
IMPORTANT:
when user remove a group, then this group and its content are deleted from the database
data are physically deleted when user clicks on SAVE button
WARNING: All removed assets and/or locations are definitively deleted from database.
What is the Inbox? only for machine monitored with RT300 apps ...
RT300 apps - ie: Machine Defender, Shaft alignment apps - can be used to create a new machine, do first measurements and edit corresponding report. User can decide to use apps in standalone mode or to send data into NESTi4 server - see How to send a new machine from RT300 into NESTi4?
By default, all new sent machines from apps with first measurements and report are presented into the user inbox in Vision:
According to the user role (privilege), inbox presents the list of new received machines from Machine defender or Shaft alignment apps. These machines are grouped by creator username and ready to be drag & drop into an existing group or asset.
Each machine presents a name and an (operating type) - example: TestMachine173152 (Alignment)
How to assign a new machine from the Inbox into a group? only for machine monitored with RT300 apps ...
In order to consult details informations about new assets coming from RT300 apps, this machine can be assigned or merged from the inbox into an existing group or asset:
Assignation
Drag & drop a new machine from the inbox into an existing group (or location) in order to add this machine into the group
When a new asset has been assigned to a group, this asset is presented with a [+] into the asset list. One or more new assets can be assigned successively before to SAVE and see these new asset into the enterprise structure.
See below an example:
Merge
Drag & drop a new machine from the inbox into an existing asset (or equipment) in order to add new measurements to the existing machine history - ex: add alignment measurements to a machine with only vibration data.
When a new asset has been merged with an existing one, it is presented with a [+] into the asset list. One or more new assets can be assigned successively before to SAVE and see these new asset into the enterprise structure.
Example: a new alignment machine (inbox) is assigned to an existing machine with some vibration measurements
When you click on SAVE button, the new merged equipment keep the name of the existing machine and measurements of the new machine are added into the existing machine:
IMPORTANT: Merge rules
a new vibration asset can not be merged with an existing vibration asset
a new vibration asset can be merged with an existing alignment asset
a new vibration asset can not be merged with an existing vibration-alignment asset
a new alignment asset can be merged with an existing vibration asset
a new alignment asset can not be merged with an existing alignment asset
a new alignment asset can not be merged with an existing vibration-alignment asset