Monday, February 15, 2010

Friday, February 12, 2010

Cloud Computing and Green IT

If you list latest buzz word in IT, certainly Green IT and Cloud will top this list. But does any body care about Green IT and SOA. I say no one. As a business person, I care only about my CapEx and OpEx. If on the way, I get some Browne Points for saving Earth, excellent.

So how to get Brownie Points and maximize the profit.

Cloud computing focuses on reduction of CapEX and converting the same into OpEx and Green IT focuses on CapEX as well as OpEx reduction.

Green IT focuses on reduction in Electricity Bills and using Bio Friendly materials and ways to reduce cost. Cloud computing give emphasis to sharing of resources to reduce CapEX. From this point of view Green IT and Cloud are tightly coupled.

Monday, February 8, 2010

BPMN Tutorial


Sunday, February 7, 2010

Off shoring Pricing Models

1.Time and Material: In this model outsourcing enterprise pays for the number of hours put in by Service provider. This model is very popular among Service provider because of its minimal risk. This pricing model is successful in the scenario where requirements are evolving and work involves lot of thinking.
2.Fixed Pricing: In this model Service Provider is paid a fixed amount for a fixed amount of work. In this model Service Provider assumes larger risk because of inaccurate estimation of work.
3. Outcome Based Pricing: In this pricing model relationship of outsourcer and service provider morphed into collaborative business entities where outcome of project decides fate not only of outsourcer but also of service provider. In this model service provider has highest level of engagement with outsourcer. In this model service provider assumes highest risk. This type of engagements are form of consulting where consulting starts much earlier and service providers understands outsourcers business in depth.

Friday, February 5, 2010

Book Review: Cloud Computing - Web Based Applications that Change the Way You Work and Collaborate Online by Michael Miller

Book Review: Cloud Computing - Web Based Applications that Change the Way You Work and Collaborate Online by Michael Miller: Publisher- Que Publishing: ISBN- 13: 978-0-7897-3803-5

I have very little to say for Cloud Cloud Computing - Web Based Applications that Change the Way You Work and Collaborate Online.

1. It is long list of web based applications
2. Incorrect projection of web based applications as Cloud based

Disclaimer: I did not get paid to review this book, and I do not stand to gain anything if you buy the book. I have no relationship with the publisher or the author.

Further reading: None

Thursday, February 4, 2010

Modelling Processes

The Process Modeling (PM) is the one of the primary requirement of any BPM project. The objective of PM is to record definition of as-is process. This recording results in analysis of existing process to understand strengths and weakness of the same. Any PM exercise needs to answer following questions:

1. What are the inputs (3Ms and One I – Man/Human Resources/Roles, Material/Document, Machine/Processing capability and Data/Information and Knowledge) to the Process?
2. What are the outcomes of the Process (tangible and non-tangible as well as direct and side effects)?
3. What are the different activities are performed in the course of execution of the Process?
4. What is the order of activities?
5. Who perform the activities?
6. What are the different events occur during the course of process execution?
7. What is the order of events?
8. What the pre-requisites of the Process to initiate?
9. What do/does trigger/s the Process?
10. What are incomplete-nesses or strengths of the Process?
11. Any historical information related to the Process.

The Process Modeling is carried out to achieve following objectives:

1. To specify the exact result of the process and to understand the value of this result.
2. To enable evolution of the Process.
3. To optimize the process (3Ms, One I and One T – Man/Human Resources, Material/Document, Machine/Processing capability, Data/Information and Knowledge and Time to execute)
4. To understand correlation among different processes.

Process Modeling results is variety of artifacts:

1. Process Map: This document – textually and/or graphically depicts various processes in enterprise and their interrelationship at very high level.
2. Roles and Relations Structure: This document - and/or graphically depicts various roles/groups and their relation in graph structure ( not organizational hierarchy) with respect to a Process.
3. As is Process Model: This model consists of following:
a. Process Environment Diagram: Detailed relationship of the Process with other interacting/intersecting processes.
b. Detailed Process Map: Detailed process map of each activity which getting executed in Process Execution all probable conditions.
c. Business rule: List of Business Rules and how they affect execution of process.
d. Exception Handling Diagram: Here detailing is carried out for error and exceptional cases for the process.
4. Publishing and Communication Process Modeling artifacts.

To carry out Process Modeling, simulation plays important role. Any simulation platform/tool/facility should exhibit following traits:

1. Simulate processes with respect to load distribution with time and non time factors
2. Simulate processes with respect to resource consumption ( 3Ms, One I and One T)
3. Statistical analysis of simulation result.
4. What if analysis.
5. Textual and graphical representation of simulation results
6. Publication of simulation results.

While carrying out Process Modeling following principles should be followed:

1. Stick to standards such as BPMN, ARIS methodology, etc.
2. Models must be semantically correct, means all activities, events and 3Ms, One I & One T are taken care of.
3. Beware of Paralysis by Analysis phenomenon.
4. Do Cost Benefit Analysis
5. Minimize technical jargon

While doing Process Modeling following challenges are common:

1. Absence of Process owner
2. Persons aware about process details are not cooperative enough
3. Modeler's point of view gets incorporated in Process Model.
4. Usage of jargon ( Business as well as IT specific)
5. As is Model start depicting To Be.