Integration of SIMATIC PCS 7 Asset Management into existing projects

Transcription

1 Application Example 10/2010 Integration of SIMATIC PCS 7 Asset Management into existing projects SIMATIC PCS 7

2 Warranty and liability Warranty and liability Note The Application Examples are not binding and do not claim to be complete regarding configuration, equipping and any eventuality. The Application Examples do not represent customer-specific solutions. They are only intended to provide support for typical applications. You are responsible for proper operation of the described products. These application examples do not relieve you of the responsibility to use safe practices in application, installation, operation and maintenance. When using these Application Examples, you recognize that we cannot be made liable for any damage/claims beyond the liability clause described. We reserve the right to make changes to these Application Examples at any time without prior notice. If there are any deviations between the recommendations provided in these Application Examples and other Siemens publications e.g. Catalogs the contents of the other documents have priority. We do not accept any liability for the information contained in this document. Any claims against us based on whatever legal reason resulting from the use of the examples, information, programs, engineering and performance data etc., described in this Application Example shall be excluded. Such an exclusion shall not apply in the case of mandatory liability, e.g. under the German Product Liability Act ("Produkthaftungsgesetz"), in case of intent, gross negligence, or injury of life, body or health, guarantee for the quality of a product, fraudulent concealment of a deficiency or breach of a condition which goes to the root of the contract ("wesentliche Vertragspflichten"). The damages for a breach of a substantial contractual obligation are, however, limited to the foreseeable damage, typical for the type of contract, except in the event of intent or gross negligence or injury to life, body or health. The above provisions do not imply a change of the burden of proof to your detriment. Any form of duplication or distribution of these Application Examples or excerpts hereof is prohibited without the expressed consent of the Siemens AG. Security information Siemens provides products and solutions with industrial security functions that support the secure operation of plants, systems, machines, and networks. In order to protect plants, systems, machines and networks against cyber threats, it is necessary to implement and continuously maintain a holistic, state-of-the-art industrial security concept. Siemens products and solutions only form one element of such a concept. Customer is responsible for preventing unauthorized access to plants, systems, machines and networks. Systems, machines and components should only be connected to the enterprise network or the internet if and to the extent necessary and with appropriate security measures (e.g. use of firewalls and network segmentation) in place. In addition, you should pay attention to Siemens recommendations on appropriate protective measures. For more information about industrial security, visit The products and solutions from Siemens undergo continuous development to make them even more secure. Siemens strongly recommends applying product updates as soon as available and using only the most recent product versions. Using versions that are obsolete or are no longer supported can increase the risk of cyber threats. To ensure that you are always kept informed about product updates, subscribe to the Siemens industrial security RSS feed at Entry ID: , V1.1, 10/2010 2

3 Table of contents Table of contents Warranty and liability Overview Preparations Plant structure Required software and licenses PC and communication settings Necessary default settings in the SIMATIC Manager Preparation of non-pcs 7-conform projects Configuration Creation of PC stations in the multiproject Monitoring of network objects and PCs by SNMP Configuring and creating the diagnostics structure Concluding activities Compiling and downloading Assigning the server data Activate detailed diagnostics (for PCS 7 V7.0) Service and Support References History Entry ID: , V1.1, 10/2010 3

4 1 Overview 1 Overview Introduction The purpose of this application is to incorporate the integrated Asset Management into an existing PCS 7 project. The document describes the conditions and the actions required to prepare PCS 7 projects mainly of the versions V5.x and V6.0 for the integration of Asset Management. Note The basic system description of the SIMATIC PCS 7 Asset Management can be found in the manual PCS 7 Process Control System - Operator Station in Chapter Use of the PCS 7 Maintenance Station and in the Manual PCS 7 Process Control System - Maintenance Station. Main contents The main focus for the incorporation of the integrated Asset Management into an existing project rests on the following key tasks: Preparatory activities Engineering and configuring Asset Management Environment of creation of document The screenshots have been made with PCS 7 V7.0 SP1. Validity This document is valid up to and including SIMATIC PCS 7 V7.1. Entry ID: , V1.1, 10/2010 4

5 2 Preparations 2 Preparations 2.1 Plant structure This description is based on a server-client architecture in which the Maintenance Server (MS Server) is configure d on a separate PC station and the Maintenance Client (MS Client) is configure d on the Engineering Station. MS Server and MS Client are connected both to the terminal bus and to the plant bus here. Note A PCS 7 OS Server BCE must be used for the case described here of a separate MS Server. It is connected to the plant bus and terminal bus via two standard network cards. With few exceptions, which are due to client-server settings, this document can also be used for an ES/OS single-user architecture. Entry ID: , V1.1, 10/2010 5

