UNICOS was born at CERN in early 2001 with the development of the LHC cryogenics control system. It deals with the two upper layers of a classical control system: Supervision and Control. UNICOS proposes a method to design and develop the control application which will run in commercial off-the-shelf products (e.g. SCADA and PLCs).
The UNICOS HMI was developed more than 15 years ago and has since then evolved with contributions of tons of developers. The overall set of panels constituting the UNICOS HMI is therefore outdated and heterogeneous. CERN wishes to modernize and homogenize the UNICOS user experience for its open source release by first updating and unifying its visual identity.
The primary objective of the rebranding is to systematically upgrade the visual aesthetics of all Human-Machine Interface (HMI) panels, bringing them in line with modern design standards. This initiative is crucial for improving both the usability and visual appeal of the system, ensuring that it remains competitive and user-friendly in today's fast-evolving technological landscape.
The existing interface is complicated as key functionalities are buried within complex menus, making it challenging for users to complete tasks efficiently.
In UNICOS, colors play a critical role as the framework is designed to represent the real-time status of various alarms and events. Therefore, establishing a well-defined and consistent color database is essential to ensure clarity and effectiveness.
In UNICOS, colors play a critical role as the framework is designed to represent the real-time status of various alarms and events. Therefore, establishing a well-defined and consistent color database is essential to ensure clarity and effectiveness.
The panels within the UNICOS interface are designed with a fixed layout that does not adapt to different screen sizes or resolutions. This can lead to usability challenges, especially for users accessing the system on various devices, such as laptops, or desktop.
Inconsistent design elements (e.g., buttons, icons, color schemes) across different modules create confusion and reduce user confidence.
→ How can we design a system that not only solve the current issues but is also helpful in future?
→ How can we redesign this framework without changing existing layout?