Edge intelligence / remote assurance

The remote site that knows what’s happening.

Power. Connect. Observe. Recover. Solatude 01 unifies energy, edge compute and resilient communications in one integrated remote-site platform.

01 Platform concept · current architecture + next-generation roadmap

4 ×managed PoE channels
2 TBnext-gen edge storage
2 pathsapplication + OOB cellular
Discover the system
01 The platform

Remote infrastructure should explain itself.

Most remote systems are assembled from separate power, network, camera and telemetry products. When one fails, the operator sees symptoms — not causes.

Solatude 01 brings those layers under one policy and one operating picture. It keeps working at the edge, uses the best available path to report home and preserves a separate route for recovery.

Less travelDiagnose before dispatch

See power, route and device state before a technician leaves.

Faster recoveryAct without the main link

Use the out-of-band path for controlled recovery workflows.

Better evidenceKnow what happened

Join telemetry, actions and media in a single incident timeline.

02 One assurance loop

Four jobs. One field platform.

Choose a layer to see how Solatude turns fragmented field hardware into a system that can observe, decide, act and report.

01 / 04

Know where every watt is going.

Solar, battery and load telemetry become one operating picture. Metered outputs can be prioritised, switched and recovered without a site visit.

  • Solar and battery telemetry
  • 4 × managed field outputs
  • 12 V / 24 V regulation options
03 Hardware architecture

Built as a site controller, not another appliance.

Compute, switching, power supervision and separate communications paths share one designed architecture — so the platform can see the dependencies that ordinary routers cannot.

01Power controlSolar regulation · metering · switched loads
02Edge computeLinux applications · local policy · storage
034 × GbE PoEManaged cameras, radios and field devices
04Dual cellular rolesApplication 5G · separate management path
05Last-gasp reserveReporting reserve · supported functions TBC

DESIGN TARGET

NXP i.MX 95 + 2 TB

More local intelligence, more retained evidence and more autonomy. The i.MX 95 family adds heterogeneous real-time compute, an NPU delivering up to 2 TOPS and hardware security foundations for advanced edge workloads.

CPU family
Up to 6 × Cortex-A55 + M7 / M33
Edge AI
Up to 2 TOPS eIQ Neutron NPU
Local archive
2 TB onboard solid-state storage
Security
EdgeLock + secure identity options

Concept render. Final enclosure, connector positions and electrical ratings remain subject to engineering release.

04 Inputs → decisions → outputs

One node sees the whole site.

Solatude correlates energy, devices and communications before it takes an action. That context is what separates remote assurance from a simple “online / offline” check.

INGEST

Inputs

  • PV + batteryVoltage, current, charge and energy state
  • 4 × Ethernet / PoELink, traffic, power draw and device state
  • WAN paths5G, Starlink, Wi-Fi and OOB health
  • Field signalsCameras, BLE, Sub-GHz and sensor events
EDGE POLICY
SOLATUDE 01
ObserveCorrelateDecideRecord
Continues locally when the cloud path is unavailable
ACT

Outputs

  • Managed powerPrioritise, isolate and restart field loads
  • Resilient routingSelect application path and preserve recovery
  • Local responseRecord, notify, illuminate and announce
  • Operational evidenceAlerts, audit trail, incident media and APIs
05 Planned cloud control plane

A fleet view with field-level truth.

The cloud does not replace the edge. It gives operators a secure way to understand it, manage desired state and coordinate action across every deployed site.

SOLATUDE / FLEET
Illustrative fleet view · concept data
NSW-042RIDGE COMPOUNDUpdated 18 seconds ago
Energy reserve74%
Application WAN5G
Out-of-bandReady
PoE channel 03Retrying
LATEST EVENT · 14:32:08

Camera 03 exceeded restart policy. Output held off and operator review requested.

Incident review concept

FASTEST TO OPERATE

One service from field node to fleet view.

The managed-cloud option is designed to provide the multi-tenant control plane, fleet health, device identity, alerting and audit pipeline. Customers would receive logically separated organisations, sites, roles and data.

Field node
Secure device channel
Solatude Cloud
Operations team
  • Managed updates
  • Fleet-wide health rules
  • Role-based tenants
  • API + webhook integration
06 Deployment scenarios

Different sites. The same operating problem.

Choose a scenario to see how the hardware, links and field actions can be assembled around the job rather than a fixed product bundle.

Site security

A construction compound after everyone leaves.

PoE cameras, local recording, 5G and optional Starlink remain visible as one system. A verified intrusion can trigger SolarSeer locally while the cloud assembles the event and escalation trail.

Reduce blind dispatches and preserve usable evidence even when the primary link is degraded.
SITE BUILD
01Up to 4 PoE connections — budget dependent
025G + optional Starlink
03Local edge archive
04SolarSeer deterrence
ASSURANCE FLOW
1Detect
2Verify at edge
3Warn / deter
4Escalate with evidence
07 SolarSeer companion

SPEAKER · RGB ALERT · MULTI-BAND RADIO

Give the remote site a voice.

SolarSeer extends Solatude from observation into local communication. Its design combines a programmable RGB strobe-style visual alert, digital audio, BLE, Sub-GHz radio and motion sensing in a field companion.

Make the edge response visible and audible.

Use the 24 individually addressable RGB LEDs and digital audio path for graduated, site-specific responses — from an amber pre-warning to a spoken instruction or high-priority alarm pattern.

