This morning on the 3b2users mailing list, Simon Taylor announced the that the M030 release of Arbortext Print Publisher (APP) Version 10 is available on the download site for maintenance customers.

This release sees the following improvements:

• Fixed “Insert Text Counter” dialogue where the “force lowercase” capitalisation option incorrectly appeared as a button. (SPR 1869893)
• Fixed spanspecs when used as the first cell in a line. (SPR 1869427)
• Fixed language selection list (accessed via dialogue from ‘tl’ macro). Problem was caused by reverse look-up of values to names when language names had aliases. (SPR 1869885)
• Fixed issue when jumping to a specific column in a table that is already occupied (SPR 1869465)
• Added new option to the document saving preferences that allows a document to be loaded without automatically going to a page.
• Added new mode to the StripSpace control stream normalize parameter to fix issue with elements within text. (SPR 1878828)
• Fixed issue when using <?tbrfill> and <?tbend 1> together. (SPR 1869465)
• Fixed <?tbrfill> so it fills in gaps in a row even when the cells are specified out of order. (SPR 1869465)
• Fixed potential lockup when prescanning a table that contains a nested table that is rotated (SPR 1854594)
• Fixed fStream.StreamSeekOrigin values to match the code.
• Extended _ex_map functionality to allow .js files to be opened directly in APP.
• Fixed issue with the inter-column gutter rule when breaking across columns and the right hand edge of the line doesn’t match that of the previous line. (SPR 1881644)
• Fixed “Below lowest line” and “Bottom, below lowest” footnotes to behave more consistently like regular “From the bottom, up” footnotes (e.g. being able to split). (SPR 1857906)
• Fixed formatting with contents control stream so it doesn’t hang (broken since v10). (SPR 1868047)
• Fixed footnote reliability when referenced from a frame on a page layer. (SPR 1857886)
• Fixed crash when inline footnotes are used on the same page as balanced text. (SPR 1884484)
• Fixed a VJ issue when a line restarts (for begin/end keep, <?bk>..<?ek> and min orphan word length, <?tporwl>). (SPR 1897432)
• Implemented <?tpkpallmax> overflow option for unsplitable content that is too big (SPR 1849287 and 1735814)
• Fixed crash when generating new style XML index. (SPR 1873381)
• Fixed problem with ttrevout. (SPR 1905266)
• Fixed problem when a change of header occurs at the top of a column and there are 3 levels or more. (SPR 1846121)
• Stopped <?tpfmt 8> from having adverse effects when trying to size-to-fit whilst measuring column widths with a prescan. (SPR 1903991)
• Fixed getvars 21887 and 21888 return the correct position when an XML stream is well formed but validation failed. (SPR 1882829)
• Fixed incorrect vertical justification of a stream caused by the presence of alignment in a different stream on the page. (SPR 1857460)
• Fixed crash with sprint when the first control stream only contains formatting settings. (SPR 1908906)
• Fixed possible crash when printing with an invalid print range. (SPR 1912764)
• Fixed problems with manipulating FOM fLog objects (SPR 1911808)
• Fixed problem where underlines and backgrounds were not stopping when instructed. (SPR 1869888)
• Added support for simplified Japanese numbering scheme (show string $82, format_seq ‘japanese-simplified’) . (SPR 1833219)
• Add new modes to support accolades on the inside or outside, use abolute units, and cooperate better with the block model.
• Fixed issues with importing and linking to external content in FOM (SPR 1914412)
• Fixed internal memory corruption and possible pointer error when using a nested table prescan (SPR 1901310)
• Fixed internal memory corruption and possible pointer error when using <?tbwref> within a nested table (SPR 1901310)
• Fixed regression in PDF bookmark generation intoduced in 10.0 M020, resulting in bookmarks in a potentially erroneous order.
• Added support to allow PDF bookmark generation to collapse missing levels. (SPR 1896026)
• Fixed problem with page sequence commands getting ignored after multiple formats. (SPR 1808146)
• Fixed problem with footnotes not getting blanked properly during a format+print (superprint). (SPR 1736073)
• Implemented Styler leading simulation options, including: <?tbcignrw>, <?tbignrw>, <?tpignrw>, <?tpdtc>, <?talbbx>, <?talglim>, <?talgap>, <?talamaxdt> and <?talamaxdtc>.
• Improved resolution of EPS files when printing to PDF. (SPR 1884524)
• Adding correct FOM frame raster scaling properties. (SPR 1908647)

