GHT: Glass House Technologies
GHT service / Physical infrastructure

Structured cabling

Every outlet labeled, every link tested, every record accurate

Copper or fiber links, outlets, patch panels, pathways, and labels for computers, Wi-Fi, cameras, phones, and building systems.

What you should have at closeoutLabeled outlets and patch-panel ports, per-link test results, and as-built records that match the installed cabling.
References4 reviewed
Last updated2026-08-20
Overview

What Structured cabling includes

Structured cabling is the standards-based permanent infrastructure between equipment rooms and outlets. It includes the cable, connectors, patch panels, outlets, pathways, labels and records, not just the cable itself.

Media and category are selected from application speed, distance, environment, pathway, power delivery and useful-life requirements. A higher category is not automatically the better design when another medium or topology fits the requirement more directly.

Question to answer before designHow many devices need service, what must each link support, and what route and test standard apply?
Common situations

This service may fit when:

  • Unlabeled or abandoned cabling obscures active links
  • New devices exceed available ports or pathway capacity
  • Moves and remodels require repeatable outlet standards
  • Link errors point to possible physical-layer faults
System components

What the system includes

A complete scope covers each part below and the connections between them.

01

Work area

Outlet or service point where the device connects

02

Horizontal link

Permanent copper or fiber segment through the approved pathway

03

Telecom room

Labeled patching, rack space, bonding and power coordination

04

Network edge

Switch port, policy and powered-device budget serving the link

Project record

How site information becomes a tested project

A complete project record connects the conditions found on site, the design decisions made from them, and the tests and closeout documents delivered afterward.

Site information

What we confirm before design

  • Floor plan and device locations
  • Application speeds and power-over-Ethernet loads
  • Cable distances and environmental conditions
Design decisions

What those findings determine

  • Typical use: Start with application, distance and lifecycle, not category name alone.
  • Acceptance: Define the required test and result format in the scope.
  • Administration: Choose the record depth the support team will maintain.
Closeout records

What you should receive

  • Outlet and cable schedule
  • Labeled patch-panel and work-area terminations
  • Per-link test-result files

The exact inputs, decisions, and acceptance records depend on the site and signed scope.

Project stagesSurvey through closeoutView details
Project stages

How the work moves from survey to closeout

Each stage should produce the records and test results needed before the next stage begins.

  1. 01

    Requirements

    Map devices, applications, distances, density, power needs and owner standards.

    EvidenceOutlet schedule, media basis and assumptions register
  2. 02

    Route and label plan

    Coordinate rooms, pathways, identifiers, patching and future capacity before placement.

    EvidenceCable schedule, pathway notes and label convention
  3. 03

    Install and terminate

    Place cable within handling limits, terminate the permanent link and dress both ends for service.

    EvidenceProgress photos and endpoint-to-panel mapping
  4. 04

    Test and hand off

    Test to the agreed link requirement, resolve exceptions and assemble the final record.

    EvidencePer-link test files, exception log, photos and as-built schedule
Design choicesCompare the available approachesView details
Options

How to choose the right approach

The right choice depends on the site, application, operating risk, and acceptance requirements. More equipment does not automatically improve the system.

FactorTypical approachMore demanding conditionsWhat determines the choice
Typical useTypical approach: Cat6 for common horizontal linksMore demanding conditions: Cat6A or fiber for higher-bandwidth, distance or environment needsWhat determines the choice: Start with application, distance and lifecycle, not category name alone.
AcceptanceTypical approach: Wiremap and continuityMore demanding conditions: Stored certification results against the specified link limitWhat determines the choice: Define the required test and result format in the scope.
AdministrationTypical approach: Labels at both endsMore demanding conditions: Room, panel, port and outlet records tied to drawingsWhat determines the choice: Choose the record depth the support team will maintain.
CapacityTypical approach: Current outlet countMore demanding conditions: Spare ports, pathway fill and growth allowanceWhat determines the choice: Balance predictable growth against unused material and space.
Before design

What we need to know

  • Floor plan and device locations
  • Application speeds and power-over-Ethernet loads
  • Cable distances and environmental conditions
  • Room, pathway and ceiling access
  • Owner labeling and test-report requirements
At closeout

What you should receive

  • Outlet and cable schedule
  • Labeled patch-panel and work-area terminations
  • Per-link test-result files
  • As-built route and endpoint records
  • Exception and remediation log
Equipment examplesSee relevant hardwareView details
Best fit

When this service makes sense

  • Office, retail, education and healthcare fit-outs
  • Multi-site standards and refresh programs
  • New wireless, camera, voice or building-system deployments
  • Remediation where reliable link records do not exist
Before we commit

What we verify first

  • Distance and channel-component limits
  • Pathway fill, bend radius and pulling tension
  • Separation and coordination with other building systems
  • Access windows, occupied-space protection and firestop responsibility
Site contextSee where this work is usedView details
Where it is used

How site conditions change the design

Occupancy, operating hours, user activity, regulation, weather, construction, and access can change the design.

Common questions

What people usually ask

Is Cat6A always the right choice?

No. The intended application, channel length, bundle and pathway conditions, device power, environment, cost and expected service life should drive the choice.

What does a cable test prove?

That depends on the instrument and limit selected. A certification result can evaluate a permanent link against defined performance limits; a basic continuity test cannot establish the same thing.

What should the owner receive at closeout?

At minimum: a cable and port schedule, durable labels, the agreed test files, as-built location information, photos where useful and a resolved exception list.

Standards and referencesReview the source materialView details