Tender text

Copy long version

Building automation, system requirements

1. Scope and structure

The building automation is to be supplied as one continuous system
consisting of automation station, engineering software and operating
interface. Logic, visualisation and data points are to be kept in a single
project. The same project is executed by the automation station and
displayed by the operating interface; a change is made in one place only
and applies to logic and operation at the same time. Separate projects for
automation and visualisation whose data points have to be reconciled are
not permitted.

2. Operational safety and independence

All control and closed-loop functions run in the automation station. The
installation must remain fully operable without an internet connection,
without a cloud service and without a running connection to the operating
interface; switching times, scenes, presence states and control functions
continue to work while the operating interface is closed. The automation
station supervises its own program execution and restarts by itself if it
is blocked.

Settings such as setpoints, positions and meter readings are to be stored
permanently and resumed after a power failure or a restart. Before a
changed project is loaded, the existing state is to be saved
automatically; at least the last ten states must be held on the device and
must be restorable separately for project and settings.

3. Engineering

Engineering is carried out with one single software for logic,
visualisation and data point administration. Required:
- Import of the KNX group addresses from the ETS project with data type
- Checking tools for invalid links, outputs written from several places
  and control elements that are not linked
- Search across the whole project, including parameter values
- Transfer of a program state into the working memory for trial operation,
  separate from permanent storage
- The number of operating pages, images and control elements is not
  limited; free layout without mandatory templates, portrait and landscape
  in parallel

4. Operation

The operating interface is to be provided for Android, iOS/iPadOS and
Windows from the same project and in several languages. Permissions, page
assignment and an individual start page are to be set up per user.
Continuous operation on a wall panel must be possible.

5. Interfaces

At least KNX, Modbus, MQTT and Matter are to be connected, without
additional protocol converters. Every value is a data point of the same
project and is therefore equally available to logic, visualisation and
recording.

6. Diagnostics and proof

The traffic of all connected bus systems is to be shown in one common
view and filtered per bus system. Measured values are to be recorded in
the automation station and output as a chart and as a text file.

7. Remote access and data protection

Remote access is to be implemented without port forwarding at the router;
the automation station establishes the connection itself. The servers
involved are located in the European Union only. Project data, measured
values and recordings must not be stored on those servers. Remote access
must be switchable off at the device and lockable through a data point of
the installation.

8. Handover

To be handed over: the complete project file, the data point list and the
access data. The client must be able to change the installation with the
engineering software; tying the client to the installer through sealed
project data is not permitted.

Make and type: uni-PRO or equivalent
Make and type offered: ..........................................

Copy long version

Automation station, DIN rail device, up to 4000 data points

Supply, mount, connect and commission an automation station for building
automation as a DIN rail device for mounting rail TS 35.

1. Mechanical and electrical design

- Modular rail system 45 mm, dimensions about 70 x 90 x 58 mm
- Supply 24 V DC (+15 % / -5 %), current draw about 200 mA; the supply is
  tendered separately
- Push-in terminals for conductors up to 1.5 mm²
- Ambient temperature -10 to +50 °C, protection class IP20
- Processor with four cores up to 1.2 GHz, working memory at least 512 MB
- Real-time clock with battery, so that switching times work correctly
  after a longer power failure even without a network
- Reset button on the device that restores the factory settings
- Status indicator whose flashing pattern shows the state of the program
  execution and of the remote access on site

2. Onboard interfaces

- Ethernet
- USB for data backup and for additional serial adapters
- RS485 with a termination resistor that can be switched on at the device
- RS232
- KNX TP for direct connection to the bus line

3. Function

The automation station executes the building automation project on its
own. Logic, visualisation and data points are held in one project; the
operating interface accesses the same data points. The data point capacity
is up to 4000 addresses.

The program is loaded from a permanently stored start project and resumed
automatically after every power failure. Setpoints, positions, meter
readings and operating hours are stored permanently and continued after
start-up. Before a changed project is loaded, the automation station saves
the existing state by itself and holds at least the last ten states;
project and settings must be restorable separately.

Program execution is supervised inside the device. If a part of the
program is blocked, the automation station restarts by itself.

4. Web interface

Without the engineering software, the following must be adjustable and
readable through a web browser:
- Network settings, plus a fixed service address in case no address server
  can be reached
- Time and time server
- Software version and software update, also with a supplied file
- Password change
- Operating state with uptime, load, temperature, memory and network
  address
- Check of the internet connection
- Restart
- Switching on the services remote access, KNX IP gateway, MQTT broker and
  runtime environment for open extensions

5. Data backup

The automation station creates a backup of the project and of the settings
automatically once a day, either on a connected USB medium or in a secured
online directory of the manufacturer. In addition a backup must be
possible at any time on request.

6. Proof and supplements

Technical data sheet, connection diagram and declaration of conformity are
to be provided. Work on mains voltage is to be carried out by qualified
personnel.

Make and type: uni-PRO uniSERVER Premium or equivalent
Make and type offered: ..........................................

Copy long version

Automation station, industrial PC, up to 16000 data points

Supply, mount, connect and commission an automation station for large
installations, designed as a fanless industrial PC.

1. Design

- fanless, without moving parts
- data point capacity up to 16000 addresses
- network connection, serial interfaces and USB
- set up through an address server or through a fixed service address if
  no address server can be reached

2. Continuity with the DIN rail device

