TWI684154B - Service-oriented architecture (SOA) for walk-through command reorganization of real-time business intelligence systems - Google Patents

Service-oriented architecture (SOA) for walk-through command reorganization of real-time business intelligence systems Download PDF

Info

Publication number
TWI684154B
TWI684154B TW102120982A TW102120982A TWI684154B TW I684154 B TWI684154 B TW I684154B TW 102120982 A TW102120982 A TW 102120982A TW 102120982 A TW102120982 A TW 102120982A TW I684154 B TWI684154 B TW I684154B
Authority
TW
Taiwan
Prior art keywords
module
data
service
reorganization
instruction
Prior art date
Application number
TW102120982A
Other languages
Chinese (zh)
Other versions
TW201447782A (en
Inventor
蕭德芳
施建同
Original Assignee
百旭科技有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 百旭科技有限公司 filed Critical 百旭科技有限公司
Priority to TW102120982A priority Critical patent/TWI684154B/en
Publication of TW201447782A publication Critical patent/TW201447782A/en
Application granted granted Critical
Publication of TWI684154B publication Critical patent/TWI684154B/en

Links

Images

Abstract

一種即時商業智慧系統之走動式指令重組的服務導向架構(SOA),包括一走動式指令重組模組由一指令重組及剖析模組、一第一服務定義檔、一第二服務定義檔及一繼承模組組成,係即時依該走動式指令重組模組重組後的指令獲得取得之資料來源,再由資料來源自多個營運系統或資料倉儲取得所需資料,並以服務為導向,以之獲得具有資料倉儲的多維度資料的分析環境及運算,該使用者端變換需求後,就算不同維度、不同營運系統或多個營運系統及資料倉儲或同質或異質資料庫,亦可立即獲得變換後資料的即時性。 A service-oriented architecture (SOA) for walk-through command reorganization of an instant business intelligence system, including a walk-through command reorganization module consisting of a command reorganization and analysis module, a first service definition file, a second service definition file and a The inheritance module is composed of the data source obtained by the reorganized instruction of the walk-through instruction reorganization module in real time, and then the data source obtains the required data from multiple operating systems or data warehouses, and is service-oriented. Obtain the analysis environment and calculation of multi-dimensional data with data warehousing. After the user transforms the demand, even if different dimensions, different operating systems or multiple operating systems and data warehousing or homogeneous or heterogeneous databases can be obtained immediately after the transformation The immediacy of the data.

Description

即時商業智慧系統之走動式指令重組的服務導向架構(SOA) Service-oriented architecture (SOA) for walk-through command reorganization of real-time business intelligence systems

本發明一種商業智慧系統之技術領域,尤指其技術上提供一種以服務導向架構(SOA)之走動式指令重組的設計實現於即時商業智慧系統,以服務為導向,當使用者需求改變指令重組及剖析模組提供應變的彈性,以之獲得具有資料倉儲的多維度資料的分析環境及運算,使用者變換需求後,就算不同維度、不同營運系統或多個營運系統及資料倉儲或同質或異質資料庫,亦可立即獲得變換後資料的即時性,且不用各別寫獨立的特定應用程式介面(API)。 The technical field of a business intelligence system of the present invention, in particular, it provides a service-oriented architecture (SOA) walk-through instruction reorganization design implemented in a real-time business intelligence system, service-oriented, when user needs change instruction reorganization And the analysis module provides the flexibility of strain, so as to obtain the analysis environment and calculation of multi-dimensional data with data warehousing. After the user changes the requirements, even if the different dimensions, different operating systems or multiple operating systems and data warehousing are homogeneous or heterogeneous The database can also immediately obtain the real-time nature of the converted data, and there is no need to write an independent specific application program interface (API).

按,參閱第一圖所示,第一圖為一個目前BIS標準的系統模型,其流程可概分為三階段: According to, see the first picture, the first picture is a system model of the current BIS standard, its process can be roughly divided into three stages:

(1)資料匯整:使用ETL(Extract-Transform-Load)工具(參閱第二圖)將來源資料庫資料來源10萃取、轉換及載入11,匯入Operational data store資料庫;再經整理,累積資料儲存12於資料倉儲(Data Warehouse)資料庫中。 (1) Data aggregation: use the ETL (Extract-Transform-Load) tool (see the second figure) to extract, convert and load the source database data source 10 into the Operational data store database; then after finishing, The accumulated data is stored 12 in the data warehouse (Data Warehouse) database.

(2)資料分析:使用ETL工具(參閱第二圖)將資料倉儲24的資料萃取而出,儲存於基於分析而建構的資料超市(Data Mart)資料庫中(有些情況Data Mart可以省略而直接從交易系統20Data Warehouse擷取21、轉換22、載入23取得分析資料)。然後再以OLAP(Online Analytical Processing)或資料探勘(Data Mining)技術作資料分析。 (2) Data analysis: use the ETL tool (see the second figure) to extract the data of the data warehouse 24 and store it in the data supermarket (Data Mart) database constructed based on the analysis (in some cases, the Data Mart can be omitted and directly Retrieve 21, convert 22, and load 23 from the trading system 20 Data Warehouse to obtain analysis data). Then use OLAP (Online Analytical Processing) or data mining (Data Mining) technology for data analysis.

(3)資料展現13:以報表工具產出報表或Web Portal等方式將資料分析結果呈現予使用者。 (3) Data display 13: The results of data analysis are presented to users by means of reporting tools or Web Portal.

而企業現今所面臨問題,是不是建置了好的BIS,就可以達成企業BI的夢想?之前BIS呼聲喊得震天價響,而企業投入了大量的成本、時間及人力等資源後,使用者從BIS所獲得的效益與預期認知上對資訊品質(Information Quality,IQ)及對系統的有用性(the use of Information)往往存在著很大的落差。到最後企業內部的員工九成還是使用Excel來進行資料的分析,而造成BI的成效不彰。本發明在使用者對資訊品質不佳的認知層面上大致歸納為下列兩點: And the problem facing enterprises today, can we achieve the dream of enterprise BI by building a good BIS? Before BIS's voice was loud and loud, and enterprises invested a lot of resources such as cost, time, and manpower, the benefits and expectations of users from BIS were useful for Information Quality (IQ) and system usefulness. There is often a big gap in the use of information. In the end, 90% of the employees in the company still used Excel to analyze the data, which caused the effectiveness of BI to be ineffective. The present invention can be roughly summarized into the following two points on the user's perception level of poor information quality:

(1)資料倉儲在BIS中扮演一個核心的角色,也是後續所有資訊分析的基礎,但隨著企業營運環境快速變化,在激烈的競爭環境下,資料倉儲中的資料無法提供決策者及時而穩定的資訊,因此縱使有好的BIS也無法滿足企業需要。另一方面資料倉儲的開發必然是一項極為龐大而 複雜的投資,不但風險性高,且須投入企業大量的資源,若在一個沒有明確商業事實(business case)的情況下,它可能是一個長期的“進展中的工作(work in progress)”或“計劃黑洞(project black hole)”,因此許多企業基於投資成本及風險因素而十分遲疑;Gartner Group在2004年一份從智慧企業(Intelligent Enterprise)的調查顯示,有55%的企業用戶質疑,認為他們的資料倉儲提供的資訊並沒有擊中目標。而另一缺點是開發相當費時,若以傳統的系統開發方法通常需要數年的時間,若因開發過程中需求會不斷地增加,會採用雛型法先行製作一個雛型,而後反覆開發,然而所費時間不貲;到最後企業投入了大量成本及時間其所獲得效益與期待之間存在顯著顯著的落差。 (1) Data warehousing plays a core role in BIS and is the basis for all subsequent information analysis. However, with the rapid changes in the company’s operating environment, the data in the data warehousing cannot provide decision makers with timely and stable information in a fiercely competitive environment. Information, so even a good BIS cannot meet the needs of enterprises. On the other hand, the development of data storage must be an extremely large and Complex investment is not only risky, but also requires a large amount of corporate resources. If there is no clear business case (business case), it may be a long-term "work in progress" or "Project black hole", so many companies are very hesitant based on investment costs and risk factors; Gartner Group's 2004 survey from Intelligent Enterprise showed that 55% of enterprise users questioned and believed that The information provided by their data warehouse did not hit the target. Another disadvantage is that the development is quite time-consuming. If the traditional system development method usually takes several years, if the demand will continue to increase during the development process, the prototype method will be used to make a prototype first, and then it will be developed repeatedly. The time spent is not conspicuous; in the end, companies have invested a lot of cost and time, and there is a significant gap between the benefits obtained and expectations.

(2)很多企業會誤認為導入了BIS就可以順利的運作獲取應有的分析資料。但企業並沒有想到資料倉儲中的資料也會隨著分析需求的改變及企業型態的改變而需要即時調整,而且另一方面IT人員常常需花費巨額的時間才能整合大量不同的異質資料來源,尤其資料整合(data integration)扮演資訊品質(IQ)重要角色,尤其是資訊內容品質(Information content quality)最後影響資訊的使用結果;BIS的有效性在於它能提供及時的商業資訊的能力,因此BIS的導入成功或失敗取決於可用的資訊;當仰賴IT人員的時間越久或是IT人員的技術不足時(the lack of IT skills) ,意謂著決策者等待分析的時間就越長,如此所產生的分析報表也絕對無法滿足該決策者隨需(on demand)的期望,意即已難反應當下營運環境的變化,這般決策,做了也無太大意義。 (2) Many companies will mistakenly believe that the introduction of BIS can smoothly operate to obtain due analysis data. However, companies did not expect that the data in the data warehouse will also need to be adjusted in real time as the analysis needs change and the type of business changes. On the other hand, IT staff often spend a lot of time to integrate a large number of different heterogeneous data sources. In particular, data integration plays an important role in information quality (IQ), especially the quality of information content (Information content quality) ultimately affects the use of information; the effectiveness of BIS lies in its ability to provide timely business information, so BIS The success or failure of the import depends on the available information; when relying on the IT staff for a longer time or the IT staff’s lack of skills (the lack of IT skills) , Which means that the longer the decision maker waits for analysis, the resulting analysis report can never meet the decision maker’s on demand expectations, which means that it is difficult to reflect the changes in the current operating environment. , It doesn't make much sense to do it.

在2006年所提出BI 2.0賦予不同的思維則主張即時性但要實現BI 2.0概念確實存在諸多落差與障礙,以當前多數企業的BI應用現況來看,若與BI 2.0主要訴求逐一比對,將不難發現,其間落差可謂甚大,在此之中,究竟存在著哪些目前BI障礙?以下說明之: In 2006, it was proposed that BI 2.0 gives different thinking, but it advocates immediacy. However, there are many gaps and obstacles to achieve the concept of BI 2.0. Judging from the current status of BI applications in most enterprises, if it is compared with BI 2.0’s main demands one by one, it will It is not difficult to find that the gap between them can be described as very large. Among them, what are the current BI obstacles? The following explains:

(1)傳統BIS目的在將資料轉換為資訊,然後再把資訊轉換成智慧,若企業只為了使用BI而導入BIS,便容易在評估工具的過程中,陷入執著於比較誰的延展性好、誰的計算速度快之盲點,最終BIS充其量僅能提升資訊獲取的準確性、時效性及整合性,未必能縱深到企業營運管理需求,而導致企業在於導入BIS後,才驚覺現實與期望之間有顯著落差,且效益難以評估;而且資料整合IT人員耗時費力,最後BIS淪為報表產生器,諸如此類的運用價值,效益自然不會太高,更與BI 2.0訴求理念相差甚遠。 (1) The purpose of traditional BIS is to convert data into information, and then convert the information into wisdom. If an enterprise only imports BIS for the purpose of using BI, it is easy to fall into the process of evaluating tools and stick to the comparison of who has good scalability, The blind spot of whose calculation speed is fast, in the end, BIS can only improve the accuracy, timeliness and integration of information acquisition at best, and may not be able to reach the needs of business operations and management. There is a significant gap between the two, and the benefits are difficult to assess; and the IT integration of data is time-consuming and laborious. Finally, BIS is reduced to a report generator, and the application value of such things, the benefits will naturally not be too high, and it is far from the BI 2.0 appeal concept.

(2)綜觀BI 2.0論點,有許多的學者坦承確實不易實現。尤其在即時性的決策中,由於前提是得將企業複雜資訊系統之中的細部資料經過諸多整理、運算,況且資料傳遞也得浪費一些時間,有時就連「增加1個欄位」等看 似簡單的需求,都可能耗費數個工作天。因此,即時性訴求,無疑正是決策者所面臨的一大關鍵障礙,因為,一但資料整合的時程被拖長,便意謂商業決策是奠基於非即時性的資料上,已難反應當下營運環境的變化,更何況決策者為了因應市場的快速變化,其分析的需求會隨時而改變,當現行先匯整後的資料(資料倉儲)無法滿足其需求時,必須再仰賴IT人員再次投入大量的時間(其間若IT人員的專業素養不足時其下達決策的時間點無疑再被延後),這般的過程對於即時的決策需求,做了也無太大意義。 (2) Looking at the BI 2.0 argument, many scholars admit that it is really not easy to realize. Especially in real-time decision-making, because the premise is that the detailed data in the enterprise's complex information system must be sorted and calculated, and the data transmission also wastes some time, sometimes even "add 1 column" Simple requirements can take several working days. Therefore, the demand for immediacy is undoubtedly a key obstacle faced by policy makers, because once the time of data integration is prolonged, it means that business decisions are based on non-immediate data, and it is difficult to reflect the current Changes in the operating environment, not to mention the decision-makers' needs for analysis will change at any time in order to respond to the rapid changes in the market. When the current consolidated data (data warehouse) cannot meet their needs, they must rely on IT staff to invest again A large amount of time (if the IT staff's professional literacy is insufficient, the timing of their decision-making will undoubtedly be postponed), such a process does not make much sense for immediate decision-making needs.

BI 2.0環境所產出的分析型資料,必須要能嵌入到不同作業流程之中,而過去BIS以特定應用程式介面(Application Program Interface,API)為基礎,藉由IT人員透過開發程序,才能大費周章擷取到分析結果。至於要採取何等新作法,才可讓工作流程之中的任一元件,都能輕易取得BIS分析結果,前提便是要跳脫IT人員利用程式所開發一個個獨立的API,而改以服務導向架構(SOA)的方式。 The analytical data produced by the BI 2.0 environment must be able to be embedded in different operating processes. In the past, BIS was based on a specific application program interface (API), which was developed by IT personnel through development procedures. Fei Zhouzhang retrieved the analysis results. As for what new approach to take, any component in the workflow can easily obtain the BIS analysis results, the premise is to get rid of the independent API developed by the IT staff using the program, and change to service-oriented Architecture (SOA) approach.

本發明的設計提供組織(企業)在管理及決策層面效益,以企業交易資訊系統(operational IS)為基礎導入以服務導向架構之智慧型“走動式指令重組”設計,克服了組織(企業)在沒有建立資料倉儲環境下即時地獲得『具有資料倉儲的多維度資料的分析環境及運算(drilldown,rollup, slice或pivoting等)』實現即時性決策之訴求,並且已實際導入至企業內部的資訊系統(operational IS),驗證了使用者與資訊需要來源、BIS間達到即時的互動關係而具體的反應在資訊品質上的評估及對系統認知上有用性的程度,進而提高資訊的使用而大幅提高BIS成功;值得一提的是本發明所設計的SOA架構,透過服務間的再結合成為一個新的服務的創新設計架構,讓異質資料整合變得容易。 The design of the present invention provides an organization (enterprise) with benefits in management and decision-making. Based on the enterprise transaction information system (operational IS), a smart "walking instruction reorganization" design with service-oriented architecture is introduced, which overcomes the organization (enterprise)'s The analysis environment and calculation of multi-dimensional data with data storage (drilldown, rollup, slice or pivoting etc.)" to realize the demands of real-time decision-making, and has been actually imported into the enterprise's internal information system (operational IS), which verifies the real-time interactive relationship between the user and the source of information needs, BIS, and the specific reaction in the information Quality assessment and the degree of system usefulness, thereby improving the use of information and greatly improving the success of BIS; it is worth mentioning that the SOA architecture designed by the present invention becomes a new service through recombination between services Innovative design architecture makes it easy to integrate heterogeneous data.

本發明所提出的設計架構能立即從企業內部的交易資訊系統(operational IS)中驗證前述所提到的BIS成功的關鍵因素,也就是說資料整合、資訊品質及資訊的使用等因素,而不需等至投入了大量的成本、時間及人力等資源後,才發現與預期獲得的效益之間存在著很大的落差;另外,資料倉儲中的數據在提供給使用者之前已經過清洗(cleaned)、解碼(decoded)、重組(reorganized)及重排(reordered),然而透過使用原始交易資料(raw transactional data),破損的和醜陋的數據在分析過程中才能與良好資料一起被揭露,企業決策者將有機會評估什麼是破損的資料及為什麼,以便有機會來解決它。因此,從IT發展BIS的效益構面來說,可以預期這樣的設計架構其價值可以提高對問題的了解程度與使用者在認知上關鍵因素的相互關聯性,大幅度減少企業導入即時BIS所投入的資源以及滿足後續使用者需求的改變,即時地提供使用者所需的分析資料 、提高BIS的資訊使用效率,更可讓IT人員節省介入資料整合時間,而更專注於企業其他的商業流程(business process)讓IT發揮最大的效益。 The design framework proposed by the present invention can immediately verify the aforementioned key factors for the success of the BIS from the intra-enterprise transaction information system (operational IS), that is, data integration, information quality and use of information, etc., without It takes a long time to invest a lot of resources such as cost, time, and manpower before discovering that there is a large gap between the expected benefits; in addition, the data in the data warehouse has been cleaned before being provided to the user (cleaned ), decoded, reorganized and reordered, however, through the use of raw transactional data, broken and ugly data can only be revealed together with good data during the analysis process, and corporate decisions The person will have the opportunity to evaluate what is the damaged data and why, so as to have the opportunity to solve it. Therefore, from the perspective of the benefits of IT development BIS, it can be expected that the value of such a design framework can improve the correlation between the understanding of the problem and the user's key factors in cognition, greatly reducing the investment in real-time BIS Resources and changes to meet the needs of subsequent users, providing users with the analysis data they need in real time 2. Improve the efficiency of BIS information usage, and allow IT staff to save time for data integration, while focusing on other business processes of the enterprise to maximize IT benefits.

因此,本發明在這樣的設計架構下,系統具有高度擴展彈性而落實了SOA所強調抽象(abstraction)、可組性(composability)、可重用性(reusability)的核心精神而實現BI 2.0即時分析服務,幫助企業達到: Therefore, under this design architecture, the system has a high degree of expansion flexibility and implements the core spirit of SOA emphasized abstraction, composability, and reusability to implement BI 2.0 real-time analysis services To help companies achieve:

(1)增加企業盈收,或提升企業競爭力。 (1) Increase the profitability of enterprises or enhance the competitiveness of enterprises.

(2)提供可變動的服務型態。 (2) Provide variable service types.

(3)降低企業導入的成本及時間。 (3) Reduce the cost and time of enterprise introduction.

(4)降低開發服務的時間以達成即時需求。 (4) Reduce the time to develop services to meet immediate needs.

(5)整合企業的網路服務技術資源。 (5) Integrate enterprise network service technical resources.

(6)降低整體風險及意外。 (6) Reduce overall risks and accidents.

有關本發明所採用之技術、手段及其功效,茲舉一較佳實施例並配合圖式詳細說明於後,相信本發明上述之目的、構造及特徵,當可由之得一深入而具體的瞭解。 Regarding the technology, means and functions adopted by the present invention, a preferred embodiment is described in detail with reference to the drawings. It is believed that the above-mentioned objects, structures and features of the present invention can be gained a deep and specific understanding .

[習知] [Knowledge]

10‧‧‧資料來源 10‧‧‧Source

11‧‧‧萃取、轉換及載入 11‧‧‧Extraction, conversion and loading

12‧‧‧資料儲存 12‧‧‧Data storage

13‧‧‧資料展現 13‧‧‧Information

20‧‧‧交易系統 20‧‧‧ Trading System

21‧‧‧擷取 21‧‧‧ Capture

22‧‧‧轉換 22‧‧‧Conversion

23‧‧‧載入 23‧‧‧ Load

24‧‧‧資料倉儲 24‧‧‧ data storage

[本發明] [this invention]

30‧‧‧交易系統 30‧‧‧ Trading system

31‧‧‧資料倉儲 31‧‧‧ data storage

40‧‧‧服務導向架構(SOA) 40‧‧‧Service Oriented Architecture (SOA)

41‧‧‧走動式指令重組模組(ReSQL) 41‧‧‧ Walking Reorganization Module (ReSQL)

411‧‧‧指令重組及剖析模組 411‧‧‧Command reorganization and analysis module

412‧‧‧第一服務定義檔(eistable.def) 412‧‧‧First service definition file (eistable.def)

413‧‧‧第二服務定義檔(valueSQL.def) 413‧‧‧Second service definition file (valueSQL.def)

414‧‧‧繼承模組 414‧‧‧Inheritance module

42‧‧‧資料集(DS) 42‧‧‧ Dataset (DS)

43‧‧‧語法轉換模組 43‧‧‧grammar conversion module

44‧‧‧多重值資料處理模組 44‧‧‧Multi-value data processing module

45‧‧‧維度整合模組 45‧‧‧Dimensional Integration Module

461‧‧‧使用者介面輸出模組 461‧‧‧User interface output module

462‧‧‧使用者介面控制模組 462‧‧‧User interface control module

47‧‧‧過濾器 47‧‧‧filter

48‧‧‧同質或異質資料庫 48‧‧‧ homogeneous or heterogeneous database

49‧‧‧快取記憶體(cache) 49‧‧‧Cache

第一圖係習知商業智慧(BI)系統架構。 The first diagram is a conventional business intelligence (BI) system architecture.

第二圖係習知數據提取轉換加載(ETL)架構。 The second graph is a conventional data extraction transformation loading (ETL) architecture.

第三圖係本發明服務導向架構(SOA)系統圖。 The third diagram is a service-oriented architecture (SOA) system diagram of the present invention.

第四圖係本發明走動式指令重組模組(ReSQL)架構系統圖。 The fourth figure is a system diagram of the ReSQL reorganization module (ReSQL) architecture of the present invention.

第五圖係本發明範例一執行結果:94年分季彙整資料(尚未下探)。 The fifth figure is the result of the implementation of Example 1 of the present invention: 94 quarterly summary data (not yet explored).

第六圖係本發明範例一執行結果:下探至部科維度之彙整資料。 The sixth figure is the result of the first example of the present invention: the aggregated data down to the departmental dimension.

第七圖係本發明範例一執行結果:下探至科室維度之彙整資料。 The seventh figure is the result of the implementation of the first example of the present invention: down to the summary data of the department dimension.

第八圖係本發明範例一執行結果:下探至醫師維度之彙整資料。 The eighth figure is the execution result of Example 1 of the present invention: digging down to the aggregated data of the dimension of the physician.

第九圖之一係本發明範例一執行結果:該醫生看診申報明細資料。 One of the ninth figures is the execution result of the first example of the present invention: the detailed information of the doctor's visit declaration.

第九圖之二係本發明範例一執行結果:季份資料彙總。 The second figure 9 is the execution result of the first example of the present invention: quarterly data summary.

第九圖之三係本發明範例一執行結果:Drill-down將第一季資料下鑽至月份。 The third of the ninth figure is the execution result of the first example of the present invention: Drill-down drills down the first quarter data to the month.

第九圖之四係本發明範例一執行結果:Drill-down至2月份部科彙總資料。 The fourth of the ninth figure is the execution result of the first example of the present invention: Drill-down to February department summary data.

第九圖之五係本發明範例一執行結果:Drill-down將2月份內科彙總資料。 The fifth of the ninth figure is the execution result of the first example of the present invention: Drill-down will summarize medical data in February.

第九圖之六係本發明範例一執行結果:Drill-down將2月份外科彙總資料下鑽至每日。 The sixth of the ninth figure is the execution result of the first example of the present invention: Drill-down drills down the surgical summary data in February to daily.

第十圖係本發明範例二執行結果:繼承範例一的定義,改變維度屬性。 The tenth figure is the execution result of Example 2 of the present invention: inherit the definition of Example 1 and change the dimension attribute.

第十一圖係本發明範例二執行結果:下探至給付類別維度之彙整資料。 The eleventh figure is the result of the implementation of the second example of the present invention: the aggregated data down to the dimension of the payment category.

第十二圖係本發明範例二執行結果:下探至住院案件分類維度之彙整資料。 The twelfth figure is the result of the implementation of the second example of the present invention: down to the aggregated data of the classification dimension of the hospitalized case.

第十三圖係本發明範例二執行結果:部科樞鈕(pivot)分析資第十四圖係本發明範例三執行結果:繼承範例一的定義,在eistable.def中產生新的定義。 Figure 13 is the execution result of Example 2 of the present invention: pivot analysis (pivot). Figure 14 is the execution result of Example 3 of the present invention: inheriting the definition of Example 1 and generating a new definition in eistable.def.

第十五圖係本發明範例三執行結果:下探至醫生維度之彙整資料。 The fifteenth figure is the result of the implementation of the third example of the present invention: digging down to the summary data of the doctor dimension.

第十六圖係本發明範例三執行結果:該醫生年度彙整資料。 The sixteenth figure is the result of the implementation of the third example of the present invention: the doctor summarizes the data annually.

第十七圖之一係本發明範例四:多重資料來源整合架構圖(數值整合)。 One of the seventeenth figures is the fourth example of the present invention: multi-data source integration architecture (numerical integration).

第十七圖之二係本發明多重資料來源整合架構示意圖(分類整合)。 Figure 17 bis is a schematic diagram of multiple data source integration architecture (classified integration) of the present invention.

第十八圖係本發明範例四執行結果:多重資料來源整合。 Figure 18 is the implementation result of Example 4 of the present invention: integration of multiple data sources.

第十九圖係本發明範例四執行結果:多重資料來源整合(下探維度為科室)。 Figure 19 is the execution result of Example 4 of the present invention: integration of multiple data sources (the dive dimension is the department).

第二十圖係本發明範例四執行結果;多重資料來源整合(下探至HR資料庫之醫師明細資料)。 Figure 20 is the execution result of Example 4 of the present invention; integration of multiple data sources (drill down to the details of physicians in the HR database).

第二十一圖之一係本發明範例四執行結果:多重資料來源整合(與去年同期比較),以一般維度顯示。 One of the twenty-first figures is the result of the implementation of Example 4 of the present invention: integration of multiple data sources (compared with the same period last year), shown in general dimensions.

第二十一圖之二係本發明範例四執行結果:多重資料來源整合(與去年同期比較),以期間維度顯示。 Figure 21 is the implementation result of Example 4 of the present invention: integration of multiple data sources (compared with the same period last year), displayed in the period dimension.

第二十一圖之三係本發明範例四執行結果:多重資料來源整合(與去年同期比較),以下探維度顯示。 The third figure of the twenty-first figure is the result of the fourth example of the present invention: the integration of multiple data sources (compared with the same period last year), shown in the following dimension.

本發明係提供一種即時商業智慧系統之走動式指令重組的服務導向架構(SOA)之設計者。 The present invention provides a service-oriented architecture (SOA) designer of walk-through instruction reorganization of an instant business intelligence system.

為使 貴審查委員對本發明之目的、特徵及功效能夠有更進一步之瞭解與認識,茲配合實施方式及圖式詳述如後:參閱第三圖所示,本發明提供一種即時商業智慧系統之走動式指令重組的服務導向架構(SOA),係包含有:一服務導向架構(SOA)40、一使用者端及一資訊科技(Information Technology,IT)人員端,該服務導向架構(SOA)40包括一走動式指令重組模組(ReSQL)41,該走動式指令重組模組(ReSQL)41包括由一指令重組及剖析模組411、一第一服務定義檔(eistable.def)412、一第二服務定義檔(valueSQL.def)413及一繼承模組414組成,該第一服務定義檔(eistable.def)412及該第二服務定義檔(valueSQL.def)413由該資訊科技(IT)人員端簡單定義,資料取自營運系統或資料取自多個營運系統或資料取自多個營運系統及資料倉儲 ,其係即時依該走動式指令重組模組(ReSQL)41重組後的指令獲得取得之資料來源,再由資料來源取得所需資料,該服務導向架構(SOA)40更包含一語法轉換模組43,藉由該語法轉換模組43得以溝通該指令重組及剖析模組411與各個營運系統或資料倉儲之同質或異質的資料庫48,使所有資料之自動取得無障礙,該繼承模組414可在各服務間透過繼承的方式修改該使用者端的需求及透過服務間的再結合成為一個新的服務,該指令重組及剖析模組411負責將服務的定義及使用者端輸入的參數設定以走動式指令重組的重組指令的運算模式完成即時的需求服務分析,並以服務為導向,當該使用者端需求改變,該指令重組及剖析模組411提供應變的彈性,以之獲得具有資料倉儲的多維度資料的分析環境及運算,該使用者端變換需求後,就算不同維度、不同營運系統或多個營運系統及資料倉儲或同質或異質資料庫48,亦可立即獲得變換後資料的即時性,且不用各別寫獨立的特定應用程式介面(API)。 In order for your reviewing committee to have a better understanding and understanding of the purpose, features and efficacy of the present invention, the detailed description of the implementation mode and the drawings is as follows: referring to the third figure, the present invention provides an instant business intelligence system The service-oriented architecture (SOA) of walk-through command reorganization includes: a service-oriented architecture (SOA) 40, a user end and an information technology (IT) staff, and the service-oriented architecture (SOA) 40 Including a walk-around instruction reorganization module (ReSQL) 41, the walk-around instruction reorganization module (ReSQL) 41 includes a command reorganization and analysis module 411, a first service definition file (eistable.def) 412, a first Two service definition files (valueSQL.def) 413 and an inheritance module 414, the first service definition file (eistable.def) 412 and the second service definition file (valueSQL.def) 413 are composed of the information technology (IT) Simple definition of personnel, data is taken from operating system or data is taken from multiple operating systems or data is taken from multiple operating systems and data warehousing It is based on the data source obtained by the reorganized instruction of the walking instruction reorganization module (ReSQL) 41, and then obtains the required data from the data source. The service-oriented architecture (SOA) 40 further includes a syntax conversion module 43. Through the grammar conversion module 43, the command reorganization and analysis module 411 and the homogeneous or heterogeneous database 48 of each operating system or data warehouse can be communicated to make all data automatically accessible, and the inheritance module 414 The requirements of the user end can be modified between each service through inheritance and recombined between the services to form a new service. The command reorganization and analysis module 411 is responsible for setting the definition of the service and the parameters entered by the user to The operation mode of the reorganization instruction of the walking instruction reorganization completes real-time demand service analysis, and is service-oriented. When the user's demand changes, the instruction reorganization and analysis module 411 provides flexibility to adapt to obtain data storage Multi-dimensional data analysis environment and calculation, after the user changes the demand, even if the different dimensions, different operating systems or multiple operating systems and data storage or homogeneous or heterogeneous database 48, you can immediately get the real-time data after conversion It does not need to write an independent specific application programming interface (API).

所述之即時商業智慧系統之走動式指令重組的服務導向架構(SOA),其中該指令重組及剖析模組411建構有完整的擷取指令,該指令重組及剖析模組411更具有重組後的指令最佳化,以縮短資料擷取的時間。 The service-oriented architecture (SOA) of the walk-through instruction reorganization of the real-time business intelligence system, wherein the instruction reorganization and analysis module 411 is constructed with a complete retrieval instruction, and the instruction reorganization and analysis module 411 further has the reorganized Command optimization to shorten the time of data retrieval.

所述之即時商業智慧系統之走動式指令重組的服務導向架構(SOA),其中該使用者端取用資料方式,包括 下探(Drill-down)、上捲(Roll-up)、樞鈕分析(Pivot)或切片(Slice)。 The service-oriented architecture (SOA) of the walk-through command reorganization of the real-time business intelligence system described above, in which the method for the user to access data includes: Drill-down, roll-up, pivot analysis or slice.

所述之即時商業智慧系統之走動式指令重組的服務導向架構(SOA),其中該服務導向架構(SOA)40更包含有一多重值資料處理模組44,該多重值資料處理模組44連結該走動式指令重組模組(ReSQL)41、該語法轉換模組43及同質或異質資料庫48,以該多重值資料處理模組44進行多重資料計算整合。 The service-oriented architecture (SOA) of the walk-through instruction reorganization of the real-time business intelligence system, wherein the service-oriented architecture (SOA) 40 further includes a multi-value data processing module 44 which is connected to the The walking instruction reorganization module (ReSQL) 41, the grammar conversion module 43, and the homogeneous or heterogeneous database 48 use the multiple-value data processing module 44 to perform multiple data calculation and integration.

所述之即時商業智慧系統之走動式指令重組的服務導向架構(SOA),其中該服務導向架構(SOA)40更包含有一資料集(DS,dataset)42及一快取記憶體(cache)49,該資料集42連結該走動式指令重組模組(ReSQL)41、該多重值資料處理模組44、同質或異質資料庫48與該使用者端,指令重組後進至該資料集42,該資料集42由該快取記憶體(cache)49找不到資料時才會至指令對應的同質或異質資料庫48擷取資料。 The service-oriented architecture (SOA) of the walk-through instruction reorganization of the real-time business intelligence system, wherein the service-oriented architecture (SOA) 40 further includes a data set (DS, dataset) 42 and a cache memory (cache) 49 , The data set 42 connects the walking command reorganization module (ReSQL) 41, the multi-value data processing module 44, the homogeneous or heterogeneous database 48 and the user terminal, and then proceeds to the data set 42 after the command reorganization, the data The set 42 only retrieves data from the homogeneous or heterogeneous database 48 corresponding to the instruction when the cache 49 cannot find the data.

所述之即時商業智慧系統之走動式指令重組的服務導向架構(SOA),其中該服務導向架構(SOA)40更包括一維度整合模組45,該維度整合模組45連結該資料集(DS,dataset)42與該使用者端,該維度整合模組45得整合二個以上不同維度資料成為一個資料,再以整合後的資料展示在該使用者端。 The service-oriented architecture (SOA) of the walk-through instruction reorganization of the real-time business intelligence system described above, wherein the service-oriented architecture (SOA) 40 further includes a one-dimensional integration module 45, which is connected to the data set (DS) , dataset) 42 and the user end, the dimension integration module 45 may integrate two or more different dimension data into one data, and then display the integrated data on the user end.

所述之即時商業智慧系統之走動式指令重組的服務導向架構(SOA),其中該服務導向架構(SOA)40更包括一過濾器47,該過濾器47連結該維度整合模組45與該使用者端,該過濾器47以該使用者端設定的條件,過濾掉該維度整合模組45整合後資料的多餘部分,再以過濾後的資料展示在該使用者端。 The service-oriented architecture (SOA) of the walk-through command reorganization of the real-time business intelligence system, wherein the service-oriented architecture (SOA) 40 further includes a filter 47 that connects the dimension integration module 45 and the use On the user side, the filter 47 filters out the excess part of the data integrated by the dimension integration module 45 according to the conditions set by the user side, and then displays the filtered data on the user side.

所述之即時商業智慧系統之走動式指令重組的服務導向架構(SOA),其中該服務導向架構(SOA)40更包括一使用者介面控制模組462,該使用者介面控制模組462連結該使用者端、該IT人員端、該走動式指令重組模組(ReSQL)41、該資料集42及該過濾器47,該使用者介面控制模組462接受該使用者端控制輸入,並將輸入訊號送至相關該IT人員端、該走動式指令重組模組(ReSQL)41、該資料集42及該過濾器47,或接收該IT人員端、該走動式指令重組模組(ReSQL)41、該資料集42及該過濾器47訊號控制往該使用者端之輸出。 The service-oriented architecture (SOA) of the walk-through command reorganization of the real-time business intelligence system, wherein the service-oriented architecture (SOA) 40 further includes a user interface control module 462, and the user interface control module 462 is connected to the On the user side, the IT staff side, the walking command reorganization module (ReSQL) 41, the data set 42 and the filter 47, the user interface control module 462 accepts the user side control input and inputs The signal is sent to the relevant IT staff, the walking instruction reorganization module (ReSQL) 41, the data set 42 and the filter 47, or receives the IT staff, the walking instruction reorganization module (ReSQL) 41, The data set 42 and the filter 47 signals control the output to the user terminal.

所述之即時商業智慧系統之走動式指令重組的服務導向架構(SOA),其中該服務導向架構(SOA)40更包括一使用者介面輸出模組461,該使用者介面輸出模組461連結該過濾器47、該使用者介面控制模組462及該使用者端,該使用者介面輸出模組461可輸出資料至該使用者端顯示器。 The service-oriented architecture (SOA) of the walk-through instruction reorganization of the real-time business intelligence system, wherein the service-oriented architecture (SOA) 40 further includes a user interface output module 461, and the user interface output module 461 is connected to the The filter 47, the user interface control module 462 and the user terminal, the user interface output module 461 can output data to the user terminal display.

以服務導向架構(SOA),背後由不同元件所組成,這些元件可依不同的目地放置在不同的流程中,以完成企業隨需(on demand)服務。其設計的架構歸納為三大層面: A Service-Oriented Architecture (SOA) is composed of different components behind. These components can be placed in different processes according to different purposes to complete on-demand services. The structure of its design can be summarized into three levels:

(1)本發明設計的BIS是建構在企業的operational IS之上(如線上交易系統、ERP、MES、CRM…),節省了資料轉換及整合至資料倉儲的時間而且提供最即時的分析資料(資料倉儲的開發往往在金錢、人員及時間是一項極為龐大的投資)。 (1) The BIS designed by the present invention is built on the operational IS of the enterprise (such as online transaction system, ERP, MES, CRM...), which saves the time of data conversion and integration into the data warehouse and provides the most real-time analysis data ( The development of data warehousing is often an extremely large investment in money, personnel and time).

(2)基於外在環境的改變、競爭壓力增強,企業除了必須仰賴即時資料做出即時分析、下達決策之外,而另一方面IT人員必須在最短的時間內支援及滿足決策者隨時調整分析的需求;再者,由於分析的資料來源並非來自彙整過的資料倉儲(Data warehouse),而是從線上交易該時段之當時「狀態」資料或是資料需整合同質或異質資料庫等不同的資料來源,因此為了要即時地獲得「具有資料倉儲多維度資料的分析環境及運算(drilldown,rollup,slice或pivot等)」,本發明設計一個以服務導向架構(SOA)之走動式指令重組模組(ReSQL),IT人員端根據決策者分析需求在極短的時間內透過簡單的定義設定提供即時分析服務,如多維度下探、上捲、切片、年度比較、多重資料來源整合及比較、年度趨勢、明細資料進階維度分析...;此走動式指令重組模組(ReSQL)動態地自動重組最佳化指令及正確剖析 (parse)資料來源,提供即時的資料而達成即時決策分析。 (2) Based on changes in the external environment and increased competitive pressures, companies must rely on real-time data to make real-time analysis and make decisions, and on the other hand, IT personnel must support and satisfy the decision-makers to adjust and analyze at any time in the shortest time. Requirements; moreover, because the data source for analysis is not from the aggregated data warehouse, but from the "status" data at the time of the online transaction or the data needs to integrate different data such as homogeneous or heterogeneous databases Source, so in order to obtain the "analysis environment and calculation of multi-dimensional data with data warehousing (drilldown, rollup, slice or pivot, etc.) in real time", the present invention designs a service-oriented architecture (SOA) walking instruction reorganization module (ReSQL), IT staff provides real-time analysis services within a short period of time through simple definition settings according to the analysis needs of decision makers, such as multi-dimensional dip, roll-up, slicing, annual comparison, integration and comparison of multiple data sources, annual Advanced dimensional analysis of trends and detailed data...; This walking command reorganization module (ReSQL) dynamically reorganizes the optimized commands and analyzes them correctly (parse) data source, providing real-time data to achieve real-time decision analysis.

(3)由於資料倉儲是匯整後的「歷史數據」,可預測未來趨勢與結果及快速提供決策者分析資料,或是企業內部已建置資料倉儲,基於企業在不同彈性需求因素下,走動式指令重組模組(ReSQL)可同步支援資料來源是來自於資料倉儲。另一方面,當資料來自於資料倉儲,決策者在分析的過程中同時又需要查看更詳細的即時資料(raw data或是某種程度匯整過的資料),然而這些資料並不存在於資料倉儲中,基於此,服務導向架構(SOA)支援可在瀏灠資料來自於資料倉儲的同時,即時串連至交易系統中呈現完整的明細資料。 (3) Since the data warehouse is the "historical data" after consolidation, it can predict future trends and results and quickly provide decision makers with analysis data, or the data warehouse has been built within the enterprise, based on the company's movement under different elastic demand factors. The Recommanded Reorganization Module (ReSQL) can synchronously support data sources from data warehousing. On the other hand, when the data comes from the data warehouse, the decision-maker needs to view more detailed real-time data (raw data or some sort of aggregated data) during the analysis process, but these data do not exist in the data In warehousing, based on this, the Service Oriented Architecture (SOA) support can be connected to the transaction system in real time to present complete details while browsing the data from the data warehousing.

在服務導向架構(SOA)中,軟體資源是被封裝成服務,將此服務模組化後,提供標準的商業功能。為了要支援共有的商業流程,服務可以被視為建立版塊(building block)以便於與其他的服務溝通而支持共有的商業流程;服務在服務導向架構(SOA)中是功能面中的一小部份伴隨著有些重要的特性,包括了服務是自主的(Services are autonomous)、服務隱藏了底層的邏輯(Services hide underlying logic)、服務是鬆散耦合(Services are loosely coupled)及完整的服務定義(Services are well defined)。服務導向架構(SOA)提供了一個彈性的架構,模組化的應用程式至服務中。另外服務導向架構(SOA)允許企業創建,部署和 整合多種服務。因此在這種方式中,服務導向架構(SOA)可以提供企業用戶靈活性和敏捷性的需要,而且定義服務可整合和重用而成為關鍵區塊,以促進持續的和不斷變化的業務需求。 In a Service Oriented Architecture (SOA), software resources are packaged as services. After modularizing this service, it provides standard business functions. In order to support shared business processes, services can be viewed as building blocks to communicate with other services to support shared business processes; services are a small part of the functional side in a service-oriented architecture (SOA) The copy is accompanied by some important features, including services are autonomous, services hide underlying logic, services are loosely coupled, and complete service definitions (Services are well defined). Service Oriented Architecture (SOA) provides a flexible framework for modular applications into services. In addition, Service Oriented Architecture (SOA) allows enterprises to create, deploy and Integrate multiple services. So in this way, Service Oriented Architecture (SOA) can provide the needs of enterprise users for flexibility and agility, and define services that can be integrated and reused as key blocks to promote continuous and changing business needs.

服務導向架構(SOA)目的是為企業建構一個具彈性、可重複使用的整合性介面,其組合的元素通常包括軟體元件、服務及流程三個部份。當決策者面對新的需求時,流程負責定義決策者要求的處理步驟;服務包括特定步驟的所有程式元件,而軟體元件則負責執行工作的程式。以下分別說明本發明的設計架構如何以服務導向架構(SOA)為基礎以實現BI 2.0即時的分析環境。 The purpose of Service Oriented Architecture (SOA) is to build a flexible and reusable integrated interface for enterprises. The combined elements usually include software components, services and processes. When the decision maker is faced with a new demand, the process is responsible for defining the processing steps required by the decision maker; the service includes all program elements of a specific step, while the software element is responsible for the program that performs the task. The following separately illustrates how the design architecture of the present invention is based on a service-oriented architecture (SOA) to implement a BI 2.0 real-time analysis environment.

第三圖為服務導向架構(SOA)BIS架構,其中走動式指令重組模組(ReSQL)在服務導向架構(SOA)扮演著即時分析環境的主要核心角色,負責建構使用者需求(服務)定義中所需的多維度資料環境及處理流程,以即時地提供決策者分析服務;無庸置疑的指令重組及剖析模組除了需建構完整的擷取指令之外,還需將重組後的指令最佳化以縮短資料擷取的時間;期間決策者依其分析模式(或決策者需求服務),如drilldown,rollup或pivot等走動式的運算,以服務導向架構(SOA)方式透過走動式指令重組模組(ReSQL)及傳訊式連結之設計,動態將資料載入至資料集(DS,dataset)中以達成即時因應使用者的需求與改變;再者該 走動式指令重組模組(ReSQL)能快速地解決前述所提到若分析資料是整合不同的資料來源(同質或異質資料庫)時所面臨的問題。 The third picture is the service-oriented architecture (SOA) BIS architecture, in which the walk-through instruction reorganization module (ReSQL) plays the main core role of the real-time analysis environment in the service-oriented architecture (SOA) and is responsible for constructing the user requirements (service) definition The required multi-dimensional data environment and processing flow to provide decision-makers with analysis services in real time; the undoubted command reorganization and analysis module needs to optimize the reorganized commands in addition to constructing complete retrieval commands In order to shorten the time of data retrieval; during the decision-making, the decision-makers according to their analysis mode (or the service required by the decision-maker), such as drilldown, rollup or pivot, etc., walk-through calculations, service-oriented architecture (SOA) method through walk-through command reorganization module (ReSQL) and communication link design, dynamically load data into data sets (DS, dataset) to achieve real-time response to user needs and changes; The Removable Command Reorganization Module (ReSQL) can quickly solve the aforementioned problems faced when analyzing data by integrating different data sources (homogeneous or heterogeneous databases).

服務導向架構(SOA)中的資料集(DS,dataset)資料載入是利用server的cache key-value設計概念,當指令重組後所得到的key不在快取記憶體(cache)中才會至營運系統資料庫擷取資料。 The data loading (DS, dataset) in the service-oriented architecture (SOA) uses the server's cache key-value design concept, and the key obtained after the instruction reorganization is not in the cache memory (cache) before going to operation. The system database retrieves data.

參閱第四圖所示,第四圖說明走動式指令重組模組(ReSQL)運作的設計架構。本發明在走動式指令重組模組(ReSQL)下設計了第一服務定義檔(eistable.def)對應交易系統30及第二服務定義檔(valueSQL.def)對應資料倉儲31為服務流程之入口(或服務介面),主要負責IT人員端根據使用者端的需求,透過該介面與行為屬性來定義該需求(服務)所需要的資料環境及流程步驟,做為描述、存取、傳輸、瞭解各項服務的要素;本發明提出一個服務創新的設計架構包括不同的定義(服務)之間可透過繼承模組修改決策者的需求及透過服務間的再結合成為一個新的服務。而走動式指令重組模組(ReSQL)負責將該服務之定義及使用者參數之設定,以“走動式指令重組”的設計方式完成即時的需求(服務)分析;而且以服務為導向概念,當使用者需求改變時,指令重組及剖析模組提供應變的彈性。從第四圖可知走動式指令重組模組(ReSQL)是整個服務導向架構(SOA) 的核心,提供走動式分析模式而達成即時的分析環境。 Referring to the fourth diagram, the fourth diagram illustrates the design architecture of the operation of the walking instruction reassembly module (ReSQL). The present invention designs a first service definition file (eistable.def) corresponding to the transaction system 30 and a second service definition file (valueSQL.def) corresponding to the data warehouse 31 under the walk-through instruction reorganization module (ReSQL) as the entrance of the service process ( Or service interface), mainly responsible for the IT staff to define the data environment and process steps required by the demand (service) through the interface and behavior attributes according to the user's needs, as description, access, transmission, and understanding of each item The elements of the service; the present invention proposes a design framework for service innovation that includes different definitions (services) that can be modified by the inheritance module to modify the needs of decision makers and recombined between services to become a new service. The Removable Command Reorganization Module (ReSQL) is responsible for the definition of the service and the setting of user parameters, and completes the real-time demand (service) analysis in the design mode of "Removable Command Reorganization"; and the service-oriented concept, when When user needs change, the command reorganization and profiling modules provide resilience. From the fourth picture, we can see that the walking instruction reassembly module (ReSQL) is the entire service-oriented architecture (SOA) At the core, it provides a walk-through analysis mode to achieve an immediate analysis environment.

以下本發明導入實際醫院內部operational IS發展主管資訊系統(EIS)為範例說明在服務導向架構(SOA)下,指令重組及剖析模組設計的架構及執行結果: The following introduces the present invention into the actual hospital internal operational IS development supervisor information system (EIS) as an example to illustrate the structure and execution results of command reorganization and analysis of module design under the service-oriented architecture (SOA):

(1)第一服務定義檔(eistable.def)之行為屬性設定-多維度資料體(Data cube) (1) Behavior attribute setting of the first service definition file (eistable.def)-multi-dimensional data cube

以下範例說明IT人員如何在第一服務定義檔定義使用者分析需求(服務)。表一是第一服務定義檔中服務的屬性、屬性設定值及代表的意義,而“住院日期”,“部科”,“科室”,…等分別是對應至維度屬性名稱及衡量屬性運算式。當服務定義完成設定,指令重組及剖析模組將藉由第一服務定義檔(國科範一)函數取得定義內容,結合使用者參數設定,重組資料運算擷取指令將資料載入至資料集(DS)中,如第五圖所示;隨後根據使用者分析需求提供多維度資料的分析環境,進行如下探(drilldown)或上捲(rollup)等運算時,指令重組及剖析模組便能辨識目前所在的維度動態的提供即時的分析資料,使得階層式的景觀變的容易,執行結果請參考第六圖至第八圖;甚至在不同的維度中可檢視其該層較詳細資料或進行樞紐(pivoting)分析,執行結果請參考第九圖。由表一得知IT人員端只需了解企業內部資料庫架構及簡單的SQL指令用以簡單編寫第一服務定義檔便可結合本發明服務導向架構(SOA)快速建構 出具有資料倉儲多維度資料的分析環境,提供決策者drilldown,rollup等分析運算。 The following example illustrates how IT personnel define user analysis needs (services) in the first service definition file. Table 1 shows the attributes, set values and meanings of the services in the first service definition file, while "Hospitalization Date", "Department", "Department", ... etc. are the expressions corresponding to the dimension attribute name and measurement attribute, respectively . When the service definition is set up, the command reorganization and analysis module will obtain the definition content through the function of the first service definition file (National Science Fan One), combined with the user parameter settings, reorganize the data operation and retrieve the command to load the data into the data set (DS), as shown in the fifth figure; then provide multi-dimensional data analysis environment according to user analysis needs, when performing the following drilldown or rollup operations, the command reorganization and analysis module can Identify the current dimension and dynamically provide real-time analysis data, making the hierarchical landscape easier. Please refer to Figures 6 to 8 for execution results; even in different dimensions, you can view more detailed data or carry out For pivot analysis, please refer to the ninth figure for execution results. It is known from Table 1 that the IT staff only needs to understand the internal database structure of the enterprise and simple SQL commands to simply write the first service definition file to quickly construct the service-oriented architecture (SOA) of the present invention An analysis environment with multi-dimensional data for data storage is provided to provide decision-makers with drilldown, rollup and other analytical operations.

Figure 102120982-A0305-02-0021-1
Figure 102120982-A0305-02-0021-1

前面提到資料集(DS)中的資料載入是利用server的cache key-value設計概念,當指令重組後所得到的key不在快取記憶體中才至營運系統資料庫擷取資料。為了加速讀取時間第一服務定義檔會載入至快取記憶體(當第一服務定義檔有所修改會自動將快取記憶體中相關的key-values移除)。 As mentioned earlier, data loading in the data set (DS) uses the server's cache key-value design concept. The key obtained after command reorganization is not in the cache memory to retrieve data from the operating system database. In order to speed up the reading time, the first service definition file will be loaded into the cache memory (when the first service definition file is modified, the relevant key-values in the cache memory will be automatically removed).

(2)服務定義繼承模組設計 (2) Service definition inherits module design

本發明融入了物件導向之繼承特性,允許子定義透過繼承父定義的方式修改決策者的需求(子定義欄位設定可以override或extend父定義的設定),其繼承的方式有 兩種(1)繼承之後在第一服務定義檔中不產生新的定義(2)繼承之後在第一服務定義檔中產生新的定義。以下說明這兩種繼承的方式:繼承之後在第一服務定義檔中不產生新的定義:倘若決策者下探的資料需求有所調整,IT人員端透過eistable函數取得範例一定義內容並重新定義drilldown的設定,修改成決策者所需的維度,如表二所示。第十圖至第十二圖分別說明繼承之後下探維度的改變,但資料來源維持範例一的設定,另外值得一提的是若下探維度不包括原分析需求維度,如決策者需看部科的彙整資料,則可進入明細,指令重組及剖析模組將重新組合擷取指令至營運系統資料庫擷取明細資料,提供決策者進行樞紐(pivot)分析(維度分析),請參考第十三圖。 The invention incorporates the object-oriented inheritance feature, allowing the child definition to modify the decision maker's needs by inheriting the parent definition (the child definition field setting can override or extend the parent definition setting), and its inheritance methods are: Two (1) No new definition is generated in the first service definition file after inheritance (2) A new definition is generated in the first service definition file after inheritance. The following two methods of inheritance are described: After inheritance, no new definition is generated in the first service definition file: if the data requirements of the decision-maker's probe are adjusted, the IT staff obtains the definition content of example 1 through the eistable function and redefines it The settings of drilldown are modified to the dimensions required by decision makers, as shown in Table 2. The tenth to twelfth figures illustrate the change of the dip dimension after inheritance, but the data source maintains the setting of Example 1. It is also worth mentioning that if the dip dimension does not include the original analysis requirement dimension, if the decision maker needs to see the department The summary data of the branch can be entered into the details. The instruction reorganization and analysis module will reassemble the retrieval instructions to the operating system database to retrieve the detailed data and provide decision makers with pivot analysis (dimension analysis). Please refer to the tenth Three pictures.

Figure 102120982-A0305-02-0022-2
Figure 102120982-A0305-02-0022-2

繼承原範例一的定義,在第一服務定義檔中產生新的定義(可允許再被繼承):假如維度屬性欲修改成部科及醫師,請參考表三及第十四圖至第十五圖之說明,其中表三中“ref=國科範一”將繼承國科範一的所有的定義而“xcols=部科”指定第一層維度屬性為部科,而“drilldown=部科,醫師”覆蓋父定義之設定重新定義維度屬 性。另外指令重組及剖析模組支援使用者端在不同的維度間走動式提供分析服務(請參考第十六圖年度分析資料)。 Inherit the definition of the original example 1, and create a new definition in the first service definition file (may be allowed to be inherited again): If the dimension attribute is to be modified into a department and a physician, please refer to Table 3 and Figures 14 to 15 The description of the figure, in which "ref=National Science Fanyi" in Table 3 will inherit all the definitions of National Science Fanyi and "xcols=Ministry" specifies the first-level dimension attribute as the ministry, and "drilldown=Ministry," Physician" overrides the definition of the parent definition to redefine the dimension Sex. In addition, the command reorganization and analysis module supports the user side to provide analysis services in different dimensions (please refer to the annual analysis data in Figure 16).

Figure 102120982-A0305-02-0023-3
Figure 102120982-A0305-02-0023-3

(3)第二服務定義檔(valueSQL.def)-多重資料來源整合:企業營運的環境裡往往有不同的交易系統運作,這些系統因建置時間不同而使用不同的資料庫管理系統(DBMS),甚至不同系統上的屬性命名方式(data naming)、資料表示法(data representation)、資料編碼(data encoding)或資料內容(data content)、資料單位(data scaling)都不一致。一個BI解決方案必須要和企業的整體資訊環境能無縫地整合在一起。在沒有建置資料倉儲或是額外的儲存體(physical data repository)的情況下要如何快速的直接整合多重資料來源至單一個即時的分析環境以提供決策者即時的分析資料,是具有高難度挑戰的任務;另一方面IT人員常常需花費大量的時間才能完成整合的工作。本發明所導入服務導向架構(SOA)透過服務間的再結合成為一個新的服務的創新設計架構,讓異質系統整合變得容易,不僅快速地解決企業經常所面臨異質資料整合的問題,而且滿足企業動態的流程需求,支援商業模式的創新。表四為住院申報的範例 資料庫(EIS1)及人事資料庫(HR),EIS1儲存著醫院每天病患住院的交易資訊,每一筆交易記錄著哪個住院病患由哪一位醫生看診及所需的藥費(MedFee)、病患部分負擔費用(PortFee)及申請費用(AppFee)。而HR資料庫儲存著每位醫生人事資料及等級歸類的資訊,為了分析醫療費用相關的數據,目前BIS必須架構在一個多維度模型的資料倉儲環境下,如表五所示。該資料倉儲C(Data Mart C)利用ETL(Extraction,Transformation,and Load)分別從EIS1及HR資料庫中取得資訊,目的是為了橫跨所有相關醫療分析維度及根據現有及可用的運營數據達成決策流程。其中醫生維度整合了從EIS1及HR資料庫中的醫生資料表。一旦多維度的資料倉儲建置完成時,通常使用OLTP的工具允許使用者根據不同的維度分析資料。相反的若資料倉儲未建置,假設要將等級A(主任醫師)的醫師在過去三年中八月份看診的資料彙整至單一個即時的分析環境以提供決策者即時的分析資料,是具有高複雜及高難度挑戰的任務。 (3) Second service definition file (valueSQL.def)-integration of multiple data sources: There are often different transaction systems operating in the environment in which companies operate. These systems use different database management systems (DBMS) due to different construction times Even the attribute naming methods (data naming), data representation (data representation), data encoding (data encoding) or data content (data content), and data units (data scaling) on different systems are inconsistent. A BI solution must be seamlessly integrated with the overall information environment of the enterprise. It is very difficult to quickly integrate multiple data sources into a single real-time analysis environment to provide real-time analysis data for decision makers without the establishment of a data warehouse or additional data storage (physical data repository) Tasks; on the other hand, IT staff often spend a lot of time to complete the integration work. The service-oriented architecture (SOA) introduced by the invention becomes a new service innovative design architecture through the recombination of services, which makes the integration of heterogeneous systems easy, not only quickly solves the problem of heterogeneous data integration that enterprises often face, but also meets The dynamic process requirements of enterprises support the innovation of business models. Table 4 is an example of hospitalization declaration The database (EIS1) and the personnel database (HR), EIS1 stores the hospital's daily patient inpatient transaction information, each transaction records which hospitalized patient is visited by which doctor and the required medical expenses (MedFee) , Part of the patient's burden (PortFee) and application fee (AppFee). The HR database stores the information of each doctor's personnel information and classification. In order to analyze the data related to medical expenses, the current BIS must be structured in a multi-dimensional model data storage environment, as shown in Table 5. The data warehouse C (Data Mart C) uses ETL (Extraction, Transformation, and Load) to obtain information from the EIS1 and HR databases, respectively, in order to reach decisions across all relevant medical analysis dimensions and based on existing and available operational data Process. The doctor dimension integrates the doctor data table from EIS1 and HR database. Once the multi-dimensional data warehouse is built, the OLTP tool is usually used to allow users to analyze the data according to different dimensions. On the contrary, if the data warehouse is not built, it is assumed that the data of the doctors of grade A (leading physician) in the past three years in August will be aggregated into a single real-time analysis environment to provide decision-makers with real-time analysis data. Highly complex and challenging tasks.

Figure 102120982-A0305-02-0025-4
Figure 102120982-A0305-02-0025-4

Figure 102120982-A0305-02-0025-5
Figure 102120982-A0305-02-0025-5

Figure 102120982-A0305-02-0026-6
Figure 102120982-A0305-02-0026-6

Figure 102120982-A0305-02-0026-7
Figure 102120982-A0305-02-0026-7

Figure 102120982-A0305-02-0026-8
Figure 102120982-A0305-02-0026-8

Figure 102120982-A0305-02-0027-10
Figure 102120982-A0305-02-0027-10

Figure 102120982-A0305-02-0027-11
Figure 102120982-A0305-02-0027-11

本發明利用以下範例說明在沒有建置資料倉儲的基礎下,如何具有資料倉儲多維度資料的分析環境及運算,而快速達成多重資料來源整合。假設前述範例中的資料來源為EIS1資料庫(醫院申報資料庫),其中“醫療費用”是指該科醫生與病人之間有醫療行為而產生需申報至健保局的總費用(包括看診費、藥費、檢查費及儀器使用費等),基於主管的分析角度,“醫療費用”應該包含了該科所有介入的資源(包括該科的護士、行政人員或是有些未看診的醫生等資源),而主管欲了解其該科醫師總人數以便於分析收入與付出成本是否有落差,進一步下達某些決策;然而要取得該科醫師總人數並不能從EIS1單一資料庫獲得,還必須從另一個資料庫才能取得完整資料。以下將說明如何透過服務間的再結合成為一個新的服務以達成多重資料的整合: 表六是本發明所設計第二服務定義檔提供處理多重資料整合的服務機制,其中“專科醫師”是指該服務的資料來源名稱經由資料來源內容設定後,也就是前述中該科所有醫生(假設包括該月有看診及未看診醫生)的人數,其資料來源是從HR資料庫;而在“專科醫師.setting”中是指該資料來源屬性設定,如本範例中的資料來源是HR資料庫及若要下探至醫師的明細資料則在<RawSelect></RawSelect>標籤中指定(如ID_DOCTOR_NAME為醫師姓名);一旦IT人員完成設定後,便可結合第一服務定義檔中所定義的服務整合至單一資料集(DS)中即完成不同資料來源整合,如表七說明。本範例四的第一服務定義檔之資料定義是繼承範例三的定義,只需將“專科醫師”加入(“+”)至vcols中即可整合至資料集(DS)中,及後續可以與其他的衡量屬性作運算(如平均看診人數);隨後使用者在不同的維度中,指令重組及剖析模組根據目前所在的維度重組兩個不同資料來源的擷取指令以達成數值整合之目的,請參考第十七圖之一整合架構說明。另外前述所提到其醫生的等級分類的資料來自表四中HR資料庫,假設要將等級A的醫生在過去三年中八月份看診的資料彙整至單一個OLAP的分析環境,請參閱表八、表九的分類之整合定義說明,其整合架構圖請參考第十七圖之二;甚至不同年度的比較資料也能快速地整合至資料集(DS)中,請參考第十九 至第二十一圖執行的結果。 The present invention uses the following examples to illustrate how to have a multi-dimensional data analysis environment and operations for data storage without quickly building a data storage, and quickly achieve integration of multiple data sources. Assume that the data source in the preceding example is the EIS1 database (hospital declaration database), where “medical expenses” refers to the total expenses (including the consultation fee) that have to be reported to the Health Insurance Bureau due to the medical behavior between the doctor and the patient , Medical expenses, inspection fees and equipment usage fees, etc.), based on the supervisor’s analysis, the “medical expenses” should include all the resources of the department’s intervention (including the nurses, administrators or some doctors who have not seen the department) Resources), and the supervisor wants to know the total number of physicians in the department in order to analyze whether there is a gap between income and cost, and further make certain decisions; however, to obtain the total number of physicians in the department cannot be obtained from the EIS1 single database, it must also be obtained from Complete information can only be obtained from another database. The following will explain how to combine services to form a new service to achieve the integration of multiple data: Table 6 is the second service definition file designed by the present invention to provide a service mechanism for processing multiple data integrations, where "specialist" refers to the name of the data source of the service after the content of the data source is set, that is, all the doctors in the department in the foregoing ( Suppose that includes the number of doctors who have been seen and not seen in the month. The data source is from the HR database; in the "specialist.setting", it means the attribute setting of the data source. For example, the data source in this example is The HR database and the detailed data to be drilled down to the doctor are specified in the <RawSelect></RawSelect> tag (if ID_DOCTOR_NAME is the doctor’s name); once the IT staff completes the settings, they can combine the information in the first service definition file The integration of the defined services into a single data set (DS) completes the integration of different data sources, as shown in Table 7. The data definition of the first service definition file of this example 4 inherits the definition of example 3, and it can be integrated into the data set (DS) by adding "specialist" ("+") to vcols Calculation of other measurement attributes (such as the average number of visits); then the user in different dimensions, the command reorganization and analysis module reorganizes the retrieval commands of two different data sources according to the current dimension to achieve the purpose of numerical integration , Please refer to the integrated architecture description in Figure 17. In addition, the data on the classification of the doctors mentioned above comes from the HR database in Table 4. Assuming that the data of the doctors of Grade A in August in the past three years have been aggregated into a single OLAP analysis environment, please refer to the table 8. The definition of the integration definition of the classification in Table 9, please refer to Figure 17 bis for the integrated architecture diagram; even the comparative data of different years can be quickly integrated into the data set (DS), please refer to the 19th To the results of the twenty-first figure execution.

另外如何有效的解決前述中提到資料整合所面臨的問題如屬性命名、資料表示法等不一致的問題。本發明以屬性命名不一致為例說明解決的方法。倘若在第十八圖中多重資料來源之間的key(維度)的屬性名稱或資料表示法不一致;例如,假設在第一服務定義檔所定義的資料來源key的屬性名稱為xyz,xyz1,…,而第二服務定義檔所定義的資料來源key的屬性名稱為abc,abc1…,本發明設計的方式則在第二服務定義檔中定義屬性的mapping,即可達成一致。請參閱表十的設定;若是資料表示法(資料型態)上的衝突,可搭配使用資料庫管理系統所提供的函數(如convert,substring,…)或自定函數(如:to_char,:substr,…),如表十中xyz=:to_char(abc),轉換成一致的資料型態。 In addition, how to effectively solve the aforementioned inconsistencies such as attribute naming, data representation, etc. that are faced by the data integration mentioned above. The invention takes the inconsistent attribute naming as an example to explain the solution method. If the attribute name or data representation of the key (dimension) between the multiple data sources in Figure 18 is inconsistent; for example, suppose the attribute name of the data source key defined in the first service definition file is xyz, xyz1,... The attribute name of the data source key defined in the second service definition file is abc, abc1.... The design method of the present invention defines the mapping of the attribute in the second service definition file to achieve agreement. Please refer to the settings in Table 10; if there is a conflict in the data representation (data type), you can use the functions provided by the database management system (such as convert, substring, ...) or custom functions (such as: to_char,: substr ,...), as shown in Table 10, xyz=: to_char(abc), converted to a consistent data type.

再舉個例子說明第二服務定義檔與第一服務定義檔服務間的結合,解決不同類型多重資料整合的問題。假設決策者需要某個分析資料,此資料根據不同的下探維度需從兩個不同資料庫中彙整(可能加總、平均其他運算)不同資料表中某個(些)欄位值(欄位名稱不一定是一致),只要類似表六在第二服務定義檔分別定義兩個資料來源(假設DS1及DS2),接下來在第一服務定義檔將DS1及DS2加入vcols中(如表七中的“專科醫師”),再利用compute(如表七中的“平均看診人數”)進行彙整而達成整合。 Another example illustrates the combination of the second service definition file and the first service definition file service to solve the problem of integrating multiple data of different types. Assuming that the decision maker needs a certain analysis data, this data needs to be aggregated from two different databases (possibly summed up, averaged other calculations) according to different drill-down dimensions. The names are not necessarily consistent), as long as similar to Table 6 define two data sources in the second service definition file (assuming DS1 and DS2), then add DS1 and DS2 to vcols in the first service definition file (as shown in Table 7) "Specialists"), and then use compute (such as "average number of patients" in Table 7) to consolidate and achieve integration.

