Applying DISCO labels to Model Map

Applying DISCO labels to Model Map

I  would like to apply the DISCO-methodology to the Model Map. The most efficient way would be to label the Functional Areas to the DISCO. 

The model map could then be visually sequenced based on the DISCO steps:


This could improve the value of the model map, because it shows the data flow more clearly. Also, it enables the modellers to model better in accordance with DISCO. 

The content in this article has not been evaluated for all Anaplan implementations and may not be recommended for your specific situation.
Please consult your internal administrators prior to applying any of the ideas or steps in this article.
Community Boss


You can do this now

Functional areas are editable by the end user and then you can apply them to the modules


Occasional Contributor

Hi David,


What Jeroen & I are getting is slightly different.

1: Next to the functional areas it would be great to group the functional areas in a DISCO grouping.This would make it possible for the model to visually mimic the DISCO view (sequentially ordered from D to O) as we see that the ordering is now sometimes very much oriented towards the relations while we want the data flow to become more clear and thereby adding more value to a Model Map

So in conclusion: yes we can already apply the DISCO to the naming of functional areas, but it would be really nice if the model map would follow suit based on this DISCO naming!

Community Boss


Yep totally agree with that - I see DISCO as sub functional areas and I have asked to have a module "type" to follow DISCO and having that on the model map would be great

One thing to add is that the model map is automatically generated, but if you build as advocated in DISCO, without subsidiary views, generally the flow is clearer

Thanks for promoting DISCO!


Community Manager
Status changed to: Needs Community Support

I would like to see this implemented

Community Manager
Status changed to: Under Investigation
Community Manager
Status changed to: Considered for Future Roadmap