Components Excel
Below is an example of an empty Excel file of the components.
The Excel file dedicated to components is made up of six tabs, each one dedicated to a specific type of information that must be uploaded into the system by the user. Below is a description of how to fill in the various tabs.
Tab COMPONENTS
This tab is dedicated to entering component data. Note that all translations related to components are not entered here, but instead must be specified in the dedicated tab (COMPONENTS TRANSLATIONS).
Each component is characterized by a group and a subgroup. The columns GROUP CODE and SUBGROUP CODE must contain the unique codes that identify the group and the subgroup. Note that it is possible to create new groups and subgroups by specifying a code that has never been used before.
The CODE column is dedicated to the component code. If the code of an existing component is entered, then the component data in the database will be updated with the values provided in the Excel file; otherwise, a new component associated with that code will be created.
For each component, it is possible to specify the name of an image to be associated with it in the IMAGE column. This image must be present in the asset’s image library; otherwise, it will not be displayed. The IMAGE 3D column is optional and allows specifying the name of a 3D image. The image format must always be included in its name.
The INSTALLATION DATE column allows specifying the date when the component was installed. The date must follow this format: YYYY-MM-DDThh:mm:ss.SSSSSSZ.
Examples of valid dates:
The MAINTENANCE STATE FUNCTION column allows specifying which function to use to select the counter that will indicate the component’s useful life. In fact, in the COUNTERS tab, multiple counters can be defined for the same component. For the system to dynamically choose one of these to indicate the component’s useful life, it is necessary to define a function as the selection criterion.
As shown in Images B and C, when the MAINTENANCE STATE FUNCTION column is selected, a custom message informs the user that only certain values are allowed in this column. A drop-down menu allows selecting one of the permitted values.
Tab COMPONENT TRANSLATIONS
This tab is used to specify all translations related to the components listed in the COMPONENTS tab. For each component, it is necessary to specify a name and a description. Note that each column is duplicated for all project languages, so its value can be specified in each language.
The CODE column must contain the unique code of the component for which translations are being defined. Note that the values in this column must match the values in the CODE column in the COMPONENTS tab.
Image D shows an example of the COMPONENT TRANSLATIONS tab. In this case, the only project languages are Italian and English, so the NAME and DESCRIPTION columns are provided in both Italian and English (NAME IT, NAME EN, DESCRIPTION IT, DESCRIPTION EN).
Tab GROUP TRANSLATIONS
This tab is used to configure all translations related to the groups listed in the COMPONENTS tab. For each group, it is necessary to specify its name in all project languages. The NAME column is duplicated for all project languages so that its value can be specified in each language.
The CODE column must contain the unique code of the group for which translations are being defined. Note that the values in this column must match the values in the GROUP CODE column in the COMPONENTS tab.
Image E shows an example of the GROUP TRANSLATIONS tab. In this case, the only project languages are Italian and English, so the NAME column is provided only in Italian and English (NAME IT, NAME EN).
Tab SUBGROUP TRANSLATIONS
This tab is used to configure all translations related to the subgroups listed in the COMPONENTS tab. For each subgroup, it is necessary to specify its name in all project languages. The NAME column is duplicated for all project languages so that its value can be specified in each language.
The CODE column must contain the unique code of the subgroup for which translations are being defined. Note that the values in this column must match the values in the SUBGROUP CODE column in the COMPONENTS tab.
Image F shows an example of the SUBGROUP TRANSLATIONS tab. In this case, the only project languages are Italian and English, so the NAME column is provided only in Italian and English (NAME IT, NAME EN).
Tab COUNTERS
This tab is used to specify all counters associated with the various components. Counters are not mandatory, since a component may have none. Other components, however, may have multiple counters.
A counter must always be associated with a component. This association is made through the COMPONENT CODE column. Here, it is necessary to provide the unique code of the component for which the counter is being created. The values in this column must match those specified in the CODE column of the COMPONENTS tab.
The CODE column allows specifying a unique code for the counter. If the code provided is not unique, then the counter with that code will be updated. Note that it is not possible to change the component associated with an existing counter. To do so, the counter must first be deleted from the current component and then recreated for the new component.
The KPI column allows specifying the value or formula to be used for calculating the counter’s value. As shown in Images H and I, when the column is selected, a tooltip indicates how to populate the cells. The values that can be entered in this column are provided through a drop-down menu. They depend on how the asset’s machine-profile.json file has been configured. Additionally, the "absolute time" value is always available, allowing the creation of a counter that tracks time.
The component’s expected lifetime must be indicated in the EXPECTED LIFETIME column, while the critical and subcritical thresholds must be indicated in the CRITICAL THRESHOLD and SUBCRITICAL THRESHOLD columns, respectively. Note that both CRITICAL THRESHOLD and SUBCRITICAL THRESHOLD are optional columns.
Il valore specificato nella colonna EXPECTED LIFETIME deve essere maggiore di quelli specificati in CRITICAL E The value specified in the EXPECTED LIFETIME column must be greater than the values specified in CRITICAL THRESHOLD and SUBCRITICAL THRESHOLD.
The value specified in the SUBCRITICAL THRESHOLD column must be greater than the value specified in the CRITICAL THRESHOLD column.
Tab COUNTER TRANSLATIONS
This tab is used to specify translations of the counters defined in the COUNTERS tab. For each counter, it is necessary to specify its name in all project languages. The NAME column is duplicated for all project languages so that its value can be specified in each language.
The CODE column must contain the unique code of the counter for which translations are being defined. Note that the values in this column must match the values in the CODE column of the COUNTERS tab.
Image L shows an example of the COUNTER TRANSLATIONS tab. In this case, the only project languages are Italian and English, so the NAME column is provided only in Italian and English (NAME IT, NAME EN).
