Lets collect here two lists:

== tools (be it needed or already written) useful for a shift summary.

* occurrence and frequency of fad-losses (maybe even statistics on boards/fads?)
* occurrence of 27s problem
* lidar visible in data? 
* some tools recently done by Thomas: 
 * http://www.fact-project.org/run_db/test6.php
 * http://www.fact-project.org/run_db/test.php
 * http://www.fact-project.org/run_db/test2.php
 * http://www.fact-project.org/run_db/test4.php
 * http://www.fact-project.org/run_db/test5.php
* https://www.fact-project.org/dch/quality.php
* https://www.fact-project.org/dch/ratescans.php
* tool that evaluates how often which limits are reached (maybe not needed for shift summary, but I think useful for this whole automation business)
* tool for data check (could be also used for defining limits) https://fact-project.org/datacheck/dch.php
* https://www.fact-project.org/sandbox/AllSkyCloudDetection/
* quality_drive.C (website still missing, but Thomas provided macro)
* quality_environment.C (or similar name, plotting humidity et al, Dominik has this maybe ready?)
* eventviewer with access to files on daq: https://www.fact-project.org/viewer/
* ...

== things you want to see in a shift summary.

* weather during the night? which runs affected by clouds? calima? haze? humidity?
* any rate problems during the night? too high rate? too low rate? / is rate as expected? (correlation with zd and nsb needed)
* any lidar problem? 
* were there runs during which the lid was closed but was not supposed to
* any problems during QLA processing?
* occurrence of 27s problem?
* possible car flashes?
* not about content directly but about concept of display: I want to have an overview on one glance showing for each system/item fine/not-fine or green/red and then clicking on it gives me more details (maybe even displaying only things that went wrong is enough)
* were data taken as planned? if not what were the reasons?
* observation mode? (wobble/orbit)
* any transfer problems? 
* system performance - any problems on the machines during the night? 
* some quality parameters from QLA? (rate after cleaning, ...)
* ... 

== other stuff important / needed / useful to go for robotic operation

I know, it is not exactly the right place, but as these points just came to my mind and we discussed few others yesterday, I put it here - we can move it somewhere else later

* orbit mode (helpful for automatic scheduling to improve homogeneity in data)
* automatic scheduling of ratescan (avoid copy&paste errors of shifters)
* redundancy in shifter-calling program