Owner
Yes. GDS Technology is an Allied Member of BOMA Georgia, with membership beginning August 10, 2026. Membership is a relevant industry connection, but it is not an endorsement or a substitute for reviewing a provider's support practices, building-system responsibilities, documentation, and follow-through. Assess the working relationship as carefully as the affiliation.
What does BOMA Georgia membership tell a property team?
GDS Technology is an Allied Member of BOMA Georgia. Managing Partner Jonathan Fitzgerald represents the company, and the membership also includes membership in BOMA International.
That affiliation gives property teams a useful point of context when considering a technology provider in commercial real estate. It does not certify the provider, guarantee service quality, or establish that the provider is right for a particular building.
Ask what the provider will own, how it coordinates with property staff, and what records you will receive when work is complete. Those details show how the relationship will work after the initial conversation.
A building issue can cross responsibility lines. A tenant may report unreliable connectivity while the cause sits in shared cabling, a network closet, a carrier handoff, or an application managed by another provider. A capable partner helps trace the dependency and clarify who should act.
GDS Technology has been a BOMA Georgia Allied Member since August 10, 2026.
Use membership to start a conversation, then verify the operating details. The practical test is whether the provider can explain the building's technology responsibilities and how it will support them.
Which building dependencies should you map before choosing support?
In a multi-tenant property, technology responsibilities may be divided among the building owner, property manager, tenants, carriers, and service providers. Internet service, riser cabling, access control, cameras, office networks, and cloud applications may each have a different owner.
When something fails, identify where the problem occurs and where responsibility changes. That makes it easier to route the issue to the right party instead of treating every symptom as a separate ticket.
Map the actual building rather than assuming every site has the same layout. Identify the telecom entrance, network rooms, riser pathways, tenant demarcation points, wireless coverage areas, and technology shared across suites.
Include facilities and property operations in the walk-through. They may know about access restrictions, previous work, and recurring trouble spots that do not appear in network diagrams or vendor records.
Separate information technology work from facilities and life-safety responsibilities. A managed IT provider can assess networked systems and coordinate within an agreed scope, but building owners and authorities retain their own approval and compliance responsibilities.
Before work involving regulated systems or construction is scheduled, identify the responsible parties and required reviews. Confirming those boundaries early helps avoid preventable delays.
For cabling and low-voltage work, ask how labeling, testing, and closeout documentation will be handled. GDS Technology references applicable TIA cabling and testing standards and BICSI installation and labeling practices in relevant scopes. These references describe project practices; they do not mean every project meets every requirement or receives an authority's approval.
A practical dependency map should identify:
- Shared building infrastructure and the party responsible for it.
- Tenant-owned systems and the provider supporting each one.
- Handoffs among the property, carrier, IT provider, and other vendors.
- Required access, approvals, and closeout records for planned work.
Start with the building's dependency map, not a product list. Clear boundaries make it easier to resolve the next fault.
How can you assess response and follow-through?
Ask a provider to walk through a realistic support scenario: a tenant cannot reach a cloud application, the building network appears healthy, and the carrier reports that its circuit is up. Listen for a clear sequence: confirm the impact, trace the affected path, identify who owns each segment, communicate next steps, and record the resolution.
Clarify what the service agreement covers. Ask how users submit requests, which systems are monitored, what support hours apply, when onsite work is available, and how urgent issues are escalated.
Do not infer response commitments from association membership or a broad description such as "managed IT." If a specific response target matters to your operations, ask for it in writing before signing.
Follow-through means leaving the property in a better-documented state. Request updated records for completed work, including relevant device details, cable labels, configuration changes, and unresolved dependencies.
A workaround known only to one employee is difficult to maintain. Documenting what changed and what remains helps property staff and future providers make informed decisions.
A client review offers one example of a service experience, not a guarantee of the same outcome in every engagement. Harold, a media client, said: "Cain responds quickly, knows his stuff, and solves problems fast. He never makes me feel behind on technology." His comment describes his experience with communication and problem-solving; it does not establish a universal response-time commitment.
Judge the written scope and the quality of the handoff. Good follow-through makes the next decision easier, even when another provider owns part of the solution.
What should you compare when planning an IT support budget?
In the Atlanta, GA market, fully managed IT is priced at $120 - $250 per user/month. This range applies to comprehensive managed IT plans, and scope and compliance needs materially affect cost. Compare included support, endpoint management, security work, backup responsibilities, and onsite coverage, not just the monthly figure.
In the Atlanta, GA market, managed IT priced per device runs $35 - $110 per device/month. This model focuses on endpoint or device management, and scope varies materially. Confirm which device types count, what ongoing support is included, and whether servers, network equipment, or specialized building systems are treated separately.
In the Atlanta, GA market, IT / Network Technician labor is $125 - $300 per hour for commercial professional-services labor. Ask whether quoted work includes diagnosis, travel, documentation, after-hours scheduling, or coordination with a landlord, carrier, or tenant vendor. These details affect the total project cost even when the hourly rate is clear.
For a property with internal IT staff, co-managed IT planning ranges run $60 - $160 per user/month nationally. The range reflects different responsibility splits, with the higher end associated with more mature co-managed delivery. Define which team handles user support, security administration, network changes, vendor coordination, and after-hours escalation before comparing proposals.
These are market planning ranges, not GDS Technology's price list. Request a written scope that names inclusions, exclusions, assumptions, and ownership boundaries. A useful comparison is between the work being delivered, not just the billing unit.
Compare proposals by scope and accountability. A clear agreement helps you understand what is covered and who acts when a building issue crosses provider boundaries.
What is a practical first step for a Norcross building?
Choose one recurring issue or an upcoming tenant change and trace the technology path with property operations and IT. Record who owns each handoff, where relevant equipment is located, what evidence is available, and what would need to happen if the issue returned.
Then ask prospective providers how they would assess that specific situation. A useful answer distinguishes immediate containment from a durable correction, identifies missing information, and explains what requires approval from the property owner or another provider.
For support across business systems, review GDS Technology's managed IT services and IT help desk. For building infrastructure, see riser management services and structured cabling and low-voltage services.
GDS Technology's BOMA Georgia membership gives property teams a relevant reason to start a conversation. A dependency walk-through will help determine whether the provider's approach fits the building's operating needs.
Frequently Asked Questions
Is GDS Technology a member of BOMA Georgia?
Yes. GDS Technology is an Allied Member of BOMA Georgia. Its membership began August 10, 2026, and Jonathan Fitzgerald represents the company. Membership is an industry affiliation, not an endorsement or certification. Property teams should still assess the provider's service scope, communication, documentation, and fit for their building.
Does BOMA Georgia membership guarantee a provider is right for my property?
No. Membership can be a useful point of context, but it does not establish service quality, response commitments, certifications, or suitability for a specific site. Ask providers to explain responsibility boundaries, escalation steps, documentation practices, and how they coordinate with property staff, tenants, carriers, and other vendors.
What should a Norcross property team ask an IT provider?
Ask which systems and locations are in scope, how tenant and building responsibilities are separated, what support hours and escalation process apply, and what records you receive after work. For shared infrastructure, ask how the provider traces dependencies across cabling, network equipment, internet service, and connected building technology.
How much does managed IT cost in the Atlanta market?
In the Atlanta, GA market, fully managed IT is $120 - $250 per user/month, while managed IT per device is $35 - $110 per device/month. The scopes differ, and support, security, compliance, and equipment coverage can affect a proposal. These are market ranges, not GDS Technology's prices.
What is the simplest way to evaluate a technology partner?
Pick one recurring failure or planned tenant change and map its technology dependencies with property operations and IT. Ask a provider to explain who owns each segment, what evidence is needed, how immediate disruption would be handled, and what documentation would remain after corrective work.
