← Back to Knowledge

Talk to the EPC firms that build grid-scale storage plants and you will often hear the same line: “there’s hardly anything to do for O&M.” Once the plant is built and connected, the thinking goes, an aggregator schedules charge and discharge, a chief electrical engineer runs the statutory inspections, and the manufacturer fixes whatever breaks — those three keep the plant running. But these three leave one thing decisively uncovered. When something goes wrong on the DC side (EMS, PCS, BESS, BMS), who triages it first and starts the recovery? The aggregator faces the market on the assumption that the plant is running; it is not the party that maintains the equipment. The chief engineer is the guardian of the AC switchgear. The OEM looks only as far as its own equipment. Between the three, the job of first response on the DC side is left empty.

This column does not call that emptiness a “gap in the rules.” Dig in and the facts run the other way: the law clearly assigns the duty of DC-side safety oversight to the chief engineer. What is empty is not the law but who, in the field, carries out that statutory duty — a gap we will call the mismatch between responsibility and execution. That is arguably more troublesome than “the rules have a hole.” On paper the hole is filled, yet in reality it is not — so no one picks it up as their own problem.

We first pin down the structure of this gap in law, then map the whole picture with a responsibility matrix of equipment × party. Next we lay out its economic consequence — that an outage is not merely lost opportunity but bites twice, as institutional penalties in the balancing market and the capacity market. Finally we draw on international practice to see how mature markets solved this gap, and turn it into decision axes that owners, EPCs and O&M providers can use in contract design. If the sister column, “Contract design splits ¥200 million over 20 years,” was a map of the five contract layers that underpin the economic operation of a plant after COD, this one is its counterpart: a map of the responsibilities that underpin the plant’s physical operation after COD.

Scope of this column
Target
Grid-scale storageHV / EHV
Central thesis
The responsibility–
execution gap on the DC side
Responsibility matrix
5equip. × 6 parties
Weight of unplanned outage
×5count
Rules as of
2026.05
Primary readers
Owners · EPC · O&M

01 — The myth that “three parties keep it running”

The operation of a storage plant is often described in terms of three parties: the aggregator, the chief electrical engineer and the OEM. But each carries a defined scope — and a defined non-scope. Stack them together and you still do not get whole-plant health.

The aggregator uses the owner’s batteries to schedule charge and discharge in the power markets and earn revenue. Its role is the economic operation of the cells; equipment maintenance is simply not in its remit. It faces the market on the assumption that the equipment is running — not the party that drives to site when it stops.

What about the chief electrical engineer? Here many stakeholders assume that “if there’s a chief engineer, the equipment is taken care of,” and that mistakes the scope. Plants at high voltage and above must, under the Electricity Business Act, appoint a chief engineer, and there is no doubt they are electrical professionals. They handle the cubicle (AC switchgear): operating it, investigating faults, shutting down and restarting. But few chief engineers can restore the EMS or PCS beneath it on their own. They are the guardians of the AC switchgear, and as a rule they do not take on, in practice, the role of guardian of the DC-side equipment. Even where the work is outsourced to a safety corporation such as an electrical-safety association, it is common to see the line drawn so the cubicle is covered while the DC side is not entered.

Then does the OEM fix it? A storage plant is built from the equipment of several manufacturers — EMS, PCS, BESS — and each handles the upkeep of its own equipment (periodic inspection, call-out, remediation). But no manufacturer keeps enough field staff to dispatch a technician instantly to every one of the storage plants now multiplying across the country. Query each maker before you have established which equipment the fault lies in, and time simply drains away in disputes over where responsibility sits. There is also a constraint that is easy to miss: a manufacturer’s warranty, as a rule, lapses if anyone uncertified touches the equipment — even a licensed person. So the DC side is less “cannot be touched” than “touch it and you void something else (the warranty)” — fenced off, in effect, by three things at once: skill, OEM certification and warranty scope. This is not a legal limit but, as we will see, a constraint that design can move.

🔧 FIELD NOTE — A grid-scale storage O&M operator (interview, May 2026)

The aggregator schedules charge and discharge assuming the equipment is up. The chief engineer goes as far as the cubicle. The maker goes as far as its own equipment. In the end, in a lot of deals, the party that moves first when something happens on the DC side isn’t written anywhere in the contract.

The biggest gap is comms. Even when the EMS shows “comms fault,” whether it was the router that dropped or the carrier’s fiber side changes the instruction to the field. If the as-builts — which router, what settings — were never handed over, no one can fix it the moment it fails.

And the one left holding the bag is usually the dealer or EPC that did the construction. That’s why you need to design how it’s handed over.

If the three do not add up to a whole, then a party that manages the entire plant — O&M — has to step to the front. Whether to move the chief engineer, move the OEM, use insurance, or whether the cause is comms: O&M takes on that judgment and the first response, becoming the single window for the owner. That is the starting point of this column.

02 — Responsibility is statutory; execution is unassigned

This is the core of the column. The field’s line — “the DC side is outside the chief engineer’s scope” — is not because the law says so. In law, the DC side sits squarely within the scope of safety oversight.

Article 43(1) of the Electricity Business Act requires a person who installs electrical equipment for business to appoint a chief engineer in order to provide safety oversight of the works, maintenance and operation of that equipment (and Article 42 requires safety management rules to be drawn up and filed). The question is whether that “electrical equipment for business” includes the DC side — and the legal definition of a storage plant answers it. Under the Electricity Technical Standards Ordinance, a storage plant is a facility that stores, in storage devices and other electrical equipment installed on site, power transmitted from outside the site, and re-transmits it outside at the same voltage and frequency. The inverter (PCS) that drives the storage device, and the protective equipment, are part of that electrical equipment. Nowhere is there language excluding the DC side from the scope of oversight.

