DLink EAS system quickly identifies malfunctioning or broken anti-theft antennas in a retail space and thus considerably reduces stock losses.DKLink EAS can be adapted to operate in a single store as well as a nation-wide chain of stores.
We recommend EAS-monitoring for any sales businesses (stores, convenience stores, department stores, supermarkets, boutiques, discounters, сash&сarry, wholesale & retail businesses, distribution networks, etc.) which have anti-theft systems by any manufacturer.
DLink EAS-monitoring: Functionality
- Online monitoring and deactivation of anti-theft antennas – quick response to emergencies, no down time.
- Event-based analysis over a specified period of time with breakdown by incidents, deactivations, suspicious events (report templates can be customized and are generated by the customer).
- Daily summary of events sent to e-mail or automatically uploaded to FTP server.
- Tracking events within prolonged zero-incident periods, absence of morning system check by the personnel, suspicious incidents occuring after hours.
General descriptionDKLink EAS is designed to perform monitoring of anti-theft systems and its periphery health, generating event notifications in case of failure of the system components, as well as providing analytical information for a required period. The system can operate at levels from local store to nation-wide retail chain.
Working scheme and system objects
Antenna controller (AC) – microcontroller embedded into anti-theft antenna to control its state and transmit events to master controller (MC).
Master controller (MC) – microcontroller embedded into anti-theft antenna or located outside; collects data from AC’s and transfers it to a central server.
For every 32 AC’s 1 MC must be installed. Controller boards are placed inside of anti-theft antennas. Controllers operate via UDP protocol and have their own buffer memory, thus even connection with the server is lost, controllers will store the information in their internal memory and transmit it after restoring the data channel.
Technical hierarchy is as follows: AC – MC – SERVER.
The scheme of the system and the concept of system objects
|The logical structure of the network defined by the system administrator during system configuration. See ''Setting up the Structur'' section of the software manual.|
|The logical hierarchy of system objects is as follows (in decreasing order): Region – City – Store – Master Controller (MC) – Antenna Controller (AC).|
System ports and protocols
By default, the system has several types of events, which depending on the system configuration may have different degrees of importance and may require reaction from operator:
Monitoring functions. The main monitoring screen
The main monitoring screen is used to perform real-time system monitoring. The screen is interactive – the colors of objects (stores, cities and regions) vary depending on the status of child objects. Alarm threshold for every object is customizable and specified at setup stage. Update rate is 5-10 seconds.
The main screen features a scalable interactive map. Objects are located on the map according to their actual address which are entered at system setup stage. The map is optional. The list of objects is interactive. Click on object to view its event log.
Monitoring Functions. Event Log
Event Log is an instrument for online monitoring and event handling in tabular mode.
The log provides real-time information about events taking place in the stores, based on user-defined sorting and filtering, and user rights. Update rate is 5-10 seconds. The event log displays all events in order of occurrence, in a single list. At the top of the log window there are filters that allow a user to set up viewing interval, to be able to view archived events.
Emergency events must be handled by the operators; the operator must supply a comment (see figure below). Emergency event cannot be closed before a solution is provided.
By default, handled events are hidden so the operator sees only pending issues. Events which have been corrected (for example, loss of communication - communication recovery) will not be hidden until the operator will writes a comment. Comments are included into analytical reports.
- Creating custom report templates
Report creation is simple and requires no special skill.
- Data export or auto upload
- Automatic report mailing daily, weekly or monthly
Setting up the system is very simple and divided into two stages: configuring the stores structure, and configuring users and roles.
DKLink EAS presentation. Download.