Features

This section provides a brief overview of each of the main features of the Technical Documentation Framework with links to associated sections for more information.

Technical Documents can exist either as a single entity - with all content contained within – or aggregate content from multiple document components. Breaking up documents into smaller components has multiple advantages including the ability to:

1. Reuse each component.
2. Enable concurrent editing.
3. Apportion each component to areas of specific specialty or expertise

In the Technical Publication domain, technical content is sometimes referred to as ‘Topics-based’ or ‘Modular’. This refers to content that is about a specific topic or area of focus and is, to some degree, context insensitive. This helps to characterize the content and enable it to exist in multiple places within a document. Contrast this with a narrative in other forms of documents where every paragraph builds upon (and thus depends on) previous paragraphs and context. Each Technical Document instance can evolve independently and be protected by specific access rights. To be reusable, each document component needs to be constructed in a way that allows it to fit within a larger context. To achieve this, the content of each Document / Document Component will be based on an overarching schema or document structure (see section Creating Documents). This document structure helps ensure consistency and provides a mechanism for determining how individual components can fit into a larger context.

The style and layout of Technical Documents is dictated by a separate style configuration that is maintained separately but associated directly with a Technical Document Type definition. Each Document Element defined in the Schema can be referenced and have a unique set of styling parameters that are used to position and render the associated Document Element instances in each document. Style settings can be assigned to HTML output, PDF Output, and the Document Editor. Referencing centrally controlled style settings ensure consistency in look and feel for published content and provides a convenient mechanism to update style in one location and have it automatically apply to all associated documents.

All Document Element content can have additional metadata information assigned to provide semantics for content classification and aid in content search and retrieval. This metadata is provided by the Technical Document Administrator when the Document Structure is designed and configured.

Technical Documents can have explicit relationships created with other Items maintained in Innovator – Business Objects (see section Creating a Link to a Document Element). This relationship establishes a direct binding between the document and associated Business Objects. In addition, property data from these Business Objects can be queried and used within the Technical Document (see section Automated Content Generation using Methods). When the Business Object property data is updated, the associated Technical Documents are updated accordingly. This binding helps maintain data integrity and identify a hard link across Objects and the documentation that was created specifically for them.

Technical documentation content should evolve as the information it references evolve. Typically, product information does not change substantially between versions. As a result, documentation about each version should conserve and reuse all that is common and identify the areas that are unique to one or more product versions. The Technical Documentation Framework provides a mechanism to tag elements within a document with one or more characteristics, a particular version or model number for example. These characteristics can then be used to filter (see section Filters) document content to only display or include information that is relevant.

The Technical Documentation Framework, together with Aras Innovator, provide an authoring and data management environment. To make use of the content created, it needs to be exposed outside the PLM environment. The publishing/export function (see section Publishing / Exporting) provides an ability to convert the content of each Technical Document to a format more suitable to end-user consumption.