LSP02 Sequoia Warehouse INET Training v.1

Transportation Management System usage
INET TMS / LCC / CPM
May 1st
R.Riessen
DISCLAIMER: This document may identify, analyze and report on issues in the context of preparation for the Intended Partnership. Any contemplated preparatory actions as well
as potential options, proposals, analyses and costings contained in this document shall or have been undertaken and/or created within the boundaries set by applicable
(competition and other) laws and regulations. Furthermore, nothing in this document is, or should be taken to be, an indication that any decision has been made by Mondelez
International, Inc., D.E Master Blenders 1753 B.V. or any of their affiliates to implement any course of action. Any final related decision will only be taken once legally required
staff and work council consultation has been undertaken and merger control approval has been obtained.
Management Summary CHARGER (Sequoia)

Charger project refecting the MDLZ coffee carve out with the forseeable result of splitting / loosing operative volume
in logistical setup.
Target briefing was to manage
carve out implementation with lowest risk,
try to hold & secure existant volume/costniveau where possible
keep system operative for potential future joint line ups with CMB ( Combined business model).
Several ways of working have been discussed and broken down to the following decision proposals on the way
forward:
1)
Usage of the INET system setup and the LCC further on for the whole inbound transportation process of ex
MDLZ coffee volume. Chance to expand to ex DEMB coffee at a later stage.
2)
Twofold strategy for the single country national outbound shipment process:
3)
1)
Countries using the MDLZ INET TMS in transportation planning will stay with INET setup using the
existant base under JDE umbrella
2)
Countries not using MDLZ INET for planning purposes will move directly to DEMB Traget scenario not
using INET in JDE but handing deliveries to warehouse provider and expecting him to do the whole job
with carriers in his own system surrounding
Usage of the CPM ( Central Pallet Management) for the control of the CHEP pooled pallets under separate
CMB account structure
*DISCLAIMER All information contained on this page is for illustrative purposes only, and refers to options only related to the Intended Partnership*
PAGE 3
Agenda
1. Learning objectives
2. Introduction to the Intended Partnership
3. Positioning within the Value Chain
4. Process explanation
Introduction
Process flow
5. Main Tasks of the warehouse user

6. Introduction to warehouse views
7. Tasks for warehouse users
8. Upload transport demands
9. Tasks to be done in the warehouse client
10. Closing
Summary
References and Support Model
PAGE 4
Ground Rules
1. Be punctual and on time
2. Respect each others input
3. Switch off mobile phones
4. Laptops closed when not needed for training
5. Participate to the fullest of your ability
PAGE 5
Introduction to the Intended Partnership

OUR BELIEF
AMAZING WHAT CAN HAPPEN OVER A CUP OF COFFEE
OUR VISION
EVERYONE DESERVES TO GET THE COFFE THEY LOVE
WHICH IS WHY
WE ARE THE CHAMPIONS OF THE COFFEE DEMOCRACY
WE FOCUS OUR FIGHT ON 3 FRONTS
QUALITY
DIVERSITY
ACCESSIBILITY
TO ACHIEVE OUR GOAL

MOVE FROM SERVING 1700 CUPS PER SECOND
TO SERVING 5000 CUPS PER SECOND
OUR VALUES INFORM OUR BEHAVIOURS
SIMPLICITY
ENTERPRENEURS
HIP
ACCOUNTABILITY
DISCIPLINE
SOLIDARITY
PAGE 6
FROM 2 DISTANT FOLLOWERS

2013 - Global Coffee Net Sales (bn)
Nestl
11.0
Mondelz
2.9
DEMB
2.6
GMC
1.7
Strauss
1.4
Tchibo
1.2
JMS
1.0
Lavazza
1.0
Kraft
0.7
Starbucks
0.7
Melitta
0.6
Segafredo
Illy
0.3
0.2
*Source: Euromonitor data which excludes Nespresso non-grocery sales.
PAGE 7
TO A CLEAR CHALLENGER
2013 - Global Coffee Net Sales (bn)
11.0
Nestl
Intended Partnership
5.5
GMC
1.7
Strauss
1.4
Tchibo
1.2
JMS
1.0
Lavazza
1.0
Kraft
0.7
Starbucks
0.7
Melitta
0.6
Segafredo
Illy
0.3
0.2
*Source: Euromonitor data which excludes Nespresso non-grocery sales.
PAGE 8
TO GROW A BETTER FUTURE TOGETHER
Stronger point of departure.
to grow a better future together
Global reach, with strong local

