Huntly Faults RegisterHelp and documentationBack to the map

Classifying issues

Every issue answers two separate questions: what is it, and what is wrong with it. A damaged kerb and a damaged sign are the same fault on different assets; a cracked footpath and an overgrown footpath are the same asset with different faults. Keeping the two apart is what lets you ask either question of the register.

Asset type

What the thing is. Twelve to start with:

Lamppost · Kerb · Drainage · Pipe · Concrete · Road Surface · Signage · Footpath · Cabling · Barrier · Vegetation · Fence

This is the axis the map is built around. Pins are coloured by asset type by default and the type is written under each pin, so a cluster reads as signage or kerb without clicking anything.

Issue category

What is wrong with it. Eighteen to start with, ordered by how often each came up on the first drive-over:

Damaged · Blocked · Overgrowth · Cracking · Missing · Base undermined · Exposed cables · Not attached · Unprotected · Misaligned · Pole missing · Damaged ducting · Obstruction · Subsidence · Dirty · Line marking obscured · Not working · Line marking faded

Adding a value the list does not have

Both lists are yours to extend. In the Asset type or Issue category picker, choose Add new…, type the name, and press Add — the new value is saved for everybody and selected on the issue you were editing.

Two things to know:

  • Type the name the way you would say it. The system derives the stored value from what you type, so Bus shelter and bus shelter become the same thing rather than two near-duplicates.
  • The values that came with the system cannot be deleted, because issues point at them. If a value is no longer wanted, it can be archived: it disappears from the picker but keeps reading correctly on the issues that already carry it.

When an axis is not set

Either axis can be blank, and blank shows as Not set. There is deliberately no Unclassified asset type — an asset nobody recorded is a gap in the record, and labelling it would make the register claim knowledge it does not have.

You can filter for Not set on either axis in the All issues list, which is the quickest way to find the issues still needing a decision.

Asset ID

Free text, for the Council's own reference for that piece of kerb, that lamppost or that sign. It is not validated, because the numbering is the Council's and it varies by asset class and by how old the record is — anything we enforced here would eventually reject a legitimate reference.

Leave it blank if the asset has no reference, or if you do not have it to hand.

Issue ID

Every issue has a six-character ID, for example K7M2QP. You will find it at the top of the Details panel, on each card in the All issues list, and in the map popup.

  • It is assigned automatically when the issue is created. There is nothing to fill in.
  • It never changes, and it is never reused — not even if the issue is archived. An ID you wrote on a works order last month still means the same issue.
  • It is not case sensitive. k7m2qp and K7M2QP are the same issue.
  • The letters O, I, L and U and the digits 0 and 1 are left out on purpose, so an ID read out on a roadside cannot be written down as a different one.

Search for an ID in the All issues box to jump straight to it, with or without a leading @.

Mentioning an issue in a conversation

Type @ followed by an issue ID in any conversation message. A picker appears as you type, listing matching issues by ID and name.

The posted message shows the ID as a link. Anyone reading the conversation can click it to select that issue and fly the map to it — which is the point: it lets one issue's conversation point at another without anybody having to describe how to find it.

A @ followed by six characters that do not match a real issue stays as ordinary text rather than becoming a link that goes nowhere.