[fostware]

Do what everyone else does - synthesize the abstract relations into views and limit the self-serve BI dashboard to the views that do make sense. Users default to only seeing it from their perspective, so have alternate methods to let them see it how they think it works.

I'm aware of a product that uses time-based attendance for education, because not every day, every school, or every campus uses the same timetable quilt and often you have to be flexible (school sports carnivals, relief swaps, joint class activities, or 14-day rolling timetables for example). Doesn't mean there isn't a view that synthesizes the quilt into class-based attendance, or even just AM/PM for those users that think that way.