Development · integration · reverse engineeringOstwald · Alsace · Remote projectscontact@dtouch.fr
Teams · flux · control

Offshore production & integration

Organize the schedule, visual sending queues, InDesign documents and their returns. Offshore production experience linked to the editorial platform and manufacturing.

01

Prepare

Data, templates, charter and files

02

Distribute

Partners, capacities and priorities

03

Reintegrate

Returns, versions and corrections

04

Validate

Control, BAT and activity monitoring

The stages of a controlled chain · principle diagram

Preparing a truly transmissible production

A start must contain the elements necessary for the work: structured texts, visuals, templates, charter, editing instructions and expected version. A field ambiguity or a missing file can affect several pages.

Preparing data at Reymann required controlling the numbering of products and the correct classification of guarantees, categories, varieties and prices. This experience nourishes an approach where the quality of the departure is verified before sending.

Coordinate variants and capabilities

The same program can combine several brands, formats and tariff versions. Production schedules followed by Patrice included in-house templates, parallel phases with partners, and common TAB timelines.

It is necessary to organize the dependencies: a first version can feed the next one; a format change may require a test on a page before adapting the file. The distribution of work takes into account capacities, schedules and return priorities.

Integrate partners into the image chain

The clipping reveals a second dimension of offshore: the automated circulation of files. Assignment to service provider, departure queue, transfer, return, integration and generation of overviews constitute different states.

The experiment focuses on engines and interfaces for tracking shipments and returns. Reconciliations between internal files, copies at the service provider and logs make it possible to identify what is really missing, without confusing a lack of return with a lack of sending.

Period documents & interfaces

Interfaces of the Reymann editorial channel, in their period version. These archives illustrate the journey of Patrice Salib, founder of Dtouch, within the agency.

Priority Tags in Planning TasksEnlarge
Priority Tags in Planning Tasks

Tasks can combine color and text tags to make priorities and shipments more visible.

Archive Reymann · interface extract · 09/11/2020
Railway and LGR double page in Rey’actif in 2011Enlarge
Railway and LGR double page in Rey’actif in 2011

The railway, the page states and the double page La Grande Récré can be viewed on the platform.

Archive Reymann · interface extract · 2011

Queues, sending visuals and InDesign feedback

The visuals to be processed were prepared and assigned to providers in queues. Sending and returning were automated, with partner load management. The file then had to be compared to its reference and reintegrated into the image chain.

The offshore organization also included sending InDesign documents and retrieving their returned versions. File replication — byte replication — accompanied these exchanges between workspaces. The schedule, the file transmitted and the version received had to remain consistent.

This continuity brings together several levels: the task to be carried out, the transfer queue, the file actually available and the result validated by the internal team.

Control quality and organize correction

A shared charter alone does not guarantee its application. Returns must preserve the layers, elements and structure of the templates, and then be compared to the instructions and modifications required.

The production cases encountered also concern alignments, updated logos, conditional blocks and photo library synchronization. The corrections must return in an identifiable circuit, with the correct file and the correct version, up to the proof.

Making activity visible

Management requires a view of current files, operations carried out and discrepancies. The Reymann scope included an offshore production and shipping schedule as well as activity reports by service provider.

In 2022, monitoring of image processing was based in particular on simple and detailed reports, with the number of operations per file, to reconcile activity and invoices. This is a concrete example of the integration between production, monitoring and management.

We apply this reading to distributed organizations: defining what is transmitted, how the work returns, who validates it and how an exception is handled.

From the work carried out to the monitoring of the activity

Monitoring of service providers was also based on the analysis of routing operations and their accounting. Developments included reconciling discrepancies and adding image names to billing reports.

Production information therefore had to remain linked to the service provider and the file after the files were returned. This traceability made it possible to understand what had actually been processed and to verify activity reports.

Understanding the exchanges

The files are circulating. The file retains their context.

Visuals and InDesign documents join partners with their instructions. Returns are reinstated and controlled in the production chain.

The files are circulating. The file retains their context.Enlarge the diagram
  1. 01

    Production file

    References and deadlines

    Images • INDD • instructions
    Preparation ▼
  2. 02

    Sending queues

    Visuals and documents

    Priorities • batches to be transmitted
    Organized shipments ↓
  3. 03

    Offshore teams

    Treatments and assembly

    Images • pages • corrections
    Return to production ▼
  4. 04

    File returns

    Byte replication

    Files and versions received
    Available files ↓
  5. 05

    Reintegration

    Bringing the folder closer

    Links • resources • documents
    Controlled result ▼
  6. 06

    Controls and planning

    Preparing for the next round

    Compliance • corrections • BAT
The files are circulating. The file retains their context.Enlarge the diagram
Functional diagram · synthetic reading of flows and control points.
Prepare

Associate the files, folder and work instructions.

Distribute

Distinguish between visual submissions and layout documents.

Reintegrate

Control returns and their use in documents.

A production experience

The Reymann route,
in detail.

How images, color, applications and partners fit together in the Rey’actif channel.

Explore this experience

Your job deserves
the right tools.

A specific need, a software to evolve, a project to frame.

Exchange on your project

Complementary expertise, the same high standards.