The time it is at every desk

The time where the work is happening

A trading floor, a support rota and an operations bridge all share one problem: the person reading the screen is in one place and the work is in several. Asking them to do the arithmetic in their head is how a handover gets missed by an hour.

A clock tile answers it on the same panel as the figures, in the same rhythm and the same type. Each one names its place, shows the date on one line and the time on the next, and ticks on the second. They move together, because the panel keeps one beat for all of them rather than three clocks slowly drifting apart.

Each clock reads in its own locale, so New York shows a twelve hour clock with its marker and London and Tokyo show a twenty four hour one, from the locale alone rather than from another setting to remember.

Figures and clocks on one panel

The two figures beside the clocks are ordinary tiles over the same rows the table holds. Filter the table to one desk and both retotal, while the clocks carry on, because a clock is not a measurement of your data and does not pretend to be one.

That is the point of putting them together: the panel at the top of an operations screen carries both the state of the business and the state of the day, in one row, with nothing kept in step by hand.

How do I add a clock to a KPI panel?

Add a tile written { kind: 'clock', label, timeZone } to the panel’s tiles. timeZone is any IANA zone name, locale sets the language and the hour convention for that tile (or the panel’s own locale when the tile declares none), seconds: false drops the seconds and date: false drops the date line. A clock tile takes none of a measuring tile’s options, so it sits in the panel’s layout, answers its column count and fires its events without ever being mistaken for a figure.