Overview
A practical architecture for real event environments.
GreenSparks is built around a simple idea: a reading is useful, but a reading connected to a problem, symptom, achievement or goal is actionable. The architecture is designed to make that connection — reliably, across the provider mix and site conditions typical of live events.
The platform works in two flows. The first brings telemetry from field Devices into the platform, validates it, and builds the operational records and analytics foundation. The second turns that foundation into the views, Maps, messages, Reports, and recommendations for remediation your team and stakeholders actually use.
Agents collect telemetry from the field.
GreenSparks Agents collect telemetry from the equipment in every Zone — Generators, Batteries, PDUs, power Monitors, Loads, solar arrays, smart controllers, and other connected sources. Agents run in the cloud for Devices reachable over the internet, on-site where local network access is required, or a hybrid of both, so collection matches how each event is actually wired.
Every signal is validated on the way in, not assumed correct — that's what makes the record trustworthy, not just complete. Gaps, stale Devices, and collection issues are visible immediately, the same way Zone Health surfaces them later, so your team catches a data problem before it looks like a site problem.
A trusted foundation for every view.
Operational records and analytics datasets form the common layer across the whole platform. Every app view, Map, message, Report, and notification draws from the same source — so producers, operators, engineers, and partners all work from the same verified information.
Every participant sees exactly what they need to.
GreenSparks controls access at two levels. Roles determine what a user can do — managing Events, deploying Devices, running diagnostics. Group membership determines what they can see — which Events, which Devices, which Reports.
This matters in multi-party event environments where an equipment provider, an event producer, and a Venue team all operate within the same platform. Each organization's data stays within the boundaries set by their Groups and Roles. An operator can only work with the equipment their organization owns, at the Events their organization is responsible for.
A workspace built for your role.
The GreenSparks app gives authenticated users a role-aware view of live operations — Maps showing status across Zones and messages when something needs attention, and access to the event structure, teams, and permissions relevant to their role. What each person sees reflects their responsibility, not the full complexity of the system.
Reports: evidence your team can act on.
Reports turn the verified operational record into evidence your team and stakeholders can act on — scoped to individual Devices, Products, Categories, Zones, Events, or Venues, and exported in a wide variety of formats.
Structured exports carry that evidence into your existing tools — spreadsheets, planning documents, whatever your team already works in. Every exported figure keeps the same scope and qualification it had on the page, so evidence from one event becomes the starting point for improving the next.
Detect & Resolve: catching problems and guiding the fix.
The same operational record feeds a rules engine that watches for real problems as they emerge — a Battery discharging with no visible downstream Load, a power Monitor gone stale during an active event, a Load with no credible upstream source. Rather than surfacing a raw alert, each finding is linked to a ranked set of likely causes and paired with investigation guidance grounded in the actual data behind it, so operators can move straight to resolving the problem instead of first figuring out what it is.
Provider-flexible. Deployment-flexible.
GreenSparks works with the equipment and infrastructure you already have — not to replace it. It supports a growing range of Device types and vendors, connects available telemetry, and produces clear evidence your team can act on — regardless of how complex the event or how varied the hardware.