Delivery schedule

from Wikipedia, the free encyclopedia

Delivery schedules (LAB) are a standard for the electronic transfer of delivery orders (purchase orders) between manufacturers and suppliers, which was developed jointly by the OEMs and suppliers in the VDA . By standardizing the data format, terms and content, the communication process between those involved is simplified and accelerated. In addition, ambiguities in understanding and communication between those involved are eliminated. In the delivery schedule, the required quantities of an OEM are communicated to the automotive supplier over a long period of time so that they can adjust their production and procurement accordingly.

On-demand principle

Characteristic of delivery schedule systems are the use of cumulative quantities . The quantities are from an agreed date (for example, from. Inventory ) for a defined sequence of order time points individually and given as a cumulative amount (s. Progress number principle ); this is also referred to as delivery schedule . Most of the time, the first classifications are fixed, ie they are no longer changed, while the other classifications, which can extend over a period of up to a year, have a preview function and can change again with the next LAB. For the first few weeks, an acceptance obligation is usually agreed between the OEM and the supplier . In the LAB, the deliveries that have already been received are also displayed to the supplier via the cumulative received quantity in order to compare them with the deliveries. This is especially important for long transport routes and the commissioning of freight forwarders and other logistical service providers (e.g. Deutsche Bahn ) ( see also contract logistics ) in order to avoid that deliveries that are still on the transport route are not included or are included twice become. A prerequisite for call-offs are framework agreements between customer and supplier that make recurring individual orders and their order confirmations superfluous.

Delivery schedules can have a substitute or a supplementary function. This means that in the case of a replacing function, the classifications of the last call are overwritten and thus invalid, while the supplementary function only supplements and cumulates the old classifications. Usually the substitute function is chosen because it is easier to handle in the IT.

However, additional information can also be sent in the delivery schedules. The last delivery received is indicated so that the cumulative quantity can be coordinated with the goods that are still on the way. In addition, periods of time can be communicated for which pre-production or raw material can be purchased.

In many cases, JIT delivery schedules are sent in addition to the delivery schedule , which only affect the next deliveries, but are binding and usually no longer changed. The delivery schedule only has a preview function so that long-term planning can be carried out.

Dispatch and formats of delivery schedules

The delivery schedules are sent regularly to the supplier. This can be done in the form of a fax . However, EDI is increasingly being used for this purpose in order to guarantee a continuous automated data transfer from the customer system to the supplier system without the need for manual data entry.

The Association of the Automotive Industry has published, for example for delivery schedules recommendations for EDI:

In the course of the globalization and internationalization of logistics networks, the VDA is adapting its EDI formats to the EDIFACT standard and is increasingly using XML as a 'coding language'.

  • VDA 4984: Data transfer of delivery schedules V2.0
  • VDA 4985: Data transfer of JIT calls V2.0

But other organizations have also developed corresponding types of messages, such as Odette the DELINS for delivery schedules and DELJIT for JIT delivery schedules or production- synchronous delivery schedules . The message type DELFOR can also be found in more recent standards, such as EDIFACT .