Vertical PV tube or flat panel: compare the project fit.
The two physical formats need different installation checks. Compare the proposed models against the site geometry, energy task, interfaces, documents and sample plan.
Compare both formats against the same project requirements.
Compare vertical PV and flat-panel options against the same site, load, mounting and document requirements.
Evidence limit
Xiuben Lighting’s public solar-energy material shows vertical photovoltaic formats and solar energy-system categories. This page does not state that any format produces more energy, fits every site, has a specified output, or is available for a particular project.
A matrix for the proposed vertical-tube and flat-panel configurations.
Record the offered values and documents for each named configuration; confirm any blank item before selection.
| Decision area | Vertical PV tube: request | Flat panel: request | Project record |
|---|---|---|---|
| Exact identity | Named model, revision, dimensions and factory-published configuration description. | Named model, revision, dimensions and factory-published configuration description. | Record the source date and unresolved differences. |
| Site geometry | Drawing showing location, height, clearances, orientation constraints and nearby obstructions. | Drawing showing location, support geometry, clearances, orientation constraints and nearby obstructions. | Attach site plan, photographs and owner constraints. |
| Energy task | Model-specific input/output information, assumptions and control/storage interfaces if supplied. | Model-specific input/output information, assumptions and control/storage interfaces if supplied. | State load profile, schedule, criticality and permitted downtime. |
| Mechanical interface | Mounting, foundation or pole interface, access and service drawing. | Mounting, support interface, access and service drawing. | Identify who designs and approves third-party supports. |
| Documents and sample | Current model/destination files and sample configuration for review. | Current model/destination files and sample configuration for review. | List document holder, scope, gaps and acceptance observations. |
What must the site team supply?
The project should state what physical and operational constraints are real before either format is narrowed. A photograph, plan and short load description are more useful than an unqualified preference.
- Space and access
Where may equipment sit, who needs access, and which routes or boundaries cannot be blocked?
- Sun and obstruction record
Provide the site location, time-based shading observations, nearby structures and planned changes around the installation.
- Load and operation
List connected loads, operating schedule, control behaviour, storage expectation and any interface controlled by others.
- Approval path
Identify the owner, designer, installer and reviewer for drawings, mounting, electrical connection, samples and documentation.
The selected configuration, before order.
Use the same acceptance criteria for each format, then record the selected model and configuration in the quotation and project documents.
Quoted specification
Confirm that the stated specification describes the quoted configuration.
Document for the quoted model
Check the file identifier, date, holder, named model and stated scope. Do not extend it to another configuration without confirmation.
A project decision
Assign site geometry, interfaces, destination needs and installation decisions to the relevant project reviewer.
Item to confirm
Request any missing value or document before selection; do not substitute an implied comparison claim.
Ask what the sample is intended to prove.
If a sample is considered, set the inspected configuration, drawing revision, site or mock-up context, interfaces, observer and acceptance questions before it is reviewed. A sample should not stand in for an undocumented variant.
- Model matchConfirm labels and described components against the proposed project record.
- Physical reviewCheck the submitted geometry, mounting interface, access and cable-routing assumptions.
- System reviewRecord the stated load, controls and storage/interface questions that remain open.
- Evidence closureMark each matrix cell supplied, conditional, unresolved or outside the project scope.
Move from format to project architecture.
The energy-system page provides the broader load-and-site framing; the document page helps keep files tied to their actual scope.
- Energy architectureReview solar energy-system categories before preparing the input record.
- Solar design inputsOrganise the site and load brief for a project-level conversation.
- Evidence boundariesRead how documents are scoped before treating a file as model-wide proof.
Send your comparison and the questions still open.
Share the site plan, load profile, candidate formats, mounting constraints, destination and evidence questions. The project brief can then request named-model information and record any remaining unknowns without claiming a universal result.
Format, site, interfaces and model evidence must be reviewed together.
Confirm the evidence for each proposed format before choosing.