# Design and Applications of GLANCE: GLanceable Alarm Notification for a User Centered Experience
## 4 Results of the 2 nd Macro-Phase: Application and Refinement of GLANCE
### Application to a Personal Customizable Notifier
Again, as already observed about the icon style, the lens is just a matter of aesthetics and may be replaced also by different (and possibly more abstract) visual solutions coherent with the model (i.e., in a fixed central position of the category bar over a scrollable category list). The final design of the GLANCE+ model is illustrated by the sample display in Figure 12a. Considering the expectations of users of a personal notifier, the display has been enriched by a _scrollbar_ on the right side to directly interact with the notification list and an interactive _control palette_ on the left side with icons for (a) pausing/restarting the automatic scrolling, (b) going directly to a notification source, and (c) deleting a notification from the list. The list is also visualizable in an _on-demand panel_, to provide quick direct access to individual selected items (see Figure 12b), thus offering an additional glanceable overviewing capability. A GLANCE+ based Java application has also been implemented, equipped with a back-office component allowing users to customize the notification aggregator. Figure 12: The final design of the GLANCE+ model, with (**a**) the notification component, and (**b**) the notification list visualized in the on-demand panel. Application of GLANCE and GLANCE+ to a Service-Oriented Fault Monitor for Digital Terrestrial Television Broadcasting Networks  
The second application project was carried out as a customary UCD-based project within the framework of co-operation between Univaq and Broadcast Solutions S.R.L., an Italian company offering system integration capabilities for broadcasting and media industries. We observe that an exhaustive description of this project goes well beyond the scope of this paper since in this case the primary company objective was to conceive a novel perspective for the fault management approach. We report on this project here, sketching its main features and results, because it was an opportunity for testing the adaptation of GLANCE and GLANCE+ features to a real context. In particular, the company's goal was to study a novel approach for fault management in digital terrestrial television broadcasting networks, shifting from a traditional _device-based_ perspective, with scarce support for detecting how the final service is affected by the alarmed device, to a _service-based_ perspective centered around faults as perceived by the final user (e.g., absence of the audio component in a given channel) without losing the possibility of clearly identifying the corrupted device(s). This issue has implications on both the \"internal engine\" managing the service/device correlation and the \"dispatching display\" alerting operators about alarms and offering efficient navigation in alarm data. As to the \"dispatching display\", after a series of brainstorming meetings with domain experts and final users, it was agreed to study a GLANCE-based fault notification component offering the operator a glanceable overview of information about incoming alarms, grounded on the final users' service-based perspective (e.g., \"absence of the video component in RaiUno\"), while guaranteeing a smooth and efficient switch to the device-based perspective (e.g., \"lack of video signal on SDI input interface\"). Though similar to the original project with Technolabs, the new application has to take into account multiple requirements:  
* The fault management package has to provide a service-centric overview to offer the operator a precise view of what the consumer is receiving;
* The fault management package has to provide a service/device correlation to make the operator able to intervene for fixing the problem;
* The alarm notification has to grasp the correct quantity of operator's attention, depending on alarm severity, and alarm data useful for fast intervention planning have to be easily identifiable.