Industry

Energy Distribution Companies

Every item traceable from request to go-live: release, owner, test step

In distribution companies, investment, maintenance and field systems evolve continuously: departments report requests and bugs, contractor teams develop, test and ship. What costs the most time in that cycle is losing track of which release, which owner and which test stage each item is in across e-mails and meeting notes.

ARAS EDAŞ and KÇETAŞ have managed the investment and maintenance management system projects they run with Sotech in a shared HibritİK workspace since January 2024. The utilities’ teams open requests, bugs and revisions directly as tasks; the software team splits them into releases, develops, tests and ships them. Every item is tracked with owner, date, status and test step.

References from this sector

  • ARAS EDAŞARAS EDAŞOn HibritİK cloud
  • KÇETAŞKÇETAŞOn HibritİK cloud

This sector’s problems and the HibritİK answer

The problems organisations in this sector run into most often, and how HibritİK answers each one.

  1. 1Problem

    Hundreds of requests, improvements and bugs are scattered across e-mails and meeting notes

    With HibritİK

    Each item is opened as a task and broken into subtasks under release headings; the same work is viewed as a list, tree, Kanban board or Gantt chart.

  2. 2Problem

    The utility cannot see which release and which test stage an item is in

    With HibritİK

    Utility staff and the software team work in the same workspace, and the utility sees the progress of its own requests in real time.

  3. 3Problem

    Work marked as done is closed without being tested

    With HibritİK

    Tasks with an assigned tester wait for a test result, and tasks with a manager go to approval. Pre-go-live test items are tracked as separate tasks.

  4. 4Problem

    Decisions from revision and prioritisation meetings are not recorded

    With HibritİK

    Meeting decisions are linked to the relevant tasks as activities, and priority and date changes stay in the task history.

Success stories from this sector

Related features

Frequently asked questions

Can an external contractor team join the same workspace?

Yes. In the ARAS EDAŞ and KÇETAŞ project, utility staff and the Sotech team work in the same workspace, and each user sees only the data they are authorised for.

Do we need a separate tool for release-based planning?

No. Releases are opened as root tasks; requests, bugs and test items are planned as their subtasks and followed on the Kanban board or Gantt chart.

Does it run in the cloud or on our servers?

Both are possible. ARAS EDAŞ and KÇETAŞ use the HibritİK cloud; organisations that prefer to can install the same software on their own servers.

Other industries

Is your sector not on the list?

The modules work regardless of sector; try it free for 14 days with your own team, or tell us about your sector.