Access Official Technical PDF

Share Summary:LinkedInEmail

Industrial automation systems depend on more than controllers, sensors and software considered in isolation. Their capabilities emerge from the integration of electronic components, embedded and application software, communications, and the wider equipment and processes in which they operate. The ECSEL Joint Undertaking’s 2018 Multi-Annual Strategic Plan (MASP) provides a European-level view of this connected technology landscape and its role in industry.

Although the MASP covers applications well beyond manufacturing, its central themes are relevant to automation engineers, system integrators and operations leaders: develop reliable, increasingly integrated systems; connect innovation across the value chain; and move research toward industrial use. For plant decision-makers, these themes help frame the technical and ecosystem considerations behind industrial digitalization.

Industrial automation systems rely on an integrated technology base

The plan describes electronic components and systems (ECS) as a foundation for digital products and services. Components may include hardware or software, while a system developed at one level can become a component within a larger system. This layered view closely reflects industrial automation: a device, embedded platform or software module has to function as part of a machine, production line or facility.

That integration makes design choices interdependent. Requirements at system level can influence component selection and embedded software, while the characteristics of available components shape what can be achieved in the complete application. The MASP emphasizes linking micro- and nano-electronics, embedded and cyber-physical systems, and smart systems. For automation projects, the practical lesson is to consider system requirements and component capabilities together rather than treating each engineering discipline as a separate workstream.

From research to industrial deployment

A key concern in the MASP is bridging research and exploitation. Its programme is intended to span Technology Readiness Levels (TRLs) 2 to 8, covering work from technology development through system qualification. The plan also describes a general emphasis on larger, market-facing projects and higher TRLs, while allowing smaller projects and lower-TRL work where there is strong industrial support.

This range matters because promising technology does not become an industrial solution simply by proving a technical concept. Development also requires integration, validation and preparation for use in applications. The plan’s emphasis on the full value chain—from materials and design tools through architectures to end-user products—recognizes that progress depends on coordination across these stages.

For system integrators and technical decision-makers, this is a reminder to define how a project will connect research outputs to the intended application. Relevant questions include:

  • Which system-level requirements will guide component and software development?
  • What integration and qualification work is needed before the technology can be used in an application?
  • Which partners across the value chain need to participate to address those requirements?

Connectivity and interoperability require cooperation

The MASP identifies connectivity and interoperability as strategic technology areas alongside systems and component design, safety, security and reliability, and computing and storage. It also describes standardization as a way to support interoperable products, methods and tools across fragmented markets.

In automation environments, equipment and software must work within larger technical systems. The plan’s focus on interoperability therefore has implications for how projects are scoped: compatibility and system integration are not peripheral concerns to be resolved only at the end. They need consideration alongside architecture and development. The MASP also points to reference platforms and standardization in the context of innovation projects, while recognizing the role of strategic standardization activity in the private sector.

For plant teams, the strategic message is not a prescription for a particular protocol or product. Rather, it is that cooperation and common approaches can help address fragmentation. Project partners should clarify interface and integration needs early, especially when work spans multiple organizations or parts of the value chain.

Reliability and security belong in the design conversation

The plan treats safety, security and reliability as a dedicated focus area, reflecting the importance of these properties in complex electronic and embedded systems. It also highlights the growing relationship between hardware and software and the need for appropriate processes and tools along the value chain to meet quality and safety requirements.

For industrial automation, this reinforces a systems-level perspective. A component’s characteristics matter, but so do the ways it is integrated, engineered and qualified within the larger application. Requirements for reliability, safety and security should therefore inform architecture and development decisions, rather than being considered only after individual technologies have been selected.

Build projects around the value chain

ECSEL’s strategy combines industrial participants, research institutes, universities and public authorities. It also aims to involve small and medium-sized enterprises alongside larger organizations and knowledge institutions. The plan argues for collaboration across the innovation and value chain, pairing demand for applications with development of the technologies that enable them.

Its application-and-capability framework is designed to encourage work that crosses technological boundaries rather than limiting projects to one application or capability. The plan also presents “Lighthouse” initiatives as a way to bring together relevant actors around shared socioeconomic objectives and connect research and innovation investment with activity in application areas.

For an automation project, the transferable principle is to assemble the expertise needed to move from technology to an integrated application. Depending on project scope, that can mean aligning component and software developers, system designers, equipment or application partners, and research organizations. The MASP presents this type of cooperation as a means of reducing fragmentation and strengthening the route from innovation to use.

Practical implications for automation leaders

The ECSEL 2018 MASP is a strategic programme document, not a plant-level implementation guide. Its value for industrial decision-makers lies in the framework it offers: industrial automation systems are part of a broader ecosystem in which components, embedded software, system architecture, connectivity and validation are linked.

When planning modernization or research initiatives, teams can apply that framework by defining application needs alongside technology requirements, addressing integration and interoperability from the outset, and involving partners across the value chain. They should also match project activities to the maturity required for their intended outcome, from early development through qualification.

Ultimately, the plan’s practical message is that industrial digitalization depends on coordinated systems engineering. Strong automation outcomes require not only capable technologies, but also deliberate integration, attention to reliability and security, and collaboration that connects research to industrial applications.

Access Official Technical PDF

About The Author