ENGDAT
ENGDAT is a defined workflow for the exchange of technical documents, primarily in the automotive industry. The current specification is V3.1, the ENGDAT module also supports the older version V2.x. Further information about ENGDAT can be found at www.vda.de/en and www.sasig.com. In addition to the exchange of technical documents, contact information can also be exchanged - these are so-called ENGPART messages, which are transmitted in an ENGDAT message. The current version of ENGPART is 4.1 and is supported by the ENGDAT module.
In general, a V3 ENGDAT message is distinguished by Conformance Classes (CC).
CC1: Request of documents (further differentiated in a and b).
CC2: Sending documents without additional information about contained files.
CC3: Sending documents with additional information about contained files.
CC4: Confirmation of an incoming message (further differentiated in a and b).
CC5: Does not exist as a message per se. The term is used to express that a software supports CC1 to CC4. This is given in the Lobster ENGDAT module.
Basic requirements
The ENGDAT module from Lobster must be licensed.
OFTP connection successfully tested via partner administration.
Parameters of the remote system are known.
The appropriate user right must be set. See the following section.
Adjust user rights
A user needs the user right " EngDat" (or " Administrator" ) in the user administration. The ENGDAT module is multi-client capable, i.e. messages are assigned to the particular client for whom they are intended.
Areas of the module
The ENGDAT module is divided into three areas.
"Outbound "(outgoing messages). Messages can be created here.
"Inbound" (incoming messages). Here you can view incoming messages.
"Templates "(templates are required to send to and receive from the respective partner, similar to a profile).
Technical process
The basis of an ENGDAT transmission (inbound or outbound) is an active template.
A new template is needed to
receive ENGDAT data (e.g. technical drawings) from a partner.
send ENGDAT data to a partner.
Such a template is always necessarily connected to an OFTP channel from the partner administration (a template cannot be saved before selecting an OFTP channel).
For ENGDAT messages to be recognized as such and not to be processed by other OFTP profiles, an active ENGDAT template must exist. The information in this template defines a unique file pattern. So if a file arrives via the configured OFTP channel and its file name corresponds to the file pattern of the ENGDAT template, that template is recognised as responsible and the message is therefore recognised as an ENGDAT message.
If there are corresponding active templates, you can, as already mentioned, send messages in the module area "Outbound" and receive and view messages in the Module area "Inbound". Details can be found in the description of the respective module area.