TW201447782A - Real-time business intelligent system realized and designed by walking instruction reconfiguration of service-oriented architecture (SOA) - Google Patents

Real-time business intelligent system realized and designed by walking instruction reconfiguration of service-oriented architecture (SOA) Download PDF

Info

Publication number
TW201447782A
TW201447782A TW102120982A TW102120982A TW201447782A TW 201447782 A TW201447782 A TW 201447782A TW 102120982 A TW102120982 A TW 102120982A TW 102120982 A TW102120982 A TW 102120982A TW 201447782 A TW201447782 A TW 201447782A
Authority
TW
Taiwan
Prior art keywords
data
service
module
instruction
soa
Prior art date
Application number
TW102120982A
Other languages
Chinese (zh)
Other versions
TWI684154B (en
Inventor
De-Fang Xiao
Jian-Tong Shi
Original Assignee
Bai Xu Technology Co Ltd
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 Bai Xu Technology Co Ltd filed Critical Bai Xu Technology Co Ltd
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

Landscapes

  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

A real-time business intelligent system realized and designed by walking instruction reconfiguration of service-oriented architecture (SOA) comprises a walking instruction reconfiguration module composed of an instruction reconfiguration and analysis module, a first service definition file, a second service definition file and an inheritance module. Source syntax of obtaining data is acquired real-time based upon the instruction reconfigured by the walking instruction reconfiguration module. Required data is then obtained by the source syntax from many operational systems or data warehouses, and the service is taken as orientation to obtain analysis environment and computation having multi-dimensional data of the data warehouse. After the user end changes demand, real-time changed data can be instantly acquired regardless of different dimensions, different operational systems or many operational systems and data warehouses or homogeneous or heterogeneous databases. The heterogeneous data source can be designed and integrated by the architecture of combining the first service definition file with the second service definition file.

Description

以服務導向架構(SOA)之走動式指令重組的設計實現於即時商業智慧系統 The design of the walk-through instruction reorganization with Service Oriented Architecture (SOA) is realized in the real-time business intelligence system.

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

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

(1)資料匯整:使用ETL(Extract-Transform-Load)工具(參閱第二圖)將來源資料庫資料來源10萃取、轉換及載入11,匯入Operational data store資料庫;再經整理,累 積資料儲存12於資料倉儲(Data Warehouse)資料庫中。 (1) Data collection: 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; tired The accumulated data is stored in the data warehouse database.

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

(3)資料展現13:以報表工具產出報表或Web Portal等方式將資料分析結果呈現予使用者。 (3) Data presentation 13: Present the data analysis results to the user by means of a report tool output report or Web Portal.

而企業現今所面臨問題,是不是建置了好的BIS,就可以達成企業BI的夢想?之前BIS呼聲喊得震天價響,而企業投入了大量的成本、時間及人力等資源後,使用者從BIS所獲得的效益與預期認知上對資訊品質(Information Quality,IQ)及對系統的有用性(the use of Information)往往存在著很大的落差。到最後企業內部的員工九成還是使用Excel來進行資料的分析,而造成BI的成效不彰。本發明在使用者對資訊品質不佳的認知層面上大致歸納為下列兩點: And the problems faced by enterprises today, is it possible to achieve a dream of corporate BI by building a good BIS? Before the BIS voice shouted loudly, and the company invested a lot of resources, time and manpower resources, the benefits and expectations of users from BIS were useful for Information Quality (IQ) and the system. There is often a big gap in the use of information. At the end of the company, 90% of the employees in the company still use Excel to analyze the data, which makes the BI less effective. The invention is roughly summarized into the following two points on the cognitive level of the user's 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 operating environment of enterprises, in the fierce competitive environment, the data in data warehousing cannot provide timely and stable decision makers. Information, so even if there is a good BIS, it can't satisfy the enterprise. Industry needs. On the other hand, the development of data warehousing must be an extremely large and complex investment, which is not only risky, but also requires a large amount of resources to be invested in the enterprise. If there is no clear business case, it may be a Long-term "work in progress" or "project black hole", so many companies are hesitant based on investment costs and risk factors; Gartner Group in 2004 from a smart enterprise (Intelligent Enterprise According to the survey, 55% of corporate users questioned that the information provided by their data warehousing did not hit the target. Another shortcoming is that 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 and then develop again. The time spent is not awkward; there is a significant gap between the benefits and expectations that the company has invested in a lot of cost and time.

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

在2006年所提出BI 2.0賦予不同的思維則主張即時性但要實現BI 2.0概念確實存在諸多落差與障礙,以當前多數企業的BI應用現況來看,若與BI 2.0主要訴求逐一比對,將不難發現,其間落差可謂甚大,在此之中,究竟存在著哪些目前BI障礙?以下說明之: In 2006, BI 2.0 proposed different thinking and advocated immediacy. However, there are indeed many gaps and obstacles in implementing BI 2.0 concept. According to the current BI application status of most enterprises, if the main requirements of BI 2.0 are compared one by one, It is not difficult to find that the gap between them can be said to be very large. 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 the company only introduces BIS in order to use BI, it is easy to be obsessed with the extension of the evaluation tool. Whoever has a fast calculation speed, the final BIS can only improve the accuracy, timeliness and integration of information acquisition. It may not be able to go deep into the operational management needs of enterprises, and the company will only realize the reality and expectation after introducing BIS. There is a significant gap between the two, and the benefits are difficult to assess; and the data integration IT staff is time-consuming and laborious, and finally BIS is a report generator, such as the use value, the benefits are naturally not too high, and 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 difficult to achieve. Especially in the decision-making of immediacy, the premise is that the detailed data in the complex information system of the enterprise has to be sorted and calculated. Material delivery also wastes some time, and sometimes seemingly simple requirements such as "adding one field" can take several working days. Therefore, immediate appeals are undoubtedly a major obstacle for policy makers, because once the time horizon of data integration is prolonged, it means that business decisions are based on non-instantaneous data, which is difficult to respond to. Changes in the operating environment, not to mention the decision-makers' needs for analysis will change at any time in response to rapid changes in the market. When the current data (data warehousing) cannot meet its needs, it must rely on IT personnel to re-enter A lot of time (when the IT staff's professional literacy is insufficient, the time for issuing the decision is undoubtedly delayed), and 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)的方式。 Analytical data produced by the BI 2.0 environment must be embedded in different workflows. In the past, BIS was based on a specific application program interface (API), which was developed by IT staff through development of programs. Fei Zhouzhang took the analysis results. As for the new approach, the BIS analysis results can be easily obtained from any component in the workflow. The premise is to get rid of the IT staff to develop a separate API and change the service orientation. The way the architecture (SOA).

