Transcript MM-FDT_Use_Cases_English

FDT Use Cases
(beyond device
configuration)
Motivation for this presentation
 FDT is more than…
... a Frame Application that …
… has a Tree View
on left hand side that
shows hierachical
ordered network
topology
… opens DTM user
interfaces for offline or
online parameterization
… uploads and
downloads
device parameters
Scenarios










Data exchange between Frame Applications
Reporting / Documentation
Audit Trail
Alternative Communication Paths
Bus Master Configuration
Control System Configuration
Bus Master without Gateway capabilities
Process Monitoring
Network Management
Update and Replacement
Data exchange between Frame
Applications
 Scenario
Vendor A: Frame Application
Vendor B: Frame Application
 Data exchange between different
Frame Applications
e.g. Data exchange between a stand-alone
Service Tool and a Control System
Topology
Import
Export XML
 FDT Definition
 Definition of standard topology data
exchange format
 Frame Application generates or reads XML files according
FDTTopologyImportExportSchema
 FDTTopologyImportExportSchema defines
Exchange of topology information
Exchange of DTM/BTM and device/block type information
Exchange of DTM/BTM instance data (Stream or PropertyBag)
Data exchange between Frame
Applications
Example XML
Communication
DTM
Gateway DTM
Gateway
DTM
Device
DTM
Device
DTM
Data exchange between Frame
Applications
Example: System Engineering Tool  Service Tool
3. Check-out single device data set or
sub-network from database and
export to XML file
7. Synchronize single device data set or
sub-network with data in XML file
and check-in to database
Data Sharing XML File
1. Load data
from database
4. Import data
from XML
file
6. Export data
to XML file
Vendor B: Service Tool
Vendor A: System Engineering Tool
2. Parameterization
via device
specific DTM
5. Maintenance
via device
specific DTM
Both Frame Applications use same DTM type and load it with shared device data
Data exchange between Frame
Applications
Example: System Engineering Tool  PDA
3. Check-out single device data set or
sub-network from database and
export to XML file
7. Synchronize single device data set or
sub-network with data in XML file
and check-in to database
Data Sharing XML File
1. Load data
from database
Vendor A: System Engineering Tool
2. Parameterization
via device
specific DTM
4. Import data
from XML
file
6. Export data
to XML file
Vendor C: Pocket Tool
5. Maintenance
via device
specific DTM
Frame Applications use different, but compatible DTM types
and load it with shared device data
Scenarios










Data exchange between Frame Applications
Reporting / Documentation
Audit Trail
Alternative Communication Paths
Bus Master Configuration
Control System Configuration
Bus Master without Gateway capabilities
Process Monitoring
Network Management
Update and Replacement
Reporting & Documentation
 Scenario
 Generation of device configuration &
parameterization reports
 Print out of reports
 FDT Definition
 DTM interface (IDtmDocumentation) called to request report information
for specific data (e.g. device configuration, offline or online configuration
etc.)
 Definition of documentation data format
- DTMDocumenationSchema.xml
 Data transformation to HTML reports
Reporting & Documentation
Example: Print of Device Settings (Frame
Application Style)
IDtmDocumentation:
GetDocumentation()
DTM
XSLT
Frame Application
specific
Tranformation File
Transformation to HTML
Reporting & Documentation
Example: Print of Device Settings (DTM Style)
IDtmDocumentation:
GetDocumentation()
DTM
XSLT
DTM specific
Tranformation File
Transformation to HTML
Scenarios










Data exchange between Frame Applications
Reporting / Documentation
Audit Trail
Alternative Communication Paths
Bus Master Configuration
Control System Configuration
Bus Master without Gateway capabilities
Process Monitoring
Network Management
Update and Replacement
Audit Trail
 Scenario
 Record data changes (what has been changed by who)
Example: - Device parameter XYZ changed from 0815 to 4711 by user
Operator
- Function Device Reset executed by user Operater at
10.30pm - 2004-02-04
-…
 Change history documentation
 FDT Definition
 Frame Application interface IDtmAuditTrailEvents
