Trends in Automation 8.2 Current Trends 137
sites are blocked by denial-of-service attacks. It is sig-
nificant if it affects the financial system by spyware
or phishing attacks, but it is devastating when a coun-
try’s infrastructure is attacked. Simply bringing down
the electricity system already has quite a high impact,
but if ahacker gainsaccess to an automation system, the
plant can actually be damaged and be out of service for
a significant amount of time. The damage to a modern
society would be extremely high.
Security therefore has to be at the top of any list
of priorities for any plant operator. Security measures
in automation systems of the future need to be con-
tinuously increased without giving up some of the
advantages of wider information integration.
In addition to technical measures to keep a plant se-
cure, security management needs to be an integral part
of any plant staff member’s training, as is health and
safety management today.
While security concerns for automation systems are
valid and need to be addressed by the plant manage-
ment, technical means and guidance on security-related
processes are available today to secure control systems
effectively [8.11]. Security concerns should therefore
not be the reason for not using the benefits of informa-
tion integration in plants and enterprises.
Engineering Integration
The increased integration of devices and systems from
plant floor to enterprise management poses another
challenge for automation engineers: information inte-
gration does not happen by itself, it requires significant
engineering effort. This increased effort is a contra-
diction to the requirement for faster and lower-cost
project execution. This dilemma can only be resolved
by improved engineering environments. Chapter 86,en-
terprise integration and interoperability, delves deeper
into this topic.
Today, all areas of plant engineering, starting at
process design and civil engineering, are supported by
specialized engineering tools. While their coupling was
loose in the past, and results of an engineering phase
were handed over on paper and very often typed into
other tools again, the trend towards exchanging data
in electronic format is obvious. Whoever has tried to
exchange data between different types of engineering
tools immediately faces the questions:
•
What data?
•
What format?
The question about what data can only be answered
by the two parties exchanging data. The receiver only
knows what data he needs, and the provider only
knows what data she can provide. If the two parties
are within different departments of the same company,
an internal standard on data models can be agreed
on, but when the exchange is between different busi-
ness partners, this very often results in a per-project
agreement.
In electrical systems, this issue has been addressed
by IEC 61850. In addition to being a communication
standard, it also covers a data model. Data objects
(logical nodes) are defined by the standard, and en-
gineering tools following the standards can easily
integrate devices of various vendors without project
specific agreements. The standard was even extended
beyond electrical systems to cover hydropower plants
(and also for wind generators in IEC 61400-25). So far,
further extensions into other plant types or industries
seem hardly feasible due to the variance and company
internal-grown standards.
The discussion on the format today quickly turns
into a spreadsheet-based solution. This approach is very
common, and most tools provide export and/or import
functionality in tabular form. However, this requires
separate sheets for each object type, since the data
fields may vary between objects. A format that supports
a more object-oriented approach is required.
Recently, the most common approach is to go to-
wards XML-based formats. IEC 61850 data is based
on XML, and there are standardization tendencies that
follow the same path. CAEX (computer aided engineer-
ing exchange, an engineering data format) according
to IEC 62424 is just one example; PLCOpen XML or
AutomationML are others.
The ability to agree on data standards between en-
gineering tools greatly eases interaction between the
various disciplines not only in automation engineering,
but in plant engineering in general.
Once the data format is defined, there still remains
the question of wording or language. Even when us-
ing thesame language,two different engineering groups
may callthe samepiece ofinformation differently. Ase-
mantic approach to information processing may address
this issue.
With some of these problems addressed in a nearer
future, further optimization is possible by a more par-
allel approach to engineering. Since information is
revised several times during plant design, working with
early versions of the information is common. Updates
of the information is normally required, and then up-
dating the whole engineering chain is a challenge. To
work on a common database is a trend that is evolving
Part A 8.2