The self-description data configuration model

ITER will consist of roughly 160 plant systems I&C delivered in kind which need to be integrated into the ITER control infrastructure. To make the integration of all these plant systems I&C, a smooth operation, the CODAC (Controls, Data Access & Communications) group release every year the core software environment which consists of many applications. In this paper we would like to describe what configuration data and how it is modeled in the version 2. The model is based on three views, the physical one which lists the components with their signals, the functional view which describes the control functions and variables required to implement them and the control view which links the two previous views. We use Hibernate as an ORM (Object Relational Mapping) framework with a PostgreSQL database and Spring as a framework to handle transactions.

► We use the relational model to represent the configuration data for ITER.
► We explain the different modeled views namely physical, functional and control.
► We explain how this information is used to generate configuration files.
► We explain that this information is validated.