Technologies

Technologies we know from practice

We work on process visualisation and supervision platforms used across industry. For each one we say what we actually do with it and what supports that.

01

Platforms

Four families of tools we use in engineering and in training.

    • WinCC
    • TIA Portal
    • SIMATIC STEP 7

    What it is for

    Environments for process visualisation and control-system engineering, widely used across industry.

    Our competence

    HMI applications, server and client configuration, synoptic screens and engineering work in automation projects.

    What it rests on

    WinCC and SIMATIC STEP 7 — hands-on project work. TIA Portal is within the team’s competence.

    • InTouch
    • System Platform
    • Historian

    What it is for

    A process visualisation and supervision platform with an application layer and process-data historisation.

    Our competence

    Work with InTouch Application Server in a production environment.

    What it rests on

    Hands-on project work, backed by four certificates.

    Certificates

    • CSI AVEVA InTouch for System Platform
    • CSI AVEVA InTouch HMI 2023 Exam
    • CSI AVEVA Application Server 2023 Exam
    • CSI AVEVA Historian Server 2023
    • Ignition

    What it is for

    A SCADA platform built around a single application server, with clients launched on different workstations.

    Our competence

    A platform within our competence, confirmed by a certificate.

    What it rests on

    Practical work plus a named vendor certificate.

    Certificate

    • Ignition 8.3 Credential
    • zenon

    What it is for

    Software for process visualisation and supervision, used in energy and manufacturing among other sectors.

    Our competence

    A platform within the team’s competence.

    What it rests on

    Team competence. We do not name a certificate here.

How much documented experience stands behind each platform differs, and we say so plainly. The full list of certificates is kept on the About page.

02

Choosing a platform for a project

We do not rank platforms. The context decides, not a vendor preference.

  • Existing infrastructure

    Usually what already runs on site decides it — controllers, network, existing applications and the standards in use.

  • Scope and scale

    A single operator station calls for a different tool than the full visualisation of a production line.

  • Integration with the rest of the system

    How data is exchanged with the automation and the higher layer often matters more than screen features.

  • Maintenance and further work

    Who will maintain the application, and how often it has to change, genuinely affects the choice.

If the platform is already chosen, we work in it. If the choice is still ahead of you, we can go through what each option means for maintenance and for extending the application later.

03

The same technologies in training

The knowledge we teach comes from working on these same platforms. That is why sessions are run as workshops, on examples from real applications rather than detached exercises.

Tell us what you run — we will match the support to it.

If the system is already live, a short conversation about what has to change is usually enough.