Friday, May 29, 2009

Sharepoint Posting

I have been working on Sharepoint for some time now and i am thinking i should use my blog to document some of the Sharepoint information i have found useful.

So starting today, i will start blogging regarding this..Hopefully i will be consistent with it...

Thursday, November 09, 2006

Star Date .... November 2 - Change Management

Its a known fact, and human nature to resist any changes that are made to the existing norms. People dont prefer changes, unless they are made to understand the importance of the change and how the change would help them to be more effective and efficient. This is what Change Management [ CM ] tries to do and thats what was discussed in todays class.

CM is nothing but a process of facilitating change. Any new implemenatation like a ERP implementation brings about a number of changes in the way the organization and the process works. Based on research , it is shown that one of the topmost obstacle for failure in ERP implementation is Resisitance to change, about 60%. This is mainly because of the stress and fear syndrome created by any change, wherein people fear that they would loose their jobs.

Some of the main reasons companies change is due to the fact that change would help them grow, reach thier vision, increase productivity, and improve overall. However, a lot of employees resist this change because of the fear of layoffs, loss of comfort, lack of information about the change and "fear of unknown". The best way to overcome this resistance is to provide more information, eduacate people about this importance and the necessity for the change and empower them by sharing information, listeninfg to employees.

There are three phases in Change management
1. Preparing for change [ Unfreeze the situation ] : this is nothing but creating a foundation for change, creating CM strategy guidelines, create a CM team ....
2.. Managing Change [ Change ] : This basically involves creating a project plan for implementing CM activities, creating a sponsor roadmap, coaching and communication plan...
3. Reinforcing Change [ Freeze ] : Basically this is to commit to all the changes by assesing all the CM activities, identifying and overcoming obstacles...

CHANGE IS REQUIRED>>> IT IS CONSTANT, NECESSARY and UNPREDICTABLE ... but running away from it will not improve the situation...

Wednesday, November 08, 2006

Star Date .... October 26 - ERP Implementation

The fifth component of the ERP Life cycle is the Transition phase, which mainly deals with the implementation of ERP.

For a successful implementation of ERP, the major back bones are PEOPLE,PROCESS, TECHNOLOGY. All the three need to be aligned for a successful implementation. The component People involves upper management, employees, consultants and the project team. All these people need to work in sync for a successful implementation... The process component, basically entials that all the processes should be well defined, easy to understand and the ERP implemetation should be aligned with these BP .The TECHNOLOGY component entails understanding clearly the technology plan which includes Database, Internet and OS.

The four ways of implementing ERP
1. Incremental : Narrow Scope , less Functions
2. Process Phasing : Broad Scope, Less Functions
3. Geographical/Business Unit Phasing : Narrow Scope , More Functions
4. Big Bang : Broad Scope, More Functions

In the incremental approach, one Module at one Business Unit is implemented at a time. It is very time consuming as it requires detailed understanding of every process.

The Phase approach is applicable when limited resouces are available for implementation, and it also has reduced risk as it is implemented in phases and gives the possibility to fall back on the legacy system, if implementation fails.

The Big bang Approch, is implemeting the ERP suite across the board as quickly as possible. This leads to Lower Cost and does not require interfacing with the legacy system, as phased approach does. However there is a lot of risk involved in this method as there are cases of companies getting liquidated due to this approach. It also requires the upper management support for successful implementation and a lot of resources.

Inspite of all this there is a 60% -80% chance of failure and therefore it is important to keep track of all warning signs and ensure they are controlled and corrected immediately.


The final stage is STABILIZATION, which involves correcting the implemented procedures once ERP goes Live...Most of the issues are related to people and process rather than on technology. One way to overcome this is continious training in order to help the employees to get used to the new system.

Thursday, November 02, 2006

Star Date .... October 12 - ERP Project Evaluation

Any Implementation finally boils down to the question, is the implementation live up to its standards and did it achieve its goals... Basicall the question that is asked is what is the Return on the investment.