Project, engineering software and operating interface are the same as for
the DIN rail device of item 1. Changing the device size must not require
re-engineering, different software or a different operating interface.
Commissioning, web interface, data backup, remote access and software
update correspond to item 1.

3. Function

The device executes the same project as the DIN rail device, including
permanent storage of the settings, automatic saving before a project is
loaded and internal supervision of the program execution.

4. Application

This item applies when the data point capacity of the installation exceeds
4000 addresses or when more computing power is required for recording and
evaluation. It is an alternative item to item 1.

Make and type: uni-PRO Server-PC or equivalent
Make and type offered: ..........................................

Copy long version

Automation station, compact device with display

Supply, mount, connect and commission a compact automation station with a
built-in display.

1. Display and operation at the device

The display is written by the project. Dedicated display pages with
measured values, states and operating options are to be engineered; the
display of the device manufacturer is not to be used. Operation takes
place through the touch surface of the display.

2. Connections

- two switching outputs as relays, operated by the program
- two network connections
- one common terminal with RS232 (transmit and receive line, signal
  ground), CAN (L and H) as well as RS485 in two-wire mode or RS422 in
  four-wire mode, plus a connection for the cable screen
- connection for a USB medium

3. Operation

Network settings and reset are to be carried out from within the program.
Device temperature, humidity and wear of the storage medium are available
as measured values of the project and are to be used for fault
signalling.

4. Continuity

Project, engineering software and operating interface correspond to
item 1. The same project runs unchanged on the DIN rail device, the
industrial PC and the compact device.

Make and type: uni-PRO LF or equivalent
Make and type offered: ..........................................

Copy long version

AZ expansion modules and bus couplers

Surcharge item to the automation station for input and output modules and
for connecting separate distribution boards.

1. Connection

The modules are plugged directly onto the automation station and supplied
by it; a separate power supply per module is not required. For separate
distribution boards, bus couplers are to be supplied, over RS485 and over
the network. The bus coupler over the network must additionally be able to
connect field bus modules.

2. Commissioning

The automation station reads the plugged modules by itself. The data
points of all modules are created and assigned to the inputs and outputs on
one command; entering every single address by hand is not acceptable.

3. Operation

The read interval is adjustable per module. Fast digital signals are to be
read in every program cycle, slow measured values at longer intervals, so
that the bus load stays low. The failure of a module is to be detected and
treated as a fault message.

4. Scope

Type, number and equipment of the modules are to be stated by the
tendering party:
..............................................................
..............................................................

Make and type: uni-PRO M2020 or equivalent
Make and type offered: ..........................................

Copy long version

Automation and visualisation software

Supply of a software for engineering the building automation. Logic,
visualisation and data point list are edited with one single program in one
single project. A separate software for the visualisation with its own data
point administration is not permitted.

1. Data points

The data point list is structured into main, middle and sub groups and
applies equally to logic, visualisation and recording. A data point is
created once only. For every data point, data type, designation and proof
of use are to be kept; an evaluation of which data points are used and
which are unused must be possible.

The KNX group addresses are to be imported from the ETS project with data
type. The data points of a function block or of an input/output module are
to be created and assigned on one command. When a control element is
linked, the data points belonging to one function, for example the data
points of a blind, must be taken over in one go.

2. Logic

A graphical editor with ready-made function blocks for logic operations,
time, counting, closed-loop control, shading, heating, energy, signalling
and communication is required. Blocks are linked through visible
connections and through data points. The logic is to be structured into
pages; per page a start delay and a switching off of the page, also
through a data point during operation, are to be provided.

For sequences that no block covers, a programming interface with a
widespread scripting language must be available, including access to all
data points, time events, permanently stored values and queries of web
services.

3. Visualisation

- graphical editor for the operating pages with grid, snapping and
  alignment tools
- the number of pages, images and control elements is not limited
- free layout without mandatory templates; own images and symbols usable
- undistorted adaptation to the screen size of the end device
- portrait and landscape in parallel within one project; the operating
  interface selects the matching version by itself
- several visual styles per project, at least light and dark, switchable
  during operation through a control element and through a data point
- navigation and start page adjustable per user
- texts of the visualisation translatable into further languages, exchange
  through a text file

4. Users and permissions

Users with password, permissions, page assignment and an individual start
page. Changing the password must be possible in the operating interface.
User passwords must not be overwritten when a changed project is loaded.
Number of users: X

5. Checking and search tools

- check of the data point links for invalid entries
- check for outputs that are written from several places
- list of control elements that are not linked
- search across the whole project and across several projects
- search for parameter values and conditions
- note on control elements that cannot read a value back

6. Safe changes during operation

A changed state is first transferred into the working memory of the
automation station only and stored permanently on a separate command. In
operating mode the states of the blocks, of the connections and of the
data points must be visible on screen and parameters must be changeable
while the installation is running.

7. Multiple editing

A parameter change must take effect on all selected blocks of the same
type. Defaults per element type and page templates are to be stored and
passed on across projects.

8. Handover

The complete project file is to be handed over to the client. The client
must be able to change the installation with the same software.

Make and type: uni-PRO Studio or equivalent
Make and type offered: ..........................................

Copy long version

Operating interface for mobile devices and PC

Provide, set up and hand over the operating interface of the building
automation on the end devices of the client.

1. Platforms