本發明的設計提供組織(企業)在管理及決策層面效益,以企業交易資訊系統(operational IS)為基礎導入以服務導向架構之智慧型“走動式指令重組”設計,克服了組織(企業)在沒有建立資料倉儲環境下即時地獲得『具有資 料倉儲的多維度資料的分析環境及運算(drilldown,rollup,slice或pivoting等)』實現即時性決策之訴求,並且已實際導入至企業內部的資訊系統(operational IS),驗證了使用者與資訊需要來源、BIS間達到即時的互動關係而具體的反應在資訊品質上的評估及對系統認知上有用性的程度,進而提高資訊的使用而大幅提高BIS成功;值得一提的是本發明所設計的SOA架構,透過服務間的再結合成為一個新的服務的創新設計架構,讓異質資料整合變得容易。 The design of the present invention provides an organization (enterprise) with benefits at the management and decision-making level, and introduces a smart "walking instruction reorganization" design based on the service-oriented architecture based on the enterprise transaction information system (operational IS), overcoming the organization (enterprise) Instantly obtained "with funding" in the absence of a data storage environment The analysis environment and calculation (drilldown, rollup, slice or pivoting, etc.) of multi-dimensional data storage realizes the demand for immediate decision-making, and has been actually imported into the internal information system (operational IS) to verify users and information. The need for source and BIS to achieve an immediate interaction relationship and the specific response in the evaluation of information quality and the degree of usefulness to the system, thereby improving the use of information and greatly improving the success of BIS; it is worth mentioning that the present invention is designed The SOA architecture, through the re-integration of services, becomes an innovative design architecture for new services, making 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 architecture proposed by the present invention can immediately verify the key factors of the aforementioned BIS success from the internal operation information system (operational IS), that is, factors such as data integration, information quality and information usage, and not After waiting for a lot of resources, time and manpower resources, it is found that there is a big 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, corrupted and ugly data can be revealed together with good data during the analysis process. The person will have the opportunity to assess what is broken and why, so that there is an opportunity to solve it. Therefore, from the perspective of the benefit structure of IT development BIS, it can be expected that the value of such a design structure can improve the correlation between the degree of understanding of the problem and the key factors of the user's cognition, and greatly reduce the investment of the company to introduce instant BIS. Resources and after meeting Continued changes in user needs, providing users with the analytical data needed to improve the use efficiency of BIS information, and allowing IT staff to save time in intervention data integration, and more focused on other business processes of the enterprise. IT is the biggest benefit.

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

(1)增加企業盈收,或提升企業競爭力。 (1) Increase the company's profit or increase the competitiveness of the company.

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

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

(4)降低開發服務的時間以達成即時需求。 (4) Reduce the time for development services to achieve immediate demand.

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

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

有關本發明所採用之技術、手段及其功效,茲舉一較佳實施例並配合圖式詳細說明於後,相信本發明上述之目的、構造及特徵,當可由之得一深入而具體的瞭解。 The above-mentioned objects, structures and features of the present invention will be described in detail with reference to the preferred embodiments of the present invention. .

[習知] [知知]

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

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

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

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

20‧‧‧交易系統 20‧‧‧ trading system

21‧‧‧擷取 21‧‧‧Select

22‧‧‧轉換 22‧‧‧Conversion

23‧‧‧載入 23‧‧‧Load

24‧‧‧資料倉儲 24‧‧‧Data warehousing

[本發明] [this invention]

30‧‧‧交易系統 30‧‧‧ trading system

31‧‧‧資料倉儲 31‧‧‧Data warehousing

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

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

411‧‧‧指令重組及剖析模組 411‧‧‧Instruction Reorganization and Profiling 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‧‧‧Data Set (DS)

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

44‧‧‧多重資料來源整合模組 44‧‧‧Multiple Data Source Integration 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 memory (cache)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

第十圖係本發明範例二執行結果:繼承範例一的定義,改 變維度屬性。 The tenth figure is the execution result of the second example of the present invention: inheriting the definition of the first example, Variable dimension attribute.

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

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

第十三圖係本發明範例二執行結果:部科樞鈕(pivot)分析資 The thirteenth figure is the result of the second example of the present invention: the pivotal analysis of the branch

第十四圖係本發明範例三執行結果:繼承範例一的定義,在eistable.def中產生新的定義。 The fourteenth figure is the result of the third example of the present invention: inheriting the definition of the first example, generating a new definition in the eistable.def.

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

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

第十七圖之一係本發明範例四:多重資料來源整合架構圖,其進行衡量值整合。 One of the seventeenth aspects is an example 4 of the present invention: a multi-data source integration architecture diagram for performing measurement integration.

第十七圖之二係本發明多重資料來源整合架構示意圖,其進行維度整合。 The seventeenth figure is a schematic diagram of the multiple data source integration architecture of the present invention, which performs dimensional integration.

第十八圖係本發明範例四執行結果:多重資料來源衡量值整合。 The eighteenth figure is the result of the fourth example of the present invention: the integration of multiple data sources.

第十九圖係本發明範例四執行結果:多重資料來源整合(下探維度為科室)。 The nineteenth figure is the result of the implementation of the fourth example of the present invention: the integration of multiple data sources (the dimension is the department).

第二十圖係本發明範例四執行結果:多重資料來源整合(下探至HR資料庫之醫師明細資料)。 The twentieth figure is the result of the fourth example of the present invention: integration of multiple data sources (investigating to the physician details of the HR database).

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

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

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

本發明係提供一種以服務導向架構(SOA)之走動式指令重組的設計實現於即時商業智慧系統之設計者。 The present invention provides a design for implementing a service-oriented architecture (SOA) walk-through instruction reorganization to implement a real-time 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 to enable the reviewing committee to have a better understanding and understanding of the purpose, features and functions of the present invention, the embodiments and the drawings are as follows: Referring to the third figure, the present invention provides a service-oriented architecture ( SOA)'s walk-through instruction reorganization is implemented in real-time business intelligence system, which includes: a service-oriented architecture (SOA) 40, a user terminal and an information technology (IT) staff, the service-oriented architecture. The (SOA) 40 includes a walk-through instruction reassembly module (ReSQL) 41. The walk-through instruction reassembly module (ReSQL) 41 includes an instruction reassembly and parsing module 411 and a first service definition file (eistable.def). 412. A second service definition file (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 Simplely defined by the information technology (IT) staff, data is taken from the operating system or data is taken from multiple operating systems or data is taken from multiple operating systems and data warehousing, which is based on the relocation module (ReSQL) The reorganized instruction obtains the obtained data source, and then obtains the required data from the data source. The service oriented architecture (SOA) 40 further includes a grammar conversion module 43 by which the grammar conversion module 43 can communicate Reorganizing and parsing the module 411 with the homogenous or heterogeneous database 48 of each operating system or data repository, so that all the data is automatically accessible, and the inheritance module 414 can modify the user end through the inheritance manner among the services. The demand and the re-integration through the service become a new service. The instruction reorganization and analysis module 411 is responsible for realizing the immediate demand service analysis by defining the service and setting the parameter input by the user terminal in the operation mode of the walk instruction reorganization. And service-oriented, when the user end needs change, the instruction reorganization and parsing module 411 provides strain elasticity to obtain a data warehouse. The analysis environment and operation of the multi-dimensional data, after the user-side transformation requirements, even if different dimensions, different operating systems or multiple operating systems and data warehousing or homogeneous or heterogeneous databases 48, the converted data can be immediately obtained. Sex, without having to write separate application-specific interfaces (APIs).

所述之以服務導向架構(SOA)40之走動式指令重組的設計實現於即時商業智慧系統,其中該指令重組及剖析模組411建構有完整的擷取指令,該指令重組及剖析模組411更具有重組後的指令最佳化,以縮短資料擷取的時間 。 The design of the walk-through instruction reorganization of the service-oriented architecture (SOA) 40 is implemented in an instant business intelligence system, wherein the instruction reorganization and parsing module 411 constructs a complete capture instruction, and the instruction reorganization and parsing module 411 More reorganized instruction optimization to shorten data acquisition time .

所述之以服務導向架構(SOA)之走動式指令重組的設計實現於即時商業智慧系統,其中該使用者端取用資料方式,包括下探(Drill-down)、上捲(Roll-up)、樞鈕分析(Pivot)或切片(Slice)。 The design of the walk-through instruction reorganization of the service-oriented architecture (SOA) is implemented in an instant business intelligence system, wherein the user accesses the data mode, including Drill-down and Roll-up. , pivot analysis (Pivot) or slice (Slice).

所述之以服務導向架構(SOA)之走動式指令重組的設計實現於即時商業智慧系統,其中該服務導向架構(SOA)40更包含有一多重資料來源整合模組44,該多重資料來源整合模組44連結該走動式指令重組模組(ReSQL)41、該語法轉換模組43及同質或異質資料庫48,以該多重資料來源整合模組44進行多重資料計算整合。 The service-oriented architecture (SOA) walk-through instruction reorganization is implemented in an instant business intelligence system, wherein the service-oriented architecture (SOA) 40 further includes a multiple data source integration module 44, and the multiple data source integration module The group 44 is connected to the walk-through instruction reassembly module (ReSQL) 41, the grammar conversion module 43 and the homogenous or heterogeneous database 48, and the multi-data source integration module 44 performs multi-data calculation and integration.

所述之以服務導向架構(SOA)之走動式指令重組的設計實現於即時商業智慧系統,其中該服務導向架構(SOA)40更包含有一資料集(DS,dataset)42及一快取記憶體(cache)49,該資料集42連結該走動式指令重組模組(ReSQL)41、該多重資料來源整合模組44、同質或異質資料庫48與該使用者端,指令重組後進至該資料集42,該資料集42由該快取記憶體(cache)49找不到資料時才會至指令對應的同質或異質資料庫48擷取資料。 The design of the service-oriented architecture (SOA) of the walk-through instruction reorganization is implemented in an instant 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 is linked to the walk-through instruction reassembly module (ReSQL) 41, the multiple data source integration module 44, the homogenous or heterogeneous database 48 and the user end, and the instructions are reorganized and then entered into the data set. 42. When the data set 42 cannot be found by the cache 49, the data will be retrieved from the homogenous or heterogeneous database 48 corresponding to the instruction.

所述之以服務導向架構(SOA)之走動式指令重組的設計實現於即時商業智慧系統,其中該服務導向架構(SOA)40更包括一維度整合模組45,該維度整合模組45連 結該資料集(DS,dataset)42與該使用者端,該維度整合模組45得整合衡量值與分析維度分散在不同資料庫之資料,以整合後的資料展示在該使用者端。 The design of the service-oriented architecture (SOA) of the walk-through instruction reorganization is implemented in an instant business intelligence system, wherein the service-oriented architecture (SOA) 40 further includes a one-dimensional integration module 45, and the dimension integration module 45 The data set (DS, dataset) 42 and the user end, the dimension integration module 45 integrates the data of the measurement value and the analysis dimension dispersed in different databases, and the integrated data is displayed on the user end.

所述之以服務導向架構(SOA)之走動式指令重組的設計實現於即時商業智慧系統,其中該服務導向架構(SOA)40更包括一過濾器47,該過濾器47連結該維度整合模組45與該使用者端,該過濾器47以該使用者端設定的條件,過濾掉該維度整合模組45整合後資料的多餘部分,再以過濾後的資料展示在該使用者端。 The design of the service-oriented architecture (SOA) of the walk-through instruction reorganization is implemented in an instant business intelligence system, wherein the service-oriented architecture (SOA) 40 further includes a filter 47, and the filter 47 is connected to the dimension integration module. And the user terminal, the filter 47 filters out the redundant portion of the integrated data of the dimension integration module 45 under the condition set by the user end, and displays the filtered data on the user end.

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