綜觀上述第二服務定義檔設計目的除了快速整合資料來源分別是從不同的資料庫,在某些情況需要較複雜的運算,只要在第二服務定義檔中定義再與第一服務定義檔結合而達到整合的目的,請參考表十一我們再更深入地探討此創新的設計架構,如表六中所定義的“專科醫師”,實際上它所代表的是一個物件的設計觀念,而這個物件可以在第一服務定義檔中任何一個服務定義的流程中被使用(只要該服務流程與物件間是可以連結),透過傳訊的連結達到整合及物件重用性目的,也呼應了前面所敘述服務間可以再結合成為一個新的服務。 Looking at the design purpose of the second service definition file above, in addition to the rapid integration of data sources from different databases, in some cases, more complicated calculations are required, as long as they are defined in the second service definition file and then combined with the first service definition file. For the purpose of integration, please refer to Table 11 and we will discuss this innovative design architecture in more depth, such as the "specialist" defined in Table 6, in fact, it represents the design concept of an object, and this object Can be used in any service definition process in the first service definition file (as long as the service process and the object can be linked), through the link of the message to achieve the purpose of integration and object reuse, also echoes the previously described service room Can be combined into a new service.

由上述說明第二服務定義檔與第一服務定義檔服務定義間的結合快速完成使用者不同的服務需求,並且解決較複雜問題及快速達到多重資料來源整合。另外值得一提的是,架構在走動式指令重組模組(ReSQL)之基礎上,可以容易地擴展不同的服務流程之定義,完成不同的服務功能,也說明走動式指令重組模組(ReSQL)嚴謹的架構設計、完整的結合性及高度的凝聚力。 According to the above description, the combination of the second service definition file and the first service definition file service definition can quickly complete different service needs of users, and solve more complicated problems and quickly achieve integration of multiple data sources. It is also worth mentioning that the architecture is based on the Removable Command Reorganization Module (ReSQL), which can easily expand the definition of different service processes and complete different service functions. It also shows the Reactive Command Reorganization Module (ReSQL) Strict architecture design, complete integration and high cohesion.

