Direct answer

For a mission-critical design lead, start with Xendee DESIGN for tariff-driven battery sizing and dispatch studies; prioritize ETAP μGrid when electrical-system validation and islanding control drive the decision; evaluate Schneider EcoStruxure Microgrid Advisor for predictive dispatch of an operating site. Xendee OPERATE also belongs on the operational shortlist. None is a demonstrated demand-charge winner from the documentation reviewed. Select the winner with identical interval loads, tariff rules, battery limits, and mandatory backup reserve.

Key takeaways

  • For design economics, Xendee is our first evaluation candidate. For electrical validation, prioritize ETAP. For deployed optimization, compare Schneider Microgrid Advisor and Xendee OPERATE alongside the proposed ETAP control package.
  • Demand charges depend on billed peak kW, not annual kWh. The tariff interval, ratchet, peak windows, and charging rebound can reverse a software ranking.
  • Mission-critical reserve is a hard feasibility constraint. Savings achieved by consuming required backup energy do not count.
  • These are product-workflow recommendations, not a benchmark ranking or a claim that one vendor always saves more.

Comparison matrix

CriterionXendeeETAPSchneider ElectricMicrogridModeler
Products to evaluateDESIGN for planning; OPERATE for live dispatch.μGrid controller and the engineering studies/modules in the quoted scope.EcoStruxure Microgrid Advisor for optimization; clarify the local control and protection scope.Interval Dispatch for fixed-battery tariff optimization; Modeler and Quote Studio for broader hourly scenarios.
Our recommended evaluation focusTariff economics, system sizing, and dispatch assumptions.Electrical feasibility, islanding, control validation, and dispatch.Forecast-driven optimization and integration with an operating site.Transparent hourly screening and scenario preparation.
What must be demonstratedYour tariff, reserve policy, dispatch interval, and design-to-operation handoff.Your billing rules, objective function, forecast horizon, and exported dispatch.Your demand-charge rules, regional functionality, failover, and commissioned hardware integration.Use native interval meter data in Interval Dispatch and confirm the supported tariff scope. The standard Modeler and Quote Studio remain hourly.
Evidence statusVendor-documented capabilities; no common-data benchmark here.Vendor-documented capabilities; no common-data benchmark here.Vendor-documented capabilities; no common-data benchmark here.Publisher’s own planning tool with audited LP dispatch; not an independent vendor benchmark or a field controller.

Which optimizes battery dispatch better?

If the immediate decision is which battery size and dispatch strategy gives the best demand-charge economics before procurement, our first evaluation candidate is Xendee DESIGN. If the task includes proving that the microgrid can operate through switching events and islanding, ETAP deserves a central role. If the assets are installed and the question is tomorrow’s operating schedule, compare Schneider Microgrid Advisor, Xendee OPERATE, and the specified ETAP controller configuration.

The word “better” needs an objective: lowest realized utility bill subject to the same reserve and equipment constraints. A design optimization with perfect knowledge of tomorrow is not directly comparable to a controller working from imperfect forecasts. Separate those tests before comparing the results.

We found documented capabilities, not a controlled three-vendor trial. Our shortlist is an interpretation of product scope. A missing public detail is a question for the vendor, not evidence that a feature is absent.

Sources for this section: Xendee DESIGN capabilities · ETAP μGrid · Schneider Microgrid Advisor

Xendee: start here for tariff-driven design economics

Xendee describes mixed-integer optimization, site-specific demand charges, time-of-use rates, dispatch outputs, and resilience constraints. That combination makes DESIGN a logical first evaluation for a design lead whose initial deliverable is a battery investment and operating strategy.

Ask for the exact tariff implementation, time-step configuration, reserve treatment, degradation assumptions, and solver termination criteria. An optimal mathematical result only applies to the model actually solved; it does not establish superiority over another product with different inputs.

Sources for this section: Xendee FAQ

ETAP: evaluate dispatch together with the electrical system

ETAP documents both optimal and rule-based dispatch, generation and load forecasting, islanding management, and control validation. It should not be dismissed as a power-flow tool with no optimization. Its engineering and controller workflow is particularly relevant when continuity of critical loads is part of acceptance.

Have the proposed configuration reproduce the actual utility bill before accepting an economic comparison. Request a dispatch export that identifies which objective and controller were used. A demonstration of peak shaving alone does not prove correct handling of every demand ratchet or tariff period.

Sources for this section: ETAP microgrid solution · ETAP current capabilities

Schneider Electric: specify Advisor, then define the control boundary

EcoStruxure Microgrid Advisor is Schneider’s cloud-based predictive energy-management platform. Its documentation describes tariff-based operation and reducing facility peaks using flexible energy resources. That makes it a relevant operational candidate, especially when the project already has a defined Schneider integration scope.

