How to create a Fusion Template?

Fusion software requirements

Fusion must be installed on a server on your network, and the SQL server using it must be accessible from the computers that will run the Fusion import.

If a computer can run a local Fusion installation to connect to the Fusion database, then the network configuration for that computer is already properly configured to allow the import to run from Isatis.neo.

The Computer which runs the SQL server should be configured to listen to inbound SQL server connections, and have those ports allowed in its firewall.

Note: Isatis.neo installs/updates Fusion Exporter on the computer when it is installed.

Preparing the data in Fusion

Import template

  • In Fusion Report Manager:

    • users define Queries. One query will result in one data table generated.
    • users then define an Export. One export will reference one or multiple Queries. Running the Export will generate one data table for each query it uses at the place specified by the user.

    Note: You can refer to the Fusion Documentation for more details.

  • In Fusion Exporter, users then define an Import template, that references an Export, to which they can customize the output with some filters.

    Isatis.neo will use Fusion Exporter to fetch the values for an Import template into data tables in memory.

Borehole table types: required structural fields

The Fusion Import will require:

  • Always one and only one Tops/Collars table (coordinates of the borehole tops). This table will need to have at least:

    • A field that identifies the Hole ID
    • The borehole top X coordinate
    • The borehole top Y coordinate
    • The borehole top Z coordinate

  • Optionally, one and only one Deviations table (direction of the borehole). This table will need to have a least:

    • A field that identifies the Hole ID
    • A field that defines a Depth
    • A field that defines the Azimuth of the hole at that depth
    • A field that defines the Dip of the hole at that depth

  • Optionally, one or several Core Samples/Assay tables. These tables will need to have at least:

    • A field that identifies the Hole ID
    • A field From that defines the start depth of the assay interval
    • A field To that defines the end depth of an assay interval

  • Optionally, one or several Logs or Markers tables. These tables will need to have at least:

    • A field that identifies the Hole ID
    • A field that defines the Depth for that sample

Performance considerations

Due to the data access interface, all the data generated by the Export template is imported at once during the import, even for the variables that are not selected in the Isatis.neo import interface.

In order to improve the responsiveness of the import interface and the speed of the import itself, it is recommended to customize the Fusion Export template so it includes only the data fields that will be needed after the import. You can for example:

  • disable useless fields
  • exclude deviation/assay samples related to boreholes that are not referenced in the Tops table