Transport
Passageways, turnstiles and service areas
Typical Controller-Based Access Control System | Seenaptec Access Platform |
|---|---|
A turnstile is treated as one or more controller access points with assigned inputs and outputs. | A turnstile is a standalone object type with readers, directional locks, and a passage sensor. |
The passage mode depends on the access point and controller configuration. | Behavior is determined by the object type, while permissions are determined by the access pass and object rules. |
Bulk configuration is performed on selected access points or controllers. | Standard turnstiles are created and linked to devices using a template. |
Changing equipment requires reviewing the entire access point configuration. | Replacing a device does not change the object's routes, access passes, or history. |
Separation of flows and zones
Typical controller-based ACS | Seenaptec Access Platform |
|---|---|
Zones and directions are formed by passage points and access modes. | Objects are combined into perimeters and routes with explicit entry and exit assignment. |
APB depends on the correct configuration of zone control at all points. | Presence state is maintained centrally; violations can either be blocked or only logged. |
Different levels and modes are created for different categories of personnel. | Passes are assigned to objects, tags, or routes and contain their own validity periods and time profiles. |
Changing the composition of a zone requires adjusting the modes of the relevant points. | The composition of the perimeter or route is changed without reconfiguring the passes issued for the corresponding tag. |
Personnel, contractors, and visitors
Typical controller-based access control system | Seenaptec Access Platform |
|---|---|
Employees and visitors are served by separate sections and issuance scenarios. | Person, identifiers, and pass are separated as independent entities; subject type does not change the access model. |
A temporary pass and a visit route are created for the visitor. | A request reserves data but does not grant access; after issuance, the pass receives objects, route, term, and restrictions. |
Escort is a special mode rule. | Escort is verified when requesting a specific access object. |
Location verification is based on entry and exit reports. | The current access panel shows the real-time status of perimeters. |
High equipment density
Typical Controller-Based Access Control System | Seenaptec Access Platform |
|---|---|
The number of controllers is determined by the number of supported access points and inputs/outputs. | Up to 64 peripheral devices can be addressed on a single OSDP line. |
A controller failure affects a group of connected access points. | Devices are addressed individually; the status of each device is monitored by the platform. |
Redundancy typically requires duplication of the controller or the entire hardware subsystem. | The line can have two adapters at the ends of a single RS-485 segment and automatic switching between circuits. |
Expansion requires the installation of additional controllers with the appropriate capacity. | Expansion is performed by adding addressable devices to existing or new OSDP lines. |
Operations and investigation
Typical Controller-Based ACS | Seenaptec Access Platform |
|---|---|
Monitoring, archive, reports, and operator log are separate functional areas. | Access event, technical status, and change audit form a single event sequence. |
The operator analyzes the source, event type, and associated access point. | The event card shows the object, person, identifier, pass, decision, and reason. |
Alarm responses depend on separately configured scenarios. | An alarm requires operator acknowledgment with a mandatory comment. |
History is used for subsequent report generation. | Investigation tags are added on top of an immutable record; adding and removing a tag is also logged. |