SDL Studio GroupShare Cloud a cloud collaboration solution...
Transcript of SDL Studio GroupShare Cloud a cloud collaboration solution...
SDL Proprietary and Confidential
SDL Studio GroupShare Cloud –a cloud collaboration solution for translation teams to share TMs, projects and terminology
Sandra Langer, Business Manager, SDL,
October 2015
2
Agenda
○ Industry business objectives
○ Challenges of working in a team and how to address them
○ Decision-making – desktop or server solution?
– Non-server solution – SDL Trados Studio
– Server solution - What is Studio GroupShare?
○ Perpetual vs Cloud
○ Conclusion
3
Create efficiencies
Achieve customer satisfaction
Ensure security
• Improve margins
• Increase profitability
• Quality
• Consistency
• Protecting assets
• Management control
• Data protection
Business objectives of today’s localization industry
4
ProductivityProductivity Quality Security
Challenges – Improve margins, increase profit
Tight deadlines
Work across time zones
Content management systems – new
content types – ‘micro-translations’
Need to do more with the same amount
of resource
Managing return on investment - making
assets word harder
5
ProductivityProductivity Quality Security
How to maximise the efficiency potential?
Reduce the project overhead
Eliminate mistakes
Easy document retrieval
Get the most out of your linguistic assets
6
Productivity Quality Security
Challenges – Customer satisfaction and quality
○ Create differentiation
through quality
Ensure consistency of
quality
Increased advocacy for
terminology adoption
Focus on existing
customers
7
Productivity Quality Security
How to ensure quality in a collaborative workflow?
Access translation memories and
terminology in real time by multiple
users whereever they are
Consistent implementation of QA
checking rules (share project
settings in real time)
Everyone uses the correct files
Support ISO Certification
8
Productivity Quality Security
Challenges – protecting assets, control and data protection
○ Loss due to hardware failure, e.g. hard disk
crash or loss due to portable computers getting
stolen
○ Leakage of information and intellectual
property caused by full TM exports being sent
out to external parties, who can then distribute
such data to other parties without you being
able to control it
○ Control of complex workflows
9
Productivity Quality Security
How to ensure security, control and data protection?
○ Implement client/server paradigm – reduce
loss of data, stop leakage of intellectual
property
○ Provide managers with complete view of
progress, streamline workflows between
resources and enable automation of manual
tasks with alerts
○ Manage who can access your projects,
translation files and what level of authority
each user is granted.
Decision making – Desktop or (AND) Server
How to …. Step 1: Maximize Studio
12
Small team solution – do I need to invest in a server?
○ SDL Trados Studio can support file sharing without the need for
an application server! After all, it offers …
– Sharing of TMs and termbases over the local network
– QA functionality
– Review by non-Studio users
– Management of projects via Studio
– Functionality enhancements through apps and plug-ins
13
Understanding the limitations of file sharing
The limitations of traditional file sharing are often underestimated
○ Files were designed to be accessed by single users, not by multiple users
from multiple locations
○ Files are based on the computing paradigms of the 1980s, i.e. standalone PCs
○ However, in the past 20 years new IT paradigms have established themselves,
e.g.:
– Distributed locations
– Web-based collaboration
– Mobile computing
14
Client/server technology: send a query, get a response,
just like a Google search - no need to download loads of
data
15
Lightweight data access: on average a TU uses only 4KB.
It only takes a fraction of a second to transfer a TU
How to …… Step 2: Centralize & Share
17
Not For External Distribution
SDL GroupShare in a Nutshell
A collaboration system to facilitate workflows between project managers, translators, reviewers, etc., that comes with an automated notification system
COLLABORATION
CENTRALIZATION
A client/server-based solution to centralize translation assets and make them available over the Intranet / Internet
19
Not For External Distribution
SDL GroupShare centralizes TM and termbase data and the actual files that require translation
SDL Studio GroupShare
Project Server TM ServerMultiTerm
Server
20
Production-side workflow savings
○ Example workflows …
21
File-based translation workflow
Sending linguistic
assets, e.g. via FTP
Translation
Versioning
(for roll-back
purposes)
Review
Versioning
(for roll-back purposes)
Approval
Versioning (for roll-
back purposes)
Eliminate inconsistencies caused by non-centralization
Versioning
(for roll-back purposes)
Project completion
Delivery Archiving
Project creation
Job assignment
22
Server based workflow: 7 manual steps
Translation Review ApprovalProject
completionDeliveryProject
creationJob
assignment
23
With GroupShare + Automation: 3 manual steps
Translation Review ApprovalProject creation
Job assignment
Project completion
Delivery
• SDL Studio Groupshare Cloud is the cloud version of the on premise SDL Studio Groupshare solution
• It offers the same core functionality (Project, TM and MT Server)
• Customers don’t need to install any server software locally
• The server is hosted by SDL Cloud Operations (Slough)
• It is multitenant, but all the data and visibility of customers is segregated
25
SDL Studio GroupShare Cloud – ideal for smaller translation teams
Conclusion
27
Efficiency increased
Easier communication and transfer
of files
Easier for translators / Reviewers to
commence work
Easier splitting of jobs
Easier and faster TM maintenance
Complete flexibility
28
Faster Translation
Cross-leveraging of TM from the
entire team
Quick cycle through the various
phases of the project (Translation /
Review / Sign off)
Faster document retrieval
29
Security and Control
Translation assets are valuable
Centralized back up of valuable
translation assets
Centralized user management
Capacity to manage all sizes of
team.
30
Quality and consistency
Consistent TMs across the project
Latest terminology updated for the
entire team
Latest files being used and up to
date. Avoid sending wrong files out
Consistent QA rules