suppliers:hvac.io:vigilia
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
suppliers:hvac.io:vigilia [2015/11/10 17:24] – [API] frozenlock | suppliers:hvac.io:vigilia [2020/09/30 22:09] (current) – old revision restored (2018/06/08 18:45) frozenlock | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | |||
====== Vigilia ====== | ====== Vigilia ====== | ||
Line 6: | Line 7: | ||
---- | ---- | ||
- | |||
[[https:// | [[https:// | ||
Line 16: | Line 16: | ||
**[[https:// | **[[https:// | ||
- | ===== Installation ===== | + | ====== Installation |
- | ==== Server Installation (Optional) ==== | + | The server installation is only required if you want to host your own Vigilia server. |
- | This is only if you want to host your own Vigilia server. | + | For most cases, you can simply use those provided by [[https:// |
- | Otherwise, you can simply use those provided by [[https:// | + | |
- | [[.: | + | * [[.: |
+ | * [[.: | ||
- | ==== Recording a BACnet Network ==== | ||
- | [[.: | + | ====== Supported Network Configurations ====== |
+ | Vigilia supports multiple VLANs and completely detaches 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 A === | |
- | ===== 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. | + | |
- | + | ||
- | {{ : | + | |
- | ==== Type A ==== | + | |
Type A is used to maximize shareability and allows multiple BACnet networks to send their data to a central Vigilia server. | Type A is used to maximize shareability and allows multiple BACnet networks to send their data to a central Vigilia server. | ||
Line 47: | Line 41: | ||
- | ==== Type B ==== | + | === 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, | 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, | ||
Line 54: | Line 48: | ||
- | ==== Type C ==== | + | === Type C === |
Type C is similar to type B, except that it isn't accessible by the Internet. Only users from within the | Type C is similar to type B, except that it isn't accessible by the Internet. Only users from within the | ||
Line 61: | Line 55: | ||
- | ===== API ===== | + | ====== API ====== |
For an example application, | For an example application, | ||
Line 75: | Line 69: | ||
</ | </ | ||
- | Otherwise, take a look at https:// | + | Otherwise, take a look at https:// |
suppliers/hvac.io/vigilia.1447176240.txt.gz · Last modified: 2015/11/10 12:24 (external edit)