7.1. Which applications are technically supported by the ENX network?
7.2. Which applications do OEMs and suppliers run using ENX?
7.3. What is the expected bandwidth requirement for the application XYZ?
7.4. Does the ENX network support VoIP?
7.5. How do I establish a tunnel?
7.6. Does the ENX network replace current EDI?
7.7. Does ENX replace OFTP?
7.8. Who can I contact on the manufacturer's side to establish an ENX connection?
7.10. Who can inform me about the ENX products of the certified ENX service providers?
Since ENX is only intended to serve as a transportation layer based on IP technology, every application that runs in an IP network is also supported by the ENX network.
- Digital Mock Up (DMU)
- Shared Data
- Filetransfer (based upon OFTP or OFTP2)
- Online-Access (Hyper-KVS, PDVS, PRISMA, SWANdirect, ...)
Logistics and Production
- Filetransfer (OFTP1, OFTP2, ...)
- Online-Access (EDIWeb, QTS, ...)
The current average bandwidth of the ENX suppliers (w/o OEMs) is 512k.
See FAQ 6.5. Which bandwidth do I need?
Your ENX Provider holds a form ready for this purpose.
You have to submit information concerning your ENX access and about your communications partner (above all, the "ENX registration number"). Your communications partner has to fill out a similar form for his provider. The "tunnel" itself is established by the providers (or only one, if both have accesses with the same provider).
FAQ 12.4. What is an "ENX tunnel" or "ENX connection"?
ENX does not replace applications like EDI. It just provides a common network transport method for multiple applications including EDI.
No. You have to consider the following differentiation: the ENX network is based on the IP protocol family, it therefore provides an IP transport layer. OFTP is a protocol used for the direct data transfer between two communication partners. It runs on different transport layers, one being the IP protocol supported by ENX.
Please check our ENX yellow pages and select the manufacturer you would like to communicate with.