Security & technology
Software solutions
Systems integration and customer-counting solutions.
A single site usually runs several independent systems at once: video surveillance, access control, an intruder alarm and counters, each with its own program and its own password. The job of the software layer is to bring them into one interface, where events line up on a single timeline and the archive is searched from one place. Customer counting is a strand of its own: a sensor or a camera at the entrance turns a passage into a number, and those numbers build a picture of hourly and daily load.
Each of those systems keeps something to itself. The camera archive sits behind its own password, the access controller holds the card database inside it, and the intruder panel often offers nothing to the outside but a dry contact. So the first question is what the equipment already installed will give out: an open protocol, an SDK or a documented API, and that is settled by looking at the devices on the site, not by reading a catalogue. Three things then have to be reconciled: the clocks, because systems that disagree on the time write one event into the log at two different moments; the naming, because the same door is called two different things in two programs; and the person, who is a card number in one system and a face in another. Server capacity, storage and network segmentation are calculated against the number of devices and the retention period. Two symptoms give away an integration nobody planned: the counter cannot separate people who walk in as a group, and user rights are not divided, so everyone sees everything.
The person on duty looks at one screen instead of four: a door opening, an alarm signal and the frame from that same second sit in one window, with no switching between programs. The reports are built from the same place, load per entrance, peak hours, access records, and that data is what decides where staff are needed and which entrance is actually used. A report is worth exactly as much as its source: if the counter is out of adjustment or a door sensor is disconnected, a number still gets written, only the wrong one. The stock of cameras and controllers changes over the years, so the integration has to rest on interfaces rather than on the quirks of one model, and replacing a single device should not pull the whole picture apart.
What it covers
- Custom software solutions
- Integration with existing systems
- Customer counting and analytics
- Reporting tools
- Support and updates
Where it applies
- Retail chains whose branches are run from one centre
- Shopping centres that measure footfall by entrance
- Business centres with several tenants
- Hotels with several blocks and one duty desk
- Warehouses and plants with several entrances and gates
- University campuses and clinics where one card opens many doors
Standards and regulations
The software is not itself a means of detection: the fire alarm decision stays in a certified panel built to EN 54 and NFPA 72, and the integrated interface only displays it and writes it to the log. On the video side the EN standards for video surveillance systems apply (the EN 62676 series), which set what image quality a given task calls for and how the recording has to be protected against alteration; on the access side the EN standards for access control apply, which set the level of protection an access point has to reach; and between devices the link rests in practice on ONVIF and OSDP. Personal data is a separate matter: recorded video, entry records and biometric data where such data is used fall under Georgian personal data protection legislation, so retention periods and access rights are fixed at the design stage.
Need a consultation?
Call or write to us. We'll establish which system your site actually needs.
Frequently asked questions
What if the cameras and access control are already installed?
In most cases the existing equipment stays, provided it supports an open protocol or a documented interface. The exact answer comes once the specific models have been looked at, because two generations of the same brand behave differently. If one part of the chain is closed, either a converter is added in front of it or that part alone is replaced and the rest stays.
How does the system count customers and how accurate is it?
Counting is done by a sensor or a camera at the entrance that recognises the direction of travel. Mounting height, viewing angle, lighting and the width of the doorway all affect accuracy, and the most common sources of error are people walking in as a group and someone standing still in the doorway. That is why the system is adjusted on site after installation and its figures are checked against a manual count.
Who can see the recordings and how long is the data kept?
Viewing rights are divided by role: who watches video, who opens the archive, who changes settings, and those actions are themselves written to the log. Retention is set by what the site needs and by personal data legislation, not by the size of the hard disk. Both questions belong at the design stage; otherwise the system has to be rebuilt later.
How much does integrating existing security systems cost?
Two things set the size of the job: how many systems have to be joined, and how open their interfaces are. Two systems with a documented API are connected to each other by configuration; a closed node needs either a converter in front of it or code written for it, and that difference moves the figure more than anything else. So the conversation about money follows a list of the equipment: here the model and its firmware generation decide more than the floor area of the site.
Request a consultation
Fill in the form and we'll get back to you during working hours.