Duplicate people data
HR onboarding plus manual re-entry into security — errors, delays, and stale permissions.
Platform integration
The problem
Common situations when Dahua DSS does not take part in enterprise processes.
HR onboarding plus manual re-entry into security — errors, delays, and stale permissions.
Area changes, offboarding, or rotation reach access control late.
Visit data lives in spreadsheets or systems disconnected from security.
Alarms and access marks stay in the VMS and never feed notifications or internal systems.
Admin and security teams redo the same tasks in disconnected tools.
Scope
Dahua documents integration capabilities for DSS Professional (APIs and partner ecosystem). What is available on each install depends on edition, version, modules, licenses, and project scope.
Directory sync into the security platform when the DSS environment allows it.
Publishing access groups and rules to reduce double administration.
Flows where visitor management is coordinated with what DSS operates.
Consuming DSS-published events for rules, alerts, or external systems — via Tork or another integration.
ERP, HR, or internal apps as source or destination, designed per project.
Otiumtek builds integrations on those capabilities; we are not the manufacturer of Dahua DSS and do not own its API.
Enterprise systems
sync and routing
Security platform
Approach
An indicative methodology to assess and implement — not a fixed-scope guarantee.
Version, topology, and how electronic security operates today.
Modules, licenses, and integration interfaces that are actually available.
Which systems send or receive information and under which business rules.
Onyx, Tork, custom development, or a combination — case by case.
Controlled rollout, tests, and agreed operational criteria.
Otiumtek solutions
Our own products that work with the platform — they do not replace it.
Centralizes people, visitors, vehicles, and permissions, and can sync that information into Dahua DSS. It is not a VMS and does not operate cameras: it organizes data and publishes into the security platform.
View Otiumtek Onyx →Consumes events published by Dahua DSS, applies business rules, and routes to notifications, webhooks/APIs, or other project integrations. It does not replace the VMS or connect device by device.
View Otiumtek Tork →We also assess custom integrations when the requirement does not fit Onyx or Tork. We do not claim every integration is possible on every version or license.
Events
Conceptual flow: what Dahua DSS publishes can feed rules and external systems via Tork or another integration.
Enterprise systems
sync and routing
Security platform
Scenarios
Indicative examples — not published projects unless listed in our projects section.
Hires, exits, and area changes update the directory security uses, with less duplicate entry.
Visit operations align with what access control in DSS needs.
Relevant marks or alarms trigger notifications or processes in other systems.
Custom integrations when the business needs a flow a standard product does not cover.
Each scenario requires validating DSS version, modules, and licenses, plus the agreed customer scope.
FAQ
Indicative answers; technical detail is confirmed in each assessment.
Yes. Dahua documents integration with DSS Professional through APIs and a partner ecosystem. Access to guides and capabilities usually depends on official manufacturer channels, and what is available varies by edition, version, modules, and licenses.
Often yes, as part of an integration project. Otiumtek may use Onyx to publish identities and permissions into DSS, or design a custom bridge. There is no universal “ERP X → DSS” connector ready for every version.
A common scenario: HR as the source and DSS as the publication destination for people and permissions, typically via Onyx or another designed integration. It depends on the HR system’s APIs or exports and on the DSS environment’s capabilities.
Yes, when DSS publishes or exposes those events and the project defines subscription and destinations. Tork is built to consume Dahua DSS events and apply rules toward Telegram, webhooks/APIs, or other integrations.
No. Onyx and Tork work with the security platform; they do not replace it. DSS remains the VMS / electronic security layer.
DSS version and edition, relevant modules/licenses, enterprise systems involved (ERP, HR, etc.), approximate volumes, and the operational outcome you want. With that we build a realistic proposal.
Also
If you run Hikvision, see our HikCentral API integration page.
HikCentral API integration →Tell us about your DSS environment, the enterprise systems involved, and the outcome you want. We assess Onyx, Tork, or custom development.
What happens next
Direct contact