1.0 Borealis General Questions
|
|
What is Borealis?
|
Borealis is Keri Systems’ cloud-based access control system.
Borealis gives you complete visibility and control of your system from any computer, tablet or mobile device that has a web browser and an active internet connection.
By using Borealis you will not need a local server or dedicated PC, you will not have to install any kind of software and you will never have to do any kind of software updates – but you will always be running the most up-to-date version.
|
What can
|
|
What can Borealis
|
|
Is Borealis easy
|
Yes. Borealis is extremely easy to setup and use. Borealis enhances the Security Application experience by simplifying previously complicated tasks, delivering global accessibility, scalability and convenience.
|
Is there an app that can be used with Borealis? |
No, Borealis is browser-based - but is accessible with any smart device or PC that has an internet connection and has a web browser installed.
|
Can I see a demo
|
A Borealis overview video can be found on the Keri Systems YouTube channel:
https://youtu.be/smo3frrdfyU In addition, you can contact Keri Systems Inside Sales and someone will be more than happy to arrange a remote demonstration of the system features and options. |
What integrations are
|
Borealis integrates with Geokey. Click
here
for further details about this integration.
|
|
|
|
2.0 Borealis Hardware Questions
|
|
Hubs
|
|
Does the hub need to be connected to a DHCP network? |
Yes, the Borealis hub MUST be connected to an internet-enabled
DHCP network. |
Can I use a hub to
|
No, you should not use the hub as a client for administering your system. The hub is only designed as a communication device between the Cloud and the field hardware.
|
Can I use multiple hubs on a Borealis system? |
Yes, multiple hubs are used in Borealis when the total number of doors exceeds 32 or if you will be using different controller types.
|
How does the Borealis hub use a secure
|
The Hub doesn't accept any incoming connections. Communications between the hub and the AWS servers are established over SSL (port 443) via direct https request and SignalR. Not accepting incoming connections and the use SSL encryption are industry standard methods of ensuring internet security.
|
What other security is there on the hub? |
Here is a document that outlines the Borealis system security.
https://help.kerisys.com/portal/en/kb/articles/borealis-security |
How and when is the hub updated? |
The hub is automatically updated whenever a new update package is released. Within Borealis, if you click on Systems Settings from the main menu on the left you will see the 'Hub Update Period' settings. This is the times between which the hub will be scheduled to update.
|
How long does it take for the hub to initially update? |
After successfully claiming a hub it will take approximately 3-5 minutes for the hub to complete its initial update. Once the hub status shows 'Update Completed' click the hub's name and you will see timestamps of when the hub received its initial update.
|
If the network has all controllers on the same subnet, do I need more than one hub? |
If all controllers are of the same type and are on the same network as the hub then you would only need one hub. More than one hub will only be required in this scenario if the system exceeds more than 32 doors.
|
What is the correct method for powering-down the hub? |
If the hub needs to be down-powered this should be done via a single press of the power-switch.
Note:
You do NOT need to (and should not) keep the power-switch held down.
|
Why would a claimed hub keep going offline then back online? |
If the hub has been successfully claimed but keeps going online/offline this indicates that the hub subscription has not been paid for. Contact Keri Systems Sales if you need to process a Cloud subscription payment.
|
Controllers
|
|
What controller types are supported?
|
|
Will Real Mercury (EP and LP controllers and MR modules) be supported in Borealis? |
Yes, support for Mercury's EP and LP controller types (plus all supporting MR sub-modules) will be included in a future Borealis release.
|
Will PXL and Entraguard controllers
|
Yes, as with the Mercury hardware support, PXL and Entraguard support will be included in a future Borealis release.
|
Can a USB-Serial Adapter be used to | No, in Borealis the only supported communication method to a PXL controller is via Ethernet (so a LAN-520 module is required) which connects to the primary PXL (controller number 1). |
Will the controllers still function if they go offline? (i.e granting access and unlock the door) |
Yes, once the controllers have been sent their access control database, they will continue to provide full-functionality even even the controller goes offline.
|
What can't I do if the controller goes offline? |
The only system functions you will not be able to do is retrieve the controller status, lock or unlock the doors from the user interface or view system events from the controller. When the controller is back online these functions will resume and the buffered events will also be collected from the controller's memory (for running reports on the system activity while the controller was offline).
|
Do the controllers need to be connected to a DHCP network? |
Yes, the controllers should be on the same DHCP network as the Borealis hub. However... it is only the NXT-MSC controllers that use a DHCP address. The Standard NXT controllers, in their factory state, will not have an IP address and so a static IP address will need to be assigned using the Scan feature. The Standard NXT controller's IP address will need to be on the same range as the hub's IP address (found in the hub details which are shown when you click the hub's name on the hubs page).
|
Does Borealis support different controller types on the same system? |
Yes you can use different controller types on the same system but each controller type will require its own hub. (One hub for NXT controllers and a second hub for NXT-MSC controllers).
|
Can I upgrade the firmware on a controller? |
Yes, the ability to update the controller firmware is supported for both NXT and NXT-MSC controller types. |
If I delete a controller will the events be lost? |
No. If a controller is deleted you will still be able to retrieve the event history from the controller. |
What happens if a controller needs to be replaced? |
In the unlikely event that a controller ever needs to be replaced, there is a defined replacement procedure in the user interface that means the replacement controller will function the same as the original. You will not need to add the replacement controller's readers back into the access rights. Once the replacement controller comes online you will just need to do a memory reset.
|
Readers |
|
What reader types are supported? |
|
What is the maximum number of
|
The maximum number of standard readers is 32
per hub
.
Note: NXT Exit readers (supported on the NXT-MSC controllers are NOT included in this count). If your system requires in excess of 32 readers you would need to add an additional hub. Each hub supports up to 32 door and if every door has an NXT Entry and an NXT Exit reader then up to 64 readers can be used. An additional hub is also required if the controllers will be on different subnets or in different world timezones. |
Can keypads be used in Borealis? |
Yes, Wiegand keypads (such as the P-640H) can be used for card-only or Card + PIN functions on Standard NXT controllers or NXT-MSC controllers. In addition... if you have Card + PIN setup in Doors.NET a database conversion will include the reader and cardholder Card + PIN settings.
|
Can BioSync fingerprint readers be | Yes, the BioSync readers are a type of Wiegand reader so can be used in Borealis. |
Are OSDP readers supported in Borealis? |
Yes, you can use a single OSDP reader per controller bus (supported with NXT-MSC and True Mercury controller types. |
|
Yes.
NXT Exit readers are fully supported in Borealis when using NXT-MSC controllers. For further details about setting up an NXT Exit reader, click
here:
|
Modules
|
|
Can 4x4 modules be used in Borealis? |
Yes, NXT 4x4 modules can be used in Borealis but currently the functionality is restricted to only allowing outputs to be controlled. Very soon you will also be able to use basic I/O control and you will also be able to configure door functions on the 4x4 modules (such as a RTE input, door contact and door strike). |
|
No, the NXT GIOX module is now an obsolete product and can only be used in on an existing system with a supported version of Doors.NET. |
Can Mercury MR16 modules be used in Borealis |
Yes, Borealis supports the use of Series 2 and Series 3 MR16IN and MR16OUT modules. They can be used with Mercury EP controller and LP controllers and also with Keri's NXT-MSC controllers.
|
3.0 Borealis Software Questions
|
|
How do I create a new system? |
Currently all new systems are setup by Keri Systems. Once you have registered a new account simply give Keri sales a call and a new Borealis system will be created. You will then be able to login and claim the system hub and then the controllers.
|
|
If all controllers are of the same type and located in the same world time zone then you can add hubs to the same site. A separate site should be added if the system has different controller types or if the controllers are in different geographical locations.
|
What is the maximum number
|
|
Are multiple credentials
|
|
Does Borealis support
|
Yes Borealis supports MIFARE credentials – reading the Card Serial Number (CSN). It does not support the reading of MIFARE sectors. Desfire EV1 and EV2 CSN can also be used. The difference between Mifare classic and EV1 & EV2 is that the later has encryption and the CNS is harder to clone.
|
Does Borealis have custom Wiegand
|
There are several popular credential formats available by default, as well as the default supported credential formats. Including: HID 34 and 37 bits, Mifare 32 and 56 bits CSN, HID corporate 1000 formats, RAW wiegand format and 26-bit Wiegand H10301.
|
Does Borealis allow custom Wiegand
|
There are several popular credential formats available by default, as well as the default supported credential formats. If you need to add a new format that isn't currently added to Borealis you will need to forward the credential details to Keri Systems tech support to evaluate and add the format. There is a form on the kerisys.com website that allows you to submit details of a new Wiegand format:
|
How do I enroll NXT, Keri MS or 26-bit Wiegand credentials into Borealis? |
The following document on the knowledge base explains how to enroll cardholders and credentials into Borealis. Use the knowledge base to learn more about other administrative functions.
|
How do I enroll
|
If you are enrolling MIFARE credentials and you do not know the Card Serial Number (CSN) you should first present the credential to one of the readers on the system. The unique CSN will then be displayed in live events. This unique number should be enrolled as the imprint and the select format should be ‘RAW’. |
Is presentation enrollment or block
|
Currently all credentials must be enrolled into Borealis using the manual enrollment method.
|
Is there a cardholder or credential
|
Yes Borealis does have a credential mass edit feature - this allows you to assign the same access group to a selected group of credentials.
|
Why are access groups referred to as access rights in Borealis?
|
There is a difference in how
access settings are handled in Borealis versus DNET. Access Group in
DNET covers all controller types with the same schedule. Access Rights
in Borealis is on a per site basis with different schedules and hardware
per site. We chose to use Access Rights because as the access
control industry evolves, so too does the terminology. The change to
using access rights is reflective of what is nowadays most commonly used
in the industry to reflect when and where cardholders have the rights
to gain access.
|
What are the client
|
The client PC requirements for using Borealis are as follows:
Desktop web browser
(Version must be no older than three years):
Mobile device web
browser (Version must be no older than three years):
|
Is an organization needed for setting up a system? |
An organization is required for all companies that are tax exempt (as are most installation companies) and organization is also useful for grouping multiple sites. However, creating an organization is NOT a requirement for setting up a new system.
|
How will I know when my organization has been approved? |
You will receive an e-mail to notify you when your new organization has been approved. This notification should be received within 1 working day.
|
Can I create a new system before the organization is approved? |
No, if you will be using an organization then you MUST wait for the organization to be approved before you setup a new system.
|
How do I update my system? |
There is no manual updating required for your Borealis system. The hub contains a built-in, automatic updating service that will retrieve and install all new system updates as and when they are required. |
How do I Backup a Borealis System? |
There is no need to. One of the main benefits of a cloud based-access control system is that the system a database is backed-up constantly and is stored safely and securely and backed-up multiple times.
|
How many concurrent system operators are allowed? |
Borealis supports all registered and added operators to be logged in to a system concurrently (as long as they are all logged-in with different accounts). There is no additional charge for multiple system operators.
|
Is it possible to edit the dashboard in the new user interface? |
No, currently it is not possible to custom-design the layout of the dashboard in the new user interface - but this is scheduled to be part of a future release. |
How do I find out more about administering a Borealis system? |
The best place to begin is on Keri's knowledge base:
|
|
|
4.0 Borealis Conversion Questions
|
|
Can I convert a Doors32
|
No. You cannot do a direct database conversion from Doors32 to Borealis (because Borealis does not currently support the PXL controllers). However, if you will be upgrading the PXL controllers to NXT or NXT-MSC then there is the option of retaining the cardholder, access groups, time schedules and holiday information by first upgrading the database to Doors.NET and then replacing the hardware - allowing you then to upgrade the system to Borealis.
|
Can I convert a Doors.NET system to Borealis? |
Yes, there is a conversion tool that allows you to quickly and easily convert a Doors.NET database over to a new Borealis system. The step-by-step guide can be found here:
https://help.kerisys.com/portal/en/kb/articles/doors-net-to-borealis-database-conversion-procedure
Note:
Borealis does not currently support each and every feature and settings that is in Doors.NET (mainly due to the length of time Doors.NET has been in development) - features such as Photo ID, Global and Local Linkage and Emergency Global Lock and Unlock. So please check with Keri's sales team if you are unsure which system features are currently in use.
|
What is included in a database import from Doors.NET to Borealis? |
The database import will include the cardholder names and assigned credentials, PIN numbers (if Card + PIN is used), active/inactive card status and temp card settings - plus access group names and assignments (as long as the cardholders in Doors.NET are not assigned more than 1 access group). The database import also includes controllers and controller settings, readers and reader settings, time schedules, access groups, holidays and custom credential formats.
|
How long is the access control system down during a Doors.NET-to-Borealis conversion? |
During a Doors.NET to Borealis conversion the actual system downtime is exceptionally minimal (a few minutes at the most). This is aided by the fact that the controllers are fully functional even when they are not connected to Doors.NET or the Borealis Cloud application.
|
What is the correct procedure for upgrading a Doors.NET system to Borealis |
Here is a video on our YouTube channel that explains the steps that are taken when converting a Doors.NET system to Borealis.
|
|
|