An enquiry arrives. It usually contains a load figure, a location, a deadline and a request for price. The useful question is not how quickly that price can be produced, but whether the information in the enquiry is sufficient to design from – and if it is not, which specific gap has to be closed first.
This is the part of a power project that is hardest to see from outside, and it is where most of the risk is either absorbed or passed downstream. What follows is how that review actually runs at YURI POWER, what the engineering team asks for and why each answer changes the design.

What Actually Arrives
Enquiries reach us in very different states, and the state of the enquiry decides how much work has to happen before anything can be quoted responsibly.
At one end is a full tender package: a bill of quantities, a single-line diagram, a technical specification, load data and site information, sometimes with drawings of an existing installation. Where a project has been through detailed design, this material is often good enough to design against directly, and the work becomes verification and equipment matching rather than architecture.
At the other end is a paragraph: a site in a country, a load in kW, and a request for a price. This is a legitimate starting point – many projects begin before the engineering has been funded – but it does not describe a system. What it describes is an intention. Between those two extremes sits the majority of enquiries, with partial information: a load figure without the profile behind it, a battery capacity without the power rating that goes with it, a site described by application rather than by conditions.
The first thing we do is not analyse the project. It is to establish which of these three states the enquiry is actually in.
Step One: Is There Enough Information to Design From?
A design can proceed when four things are known: how much power the load needs at its worst moment, how much energy it consumes over a day, when during the day that consumption falls, and what the site’s power source can and cannot do. Everything else refines the answer.
If those four are present, the work moves forward. If any is missing, the enquiry needs a question back before it can be quoted – and the question is specific, not general. “Please provide more information” is not a useful reply. “The peak load is given as 800 kW but the average load is missing, and the difference between them determines whether this system is generation-limited or storage-limited” is.
This is the point at which we decline to quote. Not because the project is unattractive, but because a price produced without load data is a number whose accuracy nobody can assess – and the cost of discovering that it was wrong falls on the project rather than on whoever produced it.
The Questions We Ask, and What Each One Changes
Most of the technical brief exists because each field moves a specific decision. It is worth setting out which.
Peak load or required capacity sets the rating of everything downstream. Inverter and PCS rating, transformer capacity, switchgear rating and generator size all follow from the worst instantaneous demand, not from the average. Size this too low and nothing else in the system can compensate for it.
Average load determines how much energy actually has to move across a day. The gap between peak and average is the single most informative ratio in the enquiry: a site whose peak is close to its average has a nearly flat load, which is straightforward to serve. A site with a sharp, short peak has equipment that must be rated for a demand it meets briefly – and storage becomes far more attractive, because it can carry that peak without every upstream component being sized for it.
Daily energy consumption sets the battery capacity once the required duration is decided. It is also the number most often missing, and the one most often confused with capacity. A battery rated in kWh stores energy; whether it can deliver it fast enough is a separate question answered by its power rating in kW.
Operating hours decide whether solar can be a primary source or only a partial one. An eight-hour shift load sits inside the solar day and can be served largely from PV. A continuous twenty-four-hour load cannot – the array produces nothing for roughly half of it, and something else has to carry the site through the night.
When the peak occurs matters as much as its size. The same 800 kW peak is a different system if it lands at 14:00, when the array is producing, than if it lands at 22:00, when the battery and the generator are the only things available. Load profiles that are only summarised as a peak and an average hide this entirely.
System voltage and frequency fix the transformer ratio, the switchgear ratings and whether 50 Hz or 60 Hz equipment is required. They also determine whether an existing installation’s equipment can be reused in a retrofit or has to be replaced.
Current power source establishes whether the project is greenfield, a retrofit or an expansion – and, in a retrofit, what has to keep running while the new system is built around it. A mine that cannot stop producing during installation is a different engineering problem from a new site.
Existing equipment and grid conditions determine the architecture. Feeder capacity, reliability of supply, whether reverse power flow is permitted, voltage tolerance and the local connection rules decide whether the system is grid-tied, off-grid or hybrid – and whether export is an option or a complication.

