Currently the columns on Deliverables Management in Infrastructure Cloud are limited to the following:
Subject
Package ID
Classification
Issued
Purpose
Status
Progress
Actions
In ProjectWise Explorer you also have:
Response due date (covered by actions in BIC)
Acknowledgement due date (covered by actions in BIC)
Sender
Sender package ID
This is barely sufficient for a Project Manager that needs to keep track of hundreds of pieces of correspondence. I have had numerous complaints from my project managers and document controller that they need more information in this view in order to find information.
Example columns that would be useful:
Sender
Receiver
CC (for RFIs)
List of attachments
Number of attachments
All custom fields added by the user. For example we use Priority, Location, Discipline, package Number, Reference No. But these will vary per company and per project.
Who responded
Response date time
Have documents been imported
Document import location (with a link to take you direct to them)
Im summary, every piece of data within a Transmittal, RFI or General Corro should be able to be displayed in a column, searched and filtered. This is basic functionality of any mail system.
Practical use of functionality?
Improved Project Oversight – Project Managers can quickly filter, sort, and locate key correspondence, reducing time spent searching for information.Enhanced Tracking & Accountability – Being able to see sender, receiver, CC, and response details in a structured view allows teams to track ownership and accountability more effectively. |
|
What is the impact of not doing this?
Reduced Efficiency – Without sufficient filtering and sorting capabilities, users spend excessive time manually searching for correspondence, impacting productivity. Risk of Miscommunication & Errors – Lack of visibility into who received or responded to correspondence can lead to missed deadlines, duplicated efforts, and project delays. Limited Usability for Large Projects – Managing hundreds of transmittals, RFIs, and general correspondence without adequate metadata visibility creates operational bottlenecks. Poor Integration with Existing Workflows – Custom fields are essential for project-specific workflows. Without them, users must resort to external tracking methods, increasing complexity and the risk of data inconsistencies. Compliance & Auditing Challenges – The inability to display and filter critical metadata may lead to difficulties in auditing project correspondence and ensuring compliance with contractual obligations. |