Since I’ve been in the business of business continuity planning software for more than 13 years, I’ve seen a lot of BC plans, software packages, and implementations – and I’ve seen all of these go wrong in one way or another. I’ve collected my thoughts about what to look for in your BCP software vendor into a blog series that will serve as a guide for companies thinking of deploying BCP software or moving to a new vendor. Leave your thoughts in the comments!
In this first installment, I’d like to discuss code ownership. It’s a more important issue than you might think. Complete ownership of all software code by your vendor is critical. I’ve seen vendors out there who have pieced together their products from modules created and owned by several other vendors/partners. In limited cases, this can make for a stronger product as experts in various areas are responsible for different pieces/functions. However, more often than not, I’ve seen that BCP software developed by a number of vendors is susceptible to several problems including:
Code Consistency and Integration Problems: Software code that is developed across multiple organizations frequently suffers from a lack of consistency, as various developers are creating modules in isolation, rather than as part of an integrated environment. Furthermore, if one company discontinues operations or the partnership agreement, all of the software is put at risk.
The Software Platform Changes: One of the biggest trends in BC software is to utilize document management platforms like SharePoint to serve as the primary engine of the software. This proves to be quite risky on a number of levels. First, the software’s primary operation cannot be controlled by the vendor, but is instead driven by a 3rd party (e.g. Microsoft) – leaving the BC software vendor and its clients on an unpredictable ride. Second, the code for such products changes frequently and sometimes evolves into something completely different. For example, SharePoint 2003 and SharePoint 2010 are completely different products. If your BC software is based on SharePoint 2003, you’ll be stuck with outdated technology, as the cost of upgrading is substantial. You will notice many future versions of products have simply made aesthetic changes because they are locked in 3rd party code and the cost of upgrading to the new platform would be phenomenal.
Software support: The original provider of the code will provide the best support. While the “purchaser” or “brander” of the code may have training in the product, you may have to go to a variety of different companies to get support on different parts of your software.
Higher costs: Modules and separate packages cost more. In situations with different vendors coming together to offer a complete BCP package, each provider needs to get their piece of the pie, resulting in higher costs passed onto you.
BC software vendors frequently will buy code or use unstable platforms and call them their own. Go beyond the “branding stamp” and ask the provider who the original developer of their code is, what platform they use, and who currently owns the rights to the code. Ensure that you have a complete product on a stable platform, developed by ONE vendor and not at the mercy at another.
-Frank