Carrier i-Vu

i-Vu is current and the name is confirmed. The current release is i-Vu Pro 10, specification sheet 11-808-1229-01 revision 10/25, and the family comprises i-Vu Pro as on-premises software licensed by controller count, i-Vu Cloud as a SaaS offering, i-Vu Express as a hardware appliance with the software preloaded, and i-Vu for Life Sciences. It is unambiguously software: Carrier describes i-Vu Pro as a PC-based web server application sold as software-only part numbers with the server itself sold separately.

Functionally it is a web supervisory head-end over BACnet field controllers: schedules, setpoints, trends, alarms, reports, dynamic floor plans, dashboards, energy reporting and analytics, fault detection and diagnostics, graphics, system backups, BACnet network discovery, engineering tools and role-based user access. BACnet credentials are strong: it is listed as a BACnet Advanced Operator Workstation supporting BACnet Revision 19, supports BACnet Secure Connect as an encrypted datalink layer, and version 10 adds smarter BACnet discovery. Field controller support spans modern Carrier TruVu controls alongside explicit backward compatibility to legacy CCN and Open controllers.

Two things set it apart from most head-ends in this category. First, the edition ladder is clean and explicit: Pro-5 for up to five controllers, Pro-32 for up to thirty-two, Pro-750 for up to 750 and Pro Unlimited, plus i-Vu Express for smaller buildings, and Carrier states it accommodates buildings of all sizes with unlimited simultaneous users. There is also a documented on-premises to cloud upgrade part number, so the platform scales from a single small building to an enterprise estate without changing product. Second, the data tier is genuinely enterprise grade and pluggable: Apache Derby is included by default, with Microsoft SQL Server 2016 through 2022, SQL Server Express, Oracle 19c, MySQL through 8.0 LTS and PostgreSQL 12 through 17.2 supported, the engines sold separately. That is rare in a BMS head-end and valuable for reporting.

Security is modern: TLS 1.3 with 256-bit encryption between client and i-Vu server, BACnet Secure Connect, stated access controls and intrusion detection, and the Life Sciences edition adds FDA 21 CFR Part 11 compliance with digitally signed reports. The cloud edition runs on Amazon Web Services, with hosting, maintenance and backups included. Localisation is deep, with eighteen languages including Brazilian Portuguese, Japanese, Korean, Russian, Simplified and Traditional Chinese, Thai and Vietnamese.

The limitations are specific. Protocol breadth is narrow in the published material: only BACnet is named, with Modbus, LonWorks, KNX, OPC UA and MQTT nowhere stated, so multi-protocol estates should expect gateways. Several buyer-critical functions are paid add-ons rather than standard, including LDAP and single sign-on, trend export, the ACxelerate commissioning tool and the Predictive Insights subscription. And one of the version 10 headline features, live and scheduled full or partial system backups, is flagged on-premises only, so the cloud edition does not get it. No REST API, BI or CMMS integration is documented.

Who it fits. Buildings of any size on a BACnet estate, which is unusual in this category: the Pro-5 edition genuinely addresses a five-controller building while Pro Unlimited addresses an enterprise estate, with a documented upgrade path between on-premises and cloud. The value case is strongest where Carrier HVAC equipment dominates. Regulated life sciences sites have a defined edition with 21 CFR Part 11 compliance and digitally signed reports. Organisations that want BMS data in a real database for reporting are better served here than almost anywhere else in this category, given support for SQL Server, Oracle, MySQL and PostgreSQL.

Who it does not fit. Mixed-protocol estates, since only BACnet is documented. Buyers who need single sign-on, trend export or commissioning tooling included rather than as paid add-ons. Buyers who want the version 10 live backup feature in the cloud edition, where it is excluded. And anyone needing an inbound API or documented BI and CMMS integration, which Carrier does not publish.

Typical use. Carrier HVAC estates from single buildings to large portfolios, delivered through the Carrier Controls Expert dealer network, either on a customer-supplied Windows server with a quad-core CPU, 4 GB RAM and 100 Mbps LAN, or on the hosted i-Vu Cloud subscription.