Skip to content

Permit metrics on the dashboard: the recipe and the permit breakdown tile

The Permit-to-Work module gives Analytics its own metrics: permits issued, concurrent peak, person time, gas tests, suspensions, lead times and more. You can put them on any dashboard tile, and on the breakdown tiles you can also break them down by a permit dimension — type, company, marker, outcome. There are two ways: the ready recipe creates a saved view with one click, the permit breakdown tile becomes part of your own view. At the end, a table says exactly what each metric measures — and what it does not.

  • Permission: editing a view and applying the recipe need analytics:manage; analytics:view is enough to view. The permit breakdown also needs the right to view permits ptw:view, and breaking down by Person and Issuer needs the “Person-level permit report” ptw:report_people.
  • Module: both the Analytics and the Permit to work module must be switched on. While the permit module is off, the metrics are not in the picker, and the recipe and template are disabled with the reason: “This recipe needs the Permit-to-Work module — it is not enabled for this organisation.”
The KPI row of the permit overview showcase view: permits issued, concurrent-open peak, gas-test failure rate, lead time, person time, extraordinary closes, expired permits and risk-assessment deviations.
The KPI row of a permit overview view in the demo organisation, with invented data. The ratios (e.g. the gas-test failure rate) come from calculated metrics in this view.
  1. Open the “Recipes” tab in Analytics and find the permit overview card, titled “Munkaengedélyek áttekintése”. The recipe’s name and description appear in Hungarian, its source language; in the editor the same view is offered as the “Permit-to-work overview” template. The description says: a ready view of the permit module’s metrics: issuance and trend, concurrent-open peak, person time, companies, suspension reasons, weekly rhythm, exceptions and lead times — and the view is yours: it can be renamed and extended.
  2. Read what it creates. The card says: “Creates a saved, company-wide view called “Munkaengedélyek áttekintése” (11 tiles) — it shows up in the view switcher on every site.”
  3. Press “Create the view”. The success message: “The view has been created — find it in the view switcher.”
  4. Open the view in the view switcher. From here on it is yours: in the Dashboard editor you can rename it and add or remove tiles.
A permit breakdown table tile: permits issued and person time per company, with the basis of the breakdown stated.
A table tile broken down by company: the basis of the breakdown is stated above the rows.
  1. Open the Dashboard editor and add or select a “Breakdown (bars)” or “Metric table” tile — the permit breakdown is only possible on these.
  2. Choose a metric (on the table, several columns): the “Breakable” column in the table below tells which ones work.
  3. In the right-hand panel, in the “Breakdown” list, pick the dimension from the “By permit-to-work” group: Permit type, Hazard marker, Company, Status, Outcome, Medium, Person, Issuer or Suspension reason. What is not available with the chosen metric is greyed out, with the reason below: “Not available (…): …”.
  4. Read the tile’s hint. “The permit-to-work breakdown reads the permits issued in the period (identical on screen and in the PDF).”
  5. Save the view: “Save view”. The tile gives the same breakdown in the PDF and in the scheduled report.

The tile’s rows are the values of the chosen dimension, and a sentence above states the basis of the breakdown — “The breakdown counts the permits ISSUED in the period over their whole life — for metrics other than issuance it can therefore differ from the tile’s headline figure.” (for the suspension-reason breakdown: “The breakdown counts suspensions in the period, by reason.”). The tile also shows the number of permits involved (“… permits”; in a table, the “Permits” column).

Metric (as in the picker) What it measures Breakable
Permits issued on the issue day, in the site’s day yes
Of which issued electronically those not issued by paper fallback no
Of which one-person issue (no requester) permits issued without a requester, per the signature chain no
Permits cancelled · Permits closed as extraordinary on the day of cancellation / extraordinary close no
Permits auto-closed at the daily cut-off · Expired but unclosed permits what the daily cut-off closed, and what expired without being closed no
Issue attempts blocked by a gate (by reason: “Blocked issue · …”) issues stopped by the gate no
Approved risk assessments on the day of approval, at the assessment’s plant (a site-wide one at the site); a company-wide approval is not a site metric, so it is not included here; the permits bound to it show in the permit pivot’s “Assessment scope” breakdown, and the number of company-wide approvals is not a metric today no
Issues that deviated from the risk assessment counts issues, not removed items: three items removed on one permit is one decision yes
Permit open time · Time spent suspended the per-plant union within a day: two concurrent permits together cannot exceed the elapsed part of the day; across several plants the parts are summed, so it is plant-hours, not calendar hours no
Peak of concurrently open permits the most permits open at once; across several plants the maximum of the per-plant peaks — a lower bound no
Person time on active permits time workers spent on the job, summed per worker (two people for one hour is two person-hours) yes
Gas tests · Of which failed gas tests the number of tests on the test day, and the failed ones only the failed
Extensions · Suspensions the number of events yes
Request→issue lead time · Issue→close lead time (total and count) the sum of lead times and the measured count no

There is no ratio in the list — on purpose. The gas-test failure %, the average lead time and the share issued electronically are quotients of two counters; you build them in the Calculated metrics editor (e.g. failed gas tests ÷ gas tests, lead-time total ÷ lead-time count). An average of averages would mislead, so the quotient is formed from the sums. The median and P90 lead times are not metrics but a measure of the permit report (they do not add up).

  • A permit breakdown can overlap. One permit can appear in several rows (e.g. several companies or markers), so the rows can add up to more than the whole — the tile says so. On the Person breakdown, person time is the exception: its rows add up, the permit count does not.
  • The breakdown is not always the same question as the tile’s headline figure. The breakdown reads the whole life of the issued permits, so for a non-issuance metric (e.g. suspensions) it can differ from the headline figure.
  • The peak and plant filtering: the “all plants” peak is a lower bound; the true combined peak is on the concurrency page.
What you see Why What to do
“A permit breakdown is only possible on ranking and table tiles.” The tile kind is not a breakdown or table. Use the “Breakdown (bars)” or “Metric table” tile.
“This metric cannot be broken down by a permit dimension.” The chosen metric is not breakable in the table above. Choose a breakable metric, or break it down in the permit report.
“The by-reason breakdown is only available on the suspensions metric.” The suspension reason is only available with the Suspensions metric. Set the metric to Suspensions.
“The per-person breakdown needs a separate permission (permit reports on people).” You do not have ptw:report_people. Ask your administrator, or pick another dimension.
“The permit breakdown needs both the Analytics and the Permit-to-Work module.” One of the modules is off. The module is ordered separately; contact us.

Last updated: