Access Official Technical PDF

Share Summary:LinkedInEmail

A TSN profile for industrial automation is intended to guide how Time-Sensitive Networking capabilities are selected and applied in industrial networks. The IEC/IEEE 60802 Joint Project brought together participants from IEC and IEEE 802.1 to develop such a profile. Meeting discussions in Pittsburgh in May 2018 offer a useful view of the engineering work behind the effort: defining relevant use cases, translating them into requirements, and preparing the basis for a draft.

For automation engineers and technical decision-makers, the central lesson is that a profile is not simply a list of network features. It must connect operational needs with consistent implementation choices, while accounting for how industrial systems are built and how standards work together.

Why develop a TSN profile for industrial automation?

Time-Sensitive Networking (TSN) refers to a set of IEEE 802.1 technologies and standards work addressing time-sensitive communication over networks. Industrial applications bring particular requirements and operating contexts, so the IEC/IEEE 60802 project was established to develop a TSN profile specifically for industrial automation.

A profile helps narrow the gap between broad standards and practical engineering decisions. It identifies which capabilities and requirements are relevant to the intended application context. This can give system integrators and equipment developers a shared basis for designing networked systems, rather than leaving every implementation decision to be interpreted independently.

The Pittsburgh meeting was part of an ongoing joint standards effort, not the release of a completed profile. At that point, the project had contributions and liaison documents, but no draft document. Participants focused on building the inputs needed to guide future drafting.

Use cases provide the foundation for requirements

One major focus was the development and review of industrial use cases. Participants discussed how proposed use cases should inform profile requirements and how their relevance to major markets should be assessed. A separate system-requirements contribution was also considered for integration into the broader use-case and requirements work.

This sequence matters. A requirement is more useful when its connection to an operational need is clear. Use cases can help a standards group distinguish essential network behavior from features that may not be necessary across all industrial settings. The meeting’s discussion also recognized that further use-case contributions could be considered and might inform a later edition of the work.

For plant teams and integrators, this approach offers a practical way to evaluate standards activity: ask which operating scenarios a requirement is meant to support, and whether those scenarios match the needs of the system being designed. The project’s use-case and system-requirements documents were intended to guide profile development, rather than become part of the profile itself.

Configuration, latency, and network structure

The meeting agenda covered policy-based configuration, an industrial use case involving hierarchical network domains, and accumulated switch latency in industrial applications. These topics point to interrelated design questions: how network behavior is configured, how the network is organized, and how delays across multiple switches may matter to an application.

The minutes do not set out final technical solutions for these topics. Instead, they record contributions and identify areas requiring continued discussion. That distinction is important for engineering teams following standards development: a topic being discussed does not mean a particular mechanism or performance outcome has been adopted.

Configuration is especially relevant when a network includes equipment from different vendors or serves multiple operational needs. The Pittsburgh discussions treated policy-based configuration as an area for further work, while the use-case review was intended to help establish requirements that could guide drafting. The practical goal is to ensure configuration considerations are evaluated against defined industrial scenarios, rather than in isolation.

Compatibility and implementation flexibility

Another discussion addressed how standards should be written and used, including compatibility levels. The meeting recorded that IEC/IEEE 60802 could be implemented in one device or distributed across several devices, and that it could be combined with implementations of other standards.

That flexibility is relevant to system architecture. Industrial networks are often assembled from multiple components, and a profile must be meaningful across different implementation arrangements. Compatibility considerations can help clarify what it means for devices or systems to conform, although the meeting minutes do not define specific compatibility levels or prescribe an architecture.

For system integrators, the takeaway is to consider the complete implementation context: which functions reside in each device, how devices interact, and how the profile relates to other standards used in the system. These are the kinds of questions that a well-grounded profile needs to address clearly.

Coordination is part of the technical work

The joint project involved IEC industrial-process measurement, control and automation participants and the IEEE 802.1 TSN Task Group. Coordination between the organizations was therefore central to the work, alongside technical contributions. The meeting also reviewed the project workflow and accepted an initial schedule with milestones.

Standards development depends on this process as well as technical content. Use cases and requirements must be reviewed, comments incorporated, and draft material developed through agreed procedures. The Pittsburgh meeting concluded with plans for continued work, including revisions to use-case and requirements contributions and preparation for a later drafting stage.

What industrial teams should take away

The May 2018 meeting illustrates a disciplined path toward an industrial networking profile:

  • Start with operational scenarios. Use cases help explain why particular network requirements matter.
  • Connect requirements to system behavior. Requirements should be considered alongside industrial use cases and system-level needs.
  • Treat configuration and latency as design topics. They require discussion in the context of the intended applications, not assumptions about solutions.
  • Account for varied architectures. The profile was discussed as applicable to implementations within one device or across several devices, and in combination with other standards.
  • Track the status of standards work. Meeting contributions and planned actions are not the same as finalized profile requirements.

For plant managers, operations leaders, and engineering teams, the practical implication is to follow how industrial use cases are translated into profile requirements before making design decisions based on the evolving standard. The IEC/IEEE 60802 work described in Pittsburgh was laying that groundwork: aligning operational needs, technical requirements, implementation flexibility, and joint standards development to shape a common approach to TSN in industrial automation.

Access Official Technical PDF

About The Author