You commit the last XML file you were editing and decide to take a quick break. You stretch your legs down to the breakroom before returning to your desk, coffee and donut in hand.
As you plop down on your chair, you open your email.
A new Windchill notification arrived while you stepped out of your cube. A change has occurred upstream that impacts the content your role manages.
In Windchill, you view the CR and learn one of the engine hoses has been replaced in the design. The impact analysis indicates this affects your remove and replace and troubleshooting procedures, as well as preventative maintenance and parts lists sections.
From Windchill, you review the list of affected service content for the CR and launch each of the impacted XML files in Arbortext.
The logistics engineer has already updated the affected parts lists.
The illustrator responsible for the technical illustrations included in your sections has already updated the illustrations for the change and committed them to Windchill, so you see the accurate, updated versions in your XML.
You don’t have to harass engineers for changes or ping illustrators for new images; you are just responsible for ensuring the verbiage in each file reflects the change.
You update and commit each file to Windchill.
The change has been fully integrated into the service content. At this point, after the updates are reviewed and approved through their workflow, you republish any manuals that contain the updated sections and push them out for delivery to the field.