The qualification tiers, too, are cut by voltage, not by type of equipment. Under Article 56 of the Enforcement Regulation, a Class-3 chief electrical engineer may supervise electrical equipment below 50,000 volts — but generating stations and storage plants of 5,000 kW or more are carved out of that. Class 2 covers below 170,000 volts; Class 1, everything. There is simply no structure that splits supervisory authority by AC versus DC, or switchgear versus battery. METI’s materials on electrical-safety personnel likewise state the Class-3 range as “below 50,000 V (excluding generating stations or storage plants of 5,000 kW or more),” so it is confirmed in government documents that a storage plant of 5,000 kW or more falls outside the Class-3 range. Note, too, that grid storage was positioned as a “power generation business” by the 2022 amendment to the Electricity Business Act (in force April 2023), for discharge above 10,000 kW.

But here a further point of precision is needed. What the chief engineer owes is the oversight of safety — confirming conformity with technical standards and reporting to the installer if non-conformity is likely — not remediating the PCS or BESS themselves. The duty of oversight extends, by law, to the whole plant including the DC side; but no provision names who actually fixes the equipment beneath it (remediation, first response). Pushed to its conclusion, the only places the law names an executing party are “safety oversight of the AC switchgear” and “cyber and technical-standard conformity at grid connection” — and DC-side remediation spills outside both. So the gap takes the form “oversight is statutory; remediation is unassigned.”

Let us put this discrepancy on a single sheet, dividing what the law assigns from what the field executes.

Responsibility under the law Execution in the field Electricity Business Act, Art. 43(1) Safety oversight of works, maintenance & operation Chief Electrical Engineer (safety supervisor) Statutory scope of oversight = the whole plant AC switchgear AC side / cubicle DC-side equipment EMS · PCS · BESS · BMS Inverter = electrical equipment Comms equipment Line / router ✓ AC switchgear Chief engineer executes (matches custom & contract) ? DC-side equipment No party contracted for remediation / first response Chief engineer won’t enter; OEM dispatch is limited ? Comms equipment No as-builts → recovery duty left hanging on failure Router-vs-fiber triage also undefined Aggregator Economic dispatch only OEM Own-equipment inspection only Oversight is statutory (whole plant) / execution stops at the AC switchgear This is the responsibility–execution gap (mismatch)

Figure 1 — The law assigns whole-plant safety oversight to the chief engineer. What is missing is not the law, but who in the field executes remediation on the DC side and on comms.

The figure shows a simple fact. The law assigns whole-plant safety oversight to the chief engineer, yet field execution stops at the AC switchgear, and remediation of the DC side and comms belongs to no one. It is not that “the rules have a hole,” but that “on paper the hole is filled while in the field it is not” — which is exactly why it goes unaddressed so easily.

03 — The responsibility matrix: equipment × party

Figure 1 read the law-versus-field discrepancy down a vertical. Expand the same structure across a plane of “which equipment, which party, on what basis,” and the location of the gap grows more concrete. With equipment domains down the side and the parties involved across the top, we shade each intersection by four bases: what the law sets, what a contract sets, what custom has made true in practice, and what is assigned to no one.

Equipment \ Party Chief Eng. Safety firm OEM Aggreg. O&M Owner AC switch-gear EMS PCS BESS Comms Statute Statute Contract Contract Statute Custom Custom Contract Contract Contract Gap Custom Custom Contract Contract Gap Custom Custom Contract Contract Contract Gap Gap Gap Contract Contract Contract Statute Statute Contract Custom Gap

Figure 2 — Responsibility matrix for a grid-scale storage plant. Each cell shows the basis for execution of remediation / first response (Statute = a provision names the party; Contract = set by warranty or service agreement; Custom = it works that way in practice; Gap = assigned to no one). The chief engineer’s statutory oversight duty itself extends to every row — AC switchgear, DC side and comms. The dark cells (Statute) fall only on the AC-switchgear row and on the part the owner bears via grid-connection cyber rules. The gold column (O&M) is where that gap can be taken on by contract.

Follow the colors and the structure is plain. The dark cells (Statute) fall only on the AC-switchgear row and on the part the owner bears via the cyber and technical-standard rules. The wider area is taken up by contract (gold), custom (grey) and gap (red). The red — the gaps — cluster in the owner column on the DC side (as-builts, procurement, evidence data) and in the safety side of the comms row (chief engineer, safety firm). Operating a grid-scale storage plant is, in the end, the work of deciding to which party, and under which contract, that contract/custom/gap territory is assigned. Spell out each intersection and it looks like this.

EquipmentChief Eng.Safety firmOEMAggreg.O&MOwner
AC switchgear /
cubicle
Safety oversight [Statute]Oversight & inspection [Statute]Equipment warranty [Contract]Inspection work [Contract]Ultimate safety duty [Statute]
EMSOversight; remediation out of scope [Custom]Outside standard scope [Custom]Config · remediation · warranty [Contract]Control & operation [Contract]First response & liaison [Contract]As-builts & procurement [Gap]
PCSOversight; DC remediation out of scope [Custom]Customarily untouched [Custom]Lead party for remediation work [Contract]Dispatch & triage [Contract]Remediation arrangement & cost [Gap]
BESS
(cell/BMS)
Oversight; remediation out of scope [Custom]Outside standard scope [Custom]Product & degradation warranty [Contract]Compliance with operating conditions [Contract]Data collection & monitoring [Contract]Warranty upkeep & evidence data [Gap]
Comms
(router/line)
Within oversight but outside design scope [Gap]Outside standard scope [Gap]Warranted by some equipment [Contract]Control assumes comms [Contract]Fault first response [Contract]Docs · redundancy · cyber [Statute]

The reading is single. The only places the law clearly names a party are “safety oversight of the AC switchgear” and “cyber and technical-standard conformity at connection.” Remediation of the EMS, PCS and BESS, and the design, documentation and recovery of comms, lie outside that. Who that gap is assigned to by contract is the core of the business design. From here we dig into the two domains where the gaps cluster — DC-side remediation, and comms.

04 — Why the gap doesn’t close

If responsibility is statutory, why does execution not get filled? The reason lies in two institutional structures: one is the regime for how a chief engineer is assigned, the other is what the safety management rules require to be written.

4-1 The constraint of the external-commitment regime

