Differences

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

--- hydraulic_usage:hydraulic_usage [2023/05/04 09:27] – su
+++ hydraulic_usage:hydraulic_usage [2023/05/04 11:19] (current) – [Hydraulic Usage Overview Page] su
@@ Line 5: / Line 5: @@
 [[https://appstore.intelligentplant.com/Home/AppProfile?appId=6e7f863503fe4984aca1d55006b9709e|Try out the Hydraulic Usage app on the Industrial App Store]]
-====Page Descriptions====
+----
-===Hydraulic Usage Overview Page===
+=====Page Descriptions=====
+====Hydraulic Usage Overview Page====
 {{:hydraulic_usage:hydraulicusage-overview.png?900|}}
-//Figure 1. Overview section of Hydraulic Usage//
-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|}}
-//Figure 2. Fluid Usage banner//
 At the top of the page, there is a green banner that provides key details on the total fluid usage calculated for reservoir level, pump run times, and valve movements since the last reset. Using these totals, a per day average is calculated for each calculation method. This total can be reset by clicking the minus icon on the right of the banner.
-===Reservoir Levels===
+====Reservoir Levels====
 {{:hydraulic_usage:hydraulicusage-reservoir_levels.png?900|}}
-//Figure 3. Reservoir Level graph//
-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.
 {{:hydraulic_usage:hydraulicusage-fluidusage.png?900|}}
-//Figure 4. Fluid Usage graph//
 The fluid Usage graph displays historical fluid usage based on each of the three calculations. In the above image, only reservoir level and pump running time are shown.
-===Pump Run Times===
+====Pump Run Times====
 Pump Run Times utilises details on pumps that have been configured on the app. This calculation takes nominal flow rates of the pumps and calculates the total amount of fluid that has passed through the pump based on running time. This calculation can also be performed without a known running time, as long as data such as an On/Off pump switch is available, the calculation can be carried out.
 {{:hydraulic_usage:hydraulicusage-pumps.png?900|}}
-//Figure 5. Pump Runs//
 Pumps will be displayed as shown on the above figure and show their nominal flow and run count for each. The user has the option of selecting only low or high pressure pumps.
 {{:hydraulic_usage:hydraulicusage-pumpfluidusage.png?900|}}
-//Figure 6. Pump Fluid Usage graph//
 Fluid usage for each pump is then shown on the Pump Fluid Usage graph
 {{:hydraulic_usage:hydraulicusage-pumpruns.png?900|}}
-//Figure 7. Pump Runs graph//
 Pump Runs graph shows when a pump run has occurred within the set time period; A value of 0 on the Y axis indicates pump was not active, and a value of 1 indicates that the pump was active.
 {{:hydraulic_usage:hydraulicusage-timebetweenruns.png?900|}}
-//Figure 8. Time Between Runs graph//
 Finally, Time Between Runs shows the On to On time for the pumps. In the above figure, it can be seen that time between runs for LP Pump A and LP Pump B decreased, therefore telling us that their activity has increased.
-===Valve Movement===
+====Valve Movement====
 The Valve Movement calculation uses valve status tags which show when the valves are moving, along with valve swept volume to determine fluid usage. This is the most accurate of the three calculations as valve actuation will require specific amounts of hydraulic fluid to operate, thus less noise is associated with this method.
-====How to configure an asset====
+----
-Firstly, click the button “Create an Asset” [show image]. This gives the user a blank asset in which they can configure. To configure, select “Go to Configure”. This will take you to an Asset Settings page that contains four tabs:
+=====How to configure an asset=====
-General - Enter a name for the new asset and select the Process Data Historian which is where the output values will be written to.
+Firstly, select "Add New" on the left menu
-Permission - Allow or revoke permission for users to interact with the asset.
-Structure - This is the main section of configuration where the hierarchy and details of components is set.
-Background Processing - Mainly to be used by developers, this tab provides information about whether the calculation for hydraulic usage has succeeded or failed.
-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-addnew.png?200|}}.
+This gives the user a blank asset in which they can configure.
+{{:hydraulic_usage:hydraulicusage-createanewasset.png?400|}}
+=====Asset Settings=====
+For further asset configuration, select "Asset Settings" at the top right of your page. This will take you to the Asset Settings page that contains four tabs:
+====General====
+Enter a name for the new asset and select the Process Data Historian which is where the output values will be written to.
+{{:hydraulic_usage:hydraulicusage-generalassetsettings.png?600|}}
+====Permission====
+Allow or revoke permission for users to interact with the asset.
+{{:hydraulic_usage:hydraulicusage-permissionsassetsettings.png?600|}}
+====Structure====
+This is the main section of configuration where the hierarchy and details of components is set.
+{{:hydraulic_usage:hydraulicusage-structureassetsettings.png?600|}}
+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|}}
-//Figure 9. Component Hierarchy//
+**Hydraulic Power Units**
 Upon clicking the tab, the user will see the base hierarchical component - the hydraulic power unit. This requires the following data:
-Supply reservoir capacity (litres)
+  * Supply reservoir capacity (litres)
-Return reservoir capacity (litres)
+  * Return reservoir capacity (litres)
-Reservoir level unit (% or litres)
+  * Reservoir level unit (% or litres)
-Supply and return reservoir level tags.
+  * 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).
 Wells can have many valves associated with them. Adding valves will require the following data:
-Function type
+  * Function type
-Status tag
+  * Status tag
-Pressure tag
+  * Pressure tag
-Subsea Control Module (optional)
+  * Subsea Control Module (optional)
-Associated well
+  * Associated well
 Finally, pumps can be added to the hierarchy. They require the following data:
-Function
+  * Function
-Nominal flow (litres/min)
+  * Nominal flow (litres/min)
-Running time tag
+  * Running time tag
-Service tag
+  * Service tag
-Status tag
+  * Status tag
-Pressure tag
+  * Pressure tag
-Output tags
+====Admin====
+Mainly to be used by developers, this tab provides information about whether the calculation for hydraulic usage has succeeded or failed.
+{{:hydraulic_usage:hydraulicusage-adminassetsettings.png?600|}}
+====Output tags====
 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.