Our Solutions

KTC SCADA Package

Event Viewer:

All events of under-control network and also SCADA system are saved in database. Event viewer lists all these events. It has the feature to submit a filtered list of events (by date, station, object, …), sorted list of events and so on. Operators may enter a remark for each event by this application. 

  

Alarm List:

While system is operating, alarm list is active to show occurred alarm. Whenever an alarm occurs, its icon blinks the operator may view the alarm and may acknowledge it by double clicking on the alarm in the alarm list. Filtering column is also supported in the alarm list.    

  

Historical Report and Graph:

There is the capability of generating historical reports by access to database and also having their graphs.

  

Security and Access Levels:

The system is implemented with several layers of security level. Operator name and password, controls the access rights allowed by different personnel.  It is the supervisor’s duty to assign “Level of Accessibility” to every user. So, each user is allowed to access part of the whole data and permitted to respond only to predefined or group tasks. 

 

 Data Gathering Protocols:

SCADA poller, manages data transfer between SCADA center and RTUs/IEDs. It gathers data from processes and hands the data to processing section. It also, sends dispatcher’s command to RTU/IED and monitors the command operation procedure.  Data could be exchanged with RTU/IED through the following standard and industrial protocols:

 • IEC 870-5-101

 • IEC 840-5-104

 • DNP3

 • Hitachi HDLC

 • INDACTIC 2033

 • OPC Client

 • KTC Persia and X-BUS. KTC has developed special protocol for reliable and safe data communication with low overhead. Persia and X-Bus protocols are based on IEC 870-5 frame R-v Mat.

 KTC SCADA is able to communicate with RTUs/IEDs, using multiple protocols simultaneously. 

  

Hierarchical Centers:

The Inter-Center Communicator (ICC) allows data exchange between a local utility control centre and other control centers, other utilities, power pools, regional control centers, and non-utility generators. The exchanged data consist of real-time, including measured values, scheduling data, energy accounting data, and operator messages. This data exchange occurs between one control center’s SCADA/EMS host and another center’s host, often through one or more intervening communication processors. In KTC SCADA the ICC subsystem is responsible for inter-center communication. This subsystem provides communication between homogeneous /heterogeneous SCADA centers. Depending on the center to be communicated with, operational philosophy and assigned functions, ICC’s communication protocols change. ICC can support three types of protocols: KTC-ICCP, LAPB and TASE 2. 

  

Choice of Scripting Languages in Interaction with the System:  

 If the system needs a specific requirement, system engineer has a choice of two high-level scripting languages: VB script and Java script to fulfill needs as well as a tailor-made procedure for KTC SCADA, and last but not least, there exists support for ISAGraf. The System engineer could use any of the languages supported by ISAGraf, programs can be described using any of SFC, FBD, LD, ST or IL graphic or literal languages to make a sequence of events or monitor and control a predefined routine.

 

Remote PC Connection via Dialup or LAN/WAN:

 The concept of using a remote system to control your SCADA system implies that there is ability to monitor, control and maintain the system from any location.  The location transparency feature, in long-term reduces the updating and bug fixing time, guarantees constant maintenance, and consequently reduces the customer support overheads, as well as providing remote monitoring.

  

Database Administration:

 Database editing and generation is done in powerful user interface. User draws process diagrams and defines process parameters in a menu-driven and dialog box supported manner which is also descriptive and easy to use. The data base administrator program generates appropriate data for all subsystems. With this scenario user looks at SCADA system as a whole and individual subsystem’s database becomes transparent to the user.