Solution

OpenText Application Delivery Management Engineering & Support

VOTUM provides engineering expertise across the OpenText Application Delivery Management ecosystem, with particularly deep experience in ALM, ALM Octane and UFT.

Enterprise application delivery rarely depends on a single tool. Quality management, requirements, testing, release processes, automation, performance engineering and operational support often span multiple systems and integrations.

We help organizations operate, modernize and evolve business-critical software delivery platforms. OpenText ALM, OpenText ALM Octane and OpenText UFT are where our team has accumulated its deepest project experience. We also work with OpenText LoadRunner and OpenText PPM as part of wider ADM environments.

Our work covers the complete lifecycle: architecture and assessment, installation and configuration, upgrades, migration, integrations, test automation, platform operations and L1–L3 engineering support.

Contact us →

The OpenText ADM products we work with

  • Core expertise

    OpenText ALM / Quality Center

    Lifecycle and quality management

  • Core expertise

    OpenText ALM Octane

    Agile, DevOps and modern software delivery

  • Core expertise

    OpenText UFT

    Functional and regression test automation

  • Wider ADM experience

    OpenText LoadRunner

    Performance and load testing

  • Wider ADM experience

    OpenText PPM

    Project and portfolio management

OpenText ALM, ALM Octane, UFT, LoadRunner and PPM are products in the OpenText Application Delivery Management portfolio. VOTUM is an independent software engineering company; this page describes the team’s engineering work with these technologies.

Core expertise

OpenText ALM / Quality Center

Many organizations run requirements, test and defect management on OpenText ALM / Quality Center, in environments that have grown with multiple domains, customized workflows and integrations. We work on the platform itself and on everything connected to it.

  • ALM architecture and platform design
  • Installation and configuration
  • Upgrades and migrations, including database and repository migration
  • Authentication and enterprise SSO integration
  • Project and domain administration
  • Workflow customization
  • Integrations with surrounding enterprise systems
  • Requirements, test and defect management processes
  • Operational support, troubleshooting and root-cause analysis
  • Modernization planning

Operate, modernize or move on

There is no single right answer for an established ALM environment. Depending on its condition and where delivery is heading, an organization may:

  • continue operating a mature ALM environment
  • modernize ALM: upgrade the platform and rework its integrations
  • migrate gradually toward ALM Octane
  • run ALM and ALM Octane in coexistence

We help assess which of these fits, and then carry it out.

Project experience: Software Delivery Platform Transformation & Operations →

Core expertise

OpenText ALM Octane

ALM Octane supports Agile and DevOps delivery, with quality management built into the delivery pipeline. We work on Octane environments from architecture and deployment through day-to-day operation, and on the processes and integrations that make them useful to delivery teams.

  • Octane architecture and deployment
  • Spaces and workspaces: design and administration
  • Agile and quality processes
  • CI/CD integration
  • Authentication and identity integration
  • Enterprise integrations
  • Upgrades
  • ALM-to-Octane migration, including test assets
  • Operational support and troubleshooting

ALM and Octane in coexistence

Moving to Octane does not have to happen all at once, and it is not the right step for every ALM environment. Organizations often keep existing ALM projects, assets and processes where they work well, while newer teams and workflows move to Octane. We design and support hybrid ALM + Octane landscapes: which teams work where, how test assets and data are shared, and how both platforms are integrated and operated.

Core expertise

OpenText UFT

UFT automation pays off when it stays stable and maintainable as the applications under test change. We design and build UFT automation, connect it to ALM and to delivery pipelines, and keep existing suites running in complex enterprise test environments.

  • Automation architecture and UFT framework development
  • Reusable automation components
  • Functional and regression automation
  • Test data and test environment handling
  • ALM integration: automated execution and result management
  • CI/CD integration
  • Test maintenance and stabilization
  • Automation modernization
  • Troubleshooting complex enterprise test environments

Project experience: Software Delivery Platform Transformation & Operations →

Upgrading and modernizing OpenText ADM environments

An established OpenText ADM environment is rarely a single application. It may include:

  • multiple ALM domains and projects
  • repositories and databases
  • customized workflows
  • UFT libraries
  • identity integrations
  • third-party integrations
  • reporting platforms
  • CI/CD integrations
  • historical project data

Upgrading or migrating such an environment is an engineering project, not a simple product installation: every customization, integration and data set has to be analysed, carried over or redesigned, and validated.

Possible transformation paths

  • ALM to a newer ALM version
  • ALM to ALM Octane
  • ALM and ALM Octane in coexistence
  • UFT automation modernization
  • Archival of ALM and PPM data
  • Redesign of surrounding integrations

