> ## Content Index > Fetch the complete content index at: https://insights-infrapick-africa.ghost.io/llms.txt > Use this file to discover other available public pages before exploring further. # Managing Long-Lead Equipment in Data Center Projects: The Case of Generators - URL: https://insights-infrapick-africa.ghost.io/managing-long-lead-equipment-in-data-center-projects-the-case-of-generators/ - Published: 2026-10-09T12:16:23.000Z - Updated: 2026-10-09T12:16:23.000Z - Author: Infrapick Africa In Data Center delivery, long-lead equipment is not simply a procurement concern. It can become a programme constraint well before construction reaches the point where the equipment is physically required on site. Generators are a useful case in point. Current 2026 market data published by Global Power Supply, covering major manufacturers including Cummins, MTU, Kohler, Hipower and Mesa Solutions, shows a significant increase in lead time as generator capacity rises. | **Generator type** | **Indicative lead time** | | --------------------------------- | -------------------------------------- | | 25–400 kW Standby Diesel | 12–26 weeks | | 500–600 kW Standby Diesel | 12–30 weeks | | 750–1,000 kW Standby Diesel | 12–39 weeks | | **1,250–3,250 kW Standby Diesel** | **52–70 weeks** | | 35–1,000 kW Mobile Diesel | 12–39 weeks | | 70–500 kW Natural Gas | 26–39 weeks depending on configuration | *Source: Global Power Supply, Generator Lead Times in 2026* The figures are indicative and remain subject to manufacturer capacity, configuration and project requirements. But for Data Center projects, the 52–70 week range for large standby units deserves particular attention. A 70-week lead time does not necessarily put a programme at risk. A 70-week lead time identified too late does. The procurement date is already a design milestone The obvious response to a long lead time is often: place the order earlier. Meanwhile, the issue is more complex. A generator package cannot be meaningfully released while fundamental inputs are still moving: electrical topology, power-block strategy, unit sizing, redundancy philosophy, interfaces, controls, environmental constraints and performance requirements all influence the package. Therefore whatsapp matters is not simply when should procurement place the order. Project Manager should focus on "**by when must the project reach sufficient design maturity to release the package?**". This distinction is very important because the answer can bring a procurement-driven decision gate surprisingly early into the programme. --- ## Practical Case — 150 MW Tier III Data Center, 36-Month Programme Consider a 150 MW Tier III Data Center development, delivered over 36 months with an N+1 power topology. For the purpose of the exercise, assume the selected generating sets fall within the 3 MW class. The headline 150 MW should not be used to simply divide the load by 3 MW and add one generator. The actual fleet would depend on the critical load, electrical topology, power-block configuration, generator rating and derating, auxiliary loads and how N+1 redundancy is implemented across the design. For the programme exercise, however, we already have the critical information: generators within the 1,250–3,250 kW range currently carry an indicative 52–70 week lead time. Assume the first units are required on site around Month 27, leaving the remaining programme for installation, integration, testing and phased commissioning. Working backwards from the upper end of the current lead-time range places the generator procurement release at approximately Month 11\. That changes the conversation. The critical milestone is no longer Month 27\. It is Month 10–11, when the package needs to be sufficiently defined and commercially ready for release. A simplified sequence could look like this: ![](https://storage.ghost.io/c/ae/a9/aea9a5ed-e74c-4627-a437-7db977568d2b/content/images/2026/10/1001166713-1.png) This means that on a 36-month programme, a long-lead generator package can require a major design and procurement decision within the first third of the project. --- ## What happens if the release slips? Suppose the package planned for Month 11 is not released until Month 14\. Those three months do not automatically disappear because civil works, structural works or other packages remain on programme. Unless the project can recover through supplier capacity, alternative equipment, resequencing or another mitigation measure, that delay moves downstream towards installation and commissioning. This is where long-lead equipment becomes a programme-level risk. It also explains why large Data Center developments should not necessarily look at the generator fleet as one single procurement and delivery event. On a 150 MW development, power-block sequencing, phased manufacturing and phased delivery can become part of the delivery strategy. The programme may be more sensitive to the arrival of the generators required for the first commissioning sequence than to the delivery date of the final unit. The same logic extends beyond the generators themselves. Switchgear, ATS, controls, fuel systems and associated interfaces must ultimately converge around the same installation, energisation and commissioning sequence. A generator sitting on site provides little programme benefit if another critical element of the power chain is unavailable. Managing the long-lead path for project teams is to work backwards: **Required-on-site date → Manufacturing & delivery → Procurement release → Design maturity required for release** That chain should be visible in the master programme and linked to the relevant design gates, procurement milestones and project risks. Long-lead management starts before the purchase order. It starts when the programme identifies the decisions that must be mature enough to release that purchase order on time. For our 36-month example, the generator may not be required on site until Month 27\. The decision window that protects that date may sit around Month 10–11\. That is the date the project team needs to manage. --- ## Have a long-lead equipment or project sequencing question? Book an Infrapick On-Demand Consultation to review your project assumptions, procurement strategy and potential schedule exposure. → [Book a consultation](https://calendly.com/infrapick-discovery-expert-call/30min?back=1&month=2026-10&ref=insights-infrapick-africa.ghost.io) --- ## ABOUT THE AUTHOR A telecommunications engineer by training, Azimath Olayemi Adjassa has spent more than fourteen years working across digital infrastructure, telecommunications and critical environments. Her areas of interest include the intersection of connectivity, Data Centers, digital sovereignty and artificial intelligence. She is a Data Center consultant and the founder of Infrapick, an advisory practice specializing in Data Center hosting decisions and capacity intelligence within the African infrastructure ecosystem. Her approach combines supporting organizations in making informed hosting decisions with improving the visibility of available infrastructure capacity for operators. Her ambition is to bridge the gap between user requirements and the operational realities of the industry, while contributing to a more transparent and accessible market—one where investment, hosting and development decisions are driven by reliable data and a shared understanding of critical infrastructure challenges. ![](https://storage.ghost.io/c/ae/a9/aea9a5ed-e74c-4627-a437-7db977568d2b/content/images/2026/10/1001100452.png)