Motorola V186 - Cell Phone - GSM System Planner Manual page 150

All the M-OPC components run on a standard PC hardware platform that supports both
MS Windows 2000 Pro and MS Windows XP Pro.
The M-OPC solution uses a standard client/server architecture. The Control center
components include Client(s) (SCADA software or other applications), M OPC server,
MDLC driver and Field Interface Unit –FIU (ACE3600, MOSCAD or MOSCAD-L
CPU). The FIU provides MDLC networking and various media connectivity to the RTUs.
The M-OPC offers the following functionality:
• Standard interface between ACE3600 and MOSCAD family RTUs and many
control center SCADA managers.
• Support of special features unique to Motorola RTUs.
• Support of the MDLC protocol and all Motorola RTU types, i.e., ACE3600,
MOSCAD, MOSCAD-L and MOSCAD-M.
The M-OPC server uses OPC Data Access (DA) V2.05. The server enables the clients to
organize the field data according to the OPC logical object model and read/write data
either synchronously or asynchronously. It automatically updates clients when new
groups are created and also enables
SCADA clients to retrieve new groups
without having to restart the server.
The server uses the MDLC driver to:
• Poll the RTU databases
• Send commands to the RTUs
• Receive data bursts from the
RTUs
The server scheduler is responsible for
scheduling the polling of RTU data.
Data polling can be performed in
periodic intervals or upon specific
requests from clients. Schedules are
set using the M-OPC Monitoring and
Setup Tool. The scheduler optimizes
the communications with the RTUs to
minimize the MDLC network
communication load. This feature is
extremely important in radio
networks.
The server holds the information
received from the RTUs in a cache database. The cache reflects the latest value of the
data as well as its quality and the server time-stamp.
SCADA System Components
146