Make up your mind, is it Information or Data?

D-I-K-W Pyramid1

It was for a while I wondered if Data and Information are interchangeable. Actually, they are NOT, but when it comes to Architecture, almost everyone thinks (except for Information Architects)  Data Architecture and Information Architecture are same. One of my colleague, who is now president of local DAMA chapter pointed me to DKIW pyramid.

Using Ackoff and other references, the following are definitions of data, information, knowledge and wisdom, but according to Danny P. Wallace, a professor of library and information science, explained that the origin of the DIKW pyramid is uncertain. 2. The presentation of the relationships among data, information, knowledge, and sometimes wisdom in a hierarchical arrangement has been part of the language of information science for many years. Although it is uncertain when and by whom those relationships were first presented, the ubiquity of the notion of a hierarchy is embedded in the use of the acronym DIKW as a shorthand representation for the data-to-information-to-knowledge-to-wisdom transformation. 

Ackoff, R, DKIW Pyramid, From data to wisdom, Journal of Applied Systems Analysis 16 (1989) 3–9,

Ackoff, R, DKIW Pyramid, From data to wisdom, Journal of Applied Systems Analysis 16 (1989) 3–9,

Data: Often referred to as the lowest conceptual form from which information can originate, data are text, numbers, symbols, graphics or images that are representations of facts or properties of objects, events, and their environment. Data are individual facts that have no meaning by themselves out of context. Examples of Data: Green, an image of building.

Information:  Data in the context that provides perspective and meaningful insights for decision-making is Information. The term often addresses questions that begin with such words as who, what, when and how many. Examples of Information: Train velocity, wheel temperature, product inventory.

Knowledge: This term describes a mix of experience, values, contextual information and expert insight that makes possible the transformation of information into instructions. Knowledge can be obtained either by transmission from another who has it, by instruction or by gaining it from experience. Knowledge often becomes embedded, not only in documents or repositories, but also in organizational routines, processes, practices, and norms. Examples of Knowledge: On-the-job training or experience, job shadowing, formal training courses, standard operating procedures or manuals.

Wisdom: This term refers to the application of knowledge gained through learning and experience, the ability to make judgments or give advice based on previous knowledge, experience, and insight. Within an organization, intellectual capital or organizational wisdom is the application of collective knowledge. Examples of Wisdom: An example of wisdom is, “It rains because it rains.” This statement encompasses an understanding of all the interactions that happen between raining, evaporation, air currents, temperature gradients, changes and raining.

 

Meta-Data Management3

Metadata is what gives your data a frame of reference. Forrester Research defines metadata as “the information that describes or provides context for data, content, business processes, services, business rules and policies that support an organization’s information systems.” For example, Apple Corporation’s App Store sells software applications online. The data, in this case, is the applications, or apps. The metadata is the information about those apps—an app’s description, price, user rating, reviews, and developing company.

Some organizations separate metadata into three major categories:

  • Technical metadata: provides technical information about the data, such as the name of the source table, the source table column name, and the data type (e.g., string, integer);
  • Business metadata: supplies the business context around data, such as the business term’s name, definition, owners or stewards, and associated reference data;
  • Operational metadata: furnishes information about the use of the data, such as date last updated, number of times accessed, or date last accessed.

Metadata is the “who, what, where, how, when, and why” about data. It is the core information about data such as where to find it, how it got where it is, and its lineage (what systems produced or changed it). According to Gartner4, metadata unlocks the value of data, and therefore requires management attention.

Types of Data and “Master of all Data = Master Data” Management5

According to MSDN (Wolter et al, 2006), there are essentially five types of data

There are essentially five types of data in corporations:

Unstructured—This is data found in e-mail, white papers like this, magazine articles, corporate intranet portals, product specifications, marketing collateral, and PDF files.

Transactional—This is data related to sales, deliveries, invoices, trouble tickets, claims, and other monetary and non-monetary interactions.

Metadata—This is data about other data and may reside in a formal repository or in various other forms such as XML documents, report definitions, column descriptions in a database, log files, connections, and configuration files.

Hierarchical—Hierarchical data stores the relationships between other data. It may be stored as part of an accounting system or separately as descriptions of real-world relationships, such as company organizational structures or product lines. Hierarchical data is sometimes considered a super MDM domain, because it is critical to understanding and sometimes discovering the relationships between master data.

Master—Master data are the critical nouns of a business and fall generally into four groupings: people, things, places, and concepts. Further categorizations within those groupings are called subject areas, domain areas, or entity types. For example, within people, there are customer, employee, and salesperson. Within things, there are product, part, store, and asset. Within concepts, there are things like contract, warrantee, and licenses. Finally, within places, there are office locations and geographic divisions. Some of these domain areas may be further divided. Customer may be further segmented, based on incentives and history. A company may have normal customers, as well as premiere and executive customers. Product may be further segmented by sector and industry. The requirements, life cycle, and CRUD cycle for a product in the Consumer Packaged Goods (CPG) sector is likely very different from those of the clothing industry. The granularity of domains is essentially determined by the magnitude of differences between the attributes of the entities within them.

There are some criteria that can help you determine if Data you have can be used or viewed as Master Data. You can check for Behavior, Lifecycle, Cardinality, Lifetime, Complexity, Value, Volatality, and Reuse. These are criteria can be used together to decide if the data should be managed as Master Data. There are tools for Master Data Management, an entire domain on Information Architecture is devoted to describing Master Data Management.

References

  1. Ackoff, R, DKIW Pyramid, From data to wisdom, Journal of Applied Systems Analysis 16 (1989) 3–9
  2. Wallace, Danny P. (2007). Knowledge Management: Historical and Cross-Disciplinary Themes. Libraries Unlimited. pp. 1–14. ISBN 978-1-59158-502-2.
  3. Hillam, J, What is Metadata Management?, Intricity 101, Source Youtube
  4. Gartner, 2011, Metadata Management
  5. Wolter, R et al., 2006, The What, Why, and How of Master Data Management available at https://msdn.microsoft.com/en-us/library/bb190163.aspx

Comments

comments

Leave a Reply