Originally Systems, Applications and Products in … · CO-OM-CCA / Cost Center Accounting SAP ERP Operations India Localization for SAP ERP Software component version = Product instance

Terminology Management at SAP

Mark D. Childress / SAP Language ServicesMay 2014 Public

Originally “Systems, Applications and Products in Data Processing”

© 2014 SAP AG or an SAP affiliate company. All rights reserved. 2Public

Or, how does terminology get …

... from SAP ... ... to the customers?


Agenda

Corporate profile (short version) and products

Terminology management at SAP

Some closing words

Appendix Corporate profile (the longer official version)

SAPterm information for those with SAP system access

Corporate profile (short version) and products


SAP AG – back when I started (1995) …

5000 SAP employees worldwide

41Countries

4Industry-specific solutions

15Languages

19Country subsidiaries

4300+SAP customers worldwide


SAP AG today

66,000+ SAP employees worldwide

190Countries

25Industry-specific solutions

47Languages

130Country subsidiaries

250,000+SAP customers worldwide


The global SAP development network (SAP Labs)

USAPalo Alto, California

IndiaBangalore

CanadaMontreal

ChinaShanghai

HungaryBudapest

IsraelRa’anana

BulgariaSofia

RussiaMoscow

BrazilSão Leopoldo

GermanyWalldorf / St. Leon-Rot


SAP today

SAP AG annual revenue 2013: €16.9 billion More than 250,000 companies use SAP products The world’s leading provider of application software for companies The world’s 3d largest independent software company

Millions of people use SAP solutions for: Integrating business processes Improving competitive strength Earning faster returns on lower system cost-of-ownership

A unique partner network 2,0 million SAP Community members

Software Developer Network

Business Process Expert Network

Industry Value Networks


What are SAP products?

Software componentversion =

Product instance = (Software) product version =

Combined groups ofsoftware component versions

Combined groups ofproduct instances

Smallest units ofsoftware coding


What are SAP products?

SAP ERP Financials

SAP ERP Human Capital Management

FI-TV / TravelManagement

CO-OM-CCA / Cost CenterAccounting

SAP ERP Operations

India Localization for SAP ERP

Software componentversion =

Product instance = (Software) product version =

Combined groups ofsoftware component versions

Combined groups ofproduct instances

Smallest units ofsoftware coding


Our strategy: Offer complete solution portfolios for all employees in all industrial sectors for all companies

On DEVICE

On DEMAND

On PREMISE

OR

CH

ES

TR

IER

UN

G

User-friendly approach Integration with On Premise

und On Demand

Industry-based orpackaged solution

Integration with On Premise

Best Practices Non-distruptive innnovation

of enhancements

SAP Business Suite 7

SAP Business ByDesign

LoB on Demand

Collaboration Analytics Mobile

Common technology foundation for many different solutions

In-Memory – Use working memory for data storage and significantly faster access speeds


SAP’s product/solutions strategy:To compete for leadership in all five market categories

Extending leadership in Applications

Broadening Analyticsfootprint

Becoming fastest growing D&T company

Strengthening leadership in

Mobile

Becoming a profitable

Cloudleader

Innovation powered by SAP HANA

Deliver the highest customer value through innovation without disruption


SAP HANA speeds up and simplifies work

Data Warehouse / Data Marts

Data Warehouse / Data Marts

OLAP

Operational system

Operational system

OLTP

Business event

Analyzeand

take action!

No aggregation / no data preparation / no data marts

SAP HANASAP HANA

In-memorytechnology


Example: Energy industryA diverse landscape with diverse terminology

Offshore extraction

Onshore extraction

Mining

Petro-chemicals

Refinery

Gas-to-Liquids

Fuels andlubricants

Energy forhouseholdsand industry

Power plant

Do

wn

stre

amU

pst

ream

Plastics

Gas storage /

LNG

Hydropower

HouseholdsRetail IndustryTransport

Renewableenergy


Sample business process – SAP Oil & Gas Business Map


What the customer sees – local frontend


Filter by: Maintenance History

Vent Pipe 3Last Maintenance: 2 Weeks

E 0.1km

What the customer sees – Mobile


SAP touches the lives of billions of people – every day

Our industry solutions support:

80%of the world’s

annual productionof chocolate

The production of

75%of all radio and televisionbroadcasts worldwide and

60%of all films worldwide

The processing of

3.0 billionutility bills per year

The monitoring of

6 billiontransactions in US stock

exchanges every day

The production of

70 millionbarrels of oil every day

82%of the world’s annual

production ofcoffee and tea

The production of the

top 20prescription medicines

in the worldThe manufacture of

95,000cars every day


42 years of experience across all industries

DIENST-LEISTUNGEN

KONSUMGÜTER-INDUSTRIE

HANDEL

FINANZDIENST-LEISTUNGEN

PROZESS-INDUSTRIE

FERTIGUNGS-INDUSTRIE