that is called by DTM whenever
- Device Parameter is changed
- Device Status changes
- Device related operation is executed
Audit Trail
Example: Change History Recording
Frame Application
Save
Change Some Parameters
Get DTM Data
User
IDtmAuditTrailEvents:
OnAuditTrailEvent()
Change History Table
´Device Data Table
Device
ID
Device
XY
Device
XY
Device
XY
DTM Binary Data
0xAF1255FFDE4323E2...
0xAF1255FFDEFFFFEE...
0xAF1255FFFFFFFFFFF...
Last Modified
2005-11-10
10:12:56
2005-11-11
10:12:56
2005-11-12
12:12:56
Time / Date
Time / Date
User
2005-10-10
10:45
Parameter XY has change from 10.0 to 20 milliampere
User 1
Parameter XY has change from 20.0 to 30 milliampere
User 2
Parameter XY has change from 30.0 to 40 milliampere
User 2
Parameter XY has change from 30.0 to 40 milliampere
User 2
2005-11-12
8:00:00
2005-11-12
9:10:00
2005-11-12
10:10:00
Scenarios










Data exchange between Frame Applications
Reporting / Documentation
Audit Trail
Alternative Communication Paths
Bus Master Configuration
Control System Configuration
Bus Master without Gateway capabilities
Process Monitoring
Network Management
Update and Replacement
Alternative Communication
Paths
 Scenario
 Device has multiple physical
communication interfaces
- field bus network (e.g. Profibus, FF, Modbus etc.)
- vendor specific service interface (e.g. RS 232,
IrDA, Bluetooth etc)
 User wants to select path to use
 FDT Definition
 Device DTM supports multiple protocols
- DTM Information XML contains multiple
„required“ protocols
 Device DTM is assigned to muliple
Communication or Gateway DTMs
Alternative Communication
Paths
SetCommunication (null)
DTM 1
DTM 2
SetCommunication (DTM 1)
DTM 3
SetCommunication(DTM
ReleaseCommunication
SetCommunication (DTM()2)
3)
DTM 4
Scenarios










Data exchange between Frame Applications
Reporting / Documentation
Audit Trail
Alternative Communication Paths
Bus Master Configuration
Control System Configuration
Bus Master without Gateway capabilities
Process Monitoring
Network Management
Update and Replacement
Bus Master Configuration
 Scenario
 Configuration of communication master
 Setup of cyclic communication
 FDT Definition
 Master Configuration Data in DTM
Parameter for a slave device
XML according DTMParameterSchema)
e.g. for Profibus: BusMasterConfigurationPart + GSD information
Bus Master Configuration
Example: Profibus Master Configuration
Functionality is typically
realized by a PLC specific Bus
Master Configuration Tool.
PLC DTM
Configure Bus Master and
setup cyclic communication
DTM representing PLC
Bus Master
(Module) DTM
DTM representing Bus Master
Module plugged into PLC
IDtmParameter:
GetParameter()
Read GSD and BusMasterConfigurationPart
from Parameter XML
GSD + BusMaster
ConfigPart
GSD + BusMaster
ConfigPart
GSD + BusMaster
ConfigPart
Slave DTM 1
Slave DTM 2
Slave DTM 3
Scenarios










Data exchange between Frame Applications
Reporting / Documentation
Audit Trail
Alternative Communication Paths
Bus Master Configuration
Control System Configuration
Bus Master without Gateway capabilities
Process Monitoring
Network Management
Update and Replacement
Control System Configuration
 Scenario
 Devices connected to a field bus must be made
known to the control system
 Device input and output signals must be create
and integrated into functional control system planning
- e.g. mapping of device input / output to PLC variables
 FDT Definition
 DTM (Process) Channels
- IFdtChannel interface
- Channel Parameter XMLs according protocol specific FDT Annex
Schema
Control System Configuration
Role of Process Channels
Process Channel Parameter typically contain
following process variable information:
- Name, Tag, ID
- Data type
- Singnal type (input / output)
- Information type (Semantic ID)
- Address information (e.g. position / length)
- Flag indicating that it is in use by control system
(protectedByChannelAssignment)
PLC DTM
Bus Master
(Module) DTM
Process Channels
describe variables
exchanged between
the device and the
PLC
Device DTM
Process
Ch 1
IFdtChannel:GetParameters()
IFdtChannel:GetParameters()
Process
Ch 2
Process
Ch 3
Cyclic data
exchange
Process
Var 1
Process
Var 2
Process
Var 3
Control System Configuration
Process Channel  Variable Mapping
Functionalitiy is typically realized
by a Control System specific
Programming Suite.
Symbolic variable names are used for Control System programming
PLC DTM
Symbolic names are applied to variables
Bus Master
(Module) DTM
Process Channel information is
mapped to PLC Module variables
Device DTM
Process
Ch 1
Process
Ch 2
Process
Ch 3
Control System Configuration
PLC Program Download
PLC DTM
Program is downloaded to PLC
Bus Master module maps process values into
PLC variables in memory.
PLC
program
The PLC variables are used in program running
in the PLC to control the system.
Cyclic data
exchange
Process
Var 1
Process
Var 2
Process
Var 3
Scenarios