Which path fits, on its own or combined in phases, is decided per environment after an assessment.

ALM to Octane migration

Moving from ALM to ALM Octane is more than moving data. Projects, processes, test assets and integrations all need a place in the new platform, and teams need to keep delivering during the transition. We support the migration engineering and the transition design:

  1. Source environment assessment

    Domains, projects, customizations, integrations and data in the current ALM environment.

  2. Project and workspace mapping

    How ALM domains and projects map to Octane spaces and workspaces.

  3. Process and data mapping

    How existing workflows, entities and fields translate into Octane.

  4. Migration planning

    Scope, sequence, phases and cut-over for each group of projects.

  5. UFT asset migration

    Carrying UFT tests and their execution over to the new platform.

  6. Validation

    Checking migrated data, test assets and integrations before teams switch.

  7. Integration redesign

    Reworking CI/CD, identity and other integrations for Octane.

  8. Phased transition and coexistence

    Moving teams in phases, with ALM and Octane running side by side where needed.

  9. Post-migration support

    Support for users and for the platform after the switch.

Wider ADM experience

LoadRunner and performance engineering

We work with OpenText LoadRunner where performance testing is part of a wider ADM environment.

  • Performance-test architecture and execution environments
  • Scenario design and workload modelling
  • Integration with application delivery and quality workflows
  • Result analysis and troubleshooting
Wider ADM experience

OpenText PPM

OpenText PPM often sits alongside ALM in the same application delivery landscape. Our PPM work centres on its data and the systems around it.

  • Enterprise PPM environments and their integration with ALM
  • Historical project information
  • Data migration and archival
  • Surrounding databases and applications

Project experience: Data Archival and Migration for an Insurance Group →

How the OpenText ADM products fit together

In an ADM landscape, each product covers one part of application delivery:

ALM / Quality Center
Requirements, quality management and testing
ALM Octane
Agile, DevOps and modern software delivery
UFT
Functional test automation
LoadRunner
Performance testing
PPM
Project and portfolio management

Around them sit the systems they depend on:

  • Identity providers
  • Databases
  • CI/CD
  • Reporting
  • Cloud platforms
  • Custom integrations

Upgrades, migrations and incidents often cross these boundaries. VOTUM works across them instead of treating each OpenText product in isolation.

Managed OpenText ADM operations

An OpenText ADM landscape needs owners after go-live. We provide L1–L3 support for OpenText ADM environments, with 24/7 monitoring and support available under agreed SLAs.

L1
User intake, basic checks and first-level resolution
L2
Application and platform investigation, configuration analysis and remediation
L3
Deep technical troubleshooting, integration issues, code- and configuration-level fixes, root-cause analysis and permanent remediation

Incidents in an ADM landscape can cross several layers:

  • ALM
  • Octane
  • UFT
  • Authentication
  • Databases
  • Application servers
  • Integrations
  • Infrastructure

L3 engineering support is one of our core strengths: following an issue through these layers to its root cause and fixing it permanently. The scope of each engagement is agreed individually: in the software delivery platform case below, the managed-services scope covered L1–L2 user support under agreed SLAs.

Project experience: Software Delivery Platform Transformation & Operations →

Relevant project experience

Members of the current VOTUM team have delivered enterprise projects involving OpenText ADM technologies before VOTUM IT EOOD & Co KD was founded in 2024.

Managed Services & Operations

Software Delivery Platform Transformation & Operations

Transformation and long-term operation of a centralized enterprise software delivery and testing platform built around OpenText ALM and UFT, including platform consolidation, migration of legacy systems and managed platform support under agreed SLAs.

Data Migration & Cloud Architecture

ALM & PPM Data Archival and Migration

Migration and archival of historical OpenText ALM and PPM data into a new architecture using PostgreSQL and AWS RDS, keeping records and attachments accessible.

Related services

How we approach an OpenText ADM engagement

  1. Review the environment

    Products, customizations, integrations, data and processes, and what has to change.

  2. Scope and success criteria agreed before build

    Scope, priorities and success criteria are agreed with you before upgrade, migration or automation work starts.

  3. Deliver in controlled steps

    Upgrades, migrations and automation are delivered in phases, with results validated along the way.

  4. Operate or hand over

    We operate the environment under agreed SLAs, or hand it over with documentation and knowledge transfer.

Need support with an OpenText ADM environment?

Whether you are operating an established ALM platform, introducing Octane, modernizing UFT automation, working with LoadRunner, migrating PPM data or planning a broader ADM transformation, our engineering team can help.

Talk to VOTUM about your OpenText environment