所述之以服務導向架構(SOA)之走動式指令重組的設計實現於即時商業智慧系統,其中該服務導向架構(SOA)40更包括一使用者介面輸出模組461,該使用者介面 輸出模組461連結該過濾器47、該使用者介面控制模組462及該使用者端,該使用者介面輸出模組461可輸出資料至該使用者端顯示器。 The design of the service-oriented architecture (SOA) of the walk-through instruction reorganization is implemented in an instant business intelligence system, wherein the service-oriented architecture (SOA) 40 further includes a user interface output module 461, the user interface. The output module 461 is coupled to 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)服務。其設計的架構歸納為三大層面: The Service Oriented Architecture (SOA) consists of different components that can be placed in different processes for different purposes to complete the on demand service. The architecture of its design is summarized into three levels:

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

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

(3)由於資料倉儲是匯整後的「歷史數據」,可預測未來趨勢與結果及快速提供決策者分析資料,或是企業內部已建置資料倉儲,基於企業在不同彈性需求因素下,走動式指令重組模組(ReSQL)可同步支援資料來源是來自於資料倉儲。另一方面,當資料來自於資料倉儲,決策者在分析的過程中同時又需要查看更詳細的即時資料(raw data或是某種程度匯整過的資料),然而這些資料並不存在於資料倉儲中,基於此,服務導向架構(SOA)支援可在瀏灠資料來自於資料倉儲的同時,即時串連至交易系統中呈現完整的明細資料。 (3) Since the data warehousing is the “historical data” after the reorganization, it can predict the future trends and results and provide the decision-makers with quick analysis data, or the data warehousing has been built within the enterprise, based on the enterprises' different elastic demand factors. The Redirection Module (ReSQL) can support data sources from data warehousing. On the other hand, when the data comes from data warehousing, the decision makers need to view more detailed real-time data (raw data or some degree of remitted data) in the process of analysis. However, the data does not exist in the data. In warehousing, based on this, Service Oriented Architecture (SOA) support can instantly and continuously connect to the trading system to present complete details while browsing data from 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 Service Oriented Architecture (SOA), software resources are encapsulated into services, and this service is modularized to provide standard business functions. In order to support shared business processes, services can be viewed as building a building block to communicate with other services to support shared business processes; services are a small part of the functionality in Service Oriented Architecture (SOA) With some important features, including services are autonomous, services hide underlying logic, services are loosely coupled (Services are loosely Coupled) and the complete service definition (Services are well defined). Service Oriented Architecture (SOA) provides a flexible architecture, modular application to service. In addition, Service Oriented Architecture (SOA) allows companies to create, deploy, and integrate multiple services. So in this way, Service Oriented Architecture (SOA) can provide the flexibility and agility of enterprise users, and defining services can be integrated and reused as key blocks to promote continuous and ever-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 elements of the combination usually include software components, services and processes. When decision makers face new demands, the process is responsible for defining the processing steps required by the decision maker; the service includes all the program components of a particular step, and the software component is responsible for the program that performs the work. The following describes 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 diagram is the Service Oriented Architecture (SOA) BIS architecture, in which the Remoting Instruction Reassembly Module (ReSQL) plays a key role in the real-time analysis environment in the Service Oriented Architecture (SOA), which is responsible for constructing the user requirements (services) definition. The multi-dimensional data environment and processing flow required to provide decision maker analysis services on the fly; undoubtedly, the instruction reorganization and profiling modules need to construct a complete capture instruction, and also need to optimize the reorganized instructions. In order to shorten the time taken for data acquisition; during the decision-makers, according to their analysis mode (or decision makers demand service), such as drilldown, rollup or pivot, etc. The service-oriented architecture (SOA) is designed to dynamically load data into a data set (DS, dataset) through the design of the Remoting Module (ReSQL) and the communication link to achieve immediate response to user needs and changes; Furthermore, the walk-through instruction reassembly module (ReSQL) can quickly solve the problems mentioned above when the analysis data is a combination of different data sources (homogeneous or heterogeneous databases).

服務導向架構(SOA)中的資料集(DS,dataset)資料載入是利用server的cache key-value設計概念,當指令重組後所得到的key不在快取記憶體(cache)中才會至營運系統資料庫擷取資料。 The data set (DS, dataset) data loading in the Service Oriented Architecture (SOA) is based on the server's cache key-value design concept. When the command is reorganized, the key obtained is not in the cache. The system database retrieves data.

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

以下本發明導入實際醫院內部operational IS發展主管資訊系統(EIS)為範例說明在服務導向架構(SOA)下,指令重組及剖析模組設計的架構及執行結果: The following is an introduction to the actual hospital internal operational IS development information system (EIS) as an example to illustrate the architecture and implementation results of the instruction reorganization and profiling 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 body (Data cube)

