In this phase you document and define the scope of your R/3 implementation and create the Business Blueprint. The Business Blueprint is a detailed documentation of your company's requirements in Winword format. Application consultants and the Business Process Teams achieve a common understanding of how the enterprise intends to run its business within the R/3 System, by carrying out requirements-gathering workshops. During Phase 2, the project team completes R/3 Level 2 training; this is recommended as early as possible and before the workshops start. Fig. : Elements of the Business Blueprint The project team selects the processes that best fit your business from R/3's functional offering, using the following tools:
Establishing a proper cycle of project management activities ensures that the implementation project stays on target. Project Management includes all project planning, controlling and updating activities. The activities in this work package are:
- Conducting Status Meetings for the Project Team
In the status meetings each project team’s status is reported on, and important information is shared among the different project teams, so that there is a complete picture of the implementation process and progress. Progress impacts budget, scheduling and resources, and also the go-live date. It is important to coordinate integration aspects between the different project teams.
- Conducting the Steering Committee Meetings
These meetings update the Steering Committee on the project status and obtain decisions about project issues that cannot be resolved by the project team (for example, changing the schedule or obtaining additional resources).
- General Project Management
ASAP makes sure that additional tasks that support the implementation project or form the basis of further project planning are not overlooked.
- Addressing organizational issues relating to organizational Change Management.
Training the project team should reflect the scope of the R/3 implementation and the needs of the individual team members. You want to conduct project team training in order for team members to obtain R/3 functional and technical knowledge to be effective members of the implementation project team. In the Business Blueprint phase, project team members attend Level 2 training courses.
At this point, you install and technically configure the quality assurance and development systems. Within this work package, you define and test system administration procedures for the development system.
The foundations of the technical design are laid by the work done in the project preparation phase. The definitions of the implementation scope and the system landscape are used for a detailed analysis of your hardware, operating system, database, and network requirements.
- ASAP assists in evaluating the impact of the implementation scope on the hardware or network infrastructure with the organization.
- You also check whether processes used at particular workplaces call for special hardware requirements (for example, different screen sizes, PC configurations).
It is also important to define the strategy for maintaining the system landscape in more detail. This should include steps on how to provide R/3 release upgrades, integrate hot packages, along with operating system and database upgrades.
The technical design is presented to the steering committee to be signed off at the end of the Business Blueprint phase.
Even though the development system environment is not needed by the business process teams until the end of the Business Blueprint phase, it is recommended that the development system (and possibly a test/quality assurance system) be installed as early as possible. This will enable the technical team to have a few weeks to work with the R/3 System prior to any development or Customizing activities. AcceleratedSAP provides a checklist for installing the hardware and the R/3 System, and for verifying the R/3 configuration.
The next step is to install and configure the development system clients. During this activity you set up R/3 clients to reflect the business process and organizational decisions.
There are a number of pre-configured systems that are designed for different enterprise and business types. These systems are described in more detail at the end of this chapter. They should however be installed as part of the system landscape before the start of the Realization phase. If you are using the Ready-to-Run R/3 (RRR), this represents an accelerator for this work package, because R/3 is pre-installed and the parameters of the Basis System are preconfigured.
The R/3 Systems Operations Manual for the system adminstrator is begun to be put together here. It contains the documentation on the system installation and system administration procedures/policies, with detailed descriptions, persons responsible and escalation management plans for all R/3 System management activities.
The Pre-Configured Remote Link is a service used to simplify the setup of the OSS link between the customer and SAP. The setup is not difficult, but entails extensive logistical organization. The customer receives the hardware, OSS IDs, software and hardware configuration, and training and support for this area.
This service can save many days of effort for the customer at the beginning of the project. Among other things, the "rcPack" as it is called, contains an analysis of network and telecommunications infrastructure, a determination and proposal for an optimal mode of transmission, application forms and documents required by carriers, and purchase and delivery of necessary hardware.
After the R/3 System is installed, it is necessary to configure the operational enviroment for the development system. This should include the backup/restore procedures along with the CCMS (Computing Center Management System) settings. These tasks are an ongoing process throughout the Business Blueprint Phase.
Defining the Organizational StructureAn important step during the implementation of R/3 is the mapping of enterprise-specific structures and requirements using R/3 organizational units. Decisions on the use of specific organizational units are influenced by various factors relevant to the organization itself and the implementation goals it is pursuing.
Fig.: R/3 Structure Modeler for displaying organizational structures
The selection, usage specification and linking of the R/3 organizational units should be carried out at an early point in the project, and involves management as well as user departments. Usually there are several different possibilities of mapping enterprise-specific organizational units. You can define alternative organizational structure scenarios in order to compare them and decide on the most suitable one.
Questionnaires and a graphic display support the discussion on organizational units between SAP consultants and their customers. Mapping the enterprise onto R/3 organizational units becomes transparent, and the simple, systematic display supports the interpretation of differences between alternative structure scenarios.
In order to create structure scenarios, SAP has developed the R/3 Structure Modeler, included in AcceleratedSAP. It is used as an add-on under Visio® 5.0 and offers comprehensive support due to its extended graphic functionality (creation, naming and allocating of new instances of the R/3 System, consistency checks, definition of views, scenario-specific documentation, help files). The Structure Modeler is available in German and English. It is integrated in the Knowledge Corner of the ASAP Roadmap.
The use of tile diagrams has proven effective for the graphic display of structure scenarios. Every occurrence (instance) of an R/3 organizational unit is represented as a colored tile. The tiles representing instances of the same R/3 organizational unit have the same color. The positioning of the tiles in several layers enables you to recognize relationships between them.
The Q&Adb enables you to describe the structure of your enterprise on two levels:
- The Business Overview level, with organizational structure questions enabling an analysis of enterprise-specific determining factors, and
- Organizational questions for each enterprise area.
The Structure Modeler also enables you to illustrate your organizational structure in relation to a distributed system infrastructure.
After you have defined your organizational structure for R/3, the definition of the business process for your Business Blueprint is the next step. You now map the enterprise requirements onto R/3 business processes, in order to create the conceptual design for your R/3 implementation. For this, the following activities need to be carried out:
- Conducting business process workshops
- Completing the Business Blueprint, reviewing it and obtaining management signoff
- Setting up an end user training schedule
Besides determining the R/3 functionality to be implemented, the following types of requirements should be identified in the business process workshops:
- Reporting requirements
- Interface requirements
- Conversion requirements
- Enhancement requirements
- Authorization requirements
Since all the results gathered during the workshops will subsequently create the Business Blueprint, the importance of this step cannot be underestimated. The main tool used to define the business processes is the AcceleratedSAP Question & Answer Database in conjunction with the R/3 Reference Model. In the process, information is gathered using the following tools:
- Business Process Questions (via R/3 Reference Model)
- Customer Input (CI) Template
- Business Process Master List
- Knowledge Corner
The R/3 Reference Model contains over 1,200 business processes, created on the basis of feedback from R/3 customers on their "best business practices". This structure and visual representation in models support the business process discussions, as well as being used to graphically illustrate a particular area of functionality. There are different types of models available for different target groups and purposes. Project managers, for example, need an overview of all the R/3 components and processes, whereas a team member is more likely to require the details of a process.
The R/3 Reference Model serves as the basis for business engineering and the definition of business process requirements. Using the various types of models, you can quickly identify potential for business process optimization.
Fig. : Different types of models in the R/3 Reference Model
The R/3 Reference Model can be used as the basis for the following:
Comparing the standard R/3 functionality with your enterprise's own organizational structures and processes, and defining all the relevant processes and functions, in order to create the Business Blueprint
Creating documentation (including graphics) for the conceptual design
Optimizing your business processes
Training the project team and users
Writing user documentation
The R/3 Reference contains the following types of models designed for different target groups and goals:
- Process model
The main type of model, containing process flow views of the entire R/3 functionality, for example, procurement of consumable materials or purchase order processing. This model is used, among other things, for industry-specific modeling and is described below in greater detail.
- Component hierarchy
In the component hierarchy, you select the R/3 components you want to use in your enterprise to support your business processes. Examples would be the component HR Human Resources, or Accounts Payable from FI Financials. This has a chain of effects throughout the entire R/3 System. The selections made in the component hierarchy also determine the structure of the following:
- Implementation Guide (for R/3 Customizing)
- Session Manager (to define company menu, user-specific menus)
- The Profile Generator (for user authorizations)
Fig. 26: Configuring the IMG by selecting the application components
For more information, see the section on R/3 Customizing under Phase 3.
- The Business Object model, which is a description of about 200 business objects such as customers, vendors, employees, cost centers, etc.
The main purpose of the Business Object Model is the determination of the input/output assignment of business objects. These are lists that tell you which business objects are required as input for a process and which are created as output. It is also used for checking the data and processes in the productive system.
Each object in the system represents something in the real world, for example, a sales order or customer. Business object technology has several merits, not least the integration and synergies between objects from both a technical and a business viewpoint. R/3 Business Objects as real-world entities will emerge more and more to allow enterprises to design parts of their business processes by using objects.
The R/3 Reference Model, together with its process models, business objects, business object models, data models and their data and links, is stored in the R/3 Repository. It also contains technical information such as data definitions, screen definitions and program objects that are used for developing and enhancing the R/3 System. In addition, the R/3 Reference Model, in particular the process model, forms the basis of requirements gathering for the Business Blueprint in the Q&Adb.
The R/3 Reference Model is used to access and link processes and business objects. Since the business objects are used to communicate with the R/3 Repository, both the data model and the structure and contents of the underlying tables can be accessed. This makes interface and enhancement design considerably simpler.
Process Model
Together, the organizational structure and the model graphic (see below) form a powerful basis for the modeling of all business process requirements and their optimization. Process models are structured hierarchically and contain the following elements:
- Enterprise process areas : an area in an enterprise that has responsibility for certain business scenarios. Examples of enterprise process areas are sales or procurement. Enterprise process areas are used for structuring purposes only and are not represented graphically.
- Business scenarios are assigned to a particular enterprise process area, and describe on an abstract level the logical flow of your business across different application areas, such as Materials Management or Quality Management, using processes. Event-driven process chains (EPCs) and value chains are used to visualize them. An example of a business scenario would be "Sales order processing for assemble-to-order".
- Process groups are groups of individual processes that are bundled so that they can be visualized more easily.
- Processes : These describe the smallest self-contained business sequences and represent the possibilities within a given R/3 transaction, where detailed functions are carried out. Processes are also represented graphically as EPCs.
Fig. 13: Hierarchical structure of business processes in the R/3 Reference Model
Industry-specific Reference Model
In Release 4.0, the R/3 Reference Model was revised and aligned more closely with different industries’ needs. The R/3 Reference Model now matches many the requirements and business process structures of many industries quite precisely, and more effectively bridges the gap between the business and technical viewpoints.
The industry-specific R/3 Reference Model was developed in cooperation with leading industry players using their underlying concepts and language. As a result, you do not have "re-invent the wheel". In the Q&Adb, you can simply choose the scenarios that correspond to your type of business. Moreover, you can mix and match scenarios, and change them to suit your requirements. Examples of industry-specific senarios can be seen in the graphic below.
Fig. 23: Industry-specific Reference Model with Enterprise Process Areas and Business Scenarios
Visualization of Process Models
Fig. Xx: Value chain for baking goods production
Event-driven process chains (EPCs) link data, tasks and organizations, and are therefore an important element in business process design. As well as describing the chronological sequence of steps in a process, they also take into account aspects of the organization and information requirements. Elements of EPCs are explained in more detail below.
Fig. 12 (2-5): The basic structure of an event-driven process chain
EPCs consist of four basic elements:
Navigation in the R/3 Reference Model
You can display the contents of the R/3 Reference Model with the Business Navigator or the Business Navigator Web, which are fully integrated into the R/3 System. You can display the model in either of two hierarchy views, as described above:
- Process flow view
- Component view
The following graphic shows the process flow view of the R/3 Reference Model in the Business Navigator.
Fig.: Process Flow View of Business Navigator
Fig. 18: Business Navigator Web
These modeling tools can be launched from the Q&Adb.
Question and Answer DatabaseThe Question & Answer Database (Q&Adb) contains technical and general business questions, the answers to which are the input for the creation of the Business Blueprint. The questions are designed to determine the enterprise's detailed business requirements in an integrated environment. In conjunction with the Business Process Master List, the Q&Adb is also used to determine the baseline scope, cycle plan and integration testing scenarios used in later phases.
- The Baseline Scope Document
Defines the business processes and requirements that will be configured and tested during the baseline configuration session.
- Cycle Plan
A tightly controlled group of business processes, which together constitute an optimal sequence and assembly that is used for configuring and developing the R/3 solution.
- Integration Test Plan
The plan that joins together the defined resources, time frames, scope and procedures for executing the integration test.
Fig. Xx: Defining the business process requirements via questions in the Q&Adb
You can also add, change, and delete questionnaire content in the Q&Adb. In this way, project teams can customize the requirements gathering process by creating new questions and editing existing ones.
The business process questions and customer input template (see below) are oriented along the current release of the R/3 Reference Model, specifically of the process model. Within this framework, what is in and out of scope is determined for the project, by toggling the business scenario or process "in" or "out" of scope in the Q&Adb.
There are several reports that you can generate once the questions in your Q&Adb have been completed. One important report is the Enterprise Area Scope Document defined in Phase 1: This is an Excel spreadsheet containing the SAP enterprise areas and scenarios that a company will be implementing. It is used in initial scoping of the project, to assign Business Process Owners, and also as a reference to begin Business Blueprinting.
Further reports are the Business Process Master List (Excel file) and the Business Blueprint (Winword file). These are explained in more detail below. You can also generate an Excel spreadsheet of all open issues in the Issues database.
Customer Input Template
When the business processes are being defined, the Customer Input Template forms a standard structure for gathering specific data on the business processes. The customer input template can be modified to reflect the areas of concern for your implementation project and is used in conjunction with the business process questions.
Fig. Xx: The CI template in the Q&Adb
The following graphic shows how tools are used in combination to ensure the flow of information through the project.
Fig. : Flow of project information through the Q&Adb
When a process or a scenario appears more than once, one of the processes or scenarios can be defined as the dominant (representing the 80% case), and the other processes/scenarios are then defined as subordinate. This means that answers given to the dominant will be used as a reference for all subordinates.
After the business process workshops have concluded, the results are processed and documented within the Q&Adb. If enterprise-specific processes come to light, they can be added to the Q&Adb at any level, as needed to provide one complete database for your requirements.
The Business Blueprint serves as your conceptual master plan and is assembled into a detailed written document. This document summarizes and documents the business requirements in detail, and serves as the basis for organization, configuration and, if necessary, development activities.
The Business Process Master List (BPML) is the primary activity-tracking and control mechanism used by the project management team during the Realization phase.
The BPML is first created at the end of the Business Blueprint phase from the Q&Adb in order to create the Baseline Scope Document and then used during the next phase for monitoring and control of the R/3 configuration and testing activities. You can find more information on the BPML in the next chapter.
The baseline scope is generated via the Q&Adb and the Business Process Master List. The amount to be included in this scope will vary based on each individual project implementation. As a guideline, the baseline scope should target to address roughly 80% of the total business requirements.
As a last step in this phase, a quality check, the final verification of all deliverables, from this phase should be carried out. You can also use the Concept Check Tool for this. However, it is also important that continuous 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, system environment, project team training and project standards. Issues regarding changes in scope, impact on budget and resource planning must be addressed.
Together, ASAP and the Business Engineer split up the work of creating the Business Blueprint and configuring R/3 in manageable steps, starting at the top with the overall structure of your business and gradually working down to the details of your business and process requirements.
Accelerated Solutions/Preconfiguration
SAP's Accelerated Solutions speed up implementations by providing you with two important types of preconfiguration:
- Technology-based preconfiguration: this refers to the "turnkey R/3 solution" called Ready-to-Run R/3.
- Content-based preconfiguration: this refers to systems preconfigured for countries, and systems preconfigured for industries. Country configurations have been created for the United States and Canada, and are also called "preconfigured clients".
Preconfigured US and Canadian Clients
Configured features for the U.S./Canadian market:
- Charts of Accounts
- Organizational Structure
- Print Forms or Layout Sets including: Checks (U.S. & Canadian), POs, Picking List, Packing List, Invoice, Sales Order Confirmation.
- American/Canadian units of measure
- An R/3 end user template
- Integration of PP with FI/CO
- Sample work-in-process calculation
- Asset Management preconfigured with American depreciations
- Sample functional areas for Cost of Goods Sold Accounting
R/3 modules containing preconfigured items are FI/CO, MM, SD, AM, some PP and Product Costing.
The preconfigured client can be used as:
- A starting point for further configuration. In this way, you avoid configuring settings that are typical for your country or industry.
- A sandbox client with a simple organizational structure. Like the IDES model R/3 company, the sandbox client in the development preconfigured system can be used to get a feel for R/3 and what it has to offer. Different configuration scenarios can be created and tested in a short time using this as a base.
Preconfigured Industry Systems
Preconfigured systems are available or planned for the following lines of industry:
- Aerospace and Defense (planned)
- Automotive Suppliers
- Banking (planned)
- Consumer Products
- Construction (for Rel. 3.1)
- Engineering (planned)
- Healthcare
- High Tech (planned)
- Insurance
- Media
- Oil&Gas
- Paper (planned)
- Pharmaceuticals
- Public Sector (planned)
- Retail (planned)
- Steel
- Utilities (planned)
A preconfigured industry system includes the following:
- The industry model with industry-specific business scenarios and processes. For each model element, an industry-specific or even enterprise-specific term can be used.
- Industry-specific system settings (Customizing settings) to run the business scenarios in the R/3 System
- Sample master data to use for every business scenario
- Documentation of all steps and presentations with examples and explanations from the industry
Fig. 21: Preconfigured R/3 Systems for vertical industries
SAP is committed to providing preconfigured industry systems for all of the SAP Industry solutions. However, the preconfigured system principle is not limited to those provided by SAP. Partners and enterprises can create their own models for accelerating implementation in particular areas or markets.
The concept of preconfigured industry systems also enables software partners or enterprises to include their specific add-ons to the specific preconfigured industry system.
No comments:
Post a Comment