Microsoft, in the end you want to do? We can not know exactly, but according to Microsoft, the dynamics of a few years ago, we can do some speculation that if these projections come to reckon more accurate, we can thus derive great benefits.
Software Initial Development vs. Purchasing and Branding. To create ERP application from scratch is probably too risky business and 70-432 exam requires venture capital intervention to make new-born MRP a success. Most Microsoft Dynamics ERP products were purchased, not developed from scratch (exception is Microsoft Dynamics CRM). Microsoft 70-630 certification is good in finding a right moment to come to the market, when it is not yet mature, but it is clear that it is from now on real, not risky
These lines are written in June of 2006, based on the analysis of Microsoft Business Solutions policy and real actions in the USA, Europe, Latin America and Brazil.
MS Outlook Interface. Obviously majority of office workers are familiar with MS Outlook, MS Word, Excel, or MS Office. And the idea to capitalize on this fact is very attractive. If you look at Microsoft Dynamics GP – it is evolutioning to get kind of the same interface as MS Outlook.
Project Green Initiative. At least this was how we understood it back in earlier XXI century. It was like this – ERP application modules should be kind of standardized: Financials, HR, Distributions, Manufacturing, Logistics, etc. The integration between so-called Microsoft Suites is just a matter of technical solution development. As MS now owns several applications: Great Plains (Financials,. Distributions, HR), Axapta (Supply Chain and large 70-271 businesses), Solomon (Project Accounting), Navision (Manufacturing) – MS can get the best part of each application, encapsulate it into respective modules/suites and integrate into Project Green (on .Net platform, using C# or VB.Net). However, look at the first bullet – this approach to Project Green requires revolutionary rewriting and modules redesign.
What is the Plan? Maybe it is a way more simple than it was initially planned? Let’s for the moment assume this – why should we merge products? We can make them interact with MS Office, MS Sharepoint, MS CRM, Exchange, etc. We can expose business logic for light development on .Net level – eConnect approach.
Multinational Corporation. Large company has to offset multiple risks, related to ERP market, MRP selection and implementation. It is good idea to have small budget to understand which international ERP brand (or combination of brands) is good for your international operations: Microsoft Dynamics, SAP mySAP or 70-236 certification Business One, Oracle E-Business Suite, etc. Good example – Brazilian operations of US company (Great Plains in Chicago headquarters) deployed SAP Business One in Brazil to comply to Brazilian regulation – one of the main reasons for this turn was GP is not localized and supported in Brazil.
Conclusion. We believe that future Microsoft Dynamics will be combination of several applications: Microsoft Dynamics AX and Microsoft Small Business Accounting will be the flagships (form large/midsize and small businesses respectively). Microsoft Dynamics GP, NAV and SL will be in maintenance mode to serve existing clients and sell to their traditional niches. Microsoft Dynamics AX will be in development and expansion mode – to get into ERP horizontals and verticals and new sales will be increasing for Microsoft Dynamics AX.