The operating interface is to be provided for Android, iOS/iPadOS and
Windows from the same project. Separate engineering per operating system
is not permitted. The operating interface shows exactly the pages laid out
in the project; rebuilding the pages in another environment is not
acceptable.

2. Connection

Inside the building the operating interface connects directly to the
automation station; the automation station must be found in the network
automatically. From outside, the connection runs through the remote access
of item 7. Several installations are to be managed in one operating
interface, with an individual name per installation and switching without
setting up again.

3. Operation on a wall panel

- operating bar at the top, bottom, left, right or hidden, separately for
  portrait and landscape
- display permanently switched on
- full screen operation in which the operating system cannot be reached
- start page per user, separately for portrait and landscape

4. Opening from outside

A particular page must be callable from outside through an address, for
example from a notification, a QR code or another application. Only
installations already set up on the end device may be addressed.

5. Languages

The operating interface is to be supplied in several languages, at least
eight. In addition, the texts of the visualisation must be translatable
into further languages.

6. Scope of this item

Setting up the operating interface on up to X end devices of the client,
creating the users, setting the start pages, checking the connection
inside the building and from outside, handing over the access data.

Make and type: uni-PRO APP or equivalent
Make and type offered: ..........................................

Copy long version

AZ remote access without port forwarding, EU servers

Surcharge item to the automation station for secured remote access to the
installation.

1. Establishing the connection

The automation station establishes the connection itself. Port forwarding,
a dynamic name service or an additional device at the router are not
required and are not acceptable, because they would open a service in the
building network that can be reached from outside.

2. Data protection

All servers involved are located in the European Union only. Project data,
measured values and recordings of the installation must not be stored on
those servers. The access data are to be held there encrypted, so that
even the operator of the service cannot read them; a forgotten password
must not be readable. The bidder has to state which data arise at the
service and where the servers are located.

3. Scope of the access

The following must be able to work through the same access:
- the operating interface on the end devices of the client
- the engineering software of the installer
- the support of the manufacturer
- the software update of the automation station
- access to the web interfaces of further devices on site

4. Switching off and control by the client

Remote access is switched off on delivery and can be switched on at the
device without the engineering software. In addition it is to be locked
through a data point of the installation, so that the lock can be put on a
switch or a push button of the electrical installation. The lock must
survive a restart and must not be releasable from the operating interface.
The state of the remote access is readable as a data point and is
recognisable on site at the status indicator.

5. Independence

The installation stays fully operable if the internet connection fails.
Control functions, switching times and operation inside the building must
not depend on the remote access.

6. Withdrawing the access

The access is to be withdrawable at any time and without intervention at
the device. After withdrawal the access must be locked immediately.

7. Scope of this item

Setting up the access, checking the connection from outside, instructing
the client in locking and releasing, handing over the access data. Running
costs of the service, if any, are to be stated separately.

Make and type: uni-PRO VPN service or equivalent
Make and type offered: ..........................................

Copy long version

AZ KNX remote programming with the ETS

Surcharge item to the remote access of item 7 for programming the KNX
devices of the installation from a distance.

1. Gateway in the automation station

The automation station brings its own KNX IP gateway. A separate KNX IP
interface in the distribution board is not required for this function. The
gateway can be switched on at the device without the engineering software.

2. Programming from a distance

Through the remote access of item 7 the ETS must be able to program the
KNX devices of the installation, including loading applications and group
addresses. This allows corrections to the KNX installation without travel.

3. Planning requirement

The gateway occupies a contiguous block of individual addresses, at least
four, five recommended. This block is to be kept free in the KNX planning
and noted in the documentation.

4. Access to further devices

In addition, access to the web interfaces of further devices on site is to
be supplied, for example heat pump, inverter, charging station or
ventilation unit. Access runs through the same secured connection; port
forwarding per device is not permitted.

5. Limits

For the secure commissioning of KNX Data Secure devices and for KNX IP
Secure a separate KNX IP interface is required; it is to be tendered
separately if needed. The bidder has to state which software versions of
automation station and ETS are required.

6. Scope of this item

Setting up the gateway, entering the address block into the KNX planning,
proof of one programming from a distance on at least one device,
instructing the installer, documenting the access path.

Make and type: uni-PRO or equivalent
Make and type offered: ..........................................

Copy long version

AZ KNX connection

Surcharge item to the automation station for connecting the KNX
installation to the building automation.

1. Connection

The automation station is to be connected directly to the KNX bus line
through its TP interface. Alternatively or additionally, the connection
through external KNX IP gateways must be possible, also through several at
the same time, so that several lines or parts of the building are reached
without further software.

2. Data points

The group addresses are to be imported from the ETS project with data
type. They are data points of the same project and are equally available
to logic, visualisation and recording. A separate data point list for the
visualisation that has to be reconciled with the ETS is not permitted.

A defined range of the data point list is reserved for the KNX group
addresses, the other ranges are available for values internal to the
installation. This makes it recognisable without further information which
value goes onto the bus and which does not.

3. Data types

To be supported are the data types for switching, dimming (step and
value), blind, percentage, temperature, floating point, counters of
several widths, time, date, text and scene.

4. Operation and supervision

- cyclic reading and cyclic sending adjustable per data point
- updating the data points when the automation station starts up
- supervision of the bus connection; if the answer fails to appear, a
  fault message is to be issued and the connection re-established
  automatically
- key figures for state, received and sent telegrams as well as errors,
  available as data points

5. Testing and proof without the ETS