Data exchange between Frame Applications
Reporting / Documentation
Audit Trail
Alternative Communication Paths
Bus Master Configuration
Control System Configuration
Bus Master without Gateway capabilities
Process Monitoring
Network Management
Update and Replacement
Bus Master without Gateway
capabilities
 Scenario
 Bus Master in a PLC doesn’t
have Gateway capabilities
 Device DTMs can’t connect to
its device through PLC
 FDT Definition
 Nothing special!
Master DTM only supports
services to access cyclic data
(e.g. Profibus DPVO)
Master DTM
Device
DTM
Device DTM needs
acyclic services (e.g. Profibus DPV1)
for configuration & parameterization
Bus Master without Gateway capabilities
Example: PLC with Profibus Master Module
Parallel Profibus
Class 2 Master
Configure Bus Master and setup
cyclic communication
Communication
DTM
Master DTM
Cyclic services are
used for observation
Read GSD +
BusMasterConfigurationPart
Acyclic services are
used for configuration &
parameterization
Device
DTM
Cyclic data
exchange
Scenarios










Data exchange between Frame Applications
Reporting / Documentation
Audit Trail
Alternative Communication Paths
Bus Master Configuration
Control System Configuration
Bus Master without Gateway capabilities
Process Monitoring
Network Management
Update and Replacement
Process Monitoring
 Scenarios
 Process Visualization
 Condition Monitoring
- Device status
 Gathering of asset management related information
- Health / predictive maintenance information
- Operation counters
- etc.
 FDT Definition
 DTM (Process) Channels
- IFdtChannel interfaceChannel Parameter
- XMLs according protocol specific FDT Annex Schema
 Single Device Data Access
- IDtmSingleDeviceDataAccess interface
- Data XML according DTM Item Schema (protocol independent)
- Semantic IDs
Process Monitoring
Role of Process Channels
Process Channel Parameter contain
information how to request process
variables directly from the device, e.g.
via Profibus DPV1
Process Channel Parameter can
also contain information about
alarms and ranges
Comm DTM
Process Channels describe
variables that are
exchanged via parallel
(acyclic) communication
path
Device DTM
Process
Ch 4
IFdtChannel:GetParameters()
Process
Ch 5
Process
Ch 6
Process
Var 4
Process
Var 5
Process
Var 6
Process Monitoring
Process Value Reading
Process Monitoring Frame Application uses
Communication or Gateway DTM communication
interface to directly connect to devices and read
process variables.
Comm DTM
IFdtCommunication:
TransactionRequest()
Process variable address information
from Process Channel Parameter
Process variable value read from the
device. Returned byte stream must be
converted to data type described in
Process Channel Parameter
Process
Var 4
Process Monitoring
Process Value Reading via OPC Server (1/2)
If OPC Server acts as a FDT Frame Application it
even can use the Communication or Gateway
DTMs, so it becomes independent from used
hardware.
OPC Server
Configuration
interface
OPC Server
Comm DTM
Frame Application reads
Process Channel Parameters
and feeds OPC Server with
information
Process Monitoring Application uses
protocol independent OPC interface to read
process variables
Device DTM
Process
Ch 4
IFdtChannel:GetParameters()
Process
Ch 5
Process
Ch 6
Process
Var 4
Process
Var 5
Process
Var 6
Process Monitoring
Drawback of Process Channel
 Information is protocol dependent
 XML Schemas defined by FDT Protocol Annex
 Frame Application must be prepared for every protocol
 Mechnismus doesn’t work for new introduced
or vendor specific protocols!
 Solution: Single Device Data Access interface
 Provides protocol independent way to access
