ebXML Framework Core Component 介紹.ppt

The Goal ebXML Business Operational View ebXML Functional Service View Business Collaboration Architecture Conceptual Overview 92年空運制訂六項訊息流程 倉租/倉租明細差異說明 對帳單/同行帳單差異說明 92年海運制訂訊息流程 配櫃指示 貨物裝載明細差異說明 融資作業全流程 ebXML與傳統EDI作業方式之比較 為什麼需要ebXML? 全球統一的命名原則 沒有使用核心元件的標準應用說明(1) 沒有使用核心元件的標準應用說明(2) 使用核心元件的好處與差異性 eAC CCTG Task Group Reports Submissions from Four Regions Chinese Taipei (GCOM) Logistics (475 entries) Hong Kong (HKANA) Fast moving consumer goods (99 entries) Japan (ECOM) Tendering (224 entries) Steel (460 entries) Korea (KIEC) Horizontal (1311 entries) Some Commonly Defined CCs/BIEs Address/Location Contact/Communication Document/Message Goods Item/Invoice Item Hazard Party/Organization/Person Period Price Summary Different sets of CCs/BIEs For different industries From different regions Different dictionary entry names and definitions E.g. Trading Party v.s. Organization, Communication vs Contact Different data models E.g. Different CCs in Address Challenges in harmonization eAC CCTG Harmonization Rule Prior harmonization scope : ACC, BCC, DT TBG17 makes above rule for declaration of business neutral core component in advance. eAC extends to harmonize BIEs after CCs are confirmed by UN . BCC should be defined clear semantic block. If needed, it could attach its code list. TBG 17 controls the supplement component as code list. 3. All terms candidated in eAC lists should be checked their semantic overlapping. If necessary, eAC uses the controlled vocabulary of TBG 17. eAC CCTGHarmonization Rule Quality assessment: First, Bottom up approach : clean-up Spread sheet And then, Top down approach should be executed. TBG17 recommends above approach. . 5. Refined eAC library is submitted to TBG17 and strongly shared among Asia region. Good harmonious relationship. 6. This rule could be modified in future. TBG 17 also defined above rule. 核心元件實現標準發展的水平整合 核心元件 儲存庫 核心元件標準技術規格文件範例(1) CC/BIE Spread Sheet Template(2)