{"id":3530,"date":"2026-10-16T07:21:00","date_gmt":"2026-10-16T07:21:00","guid":{"rendered":"https:\/\/hmxenergy.com\/bess-grid-reconnection\/"},"modified":"2026-10-10T06:01:48","modified_gmt":"2026-10-10T06:01:48","slug":"bess-grid-reconnection","status":"publish","type":"post","link":"https:\/\/hmxenergy.com\/vi\/bess-grid-reconnection\/","title":{"rendered":"BESS\u5e76\u7f51\u91cd\u8fde\uff1a\u7f16\u5199\u5b89\u5168\u8fd4\u56de\u7684\u6761\u4ef6"},"content":{"rendered":"
\"HMX
\u9a6c\u6765\u897f\u4e9a\u5546\u4e1a\u5de5\u5382\u524a\u5cf0\u5e94\u7528\u4e2d\u7684100kW 215kWh\u5e76\u7f51\u592a\u9633\u80fd\u52a0\u50a8\u80fd\u7cfb\u7edf\uff1bHMX\u5a92\u4f53\u5e93\u53c2\u8003\u56fe\u7247\u3002.<\/figcaption><\/figure>\n

The utility has returned, the battery is supplying the building, and the operator wants normal service restored. That is not enough information to authorise a breaker to close. BESS grid reconnection requires a defined sequence: establish permission, verify the relevant electrical conditions, execute the approved transfer, confirm the resulting state and then restore dispatch.<\/p>\n

The sequence differs between a live microgrid that resynchronises with the utility and an open-transition arrangement that interrupts the backed-up supply before transferring. Specify which architecture you are purchasing. “Automatic return” says little about the interruption, protection logic or behaviour when a required signal is unavailable.<\/p>\n

Write the return sequence alongside the outage sequence<\/h2>\n

Our \u50a8\u80fd\u7cfb\u7edf\u9ed1\u542f\u52a8\u4e0e\u5907\u7528\u6307\u5357<\/a> addresses establishing an island supply. Returning to the utility is a separate operating obligation. A project can demonstrate successful island operation and still lack an approved, testable return sequence.<\/p>\n

Start with the interconnection agreement and the responsible network operator’s current requirements. Record which party grants permission, whether permission is automatic or explicit, which protection functions must be healthy, and which settings require approval. Keep these requirements tied to the site and the installed equipment revision.<\/p>\n

The US Department of Energy’s distributed-energy interconnection checklist<\/a>, published in 2021, organises the utility coordination process. It is a useful project-management reference, not a source of universal settings for a project in Malaysia, Kenya or another jurisdiction. Obtain the actual conditions from the authority governing your connection.<\/p>\n

Separate grid qualification from synchronisation<\/h2>\n

Grid qualification asks whether the utility supply meets the approved conditions for return. Synchronisation, where the design reconnects a live island, asks whether the two systems satisfy the approved conditions for closing the interconnection. Neither condition should be inferred from a dashboard icon labelled “grid available.”<\/p>\n

The 2021 NLR guide to interconnection rules and IEEE 1547<\/a> describes the role of authorities in adopting technical requirements. Referencing a standard in a tender does not remove local approval or establish that the same edition and settings apply everywhere. Ask the integrator to identify the adopted rules and the project-approved configuration.<\/p>\n

For a closed-transition design, require the engineering team to document the relevant voltage, frequency, phase and switching conditions, together with the protective interlocks. For an open-transition design, require the interruption and load-restart sequence instead. Do not label an open transition “seamless” unless the delivered system has evidence supporting that claim for the loads concerned.<\/p>\n\n\n\n\n\n\n\n\n\n\n
Original reconnection state matrix for a project-specific control narrative<\/caption>\n
\u72b6\u6001<\/th>\nEntry condition to document<\/th>\nAction if the condition is not met<\/th>\n<\/tr>\n<\/thead>\n
Island remains in service<\/td>\nIsland supply healthy and permitted to continue<\/td>\nApply the approved load or shutdown policy<\/td>\n<\/tr>\n
Utility qualification<\/td>\nApproved utility measurements and permission available<\/td>\nRemain disconnected; identify the blocking reason<\/td>\n<\/tr>\n
Transfer preparation<\/td>\nSwitching architecture and required interlocks ready<\/td>\nCancel the transfer request without defeating protection<\/td>\n<\/tr>\n
Reconnection or transfer<\/td>\nApproved synchronisation or open-transition conditions met<\/td>\nRecord unsuccessful operation and follow the recovery sequence<\/td>\n<\/tr>\n
Connected confirmation<\/td>\nActual device feedback and supply state verified<\/td>\nBlock normal dispatch pending state confirmation<\/td>\n<\/tr>\n
Dispatch restoration<\/td>\nOwner’s import, export and charging policy enabled<\/td>\nMaintain the defined restricted operating state<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

One controller must own the transfer request<\/h2>\n
\"Technician
\u6280\u672f\u4eba\u5458\u4e3a\u9a6c\u6765\u897f\u4e9a\u5de5\u4e1a\u5382\u623f\u8c03\u8bd5100kW 215kWh\u5546\u7528\u592a\u9633\u80fd\u50a8\u80fd\u89e3\u51b3\u65b9\u6848\uff1bHMX\u5a92\u4f53\u5e93\u53c2\u8003\u56fe\u7247\u3002.<\/figcaption><\/figure>\n

A battery PCS, generator controller, automatic transfer system and EMS may all know that the grid has returned. They should not all act independently on that information. Identify the device that owns the transfer request and the devices that provide permission, measurements and final interlocks. Define how commands are acknowledged and how actual position feedback is distinguished from the last commanded position.<\/p>\n

NLR’s microgrid controls research<\/a> includes evaluating controls with software and hardware-in-the-loop platforms. For procurement, that supports asking for sequence-level evidence rather than accepting an isolated component demonstration. It does not prove that a particular commercial controller has passed those evaluations.<\/p>\n

When reviewing an industrial energy storage proposal<\/a>, make the return sequence a named integration deliverable. A cabinet quotation alone may not include the transfer switchgear, utility interface or site controls. Put those responsibilities in the scope instead of discovering the omission during commissioning.<\/p>\n

Test the blocked return, not only the successful one<\/h2>\n

The most informative acceptance scenario may be a utility return that should not cause reconnection. Examples include missing permission, invalid measurements, an unhealthy protection function, contradictory switch feedback or an operator lockout. Test these conditions using the approved commissioning method, with responsible personnel and the authority’s required involvement. Do not create uncontrolled live faults to demonstrate an interlock.<\/p>\n

Request an event trace that links the source measurements, qualification decision, command, feedback and resulting power flow. The time resolution must be suitable for the function being assessed. A slow cloud trend may show that grid power resumed, yet miss the transfer event itself. Avoid claiming a transfer duration from a recording that cannot resolve it.<\/p>\n\n\n\n\n\n\n\n\n\n
Evidence needed to distinguish a successful return from an unsafe assumption<\/caption>\n
Acceptance scenario<\/th>\n\u8981\u6c42\u7684\u8bc1\u636e<\/th>\nBuyer concern addressed<\/th>\n<\/tr>\n<\/thead>\n
Normal approved return<\/td>\nSequence trace and load response under the agreed test conditions<\/td>\nProduction loads resume as specified<\/td>\n<\/tr>\n
Return permission absent<\/td>\nBlocked command and an intelligible operator message<\/td>\nThe controller respects the connection authority<\/td>\n<\/tr>\n
Transfer unsuccessful<\/td>\nDevice feedback, alarm and approved recovery behaviour<\/td>\nNo repeated uncontrolled closing attempts<\/td>\n<\/tr>\n
Utility deteriorates during return<\/td>\nAborted or completed sequence according to the approved design<\/td>\nTransition logic handles changing conditions<\/td>\n<\/tr>\n
Communications unavailable<\/td>\nDocumented local fallback and restricted actions<\/td>\nA network failure does not invent permission<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Do not let recharging create the next problem<\/h2>\n

After return, the battery may need energy and the building may be restarting equipment. Unrestricted recharge can compete with returning loads for transformer or import headroom. Write a restoration policy that prioritises the owner’s actual requirements: load recovery, backup reserve, demand control and any export restriction. It should be part of acceptance, not a later optimisation experiment.<\/p>\n

Separate those supervisory decisions from the protections described in our BMS\u3001PCS \u4e0e EMS \u8d23\u4efb\u6307\u5357<\/a>. A tariff-driven EMS request must not override a battery limit or a required interconnection interlock.<\/p>\n

Before signing off, ask the integrator to demonstrate both a permitted return and a correctly blocked return. The resulting record should explain why the system reconnected, which conditions allowed it, what happened to the loads and how normal dispatch resumed. That is a more useful deliverable than an unexplained “grid restored” message.<\/p>","protected":false},"excerpt":{"rendered":"

\u5728\u63a5\u53d7\u5fae\u7535\u7f51\u63a7\u5236\u5e8f\u5217\u4e4b\u524d\uff0c\u8bf7\u660e\u786eBESS\u5e76\u7f51\u91cd\u8fde\u6743\u9650\u3001\u540c\u6b65\u3001\u963b\u65ad\u8fd4\u56de\u72b6\u6001\u53ca\u5207\u6362\u540e\u8c03\u5ea6\u3002.<\/p>","protected":false},"author":4,"featured_media":3158,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-3530","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blog"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t