process variables
Process Monitoring
Role of Single Device Data Access interface
Comm DTM
Process
Var 4
Process
Var 5
Process
Var 6
Device DTM
IDtmSingleDeviceDataAccess:Read()
IDtmSingleDeviceData::GetItemLisl
GetItemList() and DTM Process Channels
may contain redundant information. Both
describing the process variables.
Process
Ch 4
Process
Ch 5
Process
Ch 6
Process Monitoring
Process Value Reading via OPC Server (2/2)
OPC Server
Comm DTM
Process
Var 4
OPC Server starts Device DTM and
uses Single Device Data Access
interface if protocol is unknown or no
Process Channel is provided for the
process variable.
Process
Var 5
Process
Var 6
Device DTM
Process Monitoring
Drawback of Single Device Data Access Interface
 All Device DTMs must be started / shut-downed
 Start / shutdown of DTM is time consuming
 DTMs take much memory
 Lower performance than Process Channel
mechanism
Scenarios










Data exchange between Frame Applications
Reporting / Documentation
Audit Trail
Alternative Communication Paths
Bus Master Configuration
Control System Configuration
Bus Master without Gateway capabilities
Process Monitoring
Network Management
Update and Replacement
Network Management
 Scenarios
 Automatic creation of network topology
 Verification if manual engineered network topology maps to field bus
network
 Address Management
 FDT Definition
 DTM information about supported hardware
- XML according FDT<protocol>DeviceTypeIdentSchema
- IDtmInformation2 interface to request information
 Scan of field bus and information about connected devices
- XML according FDT<protocol>ScanIdentSchema
- IFdtChannelScan:ScanRequest to perform scanning
 Address setting mechanism
