Connect DELMIA Works to EDI instantly
Join thousands of businesses moving EDI orders, invoices and fulfilment updates between DELMIA Works and their trading partners on XEDI, no manual re-keying.
No credit card needed ✦ Free EDI mailbox included
Getting started with DELMIA Works EDI
XEDI connects DELMIA Works, formerly IQMS, with customer EDI so releases and orders reach the shop floor and despatch documents go back carrying the traceability a manufacturing customer expects.
One managed platform, no custom code
XEDI maps DELMIA Works to your trading partners and validates every document, so data flows straight into the systems your teams already use.
ERP and the shop floor in one system makes demand accuracy structural
DELMIA Works is unusual in combining ERP with manufacturing execution, so what arrives as a customer document does not sit in an office waiting to be actioned. It informs scheduling, machine loading and material planning directly.
That raises the cost of a bad document. An incorrect quantity or a misread delivery date does not produce an admin correction, it produces a schedule built on the wrong assumption, and by the time it is noticed material has usually been consumed.
Traceability is the document nobody mentions until it is needed
Manufacturing customers, particularly in automotive and regulated sectors, expect to trace a delivered part back to a lot, a run and often a machine. DELMIA Works holds that detail because it is on the floor; the difficulty is getting it onto the outbound document in the form the customer's system will accept.
We hold each customer's requirements for that, so batch and lot references travel on the despatch rather than being assembled afterwards when somebody asks. A recall or a quality query then starts from a record rather than an investigation.
What your plant sees day to day
You get an EDI mailbox and a portal that behaves like an inbox, so customer demand is visible to planning immediately rather than arriving via somebody's mailbox.
What ships becomes the despatch advice built from the actual shipment, adjusted where quantities moved, carrying SSCC labels and the batch detail the customer requires, with the invoice following where they do not self-bill and its delivery confirmed in the dashboard.
The integration sits over that workflow and automates it, so releases reach DELMIA Works demand and shipping raises the outbound documents. Plants running at volume often take our API alongside for finer reporting.
Documents you can exchange
- Customer orders and releases landing against DELMIA Works demand
- Order acknowledgements returned to the customer
- Despatch advice and ASN messages from shipment
- Invoices, or reconciliation where a customer self-bills
- Quality and traceability data where a customer requires it
Built for DELMIA Works teams
Whoever owns DELMIA Works in your business, XEDI keeps EDI accurate and hands-off.
- Plastics, packaging and component manufacturers
- Automotive and industrial suppliers
- Production planners and schedulers
- Shipping and quality teams
- Plant systems administrators
DELMIA Works EDI document types
Automotive and industrial programmes vary considerably, but these are the usual flows.
| Document | What it carries | Direction |
|---|---|---|
| Delivery schedules and releases | Customer requirements over a horizon, landing against DELMIA Works demand rather than as discrete orders. | Customer to DELMIA Works |
| Purchase orders | Discrete demand where a customer orders rather than schedules. | Customer to DELMIA Works |
| Order acknowledgements | What the plant commits to producing and shipping against the requirement. | DELMIA Works to customer |
| Advanced shipping notices | Pack and label detail from the shipment, carrying batch and lot references where the customer requires traceability. | DELMIA Works to customer |
| Invoices | Raised where the customer does not self-bill, referenced to the shipment. | DELMIA Works to customer |
| Quality and traceability data | Lot, run and certificate detail where a customer's programme requires it alongside the goods. | DELMIA Works to customer |
How to connect DELMIA Works with EDI using XEDI
Because demand feeds scheduling directly, accuracy at the boundary matters more than usual. The sequence below is what onboarding looks like from your side.
-
01
We scope which DELMIA Works modules carry demand, production and shipping in your plant.
-
02
We build the mapping between each customer's documents and your part numbers, work orders and shipping records.
-
03
We configure validation so demand is checked before it reaches production scheduling.
-
04
We prove the order, despatch and invoice flows against what each customer requires and against how your plant runs.
-
05
You get demand reaching the floor accurately, and despatch documented to the customer's standard.
Ready to connect DELMIA Works?
Talk through documents, mapping, testing and go-live with XEDI.
Everything about DELMIA Works EDI
Common requirements
- DELMIA Works modules and plant scope
- Part number and customer part cross-references
- Packaging and label configuration
- Traceability requirements by customer
- Which customers you supply
What we need from you to build it
Only what we cannot hold for you. Customer programme requirements, including label formats, are already ours.
- DELMIA Works scope
- Which modules carry demand, scheduling and shipping, and which plants are involved.
- Part cross-references
- Customer part numbers against your own, including revisions, since a superseded part is a common cause of rejection.
- Packaging and labelling
- Pack configuration and the label format each customer's receiving plant scans.
- Traceability requirements
- What batch, lot or certificate detail each customer expects to travel with the goods.
- Which customers you supply
- The programmes in scope now and next. Their formats and label requirements are already ours.
Why suppliers choose XEDI for DELMIA Works
- Your customers' programmes are usually connected already, so a new one does not begin with establishing connectivity.
- Demand is validated before it reaches scheduling, so the plant does not plan against a bad document.
- Batch and lot detail travels on the despatch rather than being assembled when somebody asks for it.
- Label formats are held per customer programme, which is what keeps a delivery from failing at a receiving plant.
- A new customer programme is our build rather than a project competing with production.
- If a customer's plant raises a problem, it comes to us and is fixed before it affects a line.
Does this handle releases as well as purchase orders?
Yes. Many DELMIA Works customers supply programmes that send schedules and releases rather than discrete orders, and those land against demand as releases rather than accumulating as separate orders.
Can traceability data travel with the despatch?
Where a customer requires it, yes. Batch, lot and certificate detail is carried on the outbound document in the form their system accepts, rather than being assembled later during a query.
Is this the same as IQMS?
Yes. IQMS became DELMIA Works under Dassault Systèmes. The modules in play are confirmed at the start, since deployments differ by plant.
Plan your DELMIA Works EDI setup
Everything you need to scope, map and go live with DELMIA Works, in one place.