IDAY38,
First, I like your key process diagram for CI. I assume the term "Key" also means "Major" and/or "Customer Oriented Process" (COP).
"My auditor suggested this approach of writing the major processes than with the sub processes underneath. He said this would help him when he audits."
Sounds like consulting to me, which we all know is a "no-no". Request that your auditor make his suggestions in writing; either with an NCR or an opportunity. That way when you go back to management with changes you don't have to play "He said - She said".
"However, I dont see how this shows the resposnibilities and the real interaction is in the subprocesses. I invite feedback on the interaction and sequence and my auditors comments."
Your company is not doing this to make it easy for the auditor. The requirement is that you define your processes, either tabular, or graphical. Whatever works for your company. Manoj has posted some very good documentation prepared in the tabular format. Other people have posted flow charts. What ever work for YOU not your auditor.
"Another thing , I had downloaded form AIAG a tool for identifing the processes, on that do I put down the major or sub."
This is a good tool, if your just starting. If you already have your COP's identified and the activities and support processes that cause them to function; DO NOT USE THIS TOOL. If your program is in the "infant" stages, then I would suggest that you USE THIS TOOL.
Start with your Key/Major/COP. As you proceed you will list activities/support processes and in the end you should also see your interactions.
"I am so confused. I am reading and researchien and everybodies opinion, throwing me in a state of mess."
We all are confused. And do you know who is even more confused? The OEM's and the registrars.