With many companies working across the globe the need to have a system that is understandable to all users is imperative. The ability to input in multiple languages yet not restricting output to a specific language is a necessity and keeping down the hardware cost is an absolute. The CTMS must accept multiple language inputs with the ability to display those inputs in the language of the user logged in, whether that be English, Spanish, Chinese or another. Triumph willl explain the methodology they have created to achieving this, the work they are performing to support Asian and Latin American markets and some of the technical challenges and pitfalls they have had to overcome.

1. OHSUG
4 – 7 November 2012
Becky Read – Senior Consultant

2. Why?
• Workforce that includes non-English speakers
• Typical scenario…
English only system deployed
1 x database
Workaround for non-English speakers
1 x application
Local language CTMS
Resulting in
instance
Alternative tracking solution Higher cost
•Infrastructure
Additional administrative •Implementation
tasks •Support
Inability to report on global
studies
Inconsistency in data and
process
Incomplete data in multiple
locations
2

3. Ideal Solution?
Requirements
One system that can be used by entire
workforce
Ability to translate both vanilla and
customizations
Utilizes industry translations
Able to enter data in multiple languages
Option to view same data in multiple
languages
3

4. Solution Evolution
Step 2: Step 3: Step 4:
Step 1: Vanilla
Configuration Language Pack Final Product
• OOTB • New fields • 90% Vanilla • Fully
functionality • New LOVs components translated
• New translated • LOVs
functionality • Object Mgr. for displayed in
new language local language
• All
customizations
in English
• LOV fields in
English
4

5. How: Step 3 to Step 4
• Install one system
Update • Create labels for
Deploy
with multiple customized
language packs • Identify and entities • Validate changes
configure areas of • Deploy SRF and
system that are • Import non-vanilla
LOVs Repository
not globalization
ready
Setup Add
5

6. Challenges?
• Vanilla Siebel is not translation ready out of the
box
• No simple way of locating all LOV fields used
• All existing and added configurations must
adhere to translation requirements
• Little to no guidance documentation available
• Ensuring there is an equivalent local LOV for
each existing LOV
6

7. The Result
7

8. Solution Finalization
Full set of
validation
materials
Full set of
training
materials
Comprehensive
design
documents
8

9. Biography
Becky has been working for Triumph for more than six years, having joined as a
consultant and training specialist. During her time with Triumph, Becky as worked for
more than ten different clients in the biosciences industry, delivering services ranging
from training, business analysis, and software development, right through to full CTMS
implementation management.
Prior to joining Triumph, Becky had set up and managed the IT helpdesk for a large CRO,
and became involved in supporting Siebel Clinical users after a global rollout.
Becky’s industry experience, eye for detail, passion for client satisfaction and general
management capability led her to be promoted to Senior Consultant in 2010, reporting
directly to Triumph’s COO.
Becky continues to work with Siebel Clinical on a regular basis, and has been focusing
on the development of Triumph’s multi language CTMS product in between client
engagements.
9

10. Contact
Becky Read
Becky.Read@triumphconsultancy.co.uk
Office: +44 1279 812550
Website: www.triumphconsultancy.com
10

11. Any questions?
11