LKSKS Project Approval: Checking Drawings and Specifications

Why the client should get involved in the LKSKS project

If you accept an LKSKS project “as is”, problems often appear during installation. Suddenly trays don’t fit under ducting, penetrations through walls ignore fire-safety requirements, or there isn’t enough space in the rack for patch panels. Usually that ends with rework, extra costs and schedule slips.

For the budget the risk is obvious: extra materials, additional work, lift rental and downtime for other contractors. For operations the consequences are even worse: overloaded routes are harder to service, ad-hoc labeling turns fault-finding into a scavenger hunt, and vague testing requirements lead to disputes at handover.

At approval it’s important to lock in decisions that are hard to change later without losses. For example, if the office plans to grow, it’s better to identify where spare ports, tray space and rack room will be, rather than adding them later on-the-fly.

The client’s position is especially needed where choices affect convenience and cost: how many connection points are really necessary and where; what lifetime and growth reserve are expected; which rooms are suitable for cabinets and what level of access is allowed; what acceptance and test reporting are mandatory; who is responsible for labeling and final documentation.

Details of routing and typical solutions can usually be left to the contractor, but with clear rules: what we check, how it’s proven and what counts as “delivered.”

Which documents should be included in the project package

To avoid turning approval into an installation dispute, first check completeness. If a document is missing you often have no basis to answer basic questions: where cables go, what to buy, how to hand over lines.

A minimum package usually includes:

• floor plans with routes, outlets, risers and clear nodes (wall/floor penetrations, entries into rooms)
• diagrams: overall principle, rack/cabinet diagrams, cross-connects and connections (so you can see where everything terminates)
• a bill of materials and equipment with quantities and units
• a cable register and, if kept, a route journal: lengths, paths, from-to, category/type, spare
• a testing and acceptance section: which tests, which standard, what reports and what labeling is required on delivery

Check consistency. Symbols on plans must match those in diagrams and the specification. If a zone shows 48 ports on the plan but the specification lists only 24 modules, that is not a small oversight but a future downtime risk.

A practical tip: ask for templates of final documents up front (measurement report format, line register, naming rules). That way you lock in what you consider a completed result.

Step-by-step: how to read route and outlet drawings

Start with the legend and notes. Designers use different symbols: where trays are shown, where conduits are, how outlets are marked (RJ-45, Wi-Fi, telephony), what colors or line types mean. Without the legend it’s easy to mistake a power route for a low-voltage one.

Then check scale, anchors and heights. The plan should indicate routing heights (under ceiling, in floor, on wall), points of rise/drop and alignment to axes or walls. If heights are missing, ask — this is a common installation surprise.

Match outlets to the room schedule. Walk through rooms mentally and ask a simple question: do all workstations, racks, printers, access points and cameras get the number of ports they actually need where they need them? For example, a meeting room usually needs 2–4 ports at the table, not by the door.

Then verify numbering of lines and ports against the register and specification: an outlet on the plan must unambiguously match a port in the rack and a specific cable.

To speed up approval, mark questions directly on a copy of the plan:

• unclear symbol or missing legend
• no heights or penetration details
• outlet placed in a “non-functional” location
• line numbers don’t match the register
• duplicates or missing ports

Routes and penetration nodes: what to check on the plan

On route plans you need to see not just “lines down the corridor” but a clear path from each cabinet to each work area. If the cable route can’t be described in one sentence (where it goes, what it passes through, where it drops), installers will improvise on site, which is a risk to schedule and cost.

Check that routes aren’t placed next to interference sources. SCS cables should not run in close parallel to power feeders, VFDs, elevator equipment or switchboards. The drawing should show routing corridors and separation, especially in common shafts and above ceilings.

Penetrations through walls and floors

Penetration nodes should be marked with exact locations and anchors: where the route passes, at what height and by what method. If the note says “penetration to be decided on site,” ask for clarification. Each penetration needs a fire-safety solution and a plan for restoring fire-resistance, otherwise the acceptance authority may demand rework.

Above ceilings check maintainability: where can you reach the tray, are there access panels, do ducts or luminaires obstruct the route. A good sign is routing through serviceable zones rather than “dead” areas.

Quick checklist for plans:

• routes to each zone are shown without breaks or “teleports” across sheets
• dangerous crossings with power or mechanical systems are marked and separated
• penetrations have anchors, node types and fire-safety requirements
• above ceilings there is access (panels, service corridors)
• approvals with architecture, fire service and building operations are noted

Example: if a route from the server room goes through a stairwell, that raises immediate fire-safety and access questions. Better to see that on the plan and change the route than argue after installation.

Tray capacity and arranging cables without overload

Overloaded trays and ducts are a common cause of problems during installation: cables won’t fit, bend radii are violated, and later this leads to breaks and unstable performance. At approval ask for a fill calculation for each main tray section. Drawings should show how many cables go in each tray and what tray type is selected.

If a plan shows trays without dimensions or type (width, side height, perforation, cover), pause and request clarification. Without dimensions you cannot check capacity or load on fixings.

Check five things:

• a percent fill is specified and spare capacity for growth is included
• branches and fixings are drawn, not just a “route line”
• no sharp bends or radius violations for the chosen cable
• weight limits for bundles are considered, especially on long spans and vertical runs
• separate routes are planned where needed (for separation from power or different subsystems)

Simple example: a corridor has one tray “to the server room” but doesn’t show a branch to the meeting room. On site that branch becomes improvised ties and sharp bends. A good project shows the branch, fixings and spare space so cables can be laid without pressure.

Cabinets and rooms: more than just cables

Cabinets and rooms are often overlooked, and this is where the most expensive rework appears. The cable might be laid perfectly, but if the rack is in a bad place, lacks power or overheats, the network won’t run reliably.

First check where cabinets or racks are located and how they are accessed. Doors must open fully, there must be room for servicing, and cabinets should not be next to pipes, wet zones, or high-traffic aisles.

Check basic room conditions:

• dedicated power lines and a clear shutdown scheme (breaker, labeling, UPS if required)
• ventilation or air conditioning and specified allowable temperature
• grounding and a grounding connection point
• lighting for maintenance and space for a ladder
• placement of UPS and PDUs and where their cables exit

Then the internal rack logic. Drawings should show whether cables are brought in from the top or bottom, where entry plates or brush panels are, how patch panels and cross-connects are arranged. If the spec lists many patch panels but the rack diagrams don’t include organizers and bend-radius space, expect disorder at installation.

A special note on security and control. For financial and medical areas agree locks, access restrictions and port accounting in advance (who plugged what and when). Example: in a clinic reception the rack should be in a locked room while only outlets remain in the public area — otherwise someone can accidentally unplug a workstation.

If the project is done by a systems integrator, ask them to show the intended port labeling in the rack and on patch panels. This speeds approval and acceptance.

Spare capacity and growth: what to include in advance

LKSKS projects often fail not at installation but a year later, when new staff, cameras or Wi‑Fi points appear. So it’s important to see not only what’s needed now but how the network will cope with growth.

Check spare ports and spare cabling. Practically, it’s convenient if racks have free ports in patch panels and switches, and trunk routes have room to add cables without removing existing bundles.

Look at key nodes: server room, floor cabinets, vertical and inter-building entries. Those locations benefit from spare fibers (if fiber is used) and spare ports so you can add zones without reworking trunks.

A good project shows an expansion scenario: where new desks, cameras, printers and access points would be added. If plans don’t indicate potential growth points, ask the designer how to add lines without re-laying the route.

Mini-check for spare capacity:

• free ports in racks and spare lines in busy areas
• spare fibers and space in trunk routes
• a clear method for adding servers, Wi‑Fi and work areas without rework

Specification: how to catch material errors quickly

The specification often looks like “just a table,” but it hides the most expensive mistakes. During approval go through it as carefully as the plans.

First, confirm cable types and categories match the needs and environment. Workstation runs usually use copper of the required category, while inter-floor trunks may require fiber. Also clarify the installation environment: open routes, raised floor, shafts, outdoor or wet areas. A cable of the same category can be unsuitable due to sheath type.

Then check fire and environmental requirements. Projects often omit the required flame-retardant class, smoke generation and toxicity, and for trays and ducts the material/finish requirements. These issues surface during operations approval or handover.

Quick checks:

• cable category and construction match the purpose and environment
• fire characteristics for cables and trays are specified
• sockets, modules, patch panels and connectors are compatible (category, shield type, form factor)
• quantities are realistic: length with spare plus fixings, ties, labels and consumables
• substitutions are allowed only by agreement and equivalency is defined

Example: the spec lists Cat 6A cable but Cat 6 patch panels. That may look similar, but you lose declared parameters and may fail testing. Catch those mismatches while changes are still quick.

Labeling and final documentation: so you’re not left guessing

Labeling seems small until a move, fault or replacement happens. At approval define a single naming logic so installers don’t invent it and operations can quickly find the port.

A naming scheme ties location and purpose: cabinet (or rack), patch panel, port, outlet and the line. The key rule: label the cable identically at both ends: at the outlet and in the cross-connect (and ideally on the patch panel). If only outlets are labeled, the rack rapidly becomes a forest of identical cords.

Ask that as-built documentation include not only plans but practical tables you will use:

• line register: from-to, length, category, cable type
• port register: patch-panel/port ↔ outlet/port
• rack layout and U positions
• labeling table and printing/sticker rules
• test reports for each line tied to an identifier

Also fix who will update drawings to show reality: the designer from contractor data or the contractor with subsequent verification. Agree the format of reports so that the documents are usable in operations, not just stored "for the record."

Testing and line acceptance: requirements at the start

To avoid acceptance disputes, define testing requirements during project approval. Then the contractor knows how to prove quality and the client receives comparable reports.

Tests cover line functionality, not just the cable:

• Copper: Permanent Link or Channel measurements (as stated in the project), checking length, attenuation, NEXT and other parameters.
• Fiber: attenuation testing (OLTS) and, if needed, OTDR for locating faults.
• Additionally: polarity, correct pinout, shield continuity and grounding where applicable.

