ERP

Never trust the customer 🙂 We were sure that the server had last service packs applied, that’s the first that we asked of the customer IT, and got a definite answer that “But, of course!”. So we didn’t really think this might be an issue. Then we noticed that SQL Server build number was 1399, while my laptop was running 3042.

I had no clue how good my laptop was. Seriously. Today it kicked ass of an 8-processor server. Tomorrow we have a go-live of a Microsoft Dynamics NAV deployment, with manufacturing customized to support configure-to-order functionality. Refreshing manufacturing orders now calculates dynamic BOMs and routings, and it takes time.

Four months ago I attended a conference, where I had a chance to listen to Miha Kralj, an architect at Microsoft, talk about architectures. It was one of the best presentations I ever attended, and ever since I had this topic in queue, but never really had chance to write about it.

The biggest jeopardies often lurk where we least expect them. When implementing an ERP system such as Microsoft Dynamics NAV, what should be one of our best allies, turns out to be our mortal enemy. It has a simple name: The Standard. Standard processes, standard functionality, standard documents, standard system.

It’s a well known fact that IT projects fail every so often. Standish Group has been researching the success and failure factors of IT projects for a decade and a half, and they publish their results in their CHAOS report every two years or so.

About six months ago, when I was buying a car, a friend of mine, in a typical The Good, the Bad and the Ugly fashion, told me that there were two kinds of cars: good cars, and French cars. I bought a French car.

They say the only constant is change. I’d say that the only other constant is error. We humans tend to err. Give a repeatable task to a human, and they’ll mess it up every once in a while. Some call it the human factor . One of the many repeatable tasks in Microsoft Dynamics NAV is setting up items.

I’ve stumbled recently upon a support request, where a partner asked if there was a possibility to register purchases of services in Microsoft Dynamics NAV. When it comes to selling services, such as consulting, or repairs, NAV is your true friend, because you can use Resources to register sales against them.

A few days ago, I’ve got a question from a customer, about an alleged bug in Microsoft Dynamics NAV. According to online help, when you are posting output in manufacturing module, the last line of the type Output in the journal will actually adjust the inventory level.

In reality, if you need 1,000 of whatever product, the manufacturing process is rarely going to yield exactly 1,000 of it, even if you feed into the first operation the exact quantities of raw materials system calculated as gross requirements. The process may produce 980 or 1,020, but is hardly ever going to be exactly 1,000.