Per-MW pricing, regional variance, and cost drivers for owners scoping hyperscale & AI builds.
Salary benchmarks across the 14 mission-critical disciplines.
_This is one of the biggest drug manufacturing builds in Indiana: more than _$13 billion_ in Lebanon alone, about 600 acres, roughly 12 major buildings, and first product tied to a late 2026 target._*
If I boil the full article down, the point is simple: this project is less about pouring concrete and more about getting API systems, utilities, controls, and GMP turnover ready in the right order. The main pressure points are schedule, hiring, shared utilities, equipment lead times, and the shift from construction into CQV and startup.
Here’s the article in plain English:
A short way to think about it: if clean steam, WFI, HVAC, controls, or turnover packages slip, the whole startup path can slide even if the buildings look finished. That’s why staffing has to track the project timeline just like equipment buys and field sequencing do.
This case study shows how a large GMP campus moves from sitework to startup - and where teams usually win or lose time.
The Lebanon campus is in the LEAP District, north of Lebanon and east of I-65. The site is built around two manufacturing parcels: LP1 and LP2. They serve different roles, but both run on the same shared utilities and controls backbone.
LP1 includes four manufacturing buildings, 10 support buildings, plus a central tank farm and solvent recovery area [5]. LP2 is smaller. It centers on one main building that combines production, office, utility, and warehousing functions [5][7]. Fluor is delivering LP1, while Jacobs and Messer Construction are delivering LP2 [6][3].
The site goes beyond those two parcels. It also includes QC and analytical labs, GMP warehousing, offices, a fire station, and central utility plants [7].
The building count matters because LP1 carries a heavy process load. LP1 is being built for tirzepatide synthesis. Since tirzepatide is a 39-amino-acid peptide, production relies on SPPS, large reactors, solvent-handling systems, chromatographic purification skids, ultrafiltration/diafiltration equipment, and CIP/SIP systems under GMP control [8][10].
That setup isn't simple. It drives demand for process engineering, automation, and CQV teams across the whole program.
Both parcels also depend on a long list of site utilities: purified water and WFI loops, steam, compressed air, specialty gases, and HVAC systems that hold pressure and classification control [4][5][10]. Those systems shape most of the MEP and automation work across the campus.
On top of that, the site needs DCS, PLCs, SCADA, MES, data historians, and environmental monitoring systems [10]. Each one has to be commissioned, qualified, and validated before production can start.
Eli Lilly Lebanon Campus: GMP Buildout Phases & Key Milestones
Delivering Lebanon is a multi-year program, not a one-and-done build. Fluor is coordinating design, procurement, and construction across LP1 and LP2 [2], with first medicines targeted for late 2026 and ramp-up through 2028 [11]. Core construction usually takes 12 to 18 months, and CQV plus startup can add another 9 to 18 months [14][15][16]. That timeline is why the workforce stays broad and steady across each stage.
The work starts well before crews show up in the field. In preconstruction, design teams, contractors, and key equipment vendors sort through front-end planning, conceptual and basic design, early procurement, constructability reviews, risk workshops, room classifications, equipment lists, utility tie-in points, and the integrated master schedule (IMS). On a campus with shared utilities and more than one production block, that early coordination matters a lot [2].
Here’s a simple way to think about it: fixing a clash between a structural beam and a large-diameter process pipe in a 3D model is a lot easier than fixing it after fabrication and field installation.
IDEM permitting records show staggered construction commencement dates across the Lebanon site - December 11, 2025 for one facility element and June 6, 2026 for another [12][13]. That points to deliberate phasing, not one giant start date. Site development, underground utilities, foundations, and structural steel for critical-path buildings usually move first. Then the building enclosure follows, timed to protect interior work from Indiana winters.
MEP rough-in runs alongside process equipment installation, but the sequence has to stay tight so overhead utilities - cable trays, then process piping, then HVAC - don’t force rework. Production-critical spaces like API synthesis suites are often pushed ahead of support buildings to protect regulatory and launch timelines.
Mechanical completion isn’t the finish line. It’s more like a handoff. After that, CQV and startup move through a set path: FAT, SAT, IQ, OQ, PQ, computerized systems validation, operator training, performance runs, and regulatory readiness [14][15][16].
FATs happen at vendor sites before equipment ships. They check function and documentation before the skid ever arrives in Lebanon. SATs confirm the equipment works once it’s installed and tied into plant utilities. IQ shows the installation matches design specs. OQ tests whether systems run across defined ranges. PQ shows steady performance under actual process conditions [14][15][16].
If a critical utility like clean steam slips during installation, commissioning can’t start on time, and validation gets pushed back too [14][15][16]. That’s why teams build buffers and contingency into the IMS, especially when construction and CQV overlap. During heavy construction, the big risks are weather, supply chain delays, and field clashes. During CQV, the pressure shifts to documentation gaps, software integration problems, and failed protocols that can delay product release even when the building looks finished.
System-by-system turnover packages - drawings, weld logs, calibration records, and MC certificates - help keep CQV from bogging down [14][15][16].
Those phase controls tie straight to the staffing mix the project needs on the ground.
Once the delivery sequence is locked, the next issue is ownership. Who handles each handoff, and when? On the Lebanon campus, that matters a lot because the work is split across several parallel tracks. The staffing plan has to fit LP1, LP2, and the shared site systems that tie both together. Fluor leads LP1. Jacobs and Messer Construction lead LP2. Each role group owns a different part of the handoff chain.
Project managers own cost, change, and milestone recovery. Day to day, they make scope trade-offs and decide when work needs to speed up to protect mechanical completion or GMP readiness. If one area slips, they decide what gets resequenced, what gets added, and what can wait.
Schedulers keep the integrated master schedule lined up across construction, turnover, and CQV. That schedule is built in Primavera P6, with links across civil work, building shells, MEP rough-in, cleanroom fit-out, equipment installation, and CQV gates. With peak construction employment expected to reach about 5,000 workers in 2026 [6], schedule coordination isn't just an admin task. It shapes whether CQV teams can start when systems turn over, or sit idle waiting on late work.
CSA and MEP superintendents run field sequencing every day. They release work areas to trades, enforce permit-to-work systems, and coordinate high-risk lifts for large process vessels and utility skids. Just as important, they set the system turnover plan. In plain terms, they decide how the campus gets broken into turnover packages for progressive handoff to CQV. That choice has a direct effect on how cleanly validation begins and how much rework shows up right at the construction-to-commissioning edge.
From that point, the focus moves away from schedule control and toward system readiness.
Civil, structural, and architectural (CSA) teams own the building backbone for both manufacturing and support spaces. In GMP settings, that goes well past concrete and walls. It includes layouts that control personnel and material flow, support airlocks and gowning needs, and meet cleanroom classification targets for API synthesis suites.
MEP coordination sits near the center of the site effort because the campus depends on classified HVAC, clean utilities, and highly reliable power distribution. MEP leads manage clean steam, purified water, WFI, process gases, and electrical systems that can support multiple API trains running at the same time.
CQV engineers own the handoff from construction into operations. They build qualification plans for critical systems, write and run protocols, and define what documentation construction teams must provide before turnover is accepted. On a campus aiming for medicine production toward the end of 2026 and then ramping through 2028, CQV teams need to sequence validation so API utilities and critical process systems come first. [11][1]
Automation and controls specialists configure the DCS and PLC-based systems that hold temperature, pressure, flow, and differential pressure within GMP limits across classified spaces and process trains. They also connect process automation with MES and electronic batch record systems, while helping CQV with software validation, loop checks, and data integrity. [9]
Process engineers manage tech transfer, set process parameters, and support performance qualification batches that show the process is stable before commercial manufacturing starts. [11][1]
Procurement teams on the Lebanon project have to act early. Lead times for core process equipment - peptide synthesis skids, WFI generation systems, clean steam generators, and large-scale HVAC units - can run for many months. One late skid can push CQV back and eat up float that was meant to cover other risks. [18][19]
That puts a lot of pressure on procurement sequencing. Design freeze, purchase order, FAT, shipping, and SAT dates need to be set early and built straight into the P6 master schedule so they show up on the critical path. Procurement teams also time deliveries so equipment arrives when the building can actually receive it and when CQV staff are in place to start work. [6]
Owner's representatives and facility project managers often end up being the people who decide whether the plant is ready for GMP use on time. They handle vendor coordination, drawing revision control across multiple buildings, and documentation completeness in ways contractor teams - focused on their own scope - can't always put first. Strong owner-side staffing keeps vendor coordination, drawing control, and turnover moving together across both parcels.
Those staffing pressures shape the hiring plan in the next section.
Once the role map is in place, the next issue is timing: when each discipline needs to arrive on the jobsite. On a campus like Lebanon, staffing demand tends to follow a clear pattern tied to the project phase.
Workforce demand usually moves through four main windows. Early on, the focus is on senior project managers, schedulers, and cost managers who lock down scope and the integrated master schedule. As site work picks up, field execution leads become the priority across LP1, LP2, and shared infrastructure. At peak MEP installation, attention shifts to sequencing process utilities, clean utilities, and HVAC inside tight GMP spaces. Then, as systems near mechanical completion, CQV, automation, and process engineering leads need to be ready.
The big point here is simple: those late-stage roles need to be sourced far earlier than many teams expect. CQV roles usually take 5 to 7 years of experience to build[20][17]. On a timeline like this, that means scarce talent has to be handled almost like long-lead equipment procurement. Set target fill dates. Put them into the resource plan. Start the search early.
That also means hiring criteria matter just as much as headcount.
For project managers and superintendents, look for prior delivery of multi-building GMP campuses, performance against schedule-critical milestones, and cross-functional coordination across CSA, MEP, CQV, and operations. Plain construction leadership often falls short in a regulated setting, where turnover packages and documentation standards feed straight into validation.
For CQV, automation, and process engineering senior hires, screen for full CQV involvement from URS review through PQ execution, hands-on work with platforms like DeltaV, and direct exposure to batch control, electronic records, and data integrity compliance. Process engineers should bring experience scaling API processes and turning process intent into validated control strategies. When those markers are there, projects often run into fewer late-stage design changes, smoother protocol approvals, and a shorter path from mechanical completion to regulatory inspection[17].
Some roles are just plain hard to fill, especially senior CQV managers, automation architects, and multi-building MEP leads. In those cases, a specialized recruiting partner can shorten the search by bringing prequalified candidate slates already screened for the kind of profile a Lebanon-scale site calls for.
For Lebanon-scale projects, hiring strategy starts to look a lot like schedule control.
The Lebanon campus stays on schedule only when the right people are in place at the right time across construction, CQV, automation, process engineering, and supply chain. The clearest takeaway is this: hiring for large life sciences projects has to follow the project schedule, not the other way around. Programs that treat staffing as a formal project controls function, using resource curves, phased hiring windows, and early outreach for scarce roles, will be in a much stronger position than teams that wait until the need turns urgent.
CQV matters because it’s the documented process that shows a facility and its systems perform to spec. That proof is a must for FDA audit readiness and GMP production.
Put simply, CQV connects construction completion to day-to-day operational readiness. It’s the step that turns “built” into “ready to run.”
If CQV gets pushed back or starts too late, problems stack up fast: documentation backlogs, compliance gaps, rework, and production delays. Start it early, and you’re far less likely to end up with systems that can’t be tested or a schedule that slips more than expected.
Startup delays usually come from documentation gaps, not equipment breaking down.
The biggest choke point is an incomplete Commissioning Turnover Package (CTOP). That often means things like missing weld logs, absent calibration records, or system tags that don’t match from one document to another. On paper, those may look like small issues. In practice, they can hold up handover and slow the entire startup sequence.
The systems most likely to create delays are:
That last group often causes trouble when CSV testing gets stuck and slows later phases.
Late-stage GMP roles, especially qualification and validation jobs like validation specialists and QA/QC leads, should be brought in during qualification and turnover. That gives them time to support execution, close protocols, and get the site ready for audits.
The timing matters. Hiring shouldn't be tied only to the last project phase. It should be based on documentation volume and utility complexity too. A site can look close to the finish line on paper while the workload behind the scenes is piling up fast.
There’s also a simple staffing reality: senior mission-critical roles can take 90 days or more to fill. If you wait until construction ends, you're often already behind. That delay can lead to backlogs, missed readiness milestones, and added regulatory risk.
