Optimizer
Optimizer © Larmia Control AB 2
Optimizer – Cont.
Optimizer helps you find deviations in the trend data and is a tool for creating
summary reports for e.g. energy usage. Reports are designed to find
deviations in the daily operation. Optimizer calculates grades for all the sub-
systems in the property so the operator easily can find the problem areas.
Optimizer complements the traditional SCADA software with a tool that
quickly finds errors that are normally hard and time consuming to find.
Examples:
- Are there any leaking valves?
- Are the time schedules correct for all the sub-systems?
- Is the energy consumption correct?
Optimizer © Larmia Control AB 3
Reports
Reports are designed to get a good overview on how, for example, an air
handlig unit it running and to find deviations within the report.
Values that deviate from its limits are displayed in red in the reports.
The reports are viewed in a standard web browser.
Optimizer © Larmia Control AB 4
Reports – Operational och energy reports
Operational reports display values and deviations for e.g.:
- Substations
- Heating groups
- Air handling units
- Chillers
Energy reports are used to monitor and present the water and energy
consumption in the property. Examples:
- Yearly reports with degree day correction
- Energy profile charts
- Charts for supervising the ideal values of the water and energy consumption
Optimizer © Larmia Control AB 5
Reports – Weekly and yearly reports
One way of structuring the reports is to create weekly reports that present
values on a day-to-day basis for the week, and yearly reports that present
values on a month-to-month basis.
This approach lets you see values for days, weeks, months and years.
Optimizer © Larmia Control AB 6
Reports – What is a deviation?
Deviations can be, for example:
- High runtimes
- Values that exceeds or deceeds a given limit
- Valve leakages
- High water or energy consumption
- A high number of control errors caused by a poorly adjusted regulator.
Optimizer © Larmia Control AB 7
Reports – Suggested actions
Suggested actions can be included in the report to help the maintenance staff
to attend to the error which caused the deviation.
The maintenance staff can gradually add their own suggested actions.
Optimizer © Larmia Control AB 8
Reports – Charts
The reports can also contain charts, such as:
- Bar charts
- Pie charts
- Trend curves
- Energy profile charts
Optimizer © Larmia Control AB 9
Report example 1
This is a weekly report for an air
handling unit.
This report checks, among other
things:
- That the runtime for the unit is correct.
- That the regulation is correct.
- That the pumps are run at the right time
In this example there is a runtime
deviation (marked red). The
deviation is the result of an
incorrect setting in the time
schedule made by an operator.
Optimizer © Larmia Control AB 10
Report example 2
This is a weekly report for a
heating system.
This report checks, among other
things :
- That the regulation is correct by
calculating the temperature deviation
between the actual value and the
setpoint. It also checks the stability of the
regulation by monitoring the standard
deviation and the number of control
errors.
- That the return temperature in the
system isn’t to high.
- That the valve doesn’t leak.
In this example there is a valve
leakage which also caused a high
return temperature.
Optimizer © Larmia Control AB 11
Report example 3
This energy report monitors that
the plant doesn’t consume more
energy than its given ideal values.
The values in the report are from
an office building where the
ventilation is programmed to run
between 05:00 and 18:00. Because
there are different activities in the
building during ”Operation”
(weekdays) and ”No operation”
(nights and weekends) there is a
report for each operational case.
The report is split into four parts:
building electricity, heating,
cooling and hot water.
Optimizer © Larmia Control AB 12
Report example 3 – Cont.
The consumption of building
electricity can be monitored by
dividing the consumption during
operation by the runtime. The
result is the mean effect for this
operational case, which in this case
is constant over the year.
The heating consumption is
monitored by dividing the
consumption by the runtime and
the degrees needed to heat the
outdoor air. The result is the
specific effect (kW/°C). This value
corresponds to the tangent/slope of
the curve in an energy profile chart
(see Report example 4).
Optimizer © Larmia Control AB 13
Report example 3 – Cont.
The cooling consumption is
monitored using the same methods
as the heating.
The hot water consumption is
monitored by dividing the
consumption during operation by
the runtime. The result is the mean
effect for this operational case.
Optimizer © Larmia Control AB 14
Report example 3 – Cont.
These ideal values can be
calculated.
Although it is usually simpler to:
- Check the present consumption
- Use limits to assert that the consumtion
doesn’t increase
- Lower the limits once the saving
measures has been performed.
Optimizer © Larmia Control AB 15
Report example 4
This chart shows the energy profile
for the heating consumption (the
heating consumption in relation to
the outdoor temperature).
It is also possible to add, for
example, the runtime of an air
handling unit as a parameter to the
chart to further explain deviating
points.
Select a point to see the
consumption, temperature and
runtime for a specific date.
Optimizer © Larmia Control AB 16
Report tree
Navigate the reports using a tree
view with flexible configuration
options.
The report tree contains the
following functions:
- Find a specific report.
- Modify constants, such as runtime limits
and costs, plus all the limits for the
available report checks.
- Re-calculate a report after modifying its
limits.
Optimizer © Larmia Control AB 17
Report tree - Deviations
The report tree also shows if
reports have deviations, and also
the number of deviations.
Optimizer © Larmia Control AB 18
Report tree - Grades
The report tree provides a quick
and easy overview of where the
problems are by color coding each
system by its grade. The color
ranges from green to yellow to red,
where red is a low grade (grade 1)
and green is a high grade (grade
5).
The grade is based on the number
of deviations the system has
registered in its reports for the last
seven days (this time is
adjustable).
Optimizer © Larmia Control AB 19
Grade presentation
Grades for all the sub-systems are
easily accessible via a text file, for
easy presentation in a SCADA
software.
Every report can be opened from
other softwares using its specific
link.
Optimizer © Larmia Control AB 20
The Optimizer Configuration tool
This software is used to define the
overall system structure and to
configure reports and charts.
It is also possible to create
functions, e.g. efficiency
calculations and runtime
calculations.
The programming language
contains regular arithmetic
expressions, logical operators and
several built-in functions.
Optimizer © Larmia Control AB 21
The Optimizer Configuration tool - Reports
The reports are created in an
Excel-like environment.
It contains, among other things,
functions for calculation of:
- Mean values
- Consumption
- Degree day corrections
- Runtime calculations
Optimizer © Larmia Control AB 22
The Optimizer Configuration tool - Templates
A created report can be saved as a
template.
All reports that are created using
this template are automatically
linked to the template, and all
changes to the template are
automatically reflected into all
linked reports.
Optimizer © Larmia Control AB 23
The Optimizer Configuration tool – Standard systems
It is also possible to save an entire
system as a standard system.
A system can, for example, be an
air handling unit.
A system consists of a number of
inputs (trend data), constants,
functions and several reports.
If you have many similar systems
you can speed up the configuration
by using standard systems.
Optimizer © Larmia Control AB 24
Trend database
We use the MySQL database for trend data storage.
The database has a table which contains all the points in the system.
For every point there is a description, unit etc.
Every point stores its trend data in its own table.