azimuth:setting_up_azimuth
Differences
This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
azimuth:setting_up_azimuth [2018/05/09 14:05] – created su | azimuth:setting_up_azimuth [2018/05/11 07:43] (current) – su | ||
---|---|---|---|
Line 2: | Line 2: | ||
==== Intelligent Plant Azimuth ==== | ==== Intelligent Plant Azimuth ==== | ||
+ | |||
+ | |||
+ | === Ensure: === | ||
+ | *efficient maintenance scheduling on major pieces of rotating equipment. | ||
+ | *reliability | ||
+ | *downtime tracking (planned/ | ||
+ | |||
+ | ---- | ||
+ | |||
+ | |||
+ | ==== Prerequisites ==== | ||
+ | |||
+ | * **Alarm Analysis** (//type//) data source. Source data source, will be used to define equipment events. Azimuth will use these event definitions to monitor equipment. | ||
+ | * **Edge Historian** data source. Target data source, Azimuth will use this datasource to store analysis results. | ||
+ | |||
+ | ---- | ||
+ | |||
+ | |||
+ | ==== Getting started ==== | ||
+ | |||
+ | Azimuth uses asset and equipment hierarchical structure. One or more pieces of equipment can be defined on an asset. For example: | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | - Adding an asset (subscription) | ||
+ | - Adding equipment | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | ---- | ||
+ | |||
+ | ==== Known issues ==== | ||
+ | * Creating a piece of equipment with a duplicate name on the same target datasource will cause to override previous equipment totaliser tag data. | ||
+ | |||
azimuth/setting_up_azimuth.1525874724.txt.gz · Last modified: 2018/05/09 14:05 by su