1Camera or sensor event
2Edge validation
3RGB + audio response
4Cloud incident timeline
Visual
24 × individually addressable RGB LEDs
Audio
I²S Class-D amplifier + speaker path
Radio
CC1352P7 · BLE 5.2 capable · Sub-GHz design variants
RF path
20 dBm design path · 433 / 915 MHz variants
Motion
LIS2DW12 3-axis accelerometer
LPWA / GNSS
Optional Quectel modem footprint; populated variant TBC
Board rails
3.8 V / 1 A · 3.3 V / 1 A · 1.8 V / 0.3 A from 5 V

Concept render. The design supports configurable visual and audio patterns; no life-safety, emergency-warning, candela or acoustic compliance is claimed.

08 Illustrative energy planner

Size from the load, not the wish.

Adjust the assumptions to see the relationship between continuous load, usable battery energy and solar recovery. This corrects a common remote-power mistake: nominal battery capacity is not the same as delivered autonomy.

MODEL OUTPUT

Battery-only autonomy44 hours1.8 days with no solar contribution
Daily energy1.20 kWh
PV with 30% sizing margin490 W
Battery for five days8.2 kWh
Effective delivered energy2.21 kWh
Assumptions

92% battery-to-load efficiency, 80% net solar yield and 30% PV sizing margin. This does not model a defined recharge deadline. Cable losses, temperature derating, ageing and shading require site engineering.

MATH CHECK

At 50 W continuous, a 3 kWh battery is not a five-day system. With an 80% usable window and 92% conversion efficiency, it delivers about 44 hours. Five battery-only days need approximately 8.2 kWh nominal before environmental margin.

09 Preliminary specification matrix

Known, targeted and still to be released.

This concept separates confirmed architecture from roadmap targets and configuration-dependent ratings. It is intentionally more useful than a specification sheet filled with invented numbers.

Verified architecture Current verified / next targeted Roadmap / target Configuration dependent / TBC

Scroll horizontally to compare current and next-generation specifications →

Preliminary Solatude 01 current-platform and next-generation specification comparison
SystemSpecificationCurrent platformNext generation / optionStatus
ComputeApplication processorNXP i.MX 8M Mini — up to 4 × Cortex-A53 + Cortex-M4NXP i.MX 95 — up to 6 × Cortex-A55 + Cortex-M7 / M33Current / target
ComputeAI accelerationWorkload-dependent software accelerationUp to 2 TOPS eIQ Neutron NPUTarget
ComputeLocal storageConfiguration dependent2 TB onboard solid-state storageTarget
NetworkEthernet / PoE4 × Gigabit Ethernet with managed PoE4 × Gigabit Ethernet with managed PoECurrent / target
NetworkApplication cellularQuectel RM520N; 5G Sub-6, 3GPP Release 16, SA / NSARM520N-class 5G or release configurationConfig / TBC
NetworkOut-of-band cellularSeparate management cellular pathSeparate low-power management pathCurrent / target
NetworkWi-FiIntel module; bands / generation set by buildModule option set by buildConfig / TBC
PowerSolar inputSolar-input architecture; regulation topology, voltage and current ratings TBCSite-configured solar input; electrical release TBCConfig / TBC
PowerField outputs4 × metered, switchable outputs; 12 V / 24 V regulator options4 × managed outputs; final rail ratings TBCConfig / TBC
PowerRegulated DC rails12 V / 24 V architecture; current and transient limits TBCSite-load-specific regulator configurationConfig / TBC
PowerPoE power budgetPSE class, per-port and aggregate budget TBCConfigured to camera / radio load planConfig / TBC
PowerLast-gasp reserve18650-backed last-gasp reporting reserve; supported functions and runtime TBCDedicated reserve; supported functions and runtime TBCConfig / TBC
WANStarlink Mini integrationSupported in appropriately sized DC / routing configurationIntegrated high-bandwidth WAN optionConfig / TBC
SecurityDevice identityTPM2 / secure-element architecture optionsi.MX 95 EdgeLock + secure identity optionsTarget
SoftwareDevice managementPlanned: health telemetry, desired / reported state and allow-listed commandsAdds expanded edge AI and orchestrationTarget
SoftwareCloud patternsPlanned managed multi-tenant, dedicated-tenant and hybrid choicesSame deployment choicesTarget
STARLINK MINI REFERENCE

Starlink publishes 25–40 W average consumption and a 12–48 V DC, 60 W input rating. Solatude integration therefore requires a correctly sized DC rail and energy budget; it should not be inferred from a generic PoE port.

POE RELEASE DATA

The four managed channels are part of the architecture. IEEE class, per-port limit and aggregate PSE budget remain engineering-release items and are not fabricated here.

ENVIRONMENTAL RELEASE DATA

Enclosure IP rating, operating temperature, dimensions, certifications, PV limits, regulator current and battery chemistry must be added when production variants are frozen.

10 What the platform enables next

Build the field layer once. Add intelligence over time.

INITIAL SOFTWARE

See and recover

Planned: unified health, metered outputs, resilient routes, local recording, alerts and controlled remote commands.

NEXT

Understand the event

Edge AI classification, incident packages, predictive battery and link-health models, fleet policy and automated response.

FUTURE

Coordinate the site

Cross-device reasoning, adaptive energy budgets, local natural-language operations, multi-node radio meshes and autonomous service workflows.

Start with the site profile

What needs to stay working when nobody is there?

Define the loads, autonomy, communications and response policy. Solatude can then be configured around the real operating problem.

Model site energy