THE RUNNING PRODUCT

Screens from the demo

Not mockups. This is the running instance, loaded with a synthetic fleet. Every figure on these screens is generated, and the banner across the top of each one says so.

One navigation carries all of it. Solar, wind, storage, distributed generation, thermal and data centers sit in the same left rail, against the same asset model, with the same alarm strip across the top. You license the classes you operate and the rest stays out of the way.

The RenewOps left navigation in two columns. Solar carries PV production forecast, performance ratio, DC health, asset health, tracker health and soiling. Wind carries turbine state and power curve. Storage carries BESS, the BESS ROCC console and CapWatch. Distributed Generation carries DG fleet surveillance. Data Center carries fleet, operations, alarms, events, electrical, grid interface, UPS, generators, cooling, thermal, contingencies, capacity and shift log. — **The left rail***synthetic fleet*

Thermal fleet status for a synthetic peaker plant: 366 MW online, 392 MW available ambient-corrected, nothing forced out and nothing derated, two of two units committed. Each combustion turbine shows its target, capability and headroom. Below it, the next twenty-four hours of commitment changes with start types. Unit state is derived from the event record and cannot be set by hand. — **Thermal fleet status and commitment***synthetic plants*

A live electrical one-line for a synthetic hyperscale data center: two utility feeders into two medium-voltage switchgear buses with a normally open tie, automatic transfer switches, eight UPS modules with load and state of charge, twelve standby generators shown de-energized, and eight data halls with their load and path count. Colour shows the source actually feeding each conductor. — **Data center electrical, live one-line***demonstration facility*

Screens from the running demo, loaded with a synthetic fleet. No client data appears anywhere on this site. Access to the demo is issued rather than open.

THE PLATFORM

More assets. More data. More responsibility.

Operations are becoming more complex faster than the tooling around them, and the fleet that used to be one technology is now several: solar, wind, storage, thermal plant, and the data centers they feed. Most operators run monitoring in one system, performance reporting in another, and compliance evidence in a folder somebody maintains by hand. RenewOps puts all three on one record, so the number in a board deck and the number in an audit response came from the same place.

01See what's happeningFleet dashboard, geographic fleet map, and site detail down to the single-line: contracted MW, sites online, active alarms, inverters in fault, state of charge, and operator response time in one view.
02Understand whyAlarm trends by site, by asset and by type. Curtailment tracking. Recurrence patterns that turn a hunch about an underperforming string into an evidenced maintenance decision.
03Know what to do next, and preserve the evidenceActionable alarm tables with site, asset, code and message. Grid compliance monitoring with live band status and sample counts. Monthly O&M reporting exported as a finished document.

MODULES

What's in it

Suites are made of modules. A customer licenses suites; the modules are what they get. Core is always on. Everything below it sits inside a suite or licenses on its own, and licensing the parent suite includes its modules at no extra charge.

Asset classesWhat you operate. Your first class is included, whichever it is. Each class after it adds a share of Core, and adds to deployment.

Solar PVIncluded as your first class.

Irradiance On Two BasesModelled and measured are both carried, never collapsed into one number. A pyranometer reading outside its validity window is reported as a suspect sensor, not averaged into the fleet.
Plausibility CeilingA sample above the site's own nameplate by a defined margin is counted as implausible and held out of the clean total, rather than quietly inflating a month.
Why this card is shortSolar is the class the platform was built against, so its capability is not concentrated here. The asset model is Core; specific yield, performance ratio, DC health, soiling and tracker analysis are Performance Engineering. Neither is restated on this card to make it look fuller.

WindIncluded as your first class. After the first, +25% of Core.