At high voltage and above, a storage plant either appoints a chief engineer in-house or commits the role externally. METI’s “Interpretation and operation of the chief-engineer system (internal rules)” sets, as a condition of external commitment, that the chief engineer be able to reach the site in principle within two hours (the so-called two-hour rule). METI Notification No. 249 of 2003 further caps the total conversion coefficient of sites a safety officer may take on at under 33. It is a scheme that limits how much one can take on by a “points” value scaled to capacity and output; solar plants and storage plants carry a coefficient that varies by condition (0.31–0.33 in the notification: 0.32 / 0.31 / 0.33 by category). The externally committable range for a storage plant is, as for solar, below 5,000 kW and 7,000 V (METI, “On the safety-regulation approach for storage plants,” 15 April 2022).

This vessel — “a chief engineer within two hours and with points to spare” — is no problem where personnel are plentiful. Reality is the opposite. METI’s “On the chief electrical engineer system” (31 March 2023) shows that, absent new measures, there could be a shortfall of about 1,000 Class-2 and about 800 Class-3 chief engineers by FY2030. External commitment accounts for most appointments, and the workforce is ageing: about 60% of license holders are 50 or older, and the Electrical Safety Subcommittee’s materials project a Class-3 shortfall of about 4,000 against demand of roughly 18,000 by 2045.

From this it follows that the ease and cost of securing a chief engineer vary structurally by region. Where the distance rule, the points cap and the personnel shortage overlap, finding a nearby candidate with points to spare, appointing them and turning that into a quote takes real time. An O&M firm taking several weeks to deliver a quote stems from this institutional vessel — not because a given firm is slow, but because the system is built that way.

4-2 What the safety management rules do not require

The second structure lies in what the safety management rules must contain. Article 50 of the Enforcement Regulation lists the items to be set in those rules. A storage plant that counts as a power generation business (output above 10,000 kW) falls under paragraph 2 of that article; self-use facilities and the like under paragraph 3. The paragraphs differ by equipment class, but both cover roughly the same items: the involvement and organization of the business manager and senior executive, safety education, patrol / inspection / testing, operation and switching, maintenance during an extended shutdown, measures for disasters and other emergencies, safety records, and the regime and record-keeping for statutory self-inspection and pre-use self-confirmation.

There is no provision requiring, as a standalone item, how the comms equipment’s as-builts are kept, or who restores a router when it fails. The standard structure of the safety management rules is built around the AC switchgear and electrical safety, and the comms design documentation and recovery responsibility spill outside what the rules require. When the FIELD NOTE operator says “the as-builts often aren’t handed over,” it is not because someone skimped on paperwork; it is because the rules do not require it to be written. What no one explicitly requires, no one explicitly keeps. That is the true nature of the gap on the comms side.

The responsibility for the DC side is statutory (Art. 43(1) plus the storage-plant definition in the Ordinance). But the execution of DC-side and comms work falls outside the vessel of external commitment (two hours, points, personnel shortage) and outside what the safety management rules require. Responsibility is filled while execution is not — these two institutional structures sustain the gap. If it were a “limit of the rules,” there would be nothing to do; because it is a matter of contract, custom and skill, design can move it.

05 — The real cost of downtime

“If the DC side stops, we just miss the market for a while” — if that is the thinking, the cost may be underestimated by a step. An outage at a grid-scale storage plant is not merely lost opportunity. It bites twice, as institutional penalties in the balancing market and the capacity market. First, let us fix the order of magnitude of the revenue at stake when it stops.

8,785–14,812¥/kW·yrCapacity-market main auction (FY2028 delivery, by area)
12.31¥/kWhJEPX spot, annual average (FY2024)
19.51→15¥/ΔkW·30minBalancing cap price (cut Mar 2026; stepping toward 7.21)

The capacity-market main auction cleared, for FY2028 delivery, at roughly ¥8,785–14,812/kW·yr by area (¥8,785 floor for Hokuriku, Kansai, Chugoku and Shikoku; ¥14,812 ceiling for Hokkaido, Tohoku and Tokyo — OCCTO results, published 29 January 2025); JEPX spot averaged ¥12.31/kWh in FY2024 (JEPX, “FY2024 Business Report”). The balancing market’s ΔkW cap price was cut, alongside the move to day-ahead trading in March 2026, from the former ¥19.51/ΔkW·30 min to ¥15, with a stated policy of stepping down to ¥10 and ¥7.21 if competition does not improve (Agency for Natural Resources and Energy, January 2026). If a 2 MW-class plant stops participating, the daily revenue tied to these is lost. But what really bites is less the lost opportunity itself than the institutional penalties beyond it.

5-1 Balancing market: fall short and you are docked, then locked out

A resource that has cleared in the balancing market (EPRX) owes a duty to respond to dispatch. EPRX’s trading rules set out assessment (verification of response performance) and penalties. Fail Assessment II, which verifies response performance, and a ×1.0 penalty is levied against the cleared amount (this multiplier was revised from 1.5 to 1.0 at the 36th Balancing-Market Subcommittee on 2 March 2023, on grounds of market-participation incentive; Assessment I, which checks the maintained ability to supply, is graduated by degree of non-conformity, up to a maximum of 1.5). Further, fail three times or more within a calendar month for the same resource and product, and new trading in that product is suspended. Stop and you cannot respond; fail to respond and you are docked; repeat and you are locked out of the market — a three-stage structure.

There is, however, a relief framework for events caused by the grid side — such as output curtailment — that the operator could not have foreseen at bidding: the penalty multiplier is set to 1.0 and the event is excluded from the count (an application for grid-caused penalty relief; Forms 24 and 25 apply from the 14 March 2026 delivery onward). Whether you stopped yourself or were stopped by the grid changes the treatment — here too, triaging the cause matters. The product mix, minimum bid size and the direction of the cap-price cut in the balancing market are set out in the contract-design column (Layer 5).

5-2 Capacity market: an unplanned outage bites at “×5”

