Since you mention your processes are supported with, among others, in house built applications, and you are also interested in open source, did you consider the possibility of developing your own CMDB in open source?

I once participated in a project for developing a CMDB using open source (php with postgresql) and it was a very rewarding experience...

did you consider the possibility of developing your own CMDB in open source?

I once participated in a project for developing a CMDB using open source (php with postgresql) and it was a very rewarding experience...

Having written a CMDB myself (before I even knew it had a name) all I can say is: think hard about why.

I can truthfully say that: it was fun, I learned a lot.
In hindsight I can also add: It was expensive, over engineered and I am so glad I don't have to support it.

Things change and it is very nice to let someone else do the change for you. Going for a solution with Out Of The Box software (minimal configuration and customization) seems to be a much better way to go.

I have implemented Change Management using ITIL best practice and trying to orient all involved services / processes that touch Change Management in multiple companies

This was done regardless what the tools that were in place. Clarify, Siebel, Remedy, HP, Vantive, req (cmd line), Charm, Promiss {the last 2 - in house dev tools I help make).

ITIL is about processes, procedures and people. IT IS NOT ABOUT TOOLS

A tool could say it is ITIL CERTIFIED, ITIL ACCREDITTED or PINK CERTIFIED or ACRREDITED etc. but.

If the tool out of the box (or with minor configuration) does not follow your policies, procedures, processes etc that you have written and developed and implemented without this 'certified' tool, then when you get the tool... you have to fit your processes, procedures, etc to how the company that wrote the tool thinks the various itil processes should be done.

For example: Several tools used for service desk/help desk was designed to be a Customer relationship manager tool and were adopted to be incident and problem tools. however, I have found that the use of the tool in reality does not match what the box says

So that is my issue regarding tools that says ITIL certified / verified etc.. It means absolutely nothing. It is like saying Budweiser is Anheiser Busch certified.

Pink certified tools come from what company ? PinkElephant ? or a
related company ?

As to open source tools, I think the concept here is misunderstood / misconstrued

Are you talking about a tool written in Linux (It is open source, linux) but the company selling the tool would still want money for the configuration and maintenance work

or

Are you talking about a low cost (approaching free) that you can configure yourself to do what you want ?

Gee.. If it is low cost... the value or the capability of the tool may also be low

or

are you talking about a tool that is reasonably priced - in regards to licensing / seat / user and pretty easy to use / configure

Sure there are some that meet your needs.

I only know one company - blue web software - which i and my friend created but have not worked on in a while - as we are workng too hard.

And it may well be those two dear friends clouding my judgement right now but isn't this thread all about mixing our metaphors?

What's open source got to do with ITIL? I know you've got to offer some kind of alternative product, but why? Whether you develop in-house or pay a bucket load in consultancy configuration of an esablished product, you're still going to heamorrage cash.

'Open source' has become the byword for 'healthy honest software' but in this case it's only going to be as good as the processes you've devised on paper. Just like any closed-source products.