Planning and Scheduling a BESS Project What Your Substation Experience Won't Prepare You For

Scheduling a BESS Project: What Your Substation Experience Won't Prepare You For

BESS projects look deceptively familiar at first glance. There is civil work, electrical work, a connection to the grid, and a commissioning phase. You have scheduled all of those things before. The problem is the way they interact. The dependencies, the long-lead constraints, and the commissioning logic are categorically different from anything in the conventional generation or network asset playbook.

This article is not a BESS technology primer. It assumes you can read a single-line diagram and know what a PCS is. What it does is map the sequencing logic of a utility-scale BESS project from the perspective of someone who has to build the programme, and flag where the schedule will break if you apply conventional assumptions.

1. TECHNOLOGY SELECTION

The Battery Decision Shapes Your Schedule Before You Break Ground

Battery technology selection is usually positioned as an engineering and commercial decision. From a scheduling perspective it is a procurement lead-time decision, and it will set the length of your critical path before a single activity is logic-linked.

The two dominant chemistries at utility scale are Lithium Iron Phosphate (LFP) and Nickel Manganese Cobalt (NMC). LFP has become the default for stationary storage in Australia. Lower cost, longer cycle life, and a significantly better thermal runaway profile. NMC delivers higher energy density, which matters when your site is footprint-constrained, but the manufacturing base is tighter and the supply chain is less mature for large-scale stationary applications.

From a scheduling standpoint the critical question is not which chemistry is better. It is: when can the battery management system, containers, and PCS be on site, factory-tested, and ready to install? That date is your hard constraint. Everything else is sequenced to meet it or follows from it.

For LFP containerised systems from the major vendors, allow 9 to 14 months from purchase order to site delivery. For NMC, 12 to 18 months with greater variability. If your project has a regulatory completion date, work this number backwards before you schedule anything else. The battery delivery date is almost always the longest single lead-time item in the programme, longer than the TNSP connection process in many cases, and longer than civils by a wide margin.

What Technology Selection Changes About Your WBS

Container-based BESS arrives as pre-assembled units. Battery modules racked, BMS wired, thermal management installed. Your site installation is predominantly mechanical and electrical interconnection, not component assembly. This is a fundamentally different WBS structure from a gas turbine or transformer install, and it means your civil programme must be timed to receive complete containers, not to stage component delivery across a long installation window.

The implication: your slab and pad programme must achieve practical completion before the containers arrive. You cannot receive containers and continue civils in parallel, not without a traffic management and laydown plan that most sites cannot support. Get the civil dates right first, then back-schedule the container delivery from them. Do not do it the other way around.

2. ENGINEERING AND DESIGN

Design on a BESS project runs in parallel with procurement, which is unusual for engineers used to conventional project sequencing. By the time your detailed civil drawings are issued for construction, your battery order should already be placed. That means your site layout, pad dimensions, cable routes, and foundation loads need to be confirmed early enough to inform the purchase order, not issued after it.

The earliest design deliverable that drives everything else is the site layout. Pad spacing, container orientation, access corridors for delivery vehicles and cranes, PCS locations, and transformer positioning all need to be resolved before you can finalise foundation designs, cable schedules, or earthing layouts. A late site layout is one of the most common causes of civil rework on BESS projects because downstream drawings get issued based on a preliminary arrangement that later changes.

Geotechnical Investigation

Do not underestimate the schedule impact of geotechnical work. A geotechnical investigation on a greenfield site takes four to six weeks from mobilisation to final report, and the results directly determine your foundation type and bearing capacity. If the geotech comes back with poor results, say highly reactive clays or a high water table, your foundation design changes. If that happens after you have already issued earthworks drawings, you are reissuing. Build the geotech into the very start of the programme and hold the foundation design until the report is in hand.

PSCAD Dynamic Model

This is the design deliverable that catches the most projects off guard. AEMO requires a validated dynamic model of the BESS system for the network impact assessment. The model needs to reflect your actual equipment, which means your battery vendor needs to either provide a validated PSCAD model or give your engineers enough technical data to build one.

Some vendors have models ready. Others do not. Confirm model availability at contract award, not at design stage. A missing PSCAD model has added three to six months to connection timelines on multiple Australian BESS projects. It is not a rare edge case.

Protection Philosophy

Protection design on a BESS project involves coordination between the BESS vendor's internal protection, your site protection scheme, and the TNSP's network protection. These three layers need to be coordinated early because changes to one affect the others. Get the protection philosophy document agreed between all parties before detailed protection design begins. Reworking relay settings after installation is expensive and it delays commissioning.

