Category: Engineering

Electrical Power Engineering vs Instrumentation and Control Engineering: Where the Boundary Really Lies

Electrical Engineering is a broad profession, and the boundaries between its specialist disciplines are often less clear in practice than they appear in textbooks.

This is particularly true in industrial plants, mining operations, utilities, process facilities and infrastructure projects, where Electrical Power Engineering, Instrumentation and Control Engineering, Operational Technology and Information Technology increasingly overlap.

For a practising Electrical Engineer, the important question is not simply:

“Is this electrical equipment?”

A better question is:

“What engineering function is being performed, and which discipline is responsible for that function?”

A motor, variable-speed drive, protection relay or intelligent switchboard can simultaneously form part of an electrical power system, an instrumentation system and an operational technology network.

Understanding those distinctions is therefore important for design responsibility, interface management and multidisciplinary engineering.

Electrical Engineering as an Umbrella Discipline

Electrical Engineering includes a number of recognised areas of specialisation, including:

  • Electrical Power Engineering
  • Electronic Engineering
  • Instrumentation and Control Engineering
  • Telecommunications Engineering
  • Automation Engineering
  • Mechatronic Engineering
  • Power electronics and embedded systems

The boundaries are not absolute.

For example, a modern variable-speed drive contains sophisticated power electronics and embedded control systems, but its application in an industrial motor circuit may primarily fall within Electrical Power Engineering.

Similarly, a digital protection relay contains electronic hardware, programmable logic, communications and measurement functions, but its principal engineering application is normally electrical protection.

The useful distinction is therefore not the physical size of the equipment, the magnitude of the current or whether the device contains electronics.

The distinction is principally one of engineering purpose.

Electrical Power Engineering

Definition

Electrical Power Engineering is concerned with the generation, transformation, transmission, distribution, protection, control and utilisation of electrical energy.

In an industrial environment, its primary objective is to ensure that electrical power is delivered to plant and equipment safely, reliably, efficiently, with adequate capacity, acceptable voltage and power quality, and appropriate protection against faults and abnormal operating conditions.

How is electrical energy supplied, distributed, protected and delivered to the equipment that requires it?

Typical Electrical Power Engineering systems

  • Utility supplies
  • Generators
  • Renewable generation
  • Battery energy storage systems
  • Substations
  • HV, MV and LV distribution systems
  • Transformers
  • Switchboards
  • Switchgear
  • Motor-control centres
  • Motors
  • Variable-speed drives
  • Cables and busbars
  • UPS systems
  • DC power systems
  • Earthing and bonding systems
  • Electrical protection
  • Power-quality systems
  • Electrical metering

Its focus is fundamentally on the electrical power path from source to load.

Typical Electrical Power design activities

1. Developing the electrical system architecture

This includes defining incoming supplies, system voltages, transformers, switchboards, distribution topology, redundancy, emergency supplies and the relationship between generation and loads.

2. Developing electrical load lists

The engineer determines connected load, operating load, maximum demand, diversity, starting conditions, standby loads, future loads and required system capacity.

3. Performing power-system studies

Typical studies include load flow, voltage drop, short-circuit calculations, motor starting, protection coordination, harmonic analysis, power factor, arc-flash assessment and system stability where applicable.

4. Selecting electrical equipment

This may include transformers, switchgear, circuit breakers, fuses, cables, motors, variable-speed drives, generators, UPS systems and battery systems.

5. Designing electrical protection

The engineer determines protection functions, relay requirements, breaker ratings, fuse ratings, trip settings, discrimination, backup protection and fault-clearing requirements.

6. Designing cable systems

This includes current-carrying capacity, voltage drop, short-circuit withstand, installation conditions, grouping, ambient temperature, electromagnetic compatibility and mechanical installation requirements.

7. Designing earthing and bonding systems

This includes system earthing, protective earthing, equipotential bonding, earth grids, touch and step voltage considerations, and lightning and surge interfaces.

8. Specifying motors and drives

The engineer may determine required motor rating, starting method, duty, speed range, overload capability, VSD rating, braking requirements, cable compatibility and electrical protection.

9. Preparing design documentation