ÖFFENT-LICHEVERWAL-TUNG


The Best-Run Businesses Run SAP –In Belgium

Terminology managementat SAP


Why terminology management?

Consistency in communicationDo you tell customers to use the electronic catalog, the E-Catalog, the eCatalog, the Online Catalog ... or something else entirely?

Reusability in different functional areasProduct development, documentation, consulting,customer service, marketing ...

Reliability across contexts and languages

DE Position EN item ES posición

PL pozycja FR poste ...

In a word: Quality!


UI Texts: Quality Pyramid *

No abbreviations without context

Idiomatic languageClear language

Simple language

Simple, consistentterminology

All necessary information on the UI

Spelling correctGrammar correct

Chronological order is followed

Focused on the tasks and goals of the user

Punctuation correctConsistent capitalization Parallel constructions

Direct address and active voice

Does not state the obvious

Pleasurable: Innovations

Usable: Content

Reliable: Form

Interestinghuman

conversation

1: No negative formulations, no long sentences, no nominalizations

2: Not wordy, not ambiguous, notredundant

3: Reads as if written by a native speaker

* Based on a ranking survey undertaken at SAP – see Stotz (2014)


SAP interface – language selection at logon

EnglishJapanese

Arabic


SAP interface – multiple languages and countries

Chinese

Arabic Russian

Japanese

EnglishGerman

Italian


Non-standardized terminology costs money

Changes required in –

Products, their userinterfaces...

Documentation,operating/installationinstructions ...

Training materials,multimedia, web pages, contracts,brochures and other marketinginformation ...

– in [X] languages –

– AND corresponding changes for customers and partners!


Fixed vs. variable costs in terminology work *

Costs

Frequency of terminology use

Fixed costs for terminology work

Rising variable costs if no systematic term work takes place – little/no resuability of terminology, duplicate efforts, redundant and contradictory tasks

Variable costs minus upfront investment and fixed costs of systematic term work = overall savings thanks to term reuse, decreased redundancy, and coordination of term management tasks

Crossover point at which term management results in lower costs

* afterSchwetz (1994), Wright (1996)

Personnel costsTerm databaseStandards/

processesTrainingOngoing term

work, projects, coordination, database system maintenance


The earlier the terminology investment, the better *

Specification

Technical writing (research)

Technical writing (text)

Editing

Acceptance test

Translation

Support / maintenance

0.1–0.2

0.5

1.0

2.0

5.0

10.0

20.0

Product / service phase Cost multiplier for term/definition creation

* after Schütz and Nübel (1998)


The framework for terminology management at SAP

SAP: … is active in over 180 countries and supports over 232,000 customers … offers standardized software and support for general business processes and

specialized processes for more than 25 industry sectors … pursues a worldwide, distributed development and sales strategy

This means: … over 42 standard logon languages (and a few more special project languages) … specialized terms are required from every conceivable branch of business for

all of these languages … term information is needed by 66,000+ internal SAP employees and by millions

of external customers, partners, and consultants

This results in:… a unique terminology management challenge – no other company

attempts to cover as many subject areas in depth in as many languages as SAP!


Terminology management = Knowledge management *

Organi-zational

knowledge

Personal knowledge

Knowledge creation

Knowledge capture

Knowledge distribution

implicitDaily work and experience

systemicProcess-based testing of concepts

operationalProviding role-based access to knowledge

Handoff point

conceptualFormulating experience for others in understandable and reusable ways

* After Nonaka (1997)


Terminology and conceptualization

Create concepts and formulate for others Define terminology

standards based on international norms

Require all “language workers” to enforce standards for terms and definitions in their teams

Train employees in terminology work

conceptual

systemicoperational

Termknowledge

personal


Development team organization at SAP

Software developmentEN (and some DE)

Technical writing *EN (and some DE)

* At SAP: “Information Development”

TranslationEN > DE & DE > EN

Multiple teams in software development create solutions – software component versions, product instances, product versions – based on customer/market needs

LEAN principles: Development in “takts” (production cycles) to reduce or eliminate waste in development and improve quality

Ideally 10-20 software developers to 1 technical writer and 1 translator – in reality most writers and translators work simultaneously for multiple teams in parallel

Terminology is discussed and agreed upon in the teams, between teams in the same department, and (best-case) on a cross-departmental basis


Handoff point: Terminology creation

Terminology standards Terminology trainingStandards für Terminologieeinträge in SAPterm: Deutsch (DE)Status: Januar 2004

Allgemeine Richtlinien für das Erstellen von Einträgen Die nachfolgend dargestellten Bestimmungen stimmen überein mit dem allgemein üblichen Vorgehen bei der Terminologiearbeit. Viele dieser Bestimmungen basieren auf einschlägigen ISO-Normen.

Allgemeine Form von Terminologieeinträgen Geben Sie den Eintrag in seiner unflektierten grammatischen Grundform ein. Die Struktur der

