O&M Platform
Fleet health, alarms and service cases in one place, with Metis helping your team triage and hand off with context.
Product preview. Interfaces use offline demo data or illustrative workflows. Available functions depend on the device, firmware, configuration and project acceptance; these examples are not evidence of production operation or a savings guarantee.
WEB SCREENSHOT · P1
O&M Platform · Fleet overview
Triage that starts from evidence
Metis checks each layer, groups related signals and drafts the handoff. Engineers decide.
AUROORCH O&Mcase #1029 · sample data
> The customer says the APP stopped updating. What do we know?
⏺Metis · case_review (read-only)
⎿ Last data 3 h ago · 1 site · router changed yesterday
Site power and network
NetworkHomeowner confirms power is on.
Datalogger link
NetworkLast report 3 h ago, right after the router change.
Cloud ingestion
DataHealthy in this region.
Data processing
DataNo backlog.
APP display
DataShows the last good reading, marked stale.
✻⏺Drafting the handoff…Handoff ready for the installerView case ↗
Software and platform issues in scope are ours to fix. Firmware, third-party systems and the field go to the responsible party.
From first report to closed case
One named owner, and a record at every step
1 · Intake- Device identity, time, symptoms and impact are recorded.
2 · Triage- Priority, owner and the next update time are set.
3 · Diagnose- Data, network, versions, recent changes and past cases are checked.
4 · Resolve- The responsible party applies the approved fix and records the result.
5 · Retest- Function and data are verified, on site when needed.
6 · Close and learn- Open items stay tracked. Reusable fixes are reviewed into the knowledge base.
Reliability you can inspect
We hand over deployment checklists, test results, known limits and named owners
Deployment- Hosting region, provider, capacity and data-processing boundaries must be confirmed for the project; no production region is promised here.
Monitoring- API response, data freshness, job backlog, capacity and alert delivery are watched together.
Releases- Compatibility first, then a staged rollout with key metrics watched and a rollback plan ready.
Recovery- The delivery plan should define backup and restore tests. Actual recovery time and any data gaps require evidence from the target environment.