HRMS

HRMS began with TXG, which needed one system for its people and its performance tracking. It started from TXG's KPI monitoring workflow, where drawing tasks and QA errors feed a monthly score, and LiveWires widened it into a full HR platform that more than one company can use.

The KPI score had to combine task productivity, quality, attendance and behaviour, with weights that change per company, region and department. Seven roles had to see different slices of the same data, and one company's data had to stay hidden from another's. People also work on several projects at once, so a single “team” field would not do.

One shared database where every query is filtered to the caller's company, so a cross-company read finds nothing. A permission matrix lives in the database, so each company edits its own roles. KPI scores are recalculated in the background after each approved task, leave, attendance change or rating, and staff join projects through a membership model that allows matrix staffing.

A role-aware home dashboard, a company KPI dashboard with a score ring, six-month trend, regional breakdown and top-performer and at-risk lists, and a per-employee breakdown. Around it: configurable KPI weights with region and department overrides, a permission setup matrix, leave approval chains, payroll runs, a recruitment pipeline, grievances and an org chart.

In production, deployed automatically from the main branch with a health check and automatic rollback if a release fails. No user or performance figures are recorded, so none are given.

Gaps the team has listed: real email delivery, timesheets and shift rosters, notification preferences, single sign-on, a final-settlement calculation and scheduled backups.