以下範例說明IT人員如何在第一服務定義檔定義使用者分析需求(服務)。表一是第一服務定義檔中服務的屬性、屬性設定值及代表的意義,而“住院日期”,“部科”,“科室”,…等分別是對應至維度屬性名稱及衡量屬性運算式。當服務定義完成設定,指令重組及剖析模組將藉由第一服務定義檔(國科範一)函數取得定義內容,結合使用者參數設定,重組資料運算擷取指令將資料載入至資料集(DS)中,如第五圖所示;隨後根據使用者分析需求提供多維度資料的分析環境,進行如下探(drilldown)或上捲(rollup)等運算時,指令重組及剖析模組便能辨識目前所在的維度動態的提供即時的分析資料,使得階層式的景觀變的容易,執行結果請參考第六圖至第八圖;甚至在不同的 維度中可檢視其該層較詳細資料或進行樞紐(pivoting)分析,執行結果請參考第九圖。由表一得知IT人員端只需了解企業內部資料庫架構及簡單的SQL指令用以簡單編寫第一服務定義檔便可結合本發明服務導向架構(SOA)快速建構出具有資料倉儲多維度資料的分析環境,提供決策者drilldown,rollup等分析運算。另外指令重組及剖析模組411所產生的指令(commands of ReSQL,COR)其結構請參閱圖(十)說明,圖中的COR是由resql()函數所包裝,而且根據使用者走動式的分析需求,COR會有多層(multi stage)的巢狀resql(nested resql)的組合,其主要的目的是建構多維度模型(multi-dimensional modeling)的分析環境。 The following example shows how an IT staff can define user analysis requirements (services) in the first service definition file. Table 1 is the attribute of the service in the first service definition file, the attribute setting value and the meaning of the representative, and the “hospital date”, “Ministry”, “Department”, etc. are corresponding to the dimension attribute name and the measurement attribute expression respectively. . When the service definition is completed, the instruction reorganization and parsing module will obtain the definition content by the first service definition file (National Fan Fan 1) function, and combine the user parameter setting, reorganize the data operation acquisition instruction to load the data into the data set. (DS), as shown in the fifth figure; then provide the multi-dimensional data analysis environment according to the user's analysis needs, and perform the following operations such as drilldown or rollup, the command reorganization and parsing module can Identify the current dimension of the dynamic and provide real-time analysis data, making the hierarchical landscape easy, please refer to the sixth to eighth diagrams for the results; even in different In the dimension, you can view the details of the layer or perform pivoting analysis. For the results, please refer to the figure IX. It can be seen from Table 1 that the IT staff only needs to understand the internal database structure and simple SQL instructions to simply write the first service definition file, and can quickly construct multi-dimensional data with data storage combined with the service oriented architecture (SOA) of the present invention. The analysis environment provides decision makers such as drilldown, rollup and other analytical operations. In addition, the instruction recombination and parsing module 411 generates a command (commands of ReSQL, COR) whose structure is described in the figure (10). The COR in the figure is packaged by the resql() function, and the user moves according to the analysis. Demand, COR has a multi-stage nested resql (nested resql) combination, the main purpose is to construct a multi-dimensional modeling analysis environment.

前面提到資料集(DS)中的資料載入是利用server的cache key-value設計概念,當指令重組後所得到的key不在快取記憶體中才至營運系統資料庫擷取資料。為了加速讀取時間第一服務定義檔會載入至快取記憶體(當第一服務定義檔有所修改會自動將快取記憶體中相關的key-values移除)。 The data loading in the data set (DS) mentioned above is based on the cache key-value design concept of the server. When the key obtained after the instruction reorganization is not in the cache memory, the data is retrieved 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 inheritance module design

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

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

(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) - Multiple data source integration: There are often different trading system operations in the business operation environment. These systems use different database management systems (DBMS) due to different construction time. Even the data naming, data representation, data encoding, data content, and data scaling on different systems are inconsistent. A BI solution must be seamlessly integrated with the enterprise's overall information environment. It is a difficult challenge to quickly integrate multiple data sources into a single, real-time analysis environment without the need to build data warehousing or physical data repository to provide decision makers with immediate analysis. The task; 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 present invention becomes a new service innovation design framework through the re-integration of services, which makes heterogeneous system integration easy, not only quickly solves the problem of heterogeneous data integration that enterprises often face, but also satisfies The dynamic process requirements of the enterprise support the innovation of the business model. Table 4 shows examples of hospitalization declarations The database (EIS1) and the personnel database (HR), EIS1 stores the transaction information of the hospitalized patients in the hospital every day, and each transaction records which doctor in the hospital is seen by the doctor and the required medication (MedFee) Part of the patient's burden (PortFee) and application fee (AppFee). The HR database stores information about each doctor's personnel data and grades. In order to analyze data related to medical expenses, BIS must be structured in a multi-dimensional model data storage environment, as shown in Table 5. The Data Mart C uses ETL (Extraction, Transformation, and Load) to obtain information from the EIS1 and HR databases, respectively, in order to reach a decision across all relevant medical analysis dimensions and based on existing and available operational data. Process. The doctor's dimension integrates the doctor's data sheet from the EIS1 and HR databases. Once multi-dimensional data warehousing is completed, OLTP tools are typically used to allow users to analyze data according to different dimensions. On the contrary, if the data storage is not established, it is assumed that the information of the doctors of the grade A (Chief Physician) in the past three years will be collected into a single analysis environment to provide the decision makers with immediate analysis data. Highly complex and challenging tasks.

