Why is it useful?
Traceability: The unique issue ID is critical for tracking and referencing specific comments or issues across multiple documents and communication threads.
Clarity: Without the unique ID, comments in the printed summary are ambiguous, especially when multiple issues are flagged in a single document.
Efficiency: Reduces the need for manual cross-referencing between the printed summary and the PW DM system.
Who would benefit?
Project Team: For quick review and reporting without needing to log into the system.
Document Controllers: For compiling and distributing transmittals with complete traceability.
Reviewers/Approvers: To ensure their comments are accurately tracked and addressed.
EPC Contractors & Stakeholders: For maintaining a clear audit trail during design reviews and approvals.
How should it work?
When using the "Print with summary" option, the system should:
Include the Unique Issue ID next to each comment in the summary.
Maintain the same formatting and structure as seen in the PW DM interface.
Optionally, allow toggling this feature on/off for flexibility.
|
Practical use of functionality?
Scenario: An EPC contractor submits a set of engineering drawings for review. The project team raises 15 issues across 5 documents. Each issue is assigned a unique ID (e.g., SUB-001, SUB-002, etc.). The Document Controller prints the comment summary to share with the wider team. However, the printed summary only shows comment text and flags, not the unique IDs. The Project Team wants to discuss specific issues in a meeting but cannot reference them directly from the printout. They must log into PW DM, locate each issue manually, and match them with the printed comments — a time-consuming and error-prone process. With the enhancement: The printed summary includes the unique IDs, allowing the Project Team to reference and discuss issues directly from the printout, improving meeting efficiency and decision-making. |
|||||||||||||
|
What is the impact of not doing this?
|
|||||||||||||