Owner
Yes. GDS Technology is an Allied Member of BOMA, and Jonathan Fitzgerald represents the company. The membership is a professional affiliation, not an endorsement or a promise of results. For a Carmel property team, the practical question is whether a provider can understand building operations, coordinate with the people responsible for the property, and follow through on clearly defined work.
In This Article
- What does a BOMA membership tell a Carmel property team?
- Which building technology dependencies deserve attention?
- How can you assess a technology provider's follow-through?
- What should a building technology review cover?
- What IT costs should a Carmel business use for planning?
- What is a practical first step before choosing a partner?
- Frequently Asked Questions
What does a BOMA membership tell a Carmel property team?
GDS Technology's Allied membership answers the affiliation question: the company belongs to BOMA, and Jonathan Fitzgerald represents it. The membership also includes membership in BOMA International. It does not establish that either organization has evaluated or endorsed GDS Technology's services.
For a property manager, affiliation can be a useful starting point, but it is not a substitute for checking fit. Ask how a provider documents systems, coordinates access to occupied spaces, and communicates when work affects tenants or building staff.
Those answers matter to day-to-day operations more than a membership label alone. Membership is context; the working relationship still has to be demonstrated.
Which building technology dependencies deserve attention?
A tenant reports that a camera feed is unavailable, a badge reader is slow, or a suite has lost connectivity. The visible device may not be the source of the problem. The issue could involve cabling, network equipment, power, configuration, a cloud service, or a handoff between tenant IT and property operations.
In a multi-tenant building, first identify who owns each part of that path. A tenant may manage its network while the property team oversees shared risers, access-control equipment, or common-area systems. If those boundaries are unclear, troubleshooting can stall while each party waits for another to act.
Start with the dependency and the responsible party. A useful review records what is shared, what is tenant-controlled, and who approves changes.
How can you assess a technology provider's follow-through?
Ask the provider how it will record the existing environment before making changes. For cabling, that could mean identifying routes and labeling. For network-connected systems, it means documenting relevant connections and dependencies. For proposed work, ask what could be interrupted and who needs to approve it.
Then ask how the provider will communicate. Who receives updates? What information will you get if the issue is not yet resolved? How will the team distinguish a temporary workaround from a lasting correction?
These questions reveal whether the provider treats a ticket as a closed task or as an operational issue that needs a clear handoff. Good follow-through leaves the property team with a usable record, not just a verbal update.
Harold, a media business owner, described his experience this way: "Cain responds quickly, knows his stuff, and solves problems fast. He never makes me feel behind on technology." His account illustrates the value of clear, respectful support. It is one customer's experience, not a response-time commitment for every engagement.
What should a building technology review cover?
Keep the first review tied to an operating concern. If recurring connectivity problems interrupt tenant work, map the network and cabling path before replacing equipment. If a building system depends on shared infrastructure, clarify ownership, maintenance responsibility, and change approvals before a project begins.
A focused review can cover:
- Which systems and connections are shared, and which belong to individual tenants?
- Where are the relevant network and cabling handoffs, and how are they documented?
- Who approves access, maintenance windows, and changes in occupied areas?
- What information should be captured when an issue recurs, so the team can trace the cause instead of repeating a workaround?
- Which security, privacy, or compliance obligations apply to the property's systems and data?
These are discovery questions, not assumptions about a particular building or its rules. Confirm applicable requirements with the relevant authority and qualified professionals for the project. A technology review can clarify scope and dependencies; it cannot establish regulatory approval.
Document responsibilities before a project or recurring fault makes them urgent.
GDS Technology has been a BOMA Allied Member since August 10, 2026.
What IT costs should a Carmel business use for planning?
Published fully managed IT pricing in the Indianapolis, IN market ranges from $110 - $275 per user/month. The range reflects differences in service scope. Compare what is included, such as help desk coverage, endpoint management, cybersecurity work, and planning, rather than comparing the monthly figure alone.
A lower quote may cover fewer responsibilities or assume that the client handles more work internally. Ask for a written scope naming supported users and systems, included activities, exclusions, and how project work is priced. These figures describe market pricing, not GDS Technology's rates.
For co-managed IT, where an internal IT team retains responsibilities, planning ranges run $60 - $160 per user/month nationally. The right budget depends on which responsibilities remain internal and which the provider takes on. Senior IT engineering or consulting planning ranges run $175 - $350 per hour nationally; that is not a Carmel-specific rate.
Compare scope, ownership, and exclusions before comparing price.
What is a practical first step before choosing a partner?
Choose one recurring technology issue or upcoming building change and walk through it with the people responsible for the work. Include property operations and the relevant tenant or IT contact. Ask the provider to identify dependencies, explain what information it needs, and describe how it will report findings and proposed next steps.
GDS Technology lists managed IT, cybersecurity, structured cabling and low-voltage services, riser management, and business video surveillance among its services. A focused conversation can help determine whether one of those areas fits the actual need.
For local information, see GDS Technology's Carmel location page. For building infrastructure, review riser management services and structured cabling and low-voltage services.
Bring one real operating issue, then map its owners and dependencies before discussing a broader engagement.
Frequently Asked Questions
Is GDS Technology a BOMA member?
Yes. GDS Technology is an Allied Member of BOMA, and Jonathan Fitzgerald represents the company. The membership includes membership in BOMA International. It confirms an affiliation; it should not be read as an endorsement of GDS Technology or a promise of service performance. Ask the provider directly how its services fit your property's needs.
Does BOMA membership mean a provider is right for my Carmel property?
No. Membership is one piece of context, not a substitute for checking the provider's scope and working approach. Ask how it documents building systems, coordinates with property and tenant contacts, handles approvals, and communicates unresolved issues. Confirm that the proposed responsibilities match your property's needs and ownership boundaries before work begins.
What IT costs should a Carmel business use for planning?
Published fully managed IT pricing in the Indianapolis, IN market ranges from $110 - $275 per user/month. National co-managed IT planning ranges run $60 - $160 per user/month, while senior engineering or consulting planning ranges run $175 - $350 per hour nationally. Scope affects comparisons. These are market ranges, not GDS Technology rates.
What should I bring to an initial technology discussion?
Bring one recurring issue or planned building change, a description of who owns the affected systems, and any available diagrams or service records. Identify who can approve access and changes. This helps the provider ask focused questions about dependencies, scope, and documentation rather than guessing at the source of the problem.