Tag: Business Continuity

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.

The Implicit Value of Content is Realized Through Business Process

As I have noted before, much of the historic discussion in the document management field has concerned the cost of producing content, or the cost of finding existing content.But the value of a document, or any other piece of content, is seldom the same as its cost of production.I was chatting about this the other day with my colleague James Latham. He used an invoice as an example of a piece of content that may be managed by an enterprise content management (ECM) system. James noted that, ‘There is inherent or explicit value in an invoice’. In fact the value of an invoice is fairly tightly linked to the cash it represents.A $10 bill has an explicit value of $10. Likewise a delivered invoice for $10 has a value of about $10 to an organization. Arguably it is not quite as valuable as $10 cash given the delay and perhaps uncertainty of payment, but it is close enough in most cases and will be treated as such in an accounting system.There is a case where a $10 bill is worth much more: if it is a rare, old $10 bill, it may have a lot of implicit value (e.g. to collectors it may be worth hundreds of dollars) above its explicit value of $10.Tangible value (explicit plus implicit) is established by sale of the item itself or the recent valuations of comparable items. But it is hard to think of invoices, especially electronic invoices (i.e. digital content), as having any implicit value.Are there other kinds of enterprise content besides invoices that clearly have implicit value? I think so. Here’s a good example: documents that support a patent application for a product with large market potential may have huge implicit value that greatly exceeds their cost of production and their explicit value at a given moment. This implicit value may become more explicit over time with the issue of a patent, together with product and market advances. At some point an intellectual property sale could attribute very significant tangible value to the documentation.In this patent documentation example, the application of process over time helps to create tangible value. In ECM discussions we often speak of the context of content as helping to give it meaning, but clearly we also need to consider how process can give it value.

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/

Calculating the Value of Content in ECM

It’s only worth expending effort to manage something if it has value – usually positive, but sometimes negative. So the concept of content value is implicit in enterprise content management (ECM).On the other hand, the value of a given content object (i.e. digital file) such as an email or document generally declines over time – or at least this is the common wisdom. I have seen graphs drawn mapping ‘value’ over ‘time’, with a smooth decline of value tending to zero. However, such a representation is clearly an average of value across many types of enterprise content.If you look at individual pieces of content, then you’ll find different profiles:

  • In compliance, a piece of content may retain 100% of its value for a defined period of years and then abruptly drop to having no value, or even having negative value (liability) that should trigger its destruction
  • In knowledge management, a piece of content may have declining value over time, but then because of some new event may suddenly have increased value

But this perspective is of the Inherent or Independent Value of a piece of content – the value is assessed entirely based on the information contained in the object. But it seems to me that there are at least two other factors that impact value:

  • Context – when correctly combined with other prices of content a given piece of content may have greater value. For example a specifications document is more valuable together with the associated requirements document. Value can often be realized by the way in which context is presented between content items – how they are grouped, ordered or ranked.
  • Impairment – Ironically, the value of a piece of content may be impaired by efforts to manage content. If you mix valuable pieces of content with large amounts of irrelevant materials, that should have been destroyed, you reduce the chances that the valuable content can be found and its value realized. Keeping everything is usually a bad idea. And often users impair value when they misclassify content.

So the available value of a piece of content to an organization may be expressed as follows:Available Value = Inherent Value x Context / Impairment What this says is that content management efforts can be beneficial, but if not done well can actually be destructive.

Social collaboration for productivity and problem solving

Check out this SlideShare Presentation from my colleague Deb Lavoy, covering the Open Text Social Workplace (OTSW) offering. Just this week we put an OTSW system dubbed ‘Hub’ into full production use for Open Text staff (now over 4,000 users). Social collaboration for productivity and problem solving View more presentations from dllavoy.

Google’s impact on enterprise content management

Without a doubt Google has had a huge impact on the enterprise perspective on content management (ECM).

The pluses and negatives were highlighted by two blog posts yesterday:

On the plus side, John Mancini of AIIM listed three, “fundamental assumptions about information management that affect the ECM industry,” in his “Googlization of Content” post:

  1. Ease of use. The simple search box has become the central metaphor for how difficult we think it ought to be to find information, regardless of whether we are in the consumer world or behind the firewall. This has changed the expectations of how we expect ECM solutions to work and how difficult they are to learn.
  2. Most everything they do is free…
  3. They have changed how we think about the “cloud.” Google has changed the nature of how we think about applications and how we think about where we store the information created by those applications. Sure, there are all sorts of security and retention and reliability issues to consider…”

On the negative side, Alan Pelz-Sharpe made a post today in CMS Watch titled, “Google – unsuitable for the enterprise”. Alan introduced his piece by saying:

For years now Google has played fast and loose with information confidentiality and privacy issues. As if further proof were needed, the PR disaster that is Buzz should be enough to firmly conclude that Google is not suitable for enterprise use-cases.” He went on to say, “It is inconceivable that enterprise-focused vendors… would ever contemplate the reckless move that Google undertook in deliberately exposing customers’ private information to all and sundry with Buzz.”

Google is a hugely successful company, and they are extremely profitable. However, they are not a software company. Fundamentally they are an advertising placement company and everything they do is motivated by maximizing advertising revenue, whether directly or indirectly. 99% of their revenue comes from advertising that pays for every cool project they do and every service they offer.