A plant that has signed a capacity contract — especially via the Long-Term Decarbonization Auction, where it is classed as a “firm power source” — owes a continuous-operation requirement. The capacity contract terms set out assessment and penalties; the economic penalty is levied, against the capacity contract value, on the cumulative shortfall blocks minus 8,640 blocks (≈180 days) (OCCTO, “Capacity Market Operations Manual (requirements/penalties),” and the “Capacity Contract Terms”). In other words, roughly 180 days’ worth a year is effectively a grace, and shortfalls beyond it are in scope.

What to note is how those “shortfall blocks” are counted. Maintenance filed in advance as a planned outage counts at par, but a sudden, unplanned outage counts at five times (excluding normal-time nights and holidays). The rules, that is, explicitly quantify the economic difference between planned maintenance that caught an early sign and an unplanned sudden failure, at five to one.

Outage (downtime) The damage is not limited to lost opportunity ① Lost opportunity Misses price-arbitrage revenue on JEPX, etc. = forgone gross margin ② Balancing: reduction + lockout Assessment II non-conformity → ×1.0 penalty → 3×/month per product → trading suspended ③ Capacity: contract-value reduction Requirement shortfall → capacity contract value reduced → unplanned outage counts ×5 Unplanned outages hit at ×5 Annual outage blocks = (planned blocks + unplanned blocks × 5) − 8,640 blocks (≈180 days) / Capacity Contract Terms; normal-time nights & holidays excluded ×1 Planned outage Maintenance on early signs ×5 Unplanned outage Sudden failure Where O&M response speed pays off Early diagnosis + fast triage and recovery convert sudden failures into planned outages, cutting penalty exposure to about 1/5. * Force-majeure outages may be exempt under the contract terms

Figure 3 — An outage hits through three channels: lost opportunity, a balancing-market penalty, and a capacity-market penalty. Under a capacity contract an unplanned outage counts at five times a planned one, and that is what defines the economic value of O&M response speed.

This factor of five is what most sharply explains the economic value of O&M. Leave a sudden failure as an “unplanned outage” and it bites at five times; catch the early sign and convert it into planned maintenance, and it costs par. Early fault detection, immediate cause triage, fast recovery — what O&M response speed does is convert the unplanned into the planned, compressing penalty exposure to at most about one-fifth. This is not about driving outages to zero. It is about shifting the quality of an outage to the “planned” side. That is precisely why, even where uptime itself cannot be guaranteed, response speed has a clear economic basis.

5-3 The loss figure swings by an order of magnitude with “how online you are”

That said, stating the loss of a single day’s outage as one number is risky. The amount lost scales — by orders of magnitude — with how online the plant is and which products it has promised revenue to. A 2 MW-class plant does not necessarily clear the “dedicated-line, online, large-capacity” threshold the balancing and capacity markets ask of firm power sources; in practice its main revenue tends to be JEPX arbitrage and tertiary-② regulation, where response runs to tens of minutes and a simple command system can be used. The daily loss here is the missed ΔkW (capacity fee) and ΔkWh (supplied volume) for the day’s blocks plus the foregone charge/discharge spread — and it is a mistake to add the fixed income of the capacity market or the Long-Term Decarbonization Auction (annual, 20-year revenue) into a one-day outage figure. Fixed income is impaired where an outage coincides with a requirement dispatch — the unplanned ×5 count of the previous section, or the market-exit penalty of the capacity contract — biting on the “tail.” Unless the outage is close to full operation, that contractual breach is an order of magnitude apart from the daily lost opportunity. Either way, before talking about “¥X million a day,” you must first fix how online the asset in question is.

5-4 Is there a “going rate” for the annual O&M cost?

So what about the O&M cost itself? Let me be candid here. A public standard unit rate for fixed O&M (OPEX) specific to grid-scale storage does not yet exist. The few public clues come from the operating-and-maintenance cost used for the model plant in the Long-Term Decarbonization Auction: METI’s study materials put the operating-and-maintenance cost (labor) at ¥5,000/kW·yr (“Organizing the cost and revenue issues of grid-scale and renewables-paired storage systems,” FY2024 3rd meeting of the Study Group on Expanding the Adoption of Stationary Storage Systems, 29 August 2024 — referencing the model-plant data used to set the ceiling price of the Long-Term Decarbonization Auction). On the international bench, the NREL ATB sets fixed O&M at about 2.5% of CAPEX (including battery augmentation, on a 15-year basis). As a field feel, some take a thicker view of around ¥5 million a year including insurance, while others reckon it fits within ¥2.5–3 million a year excluding insurance — but these are operator-quoted figures, not a publicly established level.

When you place an O&M cost in a business plan, keep in mind that this is a starting number, not a going rate. What you can cite publicly is the unit-rate datum of “¥5,000/kW·yr” and the international bench of “about 2.5% of CAPEX,” and both swing widely with plant scale (2 MW-class versus 10 MWh-class) and with regional differences. Only after breaking the cost into line items (chief engineer, monitoring, call-out, comms, insurance) and laying them side by side can you debate whether the level is reasonable. Indeed, the very fact that the public standard unit rate does not get beyond a single rate datum is itself an uncertainty to fold in when you set an O&M cost into a business plan.

06 — Comms is no one’s job

Of all the gaps in a storage plant, comms is the hardest to pick up. The reason is clear: comms falls right on the boundary between the AC switchgear that the electrical professional (the chief engineer) watches and the control system that the equipment professional (the OEM) watches. The chief engineer’s safety oversight is built around the AC switchgear; the OEM’s warranty closes inside its own equipment. The network itself — the line, the router, the gateway, and the wiring that ties each device together — is at the center of neither party’s remit. And as we saw in §04, the safety management rules do not require the comms equipment’s as-builts or recovery responsibility as standalone items. One layer that no one explicitly holds is formed right here.

