Ana səhifə

Technical Blueprint version 10


Yüklə 204.62 Kb.
səhifə1/8
tarix24.06.2016
ölçüsü204.62 Kb.
  1   2   3   4   5   6   7   8




Technical Blueprint
version 2.10

version: 2.10

status: definitive

date: May 7, 2013

subject: Technical Blueprint of the renovated VBN Code system

© Vereniging van Bloemenveilingen in Nederland (VBN), 2011


All rights reserved. VBN rejects any liability for damages, directly or indirectly, of whatever nature, following from, or in any way related to applying the information contained in this document.

Summary


You are reading the ‘Technical Blueprint’ of the modernized VBN code system, the new method of identifying and specifying floricultural products and lots, adorned with the name ‘Linnaeus’ (the Latin name of the great taxonomist Carl von Linné).
This document is the technical translation and crystallization of an earlier (revised) ‘conceptual’ blueprint. That conceptual blueprint described in what way, and why, the new Linnaeus system differs from the current VBN code system. These changes pertain, in particular, to the:


  • extension of the VBN product code from 5 to 7 positions

  • addition and distribution of ‘fixed’ product features

  • increase of the number of ‘variable’ lot features

  • codification of rules and constraints governing lot specifications

  • introduction of feature groups

  • specification of composite lots

  • support of multiple languages.

In practice, the new code system will be reflected in modifications of the external data exchange among supply chain business partners and of the internal business software used by the parties involved. The external data exchange adjustments involve both the structure, contents and processing of:




  • fixed reference data captured in various code lists

  • variable lot data exchanged on paper or through electronic messages

Depending on the various roles of the parties involved, their specific needs, demands and IT levels, business applications will need to be modified so as to:





  • store and display the 7 digit product code

  • check that lot specification rules and constraints are duly respected

  • store and display multiple product- and lot features

  • store and display parts of composite lots.

This technical blueprint will serve as a starting point for implementing these software changes. The document has been reviewed by representatives of all involved parties: VBN, auctions, growers and traders.



Changes


Relative to the previous version 2.8 this new version 2.9 has been changed on the following counts:
Paragraph section change
3.2.3 changed

3.2.4 changed

3.2.5 changed

3.12.3 changed

4.1.2 changed

4.1.4 removed

4.2.2 changed

5.2 changed

5.3.1 changed

5.3.2 changed

5.4.6 changed

6.1 removed

6.2 changed
Whole document some textual corrections
TABEL OF CONTENTS


Summary 3

Changes 4



1. Introduction 8

1.1 Background 8

1.2 Purpose 8

1.3 Principles 9

1.4 Contents 9

1.5 Status 9

1.6 References 9

2. Linnaeus data model 11

2.1 Fixed data 11

2.2 Variable data 11

2.3 Data model notation 11

2.4 Technical data model 12

3. Linnaeus code lists 13

3.1 Common code list aspects 13



3.1.1 Field names 13

3.1.2 Update fields 13

3.1.3 Code list description 13

3.2 PRODUCT 14



3.2.1 Definition 14

3.2.2 Relationships 14

3.2.3 Contents 14

3.2.4 Example 14

3.2.5 Explanation 14

3.3 APPLICATION 15



3.3.1 Definition 15

3.3.2 Relationships 15

3.3.3 Contents 15

3.3.4 Example 15

3.3.5 Explanation 15

3.4 PLANT 16



3.4.1 Definition 16

3.4.2 Relationships 16

3.4.3 Contents 16

3.4.4 Example 16

3.4.5 Explanation 16

3.5 GENUS 16



3.5.1 Definition 16

3.5.2 Relationships 17

3.5.3 Contents 17

3.5.4 Example: 17

3.6 SPECIES 17



3.6.1 Definition 17

3.6.2 Relationships 17

3.6.3 Contents 17

3.6.4 Example 17

3.7 CULTIVAR 17



3.7.1 Definition 17

3.7.2 Relationship 18

3.7.3 Contents 18

3.7.4 Example 18

3.7.5 Explanation 18

3.8 PRODUCT FEATURE 18



3.8.1 Definition 18

3.8.2 Relationships 18

3.8.3 Contents 18

3.8.4 Example 19

3.8.5 Explanation 19

3.9 FEATURE TYPE 19



3.9.1 Definition 19

3.9.2 Relationships 19

3.9.3 Contents 19

3.9.4 Example 19

3.10 FEATURE VALUE 20



3.10.1 Definition 20

3.10.2 Relationships 20

3.10.3 Contents 20

3.10.4 Example 20

3.10.5 Remark 20

3.11 FEATURE GROUP 20



3.11.1 Definition 20

3.11.2 Relationships 20

3.11.3 Contents 21

3.11.4 Example: 21

3.12 REGULATORY FEATURE TYPE 21



3.12.1 Definition 21

3.12.2 Relationships 21

3.12.3 Contents 21

3.12.4 Example 21

3.12.5 Explanation 21

3.12.6 Business rules 22

3.13 REGULATION TYPE 22



3.13.1 Definition 22

3.13.2 Relationships 22

3.13.3 Contents 22

3.13.4 Example 22

3.14 NAME 22



3.14.1 Definition 22

3.14.2 Relationships 23

3.14.3 Contents 23

3.14.4 Example 23

3.14.5 Explanation 23

3.15 NAME TYPE 24



3.15.1 Definition 24

3.15.2 Relationships 24

3.15.3 Contents 24

3.15.4 Example 24

3.15.5 Explanation 24

3.16 LANGUAGE 24



3.16.1 Definition 24

3.16.2 Relationships 24

3.16.3 Contents 25

3.16.4 Example 25

3.16.5 Explanation 25

3.17 GROUP 25



3.17.1 Definition 25

3.17.2 Relationship 25

3.17.3 Contents 25

3.17.4 Example 25

3.18 PHOTO REFERENCE 25



3.18.1 Definition 25

3.18.2 Relationships 26

3.18.3 Contents 26

3.19 PHOTO TYPE 26



3.19.1 Definition 26

3.19.2 Relationships 26

3.19.3 Contents 26

4. Code list distribution 27

4.1 Distribution policy 27



4.1.1 Responsibilities 27

4.1.2 Complete set 27

4.1.3 Update detection 28

4.1.4 Removed 29

4.1.5 Definition of new, expired and changed items 29

4.2 Distribution technique 29



4.2.1 File format 29

4.2.2 Character set 30

4.2.3 Distribution channel 30

5. Linnaeus in EDI messages 31

5.1 Mapping the Linnaeus technical data model on EDI messages 31



5.1.1 Lot 31

5.1.2 Base product 31

5.1.3 Part 31

5.1.4 Lot feature 32

5.1.5 Photo reference 32

5.2 Extension of lot features 32

5.3 Harmonisation of the EDI messages 32

5.3.1 Uniform specification of lot features 33

5.3.2 Uniform field formats 33

5.3.3 Extension of the VBN product code 33

5.4 Specification of composite lots 34



5.4.1 Definitions of concepts 34

5.4.2 Dealing with nested composites 34

5.4.3 Dealing with hardware 35

5.4.4 Pricing of composites 35

5.4.5 Ordering parts 35

5.4.6 Base product and parts indicators 36

5.4.7 LIN-group structure alignment 36

6. Implementation suggestions and recommendations 37

6.1 Removed 37

6.2 Checking lot specification rules and constraints 37

6.3 Storing and displaying multiple lot features 37

6.4 Storing and displaying composite lots. 37




  1   2   3   4   5   6   7   8


Verilənlər bazası müəlliflik hüququ ilə müdafiə olunur ©atelim.com 2016
rəhbərliyinə müraciət