Solutions

One Engine, Many Domains

From stadiums and commercial buildings to hospitals, data centers and fiber networks, ECMonitor adapts to the monitoring demands of different environments, each with its own infrastructure, operational priorities and performance requirements.

Available now

Shipping and deployed
DAS

See the whole DAS signal chain in real time

A DAS spans a head-end, optical transport and dozens of remotes across a venue, often from more than one OEM. When something drifts, the first sign is usually a coverage complaint, long after the cause appeared in the signal chain. Manual checks and vendor portals do not scale across a multi-building deployment.

What you get

  • Full-chain monitoring: Every active node, head-end to remote, polled continuously with health and connectivity state.
  • AI alarm grouping: Alarms from one failed head-end become one incident with the likely cause attached.
  • Secure remote OEM access: Reach the OEM interface through the edge unit; no VPN, no truck roll for a config check.
  • Multi-site, one console: A single pane of glass across every site you run, with engineers, managers and customers each seeing the sites and detail their role allows.
  • iBwave and floorplans: Alarms tied to physical location, so a fault points to a spot on the plan, not just a device ID.
  • Ticketing and SLA: Native ticketing or ServiceNow and Jira, with SLA tracking from alarm to resolution.

What we monitor

  • Head-end, OTRX, point of interface, remotes and repeaters
  • Health, connectivity and alarm state for every node
  • Multi-vendor fleets across 100+ supported devices
  • UE probes and backhaul circuits at the same sites
AI alarm grouping

Eight alarms from one failed head-end
become one incident

When a head-end drops, every remote behind it alarms at once. ECMonitor recognizes they share a head-end, folds them into one incident with the likely cause attached, and routes it to the right engineer. Press the button in the worklist to see it happen.

ECMonitor ▸ Worklist03:42:18 UTC
P1 · 2P2 · 5P3 · 11
◆ Incident #4471 · 8 alarms, 1 root cause
Head-end failure at SFO-T2 cascaded across 8 downstream remotes. Grouped into one incident with a drafted summary. The NOC has acknowledged it and your engineer is working the head-end, not the queue.
▲P1SFO-T2-DAS-04LMR-LOSS · head-end00:08:24OPEN
▲P1NYC-MSG-PS-BDA-1BDA-RF-OFF · public safety00:14:11OPEN
◆P2BOS-LOG-D7TEMP-WARN00:42:08ACK
◆P2ATL-MERC-WSPWR-FLAP01:12:33ACK
●P3LAX-T4-DAS-02LINK-DEG02:08:51ASSGN
●P3CHI-MIL-DAS-01BATT-LOW04:21:00ASSGN
■P4PHX-DC2-FIB-07OPT-DEG · data center, hall 212:33:00ASSGN
8 alarms share a head-end at SFO-T2.
Group them into one incident?
DAS head-end connected to an on-site Edge Compute Unit, which tunnels to ECCloud, which is watched by the NOC

The Edge Compute Unit connects locally to the DAS head-end, discovers the topology and tunnels only the signal to ECCloud. No inbound firewall changes, no VPN. Engineers reach the OEM interface through the same tunnel.

Schedule a DAS demo
Public Safety

When coverage fails, you have minutes

Public safety BDA and ERCES systems are life-safety infrastructure. A dead battery, a drifting signal or an offline BDA is both a safety risk and a compliance failure. Annual testing tells you the system worked once; continuous monitoring tells you it is working right now.

Detection, control and proof

  • Instant fault detection: Signal loss, battery health and BDA state monitored continuously, not sampled once a year.
  • Remote BDA control: BDAs turned on or off remotely, individually or in groups, with a mandatory reason code and audit log.
  • Compliance reports on demand: The documentation inspections require, generated from live data.
  • Escalation that reaches you: Severity-aware alerts to the right people, with grouping to cut nuisance noise.
  • Portfolio view: Every site's compliance and health state on one board.

What we monitor

  • Class A and Class B BDAs and ERCES: RF state, signal, battery and charger, antenna and enclosure alarms
  • Public safety DAS and LMR infrastructure
  • Battery, power and backhaul
  • Passive RF: antennas, cables and connectors, through supported passive monitoring

Authorities having jurisdiction

Real-time status of every monitored system and fully logged, controlled ON/OFF actions.

