DHL Automotive Process
Warning: This is an incomplete guide.
The purpose of this page is show base functionality that is in use within the Automotive Alliance system, as well as any particular options that a customer process may use.
Systems
- CALIDUS Systems
- CTMS (Base)
- WCS (Base)
- PORTAL
- Client Systems
- My Supply Chain (Base)
- Microlise
- MixMove
Process
Order Creation
Base:
- Order created in Fixed Schedule
Options:
- Add items via WCS Order Creation
- Loose Items and Assets (Roll Cases, pre-identified with fixed barcode)
- Add Items and Contents via WCS Order Creation
- Item creation through EDI
- Item Content creation through EDI
- Customer Order identification through EDI
Execution
Base:
- WCS Loading of Order Items
- ctms:Loading Management - release to WCS for loading.
- Cross-dock operation (manual)
- Mixmove cross-dock scanning
Options:
- Microlise Delivery of Order Items
- Automatic Debrief of Order and Trip Stop/Trip.
Tracking
Base:
- My Supply Chain Interface
Options:
- Portal TTM/TMS
- Customer Tracking Interface
Returns
Base:
- Manual updates via customer systems
Options:
- Portal TMS Returns of Cages.
- Portal TMS Returns of Product
- Portal TMS Return Label Production.
Config
Customer
New customer setup
Locations
Location required foe source of product (Base). This will be:
- Client Warehouse
- Option: Special/WCS Item to Asset - controls FCA process (Items to Asset)
- Client RDC/XDock locations (Base)
- Special/RF Cross-dock
Decodes
Decodes depend on the import (mostly) and export processes in use by the system.
These are used by these processes to convert the client data field content to CTMS data.
Samples of existing decodes below.
| DECODE_NAME | DECODE_TYPE |
|---|---|
| BMW_ASSET_TYPE | DU_TYPE |
| BMW_RET_TYPE | REFERENCE |
| BMW_TRANSPORT | REFERENCE |
| BMW_WAREHOUSE | LOCATION |
| FIAT_DEALERSHIP | LOCATION |
| FIAT_DUS | DU_TYPE |
| FORD_DEALERSHIP | LOCATION |
| FORD_DU | DU_TYPE |
| FORD_LOCATION | LOCATION |
| TESLA_DEALERSHIPS | REFERENCE |
| TESLA_DU_TYPES | REFERENCE |
| TOY_ASSET_TYPE | DU_TYPE |
| TOY_DEALERSHIP | LOCATION |
| TOY_PACKAGE_CODE | DU_TYPE |
| TOY_PACK_TYPE | REFERENCE |
| WCS_DEALERSHIP | LOCATION |
In general, the dealership locations are set against the imports/exports. If importing or exporting from another system, the locations are likely to be reused.
e.g. Location 11258 for Toyota may/will not be the same as location11258 for Ford.
In order to combat this, the locations are decoded. So 1148 arriving for a Ford order is perhaps decoded to e.g. F11258.
Similarly outbound - the locations are decodes in reverse.
DHL Link may also do a similar decoding.
As can be seen, any inbound interface would also need to decode customer-specific asset types, DU types, etc.
Fixed Schedules
The dealerships are strategically determined to have a delivery several times a week (perhaps even Daily).
The client works out where they will be delivering to each dealership and at what time, based on resources.
They also work out the collection time each day from the stock holding location (customer warehouse) to closest DHL hub.
This is saved onto the fixed schedule and the dealerships informed of their scheduled deliveries.
EDI
Base:
- MySC/ConnectedView Tracking EDI - Outbound
- CNV_ACC_AAMP
- CNV_OFDC_AAMPENROUTE
- CNV_OFDC_AAMPCOMPL
- Microlise - execution of initial pickup/final delivery/returns pickup
- MixMove - cross-dock processing/debrief
- ACCEPT_MIXMOVE_TRUNKS - Outbound - INT_XML_OUT2.AUTO_ACCEPTED
- MIXMOVE_SCNS - Inbound
- MIXMOVE - Outbound
Options:
- Order Inbound processes
- BMW
- BMW_INBOUND_ORDERS - Inbound - DP_BMW_EDI_IN.PROCESS_FILES
- BMW_CLAIM_ORDERS - Outbound - DP_BMW_EDI_OUT.SEND_CLAIMS
- Tesla - TESLA_ORDERS - Inbound - DP_TESLA_EDI_IN.IMPORT_ORDERS
- Toyota - TOYOTA_ORDER_ITEMS - Inbound - DP_TOY_EDI_IN.P_PROCESS_FILES
- Ford - FORD_EDI_IN - Inbound - Ford Orders EDI
- Scania - SCANIA_ORDER_ITEMS - Inbound
- BMW
- Customer-Specific Tracking EDI
- Tesla - TESLA_TRACKING - Outbound
- FCA/FIAT - CLICK_OUTBOUND - Outbound
- Ford (TBC)
WCS Maintenance
ctms:WCS Maintenance controls the basic configuration of WCS and should realistically only need to be done once.
Assets
Permanent assets need to be set up in CTMS for customers.
Note: At least 1 permanent asset for the customer must be set up BEFORE any others can be set up in the screen.
- Create a dummy one in the database first.
Reports/Imports/Exports
Reports
| AA Delivery Status Report External | AA_DEL_STAT |
| AA Delivery Status Report Internal | AA_DEL_STAT |
| AA Trip Sheet | AA_TRIP_SHEET.rep |
Extracts
See ctms:Extracts - WCS Scanning
Also:
| Automotive Planning Report | Planning_Report | DP_CSV2.PLANNING_REPORT |
| BMW Asset Dwell | AUTO_ASSET_DWELL | DP_CSV3.AUTO_AFTERMARKET_BMW |
