InnerWeb
Skip to main content

Recommendations: location address and room codes

The contractor at the furnace must reach the right place the first time, and the person accepting the permit must know which place they are reading about. A location address is built from the levels of the plant structure and a room code. Below are seven recommendations for the head of maintenance, ordered from the most important.

4
tiers of the structure: view, building, line, location
Source: implementation card
1
collective location Other in each line
Source: implementation card

Who these recommendations are for

We address these recommendations to the head of maintenance, the system administrator and the coordinator for external companies at a plant with a large site. We assume the plant has several halls, furnaces and supporting installations, and that the locations come from several older registers with different naming conventions.

The structure model has four tiers: view (department), building, line and location. A view is not a building: it is the area in which the buildings lie. A location address is therefore read from general to specific, and the room code is its last, most detailed element.

Recommendations 1-3: tiers, level prefix and the default ground floor

Recommendation 1: keep the order view, building, line, location and do not mix the tiers in names. The name of a location should not repeat the name of the building, because the address already contains it.

Recommendation 2: in a multi-level building use a prefix that is the level number. The system assigns a code with such a prefix to the matching floor without manual work. Recommendation 3: treat a code without a prefix as the ground floor and flag it for review, because a line without an assigned floor goes to Level 0 m.

  • Tiers in a fixed order: view, building, line, location.
  • Level prefix in the room code for multi-level buildings.
  • Codes without a prefix: ground floor, flagged for review.

Example: locations by the way the code is written

Example: locations by the way the code is writtenChart: 120 locations with a level prefix, 60 without a prefix and 20 ambiguous.0255075100125locationsWith level prefix: 120 locations120With level prefixWithout prefix: 60 locations60Without prefixAmbiguous: 20 locations20Ambiguous
Source: Example calculation based on the assumptions of this page: 200 locations assumed in a multi-level building.

Recommendations 4-5: codes that are readable and unambiguous

Recommendation 4: a room code must be readable over the phone, on the radio or from a sheet of paper, so avoid characters that are easy to confuse (zero and the letter O, one and the letter I). Adopt a fixed code length and a single separator.

Recommendation 5: keep exactly one collective location named Other in each line, placed in the middle of the line. This makes it possible to point to a place that is not on the list without breaking the structure. A permit with the location Other should, however, be treated as a signal of data quality: its share should be reduced from quarter to quarter.

Recommendations 6-7: compare by content and verify on the map

Recommendation 6: after each regeneration of the structure, compare the new state with the old one by content: name, area, level, geometry. Identifiers change during regeneration, so comparing by them shows differences that do not exist and hides those that do.

Recommendation 7: verify the address on the map, not only in the table. Pick several locations from different levels and check that the pin lies in the right room. For every rule that is meant to protect the address, prepare a red test, that is an example that must be stopped.

How to implement the recommendations in three steps

Step one: audit the existing codes and divide them into those with a prefix, those without a prefix and the ambiguous ones. Step two: agree one convention and a conversion table from the old codes to the new ones. Step three: migration in the test environment, a review on the map, and only then the move to production.

For contractors prepare a short instruction: how to read the address, what Other means and what to do when the place is not on the list. A simple instruction reduces the number of permits with a general location, which make it harder for the accepting person to assess the risk.

Example calculation

Example of a review of codes

Assumptions
ParameterValue
Locations in the building200 pcs
With level prefix120 pcs
Without prefix60 pcs
Ambiguous20 pcs

Result: 80 codes need review (40% of the pool).

Note: Example calculation; the figures are assumptions, not data from a specific plant.

Checklist

Video

Frequently asked questions

Must a location address contain the name of the building?

The address in the system contains the building tier from the map, so the location name does not have to repeat it. This keeps the codes shorter and easier to read.

What does the location Other mean?

It is the collective location of a line, placed in its middle, for places outside the list. It should be an exception, and its share is worth monitoring as an indicator of data quality.

Why not compare the structure by identifiers?

Identifiers change after regeneration. A correct comparison is based on name, area, level and geometry.

Let's put the addresses in your plant in order

We will review the room codes and propose an address convention and a migration plan in the test environment.

Let's talk