Typical deliverables include single-line diagrams, schematics, cable schedules, equipment schedules, datasheets, specifications, protection schedules and electrical calculations.

10. Supporting commissioning

Electrical Power Engineering remains involved during equipment inspection, energisation, protection testing, motor rotation testing, VSD commissioning, functional testing and verification against the design intent.

Instrumentation and Control Engineering

Definition

Instrumentation and Control Engineering is concerned with measuring physical and process variables and using those measurements to monitor, regulate and control plant operation.

Its primary focus is not the delivery of electrical energy. Its focus is determining what the process or machine is doing, transmitting that information, deciding what response is required, and manipulating the plant so that it operates as intended.

How do we determine what the process is doing, decide what it should do, and command the equipment accordingly?

Instrumentation

Instrumentation is principally concerned with obtaining reliable information about the physical plant or process.

  • Temperature
  • Pressure
  • Flow
  • Level
  • Position
  • Speed
  • Vibration
  • Force
  • Weight
  • Density
  • pH
  • Chemical composition
  • Equipment condition

Typical devices include sensors, transmitters, switches, analysers, transducers, encoders, position sensors, vibration monitors and other measurement systems.

A properly engineered instrumentation system must provide a measurement that is sufficiently accurate, repeatable, reliable, responsive, maintainable and appropriate for the process conditions.

Control Engineering

Control Engineering uses measurements and other system information to determine how plant or machinery should respond.

  • PID regulation
  • Sequencing
  • Start and stop logic
  • Permissives
  • Interlocks
  • Cascade control
  • Ratio control
  • Equipment coordination
  • Alarm generation
  • Shutdown logic
  • Safety functions
  • Process optimisation

Typical control platforms include PLCs, distributed control systems, programmable automation controllers, safety PLCs, embedded controllers and machine-control systems.

Supervisory functions may be performed through HMI systems, SCADA systems, plant control systems and process historians.

The Fundamental Difference

Electrical Power Engineering

How do we supply and control electrical energy?

Instrumentation and Control Engineering

How do we measure and control the behaviour of the physical process?

These functions are distinct, but they frequently meet at the same equipment.

Example: A Motor-Driven Pump

Consider a centrifugal pump driven by a three-phase induction motor through a variable-speed drive.

Electrical Power Engineering responsibilities

  • Supply voltage
  • Motor rating
  • VSD rating
  • Upstream feeder
  • Cable size
  • Circuit breaker or fuse
  • Short-circuit withstand
  • Earthing
  • Harmonic implications
  • Motor insulation requirements
  • VSD output requirements
  • Electrical protection

Instrumentation responsibilities

  • Flow transmitter
  • Suction-pressure transmitter
  • Discharge-pressure transmitter
  • Bearing-temperature monitoring
  • Vibration monitoring
  • Valve position feedback

Control Engineering responsibilities

  • Flow setpoint
  • PID control loop
  • VSD speed reference
  • Start permissives
  • Low-flow trip
  • Low suction-pressure trip
  • Pump sequencing
  • Standby pump changeover
  • Operator controls

The same physical pump is therefore simultaneously part of the electrical power system, instrumentation system and control system. The disciplines are differentiated by the function being designed, not by physical ownership of the equipment.

Variable-Speed Drives: A Particularly Important Interface

Variable-speed drives illustrate why these boundaries must be understood.

A VSD is unquestionably an electrical power device. It rectifies incoming AC power, creates a DC link, produces controlled AC output, supplies the motor and controls motor torque and speed.

Its electrical design therefore involves rating, protection, harmonics, EMC, cable selection, motor compatibility, braking and thermal considerations.

However, the same VSD may also receive start commands, stop commands, speed references, torque references, process permissives and emergency commands.

It may transmit running status, current, speed, torque, faults, warnings, temperatures and diagnostic information.

These functions bring the VSD directly into the Instrumentation, Control and OT domains.

Protection Relays Present a Similar Case

A modern protection relay may measure current and voltage, calculate power, detect faults, trip circuit breakers, provide alarms, record waveforms, communicate over Ethernet, publish data to SCADA, receive commands, implement interlocking and participate in substation automation.

Electrical Power Engineering normally owns the protection function.

