Sriram,
It depends on the project. Generally, it covers where is the client now, and what is the proposed solution you will be offering him. There is no 'right' answer to your question. 20 consultants will give you 20 different answers.
Level of detail varies between consulting companies and clients. It can be a 2 page overview, it can be a 100 page detailed analysis, and it can be anything inbetween.
The client may be starting with no Demand planning, legacy demand planning, some SAP ERP demand planning, or some existing APO demand planning that he wishes to enhance. During requirements gathering by the consulting company, the project team will document where the client stands now. Since I am pretty lazy, I don't usually spend a lot of effort on this portion of the document. In some cases, the consulting company will require the client to contribute to the As Is.
Once the consultant has fully researched what the client wishes to achieve from a business perspective, they then use their expert knowledge of APO DP to conceive of a comprehensive solution that will meet the client's requirements. Again, this could be a very general solution overview, very early in the project, or it may be rather detailed, if the client so requires. This doc is often produced before the prototype system, but sometimes after prototyping but before creating the initial attempt at a full solution in the Dev client.
Since you are new to DP, the task of creating the AI/TB doc will probably not be assigned to you directly, but more likely to a senior member of the team. Typically, the production of this doc is a milestone that requires some form of sign-off before proceeding. Talk to your team lead about what your company expects of you in this doc.
Rgds,
DB49
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.