This gap bares its teeth the moment the plant stops. A storage plant depends on comms even more than solar does: output curtailment and response to balancing dispatch both presuppose real-time communication. Yet even when the EMS screen reads “comms fault,” that alone lets no one act. Whether the thing that dropped was the on-site router, the carrier’s fiber side, or a lost configuration — depending on the cause, both whom you call and the recovery procedure change completely. If no one in any contract is charged with that triage, then the moment the message appears, the clock starts on a search for “who should move.” And the as-builts essential to that triage — which router holds what settings, which IP connects to what — are, in many deals, never handed over. Not because someone neglected the paperwork, but because the rules did not require it written and the contract did not ask for it. Comms is no one’s problem in calm times and everyone’s problem in an emergency.

On top of this gap, an institutional requirement lands from 2027. Materials from the 20th Grid-Code Study Group (16 December 2025, Agency for Natural Resources and Energy) set out a policy to require, as a technical condition of grid connection, that the “control systems with a communication function (PCS, EMS, etc.)” adopted by distributed resources use products that have obtained Level 1 (★1) under the JC-STAR scheme. Application is scheduled for April 2027 at high voltage and October 2027 for low voltage under 50 kW (low voltage is six months later under a transition that accounts for existing stock — a timeline the subsidy column also touched on). As a premise, the Electricity Technical Standards Ordinance already obliges electrical equipment for business — excluding small-scale business electrical equipment such as solar under 50 kW — to secure cybersecurity (Article 15-2).

There is one practical misconception here: that “if the gateway router has obtained ★1, the devices behind it are out of scope.” But the scheme’s design philosophy is not network-by-network; it imposes the requirement product (system) by product. The Agency’s materials state, in a footnote, that within the covered scope the products (systems) using IP communication are the targets of the ★1 requirement, and that IP-communication devices outside the covered scope are also recommended to obtain it (“On cybersecurity measures for distributed resources,” 12 February 2026, Document 5). A router’s own certification does not exempt downstream devices, and it is not the kind of thing obtained in one go for an entire battery package. It becomes the work of enumerating the devices involved in comms and control one by one and confirming whether each is a ★1-certified product. ★1 and ★2 are the maker’s self-declaration of conformity; ★3 and above are third-party certification, and the IPA began operation on 25 March 2025 and is accepting ★1 applications.

Device-unit (Japan) or zone-unit (overseas)? Both North America’s NERC CIP and the international standard IEC 62443 are built, at base, on a “system / zone” idea: carve the protected scope into zones and conduits, and defend at the boundary. Japan’s JC-STAR requirement, by contrast, imposes a minimum bar on each IP-communication product — a “device-unit” approach. This difference in philosophy strikes directly at how comms is designed and how O&M selects and updates equipment. For new connections and equipment replacements from April 2027 onward, a situation of “this device can’t connect” can arise. And unless the as-builts — which device holds what settings, which IP connects to what — are handed over, neither device-by-device conformity checking nor fault triage holds together. The more cyber requirements are imposed device by device, the more you need a party that keeps device-level design documentation.

6-1 Debunking the “must respond within 0.5 seconds” claim

On the real-time nature of comms, you will sometimes hear an explanation like “to respond to balancing dispatch, the communication response must be within 0.5 seconds.” This is not accurate. Nowhere in the balancing market’s product requirements is there a “communication response within 0.5 seconds” ceiling. Where “0.5 seconds” appears is in the lower bound of the LFC command interval (control cycle) of secondary regulation ① — “0.5 to tens of seconds” — which is not a communication-latency ceiling. The fastest beat is in fact primary regulation, which measures frequency locally at under 0.1 second. “It won’t work unless within 0.5 seconds” is most likely an explanation that mistook the lower bound of the secondary-① control cycle for a communication-response requirement.

The requirement differs by product, in steps. Response time spans from primary regulation’s ≤10 seconds to tertiary regulation ②’s ≤60 minutes, and secondary ①, which requires second-level control, is limited to a dedicated line only. Conversely tertiary ②, whose response runs to tens of minutes, can be entered with a simple command system, and its monitoring interval is in minutes.

ProductComms lineResponse timeMonitoring interval (approx.)
Primary (FCR)Dedicated line (local control)≤10 secFrequency measured locally at ≤0.1 sec
Secondary ① (S-FRR)Dedicated line only≤5 minSeconds (LFC command 0.5–tens of sec)
Secondary ② Dedicated / simple command≤5 minDedicated: seconds / simple: 1 min
Tertiary ① (T-FRR①)Dedicated / simple command≤15 minSame as above
Tertiary ② (T-FRR②)Dedicated / simple command≤60 min1–30 min

Source: EPRX, “Product requirements and trading schedule of the balancing market,” and reference materials of OCCTO’s Balancing-Market Subcommittee. Secondary ① cannot be controlled at second resolution via a simple command system, so its communication line is limited to a dedicated line.

6-2 So what is comms O&M?

Turn all of this over, and what comms O&M actually does as a service comes into view. First, keeping and handing over the as-builts — receiving, as documents at COD, the line type, the model and settings of routers and gateways, the IP allocation and the inter-device connection diagram, and keeping them updated. Second, securing a pre-configured spare — industrial-router lead times are hard to read amid world conditions, and without a spare on site, recovery can stall for weeks (the lengthening of lead times for network equipment in general is verifiable, but the specific lead time for grid-use routers is not confirmed from primary data). Third, a triage procedure and first response for emergencies — deciding in advance, when “comms fault” appears, whom to approach in what order among the site, the carrier and the OEM. Fourth, conformity checking against the ★1 requirement and equipment updates — how to maintain device-by-device conformity through connections and replacements from 2027. None of these is automatically included in the safety management rules, the OEM warranty, or the aggregator contract. Whether to leave comms “no one’s job,” or to have it taken on explicitly under an O&M contract — that single choice divides how fast recovery is when the plant stops.

Which products and which line a storage plant goes after revenue with changes, by an order of magnitude, both the quality of comms demanded and the loss when comms drops. The more you have promised second-level response over a dedicated online line, the more comms becomes a matter of life and death. Before raising “0.5 seconds” as a banner, fix — before COD — which products and which line your asset runs on, and who repairs comms when it drops.

07 — Insurance isn’t paid until the cause is known

