Preparing to deploy your access control system - Security Center 5.9

Security Center Administrator Guide 5.9

Applies to
Security Center 5.9
Last updated
Content type
Guides > Administrator guides
Security Center

To make sure that your access control deployment goes smoothly, you need to perform a series of pre-configuration steps.


  1. Have a network diagram showing all public and private networks used within your organization, and their IP address ranges.
    For public networks, you also need the name and public IP address of their proxy servers. Ask your IT department for this information.
  2. Install the following Security Center software components:
    1. Security Center Server software on your main server.
      The main server is the computer hosting the Directory role.
    2. (Optional) Security Center Server software on expansion servers.
      An expansion server is any other server on the system that does not host the Directory role. You can add expansion servers at any time.
    3. Security Center Client software on at least one workstation.
  3. Have a list of partitions (if any).
    Partitions are used to organize your system into manageable subsystems. This is especially important in a multi-tenant environment. If, for example, you are installing one large system in a shopping center or, office tower, you might want to give local administration privileges to the tenants. By using partitions, you can group the tenants so that they can only see and manage the contents of their store or office, but not the others.
  4. Have a list of all known users with their names and responsibilities.
    To save time, identify users who have the same roles and responsibilities, and organize them into user groups.
    NOTE: For large installations, users and user groups can be imported from a Windows Active Directory.
  5. Install all access control units (door controllers and edge readers) on your company’s IP network, and wire them to your doors, all the while collecting the following information:
    • Manufacturer, model, and IP address of each unit.
    • Manufacturer and model of the interface modules connected to each unit.
    • Login credentials (username and password) for each unit.
    • Which access points is each unit or interface module connected to.
    • Are the doors Card-in/Card-out or Card-in/REX-out?
    • Which inputs are connected to the door sensors, REX, and manual stations?
    • Which outputs are connected to the door locks, buzzers, our push buttons?
    Tip: A site map or floor plan showing door, elevator, controller and reader locations would be helpful.
  6. Have a list of secured areas with their perimeter doors where access is controlled.
  7. Have a list of all known cardholders (and cardholder groups where applicable).
    Cardholders are people who have physical access to the monitored site.
  8. Have a list of available credentials with their facility codes and card numbers.
  9. Have a list (and details) of all required schedules (office hours, holidays, and so on).
  10. Have a list (and details) of all required access rules (who is allowed where and when).
  11. If you are integrating Omnicast™, have a list indicating which cameras will be associated with which access points (door side and elevator floors).
    NOTE: A camera can be associated with more than one door, and vice versa.