- telegram monitor in the automation station that records the bus traffic
  even without connected engineering software
- display of the telegram field by field
- display of the time interval between telegrams, so that telegram loops
  become recognisable
- filter on an own address list
- output as a text file
- a watch window in which data points can be read and sent

6. Scope

Number of group addresses to be connected: X
Number of KNX lines: X

Make and type: uni-PRO or equivalent
Make and type offered: ..........................................

Copy long version

AZ Modbus master and slave

Surcharge item to the automation station for connecting Modbus devices in
both directions.

1. Operating modes

- Modbus master RTU through the RS485 interface of the automation station,
  with a termination resistor that can be switched on at the device
- Modbus master TCP through the network
- Modbus TCP slave, so that a higher-level management system, a
  programmable controller or an energy manager can read and write values
  of the installation

2. Device templates

For common devices, templates with a ready register list are to be
supplied, at least for heat pumps and boilers, inverters and battery
storage systems, charging stations, energy meters, air conditioning units
and weather stations. The templates must be searchable. Entering every
single register by hand is not acceptable.

3. Scope and settings

- at least 128 register rows per connection; larger devices are covered
  through further connections
- adjustable per register: device address, function code, register number,
  data type and length, factor, register order, read interval
- register counting switchable from 0 or from 1, display also hexadecimal
- values that are written are sent on change only
- readable and writable quantities are to be kept separately

4. Supervision

The loss of connection to a device is to be detected and treated as a
fault message. After its return the connection is to be resumed
automatically. A faulty device must not hold up the polling of the other
devices.

5. Diagnostics

The Modbus traffic is to be shown in a diagnostic view, with filter on
device, register and function code and with hexadecimal display.

6. Scope

Number of devices: X, thereof RTU: X, TCP: X
Device list: ..................................................

Make and type: uni-PRO or equivalent
Make and type offered: ..........................................

Copy long version

AZ further bus systems and network protocols

Surcharge item to the automation station for further interfaces. Every
protocol is to be supplied without an additional protocol converter and
without an additional server; all values are data points of the same
project. The required protocols are to be ticked by the tendering party.

1. Field buses

[ ] M-Bus
    Reading heat, water and electricity meters through a gateway at the
    serial interface. Addressed by primary or secondary address,
    evaluation of multi-part answers.

[ ] DMX
    Control of lighting through an adapter at the automation station,
    through an interface in the network or through Art-Net without an
    adapter of its own.

[ ] CAN
    Connection of CANopen modules on devices with a CAN interface.

2. Network protocols

[ ] MQTT
    Reading and writing arbitrary topics, on request single fields of a
    message in JSON form. At least 128 rows per connection, publishing
    with and without retaining the last message. A broker is to be built
    into the automation station, so that devices in the wireless network
    can be connected without an additional server.

[ ] Data point transfer by MQTT
    Transfer of whole ranges of the data point list in both directions,
    encrypted, for connecting open automation and visualisation software.
    The values must be recognised in the third-party software without
    creating every data point individually.

[ ] Matter
    The automation station appears as one bridge with several devices in
    the common voice assistants. One single pairing must be sufficient for
    all bridged devices. To be bridged are at least light, socket, dimmer,
    shading, thermostat and sensor.

[ ] SNMP
    Reading and writing values of network-capable devices, for example
    uninterruptible power supplies, network equipment and air conditioning
    units in the server room.

[ ] Web services
    Query through HTTP and HTTPS with own headers, evaluation of JSON and
    XML, further processing in the logic.

[ ] Network supervision
    Reachability check of devices in the network with fault message, and
    switching a device on through the network.

3. Proof

The traffic of every protocol used is to be shown in the common diagnostic
view of item 18.

Make and type: uni-PRO or equivalent
Make and type offered: ..........................................

Copy long version

AZ heating, air conditioning and ventilation control

Surcharge item for the control of the heating plant and of the rooms in
the automation station. Additional controllers are not to be supplied. The
control is part of the same project as logic and visualisation; all
control quantities are data points and can therefore be recorded, operated
and used for fault signalling.

1. Heating circuit, weather-compensated

- heating curve with slope and parallel shift
- limitation of the flow setpoint upwards and downwards; the upper limit
  protects the construction of an underfloor heating system
- room influence through a room sensor, weighting adjustable
- operating modes comfort, setback, frost protection and off; changeover
  through a time program and through a data point
- pump with overrun time and minimum standstill, counting of operating
  hours
- mixer control with travel pulses and pauses; the position is to be
  formed from the travel time, stored permanently and resumed after a
  restart. The feedback of the actuator is to be supervised on request and
  a fault reported
- fast heating-up and fast setback
- plain text display of the control state, for example summer shutdown or
  flow temperature limited

2. Summer shutdown and frost protection

For the summer shutdown a gliding mean of the outside temperature is to be
formed, the period being adjustable. The heating limit works with
hysteresis and minimum dwell time, so that no daily change occurs in the
transitional period. The mean value is to be stored permanently and
continued after a restart. Frost protection also acts in operating mode
Off, when locked and in summer.

3. Heat generation

- collecting the demands of several consumers, passing on the highest
  demand, priority switching with a time limit, cascading of several
  collectors
- heat generator with minimum running time and minimum pause time, two
  stage or modulating, boiler circuit pump, return temperature raising
- counting of operating hours and starts, maintenance message at an
  adjustable threshold
