Verified as of 1 August 2026. Product naming, module names and deployment options for this platform have changed repeatedly over the years, so treat specifics as a snapshot and confirm against the vendor before you commit.
Archibus turns up on shortlists for large estates and then confuses everyone in the room, because half the buyers think it is a maintenance system, the other half think it is a space-planning tool, and the vendor slide deck implies it is both plus real estate, projects and sustainability. It is closest to that last description. This is the first dedicated Archibus piece on this site, and it is written from implementation experience rather than a brochure. I will explain what Archibus genuinely is, how its module structure works and which modules organisations actually turn on, what the deployment model means for your IT team, and the realistic shape and duration of a rollout. Then the honest part: who it suits, and who should walk away.
What Archibus actually is
Archibus is an Integrated Workplace Management System, an IWMS. If you have read my breakdown of CAFM vs CMMS vs EAM vs IWMS, IWMS is the widest of those categories: it wraps facility and maintenance management inside a broader platform that also manages a real estate portfolio, leases, capital projects and sustainability reporting. Archibus sits squarely in that band. It is not a maintenance-first tool that grew some space features. It grew up on the space and real estate side and added maintenance, which is exactly why maintenance-first buyers often find its centre of gravity in an unexpected place.
Practically, Archibus spans five domains that map onto the classic IWMS definition:
- Space and occupancy → floor plans, room and desk inventory, chargeback, utilisation, moves.
- Real estate and leases → property portfolio, lease administration, critical dates, cost schedules, compliance with lease accounting standards.
- Maintenance → assets, preventive and reactive work orders, service desk requests.
- Capital projects → programmes, budgets, project tracking for fit-outs and refurbishments.
- Sustainability and energy → consumption tracking, emissions and ESG-oriented reporting.
The important word is integrated. The value proposition is not any single domain, it is that space, lease, maintenance and project data live in one model, so a floor is the same floor whether you are charging its cost back to a business unit, planning a move into it, raising a work order in it, or reporting its energy use. Systems that only do maintenance cannot answer real estate questions, and systems that only do space cannot run work. Archibus is built to answer across all of them, which is its strength and also the source of its complexity.
The tell that Archibus fits
If the hardest questions your leadership asks are about space cost, occupancy and lease exposure, and maintenance is just one of several things the estate needs, Archibus is playing to its strengths. If the hardest questions are all about work orders, PM compliance and spare parts, you are looking at a platform whose weight sits somewhere you will not use.
A note on the name
Archibus has changed hands and branding more than once. It spent decades as an independent product, then became part of a portfolio consolidation, and it is now marketed under Eptura, the company formed from the merger of iOFFICE and Condeco that also folded in SpaceIQ and other workplace brands. You will still see the product written as Archibus, ARCHIBUS, and "Archibus by Eptura", and older documentation, partners and job descriptions use naming that predates the current owner. None of this changes what the software does, but it does mean you should confirm the exact current product edition, module names and licensing with Eptura or an authorised partner rather than trusting a five-year-old comparison page. I date this article deliberately for that reason.
How the module structure works
Archibus is modular by design. You do not buy "Archibus" as one monolith and switch everything on. You license a set of application modules that sit on a shared data core, and you deploy the ones that match the problems you are actually solving. This is normal for IWMS platforms and it is the single biggest driver of both cost and scope: the more domains you light up, the longer and more expensive the programme, because each domain needs its own data, its own process design and its own owner in the business.
In my experience the mistake is rarely buying too few modules. It is buying a wide bundle because it looked good value, then trying to implement all of it at once, and stalling because the organisation cannot feed that many modules with clean data simultaneously. The organisations that succeed pick a lead domain, usually space or leases, get it live and trusted, then extend.
The table below is a practitioner's view of the modules organisations most commonly deploy. Adoption levels are my own read from implementation work, not vendor figures, and module names shift between editions, so match these to whatever Eptura currently lists.
| Module | What it solves | Typical adoption | Data it depends on | Common pitfall |
|---|---|---|---|---|
| Space & Occupancy | Floor plan inventory, room and desk allocation, utilisation, chargeback | Very high, usually the entry point | Accurate CAD or BIM floor plans, room polygons, an org and headcount feed | Drawings that do not match reality; polygons never reconciled to actual walls |
| Real Estate & Leases | Property portfolio, lease administration, critical dates, cost schedules | High in owner-occupier and government portfolios | Lease documents, cost lines, currency and escalation terms, accounting rules | Underestimating lease abstraction effort; missing a renewal date after go-live |
| Maintenance / Assets | Asset register, preventive and reactive work orders, service desk | Medium, often phased in after space | A clean asset hierarchy, locations tied to the space model, PM schedules | Treating it like a full CMMS and expecting depth it does not lead with |
| Capital Projects | Programmes, budgets and tracking for fit-outs and refurbishments | Lower, concentrated in estates with active capital pipelines | Project structures, budget lines, links to affected space and assets | Buying it before there is a real project process to digitise |
| Sustainability & Energy | Consumption tracking, emissions and ESG-oriented reporting | Growing, often the newest module added | Meter and utility data feeds, emission factors, reporting boundaries | No reliable meter data source, so reports are estimates dressed as facts |
| Workplace Services | Room and desk booking, visitor management, moves | Medium, higher in hybrid-work office estates | The space model, occupancy data, employee directory integration | Rolling out booking on top of a space model no one has validated |
Notice the pattern in the last two columns. Almost every module leans on the space model, and almost every pitfall traces back to data that was not clean before go-live. That is the defining truth of Archibus programmes: the platform is only ever as good as the space, asset and lease data you feed it, and getting that data right is most of the work. If you want the reasoning behind a durable asset structure before you load any of this, I cover it in asset hierarchy design for CAFM and EAM.
A caution on module bundles
A wide module bundle at a good discount is not a bargain if you cannot staff and feed it. Every module you switch on needs an owner in the business, a data source and an ongoing maintenance routine. Modules that go live without those three things become empty screens people learn to ignore, and an ignored module still costs you in licensing, support and the credibility of the whole platform. Buy for the phase you can actually deliver.
The Web Central deployment model and what it means for IT
Archibus has historically been delivered through a web application server layer that the product line has long branded Web Central, a browser-based server application sitting on top of a relational database. Users work in the browser, the server holds the application logic, and the database, typically a mainstream commercial engine, holds the model. Alongside the browser experience there have been mobile apps for field work and CAD and BIM integration for the drawings that feed the space model. Confirm the current edition names with Eptura, because deployment branding has shifted along with ownership.
What matters more than the branding is the choice underneath it. Archibus can be run in two broad shapes, and this is the decision your IT function needs to weigh:
- Self-hosted or on-premises. You, or a hosting partner, run the application server and database on infrastructure you control. This gives you maximum control over data residency, integration and upgrade timing, and it costs you the most in operational ownership: servers, patching, backups, the database licence and the people who keep it all healthy.
- Vendor-hosted cloud / SaaS. Eptura hosts and operates the platform for you. This is the direction the wider IWMS market has moved, and Eptura has pursued cloud credentials seriously, including US government FedRAMP authorisation for its hosted IWMS. You trade some control for far less operational burden and a managed upgrade path.
For IT, the practical implications are concrete. If you self-host, you own a Java-style application server, a commercial database and an upgrade cadence, and you need people who understand all three. You also own the integrations: an Archibus deployment is rarely an island, it needs an identity feed for single sign-on, an HR or directory feed for people and org data, and often a link to finance for lease costs and to a CAD or BIM environment for drawings. If you go SaaS, most of the infrastructure burden shifts to the vendor, but you inherit their release schedule and you still own every integration at your end. Either way, plan for single sign-on, an authoritative source for space and org data, and a clear position on where your data physically lives, because for government and regulated estates that last point is frequently the deciding factor.
The integration reality
The deployment model decides who runs the servers. It does not reduce the integration work, which lands on you in either shape. Identity, HR or directory data, finance for leases, and CAD or BIM for drawings are the four connections almost every Archibus programme needs, and they are where timelines slip. Scope them at the start, not after go-live.
The typical implementation shape and duration
Archibus is not a sign-up-and-go tool, and anyone who tells you it is has not implemented one. The shape of a realistic programme looks like this:
- Discovery and design. Decide the lead domain, agree the space, asset and lease data standards, map the org structure and the processes each module will support. This phase quietly determines whether the rest succeeds.
- Data preparation. The heaviest lifting. Reconciling floor plans to reality, abstracting leases, building the asset hierarchy, cleaning the org and headcount feed. On most programmes this is the longest phase, and rushing it is the number one cause of a disappointing go-live.
- Configuration and integration. Configure the licensed modules, build single sign-on and the HR, finance and CAD or BIM connections, set up chargeback and reporting.
- Testing and training. Validate against real scenarios, train the people who will own each module, load balance the drawings.
- Go-live and extend. Launch the lead domain, stabilise, then bring the next module up in a following phase.
On duration, be realistic rather than optimistic. A focused single-domain deployment, space and occupancy for one campus with clean drawings, can land in a few months. A multi-domain rollout across a real estate portfolio with leases, maintenance and projects, integrations to identity, HR and finance, and messy source data, is a programme measured in quarters and sometimes across a year or more. The variable that moves that number most is never the software. It is the state of your data and the maturity of your processes. Two organisations buying the identical modules can see wildly different timelines purely because one had a clean space model and clear ownership and the other did not. Budget accordingly, and expect the cost split to weigh far more toward services and data than toward licences. I break the money side down separately in CAFM pricing and implementation cost, and the same logic applies to IWMS platforms like this one.
Who Archibus genuinely suits
Archibus earns its keep where space and real estate data carry at least as much weight as maintenance. The estates where it consistently fits:
- Large owner-occupied estates where space cost, chargeback and occupancy are board-level questions.
- Universities with big, mixed portfolios, complex space allocation and a genuine need to tie maintenance, space and projects together.
- Government and public-sector portfolios where property, lease compliance and data residency matter, and where the vendor's government cloud credentials are relevant.
- Organisations where lease and space data carry as much weight as maintenance, multi-site occupiers managing a portfolio as a strategic and financial asset rather than just a set of buildings to keep running.
The common thread is breadth. If your problem genuinely spans real estate, space, maintenance and projects, and you want them in one model rather than four disconnected systems, an IWMS like Archibus is the right shape of answer, and its long history in space and real estate is a real advantage.
Who Archibus does not suit
Just as important, and less often said honestly. Archibus is the wrong tool if:
- You are a small, maintenance-first team. If your whole problem is work orders, PM schedules and spare parts, you need a CMMS, not an IWMS. Archibus can do maintenance, but you would be buying a real estate and space platform to use a fraction of it, paying for weight you never touch.
- You have no real estate or space complexity. A single site with no chargeback, no leases and no portfolio questions does not need the domains that justify Archibus.
- You cannot resource the data work. If you do not have, and cannot fund, the effort to clean floor plans, abstract leases and build an asset hierarchy, the platform will underdeliver regardless of how good it is.
- You want fast time-to-value on one narrow problem. Point tools solve point problems faster. Archibus rewards organisations that need breadth and will invest to get it.
I have seen maintenance-first teams talked into IWMS platforms and end up frustrated, running a fraction of the capability at a multiple of the cost a good CMMS would have carried. There is no shame in buying the smaller category. The category comparison exists precisely so you can match the tool to the problem instead of the other way round.
A note on independence
I am not affiliated with Eptura, I am not an Archibus reseller, and nothing here is sponsored. This is written from the perspective of someone who implements and integrates workplace and asset platforms for a living, which means my interest is in you buying the right category and the right modules, not the biggest deal. Where I have described specifics, product editions, module names, deployment options, treat them as a dated snapshot of a platform whose branding and packaging have changed repeatedly and will change again. Verify the current picture directly with the vendor or an authorised partner before you spend anything.
For the vendor's own current description of the platform, see Eptura Archibus and the parent company at Eptura .
Conclusion
Archibus is a full IWMS: space and occupancy, real estate and leases, maintenance, capital projects and sustainability, held together in one data model. It is modular, so you switch on what you need, and the modules almost all lean on a clean space model, which is why data preparation is the real work of any rollout. It runs through a web application layer, historically branded Web Central, in either a self-hosted or a vendor-hosted cloud shape, and either way your team owns the integrations. It suits large owner-occupied estates, universities and government portfolios where space and lease data matter as much as maintenance, and it is the wrong buy for a small maintenance-first team that needs a CMMS. Match the platform to the breadth of your actual problem, get your data right before you go live, and confirm the current branding and packaging with the vendor, because with this product that detail keeps moving. This is the hub for the Archibus comparisons that will follow.
Written by Muhammad Abbas
CMMS / CAFM Manager & Enterprise Integration Specialist · 22+ years across ERP, EAM, CAFM and enterprise integration.
Work with me