SlideServe
Télécharger Obtenir Pro
Menu
Accueil Pro
Préférences
ApparenceLight Aide et commentaires
© SlideServe · v2026

CMS at St. Jude Medical: An implementation case study

jaime-mcdowell avatar
jaime-mcdowell
11 diapositives · 323 Views · Nov 18, 2014

CMS at St. Jude Medical: An implementation case study. Brenda Inman St. Jude Medical. Why was SJM looking for a Content Management System?. Increased workload NO increase in head count

#cms at st. jude medical: an implementation case study #cms at st. jude medical: an implementation case study ppt #powerpoint #presentation
CMS at St. Jude Medical: An implementation case study - slide 1
01 / 11CMS at St. Jude Medical: An implementation case study
1 / 17

Télécharger la présentation

CMS at St. Jude Medical: An implementation case study
Une image / un lien ci-dessous est fourni (tel quel) pour télécharger la présentation

Politique de téléchargement : le contenu du site vous est fourni TEL QUEL pour votre information et votre usage personnel ; il ne peut être vendu, concédé sous licence ni partagé sur d’autres sites sans l’accord de son auteur.Le contenu vous est fourni TEL QUEL, pour votre information et votre usage personnel uniquement. Téléchargez la présentation en cliquant sur ce lien. Lors du téléchargement, si vous ne parvenez pas à télécharger une présentation, l’éditeur a peut-être supprimé le fichier de son serveur.Pendant le téléchargement, si vous ne parvenez pas à obtenir une présentation, le fichier a peut-être été supprimé par l’éditeur.

F I N

Plus de contenu associé

Transcription de la présentation

  1. CMS at St. Jude Medical: An implementation case study Brenda Inman St. Jude Medical

  2. Why was SJM looking for a Content Management System? • Increased workload • NO increase in head count • FrameMaker had been pushed to its limits with conditional text to achieve a pseudo “single-source” environment • Increased pace of manual releases to the point that 2+ writers were working on versions of essentially the same manual • Enormous DTP costs of localized manuals($10 per page just for DTP work)

  3. How did SJM choose a Content Management System? • Key Questions • What does a CMS mean to us? • Would a CMS solve our current challenges? • Would migrating to a CMS be more trouble than it was worth? • Genesis Methodology • Plan / Analyze / Design / Develop / Implement • Why Author-it? • Cost • Satisfied our needs • Minimal customization

  4. Author-it Overview • What is Author-it? • A content management system • An authoring tool • Localization coordination tool • A single-source publishing tool

  5. Author-it Overview • Author-it Components • Core - The authoring tool • Import - Import existing/legacy content from a variety of sources such as MS Word, Rich Text, FrameMaker, WinHelp, RoboHelp, HTML Help, HTML, and XML • Localization Manager - Manage updates to the language libraries and create translation jobs • Author-it Live - Web-based Author-it for authoring with limited functionality

  6. Benefits of Author-it • Authoring • Which files are the most current files? • Who worked on the most current files? • What should be included in this manual? • Enables better collaboration • Ease the time and effort it takes to make “global” changes • Allows for a more consistent message across manuals • Localization • Reduce effort • Reduce time • Reduce cost

  7. Author-it Implementation • Installation of Hardware & Software • SQL Server - Production database AND development database • Citrix Access to Author-it - Citrix is a web-based system that centralizes applications for remote access to applications • Desktop Application • Share Server - A server location for shared templates, language libraries, and additional supporting pieces for publishing

  8. Author-it Implementation • Develop Templates • Customize templates to fit the SJM Corporate style guide and specific language requirements

  9. Author-it Implementation • Pilot Project • Xxx languages • Xxx localization vendors • Describe workflow

  10. Author-it Implementation • Develop SJM Process & Procedures • Document the process that makes Author-it work to meet SJM requirements • Administrator • Writer • Localization • Template Developer

  11. Author-it: Where are we now? • Publish for print (Word > PDF) • Automation is still needed to format tables and graphics properly for page size • Publish for HTML • SJM requires “old style” HTML (v1.0) – NO cascading style sheet (CSS) • Author-it produces “current day” HTML (v5.0?) – uses CSS • SJM utilizes a script to strip out CSS references and imbed formatting information from CSS directly into HTML code