180 likes | 452 Views
UN/CEFACT TMG Report. Chair: Gunther Stuhec Vice Chair: Christian Huemer. TMG Mandate. Purpose
E N D
UN/CEFACT TMG Report Chair: Gunther Stuhec Vice Chair: Christian Huemer TMG Report to the Plenary
TMG Mandate • Purpose • The purpose of the Techniques & Methodologies Group (TMG) is to provide all UN/CEFACT Groups with Meta (base) Business Process, Information and Communications Technology specifications, methodologies, recommendations and education. • The TMG shall also function as a research group evaluating new information and communication technologies (ICT), as well as, techniques and methodologies that may assist UN/CEFACT and its groups to fulfill their mandate and vision in Trade Facilitation and e-Business. TMG Report to the Plenary
Why TMG? • Provides the required key methodologies that are necessary for • Highly dynamic and context driven next generation B2B • Common and unambiguous understanding on semantic level • Collaborative business processes that considers the aspects of contracts / agreements • Highly reusable and flexible building blocks of business information • These methodologies are • comparable with a natural language • a must for doing collaborative business effectively, • the key differentiatior to all other existing business standards • highly required to realize next generation eBusiness environment (ESOA) • The TMG has experience since more than 10 years • Understands the current problematic in detail • Have concepts and solutions • Significant value add for UN/CEFACT • Enables UN/CEFACT to drive future B2B TMG Report to the Plenary
General Infos • Members • ~ 35 Active Members • 200 Mailing list registrants who participate electronically • Meetings • Convened during the UN/CEFACT Forum meetings in New Delhi and Dublin. • Face-to-face meetings • June 2006 at SWIFT headquarters in Brussels • December 2006 at Oracle in Redwood City, California • Next in July 2007 in Kansas City TMG Report to the Plenary
Working Groups • Business Process Working Group (BPWG) • Provides techniques and methodologies for the description of inter-organizational business processes and the resulting information exchanges • ~ 15 Active Members (5 also in CCWG and 3 in eBAWG) • http://www.untmg.org/index.php?option=com_content&task=view&id=26&Itemid=53 TMG Report to the Plenary
Core Components Working Group (CCWG) • Provides required techniques and methodologies for the development and reuse of business information • ~ 20 Active Members (5 also in BPWG and 7 in eBAWG) • http://www.untmg.org/index.php?option=com_content&task=view&id=25&Itemid=55 TMG Report to the Plenary
eBusiness Architecture Working Group (EBAWG) • Provides the framework for the different modeling and infrastructure concepts • ~ 10 Active Members (3 also in BPWG and 7 in CCWG) • http://www.untmg.org/index.php?option=com_content&task=view&id=28&Itemid=54 TMG Report to the Plenary
Contract Scope of BPWG How to formalize contract paragraphs? What are the agreed process steps? What are the core process steps that considers the smallest legal aspects? How must the economic events linked together that they are fulfill the contract? TMG Report to the Plenary
BPWG Projects • UN/CEFACT Modeling Methodology (UMM) • First technical specification was released in December 2006 • A new project for the next version was started in March 2007 • New UMM concepts will be based on UML 2.0 profiles • Resources-Events-Agents Economic Ontology (REA) Specialization Module • REA describes an enterprise ontology, which explains the types of entities or classes that are expected to see in a specific business process • Approved requirements specification (ODP Step 2) TMG Report to the Plenary
BPWG Projects • UML Profile for Core Components (UPCC) • Was formerly Business Collaboration Specification Schema (BCSS) • Transferred to Core Components Working Group (CCWG) • At ODP step 6, Implementation Verification • Supports both UML versions 1.4 and 2.0 • Business Process Schema Specification (BPSS) • The OASIS’ BPSS version 2.4 will be submitted to ISO’s TC 154 for approval • TMG recommends supporting this submission of OASIS BPSS to ISO • If OASIS starts next version, TMG will provide business process experts for reaching the consistency between BPSS and UMM • Unified Business Agreements and Contracts (UBAC) • No resources and time to proceed • TMG transferred UBAC to Legal Group (LG) • TMG will assist the LG TMG Report to the Plenary
Is „Work Address“ necessary in all industries? Which „Postal Code. IDs“ are required in Germany? Person. Address. Person. Address. Person. Identification. IDFirst. NameLast. NameWork. AddressHome. Address Identification. IDFirst. NameLast. NameWork. AddressHome. Address Identification. IDFirst. NameLast. NameWork. AddressHome. Address House Number. TextStreet. NamePostal Code. IDCountry. Code House Number. TextStreet. NamePostal Code. IDCountry. Code Scope of CCWG How to associate? How to structure? How to name? How to structure a message? How to assemble data types in a message? TMG Report to the Plenary
CCWG Projects • Core Components Technical Specification (CCTS) • Progressed CCTS V3.0 to second public review in ODP Step 5 • Removes ambiguities, strengthens reuse, modularizes standards stack (i.e. removal of registry rules) • Fixed content (data types, CCTS V3.0 does not consider any content anymore. • All CCTs (Core Components Types) in CCTS V2.01 are moved to ATG (Applied Technologies Group) • Target is to reach ODP7 – approved technical specification by end of 2007 TMG Report to the Plenary
CCWG Projects • Core Component Message Assembly (CCMA) • Began with ODP step 3 • An initial draft is underway • CCMA specification will bridge the current gap between UMM and CCTS • Meta model allows an easy and consistent mapping into technical protocols such as WSDL (Web Services Definition Language) • Unified Context Methodology (UCM) • Expanded ODP 2 phase • This was required at the request of many major contributors • Significant interest is being realized in this project TMG Report to the Plenary
Business Partner BusinessPartner Person. Identification.IDFirst. NameLast. NameWork. AddressHome. Address Traditional EDI ebXML Framework Business Web Services SOA, POA,… EBAWG Scope Business Context UCM Motivation (why), Organization(who) UMM Collaborative (external) Business Process (how, when) UMM Business Information (what) Business Message Assembly (what) Internal Process Internal Process CCTS CCMA UMM CCTS & CCMA UML/XMI- Presentation BCSS UPCC Translation Mapping XMI XMLNDR XMI BPSS XMI BPEL XMI EDIFACT Physical Representation XMLNDR BPSS WS-BPEL EDIFACT UNeDocs TMG Report to the Plenary Frameworks
EBAWG Projects • Electronic Business Architecture Specification (EBAS) • EBAS will describe the relationships between all defined UN/CEFACT technical specifications, and non UN/CEFACT specifications • Finalized project proposal • The goal for 2007 is complete ODP Step 3 • Conformance and Compliance Definition (COD) • Develop a clear and unambiguous definition of compliance/conformance rules for each of the UN/CEFACT specifications • Newly established in March 2007 • Phased at direction of FMG • The goal for 2007 is complete phase 1 and commence phase 2 • Glossary project • Create a centralized, common UN/CEFACT Glossary • Ongoing project that will interface with all other methodology projects in the forum • First draft available at the TMG website TMG Report to the Plenary
New Website(Prototype) • Enterprise Wiki approach • Every registered user can • read, update and generate wepages • write news and submit comments • upload/download attachments • Makes the daily standardization work more efficient and effective • Guarantees a consistent and clear representation of required information • Should be used for all UN/CEFACT standardization work Online Template / Edit Mode Presentation Mode TMG Report to the Plenary
Requirements • Server of new TMG website • Administrator of TMG website • Somebody who helps us on marketing • Better control on mailing lists • Formal invitations for prospective members TMG Report to the Plenary
We need Members • We’re not finished • We have the concepts and ideas, but members are still required to • Finalize the whole stack • Distribute our methodologies • Do trainings TMG Report to the Plenary