6 2 Preparations 2.2 Required software and licenses The following table lists the installations and licenses for the ES/MS Client and the OS server using PCS 7 V7.0 as an example. Table 2-1 ES/MS client SIMATIC station Required software Required licenses Package installation ES with PDM (for use of intelligent field devices or ASSETMON functionality) PCS 7 Engineering V7.0 PCS 7 ASSET Engineering V7.0 PCS 7 OS Client V7.0 PDM PCS 7 V6.0 (optional) OS Server Package installation OS server PCS 7 OS Software V7.0 OS client Package installation OS client PCS 7 OS Client V7.0 MS Server Package installation MS Server PCS 7 OS Software V7.0 PCS 7 Asset Runtime Basic Package V7.0 PCS 7 Asset Runtime V7.0 (tags) Note For more information on software and licenses, please refer to the manual. "PCS 7 PC configuration and authorizations" Entry ID: , V1.1, 10/2010 6

7 3.1 PC and communication settings If you monitor the network components at the plant bus with a Maintenance Station and if you use a CP 1613 or CP 1623 for access, the following steps are required for older types of computers: Install SIMATIC CP 1613 NDIS adapter ConFigure SIMATIC CP 1613 NDIS adapter Perform these steps as described for every CP 1613 of the MS Server in the following table. Note On more recent types of computer the mini-port adapter replaces the NDIS adapter. It is already preinstalled. Installing the NDIS Adapter The following table describes the installation of the SIMATIC CP 1613 NDIS adapter, which has to be carried out on the MS server. 1. Open Hardware wizard by selecting Start > Settings > Control Panel > Add Hardware. Figure 3-1 Entry ID: , V1.1, 10/2010 7

8 2. Click on the Next" button. Figure Select the option Yes, I have already connected the hardware and confirm with the Next button. Figure 3-3 Entry ID: , V1.1, 10/2010 8

9 4. From the list, select the entry Add a new hardware device" and click on the Next" button. Figure Select the option "Install the hardware that I manually select from a list" and click on the "Next button. Figure 3-5 Entry ID: , V1.1, 10/2010 9

10 6. Select the entry "Network adapters" in the list and confirm your selection by clicking the "Next button. Figure Under "Manufacturer" select the entry "SIEMENS AG" and under Network Adapter" select the entry "SIMATIC CP 1613 NDIS Adapter". Then click on the "Next" button. Figure 3-7 Entry ID: , V1.1, 10/

11 8. Click the "Next" button to start the installation. Figure 3-8 Note If you get a Windows Logo Test warning during the installation, proceed by clicking on the button "Continue Anyway". Entry ID: , V1.1, 10/

12 9. Complete the installation by clicking on the "Finish button. Figure Restart the computer now. Entry ID: , V1.1, 10/

13 Configuring the NDIS adapter In the following, the configuring of the SIMATIC CP 1613 NDIS adapter on the MS server is explained. 1. Open the settings of the network connections via Start > Settings > Network Connections. Figure Open the advanced settings of the Network Connections via the menu Advanced > Advanced Settings. Figure 3-11 Entry ID: , V1.1, 10/

14 3. The terminal bus adapter must always be in the first position. The position can be set using the corresponding buttons. Figure Go to the detail view via the menu "View > Details". Figure 3-13 Entry ID: , V1.1, 10/

15 5. Select the NDIS adapter "SIMATIC CP 1613 NDIS Adapter", open its context menu and select "Rename". Assign a descriptive name such as, for example, Plant_bus_NDIS". Figure Select the "Properties" menu command in the context menu. Select the NDIS adapter "SIMATIC CP 1613 NDIS Adapter", open its context menu and select "Properties". Figure 3-15 Entry ID: , V1.1, 10/

16 7. In the list, select "Internet Protocol (TCP/IP)" and open the corresponding properties with the button "Properties". Figure Select the option "Use the following IP address" and enter the desired IP address and subnet mask. Note that the NDIS adapter and the actual plant bus belong to different networks. Confirm your settings with "OK". Figure Close the window "Properties of (the network connection)". Entry ID: , V1.1, 10/