Figure 102120982-A0305-02-0030-12
Figure 102120982-A0305-02-0030-12
Figure 102120982-A0305-02-0031-13
Figure 102120982-A0305-02-0031-13

(3)資料倉儲(Cube)及線上交易系統資料同步整合 (3) Data warehouse (Cube) and online trading system data synchronization integration

前述中提到Data warehouse及Cube具有某種程度支援的必要性或是企業內部已建置了資料倉儲,基於企業在不同彈性需求因素下,本發明所設計服務導向架構(SOA)亦適用於資料倉儲基礎上,更進一步的可同時整合資料倉儲(或Cube)及交易系統資料,其整合方法如表十二所示。在資料來源起始設定中指定該來源是從何種資料庫系統 ,如CUBE1=匯總一(假設CUBE1的資料來源是Data warehouse環境);EIS1=即時一(假設EIS1的資料來源是醫院申報交易系統),而交易系統內資料的取得則可指定從EIS1,如表十二所述Cube1.RawDataDB=EIS1及EIS1.IsCubeDB=false。本發明修改範例一說明如何在第一服務定義檔同步整合資料倉儲(Cube)及交易系統資料;請參考表十三中“table.cube=eiscubeview(DTLFBC)”意指維度屬性的資料來源是從CUBE1中的資料表“DTLFBC”取得,而即時交易資料來源則是從EIS1。前述所列舉範例二至範例四其資料來源定義皆是繼承範例一之定義,一旦範例一之定義有所修改所有繼承的範例皆一併修改。因目前CUBE1彙整後的資料與前述範例之資料來源為EIS1所執行結果是一致,所以在此無需提供整合結果畫面。 As mentioned above, the Data warehouse and Cube have a certain degree of support or the enterprise has built a data warehouse. Based on the enterprise's different elastic demand factors, the service-oriented architecture (SOA) designed by the present invention is also suitable for data. On the basis of warehousing, it can further integrate data storage (or cube) and transaction system data at the same time. The integration method is shown in Table 12. Specify which database system the source is from in the initial settings of the data source , Such as CUBE1=summary 1 (assuming CUBE1’s data source is Data warehouse environment); EIS1=real-time one (assuming EIS1’s data source is the hospital declaration transaction system), and the data in the transaction system can be specified from EIS1, as shown in the table Twelve Cube1.RawDataDB=EIS1 and EIS1.IsCubeDB=false. Modification example 1 of the present invention shows how to integrate data warehouse (Cube) and transaction system data in the first service definition file; please refer to Table 13 "table.cube=eiscubeview(DTLFBC)" means that the data source of the dimension attribute is from The data table "DTLFBC" in CUBE1 is obtained, and the real-time transaction data source is from EIS1. The data source definitions of the above-mentioned example 2 to example 4 are all inherited from the definition of example 1. Once the definition of example 1 is modified, all the inherited examples are modified together. Since the current data collected by CUBE1 is consistent with the result of the above example, the data source is EIS1, so there is no need to provide an integrated result screen here.

