Before starting using DINAMIS, it is important that you familiarize yourselves with some of its basic principles, assumptions and terminology.

How DINAMIS works?

Simplifying complex processes is what we are proud of, so if you would ask us how DINAMIS works, we’d answer:

  1. Enter your network structure. We assume that it is in a hierarchical tree form, see below.
  2. Enter the products, services, activities or whatever is that you want to target and monitor. Group them if you like, because you most probably want to monitor the performance on a product group level. 
  3. Enter the product credits, i.e. a figure the corresponds to each product’s revenue or profitability (see here for more information),
  4. Enter the product quotas for the current quarter

You need to do the above just once, or whenever something changes. Then, once per month, just enter your monthly sales figures, with a very simple .csv file. 

That’s it! You can now generate all your sales reports.

You can easily modify or import new data, add or remove products, switch between years and months, create other networks, add or remove network nodes, and more, in a straightforward way. Everything is pre-configured so there’s no need for you to build or design anything. 

Assumptions

Such simplicity comes with some assumptions, so please have a close look at the following:

Network structure
  • Dinamis assumes that your network structure has an hierarchical tree form as in the screenshot aside.
  • The network can have as many hierarchy levels as required and each level can contain as many nodes as required.
  • In our example we have a Network Director, Divisions, Area Managers and Sales Reps, the latter being the lowest hierarchy level.

  • The nodes of the lowest level are called sales nodes. Why is that? Because DINAMIS assumes that ONLY these nodes are actually your sales points (reps or stores). All the higher levels are being considered as managerial in the sense that they do not have their own discrete, quotas and sales figures, but their figures are just the aggregations of the corresponding figures of the sales nodes they manage. In the above example, the figures calculated for Jessica E., an Area Manager in London Division, are just the sum of the three Sales Reps under her supervision, London’s figures are the aggregation of Jessica’s and Harry’s, the Area Managers, and since Mike Stevens is the Network Director, his figures are those of the entire network.
  • This is the why when defining your sales network, you have to enter a node ID, only for the lowest level nodes. When the time comes to import the figures into the internal database, DINAMIS must know what accounts to who. 

 

Reporting

By the same reasoning, the Sales Reports generated for your network nodes, are identical to each other, i.e. you cannot have a distinct, from a design perspective that is, report for the Area Managers than for the Sales Reps. 

However, it’s completely up to you whether you assign quotas for the same products to all of your sales nodes. So, in our example, maybe Jessica’s team has quotas for product A while Harry’s team does not. Their reports will look exactly the same, containing both A and B,  but the overall performance will be calculated based on different product portfolio. 

 

Annual performance

This beta version of DINAMIS assumes that you have an annual budget but you set quotas per quarter and monitor the performance on a monthly basis. Therefore, the Overall Performance Indicator (OPI) is calculated on a Year To Date basis, corresponding to an annual performance.

Based on the feedback we will collect from the beta users, we’ll decide whether we must incorporate alternative approaches

Reports & Data Synchronization

Handling data is effortless in DINAMIS. You just import the data you want in the data management page. What we really want to discuss here has to do with the synchronization between the data and the reports.

Consider the following example: By the end of March you enter the monthly sales figures and generate the 1st Quarter Sales Reports. Then, you get notified that a sales figure for a sales node was erroneous, so you make the correction. The moment you do so, the synchronization banner changes to yellow with a message “Synchronization: Modified data”. However, if you try to re-generate the March Sales Report once again, nothing has been changed.   

 

This is done intentionally. It gives you the freedom to modify whatever you want and decide when you want to synchronize these modifications. All the calculations take place, only when you press the Synchronize button and you probably do this, when you are ready to generate the April’s Sales Reports.