positions
Create superior innovation

capabilities
Efficiency opportunities
Build a world class brand

portfolio
Complementary capabilities
Attract talent through inspiring values
PAGE 9
LEADING BRANDS, PART OF EVERYDAY LIFE

D.E MASTER BLENDERS 1753
Mondelz International
PAGE 10
RESULTING IN STRONGER MARKET POSITIONS
Austria
Australia
Belgium
Brazil
Bulgaria
China
Czech Rep.
Denmark
France
Greece
Germany
Hungary
Ireland
Italy
Latvia
Lithuania
Morocco
Netherlands
Norway
Poland
Romania
Russia
Slovakia
Spain
Sweden
Ukraine
United Kingdom
*Coffee joint ventures in Japan and South Korea not included

*Source: #1 and #2 rankings based on Euromonitor data which excludes Nespresso non-grocery sales.
PAGE 11
Position within the Value Chain Retail

Strategy
Budgeting and Long-term Planning
Category Development
Innovation and R&D
Supply Chain Planning & Integrated Business Planning
Supplier
Purchase to Pay
Make to Demand
Create Demand
Order-to-Cash
Customer
Record to Report
Master Data Management
Human Resource Management
Information Management / Information Technology
Quality Management
Legend
Other enabling processes
Steering process
Core process
Enabling process
PAGE 12
Position within the Value Chain Professional

Strategy
Budgeting and Long-term Planning
Category Development
Innovation, Research & Development
Supply Chain Planning & Integrated Business Planning
Supplier
Purchase
Make
Lead
to Pay to Demand to Order
Order-to-Cash*
Order
to Install
Contract
Management
Preventive
Maintenance
Corrective
Service
Customer
Record to Report
Local Reporting
Master Data Management
Human Resource Management
Information Management / Information Technology
Legend
Quality Management
Steering process
Core process
Enabling process
PAGE 13
14
Main Milestones
LSP subproject is in the critical path
Activities
Dates
Connectivity Tests
Week beginning 12th 2015
Unit tests
Week beginning 19th 2015
Go Live
July 6th 2015

Cycle I 2nd of Feb 13th of Mar
Test Cycles
Cycle II 14th of April 15th of May

Cycle III 26th of May 19th of June
Cutover rehearsal
TBC
Cutover
TBC
PAGE 14
MEU TARGET System Setup: General blue print shall give

base for basic structure of JDE setup
PAGE 15
Potential CBM / MEU Base setup Idea

LCC draft would contain 1 Central Inbound & 1 Export pool as well as country specific scheduling
pools
PAGE 16
Main Tasks of the warehouse user
PAGE 17
Main Tasks of the warehouse user

Upload transport demands
Check orders for errors
Enter DeliveryNote/Purchase Order Number
Set order status
Check loads leaving from /arriving to warehouse
PAGE 18
Introduction to warehouse views
PAGE 19
Introduction
PAGE 20
Client selection
Selection of clients
- If a user has to work in multiple clients, he will be prompted to select the
necessary client after login was done
- If the user is using only one client, this screen will be skipped.
PAGE 21
Navigating through the main screen upload client IE

Client:
If you are allowed to work in multiple clients, you can use the dropdown list to
jump to another client
Extras
Upload order data
Logout
Log out of the system and link to the login screen
PAGE 22
General Tasks: Navigating through the main screen

warehouse client
Dependent on his role, a user can see different buttons in the main screen. Only the necessary buttons for the users
work will be visible.
Order list
Link to an overview over all transport orders for the customer where he has the role shipper or recipient.
Enter status
Link to a screen for entering transport order status and reason codes.
Dock booking
Link to an overview over all dock bookings for the warehouse. Will only be visible if the warehouse has dockbooking
enabled.
Loadinglist
Link to an overview over all loads, with at least one transport order where the customer has the role shipper or
recipient. The customer can enter status information.
Extras
Administrate master data and upload order data. Will only be visible if the warehouse has dockbooking enabled.
Logout
Log out of the system and link to the login screen.
PAGE 23
Transport order / load status overview
PAGE 24
Tasks for warehouse users

