Skip to content
The Intelligent Infrastructure ReviewAI, Energy, Data Centers and RoboticsPublished by GRIDSTROM Energy Solutions

Engineering & Deployment Review · No. 01

The interfaces decide the schedule

On integrated sites, the equipment rarely fails the program. The boundaries between scopes do — utility to service, service to distribution, distribution to controls.

August 6, 2026 · 7 min read

01 · Engineering Review

Deployment challenge

Delivering storage, on-site generation, and charging infrastructure on an operating site, where the utility service, the existing distribution equipment, and the building systems were never designed to be coordinated.

02 · Engineering Review

System context

A modern integrated site is several systems sharing one point of common coupling: utility service, on-site generation, storage, controllable load, and a supervisory layer arbitrating between them. Each has its own vendor, its own commissioning process, and its own idea of who owns the boundary.

03 · Engineering Review

Key interfaces

  • Utility service to site switchgear — metering, protection, and the disconnect requirement.
  • Switchgear to storage and generation — protection coordination and fault contribution.
  • Power systems to controls — telemetry, setpoints, and fallback behavior on comms loss.
  • Controls to building and operations systems — who may curtail what, and under whose authority.
  • Civil to electrical — conduit routing, pad locations, and access for maintenance and replacement.

04 · Engineering Review

Design and procurement considerations

  • Specify the interface, not only the equipment. Protocol, point list, and failure behavior belong in the procurement documents.
  • Confirm lead times against the utility milestone dates, not against the construction schedule.
  • Require interoperability evidence before award, not a statement of intent.
  • Design for the replacement cycle — the second battery installation is easier than the first only if the pad and conduit anticipated it.

05 · Engineering Review

Common failure points

  • Protection coordination revisited after gear is ordered.
  • Controls scope assumed to be included by three parties and delivered by none.
  • Commissioning sequence that requires the site to be de-energized during operating hours.
  • Telemetry that satisfies the vendor dashboard but not the utility's requirement.
  • As-built documentation that does not survive the handoff to operations.

06 · Engineering Review

Project-stage checklist

  • Concept — single-line drawn to the point of common coupling, with every interface named and assigned.
  • Design — protection study complete and reviewed with the utility.
  • Procurement — interface requirements written into every package.
  • Construction — sequencing plan agreed with site operations, including outage windows.
  • Commissioning — witness plan covering each interface, not each device.
  • Handover — as-builts, point lists, and a documented operating envelope issued to the operating team.

07 · Engineering Review

Original diagram

Original diagram

One site, five interfaces

The boundaries where scope, protection, and controls responsibility change hands. Generic architecture — actual configurations are site-specific.

08 · Engineering Review

Questions for the delivery team

  • Who owns each interface, by name, at each stage?
  • What happens on loss of communications, and has it been witnessed?
  • Which milestone dates are ours, and which belong to the utility?
  • Can maintenance be performed without shutting down the operating site?

09 · Engineering Review

Related analysis

  • Infrastructure Explained — microgrid control hierarchy
  • Project Spotlight — how delivery roles are actually distributed

Distribution kit

LinkedIn set for this issue

Prepared from the published issue so the wording never drifts. The company post carries the official point of view; the founder post adds a separate personal observation.

Company-page announcement

Engineering & Deployment Review — No. 01 The interfaces decide the schedule On integrated sites, the equipment rarely fails the program. The boundaries between scopes do — utility to service, service to distribution, distribution to controls. Three implications we set out in this issue: • Utility service to site switchgear — metering, protection, and the disconnect requirement. • Switchgear to storage and generation — protection coordination and fault contribution. • Power systems to controls — telemetry, setpoints, and fallback behavior on comms loss. Read the full issue in The Intelligent Infrastructure Review: https://gridstrom.com/intelligence/newsletter/engineering-deployment-review/interfaces-decide-the-schedule AI • Energy • Data Centers • Robotics

Founder / personal-profile version