Turbine State AccountingEvery machine in the register resolves to one of eight mutually exclusive states: running, idle, curtailed, fault, maintenance, iced, comms-lost, unaccounted.
The Unaccounted ResidualA turbine nobody can reach is counted as unreachable, not as running. The buckets cannot be made to balance by leaving a machine out of them.
Availability Over Assessable MachinesComputed only across machines whose state is knowable, with the excluded count carried beside it rather than folded into the number.
POI Against Turbine SumPlant output at the point of interconnection against the sum of what the turbines themselves report. The gap stays visible instead of being reconciled away.
Power Curve & Density CorrectionMeasured output against the published curve, corrected for air density. Interpolated within the curve and never extrapolated past it; where density is unknown the comparison is withheld rather than flattered.
Where this class stopsTurbine operations and performance. Wind ride-through, model validation and voltage-control obligations are not carried by this class, and nothing here should be read as evidence for them.

BESSIncluded as your first class. After the first, +25% of Core.

State Of Charge & HealthDispatch headroom, round-trip efficiency, and position against the guarantee.
Absent Renders AbsentA four-state feed model. A value that did not arrive is shown as not arrived. Never as zero, which is a number an operator would act on.
Control AuthorityWhether the ROCC can actually use the controller, tracked separately from whether the controller is running.
Safety Is Never Bulk-ConfirmedSafety points are confirmed one at a time by a named person. There is no select-all on a thermal or fire signal.
Thresholds Carry Their SourceEvery limit names where it came from. A limit without a source is not loaded.

Distributed GenerationIncluded as your first class. After the first, +25% of Core.

A Different Operating ModelNot utility-scale monitoring with a filter on it. Five questions in order: online, communicating, producing, producing as expected, anything actionable.
Exception Management, Not TelemetryEquipment-level detail across hundreds of sites buries an operator. The fleet resolves to exception buckets that are mutually exclusive and sum to the fleet count.
Classified On Rating, Not Opinion20 MVA and below is distributed, rated off gross MVA. A site with no rating resolves to unclassified and is listed for a human. It is never defaulted into DG, because "we did not know" must not render as "we decided."
Curtailment Is Not UnderperformanceCurtailed sites are held out of the actionable worklist rather than counted as problems.
No Expected Basis, No NumberA site with nothing to compare against reports not-assessable. It never reports zero, and it never reports a hundred.

Thermal GenerationIncluded as your first class. After the first, +25% of Core.

Plants On The Core ScreensGas turbines, combined-cycle blocks, reciprocating engines and steam units sit on the same Dashboard, Fleet Map and Situational Awareness as the rest of the fleet, with output against nameplate, unit state at a glance and a trip flagged where the operator is already looking.
One Alarm BoardThermal alarms land on the shared alarm board, sequence of events and shift turnover. A trip at a peaker is worked from the same list as an inverter fault.
The Capability Is A SuiteUnit state, one-lines, the system view, starts, trips, fuel, emissions, cold-weather readiness and GADS are the Traditional Generation suite, priced like every other suite.
Where this class stopsRead-only. The screen reads the plant and issues no commands. Dispatch, governor and excitation control stay where they are.

Data Center OperationsIts own Core, banded on total critical IT load across the portfolio · from $180k–225k / yr · deployment per facility

Four Answers On One ScreenWhat happened, what is affected, what happens if the next piece of equipment fails, and what to do next, with the procedure that applies.
Redundancy Against The Design BasisN+1, N+2 and 2N are counted against the load the design was built for, not the load that happens to be present, and the equipment that took a system below design is named.
The Next Failure, Before It HappensEvery single loss is evaluated against current conditions, and an operator can test any combination plus the loss after it. Exposure today's conditions created is kept apart from exposure the design already carries.
One Incident, Not A Hundred AlarmsA utility loss and everything that follows from it (transfers, UPS on battery, generator starts, chiller restarts) resolve to one incident with a critical-power timeline.
PUE On Energy, Not On SamplesPeriod PUE is facility energy over IT energy. A change is attributed to the components that caused it, and the part the weather explains is separated from the part it does not.
Where this class stopsRead-only. There is no control path to any equipment. Connecting your BMS, EPMS or SCADA is integration work scoped at deployment, and the demonstration facility is simulated and labelled as such on every screen.

