Solution Documentation - InterForm Automotive Solution

Solution Documentation - Interform Automotive Solution

Interform Automotive Package

Interform Automotive Solution is an output management solution developed specifically for the automotive industry. It extends the core functionality of InterformNG2 with a comprehensive collection of industry-compliant templates, workflows, and maintenance services.

Template Packages

The Automotive Package is divided into two main types of template sets:

Base Package

OEM-Specific Package

The Automotive Package is divided into two main types of template sets:
Base Package
Contains OEM-independent templates based on international automotive standards and guidelines from the following associations:
  1. AIAG (North America)
  2. Odette (France, used internationally across Europe)
  3. VDA (Germany, used internationally across Europe)
OEM-Specific Package
Include templates tailored for individual Original Equipment Manufacturers (OEMs) and Tier-1 suppliers (first-tier suppliers delivering directly to OEMs).
These packages extend the base package with layouts, data structures, and logic specific to each manufacturer or supplier.

Customers can combine the base package with one or more OEM-specific packages to create a customized template package that fits their requirements.
The generic templates are fully prepared and ready to use; typically, only the company logo and certain data references need to be adapted in the shared sub-templates.
Our generic templates are based on an internal, default-xml-format. 

How to Obtain the Package and Maintenance

Maintenance and Updates

Version Control and Consistency

The Interform Automotive Solution Package can be obtained directly from Interform A/S or through an authorized Interform partner.
If you are interested in acquiring the package, please contact us at sales@interform400.com
Maintenance and Updates
The Automotive Solution includes active maintenance as part of the package.
This means that when any official standard or OEM requirement changes, Interform will proactively:
  1. Create an updated version of the affected templates
  2. Validate and release the new version to all customers under maintenance
Customers are encouraged to notify Interform if they receive new or updated specifications from OEMs or partners, to ensure updates are processed as early as possible.
Version Control and Consistency
All templates and configurations are maintained in a centralized internal repository.
This ensures that:
  1. There is always one approved version of the package
  2. Updates are consistent and quality-assured
  3. All customers benefit from the latest improvements and compliance updates

Purpose

This documentation provides technical information about the structure, configuration, and usage of the Interform Automotive Solution. It is intended for administrators, developers, and integration partners who implement or maintain the solution in customer environments.
Info
This documentation is intended as a combined resource. It serves both as a technical implementation guide and as a functional guideline for users. While it provides detailed steps for setting up the InterformNG2 Solution, it also includes functional explanations to support users in understanding and working with the solution. The guide does not replace project-specific requirements or customer-specific adjustments, which may be necessary depending on the individual environment and business needs.

Technical Description

Approach

Technical Process Overview

Approach
In general the customers ERP/WMS will be connected to InterformNG2. E.g. the connection between SAP and InterformNG2 takes place via the XML files created by SAP, which are sent via webservice when printing is approved. The XML files are then converted into the target format by InterformNG2 and made available as PDFs or physical printouts (ZPL/PCL).

Technical Process Overview
ERP -> REST (XML) -> Interform -> Output 
StepDescriptionDetails
ERPUser triggers a job in the ERP
REST (XML)ERP sends an XML via REST to InterformNG2.
<Data>
    <Header>
        <User/>
        <Copies/>
        <ShipmentStatus/>
        <Type>OTL14B</Type>
        <Location/>
        <ShipToAE/>
        <FormType>STANDARD</FormType>
        <ShipFromAE/>
        <Subtype>A5</Subtype>
        <Tray/>
        <AccountingEntity/>
        <LanguageCode/>
        <CustomerID/>
        <LabelType/>
        <Printer>BE10_PCLTest</Printer>
        <Reference/>
        <Component/>
        <Client>VOLVO_CARS_EU</Client>
        <OutputType>PRINT</OutputType>
        <Tpltype/>
        <ShipToID/>
        <CustomerAE/>
        <Tenant/>
        <Filename/>
        <HeaderLine/>
    </Header>
...
InterformNG2Interform processes the XML file and selects the process to start based on the XML contents.
OutputDepending on the contents of the XML file, the XML is converted to a PDF or physically printed.

Prerequisites

Standard XML-Format

Guidelines for Achieving the Standard XML Format

When Your ERP Cannot Provide the Standard XML Format

Example – VDA4902 Label Definition

Standard XML-Format
The Interform Automotive Solution Package is designed for quick and seamless implementation. It is based on a defined XML standard, allowing you to go live in minimal time.

To use the package, your system must provide data in the InterForm standard XML structure. When this structure is used directly from your ERP, no programming, no template creation, and no data mapping inside InterForm are required for the standard output.

This documentation includes example files (XML and PDF) as well as a reference spreadsheet illustrating the standard XML format and structure.
Guidelines for Achieving the Standard XML Format
Implementing the package is straightforward when approached in a structured manner. Based on proven best practices, we recommend the following steps:
  1. List all templates and labels in scope
    Identify which document types and labels are relevant for your setup.
  2. Review the required data for each label
    Understand which information each label needs to be populated correctly.
  3. Prepare a mapping table or spreadsheet
    Map your ERP data fields to the Interform standard XML elements.
When Your ERP Cannot Provide the Standard XML Format
In some cases, the ERP system cannot output data in the required XML structure. This may happen if the system provides data in spool formats, JSON, CSV, or other XML layouts.
InterFormNG2 offers flexible tools to handle these scenarios. Your data can easily be transformed into the Interform standard XML format using one of the following methods:
  1. Built-in Transformation Designer
    Create and manage data transformations directly inside InterFormNG2 using an intuitive graphical interface - no external tools required.
  2. External XSLT Transformation
    If preferred, you can use your own XSLT files to convert data into the Interform XML structure before it reaches the template or workflow.
