Services · the six patch room rounds

Six rounds that turn a diagram into a dressed, proven and readable rack

Eds Technology Inc. runs a fixed calendar of six services inside one patch room at 1704 167 St Sw, EDMONTON - T6W 3C5, Canada (CA). Each round has a defined start, a defined finish and a written record that leaves with the client. The order matters as much as the work, because a bay built in the wrong sequence produces a rack that photographs well and behaves badly. Below is the full scope of each round and how they fit together across a working week.

Rack Bay Desk

Rack Bay Desk is the planning round, and it is the round that saves the most money. Before a single unit is mounted we map the bay from the ground up: each rack unit is named, each ascent of the frame is numbered, reserve space is marked for the growth the client already expects, and power landing points are recorded against the unit that will draw from them. The desk round also settles vocabulary. If one team calls a device a node and another team calls it a controller, that disagreement is resolved here, on paper, while it still costs nothing to resolve.

The output is a bay plan that a technician can follow without a second conversation. It shows the frame elevation, the numbering scheme, the reserved units, the cable entry side and the intended path of the first loom. The plan is deliberately plain. It is not a marketing diagram and it is not a rendering; it is a working sheet that gets pinned to the inside of the door and marked in pencil as the week proceeds. Where a client already has a bay in service, the desk round begins with a survey of what is mounted rather than an assumption about what should be. Nothing is moved during the desk round. Discovery and change are kept apart on purpose, because the quickest way to lose a working system is to design and demolish it in the same hour.

Loom Dressing Rounds

Loom dressing is the physical heart of the patch room. A loom is a group of cables travelling together, and a dressed loom is one that has been combed, laced, looped and cinched so it keeps its shape under its own weight. During a dressing round we comb each bundle to a fixed pattern, lace it to the vertical manager at even intervals, leave a service loop at every point where a unit may one day be pulled, and cinch the bundle so that slack lives where it is useful instead of where it is merely convenient. The colours of the loom are not decorative. Each colour group corresponds to a function on the patch schedule, and the dressing round makes that correspondence visible from across the room.

A dressing round is also an inspection round. Cables are checked for damage at the jacket, connectors are checked for seating, and any run that arrives already suspect is quarantined before it enters the bundle. We tag the origin of every loom at the point where it meets the manager, so that a fault trace later begins from a known place rather than from the middle of a bundle in the dark. Dressing rounds take longer than most clients expect, and that is the point. A loom that is laced in a hurry has to be re-laced in an emergency, and the emergency always arrives at the worst possible moment. The round ends only when the loom holds its shape with no hands on it.

Patch Side Weeks

Patch side weeks concentrate on the patch field itself, the face of the system where change actually lands. We rebuild patch schedules that have drifted, retire runs that no longer carry a purpose, colour the field by function so that a technician can read it at a glance, and write a short change note for every jumper we move. The note records what was moved, where it went, why and by whom. That note is then walked against the field before the week closes, because a schedule that has drifted from the field is worse than no schedule at all. A client with a tidy bay and an untidy patch field is a client who will eventually spend a night tracing a single cable by touch.

Patch side work is also where we separate the network from the noise. Many patch fields accumulate runs that were added for a project, forgotten at the end of it and left in place because removing them felt risky at the time. During a patch side week we identify those runs, agree with the client which ones can be retired and confirm that the retired run carries nothing quietly important before it is pulled. Nothing is removed on assumption. The patch side week closes with a reconciled schedule, a coloured field and a written change note, so that the next person who opens the cabinet sees the same order that the schedule describes.

Circuit Test Days

Circuit test days are the sitting where the system answers for itself. Every run that was dressed, patched or repaired during the week is proved end to end, and every reading is written down on the day it was taken. We test against a written schedule rather than a mental one, because the run that gets skipped is always the run that fails. Findings are logged as findings: dated, described in plain language, assigned and retested after repair. A finding is never quietly crossed out, and a pass is never assumed on the strength of an adjacent pass. The test sheet that leaves the room is a working record, not a certificate, and it says so at the top.

Test days are open to the client. Anyone with an interest in the bay can stand beside the rack while the runs are proved, ask what a reading means and watch a failure be found and fixed rather than be told about it later. That openness is deliberate. It builds the kind of confidence that comes from having seen the system tested rather than from having read a summary of the testing. The day closes when the sheet is signed, the outstanding findings are listed with owners and the room is left in a condition that the next round can trust.

Label Run Sessions

A label run session is a scheduled sitting in which one family of labels is printed, sorted and applied across the whole bay, then walked against the schedule to confirm that every name on the face matches the name in the record. Labels are printed in one consistent family rather than assembled from three suppliers and two conventions. Port names, patch references and floor destinations all follow the same rules, so a label never lies about what it points to. A mislabelled port is a trap with a polite face, and it costs more to find than to prevent.