Core, suites and modulesWhat the platform does, applied to whichever classes you run.

CoreBase. Always on, every tier, including the whole control-room layer.

Connect & IngestLive collector with lossless store-and-forward on the SCADA gateway you already run.
Provenance & Data-TruthDefect battery, two-clock board, refusal ledger. Every value carries where it came from.
Asset ModelSite, inverter, combiner, meter and BESS, modelled once and inherited by every site.
Link & Feed HealthFreshness and stagnation detection. A feed that stopped moving is not a feed that is fine.
Alarm Board & JournalConformed to the alarm journal your gateway already emits, so it maps one-to-one.
Classification & PrioritizationCritical, High, Medium and Log, set by site type rather than by whoever configured the tag.
Deduplication & ShelvingAlarms grouped and quietened so the list is worth reading.
Acknowledge & Time-to-AcknowledgeTime from alarm to acknowledgement, measured rather than assumed.
Alarm Table & TrendsSite, asset, code and message. The actionable list, plus volume over time ranked by site and by type.
Unified Operational AlertsOne feed, rather than four consoles and a phone.
EscalationWho gets called, when, and whether they were.
Operator KPIsThe numbers the control room is actually run on.
DashboardContracted MW, sites online, active alarms, inverters in fault, state of charge, operator response time.
Fleet MapEvery site placed geographically with live status.
Situational AwarenessSite health scorecard, fleet status summary, daily site digest.
WeatherConditions at site alongside what the site is doing. Inbound weather ingest is Core.
Operator LogThe operating record and shift turnover. What the last shift handed over, written down and retrievable.

Performance Engineering+from $61k–76k / yr, scaling with fleet size

Specific Yield & Capacity FactorBoth-basis: solar against total, so the comparison survives a hybrid site.
Performance RatioThe industry measure, computed against the model rather than against last month.
Loss AttributionShortfall against expected, broken out by cause instead of reported as one number.
DC HealthCombiner-level current deviation and insulation-resistance (Riso) trending, to the string.
SoilingSoiling loss with coverage, so a partial read is not presented as a fleet read.
Tracker HealthTrackers that have stopped tracking, before the yield number tells you.
CurtailmentCurtailed energy computed and tracked separately from underperformance.
Underperformance RankingWhich site, which asset, in what order.
CapWatchDelivered capacity against nameplate and against what the site is capable of right now.
On Data CentersChiller, pump, tower and UPS efficiency against limits, battery replacement windows from the internal-resistance trend, generator start reliability, asset health with its factors shown, evidence-backed anomalies, and baselines and forecasts carried as ranges.

Contract Assurance+from $61k–76k / yr, scaling with fleet size

Availability ReconciliationTechnical against contractual. The two are not the same number and the difference is money.
Guarantee TrackingPosition against the guarantee, during the period rather than after it.
Liquidated-Damages ExposureWhat the shortfall costs, quantified while there is still time to act.
Peer ReferencingThe site against comparable sites, not against its own optimism.

Compliance+from $61k–76k / yr, scaling with fleet size

VAR-002 Voltage-Schedule VerificationVoltage schedule verified against the record, continuously.
Grid ComplianceLive band status: alarm band, live kV, delta from setpoint, in-band status, time in band over 24 hours, and live-versus-total sample counts.
PRC EvidenceRide-through evidence captured as it happens, not reconstructed at audit.
GADS PositionWhere you stand before the submittal window, not after it.
Evidence RetentionThe measurements behind each obligation held in the shape they were recorded, with provenance intact.
Site AccessWho was on site, when, and under what authorisation. Tracked as a compliance record, not a visitor book.
Corrective Action ProgramFindings to closure: root cause, owners, due dates, evidence, and linkage to the RSAW or self-report.

Reporting & Exports+from $61k–76k / yr, scaling with fleet size

