Milestone 5

Maintaining Existing Infrastructure

Remember that all business decisions should be compounding over the semester, and thus that you should ensure that all existing dashboards for past milestones remain functional and accurate to the data at hand. This may be as simple as not touching what was done before, and everything still works. But if you need to make architectural changes (which should be documented with an ADR!), it may require revisiting older milestones to ensure they still operate correctly. In general, you should plan on each business decision mapping to a single dashboard. You could reuse components of existing dashboards, but it should be clear in Grafana what business decision each dashboard maps to. Keep in mind that for these assessments, what matters is the accuracy and degree to which the provided dashboard helps inform the business decision. The technical means by which you compiled and created that dashboard is not considered here, but should be included in your documentation.

The Business Question

For this fifth and final major milestone, we are looking at incorporating event data into the pipeline to evaluate passenger wait times.

Decision 1

Even with enough trains in service to meet demand, passenger experience can vary dramatically based on how long people wait at platforms. In Prague’s metro system, inconsistent train arrival times—especially during off-peak hours or in outer zones—can contribute to frustration, missed transfers, and a perception of unreliability. With real-time train movement data now flowing into the system, planners can finally analyze the actual wait times passengers experience from the moment they enter a station until the next train arrives. By examining how these wait times vary by factors such as line, zone, station, time of day, and day of the week, city officials aim to fine-tune the frequency and spacing of trains to minimize delays and improve rider satisfaction—without having to increase total train count.

Events and Lifetimes

While you should be always be taking snapshots, there are some things you should keep in mind about train arrival and departure events:

• Events are append only. A past event can never be changed or updated through another event.
• Events will exist in the topic for a duration of one week before they start disappearing. Make sure your snapshots are operational!

Assessment

You will be assessed on the following for each dashboard/business decision:

Category	4 – Exemplary	3 – Proficient	2 – Developing	1 – Insufficient
Relevance to Business Question	Dashboard clearly and directly answers the question; all content is purposeful.	Dashboard mostly answers the question; minor gaps or tangents present.	Partially answers the question; some visuals are only loosely related.	Does not address the business question meaningfully.
Analytical Insight and Context	Provides thoughtful analysis and useful context; insights go beyond surface-level.	Provides some interpretation or context; insight is basic but present.	Interpretation is minimal; context is unclear or overly simplistic.	No analysis or meaningful interpretation provided.
Accuracy and Reproducibility	Data is accurate and internally consistent; results could be closely replicated.	Minor inaccuracies or unclear methods; mostly consistent and plausible.	Not clearly reproducible; errors or inconsistencies raise concerns.	Major inaccuracies or contradictions; cannot be trusted.
Design and Aesthetics	Visually appealing and easy to interpret; layout, labels, and colors enhance clarity.	Clear design with minor layout or labeling issues.	Layout or chart choices hinder interpretation; lacks polish.	Poorly designed; unclear or disorganized layout and labels.
Communication and Presentation	Titles, captions, and text are clear, professional, and aid interpretation.	Generally well-communicated; minor missing or unclear text elements.	Explanations are vague, sparse, or unhelpful.	No explanations or guiding text; confusing to the intended audience.