An underlying Electronic Document Management (EDM) application may be used in contemporary publishing environments to manage the sheer volume of diverse documents and data throughout the publishing process.

EDM is a powerful technology, especially when integrated with publishing tools. However, a surprising number of publishing environments have not yet embraced it.

The EDM application addresses administrative concerns such as user access to data, check-in/check-out, versioning, where-used, and even workflow, while also providing for the creation and revision of specific metadata associated with individual documents archived in the vault.

EDM Manages Illustration

Although there are numerous variations on the EDM theme, in a conceptual technical documentation workflow, legacy data and completed engineering designs are accessed and repurposed and combined with new art into illustrative product views. These are then incorporated into various forms of product documentation, such as:

• Operational Method Sheets
• Installation Guides
• Operation Manuals
• Service Manuals
• Parts Catalogs

And these publishing projects—involving multiple departments—can be efficiently managed by the enterprise using an underlying EDM as the technical publishing foundation.

The development and maintenance of artwork and documentation throughout multiple revision cycles is critical to an efficient publishing process. Typical elements that must be managed in contemporary publishing environments include:

• Reference data: line art images, sketches, CAD data, legacy art, digital photos, screen captures, video still frames
• Symbol and clip art libraries
• Illustrated components and associated metadata
• Base assemblies common across different layouts
• Service details
• Locators
• Standard page layouts and drawing borders
• Composed illustrations
• Intelligent CGMs (components) and companion XML files (attributes)
• Manuals, sections, chapters, TOCs, indices, appendices
• Style sheets, DTDs, FOSIs, templates, document instances

Effectively managing these diverse publication elements over time prevents loss of data and enables rapid access to data for use in different publications—throughout multiple revision cycles.

EDM Manages Composition

Technical documentation undergoes repetitive revision over time; making effective management of archives a key issue. And finished documentation can take many different forms, utilizing different distribution mechanisms such as hard copy, CD-ROM, Internet and intranet. Popular forms of documentation include:

• The printed page
• Hypertext page-turners
• Hyperlinked electronic books composed of chunked data
• Hyperlinked multimedia comprising text, graphics, animations, video, and sound
• Web site publications made up of the same elements mentioned above
• Interactive Electronic Technical Manuals (IETM)

The last of these examples—IETM—is a complex database-driven form of publication governed by three dovetailing Tri-Services MIL-specs; but the term "IETM" is often mistaken to be synonymous with common electronic book publications.

EDM Manages Distribution

Many times, for many business reasons, a company must distribute an electronic document in multiple forms, such as hard copy and CD-ROM page-turner. This requires considerable up-front planning in terms of the entire publishing process, as well as the overall design of the system configuration.

As publishing requirements become more demanding—largely due to the essential nature of technical information in the organization and the ongoing management of this data—an integrated EDM is emerging as the necessary foundation for automated publishing environments.

To find out more about Auto-trol™ KONFIG® EDM, PDM, and workflow product, visit KONFIG.

Related Information:

• Overview
• Product Editions
• Optional Modules
• TiAuthor
• Data Exchange

Learn more about Auto-trol Tech Illustrator

Product collateral consists of video demos, data sheets, white papers, and industry articles.

Auto-trol™ Ti Demo Downloads

To get full benefit, the recommended viewing order is Overview >12.5.3 >14.0. Each demo is a self-extracting zip file that runs an executable.
Ti Overview
Duration = 30 minutes, Disk Space Required = 180MB
Ti 12.5.3 Highlights
Duration = 28 minutes, Disk Space Required = 24MB
Ti 14.0 Highlights
Duration = 43 minutes, Disk Space Required = 98MB

Data Sheet: Tech Illustrator
Data Sheet: TiAuthor
Data Sheet: MetaWeb (Optional Module)

White Paper: WebCGM: What is it?
White Paper: WebCGM Link and Web Site CM Overview

Operating Environment: System Requirements
Ti and MCAD: How They Work Together
What Makes Ti Unique: The Auto-trol Difference
Tech. Illustration Workflow: Understanding Distinct Phases