Owner Monthly ReportThe KPI spine, per plant, customised and exported as a finished document.
GADS CSV, draftThe file built from your own operating record, in the format, without the spreadsheet weekend. You or your compliance advisor submit it.
Custom ReportsThe report your owner asks for, not the report the vendor ships.
DowntimeOutage accounting that stands up to a counterparty.
ExportYour data out, in a form other systems accept.

Lifecycle Intelligence+from $61k–76k / yr, scaling with fleet size

Asset Record & TimelineEach asset from commissioning onward: identity, status, events, maintenance, configuration and work on one timeline.
Configuration HistoryEvery setting change kept, never overwritten. Who changed it, why, whether engineering approved it and whether it was verified as left. Read the configuration as it stood at any moment.
Commissioning BaselineThe as-left state locked at commissioning, and every difference from it today. Open commissioning deficiencies stay visible until they are closed.
Evidence ChainAlarms, telemetry, assessments and correspondence attached to the event they belong to, each item hashed by the database and never edited. A correction is a new record that names the one it revises.
Warranty, LTSA & Service ObligationsThe clauses an event triggers, the notice clock measured from the first qualifying occurrence, and the evidence each one asks for that is not yet on record.
Fleet SimilarityThe same signature on other units of the same model, on the same or different firmware, and how those were resolved. Similarity is reported as similarity, not as cause.
Investigations & WorkReviews, RCAs, warranty notices and configuration validations tracked to closure. Only a person closes or approves.
Lifecycle Investigation by NORAAsk about the asset or event in front of you: deadlines, what changed, why it keeps happening, where else. NORA answers from the record, every line sourced and labelled for data quality, recommends a review and never takes an action or claims a root cause.
On Data CentersUPS modules and their batteries carry the same record: configuration history against the commissioning baseline, the evidence chain, warranty and service clocks, and similarity across facilities.

Traditional Generation+from $61k–76k / yr, scaling with fleet size · with the Thermal Generation class

Unit State Is Derived, Not TypedState comes from the event record and the commitment schedule, and it cannot be set by hand. That is what keeps the GADS record honest, because a unit cannot be marked available by somebody who wants the month to read better.
Capability Corrected For AmbientAvailable MW is corrected for ambient temperature against each unit’s own curve, so the figure on the screen is what the machine can make today rather than what the nameplate says.
Plant One-LineEach plant’s switchyard, step-up transformers and generator breakers, drawn live from the plant record. A trip shows as a tripped breaker with the lockout relay flagged, and power flow follows the breakers.
System ViewEvery plant on one picture: what each delivers into its zone, spinning and quick-start reserve, the units standing closest to their minimum operating temperature, and the weather across the fleet.
Starts, Trips And RunbacksStart success and failure counted across the record, the next twenty-four hours of commitment, and every trip and runback kept with what preceded it rather than logged as an outcome on its own.
Fuel, Heat Rate And EmissionsFuel burn and heat rate against design, degradation and anomalies from the operating record, with emissions monitored on that same record instead of assembled afterwards.
Cold-Weather ReadinessFreeze protection and the cold-weather record carried before the event rather than reconstructed after one, kept against each unit’s own EOP-012-3 records.
Unit Reliability (GADS)Equivalent availability and forced outage rates, including EFORd, computed from the event record by the methods in the GADS data reporting instructions, pooled across the fleet.
Model, Test And Protection RecordsCapability testing, model validation and ride-through records for each unit, with the next due date carried rather than remembered.
Control ReadinessEvery breaker and unit shows the checks an operator command would have to pass, run against the live record. The command itself is refused: the suite is monitoring only, and a control path is a separate decision.

Safety & Switching+$50k–63k / yr, on its own.