17 Assignment of IP networks ConFigure the plant bus, the terminal bus and the NDIS/Miniport adapter such that they are located in different IP networks. Setting up the SNMP service Set up the SNMP service on the PCs to be monitored as described in the following. 1. Open programs and features via "Start > "Settings > Control Panel > Remove or Change Programs". Figure 3-18 Entry ID: , V1.1, 10/

18 2. In the left navigation bar click the "Add/Remove Windows Components" button. Figure In the list, mark "Management and Monitoring Tools" and click the "Details button. Figure 3-20 Entry ID: , V1.1, 10/

19 4. Tick "Simple Network Management Protocol". Confirm your selection with "OK". Figure 3-21 Installing the DiagMonitor The DiagMonitor software monitors, signals, alarms and visualizes the operating states of SIMATIC PCs in an application-specific way. Install the SIMATIC DiagMonitor software on all PCs to be monitored. This software is included in the delivery scope of PCS 7 Bundle PCs. (see entry SIMATIC PC DiagMonitor V3.1 (Software) now available ). For further information, please refer to the PCS 7 - PC configuration and authorization manual, chapter DiagMonitor. Note From PCS 7 V7.1 the web server interface must be activated if the Diagnostics monitor is used. Entry ID: , V1.1, 10/

20 3.2 Necessary default settings in the SIMATIC Manager Default settings and checks are required in SIMATIC Manager for Asset Management both in the Component View and in the Process Device Plant View. The following settings must be checked in the Component View of SIMATIC Manager: Assignment of message numbers Check whether all projects of the multiproject have the same message concept. 1. For this purpose mark the CPU and call the corresponding context menu with the right mouse button. Select "Special Object Properties > Message Numbers...". Figure Check here whether the projects coincide. Version of the module library used Make sure that your multiproject uses only driver modules which were taken from the PCS 7 Library V6.1 SP1 or a more recent version. They are required for the utilization of Asset Management. Note If you have used older driver modules and update them with the required versions, an AS download in stop will be necessary due to the interface changes of the driver modules. Entry ID: , V1.1, 10/

21 Module drivers Check whether the module drivers were created faultlessly (see report). Compilation mode Check whether the OS compilation modes have been set to "area-oriented" for all subprojects of the multiproject which contain an OS. This is a prerequisite for the utilization of Asset Management. 1. For this purpose select a subproject and in the menu bar select Options > "Compile Multiple OSs" Wizard > Compilation Mode...". Note There must be at least one hierarchy folder for the selected project in the PH. Figure 3-23 Entry ID: , V1.1, 10/

22 2. Select Area-oriented and confirm by clicking on OK. Figure 3-24 Maintenance station settings 1. Mark the multiproject and select via the menu option "Options > SIMATIC PDM > Settings...". Figure 3-25 Entry ID: , V1.1, 10/

23 2. In the window which opens now go to the "Maintenance Station" tab and check whether the specified path is the same path as that of your multiproject. If this is not the case, correct the storage path using the buttons "Current multiproject" or "Search...". Figure 3-26 Note If PDM is used, the PDM Asset Service must be started / restarted after the assignment of the current multiproject. Assignment of the field devices The following settings must be checked in the Process Device Plant View of SIMATIC Manager. 1. Open the Process Device Plant View and check whether all devices have been assigned. Unassigned devices are grayed out. Figure 3-27 Entry ID: , V1.1, 10/

24 2. Assign a sensor type to the unspecified devices. For this purpose open PDM via the device context menu "Open Object". Figure Log on as a Specialist. Figure 3-29 Entry ID: , V1.1, 10/

25 4. Carry out an automatic detection by clicking on the "Device identification button. Figure If the device cannot be accessed online, you can perform the assignment manually. For this purpose select the connected sensor from the list. Figure 3-31 Entry ID: , V1.1, 10/

26 6. For devices which have already been configure d, upload the current configuration from the device using the "Upload to PG/PC button. Figure 3-32 Plant hierarchy The plant hierarchies must have the same settings in all the multiproject projects. You can check this in SIMATIC Manager via "Options > Plant Hierarchy > Settings...". All projects must have the 6 PH levels which are required for Asset Management. Figure 3-33 Entry ID: , V1.1, 10/

