Frequently asked questions and messages
Manual — Commissioning · chapter 10 of 10
The table explains the messages and warnings that may appear in commissioning. The most common questions come right after.| Message | Where | Why | What to do |
|---|---|---|---|
| N level(s) created; N already existed. | Create default levels (L1–L5) | result: levels with the same name are not repeated | — |
| Name is required | New type | empty name | fill it in and save again |
| Cannot delete: the type is used by N task(s). | trash can of the type | there is a project task with that type | rename it or unmark the phase; or change the type of the tasks first (chapter 2) |
| Register at least one type marked as commissioning phase to build the routines. | Routines by level | no level registered | Create default levels (L1–L5) or New type with the switch on |
| Computed from tickets — the typed value is ignored. | project task form | the task is a phase | the % comes from the tests (chapter 3) |
| This task is a commissioning phase: its % is computed from the tickets and cannot be dragged. | project tasks Kanban | you dragged a phase | — |
| Pick at least one phase and one asset. | Generate tickets | nothing selected | select a phase and an asset |
| No asset in the project scope for this filter. | Generate tickets | no asset of the project site with that filter | clear the filter; check the site of the assets (chapter 3) |
| Codes not found: … | Generate tickets | the pasted code is not a tag, serial or start of an asset name in the scope | check the code in the asset record |
| no routine — pick a template | phase column in the batch | there is no routine for that level and asset type | pick one in Task template or fill in the routine (chapter 2) |
| already in phase (d/t) / skipped already in phase | batch | the asset already has a ticket in this phase | nothing; to redo the test, use the retest (chapter 7) |
| skipped no task template | batch | neither a routine nor a chosen template | pick the template |
| skipped out of project scope | batch | the asset is not on the project site or below it | check the site of the asset |
| Previous incomplete: … / Previous phase incomplete: … | batch, matrix, asset | an earlier phase of the same system is not fully approved for this asset | only a warning — go on or wait, the team decides (chapter 6) |
| Technician cannot be assigned: no profile in the ticket site. | Generate / Preview | the chosen technician has no profile on the project site (the panel list already brings only those who can; the message appears if the profile changed with the panel open) | pick another technician or give them a profile on the site |
| The batch stopped: N of T ticket(s) created. Check the log and run again — tickets already created are not repeated. | Generate | error in the middle of the generation | generate again with the same selection (chapter 4) |
| Mark as FAILED? This opens a GQE item and a retest task on this ticket. | Failed button on the task row, on the web | confirmation | OK to fail the task |
| Failed: GQE item #N and retest task #M opened | web, after failing | result | handle the GQE item (chapter 7) |
| not evaluated (completing without a result = approved) | ticket task on the web | no result yet | choose the result on the row, or complete the task and answer the question |
| Confirm failure? — A GQE punch item and a retest task will be opened. | web and app, when completing | confirmation | Failed to confirm |
| Flagged for retest — the task stays open. | web and app | you chose Retest | redo the test and complete it again |
| Escalate this item to an NCR? … | Escalate to NCR | confirmation | confirm |
| This item was already escalated (RNC-…) | Escalate to NCR | there is already an NCR for the GQE item | open the NCR from Links |
| No tickets linked to the phases yet — the matrix is empty. | Gantt PDF | there are phases but no ticket | generate the tickets (chapter 4) |
Frequently asked questions
Section titled “Frequently asked questions”- The Commissioning tab does not appear in the project. The project needs at least one task whose Type is a level (marked as Commissioning phase) or with % from ticket tasks on (chapter 3).
- I chose Approved by mistake (or the task was completed without a result). Now what? Click Failed on the task row, in the Tasks tab of the ticket on the web: it opens the GQE item and the retest task (chapter 5).
- The technician has no Tasks right in the profile. Can they complete the task? Yes, if they are the technician of the ticket or of the task (directly or through the technician group): they complete, give the result, edit and create tasks on the ticket, on the web and in the app. Deleting a task still requires the right (chapter 5).
- Does the “Previous incomplete” warning prevent generating or running? No. It is only a warning: the ticket is generated, run and counts in the phase. The team decides whether to wait for the earlier phase (chapter 6).
- Have regular tickets changed? No. Test result, automatic GQE item and retest only exist in a ticket linked to a phase. The others complete as always, on the web and in the app.
- I generated the batch and the technicians got no e-mail. It is on purpose: the batch does not notify. The tickets appear in the list and in the app after the sync (chapter 4).
- I need to repeat an approved test. The batch does not duplicate an asset in a phase. In the Tasks tab of the ticket, click Retest on the task row: it reopens, stops counting and the cell goes to Retest. Once the test is redone, complete the task and answer Approved (or Failed, which opens the GQE item and the retest task).
- An asset does not appear in the matrix. The matrix only shows assets already in a ticket of some phase. To include it, use Generate tickets: all the assets of the project site are listed there (chapter 4).
- An asset does not appear in Generate tickets. It must be on the project site (or below it, or be recursive from a site above) and within your reach; tools do not enter (chapter 3).
- The legend has Failed (red), but no cell turns red. That is expected: the failure creates the retest task right away and the cell goes to Retest. The failure stays in the task badge, in the GQE item and in the asset dossier (chapter 6).
- The phase % does not match the completed tasks. The % counts approved tasks: failed and in-retest tasks do not count, and a failed task that has a retest leaves the count (chapter 3).
- I cancelled a phase ticket. What about the %? The ticket leaves the count: its tasks do not count in the phase % or in the matrix, and the phase can reach 100% without it. The asset can be generated again in the phase with Generate tickets (chapter 6).
- I failed a task and no GQE item appeared. There was already an open GQE item for that task, or the ticket is not linked to a phase. Check the Commissioning block in the GQE items of the job (chapter 7).
- I want a different template for a single asset. In the generation, change the Task template on its row; for all the projects of a site, save the routine on that site (chapter 2).
- Does H2O issue the commissioning certificate? No. It organizes the process and gathers the evidence — matrix, Gantt PDF, asset dossier, GQE items and NCRs. The formal acceptance remains with the commissioning team and the client (chapter 1).
Was this page helpful?
Thanks for the feedback!
Got it — we will improve this page.