本發明利用以下範例說明在沒有建置資料倉儲的基礎下,如何具有資料倉儲多維度資料的分析環境及運算,而快速達成多重資料來源整合。假設前述範例中的資料來源為EIS1資料庫(醫院申報資料庫),其中“醫療費用”是指該科醫生與病人之間有醫療行為而產生需申報至健保局的總費用(包括看診費、藥費、檢查費及儀器使用費等),基於主管的分析角度,“醫療費用”應該包含了該科所有介入的資源(包括該科的護士、行政人員或是有些未看診的醫生等資源),而主管欲了解其該科醫師總人數以便於分析收入與付出成本是否有落差,進一步下達某些決策;然而要取得該科醫師總人數並不能從EIS1單一資料庫獲得,還必須從另一個資料庫才能取得完整資料。以下將說明如何透過服務間的再結合成為一個新的服務以達成多重資料的整合:表六是本發明所設計第二服務定義檔提供處理多重資料整合的服務機制,其中“專科醫師”是指該服務的資料來源名稱經由資料來源內容設定後,也就是前述中該科所有醫生(假設包括該月有看診及未看診醫生)的人數,其資料來源是從HR資料庫;而在“專科醫師.setting”中 是指該資料來源屬性設定,如本範例中的資料來源是HR資料庫及若要下探至醫師的明細資料則在<RawSelect></RawSelect>標籤中指定(如ID_DOCTOR_NAME為醫師姓名);一旦IT人員完成設定後,便可結合第一服務定義檔中所定義的服務整合至單一資料集(DS)中即完成不同資料來源整合,如表七說明。本範例四的第一服務定義檔之資料定義是繼承範例三的定義,只需將“專科醫師”加入(“+”)至vcols中即可整合至資料集(DS)中,及後續可以與其他的衡量屬性作運算(如平均看診人數);隨後使用者在不同的維度中,指令重組及剖析模組根據目前所在的維度重組兩個不同資料來源的擷取指令以達成數值整合之目的,請參考第十七圖之一整合架構說明。另外前述所提到其醫生的等級分類的資料來自表四中HR資料庫,假設要將等級A的醫生在過去三年中八月份看診的資料彙整至單一個OLAP的分析環境,請參閱表八、表九的分類之整合定義說明,其整合架構圖請參考第十七圖之二;甚至不同年度的比較資料也能快速地整合至資料集(DS)中,請參考第十九至第二十一圖執行的結果。 The present invention utilizes the following examples to illustrate how to have multiple data sources integrated quickly by analyzing the environment and operations of data warehousing multi-dimensional data without building data warehousing. Assume that the source of the data in the above example is the EIS1 database (hospital declaration database), where “medical expenses” refers to the total cost of medical treatment required to be reported to the health insurance bureau (including medical expenses). , medical expenses, inspection fees and instrument usage fees, etc.), based on the supervisor's analytical perspective, “medical expenses” should include all the resources involved in the department (including nurses, administrative staff or some undiagnosed doctors in 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 the income and the cost of payment, and further to make certain decisions; however, to obtain the total number of physicians can not be obtained from the EIS1 single database, must also Another database can get complete information. The following will explain how to become a new service through the re-integration of services to achieve the integration of multiple data: Table 6 is the service mechanism designed by the second service definition file provided by the present invention to deal with multiple data integration, wherein "specialist" refers to The source name of the service is set by the source of the information, that is, the number of all the doctors in the department mentioned above (assuming that there are doctors who see and do not see the doctor in the month). The source of the information is from the HR database; Specialist.setting" Refers to the data source attribute setting. If the source of the data in this example is the HR database and the details to be traced to the physician, it is specified in the <RawSelect></RawSelect> tag (if ID_DOCTOR_NAME is the name of the physician); After the IT staff completes the settings, they can integrate the services defined in the first service definition file into a single data set (DS) to complete the integration of different data sources, as shown in Table 7. The data definition of the first service definition file in this example 4 is inherited from the definition of the third example, and only the "specialist" is added ("+") to the vcols to be integrated into the data set (DS), and the subsequent can be Other measurement attributes are calculated (such as the average number of visits); then, in different dimensions, the user reorganizes and parses the module to reorganize the capture instructions of two different sources based on the current dimension to achieve numerical integration. Please refer to the integrated architecture description in Figure 17. In addition, the above-mentioned information on the classification of the doctors is from the HR database in Table 4. It is assumed that the data of the doctors of the grade A in the past three years will be collected into the analysis environment of a single OLAP, please refer to the table. 8. The definition of the integration of the classification of Table IX, 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 nineteenth to the The results of the twenty-first figure execution.

另外如何有效的解決前述中提到資料整合所面臨的問題如屬性命名、資料表示法等不一致的問題。本發明以屬性命名不一致為例說明解決的方法。倘若在第十八圖中多重資料來源之間的key(維度)的屬性名稱或資料表示 法不一致;例如,假設在第一服務定義檔所定義的資料來源key的屬性名稱為xyz,xyz1,…,而第二服務定義檔所定義的資料來源key的屬性名稱為abc,abc1…,本發明設計的方式則在第二服務定義檔中定義屬性的mapping,即可達成一致。請參閱表十的設定;若是資料表示法(資料型態)上的衝突,可搭配使用資料庫管理系統所提供的函數(如convert,substring,…)或自定函數(如:t0_char,:substr,…),如表十中xyz=:to_char(abc),轉換成一致的資料型態。 In addition, how to effectively solve the problems mentioned in the aforementioned data integration such as attribute naming, data representation and other inconsistencies. The invention describes the solution method by taking the attribute naming inconsistency as an example. If the attribute name or data representation of the key (dimension) between multiple sources in Figure 18 The method is inconsistent; for example, assume that the attribute name of the data source key defined in the first service definition file is xyz, xyz1, ..., and the attribute name of the data source key defined by the second service definition file is abc, abc1, ... The way of designing the invention is to define the mapping of the attributes in the second service definition file, and the agreement can be reached. 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: t0_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 is to illustrate the combination of the second service definition file and the first service definition file service to solve the problem of different types of multiple data integration. Suppose the decision maker needs an analysis data, which needs to be aggregated from two different databases according to different down-search dimensions (may add up, average other operations), and some field values in different data tables (fields) The names are not necessarily consistent. As long as Table 6 defines two data sources (assuming DS1 and DS2) in the second service definition file, then DS1 and DS2 are added to vcols in the first service definition file (as shown in Table 7). The "specialist"), then use the compute (such as the "average number of visits" in Table 7) to achieve integration.

綜觀上述第二服務定義檔設計目的除了快速整合資料來源分別是從不同的資料庫,在某些情況需要較複雜的運算,只要在第二服務定義檔中定義再與第一服務定義檔結合而達到整合的目的,請參考表十一我們再更深入地探討此創新的設計架構,如表六中所定義的“專科醫師 ”,實際上它所代表的是一個物件的設計觀念,而這個物件可以在第一服務定義檔中任何一個服務定義的流程中被使用(只要該服務流程與物件間是可以連結),透過傳訊的連結達到整合及物件重用性目的,也呼應了前面所敘述服務間可以再結合成為一個新的服務。 In view of the above-mentioned second service definition file design purposes, in addition to the rapid integration of data sources from different databases, in some cases, more complex operations are required, as long as they are defined in the second service definition file and then combined with the first service definition file. To achieve the purpose of integration, please refer to Table 11 for a more in-depth discussion of this innovative design architecture, as defined in Table 6 "Specialist "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 are connectable), through the communication The link achieves integration and object reusability, and it also echoes the previously described services that can be combined into a new service.

由上述說明第二服務定義檔與第一服務定義檔服務定義間的結合快速完成使用者不同的服務需求,並且解決較複雜問題及快速達到多重資料來源整合。另外值得一提的是,架構在走動式指令重組模組(ReSQL)之基礎上,可以容易地擴展不同的服務流程之定義,完成不同的服務功能,也說明走動式指令重組模組(ReSQL)嚴謹的架構設計、完整的結合性及高度的凝聚力。 The combination of the second service definition file and the first service definition file service definition described above quickly accomplishes different service requirements of the user, and solves more complicated problems and quickly achieves multiple data source integration. It is also worth mentioning that the architecture can easily extend the definition of different service processes, complete different service functions, and also describe the walk-through instruction reassembly module (ReSQL) based on the Remoting Instruction Reassembly Module (ReSQL). Rigorous architectural design, complete integration and high cohesion.

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

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

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

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

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

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