While Google services to consumers have no monetary charge, they are not free:

  • You agree to accept the presentation of advertisements when you use Google products and services; most people believe these to be easily ignored despite the evidence of their effectiveness.
  • More importantly, you agree to offer provide information about your interests, friends, browsing and search habits as payment-in-kind. Mostly people sort of know this, but don’t think about it. If you ask them whether they are concerned that Google has a record of every search they have ever performed, they start to get uncomfortable. I expect most of us have searched on terms, which taken out of context, would take a lot to ‘explain.’

While most consumers in democracies are currently cavalier about issues of their own privacy, enterprises most certainly are not. Indeed, the need for careful management of intellectual property, agreements, revenue analyses and a host of other enterprise activities captured in content is precisely why they buy ECM systems.

The furor over Buzz points out that Google did things first and foremost to further its own corporate goals, which clash with those of other enterprises.

In contrast, Google’s goals require it to align with user needs, especially for good interfaces. An easy-to-use interface encourages and sustains use. That ought to be obvious to everyone, but when the effects of the interface on usage are easily measureable and directly tied to revenue (as in the case of Google Search), it becomes blatantly and immediately evident. In contrast, the development of an interface for an enterprise software product may take place months or even years before the product is released. Even if detailed usability research is done with test users, and in-depth beta programs are employed, the quality and immediacy of the feedback is less.

Besides easy interfaces, enterprise content management users expect ‘Google-like’ search, and are disappointed. There are generally two reasons for this:

  • Search results have to be further processed to determine if a user can be presented with each ‘hit’ based on their permissions
    • Typically 70-90% of the total computational time for enterprise search is taken up by permission checking
  • Enterprises don’t invest as much in search infrastructure as they should if the rapid delivery of search results was seen as critical

The second point is probably more important than people admit. In my experience significant computational resources are not allocated to Search by IT departments. I suspect that they look at average resource utilization, not peak performance and the time to deliver results to users. To deliver the typical half second or less response that Google considers to be essential, hundreds of servers may be involved. I am not aware of any Enterprise that allocates even the same order of magnitude of resources to content searching, so inevitably users experience dramatically slower response times.

In summary, the alignment of optimal user experiences with Google’s need to place advertisements has advanced the standards of user interfaces and provided many ‘free’ services, but the clash of Google’s corporate goals with the goals of other corporations has shown that the enterprise content has value that is not likely to be traded.

Syndicated at http://conversations.opentext.com/

The ‘Second Coming’ of Renditions – Video

Long time ECM veterans will remember the concept of document rendition – a transformed alternative. I think we’ll see renditions again.A rendition is essentially another form of a specific version of a document. There are two common types of renditions based on format and content:

  1. The same information content as the original document, but a different file format
  • For example, a spreadsheet file can be renditioned as a PDF
  1. The same file format as the original document, but different content
  • For example, a MS PowerPoint Document written in English can have a rendition that is also a PowerPoint file, but whose content has been translated into French

Renditions for limited bandwidth in the 90’sIn the 1990’s, one of the common use cases was to deal with the limited bandwidth available at the time. It often took a long time to download and open a document just to see if it contained what you were looking for. Accordingly, Open Text Livelink automatically made HTML renditions of many common formats such as MS Word that were much smaller files and so could be downloaded much faster for quick review.I remember presenting the use case to customers: “If you want to look quickly at a file without opening the full thing…” Back then bandwidth was so limited it made sense. Now it seldom does, although there are specific use-cases like renditions that contain added content like secured signatures that still have value.Bandwidth issues are backBandwidth is becoming limiting again – not for ‘simple’ text documents, but for rich media files such as videos. In fact bandwidth issues are so acute that the shape of the Internet has changed radically in the last few years. The explosive growth of video sharing has lead to the rise of Content Delivery or Distribution Networks (CDN) such as Akamai Technologies, Limelight Networks, CDNetworks and Amazon CloudFront to enable effective distribution.Akamai recently claimed they handle around 20% or the Internet traffic by volume – most of this traffic is rich media which must be delivered very quickly as users expect pages to load extremely quickly even if they contain a video. A recent Forrester report says the expected threshold to load has become two seconds.For video files to be useful to end users they have to start to play almost instantly. This is usually achieved by:

  • Locating a copy in close network proximity to the end user
    • CDNs use many distributed sites around the ‘edge of the Cloud’ to ensure that is at least one site close to an end user preloaded with files that are expected to be required
  • Reducing the size of the video through transcoding and compression
  • Streaming – starting to play before all of the content is received

The increasing use of mobile devices with narrow and unstable bandwidth connections, and different format requirements creates further hurdles to serving users rapidly.Enterprise needsSo what about the enterprise or corporate user? Trained by the web, he/she expects to click on a link and have a video start playing within two seconds. But most internal ECM systems (e.g. for document management) are designed to download a complete file before it is available to the end user.A story – Here’s a scenario I experienced recently. A Finance department prepared a new expense form. To show staff how to use it they prepared a five minute video. The trouble was that their WMV format video was over 300MB. For most staff in a global company, especially remote staff, downloading a 300MB file to view it is just not practical. What Finance needed was to be able to upload the video, and have the system take care of making a rendition that was transcoded and compressed, made stream-able and hosted on a CDN.There are just too many manual steps and too many options for most newcomers to video creation. Systems should take care of most of those steps. And one excellent way to execute several steps is to have the ECM system create a rendition of a deposited video that contains embed code to start a player and stream video from a CDN. The consumer users can then simply click on the object name in their ECM system and a streamed video starts to play almost instantly – as they have come to expect with sites such as YouTube.So renditions have a place in the new enterprise again to deal with bandwidth limitations!Syndicated at http://conversations.opentext.com/