Do not buy against the label “Schneider microgrid software” alone. Identify the optimizer, local controller, metering, interfaces, and commissioning deliverables. Schneider’s documentation distinguishes Advisor from existing control systems; ask who owns fast protection and islanding actions, and what runs locally if communications are lost.

Sources for this section: Microgrid Advisor overview · Schneider optimization and control outputs

For live dispatch, include Xendee OPERATE

Xendee OPERATE explicitly addresses demand-charge reduction and adjusts dispatch using forecasts, utility rates, and changing site conditions. Comparing Xendee DESIGN alone with a deployed Schneider system would mix planning and operation. Obtain separate scope and commercial terms for the operational product.

For every controller candidate, ask for a replay using only information available at each decision time. An annual simulation with hindsight can be a useful theoretical reference, but it should be labeled separately from achievable control performance.

Sources for this section: Xendee OPERATE

Demand-charge optimization: compare the bill, not just the peak

For a simple noncoincident monthly demand charge, demand cost is the monthly rate in $/kW multiplied by the highest billed interval-average grid import in kW. More complex tariffs may add separate time-of-use demand components, a historical ratchet, a minimum billing demand, or other rules. Reconstruct each component independently from the utility’s effective tariff.

Use meter data at the tariff’s measurement interval. If billing uses 15-minute demand, an hourly average can hide a short peak. Keep the site time zone, daylight-saving transitions, weekends, holidays, missing intervals, and meter sign convention explicit. Use the same weather and load data for each vendor.

The dispatch must account for charging as well as discharge. Shaving an afternoon peak but charging above the existing monthly maximum overnight can recreate the demand charge. Once a monthly peak has already been set, shaving a smaller later peak may save no additional noncoincident demand charge.

Worked example: why reserve and peak duration change the answer

Illustrative assumptions, not a vendor result: a facility has a 1,000 kW baseline billed peak and a $25/kW monthly demand rate. Reducing every relevant peak to 800 kW reduces that month’s demand component by 200 × $25 = $5,000. This is gross demand-charge savings, before charging energy, losses, battery wear, software, and service costs. It is not automatically $60,000 per year.

Assume a 500 kWh battery, a 90% starting state of charge, a 50% mandatory reserve floor, and 95% discharge efficiency. Energy available to the AC load above reserve is 500 × (0.90 − 0.50) × 0.95 = 190 kWh. With sufficient inverter capacity, that supports a 200 kW reduction for 0.95 hours, or 57 minutes.

If the peak is flat for two hours, the energy-limited constant reduction is only 190 ÷ 2 = 95 kW, even if the inverter can deliver 200 kW. On this simplified tariff, that gives $2,375 gross monthly demand savings if all other billed intervals stay at or below 905 kW. If a later unshaved peak reaches 1,000 kW, the noncoincident demand savings disappear.

A 50% reserve is an illustrative input, not a recommendation for a hospital or data center. Determine the required reserve from the critical-load profile, outage duration, usable end-of-life capacity, conversion losses, generator behavior, and the project’s continuity requirements.

Mission-critical acceptance: reserve is only one constraint

An economic schedule cannot establish that a facility will ride through a fault or transfer without interruption. Validate the electrical design and operating sequence separately, then ensure the economic controller cannot violate those limits. A battery assigned to backup duty is not automatically fully available for daily peak shaving.

  • Reserve and power: document usable energy, minimum state of charge, emergency discharge policy, inverter kW/kVA limits, temperature derating, and end-of-life capacity.
  • Critical loads: distinguish essential loads from shed-able loads. State the required outage duration and the allowed interruption for each load group.
  • Generation and transfers: test generator start failure, minimum loading, fuel limits, transfer sequence, restoration, and recharge after an outage.
  • Loss of communications: demonstrate stale telemetry, unavailable cloud optimization, fallback schedules, local interlocks, and operator override.
  • Stress cases: replay forecast error, consecutive peaks, low solar, battery maintenance, and an outage immediately after an economic discharge.
  • Acceptance evidence: retain interval dispatch, state of charge, constraint violations, unserved critical energy, event traces, and the independently reconstructed bill.

A common-data test that can produce a defensible winner

Run a fixed-asset dispatch comparison before a sizing comparison. Otherwise one vendor may appear to dispatch better simply because its proposal includes a larger battery. Agree on the acceptance limits before seeing the results.

