Struxen Docs

Issues Log

Every deficiency raised during commissioning, tracked from initiated through closeout, with retest tracking and aging by responsible trade

Issues Log is every deficiency raised during commissioning: equipment startup, checklist and functional-test failures, and site-visit findings, tracked from Initiated through closeout.

It is your project's Observations, scoped

Issues Log is not a second record type. It is the project's Observations register, filtered to the Commissioning category, with an Equipment column, filter, and picker added, and an option to Record retest on an issue that needs one. An issue raised here follows the same ball-in-court, distribution, and lifecycle rules as an observation raised anywhere else in the project, and an observation logged elsewhere under the Commissioning category shows up here too.

The metric strip

MetricWhat it counts
OpenIssues in the Initiated state
In reviewIssues in Ready for review
ClosedIssues closed out
OverdueIssues past their due date
Retest pendingIssues that require a retest with no result recorded yet

Aging by responsible trade

A quiet strip above the register shows how many open issues each trade is holding, and for how long, so it is obvious at a glance who is behind without leaving the page. The full breakdown is one click away in the register's own Trade filter and column.

Troubleshooting

Everything is disabled. You are on the shared demo project, which is read only.

On this page