Switching OrdersBuilt and tracked in the same system as the operating record. Written by hand on their own; drafted for you when NORA is licensed.
Lockout / Tagout & ClearancePermit-to-work management, held against the asset model.
Safety Observations & Incident LogRecorded where the work happens rather than in a separate binder.
BESS SafetyThermal, fire and auxiliary monitoring.

Integrations & Work Orders+$75k–94k / yr, on its own.

Work-Order Write-BackDispatch a ticket from a detected issue and close the loop on its status, without retyping it into a second system.
Recurring-Failure LinkageThe third time the same asset throws the same fault, the work order knows it.
Notification RoutingSMS, email, and escalation into whatever your team already watches.
Outbound API & WebhooksPush to any downstream system.
Market ConnectorsISO price and forecast feeds.

NORA+$50k–63k / yr, on its own.

Network Operations Reliability AssistantOperator response procedures at the console, and switching orders drafted from your one-lines instead of typed from scratch.
Op GuidesYour procedures ingested and served where the operator already is.

PlatformIncluded.

Role-Based AccessRoster, six roles, pillar gating.
Alarm-History Audit TrailWhat the alarm did, and who did what about it.
Multi-Tenant CapabilityPrepared, for an operator running more than one book.
AssistantAsk the fleet a question instead of building a query.
Knowledge BaseProcedures and reference where the work happens. Free and self-serve.

Training & EnablementOnboarding included with deployment.

Onboarding TrainingIncluded with deployment. Not sold back to you afterwards.
Operator & Admin CertificationRole-based, per cohort. $9k–12k per cohort.
Custom WorkshopsScoped to what your team actually runs.

Where RenewOps stops. The platform produces the record and the evidence: the measurement, the band status, the ride-through capture, the position going into a window. It does not prepare NERC submittals, write RSAW narratives or build your compliance calendar. That is regulatory work performed by people who sign their name to it, and it is what Energy Compliance, Inc. does. RenewOps gives the filing its evidence. The firm writes the filing.

UNDERNEATH ALL OF IT

Every fleet monitor works fine until the link comes back

None of the above is worth anything if the underlying series has holes in it. Steady state is easy. The failure that costs you is the recovery, when a gateway holding seventy-two hours of history reconnects and flushes it in whatever order the queue drains, interleaved with live data, sometimes re-sent on retry. We force that condition on purpose, before cutover, and we don't certify a path that fails it.

Held samples land at the time slot named by their own source timestamp, not by arrival order. The duplicate batch collapses. The endpoint reports inserted_new: 0. Gap filled, order monotonic, nothing doubled.

PASS CRITERIA

Four gates, all or nothing

COMPLETEEvery ground-truth record present after replay. No gaps, no quiet losses in the flush.
NO DUPESStored set equals truth set exactly. The deliberately duplicated batch returns zero new rows. Idempotency proved in the reply, not asserted in a datasheet.
ORDEREDA time-ordered read returns monotonic timestamps regardless of what order the buffer drained in.
STATEEvery alarm lifecycle reconstructs to the correct final state. Row-completeness alone isn't sufficient for alarms. The semantics have to survive too.

Any failure means not certified. A green run against the live production instance is the cutover gate. Not a validated reference, not a demo, the actual endpoint for that site.

GUARANTEES

Three properties, enforced by the schema

Correctness comes from a primary key on identity, not from application logic that has to remember to be careful.

Out-of-order safets from the source, never arrival

A sample or event is stored at the time slot named by its own source timestamp. A seventy-two-hour flush replays history in whatever order the queue drains; the record reassembles correctly regardless.

Idempotent / replay-safeON CONFLICT(identity) DO UPDATE

Re-sending the same identity key never creates a duplicate. Buffers re-flush on reconnect and retries double-send. The series stays stable rather than doubling.

Late-correction safelast-write-wins on existing key

A corrected value or attribute for an existing key updates in place, so a re-flush is harmless and a late fix from the field lands where it belongs.

Time-series

Metric, source timestamp, value, quality, keyed on (site_id, metric, ts).

Alarms