A storage plant is typically covered by property insurance plus business-interruption insurance that indemnifies lost profit during a shutdown. But this insurance does not pay out automatically when an incident occurs. Payment presupposes proof that “the subject suffered loss through a fortuitous accident,” and business-interruption insurance indemnifies only the loss that results from that damage. A battery is still new equipment — cell defect, faulty construction, or act of nature — and the burden of proving the cause weighs heavily on the operator; for an event like thermal runaway, cause investigation takes a long time (in the U.S., Moss Landing took about five months from the September 2021 shutdown to public disclosure of the cause). Until the cause is fixed, no claim moves. And once you integrate the equipment of several makers, a situation can arise where responsibility cannot be pinned on a single company (in Korea, 23 ESS fires occurred in 2017–2019, and although a public–private joint investigation listed four factors, it did not reach conclusive proof, and the battery makers disputed the proposed causes).

What pays off here is the preservation of evidence — beginning with the BMS and EMS logs — and the party that carries it is O&M. With a regime that can drive to site on an incident, triage, identify the cause in coordination with the maker, and even produce a remediation estimate, the proof moves forward. Sizing a business-interruption loss also requires the basis for the market revenue that would have been earned had the plant not stopped — data held by the aggregator. Insurance is not “reassuring because you have it”; it should be judged by whether you have a data regime that can prove the cause and size the lost amount when an incident occurs.

※ Coverage, carve-outs, payment conditions and proof requirements depend in their detail on each insurer’s individual policy, and public information is limited. The very fact that policies are not fully disclosed is itself an uncertainty to fold in when you place insurance as a premise of a business plan. The whole picture of insurance design is treated in the insurance-design column.

08 — How mature markets solved this gap

Is the DC-side responsibility–execution gap unique to Japan? Look at international practice and the answer becomes: “mature markets solved this gap by consolidating it into a single point of responsibility.” Japan’s three-party split can be placed as the eve before the market consolidates.

8-1 A single point of responsibility

In U.S. grid-scale storage, an O&M provider that handles on-site maintenance and an asset-management function that oversees contracts, warranties and finance are split, and the owner binds several service contracts with KPIs and penalties. The roles are further layered — an OEM that bears the product warranty (typically 2–3 years), a system integrator that closes the gap to required performance, an O&M provider that secures operation under a 10–20-year long-term service agreement (LTSA), an asset manager, and an optimizer that optimizes market operation (the equivalent of Japan’s aggregator). What is described in Japan as “three parties keep it running” is only a part of these five-or-so roles. U.S. legal practice, too, treats it as common for the OEM to bear performance guarantees under a supply contract and a long-term service agreement, and notes that in recent years, as OEMs provide integrated systems, the need for a single turnkey wrap has been thinning. Installing a single point of responsibility that takes on the whole plant in one hand is the mature-market solution. Japan’s “aggregator + chief engineer + OEM” is a state in which that single point of responsibility is absent and split on the DC side.

Japan: three-party split Mature market: single point of responsibility Owner Aggregator Chief engineer OEM DC side = gap No party binds it all → no basis for an availability guarantee Owner OEM / LTSA (single point) Takes on the whole plant in one hand Guarantees ~97% annual availability but excludes force majeure, grid, weather, theft Japan’s split is the eve before the market consolidates Who installs the single point that fills the gap, and how
Figure 4 — Mature markets consolidate the whole plant into a single point of responsibility through an OEM LTSA and guarantee availability after carving out external factors. Japan’s three-party split sits one stage before that.

8-2 Three tiers of guarantee, and their carve-outs

In a market where a single point of responsibility holds, three tiers — availability, performance and capacity — are guaranteed by contract. On the availability guarantee, the third-party certifier DNV reports that many contracts set availability at around 97% per year as the threshold before damages arise. Actual contract clauses, too, publish a structure that computes damages by multiplying the shortfall below guaranteed availability (in points) by capacity and unit price — for example, a guarantee of 98% against an actual 96.5% multiplies that 1.5-point gap by capacity and rate. Maintaining a degradation guarantee requires an operation that records and retains data such as temperature, current and SoC at 15-minute intervals (this granularity is needed for warranty claims and for confirming tax-incentive eligibility).

Here, Japan’s “can’t guarantee it” that we saw up through §07 and this international “97% guarantee” do not contradict; they are consistent. The international availability guarantee holds only after carving out force majeure and grid-caused events. Research institutions, too, note that with monitored power electronics, contractual availability of around 99.9% is achievable — but on condition that external and force-majeure events are excluded and performance is not embedded in the availability guarantee. Some O&M firms advertise “availability over 99%,” but all stand on the premise of carving out external factors. What differs is that, having carved out those external factors, a single OEM binds and guarantees the remaining equipment-caused availability. In Japan, because no party binds the whole plant, the starting point for guaranteeing availability in one hand simply does not exist.

The same goes for capacity: the OEM binds a design that guarantees the whole system on a 10–20-year scale and covers degradation with augmentation. DNV puts guaranteed capacity at roughly the initial 70%, and NREL ATB’s fixed O&M (2.5% of CAPEX) also includes augmentation cost. In Japan, too, the Long-Term Decarbonization Auction allows the cost of additional procurement and full replacement to be counted in, so O&M’s reach extends from “fix it when it breaks” to “keep the capacity over 20 years.”

8-3 Safety regulation: a fixed 3-meter setback at home, performance-based overseas

The way safety regulation is built shows the same “Japan uses fixed values, overseas is performance-based” contrast. At home, the Fire and Disaster Management Agency’s standards revision (promulgated May 2023, in force January 2024) changed the regulatory unit from cell capacity to kWh, set the floor at over 10 kWh (with 10–20 kWh that has fire-prevention measures excluded = effectively notification above 20 kWh), and requires, for outdoor installation, a setback of in principle 3 meters or more from buildings (cubicle-type and the like, deemed to pose no fire-prevention concern, are excluded). Grid-scale MWh-class plants are of course in scope. Against this, North America’s NFPA 855 sets unit-to-unit separation at in principle 3 feet (about 0.9 m) but allows it to be shortened if safety is demonstrated by the UL 9540A large-scale fire test. Fixed setback (Japan) or test-data-based performance (overseas) — even with the same aim of preventing fire spread, the design freedom differs, and either way, maintaining compliance with setbacks, compartments and inspection records through the operating period is a service someone must carry.

