An integrated Owner’s Engineer approach managed by Clarion.Engineer
Renewable-energy projects are often presented initially through a small number of headline figures: installed capacity, expected annual production, grid-connection capacity and an indicative capital cost.
A wind project may be described as 150 MW. A solar project may be presented as 200 MWp. A battery project may be specified as 50 MW / 100 MWh. A hybrid development may combine all three technologies behind one grid connection.
Those figures describe the scale of an opportunity. They do not yet define an investable project.
Before a developer can run a credible tender, approve an investment case or approach lenders, the project must answer a much broader set of questions. The design basis must be established. Site and grid constraints must be understood. Technology interfaces must be allocated. Performance guarantees must be measurable. Capital costs must be built from quantities and scope rather than headline supplier prices. Permits, environmental obligations, schedule dependencies and commissioning requirements must be integrated into one delivery strategy.
This is the commercial purpose of Front-End Engineering Design, or FEED.
Under the Clarion.Engineer delivery model, FEED is managed as an integrated Owner’s Engineer process covering engineering, commercial definition, cost, schedule, risk, procurement and lender readiness. The objective is not to produce drawings for their own sake. It is to convert an early-stage opportunity into a project that can be priced, contracted, financed, constructed, commissioned and operated with clearly allocated risks.
FEED is a commercial risk-reduction process
The cost of changing a project is lowest during development and highest after equipment has been ordered or construction has started.
A design issue identified during FEED may require an engineering review and a revised specification. The same issue discovered during construction may require redesign, contractor claims, replacement equipment, additional civil works and a delayed commercial-operation date.
This makes FEED one of the highest-leverage investments available to a project sponsor.
A disciplined FEED process reduces uncertainty in five areas that directly affect project value:
- What is being built?
- What performance must it deliver?
- What will it cost?
- When can it reach commercial operation?
- Which party is responsible when something does not work?
Without clear answers, bidders include different assumptions and exclusions in their offers. The resulting prices may appear comparable while representing materially different technical solutions and risk allocations.
A low-cost offer may exclude grid-compliance studies, auxiliary systems, fire protection, plant controls, telecommunications, augmentation, testing or long-term software access. Another offer may include those elements but appear more expensive on a headline basis.
FEED establishes a common project definition so that suppliers compete against the same technical boundaries, operating conditions and acceptance requirements.
Wind, solar and BESS must be engineered as one project
Hybrid projects are not created simply by placing wind turbines, photovoltaic modules and battery containers on the same site.
Each technology has its own design requirements, operating profile, warranty framework and construction risks. They must also interact through shared systems, including:
- The grid connection and export limit
- The substation and electrical balance of plant
- The power-plant controller
- The supervisory control and data acquisition system
- The energy-management system
- Forecasting and market-dispatch platforms
- Metering and settlement systems
- Roads, drainage, security and communications
- Environmental permits and emergency-response procedures
The value of a hybrid project depends on the performance of the complete facility at the grid-connection point.
A 100 MW wind farm, an 80 MWac solar plant and a 50 MW BESS do not automatically create a facility capable of exporting 230 MW. The approved grid connection may be limited to 150 MW. The project must therefore determine how the technologies share that capacity and how the control system manages simultaneous production.
The battery may charge from excess renewable generation, support a nominated delivery profile, reduce curtailment or respond to market signals. It may also be required to preserve state-of-charge capacity for grid services or forecast-error correction.
These operating objectives can conflict. FEED must establish the hierarchy before equipment is procured.
Wind FEED: energy yield is only the beginning
For a wind project, commercial performance begins with the resource assessment, but it does not end there.
The FEED process must connect the wind-resource model to the selected turbine class, layout, wake assumptions, site access, foundation design, collector system and grid requirements.
A bankable wind workstream normally addresses:
- Measurement campaign quality and data recovery
- Long-term correlation and uncertainty
- Turbine suitability for the site wind regime
- Extreme wind, turbulence, temperature and icing
- Wake losses and layout optimisation
- Availability and electrical-loss assumptions
- Noise, shadow flicker and environmental constraints
- Transport routes, abnormal loads and heavy-lift logistics
- Foundation and crane-pad concepts
- Medium-voltage collector-system architecture
- Power-plant controller and SCADA requirements
- Grid-code performance and reactive-power capability
A turbine with an attractive unit price may create higher project costs if it requires more substantial foundations, difficult transport arrangements or a collector-system redesign.
Similarly, a layout that maximises theoretical production may not be commercially optimal where it increases road construction, cable length, environmental impacts or wake losses.
The Owner’s Engineer must therefore evaluate the full project outcome rather than a single equipment parameter.
Solar FEED: the lowest module price is not the project strategy
Solar projects are often viewed as relatively standardised, but their commercial performance remains highly sensitive to engineering choices.
FEED must establish the relationship between the DC array, AC export capacity, inverter architecture, site conditions and grid connection.
The core solar workstream includes:
- Resource and energy-yield assessment
- Site topography and grading requirements
- Geotechnical and pull-out testing
- Flooding, drainage and erosion control
- Fixed-tilt or tracker selection
- Module and inverter technology
- DC-to-AC ratio
- Clipping and curtailment assumptions
- Row spacing, shading and terrain losses
- Soiling, cleaning and water strategy
- Cable routing and electrical losses
- Transformer and medium-voltage design
- Grounding and lightning protection
- SCADA and plant-controller integration
- Access, fencing, security and vegetation management
The optimum DC-to-AC ratio cannot be selected solely from equipment cost. It must reflect the resource profile, export limit, clipping, market prices, degradation, grid curtailment and any associated battery.
Where solar and BESS share an inverter, substation or connection point, the design must also define charging sources, metering boundaries and operating restrictions.
A lower initial price may therefore produce a higher lifetime cost where the design creates avoidable clipping, excessive grading, drainage problems or difficult maintenance access.
BESS FEED must begin with the use case
Battery procurement often starts too early with a request for a specific number of megawatts and megawatt-hours.
That approach can produce a technically compliant battery that is commercially misaligned with the project.
BESS FEED should begin by defining what the battery is expected to accomplish.
Potential functions include:
- Renewable-energy shifting
- Forecast-error correction
- Imbalance-cost reduction
- Curtailment recovery
- Negative-price avoidance
- Peak export management
- Capacity-firming
- Intraday trading
- Frequency and reserve services
- Voltage and reactive-power support
- Industrial peak shaving or backup support
Each use case creates a different requirement for power, duration, cycles, response time and state-of-charge availability.
A battery designed primarily for a two-hour energy-shifting window will not necessarily be optimised for continuous frequency response. A system used aggressively for merchant trading may consume its warranty throughput more quickly than assumed in the financial model.
The FEED process must therefore align four models:
- The commercial dispatch model
- The battery degradation model
- The supplier warranty
- The project financial model
This alignment is fundamental.
A supplier may offer a 15-year warranty, but that warranty may contain limits on annual throughput, temperature, depth of discharge, charging rate and state-of-charge range. A financial model that assumes more aggressive operation than the warranty permits is not a bankable operating case.
BESS FEED should also address:
- Cell chemistry and reference fleet
- Power and energy configuration
- Usable rather than nominal capacity
- AC-to-AC round-trip efficiency
- Auxiliary consumption
- Thermal management
- Degradation and state-of-health guarantees
- Planned augmentation
- Power-conversion-system capability
- Overload and reactive-power performance
- Fire detection and thermal-runaway propagation
- Container spacing and emergency access
- Gas detection and ventilation
- EMS and SCADA integration
- Cybersecurity and remote access
- Factory and site testing
- Data ownership and software continuity
- Recycling and end-of-life obligations
The result of this work is not simply a battery specification. It is a lifecycle operating strategy.
The grid connection is a project-wide constraint
The grid connection is frequently the most important shared interface in a renewable or hybrid project.
It determines how much power can be exported, how much electricity the battery may import, what voltage and reactive-power performance must be maintained and how the facility responds during grid disturbances.
Grid FEED typically includes:
- Connection-application support
- Load-flow analysis
- Short-circuit analysis
- Harmonic and flicker studies
- Reactive-power capability
- Voltage-control philosophy
- Fault-ride-through studies
- Dynamic modelling
- Protection coordination
- Metering and settlement design
- Telecommunications and dispatch
- Auxiliary-power arrangements
- Grid-compliance testing
A hybrid facility introduces additional control questions.
The plant controller must coordinate wind, solar and BESS output while respecting the connection limit. It must determine which technology is curtailed when the export limit is reached and how the battery responds to renewable variation, market commands and grid instructions.
This hierarchy should be engineered and tested before commercial operation. It should not be left for different vendors to resolve independently during commissioning.
Clarion.Engineer as the owner-side technical integrator
In an integrated FEED model, Clarion.Engineer acts as the owner-side technical integrator.
This role extends beyond checking vendor drawings. It connects the project’s investment objectives to the engineering, procurement and construction strategy.
The Owner’s Engineer manages the relationship between:
- The sponsor and project company
- Resource and energy-yield advisers
- Wind and solar equipment suppliers
- The BESS manufacturer and integrator
- Civil and electrical contractors
- The grid operator
- Control-system and software providers
- Permitting and environmental advisers
- Traders and offtakers
- Insurers
- Lenders and their technical advisers
No individual supplier has responsibility for optimising the complete project on behalf of the owner.
A turbine supplier focuses on the turbine package. A solar EPC contractor focuses on the photovoltaic plant. A BESS supplier protects its battery and warranty. A grid contractor delivers the connection scope. A trader focuses on market performance.
Clarion.Engineer manages the interfaces between these packages and tests whether the combined solution meets the owner’s technical and commercial objectives.
From asset register to controlled project scope
The project-control process begins with a structured asset register.
Each wind, solar, BESS, grid and shared-infrastructure asset is identified with its:
- Capacity
- Location
- Development phase
- Operating status
- Data maturity
- Target commercial-operation date
- Cost basis
- Technical dependencies
This provides a single capacity source for the project.
As the sponsor adds or revises megawatts, megawatt-peak or megawatt-hours, the project WBS, cost estimate, Owner’s Engineer scope and dashboard can be updated consistently.
This is particularly important for phased projects. A development may begin with 100 MW of wind and later add 80 MWp of solar and 100 MWh of storage. Each phase may use different contractors while sharing a substation, control system and grid agreement.
The asset register makes those changes visible and traceable.
The WBS converts engineering into a commercial estimate
A credible cost estimate must be built around a Work Breakdown Structure, or WBS.
The WBS separates the project into controlled packages such as:
- Development and land
- Surveys and resource studies
- FEED and Owner’s Engineer services
- Wind turbine supply
- Wind balance of plant
- Solar modules and inverters
- Solar civil and electrical works
- BESS supply
- BESS integration
- Grid connection
- Shared infrastructure
- Controls and communications
- Construction management
- Commissioning
- Insurance and owner costs
Each work package should have a defined quantity, cost method, unit rate, contingency, owner and evidence basis.
The estimate can then distinguish between:
- Supplier-backed pricing
- Quantity-based estimates
- Lump-sum allowances
- Percentage-based owner costs
- Risk contingency
- Uncommitted scope
This is more informative than a single €/MW or €/kWh benchmark.
A battery price of €250/kWh may refer only to the equipment supply. It may exclude power conversion, transformers, fire systems, foundations, cables, software, grid studies, testing, spares and augmentation.
Similarly, a solar or wind EPC price may exclude grid reinforcement, land, development expenditure, owner costs, insurance or financing-related requirements.
The WBS makes those exclusions visible.
Risk must be linked to cost and action
A project risk register should not be a static list prepared for governance meetings.
Each risk should identify:
- The affected asset or work package
- The cause
- The commercial or technical consequence
- The inherent probability and impact
- The proposed mitigation
- The responsible owner
- The residual probability and impact
- The early-warning trigger
- The associated cost contingency
- The required evidence for closure
This creates a direct relationship between engineering uncertainty and commercial contingency.
For example, an incomplete geotechnical campaign may justify a civil-work contingency. A pending grid study may justify schedule float and additional connection-cost contingency. An unproven BESS warranty may require a larger augmentation reserve or a lower revenue assumption.
As risks are reduced through studies, contracts or design development, contingency can be reviewed on an evidence-based basis.
FEED should lead directly into procurement
A successful FEED package provides the foundation for procurement.
Tender documents should define:
- Design and operating conditions
- Scope boundaries
- Technical specifications
- Net performance requirements
- Interfaces
- Documentation requirements
- Testing procedures
- Schedule milestones
- Warranty obligations
- Performance guarantees
- Delay and performance remedies
This allows bids to be evaluated on more than initial price.
The Owner’s Engineer can compare:
- Net power and usable energy
- Energy yield
- Efficiency
- Availability
- Degradation
- Auxiliary consumption
- Reference projects
- Construction methodology
- Schedule
- Exclusions
- Warranty conditions
- Long-term support
- Supplier credit
- Interface risk
- Lifecycle cost
The result is a procurement decision based on risk-adjusted project value rather than the lowest equipment quotation.
Lender readiness begins during FEED
Lenders do not finance equipment in isolation. They finance a project’s capacity to reach completion and generate reliable cash flow.
Technical due diligence will normally examine:
- Resource and energy-yield certainty
- Grid connection
- Design maturity
- Technology bankability
- Capital cost and contingency
- Construction schedule
- Contract structure
- Performance guarantees
- Operations and maintenance
- Permits and land rights
- Environmental and social obligations
- Insurance
- Commissioning and acceptance
For BESS, lenders will also focus on degradation, augmentation, fire risk, software dependence and whether the assumed revenue streams are genuinely accessible.
A lender-ready FEED process maintains a due-diligence tracker and conditions-precedent register before financing begins. This allows the sponsor to identify gaps early rather than receive them as late-stage lender objections.
Clarion.Engineer supports this process by ensuring that technical assumptions remain consistent across the design, cost estimate, contracts, schedule and financial model.
FEED should operate through measurable stage gates
A controlled project does not move forward merely because engineering activity has taken place. It moves forward when defined evidence is available.
A typical stage-gate structure includes:
- Strategy: The project objectives, ownership, use cases and procurement strategy are approved.
- Feasibility: Land, resource, site, grid and commercial constraints are sufficiently understood.
- Pre-FEED: The preferred technical concept and grid strategy are selected.
- FEED: The design basis, layout, electrical architecture, controls, cost, schedule and risk allocation are mature enough for tender.
- Tender: Compliant bids have been evaluated and contract risks are understood.
- Financial close and notice to proceed: Land, permits, grid rights, contracts, financing and sponsor support are effective.
- Construction: Design, quality, safety, cost, schedule and change control are operational.
- Commissioning: The integrated project demonstrates contractual performance at the agreed measurement point.
Each gate should have a readiness score, mandatory deliverables, critical blockers and documented approval.
What a Clarion.Engineer-managed FEED process delivers
The commercial value of FEED is not limited to better engineering documentation.
A fully integrated process produces:
- A defined and internally consistent project scope
- A controlled asset and capacity register
- A Basis of Design
- Technology-specific engineering requirements
- Grid and control-system architecture
- A structured WBS and cost estimate
- A credible integrated schedule
- A quantified risk and contingency framework
- An interface-responsibility matrix
- Tender-ready technical specifications
- Comparable supplier bids
- Bankable performance and testing requirements
- A lender-readiness and CP tracker
- A construction-monitoring and commissioning plan
These outputs reduce the number of unresolved assumptions transferred into EPC contracts and financing documents.
They also give the sponsor a stronger negotiating position. When the owner understands the scope, interfaces and performance boundaries, it is less dependent on supplier interpretations.
Engineering quality becomes commercial performance
Wind, solar and BESS assets are becoming more technically standardised, but projects are not.
Sites differ. Grid conditions differ. Revenue strategies differ. Contracts differ. Permits, logistics and lender requirements differ.
The competitive advantage therefore lies increasingly in how the project is integrated and delivered.
A strong FEED process does not seek the most elaborate design. It seeks the most commercially effective design: one that meets the project’s operating objectives, allocates risks to parties capable of managing them and preserves flexibility without unnecessary capital expenditure.
Managed through an integrated Owner’s Engineer framework, Clarion.Engineer connects engineering decisions to investment outcomes.
The final product is not simply a set of drawings or a technical report.
It is a project definition that can be tendered with confidence, financed on defensible assumptions, constructed with controlled interfaces and accepted against measurable performance.
That is the commercial purpose of FEED.