Overview
Solarsens documentation is organized by audience.
The Concept section explains the shared mental models behind the platform so readers can understand how the system fits together before they move into operational workflows or API integrations.
Why this section exists
Section titled “Why this section exists”The same solar monitoring platform serves different readers:
- O&M teams need to understand what the platform represents and how to interpret plant behavior
- Potential customers need a stable description of how the platform organizes assets, events, and workflows
- Developers need the same core model before they connect external systems or agents to our APIs
What you will find here
Section titled “What you will find here”- platform terminology and glossary
- system boundaries and architecture
- data flow across plants, assets, telemetry, alarms, and work orders
- permissions and shared roles
- concepts that are reused in Operations and Developers guides
Audience handoff
Section titled “Audience handoff”After reading the conceptual model:
- go to
Operationsfor day-to-day monitoring, alarms, performance, and work order workflows - go to
Developersfor authentication, API usage, and MCP-style integration patterns