Preferencje help
Widoczny [Schowaj] Abstrakt
Liczba wyników
2012 | 59 | 172--181
Tytuł artykułu

Business Intelligence in Medium-Sized Companies : Experience from Successful BI4Dynamics Solution Projects

Treść / Zawartość
Warianty tytułu
Języki publikacji
Intelligence in Medium-sized companies: experience from successful Bi4dynamics solution projects 9.1 Overview Business Intelligence (BI), a concept which emerged in the 1990s, became over the years more mature, elaborated, but also diversified. Derived from the basic concepts of Management Information Systems (MIS) and combined with Decision Supports Systems (DSS), it appeared for a short period of time as the Executive Information Systems (EIS) [1]. When the concept of data warehouses (DW) were developed and on-line analytical concepts (OLAP) became popular, the domain of BI gained importance. BI has, as do all information systems, two sides. One of them is technology side which defines the structure and technologies used. It deals with the data warehouse as the central point of BI to which data have to be collected through sophisticated processes of ETL (Extraction Transformation- Loading) which connects business information solutions at an operational level with the data warehouse. This transfer of data in the past was very batch-oriented with certain delays; it became faster with less delays than recently and is nearly on-line or even fully on-line in some solutions. Once data are in the data warehouse, they have to be formatted and disseminated to managers. At this point, companies can use different technologies from the broad group of OLAP tools. All this technological diversity has to be integrated by the company that wants to build such a system. BI also has another side. Because BI is about reporting, analysis and decision support, it can be also observed from the user side from the business side. At the beginning, these viewpoints have been somewhat neglected and the technology side was more important. But when BI became mature, in-depth research on its quality of support that was provided for managers emerged. Questions about the Business Value of BI occur more and more often. Howson defines seven areas of the Business Value of BI [2]: - BI for management and control; - BI for improving business performance; - Operational BI; - BI for process improvement; - BI for improve customer service; - BI for discovering new business opportunities; - BI for government and public services. This definition implies that BI became, even if the same technologies are used, more diversified and elaborated. The term BI maturity, the research area of several researchers [3], is explained in the literature by several models. It is very often used in the Six-stage BI maturity model by TDWI [4] which delimits six stages and defines for each one its own structural characteristics, analytics ability and focus of the stage. According to that model an up-to-date BI system is in its Adult (fifth) stage, and where the Enterprise DW is used, dashboards and cascading scorecards are implemented; the focus of the BI systems is not only in insight but more in support for action. BI systems are moving toward six stages of the aforementioned model where structure can be described as analytical services and as imbedded BI. When a system is mature, leveraging the system becomes a crucial question for an organization. So it is not surprising that more and more research on BI is recently focused on the acceptance of BI by its users (namely managers). The Technology Acceptance Model (TAM). (original abstract)
Opis fizyczny
  • Kaiser U.B. (1998). Corporate Information with SAO-EIS. Building Data: Warehouse and a MIS-Application with insight. Vieweg & Sohn Verlagsgesellschaft mbH, Braunschweig, Wiesbaden.
  • Howson C. (2008). Successful Business Intelligence: Secrets to Making BI a Killer App. McGraw-Hill, New York [etc.].
  • Popovič A., Turk T., Jaklič J. (2010). Conceptual Model of Business Value of Business Intelligence Systems. "Management", vol. 15, 1, pp. 5-30.
  • TDWI, (2005), TDWI Poster: Business Intelligence Maturity Model. Retrieved January 20, 2006, from
  • Davis F.D. (1989). Perceived usefulness, perceived ease-of-use, and user acceptance of information technology. "MIS Quarterly", 13 (3), pp. 319-340.
  • Davis F.D., Bagozz, R.P., Warshaw P.R. (1989). User acceptance of computer technology: a comparison of two theoretical models. "Management science", 35 (8), pp. 982-1003.
  • Sternad S., Bobek S. (2012). Enterprise Resource Planning Acceptance Model (ERPAM) - Extended TAM for ERP systems in the operational phase of the ERP lifecycle. [w:] Measuring Organizational Information Systems Success: New Technologies and Practices, Belkhamza Z., Wafe S.A. (Eds.). IGI Global, pp. 179-204.
  • Janke S.M. (2009). Business Intelligence within Commercial Real Estate: an Application of the Motivation and Acceptance Model: dissertation. Capella University.
  • Drelichowski L. (2012). Evaluation of the Efficiency of Integrated ERP systems and Business Intelligence Tools Based on some Diagnostic Cases. University of Technology and Life Sciences, Bydgoszcz.
  • Bradford M. (2008). Modern ERP - select, implement & use today's advanced business systems. Raleigh, NC: College of Management, North Carolina State University.
  • Aberdeen Group, (2008a). The 2008 ERP in manufacturing benchmark reports. Retrieved March 2, 2010, from
  • Aberdeen Group, (2009a), ERP in the midmarket 2009. Retrieved March 16, 2010, from
  • Sternad S., Bobek S., Deželak Z., Lampret A. (2009). Critical success factors (CSFs) for enterprise resource planning (ERP) solution implementation in SMEs: what does matter for business integration. "International Journal of Enterprise Information Systems", vol. 5, no. 3, pp. 27-46.
  • Sternad S., Gradišar M., Bobek S. (2011) The influence of external factors on routine ERP usage. Ind. Management Data Systems, vol. 111, no. 9, pp. 1511-1530.
  • Schwarz A. (2003). Defining information technology acceptance: a human-centered, management-oriented perspective: dissertation. University of Houston - University Park.
  • BI4Dynamics. Retrieved January 5, 2012, from
Typ dokumentu
Identyfikator YADDA

Zgłoszenie zostało wysłane

Zgłoszenie zostało wysłane

Musisz być zalogowany aby pisać komentarze.
JavaScript jest wyłączony w Twojej przeglądarce internetowej. Włącz go, a następnie odśwież stronę, aby móc w pełni z niej korzystać.