The label run is also the round in which the system becomes teachable. A person who has never worked on the bay can be handed the schedule and asked to find a specific run, and the label run is how we confirm that the answer is possible. If the walk takes longer than it should, the label family is wrong and the session is not finished. Label runs are conducted with the client present where practical, so that naming conventions reflect the language the operators actually use. A system that is labelled in the language of its users is a system that survives staff turnover.

Tie Wrap Evenings

Tie wrap evenings close the patch room week in a quiet and methodical way. Loose cable is dressed, wraps are tied at a consistent tension, spare slack is trimmed away, and the bay is returned to the state that the next round expects to find. Tension matters more than most people imagine. A wrap tied too tight crushes the jacket and shortens the life of the cable. A wrap tied too loose lets the bundle drift until it chafes against the frame. The evening round exists to make tension consistent across the whole loom rather than dependent on the mood of whoever tied it last.

The evening is also when the room itself is reset. Tools return to the wall, offcuts leave the bay, the floor is cleared and the closing note is written for the next person through the door. That closing note does not summarise the week in a way that flatters it. It names what was finished, what remains open and which part of the bay should be approached with care. A tidy room is not a decoration; it is the difference between a technician who starts a monday calmly and one who spends the first hour looking for the tool they need.

Circuit test windows are announced when a patch room week opens, and every client on the bay is welcome to attend the proving of their own runs.

Process overview

How the six rounds fit together

One week · six rounds · one written trail

The patch room week opens with the Rack Bay Desk, because a bay without a map is a bay without a spine. Once the plan is agreed, Loom Dressing Rounds begin while the frame is still open and the loom can be laced without disturbing mounted equipment. Mid week belongs to Patch Side Weeks, when the field is quiet enough to move jumpers without guesswork and when the schedule can be reconciled against what is actually present. Circuit Test Days follow, closing the working stretch with a written record of every run proved or flagged. Label Run Sessions then make the finished system legible, and Tie Wrap Evenings reset the room for whoever comes next.

Clients rarely need every round in a single week, and we do not pretend otherwise. Some engagements begin with a Rack Bay Desk and nothing else, because the client needs a map before committing to a build. Others arrive for Circuit Test Days alone, because a system built elsewhere needs an honest reading before it is relied upon. The rounds are modular, but they are never interchangeable. Running a patch side week before the desk round is like repainting a house before fixing the roof.

What every round leaves behind

A written record. Plans, dressing notes, change notes, test sheets, label lists and closing comments are all retained and handed over.

A named owner. Each open finding is assigned to a person, not to a department, so that it has somewhere to go.

A room condition. The bay is left in the state the next round expects, so no round begins by repairing the last one.

A standing invitation. Clients can watch any round in progress and ask the questions that will matter later.

Choosing a starting point

Which round to book first

A short guide for a first conversation

Suggested first round by situation
Your situation	Suggested first round	Why
A new rack is going in and nothing is mounted yet	Rack Bay Desk	The plan must exist before the frame is touched.
A bay is built but the cabling is unmanaged	Loom Dressing Rounds	The loom, not the hardware, is the present risk.
The patch field no longer matches the schedule	Patch Side Weeks	The field must be reconciled before anything is proved.
A system built elsewhere needs an honest reading	Circuit Test Days	Evidence comes before trust.
Operators cannot find runs without asking	Label Run Sessions	Naming is a maintenance instrument, not decoration.
The room is working but the bay is tired	Tie Wrap Evenings	A reset round restores condition without redesign.

On discipline

Why the room refuses short cuts

A patch room is a place where the cost of a shortcut is deferred rather than removed. A cable run under a floor tile will hold for months and then fail at the moment a business cannot afford it. A label applied from memory will be right until the person who wrote it leaves. A loom dressed without a comb pattern will look acceptable in a photograph and behave like a bird nest in a fault. The six rounds exist precisely to refuse those shortcuts in a structured way, so that the refusal is a schedule rather than a personality.

We also believe that clients deserve to see the refusal happening. That is why the test sheet is dated, the change note is signed and the closing comment names what remains open. A system that is honest about its remaining work is far easier to maintain than one that presents itself as finished.

On scope

What sits outside the patch room

We design, build, dress, test and label integrated systems. We do not sell hardware, we do not operate as a repair shop and we do not take on the role of a general contractor for building work. Where an engagement needs a licensed trade, a hardware supplier or a cabling contractor beyond our own rounds, we say so early and help the client place that work clearly, but we do not pretend to absorb it.

That boundary is not a limitation of ambition. It is how the patch room keeps its promises. A practice that agrees to everything ends up dressing looms on a schedule that does not exist.

Book a round and stand in the room

Tell us what the system needs to do and what the bay currently looks like. We will suggest a starting round, send a bay plan outline and arrange a visit to 1704 167 St Sw, EDMONTON - T6W 3C5, Canada (CA).

Open the contact page →