AFP (Advanced Function Presentation)

History

AFP originated at IBM, with the first specifications and products dating to 1984. It was initially known as Advanced Function Printing; the wording later broadened to Advanced Function Presentation as the architecture grew beyond driving printers into general document interchange and archival. Both expansions appear in IBM and AFP Consortium materials, and the change is best understood as an evolution of a single architecture rather than two separate products.

The Intelligent Printer Data Stream (IPDS) was likewise introduced by IBM around 1984 as part of the AFP architecture. AFP was subsequently positioned within IBM's Systems Application Architecture (SAA) strategy after SAA was introduced in 1987. The technology grew out of IBM's high-speed page-printing hardware lineage: the IBM 3800 laser printer line was foundational hardware that predated the formal AFP data-stream architecture, and the IBM 3820, announced February 12, 1985, is cited as IBM's first AFP cut-sheet printer. The core concepts — object-driven structures, print integrity, resource management, and support for high print speeds — have been preserved since inception.

Beginning in the mid-2000s, IBM opened the architecture. In October 2004 IBM initiated the AFP Color Consortium (AFPCC); in May 2006 it announced opening the AFP architecture to a consortium, finalized in September 2006 as the AFP Consortium (AFPC). In June 2007 IBM's stewardship role passed to the InfoPrint Solutions Company, an IBM–Ricoh joint venture, and subsequently to Ricoh. In February 2009 the AFPC was incorporated as a formal standards body, reported at the time as having over 35 member companies.

What problem it solved

Enterprises in the mainframe era needed to print enormous volumes of variable-data documents — bank statements, utility bills, insurance policies, invoices — reliably, at high speed, with mixed content precisely positioned on the page. Line-oriented printer data streams could not express arbitrary page composition, and they offered no guarantee that every page printed exactly once and correctly. AFP addressed three needs simultaneously:

• All-points addressability — the ability to place any element (a pel, or picture element) at any coordinate on the page, mixing fonts, images, graphics, and electronic forms freely, instead of being confined to fixed print lines.
• Print/output integrity — closed-loop, page-level accounting between host and printer, so that in a run of millions of pages each page is accounted for and recoverable after a jam or failure, which is critical for legally and financially sensitive documents.
• Resource management and device independence — describing documents against reusable, downloadable resources (fonts, overlays, page segments) so the same document can target different devices without being re-authored.

How it works

A MO:DCA document is a sequential, ordered hierarchy of independent, self-delimiting objects: documents, pages, data objects, and resource objects such as fonts and ICC color profiles. Each object is bracketed by begin/end structures, and objects to be rendered carry their presentation parameters and resource requirements in structures called environment groups.

Content itself is carried in specialized object content architectures (OCAs):

• PTOCA — Presentation Text Object Content Architecture (text)
• IOCA — Image Object Content Architecture (raster images)
• AFP GOCA — Graphics Object Content Architecture (vector graphics)
• BCOCA — Bar Code Object Content Architecture
• FOCA — Font Object Content Architecture (font resources)
• CMOCA — Color Management Object Content Architecture
• MOCA — Metadata Object Content Architecture

AFP can also carry externally-defined object types (for example TIFF, GIF, JPEG, EPS, and PDF) as embedded object-container data.

To print, a print server — historically IBM's Print Services Facility (PSF) — consumes the MO:DCA document plus its resources and generates an IPDS command stream for the target device. IPDS is a bidirectional protocol rather than strictly a page description language: it streams page-level data and control commands to the printer (font, overlay, and page-segment download; duplexing; media-bin selection; finishing) and receives back acknowledgements, error conditions, and accounting information, enabling closed-loop output integrity.

Where it sits in the print/document pipeline

The flow runs from an application (a composition tool or program) to a MO:DCA-P data stream plus referenced resources, to a print server such as PSF or InfoPrint Manager, which produces an IPDS command stream sent to an IPDS-capable printer or presentation device. Status, accounting, and error signals flow back upstream over IPDS.

In short, MO:DCA is the interchange and archival layer describing what the document is, while IPDS is the runtime device-control layer governing how it is presented and confirming that it was.

Relationship to printers

IPDS is designed to control all-points-addressable (APA) page printers, from LAN-attached workstation printers to high-speed, high-volume production presses and mailroom systems. Because IPDS is bidirectional, the printer is an active participant: it reports resource state (such as available memory and resident fonts), acknowledges pages for accounting, and signals exceptions. Many production printers implement IPDS natively; printers without native IPDS support can be driven through transforms or software raster image processors.

Relationship to operating systems

AFP is historically rooted in IBM host platforms. Print Services Facility (PSF) is the licensed program that links application programs to presentation devices, and IBM shipped platform variants including PSF/390 (PSF for z/OS), PSF/VSE, PSF/6000 (AIX), PSF/400 (AS/400 and IBM i), and PSF/2 (OS/2), later consolidated commercially under InfoPrint Manager.

