Categories

Improvement of Business Information System Part2

If you are following this post series, you know that we are trying to show a tried path for “improvement of Business information system”.

In this post I will try to explain the steps we should take to manage an improvement project.

First of all I’ll give you some hints to increase your success rate in improvement projects and will keep you away from fumbling:

  1. The First rule for an information system architect is to always keep your Up-Down Glance.
    In the other word at every situation, project, task, activity you are in; always ask yourself:
  • “Why should I do this?”
  • “Why should I choose this method of improvement?”
  • “What are the results of this method of improvement?”
  • Even “is my defined problem really exists?”
  1. Following the previous rule, Most of system engineers think the problem is “what they see” or “What Others Say”, and make horrible mistakes by choosing wrong methods at wrong time…
  2. Commitment of the top level management is another driving force for every change process. Try to get reliance of management so you will need to provide enough documents to proof your Methods and plans.
  3. Before Starting any improvement project please read all planning documents to ensure you are in the right way.

Totally the improvement project contains four phases:

Ok, now I’m going to describe how to model “as is” situation in a simple way.

In a view, modeling an organization contains these four parts:


1-Strategic Planning:

As I mentioned before having an upstream document about company’s plans is vital to keep you on the right path.

This is vital to step along the rout of organization’s main plan.

Even if your organization does not have such this script, try to write one.

In these post series I will describe how to prepare a strategic plan for your organization.

2-Organization Modeling

The most common trap that system engineers fall in is: “They don’t model Organization’s “AS IS” situation”

When we are talking about modeling organization, we don’t mean to map processes, but Organization.

In other word we have to ask simple questions about current jobs, tasks, duties and any action we are doing in the organization in this simple way:

  1. “What” actions are we doing in the organization”?
  2. “Why” are we doing this action, in the organization?
  3. “Who” does this action in the organization?
  4. “How” they do this action in the organization?
  5. “When” we do this action in the organization?
  6. “Where” are we doing this action?

Answering these simple questions about any action you observe in the organization may help you to model organization in much accurate way.

Modeling the organization in above pattern can be done by “Zachman Enterprise Architecture Framework” or any other organization architecture framework.

For more information about zachman architecture please refer to zachman international website.

In near future I will share my experiences about modeling whole organization by this method in these post series.

3-Process Modeling

These days many of process engineers use BPMN method as only tool for process mapping; unfortunately this method does not cover all needs in process mapping.

In my opinion process mapping documents at least includes:

  1. Process Flow Diagram
  2. Process Actors
  3. Related Forms
  4. Expected Results of Process
  5. Process issues
  6. Process Performance indicator measures
  7. Process Assessments
  8. Process Goals

After modeling processes in this template, you’ll realize many problems exist in organization.

4-ICT Modeling

When we talk about ICT, first thing comes to our mind is network, cable, communication, etc. but this limited look prevents modeling all ICT potentials.

I believe “information system” and “information technology” both form ICT platform.

Regarding this point documenting all IT properties (including tangible and intangible assets) is important in this part.

You may want to document all properties including:

  1. Network infrastructure
  2. Server computers
  3. Client computers
  4. Owned softwares
  5. Annually Rented softwares / licenses
  6. Website memberships
  7. Intranet / Internet connections
  8. Any other ICT properties.

After documenting this section you will be able to better recognize organization’s potential to improve information system.

Ok, I wish I’ve had successfully expressed what I was meant to…

Please follow my posts and give me feedback to improve this weblog.

Good luck

Hamed

Improvement of Business Information System Part1

Caution

All Content of This Post Series is Personal Experiences of Hamed Ghodrat as an executive and consultant in order to launch “information system improvement” projects in organizations.

Results of using methods introduced in these post series may vary depending on your organization’s structure.

Beware that no responsibility is faced to author according to miss imply of these methods.

 

Let’s suppose that you are trying to regularize your organization’s Business information System to gain the most profit from business activities.

Depending on your management manner you may chose any method of improvement to improve your business information system:

  • If you are a Process Engineering fan you may start optimization with BPR (Business Process Reengineering) or may be start with BPM (Business Process Management).
  • If you prefer to model your organization with a UP-Down Look , you may choose Enterprise architecture methods like Zachman ,pinnacle or …
  • If you are a technology fan you may start by comparing your business structure to software platforms and choose any software from the ocean of business management Softwares.
  • And many other improvement methods

Now a question is asked that which method is best suited for your purpose.

Many information analysts think that applying methods based on knowledge that mostly learned from classic books or may be gained from valued articles will solve all of business problems, but this is a very dangerous trap which mostly cause destruction of “information system improvement” projects and The loss of improvement begins with this choose.

In improvement projects this theory is vital that we apply an Up-Down Glance to define the perfection path.

Let’s start with a simple example:

Imagine you own an organization with these specifications:

  • Mission: Providing customer services
  • Main Activity: Sales and after sales services
  • Human resource: more than 100 employees
  • More than 10 million $ of investment
  • More than 20000 customers
  • Traditional , non efficient and complicated processes
  • Internal and environmental pressures (Competitive market, new Customer demands,… )

As an executive you have to decide to improve organization’s turnover or you abandon the market share!

In such this situation you realize the importance of the approach you choose to agile your organization.

When we talk about business firms, it means we have investors that expect interest; various spectrums of customers with different prospects, personnel with different culture and abilities and many other specifications. This will increase responsibility of the system analyst to choose the correct methods of improvement.

In these series of posts I will try to show you the tried way to success!

Will be back soon to continue sharing my experiences about the title…

Another Start

Hello World!

After Changing Server Platforms again and again , i decided to start a new weblog by powerful WordPress !

i Wish i’ll be able to share my experiences and knowledge about ICT Engineering and management.

Cheers!

Hamed.