We act as the client and receive all of our deliverables through PWDM. We request the following metadata on every document we receive: document code, project code, location, originator, discipline, project milestone, location code, document type, serial number, state, suitability, work package, security classification and work zone.
At the start of every project we provide our consultant with an Excel file that contains allowed values for each of these fields.
e.g. the options for Project Milestone will be: "Concept Design - 20%", "Concept Design - 80%", etc.
Currently, the consultant is able to submit to us any value in each of these fields. e.g. the Project Milestone attribute could contain "Issued for Construction" when that isn't a valid milestone, or worse it could contain "20% Concept Design" which is an incorrectly formatted version of our allowed value.
This can cause major issues with people being unable to filter for specific metadata in all the documents we receive. It means we can't reliably used saved searches on documents we receive. It results in people spending more time looking for information than if we didn't use ProjectWise at all.
Suggested solution:
For each required document metadata field, allow one party to define allowed values for every field. The other party can then import these settings into their PWDM setup.
If a document is attached to a transmittal with metadata that isn't one of the accepted values, that Transmittal cannot be sent until it is fixed.
Competitors products:
Competitors like InEight and Aconex do not allow submission of documents with incorrect metadata. Without this basic functionality, ProjectWise will not be able to compete.
Practical use of functionality?
|
|
What is the impact of not doing this?
|