Figure 102120982-A0305-02-0032-14
Figure 102120982-A0305-02-0032-14

Figure 102120982-A0305-02-0032-15
Figure 102120982-A0305-02-0032-15
Figure 102120982-A0305-02-0033-16
Figure 102120982-A0305-02-0033-16

(4)整合其他服務功能之定義檔 (4) Integrate definition files of other service functions

綜合以上的說明,本發明所設計走動式指令重組模組(ReSQL)真正落實了服務導向架構(SOA)的核心精神,也就是說強調抽象(abstraction)、可組性(composability)、可重用性(reusability)以實現BI 2.0即時分析服務。 Based on the above description, the walking instruction reorganization module (ReSQL) designed by the present invention truly implements the core spirit of the service-oriented architecture (SOA), that is, emphasizes abstraction, composability, and reusability (reusability) to achieve BI 2.0 real-time analysis services.

40‧‧‧服務導向架構(SOA) 40‧‧‧Service Oriented Architecture (SOA)

41‧‧‧走動式指令重組模組(ReSQL) 41‧‧‧ Walking Reorganization Module (ReSQL)

411‧‧‧指令重組及剖析模組 411‧‧‧Command reorganization and analysis module

412‧‧‧第一服務定義檔(eistable.def) 412‧‧‧First service definition file (eistable.def)

