Top ten reasons why your ECM system runs slowly
Added By Alan Pelz-Sharpe at 12-Jan-2007 | Twitter: @eiwatch |
- The average size of electronic documents has grown to a point whereby current network bandwidth is insufficient to deliver documents to the user in a sensible time frame
- You are running your ECM system on old hardware and operating systems that need upgrading
- You are delivering native format files to end users rather than making use of rendering functionality
- You have allowed your users to dump content into your repository without concern for process, rules or structure, and now it's a humungous mess
- You are running a centralized system but really should have a distributed one
- You bought an ECM system but never bothered to employ basic functions like version control and now have multiple, viral versions of the same content clogging and confusing system and user alike
- Every bit of content created from day one sits online and now runs the servers hot
- Your developers had to fiddle extensively with your ECM platform, and two software versions later it doesn't play nicely anymore with anything
- When designing and budgeting for your ECM system, you totally underestsimated how server hungry the system would be
- All of the above
Remember, buying new ECM software will fix none of the above. BTW, you can replace "ECM" above with "Portal," "Search," or "CMS," and keep the same list.
Next steps: Get a free research sample or purchase complete vendor evaluations to obtain immediate access.
Categories: Alan Pelz-Sharpe, Enterprise Content Management, Implementation