- IFdtChannelSubTopology2 to trigger address setting
Network Management
DTM / Device Catalog
Start all found DTMs and request
DTM and hardware information
(IDtmInformation / IDtmInformation2)
Scan Windows-Registry
for installed DTMs
FDT-Category
FDT_DTM
DTM
DTM Table
ID
Name
Version
FDT
Version
Vendor
ProgID
1
SomeDeviceDTM
1.00.00
1.2.1
M&M
MMDtm.ExampleDevice
DTM Device Type Table
ID
DTM
ID
Name
Version
1
1
Device Type 1
1.00.00
DeviceVendor 1
1, 2
´2
1
Device Type 2
1.00.00
Device Vendor 1
1, 2
3
1
Device Type 3
1.00.00
Device Vendor 1
3, 2
Supported
Protocols
Vendor
Required
Protocols
Store information regarding
DTM
Store information regarding
DTM Device Types 
Drivers representing the
devices in the software
Store protocol information
ID
Device
Type ID
Manufactur
er ID
Device ID
Hardware
Version
Software
Version
Vendor
Specific
Protocol
1
1
1234
1
*
1.0-5.5
XY=2; Z=1
1
Store information regarding
hardware (pyhsical
devices)
Protocol
Table
which Identifier
are supportedName
by the
ID
1
1234-23456-2345
Profibus DPV1
DTM
Device Types.
´2
1
2345-1
1.1
*
1.0-5.5
XY=2; Z=2
2
2
7890-6543-11111
Vendor Specific
3
1234-23456-2346
HART
Hardware Info Table
3
2
1234
2
*
1.0-5.5
XY=2; Z=3
1
4
2
2345-1
2.2
*
1.0-5.5
XY=2; Z=4
2
5
3
2345-1
3.3
*
1.0-5.5
XY=2; Z=5
2
6
3
0815
4711
*
1.0-2.0; 3
XY=2; Z=6
3
MMDTM.ExampleDevices
…
…
…
XYDTM.XYZDevices
Windows-Registry
Network Management
Scan Field Bus and Create Network Topology (1/2)
Scan field bus
Comm
DTM
IFdtChannelScan::
ScanRequest(protocolId);
IDtmScanEvents::
OnScanResponse()
DTM Table
ID
Name
Version
FDT
Version
Vendor
ProgID
1
SomeDeviceDTM
1.00.00
1.2.1
M&M
MMDtm.ExampleDevice
ID
DTM
ID
1
Bus Address 1
Manufacturer ID = 1234
Device ID
= 1
Hardware Vers = 2.3.1.2
Software Vers = 3.12.4
Bus Address 3
Manufacturer ID = 1234
Device ID
= 2
Hardware Vers = 2.4.1.2
Software Vers = 3.00.4
Bus
Address = 1
Bus
Address = 3
DTM Device Type Table
Supported
Protocols
Required
Protocols
Name
Version
Vendor
1
Device Type 1
1.00.00
DeviceVendor 1
1, 2
´2
1
Device Type 2
1.00.00
Device Vendor 1
1, 2
3
1
Device Type 3
1.00.00
Device Vendor 1
3, 2
Hardware Info Table
ID
Device
Type ID
Manufactur
er ID
Device ID
Hardware
Version
Software
Version
Vendor
Specific
Protocol
1
1
1234
1
*
1.0-5.5
XY=2; Z=1
1
´2
1
2345-1
1.1
*
1.0-5.5
XY=2; Z=2
2
3
2
1234
2
*
1.0-5.5
XY=2; Z=3
1
4
2
2345-1
2.2
*
1.0-5.5
XY=2; Z=4
2
5
3
2345-1
3.3
*
1.0-5.5
XY=2; Z=5
2
6
3
0815
4711
*
1.0-2.0; 3
XY=2; Z=6
3
XML according
FDTScanIdentSchema
Search for
corresponding entry in
Hardware Info Table
Manufacturer ID = 1234
Device ID
= 1
Hardware Vers = 2.3.1.2
Software Vers = 3.12.4
Manufacturer ID = 1234
Device ID
= 2
Hardware Vers = 2.4.1.2
Software Vers = 3.00.4
Network Management
Scan Field Bus and Create Network Topology (2/2)
Comm
DTM
Trigger bus address setting at
Communication DTM for
the newly added
Bus Address 1
Device DTMs
IDtmScanEvents::
OnScanResponse()
IFdtChannelSubTopology2:
Set bus addresses in
DTM Parameter XML
Manufacturer ID = 1234
Device ID
= 1
Hardware Vers = 2.3.1.2
Software Vers = 3.12.4
SetChildrenAddresses()
Bus Address 3
Manufacturer ID = 1234
Device ID
= 2
Hardware Vers = 2.4.1.2
Software Vers = 3.00.4
Bus
Address = 1
Bus
Adress = 3
XML according
FDTScanIdentSchema
Device
DTM
Device
DTM
Manufacturer ID = 1234
Device ID
= 1
Hardware Vers = 2.3.1.2
Software Vers = 3.12.4
Manufacturer ID = 1234
Device ID
= 2
Hardware Vers = 2.4.1.2
Software Vers = 3.00.4
Network Management
Bus Address Management in User Interface
Trigger bus address
setting to change address
in Comm DTM ActiveX control
Comm
DTM
Open ActiveX control
IFdtChannelSubTopology2:
SetBusAddresses(withGUI)
Set bus addresses in
DTM Parameter XML
Device
DTM
Device
DTM
Bus
Address = 1
Manufacturer ID = 1234
Device ID
= 1
Hardware Vers = 2.3.1.2
Software Vers = 3.12.4
Bus
Address = 3
Manufacturer ID = 1234
Device ID
= 2
Hardware Vers = 2.4.1.2
Software Vers = 3.00.4
Scenarios










Data exchange between Frame Applications
Reporting / Documentation
Audit Trail
Alternative Communication Paths
Bus Master Configuration
Control System Configuration
Bus Master without Gateway capabilities
Process Monitoring
Network Management
Update and Replacement
Update & Replacement
 Scenarios
 Device is replaced by another instance of
the same type
 Device is replaced by another device of the same classification, but from
another manufacturer
 FDT Definition
 Dataset Format IDs
 DTM Parameter access
- DTM Parameter XML (IDtmParameter interface)
- DTM Item XML (IDtmSingleInstanceDataAccess interface)
- Semantic IDs
Update & Replacement
Scenario: Update (1/4)
 Device is replaced by another instance of the same type
 New instance has new firmware version that is not supported by the
installed DTM
 DTM must be upgraded
 New DTM uses different data set format, but can load old data set format