Learn more about Arbortext Advanced Print Publisher (APP) (formerly, 3B2).

This is the second post in a 4-post series reporting on an interview I did with Greg Johnson from Medtronic. Over the years, Medtronic has increased their investment in their dynamic information delivery system. They have continued to develop it and they have seen their ROI returned again and again.

The Quality Driver

When the FDA audits, they audit manufacturing processes. They want to see the records that you followed those processes. They can go deeper and deeper. They don’t do it often, but they have the right to. Every medtech company lives in fear that the FDA will show up at the door one day and want to see everything. Everything needs to be clean. If you don’t pass, there are triggers that can shut down a business unit or an entire company. The FDA can padlock the front door if they want to.

Medtronic decided that they wanted a system that provided a level of control for information creation and delivery. They wanted the system itself validated: They wanted to validated the tool so they wouldn’t have to validate the content coming out of the tool. They decided that the best way to get that validation on the input side, so they certified the input. They wanted their documentation to be able to pass FDA audit for every change they ever made.

They implemented a system that would meet those requirements. They made sure the system itself was covered, that development was covered, and that staff was properly trained. Today, their system is Part 11 compliant for system security. The documentation team goes through all the same hoops when testing and preparing for audits that the rest of the company goes through.  It’s fair to say that their documentation is being held to a software standard.

Medtronic can prove that information coming out of their dynamic information development system:

• has a documented, approved, assigned, scope
• has defined requirements
• cannot exceed the scope
• has traceability and validation to the defined requirements
• documents produced by the system are held to standard of class 3 device

Although their main driver was quality, they’ve proven that they got that and more. In fact, because they left traditional publishing tools like Word and FrameMaker, they got all of the big three benefits in one package: increased quality, reduced cycle time, and reduced cost. As far as I know, there’s no one like them in all of Medtech.

Next: The Time to Market Driver

Previous: Benefits of dynamic information delivery for life sciences

The latest PubWright Podcast has been posted to here and on iTunes here.

This week’s podcast features Todd Hicks from Wolters Kluwer.  Todd Hicks has been an Arbortext community member for a long time. He’s presented at AUGI and at PTC/User conferences. He’s built custom applications and extensions to Arbortext that even PTC wanted (then developed).  Todd and his team at WK is always doing something special, innovative, and technically spectacular.

Just before the holidays, I saw the following in Forbes:

Recent research conducted by Washington, D.C.-based Corporation for National & Community Service reveals that charitable work literally makes the heart grow stronger. Individuals with coronary artery disease who participate in volunteer activities after suffering a heart attack report a reduction in despair and depression, and that, in turn, rives down mortality and adds years to life. It’s also true that those who volunteer have fewer incidents of heart disease in the first place.

[...]

Research from the Center for Work-Life Policy shows that high-potential employees–mostly women but also a significant percentage of men–are seriously motivated by a desire to give back to the world and increasingly seek out employers that allow them to participate on company time.

It reminded me of another article I’d seen earlier this year and meant to write a post on:

her answer to why women volunteer was simple and sweet: “We volunteer because we get back more than we give.” And then she added the kicker: “You feel better about everything because you are part of something bigger than yourself.”

When we upgraded the website, I posted on how much Single-Sourcing does for the community. I personally participate in every single one of those efforts. I also volunteer elsewhere: I’ve been an officer of the SF Bay Peninsula chapter of the ACM (founded in 1957) for over a decade and an officer or committee member of two other chapters nationwide.

Things you can do:

1. Submit a paper for PTC/User conference
2. Volunteer to present to the SF Bay Arbortext PTC/User Group
3. Ask a question — or answer one!:
   • On the Adepters Mailing List
   • On the 3b2users mailing list
   • In the MathCad forms at PTC
   • In the IsoDraw forums at PTC
