Start with the operating requirement
An autonomy claim is meaningful only when load, battery, solar input, weather and operating schedule are recorded. Begin with the site, intended operation and authority requirements. Record assumptions beside the requested configuration so the supplier, integrator and installer are reviewing the same system. The article is a buyer's planning resource; final design, compliance and operating decisions remain project specific.
Information to define before quotation
| Field | What to record | Why it matters |
|---|---|---|
| System identity | Panel, battery, controller, signal loads and revisions | Defines the tested configuration |
| Starting condition | Battery voltage/state method and prior charge | Makes runs comparable |
| Operating load | Signal program, active heads and daily hours | Captures energy demand |
| Solar condition | Location, shading, orientation and weather record | Captures available input |
| Result | Run time, minimum voltage, alarms and recovery | Shows what the system actually did |
Use a controlled review sequence
- System identity: Panel, battery, controller, signal loads and revisions Defines the tested configuration
- Starting condition: Battery voltage/state method and prior charge Makes runs comparable
- Operating load: Signal program, active heads and daily hours Captures energy demand
- Solar condition: Location, shading, orientation and weather record Captures available input
- Result: Run time, minimum voltage, alarms and recovery Shows what the system actually did
Give every important item an owner and a document reference. Where a value comes from a drawing, tender, authority instruction or product datasheet, identify that source and revision. Mark unresolved items rather than filling gaps with a catalogue assumption.
Build acceptance around observable evidence
Translate the approved requirements into checks that an independent witness can repeat. State the test setup, equipment identity, initial condition, expected result, measured or observed result and any deviation. Keep photographs, data exports and signed records with the relevant model, firmware or drawing revision.
A passing result for one configuration does not automatically cover a different voltage, optical assembly, interface, battery, mounting arrangement or software release. Define which differences require a document review, sample approval or repeated test.
Common specification mistakes
- Reporting days of autonomy without the test load
- Comparing battery voltage from different measurement methods
- Ignoring low-energy alarms and recovery after sunlight returns
These errors usually appear when a quotation is based on a short product name instead of a system description. A clear schedule and acceptance record reduce rework during sample approval, production and commissioning.
Prepare the supplier enquiry
Send the project location, intended use, quantity, destination, applicable tender or standard, required interfaces, operating conditions and requested documents. Ask the supplier to identify confirmed items, options and exceptions in writing. For GAOQIAO catalogue options, start from the relevant product category and request the current drawing and data for the exact offered model.
Frequently asked questions
How many days of autonomy should a solar signal have?
The required value depends on the project climate, load and service plan. Calculate and verify it under defined conditions.
Is open-circuit battery voltage enough?
No. Use the battery manufacturer and system method agreed for the project, and record measurement conditions.
What should accompany the test log?
Include configuration, instruments, timestamps, weather or irradiance source, events and any deviations from the procedure.