Lonix IBMS Specification
Lonix IBMS Specification
Lonix IBMS Specification
1 (23)
IBMS Specification
Specification & Design Guideline for Integrated Intelligent
Building Management System
Lonix Ltd
www.lonix.com
LONIX LTD
www.lonix.com
Teollisuuskatu 33
FI-00510 Helsinki, Finland
VAT 1043054-9
Trade Reg.No. 678.356
IBMS Specification
Lonix Ltd Finland
2 (23)
INDEX
Introduction .........................................................................................................................................4
LONIX LTD
www.lonix.com
Teollisuuskatu 33
FI-00510 Helsinki, Finland
VAT 1043054-9
Trade Reg.No. 678.356
IBMS Specification
Lonix Ltd Finland
3 (23)
LONIX LTD
www.lonix.com
Teollisuuskatu 33
FI-00510 Helsinki, Finland
VAT 1043054-9
Trade Reg.No. 678.356
IBMS Specification
Lonix Ltd Finland
4 (23)
1 Introduction
What is IBMS? - Why is IBMS an advantage? - Purpose and scope of this document.
IBMS stands for Integrated Building Management System. An Integrated
Building Management System is a single, comprehensive building management
system for HVAC, lighting, security, fire and other systems.
The Building Management System (BMS) can be defined as the system installed
in buildings that controls and monitors the buildings mechanical and electrical
equipment, such as heating, cooling, ventilation, and lighting. These systems
typically represent 70% of a building's energy usage. Obviously, the role of BMS
is crucial in management of the buildings energy demand.
Beyond controlling the internal environment of the building, the IBMS (Integrated
Building Management System) covers also access control, intruder alarms,
video surveillance, monitoring of fire alarm system and other systems as
applicable. IBMS can be referred to as the Integrated BMS and Security System;
the single, uniform system for building management.
Application of full IBMS brings the benefits of better indoor comfort, energy
efficiency, safety and security, and most importantly, better management of all
the systems under the unified system. IBMS supports efficient functional system
integration and provides maximum flexibility to support any future changes in the
building use.
This document describes the essentials of IBMS comprising the following
elements:
-
2 System Architecture
2.1
LONIX LTD
www.lonix.com
Teollisuuskatu 33
FI-00510 Helsinki, Finland
VAT 1043054-9
Trade Reg.No. 678.356
IBMS Specification
Lonix Ltd Finland
5 (23)
Each layer of the system shall operate independently of the next level up, in
order to allow for fault tolerant system functionality. Most importantly, the Control
Layer shall operate independently without support from the Management Layer.
It shall be possible to integrate BMS systems with security systems as specified
in this document. The system shall enable remote monitoring, connectivity and
value-adding services.
The system shall incorporate integrated BMS and Security Systems as described
in this document.
2.2
General
Building Automation System (BAS/BMS) comprises the control and monitoring
functionality of mechanical (heating, ventilation and air conditioning) and
electrical systems in a building. The core functionality of Building Automation
keeps the building climate within a specified range, provides lighting based on
schedule and/or occupancy, monitors system performance and device failures,
and provides notifications to building engineering staff.
The typical scope of BAS/BMS contains control and monitoring of mechanical
and electrical systems, including cooling/heating system, ventilation system,
pumps, tanks, lifts, lighting controls and often also consumption metering.
To achieve full benefits of functionally integrated BMS, the Lighting Control
System shall be implemented as part of Building Automation / Building
Management System, using smart controllers that shall be connected to the
same field bus as BMS controllers.
LONIX LTD
www.lonix.com
Teollisuuskatu 33
FI-00510 Helsinki, Finland
VAT 1043054-9
Trade Reg.No. 678.356
IBMS Specification
Lonix Ltd Finland
6 (23)
The BMS controllers and the Unit controllers shall be connected to the monitoring
and control software through the BOS platform.
To create comprehensive IBMS and to provide uniform view to all systems,
Building Automation / Building Management System shall be integrated with
security and safety systems through the Building Operating System (BOS)
platform.
3.2
BMS Controllers
The mechanical and electrical systems shall be controlled and monitored by
smart BMS controllers connected to an industry standard field bus. The BMS
controllers shall provide for capability of control and monitoring of all mechanical
and electrical systems, including cooling/heating system, ventilation system,
pumps, tanks, lifts, and lighting controls at the minimum but not limited to above
mentioned systems.
BMS controllers shall include the full intelligence for system functionality and to
be capable of operating independently without interference from any master
controllers or management applications.
BMS controllers shall support distributed intelligence and centralized system
designs alike. It shall be possible to distribute BMS controllers at electrical
switchboards or cabinets close to the controlled system to minimize cabling.
To achieve better fault tolerance and robust functionality, systems with
centralized master/zone controllers shall not be accepted. Each controller shall
be capable to function in a stand-alone manner and able to communicate with
other controllers without any master controllers.
Each BMS controller shall contain a 32-bit processor and standard field bus
connectivity. Communication between BMS controllers shall be event based,
peer-to-peer real time communication. The field bus topology shall be flexible
supporting at least bus, star and free topologies.
Any failure problem in communication bus should not affect the operation of the
controller.
BMS controllers shall be capable of using both 24VAC and 24VDC as operating
voltage. BMS controllers shall support user friendly operation and maintenance
by having clearly visible LED:s in the front panel to indicate status of the
controller and status of its I/O points.
Each BMS controller involved in process controls shall contain flexible I/O points
(each controller including a set of universal inputs and outputs, optimally 10 I/O in
each) with freely configurable software functions. Each controller shall be
capable of handling I/O point belonging to different systems to enable flexible
distribution of I/O points throughout the whole system.
The I/O points shall support the following features.
UI (Universal Input):
LONIX LTD
www.lonix.com
Teollisuuskatu 33
FI-00510 Helsinki, Finland
VAT 1043054-9
Trade Reg.No. 678.356
IBMS Specification
Lonix Ltd Finland
7 (23)
UO (Universal Output):
-
3.3
LONIX LTD
www.lonix.com
Teollisuuskatu 33
FI-00510 Helsinki, Finland
VAT 1043054-9
Trade Reg.No. 678.356
IBMS Specification
Lonix Ltd Finland
8 (23)
The FCU controller shall automatically change the FCU motor speed based on
temperature deviation. The FCU controller shall regulate the cooling valve to
meet the desired temperature conditions.
The Split Unit controller shall automatically change the fan speed of the indoor
unit based on temperature deviation. The Split Unit controller shall regulate the
compressor to meet the desired temperature conditions.
Unit Controllers shall communicate on standard field bus and shall be integrated
with BMS system to enable energy optimization and reporting.
3.4
Field Devices
Field devices shall be connected to BMS controllers using the common industry
standards:
-
3.4.1
Temperature Sensors
Temperature sensors shall meet the following requirements:
-
LONIX LTD
www.lonix.com
VAT 1043054-9
Trade Reg.No. 678.356
IBMS Specification
Lonix Ltd Finland
9 (23)
2% accuracy
Reverse voltage protected and output limited
CO2 Sensors
Carbon dioxide detection sensors shall meet the following requirements:
-
3.4.4
CO Sensors
Carbon monoxide detection sensors shall meet the following requirements:
-
3.4.5
LONIX LTD
www.lonix.com
Teollisuuskatu 33
FI-00510 Helsinki, Finland
VAT 1043054-9
Trade Reg.No. 678.356
IBMS Specification
Lonix Ltd Finland
3.4.6
10 (23)
3.5
General
Lighting Control System comprises control functionality of lighting systems in a
building, indoor and outdoor alike. Lighting control systems serve to provide the
right amount of light where and when it is needed.
To achieve full benefits of functionally integrated BMS, the Lighting Control
System shall be implemented as part of Building Automation / Building
Management System, using smart controllers that shall be connected to the
same field bus as BMS controllers.
4.2
Controllers
The Lighting Control System shall be controlled and monitored by smart
controllers connected to an industry standard field bus. The controllers shall be
connected to the same field bus as BMS controllers.
The controllers shall support lighting controls based on push-button controls,
illumination, time schedules and based on occupancy, with a definable off delay.
The controllers shall support definition of lighting scenes and lighting groups. The
lighting groups and scenes shall be flexible to modify at all times.
The system shall contain separate interface relays for on/off controls, in order to
be able to change the interface relays without having to replace the controller. It
LONIX LTD
www.lonix.com
Teollisuuskatu 33
FI-00510 Helsinki, Finland
VAT 1043054-9
Trade Reg.No. 678.356
IBMS Specification
Lonix Ltd Finland
11 (23)
shall be possible to control the lights on/off also direct from the interface relay for
e.g. testing purposes.
Controllers shall include the full intelligence for system functionality and to be
capable of operating independently without interference from any master
controllers or management applications.
Controllers shall support distributed intelligence and centralized system designs
alike. It shall be possible to distribute controllers at electrical switchboards or
cabinets close to the controlled system to minimize cabling.
To achieve better fault tolerance and robust functionality, systems with
centralized master/zone controllers shall not be accepted. Each controller shall
be capable to function in a stand-alone manner and able to communicate with
other controllers without any master controllers.
Each controller shall contain a 32-bit processor and standard field bus
connectivity. Communication between controllers shall be event based, peer-topeer real time communication. The field bus topology shall be flexible supporting
at least bus, star and free topologies.
Any failure problem in communication bus should not affect the operation of the
controller.
Controllers shall be capable of using both 24VAC and 24VDC as operating
voltage. Controllers shall support user friendly operation and maintenance by
having clearly visible LED:s in the front panel to indicate status of the controller
and status of its I/O points.
Each controller shall contain flexible I/O points (each controller including a set of
universal inputs and outputs, optimally 10 I/O in each) with freely configurable
software functions. Each controller shall be capable of handling I/O point
belonging to different systems to enable flexible distribution of I/O points
throughout the whole system.
The I/O points shall support the following features.
UI (Universal Input):
-
UO (Universal Output):
-
The controllers shall have detachable, numbered connection strips for easy
installation. The controllers shall support mounting in DIN rail. Manufacturing of
controllers shall comply with ISO-9001 and ISO-14001 standards.
LONIX LTD
www.lonix.com
Teollisuuskatu 33
FI-00510 Helsinki, Finland
VAT 1043054-9
Trade Reg.No. 678.356
IBMS Specification
Lonix Ltd Finland
12 (23)
4.3
General
The Access Control and Intruder Alarm System controls physical access to
premises and detects unauthorized access. The Access Control and Intruder
Alarm System shall be implemented as one unified system as described in this
section.
Access Control and Intruder Alarm System shall be implemented with smart
Network Controllers and Interface Panels.
Users can be classified so that they have access only to the spaces they are
allowed to enter according to programmed time schedules.
Intruder alarm system shall include perimeter protection and indoor surveillance.
Monitored doors and windows shall be equipped with magnetic contacts.
Movement detectors used in indoor surveillance shall be sensitive enough for
presence detection of a single person, so that they can also be used for lighting
controls and air-conditioning controls.
The Access Control and Intruder Alarm System shall use the Building Operating
System (BOS) platform as the Security Management System. It shall be possible
to integrate the Access Control and Intruder Alarm System with BMS through the
Building Operating System (BOS) platform.
To create comprehensive IBMS and to provide uniform view to all systems,
Access Control and Intruder Alarm System shall be integrated with Building
LONIX LTD
www.lonix.com
Teollisuuskatu 33
FI-00510 Helsinki, Finland
VAT 1043054-9
Trade Reg.No. 678.356
IBMS Specification
Lonix Ltd Finland
13 (23)
5.2
5.2.1
Network Controller
The Network Controller shall contain the full intelligence for system functionality,
with access control processing for up to 32 interface panels. Each controller shall
contain a 32-bit processor running the Linux Operating System. The Network
Controller shall make all online door decisions, input monitoring and output
control for connected interface panels.
The Network Controllers shall connect with BOS Software through industry
standard TCP/IP protocol, over 10/100 Mbps Ethernet or over Internet.
The controller shall be capable of processing real time commands received from
the BOS Software.
The Network Controller shall connect with Interface Panels through two
independent RS-485 networks, each network having two sets of input
connections for optimum system topology. This architecture minimizes the impact
on corporate LANs by using only one TCP/IP address for every 32 interface
panels and by handling low-level transactions on the RS-485 network. The
controller shall have event buffer of 99,999 events for offline transactions.
Each Network Controller shall contain two on-board inputs and outputs for local
input point monitoring and auxiliary output control.
5.2.2
Interface Panels
Interface Panels shall contain at least the following types:
-
Interface Panels shall connect with the Network Controller through a high speed
RS-485 network.
LONIX LTD
www.lonix.com
Teollisuuskatu 33
FI-00510 Helsinki, Finland
VAT 1043054-9
Trade Reg.No. 678.356
IBMS Specification
Lonix Ltd Finland
5.3
14 (23)
Field Devices
The proximity readers shall use Wiegand interface to connect with the Interface
Panel.
Field devices shall be connected to Interface Panels using common industry
standards.
5.4
General
Video surveillance shall be implemented with a fully IP based Network Video
Recording (NVR) system. The system shall be capable of running on Linux
operating system.
It shall be possible to integrate Video Surveillance with BMS using Building
Operating System (BOS) as the integration platform.
6.2
LONIX LTD
www.lonix.com
Teollisuuskatu 33
FI-00510 Helsinki, Finland
VAT 1043054-9
Trade Reg.No. 678.356
IBMS Specification
Lonix Ltd Finland
6.3
15 (23)
Cameras
The system shall include compliant IP cameras for video surveillance.
General
The monitoring & control software shall be based on the generic Building
Operating System (BOS) software platform that contains the full set of features
and functionalities to serve as the Monitoring & Control Software (SCADA) for the
fully featured IBMS system, and supports integration and interoperability of
various building systems. The BOS software platform shall consist of the BOS
Server and User Interface applications.
The BOS Server shall be a genuinely scalable solution, based on modern
software architecture and technologies, and its core applications shall be
implemented using industry standard Java technology. The software shall be
capable of running on both Windows and Linux operating systems.
The BOS Server shall support industry standard operating systems, networks
and protocols. The system shall support industry standard protocols, including at
least BACnet, LonWorks, Modbus, M-Bus, OPC, Ethernet TCP/IP and Internet
communication technologies. These protocols shall be supported on software
level without need for external gateways.
Web UI application and Client UI application shall both be supported as User
Interface applications. The BOS platform shall support a true Client-Server
architecture, enabling the server application to be run separately from the client
application. Whenever required, it shall also be possible to run both applications
on the same computer. Client connections to the server must utilize TCP/IP
network (e.g. LAN, Internet). The server application shall be able to handle many
simultaneous client connections from a number of workstations. The BOS
platform shall allow for usage through a standard Internet browser.
It shall be possible to run the BOS Server as a Windows service or Linux
daemon service. It shall be automatically started upon booting of the server
computer. The application shall be capable of logging application level events to
operating systems system log.
The internal software architecture of the BOS Server shall support service
oriented architecture, enabling adding and removing of the BOS services during
the life cycle of the project. BOS Server application shall be a software product
that is configured for each project. It is not allowed to have a project specific
application code, thus it shall not be necessary to compile any server application
code for the project.
The BOS Server shall offer an application framework consisting of core services
and network interface driver services. The application framework shall start and
LONIX LTD
www.lonix.com
Teollisuuskatu 33
FI-00510 Helsinki, Finland
VAT 1043054-9
Trade Reg.No. 678.356
IBMS Specification
Lonix Ltd Finland
16 (23)
monitor all these services. It shall also be possible to develop new services to the
framework according to the manufacturers development API specifications. It
shall be possible to support new field bus protocols by implementing new
network interface drivers.
The BOS Server shall include a SQL database for centralized storage of system
events, trends and logs. The SQL database can be run on the same computer or
in a separate computer.
The system shall include centralized alarm dispatching features for all connected
systems, using e.g. SMS and email. The system shall support triggering of
functions based on the events from the other connected systems.
The BOS Server shall be configurable using a dedicated application, e.g. a
Server Manager Tool. It shall be possible configure the Server Application, which
is installed to the same computer, or the remotely accessed server using SSH
connection. The Server Manager application shall allow for configuration of the
services, users and user rights based on the structured data model of the server.
It shall be possible to take a backup of the configurations of the server
application using the Server Manager Tool. All configuration must be done using
the Server Manager application. No manual editing or manipulation of the server
applications configuration files is allowed, in order to prevent unwanted error
situations that may be visible only during startup.
7.2
Main Features
The BOS platform shall include the following features:
LONIX LTD
www.lonix.com
The BOS shall support receiving of real time values, trends, alarms and
event logs from the connected systems. Different levels of logs (e.g.
warning, error, info) shall be available.
The BOS shall support modification of set points, time schedules and
manual (override) controls in the connected systems.
The functionalities of the BOS shall run on the server level autonomously
of the user interfaces.
The BOS shall support multiple operating systems, including Linux and
Windows.
Teollisuuskatu 33
FI-00510 Helsinki, Finland
VAT 1043054-9
Trade Reg.No. 678.356
IBMS Specification
Lonix Ltd Finland
7.3
17 (23)
The BOS shall contain drivers to industry standard field buses and shall
support third party device integrations.
The BOS shall contain a Data Model describing the structure of the
building and the control systems.
Data Model
The BOS Server shall contain a Data Model describing the structure of the
building and the control systems. The data structure of the BOS Server shall be
based on XML data model, which includes modeling of building structure,
systems and devices in a standard manner.
The data model shall describe the structure of the building and the control
systems, including devices and functions. The model shall include two main
sections: the first section contains model of the real world (e.g. building structure)
and the second models abstract items (e.g. control systems).
The data model shall define at least the following elements:
-
The data model shall be transferred to BOS Server as XML files, describing the
building structure and the control model. The XML schemas shall define the
structure and elements used in these files.
7.4
Database
The BOS Server shall come with an SQL database, which shall include ODBC
and JDBC drivers. It shall also be possible to use other database engines, in
case there are specific needs by the customers environment.
7.5
Operating System
The BOS Server shall run on Linux (preferred) or on a Microsoft Windows 8 /
Windows 7 / Vista / XP, Windows Server 2012 / 2008 / 2003 operating system.
7.6
Standby Server
Whenever theres a special requirement for High Availability (HA), the system
shall be equipped with a failover server. The failover server is normally idle,
monitoring the main server, taking over in case the main server fails.
LONIX LTD
www.lonix.com
Teollisuuskatu 33
FI-00510 Helsinki, Finland
VAT 1043054-9
Trade Reg.No. 678.356
IBMS Specification
Lonix Ltd Finland
7.7
18 (23)
Integration Interfaces
The BOS Server shall comprise defined interfaces for systems and applications
to be connected with the platform. The interfaces shall include interfaces as
follows:
7.7.1
System Interface
The System Interface shall allow any system to be integrated with the BOS
Server. The interface shall consist of Network Interface Drivers and Device
Drivers.
Network Interface Drivers shall enable communication with external systems and
devices utilizing a variety of media and protocols, such as BACnet, LonWorks,
Modbus, M-Bus, OPC, Ethernet TCP/IP and Internet communication
technologies.
Network Interface Drivers shall be services of the BOS Server to provide general
access to different field buses. Other services of the BOS Server (e.g. device
drivers) can utilize the access provided by Network Interface Drivers.
The Device Drivers shall allow integration of different systems/devices with the
BOS Server.
7.7.2
Enterprise Interface
The Enterprise Interface shall allow different applications to access the BOS
Server connected systems and to receive information from connected systems.
The interface shall utilize the latest Web Services technology, e.g. REST. All
communication shall be implemented in standard XML or JSON format. External
applications shall be able to give commands to the connected systems and to
receive information via Enterprise Interface to/from all connected systems.
The Enterprise Interface shall include the following main functionality:
-
For example, Data Point values can convey the following types of information:
LONIX LTD
www.lonix.com
Teollisuuskatu 33
FI-00510 Helsinki, Finland
VAT 1043054-9
Trade Reg.No. 678.356
IBMS Specification
Lonix Ltd Finland
19 (23)
Maintenance alarms
Intruder alarms
Fire alarms
Setpoint adjustment
Control optimization
Trending
Preventive maintenance
Regular SW updates
8 User Interfaces
8.1
General
User Interfaces shall provide access to connected systems through the BOS
platform. The User Interfaces shall be available both as a Web Application and
as a Java based client application. The client application is recommended for
professional usage and central monitoring applications.
LONIX LTD
www.lonix.com
Teollisuuskatu 33
FI-00510 Helsinki, Finland
VAT 1043054-9
Trade Reg.No. 678.356
IBMS Specification
Lonix Ltd Finland
8.2
20 (23)
The User Interface shall contain system views, floor plan views, trend view, alarm
views and event log views. The User Interface shall include an automatically
adapting tree structure of the building, buildings parts, individual spaces,
different systems and parts of systems. The tree structure can be used for
navigation through the system.
All systems connected to BOS platform can be accessed through the same
graphical User Interface. The User Interface must be available as a Java based
client application, which can be installed to unlimited number of remote
computers or laptops. The client software shall allow for remote Internet usage of
several sites using the same application.
For local and remote web usage, BOS platform installation shall include an
embedded web server, which provides information for users accessing the
system with a standard web browser.
8.3
8.4
Graphical Pages
All monitored data shall be displayed on the graphical pages of the User
Interface. It shall be possible to display all kinds of data (analogue, digital, soft
points) simultaneously.
LONIX LTD
www.lonix.com
Teollisuuskatu 33
FI-00510 Helsinki, Finland
VAT 1043054-9
Trade Reg.No. 678.356
IBMS Specification
Lonix Ltd Finland
21 (23)
All changes made by the operator (e.g. set point changes) shall be logged and
identified by both operator name and time stamp. All real-time data shall be
integrated with schematic view of the system and displayed on graphical pages
to enable easy and efficient monitoring of all systems in the building.
The User Interface shall include a template and symbol library that can be used
in creation of system schematics and graphical pages. The library shall include a
variety of components, including labels, static images, dynamic images and link
buttons.
It shall be possible to use bitmap images (jpeg, gif, png, bmp) as background
images of the system, e.g. floor plan views of system views. Graphical objects
can be arranged in relation with each other (bring front, send back).
Graphical pages shall be arranged as a tree structure. Links shall be created
between the pages to ensure easy and fast access to all needed systems during
the operation.
Functional components shall be attached with a dialogue, which provides for a
more detailed view to the controlled item and allows for changing related
parameters in a separate dialogue window.
It shall be possible to launch applications (such as Microsoft Word, Excel, custom
help files or any third party applications) from a graphical display. If supported by
the application, it shall be possible to launch the application with a specified file
opened within the launched application.
8.5
Alarms
The BOS platform shall include an alarm handling mechanism for connected
systems.
Alarms shall be displayed in chronological order on the Alarm lists. In addition, it
shall be possible to define an optional audible annunciation with user selectable
audio file. Alarming points can also include operator instructions as free-form
text. Operator can acknowledge alarms either one by one or several at one time.
Alarm lists shall be shown as separate tabs, including Active Alarms, Handled by
Me, Handled by Others and Acknowledged Alarms. The operator can accept an
alarm into his/her handling process, and the alarm is then removed from the main
list of Active Alarms.
The status of alarms shall be indicated with the following colors.
LONIX LTD
www.lonix.com
Teollisuuskatu 33
FI-00510 Helsinki, Finland
VAT 1043054-9
Trade Reg.No. 678.356
IBMS Specification
Lonix Ltd Finland
22 (23)
Alarm list shall include also the Alarm History Browser feature, which enables
queries to system wide alarm database covering all present and past alarms.
This feature can be used for trouble-shooting and auditing.
The Alarm list shall include an advanced linking feature. Each alarming point
shall be automatically equipped with a link to guide the operator straight into the
alarming point in any of the graphical views. The alarming point shall be
temporarily highlighted to guide the user to the correct point on the graphical
view.
8.6
Trending
The BOS platform shall provide a trending view containing multiple trends on the
same graph. The user can define the points to be trended and the trending
interval. Analogue values shall be shown as line graphs. Discrete and on/off
values shall be shown as bars.
The user can define which of the trended points are shown in the trending view. It
shall be possible to export the trend view as CSV file for utilization by external
applications.
The trend view shall enable zooming to enable precise investigation. The visible
period shall be possible to select freely. Shortcut buttons shall be also available
to select predefined periods, e.g. 1h, 12h, 24h. Each line graphs shall be
distinguished with colors.
8.7
Event Logs
Event log shall store all control events that are initiated from the graphical User
Interface by the operator. Each log event shall include event time, user name,
controlled point and value.
It shall be possible to export event logs as CSV file for utilization by external
applications.
The log shall also include a link to the controlled point to guide the operator
straight into the point in any of the graphical views.
8.8
LONIX LTD
www.lonix.com
Teollisuuskatu 33
FI-00510 Helsinki, Finland
VAT 1043054-9
Trade Reg.No. 678.356
IBMS Specification
Lonix Ltd Finland
8.9
23 (23)
------END OF SECTION------
LONIX LTD
www.lonix.com
Teollisuuskatu 33
FI-00510 Helsinki, Finland
VAT 1043054-9
Trade Reg.No. 678.356