Otiumtek Tork

Turn security events into processes with context.

Access control, readers, vehicles, and other devices generate events all day. Tork receives them, keeps state when needed, and connects them to applications and systems in your operation.

It integrates with Dahua DSS and HikCentral. It does not replace that platform: it adds an application layer on top. A one-off HTTP trigger is not enough when the business needs to wait, correlate, or query another source.

Tell us which event you want to process See how it runs

What it manages

Events, rules, and deliveries — toward operations

Tork does not manage the people roster (that is Onyx). It receives what security publishes, interprets it with business logic, and delivers it where operations need it.

Access events

Entry and exit marks from controls published by Dahua DSS or HikCentral.

Vehicle events

Entries and exits with usable identification for processes such as dwell.

Alarms and devices

Alarms and device health when the security platform exposes them.

Stateful applications

Logic that waits, correlates, or closes a cycle — not only a single send.

Deliveries

Webhook/API, Telegram, or another agreed integration into the business process.

History

Event and delivery history for operations and incidents.

Today the communicated integration is with Dahua DSS and HikCentral. Other brands or systems are assessed per project based on available interfaces.

Security events

Dahua DSS HikCentral
Otiumtek Tork

sync and routing

Operations and integrations

Telegram Webhooks · APIs Business systems

More detail on security-platform integration: Dahua DSS API integration · HikCentral API integration

In operations

Cases where the event alone is not enough

Security publishes the fact. Tork sustains the process: time, rules between people, external checks, or a bridge to another access system.

Available application

Vehicle that enters and never records an exit

In neighborhoods with public streets, parks, or controlled sites, an unknown vehicle can stay longer than expected without operations noticing in time.

Before

Someone watching screens or checking loose records after the fact.

After

Tork correlates entry and exit, waits the configured time, and triggers the defined action if there is no egress.

From loose events to a dwell process with state.

How the application runs

  1. 01

    Entry

    Vehicle event published by Dahua DSS or HikCentral.

  2. 02

    Wait

    The application keeps context while the timer runs.

  3. 03

    No exit

    If egress does not arrive in time, the condition is met.

  4. 04

    Action

    Webhook, ops channel, or another configured delivery.

Depends on vehicle events published with usable identification.

Usage example

Restraining order at a sports club

If a parent and child are members and a restriction exists between them, one person’s access mark can trigger a rule that blocks or alerts on the other’s entry — with the integration and policy defined in the project.

Usage example

Health certificate on a construction site

On a worker’s access event, Tork can query a third-party system, report the result, and — under the agreed rule — push a block or alert if requirements are not met.

Available application

Reports tuned to operations

Access events can feed attendance and day close, with deliveries to webhook, Telegram, or other destinations. The focus is a report useful for operations — not a generic security dashboard.

Usage example

Bridge to Lenel, Rosslare, or another ACS

Tork receives the event from Dahua DSS or HikCentral and, via a custom integration, delivers it to another access system to open or close doors and log the fact. We do not claim universal connectors: scope follows interfaces and project design.

Scenarios with third-party systems or other brands are framed as projects. Vehicle dwell and attendance from access are available applications on Dahua DSS and HikCentral.

Ways to use it

Ready applications — or custom processes

The same Tork: depending on whether your case already has an app or needs its own logic and integration.

Available applications

Vehicle dwell, attendance from access, and webhook or Telegram deliveries on Dahua DSS or HikCentral events. You configure rules and destinations without building software from scratch.

Custom processes

External API or database checks, rules between people, bridges to Lenel, Rosslare, or other systems: designed on the same events, state, and delivery platform.

In both modes, Tork provides what a single HTTP trigger from Dahua DSS or HikCentral cannot sustain: state, time, retries, and history.

The platform

How Tork looks in operation

Connections, applications, and destinations. Tap a capture to enlarge.

In the field

Partners and projects

Public references where Tork is already part of the solution.

Suite

How it fits with Onyx and with security

One possible end-to-end path. Each product is sold separately.

  1. 01

    Managed in Onyx

    People, visits, vehicles, and permissions — if you use Onyx.

  2. 02

    Dahua DSS / HikCentral

    Security execution and event publishing.

  3. 03

    Event

    Access, vehicle, alarm, or another published event.

  4. 04

    Process in Tork

    State, applications, and integrations.

Onyx keeps who may enter in order. Tork acts when the event already happened and something must be done with it. Each product can stand alone.

Explore Otiumtek Onyx →

Frequently asked questions

Frequently asked questions

Answers for teams evaluating electronic security event automation.

Does Tork replace Dahua DSS or HikCentral?

No. It integrates with them to process events. The security platform remains the hub for cameras and access.

Is Tork only for notifications?

No. It can keep state, evaluate conditions — such as dwell time — and connect processes. Notifications are one delivery option, not the product boundary.

Does it connect to each camera?

No. Devices — access, LPR, alarms — report to Dahua DSS or HikCentral; Tork works with the events published there.

Can it block an entry?

It does not replace the access controller. It can react to an event and, with the right integration, send an action to another system (alert, command, or log) according to the project.

How is it different from Onyx?

Onyx manages people, visitors, and permissions into security. Tork processes events that leave security toward operations.

Tell us which event should become a process

Dwell, rules between access events, an external system check, or a bridge to another ACS — we review it against the real capabilities of the integration.

What happens next

  1. 01 We review your inquiry on the same business day
  2. 02 We schedule a call to understand scope and systems
  3. 03 We propose the right integration or product
  • Software · Integration · Physical security
  • Montevideo, Uruguay

Direct contact