4. Join the Arbortext Technical Committee
5. Volunteer to be interviewed for the PubWright Podcast
6. Submit code to the Adepters Code Archive
7. Comment on a community blog:
   • this blog
   • Comment on Structured Authoring blog
   • our blog at dita.xml.org
8. Follow or send a tweet to
   • adepters group tweet
   • SingleSourcing
   • Arbortext folks on twitter: SingleSourcing/arbortext
9. Join an online group at LinkedIn or Facebook:
   • the Arbortext PTC/User Group on Facebook
   • Join the 3B2 Rocks User Group on Facebook (3B2 is the former name of APP)
   • Join the Arbortext PTC/User Group on LinkedIn
10. Start something and tell us about it!

Other users really do want to hear from you. We’re a tight community, always have been. If you’d like an introduction, you should follow us on Twitter here and you’ll know everyone soon.

I was fortunate enough to reconnect to an old friend. I reached out to Greg Johnson from Medtronic and had an amazing conversation about their dynamic information delivery system.

Medtronic implemented Arbortext in 1999. They have been the subject of a case study and a customer success story. I’ve seen them present at the Arbortext user conferences (AUGI) over the years. In fact, I never missed one of Greg’s AUGI presentations. I learned a lot from them in the early days and I still have his slides on my computer.

It wasn’t so much that I wanted to do what they did — I had to do what was best for my situation — but I could see what was possible, where I could go, and at least one way to get there. I always left inspired by the possibility and exhausted by the prospect of the work ahead.

Greg still presents at conferences world wide. And he will be the first to tell you not to do what they did. Technology has changed, your goals are your goals, your capabilities are your own as well. But definitely join the conversation. The payoffs really are this great. The implications of moving to this kind of system are way bigger than you can imagine.

It was great to catch up with Greg. Over the years, Medtronic has increased their investment, continued to develop, and seen the ROI returned again and again. It was great to see that the payoff is definitely there — and that it continues to be there if you keep at it.  It was also humbling because this is not a short path, it is a long, long journey to get there. It’s good to know that if you keep at it, your ROI build upon itself every step of the way.

After 10 years, their project has started to reach out to:

• software objects and applications
• specifications that need to be published
• technical services
• training and education

They’re still driving toward cradle to grave information development. As a medical device company, they chose to take their project down a difficult road: they wanted to have their dynamic information development system validated as if it were, itself, a Class 3 Medical Device. They wanted to validate the content coming out of the tool so that their information development would pass FDA audits.

He said that XML publishing addresses three main points essential for Life Sciences companies and anyone interested in producing efficient technical publications:

• The Quality Driver
• The Time to Market Driver
• The Cost Savings Factor

I’ll be addressing each one of these in the posts to come so everyone can learn from what they’ve achieved at Medtronic.

Greg says, “You don’t want to do how/what we did. It’s 10 yrs later. But I want to encourage you. There are vast savings and vast reductions in cycle time and vast improvements to do in this field, if you do it smart, build your vision, and go be passionate about it.”

Next: The Quality Driver

The latest PubWright Podcast has been posted to here and on iTunes here.

This month, the focus is on Robin Sloan from PTC. Robin was a part of the original Arbortext team before the acquisition of Arbortext by PTC.  Robin is a Product Manager in the Arbortext business unit at PTC. She was part of Arbortext prior to the acquisition. Robin was integral in designing the modularity of the DITA stylesheets that ship with Arbortext Editor, Styler, and Publishing Engine. PTC still maintains a DITA mailing list that Robin answers.

Link.

There’s still some time to get your presentation ideas in. The conference has improved year-over-year since AUGI became PTC/User due in large part to the folks who present and participate. Every year has been better than the last. More people submitted presentations than the year before which was more than the year before that.

The conference is the best place to connect with the others in the Arbortext community. If you’re worried about travel budgets, submit an abstract anyway. Presenters attend free. Better to have the option later on. Come and tell us what challenges you had and what you did to solve them. Tell us what goals you had when you started and where you’re going next.

Please consider sending an abstract.

We want to hear your story.

To submit an abstract, please go to the abstract submission form on the PTC/User member portal (login required).

See the writeup about last year’s conference.