PAGE 25
PAGE 26
Upload transport demands (1)

Kevin Faulkner: separate Presentation explaining how to fill the
FlatTO-File
PAGE 27

Switch to the relevant Upload Client (SH MI ). This country will later on pay the load. Stick
to rules!
Go to Extras
Select Upload order data
PAGE 28

Browse for exported CSV-File on your computer
For uploading selected file use button
! ATTENTION ! Field separator !

to be defined in Windows regional settings
PAGE 29

After upload you will see following screen
Now check your emails

Upload with NO errors
Upload with errors
PAGE 30
PAGE 31
Check for errors (1)

Switch to the Warehouse Client (WH )
Go to order list to:
- view order data: overview
and details behind link to order number
- download order list:

- select certain orders
view track &

trace
information
open order detail

PAGE 32

You can use filters with button
from previous screen to easier find the orders uploaded.
Field used for delivery note number or

purchase order number
PAGE 33

Enter order detail of open orders to find the errors. The error reason is displayed and
marked red.
Call central team to fix the wrong order data.

The WH is not allowed to do this.
PAGE 34
PAGE 35
Enter DN/PO-numbers or additional references (1)

Switch to the Warehouse Client (WH )
Go to order list and select the needed transport order by using filters
Go into the order detail and edit the fields DN/PO or reference
Store the transport order after changing by using
save order
after change
Edit order references

(DN, PO, RefNo)
PAGE 36
PAGE 37
Status setting Transport status

Status setting is necessary for tracking&tracing of goods
Status setting is done dependent on goods flow by warehouses, plants,
carriers, schedulers or the system
Warehouses/Plants delivering goods
- Set status collected
- e.g. National Inbounds, National Outbounds, Exports out of IE/GB
Warehouses receiving goods

- Set status delivered
- e.g. International Inbounds
Status is always set on transport order level.

If more than one order is within a load then a common status for all orders can
be copied by using the screen loading list (see later)
PAGE 38
Status hierarchy Transport status

Code
Description (EN)
Can be set by Can be set by

sending
receiving
warehouse
warehouse
CA520
GOODS COLLECTED
CA585
GOODS DELIVERED
CA622
COLLECTION CANCELLED
CA640
DELIVERY REFUSED
CA641
DELIVERY PARTLY
REFUSED
LSI108
NEW DELIVERY DATE
CA643
NEW COLLECTION
REQUEST
CA625
COLLECTED MASTER
CA626
DELIVERED MASTER
X
X
Remarks
Marks a transport order as collected.
Sets a transport order to delivered.
Precondition: status "collected" is set on
transport order
No calculation according to tariff in Module
FM. Price is 0, TSP has to claim.
The delivery was refused by the customer.
This can only be set by MDLZ schedulers.
The delivery was partly refused by the
customer. This can only be set by MDLZ
schedulers.
A new delivery date was arranged between
customer and carrier. New date has to be
entered in time field during status setting.
Can be set when transport order has status
"assigned" or "collected". Sets transport order
back to status "in progress" and removes it
from load.
Used for being able to set Reason Codes,
although no other status was set.
Used for being able to set Reason Codes,
although no other status was set.
PAGE 39
Enter status
Helpful additional information

1. When all transport orders of a load have the status Goods delivered the status Load
Delivered will be stored on load level.
As soon as the load is set to load status Delivered, the load is automatically transferred to
the freight cost management system.
2. The reason codes to choose from are depending on the selected status (see status
overview)
PAGE 40
Status setting Reason codes

Reason Codes are used for detailling special situations and documentation of
responsibilities for reporting
Reason codes are dependent on current status and must be set together with a
status
- E.g. Status delivered + RC DLD01 - Delivered clean for documenting a clean
delivery
Additionally Reason codes can be set any time by using the Status Collected
master or delivered master dependent of status of transport
Use of reason codes is obligatory for status delivered to document
clean or disputed deliveries.
PAGE 41

Possible reason codes to be set before truck has finished loading and before
leaving the site
Status
collected master
(pre gatehouse)
Reason Code
COL01 - Haulier late
COL02 - Haulier no show
COL03 - Tranship
COL04 - System issue
COL05 - Stock issue
COL06 - No trailer
COL07 - Warehouse delay
COL08 - Customer issue
COL09 - Loading issue
COL10 - Order cancelled
COL11 - Truck not fit for purpose
PAGE 42

