Embedded Online Service

VDMA 2004
240 pages

Member price visible after registration

Contents:
1 The EOS idea Motivation and approach (Horst Meier)
1.1 Introduction
1.2 Requirements for a platform for remote services
1.3 Solution approach
1.4 A standard for remote services
1.5 Validation
1.6. Summary
2 EOS concept and standard (Ingo Heine)
2.1 Basic architectural concept
2.1.1 Access scenarios and technological constraints
2.1.2 Definition and description of components
2.1.3 The EOS device standard
2.1.4 The lookup standard
2.1.5 Example of runtime processes
2.1.6 Summary of key features
2.2 Outlook
3 Security in systems for remote services (Christoph Faber)
3.1 Introduction
3.2 Security in data processing systems
3.3 Extended differentiation of the concept of security
3.3.1 Material and environmental security
3.3.2 Functional security
3.3.3 Personal security
3.3.4 Data security
3.3.5 Consideration of security against the background of different situations
3.4 Requirements for security solutions in systems for remote services XII Table of contents
3.5 The EOS security concept
3.5.1 Firewall, restriction of communication to one port and the HTTP protocol
3.5.2 Encryption of communication
3.5.3 Integration of communication technology into the control architecture from a security perspective
3.5.4 Security and plausibility check of transmitted information
3.5.5 User management concept
3.5.6 Security responsibility of service developers
4 The successful implementation of remote services (Luis Barrantes, Joachim Zülch
4.1 Social framework
4.1.2 Causes of resistance
4.1.3 Types of resistance
4.1.4 Dealing with employee resistance
4.1.5 Employee reactions to the introduction of remote services
4.2 Legal framework conditions
4.3 Economic framework conditions Literature
5 Customer-oriented design of information technologies (Joachim Zülch, Jörg Gudat)
5.1 The process of customer-oriented software development
5.2 The ergonomic dialog design of the human-machine interface
5.2.1 Principles of dialog design
5.2.2 Ergonomic design of menus
5.2.3 Ergonomic design of tabulator paths
5.2.4 Dialog design: Defaults
5.2.5 Mask layout: Grouping of information and technical design
5.2.5 Why do software projects fail?
5.2.6 How should software development ideally be designed?
5.2.7 Framework conditions for prototyping
5.3 Outlook
6 The EOS LookUp server and the central services (Bernd Volkmer, Clemens Faller)
6.1 Introduction
6.2 The core functionalities of the LookUp server
6.2.1 The LookUp service
6.2.2 The EOS overview service
6.2.3 User administration
6.2.4 Maintenance control center
6.2.5 Messaging
6.2.6 Logging
6.2.7 Live chat service
6.2.8 File transfer service
7 EOS communication services (Klaus Jung, Dirk Weinhardt)
7.1 Introduction
7.2 Still image and video service
7.2.1 Transmission formats for still images
7.2.2 Transmission formats for non-real-time video
7.2.3 Functionalities of the still image and video service
7.3 Live video service
7.3 Transmission formats for real-time video
7.3.2 Functionalities of the live video service
7.3.3 Performance of the live video service
7.4 Live chat service
7.5 Integration of communication services in EOS devices
7.6 EOS Advanced standard from the perspective of communication services
7.6.1 Restrictions imposed by the EOS Basic standard and their consequences
7.6.2 Protocols for real-time communication
7.6.3 The use of RTP/H.263
8 EOS device servers and services for PC-based controllers (Michael Boll, Stefan Hoppe, Markus Wieland)
8.1 Task definition within the EOS project
8.2 Analysis of feasibility and requirements
8.2.1 System presentation PC-based controller TwinCAT
8.2.2 Customer requirements for EOS services
8.3 Many paths lead to the goal
8.3.1 Selection of technologies
8.3.2 Supported IIS web technologies XIV Table of contents
8.4 EOS devices and services implementations
8.4.1 ADS WebService
8.4.2 TcAdsDLL
8.4.3 Teleservice with .Net Web Services on Schütte multi-spindle automatic lathes
8.4.4 TwinCAT Web Diagnostics
9 EOS device servers and services on hollow blow molding machines (Ulrich Berghaus, Michael Hermann, Martin Matthiolius)
9.1 BEKUM hollow blow molding machines as EOS devices
9.2 EOS services on BEKUM hollow blow molding machines
9.2.1 The EOS start page
9.2.2 The EOS Logfile service
9.2.3 The EOS CAN Server service
9.2.4 The EOS Upload/Download service
9.2.5 The EOS Screenshot service
9.2.6 The EOS service Image viewer
9.2.7 The EOS service Webcam
9.2.8 The EOS service Online help
9.3 Conclusion
10 EOS device servers and services for CNC controls (Matthias Päßler, Clemens Faller)
10.1 EOS device server for the Sinumerik 840D controller
10.1.1 General information
10.1.2 Structure of the EOS server interfaces
10.2 General services (Sinumerik 840D)
10.2.1 Application sharing
10.2.2 Machine details
10.2.3 Special data
10.2.4 PLC data
10.2.5 Alarm log
10.2.6 Configuration data
10.2.7 Period evaluation (database query)
10.2.8 Active NC program
10.3 User-specific services (Sinumerik 840D)
10.3.1 Overview of master area
10.3.2 Piece count information Table of contents XV
11 EOS device server and services for PLC controllers (Clemens Faller, Sascha Dilthey, Bernd Volkmer
11.1 Introduction
11.2 Embedded WebServer for PLC controllers as EOS device server
11.2.1 Siemens communication processor as EOS device
11.2.2 Pusher communication processor as an EOS device
11.3 EOS device server for integrating standard communication protocols and interfaces into the EOS scenario
11.4 Data tunnel for integrating non-web-based applications into the EOS scenario
11.4.1 Security
11.4.2 Conformity with the EOS standard Literature
12 EOS at the Volkswagen plant in Salzgitter (Hans-Jürgen Lübke)
12.1 The initial situation
12.1.1 The Volkswagen plant in Salzgitter
12.1.2 A long-cherished wish: standardized remote access
12.1.3 Teleservice, the first attempt at standardization
12.1.4 Teleservice, the result of the first trials
12.2 Implementing EOS
12.3 EOS, open questions 13 EOS experience report Case study ZF Friedrichshafen AG (Thomas Wiedemann)
13.1 Introduction
13.2. initial experiences with remote diagnostics
13.2.1 Problems with implementation
13.3 The EOS project
13.3.1 The EOS server 13.3.2 The EOS lookup server
13.3.3 Concrete use cases of the EOS prototypes
13.4 Outlook

From the perspective of the machine and plant operators, the heterogeneous teleservice offering of the various manufacturers requires considerable integration and administration effort. The use of remote access for internal operator communication requirements is usually not planned. In addition, incompatibilities between different software versions and a lack of familiarity with the special teleservice tools lead to the failure of remote support in hot incident scenarios. The solution to these problems was the subject of the joint project EOS, funded by the Federal Ministry of Education and Research (BMBF) within the framework concept Research for the Production of Tomorrow and supervised by the BMBF project management organization for production and manufacturing technologies, Forschungszentrum Karlsruhe. The aim of the joint project was to develop a reference architecture for remote services that can be used by both machine manufacturers and machine operators. The solution to be developed should be characterized by extensive use of Internet standards, be able to be operated by the operator with minimal administration and not restrict the differentiation options of the manufacturer's offering. In order to prevent unauthorized access by third parties, it should be possible to implement all of the operator's security systems. In addition to the technical challenges, there was a particular interest in involving the service and maintenance staff involved in order to ensure broad acceptance.