(a): in terms of technology and application: At present, ERP in the design of technical applications to take the main two structures: C / S structure and B / S structure.
C/S is also known as Client/Server or client/server model. The server usually uses high-performance PC, workstation or small machine, and the use of large database systems, such as Oracle, Sybase, Informix or SQLServer. client needs to install special client software.
B/S is the abbreviation of Brower/Server, the client only needs to install a browser (Browser), such as NetscapeNavigator or InternetExplorer, the server installs Oracle, Sybase, Informix or SQLServer database. Browser through the WebServer with the database for data interaction.
The advantage of C/S is that it can fully utilize the processing power of the client PC, and a lot of work can be processed on the client side and then submitted to the server. The corresponding advantage is that the client responds quickly.
The disadvantages are mainly the following:
Only applicable to LAN. With the rapid development of the Internet, mobile office and distributed office is becoming more and more popular, which requires our system has scalability. This way of remote access requires specialized technology, as well as a special design of the system to deal with distributed data.
The client needs to install specialized client software. First of all, it involves the workload of installation, and secondly, any computer problems, such as viruses, hardware damage, will need to be installed or maintained. Especially if there are many branches or specialty stores, it's not a matter of workload, but of distance traveled. What's more, when the system software is upgraded, each client machine needs to be reinstalled, and its maintenance and upgrade costs are very high.
There are also limitations on the client's operating system in general. It may be adapted to Win98, but not to Win2000 or WindowsXP, or to Microsoft's new operating systems, not to mention Linux, Unix, and so on.
The biggest advantage of B/S is that it can be operated anywhere without installing any specialized software. As long as there is a computer with Internet access can be used, the client zero maintenance. The expansion of the system is very easy, as long as you have access to the Internet, and then by the system administrator to assign a user name and password, you can use it. It can even be applied online. After passing the company's internal security authentication (such as CA certificate), the system can automatically assign an account to the user to enter the system without human involvement.
The advantages of the B/S structure used in ERP are very obvious. Of course, in terms of operating speed, human-computer interaction, etc., the B/S structure has certain shortcomings. How to B / S structure and C / S structure for effective technical integration will become the future application of technology is a top priority. (ii): RP implementation of ERP systems is a technically complex, large investment, on the management organization, internal mechanisms, corporate culture, decision-making, management thinking, etc. will have a profound impact on the systematic project, which will change people's ways and means of work, a direct impact on the enterprise's internal workflow, logistics, capital flow, the impact of the enterprise on the controllability of these processes, the transparency of business operations and business operations of the enterprise's information The role of the enterprise to change the job setup and job management system. Successful implementation of the ERP system must follow the idea of systems engineering, and the implementation of the ERP system as a process of growth along with the enterprise, the ERP system management ideas and the traditional concept of the enterprise grinding process, the two *** with the same strive to continuously adapt to the new environment, policy, market, capacity, resources and other dynamic changes in the impact of factors. ERP principles, management information systems and enterprise information technology based on the theory of simple, effective, practical technology to solve dynamic, variable, complex ERP system implementation of the various problems encountered. Make ERP system implementation low cost, fast results, easy to grasp, understand and promote the application.
ERP system implementation methods
Domestic and foreign ERP system software development and suppliers of ERP system implementation of more in-depth research, the formation of their own implementation methods, with more obvious characteristics.
1.1SAP implementation methods and processes - ASAP
SAP was founded in 1972, headquartered in Waldorf, Germany, is the world's largest enterprise management and collaborative business solutions provider, the world's third-largest independent software vendors. In the SAPR / 3 consulting and implementation process, the majority of SAP implementation consultants usually use linear ASAP () methodology, ASAP is the SAP company to make R / 3 project implementation easier and more effective set of complete rapid implementation methodology. ASAP optimized in the implementation process of time, quality and effective use of resources, such as the control. ASAP advocates the implementation of SAP based on past ASAP advocates accelerated implementation of current SAP systems based on past SAP implementation experience and the desire to further improve the performance of the current system, ASAP provides a process-oriented, clear and concise project plan. Provides step-by-step guidance in the implementation of R/3. The ASAP Rapid Implementation Methodology*** has 5 steps: Project Preparation, Business Blueprint, Realization Process, Final Preparation, and Startup Technical Support, which must be strictly sequential in the ERP implementation process. For each stage of implementation, SAP defines the purpose, specific tasks to be accomplished, methods, tools, and standards to be used.
1. Project Preparation ()
The most important work of this process is the project plan, the key to the project plan is to determine the scope of the project, to be based on the needs and capabilities of the development of a reasonable plan. The main tasks are: establish the project organization, establish the project schedule, project team training, network environment and hardware preparation, project initiation.
2. business blueprint ()
This stage is to analyze the needs of the enterprise, design an ideal management blueprint, and then based on the current needs and future ideal design of a specific goal, as well as to achieve the goal of the tools, methods, organizational structure, data conversion methods, etc., this stage is the key to the entire ERP project. The main tasks are: analysis of the current state of business processes (organizational structure, processes), the future business to determine (organizational structure, processes), to establish project documentation standards, SAP system installation, management approval of the business blueprint.
3. Realization process (Realization)
The enterprise wants to achieve the management ideas, management concepts, management guidelines, assessment standards, organizational configuration into the system, usually after the completion of this part of the work, the basic model of the ERP came out. The main tasks are: the basic configuration of the system, the project team's advanced training, process testing, design interfaces and reports, system testing to determine and improve the external interface and report development program, the establishment of user rights and system management mechanisms, and prepare for end-user training.
4. Final preparation ()
Put some of the necessary data into the system to test the results of the system operation (i.e., system testing), this part of the work is completed, the system can be on-line operation and start technical support. The main tasks are: determine the configuration system, end-user training, basic data preparation, preparation of initial data, on-line program design.
5. Go-live and technical support ()
System go-live; uninterrupted support; continuous business process optimization, project evaluation and review.
It is worth emphasizing that a completed project implementation must have high-quality documentation, but traditional implementations can sometimes result in increased costs due to excessive documentation. the guiding principle of ASAP is to assign importance to documents according to their lifecycle length, and accordingly invest more effort in documents with long lifecycles. ASAP is not a simple methodology, it is an ASAP is not a simple methodology, it is an architecture supported by a series of methodologies, tools, implementation roadmaps, solution libraries, system configuration guides, in addition to development models based on management concepts, role-based training, etc., all of which make up the ASAP system.
1. 2Oracle Implementation Methodology - PJM/AIM
It is a set of methods to build a holistic solution, mainly composed of AIM (Application Implementation Methodology) and PJM (Overall Project Management Methodology) and other independent methodologies. These methodologies can improve the efficiency and quality of project implementation. The consultant will use the implementation methodology and implementation tools to help in the project implementation process, and will use this methodology technology as part of the technology transfer.
PJM - Project Management Methodology: The goal of the Project Management Methodology (PJM) is to provide a master framework for planning, evaluating, controlling, and tracking all projects with consistent means.AIM - Application System Implementation Methodology: AIM is divided into the following seven phases:
l. Establishing an Implementation Strategy
This phase focuses on planning the scope of the project in terms of both business and technical aspects and defining the objectives of the project. This stage of the work, including the establishment of the company's main leaders headed by the project implementation of the leadership group and the departments concerned to participate in the project implementation team, and began to staff the initial business management concepts and methods of training. Specifically formulate the strategy and objectives for the implementation of application management in the enterprise.
2. Business process analysis
This stage is mainly to define the content of the project, that is, the current management of a careful review and description, so as to recognize the project's business and technical specific requirements. Generally a project definition analysis report is prepared in this sub-phase, which can be more in the form of an IPO diagram to describe the current process and identify the desired improvements from it. Conditions are created for the design of further solutions. For this purpose, members of the project implementation team need to be more systematic training on the concepts of business management and the functional levels of the Oracle system software.
3. Design solutions
This stage is mainly the formation of the previous stage of the business analysis process, combined with the basic concepts of business management and specific software functionality, item by item to review, analyze, in order to each of the current management of business processes, proposed solutions. The solution may be directly applicable to some of the functions of Oracle applications, perhaps some improvements to the current management process, may also be the management software system to do some of the necessary secondary development. At this time, generally should be written as a project description of such documents, as a milestone as well as the establishment of the system's design mission statement.
4. Establishment of the application system
This stage needs to be formulated in accordance with the previous stage of the program, the management (or organizational) need to improve the development of improvement programs, including adjusting the division of labor, standardize the process, a unified methodology, standard information coding and so on. In terms of software, system initialization design and secondary development work can begin. This establishes an application system in line with enterprise management ideas. At this time a large number of basic data will also begin to organize the work.
5. Document coding
In the establishment of the application system at the same time, in addition to the software must be secondary development, according to the software engineering requirements to provide the necessary documentation, the management of the process to improve the methodology, etc., but also must be written or modify the original system, responsibilities, flow charts. At this point, once the system has been established, you can start the main application of end-user training.
6. System switching
In order to reduce the risk of system implementation, each functional department in accordance with their daily business activities, with reference to the documented process, running a computer system for testing to confirm that their systems are basically feasible. Only then do they begin to formally enter data into the new system, create initial states, define parameters, and begin operations. In order to ensure the success of the switchover, the project leadership team is required to issue a number of instructions in a timely manner to gradually carry out the system switchover. In general, it is less risky to have a period of parallel operation between the old and new systems.
7. Operation and maintenance
After a period of time in parallel, it has been proved that the system is safe, reliable, feasible, then can be formally put into operation, and in operation to make good records and reports, and timely detection of operational problems, it seems to maintain and improve. (c): ERP failures are endless. Like any profitable thing, the ERP project itself is destined to exist risk. But as long as the risks are reasonably controlled and managed, most organizations should be able to walk the tightrope without incident. Ovid had one piece of advice for lovers in The Art of Love: it is better not to make fateful decisions based only on impressions formed in the dim candlelight of the night. Before falling y in love, he advises lovers to take another close look at their beloved in the bright sunlight of daytime. The same is true for organizations seeking ERP support, and some lessons about avoiding the risk of failure may be the sunshine.