ROI is nothing but the ratio of the project’s benefit to the value of project’s cost. However the problem with calculating ROI is that we cannot account for the intangible benefits and costs. For
So the alternative method choosen by some companies to see the value of the implemention is the Net Present Value (NPV), and Internal Rate of Return (IRR).

It is difficult to calculate the returns from an ERP implementation because the company perceives of profit in different way. However some of the beneifits of switching to an ERP system is the savings the company enjoys in operations, the improvements in the management of inventory, the real time data availability, better customer visibility .
The other intangible benefits enjoyed are improvement in the processes, efficient and effective work environment, reduced cycle time, increased accurancy etc.

As per Peerstone Survey 63% companies achieved some form of benefit. 39% of these companies achieved ROI. Successful implementation have shown to have their ROI target before launch of the ERP project. Companies that use ROI have shown more success than others..

Star Date .... October 5 - ERP Life Cycle

An ERP life cycle has six steps:
Initiation: Basically in this step, the business case is forumalted which will help in identifying the costs, the need, the justification for the ERP system. Basically there are four rationales used for creating a business case , they are Technology, Business process, Strategy, Competition.

Planning: Consists of formulating the team, its goals, and objectives. It also involves determining the staffing requirements and establishing metrics for the implementation project. The team should consist of techincal people, business process owners, consultants to make is a successful team.

Analysis and Design : Analysis is done on the basis of “As Is”, “To Be” and “Gap” methods. The AS IS tries to identify the current funcationalites of the sytem and the TO BE tries to identify where the company needs to be. GAP Method identities the gap between where the business is right now and where it wants to be. this would help in taking the right steps to close the gap. “To Be” model is Technology/ERP Driven.


Realization—The realization phase entails acquiring resources, installing a base system, customizing it to the organization, extending it if necessary, and testing the implementation.

Transition—This is usually a relatively short phase during which the organization’s former information systems are replaced with the enterprise system.

Operation—The operation phase involves ongoing efforts to monitor system performance and tune the system as appropriate. It also involves the continuing process of training employees on the enterprise system


There are various tools available for project management.
1) Critical Path method: it provides a framework for planning and control and at the same time makes assumption about the time estimated and predecessor relationships.

2) Gantt chart: Bar chart used to show project schedule. It identifies the time constraints of the project very neatly.

Star Date .... October 5 - Enterprise System Infrastructure

For any information system to work properly, the infrastructure needed to make into a system is very important... Infrastructure is nothing but the the phyiscal components that are required to make up the system. Once the infrastructure is decided upon, the architecture needs to be decided upon, whether it would be a open[interact with systems of other systems] or a closed system [ act as a standalone or have difficultites in connecting to other systems] . However an important thing to remember is an OPEN SOURCE is not the same as OPEN SYSTEM.

The main reasons for creating a ES infrastructure is to integrate all the exisiting process and for streamlining them. It also reduces cycle time and manage inventory better. Basically it will help in improving the efficiency of the overall business.

Some of the important characteristic of ES system is its modular construction. the system can be installed in modules. this provides the flexibility to the business to install only those modules which the business requires. Further it provides a central DB, wherin all information is available at one single location. Further the ES system , gives the flexibility to configure the system or customize it as required by the company. SAP offers more than 8000 confguration tables [ Source: Dr Vijay notes]... It also follows a three-tier Client-Server architecture where all the processing is done on the server side and the input/output is done on the client side. The clients have come a long way from being just dead terminals to smart terminals. They have certain powers to process the data themselves. It also provides variable interface, wherein different interfaces can be configured as per different requirements.

The important technologies required for a ES system implementation is Hardware, OPerationg System, the required middleware/Bolt Ons , the required network infrastructure and if need be the web services to integrate the interent capability.

Thursday, September 28, 2006

Star Date .... 21 Sept - Business Process Modelling

"A picture is equal to 1000 words " and thats what BP modelling tries to achieve... It gives a pictorial representation of each of the business process, which in turn helps in getting a better understanding of the process. It helps in defining the requirements to perform a process and at the same time helps to communicate and understand the business rules and processes better.

