Monitoring automation systems is a crucial aspect of electrical engineering, especially in Kenya's growing industrial and infrastructure sectors. Effective monitoring ensures system reliability, safety, and optimal performance of automated electrical processes. This chapter addresses the tools and techniques used to monitor and diagnose automation systems, enabling engineers to anticipate faults, optimize maintenance, and enhance system longevity.

5.1 Monitoring and Diagnostic Tools

Monitoring and diagnostic tools are essential for maintaining the health and performance of electrical automation systems. Their application in industries such as manufacturing plants, power distribution networks and water treatment facilities helps reduce downtime and improve operational efficiency.

5.1.1 Meaning

Monitoring and diagnostic tools are the instruments, software and methods used to observe, record and analyse the operational status of automation systems. Monitoring is the continuous or periodic observation of system parameters to detect deviations from normal operation. Diagnostics identifies the causes of faults or inefficiencies within the system.

The distinction between monitoring and diagnostics is significant in practice. Monitoring provides real-time data on variables such as voltage, current, temperature and system states, enabling operators to track performance trends. Diagnostics interprets this data to pinpoint faults such as sensor failures, communication errors or actuator malfunctions. Example: at a water treatment plant, monitoring sensors relay flow rates and pressure levels, while diagnostic software analyses these readings to detect pump wear or valve blockages.

Where infrastructure faces power fluctuations and environmental stresses, these tools help anticipate failures before they escalate into costly breakdowns. Automation engineers rely on them for proactive maintenance and system optimisation.

5.1.2 Purpose

The primary purpose of monitoring and diagnostic tools is to ensure the continuous, safe and efficient operation of electrical automation systems. Monitoring tools show what the system is doing now, and diagnostic tools explain why it is behaving that way. Example: a motor control centre driving conveyors may show a rising motor current on the monitoring screen, and the diagnostic tool then links it to a worn bearing.

Purpose of monitoring tools

• Early fault detection: Monitoring tools detect abnormal conditions such as voltage spikes or temperature rises, allowing corrective action before damage occurs.
• Performance optimisation: By continuously measuring operational parameters, these tools help adjust system settings for maximum efficiency and reduced energy consumption.
• Data logging: They maintain historical records of system performance, which are vital for analysing trends and planning maintenance activities.
• Compliance and safety: Monitoring confirms that the system operates within its safe limits, protecting equipment and personnel from hazards.
• Remote supervision: Many monitoring tools give remote access to system status, which helps oversight of geographically dispersed installations such as unattended water pumping stations.

Purpose of diagnostic tools

• Fault isolation: Diagnostics identify the exact component or subsystem responsible for a failure, minimising troubleshooting time.
• Root cause analysis: They analyse patterns and correlations in data to determine underlying causes of faults, rather than just symptoms.
• Predictive maintenance: Diagnostic tools forecast potential failures by recognising early warning signs, reducing unexpected downtime.
• System health assessment: These tools evaluate the overall condition of the system, guiding decisions on repairs, replacements or upgrades.
• Improved reliability: Through accurate diagnosis, systems keep high reliability, which is critical where uninterrupted standby power changeover automation is needed.

5.1.3 Developing monitoring and diagnostic tools

Developing effective monitoring and diagnostic tools requires a systematic approach that combines hardware capabilities, software algorithms and knowledge of the electrical automation system. Tailoring the tools to local conditions such as dust, humidity, heat and unstable supply is essential for their success. The stages below follow the order in which a development team normally works.

Understanding system requirements

Developers begin by studying the automation system's architecture, critical components and operating parameters. For example, designing tools for a sugar mill's electrical control system requires knowledge of motor loads, conveyor controls and environmental factors such as humidity. The team also records which faults are most costly so that the tool targets them first.

Defining parameters, alarm limits and diagnostic rules

The team lists the variables to be measured, such as motor current, supply voltage, bearing temperature and valve position. For each one, normal ranges and alarm limits are set from equipment ratings and the process needs. Diagnostic rules are then written, for example "high current with low flow suggests a blocked pump".

Hardware selection and integration

Selecting appropriate sensors, data acquisition devices and communication modules is fundamental. Sensors must be robust enough to withstand harsh industrial environments. The devices are connected to a central control system or programmable logic controller (PLC) with minimal electrical interference, using screened cables and correct earthing.

Software development and algorithms

Software development includes creating user interfaces, data processing algorithms and diagnostic models. Algorithms may use threshold-based alerts, statistical analysis or machine learning to interpret sensor data. For instance, the automation of a battery backup system for a control panel could use software that detects battery degradation from falling voltage under load.

Testing and validation

Tools must be tested under real operating conditions to validate accuracy, responsiveness and reliability. This stage identifies calibration needs and software errors. Alarms are deliberately triggered, for example by simulating a high-temperature signal, to confirm that the correct message appears and the correct output operates.

Deployment and maintenance

Successful deployment involves training operators and establishing maintenance schedules for hardware and software. Continuous updates may be needed to adapt to changing system demands or new technology.

Documentation and handover

