Search
Subscribe

Bookmark and Share

About this Blog

As enterprise supply chains and consumer demand chains have beome globalized, they continue to inefficiently share information “one-up/one-down”. Profound "bullwhip effects" in the chains cause managers to scramble with inventory shortages and consumers attempting to understand product recalls, especially food safety recalls. Add to this the increasing usage of personal mobile devices by managers and consumers seeking real-time information about products, materials and ingredient sources. The popularity of mobile devices with consumers is inexorably tugging at enterprise IT departments to shifting to apps and services. But both consumer and enterprise data is a proprietary asset that must be selectively shared to be efficiently shared.

About Steve Holcombe

Unless otherwise noted, all content on this company blog site is authored by Steve Holcombe as President & CEO of Pardalis, Inc. More profile information: View Steve Holcombe's profile on LinkedIn

Follow @WholeChainCom™ at each of its online locations:

« Everywhere and nowhere | Main | The Funding of the Emerging Semantic Web »
Thursday
Mar202008

Ownership Principles for Database Design

Here is one of my favorite data ownership references published by the MIT Sloan School, Cambridge, Massachusetts:

Why Not One Big Database? Ownership Principles for Database Design (by Marshall Van Alstyne, Erik Brynjolfsson and Stuart Madnick) Copyright © 1993, 1994 Van Alstyne, Brynjolfsson, and Madnick, All Rights Reserved

Some quotes I love from this publication:

“Design Principle 5 : No amount of standardization is sufficient to ensure new data availability.”

The fundamental point of this research is that ownership matters. Any group that provides data to other parts of an organization requires compensation for being the source of that data. When it is impossible to provide an explicit contract that rewards those who create and maintain data, "ownership" will be the best way to provide incentives. Otherwise, and despite the best available technology, an organization has not chosen its best incentives and the subtle intangible costs of low effort will appear as distorted, missing, or unusable data. Decentralization concerns equipment and development, but it also concerns intangible issues of ownership and control.” (emphasis added)

If the foregoing peaks your interest, here is the abstract summary:

“This research proposes database decentralization and incentive principles which drive information sharing and ultimately system performance. Existing research has identified the benefits of centralized control while formalizing the importance of setting standards, enhancing user transparency, and reducing organization-wide data inconsistency. In practice, however, many centralization and standardization efforts have failed, typically because departments lacked incentives or needed greater local autonomy. While "ownership" has often been described as the key to providing incentives, these motivational factors have largely eluded formal characterization. Using an incomplete contracts approach from economics, we model the costs and benefits of decentralization, including critical intangible factors, by explicitly considering the role of data "ownership." There are two principal contributions from the approach taken here. First, it provides rigorous mathematical definitions and a framework for analyzing the incentive costs and benefits arising from database decentralization. Second, this theoretical framework leads to the development of a concrete model and eight normative principles for improved database design. Applications of this theory are also illustrated through case histories.” (emphasis added)

Keywords : Database Design, Centralization, Decentralization, Distributed Databases, Ownership, Incomplete Contracts, Incentives, Economic Modeling

PrintView Printer Friendly Version

EmailEmail Article to Friend

References (1)

References allow you to track sources for this article, as well as articles that were written in response to this article.

Reader Comments

There are no comments for this journal entry. To create a new comment, use the form below.

PostPost a New Comment

Enter your information below to add a new comment.

My response is on my own website »
Author Email (optional):
Author URL (optional):
Post:
 
Some HTML allowed: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <code> <em> <i> <strike> <strong>