Pacific Northwest User Group Tableau Hosted Virtual Meetup

Pacific Northwest User Group Tableau Hosted Virtual Meetup March 19, 2020

The Pitch • What if you had a built-in checklist covering the most important structural elements to consider, when building an Anaplan model, that you and all other model builders were tasked to review? • What if you had a guide for the most critical Anaplan best practices, helping you understand which features to leverage and which design decisions to avoid? • What if the most useful Anaplan administrative tools and helpers were pre-built into your model? • What if you started your model build with a foundational naming convention, rather than creating one on-the-fly between multiple model builders? • What if during the model handoff process, you could open an Anaplan model, built by another person, and know the exact location of every import/export module, every subset definition, every list item creation/deletion action, and module input reset line item? What if you could start every Anaplan build with all of these benefits?

Tableau & Salesforce’s new approach to Anaplan: Anaplan Foundation Model Matthew Kuo | mkuo@tableau. com Anaplan App Marketplace March 19, 2020 “Improve Model Longevity” “Promote Best Practices” “Enhance Build Efficiency”

Agenda • Project Background, Approach, & Key Principles • Caveats & Documentation • AFM Setup & Structure • Best Practices & Features to Avoid • Module Details by Grouping • Feedback Process • Thank You & Pay it Forward

My Background Matthew Kuo - Anaplan user since 2013 Led 20+ Anaplan deployments, with focus in Sales Operations Americas Partner Award, Excellence in Sales – 2015 Americas Partner Award, Best App – 2016 Joined Tableau in 2017 – Anaplan Solution Manager Master Anaplanner Certification – 2018 linkedin. com/in/matkuo/

Project Background • Tableau and Salesforce are two of Anaplan’s longest standing customers • Both companies have faced the situation where an Anaplan use case was deprecated simply because the original builder of that use case left the firm • This outcome was deemed unacceptable • To improve our model sustainability and longevity, we realized that we needed to: - Drive better consistency across our existing use cases, in terms of structure and naming conventions - Make our models more transparent, easier to audit, and easier to hand off to future owners - Promote best practices within our existing footprint and ensure that this knowledge is leveraged for all future deployments At Tableau and Salesforce, we realized that we could significantly improve model longevity by having a company specific Anaplan template

Project Approach • Build an Anaplan template representative of the use cases leveraged at Tableau and Salesforce • Begin migrating our Anaplan use cases towards the template’s format and structure • • - For existing deployments, AFM will be referenced for all of our use case refresh projects - For new deployments, we will tweak and leverage AFM accordingly Release the template as a free, downloadable Anaplan App - Obtain feedback from the community - Enlist Anaplan Partners to assist with the feedback and testing process Continue updating and improving the template over time - Promote current best practices and establish new ones - Update and/or remove AFM elements as the New UX expands

Template Features • The Anaplan Foundation Model is a free, downloadable template, designed intentionally to be simple and free from bloat • All customized aspects of the Anaplan Foundation Model can be quickly removed or deleted - Model size less than 5 MB total - Only 1 module with a list dimension - Only 1 list that is actually populated - Only 2 populated dashboards - Time and Versions left on default settings - Required Organization list has been left alone, to be integrated by the user Anaplan customers should be confident in using AFM as the foundation of a new build or as the starting point for their own company template

Improve Model Longevity • Model Longevity is the core principle of the Anaplan Foundation Model • The primary reason that an Anaplan use case is discontinued is because of a lack of transparency - The original model builders did not invest sufficient time to produce valuable documentation - The model was designed as a black box – embedded with so much unnecessary complexity that future model owners are unable to ramp up to it • The Anaplan Foundation Model encourages you to highlight the most complex aspects of an Anaplan model, making it more transparent and easier to transfer to another person • The turnover rate in Corporate America is around 40% – no Anaplan use case will be managed by one person forever If your Anaplan model cannot survive a handoff, your deployment is destined for failure

