Industrial automation engineering education needs to connect mathematical foundations with the practical work of designing, modeling and controlling real systems. The University of Zagreb Faculty of Electrical Engineering and Computing’s 2018–19 graduate study plan offers a useful curriculum example: its Automation profile combined control theory, laboratory courses, embedded computing, robotics and process automation within a two-year master’s program.
The catalog is a historical snapshot, not a statement of current course availability. Its value for industrial automation engineers and technical decision-makers lies in the way it organizes complementary disciplines—and in the capabilities students are expected to develop by bringing those disciplines together.
Industrial automation engineering education starts with control fundamentals
The first year’s core subjects establish a foundation in system behavior and control design. In the first semester, students could select from courses including Fundamentals of Robotics, Synthesis of Linear Control Systems, and Control of Electric Drives. The curriculum also included System Modeling and Simulation as a specialization subject.
In the second semester, the theoretical sequence continued with Nonlinear Control Systems and Estimation Theory. Together, these topics address different parts of an automation problem: representing a process mathematically, determining what can be inferred from available measurements, and developing control approaches suited to linear or nonlinear behavior.
These subjects matter in industrial settings because control decisions depend on understanding both the equipment and the process. Modeling and estimation provide analytical tools for reasoning about system dynamics and measured variables, while control theory supports the design of strategies to guide system behavior.
Laboratories connect theory to engineering practice
Laboratory work was a required part of both first-year semesters. Automation Laboratory 1 carried five ECTS credits in the first semester; Automation Laboratory 2 carried three in the second. Their placement alongside theory courses creates a curriculum structure in which students encounter practical work as part of the main study path, rather than as an isolated final exercise.
The program also offered courses and skills training relevant to implementation. These included Programming for the Robot Operating System and, in the second semester, Advanced LabVIEW. In the specialization options, students could study Embedded Computer Systems Design. This mix reflects the range of knowledge involved in automation projects: control concepts must ultimately be implemented, tested and connected to computing platforms and instrumentation.
For system integrators and plant teams, the practical lesson is that automation expertise spans more than controller logic. Engineers benefit from being able to reason across control design, software, system models and the tools used to observe or simulate behavior.
Specialization broadens the automation toolkit
The curriculum’s second-year options extended beyond conventional control topics. Recommended electives included Intelligent Control Systems, Mechatronic Systems and Control of Robotic Systems. Specialization subjects included Mobile Robotics, Process Automation, Expert Systems, and Software Support for Industrial Embedded Systems.
This range reflects the variety of systems that automation engineers may encounter. Process automation focuses attention on controlling processes, while mechatronics and robotics bring together mechanical systems, sensing, computation and control. Embedded-system subjects address the software and computing foundations used within equipment. The course titles indicate areas of study; they should not be read as claims about particular industrial applications or specific technical outcomes.
Students could also choose Discrete Event Systems, Adaptive and Robust Control, and other subjects related to modeling and system behavior. Such options allow a student to build depth in a particular area while keeping the broader automation discipline in view.
A structured degree balances depth and breadth
The study plan used category-based credit requirements to shape the student’s choices. In the first semester, students were required to select at least 15 ECTS of profile theory, complete the five-credit laboratory, and take minimum amounts of specialization, mathematics and natural science, and humanities or social sciences. The second semester similarly combined theory, a laboratory and seminar with minimum credit requirements for specialization and supporting subjects.
In the second year, the plan included an eight-credit graduate project and a 30-credit thesis. Students were also directed to select at least 12 ECTS of recommended electives and at least eight ECTS from specialization subjects. This arrangement combines a defined technical core with room for focused study and a substantial independent project.
That balance is relevant when organizations consider engineering skills. A strong automation foundation includes technical depth, but projects also require engineers to communicate, organize work and make decisions within wider operational contexts. The curriculum’s inclusion of humanities and social-science requirements sits alongside its engineering subjects rather than replacing them.
What the curriculum suggests for automation teams
The Zagreb program illustrates a practical way to organize graduate-level preparation for automation work:
- Build from fundamentals: include system modeling, estimation and linear and nonlinear control.
- Make laboratory work part of the core: give students structured opportunities to connect theory with engineering tools and systems.
- Include implementation disciplines: cover embedded computing, programming and simulation alongside control.
- Offer pathways into adjacent fields: provide options in robotics, mechatronics and process automation.
- Reserve time for a substantial project: use project and thesis work to bring together knowledge from different subjects.
These are curriculum-design observations, not a guarantee that a graduate will have experience with a particular plant, platform or industrial application. Employers and engineering leaders should still assess candidates against the demands of their own systems and projects.
Conclusion
The 2018–19 Automation profile shows how industrial automation engineering education can combine control theory, laboratories, embedded systems, robotics and process automation in a coherent study path. Its practical implication is that automation capability is multidisciplinary: engineers need analytical foundations as well as experience connecting models, software and physical systems. For educators and employers alike, that combination offers a useful reference point when defining technical development priorities.