@beat was a full decimalization of time (1000 'beats' per day).

This is just giving new, universal names to hours. I can see this working a lot better than the alternative (use GMT/UTC everywhere) as you'd always have mental contention as to whether you meant a time in local or GMT. This way you don't need the additional label. And I could imagine getting used to the idea that my workday lasted from P-X & the other geographical zones had their common hour blocs.

Potential issues:

* 0/O ambiguity

* presumably the day flips over when the hour goes from X->A, which means sometimes it's tomorrow already.