The recommendations in this document are relevant for R11.x only and are recommendations, not requirements.
For projects with high number of datasets is it recommended also to include naming convention for both prefix, suffix and work with a final transform, which is appended to the master dataset.
Projects with high number of datasets
Categories
While this will vary greatly from project to project, typically we see datasets that fall into a few main categories: Finance, IT Ops, Services, and Mapping. They also are generally either Raw, Transform, Mapping, Reference or Master Datasets. The recommended dataset groupings are as follows:
| Category | Description |
|---|
| 01 - Raw - Apps & Services | Contains raw datasets related to Apps & Services objects |
| 01 - Raw - End User Devices | Contains raw datasets related to End User object |
| 01 - Raw - Finance | Contains raw datasets related to Finance objects |
| 01 - Raw - Infrastructure | Contains raw datasets related to Infrastructure objects |
| 01 - Raw - Staging | Contains datasets which has not come into play yet, but it is expected that they will do. |
| 02 - Transform - Apps & Services | Contains transforms related to Apps & Services objects |
| 02 - Transform - End User Devices | Contains transforms related to End User object |
| 02 - Transform - Finance | Contains transforms related to Finance objects |
| 02 - Transform - Infrastructure | Contains transforms related to Infrastructure objects |
| 03 - Mapping - Apps & Services | Contains mapping datasets related to Apps & Services objects |
| 03 - Mapping - End User Devices | Contains mapping datasets related to End User object |
| 03 - Mapping - Infrastructure | Contains mapping datasets related to Infrastructure objects |
| 03 - Mapping - Finance | Contains mapping datasets related to Finance objects |
| 04 - Reference - Apps & Services | Contains reference datasets related to Apps & Services objects |
| 04 - Reference - End User Devices | Contains reference datasets related to End User object |
| 04 - Reference - Infrastructure | Contains reference datasets related to Infrastructure objects |
| 04 - Reference - Finance | Contains reference datasets related to Finance objects |
| 05 - TL | A category that only contains all the last transforms. Read more about TL in the naming section. |
Naming
The reasoning for having guidlines for naming is to track the kind of dataset and to identify where we are in the data transform chain. The naming convention is extended to include primary and secondary prefix and one suffix.
<Primary Prefix> / <Secondary Prefix> / <File Name> / <Suffix>
| Prefix | Description | Example |
|---|
| ACT | Primary Prefix - This is one of the two primary prefixes. For files related to actuals is the prefix added to the filename. The ACT prefix applies for datasets in both finance, infrastructure and business. | - ACT OBJ Cost Source RAW
- ACT OBJ Servers RAW
- ACT CON Storage EMC RAW
|
| BUD | Primary Prefix - For files related to budget is the prefix added to the filename like it is with actuals. | - BUD OBJ Cost Source RAW
- BUD OBJ Servers RAW
|
| UMT | User Map Table – In most cases an UMT will not require either ACT/BUD prefix or RAW / TA Suffix. | - UMT Vendor to Application
|
| MAP | Secondary Prefix - Name of the File contains ‘MAP’ at the end of the file name without using any special characters. Also, ensure that every new mapping file that is uploaded should use ‘RAW’ as a suffix as stated in section | - ACT MAP IT Resource RAW
- ACT MAP Cost Pool RAW
|
| REF | Secondary Prefix - The system generated reference file when extracted from Apptio and uploaded with changes to be used as a reference file, ‘REF’ at the end of file name with ‘RAW’ suffix should be added without using any special characters | - ACT REF Cost Center RAW
- ACT REF Chart of Accounts RAW
|
| CON | Secondary Prefix - Consumption files are often datasets that are used for lookups from the datasets backing up objects. | - ACT CON Servers AIX RAW
- ACT CON Storage EMC RAW
|
| OBJ | Secondary Prefix - Datasets that par populating the objects in the model. | - ACT OBJ Applications RAW
- ACT OBJ Cost Source RAW
|
| Suffix | Description | Example |
|---|
| RAW | Name of the Raw File with suffix ‘RAW’ without any special characters. Ensure any file that is user uploaded should contain ‘RAW’ as a suffix. | - ACT OBJ Cost Source RAW
- ACT OBJ Fixed Assets RAW
|
T1, T2, T3 V1, V2, V3 TA, TB, TC ... | Transforms should contain suffix that indicates in what order they are created. First transform could be 'T1', 'V1' or 'TA'. A transform of a transform will then be 'T2', 'V2' or 'TB' and so on. Whether 'T1', 'V1' or 'TA' is selected is not important, what is important is that it shows a sequential order. | - Cost Source Actuals T1
- Cost Source Actuals T2
- Cost Source Actuals V1
- Cost Source Actuals V2
- Cost Source Actuals TA
- Cost Source Actuals TB
|