A lifecycle, not a point. One alarm instance raises Active, optional Acknowledge, and Clear. Each its own transition, keyed on (site_id, eventid, eventtype, eventtime). Field set conformed to the alarm journal your gateway already emits, so it maps one-to-one.

ARCHITECTURE

The buffer is a function, not another box

Store-and-forward lives on the SCADA gateway you already run. Replacing a legacy aggregator is a destination swap, not a rebuild of your buffering tier, and not another appliance in the rack.

ORIGINSite SCADA

SCADA gateway: store-and-forward, MQTT

HOPSite firewall

Outbound only

HOPNOC firewall

Your perimeter, your rules

DESTINATIONRenewOps

Fleet record, keyed on identity

Additive and reversible first

The ingest endpoint stands up and gets proved with no gateway changes and no hardware. It can be deleted with zero blast radius. Nothing about your existing path changes until a shadow test passes on the live instance.

Operator alarms stay where they belong

Audible alarms, the alarm journal, and the compliance record live on your SCADA, at the operator. A cloud monitor on the far side of a buffer cannot be your real-time alarm surface, and we won't pretend otherwise.

History survives the migration

Moving off a legacy source that already fed the platform? The identity key lets old and new overlap during cutover. An overlapping record upserts instead of duplicating.

Clone by parameter

One proven pattern parameterized by site. Standardize the tag and alarm model once in your gateway's type definitions and every site inherits it. Scale the fleet without re-deriving the path each time.

BEFORE YOU BUY

The Five Questions Read

One week. We look at the data path you're running today and tell you whether it survives a link outage, before you license anything, and without touching your network.

What we work from

Your gateway configuration: store-and-forward settings, buffer sizing, transmission setup
Your tag and alarm model, and whether it's standardized across sites or per-site bespoke
A tag list and an alarm journal export
A slice of historian data covering a period you already know had a link interruption
Whatever aggregator or historian tier sits between the gateway and your reporting today

What it does not require

No firewall change, not at the site, not at the NOC
No change to a production SCADA gateway
No connection into your network, and no vendor access to a control system
No hardware, and nothing installed

The replay test is deterministic and runs against a reference instance parameterized by your site. That's how we can do it in a week, because it was designed not to need your perimeter.

What you get back

A verdict on whether your current path is out-of-order safe, replay-safe, and late-correction safe, the three properties that decide whether your record survives a flush
The specific failure modes we found, named and located, not a score
What it would take to close each one, whether or not that involves us

$17,000–20,000 Creditable in full toward any license within 90 days.

It answers whether you need us before you buy us. If the answer is that your path is already sound, that's the finding, and you'll have it in writing.

REQUEST A WALKTHROUGH

Bring us the site that keeps losing data.

We start with the path you're running today: what's buffering, what the flush does on reconnect, and whether anyone has ever tested it under an outage.

A working session, not a slide deck
No firewall change and no access to your network to get started
We tell you what we find either way, including if your path is already sound

EMAIL[email protected] PHONE763.438.4427 OFFICEBloomington, Minnesota

Name *

Company *

Email *

Phone

Fleet size

SCADA platform

Technology

Solar Wind BESS Data center

What's driving this?

Anything else *

Keep this general. It's a first contact, not a secure channel. No site-specific configuration or operational detail until we've got an NDA in place.

COMPANION PRODUCT

Operations produces the evidence. Compliance has to prove it.

RenewOps runs the fleet. WattOps Compliance runs the program behind it: NERC, FERC, the Regional Entities, the RTOs and ISOs, and the PUCT. Registration scope, evidence, RSAWs and findings, each one traced from the claim, to the requirement, to the exact span of the document it rests on.

The two share one rule. Neither will make up a fact. License either on its own, or run both on one record so the number in a board deck and the number in an audit response cannot disagree.

See WattOps Compliance

The Operating System for Renewables, Thermal Generation and Data Centers.