Fire Engineering

Battery fire risk is a genuine and serious consideration. Your fire engineering report will influence site layout, separation distances between containers, the fire suppression system specification, and the emergency response plan. In some jurisdictions it also feeds directly into the development approval process. Commission the fire engineer early and make sure the output informs the site layout before it is frozen.

3. PROCUREMENT

Procurement on a BESS project is the schedule. If your procurement is late, your project is late. There is no recovery mechanism that substitutes for having the right equipment on site at the right time.

Tesla Megapack and Major Vendor Lead Times

For a utility-scale system from a major vendor, the procurement sequence runs from technical specification through commercial negotiation, purchase order, manufacturing, factory acceptance test, shipping, customs clearance, and site delivery. The manufacturing and shipping phases alone account for 10 to 13 months of that sequence. Add the front-end commercial process and you are looking at 12 to 15 months from starting procurement to having equipment on site.

That means procurement needs to start at project initiation, not after design is complete. On a 15-month project, you do not have time to finish engineering before placing the battery order. You place the order on preliminary design and manage the interface through the manufacturing period.

Factory Acceptance Test

The FAT occurs at the manufacturer's facility, typically in China for LFP systems from the major vendors, in months 10 to 12 of the programme. Your attendance is not optional. Key considerations for your schedule:

The FAT scope must be agreed in the purchase order and reflected in your quality plan. A poorly scoped FAT that misses BMS configuration issues or thermal management anomalies will produce those failures during SAT on site, at a cost and programme impact that dwarfs the investment in a thorough FAT.

FAT sign-off is the logical predecessor to shipping. If FAT reveals defects requiring rework, the shipping date moves right. Build a buffer between FAT completion and required site delivery. Two to four weeks minimum. Treat it as float, but plan for it. The buffer has been needed on more BESS projects than it has not.

MV Transformer and HV Switchgear

These items are often treated as standard procurement on the assumption that they are familiar equipment types. They are, but their lead times are not short. MV transformers are running at 12 to 18 months in the current market. HV switchgear is similar. These are not items you can order after the civil programme is underway. They need to be on order at the same time as the batteries.

Cables

HV cable procurement is straightforward in process but often underestimated in lead time. Custom-specified HV cable for a BESS project can take 16 to 20 weeks from order to delivery. If your cable schedule is not finalised before that window opens, you will be doing late cable procurement against a civil programme that is already in the ground. Get the cable schedule confirmed as early as possible and place the order as soon as the route is locked.

Civil Subcontractor Selection

Allow 6 to 8 weeks for a proper civil tender process. That means civil subcontractor selection needs to start as soon as your development approval is in hand, not after it. On projects where the civil contractor is engaged early, the subcontractor can contribute to constructability reviews and temporary works design, which reduces rework during construction. On projects where the civil contractor is engaged late, they arrive on site and start identifying problems that could have been resolved in design.

4. CIVIL AND STRUCTURAL CONSTRUCTION

Civil work on a BESS project is not complex. It is sequencing-sensitive. The number of activities is modest compared to a substation or transmission line. The consequences of getting the sequence wrong are disproportionately large because the civil programme sits on the critical path to container delivery, which sits on the critical path to commissioning.

Earthworks

Bulk earthworks are typically the first major construction activity after site establishment. The sequencing matters because the earthworks need to be sufficiently advanced to allow drainage and road construction to begin, which in turn need to be sufficiently advanced before pad construction can start.

The risk in earthworks is geotechnical surprises. Fill material that does not meet compaction specifications, unexpected rock, or poor subgrade bearing capacity can each add weeks to the earthworks programme. If your schedule has zero contingency in the earthworks phase, you do not have a realistic civil programme. Build a two to three week buffer into the earthworks completion date or accept that you are carrying the risk explicitly.

Staggered Pour Programme

Battery container pads do not all need to be poured at the same time. A staggered pour programme, string by string, can recover three to four weeks on the civil-to-delivery interface compared to waiting for whole-site earthworks to complete before starting any pads. Most schedulers miss this opportunity because they model civil as two sequential activities: earthworks, then pads. In reality, early earthwork zones can be ready for pad construction while later zones are still being cut and filled.

Identify the stagger opportunity in your logic build, not during a recovery schedule.

The 28-Day Cure Constraint

