// Product page — orbit (platform) and orbit(satellite) (edge device). // Sectioned as: hero → what orbit is → console screenshot → capabilities // detail → satellite edge device → CTA. const ProductHero = () => (

OPERATOR CONSOLE

{/* orbit wordmark, big */}

{"or"}{"\u0131t"}

A vendor-agnostic energy management platform.

orbit ingests data from any inverter, meter, sensor, or EMS, normalises it onto one schema, and turns it into money saved, expected yield delivered, and faults closed. EPCs deliver one solution. Operators get one console.

Book a demo → Capabilities

{/* what's in the console — a callout panel, no numbers */}

◇ WHAT'S IN THE CONSOLE

{k} {v}

); // ────────── The console — a big screenshot mock ────────── const ProductConsole = () => (

The cloud console.

The financial-first fleet view. Stats and groups top, a daily bot summary, savings and baseline tiles, and a fleet table where every row tells you what each site earned, what it should have earned, and whether it's tracking. Equipment from any vendor surfaces the same way.

{/* corner brackets */} {["tl", "tr", "bl", "br"].map((c) => (

))}

◇ ORBIT · FLEET-VIEW · LIVE PREVIEW

PLATFORM v.4.2

{[ ["FLEET VIEW", "Savings month-to-date, vs-baseline, blended tariff, wasted revenue"], ["SITE DETAIL", "Live curve with TOU bands; entity cards for Grid, PV, Weather, Environmental"], ["ALERT TRIAGE", "OEM alarms (pass-through) and Platform Signals (derived)"], ["WORKBENCH", "Lasso a window, draft a work order, compare days, run what-ifs"], ].map(([k, v], i) => (

◇ {k}

{v}

))}

); // ────────── Site-detail screenshot — proves the TOU overlay claim ────────── const ProductSiteDetail = () => (

One site,
read clearly.

Click into any site for live telemetry against time-of-use tariff bands, an energy-flow visualisation of solar / grid / load, and entity cards for Grid, PV, Weather, and Environmental. The operator sees what the plant is earning, what it should be earning, and where the gap is.

{["tl", "tr", "bl", "br"].map((c) => (

))}

◇ ORBIT · SITE DETAIL · LIVE

); // ────────── Capabilities — detailed, alternating row layout ────────── const PRODUCT_CAPS = [ { n: "01", title: "Money-first fleet view", body: "The Fleet page leads with savings month-to-date, a vs-baseline tracker, wasted revenue, and a fleet-weighted blended tariff. A daily bot summary tells the operator what the fleet has earned this month and what it's on track to close at.", }, { n: "02", title: "Time-of-use intelligence", body: "Peak, standard, and off-peak tariff bands are overlaid directly on every site's live power curve. The platform calibrates per-site, per-tariff, so the operator can read the day's TOU shape without leaving the console. Tariffs can be edited and re-applied historically.", }, { n: "03", title: "Multi-source cross-validation", body: "Where two OEMs read the same plant, orbit shows both side by side and quantifies the disagreement — a Huawei FusionSolar daily yield vs a Liveview meter, for example. The operator picks the authoritative source per metering point and keeps both for data-quality monitoring.", }, { n: "04", title: "Curtailment auto-investigation", body: "When the platform detects a curtailment event, it opens a pre-filled investigation work order — time window, site, assignee — with the surrounding telemetry attached. The OEM-alarm → field-engineer loop happens inside one platform, with no CMMS bridge to maintain.", }, { n: "05", title: "Performance against simulation", body: "Performance Ratio per IEC 61724-1, against HelioScope P50/P90 expected yield with panel-degradation curves auto-applied from the commissioning anniversary. Daily and intraday actual is shown against the curve; deviations are attributed by inverter and by weather variable.", }, { n: "06", title: "Platform Signals", body: "Alerts orbit derives that the OEMs don't raise — declining yield over consecutive days, agreed-demand breach with dead-band tolerance, PF-correction opportunity surfaced in currency-per-month. Each signal can route to email, Telegram, or in-app, with SLA-breach escalation built in.", }, ]; const ProductCapabilities = () => (

What the platform does.

{PRODUCT_CAPS.map((c, i) => (

{c.n}

{c.title}

{c.body}

))}

); // ────────── Where we're heading — agentic direction ────────── const AGENTIC = [ { tag: "A", title: "Curtailment forensics", body: "The agent watches the curtailment stream, correlates with weather, grid frequency, inverter alarms, and TOU bands, and writes the investigation report before the engineer opens the ticket.", }, { tag: "B", title: "Tariff optimiser", body: "Given a site's load shape and a tariff catalogue, the agent quantifies the saving from switching tariff structure — including PF-correction targets and demand-response opt-ins.", }, { tag: "C", title: "Yield-decay diagnostician", body: "When a yield-trend signal fires, the agent investigates: weather, soiling, MPPT fault, degraded string, comms gap, or tariff change masking real drop. Reports in plain language with a recommended action.", }, { tag: "D", title: "Asset-life forecaster", body: "Combines the asset registry — commissioning date, warranty expiry, OEM degradation curves — with actual performance history to predict the end-of-warranty value vs the replacement cost.", }, { tag: "E", title: "Conversational fleet", body: "An LLM front door over the fleet. Which sites underperformed P90 last week? How much would I save if Brickworks moved to a different tariff? Draft the monthly report for FreshBev.", }, ]; const ProductAgentic = () => (

WHERE WE'RE HEADING

The agentic
direction.

The platform already runs the data plane — telemetry in, signals out, work orders open and close. The next layer is agents that read the same data and act on it: writing the investigation report before the engineer opens the ticket, comparing tariffs against load shape, talking to the operator in plain language. Five directions, all in flight.

{AGENTIC.map((a, i) => (

{a.tag}

{a.title}

{a.body}

))}

◇ ORB-NEXT/02 Each agent lives behind the same console — invoked from the Workbench, from a Platform Signal, or from chat. They explain what they did and link to the underlying telemetry. Nothing happens without an audit trail.

); // ────────── orbit(satellite) — edge device ────────── const ProductSatellite = () => (

EDGE DEVICE {/* orbit(satellite) wordmark */}

{"or"}{"\u0131t"} ( satellite )

Site-level OEM capabilities. The other half of the platform.

orbit(satellite) is the site layer of the platform. It integrates with inverters, combiner boxes, weather stations, and the rest of the balance-of-plant equipment at the site — regardless of vendor — normalises everything onto one schema, and uplinks to the cloud console.

— {b}

{/* device diagram */}

); // A wireframe-style edge-device drawing — same family as EdgeDeviceDiagram // in orbit-brand.jsx but reshaped for a portrait-leaning frame here. const ProductSatelliteDiagram = () => ( ); const ProductPage = () => ( <>

); window.ProductPage = ProductPage;