Grundform richtet sich nach der Wortart. - Substantive: Verwenden Sie den Singular.

Beispiel Buchungskreis – nicht Buchungskreise

- Verben: Verwenden Sie den Infinitiv des Verbs (nicht den erweiterten Infinitiv mit zu + Infinitiv). Beispiel sichern – nicht zu sichern

- Adjektive: Verwenden Sie die unflektierte positive Form (keine Steigerungsform). Beispiel rechtsbündig – nicht rechtsbündige

- Adverbien: Verwenden Sie die Grundform. Beispiel plötzlich

Verwenden Sie eine von der Grundform abweichende Form (z. B. Substantiv im Plural) nur dann,

wenn durch die Flexion ein Bedeutungsunterschied gegenüber der Grundform markiert wird. Beispiel Die Pluralform Daten bedeutet etwas anderes als die Singularform Datum. Leute ist eine grammatische Pluralform (Pluraletantum), zu der kein Singular existiert.

Verwenden Sie Interpunktionszeichen – Anführungszeichen, Schrägstriche, Kommas usw. – nur

dann, wenn es sich um unverzichtbare, integrale Bestandteile des Begriffs selbst handelt. Beispiel .NET iView WE/RE-Verrechnung

Fügen Sie dem Eintrag keine kontextbezogenen Informationen hinzu (z. B. in Klammern

nachgestellte Information am Ende des Eintrags). Verwenden Sie für kontextbezogene


Standards

To 1990: No standards!

1991: “Entry Conventions” for the DICT term tool – DE and EN only

1993-1997: DE/EN standards translated to other languages – word-for-word, and not adapted for the new term tool

1998: Standards radically rewritten, based on ISO norms; teams required to create language-specific standards or be thrown out of the term database

2003: Update of the cross-language standards and quality measurements

History of term standards and training at SAP

Training

To 1993: No training!

1994: First (?) workshops for colleagues in Germany

1997-99: Training units reworked and made part of mandatory technical writer / translator curriculum

2000-2002: Additional advanced training developed, lecture series established

2005: E-learning units and online training

2008: Training concept for new external translation suppliers includes training on location and follow-up monitoring


SAP standard: Use the customers’ terminology

SAP uses established standard terminology as much as possible from relevant subject areas –

Standard dictionaries

Internet research

Consultant, subject area expert, and customer feedback

– but SAP does not avoid creatingnew terms based on SAP solutions and products when necessary

Example: “Customer Relationship Management” terms were translated into Turkish, Hungarian, and other languages for the first time as part of SAP products – the terms are now textbook standards in those languages


Terminology: Which languages do we need?

Czech

Danish

Dutch

English

Finnish

French

Hungarian

Italian

Norwegian

Chinese (Simplified)

Chinese (Traditional)

Hebrew

Japanese

Korean

Serbian

Thai

Turkish

...

Source language: German

Polish

Portuguese

Russian

Slovak

Spanish

Swedish

...

Source language: English

German

...


SAPterm statistics (Apr 2014)

Standard languages: 39ArabicBulgarianCatalanChinese (Simplified)Chinese (Traditional)Croatian

Additional languages (some not in SAPterm)Afrikaans Malaysian Portuguese (Portugal) Spanish (Columbia)

New standard languages 2014 (maybe?) :Bengali Spanish (Mexico) Tagalog …?

Main term entries: 3.8 million (165,000 DE/EN source entries translated in ca. 42 languages) plus 400,000 variants (abbreviations, etc.)

GermanGreekHebrewHindiHungarianItalian

SlovenianSpanishSwedishThaiTurkishUkrainianVietnamese

Czech

Danish

Dutch

EnglishEstonianFinnishFrench

JapaneseKazakhKoreanLatvianLithuanianNorwegianPersian

PolishPortugueseRomanianRussianSerbianSlovakian


Terminology and systems

Collect and test all terms in a central official database Designate SAPterm as the

single-source repository

Define and publicize processes; develop SAPterm improvements based on process (not the reverse)

Integrate SAPterm with other tools requiring term data

Train employees about processes and SAPterm use

systemic

conceptual

operational

Termknowledge

personal


Handoff point: Term Review

Terminology processesProject lead def ines

sof tware dev elopmentproject goals and

deadlines

KM plans docu/trans/edit ing resources

KM determines scope ofdocumentation and

resource assignments

Software development and information development DE/EN apply usability approach to minimize need forsoftware texts and documentation and standardize terminology

KM inf orms QM of docuf or Acceptance Test

SLS language coord.names subject matter

experts per language andproduct

Information development DE/EN and SAP Language Servicesagree on new/changed terminology

Follow-on languagestranslate terms in

SAPterm

Sof tware dev createssof tware interf ace and

texts

Sof tware dev releasessof tware to inf o dev DE/EN

Inf o dev DE/EN works ontexts and tool t ips

