Choose a telecom solar power system by testing each proposal against the same load, source availability, reserve target and site conditions. Set aside offers that cannot meet mandatory requirements or still lack the information needed to decide. Then compare the qualifying systems on operating margin, maintainability, monitoring and lifecycle cost, using priorities agreed before the bids arrive.
A useful solar bid comparison follows the load through the conditions the site must survive. Two offers with similar solar-panel and battery ratings can behave differently during a low-solar period, source loss or battery recharge. A lower equipment price becomes relevant only after the proposed system can perform the required duty.
Give every bidder the same site case
The comparison starts with one operating case issued to everyone. It should describe what must remain powered, the sources actually available and the conditions under which the design must work. Suppliers can propose different equipment arrangements, but they should not silently change the task being purchased. If the source arrangement is still open, use the telecom solar architecture guide to settle that decision before treating the offers as directly comparable.
- Load and electrical interface: identify continuous, peak and startup demand, essential auxiliaries, permitted interruptions, load-terminal voltage limits and committed growth.
- Energy and reserve duty: state the solar-resource basis, shading and loss assumptions, source-outage scenarios, required reserve and the time available to restore it.
- Site and service conditions: provide temperature and altitude conditions, available space, access restrictions, expected technician capability and the required response to faults.
- Purchase and evaluation basis: define the delivered installation, retained assets, evaluation period, acceptance cases and the cost assumptions used for comparison.
These inputs become the common reference for the supplier’s calculations. For example, a proposal that excludes cabinet cooling from its load model cannot be compared directly with one that includes it. Return both to the same load definition before judging their solar or battery capacities. Use the telecom solar and battery sizing guide for the detailed capacity method; the task here is to compare results produced for the same inputs.
That system-level view is consistent with ITU-T L.1210 (12/2025), which considers service availability, reliability, backup, safety and environmental conditions in access-network power feeding. The buyer still needs project-specific requirements. The qualification and scoring method below is a purchasing framework, not an ITU certification or a scorecard prescribed by the Recommendation.
Which proposals should be excluded before scoring?
Exclude an offered configuration when it demonstrably cannot meet a mandatory requirement. Hold a proposal when the result is unknown or its assumptions do not match the issued site case. Only a proposal with the required compatibility and substantiated operating cases should enter the weighted comparison.
Apply this decision to the proposed system as a whole. A large battery cannot compensate for an unacceptable load interface, and a low price cannot compensate for an unresolved safety requirement. The following checks identify the differences that must be settled first:
- Can the loads accept the delivered power? Compare voltage at the load terminals, polarity, continuous and transient capability, and the specified transfer or interruption behaviour.
- Does reserve remain usable under the stated conditions? Compare storage available to the required loads at the same temperature, permitted operating window and agreed end-of-life condition. Nameplate energy alone is insufficient.
- Can the system recover while supplying the site? Check that source and conversion limits allow the defined load and recharge duty together, within the agreed recovery window.
- Does the offered configuration fit the site safely? Check qualified environmental conditions, installation space, service access, protection and the requirements applicable to the project.
- Do the defined failure cases produce acceptable load outcomes? Review the required source-loss, component-outage and communications-loss cases, including restoration. Match the evidence to the configuration offered.
A revised offer can be reconsidered after the supplier resolves the issue. Record the changed configuration and rerun the affected checks before scoring it. A short backup demonstration or an annual energy total, by itself, does not establish performance across all required operating cases.
Put the qualifying results on the same basis
Passing the mandatory checks establishes eligibility; it does not make the offers identical. The remaining comparison concerns benefits that matter at this site, such as useful operating margin, easier restoration or better fault visibility. Ask what each difference changes for the operator rather than rewarding a larger catalogue number.
For usable battery reserve, keep the temperature, age condition, losses, protected load and recovery assumptions alongside the result. A beginning-of-life estimate at a favourable temperature should not outrank a more conservative estimate made for the required end-of-life duty. Similarly, extra PV capacity has value only if space, conversion capacity and the operating strategy allow the site to use it.
Maintenance and monitoring should be compared in practical terms. Can the available team replace the offered module through the planned access? Does a fault require a specialist visit or a locally supported action? Can the operator distinguish loss of a source from a battery limit or a failed communications link? A statement that remote monitoring is available does not answer those questions.
Normalize the financial comparison with equal care. Include the costs of reaching the same installed and operating condition, then compare energy, maintenance, replacements and any residual or disposal value over the same period. Keep currency, cost date, escalation and discount assumptions consistent. NIST Handbook 135, 2020 edition, explains the life-cycle costing method, including initial and future costs. Its U.S. federal programme assumptions are not automatically the correct rates or rules for another project.
This lifecycle cost comparison should expose uncertainty rather than bury it. If one offer assumes no battery replacement while another includes one, establish whether the difference follows from the same duty and supporting life assumptions. Test the effect of plausible changes before treating the lower total as a reliable advantage.
Once these differences are understood, choose a small set of scoring criteria. Avoid counting the same benefit twice: priced travel and routine maintenance belong in cost, while the maintenance score can address service practicality, restoration and the skills required. The following example shows how that distinction affects a selection.
A worked comparison for a site with difficult maintenance access
Consider a hypothetical telecom procurement in the Philippines. Three anonymous proposals are evaluated for the same site case. Proposal A predicts load-terminal voltage outside the required equipment input range during the specified recovery state, so its offered configuration fails qualification. Proposals B and C are assumed to pass all mandatory checks. These are teaching assumptions, not actual supplier results or a reported Huijue project.
The operator set the weights before receiving the offers: operating margin 35%, maintenance fit 25%, monitoring integration 20% and evaluated lifecycle cost 20%. Ratings use a five-point preference scale: 1 is a weak fit, 3 an adequate fit, and 5 a strong fit; 2 and 4 are intermediate. These ratings apply only after qualification, and are not probabilities of successful operation.
For this example, B has an evaluated lifecycle cost index of 100 and C an index of 115, using the same agreed cost model. The cost rubric gives the lowest eligible cost 5 points; more than 0% through 10% above it earns 4; more than 10% through 20% earns 3; more than 20% through 30% earns 2; and more than 30% earns 1. The index and ratings are illustrative, not market prices or forecasts.
| Criterion | Weight | B rating | C rating | Reason for the example rating |
|---|---|---|---|---|
| Useful operating margin | 35% | 4 | 4 | Both provide the same demonstrated improvement above the mandatory operating requirement. |
| Maintenance fit | 25% | 3 | 5 | B is serviceable under the agreed plan; C better matches the local team’s skills, access and module-replacement method. |
| Monitoring integration | 20% | 3 | 4 | B provides the required visibility; C makes the specified fault conditions easier to distinguish in the operator’s monitoring workflow. |
| Evaluated lifecycle cost | 20% | 5 | 3 | B is the eligible cost reference; C is 15% higher on the same cost basis. |
Calculate each weighted contribution as weight × rating ÷ 5, with weights expressed as points summing to 100. B scores (35 × 4 + 25 × 3 + 20 × 3 + 20 × 5) ÷ 5 = 75 out of 100. C scores (35 × 4 + 25 × 5 + 20 × 4 + 20 × 3) ÷ 5 = 81 out of 100.
C leads by six points because its maintenance and monitoring advantages outweigh its cost disadvantage under the declared priorities. B’s lower cost is still visible; it has not been dismissed or hidden inside a generic technical score. Proposal A cannot re-enter the ranking merely by offering a lower price.
The worked ratings depend on the stated differences being substantiated. For a real comparison, define what earns each rating in the individual row: the operating margin that is useful, the service action the local team can perform, and the fault information available in the receiving monitoring system. An unsubstantiated improvement should not earn extra points. If a missing item affects a mandatory requirement, return the proposal to Hold.
What can change the preferred proposal?
The preferred proposal can change when the site’s priorities, verified performance or cost assumptions change. Test those dependencies before selection, while preserving all mandatory requirements. A weighted score supports a decision under stated conditions; it does not create a universal best system.
Keeping the example ratings fixed, test a different priority policy: 10% for maintenance and 35% for cost, with operating margin and monitoring weights unchanged. B would score 81 and C 75. Holding the ratings constant isolates the effect of the weights; a changed site could also require new ratings. This is a sensitivity illustration, not permission to change weights after seeing which supplier wins. Approve the priorities for the actual site before final ranking.
Also test uncertain inputs without pretending to know their exact probability. A higher expected replacement cost, a longer fault-restoration visit or a change in required reserve can alter the decision. Recheck eligibility if the changed condition affects a mandatory case. Small score differences that disappear under reasonable alternatives call for clarification rather than an artificially precise recommendation.
The final recommendation should therefore name the selected configuration, the requirements it meets and the assumptions that make it preferable. Close unresolved mandatory items before release; retain any remaining commercial or implementation conditions explicitly. Supplier-company due diligence and contract terms remain separate from choosing the technical system.
The same site case and priorities can guide a new or revised Huijue quotation. Our telecom equipment and engineering services cover configurable site-energy equipment, energy modelling and integration support. Ask the offer to show how its configuration addresses the required operating cases, so the resulting proposal can be assessed through the same qualification and scoring process.
Request a proposal against your operating case
Send the available load information, site location, source history, reserve objective and maintenance constraints. Identify retained equipment and any unknown inputs. Request a configuration that states its assumptions, performance against the required cases and an itemized cost basis, so it can enter the same comparison as the other offers.
Discuss a site-specific telecom solar proposal