Sunday, December 25, 2011

AS-IS Process Mapping

AS-IS process mapping is mapping the business processes of your organization as it really is. This is normally done at the preparation phase of the project.  Assistance of the experts from each functional department( E.g.- Manufacturing, Quality Management, Production Planning) is critically important for mapping AS-IS processes. Processes should be mapped as it really is and not in the way people think it should be. It is important to look at the processes at a higher level and map without going into deep detailed. Always note the interaction between different functional departments of the business. 

Make a common agreement on mapping before you start. Choose symbols for process,data flow, input, output, start/end , semi finished product, document etc. which can be used commonly in mapping in all departments. It is important to present the document in a common readable format to the SAP consultants. AS-IS maps will be the foundation document for the blueprint. It will ensure you have not missed anything in AS-IS business when you are forming the blueprint. SAP is not typical software engineering it is Business Process Re-engineering (BPR). SAP consultants are suggesting new business practices in the blue print stage.  By looking at AS-IS maps consultants can decide where you need customized programs and where you can use standard SAP.  

AS-IS documentation will be used to study the current processes of the business comprehensively and as a base to form the business blue print. However this does not intend SAP should be customized completely to suit your business. 

Tuesday, December 6, 2011

Starting the Journey

SAP implementation is a huge project. It takes a considerable amount of time depending on the size and scale of the implementation. Sometimes it takes more than 2 years to complete a SAP project. However 7-8 months time will be sufficient to fully implement SAP for a mid sized company.  There are five main phase of a SAP project. (This is the general and most common definition. This can be changed depending on the different situations of the  project and company.)

1. Project Preparation
2. Business Blueprint
3. Realization
4. Final Preparation
5. Go live and Support

Preparation phase is the initial planning of the project. You need to evaluate implementation partners and choose the right implementation partner, define the scope of the project roughly,evaluating vendors, buy SAP license, assign human and other resources etc.

Evaluating Vendors

See whether they have SAP experience in your industry. Because knowing the business is critically important than knowing SAP. You need to study their SOWs (Statement of Work) carefully to evaluate their bids specially for the SAP customization processes.Some vendors are mentioning maximum number of cutomized RICEF objects (Reports, Interfaces, Conversions, Enhancements, Forms) in their proposals. Standard SAP needs to be customized to suit your business. Customizing is costly. Also it is important to evaluate the project duration, training programs an support plans proposed by each vendor.

An internal SAP team should be appointed to get their support for the project. Team should have members  representing each different business process/department of the company. Better to choose the best person from each department for your team who can be used for change management processes.

Business Blueprint phase is the documentation of company's business processes and organizational structure in the way which we are going represent our business in SAP system. Functional specifications are generated in this stage generally. Realization is the developing the system  according to functional requirements. This is the configuration of requirements of the Blueprint. Then you can do testing and adjusting in  final preparation phase and go live with your new ERP system.