413‧‧‧第二服務定義檔(valueSQL.def) 413‧‧‧Second service definition file (valueSQL.def)

414‧‧‧繼承模組 414‧‧‧Inheritance module

42‧‧‧資料集(DS) 42‧‧‧ Dataset (DS)

43‧‧‧語法轉換模組 43‧‧‧grammar conversion module

44‧‧‧多重值資料處理模組 44‧‧‧Multi-value data processing module

45‧‧‧維度整合模組 45‧‧‧Dimensional Integration Module

461‧‧‧使用者介面輸出模組 461‧‧‧User interface output module

462‧‧‧使用者介面控制模組 462‧‧‧User interface control module

47‧‧‧過濾器 47‧‧‧filter

48‧‧‧同質或異質資料庫 48‧‧‧ homogeneous or heterogeneous database

49‧‧‧快取記憶體(cache) 49‧‧‧Cache

Claims (4)

一種即時商業智慧系統之走動式指令重組的服務導向架構(SOA),包括:一服務導向架構(SOA)(40)分別與一使用者端及一資訊科技(Information Technology,IT)人員端電訊連結;其特徵在於:該服務導向架構(SOA)(40)包括一走動式指令重組模組(ReSQL)(41),該走動式指令重組模組(ReSQL)(41)包括由一指令重組及剖析模組(411)、一第一服務定義檔(eistable.def)(412)、一第二服務定義檔(valueSQL.def)(413)及一繼承模組(414)相互電訊連結組成,該第一服務定義檔(eistable.def)(412)及該第二服務定義檔(valueSQL.def)(413)由該資訊科技(IT)人員端簡單定義,一同質或異質資料庫(48)電訊連結該走動式指令重組模組(ReSQL)(41),資料取自同質或異質資料庫(48),其係即時依該走動式指令重組模組(ReSQL)(41)動態地自動重組最佳化指令,再前往該同質或異質資料庫(48)取得所需資料,該服務導向架構(SOA)(40)更包含一語法轉換模組(43)電訊連結同質或異質資料庫(48)及該走動式指令重組模組(ReSQL)(41),藉由該語法轉換模組(43)得以語法轉換該指令重組及剖析模組(411)與該同質或異質的資料庫(48),使所有資料之自動取得因語法轉換而可達成,該繼承模組(414)可在該走動式指令重組模組(ReSQL)(41)各服務間透過繼承的方式修改該使用者端的需 求及透過該走動式指令重組模組(ReSQL)(41)服務間的再結合成為一個新的服務,該指令重組及剖析模組(411)負責將該走動式指令重組模組(ReSQL)(41)服務的定義及使用者端輸入的參數設定以走動式指令重組的指令重組運算模式完成即時的需求服務分析。 A service-oriented architecture (SOA) for walk-through instruction reorganization of real-time business intelligence systems, including: a service-oriented architecture (SOA) (40) connected to a user terminal and an information technology (IT) personnel-side telecommunications ; It is characterized in that the service-oriented architecture (SOA) (40) includes a walking instruction reorganization module (ReSQL) (41), and the walking instruction reorganization module (ReSQL) (41) includes a command reorganization and analysis The module (411), a first service definition file (eistable.def) (412), a second service definition file (valueSQL.def) (413) and an inheritance module (414) are composed of mutual telecommunication links. A service definition file (eistable.def) (412) and the second service definition file (valueSQL.def) (413) are simply defined by the information technology (IT) staff, with a homogeneous or heterogeneous database (48) telecommunications link The walking instruction reorganization module (ReSQL) (41), the data is taken from the homogenous or heterogeneous database (48), which is based on the moving instruction reorganization module (ReSQL) (41) dynamically and automatically reorganization optimization Instruction, and then go to the homogeneous or heterogeneous database (48) to obtain the required data, the service-oriented architecture (SOA) (40) further includes a syntax conversion module (43) telecommunications link to the homogeneous or heterogeneous database (48) and the Removable instruction reorganization module (ReSQL) (41), through which the syntax conversion module (43) can grammatically convert the instruction reorganization and analysis module (411) and the homogeneous or heterogeneous database (48), so that all Automatic data acquisition can be achieved due to grammatical conversion. The inheritance module (414) can modify the needs of the user side through inheritance between the services of the walk-around command reorganization module (ReSQL) (41) The reorganization between the services through the Removable Command Reorganization Module (ReSQL) (41) is sought as a new service. The Reorganization and Analysis Module (411) is responsible for the ReSQL Reorganization Module (ReSQL) ( 41) The definition of the service and the parameter settings input by the user end complete the real-time demand service analysis in the order reorganization operation mode of the walk-through order reorganization. 如申請專利範圍第1項所述之即時商業智慧系統之走動式指令重組的服務導向架構(SOA),其中該指令重組及剖析模組(411)建構有完整的擷取指令,該指令重組及剖析模組(411)更具有重組後的指令最佳化。 The service-oriented architecture (SOA) of the walk-through instruction reorganization of the real-time business intelligence system as described in item 1 of the patent scope, wherein the instruction reorganization and profiling module (411) is constructed with a complete retrieval instruction, the instruction reorganization and The profiling module (411) also has reorganized instruction optimization. 如申請專利範圍第1項所述之即時商業智慧系統之走動式指令重組的服務導向架構(SOA),其中該使用者端取用資料方式,包括下探(Drill-down)、上捲(Roll-up)、樞鈕分析(Pivot)或切片(Slice)。 The service-oriented architecture (SOA) of the walk-through instruction reorganization of the real-time business intelligence system as described in item 1 of the patent scope, in which the user side accesses data, including drill-down and roll-up -up), pivot analysis (Pivot) or slice (Slice). 一種即時商業智慧系統之走動式指令重組的服務導向架構(SOA),包括:一服務導向架構(SOA)(40)分別與一使用者端及一資訊科技(Information Technology,IT)人員端電訊連結;其特徵在於:該服務導向架構(SOA)(40)包括一走動式指令重組模組(ReSQL)(41),該走動式指令重組模組(ReSQL)(41)包括由一指令重組及剖析模組(411)、一第一服務定義檔(eistable.def)(412)、一第二服務定義檔(valueSQL.def)(413)及一繼承模組(414)相互電訊連結組成,該第一服務定義檔 (eistable.def)(412)及該第二服務定義檔(valueSQL.def)(413)由該資訊科技(IT)人員端簡單定義,一同質或異質資料庫(48)電訊連結該走動式指令重組模組(ReSQL)(41),資料取自該同質或異質資料庫(48),其係即時依該走動式指令重組模組(ReSQL)(41)_動態地自動重組最佳化指令,再前往該同質或異質資料庫(48)取得所需資料,該服務導向架構(SOA)(40)更包含一語法轉換模組(43)電訊連結該同質或異質資料庫(48)及該走動式指令重組模組(ReSQL)(41),藉由該語法轉換模組(43)得以語法轉換該指令重組及剖析模組(411)與該同質或異質的資料庫(48),使所有資料之自動取得因語法轉換而可達成,該繼承模組(414)可在各該走動式指令重組模組(ReSQL)(41)服務間透過繼承的方式修改該使用者端的需求及透過該走動式指令重組模組(ReSQL)(41)服務間的再結合成為一個新的服務,該指令重組及剖析模組(411)負責將該走動式指令重組模組(ReSQL)(41)服務的定義及使用者端輸入的參數設定以走動式指令重組的指令重組運算模式完成即時的需求服務分析;其中該服務導向架構(SOA)(40)更包含有一多重值資料處理模組(44),該多重值資料處理模組(44)電訊連結該走動式指令重組模組(ReSQL)(41)、該語法轉換模組(43)及該同質或異質資料庫(48),以該多重值資料處理模組(44)進行多重資料計算整合; 其中該服務導向架構(SOA)(40)更包含有一資料集(DS,dataset)(42)及一快取記憶體(cache)(49),該資料集(42)電訊連結該走動式指令重組模組(ReSQL)(41)、該多重值資料處理模組(44)、該同質或異質資料庫(48)與該使用者端,指令重組後進至該資料集(42),該資料集(42)由該快取記憶體(cache)(49)找不到資料時才會至指令對應的該同質或異質資料庫(48)擷取資料;其中該服務導向架構(SOA)(40)更包括一維度整合模組(45),該維度整合模組(45)電訊連結該資料集(42)(DS,dataset)與該使用者端,該維度整合模組(45)得整合衡量值與分析維度分散在不同的該同質或異質資料庫(48)之資料,再以整合後的資料展示在使用者端顯示器;其中該服務導向架構(SOA)(40)更包括一過濾器(47),該過濾器(47)電訊連結該維度整合模組(45)與該使用者端,該過濾器(47)以該使用者端設定的條件,過濾掉該維度整合模組(45)整合後資料的多餘部分,再以過濾後的資料展示在該使用者端顯示器;其中該服務導向架構(SOA)(40)更包括一使用者介面控制模組(462),該使用者介面控制模組(462)電訊連結該使用者端、該IT人員端、該走動式指令重組模組(ReSQL)(41)、該資料集(42)及該過濾器(47),該使用者介面控制模組(462)接受該使用者端控制輸入,並將輸入訊號送至該IT人員端 、該走動式指令重組模組(ReSQL)(41)、該資料集(42)及該過濾器(47),或接收該IT人員端、該走動式指令重組模組(ReSQL)(41)、該資料集(42)及該過濾器(47)訊號控制往該使用者端之輸出;其中該服務導向架構(SOA)(40)更包括一使用者介面輸出模組(461),該使用者介面輸出模組(461)電訊連結該過濾器(47)、該使用者介面控制模組(462)及該使用者端,該使用者介面輸出模組(461)可輸出資料至該使用者端顯示器。 A service-oriented architecture (SOA) for walk-through instruction reorganization of real-time business intelligence systems, including: a service-oriented architecture (SOA) (40) connected to a user terminal and an information technology (IT) personnel-side telecommunications ; It is characterized in that the service-oriented architecture (SOA) (40) includes a walking instruction reorganization module (ReSQL) (41), and the walking instruction reorganization module (ReSQL) (41) includes a command reorganization and analysis The module (411), a first service definition file (eistable.def) (412), a second service definition file (valueSQL.def) (413) and an inheritance module (414) are composed of mutual telecommunication links. A service definition file (eistable.def) (412) and the second service definition file (valueSQL.def) (413) are simply defined by the information technology (IT) staff, and the mobile or heterogeneous database (48) telecommunications link the walking command Reorganization module (ReSQL) (41), the data is taken from the homogenous or heterogeneous database (48), which is a real-time reorganization module (ReSQL) (41) _ dynamically and automatically reorganizes the optimized instruction according to the walking instruction. Then go to the homogeneous or heterogeneous database (48) to obtain the required data. The service-oriented architecture (SOA) (40) further includes a syntax conversion module (43) to connect the homogeneous or heterogeneous database (48) and the walk Instruction Reorganization Module (ReSQL) (41), through which the grammar conversion module (43) can grammatically convert the instruction reorganization and analysis module (411) and the homogeneous or heterogeneous database (48), so that all data The automatic acquisition can be achieved due to the grammatical conversion. The inheritance module (414) can modify the needs of the user terminal and inherit the walkthrough through inheritance between each service of the walkable instruction reorganization module (ReSQL) (41). The reorganization of the instruction reorganization module (ReSQL) (41) into a new service, the instruction reorganization and analysis module (411) is responsible for the definition and service of the walk-through instruction reorganization module (ReSQL) (41) The parameter settings entered by the user terminal complete the real-time demand service analysis by the command reorganization operation mode of the walk-through command reorganization; wherein the service-oriented architecture (SOA) (40) further includes a multi-value data processing module (44). The value data processing module (44) telecommunications connects the walking instruction reorganization module (ReSQL) (41), the grammar conversion module (43) and the homogeneous or heterogeneous database (48), using the multiple value data processing module Group (44) performs multiple data calculation and integration; The service-oriented architecture (SOA) (40) further includes a data set (DS, dataset) (42) and a cache (cache) (49), the data set (42) telecommunications link to the walk-through command reorganization The module (ReSQL) (41), the multi-value data processing module (44), the homogeneous or heterogeneous database (48) and the user terminal, after the instruction reorganization, the data set (42), the data set ( 42) When the cache (49) cannot find data, it will only retrieve data from the homogeneous or heterogeneous database (48) corresponding to the command; the service-oriented architecture (SOA) (40) is more It includes a one-dimensional integration module (45). The one-dimensional integration module (45) connects the data set (42) (DS, dataset) with the user terminal through telecommunications. The one-dimensional integration module (45) has integrated measurement Analyze the data scattered in different homogeneous or heterogeneous databases (48), and then display the integrated data on the user-side display; the service-oriented architecture (SOA) (40) further includes a filter (47) , The filter (47) telecommunications connects the dimension integration module (45) and the user terminal, and the filter (47) filters out the dimension integration module (45) after integration according to the conditions set by the user terminal The redundant part of the data is displayed on the user-side display as filtered data; wherein the service-oriented architecture (SOA) (40) further includes a user interface control module (462), the user interface control module (462) Telecommunications link the user terminal, the IT personnel terminal, the walking command reorganization module (ReSQL) (41), the data set (42) and the filter (47), the user interface control module (462) Accept the control input from the user terminal and send the input signal to the IT staff , The walking instruction reorganization module (ReSQL) (41), the data set (42) and the filter (47), or receiving the IT staff, the walking instruction reorganization module (ReSQL) (41), The data set (42) and the filter (47) signals control the output to the user end; wherein the service-oriented architecture (SOA) (40) further includes a user interface output module (461), the user The interface output module (461) is electrically connected to the filter (47), the user interface control module (462) and the user terminal, and the user interface output module (461) can output data to the user terminal monitor.
TW102120982A 2013-06-13 2013-06-13 Service-oriented architecture (SOA) for walk-through command reorganization of real-time business intelligence systems TWI684154B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
TW102120982A TWI684154B (en) 2013-06-13 2013-06-13 Service-oriented architecture (SOA) for walk-through command reorganization of real-time business intelligence systems

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
TW102120982A TWI684154B (en) 2013-06-13 2013-06-13 Service-oriented architecture (SOA) for walk-through command reorganization of real-time business intelligence systems