Turning Answers Into a System Concept
Once the inputs are in place, the work becomes a sequence of narrowing choices.
The first is architecture: grid-tied, off-grid or hybrid. This is decided by the grid’s reliability and the cost of an outage, not by preference. A site with a dependable connection and a modest backup requirement is not the same project as a site whose connection cannot carry its load, even where the load figures match.
The second is the split between generation and storage. The question is how many hours the system must run without its primary source, and what carries the load in that window. That duration figure drives battery capacity more than any other input, and it is usually the number a client has the least basis for estimating – which is why we treat it as an engineering output rather than an input to be accepted.
The third is the operating strategy: what the EMS is instructed to optimise. Lowest fuel consumption, longest battery life, maximum solar utilisation and highest reliability all point at different dispatch rules, and a system designed for one will underperform against another. This is a choice the owner has to make explicitly, because it cannot be inferred from the load data.
Only after those three are settled does equipment selection begin.
Where the Design Usually Has to Push Back
Some enquiries contain a specified solution rather than a requirement, and part of the engineering review is saying when the two do not match.
A battery specified in kWh without a power rating. Capacity and power are independent. A system with enough stored energy but insufficient discharge rating will still fail at the moment of peak demand – the battery has the energy, but cannot release it fast enough. Both numbers have to be specified, and one cannot be derived from the other.
A system sized on peak load alone. This produces a system that meets the worst moment and runs out of energy on an ordinary day, because the daily consumption was never reconciled with the generation and storage available.
An assumption that storage removes the need to upgrade a transformer. It does not. The transformer still has to carry the peak, and the peak is unchanged by the presence of a battery behind it unless the architecture is specifically designed to shave it – which is a different design decision and has to be made deliberately.
A generator sized to carry the entire load. This is technically safe and frequently uneconomic. A large generator running at a low load fraction burns fuel inefficiently and wears faster, and in a hybrid system it is often better to let storage carry the peaks while a smaller generator runs closer to its efficient band. This is the reasoning behind retrofitting an existing diesel installation rather than replacing it with a larger one.
None of this is an argument against a client’s stated requirement. It is a statement about what the requirement will do when it is built, which is more useful before the order than after.

What You Receive, and What It Does Not Commit To
The output of this process is a system concept: an architecture, a capacity and configuration, an equipment list matched to it, and the technical documentation that goes with it. Every element in it can be traced back to a stated input, which is what makes it reviewable rather than merely acceptable.
What it does not do is commit to final specifications. Model selection, certification, scope of supply and suitability are confirmed against approved technical documents, the commercial contract and the regulations in force where the project is built. Those are not the same thing, and treating a concept as a commitment is how projects end up with an equipment list that no longer matches the site.
The point of the whole exercise is narrower than it might appear: to reduce project risk before equipment reaches the site. A design error caught during review costs a spreadsheet revision. The same error caught during commissioning costs a schedule.
If you have an enquiry at any of these stages – a full tender package or a paragraph – send it through the system proposal form with whatever is known and the rest marked as to be confirmed. For the company context behind this process, see how our design, manufacturing and support functions fit together, and for what happens after the concept is agreed, the equipment and integration side of a hybrid project.
FAQ
Q: Do you quote directly from an RFQ, or is there a review first?
A: There is a review, and how long it takes depends on the state of the enquiry rather than on its size. Where a project has been through detailed design and the tender package contains load data, a single-line diagram and a technical specification, the review is verification and equipment matching and can move quickly. Where the enquiry contains a load figure without the profile behind it, the process stops at a question back – because a price produced without load data is one whose accuracy cannot be assessed by anyone, including the party who produced it.
Q: What is the minimum information needed to start?
A: Four things: peak load or required capacity, average load, daily energy consumption, and what the current power source is and what it can do. Those four establish whether the system is generation-limited or storage-limited, and they determine the architecture. Everything else – solar capacity, battery capacity and backup time, generator capacity, transformer and switchgear requirements – refines an answer that those four make possible. Estimated values are acceptable; unfilled fields can be marked as to be confirmed, and the review will identify which of them actually blocks progress.
Q: Why does the time of day a peak occurs matter?
A: Because it determines which source has to carry it. An 800 kW peak at 14:00 can be served substantially by a solar array at its production peak; the same 800 kW at 22:00 has to come from storage or a generator, because the array is producing nothing. A load summary that reports only a peak and an average conceals this entirely, and two sites with identical figures can require materially different systems. A load profile – even a rough one – removes most of that ambiguity.
Q: What if we do not know the battery backup time we need?
A: That is normal, and it is usually the number a client has least basis for estimating. Backup duration is set by how long the site must run without its primary source, which is a question about acceptable downtime and the cost of an outage rather than about equipment. We treat it as an engineering output rather than an input to be accepted: the design work establishes what duration the load profile and the operating strategy imply, and the client then decides whether that is worth paying for.
Q: Can you work from a client’s own system design?
A: Yes, and it is a common arrangement. Where a design has been produced by the client’s own engineers or a third-party consultant, our role shifts to verification and equipment matching – checking that the specified equipment is consistent with each other and with the site conditions, and supplying against that specification with the documentation the project requires. We will still raise a concern if the specified configuration will not perform as intended, because the cost of that concern being correct is a conversation and the cost of it being ignored is a commissioning problem.
Q: How does a hybrid system differ from simply adding solar to a diesel site?
A: The difference is control. Adding solar to a diesel installation without coordinating the two means the generator and the inverter both try to regulate voltage and frequency, and the generator ends up running at low load fraction with the fuel consumption and wear that implies. A designed hybrid system sets out which source carries which portion of the load at which time, and configures the inverter, the generator’s paralleling controls and the energy management system to agree on it. The equipment may look similar; the operating logic is what makes it a system rather than a collection.
Q: What does the review deliver if the project does not proceed?
A: A system concept with traceable reasoning – architecture, capacity and configuration, and the inputs each element was derived from. That document has value independent of whether the project is built with us, because it establishes what the site actually requires and what a compliant proposal should contain. It is also the document that makes a competing quotation comparable, which is a reasonable thing for a project owner to want.
YURI POWER Engineering Team · September 30, 2026