Every recovery plan I have been asked to review traced back to an interface nobody had assigned. A modern integrated site is several systems sharing one point of common coupling: utility service, on-site generation, storage, controllable load, and a supervisory layer arbitrating between them. Each has its own vendor, its own commissioning process, and its own idea of who owns the boundary. What I would ask before committing: — Who owns each interface, by name, at each stage? — What happens on loss of communications, and has it been witnessed? — Which milestone dates are ours, and which belong to the utility? I wrote this one up for the Engineering Review. Not a pitch — the reasoning is in the issue: https://gridstrom.com/intelligence/newsletter/engineering-deployment-review/interfaces-decide-the-schedule

A separate observation, not a restatement of the company post.

Five-slide document outline

  1. 1. The interfaces decide the schedule

    • Engineering & Deployment Review
    • The Intelligent Infrastructure Review
    • AI • Energy • Data Centers • Robotics
  2. 2. The situation

    • Delivering storage, on-site generation, and charging infrastructure on an operating site, where the utility service, the existing distribution equipment, and the building systems were never designed to be coordinated.
  3. 3. Why it is live now

    • A modern integrated site is several systems sharing one point of common coupling: utility service, on-site generation, storage, controllable load, and a supervisory layer arbitrating between them. Each has its own vendor, its own commissioning process, and its own idea of who owns the boundary.
  4. 4. What it changes

    • Utility service to site switchgear — metering, protection, and the disconnect requirement.
    • Switchgear to storage and generation — protection coordination and fault contribution.
    • Power systems to controls — telemetry, setpoints, and fallback behavior on comms loss.
  5. 5. What to do next

    • On integrated sites, the equipment rarely fails the program. The boundaries between scopes do — utility to service, service to distribution, distribution to controls.
    • Full issue: https://gridstrom.com/intelligence/newsletter/engineering-deployment-review/interfaces-decide-the-schedule

Visual-explainer brief

One site, five interfaces

  • Deep navy field, GRIDSTROM green as the single accent, generous margins.
  • Diagram: One site, five interfaces.
  • Three labels maximum; no logos other than the GRIDSTROM mark.
  • Legible at mobile feed size — test at 400px wide before publishing.

Caption: The boundaries where scope, protection, and controls responsibility change hands. Generic architecture — actual configurations are site-specific.

Three follow-up posts

Question prompt

Who owns each interface, by name, at each stage? Curious how others are answering this one. Full reasoning in Engineering Review No. 01: https://gridstrom.com/intelligence/newsletter/engineering-deployment-review/interfaces-decide-the-schedule

Single insight

Utility service to site switchgear — metering, protection, and the disconnect requirement. That is the part most teams find late. https://gridstrom.com/intelligence/newsletter/engineering-deployment-review/interfaces-decide-the-schedule

Practitioner note

From this week's Engineering Review: On integrated sites, the equipment rarely fails the program. The boundaries between scopes do — utility to service, service to distribution, distribution to controls. If you are working through this on a real site, the issue lays out the sequence: https://gridstrom.com/intelligence/newsletter/engineering-deployment-review/interfaces-decide-the-schedule

Direct message for qualified prospects

Hi {{first_name}} — you mentioned {{context}}, so this issue may be directly relevant. We published "The interfaces decide the schedule" in the Engineering & Deployment Review. It covers systems architecture, electrical and civil integration, utility coordination and ends with the questions worth putting to your team. https://gridstrom.com/intelligence/newsletter/engineering-deployment-review/interfaces-decide-the-schedule If it is useful, I am happy to walk through how it applies to your site — no obligation either way.

Placeholders are filled in per recipient. Never sent unsolicited at volume.

The Intelligent Infrastructure ReviewAI, Energy, Data Centers and RoboticsPublished by GRIDSTROM Energy Solutions

Subscribe to the Engineering & Deployment Review

Systems architecture, interfaces, and what actually goes wrong in the field.

Content preferences

Only what is listed above is collected. No third-party sharing. Every issue carries an unsubscribe and preference-management link.