suppliers:hvac.io:vigilia
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
suppliers:hvac.io:vigilia [2020/09/30 17:09] – old revision restored (2020/09/20 21:27) 148.251.69.139 | suppliers:hvac.io:vigilia [2020/09/30 17:10] – old revision restored (2020/09/20 21:27) 148.251.69.139 | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | |||
====== Vigilia ====== | ====== Vigilia ====== | ||
Line 6: | Line 7: | ||
---- | ---- | ||
- | |||
[[https:// | [[https:// | ||
Line 15: | Line 15: | ||
**[[https:// | **[[https:// | ||
- | ===== Supported Network Configurations ===== | ||
- | 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. | ||
+ | {{INLINETOC}} | ||
+ | ====== Installation ====== | ||
- | ==== Type A ==== | + | ===== Server Installation (Optional) ===== |
- | Type A is used to maximize shareability and allows multiple BACnet networks to send their data to a central | + | This is only if you want to host your own Vigilia server. |
+ | Otherwise, you can simply use those provided by [[https:// | ||
- | This configuration can be used to offer a Vigilia service, like the one offered by [[https:// | + | [[.:vigilia: |
- | The easiest way to describe this configuration would be "in the cloud" | + | ===== Recording a BACnet Network ===== |
+ | [[.: | ||
- | ==== 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, | + | ---- |
- | The Vigilia server is still available via the Internet to allow users to see the historical data. | ||
+ | ====== Supported Network Configurations ====== | ||
- | ==== Type C ==== | + | 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. |
- | 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. | + | ===== Type A ===== |
+ | Type A is used to maximize shareability and allows multiple BACnet networks to send their data to a central Vigilia server. | ||
+ | This configuration can be used to offer a Vigilia service, like the one offered by [[https:// | ||
- | ---- | + | The easiest way to describe this configuration would be "in the cloud" |
- | {{ : | + | ===== Type B ===== |
- | ===== Installation ===== | + | 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, |
- | **//(For the upcoming version of Vigilia | + | The Vigilia |
+ | |||
+ | |||
+ | ===== 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. | ||
- | [[.: | ||
+ | ====== API ====== | ||
+ | For an example application, | ||
- | ===== API ===== | ||
Developers can take a look at the [[http:// | Developers can take a look at the [[http:// | ||
Line 73: | Line 82: | ||
- | TODO: DOCS |
suppliers/hvac.io/vigilia.txt · Last modified: 2020/09/30 22:09 by frozenlock