Inf o dev DE/EN appliesquality control tools

Inf o dev DE/EN inf ormsteam RE new terms

PKB rev iews quality ofexist ing terminology

Project responsiblesdef ine product/f unctionnames and key terms

Inf o dev DE/EN releasestexts

SoftwareDevelopment

Inf o dev DE/EN correctstexts and docu based on

Acceptance Test

Inf o dev DE/EN checksterm consistency

Follow-on languagesenter released terms in

Proposal Pool

PKB and f ollow-onlanguages gather and

ev aluate term candidates

Lang coords organizeterm rev iews by subject

matter experts

Follow-on languagesenter unknown terms f ornewsgroup discussion

Inf o dev DE/EN createsdocumentation

Follow-on languagestranslate changed texts

Handover toVerification

SLSTranslation

Inf o dev DE/EN enters andreleases terms in

SAPterm

Sof tware dev writes spec &design paper f or each

dev elopment

Inf o dev DE/EN enters andreleases terms in

SAPterm

Inf o dev DE/EN entersterms in SAPterm

Follow-on languagesrelease terms in SAPterm

Sof tware dev changessof tware to conf orm with

term decisions

KnowledgeM anagement

InformationDevelopment

DE/EN

SAP LanguageServ ices

gp

STePS Process Overview: Dec 2003

Terminology database

40© 2014 SAP AG or an SAP affiliate company. All rights reserved.

Portfolio Planning

Project Preparation Translation

Project Close

Translation Preparation

Project Planning

Customer Involvement

Project Administration

Supplier management

Translation

Technical Support

Portfolio planning

(interaction with customer via

questionnaire)

1

Provide info sessions for SLS/agencie

s

Create budget

item incl. IO Group

Perform system setup

Provide input on

landscape incl. test system

Determine language

strategy incl. LAT

responsibility and

organization

Create program in system SLS

Maintain translation system in

SLS

Agree quality requirement with customer/ field

Define project scope (incl. feasibility,

transl. relevance and

deadlines)

Establish system setup +

evaluation

strategy

Input on the Scope

(languages / deliverables)

After Project Close

Quality Assurance

2 3 4 5 6 7 8 109

Review terminology

(initial)

Provide test landscape incl.

languages external access

& test data

27

12 13 14 15 16 17 18

11

Request system release

for Astaro

Maintain budget item in SLS if

necessary

Create project item in SLS

Request initial worklist

run + top texts if

applicable

Create ref. TM / provide access

to ABAP search

tool

Provide more

detailed project plan

Identify PM,

identify team mem-bers

Check initial

stats + update forecast

19 20 21 23 24

Hand-over

to PM

Maintain SLS (finalize

milestones), create project book and

project pageSetup confirmation

list

Collection assign-ment to trans-lators

User admi

n

Create Res-ource

request

Update forecast data

If applicable: Check for PDF, PDF workflow

Milestone/project

reporting

Monitor statistics

Clarifi-cation of

new collection

s

Kickoff manual

translation

27 28 29 30 33 34 35

Delivery to final

assembly

Handover to DM

Handover to PM responsible for

support packages (initial translation only)

Monitor translation

close

35 36

Post-mortem/lessons

learned (“no loose ends”)

PEP

Maintain SF Postdelivery

XLS

Maintain PPMS

Knowledge transfer to

development

Get final feedback

on product in

translation language (country sign-off)

Ongoing Activities during translation: Active

communication with partners, Q-questions, general queries, generating BLIs for team Query Handling (ongoing) Regular quality checks (e.g.

QETT) Terminology review coordination

Process CSS messages

Prepare + kickoff

terminology project (project

key, etc.)

Coordination/setting up

LAT/testing of translation in

context

Provide feedback to

dev./doc. writers

based on source

queries of previous releases

Organize/execute

terminology review with

experts (field, dev.,

PM)Term Q-check

Info sessions & knowledge

transfer (product info, processes,

tools)

13-144-11 23 25 3727 31 32 33

Final LAT validation

Vendor follow-up, decide on

activity based on

QETT-results

2322

Vendor assign-ment

Create shopping

cart Confir-mation

checking (invoice)

37

2624

Translate TTTranslate

terminology

33

Project comple

-tionreport

Ongoing activities during translation: Translate SAPterm entries

Translate texts Use test system environment

directly Generate QETT and takt-based

worklists

Project evaluatio

n by partner

Process confirmation

/invoices

Ongoing activities during translation: Solve technical problemsCreate worklists regularly

Release system(s

) for Astaro

37

Close POs

Implement customer

corrections from running

releases

Create +

update style

guides

14

i

Ongoing or reported activities (not project

specific)

39

13

38

27-33

27-33

27-33

Organize LATReview terminology

(delta)Test translation in

context (test systems/LAT)

28-3324


Term process example: Data flows for shipment


Software development, product owner, usability, and information development teams create and

define terms

Source language (SL) technical writers and translators create

