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.
Use these access levels to identify which resources are available now and which project files require scope, model, or engineering confirmation.
Each access level shows what you can download now, what becomes available after basic project information, and what requires engineering review.
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.
Use these public checklists and input forms to prepare the basic project, engineering and tender information needed before quotation or document review.
These files are generic preparation resources. Actual product IES/LDT files, project-specific DIALux reports, matched datasheets, drawings, certificates and formal tender packs require confirmed project scope, model configuration and engineering review.
Prepare the minimum project information needed for a preliminary product, engineering, document and quotation review.
Confirm road geometry, pole height and spacing, operating hours, autonomy, climate, structure and required engineering files before requesting a quotation.
Identify missing scope, conflicting specifications, document gaps and clarification actions before pricing or tender submission.
Pre-review eligibility, technical, photometric, structural, compliance, logistics, installation, acceptance and submission-control documents.
Collect the geometry, criteria, mounting, model, photometric-file and output requirements needed for a preliminary simulation review.
Prepare pole geometry, mounted equipment, wind and corrosion exposure, ground conditions, flange, anchor-bolt and drawing inputs for structural coordination.
Compare normalized project scope and documented risk instead of judging offers by wattage and unit price alone.
See how a controlled product datasheet may be structured after model confirmation. This public sample contains no model-specific performance claims.
These resources help buyers understand file formats and review requirements, while final files still depend on the product model, project scope, tender requirements, and intended use.
These redacted sample formats show how photometric and simulation outputs are reviewed without exposing project files.
This sample table shows how BOQ lines can be matched to the model, optics, battery or panel scope, and document notes.
Use this checklist to plan inspection, commissioning, handover records, and owner acceptance.
Use this checklist to review factory inspection, packaging, labels, shipment readiness, and document control.
Availability of selected compliance documents depends on the tender requirements and product category.
Use this structured list to request relevant supplier evidence without asking for confidential 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.
Choose the path that matches your project stage and the document you need.
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 checklist → 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.
Organize project inputs, photometric files, BOQ notes, inspection records, and handover documents.
Continue to the right engineering, tender, product, or project support page.
Project document paths, simulation support, and engineering request routing.
Tender checklist, BOQ matching, and document pack boundaries.
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.
Files listed in the Public Project Preparation Downloads section can be downloaded directly. These are generic Layer 1 resources, including project input sheets, checklists, editable forms and sample formats. Project-specific engineering files—such as matched IES/LDT files, DIALux reports, model-specific datasheets, drawings, certificates, BOQ compliance documents and full tender packs—require confirmed project information and engineering review.
Many files depend on the product model, project scope, tender requirements, and intended use. Basic project information helps prevent the wrong or outdated file from being released.
IES/LDT files should match the selected model, optics, CCT, and mounting assumptions. Submit the project details first so Sunlurio can identify the correct file.
Yes. Sunlurio can review the request after receiving the road or site layout, pole height, spacing, target lighting level, and product assumptions.
Yes. Please provide the tender or BOQ file, product scope, quantity assumptions, and intended document use.
No. Pole, foundation, anchor-bolt, and wiring references require engineering review and may depend on local civil responsibilities, wind conditions, and project configuration.
Public and request-based resources can support tender preparation, but final tender documents depend on confirmed project scope and review. Sunlurio does not guarantee tender acceptance or approval.
Send the country and city, project type, BOQ or drawing, pole height and spacing, required nightly operating hours, required documents, known product preferences, tender stage, and deadline where applicable.
Send your BOQ, project inputs, drawings, or required document list. Sunlurio will review the project stage and recommend the appropriate 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.
