Integrated approach to the development of the ITER control system configuration data

ITER control system (CODAC) will rely on a large number of configuration data, coming from different sources. This information is being created using different tools, stored in various databases and, generally, has different life-cycle. In many cases it is difficult for instrumentation and control (IC) engineers to have a common view on this information or to check data consistency. The plant system profile database, described in this paper, tries to address these issues by gathering all IC-specific information in the same database and providing means to analyze these data. At the design phase, the current ITER infrastructure and CODAC practices have been evaluated, and the following architectural and software decisions have been made: -1) the database back-end should be Microsoft SQL Server; -2) the application should have web interface; -3) business logic and the user interface should be written in Java. Prime Faces should be used for the user interface, Spring for transactional support and Java Hibernate for interaction with the database; and -4) data integration tool should be Talend. The task was launched in September 2010; in February 2011 the first version was put in production, and it was gradually introduced into CODAC processes in the following months