and review SL terms

SAPtermTerminology

Database

Technical writers and translators review terms based on

internal/external feedback

Reference for technical writers and translators

Reference for all SAP colleagues

Reference for externals (customers, partners,

suppliers)

Term process example: High-level overview

Feedback

Feedback

Fee

db

ack

Translators create and review target language (TL) terms

Feedback


Technical writing at SAP

Knowledge Management in the source languages English and German Technical writers + translators + coordinators + editors work directly in their teams/units

Each role has a training curriculum path The basic terminology course is mandatory!

Advanced terminology training is offered for experienced colleagues

Technical writer (at SAP the “information developer”“) Approx. 600, of which 4/5 write in EN (not necessarily native speakers!) and 1/5 write in DE

Mostly located in Germany and USA; larger concentrations in India, Ireland, Israel, Canada, and China; smaller teams and individuals scattered around the globe


Internal translation at SAP

Translation English < > German Approx. 150, of which 4/5 translate EN DE and 1/5 DE EN

Translators work directly in the development teams or in the central translation team

Translation for project languages SAP country subsidiaries coordinate translation locally in non-standard languages for special

customer projects – some of these may become standard languages if supported by an official business case (language investment vs. sales potential)


The terminologist at SAP *

A technical writer, translator, or coordinator with additional SAPterm authorizations – and additional responsibilities:

Monitor term entries and their definitions in a given language and given subject area in cooperation with the terminologists responsible for the other languages

Organize and promote harmonization of terminology for the team, the unit, and, where possible for the company (and beyond)

Help team colleagues with SAPterm-related issues

* Role at SAP called “SAPterm Superuser“

NewReview ReleaseDeleteSpecial

1

2

3

4

...

new1

2

3

4

0

reviewreleased

delete

translateposition? item?


Facts about SAP Language Services (SLS)

SLS is part of Globalization Services, which includes the development teams for localization and internationalization

SLS has 200 colleagues in 20 SAP offices worldwide, coordinating translation projects for 39 standard languages and providing other language services and technologies for all SAP products, services, and corporate documents

SLS works with 110 translation suppliers (2800 translators) worldwide

In 2013 280 million words were translated from the source languages English and German


SAP Language Services: “Translating SAP for the World”

VP Office

Process & Quality Governance & Translation Cross Functions

Line Management

SLS SAP AG (& EMEA)

SLS Asia

SLS Ireland

SLS Japan

SLS North America

Business Partner Management

Translation Delivery Teams Product 1Applications

Translation Delivery Teams Product 2TIP, Cloud, M&A

Translation Delivery Teams Product Support & Corporate Content

Language Technology Group

Engineering

Language Technology

Translation Solutions Development

Terminology@SAP

GlobalProcurement

Language Services


SAP Language Services – Sample process for products

Request from SAP customer

or market research

Translation Service Team (TST)Project management, quality assurance, and translation delivery

Responsibility: Service Owner

Language Technology Group (LTG)Translation environment and formats; development and support for translation software

Product owner in the

development unit orders languages

Development unit integrates the translation in the product

SAP customer

Translation suppliersProduct translation (usually located in-country), requiring

third-party budget and approval

Business Partner Management (BPM) Assignment and administration of external translation suppliers *

SAP Language Services

* SAP translates many products and documents in-house, especially for EN < > DE


SAP Language Services / Terminology@SAP

Mission: Quality terminology at every fingertip

The “Term Team” provides cross-language,cross-topic, and cross-departmental support for all aspects of terminology management at SAP:

Collect and distribute term management information

Collect user needs and suggest (or require) solutions Standards and processes

SAPterm development

Distribution routes

Training, workshops, presentations

Monitor term work, provide user and project support

Provide training for technical writers, translators, andterminologists

Support special projects Integrate terms (and term management) of acquired companies

Implement new languages in SAPterm

Participate in developing the TBX standard for terminology (ISO 30042)


SAP Language Services / Translation Solutions Development (TSD)

TSD develops internal solutions and supports integration with other tools:

Solutions on the SAP NetWeaver platform

Translation of SAP product interfaces, documentation, table entries

Terminology tool SAPterm

Integration with other tools

Content management systems

Controlled language

Translation memory systems

Machine translation


SAPterm – initial screen


SAPterm – advanced search


SAPterm – results list


SAPterm –term entry detailed view


Terminology and operations

operational

Distribute the term database contents Define role-based access

to the term shipment and display options

Inform users about term access – presentations, posters, articles in SAP newsletters, SAP TV shows …

Provide documentation and FAQs for users

conceptual

Termknowledge

personal

systemic


The “family tree” of terminology at SAP

Until 1990Books, etc.

1990R/2 transaction DICT

SAPtermCD

SAPtermWeb Access

TradosMultiTerm

R/2 Dictionary,2 vols. (DE-EN / EN-DE)

1993Basis transaction SE64