- control of a heat pump with releases and operating modes
- buffer storage with charging demand, solar use with plant protection,
  heat metering from flow rate and temperature difference

4. Hot water

- charging by a sensor at the top, on request additionally at the bottom,
  through a charging pump or a diverter valve
- legionella program whose holding time only starts counting from the
  temperature reached, pauses while water is drawn and reports success
  with a date
- circulation pump by time program, by demand and by return temperature,
  modes combinable

5. Room, air conditioning and ventilation

- individual room control with operating modes comfort, standby, night and
  frost protection
- pre-heating that learns the heating-up rate of the room itself and
  starts early enough for the setpoint to be reached at the switching
  time; a fixed lead time is not acceptable
- air conditioning unit with several fan stages and separate manipulated
  variables for heating and cooling
- ventilation unit with stage switching by air quality and humidity,
  bypass operation for night cooling, filter change message;
  dehumidification only when the outside air is drier
- extract air control for bathroom and WC that detects a fast rise in
  humidity
- changeover between heating and cooling through a mean of the outside
  temperature with a neutral band; both releases must never be active at
  the same time
- dew point supervision that locks a cooling surface

6. Operation by the operator

Heating curve, parallel shift, room influence, heating limit, setpoints
and time programs must be adjustable during operation from the operating
interface, without the engineering software and without the installer.
Changed settings are to be stored permanently.

7. Scope

Number of heating circuits: X
Number of individual rooms: X
Number of ventilation units: X
Number of heat generators: X
Hot water charging: X, circulation: X

Make and type: uni-PRO or equivalent
Make and type offered: ..........................................

Copy long version

AZ energy management, PV surplus and storage

Surcharge item for the energy management in the automation station. An
additional energy management device is not to be supplied. The
distribution runs locally in the automation station and stays operable
with the last known values if the internet connection fails.

1. Recording

To be recorded are generation, grid import, grid export, state of charge
and power of the storage system as well as the power of the large
consumers. Recording takes place through the interfaces of items 9 to 11;
all values are data points of the same project.

2. Distribution of the surplus

The surplus is to be distributed by a fixed order of priority, at least
heat pump, charging station and heating element. Every consumer receives
what the higher stage leaves over. The charging station is to be
controlled steplessly to the available surplus. The heating element takes
up the rest but leaves an adjustable reserve, so that the higher stages
keep priority.

A release may only take place after the surplus has been present
continuously for several minutes; short cloud cover must not cause
switching. Withdrawals, in contrast, take effect immediately.

3. Storing heat in the building

While surplus is present, the setback of the heating is to be cancelled so
that the building takes up the energy as heat. For this a temperature band
with a minimum and a maximum value is to be provided: above the maximum
no further increase takes place, below the minimum heating always runs.
Cold protection and the minimum hot water temperature act immediately and
take precedence over surplus operation.

4. Storage operation by electricity price

The storage system is to be operated by the dynamic electricity price.
Charging and later discharging are to be evaluated as a pair, in cents per
kilowatt hour and after all losses, that is taking into account the
efficiency, the import price, the export price and the forgone revenue.
Charging from the grid takes place only when an adjustable minimum gain is
reached. The plan only grants a release; the power results from the
measurement, so that operation stays usable even when the forecast is
wrong. If no valid prices are available, the storage system continues to
work for self-consumption.

The price series is to be taken from a supplier of dynamic tariffs; value
added tax and surcharges are adjustable.

5. Yield forecast

The yield forecast of the photovoltaic system is to be calculated from the
position of the sun, orientation, tilt and power per sub-array and refined
with a cloud forecast. It must adjust itself to the actual yield, so that
soiling, ageing and shading are taken into account without intervention.

6. Charging stations

Charging stations are to be connected directly through their interface or
through OCPP. With several charging points, load management is to be
provided that limits the highest current per phase and reduces the current
before the backup fuse trips. Charging must remain possible if the
automation station fails.

7. Smaller consumers

Furthermore, the use of the surplus for hot water through a stepless
heating element, the switching on of loads in stages and the catching up
of a minimum running time, for example of a filter pump, preferably during
the time with surplus, are to be provided.

8. Display

In the operating interface, generation, consumption, grid import, grid
export, storage and self-consumption share are to be shown, plus up to
five freely labelled consumers. The values are to be recorded according to
item 14 and evaluated for hour, day, week, month and year, including yield
and savings according to the prices entered.

9. Scope

Number of charging points: X
Number of storage systems: X
Number of inverters: X
Dynamic tariff: yes / no

Make and type: uni-PRO or equivalent
Make and type offered: ..........................................

Copy long version

AZ recording and evaluation of measured values

Surcharge item for the long-term recording of measured values in the
automation station. An additional data logger, an additional computer or a
cloud service are not to be supplied.

1. Recording

Arbitrary data points of the project are to be recorded in the automation
station. The recording runs without connected engineering software and
without an open operating interface and survives a restart. The trigger is
to be selectable per measured value:
- on every telegram
- on value change
- by time, from seconds to years
- by time with a minimum deviation, so that quiet periods create no
  records

2. Structure and scope

The recordings are to be structured into groups, with an individual chart
per group. The number of records per recording is to be limited; the
oldest record drops out. The expected memory requirement is to be shown in
the engineering software.

To protect the storage medium the values are to be collected and written
at longer intervals. For permanent recording at a short interval a storage
medium for industrial use is to be provided; it is to be stated with
items 1 to 3.

