Tag: Governance

What’s the difference between Business Continuity (BC) and Disaster Recovery (DR)?

What’s the difference between Business Continuity (BC) and Disaster Recovery (DR)? This is a question I have had to answer multiple times. It is a very good question and the answer is not simple! So, as a good lazy ‘techy’, I tried to find the answer on the web. That way, when I am asked, all I would have to do is send a link.

I have used this approach multiple times for other questions I have received. It is convenient and a great way to avoid re-typing an answer. However, this time, I was not very successful in my quest to find an answer. I searched the web, multiple times, for hours without finding the perfect “pre-written answer” I was looking for. So I decided to stop being lazy and write it myself.

Now, if you are like me, and you’ve been looking for an answer to this question, feel free to use this one.

So, let’s start with a few definitions from the Business Continuity Institute (BCI) Glossary:

Disaster Recovery (DR): “The strategies and plans for recovering and restoring the organizations technological infrastructure and capabilities after a serious interruption. Editor’s Note: DR is now normally only used in reference to an organization’s IT and telecommunications recovery.

Business Continuity (BC): “The strategic and tactical capability of the organization to plan for and respond to incidents and business disruptions in order to continue business operations at an acceptable predefined level.”

First, I’d like to say that I have a slightly different view of DR than BCI. Now, who am I to disagree with what BCI is saying? Well, bear with me a little longer and you will see how my interpretation of DR might help people understand the differences between DR and BC better. So here’s my definition:DR is the strategies and plans for recovering and restoring the organizations (scratch technological) infrastructures and capabilities after an interruption (regardless of the severity).

Unlike the BCI, I don’t make a distinction between the technological infrastructure and the rest of the infrastructures (the buildings for example) and nor I do differentiate between the types of interruptions. In my opinion, either a system is down or a building is burnt or flooded, both should be considered a disaster and therefore both require a disaster recovery plan.

Therefore DR is the action of fixing a failing, degraded or completely damaged infrastructure. For example, the 2nd floor of a building was on fire; the fire is now out so the initial crisis is over. Now the damage caused by fire must be dealt with; there is water and smoke on the 2nd floor, the 3rd floor has damages caused by smoke and the 1st floor has water damage. The cleanup, replacement of furniture, repair of the building and its structure, painting, plastering, etc. are all part of the disaster recovery plan.

What is Business Continuity then? Business Continuity is how you continue to maintain critical business functions during that crisis. Back to the example, when the fire started, the alarm went off and people were evacuated from the building. Let say you had a Call Center on the 2nd floor and this just happens to be a critical area of your business. How would you continue to answer calls while people are being evacuated? How would you answer calls while the building is being inspected, repaired or rebuilt? Keeping the business running during this time is what I call Business Continuity.

The same approach can be taken with a system crash or when the performance of a system has degraded to the point that it has impacted business operations. So fixing the system is DR and the action of keeping the business operations running without the system being available is BC.

In conclusion, BC is all about being proactive and sustaining critical business functions whatever it takes whereas DR is the process of dealing with the aftermath and ensuring the infrastructure (system, building, etc.) is restored to the pre-interruption state.

Content Management Systems as Cities – I feel like a Mayor!

I recently realized that large enterprise content management (ECM) systems are like a city, but most ECM practices treat them as if they were a building. There’s a big difference in complexity that impacts the operation of an ECM system.Architects can design a building to suit its intended purpose and building management can maintain it. In the same manner an ECM expert can design a system to manage digital content in support of particular business processes. Much of the ECM literature talks of the benefits of clear system architecture and good governance.As an ECM system is deployed across an organization the breadth and number of applications grows rapidly – often into the hundreds – with many different business sponsors and champions! It becomes increasingly hard for any one person to understand all of the different ways that a system is being used, and to exert any effective control. The flexibility accorded users through collaborative, social tools further increases the heterogeneity of an ECM system.Not all ECM application deployments meet with equal success or longevity. In many ways the applications in an ECM system resemble buildings in a city – different sizes, different ages, different investments and different degrees of success. Some buildings are abandoned and some never get off the drawing board!No one designs cities – they are just too complex. Sure there are examples of attempts to do this – the initial design of Brasilia or the redesign of the center of Paris by Haussmann – but over time the efforts and activities of many other people determine how a city develops. In fact cities are very much an expression of human behaviour, culture and society.Overall city management falls to the Mayor and City Council, and their most important tools are Building Regulations and Permits, Ordnances, etc. While you can’t and shouldn’t control everything in a city, you can nevertheless provide some direction and minimal standards. The architects of the many buildings need to get approval for their plans before a building is constructed, and the building operators need to comply with other standards.When ECM was a new concept, the focus was on how to best design and operate a first application for the new system – a new ‘building’ standing in a ‘green field’ if you will. As ECM matures we need to think about how to operate large, multi-application systems. For me a better role analogy for the person with overall system responsibility is Mayor, not Architect. It’s not that we don’t need ECM Architects – in fact we need many of them – but we also need a Mayor and Council to provide a framework for oversight and long-term strategy. And we have to accept at least a degree of disorder that results from the activities of many different people that are only loosely coordinated – Mayors are necessarily politicians, unlike Architects!