Promote Best Practices • A number of factors make best practices inconsistent within Anaplan’s customer base: - Historically, many Anaplan users have become proficient in Anaplan without taking a single training - Certain best practices are not intuitive based on Anaplan’s setup and structure - Best practices change over time and the ideal approach can vary from use case to use case • While trainings, community forums, and online documentation are the gold standard of best practice documentation, not every Anaplan user frequents these mediums • When faced with pressure and deadlines, many Anaplan users will seek to build a model quickly and not invest the time to seek out additional guidance Using a template serves as an additional means of promoting and enforcing best practices within your organization

Enhance Build Efficiency • Most of us understand that building a model with internal documentation, good formatting, and logical organization are drivers to long term success • However, pursuing these activities can take a significant amount of time, especially if you are building a model from scratch • Examples include: - Adding “No Data” formatted “Heading 1 Style” header sections in your modules to better organize your line items - Separating counters, filters, and conditional formatting line items from core calculations within your module - Creating a detailed background section with all relevant contact information and documentation links - Building an administration dashboard covering all critical elements of your model Using a template lets you streamline certain elements of the build while encouraging good habits for newer model builders

Agenda • Project Background, Approach, & Key Principles • Caveats & Documentation • AFM Setup & Structure • Best Practices & Features to Avoid • Module Details by Grouping • Feedback Process • Thank You & Pay it Forward

AFM Caveats • • All included module groupings/naming conventions/model admin features/dashboards are suggestions for consideration, NOT absolute requirements - There are no models at Tableau or Salesforce that match AFM’s structure exactly - The template is intended to help you think about what you might need, but NOT force you to include anything - In its base format, any module or list within AFM can be easily to deleted While you should leverage AFM initially, the actual template that you use at your company should be customized for your own needs - One of the biggest drivers of model longevity is quite simply – whether or not you can you hand off your Anaplan model to another person at your company - Having a company template will help significantly with this factor

AFM Caveats • • Many of AFM’s features and customizations will be made obsolete once Anaplan’s New UX expands to Anaplan’s model building interface - Unfortunately, the actual timing for the New UX’s full expansion is still unclear - Look for this indicator for AFM features that are likely to become obsolete New UX will make this unnecessary Data Hubs - Data Hubs are a specific type of Anaplan model, intentionally designed to be simple and stable - Some elements of AFM are useful for Data Hubs while others are not – which elements fall into which category can vary by use case - Therefore, you can leverage AFM for a Data Hub model if so desired – just expect to delete a lot more foundational elements - For further guidance on Data Hubs specifically, please review the link below: - https: //community. anaplan. com/t 5/Best-Practices/Data-Hubs-Purpose-and-Peak-Performance/ta-p/48866

AFM Download The Anaplan App Hub is currently undergoing a redesign and upgrade; until that process has finished, the AFM Model can be downloaded through a specific URL 1. Click on the link below to begin the download - https: //sdp. anaplan. com/launchpad/nonpublic/App. Install. Wo rkspace. Redirect. action? appstore. App. Guid=8 a 81 b 013706 ef 3460170 ee 8 b 26 af 391 b 2. Select your Customer / Tenant 3. Select your Workspace 4. Model will save with the following name:

AFM Documentation • Link to Download AFM Documentation Deck & AFM User Access Template v 1. 0 - https: //community. anaplan. com/t 5/Anaplan-Platform/Anaplan-Foundation-Model/td-p/63452

Agenda • Project Background, Approach, & Key Principles • Caveats & Documentation • AFM Setup & Structure • Best Practices & Features to Avoid • Module Details by Grouping • Feedback Process • Thank You & Pay it Forward

Model Index • The Anaplan Foundation Model’s default landing dashboard is a Model Index, or a “dashboard of dashboards” • This view is primarily useful for model administrators to understand the full scope of their model - For users that only need access to a single dashboard, or a small subset of dashboards, a different landing dashboard would likely be more appropriate • Creating a Model Index is a very time consuming and clunky process – if you utilize AFM, you can simply leverage the dashboards/buttons that you need and delete the ones that you don’t • The New Anaplan UX will hopefully make this process obsolete New UX will make this unnecessary

