ArraySignal

Demo Portfolio · Synthetic Sample Data

Explore the full demo workspace

Browse existing fleet tools without signing in. This read-only workspace uses bundled fictional examples, never customer records. It does not connect providers, send notifications, run models, upload data, or create work orders.

The 2-site overview, incidents, and report use July 22–August 20, 2026 reference totals. Advanced feature panels are separate illustrative scenarios with their own periods and assumptions—not recalculations of that portfolio, validated accuracy, or promised savings.

Alert episodes, not sent notifications

Explore synthetic firing, pending, and inhibited episodes using the filters. Acknowledging, silencing, routing, and daily digest opt-in require authorized customer records, not these samples. No notification endpoint is connected and no background evaluation runs here.

Firing

2

Technically active

Pending

1

Waiting for persistence

Acknowledged

0

Still separate from resolution

Noise controlled

1

Visible, not notified

Delivery health

Not connected

No demo notifications are sent

Alert inbox

2 episodes · 2 require review

alert-v1
  • HIGH

    Inverter 4 persistent underperformance

    FIRING

    The same device condition persisted for 30 minutes and is estimated to be losing 42 kWh today.

    DEVICE UNDERPERFORMANCE · confidence 87% · last seen 8/30/2026, 2:00:00 PM

    Inspect evidenceUrgency: NOTIFY
    No action yet
  • HIGH

    Downstream device zero output

    FIRINGINHIBITED

    Stored and visible, but notification inhibited by the active parent grid event.

    DEVICE ZERO OUTPUT · confidence 91% · last seen 8/30/2026, 2:00:00 PM

    Inspect evidenceUrgency: NOTIFY
    No action yet

Grouping and inhibition

Parent grid, gateway, transformer, and curtailment conditions reduce duplicate child notifications without dropping evidence.

Delivery health

In-app, email, Slack, PagerDuty, and signed webhooks use idempotent intents, retry state, and dead-letter visibility.

Safe by default

Backfills never page by default. Acknowledgment and silencing do not resolve a technical condition.

Ready to use your own data? Your customer workspace preserves your existing session and applies your organization role and plan. Uploads, saved changes, verified routes, schedules, and connections require an authorized account.

Open your customer workspace