No container lands on a slab that has not achieved its 28-day compressive strength. You cannot negotiate this with the structural engineer, and you cannot crash it with extra resources. Concrete cures at its own pace.

Back-calculate pour completion dates from your container delivery window. If containers arrive in month 13 and you need 28-day cure, the last slab pour must be complete by month 12. Work backwards from there to determine when formwork, reinforcement, and concrete placement need to begin. In practice this means the civil programme needs to be underway by month 5 to 6 at the latest on a 15-month project, earlier than most EPC programmes assume.

Underground Services

Cable trenching, earthing grids, and underground conduit runs must be complete before slab pours in those areas. That seems obvious. What is less obvious is that earthing grid installation often requires testing before backfill, and the test results may trigger rework if earth resistance values are not achieved. Build the test-and-rework loop into your programme. One earthing test failure can hold a slab pour for two weeks while additional earth rods are driven and retested.

The same logic applies to conduit and draw-wire installation. Conduits cast into slabs cannot be remediated post-pour. Any rerouting discovered after pour, because a cable schedule changed or a PCS footprint shifted, becomes a coring exercise. Get the cable schedule aligned with the civil drawings before any concrete is placed. This coordination happens between the electrical engineer and the civil contractor, and on most projects it does not happen early enough.

Access Roads and Hardstands

Megapack containers are heavy and the delivery vehicles are oversized. Your access road needs to be designed and constructed to handle the delivery loads before the first truck arrives. This includes external road access from the highway to the site, the internal hardstand around the battery array, and the crane pad positions.

If your access road is not complete when containers arrive, you either delay delivery or take the risk of road damage under loaded vehicles. Neither is a good outcome. The access road should be complete at least four weeks before first container delivery.

5. GRID CONNECTION AND TNSP INTERFACE

Of all the long-lead items in a BESS schedule, the grid connection process is the one with the least schedule certainty and the most external dependency. You do not control it. You influence it through early lodgement, responsive information provision, and persistent engagement. That is your entire toolkit.

Lodge the connection application on day one of the project. Not after the design is mature. Not after the battery order is placed. Day one.

How the Process Works

In the Australian National Electricity Market, connecting a BESS to the grid requires registration with AEMO as a market participant and a connection agreement with the relevant TNSP, AusNet, TransGrid, ElectraNet, Powerlink, or Western Power depending on jurisdiction. The process broadly runs from indicative planning assessment through network impact assessment, connection offer, negotiation, executed agreement, and finally energisation permit.

From lodgement to executed connection agreement, expect 9 to 14 months in a best-case scenario. This is not a worst-case estimate. It reflects a well-prepared application, a responsive proponent, and a TNSP that is not congested with other connection applications, which is increasingly difficult to guarantee as the NEM connection queue has lengthened materially since 2022.

What This Means for Your Schedule

The energisation permit, the TNSP's formal authorisation to energise your connection, is the gate that allows you to begin system integration testing at full power. You cannot commission a BESS against the grid without it. Your string commissioning can proceed in isolation and should, to keep the programme moving. But any test that requires export or import from the network is gated behind the permit.

Map this constraint explicitly in your schedule. Create a milestone for Connection Agreement Executed and drive logic from it to your HV installation programme and your SIT start. If the agreement slips, your critical path moves right with it, and that is a contract exposure your client needs to see clearly, not absorb as a vague delay.

AEMO Registration

AEMO registration as a scheduled generating unit or market network service provider runs in parallel with the TNSP process but has its own sequence of requirements: performance standards, model submission, and compliance testing. The PSCAD dynamic model issue described above in the design section applies here directly. If your model is late, your registration is late. If your registration is late, your COD is late.

Allow four to six weeks for AEMO to allocate a compliance testing slot after you notify readiness. In a busy market this can be longer. It is an external dependency that your schedule needs to reflect.

6. ELECTRICAL INSTALLATION

HV cable installation on a BESS project follows the same sequencing as any HV installation, with one important difference: the cable route runs through an area that is also being used for battery container installation and associated civil works. Traffic management and laydown space need to be planned carefully. HV cable drums are large. They need a lay-down area near the route, and that lay-down area needs to still exist when the cable crew arrives, which is not guaranteed if the container installation programme has expanded onto the same footprint.

Earthing

The earthing system on a BESS project is more extensive than a standard substation because the battery array is a large and spatially distributed source of fault current. The earthing grid needs to extend across the full array footprint and be properly bonded to each container. This is not a small installation. Allow adequate time in the electrical programme for earthing grid installation, testing, and any rework.