Operations and monitoring companies

Multi-site portfolios in one view, AI-assisted triage, ticketing that connects to what you run.

Building and venue owners

Continuous visibility between inspections and defensible records of outages.

Public safety BDAs connected to an on-site Edge Compute Unit and modem, tunnelled to ECCloud and watched by the NOC, with role-based views for AHJs, operations companies and owners

Specific code references (NFPA 72, IFC 510) vary by jurisdiction and adopted edition. Confirm requirements with your AHJ; ECMonitor supports the monitoring and reporting, not the code interpretation.

Fiber

The transport everything else rides on

When fiber or optical transport degrades, the symptoms scatter across every service that depends on it: RF remotes, public safety links, IT connectivity. Monitored in isolation, each looks like its own problem. Monitored together, the pattern points straight at the transport layer.

Fiber, in context

  • Path and transport health: Continuous state across fiber paths and the optical transport that carries critical services.
  • One console with RF and public safety: Transport faults alongside the DAS and public safety services they affect, no silo.
  • Root-cause grouping: AI ties scattered downstream symptoms back to the upstream transport event.

What we monitor

  • Fiber paths and optical transport carrying DAS, public safety and IT
  • Link and device alarms, plus optical and connectivity indicators where exposed
  • Backhaul circuits
Data Centers

One monitoring layer across every vendor in the hall

Power, cooling, network and connectivity: the physical layer of a data center runs on gear from a dozen manufacturers that do not talk to each other. ECMonitor sits across all of it, in one console, without ripping anything out. The same engine covers the fiber between halls and the DAS the campus needs for 5G connectivity on public or private wireless.

The problem

The blind spot lives between facilities and IT

Facilities runs power and cooling on one system; IT runs servers and network on another. A single fault can surface as three alarm storms in three tools. That was tolerable at 10 to 20 kW per rack. As AI workloads push densities toward 100 kW and beyond, the seam is where outages hide.

The approach

Not another DCIM, the neutral layer across the ones you have

Connectors speak each device's native protocol, SNMP, Modbus, BACnet, MQTT and OPC-UA, and normalize everything into one model. An on-site edge unit and secure tunnel unify what is already installed. No rip-and-replace, no vendor lock-in.

The AI layer

Hundreds of sensor alarms become one incident

Topology-aware grouping collapses related alerts, same feed, same loop, same root cause, into a single incident with an AI-drafted summary. Fewer unplanned outages, faster resolution.

What it watches, from the utility feed to the rack

  • Power chain. Feeds, UPS and battery health, PDUs, branch-circuit draw, at rack granularity.
  • Cooling and thermal. CRAC and CRAH units, chilled-water and liquid loops, rack- and row-level temperature.
  • Network and connectivity. Switches, links, backhaul, and the fiber and in-building wireless the facility relies on.
  • Environmental. Leak detection, airflow and pressure, smoke, cabinet access.

Fiber and DAS on the same campus

  • Fiber paths and optical transport between halls and to the campus edge
  • DAS head-ends, remotes and transport for public and private 5G
  • Public safety BDA and ERCES, battery and power
  • Build records from ECSite's testing and closeout carried into operations, so test results stay attached to the strand
Data center FAQ

What operators ask first

Is ECMonitor a replacement for our DCIM?

No. It is a vendor-neutral monitoring layer that sits across the DCIM, BMS and standalone systems you already run, unifying them into one view rather than replacing any of them.

What protocols does it speak in a data center?

SNMP, Modbus, BACnet, MQTT and OPC-UA. Power and cooling gear often speaks Modbus or BACnet, IT and network devices speak SNMP, and newer sensors use MQTT, all normalized into one model.

Can it monitor multi-vendor power and cooling together?

Yes. Gear from different manufacturers appears side by side in one console, and a fault plus its downstream effects surface as one correlated incident.

Does it work alongside our building management system?

Yes. ECMonitor sits across an existing BMS and DCIM rather than replacing them, closing the gap where facilities and IT systems normally do not share data.

Is data center monitoring available today?

Yes. The vendor-neutral engine is proven across public safety, DAS and fiber, and it is available for data center deployments today.

Do not see your domain

If it has devices that report telemetry, the engine can likely reach it. Tell us what you run.