Conception and implementation

Conception and implementation of a resource cockpit for maintenance

Architecture and Technology of the Resource Cockpit

To maintain data security and a task-related functionality selection, user guidance in the resource cockpit is essential. On the one hand, it is determined by the role concept which rights the user can execute and, on the other hand, to which equipment he is authorized to access. For this purpose, the user is assigned qualifications and certificates, according to which a selection of maintenance and fault orders can be made, for which the maintenance engineer is suitable.

Due to the roles, the rights do not have to be assigned for each user, instead a grouping takes place. The roles include various forms of authorization to access functions offered by the resource cockpit. This can be the display of list and detail pages or the restriction of the display of content such as plans or plant documentation, as required by the manufacturers.

Since the resource cockpit should primarily be used for larger machinery, it is essential to group the systems under consideration. Lich. The grouping takes place here mainly on technical aspects. A role can apply to several resource groups, but on the other hand, a resource group is generally assigned several roles. A resource group includes several resources, it is possible to add a resource to multiple resource groups. The resources can be assigned to plug-ins, which can be used to establish a direct connection to the control unit of the plant, especially according to the OPC UA standard.
Concrete troubleshooting and maintenance orders are assigned concrete resources. The known error codes and maintenance instructions on which these orders are based are summarized in catalogs.

Equipment is assigned to the catalogs and thus also to the orders; tools and spare parts are combined under this term.

Applied technologies

The Resource Cockpit runs on Microsoft Internet Information Services. However, these must only be installed on a computer in the company network, which then access the other devices via Web browser as clients.
On the server side, resource cockpit web pages are coded in Razor syntax using the C # programming language. This is integrated into the usual Webtechno┬Člogie with HTML 5 and CSS 3. Program logic that needs to run on the client has been developed using JavaScript. The distribution of the source text follows the MVC pattern. The advantages of this design pattern for the development process have already been explained in the previous chapter.

The data is no longer stored in a relational database, but in the RDF database BrightstarDB. RDF stands for Resource Description Framework, which is considered a fundamental building block of the Semantic
Web. The data is represented by a triple of subject, predicate and object. A database server becomes redundant.

The Resource Cockpit provides a framework that allows users to expand according to their needs. This includes modifying the user interface according to the corporate identity, defining plug-ins for your own
systems or adding additional web pages with context-specific functions. The communication with the resource cockpit takes place via the formats JSON and XML.

Functions of the resource cockpit

Upon successful login, the user will be greeted with a dashboard. This shows him whether there are errors or maintenance that he could take responsibility for processing. If unread messages are available to the user, they will be notified. It also gives an overview of which personal user interface configurations have been saved.

The dashboard is in this expansion stage only a suggestion. The design and the information to be displayed must be adapted to the needs of the company using the resource cockpit. The Resource Cockpit is available in German and English. The user can configure the surface of the resource cockpit according to his preferences. Thus, it can move the order of columns or show and hide columns, define filters and sorting criteria, and determine how many records per page should be displayed. These configurations are stored on a per-user basis so that the user will find the same data the next time they call.