Product 03 · Energy & Compute Infrastructure

RoboStreet TCDC

Fleet energy and distributed compute infrastructure. Vehicles create transport value while driving — and become dispatchable energy and compute assets while parked. Depots evolve from charging sites into high-value infrastructure nodes.

Request a site evaluation → See how it works
Animated Diagram Phase 2 · the depot as a dual-resource node Solar over the yard, trucks holding their minimum departure SOC, a stationary BESS and a metered micro AI data centre — parked vehicles turn elastic while the fixed base stays stable. Departures, safety and battery life always come first.
Product Positioning

Solve charging first — then run the energy-compute network

TCDC is a modular infrastructure platform that unifies grid, solar, stationary storage, chargers, vehicle batteries, on-board AI, and depot micro data centers under one control plane.

DimensionPhase 1 · Fleet Energy & ChargingPhase 2 · Energy & Compute Operations
Near-term goalCharge on time, on demand, at low costParked vehicles become dispatchable dual-resource nodes
Core assetsGrid / solar, stationary BESS, PCS, chargers, EMSVehicle batteries, on-board AI, bidirectional charging, BESS, micro data center, cloud
Customer resultsHigh-power charging, peak shaving, weak-grid resilience, solar synergyEnergy services, edge inference, data processing, fleet optimization, distributed compute value
Business formEquipment & integration, Charging-as-a-Service, EMS softwareStorage / grid services, AI compute, software subscription, autonomous-fleet services
Operations first· Site-specific design· Modular expansion· Safety isolation· Closed data loop
Phase 1

Fleet power & charging management

Stationary storage buffers charging peaks; TCDC EMS turns the fleet plan into an executable power plan. The goal is not "more chargers" — it is making sure vehicles that must depart get their energy first, inside limited grid capacity and time windows.

Animated Diagram Figure 1 · Phase 1 Energy Closed Loop
TCDC EMS Shifts · SOC · tariffs · demand cap · PV forecast · priority Grid / Solar Existing interconnection Optional renewables BESS + PCS Peak buffering · backup Microgrid support HP Charging Dynamic power allocation Managed queues EV / Robotic Fleet Departure windows Target SOC guaranteed forecast · schedule · optimize · execute · review Closed loop: telemetry, SOC, meter & cost data feed the next plan

Figure 1 | Phase 1 energy closed loop: storage buffers power; TCDC EMS handles forecasting, scheduling, constraints, and closed-loop control. Capacity and topology are decided by site survey and utility interconnection studies.

🔋

Storage + Charging

No solar space; capacity and peak problems solved fast. Grid + BESS + high-power charging + EMS: peak shaving, power buffering, departure assurance.

☀️

Solar + Storage + Charging

Roofs, canopies, or land with good solar. PV + BESS + charging + EMS: green self-consumption, long-term energy cost, low-carbon operations.

🏝

Microgrid / Weak Grid

Remote corridors, ports, mines, temporary depots. Sources + BESS + microgrid control + backup: resilience, off-grid capability, continuity.

KPI groupCore metricsVerified against
Fleet operationsOn-time departure rate, target-SOC achievement, charging successSchedules, charge records, departure events
Energy costSite peak demand, peak-to-valley shifting, cost per kWh chargedBaseline utility bills and metering
System performanceBESS / charger availability, alarm recovery, dispatch responseEMS logs, telemetry, work orders
Asset healthCycle depth, temperature, SOH trendsBMS / vehicle data and life models
Green energyPV self-consumption, renewable share, curtailmentSegmented PV / storage / charging metering
Phase 2

Vehicles become energy & compute nodes

A commercial vehicle works ≈8 hours and parks ≈16 hours a day. Phase 2 turns parked time into infrastructure time — dispatching only the elastic capacity left inside departure-SOC, battery-life, thermal, warranty, and safety boundaries.

Animated Diagram Figure 2 · Phase 2 Dual-Resource Architecture
Cloud Training · cross-site analytics · governance TCDC Energy–Compute Orchestrator Fixed, non-negotiable priority ordering MOBILE NODES · Elastic Vehicle batteries V2B / V2G / V2V optional · SOC floor On-board AI Edge inference · preprocessing · health FIXED BASE · Stable Stationary BESS Stable supply · peak shave · backup Micro AI Data Center Metered GPU · network · cooling · SLA Grid / Site Power Interconnection · demand response energy compute

Figure 2 | Phase 2 dual-resource architecture: vehicles are elastic nodes; stationary BESS and the micro data center are stable nodes; TCDC orchestrates. Safety-critical driving domains stay isolated from general compute; workloads degrade or abort automatically on faults, thermal excursions, or dispatch pre-emption.

1 · Departures & missions→ 2 · People & equipment safety→ 3 · Compliance & cybersecurity→ 4 · Battery life & thermal→ 5 · Energy cost→ 6 · Grid revenue→ 7 · Compute SLA

A non-negotiable ordering — energy and compute dispatch never compromises departures, safety, battery life, OEM warranty, or interconnection terms.

Reference Pilot

The 250 kW demonstration hub

One measurable single-site pilot validating three value pools at once: energy, fleet operations, and compute.

0 kW
Continuous AI load (reference)
0 MWh/day
Energy at continuous operation
0–0 MWh
Recommended stationary storage
0–0
Participating vehicles
⚡

Energy value

Does TCDC cut peaks and bills without hurting departures? Peak reduction, cost per kWh, backup duration, dispatchable capacity.

🚛

Operations value

Does unified dispatch improve vehicles, charging, and batteries? On-time departures, charge success, recovery, SOH / cycle depth.

🖥

Compute value

Do local GPUs and vehicle edge tasks yield stable, meterable value? GPU utilization, task success, value per kWh, latency.

Planning math: 50–60 vehicles × 600 kWh × 15–25 % ≈ 4.5–9.0 MWh theoretical elastic energy — before deducting disconnected vehicles, SOC floors, conversion efficiency, power limits, reserves, and life derating. Not a capacity commitment. Reference parameters from the Robostreet Distributed AI Compute Network simplified business plan. RoboStreet participates in the NVIDIA DRIVE AGX SDK Developer Program; TCDC can interface with DRIVE OS, DriveWorks, CUDA, and TensorRT pipelines.

Commercial Path

Milestone-gated rollout, value at every step

MilestoneMain workGate to next stage
A · Site diagnosisLoad, fleet duty cycles, tariffs, interconnection, solar, reliability analysisBaseline, capacity plan, and business case established
B · Phase 1 pilotDeploy BESS + charging + TCDC EMS; build the vehicle-energy data loopDeparture, cost, and availability KPIs met
C · Fleet optimizationAdd route energy, SOH, predictive maintenance, cross-shift schedulingData quality, APIs, security, and ops stable
D · Dual-resource trialsSmall-scale V2B / V2G, vehicle edge tasks, 250 kW-class micro data centerOEM / interconnection / safety approvals; three value pools proven
E · Networked operationsConnect multiple depots; aggregate energy capacity and AI workloadsUnified settlement, orchestration, SLAs, cross-site operations
🏗

Equipment & Integration

Storage, charging, distribution, solar / microgrid, and software designed and delivered as one system.

🔁

CaaS / EaaS + Software

Settled by capacity, energy delivered, service fees, or shared savings — plus per-site / per-vehicle subscriptions.

📊

Energy & Compute Revenue

Demand response, peak management, reserves — and metered micro-data-center AI compute for fleets.

Deploy energy now. Orchestrate energy + compute next.

Pick a demonstration depot → import load and fleet data → get your capacity and business case.

Request a TCDC site evaluation → See Street AI orchestration