付録10-1 技術的附属書チェックリスト(英語版)
Technical Annex Checklist
The following checklist is provided as a part of the Model Interchange Agreement to indicate a list of items for which details and specifications are recommended to be developed by the parties to an Interchange Agreement.
The list is not intended to be a complete list of all possible topics which might be addressed in a Technical Annex. The items included result directly from references in the Model Interchange Agreement to the Technical Annex; those items may be completed as required by the trading partners, with the level of detail which they determine to be necessary.
Users are strongly encouraged to consider and address other items which they believe relevant to assuring a full understanding exists between trading partners on the technical and procedural requirements which relate to implementing EDI. As noted in Section 1.2 of the Model Interchange Agreement:
"The attached Technical Annex sets forth the specifications agreed upon by the parties for certain technical and procedural requirements."
Section 2: Communications and Operations
2.1 Standards
The parties should agree upon the version release of the UN/EDIFACT standards which they intend to use. Parties may also wish to specify the manner in which they will consider for use new version releases of the UN/EDIFACT standards.
The parties should also designate in practical detail the necessary related technical specifications and details. Items which should be considered include identifying directories, code lists, message implementation guidelines and other items directly connection with specified standards and the related versions.
2.2 System Operations
The parties should describe the methods and procedures for testing their system operations, the effectiveness and the reliability of the message interchange processes, the times when such testing should occur and the intended results that need to be obtained. The parties should adopt a method for clearly indicating the availability of their EDI systems for transmitting and receiving Messages.
2.4 Communications
The details and specifications with regard to the method of communication should describe:
･ the chosen communication method(s);
･ the applicable communication protocols which the parties will use, in addition to the UN/EDIFACT standards (such as X.25 or X.400, etc.);
･ where required, the information details relating to third party(ies) provider(s) to be used, including the appropriate address and contact information and other related details.
Parties may also consider specifying recovery procedures to either retrieve Messages in case of loss or failure or to provide alternate routing and procedures in case of a failure of the selected method of communication.
2.5 Security Procedures and Services
"Each party shall implement and maintain security procedures and services, including any specified in the Technical Annex, to protect Messages and their records against untoward events or misuse including improper access, alteration or loss."
Parties may elect to specify in detail the security procedures and services which they may require to be implemented in connection with their use of EDI. Different means exist for improving the reliability of EDI interchanges between business partners; the general objective is to get as many messages effectively and correctly transmitted and processed as possible, without increasing the cost to an unreasonable level.
