Data Silos
Get Data Silos essential facts below. View Videos or join the Data Silos discussion. Add Data Silos to your Like2do.com topic list for future reference or share this resource on social media.
Data Silos

An information silo, or a group of such silos, is an insular management system in which one information system or subsystem is incapable of reciprocal operation with others that are, or should be, related. Thus information is not adequately shared but rather remains sequestered within each system or subsystem, figuratively trapped within a container like grain is trapped within a silo: there may be a lot of it, and it may be stacked quite high and freely available within those limits, but it has no effect outside those limits.

Typical information silos in a hierarchic structured organization.

Information silos occur whenever a data system is incompatible or not integrated with other data systems. This incompatibility may occur in the technical architecture, in the application architecture, or in the data architecture of any data system. However, since it has been shown that established data modeling methods are the root cause of the data integration problem[], most data systems are at least incompatible in the data architecture layer.

Silo mentality

In management the term silo mentality often refers to information silos in organizations. Silo mentality is caused by divergent goals of different organizational units. It can also be described as a variant of the principal-agent problem. Silo mentality preferably occurs in larger organizations and can lead to a decreased performance and has a negative impact on the corporate culture. Silo mentality can be countered by the introduction of shared goals, the increase of internal networking activities and the flattening of hierarchies.[1]

Predictors for the occurrence of silos are

  • Number of employees
  • Number of organizational units within the whole organization
  • Degree of specialization
  • Number of different incentive mechanisms

This should not be confused with a data silo in computing, like application virtualization, operating-system-level virtualization, or a separation kernel.

Etymology

The term functional silo syndrome was coined in 1988 by Phil S. Ensor who worked in organizational development and employee relations for Goodyear Tire and Rubber Company, Eaton Corporation, and as a consultant. "Silo" and "stovepipe" (as in "stovepipe organization" and "stovepipe system") are now used interchangeably and applied broadly. Phil Ensor's use of the term "silo" reflects his rural Illinois origins and the many grain silos he would pass on return visits as he contemplated the challenges of the modern organizations with which he worked.[2][3][4][5]

See also

References

  1. ^ "Silo mentality in companies". Retrieved . 
  2. ^ Ensor, Phil (Spring 1988). "The Functional Silo Syndrome" (PDF). AME Target: 16. Retrieved . 
  3. ^ AME Study Group on Functional Organization (Summer 1988). "Organizational Renewal - Tearing Down the Functional Silos" (PDF). AME Target: 4-16. Retrieved . 
  4. ^ Pullin, James (Winter 1989). "Breaking Down the Functional Silos: Motorola Paging Division "Bandit" Plant" (PDF). AME Target. Retrieved . 
  5. ^ "Of Silos and Stovepipes". Language Log. University of Pennsylvania. 2006-03-27. Retrieved . 

External links


  This article uses material from the Wikipedia page available here. It is released under the Creative Commons Attribution-Share-Alike License 3.0.


Data_silos
 



 

Top US Cities