Info
If you prefer not to handle the transformation setup internally, Interform or one of our certified partners can provide this transformation service for you, ensuring a smooth and efficient implementation process.
This flexibility ensures that even non-standard or legacy ERP outputs can be fully integrated without changes to the source system.

Example – VDA4902 Label Definition

Example – VDA4902 Label Definition

Element
Example Value
Clientvda_eu
TypeVDA4902
SubtypeA5
LabelIndicatorS

Field on
 the label		DescriptionField in ERPERP descriptionInterForm (XML)InterForm comment
1Consignee./Receiver/Address/Name and ./Receiver/Address/City
2Dock/Gate/Warehouse address./Receiver/EDIShipTo
3Advice note numbernormalize-space(./PackingSlipNumber[not(@*)])
4Supplier Address./Supplier/Address/Name
5Net weightnormalize-space(./NetWeight)
6Gross weightnormalize-space(./GrossWeight)
7Number of boxesif (./LabelIndicator)='S' then normalize-space(./NumberofPackages) -> if (./LabelIndicator)='M' ./NumberOfPackages[@type='HandlingUnit']
8Part numbernormalize-space(./CustomerItemNumber[not(@*)])
9Quantitynormalize-space(./Quantity[1])
10Descriptionnormalize-space(./ItemDescription)
11Logistics referenceif (./LabelIndicator)!='G' then normalize-space(./ItemNumber[not(@*)])
12Supplier IDnormalize-space(./Supplier/SupplierNumber[not(@*)])
13Dateconcat('D',./ShipmentDate[not(@*)])when shipment date = ' ', then deliverydate or manufacturedate
14Engineering change./EngineeringChangeLevel
15Package No. (M)normalize-space(./ContainerNumber[not(@*)])
16Batch numbernormalize-space(./BatchNumber[not(@*)])
17Plant address

Processes (Workflows)

REST_Automotive

Master

Customer_Variables

Master_Template

Master_Output_Template

The Interform Automotive Solution is based on the following workflows.
REST_Automotive
  1. Receives data from the ERP
  2. Saves the XML request to the internal library
  3. Splits payload (when several labels are included in one XML)
  4. Calls subworkflow "Master"


Master
  1. Calls subworkflow "Customer_Variables"
  2. Sets several variables
  3. Calls subworkflows "Master_Template"


Customer_Variables
  1. Sets several variables (also customer-specific)


Master_Template
  1. Calls subworkflow "Master_Output_Template"
  2. Returns a PDF for previewing and storage in the ERP


Master_Output_Template
  1. Selects the Output Channel (mail, pdf, print)
  2. Sends the document to the printer

Interform Automotive Solution – Detailed Process

Template-Selection

Standard vs. Modifications

Individual Customer Labels

Template-Selection
The template selection is based on several contents of the xml-header.
<Data>
    <Header>
        <User/>
        <Copies/>
        <ShipmentStatus/>
        <Type>OTL14B</Type>
        <Location/>
        <ShipToAE/>
        <FormType>STANDARD</FormType>
        <ShipFromAE/>
        <Subtype>A5</Subtype>
        <Tray/>
        <AccountingEntity/>
        <LanguageCode/>
        <CustomerID/>
        <LabelType/>
        <Printer>BE10_PCLTest</Printer>
        <Reference/>
        <Component/>
        <Client>VOLVO_CARS_EU</Client>
        <OutputType>PRINT</OutputType>
        <Tpltype/>
        <ShipToID/>
        <CustomerAE/>
        <Tenant/>
        <Filename/>
        <HeaderLine/>
    </Header>
...

Template Name: Defined by the Type and Subtype
Directory/Client: Defined by the Client
In the workflow these details are processed and written into variables.


Standard vs. Modifications
With the initial deployment of the Interform Automotive package, the templates are delivered in the folder “std”:


If you want to modify a standard-template (e.g. due to specific requirements from a customer), you must not change the template in the “std” folder.
You will pick the std-template, open it and save it to the folder “mod” with the same name:




Now you can make adjustments as preferred to the mod-template. Let’s say you want to change the contents of the VDA4902 templates. You open the std-one, save it to the mod-folder. Then you edit it. As the templates are build with so called template-components (similar to Interform400-suboverlays), the same logic applies to the components. You don’t change a std-components, but first save the component to the mod-folder and then make the adjustments inside the mod-component:


Right-click on the component and save it as a component in the mod-folder.




Interform will warn you when you try to edit a component. This is a sign to check, whether you are editing a mod-component or a std-one.


The workflow always tries to find a template in the mod-folder. If no modified template is found, it will fetch the std-template. This logic secures, that we can deliver and deploy new standards without overwriting modified resources.


The solution introduces a new approach to output management, with pre-integrated components and pre-installed layouts and configurations. This ensures a fast, efficient implementation and smooth ongoing operations.
Individual Customer Labels
In the folder mod\individual_eu you can create all individual customer-specific labels. While the logic for the template name is the same, there is not std-fallback. This means you can make adjustments to the template as preferred.

Change Requests and Support

In the case of the following change requests, you should contact Interform:
  1. Additional forms/labels are needed
  2. Change in optics, contents of the forms/labels
  3. Change of logic (processes, e-mailing, etc. desired)
  4. Change of storage paths, file names, content XML, etc.
Change requests and support cases can be reported via our Help Center: https://helpcenter.interform400.com/portal/en/newticket
If you do not yet have access to the portal, you can sign up using the following link: https://helpcenter.interform400.com/portal/en/signup