3. Display and output

- chart in the engineering software and in the operating interface
- time selection through a calendar, zoom, several lines in one chart
- factor and offset per line, limitation to a value range, line shape
  selectable
- running display of several measured values without a recording of their
  own
- output as a text file with semicolon as separator for further processing
  in a spreadsheet

4. Counters and energy evaluation

- consumption per hour, day, week, month and year including the previous
  period
- consumption by tariff stages
- counting of pulses, switch-on times and operating hours
- energy evaluation with generation, consumption, grid import, grid
  export, self-consumption share as well as yield and savings according to
  the prices entered; the values are to be recorded hourly and held for
  several years
- the self-consumption share is to be formed from energy quantities, not
  from averaged percentages

5. Scope

Number of measured values to be recorded: X
Recording period: X years
Recording interval: ..............................

Make and type: uni-PRO or equivalent
Make and type offered: ..........................................

Copy long version

AZ fault messages and notification

Surcharge item for the fault message handling and the notification in the
automation station.

1. Acquisition

The fault messages of the whole installation are to be collected in one
place. A plain text is to be assigned to every message. The message is to
be latching: a fault that has occurred stays visible until it is
acknowledged, even if the cause disappears in the meantime. A message that
disappears together with its cause is not acceptable.

2. Classes and further processing

At least three message classes are to be provided, for example alarm,
warning and note, with an individual collective output per class and a
general fault. The collective outputs are data points and can therefore be
put on lamps, horns or bus signals. The delivery is to be selectable
separately per class.

For start-up it is to be defined whether messages that occurred while the
delivery was out of order are caught up or discarded.

3. Acknowledgement and log

Acknowledgement takes place in the operating interface and through a data
point, so that a push button of the electrical installation can be used as
well. A log with coming, going and acknowledging per message, including a
time stamp, is to be kept. The log survives a restart.

4. Delivery

Delivery paths, at least:
- e-mail through an own or a provided mail server, on request with an
  attachment
- notification on the end devices of the client. For this, no additional
  user account, no additional application and no entry of access data at
  the block may be required. The notification must be able to lead
  directly to the operating page concerned
- voice announcement or signal tone on existing loudspeakers

The recipient list is to carry weekdays and quiet times. If a message is
not acknowledged, it is to be forwarded to the next place after an
adjustable time; several stages are to be provided. The number of messages
per period is to be limited, so that a fluttering fault does not create a
flood of notifications.

5. Supervisions

- contact supervision for windows, doors and roof windows, with a separate
  message when absent, when it rains, during frost and when a contact has
  been open for a long time
- supervision of feedback signals against the command, for example at
  pumps, actuators and mixers
- supervision of the reachability of connected devices and bus systems
- supervision of the automation station's own operating values, for
  example temperature and memory usage

6. Scope

Number of messages: X
Number of recipients: X
Delivery paths: ...............................................

Make and type: uni-PRO or equivalent
Make and type offered: ..........................................

Copy long version

AZ connection of third-party systems and devices

Surcharge item per device or service of another manufacturer to be
connected.

1. Principle

A ready-made function block is to be used per device. The values of the
device become data points of the same project and are equally available to
logic, visualisation, recording and fault signalling. A connection that is
visible in the visualisation only and cannot be used in the logic is not
acceptable.

The data points of a block are to be created and assigned on one command.
The designations are to be meaningful.

2. Supervision

Per device it is to be supervised whether it still answers. The failure is
to be kept as a data point and treated as a fault message according to
item 15. The installation must continue to work if a third-party device
fails; the other functions must not be affected.

3. Operation

No application and no portal of the device manufacturer may be required
for operation by the client. All required functions are to be shown in the
operating interface of the building automation.

4. Local connection

Devices that can be reached locally through network, radio or bus are to
be connected locally. A cloud service is permitted only where the
manufacturer offers no local interface. Every connection through a cloud
service is to be stated in the tender, together with the data
transmitted.

5. Device groups

To be connected, as far as provided in the project:
[ ] switching, dimming and shading devices in the wireless network,
    including battery-powered push buttons and sensors through a receiver
[ ] lighting systems through a bridge, with colour and feedback
[ ] actuators for roller shutters, windows, awnings and gates through
    their radio interface, encrypted in the local network, with position
    feedback
[ ] door station with bell and motion event, door opener, light and camera
    image; the camera image is to be fetched by the automation station and
    passed on, so that it is also visible through the remote access
    without port forwarding
[ ] network cameras as a still image
[ ] door lock with state, door sensor and battery state
[ ] alarm system through network or serial interface
[ ] loudspeakers in the local network, with playback, volume, favourites
    and announcements
[ ] voice assistant, locally in the network, without additional software
[ ] inverters, battery storage systems and charging stations
[ ] heat pumps, boilers, ventilation and air conditioning units
[ ] energy, heat and water meters
[ ] weather stations
[ ] robotic mowers and garden equipment
[ ] household appliances
[ ] open automation and visualisation software through the data point
    transfer of item 11

6. Scope

Devices and services to be connected, with make and type:
..............................................................
..............................................................
..............................................................

Make and type of the connection: uni-PRO or equivalent
Make and type offered: ..........................................

Copy long version

AZ free programming with a scripting language

Surcharge item for sequences that no ready-made function block covers, for
example the connection of a web service or a function specific to the
installation.