Lists • • The lists of the Anaplan Foundation Model are intentionally light in both detail and structure - With the exception of “Time Zones”, all lists are just blank placeholders - With the exception of “Time Zones”, all lists have NOT been applied to any modules and therefore, all lists (with the exception of “Organization”) can be easily deleted - The Organization list is required component of all Anaplan models and has not been touched The simplicity of the list setup should give you the confidence to leverage the Anaplan Foundation Model, knowing that you will not be hindered by unwanted or unknown legacy items

Naming Conventions • Naming conventions are an aesthetic part of your Anaplan model that can have a significant impact on both transparency and overall ease of use • With the base AFM template, a couple of key characteristics include: - Module function/grouping designated in all caps - “ – “ used between module grouping and name for readability - No underscores used as Anaplan’s formula writing rules don’t care about spaces between words - Parentheses are used to indicate where you should put in your own custom values (ex: “DELETE – (List Name 1)” could become “DELETE – Partner Accounts”) - Lists identified with hierarchy level indicator prefix (ex: A 1 – Direct Accounts) - For hierarchal lists, smaller numbers are used for higher levels of the hierarchy – the preferred sort order will obviously vary from customer to customer

Naming Conventions (continued) • • It is not possible for one naming convention approach to work across every Anaplan client or use case; naming conventions can and will vary significantly based on: - Use Case - Industry - Connected Source Systems - Required Output Formats - Any unique complexity within your model Use the naming conventions of AFM as a starting point, but take the time to develop one that works best for your organization and use case - Naming conventions are only valuable if they are used consistently - Naming conventions are much easier to maintain when you have a company template to reference or work off of

Period Dividers • Period Dividers are simple placeholder modules that make it easier for you to read, identify, navigate, and work with your modules and lists • To create a Period Divider, simply create a module with no dimensions applied to it and name it as two periods with spaces in between the periods - “. . “ - Vary the number of spaces in between the periods to give each Period Divider a unique name - The module name will always still appear as if it only has one space in between the periods New UX will make this unnecessary

User Access by Role & Module / List • One additional benefit of using period dividers is that it can make adjusting the User Access by Role and Module/List table significantly easier, particularly if you utilize the AFM – User Access Template formatting - • https: //community. anaplan. com/t 5/Anaplan-Platform/Anaplan. Foundation-Model/m-p/63452 To leverage the User Access template: - Copy your entire User Access by Role and Module/List Table, inclusive of the module names - Paste the data you copied into the appropriate tab within the AFM User Access Template Excel file – the conditional formatting will update automatically - Make your user access edits within the template - Once your are finished, you can copy the input values (just the Read, Write, None, TRUE, and FALSE cells) and paste them back into the User Access by Role and Module/List Table New UX will make this unnecessary

Numbering & Module Groupings • The ideal way to number, group, organize, and name your modules will vary depending on your specific use case • For use cases I’ve worked on, “Module Group” has generally been the right level of detail for numbering • - Numbering individual modules generally gets complicated and difficult to manage – when your module count gets to a certain level, the numbers stop carrying any meaning - Section names are in lower case, to further differentiate them from the “all-caps” module prefixes for other module functions - Section Modules are “No Data” modules, just like period dividers - If a particular section of the AFM template is not relevant to your use case, delete it from your model and update your numbering accordingly As always, the format used in AFM is a suggestion – use the appropriate module numbering/grouping approach for your own particular use case New UX will make this unnecessary

Agenda • Project Background, Approach, & Key Principles • Caveats & Documentation • AFM Setup & Structure • Best Practices & Features to Avoid • Module Details by Grouping • Feedback Process • Thank You & Pay it Forward

Suggested Best Practices • • One of the best guides for Anaplan Best Practices is the PLANUAL: - https: //community. anaplan. com/t 5/Best-Practices/The. Planual/ta-p/49773 - I’ve noted some of the key best practices below, but the PLANUAL is definitive source on best practices and a must read for Anaplan model builders Model Size - Exclude Time Subtotals by Default (1. 01 -05) - Use Booleans rather than numbers where possible, as they take up 1/8 th of the space (2. 02 -07) - Turn off Summary options by default (2. 03 -01) - Ensure Headers are set to No Data (2. 03 -03) • Model Performance - AVOID – Nested IF statements (2. 02 -01) - DO NOT USE – SUM and LOOKUP together (2. 02 -08) - AVOID – TEXTLIST (2. 02 -11) - For IF Statements, have the most common condition occur first in the logic statement (2. 02 -17) - Break long formulas into separate Line Items where possible (2. 02 -18) - AVOID – RANK & RANKCUMULATE (2. 02 -20) - AVOID – TEXT as a format, where possible (2. 03 -02)

