The Multi-Site feature allows for a unified database (including People, Groups, Rules, Schedules, and more) to be assigned to multiple Cloud Nodes in a Customer Account. Each Cloud Node could be located at a single Site or spread across multiple Sites with the shared database. Previously, any changes had to be made to each separate Cloud Node requiring unneeded additional work for customers with multiple installation locations.
Where a Cloud Node is physically located is completely unrestricted with Multi-Site. Different sites with installed Cloud Nodes do not need to be on the same network or connected through other means.
Each Cloud Node is configured within the Customer Dashboard. The discovery of controllers and defining connections works in the same way as before PDK.io 2.0. In addition, each Cloud Node can be configured with the local time zone, ensuring configured rules process at the desired time.
Below are a series of examples of Customers showing Multi-Site in use.
- NovaFlex Marketing has one site with a single Cloud Node. Multi-Site will not affect this Customer.
- Holy Mercy Hospital has one site with over 1000 doors connected to multiple Controllers and Aperio hubs. To handle the processing requirements of the site, there are four Cloud Nodes installed at the site, spreading the doors between each Cloud Node. Multi-Site allows the database to be shared between each Cloud Node and ensures that each Cloud Node can process Access requests easily and allow additional Doors/Devices to be added if needed.
- UltraTech Initiatives has one site with three buildings and three different networks. Each building has its own Cloud Node and Controllers and employees regularly move between each building during the day. Multi-Site will allow the database to be shared between all three Cloud Nodes, with any changes made only having to be entered once.
- Acme Manufacturing has twenty different sites across the United States. Each site has one Cloud Node and a handful of Controllers. Multi-site allows a single database to be applied to all the sites, allowing HR at the main office to control who has access to each site and for executives to use their Credentials at each site without having to be manually added to each Cloud Node.
Comments
0 comments
Please sign in to leave a comment.