MBS Dev has been using the 4PIM approach for implementations for over 20 years. We constantly refine our methodology for the applications we implement and add new ideas that help our clients save time and implementation dollars while focusing on quality. Utilizing 4PIM for Microsoft Dynamics™ AX along with our Wholesale Distribution Suite (WDS) and Vertical Extensions, MBS Dev is performing an implementation and not a development effort. As with any implementation that is a large development effort, the potential for a success is greatly reduced as well as quality being risked. MBS Dev is committed to delivering quality Microsoft Dynamics™ AX supported solutions that greatly reduce the need for development during the implementation.

Phase I: Organizing
During the Organizing phase, we start with an Implementation Workshop where the project teams are formed with an emphasis on user involvement. During this phase we define how we work together, and set clear objectives. It is important for the teams to use this time to get organized. Your project team, working in partnership with MBS Dev professionals, is the key to a successful implementation.

Next, a 'big picture' software capability overview is presented, from a business perspective, along with system navigation basics. This is the foundation for development of an implementation project plan, which serves as a flexible tool used to define cross-functional roles and resources required for accomplishing specific tasks.

Phase II: Planning
During the Planning phase, the business model is established with an emphasis on understanding software capability that is specific to your business requirements. This model, is often called a 'Conference Room Pilot (CRP)', and becomes a prototype of the actual system where each business flow is analyzed and attuned to your business-integrating 'best business practices' for your particular industry view.

Phase III: Implementing
During the Implementating phase, the software solution is aligned with your business processes in a 'safe' environment prior to deployment. Continuing with the 'Conference Room Pilot', implementation risk is reduced through planned tasks, analysis of the system in your business, and through development of user operational procedures (using MBS Dev Business Process Flow templates.) The emphasis is preparation for an orderly transfer of knowledge from the project team to the user community. All business-system gap issues are addressed and documentation of personalization choices are completed. The 'Conference Room Pilot' is now used as the training vehicle for the user community to transfer system utilization knowledge thus insuring a smooth transition to the production system. Status and progress of scheduled tasks are tracked daily with the goal of full deployment within your business.

Phase IV: Go-Live
The Go-Live phase completes the implementation. The business/systems assessment (audit), usually three months after the implementation is complete, provides final analysis to ensure the implementation objectives have been met. Post ‘Go-Live’ support during the warranty period is also performed and monitored.