Commercial networking Columbia offices need as downtown growth collides with campus

No two closets tell the same story

Three institutions shape Columbia’s office market: the statehouse, the university, and the professional firms that grew up serving both. Each runs on its own construction cycle, which means each wired its buildings for a different decade’s demands. A state agency office and a law firm two blocks apart can share the same complaint, wifi that holds in the lobby and gives out by the third floor, for entirely separate reasons. The reasons rarely match. The fix has to start with which building you’re in, not which symptom you’re seeing.

Diagnosis first, then the drawings

We design to the building in front of us. A decades-old office near the statehouse allows different routing than a renovated space near campus, and pretending otherwise is how closets end up in the state they’re in.

Matched to the building’s age and the tenant’s load

• A plan built from your floor plan, your headcount, and the era of the construction around them
• Redundancy placed where an outage would hurt most during business hours
• Capacity that absorbs new staff or new square footage without a redesign
• Runs specced to carry what the office pushes at peak, well past the code minimum

Pulled, terminated, documented

Fiber backbone, shielded CAT6 horizontals, every run tested before we sign off on our own work. Labels match a drawing you keep. Firewall and VPN are part of the handover, not an add-on quote, and monitoring continues around the clock on our side, so a fault gets flagged before it becomes a help-desk morning.

Why we don’t pretend to be from Columbia

DCMM is a Georgia company, and Columbia projects get the same crew as our Georgia installs. That’s the argument for the arrangement: no local franchise, no subcontractor lottery, one team accountable from the opening walkthrough to the last test result. Walkthroughs fit agency hours or the academic calendar. Nothing gets pulled until the drawings carry your signature, and install week ends when the tests pass, not when the calendar says. Support is remote after that. If a fix ever calls for someone on site, the people who did the build make the trip.