Functional map | Horus@Fidumtec

Map of Horus organized by domains to document capabilities, operating scope, and application value with a uniform structure.

Horus functional map

This section documents the Horus application at a functional level. It starts from the platform capability inventory and organizes it into independent documents so each domain keeps a homogeneous, comparable, and easy-to-extend structure.

Each document uses a common template:

Functional purpose: what that domain solves within Horus.
Operating value: practical impact for users, administrators, and operations teams.
Included capabilities: main functions covered.
Relationship with the Horus ecosystem: connection with other modules, instances, devices, users, or automations.

Documented domains

Core Platform

Multi-environment base, independent instances, cloud synchronization, and distributed architecture.

Users and Community

Registration, roles, permissions, groups, invitations, and collaborative environment management.

Devices and Infrastructure

Cameras, IoT, sensors, actuators, status monitoring, and secure remote connectivity.

Dashboards and Visualization

Personalized dashboards, real-time monitors, camera visualization, events, and layouts.

Automation and Scenarios

Manual scenarios, automated workflows, conditional rules, notifications, and playbooks.

Scheduling and Time

Shared calendars, time-window permissions, recurrences, and temporal restrictions.

Collaboration and Communication

Multi-user coordination, community interaction, shared notifications, and incident response.

Security and Governance

Authentication, ownership, data isolation, permission inheritance, and contextual authorization.

Intelligent Operations

Event coordination, autonomous flows, real-time response, and distributed intelligence.

Commercial Value

Positioning messages to communicate Horus value as an intelligent platform.

Using this map

The functional map serves as a base for commercial presentations, internal specifications, module definition, team onboarding, and product evolution. Each domain can grow with use cases, business rules, associated screens, required permissions, or technical integrations without losing the same reading structure.