NOVALUX · Smart home & building automation

Building system integration & functional planning

When building functions need to work together, they need a clear functional specification. NOVALUX records the intended connections between systems and organises interfaces, responsibilities and acceptance criteria before individual devices are selected.

Enquire about your project
Building automation with a closed control cabinet and user interface – illustrative image
Illustrative image

Who is this service for?

  • Private clients
  • Businesses
  • Property managers

Possible scope of work

  • Describe dependencies between lighting, shading, room controls and other systems.
  • Record available interfaces and required permissions.
  • Define behaviour during failures, restarts and manual operation.

What you receive

  • A scope matched to your information with the relevant technical interfaces identified.
  • Depending on the confirmed commission: agreed functions and the associated operating and handover information.

From enquiry to handover

  1. Record functions and existing systems

    Describe the intended use and identify existing components. Concrete examples are more useful than a general list of preferred products.

  2. Clarify interfaces and scope

    Compatibility, access and responsibilities are assessed against the actual system. Necessary preparation and dependencies form part of the agreed scope.

  3. Provide an understandable handover

    Agreed functions, controls and relevant records determine the handover. Additional requests or subsequent changes in system conditions are agreed separately.

What we need for your quotation

  • Inventory of the systems involved
  • Desired functional sequences and available interface documents

Frequently asked questions

Must every system come from one manufacturer?

Not necessarily. Suitable interfaces and the actual functions required are what matter. A shared brand does not replace that assessment either.

What belongs in a functional specification?

It describes triggers, conditions, responses and feedback clearly. Manual intervention and behaviour when information is unavailable should also be explicit.

Can an existing installation be integrated?

That depends on product versions, documentation and access rights. Missing project files or restricted interfaces can limit the achievable scope.