Data center

A door is configured as an access point on a specific controller: readers, inputs, outputs, operating mode, and standalone configuration are managed together.

A machine room, electrical room, or cooling room is created as an independent access object. The reader, lock, exit button, and door sensor are assigned to its functional slots.

Access rights are assigned to access points and modes associated with the equipment structure.

A pass contains objects, tags, or routes, as well as a validity period, schedule, identifiers, and restrictions.

When equipment is changed, the access point configuration and controller settings must be checked.

Replacing a device does not change the access object, granted rights, or event history; only component assignments are restored.

The cabinet is implemented as an additional access point or via a separate locking subsystem.

"Server cabinet (1 door)" and "server cabinet (2 doors)" are standard access object types.

Controller inputs and access point events are used to monitor opening.

The cabinet type provides slots for a reader, lock, door sensor, and handle sensor.

The fact of passage or opening is recorded.

Work with the cabinet can be tracked as a session: start, activity confirmation, last action, and completion.

Room access and cabinet access may be in different management loops.

The room and cabinet are part of a unified model for credentials, rules, events, and investigation.

A temporary pass is created for the contractor, granting access to a set of access points. The route and additional requirements are configured separately.

The pass may specify particular assets, tags, or a route, as well as a validity period, schedule, and access limit.

Escorting is implemented through a special access mode rule.

Escort mode is an asset parameter: after the visitor's identifier is presented, the escort's identifier is presented.

Clearances and restrictions are often encoded as modes or additional personnel parameters.

An asset can be assigned a requirement for the presence or absence of a condition: clearance, safety briefing, or authorization for a specific type of work.

After the work is completed, it is necessary to separately verify that the person has left the premises and that the cabinet has been closed.

The “Current Access” panel shows presence within perimeters and active cabinet sessions.

New points are created within controllers; then inputs, outputs, modes, and standalone memory are configured.

Devices are discovered on the OSDP line, after which objects are created and bound using group operations.

Configuration is repeated for each controller or group of identical controllers.

Hardware and binding templates are applied to groups of devices of the same model.

Mass update is performed by sequential processing of selected controllers.

Firmware file is selected from the catalog automatically; the result is displayed separately for each device.

When expanding, the number of hardware configurations increases.

When expanding, the number of objects and devices increases, but unified rules for their creation and maintenance are preserved.

Access records, operator activity logs, and technical diagnostics are available through separate functional sections.

Access events, change audits, and equipment status are available in a single log.

An investigation requires correlating access point events, controller events, and operator actions.

The event card contains the participants, object, decision, reason, and “before/after” changes.

The outcome of a command is determined based on the controller status or subsequent events.

The command is separate from confirmation of execution: “command accepted” is not considered proof of execution.

The archive serves as the source of reporting data.

The log is append-only; saved records cannot be edited, and integrity verification is provided.