972-836-7750 Request a Demo Talk to an EDI/API Expert Search
    See all results Browse the sitemap Tip: press / to search from any page
    Talk to an EDI/API Expert Request a Demo Call Sales 972-836-7750

    B2B communication protocols

    OFTP2: secure file transfer for the automotive industry

    OFTP2 is the ODETTE File Transfer Protocol used by European automotive manufacturers and suppliers to exchange delivery schedules, dispatch advice, invoices and engineering data. ECOM sets up OFTP2 connections, certificates and receipts, and maps the files they carry.

    Published by
    ODETTE; described in IETF RFC 5024
    Transport
    TCP/IP, with TLS
    Security
    TLS, file signing and encryption
    Receipts
    Signed End-to-End Responses (EERP)
    Talk to an EDI/API Expert
    Where OFTP2 fitsA hub diagram: OEMs, tier suppliers, logistics providers and engineering partners exchange OFTP2 files with the ECOM B2B gateway, which handles TLS sessions, signed and encrypted files and signed receipts for the ERP, production planning, warehouse and engineering systems.Where OFTP2 fitsPartners, the ECOM gateway and your systemsAUTOMOTIVE PARTNERSOEMsTier suppliersLogistics providersEngineering partnersYOUR SYSTEMSERPProduction planningWarehouse (WMS)EngineeringECOM B2B gatewayOFTP2TLS sessionsSigned, encrypted filesSigned EERPs
    Where OFTP2 fitsA hub diagram: OEMs, tier suppliers, logistics providers and engineering partners exchange OFTP2 files with the ECOM B2B gateway, which handles TLS sessions, signed and encrypted files and signed receipts for the ERP, production planning, warehouse and engineering systems.Where OFTP2 fitsPartners, the ECOM gateway and your systemsAUTOMOTIVE PARTNERSOEMsTier suppliersLogistics providersEngineering partnersECOM B2B gatewayOFTP2TLS sessionsSigned, encryptedfilesSigned EERPsYOUR SYSTEMSERPProduction planningWarehouse (WMS)Engineering

    Automotive partners exchange OFTP2 files with the gateway; their contents are mapped to your systems.

    Expand diagram Download SVG

    Overview

    What OFTP2 is

    OFTP was created by ODETTE, the European automotive industry's standards organization, for exchanging files between manufacturers and suppliers. OFTP2 brought it to the internet, adding TLS on the session, signing and encryption of files, compression, and signed receipts.

    Each party is identified by ODETTE identifiers for its station and its files. When a file has been delivered and processed, the receiver returns an End-to-End Response (EERP), which can be signed to give proof of delivery.

    Where businesses use it

    • Automotive supply chains

      Delivery schedules, dispatch advice, invoices and self-billing between OEMs and suppliers.

    • Engineering data

      Large CAD and engineering files exchanged with partners.

    • European manufacturing

      Other industries that adopted OFTP2 from automotive practice.

    How it works

    How an OFTP2 transfer works

    The initiating station opens a TCP connection, typically over TLS, and the two sides exchange start-session commands with their identifiers and passwords and agree capabilities such as compression and restart. The sender then transfers the file, which may itself be signed, compressed and encrypted.

    The receiver acknowledges the transfer, processes the file, and returns an EERP, signed if agreed. OFTP2 can restart an interrupted transfer from where it stopped, which matters for very large files.

    An OFTP2 session with a signed receiptA sequence diagram: the sender opens a TLS session, exchanges start-session commands, sends a signed and encrypted file, the receiver confirms the transfer, processes the file and returns a signed EERP.An OFTP2 session with a signed receiptSession, transfer, end-to-end responseSender stationReceiver stationTCP connection with TLSStart session: identifiers, capabilitiesSigned, encrypted fileTransfer confirmedSigned EERP (end-to-end response)
    An OFTP2 session with a signed receiptA sequence diagram: the sender opens a TLS session, exchanges start-session commands, sends a signed and encrypted file, the receiver confirms the transfer, processes the file and returns a signed EERP.An OFTP2 session with a signedreceiptSession, transfer, end-to-end responseSender stationReceiver stationTCP connection with TLSStart session: identifiers,capabilitiesSigned, encrypted fileTransfer confirmedSigned EERP (end-to-endresponse)

    TLS protects the session. File signing and encryption protect the file. The signed EERP proves it was received and processed.

    Expand diagram Download SVG

    In depth

    OFTP2 in practice

    • Identifiers

      Station and file identifiers, with session passwords, are agreed with each partner.

    • TLS sessions

      The connection is protected with TLS and certificates.

    • File signing and encryption

      Files can be signed and encrypted independently of the session, so they stay protected after delivery.

    • Certificates

      Many partners require certificates from a recognized authority; renewals are planned before expiry.

    • Signed receipts

      Signed EERPs give proof of delivery and processing.

    • Restart and large files

      Interrupted transfers resume from the last confirmed point.

    In practice

    Example: delivery schedules from an automotive OEM

    A supplier receives delivery schedules from an OEM by OFTP2 and sends dispatch advice back.

    Example: delivery schedules from an automotive OEMFive steps: set up the OFTP2 link, receive delivery schedules, return a signed EERP, map the schedules to the ERP, and send dispatch advice back by OFTP2.Example: delivery schedules from an automotive OEMA practical example, step by step1Set up the linkIdentifiers,certificates andconnection detailsare exchanged.Step 12ReceiveschedulesThe OEM sends VDAor EDIFACTdelivery schedules.Step 23Return EERPA signed receiptgoes back afterprocessing.Step 34Map to ERPSchedules updateplanning in the ERP.Step 45Send dispatchadviceShip notices go tothe OEM by OFTP2.Step 5
    Example: delivery schedules from an automotive OEMFive steps: set up the OFTP2 link, receive delivery schedules, return a signed EERP, map the schedules to the ERP, and send dispatch advice back by OFTP2.Example: delivery schedulesfrom an automotive OEMA practical example, step by step1Set up the linkIdentifiers, certificates and connectiondetails are exchanged.Step 12Receive schedulesThe OEM sends VDA or EDIFACTdelivery schedules.Step 23Return EERPA signed receipt goes back afterprocessing.Step 34Map to ERPSchedules update planning in the ERP.Step 45Send dispatch adviceShip notices go to the OEM by OFTP2.Step 5

    OFTP2 carries the files; the VDA or EDIFACT messages inside are mapped to your ERP.

    Expand diagram Download SVG

    Connections

    How OFTP2 connects your business

    • Automotive partners

      OEMs and suppliers that require OFTP2.

    • Message standards

      VDA, ODETTE and EDIFACT messages carried in the files.

    • ERP and planning

      Schedules and dispatch data flow to and from your systems.

    • Engineering

      Large engineering files reach the right teams.

    ECOM

    How ECOM supports OFTP2

    ECOM supports OFTP2 with dedicated implementation, mapping, communication and support teams, and with specialists who know the industries your partners work in.

    • Implementation team

      Plans the OFTP2 setup with you, configures it on the gateway and runs the tests with your partners and systems.

    • Mapping team

      Builds and maintains the maps, code conversions and validation rules between partner data and your applications.

    • Communication team

      Sets up and monitors partner connections, certificates, keys and credentials, and coordinates changes with each partner.

    • Support team

      Watches the flows, investigates failed or missing documents, and works the issue through with you and your partner.

    For OFTP2 in particular

    • OFTP2 setup with identifiers, TLS, certificates and EERP handling.
    • Maps for the VDA, ODETTE and EDIFACT messages the files carry.
    • Partner onboarding for OFTP2: exchanging connection details, testing in both directions and confirming the go-live date with each partner.
    • Monitoring of every connection, with alerts for failed, missing or unacknowledged transfers.

    Frequently asked questions

    What is the difference between OFTP and OFTP2?

    OFTP2 adds internet-grade security: TLS sessions, file signing and encryption, compression and signed receipts, and it is designed for use over the internet.

    What is an EERP?

    An End-to-End Response is the receipt the receiver sends after processing a file. When signed, it proves the file was delivered and accepted.

    Do we need special certificates?

    Many automotive partners require certificates from a recognized certificate authority. ECOM confirms each partner's requirement and manages renewals.

    What messages does OFTP2 carry?

    Any file. In automotive these are usually VDA, ODETTE or EDIFACT messages, and sometimes engineering data.

    Related pages

    Talk to an EDI/API Expert

    Tell us which partners, systems and OFTP2 requirements you are working with. An ECOM specialist will review them with you and outline the setup, the maps and the tests.

    Talk to an EDI/API Expert Request a Demo