Suggested Best Practices • Model Sustainability - DO NOT USE – SELECT with TIME (1. 01 -01) - AVOID – List Properties (1. 05 -03) - AVOID – Subsidiary Views (2. 01 -12) - AVOID – Versions (built-in functionality)

AVOID – List Properties • It is an Anaplan best practice NOT to use List Properties - List Properties do not have the same formula editing/auditing interfaces as module line items - List Properties are less transparent and take the end user longer to audit - https: //community. anaplan. com/t 5/Best-Practices/The-Planual/ta-p/49773 - Section: 1. 05 -03 • If you completed your Anaplan training years ago, or just started building a model without Anaplan training, this will not be an intuitive best practice; Anaplan was originally designed with list properties in mind • The alternative to List Properties are List Attribute modules, which will be discussed in a later section No point-andclick formula editor No “Show History” on right-click

AVOID – Subsidiary Views • Subsidiary views are a way to adjust the dimensionality of a module, but only for specific line items - • Instead of one dimensionality setting, your module can have multiple The key problems with subsidiary views are: - If used extensively, subsidiary views make your model significantly harder to audit - When using the basic formula editor, Anaplan does not indicate whether or not the line item you’ve referenced is dimensioned against a subsidiary view – this can cause errors when writing formulas, after you’ve become accommodated with a module’s dimensionality, but get surprised by one line item’s subsidiary view - Import actions that reference a module cannot read subsidiary view line items – you’ll have to build a new module using just the subsidiary view’s dimensionality settings • However, Subsidiary Views can be helpful in reducing module size • Use at your discretion – try not to have too many subsidiary view line items in any given module - When you reach a certain threshold, just create a new module with the desired dimensionality setup

AVOID – Versions (built-in functionality) • Versions is easily one of the most powerful, popular, and useful features that Anaplan has to offer - • Certain Anaplan formulas, such as “ISCURRENTVERSION”, were created specifically to work with Versions When we make Model Longevity our top priority, one of the problems with Versions is: - It is very rare to have a model with Versions applicable to EVERY SINGLE module – for the vast majority of use cases, the built-in “Versions” dimension is only applicable to a subset of your modules - If you have Versions enabled, over time and with multiple builders, you will undoubtedly apply Versions to more modules than necessary; this will increase your model size, make your model more complex and more difficult to audit - Having maintained and audited a 6 year old Anaplan model, it was not uncommon to find several modules that didn’t need Versions but had that dimensionality applied to them • This guidance represents my personal opinion – on the Anaplan forums there is a healthy debate regarding whether or not you should use Anaplan’s built-in Versions functionality • If you do absolutely want to leverage Versions, just make sure you can justify its use – don’t start your Anaplan model assuming that you absolutely need it

ALTERNATIVE – Versioning Lists • • • A simple alternative to using Anaplan’s built-in Versions functionality is to create your own “Versioning” lists - Common examples include “Import Data Version”, “Forecast Version”, and “Ramp Scenario” - You and your fellow model builders will be much less likely to apply a well defined Versioning List to a module that does not need it during the initial build - Your model also becomes more transparent – the names of your Versioning Lists give direction regarding where and how they should be applied for future model owners A handful of Anaplan features related to Versions will no longer be useful, including: - Anaplan’s built-in formulas that specifically reference Versions - Designation of a Current Version and Switchover between Versions - Certain interface options/benefits (i. e. the Versions column will always say “Not Applicable”) If you stop using the built-in Versions functionality, but still want these features, you’ll have to build manual workarounds to accommodate the loss of functionality

Agenda • Project Background, Approach, & Key Principles • Caveats & Documentation • AFM Setup & Structure • Best Practices & Features to Avoid • Module Details by Grouping • Feedback Process • Thank You & Pay it Forward

