01
Six capabilities in one site system
Access, attendance and surveillance may have different business owners, but they share identity, location, network, time and event information. The design separates their purposes and data boundaries so attendance rules do not replace physical security and video does not become the only event record.
Identity and people
Maintain employee, visitor, contractor and temporary identities with source, approver and expiration.
Doors and permissions
Assign area, schedule and access rules for offices, server rooms, stores and critical zones and record abnormal openings.
Attendance and schedules
Collect entry or check-in events according to enterprise policy; business owners confirm exception and calculation rules.
Video surveillance
Select camera positions, view, recording and playback from the observation objective, light, distance and site conditions.
Alarm integration
Connect door exceptions, alarm inputs and related video to an actionable notification and review method.
Administration and audit
Record users, permissions, events, configuration and exports, reducing ambiguity created by shared administrator accounts.
02
Endpoints, control and platform
The system combines readers or recognition terminals, locks and exit devices, access controllers, cameras, networks, storage and management software. Critical door logic should account for network loss, while video storage is calculated from points, bitrate and retention.
Door endpoints and controllers
Terminals identify users; controllers execute door rules and connect locks, contacts, exit buttons and alarm inputs.
Cameras and recording
Cameras use a dedicated or segmented network to reach recording and management, with capacity based on quality, frame rate and retention.
Management platform and accounts
The platform manages people, doors, schedules, events, playback and reports through role-appropriate access.
Network and power
PoE, controller power, backup power, VLANs, addresses and server-room links are designed with explicit network- and power-loss behavior.
03
Point design depends on site conditions
Identical devices behave differently in different locations. Door construction, opening direction, fire requirements, cable distance, backlight, night illumination and privacy areas all require site verification.
Door survey
Record door and frame, lock, contact, exit method, fire integration, power and cable route.
Camera field of view
Use the target, distance, angle, obstruction, backlight and night conditions to choose lens, height and illumination.
Server-room and low-voltage conditions
Place controllers, switches, recording, distribution and racks with sufficient cooling, maintenance and growth space.
04
Engineering and system go-live
Smart-building systems combine construction and software. Concealed works, installation, permission rules and user training are checked separately so cabling and logic defects are not discovered after every door is complete.
- 01
Requirements and points
Confirm policies, zones, people, observation targets, retention and site conditions.
- 02
Detailed design and materials
Produce point, system, cabling, power and equipment schedules and check interfaces and accessories.
- 03
Cabling and installation
Inspect concealed work, identification, termination, mounting, power and network access.
- 04
Configuration and integration tests
Build people, door, schedule, recording and alarm rules and test normal, abnormal, network-loss and power-loss conditions.
- 05
Training and handover
Deliver points, configuration, accounts, procedures, backups and maintenance information, including permission changes and exports.
05
Data, permission and use boundaries
Identity and video information involve enterprise policy and privacy. The technical platform provides collection, control and retention capabilities; attendance rules, data use, viewing permissions and retention periods remain enterprise decisions under applicable requirements.
Least privilege
Reception, HR, security and technical staff receive only the people, door, playback and configuration access needed for their work.
Accounts and operation records
Avoid shared privileged accounts and record critical configuration, permission, export and deletion activities.
Retention and backup
Set event and video retention from policy and define capacity, export, backup and expiration handling.
Identity lifecycle
Joining, role changes, temporary access and departure trigger authorization, review and revocation.
06
Operations and fault diagnosis
A failed door, missing recording or attendance exception may originate in an endpoint, cable, network, controller, platform, time or business rule. Operations follow the chain and retain configuration backups and replacement records.
Devices and circuits
Check locks, contacts, exit devices, readers, cameras, power, ports and links.
Platform and storage
Monitor services, databases, recording capacity, time synchronization, alerts and backup to identify retention problems early.
Rules and people
Verify identity, doors, schedules, shifts and permission changes to separate technical faults from policy behavior.
For a related implementation path, you can also review Network Equipment, Switching and Routing, IT System Integration and Low-Voltage Systems, Structured Cabling.
Questions
Questions specific to this solution
Must access, attendance and video use one platform?
No. Integration depends on existing systems, interfaces, administration and data boundaries; relationships and responsibilities are more important than a forced single product.
How is video retention capacity calculated?
Camera count, resolution, frame rate, codec, recording method and retention period are calculated with allowance for equipment and business growth.
Can access control continue during a network outage?
That depends on controller architecture and local rules. Network loss, power loss, fire and emergency opening behavior must be defined in design.
Is every attendance exception a system fault?
No. Time, schedules, identity data, permissions and business rules can affect results and require both technical and administrative review.
How are permissions managed after go-live?
Roles receive least privilege, and joining, job changes, temporary access and departure are connected to authorization and revocation.