411‧‧‧指令重組及剖析模組 411‧‧‧Instruction Reorganization and Profiling 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‧‧‧Data Set (DS)

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

44‧‧‧多重資料來源整合模組 44‧‧‧Multiple Data Source Integration 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 memory (cache)

Claims (9)

一種以服務導向架構(SOA)之走動式指令重組的設計實現於即時商業智慧系統,包括:一服務導向架構(SOA)、一使用者端及一資訊科技(Information Technology,IT)人員端,該服務導向架構(SOA)包括一走動式指令重組模組(ReSQL),該走動式指令重組模組(ReSQL)包括由一指令重組及剖析模組、一第一服務定義檔(eistable.def)、一第二服務定義檔(valueSQL.def)及一繼承模組組成,該第一服務定義檔(eistable.def)及該第二服務定義檔(valueSQL.def)由該資訊科技(IT)人員端簡單定義,資料取自營運系統或資料取自多個營運系統或資料取自多個營運系統及資料倉儲,其係即時依該走動式指令重組模組(ReSQL)重組後的指令獲得取得之資料來源,再由資料來源取得所需資料,該服務導向架構(SOA)更包含一語法轉換模組,藉由該語法轉換模組得以溝通該指令重組及剖析模組與各個營運系統或資料倉儲之同質或異質的資料庫,使所有資料之自動取得無障礙,該繼承模組可在各服務間透過繼承的方式修改該使用者端的需求及透過服務間的再結合成為一個新的服務完成多重資料來源整合,該指令重組及剖析模組負責將服務的定義及使用者端輸入的參數設定以走動式指令重組的運算模式完成即時的需求服務分析,並以服務為導向,當該使用者端需求改變,該指令重組及剖 析模組提供應變的彈性,以之獲得具有資料倉儲的多維度資料的分析環境及運算,該使用者端變換需求後,就算不同維度、不同營運系統或多個營運系統及資料倉儲或同質或異質資料庫,亦可立即獲得變換後資料的即時性,且不用各別寫獨立的特定應用程式介面(API)。 A service-oriented architecture (SOA) walk-through instruction reorganization is implemented in an instant business intelligence system, including: a service-oriented architecture (SOA), a client, and an information technology (IT) staff. The Service Oriented Architecture (SOA) includes a walk-through instruction reassembly module (ReSQL), and the walk-through instruction reassembly module (ReSQL) includes an instruction reassembly and parsing module, a first service definition file (eistable.def), a second service definition file (valueSQL.def) and an inheritance module, the first service definition file (eistable.def) and the second service definition file (valueSQL.def) are used by the information technology (IT) personnel Simple definition, data taken from the operating system or data taken from multiple operating systems or data taken from multiple operating systems and data warehousing, which are obtained immediately from the reorganized instructions of the Remoting Reassembly Module (ReSQL) Source, and then obtain the required information from the source. The Service Oriented Architecture (SOA) further includes a grammar conversion module through which the grammar conversion module can communicate the reorganization and analysis of the module and the various operating systems or materials. The storage of a homogenous or heterogeneous database enables all data to be automatically accessible. The inheritance module can modify the needs of the client through inheritance in each service and become a new service through the re-integration of the services. The integration of multiple data sources, the instruction reorganization and analysis module is responsible for the definition of the service and the parameter input of the user input to complete the real-time demand service analysis in the operation mode of the walk-through instruction reorganization, and the service-oriented, when the user End demand changes, the order is reorganized and cut The analysis module provides the flexibility of strain to obtain the analysis environment and calculation of multi-dimensional data with data storage. After the user transforms the requirements, even different dimensions, different operating systems or multiple operating systems and data storage or homogeneity or The heterogeneous database can also immediately obtain the immediacy of the transformed data without having to write separate application-specific interfaces (APIs). 如申請專利範圍第1項所述之以服務導向架構(SOA)之走動式指令重組的設計實現於即時商業智慧系統,其中該指令重組及剖析模組建構有完整的擷取指令,該指令重組及剖析模組更具有重組後的指令最佳化,以縮短資料擷取的時間。 The design of the service-oriented architecture (SOA) walk-through instruction reorganization described in the first application of the patent scope is implemented in an instant business intelligence system, wherein the instruction reorganization and profiling module constructs a complete capture instruction, and the instruction reorganization And the profiling module has more reorganized instruction optimization to shorten the data acquisition time. 如申請專利範圍第1項所述之以服務導向架構(SOA)之走動式指令重組的設計實現於即時商業智慧系統,其中該使用者端取用資料方式,包括下探(Drill-down)、上捲(Roll-up)、樞鈕分析(Pivot)或切片(Slice)。 The design of the walk-through instruction reorganization of the service-oriented architecture (SOA) as described in the first application of the patent scope is implemented in an instant business intelligence system, wherein the user access data method, including Drill-down, Roll-up, Pivot, or Slice. 如申請專利範圍第1項所述之以服務導向架構(SOA)之走動式指令重組的設計實現於即時商業智慧系統,其中該服務導向架構(SOA)更包含有一多重資料來源整合模組,該多重資料來源整合模組連結該走動式指令重組模組(ReSQL)、該語法轉換模組及同質或異質資料庫,以該多重資料來源整合模組進行多重資料計算整合。 The design of the service-oriented architecture (SOA) mobile command reorganization as described in claim 1 is implemented in an instant business intelligence system, wherein the service-oriented architecture (SOA) further includes a multiple data source integration module. The multiple data source integration module connects the walk-through instruction reassembly module (ReSQL), the grammar conversion module, and the homogenous or heterogeneous database, and uses the multiple data source integration module to perform multiple data calculation and integration. 如申請專利範圍第4項所述之以服務導向架構(SOA)之走動式指令重組的設計實現於即時商業智慧系統 ,其中該服務導向架構(SOA)更包含有一資料集(DS,dataset)及一快取記憶體(cache),該資料集連結該走動式指令重組模組(ReSQL)、該多重資料來源整合模組、同質或異質資料庫與該使用者端,指令重組後進至該資料集,該資料集由該快取記憶體(cache)找不到資料時才會至指令對應的資料庫擷取資料。 The design of the walk-through instruction reorganization of Service Oriented Architecture (SOA) as described in item 4 of the patent application scope is realized in the real-time business intelligence system. The service oriented architecture (SOA) further includes a data set (DS, dataset) and a cache memory (cache), the data set is linked to the walk-through instruction reassembly module (ReSQL), and the multiple data source integration module The group, the homogeneous or heterogeneous database and the user end, the instruction is reorganized and then entered into the data set, and the data set is not found by the cache memory (cache) until the data corresponding to the instruction is retrieved. 如申請專利範圍第5項所述之以服務導向架構(SOA)之走動式指令重組的設計實現於即時商業智慧系統,其中該服務導向架構(SOA)更包括一維度整合模組,該維度整合模組連結該資料集(DS,dataset)與該使用者端,該維度整合模組得整合衡量值與分析維度分散在不同資料庫之資料,再以整合後的資料展示在該使用者端。 The design of the service-oriented architecture (SOA) walk-through instruction reorganization described in item 5 of the patent application is implemented in an instant business intelligence system, wherein the service-oriented architecture (SOA) further includes a one-dimensional integration module, and the dimension integration The module connects the data set (DS, dataset) and the user end, and the dimension integration module integrates the data of the measurement value and the analysis dimension dispersed in different databases, and then displays the integrated data on the user end. 如申請專利範圍第6項所述之以服務導向架構(SOA)之走動式指令重組的設計實現於即時商業智慧系統,其中該服務導向架構(SOA)更包括一過濾器,該過濾器連結該維度整合模組與該使用者端,該過濾器以該使用者端設定的條件,過濾掉該維度整合模組整合後資料的多餘部分,再以過濾後的資料展示在該使用者端。 The design of the walk-through instruction reorganization of the service-oriented architecture (SOA) as described in claim 6 is implemented in an instant business intelligence system, wherein the service-oriented architecture (SOA) further includes a filter that links the The dimension integration module and the user end, the filter filters out the redundant portion of the integrated data of the dimension integration module by using the condition set by the user terminal, and displays the filtered data on the user end. 如申請專利範圍第7項所述之以服務導向架構(SOA)之走動式指令重組的設計實現於即時商業智慧系統,其中該服務導向架構(SOA)更包括一使用者介面控制模組,該使用者介面控制模組連結該使用者端、該IT人員端、 該走動式指令重組模組(ReSQL)、該資料集及該過濾器,該使用者介面控制模組接受該使用者端控制輸入,並將輸入訊號送至相關該IT人員端、該走動式指令重組模組(ReSQL)、該資料集及該過濾器,或接收該IT人員端、該走動式指令重組模組(ReSQL)、該資料集及該過濾器訊號控制往該使用者端之輸出。 The design of the walk-through instruction reorganization of the service-oriented architecture (SOA) as described in claim 7 is implemented in an instant business intelligence system, wherein the service-oriented architecture (SOA) further includes a user interface control module. The user interface control module connects the user end, the IT staff, The walk-through instruction reassembly module (ReSQL), the data set and the filter, the user interface control module accepts the user-side control input, and sends the input signal to the relevant IT personnel, the walking instruction Reorganizing the module (ReSQL), the data set and the filter, or receiving the IT personnel, the walking command reassembly module (ReSQL), the data set, and the filter signal to control the output of the user end. 如申請專利範圍第8項所述之以服務導向架構(SOA)之走動式指令重組的設計實現於即時商業智慧系統,其中該服務導向架構(SOA)更包括一使用者介面輸出模組,該使用者介面輸出模組連結該過濾器、該使用者介面控制模組及該使用者端,該使用者介面輸出模組可輸出資料至該使用者端顯示器。 The design of the service-oriented architecture (SOA) mobile command reorganization as described in claim 8 is implemented in an instant business intelligence system, wherein the service-oriented architecture (SOA) further includes a user interface output module. The user interface output module connects the filter, the user interface control module and the user end, and the user interface output module can output data to the user terminal display.
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 true TW201447782A (en) 2014-12-16
TWI684154B 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)

