Billen, R.

Paper	Title	Page
TUB001	Accelerator Data Foundation: How It All Fits Together	61
	R. Billen, P. Le Roux, M. Peryt, C. Roderick, Z. Zaharieva CERN, Geneva
	Since 2003, a coherent data management approach was envisaged for the needs of installing, commissioning, operating and maintaining the LHC. Data repositories in the distinct domains of physical equipment, installed components, controls configuration and operational data have been established to cater for these different aspects. The interdependencies between the domains have been implemented as a distributed database. This approach, based on a very wide data foundation, has been used for the LHC and is being extended to the CERN accelerator complex.
	Slides
TUP013	On-change Publishing of Database Resident Control System Data	120
	K. Kostro, R. Billen, C. Roderick CERN, Geneva
	The CERN accelerator control system is largely data driven, based on a distributed Oracle database architecture. Many application programs depend on the latest values of key pieces of information such as beam mode and accelerator mode. Rather than taking the non-scalable approach of polling the database for the latest values, the CERN control system addresses this requirement by making use of the Oracle Advanced Queuing - a Java Messaging Service (JMS) implementation - to publish data changes throughout the control system via the CERN Controls Middleware (CMW). This paper will describe the architecture of the system, the implementation choices and the experience so far.
	Poster
WEP005	The LHC Logging Service: Handling Terabytes of On-line Data	414
	C. Roderick, R. Billen, R. D. Gaspar Aparicio, E. B. Grancher, A. Khodabandeh, N. Segura Chinchilla CERN, Geneva
	Based on previous experience with LEP, a long-term data logging service for the LHC was developed and put in place in 2003, several years before beam operation. The scope of the logging service covers the evolution over time of data acquisitions on accelerator equipment and beam related parameters. The intention is to keep all this time-series data on-line for the lifetime of LHC, allowing easy data comparisons with previous years. The LHC hardware commissioning has used this service extensively prior to the first beams in 2008 and even more so in 2009. Current data writing rates exceed 10TB/year and continue to increase. The high data volumes and throughput rates, in writing as well as in reading, require special arrangements on data organization and data access methods.
	Poster
WEP006	The LSA Database to Drive the Accelerator Settings	417
	C. Roderick, R. Billen CERN, Geneva
	The LHC-era Software Architecture (LSA) used to operate the particle accelerators at CERN is dependent on an online database to manage both high and low level parameter settings, including their evolution over time. Accelerator optics models, control sequences, reference values, are amongst the other entities being managed within the database. The LSA database can be considered as being located between the operators and the accelerators; therefore performance, availability, and security of the service as well as data integrity are paramount. To meet these requirements the LSA database model has been carefully developed, all database access is tightly controlled and instrumented, business logic is implemented within the database, and there is a semi-automatic integration with other key accelerator databases. Currently 7 million settings for some 40 thousand devices of the LEIR, SPS, and LHC accelerators are being effectively managed.
	Poster
THP108	Rapid Development of Database Interfaces with Oracle APEX, Used for the Controls Systems at CERN	883
	Z. Zaharieva, R. Billen CERN, Geneva
	The need to rapidly prototype, build and deploy applications and to be able to react immediately to the changing user requirements is a challenge facing every enterprise. CERN - the largest particle research centre in the world - has tremendous data storage requirements, encompassing many different databases and has to quickly provide interfaces to visualize the data. This article will cover how Oracle APEX has been used to build several different database-centric interfaces related to the accelerator complex. Real-world applications will be discussed and it will be shown how Oracle APEX has met the preliminary requirements of the application developers and the user community at CERN. The article will address the question of when APEX could be a suitable choice of application development technology, and will share a developer's first-hand experience of both the good and bad points.
	Poster