ERP – Page 5 – Vjeko.com

Panorama’s ERP Report reveals important facts

Post published:March 5, 2009
Post comments:2 Comments
Reading time:4 mins read

For a long time, the ruler of project reports was Standish Group’s (in)famous Chaos report, which analyzed IT project success/failure factors. While many of the Chaos report’s findings applied to ERP implementation, the report as a whole was primarily about software development projects. And as we all know, implementing ERP is not the same thing as software development. Hopefully.

Panorama Consulting Group, an independent ERP consulting firm from Denver, Colorado, has conducted a market research in 2008, that explains ERP implementation project success factors and reveals some interesting metrics about real ERP costs, duration and benefits. Finally, we have a decent ERP project report, which reveals some important facts about Microsoft Dynamics.

(more…)

Associazione Marittima di Sabioncello

Post published:February 19, 2009
Post comments:6 Comments
Reading time:6 mins read

A short story about maritime trading, steamboats and Microsoft’s Azure Services Platform in short to mid-term ERP and Microsoft Dynamics NAV perspective

This is a story of a business which failed, and it didn’t have to. It had all the capital and resources it needed to grow, it held a solid share in an expanding market. And yet, they failed.

Associazione Marittima di Sabioncello (AMS), or Maritime Society of Pelješac, was a shipping company founded in 1865 in Orebić, a small coastal town of southern Croatia. They grew to a fleet of 33 sailing ships, they shipped worldwide, their business expanded so much that eventually they built their own shipyard. Allegedly, they were one of the biggest and most prosperous maritime merchant companies in the Mediterranean.

And then an innovation came along, which ruined them.

(more…)

Why is add-on better than custom, any day?

Post published:February 16, 2009
Post comments:21 Comments
Reading time:6 mins read

Implementation is like marriage. For better or worse, you choose a piece of software, take it under your roof and commit to it for a long term, so help you God.

And as in marriage, if you want to live happily ever after with your new software, the my way or the highway attitude doesn’t help much—you must be open to compromise.

Last Monday, I argued for avoiding customizations if at all possible, an argument I stand by firmly. It’s like forcing your wife to color her hair pink. I don’t know about your wife, but mine doesn’t color her hair pink. If you like it pink, it’s probably something to think about before turning your yes in.

But NAV is NAV, isn’t it? It has what it has, and if I need it different, I have to customize it, right?

Wrong. You can compromise.

(more…)

Top 12 Microsoft Dynamics NAV features to defeat recession

Post published:February 12, 2009
Post comments:6 Comments
Reading time:8 mins read

There are three kinds of people: those who watch things happen, those who make things happen, and those who wonder what happened.

The world is in crisis. Some countries are hit harder than the others, some markets have sunk deeper than the others, but the effects of global economic recession are obvious, and if the crisis didn’t hit you yet, fasten your seatbelt—it surely will.

With the whole world wondering what’s going on, the winners will be those who learn to navigate the troubled waters and make things happen. This is much easier with a piece of good business management software, such as Microsoft Dynamics NAV.

(more…)

Sure Step in action: Architecture Assessment

Post published:January 29, 2009
Post comments:0 Comments
Reading time:6 mins read

Implementing a new Microsoft Dynamics solution doesn’t merely introduce a new piece of software into your environment. Yes, the software is an important part, you need to deploy it successfully, configure it as necessary, probably even customize it and change the business logic under the hood.

One component, however, is easily overlooked, and you wouldn’t believe how often it’s not addressed until late. Or too late. It’s the infrastructure.

Infrastructure is tough. It’s not just servers and desktops with some wires, switches and access points in between. Its a lot more. What kind of hardware do you need for your servers or desktops? What kind of performance do you really need? What kind of network layout is optimal for your transaction volume? Should you run the client on desktop machines, or would a remote desktop access be a preferred method? Do you virtualize your servers? What kind of failover capacities do you need? Can you retain any of your old hardware? How many users will use the system? Tomorrow? In five years? What about interfaces and integration to other systems or applications?

A couple of wrong answers, and down you go.

(more…)