Managing a Mixed-Brand Elevator Portfolio: Otis, KONE, Schindler, and TK Elevator

Most property managers don't choose to have a mixed-brand elevator portfolio. It happens over time — you acquire a building with Schindler equipment, inherit a KONE installation when you take over a new property, and suddenly the Otis-only approach that worked for your first ten buildings doesn't scale to your thirtieth.

The four major elevator OEM brands and their monitoring platforms

Each of the four major elevator manufacturers offers its own remote monitoring platform:

OEM Brand	Monitoring Platform	Coverage	Access Requirement
Otis	Otis ONE	Otis elevators only	Active Otis service contract
KONE	KONE 24/7	KONE elevators only	KONE Care maintenance agreement
Schindler	Schindler Online	Schindler elevators only	Schindler service contract
TK Elevator	TK Elevator Portal	TK Elevator units only	TK service agreement

Each platform provides genuinely useful data — fault codes, service history, predictive alerts, and maintenance schedules — but only for its own equipment. There is no native cross-brand view. If your portfolio has buildings with multiple brands, you are monitoring them through four separate browser tabs, four separate email alert streams, and four separate reporting formats.

The three problems that compound as your portfolio grows

1. Alert fatigue from four inboxes

Each OEM platform sends its own email notifications. Most property managers, after the first few months, tune them out. You set up inbox filters, route them to folders, and — if you're honest about it — stop checking those folders with any regularity.

The alerts don't stop being valuable because you stop reading them. The information is there. The problem is the format — separate, siloed, with no priority ranking across systems.

2. No portfolio-level health picture

When a board member or CFO asks for the elevator uptime report for Q3, you don't have one. What you have is four exports from four different platforms in four different formats, which then need to be normalized, combined, and formatted before they're presentable.

This is time most facilities teams don't have. So the report either doesn't get produced, or it gets produced inconsistently, or it takes two days of manual work every quarter.

3. No cross-brand benchmarking

If your Otis equipment is consistently outperforming your KONE equipment in older buildings, that's valuable information — both for maintenance planning and for contract negotiations. But you can only discover it if you can see both datasets side by side, normalized against the same health scoring framework.

OEM platforms aren't designed to give you this information. They're designed to show you how their equipment is performing — not how it's performing relative to your other brands.

How high-performing operations teams solve this

The best-run mixed-brand portfolios we've seen use one of three approaches:

Approach 1: The manual aggregation spreadsheet

A shared spreadsheet that someone updates weekly (or monthly) with data pulled from each OEM portal. Works for small portfolios. Breaks down above 15 buildings because the maintenance overhead becomes a job in itself, and the data is always stale by the time it's useful.

Approach 2: The BMS aggregation layer

Buildings with a modern Building Management System (BMS) — Johnson Controls Metasys, Siemens Desigo CC, Honeywell EBI — can route elevator data from multiple OEM controllers into the BMS via BACnet protocol. The BMS becomes the single source of truth for building operations, including elevators.

This works well operationally but doesn't give you the portfolio-level view. Each BMS covers one building or campus. Cross-portfolio reporting still requires aggregating across BMS systems.

Approach 3: A portfolio aggregation platform

Connect a platform layer above the OEM monitoring systems and BMS installations that normalizes all elevator data — regardless of brand — into a unified dashboard with consistent health scoring, a single alert feed, and portfolio-level reporting.

This is what ElevPulse is designed to do. It connects to your existing BMS or OEM accounts via read-only API access and aggregates the data you're already paying your OEM contracts to collect. No additional hardware. No changes to service agreements.

What unified elevator monitoring looks like in practice

With a mixed-brand portfolio running on a unified monitoring platform, the daily operations picture changes significantly:

• ✓One alert digest per morning — all brands, all buildings, ranked by urgency.
• ✓Consistent health scores (0–100%) across Otis, KONE, Schindler, and TK equipment.
• ✓One-click quarterly report showing portfolio-wide uptime, cost avoidance, and incident count.
• ✓Cross-brand benchmarking: KONE equipment in older buildings vs. new Otis installations.
• ✓Maintenance scheduling that accounts for all brands in one calendar view.

The right approach for your portfolio size

Not every portfolio needs the same solution:

• 5–10 buildings, one brand: OEM's built-in monitoring platform is sufficient. Use Otis ONE or KONE 24/7 as provided.
• 10–20 buildings, 2–3 brands: Manual aggregation starts to break down. A portfolio platform pays for itself with the first emergency repair it catches early.
• 20+ buildings, 3–4 brands: Unified monitoring is not optional — it's a cost control requirement. The math on emergency repairs vs. planned maintenance makes the ROI immediate.

What to ask when evaluating elevator monitoring software

If you're evaluating platforms for a mixed-brand portfolio, these are the questions that separate real solutions from demos:

• →Does it cover all four major OEM brands — Otis, KONE, Schindler, and TK Elevator?
• →Does it require hardware installation, or does it connect to existing monitoring systems?
• →Can it normalize health scores across brands using consistent methodology?
• →Does it provide portfolio-level reporting, not just building-level reporting?
• →How long does initial setup take? (The answer should be hours, not months.)
• →Is there a trial period where you can verify it works with your specific BMS or OEM accounts?