Initial Custom Configuration Check List

Following presents issues a gINT developer should consider when implementing the DLST in a new organisation.

1. Start with the latest DLST gINT Files, or the latest relevant compiled Datgel Product gINT Files (that incorporate many Datgel Products merged into one set of gINT Files – ask Datgel Support for this)
   1. Set file names
   2. Company 1.00.gpj
2. Company 1.00 lib.glb
3. Logo: SYMBOL DESIGN | Bitmap Symbols
   1. Merge Logo or Logos
   2. Delete other dummy logos
   3. See section Configuring Logos in the Library for more details.
4. DATA DESIGN | Library Data | DG_COM_OFFICE
   1. Set Office name
   2. Set default logos for the office
   3. test a log and graph, configure the offset field on DG_COM_OFFICE after testing a graph report
   4. Remove Datgel Office
5. Project table
   1. Set value for PROJECT.Office
   2. Set default value for PROJECT.Office
   3. Set PROJECT.Data_Template_History Caption as: Company 1.00 yyyy-MM-dd
   4. Set PROJECT.Data_Template_History Default Value as: Created with Company 1.00 yyyy-MM-dd, and set the value as: Created with Company 1.00 yyyy-MM-dd
   5. Coordinate System and Elevation
      1. For Australian users set the value and default for Elevation Datum to AHD, and if the user is only in one city set the default for the Coordinate System to the relevant MGA94 Zone ##. Sydney, Melbourne and Brisbane = "MGA94 Zone 56", Adelaide "MGA94 Zone 54", Perth "MGA94 Zone 50"
      2. Singapore: SVY21 and MSL
   6. Set default values and values for Default SPT Pen 1 3 5 and Default SPT Pen 2 4 6. For AS/ASTM set the former to 150 and later blank, and for BS set both to 75.
6. Set Help > User File Visioning. Fill both fields with Company 1.00 yyyy-mm-dd.
7. PROJECT_OPTIONS
   1. Set Classification_Standard Value
   2. Set Classification_Standard Default Value
   3. Set List_Filter Value
   4. Set List_Filter Default Value
   5. Set SPT_N_Value_on_Plots_For_Refusal, and default value
8. Set the most relevant value and default for TRANSMISSION_INFORMATION_EXPORT.AGS_Edition.
   1. AU "3.1 RTA 1.1"
   2. NZ: "4.0.3 NZ"
   3. SG: "3.1 (SG)"
   4. MY: "4.0.3"
   5. Rest of world: "4.0.3"
      Perhaps set values and defaults for other fields on TRANSMISSION_INFORMATION_EXPORT.
9. Consider DATA DESIGN | User System Data | DG Com Strata Description. This controls which Component description tables are referenced by log reports. Currently gINT is limited to how many fields may be referenced by one entity resulting in the need to not reference all component tables in one expression. By default, the ASTM component description tables are not listed, you can list them by copying the relevant lines from DG Com Strata Description Z, and replace one of the other references in DG Com Strata Description.
10. Delete unneeded component description tables, or move them to end of Main Group
11. Set Lists and set table property "Keep data when cloning", particularly:
    1. GEOLOGY_UNIT_1, 2, 3
    2. PLANT_LIST
    3. ORGANISATION
    4. OPERATOR
    5. LOGGED_BY
    6. TESTED_BY
    7. PROCESSED_BY
    8. APPROVED_BY
    9. COORDINATE_SYSTEM
    10. ELEVATION_DATUM
12. Optional, Migrate pre-existing custom gINT Objects
    1. Merge selected project tables and fields
    2. Set field and table properties
    3. Add ItemKey table data, such as Plant List
    4. Merge library objects, such as reports, blocks, material graphics, library tables etc
    5. Make a field map Excel file, where you list
       1. old Table.Field and DLST table.field,
       2. old and new User System Data
    6. old and new library Table.Field and DLST table.field
    7. Then use the DATA DESIGN | Project Database | Tools > Replace Field Names… to translate old references to DLST.
    8. You will need to review code on each report.
13. Make a data template
14. Repair and compact gpj, glb and gdt files
15. Distribute the files to users. Best to include other relates files such as correspondence files, gINT AGS Schemes, example photos and data files, and user guides. Make a zip, named "yyyy-MM-dd_Company_#.##.zip".

Recommendations for Customisation

The Lab and In Situ Tool should be considered as an advanced starting point for your organisation to create organisation specific gINT system. Someone will need to customise what users see in INPUT and the report presentations to suit your organisations exact needs. Datgel's general recommended approach to customisation is described below.

1. Install the DLST Program, and open the DLST Tool user gINT Files, and activate the license.
2. Navigate to INPUT | Options | Project_Options, and set the Classification_Standard and the List_Filter that best suit your needs.
3. Review the project database, and what fields and tables you don't need. Then adjust a Hide Scenario to support this. Do not delete field/tables.
4. Review lookup items and add/edit what is needed. Note, many lists are controlled by list filters. To know where the list is stored, right click on the field and select field properties.
5. Review the standard reports, and identify what changes are needed to some of these to suit your needs. Then copy the report, rename them to <Company name abbreviation> *, and make changes.
6. Prefix the name library objects that you make or edit with <Company name>_ or <Company name abbreviation> *, so that migration to future version of Datgel standard gINT files is easier. Also, in Library tables when you edit or add records have <Company name abbreviation> in Customisation_Remark to make it easy to know what has been changed from Datgel's standard items.

Datgel can do the development tasks described above on a consulting basis.
If you require technical support related to gINT development you should contact your gINT support provider, which may not be Datgel. If Datgel is not your normal gINT support provided, you can purchase a Prepaid Technical Support Package from Datgel to enable Datgel to assist you.