Committee Chair Members

Mr.Supachok Jantarapatin

Chairman of Business Domain Committee

+66 0 2123 1234


Business Domain Committee (BDC) Charter

1Committee Name
The name of the Committee shall be designated as “AFACT Business Domain Committee”.
2Committee Membership
The Business Domain Committee shall comprise of a Chair, Vice-Chair and Secretary at minimum; and preferably each of these persons holding office are actual trade practitioners or generally well-versed in the area of international trade transactions (ITT) and are familiar with ITT terminology as documented by UN/CEFACT.
3Language
The English language shall prevail as the lingua franca of this Committee and any documents or communications produced by this Committee shall also be in English.
4Duration of Charter
The expiration date of this charter is 31 December 2009.
5Purpose
The purpose of the AFACT Business Domain Committee is to ascertain: a) the continuance of existing specialized and focused AFACT Working Groups based on their existing Terms of Reference; b) the ratification of transitioned specialized and focused AFACT Working Groups; and c) the endorsement of new specialized and focused AFACT Working Groups Decision-taking on dissolution of existing specialized and focused) AFACT Working Groups without work programmes and work plans shall also be within the ambit of this Committee.
6Scope
At every Plenary, AFACT Working Groups are expected to meet (with stipulated minimum participation) and to recommend work programmes and work plans for a forthcoming 3 years. The Business Domain Committee shall then assess the work programmes and plans submitted by the AFACT Working Group to ensure these shall be executed in accordance with the stipulated Terms of Reference. The Committee shall also ensure that there is no duplication of work programmes or work plans amongst AFACT Working Groups. In addition to the above, the Business Domain Committee may also make recommendations for Joint Working Group work programmes and work plans to be the path forward, so that productivity and resources amongst AFACT Working Groups are always optimized.
7Deliverables
The deliverables of the Business Domain Committee recommendations to the AFACT Steering Committee: 1. Confirmation of AFACT Working Groups (new, transitioned and dissolved) 2. Confirmation of AFACT Working Groups/Joint Working Groups work programmes and work plans that have not been executed
8Committee participation
Effective participation is expected to consume at least one day per calendar quarter via teleconferencing To be successful, it is expected that the Committee to have the minimum 3 persons throughout the duration of the Charter. It is also expected that the Steering Committee Members will participate in the mailing list discussions.
9Meetings
The Business Domain Committee also expects to hold one or two face-to-face meetings.
10Communication
The Business Domain Committee will utilize a Member mailing list. The “public” mailing list, with its wider audience at the Steering Committee level, exists to promote openness and is the preferred channel of communication.
11Confidentiality
The proceedings of this Committee Group are public to the AFACT Steering Committee at all times, without any exceptions.

Dr. Eva Yi-Yuan Yueh

Chairman of Community Support Committee

+886-2-6607-2103


Community Support Committee (CSC) Charter

1Committee Name
The name of the Committee is designated as “Community Support Committee (hereinafter referred to as the CSC).”
2Committee Membership
The CSC shall elect a chair and optionally vice-chair(s) and/or secretary, depending on the committee requirements and resources.
3Duration of Charter
The normal duration of this Charter is 2 years. The Charter should be revisited by the CSC for re-adoption or amendment upon its expiration date. The CSC may amend the Charter anytime if deemed necessary.
4Purpose
The purpose of the AFACT CSC is to provide necessary support to AFACT community, in consultation with the Steering Committee, on capacity-building, awareness, and promotion of standards and specifications developed by UN/CEFACT, and guidelines developed by TMC or BDC in the areas of electronic business and trade facilitation
5Scope
The functions of CSC are: a. To be the driver for awareness and promotional activities to the AFACT community, and to serve as a focal point of AFACT for the promotion of Trade Facilitation and Electronic Business. b. To work with the AFACT Secretariat to develop the capacity building programs such as training, seminar, workshop, road-show, etc, if deemed necessary. c. To assist the AFACT Secretariat in enriching AFACT information resources on the AFACT website. d. To assist in the publication of the AFACT Year Book by the AFACT Secretariat. e. To assist in maintaining the contents of the eASIA Award Manual by the request from eASIA Award hosting member.
6Deliverables
The deliverables of the CSC recommendations to the AFACT Steering Committee are: 1. Training Roadshows, in consultation with the Steering Committee, in AFACT member countries or economies who express interest, with necessary funding available; 2. Results analyzed from collected survey forms when conducting a survey in support of TMC or BDC. 3. Other deliverables based on the need specified by the joint meeting with TMC or BDC.
7Committee participation
For effective participation, if deemed necessary, the CSC could meet once every half year, preferably by teleconferencing. The CSC can come into existence only if at least three member countries/economies submit written interest of participation to the Steering Committee and express desire to continue throughout the duration of this Charter.
8Meetings
The CSC will hold at least one face-to-face meeting and several virtual conferencing sessions separately or jointly with TMC or BDC.
9Communication
The CSC will use its member’s mailing list. The “public” mailing list, with a possible wider audience at the Steering Committee level, exists to promote openness and is the preferred channel of communication
10Confidentiality
The proceedings of the CSC are public to the AFACT community at all times, without any exceptions.

