Planual rules regarding data hubs.
5.07-01 No hierarchies
There should be no need for composite list hierarchies in the Hub. They can be built to "test" the actions, but after testing they should be deleted.
exception
| 5.07-01a Validation purposes | Used if data needs to be consolidated to check against source systems, although the flat modules with attributes can be used to sum data. |
| 5.07-01b Combining source systems | Used if you want to combine multiple source systems into one feed from the Data Hub to the spoke model(s). |
bestPracticesArticles
5.07-02 No Analytical modules
Keep Analytical modules (modules with multiple lists in the Applies To) out of the Data Hub.
5.07-03 Flat lists for data export
Use the flat list structures to create modules and views for downstream targets.
5.07-04 Get the correct format
Get the data from IT in the correct format as well as the correct granularity.
relatedToRule
5.07-05 Use System modules
Use System modules for filtering data (current period, current FY year, etc.).
relatedToRule
bestPracticesArticles
5.07-06 Master data should be built by the source system
Avoid creating master data in the hub. This should really come from the source system(s).
5.07-07 Keep Transactional Analysis out of the planning models
Use another reporting model (FIN Trans Data) to keep detailed transactional data out of the main planning models.
Large amounts of historic transactional data can inflate the size of the planning model and lead to reduced performance.
5.07-08 Pre aggregate for downstream exports
It is more efficient to aggregate the data in the hub and then export it, rather than accumulate it through the import to the downstream models.
5.07-09 Avoid using a top level for large lists of transaction data
Don't create a transaction list with a top level. The calculations will sum for all items in the list even if only a single item is added.
If a sum of all transactions is needed, consider using a "dummy" list and summing the data within a module dimensionalized by the "dummy" list.
relatedToRule
bestPracticesArticles
5.07-10 Add intermediate sub-totals to transaction lists
If you need the totals for validation purposes, create intermediate sub-totals within the transaction list. This will significantly reduce the calculation load.
Another alternative would be to create a "dummy" list and sum the data using a list formatted member within the "Dummy" list.
relatedToRule
5.07-11 Create the Data Hub in a separate workspace
Create the Data Hub in its own workspace. This allows for the Data Hub to expand in size without disrupting inbound or outbound integrations.
It also allows for segregation of duties (users who manage the data are kept separate from the production models).
5.07-12 Don't confuse the Data Hub with an Export Hub
If you need to consolidate your exports from multiple models to one export, create an Export Hub model to keep the Data Hub (data coming from outside source systems) clean.