Publications (2)

Publication Number Publication Date
TW201447782A TW201447782A (en) 2014-12-16
TWI684154B true TWI684154B (en) 2020-02-01

Family

ID=52707540

Family Applications (1)

Application Number Title Priority Date Filing Date
TW102120982A TWI684154B (en) 2013-06-13 2013-06-13 Service-oriented architecture (SOA) for walk-through command reorganization of real-time business intelligence systems

Country Status (1)

Country Link
TW (1) TWI684154B (en)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050240354A1 (en) * 2003-08-27 2005-10-27 Ascential Software Corporation Service oriented architecture for an extract function in a data integration platform
CN101174957A (en) * 2007-10-09 2008-05-07 南京财经大学 Cooperation service platform facing different source data
CN101969475A (en) * 2010-11-15 2011-02-09 张军 Business data controllable distribution and fusion application system based on cloud computing

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050240354A1 (en) * 2003-08-27 2005-10-27 Ascential Software Corporation Service oriented architecture for an extract function in a data integration platform
CN101174957A (en) * 2007-10-09 2008-05-07 南京财经大学 Cooperation service platform facing different source data
CN101969475A (en) * 2010-11-15 2011-02-09 张军 Business data controllable distribution and fusion application system based on cloud computing

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
1、B.S. Sahay, Jayanthi Ranjan 2008. "Real Time business intelligence in supply chain^&amp;rn^analytics".Emerald.,Pages 28-44.^&amp;rn^
1、B.S. Sahay, Jayanthi Ranjan 2008. "Real Time business intelligence in supply chain^&rn^analytics".Emerald.,Pages 28-44.^&rn^ *

