4. The Packagers Compared

A packager decides the output format and the viewer. Everything upstream (designs, style sets, embellishments) is shared; the packager chosen at generation time decides what comes out.

Packager	Output	Viewed in	Extra licence	Main config files
Capital Service Explorer	Interactive HTML package with Lean SVG diagrams	Any web browser; Windows tablet	No	config.xml, attributeList.xml, NavigationPanel.xml, popup.xml, publisher_report.xsl, server-config\service-explorer.xml
Capital Design Explorer	Licensed executable that spawns a self-contained viewer, for internal use	The generated viewer	Yes, to run it	as Service Explorer, plus server-config\design-explorer.xml
Capital Change Explorer	Stand-alone comparison of two design versions, showing additions, deletions and changes	Web browser	Yes, to generate and to view	changeExplorer\config.xml, changeExplorer\comparisons.xml, changeExplorer\reports\*.xml, server-config\change-explorer.xml
PDF Packager	One PDF package, folder structure matching the scope, with off-page references you can follow	PDF reader	No	pdf\pdfConfiguration.xml, pdf\a4LandscapeTemplate.xsl, pdf\a4PortraitTemplate.xsl, pdf\html_to_fo.xsl, pdf\fop.xconf
Smart Flow Packager	Hierarchical, visual work-flow packages linking to PDFs, videos, help and web pages	Web browser	No	SmartFlow\NavigationPanel.xml, SmartFlow\attributeList.xml, SmartFlow\popup.xml, server-config\smart-flows.xml
S1000D Packager	S1000D data modules: a CGM per wiring schematic plus wiring XML per system	S1000D publishing systems	No	S1000D\CONTROL.xml and the *Map.xml / *Hdr.xml mapping files
Mobile Packager	One service documentation .xml per diagram	iPad (iOS 7 and later)	No	shared attribute and popup files
CGM Packager	One CGM file per diagram, with attributes and cross references	Any CGM viewer	No	config.xml (greyscale switch)

The "Main config files" column is from the files that ship in the install's publisher folder and the packager pages that name them. It is DERIVED: which file each packager actually reads at run time was not traced on this workstation.

Picking one

• Technicians in the field, no Capital installed: Service Explorer.
• Engineers inside the company who want the same interactivity: Design Explorer.
• "What changed between revision B and C?": Change Explorer. It is also the packager most worth automating on a trigger such as a release level change (see 5. Background Generation with FEM).
• A document that has to be printed, filed or emailed: PDF.
• An aerospace or defence publication chain: S1000D.
• A guided repair procedure: Smart Flow.

Vendor pages

ee-publisher/: Capital Service Explorer, Capital Design Explorer, Capital Change Explorer, PDF Packager, Smart Flow Packager, S1000D Packager, Mobile Packager, CGM Packager, Effectivity Aware Capital Service Explorers.