Introduction


OPC Interface Server will communicate with CC Command Center via MSMQ message queue. OPC Server able to examine BTEPS  door point status and event in real time. Using standard OPC protocol, BTEPS able to transfer information to 3rd party system and setup the data transfer interval.
    
OPC Server able to provide the following BTEPS system information:
(1) Door Status include door open, always open, always close, arm, intrusion alarm, door left open, door force open, communication failure, door open by time zone.
(2) Controller Status include tamper, main power fail, battery low, communication fail.
(3) Event include access record and alarm event. Access record include card user name, user ID, card ID, date and time, location, event code etc. 

3rd party system will be going through the OPC Server to perform the following remote control operation of the BTEPS door point: remote release, always open, always close and system auto.

Able to setup which door and controller status and event information will be transfer to 3rd party system via OPC interface . At the same time able to perform simulation by manually enter an information and transfer to 3rd party system.


The MS Alarm Monitoring System has integrated a OPC client. By making use of 3rd party OPC interface server, MS is able to receive alarm information from 3rd party system in real time and perform remote control operation of a particular door or all door within an area when receive alarm information. Remote control operation include: remote release, always open, always close and system atuo. This feature is especially useful for fire alarm and CCTV integration on back end system.

Bostex is an OPC Foundation member.