I am new to Configuration Management and looking for guidance and help. I am attempting to create CMDB process for applications that are currently in use at an organisation. I am also creating a template that would help capture CI details and am loking for some help in this regards

some question I have are:

1) at application level what CI attributes needs to be captured for an application- I know the depth upto which I want to capture detail is decision the Configuration Manager need to take, but at high level what attributes get captured for applications.

2) Since application reside on hardware should I also capture hardware details in the tracker or tracking dependencies of only application is ok?
Exp: Application ABCD depends On Server XXXXX

3) what would be relationship type for application CI?
I can think of
Connects To
Depends On
Fails Over To
Part of
Peer
Uses

Your CMDB exists to support your service management function, so you need to determine what information you need to run your service management function, and naturally the relationships between these.
Generally speaking however I would advise the following:-

1. Start small and expand.
2. You should only add things that are controlled by change management.
3. Audit audit audit.

1a) put nothing in the CMDB for which you have not defined a use and identified at least one user and an owner._________________"Method goes far to prevent trouble in business: for it makes the task easy, hinders confusion, saves abundance of time, and instructs those that have business depending, both what to do and what to hope."
William Penn 1644-1718

you need policies too.
I also am new to the wonderful world of configuration management so I'm finding this thread interesting although I don't have much to contribute as yet.
However I haven't seen ownership mentioned.
In the process of determning CIs and relationships, the following questions kept coming up for us....
What is it?
Where is it?
How critical is it (i.e. how much pain will be suffered if it is not available)?
Who and what uses it?
What are the dependencies?
Who is responsible for it (ie who is standing in front of the fan?)
Who needs to approve changes and/or planned outages
Who needs to be told?
Please bear in mind that this is the perspective of a configuration management noob_________________DYbeach
ITIL V3 Release, Control & Validation,
ITIL V3 Operation SUpport & Analysis
PMI CAPM (R)

"In times of universal deceit, telling the truth will be a revolutionary act." George Orwell

I don't go to all the bother of thinking up these difficult ideas just to be ignored.

Just cos your lot got to the World Cup finals!_________________"Method goes far to prevent trouble in business: for it makes the task easy, hinders confusion, saves abundance of time, and instructs those that have business depending, both what to do and what to hope."
William Penn 1644-1718

I said "finals" not "Final" I assume you are either a dyed in the wool [hope that's not too clever for everyone] Australian or somewhat adopted to that country.

If you have been watching the games, I hope you have better commentary teams than the English provide._________________"Method goes far to prevent trouble in business: for it makes the task easy, hinders confusion, saves abundance of time, and instructs those that have business depending, both what to do and what to hope."
William Penn 1644-1718