By environment

Six environments we know the inside of

Each of these comes with a reference architecture, a device schedule and the commissioning questions that decide whether the handover goes smoothly. Open the one your project resembles.

01 — Hospitality

Hotels where the room knows the guest

A hotel is the hardest smart-space client you will ever have: the guest changes every two nights, the room must work without explanation, and the engineering team must be able to service it at 2 a.m.

We design the room as a repeatable unit — one template, applied 200 times — with the guest-facing layer on iFLYTEK WallEX, the energy layer on room controllers and sensors, and the power and network underneath from the ELV portfolio.

  • Guest room template with scene, voice and panel control
  • PMS interface for check-in, check-out and room status
  • Energy management on occupancy and window/door state
  • Back-of-house network, CCTV and Wi-Fi in the same programme
  • Rack power and UPS sized per floor distributor

Reference stack

Hospitality reference stack
In roomWallEX room controller, panel, voice terminal, sensors
Per floorPoE access switch, Wi-Fi APs, UPS for the IDF
CoreeKit or enterprise switching, routers, firewall
Head-endUPS + SmartLi, NVR and storage, management platform
SoftwareWallEX platform; NetLogg for operational telemetry
See the AI practice

Sizing conversation, in order

  1. Load & growth

    Rated kW today, expected kW at year three.

  2. Redundancy

    N+1 inside the frame, or 2N across two halls.

  3. Runtime

    Generator start, orderly shutdown, or both.

  4. Battery technology

    Lead-acid room versus lithium cabinet — floor space decides.

See the UPS range

02 — Data centres & critical facilities

Power you can add to without rebuilding

The UPS decision in a data centre is rarely about kVA — it is about how the hall grows, how maintenance happens without downtime, and whether the battery room exists at all.

We work through the modular versus monolithic question with your MEP consultant, model the lithium option against lead-acid over a ten-year horizon, and quote the PDU and monitoring layers so the whole distribution path is one commercial package.

  • UPS5000-A tower or UPS5000-E modular frames
  • SmartLi lithium cabinets replacing battery rooms
  • PDU8000 rack distribution and metering
  • SNMP / Modbus integration into BMS or DCIM
  • Staged delivery matched to commissioning phases

03 — Commercial & mixed-use

Towers with many tenants and one riser

Mixed-use means the landlord owns the infrastructure, the tenants own the fit-out, and nobody owns the integration. That gap is where smart-building projects fail.

We supply the base-building layer — core network, distributor power, access control, CCTV and the BMS interface — so each tenant fit-out connects to something finite and documented, rather than inventing its own island.

  • Base-building network and tenant demarcation
  • Access control power and lock-side wiring
  • Lift, lighting and BMS interfaces
  • UPS for security, comms and life-safety racks
  • Landlord dashboards for energy and occupancy

The tenant-fit-out problem

Every tenant arrives with a different contractor and a different idea of what the base building provides. Our answer is a handover document: what the distributor gives you at the demarcation point — power, ports, VLANs, access-control interface — and what the fit-out must supply itself.

Ask us for the tenant demarcation template we use on handover.

Request the template

A branch kit, defined once

  • Router with dual-WAN failover
  • PoE access switch sized to cameras + APs
  • Two to four Wi-Fi APs per store format
  • Four to sixteen cameras with calculated retention
  • Branch UPS sized to the actual rack load
  • Management app onboarding template

Kits are labelled per site and shipped as one delivery, so the fit-out team is not chasing four suppliers.

04 — Retail & F&B chains

Twelve branches, one standard, one SKU list

For a chain, the cost is not in the first store — it is in the eleventh, when someone has improvised and the standard has quietly drifted.

We build a standard branch kit per store format, hold it as a repeatable configuration, and supply it with the same part numbers every time. Rollouts stop being projects and become orders.

  • Standardised branch kit per store format
  • Central visibility of network and camera health
  • Consistent UPS runtime across the estate
  • Spares holding for the roll-out period

05 — Education & campuses

Campuses where the network is the timetable

Attendance, exams, CCTV, access control and classroom AV all ride on one network — and the load arrives in bursts that a branch design will not survive.

We size for density rather than coverage: high-density Wi-Fi in lecture halls and labs, resilient power for the comms rooms, and room automation that a teacher can operate without training.

  • High-density Wi-Fi for halls, labs and libraries
  • Classroom AV and voice-reinforcement control
  • Campus access control and CCTV integration
  • UPS for IDFs and the core, with runtime for safe shutdown
  • Phased summer-window installation planning

Why capacity, not coverage

The usual campus failure is a design signed off against a coverage heat map: full bars, and 300 students unable to authenticate. We plan on concurrent clients and airtime per room, then propose AP counts against that number — and we show you the assumption so your IT team can argue with it.

See the eKit portfolio

06 — Government & enterprise

Where the data cannot leave the building

Sovereignty is not a slide in the proposal — it is the reason a project is approved or stopped. NetLogg exists for exactly this constraint: the platform runs inside the customer's estate, under the customer's policy.

We support the compliance conversation with documentation rather than assurances: where data is stored and processed, who holds the keys, how access is audited, and what happens to the data if the vendor relationship ends.

  • On-premise or in-country deployment
  • Role-based access and audit trail
  • Integration with existing SIEM and ITSM
  • Local support and escalation obligations
  • Exit plan: data portability, not lock-in

What we put in writing

Sovereign deployment commitments
Data locationNamed site or in-country tenancy, confirmed before contract.
Access controlRoles, MFA, audit log retention stated in the design.
Support modelNamed escalation tiers with response windows.
ExitData export format and timeline agreed at day one.

At a glance

Which practice leads in which environment

Every environment uses all three practices. What changes is which one drives the design and which one follows.

Practice involvement by environment
Environment AI & smart spaces ELV & power IoT & integration
HospitalityLeads — room experienceRack, power, Wi-Fi per floorPMS and energy integration
Data centresSecondary — DCIM analyticsLeads — UPS, lithium, PDUMonitoring and alarms
CommercialSecondary — shared spacesLeads — base buildingBMS and tenant dashboards
Retail chainsOptional — in-store audio and screensLeads — branch kitCentral estate visibility
EducationClassroom AV and controlDensity Wi-Fi and resilienceLeads — campus integration
GovernmentSovereign AI workloadsResilient infrastructureLeads — telemetry sovereignty

Tell us which one your project is

Send the environment, the scale and the stage you are at. We will come back with the reference architecture and the questions your consultant will ask next.