1998SAP NetWeaver STERM

WinHelpGlossar

SAPtermJunior

HTMLGlossary

sapinfo.netGlossary

Lotus Notes(projectcancelled)


Circles of Terminology Users

Customers

Terminologists

Internal Users

Other (“rest of world”)

Partners/Contractors

Industry/Branch

Users need less access

and less detailed

information as one moves

outwards

TerminologyDatabase


Handoff point: Terminology distribution

Shipment / availability based on defined user roles

Terminology and glossary SAPterm in SAP NetWeaver

SAPterm Web Access (internal)

SAPterm CD (external OBSOLETE)

SAPterm.com (external)

Glossary (monolingual definitions only) SAP Help

Glossary appendix for brochures, training materials, etc.

SAPtermdata


Term distribution example: Glossary in SAP Help

Available from SAP product documentation (Help > Glossary) in Plain HTML format with a browser

Glossary available separately in the SAP Library menu bar


Term distribution example: SAPterm CD (obsolete)


Term distribution example: www.sapterm.com


Terminology and the individual

operational

Support uptake and acceptance of terminology for daily use Allow all employees to

participate in term work at the appropriate levels

Provide easy access routes to terms

Emphasize terminology as a central pillar of the knowledge company

Get rid of “terminology phobias”

conceptual

Termknowledge

systemic

personal


Terminology and knowledge management work together!

• Creating knowledge (that is, creating terms) by individuals as part of their work for a company

• Distributing knowledge, (in the form of terms) by means of best practices defined and supported by the company

• Improving knowledge (terms and definitions) by constantly evaluating situations and developing solutions


Terminology is everywhere!

• Companies can neither avoid nor ignore terminology issues.

• Well-defined processes and procedures for dealing with terminology issues, continuously monitored and improved, are better than ad-hoc actions and spur-of-the-moment terminology projects.


It’s management, not magic!

Neither knowledge management nor terminology management are instant cure-alls!

Open communication between all stakeholders is vital.

The active support of management (upper and middle) is, as always, decisive for terminology strategy.


Term management = pure knowledge management!

Termknowledge

Personalknowledge

Knowledgecreation

Knowledgecapture

Knowledgedistribution

Daily work andunvoicedknowledge

TerminologycreationFormulating aterm usefulfor others

TerminologyreviewProcess-basedtesting of termsand theirmeanings

TerminologydistributionRole-basedaccess andshipment


Terminology management: Summary

The general principles:

Look at all aspects of term work, from development to serviceUse established analysis techniques to find the pain points

Accounting / controllingProcess management and knowledge managementQuality management

Look for alliesCommunicate with everyoneManagement support is vital

Don’t try to solve everything at oncePrioritize – start off small – chart incremental progress – finish big

Publicize the successes

Repeat everything every 2-3 years (people forget …!)

And most of all:

Practice patience and fortitude …Never give up … never surrender!


The goal of Terminology@SAP

WorkContents,

tools,and processes

EffortLeverage

Continuous improvement of contents, tools, and processes in terminology management!


The alternative?

WORK


And that’s how terminology gets ...

... from SAP ... ... to the customers!

Some closing words


Further information

SAP AG: www.sap.com

SAPterm.com + SAP Terminology Community: www.sapterm.com

SAP Help Portal: http://help.sap.com – monolingual glossaries (DE / EN, soon JA / ZH)

Articles/ presentations / publications by your presenter(mit Christian Lieske) „Terminology Activity at SAP“ in MDÜ / Mitteilungen für Dolmetscher und Übersetzer 1/2001

„Applying a Knowledge Management Approach to Terminology Management“ in TKE '02: Terminology and Knowledge Engineering Proceedings (Aug 2002) – www.loria.fr/projets/tke

„The Practical Use of Knowledge Management in Terminology Management“ in TAMA 2003 South Africa Proceedings (Feb 2003) –www.tama-sa.gov.za

„Terminologiemanagement und Wissensmanagement bei SAP“ in Deutscher Terminologie-Tag e.V. Akten des Symposions Köln, 26.-27. März 2004

“Die Kundensprache als Teil der terminologischen Strategie einer Firma” in eDITion. Das Fachmagazin für Terminologie 1/2005

„Terminologiphobia!“ in MultiLingual 80 (Jun 2006)

„Terminology Work Saves More Than it Costs“ in MultiLingual 87 (Apr/May 2007)

„Terminologie im Kommunikationsprozess eines Unterhemens“ in Deutscher Terminologie-Tag e.V. Akten des Symposions Mannheim, 18.-19. April 2008

(Projektleitung mit Petra Drewer) Terminologiearbeit – Best Practices. Deutscher Terminologie-Tag e.V. (Köln, 2010). ISBN 978-3-9812245-1-1

„Projekte und Prozesse der Terminologiearbeit“ in Deutscher Terminologie-Tag : Akten des Symposions Heidelberg, 15.-17. April 2010

