David Kampert

Modeling asset information for interoperable software systems

Software of various domains needs to access information on assets in an industrial facility. For this purpose, it is not only necessary to provide the required technical infrastructure, but also to have a common understanding of the way assets are modeled. Since globally valid models are currently not available, sharing asset information between different software tools is hard to accomplish. In this paper, a basic model for information on assets is introduced, which only involves the common, fundamental concepts. The model is described both on a semantical level and with respect to its implementation. Finally, an outlook on the integration in a service-oriented architecture is given.

A service interface for exchange of property information

The flexible application of automation systems in an industrial environment requires new concepts of information exchange in order to keep configuration efforts low. Since the number of networked automation systems constantly increases, the challenge is to make these systems interact without standardizing extensive information models for each and every use-case. As a common and generic tool, system properties are used to model systems and suffice different communication tasks. In this paper, a concept for information exchange by means of services is introduced for property-based system models. The services are specified with respect to function, integration and use. Groups of services that comply with typical applications are identified. The applicability of the services across different domains is illustrated in a use-case scenario.

Model based synthesis of automation functionality

Abstract The article demonstrates the advantages of meta-model-based solutions for multi-aspect automation tasks. Multi-aspect tasks require solutions that consider information of multiple system aspects simultaneously. In todays practice, these aspects are maintained in different tools which make implicitly use of tool-driven system models. In contrast, we propose to prioritize the models in order to facilitate the handling of multi-aspect automation tasks. The article exemplifies this idea by introducing typical automation and engineering models and illustrates their utility in a use-case example.

Outside-in: Simplifying systems by integrating the outside perspective

The more complex technical systems grow, the more important abstract system characteristics become apart from the actual implementations characteristics. The abstract viewpoint facilitates system development and inter-system interaction, which is also useful inside a system during its operation. This can be achieved by inverting the encapsulation principle: Hiding the outside of a system from the inside, instead of hiding the inside from the outside. In comparison, the resulting systems are simpler and more flexible. This paper points out how and to what extent the required abstract system models can be created and integrated in system development and exploited on runtime.

Operative Verwendung merkmalbasierter Information in der Automatisierung

1 Konstruktionstechnik/Maschinenelemente 2 Fertigungstechnik 3 Verfahrenstechnik 4 Bauingenieurwesen 5 Grundund Werkstoffe/Kunststoffe 6 Energietechnik 7 Strömungstechnik 8 Mess-, Steuerungsund Regelungstechnik 9 Elektronik/Mikround Nanotechnik 10 Informatik/Kommunikation 11 Schwingungstechnik 12 Verkehrstechnik/Fahrzeugtechnik 13 Fördertechnik/Logistik 14 Landtechnik/Lebensmitteltechnik 15 Umwelttechnik 16 Technik und Wirtschaft 17 Biotechnik/Medizintechnik 18 Mechanik/Bruchmechanik 19 Wärmetechnik/Kältetechnik 20 Rechnerunterstützte Verfahren (CAD, CAM, CAE CAQ, CIM . . . ) 21 Elektrotechnik 22 Mensch-Maschine-Systeme 23 Technische Gebäudeausrüstung

Model-Based Management of Asset Information

Software tools for engineering tasks typically aim at welldefined aspects of an overall project, for which they employ domain-specific models. Managing information on assets is an important cross-sectional task, which makes the exchange of information valuable to many domains. In order to enable software tools to exchange information, the underlying meta-model needs to be open and common. This primarily accounts for the contents of the meta-model (what is modeled), which is a different issue than the question how the model is technically represented. Hence, in this article the combination of an appropriate meta-model for asset information along with its integration into a service-oriented architecture is discussed from a conceptual perspective. It is not intentended to provide details of a possible implementation.