Start here / 01 Commercial landscape, radar and battlecard

Competitive landscape · the proof and the matrix

Measured whole-site behavior is the next proof to publish

Rivals have documents. So does EKU. The rival documents read hold no measured report of a whole mixed-brand site with the cloud link down.

What does your site do on its own when the link drops, and can you show it?

Public documentation read 23 to 30 September 2026

9dimensions compared, each cell Confirmed at the rival's documentation or stated in EKU's own documents
Public documentation read 23 to 30 Sep 2026
4numbers EKU would publish: response, duration, repeatability, link loss
Criteria named by data-center buyers, 16 Sep 2026
0rivals on this radar that publish those four numbers for a whole site
Observation about what is published, not about capability
8 weeksfrom picking the site to the published page
Working plan; owners by role
What you are seeingThe rivals have brought their driving licence: documentation of what their controllers do. The documents read include no dashcam video of the whole car braking, holding the lane and reacting to an emergency. That video is the proof, and it costs eight weeks of an engineer's attention, not a product change.

The matrix: Maximus ecosystem against four rivals on nine dimensions

Read the colors before the words. A Confirmed cell on a rival is their own documentation. A cell marked Stated by EKU comes from EKU's own technical documents; it enters public copy when engineering confirms the wording.

Three layers of control: the contest moved from the engine to the whole site

Cloud layer: the fleet seen from anywhereMonitoring, analytics, reports. Where most rivals added "any manufacturer" this year.Sophia CloudGenerac LinkDSEWebNetmtu GoCat VisionLinkSite layer: who decides for the whole siteDispatch, load sharing across brands, behavior when the cloud link drops.MaximusComAp ICCC + InteliNeo 5500Generac ARCCat ECSmtu EnergetIQGenset layer: one controller per engineStart, stop, protect and parallel one machine. The specialists' home ground.ComApDeep SeaDEIFWoodwardBaslerthe contest is here
Kanbina Lumina reading of public product documentation, 23 to 30 Sep 2026. Product names are placed by what each vendor documents; placement is an inference, not a vendor statement. Sophia works on site and in the cloud.

Read the colors first: the rivals' columns are documented; the EKU column turns green as engineering confirms each line

