Supply Chain Communication Tool Interface constraints
1st May 2009
Introduction • Within the Supply Chain Communication tool, the IT developer has to build an interface between Supplier and Customer. • The tool interface allow exchange of information. • Constraints for tool interface have to be setup to ensure efficient and proper exchange. • The tool will be required until after the 2018 registration window • The basis for the tool is the Exposure Scenario Development and Communication Model developed by the Cefic Supply Chain Communication Task Force. Specifically, the tool supports the communication component of the Model. See slide 3 - Shaded green section. Reminder from IT requirements document – the phased communication:
In Phase 1, the tool will provide functionality to download the information provided by Suppliers.
The tool will have the option to provide an extract in XML format.
Page 2
ES Development & Communication model M/I and/or M/I-DU Associations => determine strategy Systematic assessment of safe uses (use of Tier1 tool)
for safe uses only
Map uses and use conditions in supply chain
M/I Communicate Uses (ES titles, Use Descriptors) to direct DU for further communication in the supply chain
Initial ESs, ES titles and Use Descriptors
Yes
M/I and DU partnership via trade associations
M/I and selected DU’s
Generic ES Development
Specific ES development
• Input of DU Associations • Development GES library
• Input of selected customers • Use of Cefic ES template
DU Wait for final ES
No
Final Exposure Scenario (M/I)
Legend M/I = Manufacturer / Importer DU = Downstream User
DU Use covered?
or DU • Complete feedback form • Await decision M/I
Communication to direct DU
DU • Prepare CSA/CSR • Inform Agency
Distribution of e-SDS
For specific products and applications the appropriate (next) steps in the above diagram need to be determined based on expert judgement: not always all steps are needed and/or the order can be adapted.
Data Hierarchy Material Material Short Name Material Code Other identifiers (Company defined)
(link to PDF file)
0:1
1:n
0:n
Use Identifier
Product Trade Product Name Trade Product Code Other identifiers (Company defined) Input Deadline
1:n
Use Descriptor = Process Activities Sector of Use Process Category Product Category Article Category Environmental Release Category
N/A ALL SU0-1 SU0-2 SU1 SU2 …
ERC ERC1 ERC2 ERC3 ERC4a ERC4b ERC5 …
Supplier 1:n
Name - Code email
Page 4
N/A ALL PROC0 PROC1 PROC2 PROC3 …
PC N/A ALL PC0 PC1 PC2 …
1:n
1:n
Customer
PROC
1:n
0:n
1:n
Name ID# - Code email (default) Address Optional alternative emails for specific products
SU
Exposure Scenario
AC AC0 AC1-1 AC1-2 AC2 AC3 AC4 …
Data for Upload and Download Fields (for Download) 1. Supplier Code 2. Supplier Name 3. Customer Code (mandatory) 4. Trade product code (mandatory) 5. Trade Product name 6. Material Code(s) mandatory (multiple possible) 7. Material Name (one per Material Code) 8. Input Deadline 9. Use Identifiers (mandatory)
Page 5
Fields (for Upload) 1. Customer Code 2. Trade Product Code 3. Material Code 4. Use Identifiers
Supplier Customer Customer Name ID# - Code email (default) Address Optional alternative emails for specific products
• • • •
Supplier 1:n
Name - Code email
The Supplier database contains all supplier’s customers. The tool interface is designed for one customer at a time. The xml file is downloaded by customer: it contains supplier name and code. The (supplier’s) customer code is mandatory to reconcile information at the supplier level.
Page 6
Customer Product Product Trade Product Name Trade Product Code Other identifiers (Company defined) Input Deadline
•
The interface contains the list of products purchased by the Customer. The list will be exhaustive.
•
Customer will see only the products he purchases.
•
Customers will see all products he purchases, regardless of the feedback deadline or the need for an ES.
•
The product is identified by trade name & code.
•
Suppliers will determine the feedback deadline for a product based on the registration requirements for the constituent substances. The deadline is defined on product level.
1:n
Customer Name ID# - Code email (default) Address Optional alternative emails for specific products
Page 7
Product Material • Material Material Short Name Material Code Other identifiers (Company defined)
•
1:n
•
Customers are responsible for mapping supplier trade and material codes to their internal naming/coding system. If needed, the supplier can define on or more materials linked with the product. Material can be identified by name and code.
Product Trade Product Name Trade Product Code Other identifiers (Company defined) Input Deadline
Page 8
Product Use Identifier Use Identifier Product Trade Product Name Trade Product Code Other identifiers (Company defined) Input Deadline
•
• •
0:1
Exposure Scenario (link to PDF file)
Phase 1: Suppliers will advise Customers of the Uses to be included in the registration dossier. Customers can advise Suppliers if their particular Use is not covered The Uses are listed on the product level. For each Product, Suppliers will make available the following Use Identifier information:
•
1:n
Use Descriptor = Process Activities Sector of Use Process Category Product Category Article Category Environmental Release Category
Use Description Sector of Use Process Category Product Category Article Category Environmental Release Category
On phase 2, the supplier will make available a/ PDF file containing the Exposure Scenario. Page 9
Use identifier Standard Libraries •
SU N/A ALL SU0-1 SU0-2 SU1 SU2 …
0:n
Use Identifier Use Descriptor = Process Activities Sector of Use Process Category Product Category Article Category Environmental Release Category Optional flag
• PROC N/A ALL PROC0 PROC1 PROC2 PROC3 …
1:n
PC 1:n 0:n
1:n
ERC ERC1 ERC2 ERC3 ERC4a ERC4b ERC5 …
•
AC
N/A ALL PC0 PC1 PC2 …
AC0 AC1-1 AC1-2 AC2 AC3 AC4 …
Page 10
•
The Uses are listed on the product level. Suppliers will undertake a process to assign Use Descriptors to their products The Standard Use Descriptors (sector of uses, process & product & article & Env. release categories) are selected from the Standard Libraries. Article Category & Sector of Use are not mandatory