AFM Module Groupings 3 6 List Item Creation List Item Selectors 1 Import Modules 7 4 12 Summary / Reporting User Input 10 15 Model Admin 13 Mapping / Assumption Tables List Item Deletion List Attributes 2 9 Export Modules Official Data 16 Trash 5 8 List Subsets 11 Module Input Reset 14 Calculation Engine Error Checking

AFM Module Groupings Data Inputs System 3 1 Import Modules 2 User Input List Item Creation Mapping / Assumption Tables 5 15 11 13 Calculation Engine 16 Trash 8 List Subsets Summary / Reporting Model Admin List Item Deletion List Attributes Outputs 12 7 4 10 Official Data 6 List Item Selectors 9 Calculations Module Input Reset The AFM Module Groupings are essentially a more detailed version of DISCO Use the grouping and ordering that works best for your organization Export Modules 14 Error Checking

Import & Official Data Modules • • • The Import & Official Data modules serve the very important purpose of housing all of the data that enters your model The secondary Official Data modules are intended to allow for any transformations and adjustments that need to be made, immediately after the data has been imported - If you need to store multiple versions of your import data, consider Versioning your Import Module and having only the official/current version flow through to the Official Data module - If your use case has multiple model builders, the Official Data modules serve as a good reference point so that everyone knows which set of data should flow through to the rest of the model For many use cases, data is imported from an Anaplan Data Hub model - In these situations, it’s likely that the transformations and adjustments performed by the Official Data modules have already occurred - For models sourcing information from a Data Hub, you should evaluate the overall setup to determine whether or not a secondary Official Data section is beneficial or can be removed 1 Import Modules 2 Official Data

List Item Selectors • List Item Selectors are simple modules with data validated input cells, that allow you to pick an input value delimited by the items available within that particular list format – examples include: - Selecting a Version of the Top Down Target data that you want to flow through to the rest of the model - Selecting a Rep when you want a detailed view of their accounts in a the subsequent reporting module • Only leverage these when a Page Selector will not work or would not be efficient to build • Generally, you will have lookup formulas that reference the selector input cell to display data based on the selected value - ex: if the Selector says Rep A, show Rep A’s accounts New UX will make parts of this unnecessary 3 List Item Selectors

List Attributes • An Anaplan best practice is NOT to use List Properties • List Attributes are a simple, module-based replacement for the majority of your List Properties • - Instead of using List Properties, dimension a List Attributes module by ONLY the list in question - Add line items to the module – these “attributes” are the replacement for “properties” List Properties do still need to exist in your Anaplan model to support List Subset identifiers and Numbered List display names, and are required if you want to utilize the “list dependent drop down” feature 4 List Attributes 5 List Subsets

List Subsets • List Subsets are technically defined by a hardcoded input Boolean within a List’s settings • List Subsets by default lack transparency – while you have a definitive input indicator of what is in and not in the subset, you don’t necessarily know how it’s inclusion into the subset was determined • For any subsets you define and need to update within your model: - Build the definition of those subsets into a separate module - Typically, you’d set an import action into the Subset indicator within the list, to actually define the subset • That way, whenever you want to understand why a list item has been included in a subset, you can just quickly reference the corresponding LIST SUBSET module • List Subset definitions are one of the most common causes of errors within Anaplan – having separate modules for their definition makes them significantly easier to audit 4 List Attributes 5 List Subsets

List Item Creation & Deletion • • List Item Creation and Deletion are critical functions within your Anaplan model, as they have the potential to drastically change your overall model structure and size List Item Creation and Deletion are common functions that can serve many purposes: - Adding “child” list items under a “parent” list to establish a hierarchy and relationship (ex: with Rep as the “parent”, add Account as the “child” to establish Rep Account) - Re-parenting list items based on specific criteria (ex: Account “xyz” is now the child of Rep “abc”, because that rep is the new owner) - Appending list items based on certain criteria (ex: add Account to Active Account list if Revenue > 0) - List Item Deletion serves a very similar purpose, within the same context, except you are removing list items • The List Item Creation and Deletion modules are intended to house all of the specific formulas and filters that your import/delete actions will run off of • List item creation/deletion actions have a high potential of becoming critical points of failure – make their definitions as prominent, transparent, and easy to audit as possible 6 List Item Creation 7 List Item Deletion

