Combination and revision list
Identify luminaire, power supply, controller, gateway and software revisions.
How this deliverable is checked
Each test corresponds to a specific combination.

Review the service and its applications. Scope, deliverables and fees are agreed following discussion.
Discuss the service →Identify which combinations work together and which conditions still need testing.
Professional service · Acceptance against agreed deliverables
The following deliverables can be agreed. The project brief defines their depth, quantity and verification responsibilities.
Identify luminaire, power supply, controller, gateway and software revisions.
Each test corresponds to a specific combination.
Compare interfaces, functions, settings and limitations.
Recommended combinations have supporting evidence and prerequisites.
List configurations, functions, fault conditions and actual results.
Distinguish passed, failed and untested cases.
Handover setup steps, issue records and regression requirements.
Tests of the agreed combination can be reproduced; untested areas are explicit.
Agree device combinations, revisions, operating conditions and integration rounds for the luminaires and modules involved.
Product electrical/control architecture, device models and revisions, protocols, functions and operating conditions.
Fees depend on device combinations, hardware and software revisions, functions tested and integration rounds. Sharing a protocol name does not prove interoperability.
We confirm workload, service period and both parties' responsibilities before issuing a formal quotation. Samples, site work and third-party services are listed separately where required.
This service tests combinations of existing products and modules. New controller boards or software development are handled by electrical and control design; protocol certification and whole-home deployment are scoped separately.
Conclusions apply to the specific models, revisions, configurations and functions tested. New combinations or changes after an update require regression testing.
Every agreed combination has recorded inputs, revisions, steps, results and limitations. Untested combinations are labelled clearly.
We first assess how gaps or changes affect deliverables, timing and fees. They are included only after both parties agree; items outside the original scope are recorded separately.
Start with a summary of the product type, objectives and issues. Share detailed information after its intended use, confidentiality requirements, access scope and delivery permissions have been agreed.
Describe your current stage, main objectives and desired deliverables, then we can confirm the suitable scope and next step together.
Use the enquiry page to share a project summary. Detailed information can follow once its use and confidentiality requirements are agreed.