DimensionMaximus ecosystem (Maximus + Sophia + GeneSys)ComAp ICCC + InteliNeo 5500Generac ARCDEIF AGC-4 Mk IICaterpillar ECS 300/400
Who owns the site-control logicStated by EKUConfirmedConfirmedConfirmedConfirmed
Third-party genset controllers supportedStated by EKUConfirmedObserved: no public proof foundObserved: no public proof foundConfirmed
Load and VAr sharing across brands on one siteStated by EKUConfirmedObserved: no public proof foundObserved: no public proof foundObserved: no public proof found
Switchgear sequencingConfirmedConfirmedObserved: no public proof foundConfirmedObserved: no public proof found
Behavior when the cloud link dropsStated by EKUObserved: no public proof foundObserved: no public proof foundObserved: no public proof foundObserved: no public proof found
Black start and islandingStated by EKUConfirmedObserved: no public proof foundConfirmedConfirmed
Batteries, solar and load coordinationConfirmedConfirmedConfirmedConfirmedConfirmed
CommissioningStated by EKUConfirmedObserved: no public proof foundObserved: no public proof foundObserved: no public proof found
Quantified outcomes publishedObserved: no public proof foundConfirmedObserved: no public proof foundConfirmedObserved: no public proof found
ConfirmedStated by EKUNeeds ValidationWorking HypothesisObserved: no public proof found
One cell per dimension and company, colored by its claim label. Confirmed on a rival means their own public documentation says it. Stated by EKU means EKU's own technical documents say it and it is not public yet. "Observed: no public proof found" means nothing was found in the documents read, 23 to 30 Sep 2026; it is not a statement about capability. Hover a cell for its text; the full wording is in the table below.
The full wording of every cell (45 cells)
DimensionMaximus ecosystem (Maximus + Sophia + GeneSys)ComAp ICCC + InteliNeo 5500Generac ARCDEIF AGC-4 Mk IICaterpillar ECS 300/400
Who owns the site-control logicMaximus, a site controller above the genset controllers; fast loops stay on site and the cloud supervises Stated by EKUThe ComAp controller group; third-party gensets observed over Modbus ConfirmedARC, local microgrid controller ConfirmedDEIF controller group ConfirmedECS site controller with one genset controls group per site Confirmed
Third-party genset controllers supportedCaterpillar EMCP, ComAp InteliGen and InteliSys, DEIF AGC, Deep Sea and Woodward easYgen are named in EKU's comparison document; models and count for engineering to confirm Stated by EKUDSE8610 MKII, DSE8620 MKII, DEIF AGC 150 for load sharing; InteliNeo 5500 "recognise and observe" over Modbus, no brands or count published ConfirmedNo third-party controller brand is named in the documentation read; 65+ verified energy resourcesNo third-party controller is named in the documentation read; up to 992 DEIF-controlled gensetsComAp, Deep Sea, DEIF and Woodward as compatible genset controls, one group per site Confirmed
Load and VAr sharing across brands on one siteMulti-unit synchronization, load sharing and reactive power control listed as functions; no published measurement Stated by EKUDocumented: up to 32 controllers over CAN, dead-bus closing ConfirmedNot published Not publishedDocumented within DEIF controllers; sharing across brands is not in the documentation readDocumented within one controls group per site; sharing across groups is not in the documentation read
Switchgear sequencingGeneSys integrated MV/LV switchgear with supervisory control (Confirmed as product; sequences not published) ConfirmedVia InteliGen/InteliNeo paralleling; sequences in manuals ConfirmedNot published for third-party switchgear Not publishedAGC-4 Mk II breaker control ConfirmedNot published in detail Not published
Behavior when the cloud link dropsRedundant on-site controllers; the site runs on its own if the connection is lost; protection stays in the relays. Design, not yet measured in public Stated by EKUControllers are local by design; no whole-site measurement publishedLocal controller by design; no measurement publishedLocal by design; no measurement publishedLocal site controller; no measurement published
Black start and islandingControlled restart of several units with gradual load pickup; planned and unplanned islanding; about 1 ms sampling and under 50 ms response as design figures Stated by EKUDead-bus closing documented ConfirmedMicrogrid islanding is the product's purpose; no measured case publishedDocumented in product manuals ConfirmedDocumented for Cat assets Confirmed
Batteries, solar and load coordinationMaximus covers gensets, BESS, PV, fuel cells, switchgear (Confirmed as product scope) ConfirmedInteliNeo 530 BESS controller; Advanced Reporting for hybrid sites ConfirmedARC coordinates generators, storage and solar ConfirmediE 250 and AGC-4 Mk II hybrid control ConfirmedUp to 32 assets including BESS and solar Confirmed
CommissioningEKU-led: definition, hardware-in-the-loop testing with pass and fail criteria, commissioning, support; duration not published Stated by EKUEmulation tool for office validation (Confirmed, 5 May 2026) ConfirmedDealer-led; not publishedUtility software; not published in detailDealer-led; not published
Quantified outcomes publishedNone public. Three reference projects are described in words in EKU's platform presentation; the field case is under leadership correction NoneOilfield case: 16 gensets, 6 MW ConfirmedNone found NoneHouston construction hybrid case ConfirmedNone found for ECS None

Sources: ComAp Inter-Controller CAN Convertor and InteliNeo 5500 documentation (read 23 Sep 2026); Generac ARC product page; DEIF AGC-4 Mk II datasheet; Caterpillar ECS 300/400 data sheets (Oct 2025) and VisionLink page (read 24 Sep 2026); EKU Control Box datasheet DRM-203, official product pages, EKU's Maximus platform presentation and two EKU comparison documents received 1 Oct 2026. Vendor documentation is the vendor's own claim. Absence of public proof is not proof of incapacity.

For engineering: how the EKU column turns green

The input: engineering reads each statement in EKU's own documents and confirms the wording. What it unlocks: the EKU column moves to Confirmed, and the battlecard can quote it.

EKU's own documents already say what Maximus does without the cloud

Leadership pointed to the Maximus fact sheets. They state the design. Observed, 23 to 30 September: The rival documents read hold no measured report of a whole mixed-brand site with the cloud link down. That says nothing about what a vendor can do.

What the documents stateWhereHow to use it in public
The site keeps running without the cloud. Redundant controllers on site; the site runs on its own if the connection is lost; fast control loops stay on site and the cloud only supervises.Maximus platform presentation; comparison documentStated by design. The measured record on a real site is the proof plan below.
Speed. About 1 ms sampling and under 50 ms response on critical events.Maximus platform presentation; comparison documentDesign figure. Quote it as "designed for", never as a measured site result.
Protection stays apart. Dedicated protection relays work on their own, whatever the state of the site controller.Comparison documentStated. Engineering confirms the wording.
Genset controllers it works with. Caterpillar EMCP, ComAp InteliGen and InteliSys, DEIF AGC, Deep Sea and Woodward easYgen.Comparison documentThis fills the blank in the matrix. Engineering confirms models and count before any page names them.
More than generators. Batteries from six makers and solar inverters from eleven are listed, plus gas processing and fuel systems.Comparison documentStated. Name makers only as technical compatibility, never as partners.
Protocols. Modbus TCP and RTU, CAN J1939, DNP3, SunSpec, OPC UA, Ethernet/IP.Maximus platform presentation; comparison documentStated. One protocol is listed as supported in one document and as roadmap in the other: see below.
Black start and islanding. Controlled restart of several units with gradual load pickup; planned and unplanned islanding.Maximus platform presentationStated. A good second measurement after the cloud-link test.
Three reference projects. A two-site microgrid with batteries; a battery plant for a data center; a fleet of mobile generator units.Maximus platform presentationOutcomes are described in words, without figures. Each one is a candidate for the case template.

