Boards
Board metrics built from job history printouts: how much of the time positions are at work, away from home, at home or unavailable, plus position counts, missed calls and how fast vacancies are filled. Upload new printouts as they come in. Each batch should overlap the last one by a day.
Loading…
Check against snapshots
Compares the board the app rebuilt from the job histories with each snapshot taken inside the uploaded dates: the position count, and for every position where it is, whether it's on duty, the name shown and its place on the board.
This section is purely for testing purposes to ensure the app is keeping track of all positions. The earliest snapshot will often have mismatches because it doesn't have the preceding data.
Compare boards
Pools and extra boards from any terminal, side by side over the same dates (the dates every chosen board has data for, within From / To).
Attrition · seniority district
Retirements (RE AG), investigations, terminations (LF L5) and resignations due to pending discipline (RE AI, RE NH, RE AW, status NH, or any other RE within 90 days of an investigation pending) for everyone in the seniority district, grouped by the terminal where they last worked. Read from every uploaded job history at every terminal, including the holding boards (NZ335 OT30 holds inactive people from the whole district) and the systemwide holding boards ZZ65 and ZZ66 (only people moved there from one of the district's boards).
Loading…
Headcount · seniority district
How many people hold a position on each board, by terminal, month by month: the holders of pool turns and extra board positions, and the assigned employees of yard and local jobs (vacation relief and fills don't count; someone laid off or on vacation still does). Joined and left count people starting or stopping on a board, or for a terminal on any of its boards, so moves between a terminal's own boards don't count.
Loading…
Displayed metrics
Choose which tiles, charts, table rows and detail sections each preset shows, by board type. Everyone picks the preset they view with Display, next to the tabs; owners set up the presets and the default.
Loading…
Terminals and boards (owners)
Terminals
Boards (of every terminal)
Add a board
An extra board's away terminals are the away terminals of the pools it fills. Yard (e.g. YT31): home terminal only, positions FBY, SW1. Local (e.g. AT30): home terminal only, position CON. The first position is the one on every start. Uploads are matched to boards by the board ID in each printout's header.
Upload printouts
Drop job history and snapshot printouts here (the saved .html pages), or
What to upload
- Job histories: one per board per terminal (RT30: NZ335, NX001, NZ140 · RT35: NZ335, DM136 · XK30: NZ335, NX001, NZ140, DM136). All terminals of a board should cover the same dates. The next batch starts on the last batch's END date.
- Snapshots at the start: for the first batch (or after a gap), a pool snapshot of every terminal of each pool and an extra board snapshot, for the same time on the first day. They set where every position is.
- Attrition: the job histories of the holding boards (NZ335 OT30) and the systemwide holding boards ZZ65 and ZZ66 (no terminal; the END date can be left blank).
- Seniority rosters: for time in service in attrition, and in Headcount to explain who joined and left and to check the counts (print them regularly, e.g. on the 1st; conductor and brakeman rosters; a conductor's seniority date is their hire date).
- Snapshots near the end: optional, as a check. The day before the last day works best (the last day of a printout is often incomplete).
- The app reads each file's board, terminal and dates from its header. A newer printout replaces an older one's overlapping days. Printouts filtered to one crew are kept but not used.
What's uploaded
Loading…