BatchMaster has evolved its own ERP implementation methodology to suit the specific need of Small and Medium Enterprises (SMEs). This is a proven, cost effective and time saving methodology. Also the methodology aims at ensuring that not only the BatchMaster ERP system is deployed quickly and easily, but also all the end users are comfortable using the system, and you start reaping from your investments very early. The methodology has classification based on the stages of implementation, and each stage has distinct set of activities and deliverables. Following are the glimpses from methodology used by BatchMaster for ERP implementation
This includes all knowledge transfer from Pre-Sales including the understanding of the Customer's high level expectations, business environment and what the main pain points, or areas of improvement, that have been discussed in the Sales process (including all application and report customizations shown/discussed during the sales demonstrations). This helps build credibility with the customer and give them a level of comfort that the BatchMaster team understands their 'Business' - which will in turn gain their trust and establish early confidence with the team. BatchMaster initiates the kick-off meeting by issuing an agenda to the entire project team including the customer team. BatchMaster ensures the involvement of stakeholders early on. This meeting is crucial for a couple of reasons:
- Introduction of the Implementation Services - processes, methodology and teams
- Setting up customer expectations for the engagement
- Defining success criteria and defining milestones and high level project timelines
Finalizing the Initiation Stage
By the end of the initiation stage BatchMaster has a clear picture of the proposed project idea, some thoughts on what might be involved, a clear idea about the major steps required, and a view of the project's boundaries/scope. To wrap up the Initiation stage, BatchMaster produces a document that encapsulates this wide agreement over the "arrows". This document is the SOW. This document is usually brief. In spite of its brevity, however, the big advantage in writing it up is that it gets everyone literally reading from the same page. It also serves as the input to the later Business Requirements and project planning documents.
Finalizing the Discovery
The Discovery stage represents the requirements collection aspect of the implementation. This stage defines the activities required to further detail the entire project and plan at a granular level. The implementation consultants conduct business process workshops to document and model the future state business processes. During the Discovery stage, gathering and documenting the customer's business processes and functional requirements is done. These requirements are documented which is an input to the Detailed Analysis Workshop in the Design stage. Additionally, all purchased software (as per the contractual agreement) is installed in the customer environment. The customer is given an overview of the Master Data system requirements which forms the base for all future data setup in the system.
The Analysis stage represents the detailed requirements analysis aspect of the implementation. This stage defines the activities required to further analyze the customer's business processes and functional requirements. BatchMaster team gets involved in a detailed and iterative analysis workshop and involves the customer power users as needed to iron out precise requirements by digging deeper into the needs of the customer. This ensures a quality solution design in the next stage. After the requirements are documented, they are analyzed and reviewed with the customer To obtain final approval. This forms the basis of a detailed scope for the implementation.
A gate review is conducted at the end of the stage to ensure that deliverables are provided per quality standards and that any risks and issues are proactively addressed going into the next stage.
This is one of the most fundamental steps involved in crafting the implementation to be carried out. Its outcome defines the system to be originated. In ERP implementation design phase requirements feasibility with BatchMaster is portrayed completely. The customer is involved in meetings and discussions as necessary. The Design stage builds on the previous Discovery stage by acting on the deliverables that result from the requirements workshops conducted. The Design phase culminates with the completion of the Solution Blueprint Document. A gate review is conducted at the end of the stage to ensure that deliverables are provided per quality standards and that any risks and issues are proactively addressed going into the next stage.
Involving testing of the system components as defined and approved in the Solutions Blueprint, and populating the system with Customer Master Data, this stage incorporates within itself the 'Pilot Configuration' which is based on the real customer scenario. Pilot is done and performed by the BatchMaster consultant based on the customers' processes and requirements. BatchMaster Consultant acquires the Master Data from the Customer via a Master Data template spreadsheet which is then put into the system by the BatchMaster team.
This stage marks the conclusion of the implementation project. To successfully transit form the current legacy system to the all new BatchMaster, mutual efforts from the whole project team is vital. This stage includes key activities such as, end User Training, User Acceptance Tests (UATs) and the actual cut-over to the new production environment and Post Go-Live Support.
Upon successful completion of the training of key users and the User Acceptance Testing, to tune up the performance, BatchMaster has to arrive to a decision wherein the customer needs to proceed with the go-live or to delay the same until any critical issues are resolved. As all Data Migration tasks have been executed, the system is now ready to go-live. After which, any changes done would be placed under the change control process. As the project is ready to be closed, an Implementation Closure Issue List is prepared to keep a track of all the outstanding issues to be carried forward. Once the customer goes live, post go-live support is provided by the BatchMaster consulting team. A stage gate review is performed at the end of this stage to ensure that deliverables are bestowed as per the desired quality standards and that any risks and issues are proactively addressed prior to going into the next stage.
This stage signifies that the project is now complete and is ready to be closed. To close a project certain actions need to be performed and also includes transition knowledge to the customer. Final invoices, lessons learned and the Project Closure Report are prepared. In order to keep a track of all the documents, the team also prepares a folder with all the project deliverable documents with their approvals till date. These documents are sent to the customer to be reviewed again and a final sign off and acceptance is obtained, thus marking the end of the implementation cycle.