Family Cites Families (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

Also Published As

Publication number Publication date
TWI684154B (en) 2020-02-01

Similar Documents

Publication Publication Date Title
US11086751B2 (en) Intelligent metadata management and data lineage tracing
Berthold et al. An architecture for ad-hoc and collaborative business intelligence
US11847040B2 (en) Systems and methods for detecting data alteration from source to target
US20120310875A1 (en) Method and system of generating a data lineage repository with lineage visibility, snapshot comparison and version control in a cloud-computing platform
US20110295791A1 (en) System and method for specifying metadata extension input for extending data warehouse
US20130179229A1 (en) Analyzing business data for planning applications
US20110087708A1 (en) Business object based operational reporting and analysis
US20060095413A1 (en) Method of exposing normalized data as denormalized tables
CA2511196A1 (en) System and method for embedding business data in forms
US20150293947A1 (en) Validating relationships between entities in a data model
US20120005151A1 (en) Methods and systems of content development for a data warehouse
US20090228485A1 (en) Navigation across datasets from multiple data sources based on a common reference dimension
US20210103862A1 (en) Methods and apparatus for exposing workflow process definitions as business objects
CN101710280A (en) Packaging method and devices of BI product members
US10468126B1 (en) Clinical activity network generation
US20160191431A1 (en) Streamlining end-to-end flow of business-to-business integration processes
El Beggar et al. DAREF: MDA framework for modelling data warehouse requirements and deducing the multidimensional schema
TWM487489U (en) Walking-around type instructions reorganization design with service oriented architecture (SOA) to implement real-time business intelligence system
CN112862581A (en) Refined cost management system based on industry and finance integration in hospital in DRG payment mode
CN105528360B (en) Design of walking type command recombination with service oriented architecture is realized in real-time business intelligent system
Longo et al. Fact–Centered ETL: A proposal for speeding business analytics up
US10409793B2 (en) Secure and flexible inter-program communication
Su et al. Business intelligence revisited
TW201447782A (en) Real-time business intelligent system realized and designed by walking instruction reconfiguration of service-oriented architecture (SOA)
KR20160093289A (en) Method for managing property and system using the same