Sunday, November 30, 2008  

Open filing systems, why?

It's always confused me why some online document management systems have an 'open filing' approach where all project files are available at point of upload. A better model is one that requires the user to create a 'transmittal/transmission' of the documentation.

Whereas the open filing model is straightforward to use, it doesn't include the audit trail that a transmittal provides, where key transmission metadata can aid reporting and tracking (not to mention reduce the likelihood of disputes).

The second model also more closely simulates the paper-world view. Although having an open filing system provides an effective 'dumping ground' for documentation, this isn't what really happens on a project. There still needs to be an environment where each organization can store and manage its own data prior to release to the required project team. Because of this, there needs to be a location for all project documentation with the ability to selectively distribute them as and when required.

This is my view, but I'd be interested to hear examples of where open filing systems work.

Labels:

Comments:
Couldn't agree more. Whilst some "open filing system" vendors default to visibility only to the uploading party, these systems pave the way for "Claytons Transmissions". That is, to 'publish' documents to say the entire consultant team without actually transmitting them. The parties invited to refer to the documents can read, but can't download them and there certainly is no log of them ever being transmitted. This is a deceitful way of treating project participants and does not contribute to a trustworthy project environment.
 
Good point, Steve. (I should point out that Steve is a colleague of mine at Aconex and, like many of us, also battles against deceit and poor process in the project environment!).
 
Post a Comment



<< Back to home