Industrial automation projects draw on expertise from controls, communications, computing, electronics, and artificial intelligence. As technical information crosses these boundaries, consistent terminology becomes important. The IEEE Taxonomy offers a structured way to view related engineering topics: its 2019 edition presents a hierarchical subset of terms from the IEEE Thesaurus, organized into broad subject families and nested subtopics.
For automation engineers, system integrators, and technical decision-makers, the taxonomy is best understood as a map of subject areas—not as a design standard or a complete list of industrial automation terms. Its value lies in showing how technical concepts are grouped and how one topic may connect to several wider fields.
What the IEEE Taxonomy contains
The 2019 document describes itself as a subset hierarchical display of IEEE Thesaurus terms. It covers the first three hierarchical levels under each term-family, with families arranged alphabetically. Indentation shows the relationship between a broader subject and its more specific topics.
For example, the “Communications technology” family includes “Communication systems,” which branches into areas such as “Computer networks,” “Data communication,” “Industrial communication,” and “Wireless communication.” A reader can move from a general discipline to a more focused subject without losing sight of the broader context.
The taxonomy also notes that a term can appear in more than one branch, or more than once within a hierarchy. That reflects an important feature of technical language: a concept may be relevant to multiple domains. The document remains a subset of the 2019 IEEE Thesaurus, rather than attempting to reproduce the full thesaurus.
Why the structure matters in industrial automation
Automation systems connect equipment, control functions, and information processing. As a result, project discussions can involve concepts that belong to different engineering disciplines. The taxonomy’s coverage shows some of those intersections, including communications, computer networks, data systems, control engineering computing, embedded software, and artificial intelligence.
Consider a discussion about connecting devices across a facility. The taxonomy places “Industrial communication” within communication networks and lists related topics elsewhere, including Ethernet, wireless networks, field buses, and the Internet of Things. These labels do not prescribe an architecture or recommend a particular technology. They do, however, illustrate how a broad topic can be described through more specific, related areas.
Similarly, a team discussing data collected from equipment may need language spanning data acquisition, data processing, data analysis, and data integrity. In the taxonomy, these subjects appear within the wider “Data systems” and “Data processing” groupings. This structure can help teams identify relevant terminology when organizing engineering materials or clarifying the scope of a technical discussion.
Using the taxonomy as a terminology reference
In practical settings, the taxonomy can serve as a starting point for organizing technical subjects. It may be useful when teams are creating topic lists, classifying internal documentation, or trying to make terminology consistent across disciplines. These are potential applications of its hierarchical structure, rather than functions the taxonomy itself claims to perform.
A disciplined approach can make the reference more useful:
- Start with the broad subject. Identify the relevant term-family, such as communications technology, circuits and systems, or computational and artificial intelligence.
- Follow the hierarchy. Move from a general category to a more specific term when the distinction matters to the document or discussion.
- Check neighboring branches. Because terms can appear in multiple branches, look for related groupings when a topic crosses disciplinary boundaries.
- Preserve project-specific meaning. Use taxonomy terms as a reference, while defining any local terminology that has a narrower or different meaning in your organization.
For example, a team documenting a machine-vision application might consult the taxonomy’s “Image processing” branch, which includes machine vision, image recognition, object detection, and image segmentation. This can help describe the subject at an appropriate level, while project documents still specify the actual system requirements and implementation details.
Important limitations for engineering teams
The 2019 IEEE Taxonomy is a classification resource, not an engineering specification. Its entries name and arrange subject areas; they do not establish how to design a control system, configure a network, select a component, or verify a safety function. A term’s presence in the taxonomy should not be interpreted as an endorsement, requirement, or technical recommendation.
Its coverage is also broad. Industrial automation professionals will find relevant topics among its many branches, but the document is not presented as a dedicated automation vocabulary. Teams should therefore avoid treating it as a complete index of every term used in a plant, project, or industrial standard. It can complement established project glossaries and discipline-specific documentation, not replace them.
Finally, version matters. The document is explicitly the 2019 edition and describes a subset of the corresponding 2019 IEEE Thesaurus. When using its terms in a long-lived information system or shared documentation workflow, record the edition being referenced so that the basis for classification remains clear.
Conclusion
The 2019 IEEE Taxonomy provides a hierarchical view of technical subject areas across fields that intersect with industrial automation, from communication networks and data systems to circuits, computing, and artificial intelligence. Its practical contribution is organizational: it helps readers navigate relationships among engineering topics and choose a suitable level of descriptive detail. Used with clear project definitions and the right technical specifications, it can support more consistent terminology without being mistaken for a design guide or a complete industrial automation standard.