Add the timezones to AVEVA Measurement Advisor

The following procedure will guide you through the process of adding a new timezone for AVEVA Measurement Advisor. The example we provide demonstrates adding the Central European timezone. This timezone is one hour ahead of Coordinated Universal Time (UTC) in the winter, and two hours ahead in the summer.

To add the timezones to AVEVA Measurement Advisor

1. Open the measConfig tool.

2. Log in to CONNECT. For more information, refer to Opening the MeasConfig tool.

3. Define a New Module. In this example, we use CD_EUROPE, where CD_EUROPE is the name of the region for which you would like to define timezones.

4. Select the configDesc tab.

   Alternatively, you may locate the configDesc table on the Select Table tab.

5. Select Insert.

6. Fill out each field for the CD_EUROPE configDesc feature.

   • Enter the configName is the name of the feature. In this example, it would be Europe.

   • The configDefine should be the same as your module. In this example, it would be CD_EUROPE.

   • Enter a description.

   • The configTypeDefine should be set to Boolean.

   • The configSetting should be set to Feature.

   • The booleanValue should be set to Y.

7. Optional: You may wish to disable the North American timezones when you introduce new timezones. To do so, do the following:

   1. Change the Module to the Database name (CLOUDDB).

   2. Locate CD_NORTH_AMERICA on the configDesc tab.

   3. Select the N option from the booleanValue dropdown list.

   4. The row changed will be highlighted in red and the individual cells that were edited will be identified with the following marker: .

   5. Editing a value will result in the creation of a new row. The row that you have edited will be displayed first, but selecting will allow you to view the default value.

   6. Switch the Module back to CD_EUROPE.

8. Navigate to Select Table.

9. Double-click the timezoneDesc table.

   The timezoneDesc tab will open.

10. Select Insert.

11. You will need to provide information for the following columns for each of the timezones used in your region:

    • timezoneCode — AVEVA recommends that you use a unique code starting at 200. The timezoneCode in timezoneDesc can take a maximum value of 255.

    • timezoneName — Enter the name of the timezone. For example, Central European.

    • dstSupported — Indicate whether or not Daylight Saving Time (DST) is supported. For Central European time, DST is supported. The field should be set to Y.

    • standardOffset — This is the number of minutes from UTC when DST has not been applied. For Central European, this is 60 (minutes).

    • description — Provide any additional information for the timezone setting.

    • timezoneDefine — Define the timezone applicable to your region. We recommend prefacing the entry with TZD_. Consider the following example of proper format: TZD_CENTRAL_EUROPEAN.

    • timezoneEnv — You must use the timezoneEnv in accordance with the Olson database. To find the valid names for the tz (Olson) database, execute tzutil.exe /l from the command line. In our example for Central Europe, it is CET.

12. Navigate to the configDesc tab.

13. Change the Module to the Database name (CLOUDDB).

14. If you want to use one of the new timezones for the AVEVA Measurement Advisor system's timezone, find CD_CONTRACT_TIMEZONE_CODE and enter the timezoneCode you have just created. To do this, change the intValue from the default to the <timezoneCode> used above.

15. Switch the Module back to CD_EUROPE.

16. Navigate to the Select Table tab, and double-click to open the objItemDomainDesc.

17. Select Insert.

    A new row will be created for CD_EUROPE. You will need to repeat this process for each timezone.

    • The objItemDomainCode needs to be set to a unique value.

      Note: AVEVA recommends that, in order to ensure the codes used are unique, that you find the maximum baseline code used starting at 10,000. This will ensure that collisions are avoided. This is the recommendation for all instances where a code is required.

    • The objItemSubGroupDesc:objItemSubGroupName should be Meter General or Gas Quality General.

    • The objItemDesc:objItemName should be Field device local timezone

    • The objItemDomainName should be the name of the timezone. For this example, it would be Central European.

    • The subGroupSelect should be set to N.

    • The displayOrder should be set to the order in which you want to display the European timezones in the dropdown list.

    • The description should include any additional information.

    • The objItemDomainDefine should be formatted as follows. We have used the Central European timezone to demonstrate: OIDD_GMG_FIELD_DEVICE_LOCAL_TIMEZONE_CENTRAL_EUROPEAN for meters, and OIDD_GQG_FIELD_DEVICE_LOCAL_TIMEZONE_CENTRAL_EUROPEAN for gas qualities.

    • The configDesc:configDefine will be CD_EUROPE.

18. Navigate to the Select Table tab, and double-click to open objItemDesc.sysdefDomainValues.

19. Change the Module to the Database name (CLOUDDB).

20. Find the rows for Meter General — Field device local timezone and change the objItemDomainDesc:objItemDomainName to Central European.

21. Repeat this for the Gas Quality General — Field device local timezone.

22. After completing your setup, navigate to the Save and Load tab, and select Save All.

23. Select Update Database.