Hub - MBI - header

Hub - MBI - header

Tasktop Hub

Model-Based Integration

Get the sophisticated integration you want, without the overhead.

Hub - MBI - left

Hub - MBI - left

Most integration solutions don’t scale.

70% of large-scale software delivery organizations integrate at least four artifact types across a minimum of three tools. Yet native integrations and plugins are a hassle to manage as you expand to tens of teams and hundreds of projects.

Hub - MBI - center

Hub - MBI - center

Point-to-point field mapping has massive overhead costs.

Mapping—and then maintaining—hundreds of project pairs is draining your team’s resources. Every subsequent change to fields, values or workflows needs to be updated in tens or hundreds of places, such that you lose track.

Hub - MBI - right

Hub - MBI - right

Every integration becomes a snowflake.

With nothing to standardize the organizational definition of what flows between tools, per artifact type, every integration is set up differently. Knowledge and understanding of the integration landscape comes and goes as your staff changes.

model based integration benefits

Hub - Model Based Integration Page - Integrate using models. Standardize what flows.

Integrate using models. Standardize what flows.

Models standardize the information exchanged by integrations into archetypes of business value. They express the organizational consensus of the data package that needs to flow, for each artifact type.

  • Models are defined upfront and in advance on Tasktop Hub to prevent ad-hoc, subjective or arbitrary data selection and field mapping.

  • While the full data set will remain in the source repository to support its users, any data that flows out of the repository en route to another destination will be aligned to the model.

  • Collections of projects are mapped to the model to eliminate the overhead of point-to-point mapping.

Hub - ModeL Based Integration page - Deploy fast. Implement changes even faster.

Deploy fast. Implement changes even faster.

Model-based integration reduces setup time by 75% and maintenance overhead by 90%. How?

  • Models eliminate the need to map the fields and values of each project pair individually, which can take up to three hours per pair. At enterprise scale, we’re talking hundreds of hours.

  • With Tasktop, bulk project collections are mapped to a model. When down the line you need to add a project, modify a field mapping, or even switch out a tool, you do so through the collection and model—not individually.

  • Unlike templates (which merely provide a pre-populated shortcut for point-to-point mapping), models completely isolate relationships between your tools and can be reused in multiple integrations.

Tasktop Hub provides curated out-of-the-box models to help you get started quickly.

Hub - Model Based Integration page - Switching tools? No sweat.

Switching tools? No sweat.

The DevOps toolchain is always changing and evolving, as organizations experiment and then adopt new best-of-breed tools.

Models minimize the impact of those changes on your integrations. Tools are mapped to the central model, not to each other. So even when you switch out a tool, half your setup is still intact. Simply add the new tool and map it to the model, and you’re done.

Integration Hub Enterprise Data Stream

Hub - Model Based Integration Page - Simplify cross-tool reporting. Normalize data-on-the-fly.

Simplify cross-tool reporting. Normalize data-on-the-fly.

Metrics need to be based on clean, normalized, well-architected data.

Models serve to extract “messy” data from a large variety of teams, tools, products and workflows and clean it up to represent things you want to measure.

Aligning repository data to models in near real-time pre-optimizes it for all reporting purposes and reduces the effort to create those reports and derive real insight.

Subscribe to Updates to "Hub - Model Based Integration"