From news article or internet information, find an example of an organization that is installing an ERP package. If possible get a copy of the over-all project plans and analyze the various activities and compare them with a standard SDLC.
Openbravo is an award-winning developer of professional open source solutions for businesses, offering the industry's first real alternative to proprietary enterprise software. The company's web-based Enterprise Resource Planning (ERP) and Point of Sale (PoS) solutions, the most popular in their market, have been downloaded more than 1.5 million times and are used in over 50 countries.
Openbravo ERP is a web-based business management system developed to help organizations streamline their daily operations and optimize back-office processes. The latest release, Openbravo ERP 2.50 Professional Subscription, introduced the concept of modularity, simplifying customization and the creation of third party add-ons. This makes it even easier for organizations to tailor their ERP system to their exact needs, while maintaining upgradability.
Openbravo ERP is now included in the Ubuntu partner repository, allowing Ubuntu users to add the software quickly and easily to their Ubuntu server. The newly created Openbravo ERP Professional Subscription for Ubuntu provides expert support and business continuity for the entire open source software stack, which includes the ERP software, operating system, application server and database.
What is ERP?
ERP (Enterprise Resource planning) covers the technique and concepts employed for the integrated management of business as a whole, from the viewpoint of the effectiveness use of management resources, to improve the efficiency of an enterprise. ERP packages are integrated software packages that support the above ERP concepts.
An Enterprise Resource Planning system (ERP) is a collection of modules/components integrated together while utilizing one database typically used primarily by medium to large manufacturing organizations with multiple sites located worldwide. Connecting to one database allows users from all departments of the organization located anywhere in the world to attain the necessary information to carry out their responsibilities. This integration approach offers improved operational processes and streamlined information to the fingertips of anyone with the security rights to access it. Paper documents are reduced or eliminated as online documents travel throughout the system to the appropriate department for updating and forwarding. Transactions pass through the system automatically updating several modules/components in real-time to provide timely and accurate data for users to access and share from any location in the world.
Phases of ERP Implementation Life Cycle
1. Pre-evaluation Screening
Once the company has decided to go for the ERP system, the search for the package must start as there are hundreds of packages it is always better to do a through and detailed evaluation of a small number of packages, than doing analysis of dozens of packages. This stage will be useful in eliminating those packages that are not suitable for the business process.
2. Package Evaluation
This stage is considered an important phases of the ERP implementation, as the package that one selects will decide the success or failure of the project. Implementation of an ERP involves huge investments and it is not easy to switch between different packages, so the right thing is ‘do it right the first time’. Once the packages to be evaluated are identified, the company needs to develop selection criteria that permit the evaluation of all the available packages on the same scale.
3. Project Planning
This is the phase that designs the implementation process. It is in this phase that the details of how to go about the implementation are decided. Time schedules deadlines, etc for the project are arrived at. The plan is developed, roles are identified and responsibilities are assigned. It will also decide when to begin the project, how to do it and it completion. A committee by the team leaders of each implementation group usually does such a planning.
4. Gap analysis
This is considered the most crucial phase for the success of ERP implementation. This is the process through which the companies create a complete model of where they are now, and in which direction will they opt in the future. It has been estimated that even the best packages will only meet 80% of the company’s requirements. The remaining 20% presents problematic issues for the company’s reengineering.
5. Reengineering
It is in this phase that human factors are taken into consideration. While every implementation is going to involve a significant change in number of employees and their job responsibilities, as the process becomes more automated and efficient, it is best to treat ERP as an investment as well as cost cutting measure.
6. Team training
Training is also an important phase in the implementation, which takes place along with the process of implementation. This is the phase where the company trains its employees to implement and later, run the system. Thus, it is vital for the company to choose the right employee who has the right attitude- people who are willing to change, learn new things and are not afraid of technology and a good functional knowledge.
7. Customization
This is the main functional area of ERP implementation. There is a bit of mystique around the customization process and for good reason: the Holy Grail of ERP implementation is synchronizing existing company practices with the package. In order to do so, business processes have to be understood and mapped in such a way that the arrived-at solutions match up with the overall goals of the company. But, companies cannot just shut down their operations while the mapping processes take place. Hence the prototype-a simulation of the actual business processes of the company-will be used. The prototype allows for through testing of the “to be” model in a controlled environment. As the ERP consultants configure and test the prototype, they attempt to solve any logistical problems inherent in the BPR before the actual go-live implementation.
8. Testing
This is the phase where one tries to break the system. One has reached a point where the company is testing the real case scenarios. The system is configured and now you must come up with extreme cases like system overloads, multiple users logging on at the same time, users entering invalid data, hackers trying to access restricted areas and so on. This phase is performed to find the weak link so that it can be rectified before its implementation.
9. Going Live
This is the phase where ERP is made available to the entire organization. On the technical side the work is almost complete: data conversion is done, databases are up and running and on the functional side, the prototype is fully configured and tested and ready to go operational. The system is officially proclaimed operational even though the implementation team must have been testing it and running it successfully for some time. But once the system is ‘live’ the old system is removed and the new system is used for doing business.
10. End-user Training
This is the phase where the actual users of the system will be given training on how to use the system. This phase starts much before the system goes live. The employees who are going to use the new system are identified. Their current skills are noted and they are divided into groups based on the current skill levels. Then each group is given training on the new system. This training is very important as the success of the ERP system is in the hands of the end-user. So, these training sessions should give the participants an overall view of the systems and how each person’s actions affect the entire system.
11. Post implementation
Once the implementation is over, the vendor and the hired consultants will go. To reap the fruit of the implementation it is very important that the system has wide acceptance. There should be enough employees who are trained to handle problems those crops up time to time. The system must be updated with the change in technology. The post implementation will need a different set of roles and skills than those with less integrated kind of systems. At a minimum, everyone who uses these systems needs to be trained on how they work, how they relate to business process and how a transaction ripples through the entire company whenever they press a key.
However, an organization can get the maximum value of these inputs if it successfully adopts and effectively uses the system.
-----------------------------------------------
System development life cycle. SDLC is the process of developing information systems through investigation, analysis, design, implementation and maintenance. SDLC is also known as information systems development or application development. SDLC is a systems approach to problem solving and is made up of several phases, each comprised of multiple steps:
• The software concept - identifies and defines a need for the new system
• A requirements analysis - analyzes the information needs of the end users
• The architectural design - creates a blueprint for the design with the necessary specifications for the hardware, software, people and data resources
• Coding and debugging - creates and programs the final system
• System testing - evaluates the system's actual functionality in relation to expected or intended functionality.
software development life cycle (SDLC) and also synonymous with software process as well as software engineering, it is a structured methodology used in the development of software products and packages. This methodology is used from the conception phase through to the delivery and end of life of a final software product. See under software engineering.
REFERENCE:
http://docs.google.com/viewer?a=v&q=cache:l5xlR5Ocv3sJ:www.ubuntu.com/system/files/Openbravo%2520Professional%2520Suscription%2520for%2520Ubuntu%25205%2520Aug%252009.pdf+organization+that+is+installing+an+ERP+package&hl=tl&gl=ph&pid=bl&srcid=ADGEESihjSMgxh6OsM6iF8qNeA820kBNhY7WNeJJGpdNavzHvTXQvMu7J9XL9cBVtNRrgTFpB8hZKXroM_VK7Y18iwVjhg9rdvQ6VtG8ZVGeZyy_8TimXEgc5wFY48m-kp2bfE7osbeF&sig=AHIEtbSHJvXdmj2SPENg7g9PfILdlaN0lg
http://www.docstoc.com/docs/5410205/ERP-Implementation
http://www.webopedia.com/TERM/S/SDLC.html
http://www.openbravo.com/about-us/
Openbravo is an award-winning developer of professional open source solutions for businesses, offering the industry's first real alternative to proprietary enterprise software. The company's web-based Enterprise Resource Planning (ERP) and Point of Sale (PoS) solutions, the most popular in their market, have been downloaded more than 1.5 million times and are used in over 50 countries.
Openbravo ERP is a web-based business management system developed to help organizations streamline their daily operations and optimize back-office processes. The latest release, Openbravo ERP 2.50 Professional Subscription, introduced the concept of modularity, simplifying customization and the creation of third party add-ons. This makes it even easier for organizations to tailor their ERP system to their exact needs, while maintaining upgradability.
Openbravo ERP is now included in the Ubuntu partner repository, allowing Ubuntu users to add the software quickly and easily to their Ubuntu server. The newly created Openbravo ERP Professional Subscription for Ubuntu provides expert support and business continuity for the entire open source software stack, which includes the ERP software, operating system, application server and database.
What is ERP?
ERP (Enterprise Resource planning) covers the technique and concepts employed for the integrated management of business as a whole, from the viewpoint of the effectiveness use of management resources, to improve the efficiency of an enterprise. ERP packages are integrated software packages that support the above ERP concepts.
An Enterprise Resource Planning system (ERP) is a collection of modules/components integrated together while utilizing one database typically used primarily by medium to large manufacturing organizations with multiple sites located worldwide. Connecting to one database allows users from all departments of the organization located anywhere in the world to attain the necessary information to carry out their responsibilities. This integration approach offers improved operational processes and streamlined information to the fingertips of anyone with the security rights to access it. Paper documents are reduced or eliminated as online documents travel throughout the system to the appropriate department for updating and forwarding. Transactions pass through the system automatically updating several modules/components in real-time to provide timely and accurate data for users to access and share from any location in the world.
Phases of ERP Implementation Life Cycle
1. Pre-evaluation Screening
Once the company has decided to go for the ERP system, the search for the package must start as there are hundreds of packages it is always better to do a through and detailed evaluation of a small number of packages, than doing analysis of dozens of packages. This stage will be useful in eliminating those packages that are not suitable for the business process.
2. Package Evaluation
This stage is considered an important phases of the ERP implementation, as the package that one selects will decide the success or failure of the project. Implementation of an ERP involves huge investments and it is not easy to switch between different packages, so the right thing is ‘do it right the first time’. Once the packages to be evaluated are identified, the company needs to develop selection criteria that permit the evaluation of all the available packages on the same scale.
3. Project Planning
This is the phase that designs the implementation process. It is in this phase that the details of how to go about the implementation are decided. Time schedules deadlines, etc for the project are arrived at. The plan is developed, roles are identified and responsibilities are assigned. It will also decide when to begin the project, how to do it and it completion. A committee by the team leaders of each implementation group usually does such a planning.
4. Gap analysis
This is considered the most crucial phase for the success of ERP implementation. This is the process through which the companies create a complete model of where they are now, and in which direction will they opt in the future. It has been estimated that even the best packages will only meet 80% of the company’s requirements. The remaining 20% presents problematic issues for the company’s reengineering.
5. Reengineering
It is in this phase that human factors are taken into consideration. While every implementation is going to involve a significant change in number of employees and their job responsibilities, as the process becomes more automated and efficient, it is best to treat ERP as an investment as well as cost cutting measure.
6. Team training
Training is also an important phase in the implementation, which takes place along with the process of implementation. This is the phase where the company trains its employees to implement and later, run the system. Thus, it is vital for the company to choose the right employee who has the right attitude- people who are willing to change, learn new things and are not afraid of technology and a good functional knowledge.
7. Customization
This is the main functional area of ERP implementation. There is a bit of mystique around the customization process and for good reason: the Holy Grail of ERP implementation is synchronizing existing company practices with the package. In order to do so, business processes have to be understood and mapped in such a way that the arrived-at solutions match up with the overall goals of the company. But, companies cannot just shut down their operations while the mapping processes take place. Hence the prototype-a simulation of the actual business processes of the company-will be used. The prototype allows for through testing of the “to be” model in a controlled environment. As the ERP consultants configure and test the prototype, they attempt to solve any logistical problems inherent in the BPR before the actual go-live implementation.
8. Testing
This is the phase where one tries to break the system. One has reached a point where the company is testing the real case scenarios. The system is configured and now you must come up with extreme cases like system overloads, multiple users logging on at the same time, users entering invalid data, hackers trying to access restricted areas and so on. This phase is performed to find the weak link so that it can be rectified before its implementation.
9. Going Live
This is the phase where ERP is made available to the entire organization. On the technical side the work is almost complete: data conversion is done, databases are up and running and on the functional side, the prototype is fully configured and tested and ready to go operational. The system is officially proclaimed operational even though the implementation team must have been testing it and running it successfully for some time. But once the system is ‘live’ the old system is removed and the new system is used for doing business.
10. End-user Training
This is the phase where the actual users of the system will be given training on how to use the system. This phase starts much before the system goes live. The employees who are going to use the new system are identified. Their current skills are noted and they are divided into groups based on the current skill levels. Then each group is given training on the new system. This training is very important as the success of the ERP system is in the hands of the end-user. So, these training sessions should give the participants an overall view of the systems and how each person’s actions affect the entire system.
11. Post implementation
Once the implementation is over, the vendor and the hired consultants will go. To reap the fruit of the implementation it is very important that the system has wide acceptance. There should be enough employees who are trained to handle problems those crops up time to time. The system must be updated with the change in technology. The post implementation will need a different set of roles and skills than those with less integrated kind of systems. At a minimum, everyone who uses these systems needs to be trained on how they work, how they relate to business process and how a transaction ripples through the entire company whenever they press a key.
However, an organization can get the maximum value of these inputs if it successfully adopts and effectively uses the system.
-----------------------------------------------
System development life cycle. SDLC is the process of developing information systems through investigation, analysis, design, implementation and maintenance. SDLC is also known as information systems development or application development. SDLC is a systems approach to problem solving and is made up of several phases, each comprised of multiple steps:
• The software concept - identifies and defines a need for the new system
• A requirements analysis - analyzes the information needs of the end users
• The architectural design - creates a blueprint for the design with the necessary specifications for the hardware, software, people and data resources
• Coding and debugging - creates and programs the final system
• System testing - evaluates the system's actual functionality in relation to expected or intended functionality.
software development life cycle (SDLC) and also synonymous with software process as well as software engineering, it is a structured methodology used in the development of software products and packages. This methodology is used from the conception phase through to the delivery and end of life of a final software product. See under software engineering.
REFERENCE:
http://docs.google.com/viewer?a=v&q=cache:l5xlR5Ocv3sJ:www.ubuntu.com/system/files/Openbravo%2520Professional%2520Suscription%2520for%2520Ubuntu%25205%2520Aug%252009.pdf+organization+that+is+installing+an+ERP+package&hl=tl&gl=ph&pid=bl&srcid=ADGEESihjSMgxh6OsM6iF8qNeA820kBNhY7WNeJJGpdNavzHvTXQvMu7J9XL9cBVtNRrgTFpB8hZKXroM_VK7Y18iwVjhg9rdvQ6VtG8ZVGeZyy_8TimXEgc5wFY48m-kp2bfE7osbeF&sig=AHIEtbSHJvXdmj2SPENg7g9PfILdlaN0lg
http://www.docstoc.com/docs/5410205/ERP-Implementation
http://www.webopedia.com/TERM/S/SDLC.html
http://www.openbravo.com/about-us/
No comments:
Post a Comment