Module Input Reset • For some Anaplan use cases, typically those that are re-released on an annual cadence, you’ll need to periodically reset your inputs • The Module Input Reset section serves the simple purpose of housing those specific reset line items - You can either hardcode “ 0” and “BLANK” values, or have those values locked in by setting “ 0” and “BLANK” as the formula - You should also consider building an import action to automate the reset process • Having these particular inputs and modules called out helps from the perspective of model transparency and performing model hand-offs • If this functionality is not relevant to your use case, you should remove this section 8 Module Input Reset

User Input, Mapping Tables, and Calc Engine • User Inputs, Mapping Tables, and Calculation Engines are the primary elements that we traditionally associate with model building • Isolate all of your user input locations to designated modules; also, consider having different modules for different user types – this makes locking down the model and checking for user changes a much simpler process • • Your mapping tables are the lookup tables utilized by the rest of the model - Any critical and far-reaching assumption inputs should be stored here - List Attributes, described previously, have a function very similar to mapping tables with the caveat they are only dimensioned by one List - You’ll need to decide how you want to organize your model’s assumptions (i. e. use both List Attributes and Mapping Tables as separate sections or use Mapping Tables only to account for both situations) For complex use cases, the calculation engine modules will likely become either the most complex or largest set of modules in your model - You may need to break this out beyond just the simple “CALC” prefix 9 User Input 10 Mapping / Assumption Tables 11 Calculation Engine

Reporting, Export, & Error Checking • • • Reporting, Exporting, and Error Checking are all similar functions that generally occur after all inputs and calculations have been completed Most Anaplan model builders will group all of these functions into the same set of modules and potentially differentiate them with Saved Views – there is nothing fundamentally wrong with this approach You should just consider breaking them out into different sections if any of the following apply to your use case: - You require exports or error checking either on a different dimensionality or upstream relative to your reporting modules - You have one requirement (ex: reporting) that will change regularly and another requirement (ex: exporting) that will remain relatively fixed – separating these functions from a module perspective reduces the risk of unintentional changes across requirements - You want Error Checking displayed more prominently in your model so that your model builders understand its importance and know to reference it frequently 12 Summary / Reporting 13 Export Modules 14 Error Checking

User Notifications • For some Anaplan Use Cases, it is useful to have a user notification message at the top of the landing dashboard • User Notifications are ideal for situations where you need your users to be “on the lookout” for something - Your users still need access to the model, but something may be off - For more critical situations, consider just locking your users out or sending them an email/instant message • By default the cell is white – you can check a box to highlight it either green or red • All of these input settings are published to Dashboard MA 1 – User Notifications, Restore Point, and Background Info 15 Model Admin

Restore Point • The ADMIN – Restore Point module is a simple administrative tool that allows you to create a model change history reference point, right before making a significant model change • Using this module allows you to more easily restore your Anaplan model to the reference point in question, after the model change has occurred • Leveraging this approach prevents situations where you’re not sure which restore point to choose, between two consecutive change IDs • Be sure to give your restore point an easily recognizable and searchable name 15 Model Admin

Background & Contact Info • The ADMIN – Background & Contact Info module stores relevant context and links • The module is published at the top of the Model Index dashboard, for prominent visibility and easy access • Consider housing all of the images you’ve published to dashboards on a single internal wiki URL and include it in the Model Images Location field; sometimes images don’t display on Anaplan dashboards due to firewall issues – that way, if someone has access to that Model Images Location, they should also be able to see all of the Anaplan dashboard images rendered • Having a specific LAN folder for all Import and Export files will help prevent data versioning issues outside of Anaplan 15 Model Admin

Anaplan Support • The ADMIN – Anaplan Support module houses contact information and links for key Anaplan Support resources • The module is published at the bottom of the Model Index dashboard • Consider adding your contacts for Sales & Licensing, Customer Success, and Hypercare if they are relevant to your use case 15 Model Admin

