Symology Set Up

IEG4 Set Up Pre-requisites

In order to power the Symology no code integration we need you to provide us with the following information:

To Retrieve Assets

• The number of different assets you'd like to import

• The number of columns and the labels/descriptions of each column in each extract imported

To Retrieve Outstanding Jobs

• The number of different outstanding job types you'd like to import

• The number of columns and the labels/descriptions of each column in each extract imported

To Retrieve Roads with different responsible parties

Where there is another organisation responsible for a road/street, like Transport for London in the case of London Boroughs, there is the ability to import a list of all streets with an indicator to set the organisation responsible.

The prerequisite is that you provide a file of addresses in CSV format and clearly indicate which column heading contains the responsible party. This value will be populated int the map's CustomField so it's obviously important this file is accurate/kept up to date.

To Create Jobs

• The Symology API URL for TEST and LIVE

• The Symology API username and password for TEST and LIVE

When you provide this information we will create the functions to make the process an entirely no code experience.

Extract Batch Import

Once we have completed the above set up you will be able run the batch import process we provide as a part of implementation called the:

Bulky Import Application

Our expectation is extracts for assets, which change infrequently will be imported relatively infrequently. But the extract(s) for outstanding jobs will happen daily.

Each extract you import will overwrite the one before ensuring an always accurate snapshot as at that day.

The Bulky Import Application (BIA) is an executable application that is capable of taking a file from your network and pushing it to our Microsoft Azure Cloud, which also hosts eDesigner.

The BIA has configuration, which allows it to look into a specific folder for a specific file name and import it to a specific location related to that extract type. The reason why it is important IEG4 first do their set up in the cloud is the different extract cloud storage locations are created and we can then provide these to you to use in the configuration.

The BIA executable can be automatically run by a window batch file, which comes with the implementation pack we will send you. Therefore it is possible, once you have the necessary folders in place for each extract, to fully automate the import process.