Considering the Cost & Value of Digital Content for an Enterprise

The way that the value of digital content changes over time, and how an enterprise content management (ECM) system might help to realize and/or retain greater value was the subject of my last post (http://martin-fulcrum.blogspot.com/2010/06/calculating-value-of-content-in-ecm.html). Lee Dallas retweeted that post, but also referenced a very interesting earlier blog post (2008) by fellow member of ‘Big Men on Content‘ Marko Sillanpääon the cost of content (link). Sillanpää considered content lifecycle costs as follows:Cost of Content = (Annual Authoring Costs + Annual Review Costs) / New Objects per AuthorContent authoring and review are not the only activities that incur cost – there are costs associated with each step in its lifecycle, notably including the costs of distribution, storage and ultimate destruction. Effective content distribution is becoming increasingly important to the realization of value.Cost and value are of course different concepts. The cost of an item does not necessarily reflect its value, as anyone who has watched the TV show “Antiques Roadshow” knows!In business, where there is an emphasis on the bottom line, the value of content ought on average to exceed its cost, or it should not have been created. But for a given piece of content, its cost is generally related to size and complexity, not what it enables. On the other hand, value is tied to enablement and varies over time – often declining gradually or precipitously, but sometimes increasing!It can be hard to explain to people how managing content benefits a business. However, I have found that identifying its ‘enterprise value’ is powerful. A good top-down approach is to reference the value chain of a business, using Michael Porter’s original simple model.People understand that enterprises take input from suppliers and partners and, through a series of steps, add value that can be realized in a final sale to customers. Clearly the effective execution of those steps adds to efficiency. When challenged, most people can identify content that contributes or is even essential to the completion of each of those value steps and their constituent processes. For example, an Engineering Department must create, review and approve engineering drawings, and then pass them on to the Manufacturing Department (see E, C & O value chain).In my experience, taking a value perspective is generally more attractive, especially in growth industries, than a cost and cost avoidance perspective – which has classically been the basis for return-on-investment (R.O.I.) approaches to software justification.  Syndicated at http://conversations.opentext.com/

Customer Community Success Metrics for 2009

Customer communities are all the rage nowadays, but it is not always clear what works and indeed how to measure success.As 2009 draws to a close we have been reviewing how Open Text customer communities have been doing.Background: For those not familiar with Open Text, we are a vendor of enterprise-class software to manage digital files (called content). The term enterprise indicates that we sell to organizations not consumers. We have relatively few customer organizations, but they are often typically some of the biggest organizations in business and government. We estimate that at least 1 in 3 Internet users visit sites that run our software! The software we use for our own communities is the same as we sell. The SitesFor historic reasons, we run three primary community sites (requiring membership) in addition to our typical corporate websites. The community sites are:

  • Open Text Knowledge Centre (KC)
    • Primarily for system administrators of the software we sell
  • Open Text Developer Network (OTDN) which is housed on the KC
    • Primarily for developers using Open Text APIs
  • Open Text Online Communities
    • Primarily for business champions and power users

Site Metrics

  1. The Knowledge Centre is by far the oldest community, dating back to 1996! As you’d expect, it has the most members and the most ongoing activity. Every day approximately 4,000 users access the site, and between 150,000-200,000 documents downloads are performed every month!
  2. OTDN just completed its first full year during which just over 3,200 unique users participated over the past year
  3. Online Communities got started in its present form in 2005. This last year 10,600 members collectively visited 118,000 times over the year

These numbers only measure direct participation. As you might expect, many community members participate through email-mediated discussions.ConvergenceMultiple systems have traditionally meant that there are multiple, disconnected silos of information. As a result, users don’t know where to look and administrators have to duplicate critical content between systems.A better approach is to deploy a single, ‘enterprise library’ of digital files (content) which contains all of the files, but just one active copy of each. The three sites above will soon converge to use the same enterprise library, which will also be used by our corporate website that is open to the general public.One single repository can make user navigation harder unless the most relevant content is presented and organized in a fashion that best meets the needs of each type of user (i.e. persona). Communities of users with similar interests or jobs are one approach to organizing content, but of course there are others, including personalization based on the activities and preferences of specific users.Measuring 2010 successThese communities will continue to develop, but the latest social networking approaches provide new ways to surface important content. As we deploy more social networking approaches during 2010 we’ll have a solid base of community metrics from 2009 to judge progress. As you might expect, activities on external sites like twitter, YouTube and facebook are becoming increasingly important.Syndicated at http://conversations.opentext.com/