From multilingual datasheets to a broader publishing workflow

A working multilingual start

Heras did not begin by replacing its complete publishing operation. The first step was deliberately focused: use existing product data from Virto to generate datasheets through an automated multilingual document workflow.

The required product selection and briefing are prepared in Virto. The corresponding structured product data is then supplied to 2imagine Pulse, which combines it with the approved document template and generates the required datasheets in six languages.

This provides Heras with a limited but operational foundation. Product information remains managed in its existing data environment, while the repeatable production of language versions is handled through a controlled publishing workflow.

Expanding the publishing scope

The working datasheet flow has now led to a signed expansion for two brands: Heras Mobile and Hela. The new scope adds product brochures and product books to the existing datasheet process.

For each brand, all three publication types will be generated in six languages. Together, this creates six publishing processes: one process per output type and brand, each supporting the agreed language versions.

These publications form the signed implementation scope. The additional brochure and product-book flows are entering implementation and are therefore not yet presented as completed results.

How the expanded workflow will operate

The expanded setup combines Virto, Pulse and BrandPortal, with each system supporting a distinct part of the publishing process.

Virto remains the starting point for selecting products and briefing the required publication. Pulse uses the supplied data to automate structured product pages. BrandPortal provides the flexibility needed to add and manage non-product pages that cannot be generated directly from product data.

This combined approach automates the structured and repeatable parts of each publication without removing the flexibility required for introductions, navigation pages and other editorial content.

From first output to phased completion

The expanded project will not introduce all six publishing processes simultaneously. Implementation begins with one output type that can be tested and validated before the remaining flows are completed in phases.

Timing

The first output is targeted within approximately four weeks of project start. The remaining publication flows will then be completed in phases, aligned with Heras’ availability and approval process.

This first milestone is treated as a proven concept: an objective validation of the implemented workflow rather than a new commercial approval round.

Project approach

During implementation, Heras and/or Innovadis participate in two fixed technical meetings of thirty minutes each week. The 2imagine team works in two-week sprints. Where custom development is required, delivery can also be aligned with a scheduled platform release.