Managing XML documents in a content management system (CMS) is not a new technology. It’s been commercially available in various software products for over 20 years. Most do a great job of doing those things we have come to expect from a CMS: granting/denying access, checking objects in/out, identifying who did what when, and automating workflow processes.
With the right CMS, there is so much more you can do. Before getting into all that, first let’s define XML awareness.
What is XML Awareness?
XML uses plain text to define rules and describe a structure that organizes document content. It is intended to be human-readable and machine-readable. Images and other content types are included by reference; they are not part of a self-contained file that is typical of many proprietary desktop publishing solutions. When processors and applications understand how to parse and validate XML markup, they are XML-aware. This means the system can process relationships for referenced content types to construct intelligible documents and publications from the data stream.
When a CMS Has XML Awareness
When a CMS has XML awareness, it can create objects based on XML element names and attribute values. For example, every section or caution or table in an Arbortext document can become an object in the CMS. This provides the ability to slice and dice content into objects that are reuseable in publications throughout the system.
We’ve spelled out how a CMS with XML Awareness enables users. Now let’s look at a CMS without XML Awareness.
When CMS is Not XML Aware
Conversely, an XML-unaware CMS can manage XML as binary files rather than a standardized way to structure and store content. An XML-unaware system can upload and download individual XML files or groups of text and images in a folder or zip file; however, it cannot process relationships for files that are included by reference.
Beyond Object Reuse: Windchill Service Information
As mentioned in the introduction, the right CMS can enable users with more than XML awareness or Arbortext content management.
Beyond object reuse, Windchill Service Information enables applying filters to content structures to show objects that are specific to a certain product configuration and hide objects that do not apply. This filtered, structured view of objects can then be published to create a PDF or HTML or other output formats for consumption by end users.
Let’s dig into the more of Windchill Service Information.
Content Aggregation Via Windchill Service Information
Windchill Service Information adds a whole new dimension to content aggregation. For one, objects that meet the selection criteria are assembled to create publications. From one structure, you can produce many variations of a service manual using classifications that pertain to your business. That could include anything from engine types and electrical voltage to colors and sizes, from different materials to other brand variations. Content objects that depend on variables, whatever they may be, can be included or excluded from the data stream so that published content is adapted to the end item.
Applying BOM Strategy to Service Information Via Connected Data
If you have overloaded BOMs for design engineering drawings or options built into your product marketing configurations, then you might already have the hard part done. Applying the same strategy to service information is a matter of connecting the dots.
We understand the connections and relationships between PTC products and Arbortext service information. Were here to provide our expertise, helping you exploit the products and achieve the best results to meet your business needs.
Now let’s consider another, less-standard-but-important feature: Translation Management.
Translation Management
Translation Management is another gray area in the XML-aware CMS product space. This is not a standard content management feature so if you are shopping for products, be sure to ask if translations are supported. Windchill Service Information does include translation management for Arbortext content. This feature is also a great way to justify a new software expense because effective translation management often generates more revenue than it costs.
Next Steps
XML-aware CMS platforms enable structured, reusable content by managing XML at the element level rather than as static files. Windchill Service Information builds on this by filtering and assembling content based on product configurations to produce tailored service publications. Together with built-in translation management, these capabilities help organizations scale documentation efficiently, reduce duplication, and deliver accurate, localized content with greater business impact.
When using structured content, it is important to maintain good XML practices. Mixing XML-aware and -unaware applications can compromise the ability to exchange and use the information to its full potential.
Additionally, Service Parts Information and Instruction (SPII) is an optional add-on to PTC’s Windchill PDMLink. PTC’s Arbortext product suite has built-in interoperability with Windchill SPII and XML-aware capabilities that are insurmountable.
Looking for more information on Arbortext, Windchill Service Information, or Technical Publication services? Explore the topic on our blog to learn more!
