Quelltext der Seite Concept of a Migration Process from a Database-Based Device Type Configuration System to a Model-Driven System

{{Vortrag
|vortragender=Malte Püschner
|email=malte.pueschner@student.kit.edu
|vortragssprache=Deutsch
|vortragstyp=Masterarbeit
|betreuer=Thomas Weber
|termin=Institutsseminar/2026-01-09
|vortragsmodus=in Präsenz
|kurzfassung=Automation is used in factories to reduce manual labor. With an increasing level of automation, more and more devices are used to act, measure, and control the factory. Multiple vendors offer various device types with different functionalities; for example, motors for moving conveyor belts, sensors like light barriers, controllers to implement a specific behavior, and interface devices used to connect all devices and to reduce wiring.

To enable the concurrent use of products of different vendors, they communicate with
standardized protocols. To program a controller, an engineering tool is used to describe the
topology of the system such that the programmer of the controller knows how to access
data received from and how to send data to different devices. Device configuration files are
imported into the engineering tool to provide information about the process data a device
sends and expects to receive, about parameters that can be used to alter the behavior of
a device, and about what diagnostic data the controller can expect from a device.Those
configuration files are dependent on the protocol that is used for communication. One
device type can support multiple protocols; therefore, multiple configuration files need to
be provided for that device type. Since such configuration files can easily exceed thousands
of lines in length, it is not efficient to write them by hand. Therefore, typically a generator
is used to generate the configuration files based on some kind of description of the device
type. We call the process of describing device types device type configuration and the
system that is used for the process device type configuration system (DTCS).
We propose a migration process from a database-based DTCS to a multi-level modeling
DTCS. First, we analyze an industrial database-based DTCS to derive requirements for a
DTCS. Then we present our migration process, which results in an FMMLx multi-level
model with six levels.
We evaluate the migration process with an expert survey. A model-driven approach
enables model checking and consistent device types. Multi-level models enable the reuse
of parts of the domain specific language.
}}