Operational Technology may own network architecture, Ethernet switches, communication configuration, time synchronisation, cybersecurity and SCADA integration.

Again, the boundary is functional rather than physical.

Where Operational Technology Fits

Operational Technology is often confused with Instrumentation and Control Engineering. They overlap heavily, but they are not identical.

OT comprises the hardware and software infrastructure used to monitor and control physical processes.

  • PLCs
  • DCS systems
  • SCADA
  • Industrial networks
  • Historians
  • Remote I/O
  • Control-system servers
  • Engineering workstations
  • Protection communications
  • Power-management systems
  • OT cybersecurity infrastructure

Instrumentation and Control Engineering defines what must be measured and how the process must behave.

Operational Technology defines how the digital control and communications infrastructure will implement those requirements.

Where Information Technology Fits

Information Technology becomes increasingly prominent as plant information moves upward from real-time control toward enterprise use.

The distinction between IT and OT again lies primarily in purpose.

An Ethernet network connecting business laptops is IT. An Ethernet network carrying PLC control traffic is OT.

The underlying technology may be virtually identical while the engineering requirements are very different.

The Plant Hierarchy

Information and Systems Hierarchy

Equipment and Process Level

This includes the physical plant: motors, pumps, conveyors, valves, transformers, switchgear, sensors, actuators, field instruments and process machinery.

Electrical Power Engineering and Instrumentation are especially prominent here.

Control Level

This includes PLCs, DCS, SCADA, protection systems, safety systems, machine controllers and industrial communications.

Instrumentation and Control Engineering and OT are particularly prominent here.

Operations and Process Level

This includes production supervision, process optimisation, historians, operational reporting, asset monitoring, production scheduling and performance analysis.

OT and IT increasingly overlap here.

Management Level

This includes enterprise planning, financial systems, management reporting, business analytics, corporate governance and enterprise information systems.

IT is generally dominant at this level.

Why the Distinction Matters to a Design Engineer

Ambiguous discipline boundaries create design risk.

  • An Electrical Engineer may assume the controls team will define VSD communications.
  • The controls team may assume Electrical will define all VSD signal mappings.
  • An instrument may be specified without adequate electrical power provision.
  • A protection relay may be installed without its Ethernet interface being included in the OT design.
  • A PLC command may be designed without consideration of the electrical protection philosophy.
  • An IT team may apply enterprise network practices to an OT system without considering operational consequences.
  • Control functionality may be embedded in vendor equipment without a clear definition of where control authority resides.

These are not merely organisational problems. They can result in unsafe operation, equipment damage, nuisance trips, loss of production, commissioning delays, cybersecurity vulnerabilities and expensive design rework.

Interface Engineering

For multidisciplinary systems, the interfaces should be deliberately engineered.

  • Who owns the equipment?
  • Who owns the function?
  • Who defines the operating requirement?
  • Who defines the software?
  • Who owns the communications network?
  • Who determines protection behaviour?
  • Which system has final control authority?
  • What data is exchanged?
  • How are failures handled?
  • Who approves changes?

Useful engineering documents include control philosophies, functional descriptions, interface matrices, responsibility matrices, I/O lists, signal schedules, communication registers, network architecture drawings, cause-and-effect matrices, protection philosophies and design review checklists.

A Practical Rule for Classifying Design Work

Primary engineering questionPrincipal discipline
How much electrical energy is required, how is it supplied, and how is the equipment protected?Electrical Power Engineering
What physical quantity needs to be measured and how accurately?Instrumentation Engineering
How should the process respond to the measured condition?Control Engineering
How will controllers, intelligent equipment and supervisory systems communicate and operate as an integrated plant system?Operational Technology
How will operational information be integrated into enterprise systems and managed as organisational information?Information Technology

This method is generally more useful than trying to classify work by equipment type alone.

Final Perspective

Electrical Power Engineering and Instrumentation and Control Engineering are distinct engineering disciplines, but modern industrial systems make their interaction unavoidable.

Electrical Power Engineering provides and controls the electrical energy required to operate the plant.

Instrumentation determines what the physical process is doing.

Control Engineering determines how the process should respond.