Mr. Hisanao Sugamata

Chairman of Technology and Methodology Committee

+81-3-5805-0107


Technology & Methodology Committee (TMC) Charter

1Committee Name
Technology and Methodology Committee (hereinafter referred to as “TMC”)
2Purpose
TMC is to promote the implementation of eBusiness Technologies and Methodologies based on eBusiness standards for facilitating e-Business / e-Trade in Asia Pacific Region, in order to enable a global electronic marketplace where enterprises of any size and in any geographical location can meet and conduct business with each other. TMC contributes the global business standardization activities of UN/CEFACT, OASIS and other international organizations for standardization and trade facilitation through harmonization and interoperability in e-Business / e-Trade.
3 Work Scope
TMC will handle the issues of interoperability, productivity (reusability, openness), using Technology and Methodology in e-Business / e-Trade. The scope of work subject may include as follows: - Reference framework (Technology, Methodology and Library) for eB usiness. - Modeling Methodologies - Core Component Harmonization (may include Metadata) - Context methodology (may include Ontology) - Message Assembly - XML Schema Design - Messaging Service Protocol - SOA - Registry and Repository - Securities
4Deliverables
Deliverables of TMC are expected as follows. - Guideline for Reference framework (Technology, Methodology, And Library) for eBusiness. - Submission DMRs for CCL - Core Component Libraries (CCL) in the Asian region - Business Process Library in Asian region - Implementation Guidelines for CCL and other relevant data models used in Asian Region - Message Assembly Guidelines - Interoperability Test Specifications and Certificates - Registry Guidelines (may include Federation) - Security Guidelines for e-Business
5Membership and Structure
TMC is an executive committee under AFACT. TMC may have several working groups, such as Core Component Working Group, Interoperability Promotion Group, Security Group. Members of TMC are consists of the person who is representing the member of AFACT. Participants of TMC are open to any organizations who are interested in e-Business implementation in the Asia Pacific region.
6 Organization
TMC has a Chairperson. The chairperson is elected by the member of TMC, and ratified by the AFACT Plenary. The chairperson will serve two years term. The chairperson can be re-elected. The duties of the chairperson are as follows. 1. Call to order and preside over meetings and prepare those agenda 2. Facilitate Working Groups 3. Report activities and results of TMC to AFACT Plenary 4. Communicate the official position on the matter of Technology or Methodology to UN/CEFACT Working Groups, OASIS TCs and related standard bodies TMC may have Working Groups (hereinafter referred to as the “WG”). WGs are subject to be approved by TMC and to be endorsed by Plenary. Establishment each WG should be supported by at least three AFACT members. To establish a WG under TMC, the interested parties shall submit an expression of interest, Objectives, Scope, a terms of reference and an initial work program to TMC for approval. TMC propose the new WG to Plenary for endorsement. Each WG shall appoint its own Convener, and may appoint a WG Secretariat whenever necessary. The term of office for the Convener and the WG Secretariat if it is appointed, shall be for a period of two years. The Convener of each WG shall report its activities to TMC and report to Plenary as requested.
7Voting Procedure
There are 2 types of voting in TMC, the member voting and the participant voting. The member voting shall be taken for the following cases. 1) Election of TMC Chairperson 2) Amendment of TMC ToR 3) Creation or Disbandment of WG The participant voting may be taken for the other cases of the member voting, such as technical matters, working programs. The objective within TMC is to achieve a consistent consensus in all matters. In case of doubt concerning consensus, then, and only then, shall a vote be taken in an official TMC meeting. Any participants who feel that a consensus has not been reached may call for a vote, while the chairperson declares consensus. These ballots require a simple majority of the members (the case of the member voting) or the participants (the case of participants voting) attended at the official meeting at the time of the vote. Any voting can be taken when at least 3 members are present at the meeting. The use of proxies shall not be permitted. The chairperson is not eligible to vote
8 Frequency of the Meeting
The meetings shall be held under the coordination of AFACT. Therefore the meeting may be held with AFACT plenary meeting and AFACT midterm steering committee meeting. The chairperson can call for the interim meetings between AFACT meetings. The chairperson can organize the teleconference instead of the face to face meeting.
9Official Language
English
10Project1: CCL Utilization in Asia
TMC has a program of work.
1. Name: CCL utilization in Asia.
2. Background: - UN/CEFACT CCL is getting too big for covering many domains. It is getting difficult to find the suitable CCs/BIEs in CCL for message designers, and there are concerns about the computer performance using the big XML Scheme modules always. - There are several data model libraries other than UN/CEFACT CCL, such as GS1, OAGI, WCO, UBL and local implementations in Asian region. Many of them are developed using CCTS, but there are no interoperability. - UN/CEFACT Standard Message has a lot of BIEs in order to cover various domains. But user needs a small part of BIEs for daily EDI, but he has to implement all the parts of the Standard Message.
3. Objective: To establish the methodology for utilizing CCL in the efficient manner, and to promote the methodology implementation in the Asian region.
4. Work items: - Analyze the actual problems around CCL. - Prepare the framework for utilizing CCL. - Define the packaged CCL for Asian Region. - POC for utilizing CCL. - Prepare the guidelines for utilizing CCL.
5.Deliverables: - CCL Framework (based on CCTS V3 and NDR V3) - Pilot packaged CCL for Asian Region - Guidelines for utilizing CCL
11Project2: Single Window Interoperability Framework
TMC has established a Working Group. 1. Name: SWIF(Single Window Interoperability Framework) WG 2. Membership and Structure The members of AFACT could join SWIF WG as a primary member. Any individual or organization who is interested in e-business and trade in Asia Pacific region could join as an observer member. 3. Objective For realizing single window, interoperability is a most critical issue in technical area. Nowadays, SOA is becoming rapidly core technical framework for most technical areas, which could be best solution for ensuring interoperability. Many governments are adopting SOA for connecting various systems for interoperability. Also, many big companies introduce SOA as their main software backbone systems. SOA enables very easy connection and communication among software systems with low cost by loosely-coupled mechanism. Single window or e-trading requires complex connection mechanism among systems developed by various stakeholders. This SWIF WG will study and provide a guideline and standard for implementing interoperability framework based on SOA. Even though SOA is a good solution for single window, most people have different ideas in implementing SOA system because SOA is now concept-oriented. So, SWIF WG will provide a guideline for implementing single window with interoperability framework. It can be a practical and detailed guideline for single window system, which also could be helpful in operating e-trading system. 4. Work items This project requires following work items. 1. Analysis for interoperability framework on SOA 2. Analysis for e-trading business in Asia 3. Study for SOA design methodology for SW 4. Define the interface of components for SW 5. Make a guideline and a work template 6. Test guideline for SOA 5. Deliverables: 1. Analysis report of Asia e-trading business 2. A guideline and a work template for SOA in SW 3. A standard for definition of component interface 4. Test guideline