ProductFeaturesSolutionsLearnResources
Product Overview

Know what's happening on your floor right now.

TaktClock is a Windows-based, on-premises production monitoring system. Operators start sessions, timers run, supervisors see status on a live screen. No MES required. No new hardware. Running in under a day.

See All Features
How It Works

From installation to live floor data in four steps.

1

Install the Server

Run TaktClock_Server.exe on one Windows PC. It hosts a local web server on TCP port 5000. No cloud account needed.

2

Configure Your Floor

Add your areas, processes, and subprocesses. Import standard hours from your ERP (M3, SAP, Oracle, Epicor) or enter them manually.

3

Operators Start Sessions

Each operator opens TaktClock.exe and scans or types their MO number. Their personal takt timer starts. The elapsed clock runs until they close the session.

4

Supervisors See Live

The Floor Map and Operations Table update every 30 seconds. Alerts fire when any job exceeds takt. No manual data entry required.

Architecture

Three executables. One local network.

TaktClock runs entirely on your local network. No data leaves your facility unless you configure the optional ERP sync. Three executables handle the full system.

TaktClock_Server.exe
Flask + Waitress web server. Hosts the API and serves the web UI to all clients on the LAN.
TaktClock.exe
The operator client. Runs on any Windows workstation. Connects to the server over TCP 5000.
TaktClock_Updater.exe
Auto-update agent. Pulls the latest version from GitHub Releases on server startup.

All session data is stored in a local SQLite database on the server machine. Lightweight, zero administration, full data ownership.

TaktClock_Server.exe
Flask + Waitress • Port 5000 • SQLite
LAN / TCP 5000
TaktClock.exe
Operator client • Windows 10/11 • Unlimited seats
Auto-update
TaktClock_Updater.exe
GitHub Releases • On server startup • Silent
Internet: Optional • ERP: Read-only sync • Data: On-premises
Technical Specifications

Built for the plant floor, not the cloud.

Platform
Windows 10 / 11
64-bit. No Linux required.
Web Server
Flask + Waitress
Python-based, zero IIS config.
Database
SQLite
Local file. No DB admin required.
Network Port
TCP 5000
LAN only. No inbound internet.
Refresh Rate
30 seconds
Operations Table & Floor Map.
Internet
Optional
Required only for ERP sync & updates.
Client Seats
Unlimited
All operator workstations on the LAN.
ERP Connectivity
M3, SAP, Oracle
Also Epicor, Dynamics 365. Read-only.
Updates
Auto via GitHub
Pulled on server startup. Rollback supported.
ERP Integration

Standard hours from your ERP. Automatically.

TaktClock reads standard hours directly from your ERP system via a read-only API connection. When your routing is updated in the ERP, TaktClock's takt targets update automatically — no manual re-entry, no spreadsheets.

No API licence is required for Infor M3. SAP, Oracle, and Epicor connections use existing API infrastructure. All ERP communication is read-only — TaktClock never writes back to your ERP.

Infor M3 SAP ECC / S4HANA Oracle EBS Epicor Dynamics 365 Other — ask us

What TaktClock reads from your ERP

Standard hours per operation
Mapped to TaktClock subprocesses automatically
Part number and routing data
Links MO scans to correct standard time instantly
Work center assignments
Operator sessions routed to the correct area automatically
MO open/close status
Validates that sessions match active orders in the ERP
See It Running

30 minutes. Live product. No slides.

We'll configure TaktClock for your areas, your processes, and your ERP system before the call so you see exactly how it works in your environment.

Download & Try It