Differences

This shows you the differences between two versions of the page.

--- hydraulic_usage:hydraulic_usage [2023/05/04 10:29] – su
+++ hydraulic_usage:hydraulic_usage [2023/05/04 11:19] (current) – [Hydraulic Usage Overview Page] su
@@ Line 4: / Line 4: @@
 [[https://appstore.intelligentplant.com/Home/AppProfile?appId=6e7f863503fe4984aca1d55006b9709e|Try out the Hydraulic Usage app on the Industrial App Store]]
+----
 =====Page Descriptions=====
@@ Line 10: / Line 12: @@
 {{:hydraulic_usage:hydraulicusage-overview.png?900|}}
-The Overview section of Hydraulic Usage provides results on the three different calculations available within the app; Reservoir Levels, Pump Run Times, and Valve Movement. These are all used to determine fluid usage within a set time. If configuration has been done correctly, it is likely that Valve Movement values will be the most accurate. However, if data is not available on these, then the previous two calculations can be used for results.
+The Overview section of Hydraulic Usage provides results on the three different calculations available within the app; Reservoir Levels, Pump Run Times, and Valve Movement. These are all used to determine fluid usage within a set time. If configuration has been done correctly, Valve Movement values will provide the most accurate results. However, if the required data for Valve Movement is unavailable, then the previous two calculations can still be used for similar results.
 {{:hydraulic_usage:hydraulicusage-statusbanner.png?900|}}
@@ Line 18: / Line 21: @@
 {{:hydraulic_usage:hydraulicusage-reservoir_levels.png?900|}}
-Reservoir Levels utilises data from the reservoir to calculate fluid usage. It shows the historical levels of the hydraulic usage power unit’s supply and return reservoirs. It contains logic to remove noise caused by external sources such as swaying from wave and tidal movements, and reservoir refilling.
+Reservoir Levels utilises data from the reservoir to calculate fluid usage. It shows the historical levels of the Hydraulic Power Unit (HPU) supply and return reservoirs. It contains logic to remove noise caused by external sources such as swaying from wave and tidal movements, and reservoir refilling.
 Overall usage is shown for the current day, the last 3 days, along with an average usage per day, and the estimated days remaining at current levels.
@@ Line 74: / Line 77: @@
 The Structure section is where the majority of the configuration will occur. The hierarchy of the components will follow the following structure:
 {{:hydraulic_usage:hydraulicusage-hierarchy.png?600|}}
+**Hydraulic Power Units**
 Upon clicking the tab, the user will see the base hierarchical component - the hydraulic power unit. This requires the following data:
@@ Line 81: / Line 86: @@
   * Supply and return reservoir level tags.
-The next step is the configuration of HP and LP hydraulic systems. These require only a name and abbreviation.
+**NB:The minimum requirements for the Hydraulic Usage App to function are the above HPU Levels.**
-Third stage is the configuration of fields. These are just names and are used exclusively for grouping of components.
+**Hydraulic Systems**
+The second stage of configuration is of the HP and LP hydraulic systems. These require only a name and abbreviation.
+**Fields**
+The final stage of configuration are the fields. These only require names and are used exclusively for grouping of components.
 Within the field level, wells can be defined. Wells require a name and water depth (metres).
@@ Line 102: / Line 113: @@
   * Pressure tag
-**The minimum requirements for the structure are the HPU Levels.**
 ====Admin====
 Mainly to be used by developers, this tab provides information about whether the calculation for hydraulic usage has succeeded or failed.
@@ Line 111: / Line 122: @@
 The following output tags are supplied from the Hydraulic Usage app:
-Cumulative Usage Tags:
-HydraulicUsage/{Asset}/FluidUsage/ReservoirLevel
+**Cumulative Usage Tags:**
-HydraulicUsage/{Asset}/FluidUsage/PumpRunningTime
+  * HydraulicUsage/{Asset}/FluidUsage/ReservoirLevel
-HydraulicUsage/{Asset}/FluidUsage/ValveMovements
+  * HydraulicUsage/{Asset}/FluidUsage/PumpRunningTime
+  * HydraulicUsage/{Asset}/FluidUsage/ValveMovements
-Leakage Tags:
+**Leakage Tags:**
-HydraulicUsage/{Asset}/Leak/ReservoirLevel
+  * HydraulicUsage/{Asset}/Leak/ReservoirLevel
-HydraulicUsage/{Asset}/Leak/PumpRunningTime
+  * HydraulicUsage/{Asset}/Leak/PumpRunningTime
-Sensor Offsets (one generated per sensor):
+**Sensor Offsets (one generated per sensor):**
-HydraulicUsage/{Asset}{Field}/{WellId}/{System}/{SensorName}.SensorOffsetAverage
+  * HydraulicUsage/{Asset}{Field}/{WellId}/{System}/{SensorName}.SensorOffsetAverage
 The tags associated with cumulative usage and leakage are the standard five tags, sensor tags are dependent on the amount of configuration added to the app. For every sensor configured, a sensor tag will be created. Therefore, the number of output tags could increase substantially.