Differences

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

--- suppliers:hvac.io:vigilia [2015/08/31 21:04] – [Type C] frozenlock
+++ suppliers:hvac.io:vigilia [2020/09/30 17:11] – old revision restored (2020/09/20 21:27) 148.251.69.139
@@ Line 1: / Line 1: @@
+{{INLINETOC}}
 ====== Vigilia ======
@@ Line 9: / Line 11: @@
 [[https://hvac.io/services/vigilia|Vigilia]] allows you to record BACnet networks and send the data back to remote servers.
+The logs of your HVAC systems are then available on the web interface, or directly through the API.
+Vigilia is usually sold as a service, but self-hosted licenses are also available.
-Vigilia is usually sold as a service, but self-hosted license are also available.
+**[[https://vigilia.hvac.io/s/vo|Online Example]].**
-===== Supported Network Configurations =====
+====== Installation ======
-Vigilia supports multiple VLANs and completely detach the control networks from the recorded data. This separation allows users to freely share the historical data with everyone without ever putting the control network at risk.
+===== Server Installation (Optional) =====
+This is only if you want to host your own Vigilia server.
+Otherwise, you can simply use those provided by [[https://HVAC.IO|HVAC.IO]].
-==== Type A ====
+[[.:vigilia:installation|Server Installation]]
-Type A is used to maximize shareability and allows multiple BACnet networks to send their data to a central Vigilia server.
+===== Recording a BACnet Network =====
-This configuration can be used to offer a Vigilia service, like the one offered by [[https://hvac.io/services/vigilia|HVAC.IO]].
+[[.:vigilia:recording|Recording]]
-The easiest way to describe this configuration would be "in the cloud".
+----
-==== Type B ====
-Type B is defined as the Vigilia server being installed within the enterprise network. This allows whoever is in charge of the BACnet network to also be in complete control of all the recorded data. (Building manager, IT departement, etc...)
+====== Supported Network Configurations ======
-The Vigilia server is still available via the Internet to allow users to see the historical data.
+Vigilia supports multiple VLANs and completely detach the control networks from the recorded data. This separation allows users to freely share the historical data with everyone without ever putting the control network at risk.
+{{ :suppliers:hvac.io:vigilia:vigilia-networks.png?700 |Vigilia Network Configurations}}
+===== Type A =====
-==== Type C ====
+Type A is used to maximize shareability and allows multiple BACnet networks to send their data to a central Vigilia server.
-Type C is similar to type B, except that it isn't accessible by the Internet. Only users from within the
+This configuration can be used to offer a Vigilia service, like the one offered by [[https://hvac.io/services/vigilia|HVAC.IO]].
-enterprise network will be able to see the data.
+The easiest way to describe this configuration would be "in the cloud".
-----
+===== Type B =====
+Type B is defined as the Vigilia server being installed within the enterprise network. This allows whoever is in charge of the BACnet network to also be in complete control of all the recorded data. (Building manager, IT departement, etc...)
-{{ :suppliers:hvac.io:vigilia:vigilia-networks.png?700 |Vigilia Network Configurations}}
+The Vigilia server is still available via the Internet to allow users to see the historical data.
-===== Installation =====
-**//(For the upcoming version of Vigilia - not yet active)//**
+===== Type C =====
+Type C is similar to type B, except that it isn't accessible by the Internet. Only users from within the
+enterprise network will be able to see the data.
-[[.:vigilia:installation|Installation]]
+====== API ======
+For an example application, see [[http://blog.hvac.io/2015/10/20/fun-with-vigilias-api/|Fun with Vigilia's API]]
-===== API =====
 Developers can take a look at the [[http://swagger.io|Swagger]] representation of the RESTful API.
@@ Line 72: / Line 82: @@
-TODO: DOCS