Button Symbols • The ADMIN – Button Symbols module is a simple resource that provides you text symbols to copy into your process names - These should only be used for the purposes of visually enhancing process buttons, published to dashboards, that are NOT linked to any data integration scripts - Do NOT use symbols within the names of any actions that are used in data integration scripts, as they may not be read properly • Having symbols makes your interface more intuitive for the end user when you publish them as buttons on your dashboards • Using symbols technically goes against Anaplan best practices New UX will make parts of this unnecessary 15 Model Admin

Legend • The ADMIN – Legend module is a simple, color highlighted module that you can leverage as your model legend for cells displayed on dashboards • Placeholders for common value types have been added • Avoid using the darkest colors on Anaplan’s color scale, as these can obscure input values 15 Model Admin

Time Zones • The ADMIN – Time Zones module is a simple data table that shows you all time zone differences relative to UTC • All change history IDs are stamped with a UTC time • The sole purpose of this module is to help you figure out when exactly a change occurred when you are auditing the model’s change history • This is particularly helpful for global deployments involving multiple time zones • If the period you’re investigating is between March and November, remember to account for Daylight Savings Time (DST) by adding 1 hour when appropriate; not all countries recognize DST and the actual days it affects can vary 15 Model Admin

Module Formatting Template • New UX will make parts of this unnecessary 15 Model Admin The ADMIN – Module Formatting Template is a simple module with basic formatting intended to speed up the overall model building process - Many Anaplan models become less usable over time simply because model builders don’t invest time in formatting; this is literally the process of creating “No Data” formatted line item section headers and updating the Style to Heading 1 - Using a template encourages this behavior for new users while simply making it more efficient for everyone else • Instead of creating a new module from scratch, just copy this module instead • No singular module template is ideal for all Anaplan use cases – you are HIGHLY encouraged to create your own module formatting template, to best match the needs of your users Each module section is preceded by dashes – when displaying Line Items as columns, if you adjust the column width to 15 pixels, it will only show the headers dashes between sections, rather than the full section name

Trash Section • When building or cleaning up an Anaplan model, you’ll often run into the following situation: - You’ve identified a module you want to delete - You don’t immediately have time to put in the due diligence required to ensure that the deletion won’t break anything or affect another user’s experience • A simple solution for this is to include a Trash section – simply update the name of the module that is pending deletion and reorder it into this section. • Just make sure to follow through and actually put in the time required to delete the modules that have this pending status 16 Trash

Agenda • Project Background, Approach, & Key Principles • Caveats & Documentation • AFM Setup & Structure • Best Practices & Features to Avoid • Module Details by Grouping • Feedback Process • Thank You & Pay it Forward

Feedback Process • One size does not fit all and it’s very unlikely that a single release of the Anaplan Foundation Model will fulfill everyone’s needs • I will therefore commit to updating the AFM model once per quarter, based on your feedback • • - Email: mkuo@tableau. com - Linked. In: linkedin. com/in/matkuo/ I have also enlisted a number of Partner Advocates to assist with the process - The Anaplan Partner network will have access to both a broad variety and a high number of use cases - AFM Partner Advocates have committed to connect with me once per quarter to provide this feedback “Best-in-Class” cannot be achieved by a single version or release of a product – in practice, it is a standard that has to be maintained over time

Agenda • Project Background, Approach, & Key Principles • Caveats & Documentation • AFM Setup & Structure • Best Practices & Features to Avoid • Module Details by Grouping • Feedback Process • Thank You & Pay it Forward

Thank You Jeremy Smith - Being the Hyper. Care support representative for a Master Anaplanner at an Anaplan customer with 6 years of tenure is likely not a fun job Whether it be guidance on Windows command line syntax or overnight, blind meeting invites I send to address a critical problem, Jeremy has always addressed my Anaplan issues with a smile and an amazing attitude With Jeremy’s support, I’m never worried about achieving my goals within the Anaplan platform Aaron Wasinger - Hands down, the best customer success representative I’ve ever worked with When I first started working with Aaron, I suggested several activities to grow the Northwest Anaplan community, including User Groups, live trainings, and Customer Meetups – Aaron has made every single one of these happen Aaron always makes my priorities his own The current vibrancy of the Northwest Anaplan community is primarily driven by Aaron’s hard work and dedication

