The "Blueprint" refers to all the activities, which are necessary for the reproduction and description of the customer's business operations in an ERP System. These activities commence before the ERP project itself. This activity is to complete the Blueprint, which is one of the main deliverable. The Blueprint serves as your master plan, and becomes a detailed written document. This document shows you the business requirements in detail, and serves as the basis for organization, configuration and, if necessary, development activities.

The ERP Systems Blueprint – Where it all begins

The "Blueprint" refers to all the activities, which are necessary for the reproduction and description of the customer's business operations in an ERP System. These activities commence before the ERP project itself. This activity is to complete the Blueprint, which is one of the main deliverable. The Blueprint serves as your master plan, and becomes a detailed written document. This document shows you the business requirements in detail, and serves as the basis for organization, configuration and, if necessary, development activities. Before any transactions can be reproduced in the system, the total business extent involved must first be defined. This is done by writing down the essential business processes that are to be supported by the ERP System. Some systems may have a built in analyzer tool to support this activity. Once the framework has been defined (overall implementation plan), the individual business operations can be systematically analyzed in greater detail, documented ("scripted") and reproduced ("prototyped"). The activities stretching from the conceptual design to the documented prototype thus lead to the detailed solution. This article outlines the overall context in and a modular manner of building and working with an ERP Business Blueprint. The Blueprinting phase is made up of seven major sections. 1. Project Management The purpose of this section is to establish a proper cycle of project management activities to ensure that the implementation project is on target. It determines all project planning, controlling and updating activities. It also identifies where changes in the relationship between business processes and the organizational structure need to be managed, in consultation with departmental management. Activities will include; Conduct project team status meetings, conduct steering committee meetings and general project management. 2. Change Management The change management section addresses the organizational and human resource factors that impact the ERP implementation, ensuring the timely success of the implementation. This includes a series of change processes that allow the change team to manage organizational risk, accelerate the implementation, and optimize organizational processes. These change management processes ensure that the change team understands and manages the organization’s perceptions of and responses to the changes that will occur as a result of implementing the ERP system. Activities: • Create a Business Impact Map • Complete the leadership risk assessment • Develop sponsorship strategy • Complete the baseline project team risk assessment • Complete the baseline organizational risk assessment • Establish the change communications framework • Establish management structure for skills development process • Establish management structure for knowledge transfer process 3. Project Team Training The purpose of this section is to train the project team to implement the system efficiently. Training should reflect the scope of the implementation, and the needs of the individual team members. 4. Develop System Environment The purpose of this section is to install and technically configure the technical sandbox client and development systems. You must define and check quality assurance system administration procedures for the development system. Activities: • Create technical design • Set up development environment • Install setup of system landscape • Systems administration • Initialize implementation table settings 5. Business Organization Structure This section is to define the enterprise organizational structure using organizational units, such as company codes and sales organizations. In conducting the organization structure workshop, several topics are discussed, including; what enterprise process areas and business processes will be used in the ERP system setup or configuration? What organizational units within the company will be affected by the implementation? This will be the creation and definition of the organizational structure. 6. Business Process Definition The purpose of this section is to define the company requirements based on ERP business processes, to provide the required functions. You must first define your organizational structure. The business process definitions create your Business Blueprint. Activities will include: • Prepare for business process workshops • Conduct global requirements workshop • Conduct business process workshops • Conduct detailed requirements workshops • Prepare end user training plan • Complete Business Blueprint • Business Blueprint review and sign off 7. Business Blueprint Quality Check The purpose of this section is final verification of all deliverables from this phase. It is critical that quality checks be performed throughout the phase, as tasks are completed. The Business Blueprint ensures that everybody has an accurate understanding of the final scope of the project regarding business processes, organizational structure, and system environment. In addition, this includes project team member training, project standards, and strategies in the technical area. You must address issues regarding changes in scope, impact on budget, and resource planning. Perform quality check and obtain a signed approval. Summary The Business Blueprint is one of the main deliverables. It serves as your conceptual master plan, and becomes a detailed written document. This document shows you the business requirements in detail, and serves as the basis for organization, configuration and, if necessary, development activities. Results: • Documented and approved project goals and objectives. • A well-grounded and detail implementation plan. • Overall project schedule and implementation sequence. • Business process definition and organization structure. • A coordinated, cost-effective, and organizationally effective rollout plan. • A successful ERP implementation.