Operational Technology provides much of the digital infrastructure through which these control functions are implemented.

Information Technology extends operational information into the broader enterprise.

The boundaries between these domains should therefore not be viewed as hard barriers. They are better understood as areas of primary engineering responsibility connected by deliberately managed interfaces.

For the Design Engineer, recognising these interfaces is essential. A technically sound motor circuit, instrument loop or control system is not sufficient if the adjoining discipline has been ignored.

Successful industrial design depends on integrating power, measurement, control, communications and information into one coherent operating system.


Developing a Continuous Caster Breakout Detector: An Engineering Case Study

In the early 1990s, the continuous casting plant at Iscor’s Pretoria Works faced a serious operational problem: sticker breakouts.

A breakout in a continuous caster is not merely a production interruption. It involves molten steel escaping from the partially solidified strand, with the potential for extensive equipment damage, prolonged production downtime and significant risk to personnel.

By 1993, the Pretoria Works caster was experiencing approximately two to three sticker breakouts per month. Rather than purchase a proprietary commercial detection system, a small multidisciplinary engineering team set out to understand the phenomenon and develop an in-house solution.

The result was a continuous caster breakout detector combining mould temperature measurement, supervisory control, mathematical modelling and an expert-system decision engine.

It became an early example of what would now be described as industrial condition monitoring combined with real-time predictive control.

What Is a Sticker Breakout?

During continuous casting, molten steel at approximately 1540 °C is poured into a water-cooled copper mould.

As the steel contacts the mould walls, its outer surface begins to solidify. A solid shell therefore develops around a still-molten core while the strand is continuously withdrawn from the mould at approximately 1 metre per minute.

Under normal operating conditions, mould powder provides lubrication between the solidifying strand and the copper mould.

If lubrication becomes inadequate, friction may increase sufficiently for part of the solidifying steel shell to stick to the mould wall near the meniscus.

The strand, however, continues moving downwards.

The result is a tear in the newly formed shell.

Because this occurs beneath the surface of the molten steel, the operator cannot see it. As withdrawal continues, the tear propagates downward through the mould. Unless the shell can heal before reaching the mould exit, molten steel escapes from the strand.

This is the sticker breakout.

The consequences can include damage to the mould and downstream segments, lost steel, substantial repair effort and several hours of production downtime.

The mechanism of a sticker breakout showing the progression of temperature associated with slab wall thickness.
The scar of a prevented breakout on the continuously cast steel slab.

The Engineering Problem

At the time, Pretoria Works had no practical means of predicting or detecting a developing sticker breakout.

Commercial detection systems were available, but their installed cost was estimated at between R2 million and R3 million. They also presented another engineering disadvantage: their proprietary nature made them difficult to understand, modify and optimise for local casting conditions.

For the project team, this presented an opportunity.

Could the plant develop a system internally that was:

  • effective at detecting developing sticker breakouts;
  • fast enough to allow corrective action;
  • inexpensive compared with proprietary alternatives;
  • based on standard, maintainable hardware;
  • understandable by plant engineering and maintenance personnel;
  • adaptable to the particular behaviour of the Pretoria caster; and
  • capable of improving the plant’s understanding of the continuous casting process itself?

A preliminary investigation was therefore approved.

The ultimate objective was ambitious: reduce the breakout frequency to less than one per year.

Detecting a Breakout Through Temperature

The key to detecting a sticker breakout lies in understanding what happens thermally when the steel shell sticks to the mould.

Thermocouples installed in the mould allow the temperature distribution across its faces to be monitored continuously.

A developing sticker produces a characteristic change in this temperature pattern.

Rather than relying on a single temperature limit, the project sought to identify the spatial and temporal temperature behaviour associated with a developing tear.

This required much more than installing instrumentation.

Temperature histories had to be gathered during actual casting operations, archived and compared with plant events. Literature describing the theoretical breakout mechanism was then compared with what was actually observed on the caster.

Over time, recognisable patterns emerged.

The engineering challenge was then to convert those patterns into mathematical rules capable of distinguishing a genuine developing sticker from the many normal temperature variations occurring during casting.

From Plant Data to an Expert System