Thank You The Master Anaplanner Community - For the majority of my Anaplan career, whether I was an implementation partner or an Anaplan customer, I often felt very alone when trying to promote and demonstrate Anaplan’s value proposition The Master Anaplanner community changed that – this small group of the very best Anaplanners in the world is filled with supportive people, all of whom are genuinely passionate about the Anaplan platform One of my first posts on the Master Anaplanner forum, regarding how Tableau could perform a Fiscal Year shift, quickly led to two deep-dive interviews with other customers that faced a similar situation The members of this group never shy from providing honest feedback and are always willing to lend a hand And yes, they mailed me a toaster

Paying it Forward – How to Support AFM • As a Master Anaplanner who has used the platform for 6+ years, my own career opportunities are directly in line with the success of the Anaplan platform as a whole • I built AFM because I genuinely want to see the platform continue to advance in terms of maturity, legitimacy, and sustainability • I promise to you that: • - There will never be a charge for the model - You will never be forced to contact a consulting firm prior to using the model If you want to thank me for building this resource, please consider: - Providing feedback after using the template - Supporting my most wanted Anaplan feature requests

Matthew’s Most Wanted Anaplan Features • If you are interested in the continued advancement of the Anaplan platform, please consider reviewing my most wanted Anaplan features, by clicking on the associated idea link below, and supporting them with comments and/or examples • Your support will hopefully move these features up in the development cycle - Saved View Categorization and Priority Sorting - Toaster Time / Blue Box Culprit Anonymity - Explicit Option to Save or Not Save Import Actions - Display Notes Next to Process/Action Pop-up Message - Refresh Button on Blueprint Toolbar - Ability to Sort / Group / Filter the User List - Move or Hide the Model Map Button - Dashboard Text Box Alignment / Pixel Settings

Matthew’s Most Wanted Anaplan Features Saved View Categorization and Priority Sorting • https: //community. anaplan. com/t 5/Idea-Exchange/Allowthe-option-to-not-create-an-import-as-an-action/idip/38627 Toaster Time / Blue Box Culprit Anonymity • https: //community. anaplan. com/t 5/Idea-Exchange/Toaster -Time-Blue-Box-Culprit-Anonymity/idi-p/62180

Matthew’s Most Wanted Anaplan Features Explicit Option to Save or Not Save Import Actions • https: //community. anaplan. com/t 5/Idea-Exchange/Allowthe-option-to-not-create-an-import-as-an-action/idip/38627 Display Notes Next to Process / Action Popup Message • https: //community. anaplan. com/t 5/Idea-Exchange/Display. Action-Notes-on-the-Pop-Up-Message-before-a. Process/idi-p/59393#M 4679

Matthew’s Most Wanted Anaplan Features Refresh Button on Blueprint Toolbar • https: //community. anaplan. com/t 5/Idea-Exchange/Movequot-Refresh-quot-button-from-Edit-Menu-onto-Main. Blueprint/idi-p/58958 Ability to Sort / Group / Filter the User List • https: //community. anaplan. com/t 5/Idea-Exchange/Abilityto-Reorder-Sort-Filter-Group-and-generally-Organizethe/idi-p/50032

Matthew’s Most Wanted Anaplan Features Move or Hide the Model Map Button • https: //community. anaplan. com/t 5/Idea-Exchange/Hide. Move-Model-Map-Button/idi-p/53799 Dashboard Text Box Alignment / Pixel Settings • https: //community. anaplan. com/t 5/Idea. Exchange/Dashboard-Text-Box-Default-Alignment-Pixel. Settings/idi-p/58014

Appendix

Model Logo Creator • If you like the format of the AFM logo, use this slide to create your own model logo • Remember to publish your logo to a URL accessible by your users • Imgur. com is good option for a publicly available URL, just be mindful not to post anything sensitive • Include the image URL in your ADMIN – Background & Contact Info module AFM Anaplan Foundation Model