27 Consistency check Compiling the OS The check of the consistency between projects should be completed successfully (e.g. the names of the S7 programs are unequivocal across the whole multiproject, S7 program names should not contain any blanks). The option "Picture Tree" must be activated during the OS compilation. Figure 3-34 Naming of components in the Hardware Configuration The names of all components (e.g. stations, modules) should not be longer than 14 characters and should be unequivocal. The function Generate module drivers uses this name to create the respective driver module, which is displayed in the diagnostics area. The name is cut after 14 characters and _1 is added as an ending. This ensures that it is unequivocal in the CFC. A CFC module can consist of a maximum of 16 characters. Note The name of the AS station in the component view in SIMATIC Manager should not be longer than 14 characters. If it is necessary to record information in more than 14 characters, this can be done in the comment of each component. Tests from the comment fields are additionally displayed in the Asset Management faceplates. Entry ID: , V1.1, 10/

28 3.3 Preparation of non-pcs 7-conform projects With a PCS 7-conform configuration the PLT are stored in the AS project plant hierarchy according to the picture hierarchy. Projects which have not yet derived the picture hierarchy from the PH must observe the following additional points. If in this context your project is PCS 7 conform, you can skip this chapter. 1. In SIMATIC Manager open the context menu of the multiproject folder and select Plant Hierarchy > Settings...". Tick "Derive picture hierarchy from the plant hierarchy". Figure 3-35 Entry ID: , V1.1, 10/

29 2. The Picture Tree must be identical with the plant hierarchy (PH) of the OS project. For this purpose select the OS Server project and open WinCC Explorer via the OS project context menu, the select "Open Object". Figure Open the Picture Tree Manager. Figure 3-37 Entry ID: , V1.1, 10/

30 4. Recreate the Picture Tree in the Plant View of the OS project now by creating the respective PH folders. Figure In the Component View of SIMATIC Manager, select the OS project of the OS server, open its context menu and select "Import WinCC Objects". Figure 3-39 Entry ID: , V1.1, 10/

31 Note For the import of the WinCC objects, the names both of the pictures and of the reports have a maximum 24 characters. 6. Assign the pictures to the PH folders by cutting the pictures from the Component View and pasting them into the Plant View in the hierarchy. Figure 3-40b 7. Switch to the Plant view of the SIMATIC manager. 8. For the area-oriented compilation the PH structure of the AS projects must be recreated in the PH structure of the OS project now. Figure 3-41 Entry ID: , V1.1, 10/

32 Note No pictures may be pasted here. The recreation is required only up to the OS area level set. If subordinate hierarchy folders exist in the AS project, they need not be recreated in the OS project. 9. Select an area in the OS project, open the context menu and select "Object properties ". 10. Switch to the AS-OS Assignment" tab. 11. Under "Assigned OS:" assign the OS to the area. Figure 3-42 Entry ID: , V1.1, 10/

33 12. Remove tick from Picture Tree when compiling the OS server and maintenance server. Figure 3-43 Note However, the diagnostics hierarchy is still generated or updated when compiling the Maintenance Server. Entry ID: , V1.1, 10/

34 13. During the OS compilation warnings will be given due to the absence of pictures in the AS PH structure, but they can be safely ignored. Figure 3-44 Note In spite of the PH settings made to the no longer PCS7-conform project, the automatic generation of the module icons remains impossible even with the PCS 7 V7.0 SP1. The CFCs and SFCs are still not located in PH folders with the same name as the pictures which would be a requirement. Entry ID: , V1.1, 10/

35 4 Configuration 4 Configuration 4.1 Creation of PC stations in the multiproject Below you will find step-by-step instructions for the creation of the required PC stations. For detailed information about the individual configuration steps please refer to the SIMATIC Process Control System Operator Station, Chapter Configuration Steps at a Glance" Setting up the PC stations for the ES The PC station created here serves as Engineering Station. 1. Open the shortcut menu of the project in the component view and add a new PC station via "Insert New Object > SIMATIC PC station". Figure 4-1 Note The OS may not be deleted. Entry ID: , V1.1, 10/

36 4 Configuration 2. Open the HW Config of the PC station via the context menu. Figure Insert a WinCC Application and a CP ConFigure the "CP 1613" communication processor matched to your PCS 7 project (see "PCS 7 Engineering System Configuration Manual"). Figure 4-3 Entry ID: , V1.1, 10/

37 4 Configuration Note From PCS 7 V7.1 the following has to be observed: If PDM is used a PDM application must be incorporated into the PC station for the ES with the WinCC application. 5. Open "Object Properties..." of the PC station. 6. In the "General" tab enter the station name of the component configurator under "Name:". A yellow arrow then appears in the icon of the PC station. Figure 4-4 Note Do not enter a name in the field "Computer name:" for this PC station. Entry ID: , V1.1, 10/

