Chorafas Identification (1) Pertemuan 19-20

2. Chorafas Identification (1)Pertemuan 19-20 Matakuliah : M0594 / Enterprise System Tahun : 2007

3. Chorafas Identification (1)

4. Chorafas Classification/Identification • The concept of Underpinning a Classification Code • Benefits Resulting from Architecturing an Identification Code • Developing the Classification Part of a Parallel Code System • Example of Classification • Coding for Organized complexity

5. Introduction • Down to its fundamentals, an identification code, such as EPC, is a composition of numbers (binary, octal, decimal, hexadecimal, or other), letters or other symbols used to identify a physical or logical entity (for example, a motor vehicle, a book, a razor, or an information element (IE)) • A classification code is prerequisite to identification because it enables an item to express its relationship to other items of the same or similar nature • Identification (ID) should be a short number designed for cost-effectiveness and error-free data transcription and transmission. • The classification code (CC) is a semantic and taxonomical. It should be a databased descriptiove structure, the goal of which is to provide detail and remove ambiguity

6. Introduction

7. Introduction • The rationalization of identification and definition of all materials, as well as of the internal structure of a database, is at the very heart of every classification system • A flexible and effective organization can be instrumental in putting into application the opportunities presented by rapid developments in technology • As discussed in the previous chapter, one of these developments is very low-cost chips able to serve as ID elements. • This has important implications on the nature of input and output: where transactions happen, how they are recorded, and when the database is updated

8. Introduction • Years of practical experience with development and implementation of identification codes and classification codes have demonstrated that one single number cannot perform both functions. • Efficient coding is a problem of specialization. • To develop a cost-effective coding system, it is necessary to select the most compact, complete, and methodological solution, and to implement this solution in the population of physical items, or information elements, that will be stored in mass storage media and retrieved interactively online.

9. The concept of Underpinning a Classification Code • A code can consist of characters such as letters, punctuation marks, or numerals. • Identification through characters such as punctuation marks is the least suitable for data communication and data processing. • The use of letters has a greater coding capacity per character position than decimal numbers because alphabes consist of more than ten different characters. The radix, or base, for a numbering system based on the English alphabet would be twenty-six. • Code composed of letters alone can thus be shorter than purely decimal numerical codes: but even better, one can develop a radix 32 code that is expressed in binary form and is used on a strictly numerical basis. • With this coding, the pseudo-alphabetic characters A, B, C ... X, Y, Z serve as an extention of numerical signs to reach 32 positions. • This solution has been adopted by the Dimitris Chorafas System (DCS) and it helps shorten the field size in terms of transcription, storage, and transmission

10. The concept of Underpinning a Classification Code • The classification code is a different ballgame. In its background is organization and semantics. • In a classification system, items of similar type must be grouped into homogeneous categories using their similarities and the relationships developing therefrom. • This is primarily a taxonomical approach, and it has been chosen to underpin the classification part of DCS. • Taxonomy is an important organizational principle, but is not everything in terms of a rational classification • Left to its own devices, a collection of sources such as machines, books, drawings, reports or other entities will not contribute original research or invent anything. • However, if these entities are efficiently classified, this will save that managers, engineers, designers, and other professionals would otherwise waste in seeking buried or widely scattered information • This is where the economies of classification system come in.

11. The concept of Underpinning a Classification Code • The key to a valid classification system-design lies in a few basic rules: • Observed the logical structure and general requirements of the population under study. • Establish and observe classification rules and the process of ordering that these imply • Properly define entity characteristics so that the resulting codification can be tailored to a user’s needs • Assure the right place (and only one place) for each physical item (or data) in the population being ordered • Provide for further expansion of the system being developed as the applications domain itself enlarges.

12. The concept of Underpinning a Classification Code • There are also identification rules that must be followed. • First and foremost the identification code must be short for economical transcription and transmission purposes. • It must be linked to the classification code in a way that allows one to distinguish between user requirements (technical, commercial other) concerning the same item. In addition, it must feature a parity check for error control (something both UPC and EPC are, thus far, lacking) • In conclusion, once properly developed, a classification/identification system becomes a pivot point in technical information, management information, and internal control.

13. The concept of Underpinning a Classification Code