„Due Diligence: Aufgaben der Terminologiearbeit bei Fusionen und Übernahmen“ in: eDITion. Das Fachmagazin für Terminologie 1/2011


Deutscher Terminologie-Tag e.V. – www.dttev.org

Zielsetzung: durch Beratung und Koordination sowie durch die Veranstaltungvon Symposien und Workshops zur Lösung fachlicher Kommunikations-probleme beizutragen.

14. DTT-Symposion: Mannheim Dorint Hotel, 27.-29. März 2014

DTT-Seminare: s. Web-Seite

Das Terminologiemagazin –erscheint 2x Mal im Jahr


Contact information for further questions

Mark D. ChildressSAP Language ServicesSAP AGDietmar-Hopp-Allee 16D-69190 [email protected]


Questions?


Thank you!


RUNBETTER WITH

AppendixCorporate profile (the longer official version)

SAPterm information for those with SAP system access

Driving Business Innovation through Radical Simplification

2014


75%of global workforce

will beMillennials

We are entering into a new era of unprecedentedchange across a multitude of dimensions

5 billionpeople worldwide

will becomemiddle class

50%of the world’s population

will live underwater shortage

1.3 billionusers on business & social

networks today

50 billion connected devices and

“internet of things” by 2030


These changes unveil new areas of opportunityfor businesses to innovate and grow

Hyper-personalizeCustomer Experience

Plan & optimizeResources in Real-time

Engage & empowerWorkforce of the Future

Harness the intelligence ofNetworked Economy


Cloud

Abundance of cost-effective computational

power and storage

Mobile

The new de facto standard in business

interaction

Disruptive technologies offer significant potential to drive business innovation

Social

Connected businessand social networks

Big Data

Real-time analyticfor behavioral and predictive insights

More than 60% of CEOs expect 15-50% of their earnings growth in the next 5 years to come from technology-enabled business innovations.– McKinsey study, 2013 ”“


40% executives worry that their organizations will not keep pace with technology change and lose their competitive edge.

– McKinsey study, 2013”“

Drive business innovation

Keep the lights on

Technology Stackof multiple layers of hardware & software

User Experiencethe ability to engage customers and users

28%

72%

Drive business innovation

Keep the lights on

Consumptionof new technologies to differentiate

Forrester IT Survey, 2013

Complexity built up over decades hampers the ability to innovate; radical simplification is needed to unlock the potential.


Our Visionhelp the world run better and improve

people’s lives.

Our Missionhelp organizations become best-run

businesses.

Our Passionsteamwork, integrity,

accountability,professionalism,

and trust.

At SAP, we help accelerate business innovation through radical simplification


SAP HANA Platform

Simplify your technology stack with the SAP HANA platform

Applications Analytics

Insight to ActionContextual. Real-time. Closed-loop.

Faster Process massive amounts of data, and deliver information

at unprecedented speeds

SmarterRethink and envision entirely new ways and applications to

run your business

SimplerDramatically simplifies complex and expensive

IT architectures


Simplify your user experience with a mobile-first experience

Mobile First Experience

SAP HANA Platform



Simplify consumption with SAP cloud, powered by SAP HANA

Public Cloud

Human ResourcesCustomersSuppliers


SAP HANA Platform

Managed Cloud

Business SuiteBW

Marketplace

HANA cloud appsPartner ISV appsApplications Analytics


With our open platform, thousands of partners and startups are bringing more innovations to you faster than ever

SAP HANA Platform



Partners&

Startups

1,200HANA startups

2,000Software & tech

partners

3,000Service partners

4,000Solution resellers


We combine our technology innovations and business expertise into a complete solution that best meets your needs

Design ThinkingValue Engineering Services & SupportIndustry Expertise

UX

For 11 lines of business For millions of SMEsFor 25 Industries For consumers

POV Example Solution Explorer


With our solutions, you can focus on driving immediate business outcomes across key priority areas

Customer Experience

71% business leaders believe that customer experience is the next battleground

Employee Engagement

3x higher operating margin thanthe ones with poor employee engagements

Resource Optimization

60% increase in operating margin in retail leveraging Big Data as the new resource

Networked Economy

Networked enterprises are 50% more likely to have higher sales & margins

BusinessOutcome


SAP Predictive Analytics SAP Mobile solutions

Seamless experience acrossmultiple channels

Co-innovation and co-creationwith customers

Hyper-personalization usingcustomer insights

Helping you reimagine your customer experiences like never before.

SAP Cloud for Sales

Learn More


Enabling you to engage and empower yourpeople at scale.

SAP Cloud for HRSAP Social Media Analytics by NetBase

Embrace social savvymillennial workforce

Transform the way you recruitand manage talents

Empower & engage peoplewith real-time information

Learn More

SAP Predictive Analytics


Empowering you to manage, predict and optimize resources in seconds.

SAP HANA Enterprise CloudSAP Business Suite on HANA

