# Presentation: 083275

## Composition System Replacement

- March 19, 2007

- Composition System Replacement

**Notes:**
KIRK
Thank you for coming
What is CSR? (CSR) will be composed of the necessary technology and business practices to enable GPO to replace or integrate all existing discrete applications, utilities, and processes currently used by GPO and its users to compose and create files optimized for printing and access of select Congressional and Federal agency publications.
CSR will allow GPO and its users to employ XML while maintaining the current functionality of GPO locator codes. It is assumed that over time all users will migrate to the new XML workflow to take advantage of XML’s flexibility and robustness.
Why is this project important? What’s in it for you?
Interest in printing, technology, democracy.
It’s a chance to make history...or at least compose it.
Benjamin Franklin is link to GPO. GPO opened its doors in 1861 (146 yrs)
The day President Lincoln was inaugurated, GPO opened its doors.

Acquisition Regulations
House Resolutions
House Rules and Manual
Justice Department - Administrative Decisions
Briefs - Commission on Security and Cooperation in Europe
Medicare Commission Report
Code of Federal Regulations
Committee hearings
Committee prints
Committee print compilations
Congressional bills and resolutions
Congressional Documents
Congressional Record
Public and Private Laws
Congressional Record Index
Congressional Reports
Senate Ethics Manual
Economic Indicators
Economic Report of the President
Eulogies
Senate Intern Handbook
Federal Register
Hearings/Reports
Supreme Court Briefs
U.S. Budget
U.S. Code
U.S. Government Manual
U.S. Tax Court Monthly Reports
Weekly Compilation of Presidential Documents

14 most influential people in history
AristotleAugustusBuddhaColumbusConfuciusEinsteinGalileoGutenbergJesusMohammedNewtonSt.PaulShi Huang-tiT'sai lung

## Agenda

**8:30-8:50 ****	****Introduction and Overview****	****	****	****	****	****	*****Kirk Knoll***
**8:50-9:05****	****Overview of Microcomp and Motivations for Change ****	****	****	*****Reynold Schweickhardt***
**9:05-9:30****	****Input Types Discussion (Includes Q&A)***** ******	******	******	******	******	******Kirk Knoll and Panel***
**9:30-10:00****	****Content and Processing Discussion (Includes Q&A)*****	******	******	******Matt Landgraf and Panel***
**10:00-10:20 ****	****Break**
**10:20-10:50****	****Layout Discussion (Includes Q&A)****	****	****	****	****	*****Kirk Knoll and Panel***
**10:50-11:20 ****	****User Interface Discussion (Includes Q&A)*****	******	******	******	******	******Matt Landgraf and Panel***
**11:20-11:45 ****	****Output Discussion (Includes Q&A)****	****	****	****	****	*****Kirk Knoll and Panel***
**11:45-12:00 ****	****White Paper and Capabilities Definitions****	****	****	****	****	*****Kirk Knoll and Panel***
**Break/End of Official Industry Day**
**1:00-2:00 ****	****Optional Tour of Production Composition Area****	****	****	****	*****Dannie Young*****	****	****	**

**Notes:**
KIRK
Restrooms
Cafeteria
Optional Tour (sign up sheet)

## GPO CSR Panel

- Joel Reeves
- Lyle Green
- Dannie Young
- Dave Robare
- Matt Landgraf
- Kirk Knoll

**Notes:**
KIRK

Joel- Manager of Graphic Systems Development Branch
Lyle- Director, Office of Congressional Publishing Services
Dannie- Assistant Superintendent EPD Electronic Photocomposition Division
Dave- Chief of Composition in GSDD
Matt- Lead Program Planner	
Kirk- CSR Program Manager

## Session Objectives

- Explain the desired functionality identified by GPO
- Provide an open forum for GPO and industry to discuss these areas and GPO’s challenges
- Provide industry with enough data and understanding to effectively respond to the material noted in the RFI

**Notes:**
KIRK

## Overall Objectives

- To obtain industry feedback
- Assessment of materials
- Include white papers, and other industry best practices
- Budgetary
- To understand possible technology roadmaps– through capability statements.
- Is COTS support available?
- How soon will COTS support be available?

**Notes:**
KIRK

## GPO Mission

- To provide the three branches of the Federal Government with expert publishing and printing services.
- To provide perpetual, free and ready public access to the printed and electronic information published by the Federal Government in partnership with Federal Depository libraries.
- To distribute, on a cost recovery basis, printed and electronic copies of information published by the Federal Government.

**Notes:**
KIRK

## GPO’s Composition Background

- March 19, 1972—birth of Microcomp.....
- GPO developed
- Used to compose Congressional and Agency documents
- GPO locator codes
- Typesetting specific codes used to compose data
- Approximately 700 utilities have been developed to enhance and sustain Microcomp

**Notes:**
Reynold
Chief information Officer
With GPO for 3 years
Director of technology at the House Administration Committee, where he was responsible for IT strategy for the House of Representatives.

## Motivations for Change

- To improve workflow processes
- To improve search and retrieval
- Seamlessly accept, compose, and output XML
- Reduce GPO’s dependency on a system:
- not based on industry standard data model
- with limited or no IT support

**Notes:**
Reynold

## ConOps and RD Development

- ConOps - November 2006
- Requirements Document – March 2007
- Developed in collaboration with all user groups
- GPO Plant and IT&S
- Congressional Users
- House and Senate
- Agency Users

**Notes:**
KIRK    FY08 development project

## CSR RD Areas

- Input Data
- Content and Processing
- Character Formatting
- Layout
- Output
- User Interface

**Notes:**
KIRK

## Input Types

- The Composition System Replacement (CSR) will be the central point for composition of content that is intended for in-house print and electronic output.
- CSR will have the capability to accept input data for composition in all formats that are submitted by users, including XML, SGML, XML/SGML hybrids, Locator Files, and hybrids.
- Regardless of the type of input data, CSR will have the capability to compose input data into formatted pages.

**Notes:**
KIRK

Hybrids include XML/SGML and Locator/XML

## Characteristics of Input Types

- Optimum scenario is to move to an XML based workflow. The assumption is there will be a long transition period during which the legacy formats will have to be supported.
- Transition period is driven by our content originators.
- GPO receives multiple input types for one publication type
- Bills are 90% XML, 10% locators.
- GPO currently converts XML to locators. The goal is to be able to compose the native XML files.

**Notes:**
Bullet #1. Lyle     2.Joel

## Content and Processing

- Publications that are printed using composition engines are comprised of many different document components:
- Text: often output as two or more columns on a single page, and CSR must support these requirements.
- Tables: includes all formatting and display requirements that pertain to individual tables and tables that span multiple columns and pages
- Graphics and Equations: includes embedded and linked

**Notes:**
MATT

## Content and Processing (con’t)

- Continuation Indicators: indicators that a document component has been continued from one page to the next or from one column to the next
- Indices (Indexes) and Table of Contents
- Side Notes: denote cross-references to sections of other publications.
- Footnotes: includes composition of sequential numeric footnotes and symbolic footnote patterns

**Notes:**
MATT

## Characteristics of Content and Processing

- Content from one publication has to be repurposed for other formats. GPO currently tags once and reuses the data in multiple products and formats. For example:
- Bills and the Bills printed in the Congressional Record
- Federal Register and the CFR
- Managing various input types and workflows.
- Composition of multiple publication fragments.

**Notes:**
1. Joel  2. Dannie  3. Joel

## Layout

- CSR will:
- Conform to distinctive formatting requirements for documents that are printed by GPO, including the Congressional Record, Congressional Bills, and Federal Register.
- Automate the placement of content within a publication.
- Use publication specific settings during composition.
- Apply multiple sets of publication specific settings to the same document
- Allow authorized users to override publication specific settings.

**Notes:**
KIRK
Includes Character Formatting and Layout
Publication specific style settings: Formatting rules and specifications associated with a publication.

Tracing = Letter Spacing

Composite characters: A combination of two or more component character shapes usually, but not limited to, a base character and one or more diacritical marks that are placed above and/or below the base character (e.g., accent mark).

Bullet 4 = same data used in the Federal Register and Code of Federal Regulations.

## Layout (con’t)

- Printed publications composed by GPO often require specific formatting of characters, text, tables, and columns:
- Change formatting
- Font styling
- Text alignment
- Tracking
- Adjusting of character width
- Kerning
- Drop Caps and Raised Caps
- Special and Unicode Characters
- Composite Characters
- Leaders
- Horizontal and Vertical Fixed Spacing

**Notes:**
KIRK

## Characteristics of Layout

- CSR will need to be capable of printing complex multi-page tables.
- The volume of work GPO produces requires that CSR be an automated batch process. A manual process would not be effective in GPO’s workflow.
- GPO composes and produces publications daily under strict deadlines.

**Notes:**
1. Robare  2. Joel (Speak about congressional responsibilities, deadlines.) 

## User Interface

- Windows-based Graphical User Interfaces (GUIs) and workbenches are key components of CSR.
- Workbenches for internal and external user classes will allow users to access toolsets and perform authorized functions according to user roles, access rights, and privileges.

**Notes:**
MATT

## User Interface (con’t)

- Users will be permitted to apply and modify processing instructions through the user interface.
- The system will provide the capability for administrators to customize default GUIs and workbenches for all user classes.
- The system must conform to best practices, standards, and guidelines regarding usability for GUI design.

**Notes:**
MATT

## Characteristics of User Interface

- The user interface will allow users to preview their composition work and have access to an editor to modify source documents.
- The system must provide error identification, location, severity, and notification.

**Notes:**
1.Robare (must specify where errors occur, ex. data, composition. Give a specific example)   2. Robare

## Output

- Includes all the processes and capabilities necessary for CSR to render files that can be used for creating printed and digital output.
- CSR will be able to produce output in PostScript, XML, PDF, locator tagged files, and HTML.
- The system shall also allow users to specify output options, including duplex printing and Galley and Page mode rendering options.
- The system must also be capable of re-composing pages and frames after corrections are made to content. Must be able to limit the effect of a particular change as to not require changes to the flow of a complete document.
- The system will also be capable of outputting content to multiple printing devices and distributing the output on several devices simultaneously.

**Notes:**
KIRK

Frame: GPO term for a composition page unit. The number of frames in a publication differs from the number of pages by the number of blank pages. Frame numbers always are numbered consecutively starting from ‘1’ for the first printed page in the publication. Page numbers may or may not start at the first printed page (i.e. because preliminary pages are often numbered i, ii, iii, etc.), or only restart at ‘1’ in the first issue of the year (e.g., for the Federal Register).

## Characteristics of Output

- The system must be able to insert processing instructions (e.g. line and page breaks, page and line numbers) within the native document file.
- The system must be able to print information outside the page margins (e.g. job identifiers, file name, operator name, date and time).

**Notes:**
1. Joel   2. Joel

## Integration

- CSR needs to be integrated with existing pre-processing and post-processing applications, including:
- Authoring tools/Text editors (e.g., XMetaL, Xywrite, TextPad, word processors, MathType)
- Translation tools and Conversion programs
- Acrobat Distiller
- Bound Record indexing process
- Other electronic distribution utilities (e.g., add hot links)
- Productivity Management systems

**Notes:**
Joel

## Next Steps - White Papers and Capability Statements

- Vendors who are interested in any or all of the solution sets must submit a packet of material which includes:
- Capability statement
- White Paper that:
- Addresses gaps between current technology and areas.
- Addresses any concerns with CSR documentation.
- Provides technology roadmaps, with timelines for notional area support.
- Budgetary estimates along with estimated implementation timelines and effort.
- All documents due by noon on 30 April 2007
- 	The complete list of requested materials, due dates and instructions are noted in the published RFI at _[www.gpo.gov/compsys.htm](http://www.gpo.gov/compsys.htm)__. These instructions must be followed for consideration._

**Notes:**
KIRK
Post Industry Day Requested Information:
Following Industry Day and keeping GPO’s goals in mind please outline how your products and/or technology provide any of the listed notional areas, or describe how your products and/or technology set provide additional solutions that would be advantageous for the Government. Please also list budget estimates along with estimated implementation timelines and effort. 
Vendors who are interested in any or all of the solution sets must submit a packet of material which includes:
A separate capability statement (10 pages or less per notional area and no marketing material) for any notional area address specific solution sets or clusters. 
A single page listing company points of contact (name, title, email and phone) and GSA Schedule information (if applicable). 
A separate White Paper (no more than 50 pages total) that:
Addresses gaps between current technology and notional areas.
Addresses any concerns with CSR documentation. Concerns should be accompanied by clear recommendations supported by industry best practices for refining documentation.
Provides technology roadmaps, with timelines for notional area support.
Questions regarding capability statements, white papers and other documentation must be submitted in writing to the address listed below. Questions must be submitted by 3 April 2007.

## Contact Information

- _[PMO@gpo.gov](mailto:PMO@gpo.gov)_
- _[www.gpo.gov/compsys.htm](http://www.gpo.gov/compsys.htm)__ _