The earthing design should be confirmed before trenching begins. Late changes to the earthing design after trenching is complete, because the protection coordination study revealed a gap, are a common source of programme delay and cost overrun.

7. COMMISSIONING

BESS commissioning is where schedules collapse if the logic has not been built correctly from the start. It involves more sequential dependencies than any other phase of the project, it is governed by external parties at multiple stages, and it cannot be meaningfully crashed without introducing quality risk that manifests later as availability failures.

String Commissioning

Once containers are on site and mechanically installed, SAT begins at the string level. A string is the smallest independently commissionable unit, typically one battery container and its associated PCS. The SAT sequence for each string covers insulation resistance tests, BMS configuration verification, PCS startup, initial and full charge and discharge cycles, protection relay testing, and SCADA integration verification.

The critical scheduling point: strings can be commissioned in parallel. A 10-string project does not commission string by string over 10 sequential periods. You can run three to four strings simultaneously with the right commissioning resource plan. Your schedule should reflect this. If it does not, you are padding the commissioning programme unnecessarily.

Parallel string commissioning requires one commissioning engineer per active string. These are specialist roles. Confirm the vendor's commissioning team size at contract award and model the parallel string commissioning rate explicitly. If your resource plan shows two engineers on a 10-string project, you are sequentialising your commissioning whether your schedule says so or not.

SIT Preparation

The most common commissioning scheduling error is modelling the System Integration Test as a single activity starting after the last SAT completes. In reality, SIT preparation, which includes SCADA configuration, protection relay coordination review, and grid code compliance documentation, must begin while SAT is still running. Build SIT preparation as a parallel activity with a finish-to-start link from first string SAT, not last string SAT. This alone can recover three to five weeks from the commissioning phase.

System Integration Test

The SIT is the convergence point of all programme tracks. It tests the BESS as a complete system connected to the grid, including round-trip efficiency, response time, FCAS capability, SCADA integration, and grid code compliance. The energisation permit must be in hand before SIT can begin. All strings must have completed SAT. The SCADA and EMS system must be configured and tested in simulation mode before live grid testing begins.

8. HANDOVER AND OPERATIONS READINESS

The handover phase is consistently underscoped in BESS project schedules. It is treated as an administrative afterthought when it is actually a technical phase with real duration and real dependencies.

As-built documentation takes time to produce correctly. Operations and maintenance manuals for a BESS project are more complex than for a conventional generator because the technology is newer, the vendor documentation less standardised, and the integration between battery, PCS, EMS, and SCADA systems requires explanation. Allow three to four weeks for as-built and O and M documentation, not two days.

Operator training is a gating activity for COD on some contracts. Your operations team needs to be trained on the SCADA system, the battery management system, and the emergency response procedures before you can declare commercial operation. Build the training programme into the commissioning phase schedule so it runs concurrently with SIT defect rectification rather than after COD is already late.

Performance testing, specifically capacity verification at full rated power, is often required before COD can be declared and before the asset can enter the market. Allow one to two weeks for performance testing and the associated reporting after SIT sign-off.

9. THE SCHEDULE FAILURE MODES

If you are planning your first BESS project, the failures that will hit you are not random. They cluster around four areas:

Battery delivery later than planned. The lead time was underestimated, the FAT found defects, or shipping was delayed. The civil programme is complete and the site is sitting idle waiting for equipment. The mitigation is to treat the battery delivery date as the most important date in the schedule and protect it with a buffer that reflects actual shipping and customs variability.

TNSP connection agreement later than planned. The network impact assessment took longer than expected, the connection offer required renegotiation, or the queue for TNSP engineering resources was longer than anticipated. The mitigation is early lodgement and proactive engagement, not optimistic programming.

Concrete cure time not properly modelled. The scheduler applied a five-day working week calendar to a 28-calendar-day cure constraint, which means the cure was modelled as 20 working days rather than 28 calendar days. The concrete is not ready when the schedule says it is. Check your cure time modelling against a calendar, not a working day count.

Commissioning resources not confirmed at programme build. The schedule assumed parallel string commissioning but the vendor commitment was for sequential commissioning with one engineer on site. The programme was three weeks shorter than the vendor could actually deliver. Confirm the commissioning crew size and confirm it in the contract, not in a meeting note.

The projects that finish on time are the ones where these four failure modes were identified in the planning phase and managed throughout execution. They are not surprises. They are known risks that become surprises when the schedule does not reflect them.