In reports request evidence per line: line ID, date, tester model and serial number, chosen standard and Pass/Fail result, plus a summary table for all ports.

Acceptance criteria should describe in advance:

• what counts as Pass (which standard and category)
• allowed deviations (usually none unless agreed)
• actions on Fail: re-termination, replacement of sections, route correction and mandatory retest

To validate reports, perform random re-tests on site with the contractor and compare results. If lines fail, list them with numbers and do not accept until re-testing passes.

Example: approving a project for a two-storey office with a server room

Imagine a new two-storey office with 80 workstations, meeting rooms and a separate server room. The purpose of approval is simple: make sure all outlets are in place, routes will fit, and growth reserve is included.

For work areas start with floor plans. Verify that outlets are placed relative to actual furniture and walls: each desk has the needed ports, printers and Wi‑Fi points have dedicated lines, and meeting rooms have locations for panels/TVs and table connections. A common small mistake: outlets are shown on the plan but modules or sockets are missing in the specification.

In the server room check not only racks but route entries. Verify cable entries are shown, there is service space in front of racks, and climate and power requirements are at least indicated as input data.

One way to close most issues in a single meeting is to walk through these items:

• per floor: how many outlets, their locations and types (workstation, Wi‑Fi, cameras, printers)
• corridor trays: fill calculations, percent spare and planned expansion locations
• wall/floor penetrations: who will seal, whether a fire-rated solution is needed and how access is provided
• server room: rack locations, trunk entries, patch panel positions and electrical inputs
• acceptance: what test reports you will receive and how labeling will look

After this review usually only minor edits to routes and materials remain.

Common LKSKS project mistakes and how to spot them

The most expensive problems often don’t look like a clear “error” on the drawing. They show up during installation: not enough cable, tray doesn’t fit, a penetration isn’t approved, and deadlines become critical. At approval it helps to look for typical mismatches.

First group — plans and specification living separately. A plan may show 48 lines while the register has 44, or a different cable type is listed (different sheath or fire rating). Check a simple linkage: number of points per floor, number of rack ports and total cable meters should add up logically.

Second group — under-drawn routes. Common signs: no penetration nodes, no heights, no tray sizes. Installers will “decide on site,” leading to extra ducts, additional drilling and questions from operations.

Third — overloaded trays and no spare. If a tray is specified to the brim, any additional line becomes a problem. Request a fill calculation and a clear spare margin.

Short checklist for weak spots:

• reconcile counts: outlets, ports, lines, cable drums
• each route should have heights, tray sizes and penetration details
• check spare capacity in trays and port counts
• labeling must connect outlet, line, patch panel and switch port
• testing must have clear acceptance criteria: what is measured, to which standard and what report you get

Example: plan includes additional workstations but the rack has no free ports and no space for a second patch panel. You’ll spot this immediately if port capacity is listed per rack rather than as a global number.

Short checklist before signing the project

Before signing, go through the project once with the aim of catching things that will cost time and money later. At approval changes are still quick.

Check per floor and in the server room that solutions are actually installable and serviceable. If on the plan something looks fine but you cannot access a penetration node because of a ceiling or facade, rework will start on site.

Quick checks across drawings and specifications:

• routes and penetrations: sizes, heights, clear penetration nodes and assurance that access remains after finishes
• trays and cables: not filled to capacity, bend radii preserved, fixings indicated, and power lines separated from low-voltage
• cabinets and rooms: room in front and to the sides, power, ventilation, grounding and a clear path for bringing in equipment
• spare capacity: free ports, spare fibers/pairs, room in trays and a clear expansion plan
• acceptance: tests, report formats, pass/fail criteria and the composition of as-built documentation

If any item makes you ask “how will this be done on site?” return the project for revision before signing.

Next steps after approval: preparing for installation and acceptance

After signing the project, turn it quickly into clear working rules on site. Start by checking the project against the building’s real conditions: which shafts and trays are already occupied, which zones are closed to works, and what security and fire-service requirements exist. This reduces the risk of stoppages from "sudden" constraints.

Fix the change order process immediately. On site you will almost always need to replace a specification item or adjust a route. Agree who can initiate a change, who approves it and which conditions are mandatory (category, fire class, compatibility, delivery times).

It’s useful to prepare a short working protocol before starting:

• who signs changes in the project and in what timeframes
• how concealed works are certified and how penetration nodes are photo-documented
• what measurement report forms are required and when to submit them
• where the as-built documentation is stored
• who accepts work in stages (by floor, zone, cabinet)

Assign one responsible client representative for acceptance and archiving of final materials: as-built diagrams, “as installed” specifications, line test reports, labeling tables, component datasheets. That way in a year you won’t need to reconstruct from memory where a route runs and which port an outlet belongs to.

If the project involves IT modernization, align LKSKS with the server room, racks, power and active equipment in advance. It can be useful to involve a systems integrator for independent project review and acceptance. For example, GSE.kz as a manufacturer and systems integrator can help align LKSKS with server infrastructure (servers, workstations, data-center solutions) and with ongoing operational support.