1. Environment

Programming takes place in a widespread scripting language, embedded in
the same engineering software. An additional tool, an additional runtime
environment or an additional computer are not to be supplied. The block
receives a freely selectable number of inputs and outputs, which are wired
and linked with data points like any other block.

2. Scope of the interface

- reading and writing all data points of the project
- call at start-up, on change of an input, on a bus event and at
  selectable intervals from tenths of a second to hours
- permanently stored values that survive a restart, as well as values
  valid across the installation
- query of web services through HTTP and HTTPS with own headers
- access to serial interfaces and to network connections
- ready-made algorithm for continuous closed-loop control
- sending notifications through the paths of item 15

3. Verifiability

Error messages, intermediate values and watched quantities are to be made
visible in the diagnostics of item 18, also while the installation is
running.

4. Operational safety

A blocking or endlessly running script must not bring the installation to
a standstill. The automation station detects the blockage and restarts by
itself.

5. Protection and handover

The script is to be protected against inspection if the client requires
this. The function is to be described in the plant documentation, so that
it remains comprehensible without inspecting the program text.

Make and type: uni-PRO or equivalent
Make and type offered: ..........................................

Copy long version

AZ diagnostics of all bus systems

Surcharge item for the diagnostics of the installation during operation
and for fault finding.

1. Common view

The traffic of all connected bus systems is to be shown in one common
view, at least:
- KNX over twisted pair and over the network
- Modbus as master and as slave
- MQTT
- M-Bus
- the input and output modules
- messages and errors of the automation station

One separate, filterable area is to be provided per bus system. A separate
tool per bus system that has to be procured or started separately is not
accepted.

2. Recording of the bus traffic

The bus traffic is to be recorded in the automation station, also without
connected engineering software. Required:
- buffer in the working memory with an adjustable size, so that the
  storage medium is not burdened
- filter on everything, on individual bus systems or on an own address
  list
- display of the time interval between telegrams and highlighting of
  rapidly repeating telegrams, so that telegram loops are detected
- permanent recording in daily files with an adjustable number of days
- output as a text file

3. Observing and testing

A watch window must allow data points to be observed in groups, values to
be displayed, values to be read and values to be sent. In operating mode
the states of the blocks, of the connections and of the data points are
visible on screen; parameters are changeable while the installation is
running.

4. Diagnostics on site

At the device it must be recognisable without aids whether the program
execution is running and whether the remote access is up. Through the web
interface, uptime, load, temperature, memory usage and network address are
to be readable, plus a check of the internet connection.

Make and type: uni-PRO or equivalent
Make and type offered: ..........................................

Copy long version

AZ distributed project, up to 16 automation stations

Surcharge item for installations whose equipment is spread over several
buildings or several distribution boards, for example a house with an
outbuilding, a school with a gym, or a company with office, hall and
store.

1. Principle

Several automation stations, at least 16, execute one common project. Per
program page it is defined which station executes it. In this way the
equipment of every building is run by the station on site, while planning,
maintenance and operation stay uniform for the whole installation.

Several separate projects whose values have to be exchanged individually
and which have to be maintained more than once on every change are not
acceptable.

2. Distributing the project

The project is loaded into one station and distributed from there to the
others. A station that could not be reached while loading fetches the
state by itself afterwards. The project state of every station is to be
shown in the engineering software.

3. Availability

Every station handles its tasks independently. If one station fails, the
others continue to work undisturbed; only the functions of the failed
station are missing. The failure of the central station must not bring the
whole installation to a standstill.

4. Operation

The operating interface connects to any station and operates the whole
installation, including the pages whose values reside on other stations. A
separate connection per building is not acceptable.

5. Common settings

Common settings, at least switching times, setpoints, scenes and presence
states, apply on all stations and are reconciled automatically. Operating
values that belong to the respective station only, for example meter
readings and operating hours, stay local.

6. Supervision

The stations supervise each other with a sign of life at a short interval.
If a station is absent for longer than an adjustable time, a message
according to item 15 is to be issued. A short restart must not cause a
false alarm. The state of every station is available as a data point.

7. Device replacement

A station is assigned to its task through a number that is set at the
device and is not held in the project. When a device is replaced, the new
device takes over the number of the old one and executes the same tasks; a
change to the project is not required for this.

8. Scope

Number of automation stations: X
Assignment of the plant sections: .............................
..............................................................

Make and type: uni-PRO or equivalent
Make and type offered: ..........................................

Copy long version

AZ backup automation station, automatic takeover

Surcharge item for a second automation station that takes over the
installation automatically when the first one fails. To be provided for
installations whose standstill cannot wait until the next working day, for
example a hotel, a care home, a business or a remote site.

1. Standby operation

The second station runs along in standby. It executes the same project,
computes all values, states and recordings and keeps polling the connected
devices. After a takeover no mean values, no meter readings and no trends
are missing. A station that only starts up after the failure and has to
form its values anew is not acceptable.

In standby the second station issues no command to the outside; nothing
may be switched twice and nothing may be reported twice.

2. Detecting the failure

The failure is to be detected on two paths:
- through a sign of life that the first station sends regularly onto the
  bus of the electrical installation
- through a query in the network at a short interval that checks not only
  the reachability but also the running program execution

Both paths are selectable individually and together. If both are selected,
the takeover happens only when both fail; a restarting network switch must
not cause a takeover. The waiting time until the takeover is adjustable.