Sources: EKU's Maximus platform presentation and two EKU comparison documents exported 23 June 2026, received 1 October 2026. A vendor's document is the vendor's own statement. Label for every line: stated by EKU, not yet published, not yet measured on a site.

For engineering: where the documents disagree, and one comparison to fix before a customer sees it
PointWhat the documents sayWhat to do
How many gensets one Station View runs"100+" in the presentation, "up to 60+" in the comparison document.Engineering picks one figure. Use it everywhere.
IEC 61850Listed among the supported protocols in the presentation, and as "roadmap" in the comparison document.Say "roadmap" until engineering confirms. A buyer in a utility will ask.
Retired wordsThe documents use the compatibility shorthand that leadership retired in July, on almost every page.Replace with "mixed-brand" and "cross-manufacturer integration" before the next customer sees them.
How rivals are describedOne rival's site controller is described as working only with its own engines. That maker's data sheets of October 2025 list four other makers' genset controls as compatible. Another rival is described as having no battery control and no site-level layer; it documents a battery controller and load sharing with other makers' controllers.Do not hand the comparison to a customer as it stands. A rival's engineer can take it apart in one meeting. Update the rival columns from the matrix on this page first.

The proof protocol: six steps, one owner each

1

Pick the site

Engineering lead, with the sales lead

Week 1 of October

2

Define the four numbers

Engineering lead

Week 1

3

Agree the test

Engineering lead and site owner

Week 2

4

Run and log

Site engineer

Weeks 3 to 6

5

Report

Engineering lead

Week 7

6

Publish

Marketing lead

Week 8

M

What the test looks like. The cloud link is cut on purpose. The gensets keep running, protection and load sharing stay on site, and the log records what happened and when.

Each step in full: what, who and when (6 rows)
StepWhatWhoWhen
1 · Pick the siteOne mixed-brand site already running Maximus: at least two genset controller brands, one battery or solar asset if available, GeneSys or third-party switchgear. Name the asset mix in the report.Engineering lead, with the sales leadWeek 1 of October
2 · Define the four numbersResponse: seconds from a dispatch command to stable output. Duration: hours the site holds the commanded level. Repeatability: the same sequence and timing across at least five logged events. Link loss: the sequence the site runs when the cloud link is cut, who owns protection and load sharing, and what the operator sees.Engineering leadWeek 1
3 · Agree the testA written one-page test plan: events to trigger, instruments, who records, safety approval by the site owner.Engineering lead and site ownerWeek 2
4 · Run and logRun each event at least five times across two days. Sophia logs are the record; screenshots are the backup.Site engineerWeeks 3 to 6
5 · ReportOne page: site description, asset mix, the four numbers with method and date, limits, confirmed by the engineering lead.Engineering leadWeek 7
6 · PublishA page on ekupd.com in buyer language, the FAQ block, and a one-line claim for the battlecard: measured on one site, dated.Marketing leadWeek 8

When each number counts as proven

NumberAccepted when
ResponseA median and a worst case over the logged events, in seconds, with the command type stated.
DurationHours sustained at the commanded level, with the fuel and battery limits stated.
RepeatabilityAt least five events with the same sequence; the spread of timings reported.
Link lossThe full sequence after the cut, the time to local control, and confirmation that protection and load sharing stayed on site.
Honesty rulesAnonymous site is fine; numberless is not. No comparison with a rival is made on the page; the rival matrix stays internal until the engineering lead confirms it.

What the published page says, and what it never says

Closing

Strategic conclusion

The competitive question is no longer who can run mixed brands; it is who can show, with numbers, what the whole site does on its own.

Commercial implication

One measured report replaces every exclusivity claim EKU ever made and gives sales a question to put to every vendor.

Recommended use

Engineering lead owns steps 1 to 5; marketing lead owns step 6. Review the matrix at each quarterly re-sweep.

Validation status. Rival cells Confirmed at their public documentation, 23 to 30 Sep 2026. EKU cells Stated by EKU, from its own documents received 1 Oct 2026, until engineering confirms the wording. The protocol is a working plan, dated 30 Sep 2026.

Working foundation for executive review. Not approved external copy. Prepared for EKU Power Drives, 30 September 2026, by KanbinaLUMINA