Dashboard

What is this?

The dashboard is the landing page after sign-in and answers three questions: how is the lab doing overall ("Current status", the same for every lab employee)? What genuinely needs attention ("Attention required")? And what do I personally have to do ("Tasks", different per user)? Metrics, trends, and recurring failures live on the analytics page.

How to use it

• Customize dashboard: The button in the top right opens a list of available widgets to check or uncheck. The selection only applies to your own view.
• Current status: Comes first because it answers "how is the lab doing right now?" the same way for every lab employee.
  • Upcoming-schedule gadget: A compact tile at the top — the total count and the next upcoming event (milestone or maintenance) within the next 14 days. Clicking it jumps straight to the "Upcoming schedule" tab below.
  • Tests: Two tabs — "Today, ⟨date⟩" and "This week (week ⟨number⟩)". Both show the same table (test, project, station, status): currently running test cases ("running") plus the sequences scheduled for the selected period (start time; in the week view also the weekday).
  • Station status: A table with station, station type, effective status (colored dot), and the linked running test case. A station configured as “Available” is shown as “In use” while a test is running; Maintenance and Out of service continue to take precedence. The status legend sits below the table in its own bordered box.
  • Upcoming schedule: Milestones, maintenance, and calibrations due within the next 14 (calibration: 30) days — chronologically mixed, not yet overdue. Once a date is overdue, it moves to "Attention required".
• Attention required: Deliberately shows only what's genuinely overdue — upcoming (not yet overdue) dates live under "Current status" instead (see above). The whole section, and each category inside it, can be collapsed and expanded independently by clicking its heading. A category only appears if there's something in it:
  • Double-booked time slots: Conflicts grouped by test station (e.g. "Elektrischer Prüfstand EP1 – 9 overbooked time slots") instead of one row per overlap. Click "Resolve conflict" to jump to the station. Loads separately (see below) so the faster categories don't wait for it.
  • Overdue test cases (SLA): Due date passed, still open. Small icons in front of the project and sequence name make it clear at a glance which part of the entry is which; a person icon marks the assigned tester.
  • Overdue milestones: Same project icon.
  • Maintenance overdue: Test stations whose maintenance date has already passed.
  • Calibration overdue: Equipment whose calibration has already expired.
• Tasks: Its own, clearly separated section below — your personal work list, embedded directly in the dashboard without its own nav item. Defaults to "Assigned to me"; the "Open", "Failed", and "Recently completed" tabs plus the project/station filters widen the view to the whole organization. Switchable between list and board (kanban).

Metrics (pass rate, throughput, active testers, …) and recurring failures live on the analytics page.

Common issues

• "The double-booking notice appears shortly after the page loads." Intentional: the conflict check needs the full schedules of all affected projects and is therefore the most expensive part of the page — it streams in separately so the other categories don't have to wait for it.
• "A station under maintenance still shows a running test." The app keeps Maintenance or Out of service as the warning status and additionally shows the running test. Resolve this data conflict on the station.
• "An upcoming maintenance/calibration is missing from 'Attention required'." Intentional: as long as the date hasn't passed, it lives under "Current status" in the "Upcoming schedule" tab, not under "Attention required".
• "I see a different dashboard than a colleague." Intentional: the "Current status" widget selection is purely personal, there is no organization-wide default. Everyone adjusts their own view via "Customize dashboard". The task list, on the other hand, defaults to each user's own assigned tasks.
• "My selection is gone after a reload." That would be a bug — the selection is saved immediately when you click "Save" in the customize dialog. Without that click, the previously saved selection still applies.
• "Where are metrics like pass rate or turnaround?" They live on the analytics page, together with recurring failures — the dashboard focuses on what needs attention, the current status, and your personal tasks.