14. Benefits Resulting from Architecturing an Identification Code • With DCS, each classification number has a dedicated identification code in one-to-one correspondence, and that an ideal ID code must be short and unique. • One can enrich this reference with the statement that this uniqueness should respond to functional requirements. • The problem that arises most often is that there are conflicting functional criteria. • What suit one department is not necessarily what another department wants to have. • The identification number of DCS has been divided into three parts, in order of priority: • Basic code, <bc>, for engineering characteristics • Suffix, <s>, for commercial requirements • Origin, <o>, for identification of the factory where the product is made

15. Benefits Resulting from Architecturing an Identification Code • Exhibit 10.3 identifies the nuts and bolts of the adopted solution: • The basic code is allocated on the basis of the technical characteristics of an item (or data) as outlined in the classification code (taxonomy) and <bc> oriented further defiens. • The suffix <s>, which complements the basic code, identifies commercial or secondary characteristics of an item (or data), depending on the family in which the item belongs • The origin <o> indicates where an item was made (multiple production sites is a frequent case with globalization), or where the item is installed (this is the case with machines)

16. Benefits Resulting from Architecturing an Identification Code

17. Benefits Resulting from Architecturing an Identification Code

18. Developing the Classification Part of a Parallel Code System • Classification can be done either linearly, through a roster, or in a matrix form permitting two entries to a taxonomical pigeonhole. • The linear order of classification has a major weakness: the difficulty of inserting other items in the list (or deleting them) without upsetting the order. • Even if care has been taken to provide spaces for further growth, no one can foresee the precise number of spaces needed during, say, the next 10, 20 or 30 years – which is a reasonable lifetime for a new classification system. • Therefore, the decision was taken during the design phase of DCS to use a matrix basis for classification. This matrix, shown in Exhibit 10.6, observes a taxonomical order

19. Developing the Classification Part of a Parallel Code System

20. Developing the Classification Part of a Parallel Code System

21. Developing the Classification Part of a Parallel Code System • The example shown in Exhibit 10.6 is the one retained and applied at Osram, and is further discussed in subsequent chapter sections. • Note that everything used by company has been classified: from products, machines, instruments, and other assets, to human resources and management reports. • In the manner explained in preceding paragraphs, each family has been divided into 100 classification groups, and each group into 100 taxonomical subgroups or classes • The way to proceed with the classification is shown in Exhibit 10.7

22. Developing the Classification Part of a Parallel Code System

23. Developing the Classification Part of a Parallel Code System • Once the outlined preparatory number is allocated, associated with this classification. • Such an identification number, is used in transcriptions, transmissions, accesses, transfers, and search procedures. • As already seen, this is the running number of the simplest linear form: the basic code <bc> • As shown in Exhibit 10.8, basic code is the metalayers of suffix and origin

24. A matter of Fact Example of Classification and Further Definiens • The choice of both a six-digit basic (including parity) code and a six-digit taxonomical number (two decimal digits per family, group, class) has been influenced by requirements of economy, dependability and the assurance of a short dialing system, which comes in handy today in connection with nomadic computing. • A six-digit to eight-digit number is quite similar to a telephone number in most cities, a fact giving a good hint as to the possible size of an identification or classification code, as well as to the user’s ability to retain either one in memory • If one allocates the digits in the classification system – particularly its taxonomical part – in this way: • KL, for family (therefore, the original matrix) • MN, for group (a subset of the family) • PR, for class (a subset of the group) • Then one can easily see that KL is a metalayer of MN and that MN is a metalayer of PR. • The existance of PR is conditioned by the MN to which it belongs, and that of MN by the KL of which it is part. That is PR and MN have no own existance.They get meaning only within their metalayer.

25. A matter of Fact Example of Classification and Further Definiens

26. Coding for Organized complexity • A classification and identification structure specifically designed for usage in conjunction with computer-based systems must be able to cope with the organized complexity that characterizes modern business and its any-to-any network connection. Organized complexity results from the existance of a large number of information elements that have a meaningful relationship between themselves, their origins, their environments, and their users. • Information elements are, as a rule, distributed unevenly within the working procedures of an industrial, commercial, or financial organization. Furthermore, operational characteristics and their change over time make the process of data management more complex. • This suggest the need for a systematic arrangement of similar items into suitably selected categories that can be restructured without having to start the classification work from scratch.