ZENERGY 众壹能源
Start pilot

Scenarios

Choose the first AI operations pilot scenario

Select a verifiable starting scenario by team role, then expand across the 335+ scenario library.

Scenario selector

Start from the first pilot scenario that is easiest to accept.

The 335+ scenarios are not meant to launch all at once. Start with one daily workflow that has clear data boundaries and acceptance criteria.

01

Asset owner

Focused on yield, loss attribution, post-investment review, and management reporting.

Recommended start

Weekly operating review / Deep management report

ZenovaOS AI turns production, PR, device, and alarm data into conclusion-first reports.

Acceptance focus

Validate review efficiency and evidence completeness with one conclusion-first report.

02

O&M lead

Focused on alarm priority, device anomalies, field action, and closure efficiency.

Recommended start

Alarm storm governance / Inverter trend diagnosis

ZenovaOS AI groups alarms into P0/P1/P2 action priorities with plant and device context.

Acceptance focus

Validate daily handling efficiency with P0/P1/P2 priority and action lists.

03

Regional / group operator

Focused on cross-plant comparison, anomaly ranking, and unified metric definitions.

Recommended start

Multi-plant comparison

ZenovaOS AI compares plants by operating signal and produces ranked follow-up actions.

Acceptance focus

Validate portfolio management value with regional ranking and exception lists.

04

IT / data owner

Focused on account permissions, field gaps, history windows, and audit boundaries.

Recommended start

Transparent data gaps / Knowledge-to-asset linking

ZenovaOS AI explains verified SaaS data boundaries instead of fabricating charts.

Acceptance focus

Validate whether AI is controllable and auditable through data-boundary explanations and KB linking.

Scenario coverage

335 scenarios, 4 global principles, one coverage matrix.

The scenario library hardens high-frequency operating questions into agents with deterministic, auditable output, organized by domain and enabled scenario by scenario as the pilot grows.

335+
S-scenarios
4
Global principles
19
Domains covered

Plant information

60 scenarios

Example question · What is this plant's live power and equivalent hours today?

Device information

59 scenarios

Example question · Do the string currents on inverter #3 show dispersion?

Combined analysis

41 scenarios

Example question · Where did last week's generation losses come from?

Device management

29 scenarios

Example question · Which devices failed most often in the last 30 days?

Data analysis

26 scenarios

Example question · Compare the PR trend of these two plants.

Generation statistics

23 scenarios

Example question · How does this month's generation compare with last year?

Plant management

23 scenarios

Example question · How do plants rank on health across regions?

Alarm management

17 scenarios

Example question · Which alarms need attention first today?

Plus 57 scenarios across 11 more domains, including communications, reporting, robots, and billing.

Launch checklist

After choosing a scenario, you should know how acceptance starts.

The scenario page no longer repeats resource content. It helps you turn the first pilot scenario into real data boundaries, real owners, and real acceptance criteria.

01

Data boundary

Confirm account scope, target plants, device types, history windows, and available fields.

02

Business owner

Clarify who uses the result daily, who reviews reports, and who decides whether it enters operations.

03

Acceptance metric

Write success as observable outcomes such as report hours, alarm priority, or anomaly-location speed.

04

Review cadence

Review output quality, data gaps, and next scenario expansion weekly instead of relying on one demo.