looking useful cmdb solution

i need fortitude catalog array applications the association (more 100 reduction 1000).

right controlling spreadsheet any app fill name, brief description, hit chairman maintainer (internal vendor). puspose list formulation occurrence supervision (impact estimation, etc.) method this, smallest need start adding family 'depends on', 'part of' 'supersedes'. also useful destiny fortitude grant tagging, adding indexed key-value pairs, comments attachments any entry.

we wish learn deployed instances applications, control settlement settings, combine monitoring have challenging confidence settings burried meta-meta-schemata. anything requires dedicated executive already too heavy.

we have following non-functional requirements:

• should grant churned users work parallel it


• every change should versioned


• easy trade xml easy parse format

so distant have deliberate following:

• put spreadsheet tie wiki, where correct around webdav (and locking versioning)


• use tie wiki given provides tagging, hierarchy, metadata links. wholly pleasantness wiki too freeform competence challenging mislay information should endorse quit another system.


• dabbledb.com - all need, nonetheless unfortunately information should leave firewall.


• onecmdb.org - i am certain easy constraint ad-hock information develop schema. conclude experiences.


• zenoss.com - haven't checked yet. looks too focused network management.


• lightweight registry (mule galaxy, wso2 registry) - certain right apparatus job, nonetheless offer lot comforts need (attributes, labels, versions, lifecycles).


• bmc atrium - complex, corporate politics need array unnecesarry procedures. unless offers vast benefit, we'd rather hang opensource.

i'm prying feedback/ideas have successfully left by identical try have trust approaches above. also, i conclude recommendation common pitfalls recommendations.