Activity Tracking & Session Replay

What you stop doing every day

Before this module, the production manager keeps a spiral-bound A4 pad next to the terminal. Every time a loom supervisor logs in, the manager jots the time, the user name and the screen they opened. If the supervisor changes a beam allocation, the manager flips back, finds the line and adds a note: “beam 12 → loom 4, 14:23”. At shift end the pad is handed to the office clerk, who types the entries into a spreadsheet. The spreadsheet is saved on a shared drive with a date-stamped file name. By Friday the drive is cluttered with five files, none of them searchable by user, by document or by time.

The accountant has a separate routine. When a journal is posted, the accountant prints the journal, signs it and files it in a lever-arch folder. If the ledger later shows an unexpected debit, the accountant must pull the folder, page through each journal and hope the handwritten narration matches the entry. If the narration is missing or illegible, the accountant calls the supervisor who raised the journal. The supervisor may have left the shift; if not, they must walk to the office, log in again and try to recall which beam or towel count was changed three days earlier.

Both routines rely on manual transcription, which means transcription errors. A beam number mistyped becomes a stock discrepancy; a missing narration becomes an unexplained ledger movement. The pad, the spreadsheet and the lever-arch folder are not linked, so no one can trace a single document from login to ledger.

How a document moves through the system

Consider a beam allocation change. The loom supervisor logs in from the shop-floor terminal. The module records the login: browser, operating system, device, IP and geo-location. The supervisor opens the Beam Allocation screen. The module notes the page visit and starts a timer. The supervisor selects beam 12, changes the loom from 3 to 4 and saves. The module logs the edit: document type, document number, field changed, old value, new value, timestamp and user. If session replay is enabled, the module also records low-bandwidth screen frames.

When the supervisor posts the allocation, the module logs the post operation. The stock ledger is updated: beam 12 moves from loom 3 to loom 4. The general ledger is updated: the work-in-progress account for loom 4 is debited; the work-in-progress account for loom 3 is credited. The module logs both ledger movements, linking them to the original allocation document and to the user who posted it.

Later, the production manager can open the Activity log, filter by user or by document, and see the entire chain: login, page visit, edit, post, stock update, ledger update. If the manager needs to verify what the supervisor saw, they can open the Session replay and watch the exact sequence, including the values on screen before and after the change.

The reports and the decisions they support

Illustration: a loom supervisor reports that beam 12 was allocated to loom 4, but the stock ledger shows it still on loom 3. The production manager opens the Activity log, filters for beam 12 and sees that the supervisor saved the allocation but did not post it. The manager replays the session and confirms the supervisor closed the screen before clicking Post. The manager posts the allocation, the stock ledger updates, and the discrepancy is resolved.

What goes wrong without it

Without activity tracking, the plant relies on memory and paper. A supervisor changes a towel count on a production order but forgets to tell the accountant. The accountant posts a journal based on the old count, creating a variance in the cost ledger. When the variance is spotted, no one can say who changed the count or when. The accountant must reverse the journal and re-post it with the correct count, adding two more entries to the ledger and delaying the month-end close.

Without session replay, disputes about data entry become unresolvable. A supervisor insists they entered the correct beam weight; the stock ledger shows a different value. The production manager must either accept the supervisor’s word or assume a system error. Neither option is satisfactory. The manager may ask the supervisor to re-enter the weight, but if the error was in the original entry, the ledger remains incorrect.

Without retention limits, log files grow until they fill the server. The IT manager must manually delete old files, risking the deletion of logs that are still needed. If a log is deleted prematurely, the plant loses the ability to trace a document or verify a ledger entry. The accountant may have to reconstruct the entry from paper records, if they exist.

Without switchable tracking, the module runs continuously, consuming storage and bandwidth. The plant may disable it entirely to save resources, losing the ability to track activity when it is most needed. With switchable tracking, the plant can enable it only during critical periods, such as month-end or when a new supervisor is trained.