AFP is thus tightly associated with z/OS mainframes and IBM i. The architecture itself, however, is device- and application-independent, and it is implemented across Windows, Unix/Linux, and cross-vendor tooling today.

Relationship to PDF / PostScript / drivers

AFP occupies a role comparable to PostScript and PDF — a device-independent page and document description — but it was engineered for a different problem: industrial-scale, integrity-critical variable-data production rather than general desktop publishing. Key contrasts:

• PostScript is a programmatic page description language interpreted at the device; PDF is a fixed, final-form document format; MO:DCA is an object-structured, resource-referencing data stream optimized for streaming and reuse across very large print runs.
• IPDS versus drivers: IPDS replaces the conventional print-driver abstraction with a standardized bidirectional device protocol that provides page-level acknowledgement — something PostScript and PDF workflows do not natively provide.
• Interoperability with PDF is formalized in ISO 22550 (Document management — AFP interchange for PDF), which specifies MO:DCA as a container able to include single- and multi-page PDF objects, targeting workflows where final production is managed in an IPDS environment. AFP toolchains also embed and transform PDF and PostScript objects and can transform to and from PDF.

Modern use

AFP remains a cornerstone of enterprise transactional and variable-data printing and of electronic document and content-management archives. It is heavily used in banking, insurance, telecommunications, and utilities for bills, statements, policies, and correspondence produced in the millions. It is a supported output in IBM z/OS and IBM i environments and in cross-vendor production print software.

Beyond physical print, MO:DCA is widely used as an archival final-form format for regulated documents, including within content-management and document-archive product families.

Advantages

• All-points addressability with rich mixed content — text, image, vector graphics, bar codes, and forms — precisely positioned.
• Output and print integrity: closed-loop, page-level accounting and recovery, essential for financial and legal documents at scale.
• Resource management: reusable, downloadable fonts, overlays, and page segments reduce data volume and enforce consistency across large runs.
• Device and application independence at the MO:DCA layer, so a document can target many devices.
• Optimized for very high-speed, high-volume production printing.
• Open, versioned standard maintained by a multi-vendor consortium, with defined PDF interchange via ISO 22550.

Limitations

• Complexity and specialized tooling: authoring, transforming, viewing, and driving AFP require dedicated software and expertise; it is not a general desktop format.
• Ecosystem concentration: strongest in IBM mainframe and midrange environments and among production-print vendors, and less ubiquitous than PDF for everyday exchange.
• Not human-editable or a simple exchange format: MO:DCA is a binary structured data stream, unlike PDF's broad end-user tooling.
• IPDS device dependence: the full closed-loop integrity benefits require IPDS-capable devices or transforms.

Related standards and protocols

• MO:DCA — the AFP document content and interchange architecture (AFPC Reference).
• IPDS — the AFP host-to-printer bidirectional protocol (AFPC Reference).
• Component OCAs — PTOCA, IOCA, AFP GOCA, BCOCA, FOCA, CMOCA, and MOCA.
• PSF / InfoPrint Manager — IBM implementation software.
• ISO 22550 — Document management — AFP interchange for PDF (MO:DCA as a container for PDF objects in IPDS workflows).
• Adjacent and contrasting page technologies — PostScript, PDF (ISO 32000), PCL, and IPP (the last being a different, general-purpose network print protocol).

Timeline

1. 1984

   IBM introduces the Advanced Function (Printing) architecture and the IPDS data stream; first AFP specifications and products.

2. Feb 12, 1985

   IBM announces the IBM 3820, cited as IBM's first AFP cut-sheet printer.

3. 1987

   IBM introduces Systems Application Architecture (SAA), within which AFP is subsequently positioned.

4. Oct 2004

   IBM initiates the AFP Color Consortium (AFPCC).

5. 2006

   The CMOCA (Color Management OCA) specification is first published.

6. May 2006

   IBM announces opening the AFP architecture to a consortium.

7. Sep 2006

   The initiative is finalized as the AFP Consortium (AFPC).

8. Jun 2007

   IBM's stewardship role transfers to the InfoPrint Solutions Company (IBM–Ricoh joint venture), later Ricoh.

9. Feb 2009

   The AFPC is incorporated as a formal standards body, reported with over 35 member companies.

10. 2019 / 2021

    ISO 22550 is published (2019 edition; 2021 revision), defining AFP/MO:DCA interchange for PDF.

11. Jun 28, 2023

    The AFPC publishes simultaneous updates: the IPDS Reference 13th edition (AFPC-0001-12) and the MO:DCA Reference 11th edition (AFPC-0004-10).