OpsCon · monitoring, early warning, operations

The command center your duty officers actually open at 3am

OpsCon turns hazard feeds, asset registries and your own thresholds into one operating picture — with the alert, the instruction and the situation report attached to it.

Request a walkthrough → See it deployed

Rainfall · Sta. Cruz42 mm/h Assets online128 / 131 Red alerts06

The operating picture

One map, every exposure

Weather, flood, seismic, air quality and sea state feeds are overlaid on your own sites, vessels, crews and customers. Exposure is calculated per asset, not per region, so the alert names the thing that is actually at risk.

Feeds refresh on their own cadence; the picture is never more than a few minutes old.

Modules

From signal to instruction

The gap in most monitoring projects is not data. It is what happens in the ninety seconds after a threshold is crossed.

◉

Hazard feeds

PAGASA, PHIVOLCS, global model output and your own sensors, normalised into one schema with provenance kept.

☷

Asset registry

Sites, vessels, routes, crews and customers with attributes that matter for exposure: elevation, build type, criticality.

▲

Threshold engine

Your rules, not generic warnings. Different thresholds by asset class, season, tide state or time of day.

☉

Alerting & escalation

SMS, Viber, email and in-app, routed by duty roster, with an escalation ladder when nobody acknowledges.

▤

Command board

Shared status board for an active event: who is doing what, what is unresolved, what leadership has been told.

✎

Situation reports

The SitRep drafts itself from the event log and the map, on your template, ready for review and release.

Event · TY Basyang Red

1Threshold crossed · Sta. Cruz depot04:12

2Duty officer paged · R. Dela Cruz04:12

3Acknowledged · 94 seconds04:14

4Convoy held · 12 units rerouted04:21

5SitRep 01 released04:40

Ack time94swithin SLA

Assets held120 losses

Open tasks031 late

During an event

Everything gets a timestamp and an owner

The event log is the after-action review. Who was paged, when they acknowledged, what was decided and what it cost are all recorded as the event unfolds rather than reconstructed afterwards.

Read the Batangas deployment →

Alerts dispatched, last 30 days 24,918

At scale

Built for the bad week, not the demo

Alert dispatch runs on its own queue, independent of the dashboard. When three hazards overlap and half the province is watching, the messages still go out.

Deployments

Four common shapes

Most OpsCon programmes start as one of these and grow sideways from there.

Ports & logistics

Keep cargo moving safely

Berth, yard and convoy status against sea state and rainfall, with hold and release decisions logged.

Utilities & energy

Protect the network

Asset-level exposure, crew dispatch and restoration tracking through a typhoon and its aftermath.

Local government

Warn the public early

Barangay-level thresholds, mass notification and an evacuation picture the PDRRMO can brief from.

Agriculture & estates

Watch the growing season

Block-level heat, drought and rainfall watch with advisories pushed to farm managers.

< 4 minMedian time from feed update to dispatched alert

18Hazard and sensor feeds normalised

128kAssets under active monitoring

99.95%Alert-queue availability

Build with Komunidad

Stand up the operating picture before the next season.

Bring your asset registry and your thresholds. We will show you the command board running on them.

Request a walkthrough → Compare with Komplee