fig1 shows in abstracted form the links within a representation of an industrial system . the industrial system has four lines 1 , 2 , 3 , 4 in the embodiment presented in fig1 . line 1 in its turn includes four machines 10 , 12 , 14 , 16 . this can be in relation to a line for the filling of bottles with beverages , whereby each machine executes am appropriate work - stage within the line , maybe the washing and arranging of the bottles , the filling , the sealing of the bottles and the labelling of the bottles . the machine in its turn includes four components 110 , 112 , 114 , 116 . obviously the lines 2 , 3 & amp ; 4 and the machines 12 , 14 , 16 also include several machines or components , but these are not shown for overviewing reasons . the presentation of the status data is arranged in a hierarchic structure . in addition , as per the invention , not only the status data for one machine is shown , but also in fact the status data of all of the machines of all of the lines . in this way it is possible to switch between the respective lines 1 , 2 , 3 , 4 as well as to navigate within the lines 1 , 2 , 3 , 4 . all of the data of the industrial system can be accessed in this way on one user unit . fig2 shows a flow - chart , which illustrates a possible navigation within the presentation . commencing from the starting point a , a line 1 is first of all selected . basically it is of course possible to also select one of the other lines 2 , 3 ,& amp ; 4 and to jump within a lines level between the different lines . the possibility exists within line 1 to select a specific machine of line 1 in a step 301 . if no selection is made the presentation remains unchanged and if a selection is made , e . g . that of machine 10 , the presentation will then be restricted to machine 10 . the possibility now arises of selecting a component of machine 10 in a step 302 . if no selection is made , another machine can be selected in a step 303 . it is also possible in this way to move horizontally within the machines level without performing the navigation via the roundabout way of the higher - ranking lines level . if another machine is selected , the information retrieval starts again from point b . should no other machine be selected , the possibility exists to jump back in one step 304 to the higher - ranking lines level , whereupon the information retrieval commences once more from point a . if no selection is made , the presentation remains unchanged . the information retrieval commences once more from point b . if a component , which is subordinate to the machine 10 is selected in step 302 , the presentation jumps to the components - level . basically another component can be selected here in a step 305 , so that a horizontal move at the components level is also possible without having to take a roundabout way via the machines level and the lines level . if no selection is made in the step 305 , a return can be made in a step 306 back to the machines level . if this selection is made , the information retrieval will be continued to point b for the respective machine , which includes the component 110 . should no selection be made in step 306 , a return can be made in step 306 directly to the lines level back in line 1 , which includes the machine 10 , which in turn includes the component 110 . the information retrieval then continues to point a . if this selection is also not made , the information retrieval will continue to point c and the presentation / display remains unchanged . fig3 shows a flow - chart , which illustrates a preferred way to deal with error messages within the presentation . if an error message is prompted at point x into the user unit , it will firstly be determined whether the error message concerns the line that is currently selected for display . if the selected line is not affected , then no action is taken and the information retrieval is restarted . obviously it can moreover also be arranged in a modified embodiment that instead of just ignoring the error message , a highlighting is made in the display that another line is the subject of an error message . should the selected line be affected , it will be determined in steps 402 , 403 , 404 , 405 & amp ; 406 , whether the message relates to a currently selected item , i . e . the currently selected machine or component or to a subordinate , higher - ranking , similar - ranking or to a subordinate object of a similar - ranking object . a status line is therefore arranged in the presentation , which clarifies the current position of the display in the hierarchic structure . with this , the currently selected line is displayed in the status line by an means of an icon , the currently selected machine by a further icon and the currently selected component by a third icon . accordingly there is a lines icon that is shown at the lines level . if a specific machine is selected , an icon for the selected machine will be displayed next to the corresponding lines icon . if a further component is selected , a third icon is added , which represents the selected component . a navigation within the display is possible via this icon . for example , a move back into the lines level can be made by selecting the corresponding line icon . it can also , for example , be arranged to equip the user unit with a touchscreen , which enables easy selection of the icon . after it has been determined in the steps 402 , 403 , 404 , 405 and 406 which object — i . e . which machine or component — is affected by the error message , one of the corresponding steps 407 , 408 , 409 , 410 & amp ; 412 is then followed in the signal words of an icon in the status line . when one of the corresponding aforementioned icons is selected , the corresponding signal words are amended . in this way a user can only follow the signal words with his / her selection in order to get to the object — i . e . machine or component — that is affected by an error message within the hierarchic structure . the user does not need to orientate him / herself within the hierarchic structure as this is enabled by a secure navigation particularly in stressful situations . fig4 shows a glow - chart , which presents a possible resolution for a conflict situation , in which a user with a mobile user unit is close to a machine , which has in addition a static operating unit . in this the term “ panel ” is used to describe a static operating unit . if a user of a mobile user unit is close to a machine , it can be ascertained in a step 401 as to whether a user is already utilizing the panel for monitoring and controlling the corresponding machine . if this should be the case , it is arranged that no take - over of the panel and of the control function of the machine is made . obviously , alternative arrangements can be made so that the user profiles are aligned and so that the control over the panel and the machine is transferred to the user who has been given a higher ranking in his / her user profile . should no user be logged - in on the panel , it can be checked in step 402 as to whether the panel is permanently assigned to a particular machine . should this not be the case , the current display of the mobile user unit is shown on the panel . the user can use the panel , which as a rule has larger and more convenient display and operating elements . if the panel should be dedicated to a particular machine , a check will be in a step 403 as to whether the currently selected machine on the mobile user unit corresponds to the dedicated machine . if this is the case , the current display of the mobile user unit will be shown on the panel and the user can utilize the panel with its more convenient operating elements for further operations . should this not be the case , a summary about the machine will be displayed on the panel , which is automatically adapted to the profile of the user , so that the user can only access the particular status data that are assigned to him / her via his / her profile . an automated transfer of operation of static user units is thus achieved in a convenient way , when a user with a mobile user unit is moving around within the industrial system and is close to a static user unit . fig5 shows a flow - chart that illustrates a possibility of how things can be handled in a conflict situation , in which two users wish to access the same object — i . e . a component or a machine . it is first of all established that several users wish to access the same machine or component . in this there is the situation where a first user having a first user profile is already accessing the machine or component and now a second user with a second profile also wishes to access the machine or component . it is established in step 501 as to whether the input of the second user is in relation to a matter of a critical safety function , for example the stoppage of a machine based upon an error message . should this not be the case , a user switching will be made . obviously it can in addition be arranged here that the user switching will be refused despite everything , depending on the profiles of the first and second users . if it should be a matter if critical safety function , then it will be established in a step 502 as to which user has a higher authorisation or ranking . these values are on file in the respective user profile . should the second user have a lower authorisation or ranking , the change will be refused and the second user &# 39 ; s input will be ignored . should the second user have a higher authorisation or ranking , he / she has to confirm , as a further stage in step 503 , that he / she wishes to make a critical safety input . should he / she not confirm this , no user switch will be made and the input of the second user will be ignored . should he / she also confirm this safety step 503 , the user switch will be made and the input of the second user accepted . the second user is now logged - in to the appropriate machine and has the sole control over the machine . in this way it is simply ensured that in a case of critical safety , particularly when several users with mobile user units receive an error message and wish to correct this , only the input will be executed of the user with the highest ranking or authorisation for the case in question . all of the aforementioned examples have been given for an industrial system that has the three levels of line , machine and component . obviously the invention can be utilized for an industrial system with fewer or more than three levels . in particular , this invention can also be utilized in other applications than bottling plants for beverages .