The Software and Systems Engineering Experts​
The Software and Systems Engineering Experts​
SmarterProcess logo

Contacts

SmarterProcess / ReqPro

ul. Antoniego Pajdaka 5/98
03-134 Warsaw, Poland
NIP : 8921405210
Regon : 146293701

About Products

About us

Home · Products · Integration Hub

Integrations · IBM ELM

IBM Engineering Integration Hub

Keeps IBM ELM in sync with Jira, Azure DevOps and other third-party tools, configured point and click.

Overview

What is IBM Engineering Integration Hub?

IBM Engineering Integration Hub, formerly IBM Engineering Lifecycle Optimization – Lifecycle Integration Adapters Tasktop Edition, connects IBM Engineering Lifecycle Management with third-party tools. Data and updates move between the tools automatically, so each team keeps working in the tool it already uses.

On the IBM side it connects IBM Engineering Workflow Management, IBM Engineering Requirements Management DOORS and IBM Engineering Requirements Management DOORS Next. On the other side there are connectors for agile, DevOps and IT tools such as Atlassian Jira, Microsoft Azure DevOps Server, Jama Connect, Polarion ALM, PTC Windchill and ServiceNow.

Integrations are set up point and click in a web designer, on top of one central model instead of a separate bridge for each pair of tools. The same model scales from one project to hundreds.

Relationships such as parent-child, validated-by and depends-on travel with the artifacts, so traceability holds across tools and stays ready for an audit.

Integration Hub is built on Planview Hub technology. Customers of Lifecycle Integration Adapters Tasktop Edition are entitled to it.

Your starting point

Where is your team starting from?

Find the line closest to your team. Each one shows what changes with Integration Hub.

From copy and paste between tools

  • Until now: Defects retyped from Jira into Workflow Management
    With Integration Hub:Jira issues and work items kept in sync
  • Until now: Status chased by email across tools
    With Integration Hub:Updates flow both ways automatically

From home-made scripts

  • Until now: A custom bridge for every pair of tools
    With Integration Hub:One central model and ready connectors
  • Until now: Scripts that break after each upgrade
    With Integration Hub:Connector versions listed in every release

From another requirements tool

  • Until now: Requirements in Jama or Polarion, work in ELM
    With Integration Hub:Requirements synchronised into DOORS Next with their links
  • Until now: Suppliers on a different tool
    With Integration Hub:Each team keeps its tool, data stays in step

From Tasktop Edition

  • Until now: Lifecycle Integration Adapters Tasktop Edition
    With Integration Hub:Entitled to Integration Hub, upgrade with your IBM account team

Capabilities

What your team can do in Integration Hub

Bidirectional synchronisation

Artifacts and updates stay in sync in both directions between IBM ELM and the other tool. You set it up point and click, without writing code.

IBM Engineering Integration Hub

Gateway integration

An event in one tool creates or updates an artifact in another, in one direction.

IBM Engineering Integration Hub

Enterprise data stream

Artifact data from every connected tool flows into one stream for reporting.

IBM Engineering Integration Hub

Relationships kept

Parent-child, validated-by, depends-on and blocked-by links move with the artifacts.

IBM Engineering Integration Hub

One model for all tools

Artifacts map to a central model, not to each tool pair, so new tools join faster.

IBM Engineering Integration Hub

Visual integration design

Routes, filters and state transitions defined in a web designer.

IBM Engineering Integration Hub

See every product we implement and support

All products
Product tour

See Integration Hub before your first demo

Integration landscape

01Integration landscape

Every repository and the integrations between them on one map: Jama, Azure DevOps, Workflow Management, DOORS Next and Jira.

Workflow Management and Azure DevOps

02Workflow Management and Azure DevOps

Two-way creation between Workflow Management stories and Azure DevOps stories, each field mapped through the central model.

DOORS Next and Jira

03DOORS Next and Jira

User story requirements in DOORS Next synced with Jira stories: summary, description, status, owner and links.

DOORS Next and Azure DevOps

04DOORS Next and Azure DevOps

Requirements in DOORS Next and stories in Azure DevOps, with priority, owner and IDs mapped in both directions.

One model instead of point to point

05One model instead of point to point

Each tool maps once to the central model instead of to every other tool.

Where Integration Hub runs

06Where Integration Hub runs

A web app on a Windows or Linux server with its own database. It reaches each tool over HTTPS through the tool API.

Where it fits

IBM ELM and the rest of your toolchain

Integrations

Atlassian Jira

Issues kept in sync with work items and requirements.

Microsoft Azure DevOps Server

Work items synced with Workflow Management.

Polarion ALM

Requirements exchanged with DOORS Next.

Jama Connect

Requirements and their links synced with DOORS Next.

ServiceNow

Service tickets linked to engineering work.

PTC Windchill

PLM items synced with IBM ELM artifacts.

GitLab Issues

Issues synced with Workflow Management work items.

OSLC

Open standard for links between IBM ELM tools.

Trusted in regulated industries

Our CustomersCustomers and Partners

Our clients build products under strict standards and regular audits. We supply licences, implementation, hosting and training.

Our clients build products under strict standards and regular audits. We supply licences, implementation, hosting and training.

Our Partners

We are a partner and reseller of these technology providers.

FAQ

Questions we hear before an Integration Hub project

Which licences do we need?

Integration Hub is a separate IBM product next to your ELM licences. Customers of Lifecycle Integration Adapters Tasktop Edition are already entitled to it. We size the licences from the tools and projects you want to connect.

Where does Integration Hub run?

On a server of yours, next to IBM ELM. It connects to each tool with service accounts, one to create and update artifacts and one to add comments.

We use Lifecycle Integration Adapters Tasktop Edition. What changes?

Integration Hub is the same product under its new name, and your entitlement carries over. We plan the upgrade and move your existing integrations.

Which tools can it connect?

On the IBM side Workflow Management, DOORS and DOORS Next. On the other side tools such as Atlassian Jira, Microsoft Azure DevOps Server, Jama Connect, Polarion ALM, PTC Windchill, ServiceNow and GitLab Issues. IBM adds connectors and versions with each release.

How is this different from an OSLC link?

An OSLC link points to an artifact where it lives. Integration Hub copies and updates the artifact in the other tool, so each team works in its own tool. Many teams use both.

Does traceability survive for an audit?

Yes. Relationships move with the artifacts and changes are recorded, so you can show where each item came from.

Talk to our consultants

Leave your details and we will get back to you, usually within one business day.

    We will only use your details to respond to your inquiry. Privacy policy