Also Published As

Publication number Publication date
TW201447782A (en) 2014-12-16

Similar Documents

Publication Publication Date Title
US8793285B2 (en) Multidimensional tags
Ranjan Business justification with business intelligence
Berthold et al. An architecture for ad-hoc and collaborative business intelligence
US7716253B2 (en) Centralized KPI framework systems and methods
US9552403B2 (en) Converting data models into in-database analysis models
US20050273352A1 (en) Business method for continuous process improvement
US20060095413A1 (en) Method of exposing normalized data as denormalized tables
Tao et al. Enterprise application architecture development based on DoDAF and TOGAF
Ali et al. Business intelligence solutions in healthcare a case study: Transforming OLTP system to BI solution
CA2511196A1 (en) System and method for embedding business data in forms
US7454310B2 (en) Method for calculating business process durations
Diamantini et al. Extended drill‐down operator: Digging into the structure of performance indicators
CN102819616B (en) Cloud online real-time multi-dimensional analysis system and method
US20160063424A1 (en) Integrated framework for monitoring business activities
Orlovskyi et al. Enterprise architecture modeling support based on data extraction from business process models
CN105528360B (en) Design of walking type command recombination with service oriented architecture is realized in real-time business intelligent system
TWI684154B (en) Service-oriented architecture (SOA) for walk-through command reorganization of real-time business intelligence systems
TWM487489U (en) Walking-around type instructions reorganization design with service oriented architecture (SOA) to implement real-time business intelligence system
Longo et al. Fact–Centered ETL: A proposal for speeding business analytics up
Su et al. Business intelligence revisited
CN112862581A (en) Refined cost management system based on industry and finance integration in hospital in DRG payment mode
Malaverri et al. Estimating the quality of data using provenance: a case study in eScience.
Dunlop Beginning Big Data with Power BI and Excel 2013: Big Data Processing and Analysis Using PowerBI in Excel 2013
US20050251436A1 (en) Method of separating reporting definitions from execution definitions in a business process
El Mohajir et al. Towards a framework incorporating functional and non-functional requirements for data warehouse conceptual design