Outcome
Name the operational goal: resilience, energy shifting, demand management or another defined use case.
SYSTEM PLANNER
A practical system plan is a shared brief, not a promise of a final design. Use it to capture what the project is trying to accomplish and what needs verification.
Start a project brief
FOUR INPUTS
Each input helps move a request from a broad category question to a more useful technical conversation.
Name the operational goal: resilience, energy shifting, demand management or another defined use case.
Provide the approximate power range and intended operating duration, noting what still needs study.
Describe the site, electrical boundary, available footprint and any monitoring or control relationships.
List the documentation, standards and approval questions that the project team must address.
Early planning is valuable because it exposes assumptions before they become commitments. A system brief can distinguish confirmed facts from estimates, identify missing site data and define which questions require a qualified engineering response. This approach supports a more orderly discussion between procurement, design, operations and regional stakeholders.
It also helps teams compare options on the criteria that matter for the project: electrical compatibility, control strategy, safety documentation, installation context and service responsibility. No single category label can resolve those questions alone.
Even partial information is useful when it is clearly labelled as preliminary.
Selection note: LFP and NMC storage choices involve thermal behavior, energy density and lifecycle economics. Usable capacity, cycle life, C-rate and state-of-charge operating window must be verified for the intended duty cycle, together with the applicable UL 9540, UL 1973 and local installation requirements.