The Anaplan Data Management System is not currently available and as such all statements below are subject to our standard safe harbour statement and are subject to may change.
The Data Management System is aimed at a technically savvy business user that is comfortable building models in Anaplan and working in Excel. They have a good knowledge of the business problem to be solved and the data that is available to do it, but are not necessarily Master Anaplanners, experts in SQL or database management. We call them Data Modellers.
Data Modellers configure connections to common on-premises and cloud source systems through intuitive interfaces tailored to the data source. Modellers will authenticate, be guided through the selection of source data defaulting to delta loads where that is supported by the source application and schedule execution. Executions will be logged to support failure alerting, monitoring, summary reporting and housekeeping.
The modeller will be able to connect to Anaplan models as an inbound data source to support inter model data transfer and reporting and analysis capabilities outside of Anaplan.
The approach is to build a connector framework into which connectors for specific data sources can be introduced quickly and without significant effort. In the longer-term partners should be able to certify and register additional connectors.
Data Modellers restructure the extracted data into the format required for modelling and planning by configuring a repeatable sequence of transforms through an intuitive graphical interface. In addition to basic primitives (filter, lookup, join, calculate, sum, union) there will be extended capabilities for OLAP such as balance and validate hierarchies, aggregation to dimension levels, and data quality and anomaly detection capabilities.
The catalogue exists at a tenant level and Modellers across workspaces in the tenant can consume accessible Data and Master data objects into their models. It also allows the Data Modeller to assign semantics to objects to simplify, accelerate, and automate the mapping for consumption of data into Anaplan models.
The Data Modellers will have access to statistics for objects in the library (for example where these are consumed, how frequently and recently, volatility, quality) for housekeeping and maintenance purposes.
Data Modellers will be able to create and update lists and data in their models from accessible objects in the DMS catalogue for faster model development and maintenance.
When consumptions are executed, these are logged for success / failure, data volumes, execution time and rejected data so that the Data Modeller can report on statistics of catalogue object use.
In alter releases:
The DMS will be the solution for extracting, transforming, enriching, validating, staging, and orchestrating the incoming and outgoing data for Anaplan.
It is not:
@JohnC Thanks for the insight !
@JohnC Is there any list of tools or servers to which DMS can connected? And is there any timeline for when we can expect the DMS release?
@JohnC Thank you for Sharing. Excited to Know more about this in future.
The current time line is for a Beta in April with Early Adopters being able to leverage Anaplan DMS from July of this year. In the Beta data can be loaded from S3, local CSV file and Anaplan models.
In the July release we expect to add Azure Blob, GBQ, SFDC, Snowflake and SAP through OData. Post July we have plans for connectors to Workday and SQL Databases. Additional connectors will be added based in customer demand.
@JohnC Great to Know this. Looking forward!
@JohnC : thanks for sharing the info. All clear from architecture point of view and looking forward to see it implemented. :)
How will work the "automated" data flows using DMS? Will be similar to CloudWorks integration flows?
In that case, how would you "see" an automated integration using a local CSV file?
Will be still needed of some external tools to automate the upload the file using some REST APIs and triggere the DMS integration flow? If yes, will these REST APIs be released in Beta version ?
thanks
Alex
Orchestration and Scheduling will leverage Workflow capabilities - but the steps will be DMS tasks. Upload of local CSV files is manual - until we provide a local file connector. For files in S3 or in another source with an available connector the steps to extract / load the data from that source, transform it and publish into one or more models will be handled through this orchestration capability, either run manually or on a schedule.
The available schedules will be similar to those in CloudWorks but be based on a starting time range and / or throttled to avoid excessive loading on the platform at the top and bottom of the hours.
We will provide Rest API's to allow customer to push data into the DMS in some future release. Our priority is on avoiding the need for the use of API's at this stage.
It's like a behind-the-scenes maestro coordinating tasks seamlessly. Right now, uploading local CSV files is a bit hands-on, but they're working on a local file connector to automate that. For files in S3 or other sources, the DMS takes charge of extracting, transforming, and loading data into models, either manually or on a set schedule.
Oh, and they're planning to introduce Rest APIs down the line for customers to push data into the DMS. It's all about making things easier without diving into complex APIs just yet.
By the way, speaking of systems, have you ever wondered, what is ERP and how does it work? It's like the backbone of many businesses, managing everything from finances to HR seamlessly. Pretty neat, right?
@JohnC For early adaption of the Beta version to test the functionality and workability, it is available for all customers or is it only for a few customers?
The Beta will be made available to a small number of existing Anaplan customers. Please work with your Anaplan Account team and Business Partner if you are interested in getting involved.
I have 2 lists used in modelling, In Input module I'm using subset of territories from Country List and subset of Regions from Flat list. But in Output module,Its reversed, I'm using subset of regions from Country list and subset of territories from flat list.How to derive the numbers from input to output module. I do have…
This shows all comments across all data to all users with access to the UX page. This is not appropriate for any UX which might contain security access sensitive data. Comments on grids and cards ARE security dependent. That works fine. But anyone with access to the page can open this Summary Panel and see ALL comments…
If anyone is aware of idea exchange ideas that are currently being evaluated by the product team, if you don't mind linking them here, would love to give them an upvote. Thanks!