Loading done truck is delivering
Status
delivered master
(in transit)
Reason Code
RSC01 - Possible rescue
ITR01 - Stolen Load
ITR02 - Traffic issues
ITR03 - Weather issues
ITR04 - Driver out of hours
ITR05 - Breakdown
ITR06 - Own vehicle RTA (Road Traffic Accident)
ITR07 - Wrong delivery address
ITR08 - Refused Awaiting rebook
TRF01 -Temperature
TRF02 - Incorrect truck
TRF03 - To be Returned to Stock
TRF04 - To be redelivered
TRF05 - Carrier late
TRF06 - Wrong delivery date/time
TRF07 - Not ordered
TRF08 - Stock damage
TRF09 - Short dated
TRF10 - Not booked in
TRF11 - Mixed pallets
TRF12 - Pallets too high
TRF13 - Incorrect pallet type
TRF14 - Incorrect loading sequence
TRF15 - Failed to scan
TRF16 - Duplicate order
TRF17 - Insufficient wrapping on pallet
TRF18 - Customer cannot unload
POD01 - POD lost in transit
POD02 - Wrong POD RC from carrier
POD03 - Incorrect POD document uploaded
PAGE 43

Orders delivered or refused
Status
Delivered
(goods at customer)
Reason Code
DLD01 - Delivered clean
DLD02 - Missing items
DLD03 - Over and kept
DLD04 - POD not signed
DLD05 - Not checked by customer
Total Refused
(customer refused
all the goods)
TRF03 - Returned to Stock
Partially Refused
(customer refused
part of the goods)
PRF01 - Temperature
PRF04 - Not ordered
PRF05 - Stock damage
PRF06 - Short dated
PRF07 - Mixed pallets
PRF08 - Pallets too high
PRF09 - Incorrect pallet type
PRF10 - Failed to scan
PRF11 - Duplicate order
PRF12 - Customer cannot unload
PAGE 44
Status setting detailed workflow

2 possible screens for status setting available
- enter status from main screen
- loading list
and use of status entry function
Needed values for status settings:

- Status
- Remarks (enters details for special events free text)
- Receipt (PO-Number: only for Inbounds if empty)
- Date/Time (+/- 9 days of requested date)
- Reason codes (mandatory if delivered status is set)
PAGE 45
Status entry: Enter Status screen

Usage of screen Enter Status
use filter
Save status
select status and up to

two reason codes
Remark: in Enter Status a status needs to be entered per single order. In loading list,
status can be entered and copied to other orders within a load.
PAGE 46
Enter status: Filter in order list

To reduce the number of displayed orders, additional filters can be
applied.
Reset filter
Apply filter
PAGE 47
Enter status: Loading list

Status can also be set in loading list by using button
Enter filter screen
PAGE 48

For finding loads easier, following filters can be used
Reset filter
Apply filter
PAGE 49
PAGE 50
Track & Trace of status

Status can be tracked in the Track&Trace part of the application
Order List: Order detail
Enter
Track&Trace
Loading List: Load AND order details
Enter
Track&Trace
PAGE 51
Track & Trace of status

Detailed status history in Track&Trace
MouseOver shows, when

status was entered
PAGE 52
PAGE 53
Check for loads leaving from /arriving to warehouse

Loads leaving the warehouse of arriving to the warehouse can be seen by using the
loading list
A download of the loading list will be available as of Go-Live
Enter filter screen
PAGE 54

To distinguish between incoming/outgoing loads the user can filter by pickup/delivery
locations
E.g. loads to Milton Keynes:
Enter recipient country + ZIP
Eg. Loads from Milton Keynes:
Enter sending
country + ZIP
PAGE 55

In the filter view a user can also download a list
Download results
Use to search in status history, e.g.

Collection cancelled
PAGE 56
Loading list download

The loading list can be downloaded by using
Format is CSV, which can easily be opened by use of MS Excel.
PAGE 57
PAGE 58
Status setting during dock booking process
PAGE 59
PAGE 60
Gatehouse Tasks
The gatehouse is responsible for controlling arriving trucks and for registering
trucks in the inet TMS
3 basic process steps need to be documented by the gatehouse users
- Registration IN
Truck arrives, delivers trailer
- Tractor unit arrived