Update & Replacement
Scenario: Update (2/4)
1. Save
Old
DTM
2. DTM stores binary data in
Frame Application database +
binary data format information
(used and supported)
´Device Data Table
Device
ID
DTM Binary Data
Used Dataset
Format
Supported
Dataset Formats
Device 3
0xAF1255FFFFFFFFFFF...
123-456
123-456
Vendor specific identifier that
specifies format of DTM data set.
Update & Replacement
Scenario: Update (3/4)
5. Update DTM / Device Catalog and
store information about new installed DTM
(IDtmInformation / IDtmInformation2)
4. Install
new old
DTMdevice
and register
3. Replace
with in
Windows-Registry
new device
DTM
Store dataset formats
that are supported
DTM Table
ID
Name
Version
FDT
Version
Vendor
ProgID
1
SomeDeviceDTM
1.00.00
1.2.1
M&M
MMDtm.ExampleDevice
ID
DTM
ID
Name
Version
Vendor
1
1
Device Type 1
1.00.00
DeviceVendor 1
1, 2
DTM Device Type Table
Supported
Protocols
Required
Protocols
´2
1
Device Type 2
1.00.00
Device Vendor 1
1, 2
3
1
Device Type 3
1.00.00
Device Vendor 1
3, 2
Dataset Format Table
Device
Type ID
Supported
Dataset Format
1
123-456
1
123-4567
1
123-45678
Scan Windows-Registry
for installed DTMs
Protocol Table
Hardware Info Table
ID
Device
Type ID
Manufactur
er ID
Device ID
FDT-Category
Hardware
Version
Software
Version
Vendor
Specific
Protocol
1
1
1234
1
*
1.0-5.5
XY=2; Z=1
1
´2
1
2345-1
1.1
*
1.0-5.5
XY=2; Z=2
2
3
2
1234
2
*
1.0-5.5
XY=2; Z=3
1
4
2
2345-1
2.2
*
1.0-5.5
XY=2; Z=4
2
5
3
2345-1
3.3
*
1.0-5.5
XY=2; Z=5
2
6
3
0815
4711
*
1.0-2.0; 3
XY=2; Z=6
3
ID
Identifier
Name
1
1234-23456-2345
Profibus DPV1
2
7890-6543-11111
Vendor Specific
3
1234-23456-2346
HART
FDT_DTM
MMDTM.ExampleDevices
…
…
…
XYDTM.XYZDevices
Windows-Registry
Update & Replacement
Scenario: Update (4/4)
DTM Table
ID
Name
Version
FDT
Version
Vendor
ProgID
1
SomeDeviceDTM
1.00.00
1.2.1
M&M
MMDtm.ExampleDevice
New installed
DTM
ID
DTM
ID
Name
Version
DTM Device Type Table
Supported
Protocols
Vendor
1
1
Device Type 1
1.00.00
DeviceVendor 1
´2
1
Device Type 2
1.00.00
Device Vendor 1
3
1
Device Type 3
1.00.00
Device Vendor 1
Dataset Format Table
Required
Protocols
Device
Type ID
1, 2
1
123-456
1
123-4567
1
123-45678
1, 2
7. New installed DTM loads
„old“
3,
2
dataset and converts it to new
format
Supported
Dataset Format
´Device Data Table
Device
ID
DTM Binary Data
Used Dataset
Format
Supported
Dataset Formats
Device 3
0xAF1255FFFFFFFFFFF...
123-456
123-456
Frame Application uses dataset format stored together with
DTM binary data to search for DTM supporting this format
Update & Replacement
Scenario: Replacement (1/2)
 Device is replaced by another device of the same
classification, but from another manufacturer
 DTM must be replaced by another DTM
 Data set is incompatible
 Data exchange between two totally different DTM provided by different
vendors
Update & Replacement
Scenario: Replacement (2/2)
Old
DTM
IDtmParameter:GetParameter()
OR
IDtmSingleInstanceDataAcess:Read()
DTM for new device
DTM for device that must be replaced
New
DTM
IDtmParameter:SetParameter()
OR
IDtmSingleInstanceDataAcess:Write()
Frame Application reads parameter values from „old“
DTM and sets it in „new“ DTM. The mapping between
parameters in the DTMs is done by Semantic IDs.
Only common defined parameters, e.g. defined by a
profile or by a field bus specification, are exchanged.
Discussion / Questions
M&M Software
Thank you for your
attention
M&M Software GmbH reserves all rights for its documents and printed
information. These documents and information material may be used
internally for the designated purpose. But this material, either completely or
in parts, may not be passed on to third parties, especially to competitors of
the M&M Software GmbH, and it may not be duplicated.
These documents and information material contain confidential information
and you are therefore requested to keep it strictly confidential. You are also
requested to commit your staff that is using these documents and
information, to the confidentiality obligation. Thank you.