1) Are you starting with a tool, or have you already defined your configuration management process?
2) what other process tools does it tie into?
- Incident Management
- Change Management
3) Do you have to manually enter everything or is there way of "autodiscovering CIs? You need to verify and audit the data if you have a proper Configuration Management process in place? How are you going to accomplish these activities?
In my mind, configuration management is the glue that holds all the processes together. It does not provide any quick visible wins to the business but it very important base for all other processes. I don't think the tool should drive the process and if you are starting with a tool, you might find yourself limited in the future.
I know I didn't really answer the question, and hopefully you have thought about the process before the tool.
Joined: Jan 01, 2006 Posts: 500 Location: New Jersey
Posted: Wed Sep 05, 2007 9:39 pm Post subject:
The $2/CI is their cost model. They charge by the database CI record. If you're a small firm, you will most likly enter and manage fewer CIs than a larger firm.
My gut feeling tells me that it's a single user system, like OneCMDB, which means you can't license the product by users/people, so they had to find another alternative to scale price according to size of the enterprise. It looks like they did this by having a cost model that charges by the quantity of records in the database.
I hope this helps.
Frank Guerino, CEO
On-Demand ITIL Platform
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum