The APS section provides comprehensive software solutions in the following areas:
- Settings generation and management (InCA/LSA, CESAR);
- Operations automation (Sequencers);
- Services for monitoring (Fix Display Framework, Concentrators [BLM, BPM + SPS], OASIS server & client [with CO/SRC]);
- Services related to machine protection (SIS, Post-Mortem Analysis [with TE/MPE] IQC [LHC + SPS], XPOC);
- Monitoring and Diagnostic tools (DIAMON and LASER);
- Generic, data-driven applications, components and libraries for accelerator control (WS/Knobs, ASC Beans, JAPC, JDataviewer, Timing applications [with CO/SRC]).
The members of the section carry out the following tasks:
- All aspects related to developing these services and making sure they fulfil their purpose over the years, taking a leading role in all technical matters, collaborating with the operators and equipment specialists and partners*. This covers requirement analysis and data modelling, design and implementation of the corresponding data repositories, server-side processes, client APIs and generic user-oriented applications.
- The development of generic software components to be used by all application software aimed at accelerator control developed inside or outside of the Controls group, as well as general-purpose client APIs to allow access to specialist applications.
The section provides a coherent suite of tools to all Java developers in the accelerator sector: an Eclipse distribution, a build tool (CommonBuild and CBNG), and tools to deploy software on consoles and servers (Console Manager, jws and the deploy tool). It provides expertise in using these tools, as well as guidance and assistance in software development in the Java ecosystem, always with a focus on quality, and the re-use of standard solutions.
The Applications section is not responsible for providing equipment-specific applications nor expert applications; this is the responsibility of BE/OP and/or the equipment specialists. It can however ensure basic support of such applications in the absence of the primary developer under the condition that they have been developed following the guidelines and using the components and infrastructure provided by the section.