MRP-30

Mobile resilience for incident-command continuity.

Towable solar, LiFePO4 storage, communications, and a weatherproof enclosure for incident-command and dispatch continuity.

MRP-30 A mobile resilience architecture programs can specify with Sunwave — towable solar, storage, communications, and enclosure, sourced with EnoTech.
Illustrative MRP-30 architecture connecting deployable solar, battery storage, communications, and a towable enclosure
MRP-30 architecture: deployable solar, battery storage, communications, and a towable enclosure for incident-command continuity.

Reference envelope

Starting targets for program conversations — load, runtime, and site constraints refine the package with EnoTech.

Storage

~30 kWh LiFePO4 class

Buffer sized with the buyer for silent runtime and surge.

Solar

~4–6 kW deployable array

Generation layer for recharge and daytime sustainment.

Communications

Starlink-class + LTE backup

Backhaul options provisioned into the enclosure path.

Form factor

Lockable weatherproof trailer

Towable enclosure for a light-truck class platform.

Power path

Generation → buffer → distribution

Catalog strata stay separable so programs can mix families.

Sourcing

With EnoTech

OEM and distributor paths discovered as part of the program work.

Product boundaries

Sunwave is the hardware line card and sourcing partner. Adjacent software stays separately owned.

  • Sunwave: architecture, hardware families, and OEM/distributor path discovery with the buyer.
  • VITO: optional edge software for telemetry and local operations when separately deployed.
  • Keel / OIDF: optional commissioning runtime and evidence format; not implied by this hardware brief.
  • Sentinel / CEL: optional hazard context and language layers; neither is an actuator in this architecture.

Next step: a customer-shaped package with load, runtime, and site constraints — then EnoTech maps families and pursues OEM and distributor paths with you.

Bring one real site or materials request and we scope the package together.

Start a sourcing conversation →