38 4 Configuration Setting up the PC station for the MS Client In the following you create the MS Client. The MS Client is an OS Client which is operated on the Engineering Station. 1. Create a PC station for the MS Client analogously to "Creation of the PC station for ES" and add to it a "WinCC Application Client". Figure Use the context menu of the PC station to open Object Properties In the "General" tab you can enter a freely selectable name in "Name:". 4. It is important that you enter the name of the master ES for "Computer name:". Figure 4-6 Entry ID: , V1.1, 10/

39 4 Configuration Creation of the PC station for the MS Server In the following you create the MS Client. Depending on the plant architecture it can be designed as a stand-alone or redundant server. 1. Create a PC station for the MS Client analogously to "Creation of the PC station for ES" and add to it a "WinCC Application". Figure Use the context menu of the PC station to open Object Properties In the "General" tab you can enter a freely selectable name in "Name:". Entry ID: , V1.1, 10/

40 4 Configuration 4. Enter the Windows computer name of the destination computer for Computer name:. Figure Optional: If the MS server is designed redundant, create an additional PC station for the MS Server Stby and add a WinCC Application (Stby)" to it. Figure 4-9 Entry ID: , V1.1, 10/

41 4 Configuration 6. Open the Object Properties... via the context menu of the PC station. 7. In the "General" tab you can enter a freely selectable name in "Name:". 8. Enter the Windows computer name of the destination computer for Computer name:. Figure 4-10 Entry ID: , V1.1, 10/

42 4 Configuration 4.2 Monitoring of network objects and PCs by SNMP In the following you create the OPC Server in the component configurator on the MS Server. It is needed to process the information of the PC stations and switches via SNMP. Profile and community of the components The following table shows diverse components with their profile and their community, using SIMATIC PCS 7 V7.0 and its community as an example. Table 4-1 Components Profile Community SCALANCE, X200-class Profil_SCALANCE_X200_V11.txt public SCALANCE, X200IRT-class Profil_SCALANCE_X200_V11.txt public SCALANCE, Class X300X400 V30 Profile SCALANCE X300X400_V30.txt public SCALANCE, Class X400 Profil_SCALANCE_X400_V11.txt public SCALANCE, Class X408 Profil_SCALANCE_X400_V22.txt public ESM/OSM Profil_OSM_V10.txt public IPC Profil_IPC_V13.txt SOL CP1613 communications processor MIB-II_V10.txt private Other devices e.g. network card; switches All devices which have been added by importing, but which are not to be displayed MIB-II_V10.txt No SNMP Determine the community configure d in the device. Entry ID: , V1.1, 10/

43 4 Configuration Configuration of the SIMATIC NET OPC Server Proceed as follows: 1. Open HW Config of the PC Server Station using its context menu and select "Open Object". 2. In the hardware catalog, find the OPC Server (path: "SIMATIC PC Station > User Application > OPC Server") and add it to the hardware configuration using drag & drop. Figure Open the properties of the OPC Server via the context menu "Object Properties...". 4. Go to the "SNMP" tab and enter a value between 100ms and 1000 ms for "Cycle time:". 5. Click the "Edit Plant Configuration..." button. Figure 4-12 Entry ID: , V1.1, 10/

44 4 Configuration 6. In the window which opens now you can state your SNMP components via the button "Add...". The following fields must be filled in for every SIEMENS component such as PC, switch, etc.: Name: (for PCs the name must be the same as the Windows computer name of the PC station in capital letters) IP Address: "Device profile: (see table) Community: (see table) TimeOut: 9000 (Standard) Tick "SNMP Optimization". A longer "Timeout, e.g. 30s, is recommended for large projects. Optionally you can add to the SNMP component a description under "Comment:". After entering all the components, exit the configuration window clicking the "OK button. Figure 4-13 Entry ID: , V1.1, 10/

45 4 Configuration 7. In the properties window of the OPC Server, now compile the SNMP variables by clicking the "Export Tags for WinCC button. Figure In the HW Config Editor of the MS Master Server select the OPC Server and copy it. Figure 4-15 Entry ID: , V1.1, 10/

46 4 Configuration 9. Open the hardware configuration of the MS stand-by server. 10. Select an empty line and add the copied OPC Server to the configuration. Figure 4-16 Note With this procedure you need not enter the SNMP components anew. Entry ID: , V1.1, 10/