3. Takeover and handback

The takeover happens without intervention on site, without replugging and
without operation. As soon as the first station works again, the second
hands back automatically and returns to standby.

4. Transfer

Project, scenes, switching times and settings are to be taken over from
the first station daily, so that the second station always holds the valid
state.

5. Messages

To be reported according to item 15: takeover, handback and failed
transfer. On request a daily confirmation of standby operation is to be
issued in addition.

6. Interaction

The backup station must work together with the distributed project of
item 19: it backs up the leading station and takes its place in the
network of stations on takeover. If the first station has a KNX IP
gateway, this is to be provided on the backup station as well.

7. Scope

Number of backup stations: X
Detection paths: bus / network / both
Waiting time until takeover: X minutes

Make and type: uni-PRO or equivalent
Make and type offered: ..........................................

Copy long version

Engineering and programming building automation

Creating the building automation project, consisting of logic, operating
pages and data point list in one project.

1. Basis and data import

- recording the plant data, agreeing the operating philosophy with the
  client
- import of the group addresses from the ETS project with data type; the
  group addresses are not changed, not overwritten and not newly created
- building up the data point list with meaningful designations and a
  comprehensible structure by storey, room and trade
- automatic creation of a basic framework from the group addresses, with
  program pages per room, operating pages, overviews and navigation; the
  rule set for the assignment is to be defined and handed over to the
  client, so that future extensions are built up in the same way

2. Logic

- approx. X logic functions for lighting and shading, including shading by
  the position of the sun as well as wind and rain protection
- approx. X logic functions for heating, air conditioning and ventilation
  according to item 12
- approx. X scenes, on request with learning of the current states
- approx. X time programs, X of them with sunrise and sunset; public
  holidays are to be taken into account without an internet connection
- present, absent and holiday as central states; per element it is to be
  defined which value applies on a change
- presence simulation, on request only during darkness

3. Operation

- approx. X operating pages with up to X data points
- navigation, start pages and users as specified by the client
- portrait and landscape, as far as required by the client
- at least two visual styles, light and dark

4. Third-party plants

Connecting approx. X data points from third-party plants, fault messages
and measured values of the instrumentation, including coordination with
the technicians of the trades concerned and checking the point lists
handed over.

5. Messages and recording

- approx. X displays for fault messages including forwarding in case of a
  fault according to item 15
- setting up the recording of item 14 for approx. X measured values

6. Checking

Before handover the project is to be checked for invalid links, for
outputs that are written from several places and for control elements that
are not linked. The result is to be documented.

7. Work on the running installation

Intermediate states are transferred into the working memory of the
automation station only; permanent storage takes place after release.
Before every permanent storage the existing state is to be saved.

Copy long version

Commissioning, documentation and training

1. Commissioning

- integrating the automation station into the network of the client,
  agreeing the network settings with the operator of the network
- setting time and time server
- loading the current software version
- changing the default passwords and handing over the new passwords

2. Functional test

Functional test per plant section against the functional description, with
a test report. At least to be tested:
- switching, dimming and shading per room
- control functions according to item 12, including frost protection and
  summer shutdown
- fault messages according to item 15, including delivery to the
  recipients entered and acknowledging
- recording according to item 14
- behaviour after a power failure: restart, continuation of the settings
  and of the meter readings

3. Data backup

Setting up the daily automatic data backup and proof of one restore. The
client is to be shown how an earlier state is restored and how project and
settings are restored separately.

4. Remote access

Setting up the remote access according to item 7, checking the connection
from outside, instruction in locking and releasing.

5. Documentation

To be handed over:
- data point list with designation, data type and use
- functional description of the installation in plain language
- connection diagram of the automation station and of the input/output
  modules
- assignment of the plant sections to the automation stations in case of a
  distributed project according to item 19
- list of the individual addresses occupied, including the block for the
  KNX IP gateway according to item 8
- description of the free programming according to item 17, if present

6. Handover

The complete project file and all access data are to be handed over to the
client. The client must be able to change the installation with the
engineering software.

7. Training

Training of up to X users on the installation, including operating pages,
time programs, setpoints, scenes, presence states, fault messages and
acknowledging. The operating staff is to be trained separately in locking
and releasing the remote access, in the data backup and in the fault
message handling.

Number of users to be trained: X
Duration of the training: X hours

Copy long version

AZ maintenance and remote support per year

Surcharge item for the ongoing support of the installation through the
secured access of item 7.

1. Software maintenance

Loading the software updates of the automation station from a distance.
Before every update a backup is to be created. The software version before
and after the update is to be documented.

2. Annual check

- check of the daily data backup and of one restore
- check of the fault message delivery to all recipients entered
- check of the recording for gaps
- check of the operating values of the automation station, at least
  uptime, load, temperature, memory usage and wear of the storage medium
- check of the reachability of all connected bus systems and devices
- review of the fault message log for recurring messages

3. Fault handling

Handling faults from a distance. Response time and availability are to be
stated by the bidder. A site visit may only be charged if the fault cannot
be remedied from a distance.

4. Smaller adjustments

Adjusting time programs, setpoints, designations and operating pages
within the agreed scope.

5. Report

Per maintenance a report is to be handed over naming the points checked,
the defects found and the work carried out.

6. Scope

Term: X years
Response time: ................................................
Availability: .................................................
Hours included for adjustments per year: X