It’s difficult to get good design advice for IBM FileNet systems without engaging an experienced consultant; after all, that’s the ‘secret sauce’ that makes a consulting business profitable. At Kabeus, we’re going to publish our ‘good practices’ for IBM FileNet design with the hope that the customer and partner community will grow through making it simpler and more accessible to get information on what works and what doesn’t.

There are many blogs about designing your classification structures for content and records management systems around the web, but we haven’t found any that are specific to best practice designs for IBM FileNet P8. Most of the existing discussion forums are very specific questions and answers, mostly related to something broken and how to fix it, or someone searching for a response on how to deal with a specific design issue. This blog will be a series of entries that can be read in sequence or searched by a specific topic, all about “building better solutions faster”.

This blog will contain our thoughts on designing solutions for IBM FileNet based on our experience. Our design approaches are not the only way to build a solution, but they’re based on decades of delivering value for our clients, and we think it’s about time to collect the knowledge together and make it available for others. We’re not going to sell the features of the products, and we’re not going to give you a list of shortfalls. We’re going to document our experience and the way we’ve approached the design goals. We make our living from working with the entire range of IBM FileNet products and we like working with them.