With part of the team at home, the question moved. It is no longer who is at the desk — it is what is being used, for how long and to what result, wherever the person happens to be.
Real-time measurement · the basis for renegotiating licences and seeing distributed work
Working from home
The distant machine produces numbers too.
A workstation at an employee’s home falls under the same measurement as one at head office — time in use, application open, a licence sitting idle. It is not a camera and it is not a screenshot: it is the same count, applying to people working from home as well.
tz0.suaempresa.local/metering/energia
Tz0 Metering · web console
Console capture from an estate in production. Machine and person identification replaced; figures untouched.
What the module does
Measuring the work without watching the person.
The module measures resource use, not individual behaviour outside the scope of work. That is what separates productivity management from invasive monitoring — and it is what keeps its use within the LGPD, Brazil’s data protection law.
Real software usage
How long each program is actually used on each machine, in real time and with history.
Idle licences
The licence you pay for and nobody uses shows up before renewal. It is the line in the contract you can cut without anyone noticing.
Distributed teams
Working from home is work, and work gets measured. Visibility of people outside the office, on the same basis as those inside it.
Idle time and peaks
Identifies idle periods and overload periods — the basis for redistributing work instead of hiring.
One dashboard
One screen with what the team is using right now, by department, by project or by person.
Policy violation
Access to confidential data outside the authorised group becomes an alert, not a late discovery.
Without blocking applications
Improves performance by measuring and showing, without turning the workstation into a locked-down machine.
Windows, Linux and Android
Three platforms and three languages — Portuguese, English and Spanish — in one console.
How it works
From measured usage to a contract decision.
Measurement only counts if it becomes a decision. The path here ends in a renegotiated licence or redistributed work.
Console
From the dashboard to the report, all in the browser.
The 5 groups below the workday, and who pulls the average. Average index of 41%, 2 points above the previous week. Development reaches 65% of the workday; each machine spends 5h19 a day switched on and unused; and in Administration only 1 of 3 machines reported.Who rose and who fell, in points of the workday. Quality gained 7 points, Support 5, and Administrative lost 3. The line marks 100% of the workday: no group reaches it.The report comes already read. In 30 days, 239 programs and 1,728h13 of use by 59 users: time rose 250%, 112 programs appeared for the first time and 5 of them account for 47% of the time.
Printing, down to the cent. 50 print jobs in the week, 50 pages, 1.6 MB and R$ 10.17 in cost — with the machine, the person and the printer that ran the most. Paper is inventory too.The week on the web, compared with the previous one. Time on websites fell 36% (from 143h17 to 92h23) and the productive share went from 76% to 69%. Tz0 draws the conclusion itself: 2 people account for 94% of unproductive time, and one targeted conversation does more than a rule for everyone.
What changed on the web this week. WhatsApp Web went up 2h31, cloud Outlook dropped 26h28 and five sites appeared for the first time in 90 days. Each change shows the site’s class next to it.The topic, not the term. 799 Google searches and 280 YouTube videos classified by subject: 35% of searches are about technology and work, 32% of videos are music. What was searched does not appear.Eleven teams, one yardstick. Average and total side by side in every column — activity, productive, unproductive, neutral, uncategorised, idle — and a verdict at the end of the row, from “highly productive” to “highly unproductive”.One workday, with proof the number holds. 6h30 productive in a 9h10 span: 81.38% of an 8-hour day. Because 99.2% of active time is classified, the index reflects real work. And you can ask about the day in plain language.Hour by hour, no guesswork. The timeline shows when the person was productive, stopped, locked or unlocked the screen. Each column is a 60-minute hour, compared with the average of 45 active minutes per hour.Which documents the time goes into. In 30 days, 775 documents and 47h53 of use by 16 people; time rose 191% and 733 documents did not appear in the previous period.41% of the energy was spent with nobody using the machine. In 7 days, 40.81 kWh, of which 16.93 kWh with the machine idle, suspended or with the monitor on standby.Suspending workstations after 15 idle minutes would save 1,475 kWh a year, 69% of consumption. Seven workstations spent 382 hours switched on outside working hours in one week.The machines don’t sleep. The heat map shows Saturday, Sunday and late nights with the fleet on, hour by hour.
Screens from a real estate in production, not a demo environment. Anything identifying people, team names, document names and internal addresses was replaced with generic equivalents before publishing; figures, percentages and the interface itself are untouched.
Trend
Each person’s trend, against their own baseline.
Each person is compared with their own baseline, not with the group average. A drop shows up weeks before it turns into a difficult conversation, and a rise is recorded too.
Who is slipping before it becomes a problem. Of the 17 people with an 8-week trend, 2 are in a sharp drop, one of them from 131% to 47%, and 4 are rising. Tz0 compares the last 5 business days with the previous ones and tells you who to talk to.The trend, not the day. Each person against their own baseline: from 131% to 47% is a sharp drop (-64%); from 17% to 72% is a rise (+314%). The sparkline shows the curve of the last few weeks.Week by week, day by day. Each person’s index on each business day and the week’s verdict, from 37% (Unproductive) to 123% (Super productive), with an arrow when the week changes band.The trend, week by week, with the conclusion ready. Over 4 weeks the index reached 78%, 32 points above the previous period. Thursday is the weakest day (67%); two people dropped 29 and 18 points in the last week. And the team was 113 hours below the contracted hours.Week by week, the arrow shows where each person is heading. The average fell from 89% to 76% in three weeks. Thursday stays at 67% while Tuesday and Wednesday reach 88%, and a day that is repeatedly low is usually meetings or travel.
Workday
Where the contracted hours went.
Payroll hours on one side and what the machine measured on the other: productive work, absence, arrival and departure outside the tolerance, machine on with nobody at it.
Where the workday went. On one day, 21 people had 164h00 contracted: 45% became productive work and 48% was absence. Only 5 of 21 arrived and left on time, and the machines stayed on for 156h44 with nobody at them.Who arrived and left on time. Each bar is one person’s day over the account’s business hours (08:30-18:00): green within the tolerance, amber outside it.
Data quality
When the number misleads, the index warns you.
Machines on but unused, long sessions with no break, work outside business hours: Tz0 flags what can distort the measurement and shows what is still unclassified.
The index that doubts itself. In 31 days there were 2,344 long idle sessions (3,628 hours of machines on but unused), 767 sessions outside business hours and 1 “productive” session of 2h+ with no break at all, which may be a video or a mouse jiggler. Tz0 flags it and the manager checks.Each signal, counted and located. 89 long sessions outside business hours and 358 patterns that repeat day after day. The heat map shows in orange the hour when work starts outside business hours.The index says what is missing to get it right. The queue puts what weighs most first: a single executable with no class accounts for 41% of unclassified time. Each item registered improves everyone’s index.An index is only worth something if the classification covers the usage. 98% of time in programs and 87% of time on sites fall into some category; of the 505 items still outside, the rule already suggests 51 entries.
License
Paid software nobody opens.
Adoption measured by program and by person: how many have the software, how many opened it and for how long. These are the numbers you take to the renewal.
Paid license, opened by nobody. In 7 days, PowerPoint was opened by 0 of 24 people and Outlook by 1 of 24. The Office suite took 9% of active time, and 22 machine-user combinations opened none of it.
Machine activity
A machine’s day on one screen.
Programs, screens, connections and idle time for the same machine on the same day, with a reading of what deserves attention. Remote access servers are part of the same measurement.
The product reads the day and tells you what to look at. 21 screens with a CPF or password, 1h07 outside business hours, 389 connections with alerts and one machine idle for 15h53 with a session open.
Everything that happened on a machine, in one day, on one screen. 6h17 in programs against 15h53 idle, 416 screens captured (21 with sensitive data) and 389 connections with alerts.Each machine keeps its day-by-day history. 30 days with data and an average of 14h41 of use: on Oct 6, 23h18 were measured, from midnight to midnight.
Remote access servers are measured too. In 7 days: 25 sessions, a peak of 15 concurrent and 13 SQL login attempts from outside: brute force.
What changes in practice
Eight questions that stop being guesswork.
How much of the licensing you pay for is genuinely in use.
Which contract can be cut at the next renewal.
Whether the team at home carries a load similar to the one in the office.
Where there is idle time and where there is overload, by department.
Whether usage of a critical piece of software has gone past what was contracted.
Who reached a confidential repository from outside the authorised group.
Which software the company pays for and nobody opens.
How to justify a cut or a purchase with data rather than impressions.
Included with the module
Three tools in the same package.
A new report does not become a project. We do not build bespoke work for a single customer, but we look at every request: when the need serves everyone, the report goes into the product and reaches all customers in the next update.
Tz0 EIS
Report builder
Ships with the package, not sold separately. It is for people who want to build their own reports outside the browser.
Tz0 TNetX
Development platform
Carries agent communication across segmented topologies and lets the product be extended.
Tz0 Dashboard
Operations dashboard
The state of the estate on one screen, with whatever went off-target at the top. More than 600 ready-made reports, covering every module.
Who works this way
Measure in order to stop spending.
We cut costs with Tz0 — we stopped spending. Not spending is a gain too.
Translated from Portuguese
Caldema
Manufacturing
Tz0 Cycle gave the team more agility and more visibility over the company’s demands.
We use cookies to measure the site’s audience (Google Analytics) and to measure and show Trauma Zer0 ads (Google Ads). They are already active; you can reject them now or later under “Manage cookies”. Cookies needed for sign-in and language do not depend on this choice.
Necessary
Always active
Keep you signed in to the customer area, remember your language and protect the forms. The site does not work without them.
Preferences
O armazenamento ou acesso técnico é necessário para o objetivo legítimo de armazenar preferências que não são solicitadas pelo assinante ou usuário.
Audience measurement
Google Analytics: counts visits and page views in aggregate, so we understand how the site is used.O armazenamento ou acesso técnico que é usado exclusivamente para fins de estatísticas anônimas. Sem uma intimação, conformidade voluntária do seu provedor de serviços de internet ou registros adicionais de terceiros, as informações armazenadas ou coletadas apenas com esse objetivo geralmente não podem ser usadas para identificar você.
Advertising
Google Ads: measures which ads led to an evaluation request and lets us show Trauma Zer0 ads to people who have visited the site.
