About Cost Transparency Configuration Conventions
This page discusses standard data organization and configuration. These practices should be followed unless there is a compelling use case that makes following them impossible. Organization of data tables falls into to two areas, categorization and naming of the individual tables.
Basic
The basic conventions are intended for the majority of implementations including Jumpstart, and CT Enterprise.
Categories
While this will vary greatly from project to project, typically we see data tables that fall into a few main categories: Finance, IT Ops, Services, and Mapping. They also are generally either Transform, Mapping, Reference or Master Datasets. The recommended table groupings are as follows:
Category | Description |
01 Financials | Contains data tables like GL, Budget, HR, Fixed Assets |
10 Infrastructure | Contains data tables like CMDB, Storage Pools, Application List |
20 Business and Services | Contains data tables like Business Units, Apps & Business Services |
50 Mapping | Contains mapping data tables like Server to Apps, Cost Centers to ITRTs |
60 Reference | Contains data tables that are generally system generated like Cost Center Hierarchy, Chart of Accounts, or Business unit Hierarchy |
Data table Naming
Data table core name
Table Type | Description | Examples |
Uploaded Data Table | The name of the table should be named in such a way that it can be easily identifiable in terms of where the data have come from, and what they will be used for. The file name should not include dates, and where possible avoid using alpha numeric characters. You should ensure the name is not the same as the modeled data table that the Master Dataset will be associated with. Using the suffix Data can be used to help make this distinction clear. | GL Cost Source Actuals Fixed Asset Data Server Data |
Modeled Data Table | The table should be named in such a way that it makes sense in terms of its function with regards to the flow and allocation of costs, and be consistent with the standard Apptio Modeled Data Tables. | Servers to Applications SAP Platform Managed Service Providers Software Licenses |
Suffix
Suffix | Description | Examples |
MAP | Mapping Files - Name of the File contains ‘MAP’ at the end of the file name without using any special characters. | Fixed Assets to ITRT MAP Fixed Assets to ITRT MAP |
REF | 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 should be added without using any special characters | IT Resource Towers List REF IT Resource Towers List REF |
TA, TB, | Transforms should contain suffix that indicates in what order they are created. Although transforms should be rarely needed. | Cost Source Actuals TA Cost Source Actuals TB |
Column Names
In the main the naming and configuration of column names is determined by the functionality of the column, and to be called something that makes sense to the context of that functionality and the client. However, there are a couple of cases where it makes sense to use a common approach.
Name | Description | Example |
Helper | When creating a lookup between two data tables, it is often necessary to create a column that concatenates a number of columns in order to have the required elements in the Lookup. T make clear why this has been create a column name that either describes the contents, or describes the functionality, followed by Helper. | In Labor Master Data CostLabor Helper or Cost Center_Region Helper |
Return | When creating a lookup between two tables, it is often necessary to return more than one column. Rather than create multiple lookups, create a Return column that returns a number of columns separated by “|” | Labor Details Return =”Cost Center”&”|”&Region |
Extended
The extended conventions are intended for implementations where there are a large number of data tables, such that the Basic conventions don’t adequately cater for a clear understanding of those tables, their orientation, and purpose.
Categories
While this will vary greatly from project to project, typically we see tables that fall into a few main categories: Finance, IT Ops, Services, and Mapping. They also are generally either Transform, Mapping, Reference or Master Datasets. The recommended table categories are as follows:
Category | Description |
01 Financial | Contains tables like GL, Budget, HR, FA. |
01 HR | HR Specific data tables. |
01 Project | Project data tables. |
01, 02, 03 XXX | For very large customers with many data tables there may be the need to create more specific categories. |
02 Financial Mapping | Mapping data for financial data. E.g. Cost Center to ITRT |
03 Financial Reference | Reference data for financial data. E.g. Cost Center Hierarchy |
… | And similar for all other areas |
10 Infrastructure | Contains tables like CMDB, Storage Pools, and Application List. |
20 Business and Services | Contains tables like Business Units, Apps & Business Services. |
50 Mapping | Contains mapping tables like Server to Apps, Cost Centers to ITRTs. |
60 Reference | Contains files that are generally system generated like Cost Center Hierarchy or IT Resource Tower Reference List. |
10 End User Devices | |
10 Servers | |
20 Applications | |
20 Services | |
70 TL Files | There are some occasions where many data tables need to be appended to together, then have a similar set of formulae applies, before appending to a Master Data Set. In this situation, it is recommended to create a TL data table. A common example of where this is necessary is when a customer has multiple GL files (for example from multiple regions) that have a very similar structure. |
80 Modelled Tables | A category to keep custom modeled data tables together and isolated from standard data tables. |
Data Table Naming
Core Table Name
Table Type | Description | Examples |
Uploaded Data Table | The name of the table should be named in such a way that it can be easily identifiable in terms of where the data have come from, and what they will be used for. The file name should not include dates, and where possible avoid using alpha numeric characters. You should ensure the name is not the same as the modeled data table that the Master Dataset will be associated with. Using the suffix Data can be used to help make this distinction clear. | GL Cost Source Actuals Fixed Asset Data Server Data |
Modelled Data Table | The table should be named in such a way that it makes sense in terms of its function with regards to the flow and allocation of costs, and be consistent with the standard Apptio Modeled Data Tables. | Servers to Applications SAP Platform Managed Service Providers Software Licenses |
Prefix
Prefix | Description | Examples |
ACT | For files related to actuals is the prefix added to the filename. The ACT prefix applies for tables in both finance, infrastructure and business. | ACT OBJ Cost Source ACT OBJ Servers ACT CON Storage EMC |
BUD | For files related to budget is the prefix added to the filename like it is with actuals. | BUD OBJ Cost Source BUD OBJ Servers |
CON | Consumption files are often tables that are used for lookups from the tables backing up objects. | ACT CON Servers AIX ACT CON Storage EMC |
Suffix
Suffix | Description | Examples |
MAP | Mapping Files - 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 | Fixed Assets to ITRT MAP Fixed Assets to ITRT MAP |
REF | 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 should be added without using any special characters | IT Resource Towers List REF IT Resource Towers List REF |
LOOKUP | It is sometimes required to have a duplicate of data table that is used as a lookup table in order to avoid a circular reference. To make it clear that this is the reason that this has been done, add LOOKUP as a suffix | Servers LOOKUP |
TA, TB, | Transforms should contain suffix that indicates in what order they are created. Although transforms should be rarely needed | Cost Source Actuals TA Cost Source Actuals TB |
TL | There are some occasions where many data tables need to be appended to together, then have a similar set of formulae applies, before appending to a Master Data Set. In this situation, it is recommended to create a TL data table. A common example of where this is necessary is when a customer has multiple GL files (for example from multiple regions) that have a very similar structure. | Cost Source Master TL |
Column Names
In the main the naming and configuration of column names is determined by the functionality of the column, and to be called something that makes sense to the context of that functionality and the client. However, there are a couple of cases where it makes sense to use a common approach.
Name | Description | Example |
Helper | When creating a lookup between two data tables, it is often necessary to create a column that concatenates a number of columns in order to have the required elements in the Lookup. T make clear why this has been create a column name that either describes the contents, or describes the functionality, followed by Helper. | In Labor Master Data CostLabor Helper or Cost Center_Region Helper |
Return | When creating a lookup between two tables, it is often necessary to return more than one column. Rather than create multiple lookups, create a Return column that returns a number of columns separated by “|” | Labor Details Return =”Cost Center”&”|”&Region |