Development proceeded along two parallel paths.

The first concentrated on refining the physical measurement system.

The second concentrated on developing a software decision-support system capable of evaluating the measured temperatures and determining whether a sticker breakout was developing.

The system ultimately combined:

  • mould-mounted thermocouples;
  • signal acquisition hardware;
  • personal computers communicating over a NetBIOS network;
  • commercial supervisory control and data acquisition software;
  • a proprietary decision-support application written in C++;
  • mathematical breakout-prediction algorithms;
  • operator displays; and
  • integration with the plant programmable logic controller.

For the early 1990s, this was an unusually distributed and software-intensive industrial control application.

Importantly, most of the system was constructed from commercially available, off-the-shelf components.

Only the specialised temperature-sensing arrangement and the breakout decision software were proprietary developments.

This deliberately avoided the “black box” problem associated with proprietary commercial systems. Plant engineers could understand how the system worked, maintenance personnel could replace standard components, and the detection parameters could be modified if operating conditions changed.

Components of the Breakout Detector.

Engineering Was Only Part of the Project

A technically correct detector would have achieved little without the cooperation of the people operating and maintaining the caster.

The core project team consisted of three people:

Alf Jansen van Rensburg — project leader, Process Control
Nico Davies — hardware, supervisory control and data acquisition
Christelle du Raan — development of the expert-system decision logic

However, the effective project team was considerably larger.

Maintenance personnel modified the mould, installed instrumentation and supported thermocouple replacement.

Production personnel contributed their operating experience.

This proved particularly important.

Operators had accumulated considerable practical knowledge concerning mould lubrication, casting behaviour, mould powder and abnormal operating conditions. Their anecdotal observations helped the engineering team interpret temperature behaviour that could not be understood from theory alone.

The development process therefore became a combination of:

theoretical knowledge + measured plant data + operator experience

That combination was fundamental to the performance of the finished system.

Human-Machine Interface Design

The operators were also actively involved in determining how information should be presented.

Different representations of mould temperature behaviour were evaluated, with operating personnel identifying those that best matched their understanding of the casting process.

Control-room operators, shift personnel and engineers were trained to interpret the system.

Mould operators were trained in the actions required following a breakout warning.

Initially, the principal response was to reduce strand withdrawal speed, providing additional time for the torn shell to heal.

As confidence in the detector increased and false alarms became sufficiently rare, the system progressed from decision support to automatic intervention.

When a sticker was detected, the casting machine could be stopped automatically through the plant PLC, although the operator retained a short opportunity to override the automatic action.

This represented an important transition.

The system was no longer simply monitoring the process.

It had become part of the process control strategy.

Measuring the Results

The operational results were substantial.

Before installation of the detector, the Pretoria Works continuous caster averaged approximately:

2 sticker breakouts per month

Immediately following commissioning, this reduced to approximately:

1 breakout every 2 months

The breakout frequency had therefore fallen to approximately one quarter of its previous level.

The chart shows a dramatic change in the frequency of breakouts after commissioning the Breakout Detector.

The project report calculated the average cost of a breakout at R359,379, including production downtime, labour, equipment damage and lost steel.

Development of the complete system, including engineering labour and purchased equipment, was calculated at approximately:

R1.025 million

The cost of the system was consequently recovered through approximately the first three prevented breakouts.

Those prevented breakouts occurred within approximately the first two months of operation.

The annual saving resulting from reducing the breakout rate from two per month to 0.5 per month was conservatively calculated at approximately:

R6.47 million per year

The corresponding increase in steel slab production was calculated at approximately:

7,752 tonnes per year.

At the target production rate of 45,000 tonnes per month, the project was estimated to reduce the variable production cost of steel slab by approximately 1.92%.
All monetary values quoted above are historical South African rand values from the original 1996 project report and should not be interpreted as present-day values.

Benefits Beyond Production

The financial return was significant, but the system produced several other benefits.

Improved Safety

A breakout releases molten steel into the caster structure.

Preventing the event therefore reduced the exposure of production and maintenance personnel to both the breakout itself and the difficult cleanup and repair activities that followed.

Reduced Maintenance Work

Preventing damage to the mould and caster segments reduced emergency maintenance work.

