Don’t Take the Source Code

source code

The most difficult questions are the most open ones. What would you do if you were Prime Minister? Better to be asked specific questions: What would you do about school dinners, or Iraq, or capital punishment, or conscription, or food labelling or the railways? If the questions are more particular then you’ll probably have an opinion, or at least something to say.

I remember English composition lessons at school. Write a story, the teacher would say, and I wouldn’t know where  to begin. Write a story about four-eyed Martians and I’d know where to start. Complete freedom is paralysing. When everything is possible, nothing comes to mind.

For somewhat different reasons, being able to do anything at all with business systems is also terrifying. Partly, perhaps, because you don’t know where to start, but ,mainly because you don’t know when to stop.

Although nothing falls entirely into one or the other category, you can roughly divide business systems into those where you get the source code, and which you can do anything with, and those where you don’t get the source code, where possibilities are constrained.

I like constraints. When there are constraints, possibilities are very many fewer, and there are clear choices to make. This is the better situation.

Of course, if you get the source code you can build something that does exactly what you want to do (well, what you want to do NOW), but it will take you forever and cost you an infinite sum. When you don’t get the source code you may get 90% of what you want at a reasonable price, and soon. Moreover, you will find upgrades immensely easier.

I worked years ago, as a consultant, with an oil company that decided to take one of the largest business systems in the world, adapt the source code and implement it globally. The project was immensely expensive, took far longer than planned, and when the system was ready it was already out of date and impossible to upgrade. The system was abandoned in favour of another even bigger one that needed less adaptation.

And at LLP Group, a software reseller, where I work, we had two divisions – one selling Microsoft’s modifiable Dynamics software, where our projects were often disastrous, and one selling Infor’s non-modifiable software, where our projects were manageable, satisfying and profitable.

Don’t touch the source code!


Choosing New Software – Best of Breed or Integrated?

When you’re looking for new software, one of the first things you must decide is whether to look for two or more systems that are best in their particular fields, or one software system that does nearly everything you need.

This choice is between ‘best of breed’ systems:

Best of Breed

or ‘integrated’:


The problem with the best-of-breed choice is that you have to do the integration yourself, or commission it. This means developing software to map the data in one system to the data in the other, scheduling the execution of the integration software, ensuring that reference data such as account codes and department codes are synchronised in both systems, and that both systems can be reconciled. It gets even more complicated if there are more than two systems in the mix.

The problem with the integrated choice is that you rarely get everything you want from one system, or, not affordably. And it means that if you only want new software for one particular purpose (e.g. professional services management) then you have to throw away everything else that you have and start again.

It’s not easy to choose.

But if you decide to go the best-or-breed way then Infor’s ION integration framework solves the integration problems by providing technical, logical and procedural management of all aspects of integration.

See this YouTube video to see how we’ve integrated time@work (for Professional Services Management) and Infor SunSystems (for back-office accounting):