Operate NAZARE and NAVIS within each site’s permissions.

Define separate operating spaces and team and user access in NAZARE. Specify which equipment data, site knowledge, menus and analysis resources each group may use.

Configure NAVIS with the sources and tools needed for each role. Separate read access from action approval, and send equipment control requests to NAZARE after manager approval. As new sites are added, register their equipment, users and approvers under the same operating principles.

Shared hubs need separation as well as collection. NAZARE supports tenant-isolated data, settings, users and analytical resources, independent sandboxes, data marts and pipeline history.

Resource quotas and network policies limit cross-tenant impact. Define shared and private datasets at the start.

Configurations support Parquet Modular Encryption with tenant-specific keys and encrypted transport such as TLS. Key creation, custody, revocation and query access must be managed together.

VM requests specify CPU, memory and disk for administrator approval and allocation, with Linux/Windows guests and create, change, return and status management. Virtualization infrastructure and physical procurement are scoped separately.

1. Verify cross-tenant data, configuration and user isolation.
2. Test delegation and revoked access.
3. Validate quotas during high analytical load.
4. Review key recovery and backup procedures.
5. Agree retention, export and offboarding rules.

Data trading, billing and integrated ROI services are separate service scopes.