Skip to content

[FEAT]: Define and Collect Core KPIs #10

@mulirow

Description

@mulirow

User Story

As a Data Analyst
I want to ensure the application reliably captures all state changes of bookings, resources, and user interactions
So that I have a clean, structured dataset to calculate core KPIs (like occupancy rates, peak hours, and cancellation frequencies).

Acceptance Criteria

  • The team must identify and document the exact data points required to calculate "Occupancy Rate" and "Peak Usage Hours".
  • The system's database schema and logic must guarantee that timestamps for creation, updates, and status changes of bookings are accurately recorded.
  • The team must be able to extract or connect to a read-only replica of this data without impacting the performance of the live application.

Context / References

Before building dashboards, the data team must guarantee the integrity and availability of the raw data generated by the software engineering team.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    Status

    Backlog

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions