SIRAM: Integration Protocols (OCR)
EASY INTEGRATION
SIRAM OCR is the software that performs the automatic recognition of the number plates for each capture unit or camera.
In the event of it being integrated with external management applications, SIRAM OCR allows the exchange of information necessary for the synchronisation of both systems and can manage information from the integrated system or function as a simple number plate reader, so that all the management rests with the external application.
The main types of integrated software are:
- Car Park Management software.
- Security Access Points Control software.
- Other software (scales, video supervision, etc.).
The tools generated for the integration of the systems allow the integrated system to have all the data
collected by the number plate recognition system, such as number plate, images of the vehicles, the
date and time or lane of access, etc.
COMMUNICATIONS PROTOCOL CHARACTERISTICS
Communication between the different applications of the SIRAM Suite is performed through TCP/IP sockets, so the SIRAM OCR communication with external applications is also performed in the same way.
The communications protocol includes the commands required to perform the number plate request or control the relays of the control electronics. This allows SIRAM to become another peripheral device in the system.
The OCR number plate reading process can be initiated by the external application or by the suite’s control electronics (Siram Conex). In view of the above architecture, TWO possible scenarios can be described: Scenario 1 and Scenario 3.
INTEGRATION SCENARIOS
COMMUNICATIONS PROTOCOL
In all the integration scenarios there is a phase of request for reading the number plate and one of response by the OCR.
Request:
In Scenario 1, the external application is connected as TCP/IP client through a configurable port for each SIRAM and sends the trigger command.
In scenario 3, the request is done by the SIRAM CTRL after the activation of the alarm input of the SIRAM Conex.
Response:
Both in Scenario 1 and in Scenario 3, the SIRAM OCR responds with a message incorporating the following information:
- Number plate: this is the OCR of the number plate. There are no spaces or dashes.
- Lane: Identifies the lane or capture unit through which the OCR has been performed.
- Date: Day, month and year of capture.
- Hour: Hour, minute and second of capture.
- JPG Path: path where the JPG is saved. – JPG Length: this is the length of the JPG in bytes. – JPG Image, although its sending is configurable.
It is possible to configure the SIRAM to not send or not save the JPG.
CAR PARK INTEGRATION
When SIRAM is integrated with the different car park management systems, the trigger for the OCR is carried out by the application for the parking automation system, so in most cases neither the Conex electronics nor the management software are needed. Some of the parking management systems with which SIRAM can be integrated are as follows: AMANO, APD COLOMBIA, CAME, CBL, COSIENSA, DATAPARK, EGLOBALT, HUB PARKING, JADEPARK, NEPOS, PARKARE, PROSIGA, SKIDATA, TAU, XEROX
SECURITY INTEGRATION
The integration of SIRAM with the different access control systems or electronic security management platforms is done in many ways, and information can be sent via TCP/IP, RS232 or Wiegand.
Some of the integrations available are described below.
IMPORTANT: Before making any proposals for SIRAM integrated into any of the systems set out below, you must contact the manufacturer of the Access Control System to verify the elements needed in your system.
SIRAM ARQUERO
In this integration OCR activation takes place through the detecting of the presence of a vehicle through a loop connected to the Conex electronics. Once the OCR has been performed, the number plate data is sent to the Arquero software through TCP/IP.
SIRAM DESICO
In this integration OCR activation takes place through the detecting of the presence of a vehicle through a loop connected to the Conex electronics. Once the OCR has been performed, the number plate data is sent to the Desico software through TCP/IP.
SIRAM LENEL
In the integration with Lenel, the activation of the OCR is performed through the Conex electronics. Once the OCR is performed and the number plate number is obtained, the query is performed in Onguard to obtain the BadgeID or ScanID number associated with it. Finally, the ScanID or BadgeID data is sent to the corresponding reader in Wiegand format.
SIRAM DORLET
In this integration OCR activation takes place through the detecting of the presence of a vehicle through a loop connected to the Conex electronics. Once the OCR has been performed, the number plate data is sent to the Dorlet CPU AS/3-IP or UCA ASD/2 or ASD/4 through TCP/IP.
SIRAM PAXTON
In the integration with Paxton, the activation of the OCR is performed through the Conex electronics. Once the OCR is performed and the number plate number is obtained, a conversion to Wiegand 26 bits format is performed and it is sent to the Paxton controller.
SIRAM PRIMION DIGITEK
In this integration it is the Primion Digitek platform that performs the OCR activation. Once the OCR has been performed and the number plate number obtained, this data is sent to Primion Digitek software though TCP/IP.
SIRAM SPEC
In the integration with Spec, the activation of the OCR is performed through the Conex electronics. Once the OCR is performed and the number plate number is obtained, a conversion to RS232 is performed and it is sent to the Spec controller.
SIRAM WIEGAND
In the integration with Wiegand, the activation of the OCR is performed through the Co- nex electronics. Once the OCR is performed and the number plate number is obtained, a conversion to Wiegand 26 bits format is performed and it is sent to the controller of the access control system.
SIRAM AVIGILON
In the integration with Avigilon (ACM), the activation of the OCR is performed through the Conex electronics. Once the OCR is performed and the number plate number is obtained, a conversion to Wiegand 26 bits format is performed and it is sent to the controller of Avigilon (ACM).
COMMUNICATIONS PROTOCOL CHARACTERISTICS
Communication between the different applications of the SIRAM Suite is performed through TCP/IP sockets, so the SIRAM OCR communication with external applications is also performed in the same way.
The communications protocol includes the commands required to perform the number plate request or control the relays of the control electronics. This allows SIRAM to become another peripheral device in the system.
The OCR number plate reading process can be initiated by the external application or by the suite’s control electronics (Siram Conex). In view of the above architecture, TWO possible scenarios can be described: Scenario 1 and Scenario 3.
COMMUNICATIONS PROTOCOL
In all the integration scenarios there is a phase of request for reading the number plate and one of response by the OCR.
Request: In Scenario 1, the external application is connected as TCP/IP client through a configurable port for each SIRAM and sends the trigger command.
Response: Both in Scenario 1 and in Scenario 3, the SIRAM OCR responds with a message incorporating the following information:
- Number plate: this is the OCR of the number plate. There are no spaces or dashes.
- Lane: Identifies the lane or capture unit through which the OCR has been performed.
- Date: Day, month and year of capture.
- Hour: Hour, minute and second of capture.
- JPG Path: path where the JPG is saved. – JPG Length: this is the length of the JPG in bytes. – JPG Image, although its sending is configurable.
It is possible to configure the SIRAM to not send or not save the JPG.
Do you want to know more?
Give us your details and we will call you: