Document Collation

With the maturation of the GRC domain, clients increasingly require the compilation of more complex documentation artifacts. For example, Model Risk Management clients frequently maintain Model Documentation, which are complex, technical reports that can be more than a hundred pages. The documentation is highly technical, and comprises formulas, tables, charts, images and footnotes. The reviewers of the Model also write an equivalently lengthy document as a record of their reviews. The compiled document includes hand-crafted technical writing and OpenPages reports. The final output is a PDF.
Model Risk Management is only one example where the compilation of documentation artifacts is required. Recently, OpenPages Service teams had six concurrent projects with documentation challenges, four that required some form of document compilation with PDF output and two that required Rich Text formatting in a PDF file.
OpenPages offers minimal support for this kind of artifact. Rich Text promises to support a part of the solution, but its capabilities are marginal. A separate enhancement request covers Rich Text.
The high level requirements for Documentation Compilation are:
• User or Services can define a documentation artifact that is the compilation of an ordered sequence of files that include a Title Page, a Table of Contents, OpenPages reports, the MS Word equivalent documents, and, possibly, other attached files such as Excel or Visio
• User can designate the format of the final artifact, though initially only PDF is required.