Welcome to the GXS Beta Program FAQ! We're excited to have you participate with us in bringing innovative solutions to the market that will deliver breakthrough results in operational efficiencies and cost savings to your organization. If there is a question that we have not answered, please email us at beta@gxs.com.

Q - What are the benefits of participating in GXS Beta Programs?
A - There are many benefits to participating in GXS Beta Program including:

• Early access to new solutions or new solution releases
• Understanding new solution functionality prior to its commercial release
• Receiving dedicated functional and technical support from the GXS Beta Team
• Ability to influence the final solution deliverable and to suggest enhancements for future releases
• Collaborate with other industry peers that are also participants in the program
• Learning ways to expand your usage of the solution prior to actual implementation
• Receiving product-specific training during the program
• Direct contact with GXS Product Management, Engineering, Quality Assurance, Documentation, Customer Support, and Professional Services
• Solution discounts (as applicable per program)

Q - How do I get involved?
A - Below are the instructions for getting involved:

1. Complete the Beta Program Participant Application Form
2. Submit the form to GXS or send via email to beta@gxs.com
   Important, please include "Beta Program Participation" in the subject line.
3. Your submission will be reviewed and you will be notified on the appropriate next steps for participation
4. As a selected participant, you will be emailed a Beta Agreement, which you must complete, sign, and fax back to the attention of David Goldberg at 301-340-5795.

Q - Who is eligible to participate?
A - Current GXS customers and partners can participate in the beta programs.

Q - If I participate, how much time will it take out of my work week?
A - Beta participants are expected to commit to dedicating up to eight hours of beta testing time per week, in addition to scheduled conference calls taking no more than 1 hour to discuss incidents found during testing and their anticipated resolution steps or timeline.

Q - Can I choose to participate in future beta programs?
A - Certainly, you can make your selection of the solution you wish to be a beta participant for in the Beta Program Participant Application Form and we will contact you when programs are active for the solution of your choice.

Q - What are the requirements to participate in the program?
A - The requirements for participating in GXS beta programs are:

• Complete and submit the Beta Program Participant Application Form
• Complete, sign, and fax the GXS Beta Agreement
• Commit to perform tests for a minimum of eight hours per week, and attend scheduled conference calls hosted by the GXS Beta Team
• Report defects found during the beta program period
• Retest previously found defects once corrective code has been applied
• Answer any survey questions upon completion of the beta
• Provide overall feedback on the reliability, stability, and readiness of the solution for the market
• Provide feedback on suggested enhancements for consideration in future releases or for the development of new solutions
• Agree to limited public relations participation
• Provide the required hardware and pre-requisite software to adequately test the solution (for on-site installed software only)

Q - Are beta participants testing the entire solution ad-hoc?
A - No, the GXS Beta Team will make test plans available to each participant based on key areas of the solution of interest to them, and based on interest by the overall team in a particular area of the solution due to its complexity or to solve usability constraints.

Q - When will products that I participate in testing on as part of a beta program be commercially available?
A - GXS solution release dates are based primarily on the quality of the solution and on market demand. When a new solution or version successfully passes our internal certification process, it becomes a candidate for release. Your feedback during the beta program is paramount to help us determine when a new solution or release meets our certification standards.

Q - What types of feedback are you looking for during the beta program period?
A - Here are some examples of incidents/issues that should be reported during the beta program period:

• Conflicts with other software or hardware (for on-site installed software only)
• Incorrect functionality deviating from the product’s design documentation
• Usability and navigation bottlenecks
• Cosmetic problems
• Abnormal performance impacts
• File import or export problems
• Documentation errors
• Files corruptions

Q - How are beta program participants selected?
A - Beta participants are evaluated based on a set of selection criteria that varies from program to program. The criteria include experience with the solution, expressed level of interest and value expectations of a solution, and willingness to commit the respective level of time to participating throughout the program.

Q - Will I be able to talk/work with other beta participants?
A - Absolutely. A key benefit to our program participants is to be able to network with industry peers and trading partners to compare experiences, exchange thoughts on best practices, and to optimize their joint business processes to contribute to overall value chain agility.

Q - How to I report incidents found during the program?
A - Beta participants should report incidents found during the program via the Beta Incident Reporting Form

Q - How do I provide feedback for improvements to the program?
A - We're always interested in continuous improvements to our programs that will maximize the value of participating, so please send any suggestions to beta@gxs.com