FM:Systems Workplace vs Serraview

Serraview is still separately marketed, and that needed confirming

Given how much of this segment has consolidated, the first question about Serraview is whether it still exists as something you can buy. It does. Eptura current platform page lists it under Specialized Solutions alongside Archibus, distinct from the platform apps Eptura Workplace, Eptura Engage, Eptura Asset and Eptura Visitor. It retains its own product page, its own call to action and its own live knowledge base, and no vendor or press source announcing a sunset, rename or merge was found. The 2026 documentation describes current work, including an early access Serraview to Eptura Engage integration in which Serraview is the source of truth for team and neighbourhood groupings. That detail matters: it tells you Eptura architecture treats Serraview as owning space structure and the booking product as consuming it.

What Serraview actually does

The documentation index is a better guide than the marketing page. It lists a Spaces module with floorplan navigation and tools for editing, measuring and tagging space, plus space types and layers. It lists Block and Stack, internally VBS, assigning fixed and flexible teams, neighbourhoods and villages to floors and blocks. It lists chargeback and space charge rules. It lists accommodation and occupancy reporting covering people, allocations, workstation audits and variance in desk allocation. It lists two separate utilisation report families, one driven by SVLive data and one by badge swipe data, with views by building, floor, space type and organisational unit. It lists a Workplace Portal supporting a monthly validation cycle where occupants confirm occupancy and workpoints. It lists BOMA reports and area calculations, automated and custom reporting, and cross-building moves and region summaries. That is genuine portfolio machinery, not booking features relabelled.

Treat the marketing figures with more caution. The product page claims Serraview can reduce portfolio size by up to 25 percent and cut desk search time by up to 40 percent, with no published methodology. Those are vendor claims, not benchmarks.

What does not carry over

Serraview is the wrong product for a single-site organisation that wants employees to book a desk. Desk booking appears in its reports, booking rules and reservable space settings, but the documentation does not describe a booking experience in its own right, and Eptura sells Engage for that. Its booking is administrative configuration supporting space data. Visitor management, wayfinding and a mobile app were not verified either.

The integrations position is now documented, and it is better than it first looked. The Serraview knowledge base Integrations section has been read in full, and it names a Serraview Public API covering OrgUnits and People and a Serraview Core API with enumerated endpoints including graphql, buildings, floors, spaces, people, reporting, servicerequests and oauth2. Single sign-on is SAML with Microsoft Azure AD and SAML with Microsoft ADFS. Work management connectors cover Accruent 360Facility and ServiceNow. Occupancy sensors are supported, with an Occupancy Sensor API and sensor maintenance documentation, alongside badge swipe data, SFTP, portfolio data import and extract, a Utilization API, and an Insights Direct Connect naming Power BI, Tableau, Qlik and Microsoft Excel against Snowflake. So this is a well-connected product, not an isolated one.

The calendar nuance matters and should not be flattened: Outlook yes, Teams no. The documentation describes a Serraview to Engage calendar integration using the Office 365 Graph API, a Microsoft Exchange connector and Google Calendar, plus an FAQ about a room timeline not matching Microsoft Outlook. That is real evidence of calendar connectivity. But Microsoft Teams is not supported in Serraview: the only Teams reference in the documentation index is a person-lookup link inside the Engage sections, which is a different product. And what is documented is availability syncing, not proven calendar-native create, cancel or recurring booking. This is the same pattern as Skedda elsewhere in this category: a documented calendar connector is not the same thing as booking from the calendar, and Serraview should not be read as reaching Microsoft Places parity. Several other items commonly asked about, including Teams, SCIM, webhooks, Zapier, Revit, AutoCAD and Slack, are simply not named in the index, which is not a vendor statement that they are unsupported.

The platform question

An FM platform module and a specialist product differ in predictable ways. The module inherits the platform data model, so your space data sits next to your maintenance and asset data without an integration, and your reporting is one stack. The specialist product goes deeper in its own discipline, and in Serraview case the depth is real: chargeback rules, workstation audits, BOMA area calculations and a monthly occupancy validation cycle are not things a general module typically matches. Against that, you are adding a vendor, and in Serraview case a vendor whose other products overlap it.

That overlap is worth naming. Archibus and Serraview both sit under Eptura Specialized Solutions and both address complicated estates and portfolio planning, and Eptura publishes no crisp decision rule for choosing between them. Expect to work that out in a sales conversation. Neither publishes pricing: the Serraview page offers only Get a demo.