his video goes with the original meeting notice. This video is a recorded version of:

“Managing technical data sets using XML”

Presented by Jonas Härdner, Simonsoft

This is a recorded version of a live Go2Meeting webcast. The video is posted as is. It has not been edited. Every last bit is completely live.

Download the slides (coming soon!) and see the live-tweet roundup.

Managing technical data sets using XML [ 48:45 ] Play Now | Play in Popup

Managing technical data sets using XML [ 48:45 ] Play Now | Play in Popup

Share/Save

Tweet roundup from the March meeting:

“Managing technical data sets using XML”

Presented by Jonas Härdner, Simonsoft

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!

Share/Save

Please join us online for our regular meeting:

“Managing technical data sets using XML”

Presented by Jonas Härdner, Simonsoft

Date: Saturday, 26 March 2011, 9:00-10:30 AM Pacific/US

Location: Online via GoToMeeting. You must Register to receive the GoToMeeting invite.

Cost: Free and open to all who wish to attend.

Product information on a data level is often managed by many different disciplines in a manufacturing company. Marketing looks after Data sheets, R&D has their own data set of product attributes and so on. The information is often stored in different databases or at worst just as a text string in a document.

The challenge is with growing product portfolios, increased regulations and large organizations, to manage this data-set in a single source environment and to be re-used in all depending documentation.

This session will present a possible way to solve the problem using XML and CMS as a single source using different layers of authoring to allow the whole organization to contribute. We also talk about how the data is easily is reused in to the XML based documentation.

Speaker

Jonas Härdner, Simonsoft

Simonsoft is a company who distributes the Arbortext product portfolio to the complete Nordic market. Working with many experienced publishing companies in the Nordic region, we also provide these solutions directly to the end user, in specific cases.

Share/Save