Guide to the TechWeb Network

Intelligent Enterprise

Better Insight for Business Decisions

Intelligent Enterprise - Better Insight for Business Decisions
search Intelligent Enterprise
Advanced Search
RSS
Webcasts
Whitepapers
Subscribe
Home




January 14, 2002

/020114/502analytic1_1.jhtml">

Symmetry Found

Analytic problem solving and communication are easier with a standard language

By Erik Thomsen

Continued from Page 1

Thus, the query SELECT SALES WHERE STORE = CAMBRIDGE AND YEAR = 1996 parses into T1: sales, T2 : store, i2n: Cambridge, T3 : year, i3n : 1996. This query reads as "Sales" is the name of type one, "Store" is the name of type two, "Cambridge" is the name of the nth instance of type two, "Year" is the name of type three, and "1996" is the name of the nth instance of type three. The result set is the collection of instances for the type sales that correspond to Cambridge 1996. So for this query, sales is the content, and store and time are the locators.

In contrast, for the query SELECT STORE WHERE SALES > 300, stores are the content because you are only given the name, and sales are the location as you are given the name and instance.

The dimension and measure symmetry applies to all operations, not just querying (which is supported by many analytic models).

TYPE STRUCTURES

Types can have any form of single or multiple hierarchy, which can be leveled, ragged, or mixed. Types, in this sense, provide for very rich dimension structuring. You can combine types through structural operators such as Cartesian product, insert, concatenate, and 1-N and 1-1 correspondence. In this sense, types behave like sets and can support the set-like operators used in relational algebra. Types can also enter into equations with the whole type serving as an independent variable (right-hand side of the equation) or dependent variable (left-hand side of the equation) or with an instance of a type serving, on either side of the equal sign. In other words, formulas may be associated with the instances of a type or between types.

Type Schemas. Schemas are type structures in LC form. For example, assume you have the types "time," "store," "product," and "sales." Using time, store, and product as locators and sales as contents yields (TIME. STORE. PRODUCT.)- SALES.

The schema breaks down as follows:

  • The operator "" means "cross product" or "Cartesian join," so the expression in parentheses above refers to the cross product of the unique instances of Time, Store, and Product.
  • The operator "~" means the count of the instances denoted by the expressions on either side of "~"are in one-to-one correlation with each other.
  • The sales term, which has the form "Tx", (note without the ".") means some instance of the type named "x." or "sales."

In other words, you take the cross product of the distinct instances of time, store, and product and for every intersection associate some value of sales. This functional definition of a so-called cube or fact table captures the "sales" measurement event. It implies that, when measuring sales, you need to know for which stores, times, and products you are doing the measuring. However, you don't need to know what the sales were. That's why they're being measured!

What if instead of measuring the sales values for particular store-time-product combinations, you wanted to measure the distribution of stores as a function of how much they sold of all products in 2000? How would you express the schema using the same combinatorial operators that were just introduced? How about the following? (SALES.BIN. PRODUCT.ALL TIME.YEAR.2000) ~ COUNT (STORE).

This schema says to take the cross product of every sales bin with the "all" member of the product dimension and the "year 2000" member of the time dimension, and for every defined intersection associate some value for the count of stores.

The design, implementation, use, and maintenance of activity-based management systems, enterprise decision support, performance indicators, or any other decision-oriented analytic solution requires clear thinking about and within the notions of type, type structure, schema, and model.

In future columns I will leverage these concepts to describe ways of creating different types of analytic solutions, or components of analytic solutions such as formulas, and help the reader think through their associated challenges.



Rate This Article

Comments:

Optional e-mail address:


Erik Thomsen [erik@dimsys.com] is cofounder of Power Thinking Tools, which developed the first OLAP engine with integrated statistics, visualization, text processing, and object management. He is a researcher and consultant for Dimensional Systems and focuses on integrated multitechnology analytic solutions. He is the author of OLAP Solutions (John Wiley & Sons, 1997) and coauthor of Microsoft OLAP Solutions (John Wiley & Sons, 1999).


RESOURCES

LC Model paper: www.dsslabcom

Related Article at IntelligentEnterprise.com:

"Symmetry Lost," March 30, 1999





IE Weekly Newsletter
Subscribe to the newsletter
    Email Address







InformationWeek Business Technology Network
InformationWeekInformationWeek 500InformationWeek 500 ConferenceInformationWeek AnalyticsInformationWeek CIO
InformationWeek EventsInformationWeek ReportsInformationWeek MagazinebMightyByte and SwitchDark Reading
Digital LibraryIntelligent EnterpriseInternet EvolutionNetwork ComputingNo Jitter
space
Techweb Events Network
InteropVoiceConWeb 2.0 ExpoWeb 2.0 SummitEnterprise 2.0 ConferenceMobile Business ExpoSoftware ConferenceCSI - Computer Security Institute
Black HatGTECEnergy CampMashup CampStartup Camp
space
Light Reading Communications Network
Light ReadingLight Reading EuropeUnstrungLight Reading's Cable Digital NewsConstantinopleInternet Evolution
Heavy ReadingLight Reading Live!Light Reading InsiderEthernet ExpoOptical ExpoTeleco TVTower Technology Summit
space
Financial Technology Network
Advanced TradingBank Systems & TechnologyInsurance & TechnologyWall Street & TechnologyAccelerating Wall StreetBank Systems & Technology Executive SummitBuyside Trading SummitInsurance & Technology Executive Summit
space
Microsoft Technology Network
MSDN MagazineTechNetThe Architecture Journal
space