47 4 Configuration 4.3 Configuring and creating the diagnostics structure The diagnostics structure is configured and created as described below. When PCS 7 is created, it generates several additional subfolders and diagnostic screens and automatically assigns the names to these folders/diagnostic screens. Note When the diagnostics structure has been created, the names of the hierarchy folders in the plant hierarchy which are relevant for the Maintenance Station may no longer be changed. 1. In SIMATIC Manager select the multiproject folder, open its context menu and select Plant Hierarchy > Settings...". 2. Tick "Derive diagnostics screens from the plant hierarchy". Figure 4-17 Entry ID: , V1.1, 10/

48 4 Configuration 3. Select the Maintenance Server as Maintenance Station and confirm your selection with "OK". Figure Optionally you can change the OS area ID of the diagnostics folder for the display in the OS. For this purpose, in the PH select the diagnostics folder "Diagnostics", open the context menu and select "Object Properties...". In the window that now opens, go to the "Control and Monitoring Attributes" tab. In "OS area ID:" you can now assign a unique name for the OS visualization. Figure 4-19 Note Please bear in mind that this change of the OS area ID is required for all projects of the multiproject, that you have to assign the same name and there is no automatic function for this. Entry ID: , V1.1, 10/

49 4 Configuration 5. In SIMATIC Manager select the multiproject folder and execute Options > Plant Hierarchy > Create/Update Diagnostic Screen...". Figure 4-20 Note With this selection the function "Create Module Driver" is called and the "Control and Monitoring" functionality of the driver blocks which are required for the visualization is activated (the ticks are set automatically). In addition, the diagnostics hierarchy, pictures and objects are created. Entry ID: , V1.1, 10/

50 5 Concluding activities 5 Concluding activities When you have carried out the required configuration steps you can start the following final activities. 5.1 Compiling and downloading 1. Download and compile the S7 programs of all AS stations. Note If you used older modules in the CFC charts and you updated them with the required versions, an AS download in stop will be necessary due to the interface changes of the driver modules. 2. Full OS Compile and download all OS servers and the Maintenance Server. Note Because the diagnostic screens are derived from the Plant Hierarchy a complete OS download will be necessary. 3. Download the PC station of the Maintenance Server Entry ID: , V1.1, 10/

51 5 Concluding activities 5.2 Assigning the server data Check in the MS Client project whether the server data of all required OS Servers and of the MS Server have been assigned. 1. For this purpose, in the SIMATIC Manager in MS Client select the OS Client Application, open its context menu and select "Assign OS server...". Figure Select the server data required and confirm with "OK". Figure 5-2 Entry ID: , V1.1, 10/

52 5 Concluding activities 5.3 Activate detailed diagnostics (for PCS 7 V7.0) Activate the detailed diagnostics in the object properties of the MS Client. Note Activation of the detailed diagnostics is possible and necessary only from the version PCS 7 V In SIMATIC Manager, open the context menu of the MS client and select "Object properties". Figure Go to the "Target OS and tick "Detailed diagnostics". Figure 5-4 Entry ID: , V1.1, 10/

53 6 Service and Support 6 Service and Support Industry Online Support Technical Support Do you have questions or need assistance? Using the Industry Online Support, you have round-the-clock access to expertise spanning the entire range of service and support, as well as to our services. The Industry Online Support is the central address for information about our products, solutions and services. Product information, manuals, downloads, FAQs and application examples all information can be accessed with just a few mouse clicks: The Siemens Industry Technical Support offers you fast and competent support for any technical queries you may have with a number of tailor-made solutions ranging from basic support to individual support contracts. Please send any queries to Technical Support via Web form: Range of services Our range of services includes the following: Product training courses Plant data services Spare parts services Repair services On-site and maintenance services Retrofitting and modernization services Service programs and contracts You can find detailed information on our range of services in the service catalog: Industry Online Support App Contact partners The "Siemens Industry Online Support" app provides you with optimum support, including while on the road. The app is available for Apple ios, Android and Windows Phone: If you want to request on-site service or need spare parts, please get in touch with your local Siemens representative, who will put you in contact with the responsible service center. You can find your contact partner in the contact database: Entry ID: , V1.1, 10/

54 7 References 7 References Table 7-1 Topic \1\ Siemens Industry Online Support \2\ Download page of this entry 8 History Table 8-1 Version Date Change V1.0 03/2010 First edition V1.1 10/2010 Text adaptations Entry ID: , V1.1, 10/