KT Template please

[Former Member]

Dear Gurus,

Our project is in a phase of trasistion. Its a fresh implementation ( Not roll out / migration ).

I just wanted to know during the KT transition phase what are all the information we need to get from the implementors to completly take over post implementation support.

If any KT docs will be appreciated.

Please forward the docs to mohan.kumar at hotmail.com

FYI......its a fresh BI 7.0 implementation.

Regards

Mohan

Edited by: Mohan Kumar on Jun 27, 2008 7:49 AM

[former_member345199 · Accepted solution]

Hi,

In our case we maintain KT documents for later reference as well as team handover purposes as in your case.

We maintain very detail level KT document for everything.

Every object, every routine, transformations, DS,Cube, ODS, etc have separate KT documents.

It basically contains data about the purpose, design, technical specifications, prerequisites, developer, version, data flow, etc about the object.

It contains an overall view of the object.

Each document is given a separate name based on certain naming conditions and stored in a DB like Lotus notes so that its easy to refer it later.

In your case you need to collect the design documents from the implementation team and compare it with the actual objects in the system. It should be identical, any changes should be recorded in detail and if it is not there you need to ask for explanation.

Also collect data about Scheduled activities in the system and see if they are recorded properly.

You should add these points for sure.

Make an Excel sheet with these columns

Technical Object, Business unit (which it belongs to), Source system, Region, Object Status, Development Spec in Synch with Actual production object, Design Document in Synch with Production object, Sign offs (approvals at each stage during development, testing and transportation) , Active / Inactive status for Object in Dev,Qual, Prod., Object is in Synch in Dev,Qual, Prod. , Person responsible for development.

In another word document maintain every detail for Every object, every routine, transformations, DS,Cube, ODS, etc

It should contain data about the purpose, design, technical specifications, prerequisites, developer, version, data flow, etc about the object.

It should contain the overall view of the object.

Remember you need to collect as much as data as possible during this phase as after handover you may be on your own.

Refer

Hope this helps.

Thanks,

JituK

[Former Member · Accepted solution]

Hi Jitu,

Thanks for tons of information.

Can you throw some light on "Scheduled activities in the system".

Need some more clarity on this.

Also can you please send across the KT docs if you have any pertaining to any project to my ID mohan.kumar at hotmail.com.

Appreciate with tons of points if you could send the KT docs across....

Regards

Mohan

[Former Member · Accepted solution]

Hi Jitu,

No probs..thanks a lot...assigned points.

Closing the thread.

Regards

Mohan

[former_member345199 · Accepted solution]

Hi,

Scheduled activities in the system can be mainly of two types. One is application wise and two is maintenance wise.

Application wise you need to consider scheduled jobs, or chains on a daily, weekly , monthly or adhoc basis.

Also other activities like open hubs etc should be understood well.

Also find out the transport frequency. It may be once or twice a week on a particular day (weekends generally).

Second is Scheduled maintenance activities like Monthly maintenance windows, back up plans, DB2 reorgs etc. This mostly comes into Basis purview.

You can very well go ahead and create a excel document with the points I mentioned. Its the same one I am having.

One more point you can add is the point of contact for the business for each stream.

Hope this helps.

Thanks,

JituK

[Former Member]

Good information