FMS:Workplace

FM:Systems is now part of Johnson Controls, which acquired it on 17 July 2023 for a 455 million dollar base price plus a post closing earnout. That is the single most important fact about buying it today, because the product naming is actively in transition. The FM:Systems products page simultaneously presents new suite names, OpenBlue Workplace, OpenBlue Employee and OpenBlue Insights, and the legacy product names FMS:Workplace (described as the comprehensive IWMS solution), FMS:Employee, FMS:Visitor, FMS:Engage, FMS:Marketplace and FMS:Connect for the API. Two formerly listed products, FMS:Portfolio and FMS:Insight, could not be found anywhere and appear to have been retired, with the portfolio capability now presented as Real Estate Portfolio Software and OpenBlue Insights.

The ownership history before Johnson Controls is worth knowing. FM:Systems was founded by Michael Schley, took growth equity from Accel-KKR on 2 February 2017, and then sold to Johnson Controls in 2023. At acquisition it had roughly 1,200 customers and 200 employees with headquarters in Raleigh, North Carolina. It now claims 1,200 plus customers across 80 plus countries with an EMEA headquarters in Blackburn, UK, and names HSBC, Samsung, Banner Health, Boston University, JLL, Sysco and Southwest Airlines as customers.

The capability set is one of the better documented in this profile and notably includes things several competitors omit. FM:Systems states SLA and KPI management and contractor and vendor management explicitly, which Archibus, FAMIS 360 and ManhattanONE do not. It also states asset tracking and classification, work order and ticketing with preventive maintenance scheduling, an FM:Mobile field application, service requests, space and floor plan management, real estate portfolio and lease operations, reporting and dashboards and multi site portfolio management.

Two areas are genuinely strong. First, BIM and CAD: FM:Systems states bidirectional AutoCAD and Revit integration, which is a stronger claim than one way import and matters if your drawings are a live record rather than a snapshot. Second, occupancy sensing: FM:Systems sells its own workplace sensors product line and names VergeSense as a partner, so BMS and IoT integration is a product line rather than a promise. Named ERP integrations include SAP and Oracle or PeopleSoft, and Outlook calendar is named for workplace experience.

Two capabilities are not stated: inspections and audits, and procurement and purchase orders. For a regulated estate with statutory inspection obligations, that is worth probing hard in a demo.

The disclosure weaknesses are real. There is no public documentation or knowledge base at all; everything is behind a customer login. FMS:Connect is described as an enhanced API but no page says REST, and there is no published API specification, so the ERP integration claims name legacy systems (SAP, PeopleSoft, Lawson, Banner) without technical substantiation. Support is business hours only, Monday to Friday 08:00 to 20:00 Eastern, with a paid Enterprise Support tier for better response. For a global estate on a follow the sun operation, that standard support window is a genuine constraint and the upgrade is a cost line.

On pricing, FM:Systems publishes no figure but does something unusually honest: its pricing page names the cost drivers, managed resources, portfolio size, integrations and hardware. And it states plainly that trial versions are not offered, because of the configuration required. A clear no is more useful than silence.

FMS:Workplace fits mid market to large enterprises that want one system spanning space, real estate and maintenance, and that care about drawing fidelity. The bidirectional AutoCAD and Revit integration is the clearest technical differentiator. If your organisation maintains CAD or Revit as the authoritative space record and needs changes to flow both ways rather than be re imported by hand, this product addresses that directly where most competitors do not.

It is also a strong fit for hybrid work and occupancy programmes. FM:Systems sells occupancy sensors as its own product line and integrates VergeSense, so the sensor to space to utilisation chain is first party rather than stitched together. Combined with FMS:Employee, FMS:Visitor and FMS:Engage, it covers the workplace experience layer as well as the facilities layer.

Unusually for a space led IWMS, it also fits buyers who need SLA and KPI tracking and contractor management, both of which FM:Systems states explicitly. That makes it a more credible single system choice for an in house FM team that also manages outsourced contractors than Archibus or FAMIS 360.

FMS:Workplace does not fit buyers who need to validate technical fit before purchase. There is no public documentation, no public API specification, and no trial, and FM:Systems states explicitly that trials are not offered. You will be evaluating on demos, references and written commitments only. If your procurement requires a documented API contract or a proof of concept in your own tenant, negotiate that as a paid pilot and get it in writing.

It does not fit organisations needing 24 by 7 vendor support as standard. Support is business hours Eastern time Monday to Friday, with better response available only on a paid Enterprise Support tier. For a critical estate spanning Asia and Europe, price that tier in from the start rather than discovering it later.

It is also a poor fit for small organisations, and for estates whose primary driver is statutory inspection compliance or in system procurement, neither of which is stated.

Typical use cases. Space inventory and chargeback kept in sync with authoritative CAD or Revit drawings. Hybrid work utilisation measurement using first party occupancy sensors, feeding space planning decisions. Real estate portfolio and lease administration for a multi country estate. Work order and preventive maintenance delivery with SLA tracking against internal teams and external contractors. Visitor management and employee workplace experience on the same platform as the space data. Extending an existing Johnson Controls OpenBlue footprint into workplace management.

Watch for. Which product name appears on the contract, OpenBlue or FMS, since the page uses both. Whether FMS:Portfolio or FMS:Insight is mentioned in any older proposal, because neither could be found as a current product. The support window and the cost of the Enterprise tier. Written confirmation of the API protocol and specification. And how the Johnson Controls relationship affects your controls vendor strategy, given trust and privacy pages now point to johnsoncontrols.com.