Security & Compliance

Every engagement begins with a read-only connection. During this phase Aphelium cannot issue any command to site systems. Write access is granted only by the operator, only for agreed setpoints, and only after the recommendation phase.

Temperature, humidity and redundancy limits are defined by the operator and enforced as hard constraints. The optimizer cannot trade a limit for savings. A command outside the limits is not issued.

Operators can override Aphelium at any time from the existing control system. An override takes precedence over any Aphelium command.

If Aphelium stops for any reason, control returns to the existing BMS logic. Safe operation of the facility does not depend on Aphelium.

Aphelium is deployed with network isolation between the operational network and external networks. One-way data export is used where possible.

Facility data stays in the customer's country if required. The location of storage is stated in the contract.

Data may be stored within the territory of Uzbekistan for state and corporate customers.

Access to facility data is limited by role. All access by Aphelium personnel is logged.

Standards are listed as held only when a certificate has been issued. The following are on the roadmap.

• ISO/IEC 27001 (Roadmap)
• ISO 50001 (Roadmap)