I don't have access to the v3 documents (except the summary), but surely the chapter/section/sub headings would form the framework for a gap analysis?_________________"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

The bulletpoints in your GAP analysis is pretty much decided from how your current service architecture is (or not) working and how that differs from how you want it to work. It is not a static list of bullet points.

The bulletpoints in your GAP analysis is pretty much decided from how your current service architecture is (or not) working and how that differs from how you want it to work. It is not a static list of bullet points.

You have it the wrong way round. The bullet points are derived from how you want it to work (e.g. the ITIL books). In a gap analysis you are trying to find out what parts are not working or missing in your current service architecture._________________"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 have it the wrong way round. The bullet points are derived from how you want it to work (e.g. the ITIL books). In a gap analysis you are trying to find out what parts are not working or missing in your current service architecture.

I see your point but I meant the same thing; the only difference is the direction of the GAPs

Here, I have moved a further and drafted the TO - BE Service architecture document for the customer. In this I have selected each module of the v3 and tried to balance it with the customer requirements.

Moving ahead, I now need to create another detailed document which will describe how exactly every module of V3 will operate in the customer premises, takng into consideration the operational and busioness aspects of the customer.

Here I seek a gidance in determining the level of the detailings I should go in for each V3 module(IM,PM,RM, etc...). Must it so detailed as to helpa implementer to customise the Remedy/HP service Desk etc ?

Have anyone created such document which describes in detail the service design for a specific engagement / cusotmer?

I'm not sure what kind of advice will be useful to you here. The level of detail is what is required to ensure the good working of the processes. This is largely a function of the nature of the people and the environment in which the processes take place.

So, inexpert staff, high staff turnover and complexity of the operations all affect how much detail are required.

The very minimum is the expression of policy and objectives in all procedures and this includes criteria for decision making and authority.

The very maximum of detail is to stop short of damaging efficiency by swamping staff with too much.

I don't see how to be specific about your case without analysing the specific circumstances.

You say that you need to create a document, but you do not say what the purpose of the document is. Reflect on the purpose and consider the circumstances and the required level of detail should begin to emerge.

You ask if it should be sufficient to instruct/guide an implementer. - Is that part of its purpose? Or will there be other documents for that purpose?_________________"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

Yep I think a bit of decent consultancy would be useful seeing as this piece of work is taking so long to develop.

UJ

I can start tomorrow!_________________"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

The detailed Target Service Architecture Document will let the customer see hpw the various processes (IM/PM/CM/RM) will be functioning / operating in his business and operational environment.

So, these V3 process detailing in this document must be so deep so as to allow customer to see that "OKAY this is the way all the incients in my Org will flow end to end".

Now, after I am able to make customer happy seeing this doc, the next objective is to transalate those process workflows into technicalities(e.g. How the C T I will be created, Hpw the CMDB will be conceptualised and then populated on regular basis, how to derive the Esclation matrix for varuois suport tracks, How to assign the ratings to the CIs--- Threat + vulnerablity analysis, how this can be done, How the SLA will be confgured in tool[Remedy or HP Service Desk].................). So friends, do U think I need to mention all these technalities as mentioned within the round braces in my document.

It is ultimately your document and your responsibility/creidibility on the line for this document.

While you can ask us our opinion about major items / focus of the document set, none of us are part of your company nor have an idea of what your customer wants /expects.

Only you do .

I think you are being lazy in writing your document.

From what I can infer from your post, you are using the 5 ITIL v3 books - chapters/ heading /etc to produce your own document.

I think that instead... you should base this document - what ever its purpose - on what services you can actually provide to your customer and weigh that document against IT Operations - Incident, problem, change, config and release as well as IT Planning - etc

But .. as I said.. it is YOUR document

I can not tell / advise you what font to you, how to format the document, or what to puit in the document

I think you will find that my posts and that of UJ are pretty much in line with what John is saying, not that I can ever hope to have his facility with language in expressing myself.

The only way to answer your question further is to know everything about your circumstances and that cannot be achieved at the forum, nor is it reasonable to expect people to freely analyse your requirement to such depth as to provide a confident and useful answer._________________"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