NayotaNayota
English / FAQ
Product & Delivery Guide

Frequently asked questions

Practical answers for integrators, technology partners, and project teams evaluating Nayota products, interfaces, delivery responsibilities, and acceptance evidence.

Ask a project questionReview technical resources
Evaluation guide

Direct answer

What should a project team confirm first?

Confirm the operating objective and delivery boundary before comparing feature lists. A reliable evaluation covers existing systems, protocols, point-list quality, asset and spatial coding, network security, control authority, implementation roles, and acceptance evidence.

Product scope
Required IoT, IBMS, energy, automation, spatial visualization, and AI capabilities.
Site readiness
Commissioning status, protocols, point lists, networks, servers, security, and access rights.
Acceptance
Data quality, functional results, control feedback, exception handling, documentation, and training.
Platform & Integration

Architecture and compatibility

What is the difference between Nayota and a traditional BAS or IBMS?

BAS generally focuses on equipment and specialist-system control, while IBMS focuses on integration. Nayota combines device data, spatial relationships, system integration, energy applications, and governed automation. Actual scope remains subject to project interfaces and control boundaries.

Can existing building systems and equipment be retained?

Potentially. Retention depends on protocol support, interface openness, data quality, security requirements, equipment condition, and testing. Existing specialist safety controls and protections are not automatically replaced.

Is the platform tied to one hardware vendor?

The architecture is designed for multi-vendor integration. Compatibility must still be confirmed against exact device models, firmware, protocols, point lists, permissions, and site conditions.

How are buildings, floors, rooms, and equipment related?

Project drawings and confirmed equipment identifiers are used to establish spatial relationships. Drawing vectorization and equipment-point annotation are separate tasks and should be scoped independently.

Energy & Operation

Claims, controls, and evidence

Does the energy and carbon platform certify a zero-carbon building?

No. It can provide data, accounting processes, operational records, and project evidence. Evaluation, verification, or certification must follow applicable standards and qualified-party requirements.

Does Nayota guarantee a fixed energy-saving percentage?

No fixed percentage should be promised before site diagnosis, baseline definition, operating-condition review, and agreement on measurement and verification.

How are automation strategies governed?

Strategies should define triggers, target objects, permitted actions, approvals, safety conditions, execution feedback, exception handling, manual takeover, and audit records.

Can AI directly control building equipment?

AI-assisted analysis or interaction is limited by available data, permissions, and project configuration. Equipment control must follow explicit authorization, safety interlocks, confirmation rules, and operational accountability.

Delivery & Partnership

Project responsibilities

What must be ready before platform integration starts?

Equipment, power, cabling, unique identifiers, specialist commissioning, interfaces, point lists, parameters, drawings, network conditions, and agreed test data should be ready to the extent defined by the contract.

What is the difference between platform supply and full delivery?

Platform supply generally begins from tested interfaces and agreed inputs. Full delivery includes the broader responsibilities explicitly assigned in the contract. Construction and specialist-system commissioning are not automatically included.

How is acceptance defined?

Acceptance should cover interfaces, data quality, functions, performance, security, operations, training, documentation, execution feedback, and the evidence required for each agreed boundary.

How do international partners start?

Share the target market, customer type, project context, expected role, current systems, required localization, and delivery constraints. Nayota can then arrange a technical and partnership discussion.

Still evaluating project fit?

Send the project context and the questions that need technical confirmation.

Book a technical discussionEmail our team