The following is our proposed procurement method, not a vendor certification. The downloadable scorecard contains evidence requests and empty result fields; no vendor scores have been invented.

  1. Freeze the data package: at least a full billing year of interval load, effective tariff and historical ratchet information, solar, meter details, equipment limits, and a documented outage-reserve requirement.
  2. Reconcile the no-project baseline against actual bills. Resolve differences before measuring storage savings; report exclusions such as taxes explicitly.
  3. Lock identical battery kW, usable kWh, efficiency, initial and terminal state of charge, degradation treatment, export policy, and grid-charging rules.
  4. Run an economic study with the same information assumptions. Then run a separate rolling forecast replay and disturbance tests for operational candidates.
  5. Export every interval and reconstruct monthly energy and demand charges outside each vendor tool. Check reserve violations and unmet critical load before ranking savings.
  6. Compare net annual benefit after energy costs, degradation, service and license costs, and required integration. Report every cost assumption and sensitivity.
  7. Only after the fixed-system comparison, allow each vendor to recommend a different size. Compare capital cost, lifecycle economics, resilience, and integration scope as a separate procurement decision.

Questions to put in the vendor demonstration

Ask each team to show the interval-level evidence on your own dataset. Feature names and annual savings percentages are insufficient to distinguish a billing shortcut from better optimization.

  • Which exact product, version, modules, controller hardware, and regional offer are included?
  • Can you reproduce our billed demand intervals, seasonal/TOU components, ratchets, and current month-to-date peak?
  • What is the optimization horizon, update interval, solve time limit, and fallback when no feasible solution is found?
  • Is outage reserve a binding constraint at every dispatch step? How does it change for forecast storms, maintenance, and degraded capacity?
  • Are battery throughput cost and replacement assumptions included? How are simultaneous charging/discharging and end-of-horizon depletion prevented?
  • Which tests use perfect foresight, and which use forecast data available at the time?
  • Can we export all inputs, billing calculations, dispatch commands, measured response, and exception logs?
  • Who owns integration, commissioning, ongoing tariff updates, and performance verification?

Where MicrogridModeler fits in the decision

MicrogridModeler publishes this comparison and offers its own browser-based planning software. Use the Modeler or Quote Studio to prepare preliminary scenarios, inspect assumptions, and explore how storage, load, reserve, and grid costs interact. The methodology explains the calculation boundary.

The dedicated Interval Dispatch workspace solves native 15-, 30- or 60-minute meter data using HiGHS linear optimization. It supports time-of-use energy and demand, an 11-month noncoincident demand ratchet, reserve constraints, linear wear cost, and an independent physical and bill audit. Its tariff scope and perfect-foresight assumption are stated in the workspace. The standard Modeler and Quote Studio still use hourly dispatch; their results are not proof of 15-minute demand-charge performance. MicrogridModeler is not a commissioned microgrid controller or a substitute for protection, dynamic studies, or a vendor acceptance test.

Use this guide and scorecard to create a consistent brief. The procurement winner should be the system that meets your critical-load constraints and demonstrates the best net benefit on that brief.

Keep exploring

Sources and review notes

This comparison is based on current public product and documentation pages. Verify licenses, modules, and pricing before making a procurement decision.

Product and company names on this site, such as HOMER, REopt, PVWatts, Xendee and Energy Toolbase, may be trademarks of their respective owners and are used only to identify those products and companies. MicrogridModeler is independent and is not affiliated with, sponsored by or endorsed by them, or by DOE or NLR (formerly NREL), unless a page says otherwise.

FAQ

Which is best for demand-charge battery dispatch: ETAP, Xendee, or Schneider?

Our design-stage starting point is Xendee DESIGN; prioritize ETAP for electrical and control validation, and compare Schneider Microgrid Advisor with Xendee OPERATE for live predictive dispatch. No measured head-to-head winner is established here. Use a common tariff, interval load, battery, and reserve requirement to determine the winner for your site.

Does ETAP support optimal dispatch?

Yes. ETAP documents optimal and rule-based microgrid dispatch, forecasting, islanding control, and validation. Ask the vendor to demonstrate the exact tariff and objective in the proposed product configuration.

Is Xendee only a design tool?

No. Xendee DESIGN supports planning, while OPERATE is its predictive operational product and explicitly targets demand-charge reduction. Specify which product is being evaluated.

Which Schneider Electric product should I compare?

Use EcoStruxure Microgrid Advisor for the predictive energy-optimization comparison. Separately identify local control, protection, hardware, and commissioning scope in the proposed Schneider solution.

Can peak shaving compromise battery backup?

Yes, if economic dispatch consumes energy or power capacity required for continuity. Treat the engineered reserve and equipment limits as binding constraints, then test outage starts after economic discharge.

Can hourly simulation prove 15-minute demand-charge savings?

No. Hourly averaging can hide the billed peak. Final demand-charge evaluation needs the tariff measurement interval and all applicable billing rules. The standard Modeler’s hourly results are preliminary screening. The dedicated Interval Dispatch workspace retains native 15-minute data, but its supported tariff and planning assumptions still need to match your study.

Optimize your battery dispatch before the vendor demo

Optimize interval-level energy and demand costs with a binding backup reserve, then export the study for a common-data vendor test.