FluxPilot is desktop BESS site layout software that places a sized battery project on your real parcel. Import the site as a DXF and FluxPilot lays out battery and inverter blocks in rows and clusters, generates access roads with realistic turning radii, routes the medium-voltage feeders, and holds your setbacks and exclusion zones. You get a site plan draft to shape and export back to DXF, so you can prove a target MWh fits a specific piece of ground in minutes instead of a day at a CAD seat.
It picks up where sizing leaves off. Once you know the container and inverter counts a project needs, the real question is whether they fit the ground you actually have, with the aisles, roads, and clearances a build requires. FluxPilot turns that fit check into something you run and re-run while the design is still moving.
A layout tool takes an equipment list (container and inverter counts) and resolves it into geometry on a real boundary. FluxPilot handles the parts that make BESS layout different from generic site planning:
FluxPilot imports your site DXF so the layout sits on the actual boundary and features, not a clean rectangle. Bring the parcel outline, mark the areas you can build in, and mark the areas you cannot: wetlands, easements, grading limits, floodplain. You can lay out across multiple build areas on one parcel, so a site split by a road or a drainage channel stays a single project instead of three disconnected drawings.
FluxPilot places each inverter or PCS with the battery containers it serves, then repeats that block across the buildable area. You control block size, container and row spacing, and how blocks group, so the layout matches how you build and maintain the site. For DC-coupled (DC-block) designs the container-to-inverter pairing carries straight through from sizing. For AC-coupled designs the inverter and its containers place as a unit. Change the grouping and the layout re-flows in one pass. Because you set the spacing, you can open aisles wide enough for the separation your fire strategy calls for and still see how many blocks the parcel holds.
A battery site has to be drivable, first by the trucks delivering containers and then by emergency vehicles once it is energized. FluxPilot generates access roads around the equipment rows with turning radii, so the geometry reflects a vehicle that has to reach every block and turn at the ends, not just centerlines on a plan. The roads follow block placement, so re-clustering the equipment regenerates the roads instead of forcing a manual redraw.
FluxPilot routes the medium-voltage feeders from the inverter blocks through the site, so the layout carries its collection as well as its equipment footprint. Feeder runs follow block placement, which lets you see how a grouping decision lengthens or shortens the collection before you commit. That feedback matters because a tighter cluster that shortens feeder run can cost you road access or aisle width, and a layout you can re-run makes that tradeoff visible instead of hidden.
Property-line setbacks, internal spacing rules, wetlands, easements, and other keep-out areas are constraints the placement respects from the start, not lines you clean up afterward. When a setback tightens or an exclusion zone moves after a survey update, re-run the layout and see what still fits and what spills over the boundary. This is where hand layout hurts most: one boundary change can invalidate an afternoon of block-by-block CAD work.
The reason to do this in software is iteration speed. Swap the battery model, change the target MWh or duration, move a build area, tighten a setback, or re-group the blocks, and FluxPilot re-lays the site in one pass. That turns layout from a one-shot CAD exercise into something you run several times an hour, which is exactly when layout feedback changes decisions, while the parcel, the battery, and the target are all still in play.
When the draft is where you want it, export it back to DXF and take it into your own CAD environment for detailed design. FluxPilot produces a design draft to hand off and refine, not a final construction set, so it sits in front of your existing engineering workflow rather than replacing it.
A layout is only as good as the numbers behind it, so FluxPilot keeps sizing and layout together. Container and inverter counts from sizing flow straight into placement, so the layout reflects the equipment the project actually needs. The augmentation schedule tells you how many containers and inverters you add across a 20-year horizon to hold usable energy flat as cells degrade, so you can reserve buildable area for them now instead of finding the shortfall at year 5. Weather-driven auxiliary load and capacity derate, modeled from about 20 years of climate data (a typical year and a hot year), feed the same design, so the footprint reflects the system you will actually operate. See the capabilities overview or the guide on how to size a utility-scale BESS.
FluxPilot is for utility-scale storage and solar-plus-storage developers, IPPs, and EPC and engineering firms: the people who have to prove a project fits a specific parcel before it advances. Whether you are checking that a pipeline site holds its target capacity or laying out several candidate parcels to compare, a layout you can re-run is worth more than a drawing you redraw.
The best way to see it is on your own ground. Book a 30-minute demo, bring a site DXF and a target MWh, and we size a real project and lay it out on your parcel on the call. You leave with the design draft to refine yourself. See the full picture of what FluxPilot does across sizing, layout, augmentation, and weather.
Yes. FluxPilot imports your parcel as a DXF and lays the design out on the real boundary and features, including multiple build areas on one parcel. When the draft is ready, you export the layout back to DXF and take it into your own CAD for detailed design.
Yes. FluxPilot generates access roads with turning radii around the equipment rows and routes the medium-voltage feeders from the inverter blocks toward the point of interconnection. Both regenerate when you move or re-group the equipment.
Yes. You set container, row, and block spacing, and FluxPilot holds those clearances while it places equipment and roads. That lets you match the separation your fire strategy and maintenance access require and still see how many blocks the parcel holds.
No. FluxPilot produces a site plan draft to iterate on and hand off, not a final construction set. You export it as DXF and take it into your own CAD environment for detailed design.
The container and inverter counts from sizing flow straight into placement, so the layout reflects the equipment the project actually needs. The 20-year augmentation schedule shows how many containers and inverters you add over time, so you can reserve buildable area for them from the start.