Month: October 2013
-
We don’t need no stinkin’ change management
Funny, but I don’t agree with Dilbert on this one. Better that we do both proper change management AND have sensible strategies for Asset Lifecycle Information Management system implementations. (Click the title if you don’t see the image) http://www.dilbert.com/strips/comic/2012-10-29/
-
Horses for Courses
1. “Horses for Courses” One could write a letter with Microsoft Excel or calculate a table with Microsoft Word, but both are designed for particular purposes. The same is true for systems that were designed for engineering information management from the ground up, verses systems that are designed for simple office document management. The best…
-
Milestone vs. In-Progress
Since there’s a mountain of evidence (Search this blog for “Do you want to manage engineering”) that an engineering specific repository is necessary to support the complexity of engineering content management, engineering content review and engineering content publishing, some EDMS vendors will admit that they cannot provide all of the capability of ProjectWise, but that their…
-
The Fallacy of the “Single” Repository
While it seems logical that having a single repository for the whole enterprise is desirable, the post “Engineering Content is Different” clearly shows that a system that is purpose built for engineering data is necessary for the engineering team and larger organization to gain benefit. While providers of third party tools that overlay on top…