The APS Publishing Engine
Publishing automation
Catalogues, gazettes and price lists build themselves from your data.
Publishing automation builds documents from structured data instead of by hand. The APS Publishing Engine, which APS built, reads your data once and republishes every page automatically. At Government Printing Works it cut a 15,000 page publication from two weeks to 45 minutes, and Ster-Kinekor cut catalogue production from three days to three hours.
The situation
- Catalogue production takes weeks.
- Design teams spend most of their time updating layouts by hand when products change.
- Errors creep in and deadlines slip.
- A misprinted price you are legally obligated to honour.
What we do
Structured data in
ERP, PIM, spreadsheets
APS Publishing Engine
InDesign Server + EasyCatalog
Paginated document out
Every page updated, nothing retyped
Built on Adobe InDesign Server and EasyCatalog, the APS Publishing Engine automates high volume document production at volumes most platforms cannot handle.
Where manual layout means retyping and re-checking every update by hand, the Engine reads structured data directly from your systems and rebuilds the document automatically. A price changes once in the source. Every page updates. Nobody retypes anything.
The APS Publishing Engine is our own technology, built by APS.
Adobe InDesign Server EasyCatalog WoodWing Studio PublishOne
Proof client: Government Printing Works
Inside the APS Publishing Engine
Adobe InDesign Server draws the pages, but it needs scripts written for each job before it can do real work. APS wrote those scripts. They accept whatever arrives, extract the content, clean it, lay it out and render the finished pages with nobody watching.
Messy input
Submissions in any state
APS Publishing Engine
Extract
Pull content out of whatever arrived
Clean
Normalise text, strip junk, fix encodings
Lay out
Template-driven pagination via scripts
Render
Adobe InDesign Server, unattended
Runs overnight, unattended
Output
Publication-ready, identical pages
Same engine fits
Any organisation that receives messy submissions and must publish them consistently. Gazettes, legal notices, tender bulletins, classifieds, journals, listings, regulatory filings.
What you get
- Automated catalogue production from product data
- Layout templates that update when data changes
- No manual layout for repeat publications
- Multi-channel output from a single content source
Works well for: Catalogue teams, retail, publishing, marketing production
Proof
Faster publishing
2 weeks45minutes
Production time for a 15,000 page publication at Government Printing Works. Government Gazette, live since 2016.
Faster catalogues
3 days3hours
Ster-Kinekor's catalogue production time, with a 99 percent reduction in human error.
Common questions
How is a newspaper or gazette page automated?
Source data is held in a database or files. Templates take that data and format it into pages. At Phumelela, APS built the templates that format raw horseracing data into its form guides and newspaper racing pages.
How much faster can it be?
At Government Printing Works, a 15,000 page publication went from two weeks to 45 minutes. Results depend on your data and your templates. We scope that with you first.
Does it work for catalogues and price lists too?
Yes. The same approach applies to any document built from structured data. See our retail page for catalogues.
Who builds the engine?
APS. The APS Publishing Engine is our own technology.
Keep reading
Where is the risk in how you work right now?
Tell us how your work moves today. We will tell you honestly whether we can help.
find where work gets stuckJust a conversation, with no obligation.