Data as the biggestnew resource

Turning productsinto services

Real-time resource planning& optimization

Learn More

SAP Predictive Analytics


Enabling you to harness the intelligence of your business networks

Explore the potential of“commerce graphs”

Networked visibility& intelligence

Networked collaboration& innovation

“We can’t predict what, where, or when disasters will happen. We have to manage it regardless.”

Jill BossiAmerican Red Cross

Ariba Supplier Network SAP Business Suite SAP Predictive Analytics

Learn More


For over 40 years, SAP has helped businesses run better and improve people’s lives everywhere

At the global level

Helping customers optimize resources

and protect the environment

At the business level

Helping companies harness data to stay ahead of change and innovate for growth

At the personal level

Helping people havea greater voice and

live better livesby personalizing

engagement

74% of the world’s transaction revenue touches an SAP system.

SAP mobile solutions reach 97%of the world’s mobile subscribers

via text messaging.

SAP customers represent 98%of the top 100 most valued brands

in the world.


We practice what we preach.Every day.

We deploy 25,000smartphones, and 14,000 tablets to

employees worldwide.

We believe creativitydriven by diversity of

thought is critical to our business. Attracting the

most diverse talent guarantees a rich pipeline

for future innovation.

We provide the freedom to perform and are seen as an

employer of choice. Our retention rate is 94%.

We made €16.1 million social investments in 2011to create lasting change, in projects and communities

around the world.

Learn More


SAPterm: Initial screen


© 2014 SAP AG or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG or an SAP affiliate company.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG (or an SAP affiliate company) in Germany and other countries. Please see http://global12.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

National product specifications may vary.

These materials are provided by SAP AG or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP AG or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP AG or SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

In particular, SAP AG or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and SAP AG’s or its affiliated companies’ strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP AG or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.


© 2014 SAP AG oder ein SAP-Konzernunternehmen. Alle Rechte vorbehalten.

Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrückliche schriftliche Genehmigung durch SAP AG oder ein SAP-Konzernunternehmen nicht gestattet.

SAP und andere in diesem Dokument erwähnte Produkte und Dienstleistungen von SAP sowie die dazugehörigen Logos sind Marken odereingetragene Marken der SAP AG (oder von einem SAP-Konzernunternehmen) in Deutschland und verschiedenen anderen Ländern weltweit.Weitere Hinweise und Informationen zum Markenrecht finden Sie unter http://global.sap.com/corporate-de/legal/copyright/index.epx.

Die von SAP AG oder deren Vertriebsfirmen angebotenen Softwareprodukte können Softwarekomponenten auch anderer Softwarehersteller enthalten.

Produkte können länderspezifische Unterschiede aufweisen.

Die vorliegenden Unterlagen werden von der SAP AG oder einem SAP-Konzernunternehmen bereitgestellt und dienen ausschließlich zu Informations-zwecken. Die SAP AG oder ihre Konzernunternehmen übernehmen keinerlei Haftung oder Gewährleistung für Fehler oder Unvollständigkeiten in dieser Publikation. Die SAP AG oder ein SAP-Konzernunternehmen steht lediglich für Produkte und Dienstleistungen nach der Maßgabe ein, die in der Vereinbarung über die jeweiligen Produkte und Dienstleistungen ausdrücklich geregelt ist. Keine der hierin enthaltenen Informationen ist als zusätzlicheGarantie zu interpretieren.

Insbesondere sind die SAP AG oder ihre Konzernunternehmen in keiner Weise verpflichtet, in dieser Publikation oder einer zugehörigen Präsentationdargestellte Geschäftsabläufe zu verfolgen oder hierin wiedergegebene Funktionen zu entwickeln oder zu veröffentlichen. Diese Publikation odereine zugehörige Präsentation, die Strategie und etwaige künftige Entwicklungen, Produkte und/oder Plattformen der SAP AG oder ihrer Konzern-unternehmen können von der SAP AG oder ihren Konzernunternehmen jederzeit und ohne Angabe von Gründen unangekündigt geändert werden.Die in dieser Publikation enthaltenen Informationen stellen keine Zusage, kein Versprechen und keine rechtliche Verpflichtung zur Lieferung von Material, Code oder Funktionen dar. Sämtliche vorausschauenden Aussagen unterliegen unterschiedlichen Risiken und Unsicherheiten, durch die die tatsächlichen Ergebnisse von den Erwartungen abweichen können. Die vorausschauenden Aussagen geben die Sicht zu dem Zeitpunkt wieder, zu dem sie getätigt wurden. Dem Leser wird empfohlen, diesen Aussagen kein übertriebenes Vertrauen zu schenken und sich bei Kaufentscheidungennicht auf sie zu stützen.

Documents

Originally Systems, Applications and Products in … · CO-OM-CCA / Cost Center Accounting SAP ERP Operations India Localization for SAP ERP Software component version = Product instance