
Single-Sourcing |
#arbortext #ptcuser hearing about challenges at Electrolux – huge amount of data into a small PLM system |

Single-Sourcing |
#arbortext #ptcuser J.Hardner: Synching data from eng, marketing, etc into Reports, web, brochures, dataset tool |

Single-Sourcing |
#arbortext #ptcuser J.Hardner: We used Arbortext for technical docs, but what about the rest? |

Single-Sourcing |
#arbortext #ptcuser J.Hardner: wanted simple, a UI where you couldn’t make errors – special purpose tools or configure Editor to simplify |

Single-Sourcing |
#arbortext #ptcuser J.Hardner: Cost prohibited building a special purpose web-based tool |

Single-Sourcing |
#arbortext #ptcuser J.Hardner: we’re in UAT now, better to get people up and editing rather than holding back b/c unsure |

Single-Sourcing |
#arbortext #ptcuser J.Hardner: driving force behind project was translation: electrolux goes to 28 languages, opening 28 docs ineffective |

Single-Sourcing |
#arbortext #ptcuser J.Hardner: electrolux updated 28 langs every 3 months, and had to recalculate imperial to metric for every change |

Single-Sourcing |
#arbortext #ptcuser J.Hardner: they used to enter all the data by hand in tables + graphic… Now? pull from browsable techdata repository |

Single-Sourcing |
#arbortext #ptcuser J.Hardner: pulled data from techdata repository is “by reference” so updated & converted automatically |

Single-Sourcing |
#arbortext #ptcuser J.Hardner: the tag that decides the language of the document determines whether it shows metric or imperial measurements |

Single-Sourcing |
#arbortext #ptcuser J.Hardner: advantage of using attributes rather than XML entities? helps us build the techdata browser & ACL code |

Single-Sourcing |
#arbortext #ptcuser J.Hardner: did most of the work in 5-10 days |

Single-Sourcing |
#arbortext #ptcuser J.Hardner: no software or anything that isn’t standard, and w/in the API libraries available from Arbortext |

Single-Sourcing |
#arbortext #ptcuser J.Hardner: Now seeing 3 companies doing this.. more and more will follow |

Single-Sourcing |
#arbortext #ptcuser J.Hardner: XML authored docs can reduce translation costs 70-80% |

Single-Sourcing |
#arbortext #ptcuser J.Hardner: We integrated with Assert to get shopping card catalog functionality from the single-source content |

Single-Sourcing |
#arbortext #ptcuser J.Hardner: who’s proofreading? you or your translation house? Taking data out of single-source, then get it back in |

Single-Sourcing |
#arbortext #ptcuser J.Hardner: Electrolux adoption was very quick. W/in weeks. We didn’t migrate old InDesign data, started w/newgen producs |

Single-Sourcing |
#arbortext #ptcuser J.Hardner: Electrolux started with Editor & PDF publishing (1-2 wks), added attributes/metadata/file storage, xml repos. |

Single-Sourcing |
#arbortext #ptcuser J.Hardner: Electrolux project at the end (publishing was 1st)… a number of enhancments: 1-click print 28 docs/langs |

Single-Sourcing |
#arbortext #ptcuser J.Hardner: Electrolux enhancements later on? Automated sending docs to 5 different places w/1-click |

Single-Sourcing |
#arbortext #ptcuser J.Hardner: In Sweden, we’ve been focused on mfg, now see movement in SW. |

Single-Sourcing |
#arbortext #ptcuser J.Hardner: In SW, they’re talking about topics (help topics), and lots of need for consistency bet SW & Docs |

Single-Sourcing |
#arbortext #ptcuser Thanks, Jonas, for such a great presentation! |