8-4 Three generalizations

Generalizing from the international comparison: First, the idea of function-splitting itself is universal worldwide. Second, the responsibility gap in the comms layer is strongly Japan-specific. The institutional split between the chief-electrical-engineer system (electrical safety) and comms / control (OEM / O&M) produces the DC-side and comms gap. Overseas, because the LTSA wraps the whole on an availability basis, the gap is structurally less likely to arise. That said, as the Korean ESS fires showed, the very unclearing of responsibility when several makers are integrated is universal. The “split between electricians and comms people” may be Japan-specific, but the structure of an integration-responsibility gap is universal worldwide. Third, that the chief engineer does not substantively cover DC-side remediation is not an inevitability of institutional design but a Japan-specific operating custom stemming from skill, OEM certification and warranty scope. In law, the DC side, too, is within the scope of safety oversight.

09 — Sequence and decision axes before COD

What this all shows is that O&M is not “something to think about after COD” but a design matter before it. DC-side remediation, comms documentation, the warranty boundary, penalty exposure — these are fixed at the moment of handover, and hard to slot in afterward. In practice, you want to start composing O&M roughly six months before grid connection.

Place the sequence for building O&M in before COD alongside the connection procedure, in time order, and it looks like this.

−6 months Lock in O&M, chief engineer & comms Construction Appoint chief eng. via O&M Commissioning Just before COD Pre-use self-check COD Next April Balancing market Quote: 2.5–3 weeks Need a chief-eng. candidate within 2h & with point capacity Router lead time ~2.5–3 mo. Long under supply constraints; deploy a configured spare The turnkey-handover trap Chief eng. is incumbent; switching mid-way is possible, but exit terms & a 1-year gap become issues
Figure 5 — A quote takes about 2.5–3 weeks, and procuring a pre-configured router takes about 2.5–3 months under supply constraints (the latter is verifiable as a general lead-time trend; the specific lead time for grid-use routers is not confirmed from a primary source). The closer to COD you act, the more you are chased by lead times.

An easy trap here is the expectation that a turnkey wrap (full-wrap EPC) “will take care of everything if you just hand it all over.” A single EPC wrap does bundle responsibility up to handover, but it is not guaranteed that post-COD O&M, warranty and comms documentation are included in that contract. In U.S. legal practice, too, as OEMs provide integrated systems the need for a single turnkey wrap has thinned in recent years, and a structure where the developer procures equipment directly from the OEM and entrusts construction to a separate EPC — the EPC bearing installation and construction defects, the battery supplier the equipment warranty — has become one common form. Bundling does not necessarily concentrate responsibility into one point. Rather, you need to break out explicitly, by contract, who holds which equipment, until when, on what basis. Whether you can receive the as-builts (especially the comms configuration documents) at handover, where the warranty boundary lies, who bears the unplanned-outage penalty exposure — holding these as pre-COD checklist items can substantially reduce later disputes.

We have gathered the points that owners, EPCs and O&M providers will want to confirm before COD into nine axes. Tap to record your status.

9Nine axes to check when designing O&M and the safety regime
0 / 9

※ The above are design-check axes; they do not substitute for the legal conformity or contract negotiation of an individual project. The applicable relationships change with equipment class, output scale and grid conditions.

10 — Future issues

O&M for grid-scale storage is still a moving field, in both regulation and markets. Finally, the issues that will harden from here.

The structural shortage of safety personnel. Renewable and storage facilities requiring Class-3 oversight grow year on year, while the workforce is projected to fall short toward 2030 and 2045. The external-commitment vessel — the distance rule (2 hours) and the points cap (total under 33) — bites harder as personnel thin. The ease and cost of securing a chief engineer vary structurally by region; this premise must be folded into site selection and the O&M cost estimate.

International harmonization of cyber requirements. JC-STAR began ★1 mutual recognition with the UK PSTI Act from January 2026 and with Singapore’s CLS from June 2026, and the U.S. Cyber Trust Mark and the EU CRA are already in force and operating. How Japan’s device-unit requirement connects with these zone-unit overseas regimes bears directly on equipment procurement and updates.

OEM certification and the build-out of integrated O&M. The key to moving the current state — where the DC side is fenced off by skill, OEM certification and warranty scope — lies in how OEM certification is taken in and who binds and guarantees availability and capacity. How to compose, within Japan’s institutions and commercial customs, the problem that mature markets solved with a single point of responsibility is a field still to take concrete shape.

The exit: augmentation and disposal. The exit of 20-year operation — the cost and responsibility of augmentation to cover degradation, and how to design disposal and recycling after operation ends. As long as the Long-Term Decarbonization Auction allows the cost of additional procurement and full replacement to be counted in, and fire and hazardous-materials regulation requires a safety regime through the operating period, O&M’s reach extends from “build and run” to “keep and retire.”

For reference, the market’s depth in numbers. In the first Long-Term Decarbonization Auction, battery bids were about 4.559 GW and awards about 1.092 GW (an award rate of about 24%) (OCCTO results; note that batteries and pumped hydro together bid about 5.397 GW, and this combined figure should not be mistaken for batteries alone). Applications for grid-connection study reach tens of GW nationwide, and as these storage plants reach COD one after another, who fills the DC-side gap this column has examined rises as an issue for the market as a whole.

Conclusion — It isn’t that there’s nothing to do; it’s that no one does it

“There’s hardly anything to do for O&M” — this column set out from that line. But as we dug in, the structure ran the other way. It is not that there is nothing to do. The law clearly assigns the duty of DC-side safety oversight to the chief engineer. What is empty is not the responsibility but who, in the field, executes that statutory duty — the gap of “oversight is statutory; remediation is unassigned.”

