Using TaktSignal

TaktSignal answers two questions every morning:

1. Where are we about to lose time? — material shortages, stalled or late work, overloaded work centers and customer orders at risk, ranked by severity and the factory time at stake.
2. Can we trust the numbers? — how fresh and complete the ERPNext data is, and where recorded consumption, receipts and stock counts disagree.

Everything comes from documented rules applied to your ERPNext data — no AI. Every alert says why it exists, shows its evidence, estimates the time at stake with a written basis, and states how sure it is.

TaktSignal can be wrong. Its view is only as good as the ERPNext data it can read, and Community Alpha rules have not been calibrated on enough real factories. Before acting on an alert, check it — see Verifying an alert.

Signing in

Open TaktSignal from the Control Center (Open TaktSignal) and sign in with the administrator you created. An administrator can add colleagues on the same computer under Settings with one of four roles: Admin, Operations manager, Planner, Viewer. (The desktop Community Alpha is reachable only from the computer it runs on.)

The pages

Page	What it shows
Dashboard	Factory time at stake, the next expected impact, whether the data can be trusted, data freshness per source, and the alerts that need attention, ranked. Customer orders at risk on the side.
Alerts	Every open alert with severity, time at stake, confidence and owner. Open one for its explanation, evidence, affected orders and timeline. (Understanding alerts)
Customer orders	Each sales order's projected ready time against its promise, and the work orders and materials behind it — follow a shortage from the store to the ship date.
Work orders	Status, risk and operations of each production order, what it is waiting for, and its dependencies.
Production queue	What each work center has to do next, in order.
Materials	Need versus available and incoming supply per material, and when a shortage starts.
Capacity	Load against available hours per work center and day, and the bottleneck.
Reconciliation	Expected versus issued material per completed work order (known and unexplained variance), supplier receipts, stock counts and inventory trust. (Data Trust)
Scenarios	What-if: demand up, a line losing capacity, a supplier slipping — on a copy, never on your data.
Daily brief	A short written summary of today's priorities, from the same rules; every line links to its evidence.
Integrations	The ERPNext connection, its last syncs and Sync now. (Sync and freshness)
Import	CSV imports (for example stock or orders from a system without an API).
Audit log	Every change people made in TaktSignal.
Settings	Users, plant time zone, work-center calendars and thresholds.

A good daily routine

1. Open the Dashboard. Check the freshness line first: if a source is stale or incomplete, alerts depending on it carry lower confidence.
2. Work down Needs attention — highest severity and most time at stake first.
3. For each alert: read why it exists, check the evidence in ERPNext, then acknowledge, assign an owner or snooze it.
4. When it is dealt with, resolve it and record what actually happened and whether the alert was right. These outcomes are how alert quality is measured — and the most useful Community Alpha feedback.

What TaktSignal will not do

It never changes ERPNext, never reschedules production and never places orders. It suggests where to look; people decide what to change, in ERPNext.