Anaplan Technical documentation

ankulkarni
Contributor

Anaplan Technical documentation

Hello All,

Currently our team is new to Anaplan and thus have hired a vendor to build a solution for our company, the challenge is that there is no document in place which explains the technical and functional aspects of solution that has been built so far ( Model building/ user guide) 

 

can anyone help us with a template or document sample so that we can modify and ask our vendor to update it 

 

Objective:-1) Model builders ( Beginners) should be able to understand how the model was build and maintaining solutions if some challenge comes up

2) This document should help end user to understand the process (SOP Draft) 

Currently the vendor does not have any document in place 

 

Thank you 

1 ACCEPTED SOLUTION

Accepted Solutions
SMaddi
Occasional Contributor

Re: Anaplan Technical documentation

I am not sure if there is a formal documentation model that Anaplan suggests/recommends, however, in my past projects I have seen Documents explaining each Dashboard that's been built by the partner/vendor and modules/lists used underneath. And in general, what are limitations/assumptions used when build commenced.

Also, make sure you have the list of Data loads (Annual/Monthly/Weekly etc) and the dashboards where the Process are published for those data loads.

Hope this helps and you can ask your vendor accordingly that will help your team manage the models effectively.

 

Sunil.Maddi

View solution in original post

2 REPLIES 2
andrewtye
Master Anaplanner/Community Boss

Re: Anaplan Technical documentation

Personally I wouldn't pay the invoice to the vendor if they've not provided you with suitable user and technical documentation.

That being said they should have the ability to come up with a good enough document that works for you explaining how the modules, lists, etc all interlink

SMaddi
Occasional Contributor

Re: Anaplan Technical documentation

I am not sure if there is a formal documentation model that Anaplan suggests/recommends, however, in my past projects I have seen Documents explaining each Dashboard that's been built by the partner/vendor and modules/lists used underneath. And in general, what are limitations/assumptions used when build commenced.

Also, make sure you have the list of Data loads (Annual/Monthly/Weekly etc) and the dashboards where the Process are published for those data loads.

Hope this helps and you can ask your vendor accordingly that will help your team manage the models effectively.

 

Sunil.Maddi

View solution in original post