The aggregator faces the market on the assumption that the equipment is running, the chief engineer oversees the AC switchgear, and the OEM maintains its own equipment. The three each fulfill their scope, yet a gap remains — DC-side remediation and comms recovery, named in no one’s contract. And the economic consequence of that gap bites in two stages: as the balancing market’s assessment, and as the capacity market’s ×5 count of unplanned outages. Mature markets solved this gap by consolidating it into a single point of responsibility that binds the whole plant. That such a party has not yet grown in Japan is not a limit of the rules but a matter of contract, custom and skill. Which is exactly why design can move it.

For those buying a grid-scale storage plant, look — beyond price, site and equipment specs — at “who holds the DC side, under which contract.” For those selling, folding O&M and the as-builts into the design is the shortcut to avoiding post-handover disputes. And those who build and maintain can start by treating the three walls of skill, OEM certification and warranty scope not as walls of law but as design variables. It isn’t that there’s nothing to do; it’s only that no one does it — so who fills that gap, under which contract, by when? Deciding that before COD is the heart of the design that underpins the physical operation of a plant you will run for 20 years.

Consult on storage projects, including O&M and safety-regime design

Project-specific information that can’t be judged from an article alone is
disclosed after inquiry, under an NDA.

Contact us →

Primary sources (confirmed as of May 2026)
Statutes: Electricity Business Act (Art. 43(1), 42, 2); Enforcement Regulation of the Electricity Business Act (Art. 52, 56, 50, 3-4); the Ordinance Setting Technical Standards for Electrical Equipment (definition of a storage plant; Art. 15-2); METI Notification No. 249 of 2003 (conversion-coefficient total under 33; solar power plants / storage plants at 0.31–0.33) / e-Gov, METI.
Safety & personnel: METI, “On the safety-regulation approach for storage plants” (15 April 2022, Electrical Safety Division, Document 1); “Interpretation and operation of the chief-engineer system (internal rules)”; “On the chief electrical engineer system” (31 March 2023); Electrical Safety Subcommittee materials on electrical-safety personnel (FY2030 shortfall of ~1,000 Class-2 and ~800 Class-3; ~4,000 Class-3 shortfall by 2045; ~60% of license holders aged 50 or over).
Markets: OCCTO, “Capacity Market Operations Manual (requirements/penalties)” and the “Capacity Contract Terms” (economic penalty = contract value × (cumulative shortfall blocks − 8,640 blocks ≈ 180 days); unplanned outages counted ×5; normal-time nights & holidays excluded); capacity-market main-auction results (published 29 January 2025; by area ¥8,785–14,812/kW·yr; Net CONE ¥9,875); Balancing-Market Subcommittee materials (Assessment II penalty strength revised from ×1.5 to ×1.0 — 36th meeting, 2 March 2023; Assessment II non-conformity is ×1.0 regardless of degree; Assessment I is graduated, max ×1.5); EPRX trading rules and grid-caused-relief forms (Forms 24 and 25 apply from the 14 March 2026 delivery); balancing cap price (¥19.51 → ¥15 in March 2026, stepping to ¥10 and ¥7.21 / Agency for Natural Resources and Energy, January 2026); JEPX, “FY2024 Business Report” (spot annual average ¥12.31/kWh); Long-Term Decarbonization Auction results (battery bids 4.559 GW; awards 1.092 GW; award rate 24%).
Cyber: 20th Grid-Code Study Group, Document 4 (JC-STAR ★1 requirement; HV April 2027 / LV under 50 kW October 2027; 16 December 2025); Agency for Natural Resources and Energy, Document 5 (products using IP communication = device-unit requirement; 12 February 2026); IPA JC-STAR (★1/★2 self-declaration of conformity; ★3 and above third-party certification; operation began 25 March 2025); METI/IPA UK PSTI mutual recognition (1 January 2026; ★1 only) / Singapore CLS mutual recognition (1 June 2026).
Safety: Fire and Disaster Management Agency, revision of the standards for storage-battery facilities (promulgated May 2023, in force January 2024; regulatory unit changed from Ah/cell to kWh; floor above 10 kWh; 10–20 kWh with fire-prevention measures excluded = effectively notification above 20 kWh; outdoors, ≥3 m setback from buildings; cubicle-type and the like excluded); NFPA 855 (separation 3 ft ≈ 0.9 m) and UL 9540A; NERC CIP / IEC 62443.
O&M & international: Study Group on Expanding the Adoption of Stationary Storage Systems, Document 3 (operating-and-maintenance cost ¥5,000/kW·yr = referencing the Long-Term Decarbonization Auction model plant; 29 August 2024); NREL ATB (fixed O&M = ~2.5% of CAPEX, including augmentation, 15-year basis); DNV (availability around 97%/yr as the damages-trigger point; guaranteed capacity roughly the initial 70%); published contract clauses (a structure computing damages as the shortfall below guaranteed availability × capacity × unit price); research-institution analyses (monitored power electronics can contractually achieve ~99.9% availability, on the premise of excluding force-majeure / external events); Norton Rose Fulbright (15-minute-granularity data retention for degradation warranties and tax-eligibility confirmation); Vistra (Moss Landing Phase I; September 2021 shutdown → January 2022 cause disclosure ≈ 5 months).
❓ The following are stated as findings because the primary original was not reached or no public data exists: the four factors, the US$32 million in damages, the 522 units (~35%) taken offline and the makers’ rebuttal in the Korean ESS fires agree across multiple English-language reports, but the Korean-language original from the Ministry of Trade, Industry and Energy (MOTIE) was not reached. No public data exists showing a regional ranking of chief-engineer pay, the lead time of specific grid-use router items, or actual domestic uptime figures; “no public data” is recorded as a finding. Some details of the external-commitment ratio and the age composition of safety personnel, and the annual rate of increase in facilities requiring Class-3 oversight, were not reached in the corresponding primary slides.
※ This is a self-edited article with no supervisory review. Regulation and markets are mid-amendment; figures and effective dates may change. Make the final confirmation of investment decisions and legal conformity by reference to primary sources and to qualified experts.