There are different types of modelling tools such as Flowchart, Cause-Effect Diagram, Dataflow diagram, EPC diagram and Work Flow Diagram. Each one of these models has its own way of graphically depicting a Process... The Complexity of the diagrams also increases based on the type of tool we are using...

Process Improvement was the other topic we covered .. Process Improvement is basically a cumulative process of improving a process. In this method a process is developed over a period time. For process improvement we need to consider the cost and time factors tooo... at the same time we need to also analyse the value that is added at each increment... Value can be of three types, Real , Business Value or NO Value... An Activity which has no Value needs to be eliminated immediately...

So the important thing to consider here is ... If the graphical representation itself is too complex... then is it still worthwhile to Model a Process,,,???

Tuesday, September 19, 2006

Star Date....Sept 14 - Business Process ReEngineering

Business Process ReEngineering [BPR] ... What is this ..?? This is one of the revolutionary procedures implemented by certain organizations to reengineer thier Business Processes to improve the performance of the various Business Process... It makes use of technology to bring about these quantum leaps in performance.

BPR mainly focuses on WHY a particular process is carried out rather than HOW it is done... Bcoz it looks into the reason behind carrying out the process, it helps the organization to better under the process and reengineer it... During Reengineering the entire focus is around the obkective or the outcome desired and not on one of the tasks that will help in getting the desired outcome.. The entire reengineering depends on capturing the data at a centralized location so as to reduce the redudancy of data... At the same time to redesign the process its important that the employees are empowered and all the parellel acitivites are integrated.

The main people who should be involved in the BPR process as per the article "Business Process Reengineering" is the internal auditors. They not only advice management and system analyse on reengineering processes but also create new audit plans once the reengineered process is in place....

The various examples of successful implemetation are FORD, Mutual Benefit Life etc, which were able to redesign their BP's to better the perfomance.


BPR basically helps reducing the defects leading to better quality products which leads to cost and time savings. However on the downside... the failure rate is about 50%-70% which is quite high. The reason for this high failure rate is the lack of oversight, Leadership commitment, employee resistance, appropriate staffing etc...

Reengineering can be implemented either using a particular technology or by redesigning the entire process from scratch . Both have thier pros and cons, and the decesion is for the top management to take...

Noadays BPM, Business Process Management is the lastest Buzzword where it tries to bring people, technology and processes together, this includes integrating the BP of the company with the those of the suppliers and partners...

So which one should a company use...??? And how do we decide ..???

Wednesday, September 13, 2006

Star Date ...Sep 7 - Business Process

What is Business Process Reengineering[BPR]...? With so many TLA* floating around, its very difficult to keep up with it... However before we understand this we need understand what a business process is... During this session Dr Vijay shed light on the topic... In all the traditional organization , each unit was considered to be a discrete unit with its own functional boundaries, however such a traditional thought does not work well noadays. As customers become more demanding and unpredictable in their needs, its very important that more importance is given to the each process of the business in the development procedures. Each process should involve the inputs of representatives from each of the functional departments. Apart from that each business process should have a clearly defined inputs and outputs and should be carried out with a goal in mind...

Integrating each of the functional departments of the organization, leads to more efficient and effective flow of data among them leading to more efficient busniess process which indirectly adds more "value" to the organization. The best example to support this is the Texas Instruments organization, which changed from a traditonal system to a business process system which helped it to churn out better products quicker and more efficiently... Other examples include Duke Power and IBM who went through the same...

Some examples of Business Process include Bill Recievable or Bills Payable process in an organization...

Further every business process should be assigned a business owner who helps in integrating all the functional divisions of the organization and he is totally responsible for that business process.. Based on the article Business Process Reengineering by Marshall Romney..." changing a business process leads to a improvement of 48 percent in cost, 80 percent in time and 60 percent in defects...."


Inspite of these advantages why do some companies still follow traditional methods and more interesting question is Can "Family- Based " organizations adopt this method and become more successful... ??? Any comments Any one..??