1. What Capital Publisher Is

Capital E/E Publisher turns engineering designs into service documentation. It takes the logical schematics, wiring designs and harness designs that engineers author in Logic Designer, Systems Integrator and Harness Designer, lets a documentation engineer rearrange and annotate them for technicians, and packages the result as a self-contained viewer that runs with no Capital installation.

This section explains how the pieces fit together. The vendor reference pages it draws on are in the E/E Publisher section of this site; each page here links to the ones it summarises.

The one idea to hold on to

Publisher works on a copy of the engineering data. Renaming a wire, hiding a property, moving a connector or re-styling a diagram in Publisher does not change the engineering design. That separation is the whole point of the product: the service view can be tuned for a technician without risk of altering what engineering released.

The four phases

Phase	What happens	Where it is covered
1. Load engineering data	Import and open a Capital project, or bring in foreign data through Capital Connectors and render it with the Schematic Generator	2. Loading and Preparing Designs
2. Prepare	Partition big diagrams into smaller ones, format them (visibility, fonts, colours, wire colouring, symbol swaps), embellish them with service-only content (service names, notices, comments, tables, translations)	2. Loading and Preparing Designs
3. Generate	A packager writes the documentation package: scope, artifacts, configuration filtering, effectivity	3. Generating Documentation Packages, 4. The Packagers Compared
4. View	Technicians open the package in a browser, a Windows tablet, an iPad, a PDF reader or a CGM viewer	Covered by the separate Exploring Service Documentation guide

What goes into a package

A package combines three kinds of input:

1. Designs from the project, rendered as diagrams (SVG, CGM or PDF depending on the packager).
2. Generated artifacts: wire lists, net lists, BOMs, connector face views, ground reports, cross references, fault code data, "What's In Common" troubleshooting.
3. External resources from a folder you point at when generating: introduction documents, 2D location views (SVG or PDF, auto-linked to object names), training videos, diagnostic data.

What controls how it looks

Almost everything about a package's appearance and content, beyond the diagrams themselves, is driven by XML configuration files in the publisher folder of the Capital installation (or in a central folder named by a system preference). Which attributes appear, the navigation panel order, what each popup shows, PDF page templates, Change Explorer comparison rules and report columns are all file-driven. See 6. The Publisher Configuration Files.

Licensing, briefly

Generation consumes Publisher licences whether it runs interactively or in the background. Two packagers need an additional licence: Capital Design Explorer (to run the viewer) and Capital Change Explorer (to generate and to view). DERIVED from the vendor guide; not exercised on this workstation.