23.03.2017 Views

wilamowski-b-m-irwin-j-d-industrial-communication-systems-2011

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

56-8 Industrial Communication Systems<br />

scripting of the elements. Browsers can use plug-ins for rendering and display. Other XML-based<br />

formats are available for use in multimedia applications. They may be used in <strong>industrial</strong> applications<br />

whenever they become standards and the support by tools is stable.<br />

56.3.3 technologies for Server-Side and Client-Side Functions<br />

The functionality of combining content description, application-depending interpretation, and transport<br />

is provided at both the server side and at the client. Different technologies have been developed.<br />

Popular client-based solutions are—without making any claim to be complete—JavaScript, Java-<br />

Applets, ActiveX-Controls, and Flash. They require client-based runtime environments, like Java<br />

Virtual Machine (JVM), Flash Players, and alike. They might be available bundled with the client software<br />

(e.g., a browser), or may require installation of plug-ins. An interesting and rapidly used approach<br />

is Asynchronous Javascript and XML (AJAX), which allows highly interactive applications with automatically,<br />

dynamically loading and rendering of information fragments.<br />

Well-known server-based technologies include PHP, Java-Servlets, Active Server Pages (ASP), and<br />

Common Gateway Interface (CGI). In this case, the server component requires the runtime environment,<br />

for example, scripting engines or servlet containers. The latter are often bundled with Web servers;<br />

Apache Tomcat is an example.<br />

Applications of client- and server-side technologies in the <strong>industrial</strong> domain can be compared to standard<br />

IT-based solutions. They are as manifold as the technologies supported. Depending on the use cases,<br />

a combination of different technologies may be required. Additional constraints may be derived concerning<br />

real-time aspects, data consistency, and data and interface management. Typically, gateways to<br />

underlying levels of the automation pyramid (see Chapter 13) are implemented at the server components.<br />

An important feature for selection of a server- or client-side technology in the <strong>industrial</strong> application<br />

area is its maturity, often treated as a combination of time of availability, standardization, tool support,<br />

etc. Taking into account the typical life cycles of automation <strong>systems</strong> ranging from 3 to 5 years in factory<br />

automation to more than 40 years in process automation and power plants, newly introduced technologies<br />

are hesitantly applied.<br />

56.4 application Examples<br />

The application of Internet technologies in Industrial automation depends on the specific use cases.<br />

These use cases also define the criteria for technology selection. Thus, the application range becomes<br />

broader and broader. Without claiming completeness, some of the typical application examples are<br />

described in this section.<br />

56.4.1 Description Technologies<br />

Device descriptions like Electronic Device Description (EDD) [IEC07] became more and more important<br />

for many applications in <strong>industrial</strong> automation, especially in engineering and network set-up,<br />

but not limited to. Together with the evolving functional complexity of field devices the description<br />

languages had to be adapted in order to reflect all the features of devices. They typically require specific<br />

parsers and interpreters for integration into applications. These parsers and interpreters have to<br />

be adapted as well upon changes of the description language. It is quite usual that several parsers exist<br />

within one application, allowing to support a broad range of field devices and different networks.<br />

XML seems to solve several of the problems stated above. XML as a meta language is intended to<br />

be used for the definition of specific languages—device descriptions are an example for this. Good<br />

quality parsers and software tools are available and can be easily integrated into applications. So using<br />

an XML-based device description would reduce implementation efforts at the application processing<br />

device descriptions. Thus, several activities have been started to define XML-based device descriptions.<br />

© <strong>2011</strong> by Taylor and Francis Group, LLC

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!