Sustrack Integration, Custom Software and On-Premise Installation

Sustrack's four modules work from the same shared data and receive it in three ways: through the interface, by bulk upload, or through a connection to the systems you already run. System connections, custom development tied to the modules and on-premise installation are not offered as off-the-shelf features; they are run as projects after your needs have been examined. None of them is mandatory; the modules can be used in the cloud, through the interface and bulk upload.

When You Need It

Keying data in through the interface is enough for a small number of sites and periodic data. Bulk upload suits cases where the data is already kept tidily in tables and transferred once per period. A system connection is built where there are many sites, high data volumes or frequent updates, to bring data straight across from enterprise resource planning (ERP), manufacturing execution, energy monitoring, purchasing or supplier management systems.

If transferring the same data by hand every period creates repeated work for your IT and process teams, if your internal processes need a set-up that differs from the standard flows, or if your corporate data policy requires systems to run on your own infrastructure, one of the project types on this page comes into play.

Scope

The project types apply to all four modules: S-CBAM, S-ETS, S-LCA and S-EUDR.

System connection. Covers transferring the records the modules need from your source system into Sustrack; production and consumption data, product and raw material records or supplier information can fall within this scope. Which records are transferred is decided together at the start of the project. Your source system may be an off-the-shelf package or a system developed specifically for your company; how the connection can be built is decided once your source system has been examined.

Custom software tied to the modules. Covers adapting Sustrack modules to your company's internal processes — for example, shaping a reporting flow around your internal approval steps, or passing module outputs to an in-house system. Custom development is always tied to a Sustrack module.

On-premise installation. Sustrack is a cloud-based platform. For organisations whose data policies require them to run their systems on their own infrastructure, on-premise installation of Sustrack is assessed as a project. The scope of the installation, the infrastructure requirements and the update and maintenance model are agreed together in conversation.

The Process

  1. Reviewing your needs and existing systems. The type of project, the data to be transferred or the flow to be adapted, and your current infrastructure are established.
  2. Setting the method and scope. How the connection, development or installation will be carried out, and its limits, are put in writing.
  3. Implementation. The connection rules are defined, the development is done or the installation is carried out.
  4. Testing. The result is checked together against one period of data.
  5. Go-live. The work is put into live use and monitored.

The Outcome

At the end of the project, the selected records transfer from your source system under defined rules, the adapted flows work alongside your internal processes, or Sustrack is ready for use on your own infrastructure. The scope and limits of the project are set out in writing at the start.

There is no list of ready-made connectors. The duration and cost of a project depend on its type, the structure of your source systems, the data volume and, for on-premise installation, the infrastructure requirements.

Contact

Tell us about the systems you use, your internal processes and your infrastructure requirements; let us assess what you need together.