← Form Energy, Inc.
Something new at Form Energy, Inc.

Expose 72-hour coverage without overstating planning certainty

You’re the software engineer. Your team is in the room. Printed Oct 12, 2026.

Planner demand for a usable capacity view is pulling against the limits of operational battery data.

Grid resource planners need scenario clarity while engineering must avoid turning incomplete operating data into unsupported commitments.

Who you’d be doing this for

“I keep getting asked what the system covers on day three, and today I’m piecing it together from separate files.”

Timo Holmberg · Grid Resource Planner

Assesses capacity resources for a utility facing rising load and prolonged reliability risks.

What is at stake

Planners are manually stitching together battery information to answer day-three reliability questions. You must weigh a simple pilot experience against assumptions that need clear review.

Why it isn’t already fixed

Every obvious fix costs something else. That’s the part you’d have to decide.

  • planner clarity vs technical fidelity
  • pilot speed vs reviewed assumptions
  • new interface value vs live-system isolation
  • broad planning needs vs focused first version

Why Form Energy, Inc.

The iron-air battery system’s multi-day discharge capability must be legible to grid resource planners evaluating reliability capacity.

Written with these in mind

product-minded software engineersystems integration engineerdata-interface builder

Not your kind of problem? 20 more at Form Energy, Inc., or browse every organization.

This is the setup. The work is inside.

Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.