This article explains how the C•CURE 9000 integration works with FacilityOS and how to configure your C•CURE environment for the integration.
How the integration works
The integration works through the EmergencyOS and SecurityOS modules offered by FacilityOS.
Credential management with SecurityOS
When a visitor signs in or pre-registers, SecurityOS automatically creates a user in C•CURE and assigns access credentials based on your C•CURE access control system configurations. This allows SecurityOS to:
- Issue temporary access credentials to specific visitor types based on configured rules.
- Print QR code credentials on visitor badges to streamline access (additional hardware may be required).
Generate accurate mustering lists in EmergencyOS
EmergencyOS uses activity from C•CURE to identify who is currently on site and generates an accurate mustering list. It does this by:
- Recognizing a cardholder's activity in C•CURE, such as "Access Granted".
- Based on the activity response, EmergencyOS locates the matching "Cardholder" or "Personnel" record in the C•CURE directory.
- Key details, such as first name, last name, email address, and phone number, are extracted to generate a mustering list in EmergencyOS showing who is on site.
Configure your C•CURE environment
Follow the instructions below to integrate your C•CURE environment with FacilityOS.
Important:
C•CURE version 2.9 or later is required.
User permissions
Make sure you have a C•CURE Operator account with the "SYSTEM ALL" privilege. You will need this account to install the Victor web service license and the FacilityOS integration driver. If you need to create a new Operator with this privilege, see Creating an operator.
Victor web service license
The victor Web Service for End Users license must be enabled and installed on your device to allow the use of C•CURE's REST APIs. For more information, see victor Web installation procedures.
Network Configuration
To ensure secure communication between FacilityOS and your C•CURE 9000 instance, allow inbound and outbound traffic over port 443 (HTTPS).
Your firewall must also allow traffic to the following DNS entry: egress-us.facilityos.com
This DNS entry resolves to the IP addresses used by FacilityOS. Make sure your firewall supports DNS resolution and permits traffic over port 443 to this domain so the connection can be established and maintained successfully.
Note:
If your organization requires static IP allow listing, the corresponding IP addresses can be provided by the FacilityOS Support team upon request.
FacilityOS integration driver
The "CC9WS-ILOBBY" licensed option must be enabled. Contact your C•CURE representative for more information.
Once the license is enabled, you must run the injection script for your license option. For more information, see Run Injection Script and Apply License.