Workshop capacity previously consumed repairing breakout damage could instead be directed towards preventive maintenance and other productive work.

Improved Process Information

The temperature monitoring system gave production personnel far greater visibility into conditions within the mould.

Among other things, the temperature distributions could provide information regarding the effectiveness of mould lubrication.

This allowed operating personnel to respond to inadequate lubrication before it developed into a more serious condition.

Improved Slab Quality

Better mould lubrication does not merely reduce the probability of sticking.

It also contributes to improved slab surface quality.

The breakout detector therefore became useful not only as a protective system, but also as a process diagnostic instrument.

Knowledge Retention

Because the system was internally developed and deliberately constructed from understandable components, the knowledge remained within the organisation.

Detailed documentation and training material were developed for production, maintenance and engineering personnel.

The system therefore became part of the plant’s accumulated technical knowledge rather than remaining a proprietary technology understood only by an external supplier.

Designing for Maintainability

Maintainability was an explicit design objective from the beginning.

The thermocouples were standard commercial components.

The computer and data-acquisition hardware consisted largely of standard products.

Detection parameters were accessible through the expert-system interface, subject to password protection.

The C++ source code was retained so that future engineers could modify the application if required.

This approach proved successful.

The completed breakout detector was sufficiently stable that its maintenance burden was extremely small, apart from occasional replacement of mould thermocouples.

That design philosophy remains relevant today.

Industrial systems often remain in service far longer than the computers, software packages and communications technologies originally used to construct them.

A system built around open interfaces, understandable logic and replaceable components has a much better chance of remaining supportable throughout its operational life.

Lessons From the Project

Looking back three decades later, several aspects of the project remain particularly relevant to modern industrial automation.

1. Understand the Process Before Automating It

The project did not begin with software.

It began by understanding the physical mechanism that produced the failure.

Only once the thermal behaviour of a developing sticker was understood could meaningful detection logic be developed.

2. Plant Data Must Be Interpreted in Context

Raw temperature data was not enough.

The theoretical models had to be reconciled with actual plant behaviour.

Production knowledge was essential to explaining deviations from theory.

3. Operators Are Part of the Control System

The people operating the caster were not treated merely as end users.

Their knowledge influenced the detection model, the interface and the operating response.

That involvement was important in establishing confidence in the system.

4. Transparency Has Engineering Value

The decision to avoid a proprietary black-box solution provided benefits extending well beyond initial capital cost.

It allowed the plant to understand the technology, modify it and use it as a platform for further process investigation.

5. Automation Should Be Introduced According to Confidence

The system initially provided warnings and operator guidance.

Only after sufficient operating experience demonstrated reliable detection and a sufficiently low false-alarm rate was automatic machine intervention introduced.

This remains a sound philosophy for implementing predictive control systems.

6. The Greatest Value May Be the Knowledge Created

The detector prevented costly failures, but it also created a new capability.

Continuous mould temperature measurement provided metallurgical and process engineers with a platform for studying the influence of casting speed, mould oscillation, mould taper, mould powder, superheat and other parameters on caster behaviour.

The project therefore evolved from solving one operational problem into providing a broader process-development tool.

From Expert Systems to Modern Predictive Analytics

The terminology used today would be different.

A similar project might now be described using terms such as:

  • edge computing;
  • predictive analytics;
  • anomaly detection;
  • multivariable condition monitoring;
  • machine learning;
  • digital twins; or
  • industrial artificial intelligence.

But the fundamental engineering problem has not changed.

Measurements must reliably represent the physical process.

The failure mechanism must be understood.

The distinction between normal process variation and an incipient failure must be identified.

The detection system must respond quickly enough to matter.

And operators must trust the result.

The Continuous Caster Breakout Detector developed at Pretoria Works achieved these objectives using the technology available in 1993–1994.

Perhaps the most important lesson from the project is therefore not about any particular technology.

It is that deep process understanding, good instrumentation, disciplined analysis and close cooperation between engineering, operations and maintenance can solve problems that initially appear to require expensive proprietary solutions.

That principle remains as valid today as it was thirty years ago.

Pretoria Works Focus Newsletter