Before You Implement Archibus: The 10 Decisions That Matter Most

Most Archibus projects don’t struggle because of the software. Instead, they struggle because of decisions that were made late, made casually, or never made at all. Before you implement Archibus, a handful of choices will shape everything that follows.

Think about how you structure your buildings, what you call things, and who approves what. Then add what leadership expects to see on a dashboard. These aren’t technical decisions in the narrow sense. Rather, they’re business decisions, and they’re far easier to settle before data, drawings, and reports are built on top of them.

Here are the 10 that matter most.

1. What Problem Are You Solving First?

Archibus covers a lot of ground, including space, maintenance, assets, leases, and projects. That breadth is a strength. However, it can also be a trap, because teams that try to turn everything on at once often end up with a system that does many things adequately and nothing well.

Instead, start with the pain. Maybe it’s work orders that disappear, space data nobody trusts, or assets nobody can find. Once you pick the first problem, define what “fixed” looks like and let that set your phase-one scope. After that, everything else can follow.

2. How Will You Structure Your Space Hierarchy?

Archibus organizes space in layers: sites, buildings, floors, and rooms. Because almost every other record hangs off that structure, it’s one of the most important decisions you’ll make.

For example, is a campus one site or several? Does a building with two wings count as one building or two? And how should you treat a leased floor in a multi-tenant tower?

There’s rarely one right answer. Still, there is a consistent answer, and consistency is what makes reporting work later. So decide the rules, write them down, and apply them everywhere.

3. How Will You Structure Your Organization Hierarchy?

Space tells you where things are. Your organization hierarchy, on the other hand, tells you who they belong to.

In Archibus, that typically means divisions and departments. Here’s the catch: your org chart, your finance system’s cost centers, and your HR data may not agree with each other.

First, choose which source wins. Next, set how often it updates. Finally, plan for reorganizations, because they will happen. Cost allocation, chargebacks, and space reporting all depend on getting this right.

4. What Are Your Naming and Coding Standards?

This is the decision that sounds boring and causes the most pain.

Building codes, room numbers, equipment tags, and drawing names all need a convention. Without one, you get duplicates, near-duplicates, and codes that only mean something to the person who created them.

A good standard is short, predictable, and documented. It should answer questions like these:

• How long can a code be, and which characters are allowed?
• Should room numbers match the signs on the doors or the architect’s drawings?
• When new buildings appear or rooms are renumbered, how will you handle them?

So agree on the rules early. Otherwise, retrofitting a naming standard across thousands of records becomes a project of its own.

5. How Will You Classify Rooms and Equipment?

Archibus uses categories, types, and standards to classify space and assets. In turn, those classifications drive nearly everything useful, including utilization reports, planning, and benchmarking.

Too few categories, and your data is too vague to act on. Too many, and nobody can apply them consistently.

Aim for a list that is detailed enough to answer the questions leadership actually asks. At the same time, keep it simple enough that a new employee can pick the right option without a training manual. Equipment standards deserve the same thought, so decide how deep you’ll go before you start registering assets.

6. How Should Workflows and Approvals Work?

Every organization has a way work gets requested, approved, assigned, and closed. Often, that process lives only in people’s heads.

Implementation is your chance to make it explicit. For instance, who can submit a request? Who approves it, and above what cost? How does an urgent request differ from a routine one? And what happens when something sits too long?

However, resist the urge to copy a broken process into a new system. Likewise, don’t over-engineer. Instead, start with a workflow your team can actually follow, then refine it once real requests are flowing.

7. Who Gets Access to What?

Not everyone needs to see everything. A technician, a department manager, a space planner, and an executive each need different views and different permissions.

Therefore, define your roles before you build your security model. Next, decide who can create, edit, approve, and delete, and who can see cost data. For public sector and regulated organizations, this also ties directly to audit and compliance expectations.

In short, it’s much easier to design access around real roles than to patch it after users complain.

8. Where Will Your Data Come From?

Archibus rarely works alone. For example, employee data may come from HR, cost data may come from a financial system, and floor plans may come from CAD or BIM files.

For each source, settle three things up front:

• Which system is the source of truth
• How often the data syncs
• Who fixes it when the two systems disagree

Data quality is the quiet make-or-break factor in any IWMS project. If your floor plans are outdated or your employee list is stale, the system will faithfully reflect that. For that reason, cleaning data before migration costs far less than cleaning it after.

9. What Will Your Reporting Structure Look Like?

Here’s a useful exercise: write down the five questions leadership asks most often. Then work backward.

Ask what data it takes to answer them. Check whether your hierarchy supports the groupings leaders want. Confirm that your classifications let you slice the data the way they think.

Unfortunately, too many teams design the data first and discover later that the reports they need aren’t possible. So flip that order. Decide your key metrics and dashboards early, and let them shape the structure beneath.

This matters even more as AI enters the picture. Because tools like IMS.ai work from the data already in Archibus, a clean, consistent structure makes every answer better.

10. Who Owns the Data After Go-Live?

This is the decision most often skipped. However, it’s the one that determines whether a good implementation stays good.

Data decays over time. Rooms get renamed, employees move, and equipment gets replaced. Without an owner for upkeep, the system slowly drifts away from reality, and users stop trusting it.

So assign ownership before go-live. For example, decide who maintains space data, who approves new codes, and how often someone reviews data quality. In practice, a lightweight governance process beats a perfect one that nobody follows.

Bringing It Together

Notice what these ten decisions have in common. None of them requires you to be an Archibus expert. Yet all of them require your organization to agree on how it works.

That agreement is the real work of implementation. The software can be configured to fit almost any answer, but it needs you to choose one.

If you’re planning to implement Archibus, or you’re partway through and wondering whether the foundation is right, it’s worth pressure-testing these decisions with someone who has seen them play out many times.

IMS Consulting has guided organizations across higher education, government, healthcare, and the private sector through Archibus implementations. If you’d like help working through these decisions, we’re happy to talk.

About IMS Consulting:
For over a decade, IMS Consulting has been at the forefront of delivering comprehensive services across multiple platforms, including Archibus, ServiceNow, and ESRI, to our diverse clientele in both public and private sectors. As a dedicated small business, we offer personalized attention from experienced and certified consultants. Our experts collaborate closely with clients to gain a deep understanding of their operational processes, identify unique requirements, and uncover opportunities for enhanced management of their infrastructure. We are committed to helping you make informed capital budgeting decisions that yield benefits today and sustainably into the future.