ohsug 2012 presentation - using ctms in local language
DESCRIPTION
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.TRANSCRIPT
OHSUG4 – 7 November 2012
Becky Read – Senior Consultant
• Workforce that includes non-English speakers• Typical scenario…
Why?
English only system deployed
1 x database1 x application
Workaround for non-English speakers
Local language CTMS instanceAlternative tracking solutionAdditional administrative tasks
Resulting in
Higher cost•Infrastructure•Implementation•Support
Inability to report on global studiesInconsistency in data and processIncomplete data in multiple locations
2
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
Solution Evolution
Step 1: Vanilla
• OOTB functionality
Step 2: Configuration
• New fields• New LOVs• New
functionality
Step 3: Language Pack
• 90% Vanilla components translated
• Object Mgr. for new language
• All customizations in English
• LOV fields in English
Step 4: Final Product
• Fully translated
• LOVs displayed in local language
4
How: Step 3 to Step 4
• Install one system with multiple language packs
• Install one system with multiple language packs
Setup
• Identify and configure areas of system that are not globalization ready
• Identify and configure areas of system that are not globalization ready
Update • Create labels for customized entities
• Import non-vanilla LOVs
• Create labels for customized entities
• Import non-vanilla LOVs
Add
• Validate changes• Deploy SRF and
Repository
• Validate changes• Deploy SRF and
Repository
Deploy
5
• 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
Challenges?
6
7
The Result
Solution Finalization
8
Comprehensive design
documents
Full set of training
materials
Full set of validation materials
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
11
Any questions?