Minimizing risk, maximizing returns

Posted by Alvin You
2013.10.25 22:14 Dynamics AX

많은 BP(Business Partner)들이 자사만의 프로젝트 방법론을 통해 AX 프로젝트를 수행하지만, 목표는 성공적인 프로젝트를 수행하고 고객 만족도를 최대화 시키는게 공통 사항이라고 생각합니다.

많은 방법론들이 있지만 대표적인 방법은 MS의 SureStep이라는 표준 방법론이 있습니다. SureStep같이 표준화된 프로세스를 100% 따르기는 힘들어 많은 방법론들이 프로젝트에 꼭 필요한 내용을 기반으로 구성되어 있습니다.

아래 내용은 방법론적인 내용보다는 BP 또는 VAR(Value Added Reseller) 회사들이 AX 기반의 Solution을 구축할때 어떻게 하면 위험요소를 줄이고 이익을 극대화 할 수 있을지에 대해서 MS Dynamics R&D 직원이 도식화 시킨 내용입니다.

Solution을 만드는 과정도 하나의 프로젝트라고 생각한다면, 고객사에 AX Implementation 즉 프로젝트 방법론 중 일부를 아래 단계별 과정을 응용해 프로젝트를 수행하면 좋지 않을까 싶습니다.


이 댓글을 비밀 댓글로

SAP vs Oracle vs AX

Posted by Alvin You
2013.10.13 23:41 Dynamics AX

Welcome to the ERP Fight Club:

In Today’s match let me introduce you with our fighters:
2.) Oracle(E-Business Suite)

3.) Microsoft (Microsoft Dynamics)

4.) Other ERP vendors.

Each of these has their own advantages and disadvantages. So to get the clear idea we will compare all of these according to different points. Starting with

1.Market Share:


So i think SAP is leading the way in this Game.

2.Average ERP Solution Satisfaction and Benefits Realization.

According to survey carried out over thousands of companies which use the ERP Tools.

SAP Gives : 75%

Oracle Gives : 60%

Microsoft Gives : 58%

Other ERP Vendors gives : 60%


So again SAP wins the game. The biggest advantage with SAP is the huge experience which it gets from its client and makes the ERP Tool more Power full to satisfy each and every business need.

3.Average Cost to maintain and implement the ERP Tool

SAP : $16 M

Oracle : $12 M

Microsoft :$3 M

Others : $3.5 M


if you don’t want to spend much for ERP tool just go for the last two options.

4.Average implementation Time Duration :

SAP : 15 Months

Oracle : 13 Months

Microsoft : 12 Months

Others : 11 months

5.Business Risk Factor:

This factor is most important as it gives the proportion of the companies that suffered from operational interruptions following go-live are relatively high.

이 댓글을 비밀 댓글로


Posted by Alvin You
2013.10.12 01:00 Dynamics AX

Dynamics AX 업계에 종사하면서 SAP 시스템과의 차이점에 대해서 고민하지 않으면 안 될 것 같아, 외국 친구들 중에 나와 비슷한 고민을 하는 사람은 없을까 해서 Google 검색을 해봤다.

아래 답변 내용은 Dynamics User Group이라는곳에서 누군가 AX VS SAP? 이라는 질문에 답변을 단 내용을 원본 그대로 가져온 내용이며, 찾아본 내용 중 가장 괜찮은 답변 같아 이곳에 옯겨놨습니다.


My company left SAP R3 for AX 2009 since 2008, I would say SAP is good for large companies but doesn't fit to middle-sized and small companies.

In terms of integration and implemantation, SAP is really heavy. and rustic, works on HP UX for me with text administration console for the database. An advantage, SAP is very stable and in my case had a better SGBD (Oracle 10) than SQL Server 2005 with AX. An other advantage, the financial and accounting module is better in SAP, a lot of things are automated,

My personnal point of view about development : there's no possible comparison, SAP is a frozen environnment, extremely complicated even if you want to do small visual customization as change labels in forms. AX is very flexible,has a simple and efficient development interface, the X++ language is easy to learn ( most like C# and java) once you have a small development experience and if you have skilled developpers, you can do just about what you want.

In summary, AX is more flexible and you can customize yourself your environment and adapt the processes to your company activity. you can do much more by yourself than in SAP which oblige to deal with external services providers but is more stable and efficient on a few processes. the cost aspect depends on your retailor but SAP is expensive, much more than AX.

About careers, I'm located in the country-sided France, so it's complicated but in large cities like Paris, for example, there's a lot of AX opportunities

You can mail me if you have precise questions



원본 위치 :


이 댓글을 비밀 댓글로