- Tender: tender@sunlurio.com
- Engineering: engineering@sunlurio.com
- WhatsApp: +86 186 5321 8098
Sunlurio provides public checklists, project input templates, and request-based engineering documents for outdoor lighting projects. Some files can be downloaded directly, while project-specific files such as IES/LDT, DIALux reports, drawings, BOQ compliance notes, and full tender packs require confirmed project scope and product configuration.
P1B-04B resource access-level rebuild visible.
Not every engineering file should be publicly downloadable. Use these levels to match document access with project stage and review risk.
Available documents depend on confirmed project scope, product configuration, tender requirements, and document stage.
Generic catalog, public checklists, input sheets, and sample formats that help buyers prepare early-stage information.
Redacted samples and review templates that require company email, project type, country, and basic requirements first.
Actual IES/LDT, project DIALux reports, matched datasheets, drawings, BOQ compliance sheets, and full tender packs.
Only confirmed public-safe files use Download. Other target templates are shown as request or planned resources until the file exists, returns 200, and is approved for public Layer 1 access.
Public catalog for early supplier review and product-family orientation.
For early quotation inputs before product path, document scope, and engineering review are confirmed.
For solar road lighting projects where country, road width, pole height, spacing, working hours and backup days must be confirmed.
For checking whether BOQ line items, model selection, quantities, and document expectations are reviewable.
For mapping tender document needs before requesting a technical document pack.
For road geometry, pole layout, target lux, uniformity, and simulation purpose before report support.
For pole height, wind speed, flange, anchor bolts, foundation reference, and local civil review inputs.
For comparing supplier quotations by configuration, documents, assumptions, and project fit.
For understanding datasheet format before model-specific datasheets are matched to a confirmed configuration.
These resources help buyers understand format and review logic, but final files depend on product model, project scope, tender requirement and document purpose.
Sample photometric or simulation format used to show review logic without exposing actual project files.
A sample table showing how BOQ lines may connect to model, optics, battery/panel scope, and document notes.
Checklist for inspection, commissioning, handover records, and owner acceptance planning.
Factory inspection, packaging review, label checking, shipment readiness, and document-control reference.
Selected compliance references may be reviewed according to tender requirement and product category.
A structured list to request supplier evidence without asking for confidential or irrelevant project files.
Controlled project files such as DIALux reports, IES / LDT files, BOQ matrices, drawings, wiring diagrams, and certificate packs depend on confirmed scope and engineering review.
These documents are released only after project scope, product configuration, tender requirements and document purpose are confirmed.
Use these buyer paths to avoid requesting the wrong file before the project stage is clear.
Project Input Sheet → RFQ Form → Product path confirmation
Tender Checklist → BOQ Review → Document Pack Request
Submit road/layout data → Confirm product model → Request simulation/file support
Submit pole height, wind speed, flange/anchor information → Request drawing/reference support
Catalog + sample checklists → Project RFQ → document pack after scope confirmation
The Resource Center supports procurement preparation, tender review, engineering requests, and project handover planning without exposing controlled files too early.
Clarify country, road width, pole height, operating hours, autonomy target, product path, and document scope.
Separate product scope, pole/foundation assumptions, document responsibilities, and comparison notes.
Connect catalog, datasheet, drawing, IES/LDT, DIALux, compliance, and handover needs to the right stage.
Submit layout geometry, target lux, uniformity, pole spacing, mounting height, and product model before simulation.
Share pole height, wind speed, flange, anchor bolt, foundation reference, and civil responsibility before drawing support.
Prepare submission folders around inputs, product files, photometric files, BOQ notes, inspection records, and handover files.
Move from public resources to the correct engineering, tender, product, or project page without using legacy URLs.
Project document paths, simulation support, and engineering request routing.
Lighting simulation support after road/layout inputs are confirmed.
Photometric file request path after model and optic assumptions are clear.
Datasheet, product drawing, pole/foundation reference and drawing support.
Submit BOQ, drawings, project inputs, or document requirements.
Common questions about public downloads, request-based resources, and engineering-review documents.
Only confirmed public-safe files can be downloaded directly. At this stage the public catalog is the confirmed direct download; project-specific engineering files are not public downloads.
Many files depend on product model, project scope, tender requirement and document purpose. Basic project information helps prevent wrong or misleading file release.
IES/LDT files should match the selected model, optics, CCT and mounting assumptions. Submit project information first so the correct file path can be reviewed.
Yes, when road or site layout data, pole height, spacing, target lighting level and product assumptions are available for review.
Yes. BOQ matching and deviation notes require the tender or BOQ file, product scope, quantity assumptions and document purpose.
No. Pole, foundation, anchor bolt and wiring references require engineering review and may depend on local civil responsibility, wind condition and project configuration.
Public and request-based resources can help organize tender preparation, but final tender documents depend on confirmed scope and review. No acceptance or approval is guaranteed.
Send country/city, project type, BOQ or drawing, pole height and spacing, working hours, required documents, product preference if known, tender stage and deadline if applicable.
Send your BOQ, project inputs, drawings or required document list. Sunlurio will review the project stage and suggest the suitable resource or engineering document path.
Share your project location, road width, pole height, spacing, working hours, backup days, and required documents. Our team can help prepare configuration guidance, datasheets, IES/LDT files, DIALux support when applicable, drawings, and BOQ matching notes.