The developer supplies wiring diagrams, tag lists, alarm descriptions, software backups and operating instructions. This allows other technicians to maintain the tool and restore it quickly after a failure.

5.1.4 Types of monitoring and diagnostic tools

The tools covered here are the human-machine interface (HMI), the data logger and the supervisory control and data acquisition (SCADA) system. They differ in scope: an HMI serves one machine or panel, a data logger records measurements, and SCADA supervises a whole plant or several sites. The table lists their specifications and uses, together with the field devices that supply them with data.

5.1.4.1 HMI

A human-machine interface (HMI) is a panel or screen through which an operator sees the state of a machine or process and sends commands to the PLC. It turns raw controller data into graphics, numbers and messages that can be understood at a glance. Example: on a packaging line, the HMI shows motor running status, conveyor speed and a red alarm banner when a motor overload trips.

Typical monitoring and diagnostic features of an HMI include:

• Process screens: Graphic pages show equipment such as motors, tanks and valves with live values and colour changes for running, stopped or faulted states.
• Alarm display: Active alarms are listed with time, description and priority, so the operator knows which fault to attend to first.
• Alarm history: Past alarms are stored with times, helping a technician see how often a fault recurs and in what order alarms occurred.
• Trend displays: Live graphs of variables such as temperature or current reveal slow drifts that a single reading would hide.
• Operator control and access levels: Start, stop and set-point entries are protected by user levels so that only authorised persons change critical settings.
• Diagnostic pages: Screens showing input and output states and communication status help the technician locate a failed sensor or a broken network link without a laptop.

5.1.4.2 Data logger

A data logger is an electronic device that measures one or more signals at set intervals and stores each reading with its time. It works independently of the plant control system, so it can be connected temporarily to investigate an intermittent fault. Example: an electrician clamps a current sensor on a pump motor supply and records the current for a week to find when overloads occur.

The sampling interval and the recording period decide how much memory is needed:

number of samples = recording time ÷ sampling interval

Recording time = 7 days = 7 × 24 × 3600 s = 604 800 s

Number of samples = 604 800 s ÷ 10 s = 60 480 samples per channel

For 4 channels, readings = 60 480 × 4 = 241 920 readings

Key characteristics when using a data logger for diagnostics:

• Input channels: Analogue inputs accept sensor signals such as 4 to 20 mA, and digital inputs record on and off states, so voltage, current, temperature and contact status can be captured together.
• Sampling interval: A short interval catches brief events such as voltage dips but fills memory quickly. A long interval suits slow changes such as room temperature.
• Time stamping: Each reading carries a date and time, which allows a fault to be matched to a production event or a supply disturbance.
• Power supply: Battery operation allows recording at remote or temporary locations, while mains operation suits long-term installations.
• Triggers and alarms: Many loggers start recording or flag an event when a set limit is crossed, which saves memory and highlights the fault moment.
• Download and review: Records are transferred to a computer and viewed as graphs or tables to identify patterns and causes.

5.1.4.3 SCADA

SCADA (Supervisory Control and Data Acquisition) is a networked system that collects data from many PLCs or remote terminal units, displays it centrally and allows supervisory commands to be sent back. It integrates monitoring functions with control commands, and diagnostic software may add fault tree analysis or artificial intelligence to predict failures. Example: a water utility supervises several remote pumping stations from one control room, seeing pump status, tank levels and motor currents on a single screen.

The main parts of a SCADA system are:

• Field devices: Sensors and actuators at the plant measure and operate the process, for example level transmitters and pump starters.
• PLCs and remote terminal units: These controllers read the field devices, run local control and pass data upward. They keep the process running even if the network fails.
• Communication network: Cables, radio or cellular links carry data between the controllers and the control room using agreed protocols.
• Master station or server: This computer polls the controllers, processes the data, raises alarms and holds the supervisory software.
• HMI workstations: Operators view mimic diagrams, alarms and trends and issue supervisory commands from these screens.
• Historian and reporting: Recorded values are kept for trend analysis and reports, supporting fault investigation and maintenance planning.

Remote access, automated reporting and user-configurable alarms make SCADA suitable for supervising widely spread installations. An alarm that a pump motor current has exceeded its limit can be sent to the on-call technician before the pump trips.

Chapter Summary

This chapter explored the critical role of monitoring and diagnostic tools in electrical systems automation, beginning with their definition, purpose, and development. Various types of tools such as Human Machine Interfaces, data loggers, and SCADA systems were examined for their functions in system oversight. The integration of these tools was discussed through different methods and step-by-step procedures to ensure seamless operation within automation frameworks. The chapter then addressed the extraction of data from monitoring devices, detailing the types of data involved, techniques for retrieval, and procedural guidelines. Storage solutions including data loggers and secure storage systems were presented, emphasizing the importance of safeguarding collected information. Techniques for analyzing data were outlined alongside the identification of Key Performance Indicators and the use of specialized analysis tools. Finally, the chapter concluded with approaches to system optimization by identifying areas for improvement, implementing effective strategies, and applying these methods to enhance overall automation performance.