Migrating from Nedap systems - Best practices - Security Center 5.5 - 5.10

series
Security Center 5.5 - 5.10
revised_modified
2021-07-20
category_custom
Best practices
prodname_custom
Security Center unified platform > Security Center
vrm_version
5.10
5.9
5.8
5.7
5.6
5.5
ContentOps
ContentSolution

Nedap system insights

Use the following information to understand the basics of how Nedap systems work and know what to expect when migrating from Nedap to a Security Center access control system.

NOTE: This information is collected by Genetec™ system integrators and is being updated as required.
Nedap system integrations often require the following features:

Nedap integrations and technology

Before migrating, make sure you understand how Nedap integrations work and what technology they use.

  • Nedap hardware is proprietary. You must replace the board and connectors; the wiring to and from controllers and readers can be left in place.
  • Newer Nedap systems mostly use HID readers. Previous integrations mostly used Nedap readers (RS-485 with AEOS protocol).
  • Nedap cabinets are often integrated with deister or Traka lockers.
  • Nedap uses MIFARE DESFire card technology. DESFire stores keys in the controller.
  • Proximity or 125kHz card technology is no longer frequently used.
  • Nedap controllers have PLC functionality. AEmon's State Monitor works like a PLC controller and uses visual programming.
  • SAM modules inside the door controllers allow for encryption based on ANSSI guidelines.
  • Nedap uses Java on their platform, controllers, and software.

Migration tips for Nedap AEOS Blue devices

The AEOS Blue is Nedap's main line of door controller hardware. The following section provides a brief description of the AEOS Blue devices to assist you in migrating from Nedap to a Security Center access control system.

  • AEOS Blue hardware line supports RS-485 protocol for Nedap readers, and Wiegand protocol.
  • One AP70803 door controller can handle up to 31 AP7000s interfaces, using the RS-485 BUS at a maximum distance of 1200m.
  • Start each system with 1 Synergis™ Cloud Link (SCL).

    Each SCL can have a maximum of 32 Mercury LP1502 controllers, and each LP1502 controller can have a maximum of 64 readers, up to a maximum of 256 readers per SCL. The recommended integration is 4 controllers per SCL.

Device Description Migration tips for RS-485 BUS Migration tips for TCP/IP
AEOS Blue door controller

(AP7803)

IP PoE intelligent controller.
  • Supports up to 32 devices (32 AP7x03 modules on one RS-485 BUS)
  • Provides 2x3 supervised inputs, 2x1 relay outputs, and 2x3 open connectors
  • Communicates peer-to-peer with all other AP7803 devices in the system
  • Supports offline mode
  • Stores up to 1,000,000 events
  • Replace with 1 Mercury LP1502 per AP7803
  • Replace with 1 SCL per 60 readers
AEOS Blue door interface

(AP7003)

Extension module and door interface with the same functionality as AP7803, but without a processing unit.
  • Can be installed up to 1200m from the door controller
  • Replace with MR modules to support the required number of readers and I/O
  • Use up to 32 MR units per 1 LP1502
  • MR52-S3 supports 8 inputs and 6 outputs
  • Replace with:
    • A1601 or A1001 Axis controller, or;
    • MR62e Mercury controller
AEOS Blue I/O interface

(AP7031)

I/O peripheral interface for the AP7803.
  • Provides 12 supervised inputs and 6 relay outputs
  • Can be installed up to 1200m from the door controller
  • Replace with MR16IN and MR16OUT
  • Replace with MR16IN and MR16OUT
Hardware setup for 256 readers Setup that uses 4 AP7803 and 124 AP7003.
  • Use 1 SCL, 4 LP1502, and 124 MR52-S3
  • Supports 512 inputs and 512 outputs because of SCL max capacity; however, physically on all boards, there are 1024 inputs and 760 outputs
  • Use 5 SCL and 128 A1601 or A1001