Archive for the ‘Information Management’ Category

Architecting for the E-Record: ARMA Spring Workshop

Wednesday, June 23rd, 2010

Systemscope’s Linda Daniels-Lewis and Lindsay Fraser, along with Alexandra Freeland of the Canadian Nuclear Safety Commission, presented a workshop at the ARMA NCR Spring Workshop Session in Ottawa. The workshop presentation gave a synopsis of  CNSC’s E-Records Framework Project, begun in 2008, and their considerable head-way to date. Alexandra Freeland, CNSC’s Deputy CIO/Director Planning and Coordination (Information Management Division) explained CNSC’s original thinking regarding the project, project drivers, the approach undertaken and the various components of the overall project as well as specific information architecture pieces of the project.

Systemscope’s Lindsay Fraser (IM Practice Lead) and Linda Daniels-Lewis, Senior Information Architect on the project, also shared with participants the methodology and the various tools that were created for the project, in addition to a detailed discussion of the thinking that went into the planning and execution of the project.  Key points covered included:

  • Understanding and identifying e-records in all their various formats
  • Establishing the requirements for managing an electronic record
  • Examining the need for signatures and what constitutes an electronic signature
  • Identifying which systems can and should be regarded as Systems of Record deserving of RM rigor.
  • The key information architecture components required to manage records across multiple systems.
  • Developing and using a “Business Information Relationship Model” to help identify those IA components.

Download the presentations: CNSC’s description of the E-Records Framework Project and Systemscope’s accompanying presentation on Architecting for the E-Record

Google – Better on the Outside than on the Inside?

Tuesday, February 23rd, 2010

By Lindsay Fraser

My all time favourite Far Side cartoon features two polar bears looming over an igloo.  One says to the other: “I just love these things – cool and crunchy on the outside, warm and chewy on the inside”.

This cartoon comes to mind whenever I am talking to colleagues about the use of Google on Canadian government intranets. I can’t help but think that Google is better on the “outside” than it is on the “inside”.  Now, don’t get me wrong, I am not a Google-basher. I love Google. I love Google today the way that I loved and adored Yahoo back in 1994, when I couldn’t imagine anything better.

Google is a tremendous resource, second only to GEDS in my personal favourites list. It is such a marvelous Internet search engine that it leads decision makers to think “anything that good must be a great solution for our intranet too – right?”

NO, No, an emphatic no.  And I hate to say it – I really do.

I am the first to agree that any search is better than no search – absolutely.

But the black-box that is Google does not typically help workers inside the organization find the materials on the intranet that are best suited to their working requirements.

Granted, we don’t understand all that well how the Google algorithms work (a closely guarded secret as you might well appreciate); but we do understand that Google focuses on concepts such as word counts, proximity of words to other words, location of words in web pages (titles, top of page) etc. This focus allows Google to do a great job of bringing to its users potentially relevant returns from a massive and totally random world wide web.

But on the inside, where the information collection is much smaller, far less random and actually has some structure and logic to it, Google’s effectiveness is greatly reduced. Employees want access to particular types of information (leave forms, for example), and don’t want a results set that contains every instance of the word “leave”.

Employees also want easy access into the top level of various information resources (the key entry and summary documents) so they can understand the context of the information returned to them and then choose the depth to which they will perform their reading and analysis.

Owing to significant challenges at the time, Google designed its algorithms to foil search engine spammers and other unreliable publishers who were misrepresenting the nature of their information content in order to have it come up in as many relevant results lists as possible. Google couldn’t trust that the information that publishers provided in association with their Web resources (metadata) was truly reliable and therefore built algorithms that placed little credence in such data.

Internally though, organizations understand their information holdings and understand who the users of said holdings are. Organizations also have information architects, publishers and editors, who can assign reliable metadata such as objective indications of page importance, page “type” in a hierarchy and resource type (e.g. form, policy etc.). It is this trusted metadata that allows search engines to return truly relevant search results to organizational users – and sadly, metadata is not something that Google has been developed to exploit.

For internal intranet search purposes, organizations should look to search tools and appliances that will also allow for the rich exploitation of trusted publisher input. If Google is the only option, then organizations should look to acquire the most flexible of the Google offerings and to take full advantage of the “weighting” options that are available. Google is undeniably great – but perhaps better on the outside than on the inside.

Lindsay Fraser is the Principal and Practice Lead for Systemscope’s Information Management practice.She can be reached at fraser@systemscope.com.

IM and Business Process Mapping: A Tale of Two Consultants

Tuesday, January 19th, 2010

By Kellen Greenberg and Linda Lee

As consultants working for government clients, we have recently noticed that “business process mapping” has become a loud whisper among the IM community. It has been said with interest, as well as with some trepidation. Regardless, IM specialists are starting to feel the need to understand this tool better and understand how it can be used within the IM context.

One of the reasons business process mapping is sparking a lot of interest is due to the new Directive on Recordkeeping that was released in July 2009. Government organizations are being asked to identify and focus on managing information resources of business value. One of the suggested methods for identifying information resources of business value is through business process mapping.

View of a Management Consultant

I’m continually surprised at the new challenges that can be overcome using process mapping tools and techniques. When we first sat down and looked at the new Directive on Recordkeeping, it became apparent that the core challenge was not just identifying which records are of “business value”, but doing so with accuracy and efficiency – going through records one-by-one is not practical and applying batch values can often miss the mark.

As we talked through the challenges, process mapping started to show promise as the tool that could find the balance between “getting it right” and “cost effective”. Process mapping lets us focus on how documents are used, rather than what the document is. First, we identify the processes that are of value to your business, and associate with those, the records that are of value to the process.

The solution: Records, meet process.

Let’s take a transactional process as an example. The specifics of a transactional process will vary from one business line to the next. The specific steps may be different and the records used and produced throughout these steps will be different. However, at a higher level of detail, there are similarities that hold true across nearly all transactional processes. They all typically involve four basic steps: Receive request, process request, produce response, and follow-up. Further, the documents produced and used along these steps will have significant similarities in value.

By defining these generic processes for your organization, and defining generic records of business value within them, you can begin rolling-out the model across the whole organization.  Doing this will provide you with a sound first cut at defining the records of business value across the whole organization, and do so far more efficiently than other methods.

What this gets you:

  • Identification of records of business value at a generic level across the whole organization
  • Common approach for defining process types and records

What to do next:

  • Link specific documents from business lines to the generic ones identified
  • Continue to manage the definition of ‘business value’ at a process level

View of an Information Management Consultant

Although the Directive on Recordkeeping may have ignited the interest in business process mapping, I have found that this tool can be very useful for both the IM specialist and the IM group in an organization.  This is true more than ever as the role of IM specialists is changing in this evolving GC IM environment. More and more, we are being asked to be business analysts.

Business process mapping can be a powerful communication tool. Communication is a large part of IM in an organization – communication of IM responsibilities and properly managing information. Process maps can very simply and effectively show the links between the business processes and IM requirements. For instance, process maps can clearly show business managers when and where to store the information resources created and collected in their business processes.

The exercise of identifying information resources of business value, although potentially a large investment, can be worthwhile in the long run.

Kellen Greenberg is a consultant with Systemscope’s Strategic Business Consulting practice. He can be reached at greenberg@systemscope.com.
Linda Lee is a consultant with Systemscope’s Information Management practice. She can be reached at lee@systemscope.com.

MANAGING INFORMATION IN THE PUBLIC SECTOR
April 26-27, 2010
- Architecting for the E-Record, presented by Linda Daniels-Lewis. Read More

Procurement - Talk to us about
TBIPS and SBIPS! Read More