Carrier arrives to collect loaded trailer
- Registration OUT
Truck leaves with loaded trailer
PAGE 61
Dock booking list

Warehouse and gatehouse users can survey the current dock status using the
dock booking list
PAGE 62
Dock booking list

Buttons on dock booking list
Symbol
Description
Tool tip: Lock the site
Locking is only done for LSP only, site can still book docks. This button is only active if the user has the right
DOCK_LOCK and the booking functionality is active for the following workingday (weekends are considered).
Tool tip: Remove lock on the site
This button is only active if the user has the right DOCK_LOCK and the booking functionality is inactive for the
following workingday (weekends are considered).
Tool tip: Create new dock booking
This button is only active if the user has the right DOCK_NEW and is allowed to create orderless dock bookings.
Tool tip: Dock monitor
This button is always active and shows current bookings in a new screen.
Tool tip: Show open dock bookings
Display of all dock bookings with status open, cancelled and booked with a date greater or equal the actual
date.
Tool tip: Show dock bookings of today
Display of all dock bookings of the actual date. The dock bookings are selected by requested date and booking
date.
Tool tip: Show complete dock bookings
Display all dock bookings with status confirmed, registered or processed with a date greater or equal the
actual date.
Tool tip: Show selection of dock bookings
Open an additional selection screen for dock bookings.
PAGE 63
Set timestamps for in- and outgoing trucks

The warehouse user can set needed timestamps in the dockbooking list by
either entering a value in the corresponding fields or by inserting current time
using the button
insert time stamps

press store
registration
time button
PAGE 64
Enter truck plate number for trailers

If Trailer details are not known before picking start, the warehouse user can
enter the truck information online
PAGE 65
Dock booking list - filter

Filter can be used to narrow results displayed in dock booking list by following
criteria.
This screen can be reached by using the button
in the dock booking list
PAGE 66
Dock Monitor
To view current dock reservations you can press the button
monitor.
to enter the dock
There you can see all carriers and the current dock status in a graphical
overview. Using mouse-over you can see details of the booking.
(registered IN)
(handling start)
PAGE 67
Dock Monitor
Click on booking to see details
You can also set status and reason codes for selected booking by using buttons
for status and to enter reason code screens.
PAGE 68
PAGE 69
PAGE 70
Warehouse Tasks
The warehouse users are responsible for setting warehouse order status in the
inet TMS to inform carriers, the schedulers and the gatehouse about the current
status of load preparation in the warehouse.
Status setting can be reached by using the button for registered dock
bookings or can also be entered through the dock monitor.
PAGE 71
Set load preparation status

Enter timestamps for status
- Handling start: start of picking
- Marshalled: picking finished goods ready for loading
- Handling end: trailer loaded
PAGE 72
Enter truck plate number for trailers

If Trailer details are not known before picking start, the warehouse user can
enter the truck information online
PAGE 73
Overview of Dock Status

By clicking on the Track&Trace button
see the dock booking status history.
in the dock booking list the user can
PAGE 74
Dock Booking Reason Code setting

Additionally to status setting a user can also set reason codes during dock
booking by using button in the dock booking list
Add
additional
lines for
reason code
Select reason code and

press save
Reason codes
can be deleted,
too
PAGE 75
Summary Pallet Management Common Design Process shall be

adopted
Currently MEU moves 9 Mio pallet all types thereof 2,5 Mio White EU pallets.
Until 2007 pallet tracking was insufficient, leading to stock differences and late declaration claims By CHEP
In 04/07 installation of Central Pallet Management (CPM) EU, tracking all Blue pallet movements, providing
correct allocation of pallet costs resulting in pallet inventory end 2007, 2008, 2009, 2010, 2011, 2012 with
zero stock deviation
EOC/Bridge2: Harmonised pallet management for owned pool pallets (CHEP/LPR) and functionality of the
Central Pallet Management will stay as is
In EOC/Bridge2 differing approach for white pallets - Implications:
White Pallets on Buy will be put into conversion and sourced/called off by Plant
White Pallets on Exchange will be called off by LOG OPS/Plant
All pallet costs shall be invoiced by Direct Posting Planned for future concept after EOC: Check of all charged
pallet movements by Central Pallet Management
Extension of Central Pallet Management System on White Pallets existing . Local country to decide on
integration of white pallets
Local connectivity into CPM to be taken care of by local implementation team
76
PAGE 76
Course ID
Work stream
Module
Support
-
<.>
<.>
<.>
More information available:

-
<> (Link/Document)
<> (Link/Document)
In case of any questions or concerns:

Trainer
John Doe
John.Doe@demb.com
BPO
John Doe
John.Doe@demb.com
IBPO
John Doe
John.Doe@demb.com
WS
Marcel Leijenhorst
marcel.leijenhorst@demb.com
PAGE 77
Questions
PAGE 78
Evaluation
Formal evaluation via <..>
For now think about:

-
What are your main takeaways?
Have the course objectives been met?
Do you feel comfortable with the content?
PAGE 79
Appendices
DISCLAIMER: This document may identify, analyze and report on issues in the context of preparation for the Intended Partnership. Any contemplated preparatory actions as well
as potential options, proposals, analyses and costings contained in this document shall or have been undertaken and/or created within the boundaries set by applicable
(competition and other) laws and regulations. Furthermore, nothing in this document is, or should be taken to be, an indication that any decision has been made by Mondelez
International, Inc., D.E Master Blenders 1753 B.V. or any of their affiliates to implement any course of action. Any final related decision will only be taken once legally required
staff and work council consultation has been undertaken and merger control approval has been obtained.
81
Central Pallet Management
PAGE 81
Former ABPA process element prices incl. surcharges

were transferred back to 1 single fee structure
PAGE 82
The Single Fee is based on issue per Country
EOC Model is based on the priciple of Receiving Country pays full

One invoice raised per country containing all movements affecting the country
This implies that production in country is paid by Country Proc. Comp.
PAGE 83
84
System control cycles in MDLZ/CHEP are interlinked but

triggered and monitored manually
PAGE 84
85
Declaration Process Timeframes
PAGE 85
86
The EOC single fee billing process for pallets will run in
Procurement Company on direct posting
PAGE 86

LSP02 Sequoia Warehouse INET Training v.1

Загружено:

Сведения о документе

Исходное описание:

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

LSP02 Sequoia Warehouse INET Training v.1

Загружено:

Авторское право:

Доступные форматы

Transportation Management System usage

INET TMS / LCC / CPM

Management Summary CHARGER (Sequoia)

carve out implementation with lowest risk,

try to hold & secure existant volume/costniveau where possible

5. Main Tasks of the warehouse user

References and Support Model

2. Respect each others input

3. Switch off mobile phones

4. Laptops closed when not needed for training

5. Participate to the fullest of your ability

Introduction to the Intended Partnership

TO ACHIEVE OUR GOAL

FROM 2 DISTANT FOLLOWERS

TO GROW A BETTER FUTURE TOGETHER

Stronger point of departure.

to grow a better future together

Global reach, with strong local

Create superior innovation

Build a world class brand

Attract talent through inspiring values

LEADING BRANDS, PART OF EVERYDAY LIFE

RESULTING IN STRONGER MARKET POSITIONS

*Coffee joint ventures in Japan and South Korea not included

Position within the Value Chain Retail

Other enabling processes

Position within the Value Chain Professional

Week beginning 12th 2015

Week beginning 19th 2015

July 6th 2015

Cycle II 14th of April 15th of May

MEU TARGET System Setup: General blue print shall give

Potential CBM / MEU Base setup Idea

Main Tasks of the warehouse user

Main Tasks of the warehouse user

Introduction to warehouse views

Navigating through the main screen upload client IE

General Tasks: Navigating through the main screen

Transport order / load status overview

Tasks for warehouse users

Tasks for warehouse users

Upload transport demands (1)

Upload transport demands (2)

Select Upload order data

Upload transport demands (3)

! ATTENTION ! Field separator !

Upload transport demands (4)

Now check your emails

Upload with errors

Tasks for warehouse users

Check for errors (1)

and details behind link to order number

- download order list:

view track &

open order detail

Check for errors (2)

from previous screen to easier find the orders uploaded.

Field used for delivery note number or

Check for errors (3)

Call central team to fix the wrong order data.

Tasks for warehouse users

Enter DN/PO-numbers or additional references (1)