Вы находитесь на странице: 1из 198

Confidential

August 15, 2001


Oc Technologies B.V.

BU-DPS

Internal report 01.DPS.1022

Author

T. van den Honert

Department

BU-DPS

Tittle

Product Specification Document


Oc Doc Works R1.2.1

Keywords

Oc Doc Works, Newton

Abstract

The PSD of Oc Doc Works defines the functionality and quality of the
product, on a user and quality assurance abstraction level. This PSD is
the specification reference for:
The development of the product (project targets),
The development of documentation and manuals for the operations
departments (marketing, service and consultancy mgt), and
For quality assurance purpose during operation of the released product.

o
o
o

Agreed

A. Habets

Signature

Total of pages

44

Reference

To

Copy

Project Committee Newton

PI(BIC) (EWIJ)
MI-DPS (GP)

(AHH, THO, YWI, EPR, DAAS,


FVDK, TW, BEUT, MRON)

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released

Page:
2
Date:
August 15, 2001
Version: 1

0. Table of contents
1.

THE PRODUCT ..................................................................................................................................... 4


1.1.
1.2.
1.3.

MARKET ............................................................................................................................................ 4
THE PRODUCT ................................................................................................................................... 4
POSITION IN PORTFOLIO .................................................................................................................... 5

2.

TECHNICAL LIFE TIME ....................................................................................................................... 6

3.

FUNCTIONALITY .................................................................................................................................. 7
3.1. INTRODUCTION .................................................................................................................................. 7
3.1.1. Changes with respect to R1.2................................................................................................ 7
3.1.2. Changes with respect to R1.1................................................................................................ 7
3.1.3. Abbreviations........................................................................................................................... 8
3.2. CLIENT JOB SUBMISSION .................................................................................................................... 8
3.2.1. File - Print - Oc Doc Works .................................................................................................. 8
3.2.2. PDF upload............................................................................................................................ 10
3.2.3. Web submission (Pro only) .................................................................................................. 10
3.3. O PERATOR CONSOLE...................................................................................................................... 11
3.3.1. Job overview frame............................................................................................................... 11
3.3.2. Jobs........................................................................................................................................ 12
3.3.3. Job Ticket Frame .................................................................................................................. 14
3.3.4. Printers................................................................................................................................... 14
3.3.5. Import job, PDF and ticket (Pro only) .................................................................................. 16
3.3.6. Export job, PDF and ticket (Pro only).................................................................................. 16
3.3.7. Ticket format (Pro only) ........................................................................................................ 17
3.3.8. Customer Communication.................................................................................................... 17
3.3.9. Joblog..................................................................................................................................... 17
3.3.10.
Preferences ....................................................................................................................... 17
3.4. SYSTEM ADMINISTRATION APPLICATION........................................................................................... 18
3.4.1. Oc Doc Works Station ........................................................................................................ 18
3.4.2. Licenses................................................................................................................................. 18
3.4.3. Automatic Import (Pro only) ................................................................................................. 18
3.4.4. Automatic Export (Pro only) ................................................................................................. 18
3.4.5. Advanced............................................................................................................................... 19
3.5. JOB TICKET EDITOR ........................................................................................................................ 19
3.5.1. Job ticket definition ............................................................................................................... 19
3.5.2. Job ticket items ..................................................................................................................... 19
3.5.3. Job ticket views ..................................................................................................................... 19
3.5.4. View and print........................................................................................................................ 19
3.5.5. Identification........................................................................................................................... 19
3.5.6. Open, Save, Import, Export.................................................................................................. 19
3.5.7. Factory defaults..................................................................................................................... 20
3.5.8. Software protection ............................................................................................................... 20
3.6. TIFF TO PDF CONVERTER .............................................................................................................. 20
3.7. COPY PROTECTION.......................................................................................................................... 20
3.7.1. Client side .............................................................................................................................. 20
3.7.2. Server side............................................................................................................................. 20
3.8. O THER ASPECTS ............................................................................................................................. 20
3.8.1. Language support ................................................................................................................. 20
3.8.2. Help ........................................................................................................................................ 21
3.8.3. Homepage ............................................................................................................................. 21
3.9. SERVICE ASPECTS .......................................................................................................................... 22
3.9.1. Performance .......................................................................................................................... 22
3.9.2. Release identification............................................................................................................ 22
3.9.3. Diagnostics ............................................................................................................................ 22
3.9.4. Backup/restore ...................................................................................................................... 23

Copyright 2001

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released

Page:
3
Date:
August 15, 2001
Version: 1

3.9.5. Distribution............................................................................................................................. 23
3.9.6. Installation.............................................................................................................................. 23
3.9.7. Upgrades ............................................................................................................................... 23
3.10.
OC DPS400 PAGE PROGRAMMER ......................................... ERROR! BOOKMARK NOT DEFINED.
3.10.1.
Scope Oc DPS400 Page Programmer...............................Error! Bookmark not defined.
3.10.2.
Functionality Oc DPS400 Page Programmer ....................Error! Bookmark not defined.
3.10.3.
Limitations Oc DPS400 Page Programmer .......................Error! Bookmark not defined.
3.10.4.
Commercial aspects Oc DPS400 Page Programmer .......Error! Bookmark not defined.
3.10.5.
Service aspects Oc DPS400 Page Programmer...............Error! Bookmark not defined.
3.11.
RELATED DOCUMENTS .............................................................. ERROR! BOOKMARK NOT DEFINED.
4.

OPEN INTERFACES................................................................ERROR! BOOKMARK NOT DEFINED.

5.

CONFIGURATIONS .................................................................ERROR! BOOKMARK NOT DEFINED.


5.1.
5.2.
5.3.
5.4.

G ENERAL ..................................................................................... ERROR! BOOKMARK NOT DEFINED.


PROTECTION OF NEWTON-SOFTWARE ......................................... ERROR! BOOKMARK NOT DEFINED.
INTERRELATIONS .......................................................................... ERROR! BOOKMARK NOT DEFINED.
O PTIONAL FUNCTIONALITY............................................................ ERROR! BOOKMARK NOT DEFINED.

6.

PRODUCTIVITY/PERFORMANCE ........................................ERROR! BOOKMARK NOT DEFINED.

7.

SITE REQUIREMENTS ...........................................................ERROR! BOOKMARK NOT DEFINED.


7.1.
7.2.
7.3.
7.4.
7.5.
7.6.
7.7.

CLIENT APPLICATION .................................................................... ERROR! BOOKMARK NOT DEFINED.


W EB SUBMITTER CLIENT ............................................................... ERROR! BOOKMARK NOT DEFINED.
SERVER SOFTWARE ..................................................................... ERROR! BOOKMARK NOT DEFINED.
NETWORK ENVIRONMENT ............................................................. ERROR! BOOKMARK NOT DEFINED.
PDF FILES.................................................................................... ERROR! BOOKMARK NOT DEFINED.
O THER APPLICATIONS .................................................................. ERROR! BOOKMARK NOT DEFINED.
RELATED DOCUMENTS ................................................................. ERROR! BOOKMARK NOT DEFINED.

8.

INTERDEPENDENCIES ..........................................................ERROR! BOOKMARK NOT DEFINED.

9.

CONSULTING...........................................................................ERROR! BOOKMARK NOT DEFINED.

10.

SERVICE AND SUPPORT...................................................ERROR! BOOKMARK NOT DEFINED.

10.1.
INTRODUCTION ......................................................................... ERROR! BOOKMARK NOT DEFINED.
10.2.
IMPLEMENTATION...................................................................... ERROR! BOOKMARK NOT DEFINED.
10.2.1.
Implementation Services .......................................................Error! Bookmark not defined.
10.2.2.
Upgrades.................................................................................Error! Bookmark not defined.
10.3.
SUPPORT ................................................................................. ERROR! BOOKMARK NOT DEFINED.
10.3.1.
Support Services ....................................................................Error! Bookmark not defined.
10.4.
SERVICE KEY FIGURES .............................................................. ERROR! BOOKMARK NOT DEFINED.
10.4.1.
Remote Services ....................................................................Error! Bookmark not defined.
10.4.2.
Repairable items.....................................................................Error! Bookmark not defined.
10.4.3.
Support tools...........................................................................Error! Bookmark not defined.
10.5.
DOCUMENTATION ..................................................................... ERROR! BOOKMARK NOT DEFINED.
10.6.
TRAINING.................................................................................. ERROR! BOOKMARK NOT DEFINED.
10.7.
PRINTING TABLES ..................................................................... ERROR! BOOKMARK NOT DEFINED.
11.

ENVIRONMENTAL AND SAFETY ASPECTS ..................ERROR! BOOKMARK NOT DEFINED.

12.

SOFTWARE LICENSES ......................................................ERROR! BOOKMARK NOT DEFINED.

12.1.
12.2.
12.3.
12.4.
12.5.

ADOBE ..................................................................................... ERROR! BOOKMARK NOT DEFINED.


DBITECH COMPONENT TOOLBOX OCX V4.0............................ ERROR! BOOKMARK NOT DEFINED.
MICROSOFT XML ..................................................................... ERROR! BOOKMARK NOT DEFINED.
ASPEMAIL................................................................................. ERROR! BOOKMARK NOT DEFINED.
OC QUITE PLUG-IN ................................................................. ERROR! BOOKMARK NOT DEFINED.

Copyright 2001

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released

1.

The Product

1.1.

Market

Page:
4
Date:
August 15, 2001
Version: 1

Oc Doc Works is targeted at small to medium sized DPC's that are


shifting to digital printing. Typical volumes are in the range of 100k to 1
mln prints per month. In Europe there are about 25.000 of these sites.
Oc is present in about 5000 of them.
Especially the small DPC's are in the process of becoming more
professional and going digital, or of being outsourced or decentralised. In
surviving this development, DPC's can be led into a new phase by
providing them with digital products and software. Oc Doc Works is an
important element in supporting this digital workflow of the DPC.
Oc Doc Works is not specifically targeted at the print-for-profit market.
However, the openness of the product will enable the application of Oc
Doc Works in selected cases via e.g. partner extensions.

1.2.

The product
Oc Doc Works is a client server product that supports the digital
workflow to and in the DPC. In the DPC it also supports advanced
document production processes.
The functionality will be extended by successively developing new
modules. The modules provide functionality to submit digital jobs to the
DPC and to empower the operator in preparing and printing jobs.
Job submission to the DPC
A major unique selling point of Oc Doc Works is the digital repro job
ticket that solves the issue of getting digital jobs from the office to the
DPC. The job ticket is a digital equivalent of the current job ticket in
paper form that DPC's and end users are used to . All the services of the
DPC can be ordered directly from the end-user desktop in the office.
Job submission to the DPC is a relevant topic in each DPC. Therefore
this will be available in both the Desk and the Pro configuration of Oc
Doc Works.
Next to digital jobs coming from the office, there can be jobs from
external customers or there can be paper jobs that have to be scanned
before they can be printed.
Alternative inputs to the Oc Doc Works server are possible in the Pro
version through the 'import robot' (automatic PDF import folders). With
R1.2 we can also submit PDF files from the Oc Doc Works client or with
the Web Job Submitter. Furthermore scans by the Oc 3165 SL can be
imported in to Oc Doc Works.
Job preparation by the operator
Jobs often need some preparation by the operator before they are ready
to be printed. Examples are: lay out previewing, booklet making, adding
a scanned page, adding page numbers, merging documents, page
programming. By using the standard of PDF and Adobe Acrobat
software, many of the mentioned examples can be addressed by
integrating 3rd party products into the Oc Doc Works server.

Copyright 2001

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released

Page:
5
Date:
August 15, 2001
Version: 1

Job preparation is a means by which the operator can add value to the
job. Therefore we will integrate some of this functionality in the Pro
version of Oc Doc Works (e.g. booklet making). Page Programming for
the Oc DPS400 is implemented in R1.2.
Job printing support for the operator
Ultimately the operator wants to prints the jobs. Therefore a print server
needs to support all printers that are available in the repro. Additionally
the operator is better supported if he can control the printers from the
server and if he can easily send a job to a certain printer.
In Oc Doc Works Desk basic printing support for all printers is offered.
In the Pro version the operator gets more extensive printing support by
the 'direct printing' mechanism for a selection of printers.

1.3.
Oc Doc Works/Dirac/

Position in portfolio
Oc Doc Works is targeted at manned production environments. As such
Prisma/ORC Oc Doc Works is the successor of Oc ReproCenter. The
year 2001 will be a phase in/phase out period.
Oc Doc Works is not targeted at EDP-environments or at processing
transaction documents. Prismaflow will address this market of
unattended output management, later on succeeded by Dirac.
Mixed environments: Oc ReproCenter was based on the Prismaflow
product. This means that mixed environments could be addressed by
one product. In the new situation, with Oc Doc Works and Dirac, these
environments need special consideration.

Printer/copiers

Oc Doc Works will, as part of Oc DPC solutions, mainly be sold at


customers that have other Oc products that are targeted at central
environments. It is essential that all our DPC products are part of one
integrated sales approach. Integration with Oc 3165 R4 (Scan Logic)
and Oc DPS400 are major attention points.
In 2001, the Oc DPS400 will be Oc's major offering in the DPC. From
then on Oc Doc Works will become the 'Digital Desk' of the DPC, with
the Oc DPS400 as main production machine.
Oc Doc Works, as server that supports the operator, is able to connect
with Oc 3165 Scan Logic through the Scan2PDF option.
Oc Doc Works is able to print to any DPS printer as it uses the NT
postscript driver of each specific printer.

Other software

Printer management applications like Print Logic and EFI Command


Workstation can be used next to Oc Doc Works on the same server.
Main application for Office Exec is in the office, offering a uniform driver,
routing and accounting. The positioning of the DPC version of the Oc
USA product Office Exec is however close to the positioning of Oc Doc
Works, with job submission and operator support.

Copyright 2001

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released

2.

Page:
6
Date:
August 15, 2001
Version: 1

Technical life time

Due to frequent changes in the software industry, the validity of the


ODW PSD has to be checked every year.
The PSD has to be checked every year on the following items:
A follow up PSD is implemented.
Operating systems or browsers are not supported anymore by its
suppliers.
e.g. MS support for Windows 95 stops completely.
Used applications are not supported anymore by its supplier
e.g. transition Acrobat 4 to 5.
The decision of changing the PSD is up to the PC Newton.

Copyright 2001

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released

Page:
7
Date:
August 15, 2001
Version: 1

3.

Functionality

3.1.

Introduction
This document specifies the functionality of Oc Doc Works R1.2.1. This
specification covers both the Desk and Pro configurations.
Oc Doc Works handles the job submission from the end users desk
towards the DPC and provides operator support for processing received
jobs.
For this, Oc Doc Works has a client side and a server side containing
the following groups of functionality:
Client
A submission client integrated with Windows print environments
A submission client for existing PDF files (integrated with the client
mentioned above)
A websubmitter for job submission via the Web
Server
An operator console for viewing, editing, printing and managing
incoming jobs
A Job Ticket Editor to configure the flexible job ticket definition
An administration module to administer and configure the system
A scan input for documents scanned on the Oc 3165
An open interface for import and export of jobs and ticket definitions
This document specifies the functionality of both the Desk and Pro
configurations. Topics only available in the Desk configuration will be
labeled Desk only, topics only available in the Pro configuration will be
labeled Pro only. All non-labeled topics are available in both
configurations.

3.1.1.

3.1.2.
3.1.2.1.

Changes with respect to R1.2


Windows 2000 support for ODW client.

Changes with respect to R1.1


Client side

Addition of PDF upload


Addition of web submitter

Only when using the original Client application (File- Print Oc Doc
Works), the ODW system is in control of the generated printable
document. With all other client side additions, the ODW system is not in
control and cannot guarantee the quality of the printable document.
This means that the promise of flawless printing cannot be
maintained for the total ODW system.
3.1.2.2.

Server side

Copyright 2001

Operator Console
o Addition of manual subset printing via Acrobat thumbnails

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released

3.1.3.

Page:
8
Date:
August 15, 2001
Version: 1
o List separator in log file based on regional settings
Job Ticket Editor
o Updated WYSIWYG user interface
o Import & export of ticket definitions
o Move of client bitmap selection to System Administration
application
Open interface
o Improvement of job ticket format for open interface (format
changed)
o Addition of open interface for ticket definitions
System Administration
o Move of logging settings to Job Ticket Editor
Printer Table Creator
o Completely updated user interface
o Change of printer tables file format
Installation
o Removal of NT, boot floppy and Acrobat installation
o Addition of full software only installation
o Addition of uninstall

Abbreviations
In this document the following abbreviations will be used.
ODW
PDF
DPC

3.2.

Oc Doc Works
Portable Document Format
Document Production Center

Client job submission


ODW offers three different ways of submitting jobs from a client towards
the ODW server:
File - Print Oc Doc Works (using a Client application)
PDF upload (integrated in the Client application)
Web submission (using a web-browser)
Only in the first option is the ODW system in control of the generated
printable document. With all other options the ODW system is not in
control and cannot guarantee the quality of the printable document.
This means that the promise of flawless printing cannot be
maintained for the total ODW system.

3.2.1.

Copyright 2001

File - Print - Oc Doc Works


The client application offers the user:
An easy way of submitting jobs from Windows office applications
towards the DPC. For the end-user the DPC is able to produce
documents in large quantities, enhance documents and/or offer
additional services.
A preview of the job to ensure that e.g. fonts and layout are correct.
A flexible digital job ticket to address the capabilities and services of
the DPC needed to produce the end-user job (note that these job
tickets are not comparable to device tickets as JEC or OJT). This
digital job ticket will be offered as a tree view of the settings. It is
also possible to install the Client on the ODW server.

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released

Page:
9
Date:
August 15, 2001
Version: 1
A separated message field is used to give additional information
from the DPC to the end-user (i.e. now duplex color printing
available).
A generic comment field is used to give the user the possibility to
provide additional information not covered in the job ticket settings.
(This depends on the ticket definition. A Comments field is included
in the default definition)

The progress of getting a connection to the server, retrieving the latest


job ticket settings, transferring the print data and job ticket are displayed
to the end-user.
3.2.1.1.

PDF

For each job a PDF file is generated to:


Describe the job contents in a device independent way.
Enable a preview of the document.
Adobe Acrobat Distiller R4.0, running on the Microsoft NT 4 server, is
used to generate PDF. Acrobat Distiller is configured in such a way that
the resulting output is optimised for printing. The resulting PDF is R1.3
compliant.
3.2.1.2.

Preview

The user has the possibility to preview the generated PDF file. On the
other hand a job can be submitted to the DPC without the need to wait
for the complete PDF file to be generated if the user doesnt want the
preview. To enable a preview of a job a PDF file is generated. Adobe
Acrobat Reader 4.0 is used to view the generated PDF.
Preview functionality is an optional feature.
3.2.1.3.

Notification

3.2.1.4.

Printer driver

See paragraph 3.3.8.


Adobe PS printer driver technology (latest available version) is used. An
ODW specific PPD file is used to optimize these PPD settings. The PPD
file will support the regular 43 Type 1 fonts (the same fonts as in our
engine products).
The PPD file is independently from which Microsoft Windows
environment (so the same for Windows 9x and NT and 2000
environment).
The Adobe PS printer driver depends on the Windows environment:
Driver for Windows 95/98
Driver for Windows NT 4
Driver for Windows 2000
The functional specifications of the printer driver are specified in a
separate document [DRIVER].
Note that the restrictions that hold for the Adobe PS driver also hold for
the ODW client job submission driver. The Windows 9x, NT and 2000
drivers cannot be shared (point & print) from the ODW server.
3.2.1.5.

Startup procedure

The client job submission application is installed as a generic process,


using the standard Windows mechanisms, so that it is always available.
If the job submission application is running, an icon is displayed in the
Windows system tray.
3.2.1.6.

Configuration

After installation there are two configurable items:


The IP address of the server is displayed and can be changed and or
extended. Instead of the IP address it is also possible to use the DNS
name. See also paragraph 3.4.1.
It is possible to change the name and/or location of the print file.

Copyright 2001

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released
3.2.1.7.

Page:
10
Date:
August 15, 2001
Version: 1

Remembered Job ticket items

Parts of the job ticket items are more or less static. This information is
stored on the client PC and is used as default value in the job ticket. The
job ticket items that are stored are defined with the Job Ticket Editor. If a
job ticket item is changed by the end-user, then this new value will be the
default value.
If possible to retrieve, the following fields are automatically filled in: login
name, computer name, company name, Client application version,
model name (extended/basic client), view name (fixed for now) and
definition identifier.
3.2.1.8.

Required job ticket items

Parts of the job ticket items are required (i.e. telephone number). Only if
the client fills in these job ticket settings with a correct value the job will
be accepted. Which job ticket items are required is defined with the Job
Ticket Editor.
3.2.1.9.

Language setting

Language is set during installation, choosing another language will mean,


install software again. The language setting must be the same as the
language used in the other ODW applications.
3.2.2.

PDF upload
The user has the possibility to submit existing PDF files towards the
ODW server.
The user will be asked to fill in a job ticket. This job ticket is equal to the
job ticket used for normal submission.
All sub paragraphs of paragraph 3.2.1 except 3.2.1.1, 3.2.1.4 also apply
to PDF upload.

3.2.2.1.

PDF file

The system will only be supported when used with valid PDF files. See
paragraph Error! Reference source not found.. Only one PDF file can
be submitted per job. So there is no support for multiple documents on a
single job.
The size of the PDF file will determine the submission speed. The
maximum file size depends on the available hardware of the ODW
server. The ODW server will not be able to accept files that are larger
then:
The available virtual memory on the ODW server or
Half the available disk space of the disk containing the storage
directory or
The available disk space of the disk containing the IIS ftproot
directory or
1Gb
3.2.2.2.

Ticket

The ticket that has to be filled in by the end-user is equal to the ticket
that is used in the client application (which is set using the Job Ticket
Editor).
The language of the ticket will be equal to the language used on the
ODW server software.
3.2.3.

Copyright 2001

Web submission (Pro only)


The web-submitter can be used to submit a combination of one existing
PDF file and a filled-in ticket to the ODW server, using a web-browser.

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released
3.2.3.1.

Page:
11
Date:
August 15, 2001
Version: 1

PDF file

The system will only be supported when used with valid PDF files. See
paragraph Error! Reference source not found.. Only one PDF file can
be submitted per job. So there is no support for multiple documents on a
single job.
The size of the PDF file will determine the submission speed. The
maximum file size depends on the available hardware of the ODW
server. The ODW server will not be able to accept files that are larger
then:
Half the available disk space of the disk containing the storage
directory or
The available disk space of the disk containing the Windows Temp
directory or
1Gb
3.2.3.2.

Ticket

The ticket that has to be filled in by the end-user is equal (the


presentation is comparable but not 100% equal) to the ticket that is used
in the client application (which is set using the Job Ticket Editor).
The language of the ticket will be equal to the language used on the
ODW server software.

3.3.
3.3.1.

3.3.1.1.

Operator Console
Job overview frame
In the job overview frame, all jobs in the system are shown. These jobs
are shown in a detailed view with several columns in which the main jobproperties are shown (Job number, user, status, ).
The jobs are stored in categories (folders), only one category is visible at
a time. Default there are two categories Unprocessed jobs and Ready
jobs. Only the user can move a job from Unprocessed jobs to Ready
jobs. A job can only be present in one category at a time.
Statuses of jobs in process

One of the main characteristics of a job in process is its status, which will
be displayed in the overview. The following statuses are automatically
detected and will change accordingly:
loading jobs, the ticket is present, the PDF document not.
new jobs, both ticket and PDF document are present, but not opened
yet
opened jobs
Opening a job means that the job is clicked and the ticket is shown,
comparable with e-mail programs.
jobs sent to printer
error jobs
The icons in the job overview list will represent the difference in status.
Furthermore a job can be marked ready, which will be done after
printing the job. The icons of all ready jobs will contain a ready mark.
3.3.1.2.

Announcement of new jobs

As stated, new jobs will be marked with a specific icon. Furthermore the
Operator is able to make the following settings for the announcement of
new jobs:
Pro only: Whether or not the ticket should be sent to a specific
printer automatically, as soon as a new job comes in

Copyright 2001

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released

Page:
12
Date:
August 15, 2001
Version: 1

Pro only: Whether or not a sound is played as soon as a new job


comes in. He is also able to choose the sound. (This depends on the
availability of a Sound card)
Furthermore the operator is able to automatically send an e-mail
message to the client, when a new job comes in.
Pro only: Announcement of news jobs can occur when the job comes in,
or when the operator first clicks on the jobs. This depends on an
Operator Console setting.
3.3.1.3.

Settings on the job list

An operator can make the following settings on his job list overview:
Pro only: Define the columns (number, content and order) of the
detailed view. All job ticket items and properties are available for
selecting them as the content of a column. The column settings will
be saved and restored, after, respectively, closing and opening the
application.
Pro only: Manage categories for jobs.
In order to manage the categories for jobs, it will be possible to
create new categories, delete categories and rename categories.
However, it will not be possible to make subcategories, i.e. nesting
categories in other categories. Furthermore, it is not possible to
delete the two default categories: Unprocessed jobs and Ready
jobs.
3.3.1.4.

Actions on the job list

An operator can perform the following actions on the job list:


Sort jobs on certain characteristics
It is possible to sort jobs on each property or settings shown in the
columns, by clicking the specific column. This mechanism is comparable
with the details view of Explorer.

3.3.2.
3.3.2.1.

Jobs
Actions on single job

When a job is selected in the job list, the job ticket frame shows the
settings of the job ticket. At that point the status of a document is
changed to opened. A number of actions on the selected job are
possible:

Copyright 2001

Desk only: Open document for viewing


Adobe Acrobat 4.0 is started, and the operator can view the
document. Saving of changes is not possible. (note: the print
function of Acrobat is directly integrated with the console).
Pro only: Open document for viewing and editing
Adobe Acrobat 4.0 is started, and the operator can perform all
actions supported by Adobe Acrobat and its plug-ins. After closing
Acrobat or the file, the changes are automatically saved to the PDF
file in the Operator Console. (note: the save and print function of
Acrobat are directly integrated with the console).
Acrobat makes a difference between plain edit functionality and, for
example, the booklet making of Quite. For simple editing the
document is modified, this in contrast with using Quite, which leads
to the creation of an extra document. Provisionally, only the
document with the focus, will be saved for ODW, when Acrobat is
closed.
Furthermore, a specific plug-in is be developed, by Quite on ODWs
specifications, for booklet making. This, in order to offer a simple
and easy-to-use user-interface for this functionality.

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released

3.3.2.2.

Page:
13
Date:
August 15, 2001
Version: 1
Pro only: Restore original file
With this function the original file is restored, only needed when the
operator accidentally saved the wrong file in Acrobat.
Print Job Ticket
Make a hardcopy of the job ticket that can be used for further
processing of the job or the ticket in the DPC. One printer can be
chosen to be the default ticket printer.
Pro only: Proof print
This function prints one copy of the document to a selected printer.
The settings of the job ticket will automatically be filled-in in the
printer driver, if possible. It will be made visible to the end user which
settings are not automatically handled. The operator can change
these, and other settings manually in the printer driver. The name of
the printer on which the proof print was made will be saved as an
extra job attribute.
Print Document
This function prints the whole job to the selected printer. Pro only:
The settings of the job ticket will automatically be filled in, in the
printer driver. Not all printers are totally supported, so it will be made
visible to the end user which settings are automatically handled and
which are not. The operator can change these non automatic and
other settings manually in the printer driver. Whether the driver
window is shown, depends on a per printer settings. For more
information about supported printers see also 4.2. The name of the
printer on which the print was made will be saved as an extra job
attribute.
Pro only: Move jobs to another category manually. It is not possible
to manually move jobs to the Ready jobs category. Use Mark jobs
as ready for this.
Mark jobs as ready.
When a job is marked ready, the icon will get a ready mark. As a
default the job is moved to the Ready jobs category. This can also
be turned off. It is also possible for the operator to automatically
send an e-mail to the client when he marks a job ready.
Delete jobs manually
Note: jobs that are in the Ready jobs category are deleted
automatically after a specified time frame.
Pro only: Export job manually,
The job, including the file and the ticket can be exported to any
directory the user wants, see also 5.1.
Save document as
The current PDF file of the document can be saved in any directory
the user wants.
Pro only: Send e-mail manually
As already mentioned, the operator is able to automatically send an
e-mail when a new job comes in or when a job is marked ready, see
also chapter 6. In addition it is also possible to send an e-mail
manually. In this case, the e-mail address of the client (of the
selected job) is used, and the Operator can type his own personal
message.

Actions on a multi-selection (Pro only)

It will be possible to select more then one job, using the standard button
combinations. In the menu is also a select all function available. The
following actions will stay available for a multi-selection of jobs:
Restore original file
Proof print, however this will only be convenient when the driver
window is set invisible by the operator, see also 4.2 Printer
configuration.
Copyright 2001

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released

3.3.2.3.

Page:
14
Date:
August 15, 2001
Version: 1
Print Document, just like proof print; this is only useful when the
operator sets the driver window invisible.
Print Job Ticket
Move jobs to another category manually
Mark jobs as ready
Delete jobs manually
Export jobs manually

New Jobs

Customers are sending jobs to the DPC; these are displayed as new in
the job overview. However there are two other ways of getting new jobs
into ODW:
Create new job
For creating a new job, the operator must select a PDF-file and fill in
a ticket. For this the same job ticket view is used as in the client
software. This function can be compared with PDF upload in the
client software.
Pro only: Import job manually
Single jobs can be imported manually, see for more information
paragraph 3.5.
3.3.3.

Job Ticket Frame


The settings shown in the job ticket frame are shown in the operator
view. This means that the settings do not have to be represented in the
same way as the end user sees them.
The operator can change the settings of the job ticket, but some of the
settings can be make read-only so that they cannot be changed. (e.g.
name owner, phone number, owner etc.). Furthermore some settings are
required, the operator must fill these in, before he is able to export,
delete or mark ready a job.
Making certain settings read-only and/or required, should be done in the
Job Ticket Editor.
Changes in the job ticket made by the operator are automatically saved.
Pro only: In the job ticket frame, the settings that are automatically
taken over into the printer driver of the selected printer can be
recognised by a small icons. Changing the values of a setting, or
selecting another printer could lead to a change in these icons.
Whether or not a setting can be taken over automatically is depending
on:
- the existence of a Printer Table for the driver of the selected printer.
This incorporates the capacities of the printer (an A4 printer will not
support the media size settings of an A3 job), see also paragraph
4.3.
- the existence of a mapping between a setting in the job ticket and a
setting in the printer driver. These mappings can be created in the
System Administration tool. The most frequently used mappings are
created by default.
The job ticket of the operator contains a notes field (this holds for the
default ticket. Customised tickets may not contain this field), where the
operator can enter comments to that specific job.

3.3.4.

Copyright 2001

Printers
In the printer overview, all the printers installed in the system (these are
all the printers installed under Windows NT) are visible except those that

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released

Page:
15
Date:
August 15, 2001
Version: 1

are Acrobat specific. The following information can be obtained from this
printer overview directly:
The currently selected printer
The default printer
The printer, to which all job tickets are sent
From this printer overview it is possible to reach the printer settings for
the several printers, in order to view or edit them, see paragraph 4.2. No
status feedback of the printers is offered.
3.3.4.1.

Printer overview

In the printer overview all available printers are visible. In the icons is
visualised, which printer is the default and which printer is the ticket
printer.
The currently selected printer has a blue or grey background (depending
on the PCs colour settings).
It is possible to:
Select another printer
Set another printer as ticket printer
Set another printer as the default.
3.3.4.2.

Printer configuration

An operator can configure individual printers in the printer Options menu:


Pro only: Set the visibility of the driver window on or off per printer. It
is only useful to hide the driver window, when a driver-translationtable is available.
Pro only: Availability and location of printer management tooling, like
Print logic.
When this field is filled in, it is possible to start up the printer
management application from within the operator console
In the printer options form also some special settings can be done, that
are required for printing with the help of Acrobat:
Set the Postscript level per printer.
Set binary printing on or off per printer.
Set truetype fonts on or off per printer
No NT printer settings can be done in the Operator Console. Limited load
balancing will be available via printer pools of NT. The number of
printers per pool is limited by NT specifications. Unfortunately the NT
specification is not clear on this. It states two or more print devices.
3.3.4.3.

Supported Printers

Only Oc DPS Postscript printers are supported, in combination with


their latest NT printer driver. Other printers may work, but are not
supported.
3.3.4.4.

Supported drivers for automatic takeover of settings (Pro only)

The settings of the job ticket can only be taken over in the printer driver,
when the following files are available on the Oc Doc Works system:
A printer-transformation-table for the driver of the selected printer
(each driver version needs a new table)
A mapping table, which contains information about the links between
ticket settings and driver items. A general mapping table will suffice.
In some cases a special mapping table for one specific printertransformation-table will be needed.
Oc R&D will only deliver the generic mapping table. All tables are
generated and tested by IS&S (partly outsource towards HWS DPS).
An application will be offered to Oc Support, in order to create and fill
new printer-transformation-tables, (see 3.3.4.5). Printer-transformationtables will be offered for the latest version of each DPS printer (these will
be created and released by IS&S). In the System Administration of Oc
Doc Works it is possible to edit or extend the links in the generic
Copyright 2001

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released

Page:
16
Date:
August 15, 2001
Version: 1

mapping table, or create printer specific mapping tables. This might be


needed when new printers are installed and/or when the ticket is changed
with the Ticket Editor, in order to rearrange the links between the values
of the ticket settings and the values of the driver items.
3.3.4.5.

Driver Table Creator (Pro only)

The Driver Table Creator assists IS&S (and HSW DPS) in the creation of
printer transformation tables. The driver for which the transformation
table is needed should be installed on the same NT 4 server system as
this application. A question-based discovery of possible printer settings
follows. This application will only be available in English and can be
installed with a regular setup application.
Using this application, printer transformation tables can be created for all
those drivers that store their document defaults information according to
the Win32 DEVMODE specification.
For those drivers that store their information outside the DEVMODE,
settings cannot be taken over into the driver.
3.3.4.6.

Printer feedback

3.3.4.7.

Banner page configuration

No printer feedback will be shown.


The operator console will not provide any banner page functionality
except for the banner page configuration that is possible in the Windows
NT printing mechanism.
3.3.5.
3.3.5.1.

Import job, PDF and ticket (Pro only)


Manually

Jobs can be imported manually by choosing the Import function in the


menu bar. In order to select a job, a PDF-file with corresponding ticket
file must be available in the same directory.
3.3.5.2.

Automatically

PDF files moved or copied into a so-called hot-folder are automatically


pulled into the ODW system using an Import Robot. For each PDF file
the default ticket is generated. This ticket can be overwritten with
settings from a per folder ticket file. After that this ticket can be
overwritten with a ticket file, belonging to that particular PDF file.
Hot-folders can be added and removed using the System Administration
application. For each hot-folder it can be specified if a ticket file is
required. If a ticket file is required, the PDF file is not imported before a
corresponding ticket file is available.
Files that are imported in ODW, will be deleted from the hot-folder
3.3.6.
3.3.6.1.

Export job, PDF and ticket (Pro only)


Manually

Jobs can be exported from the system manually by choosing the Export
function in the menu bar. This function will ask for a destination
elsewhere on the file system, copy the PDF file attached to the job to
that destination and create a ticket file with the same name (except for
its extension) in that destination. Note that both the original and the
edited PDF document (if available) are copied into the destination.
3.3.6.2.

Automatically

Jobs can be exported from the system automatically to a destination


specified in the ODW preferences. For each job that reaches the state
New and has a PDF file attached, the attached PDF file will be copied
to the destination, a ticket file will be created with the name (except for
its extension) in that destination.

Copyright 2001

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released

Page:
17
Date:
August 15, 2001
Version: 1

Optionally jobs that are exported can be removed from the ODW
system.
This option can be specified in the System Administration application.
3.3.7.

Ticket format (Pro only)


The format of the ticket file used for import and export is xml-based. See
[IMPEXP] for details.

3.3.8.

Customer Communication

3.3.8.1.

E-mail notification received

ODW offers the possibility to give an e-mail notification to the customer,


when the job is arrived at the DPC and the PDF-file is successfully
created. Only SMTP compliant mail-servers are supported.
For this, the customer should have filled in an e-mail address and
checked the box notify when arrived (when this option is in the client
ticket). In the Operator Console the operator is able to predefine the text
of these messages.
Pro only: As an extra the operator is able to attach the incoming PDF
file and the ticket to this e-mail.
3.3.8.2.

E-mail notification ready

The console application offers the possibility to give an e-mail


notification to the customer when his/her job is ready. Only SMTP
compliant mail-servers are supported.
Pro only: Furthermore he has the option to attach the current PDF-file
and/or the current ticket to his message. If the PDF is already changed
before an e-mail is sent, this edited version will be used.
When a job is marked ready and the customer has filled in an e-mail
address and checked the box notify when ready (when this option is in
the client ticket), an email message is send with the subject and a part of
the message filled in.
In the preferences the operator is able to set the predefined text for this
message. The operator is also able to switch off the preview of the email, so the e-mail can be send behind the scenes.

3.3.9.

Joblog
Joblog information on a job will be saved after:
deleting a job
marking a job ready
Pro only: printing a job
Pro only: proof printing a job
Pro only: exporting a job
Pro only: importing a job
See Job Log specification for details.
In the Job Ticket Editor can be set which settings must be logged and
which not.

3.3.10.

Preferences

3.3.10.1. Operator settings

The operator can set a lot of preferences. These will be offered at the
Option menu at the menu bar. For the following parts preferences can be
set:

Copyright 2001

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released

Page:
18
Date:
August 15, 2001
Version: 1
New jobs, including automatic notification e-mail to the customer,
see paragraph 3.3.1.2
Ready marked jobs, including automatic notification e-mail to the
customer, see paragraph 3.3.8.2
Pro only: Job overview; manage content of columns, manage
categories and sorting jobs, see paragraph 3.3.1.3 and 3.3.1.4
Printer configuration, see paragraph 3.3.4.1
The text of the client banner. This text will be displayed in the header
of the client ticket.

3.3.10.2. Implicit preferences:

The following aspects of the UI of the Operator Console can be changed


by the operator, and are automatically saved:
size and position of main window
size of Job window or frame
size of Printer window or frame
proportion of width between job ticket and job list within Job window
order, content and width of columns in the job list

3.4.

System Administration application


In the System administration application, the following items can be
configured.

3.4.1.

Oc Doc Works Station

3.4.2.

Licenses

3.4.3.

Import settings, like setting the import interval, see also paragraph
3.3.5.2

Automatic Export (Pro only)

Copyright 2001

View all available licenses.


Enter a license for an ODW option (all options, except the client
options)

Automatic Import (Pro only)

3.4.4.

Storage directory. Only directory on the hard disks of the ODW


system are supported. (So the storage directory may not be located
on a network drive)
ODW computer name (hostname or IP-address). This name must be
filled in, since it will be send to all clients. Each client will use this
address for the next submission. (This can e.g. be used to move all
client of an ODW system to a new system, without modifying all
client configurations)
Setting the time frame, after which the jobs from the Ready job
category will be deleted (no, 1 day, 7 days, )
Company logo. It is possible to specify a company logo.
Email settings
Mail server hostname & port number
Mail from address & name
Pro only: Mail CC address(es). Multiple addresses may be entered,
separated by a semicolon.
Pro only: Maximum size for mail attachments.

Export settings, like settings the target path, see paragraph 3.3.6.2

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released
3.4.5.

Advanced

3.5.

Page:
19
Date:
August 15, 2001
Version: 1

Pro only: As an advanced option, the mappings between job ticket


settings and settings in the printer drivers can be created within the
System administration, see also paragraph 3.3.4.5.
Update the query cache. The system uses a cache for fast searching
on job ticket items. This cache is maintained automatically, but may
become outdated when incomplete backups are performed.

Job Ticket Editor


The Job Ticket Editor enables an Oc consultant to maintain and change
the job ticket definition. This definition describes the capabilities and
services provided by the DPC. If desired, after some training, the
administrator can also use the Job Ticket Editor.

3.5.1.

Job ticket definition


A job ticket definition is a combination of a list of job ticket items and
multiple views on these items. Items may be present in multiple views.
For now two views are supported; one used for the submission clients
(Client application, Web submitter and New job in the Operator
Console), the second used in the Operator Console.

3.5.2.

Job ticket items


A job ticket item has an (English) identifier, a data type, a range of
possible values and (translated) captions. Items can be added or
removed.

3.5.3.

Job ticket views


A view specifies the presentation of (a subset of) the list of job ticket
items in a definition. Per view can be specified:
Which items are displayed
How these items are organized into a tree structure (both structure
and order can be specified)
Which items are required, read-only and remembered

3.5.4.

View and print


It is possible to view the resulting job ticket definition and/or to print out
the job ticket definition for a specific view.

3.5.5.

Identification
The system uses a (non-human readable) unique identifier to distinguish
between multiple definitions. For each definition a human readable
description can be entered.

3.5.6.

Open, Save, Import, Export


The Job Ticket Editor will load the current definition on start-up. From
this definition a copy will be made (with a new unique identifier) that can
be modified and can be saved. When a definition is saved, this definition
is set as the current definition that will be used by everyone that submits
a new job.
The Job Ticket Editor can also export a definition into a file to the file
system. This file can be imported on another system and set as the
current definition (or modified as new definition).

Copyright 2001

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released

Page:
20
Date:
August 15, 2001
Version: 1

3.5.7.

Factory defaults.
During the installation, a default definition will be installed, containing
default list of job ticket items and default views for the Client and the
Operator.
It is the intention that these factory defaults will cover the needs of a
large group of customers. The captions in the factory defaults depend on
the chosen language.

3.5.8.

Software protection
A software license key will protect the Job Ticket Editor.

3.6.

TIFF to PDF converter


The ODW system can be extended with a TIFF to PDF converter that
allows for scanned documents from an Oc 3165 (in TIFF format) to be
converted into PDF documents.

3.7.

Copy protection

3.7.1.

Client side
A software license key protects the job submission client. The preview
option is also protected with a software license key.

3.7.2.

Server side
The server is protected by a software license mechanism. The servers
will be serialised with a unique serial number. This serial number will be
distributed by M&L. Beside this serial number; each application will have
a software license key.
During start-up of the application it is checked if a valid license key is
available, if not a message dialog is presented to enter a valid license
key. These licenses can also be entered and viewed using the System
Administration application.
In this way the installed software is generic and the licenses can be
distributed separately.
The software licensing is detailed in [ODWLICENSE].

3.8.
3.8.1.

Other aspects
Language support
The language on the client and the server must be the same.
For the operating system for the server applications only Microsoft NT
English is supported.
The following table specifies the languages supported.
Language
UK English
Dutch
German
French
Danish
Italian
Norwegian
Portuguese
Spanish
Swedish

Copyright 2001

Oc-Technologies B.V.

Adobe Acrobat language


English
Dutch
German
French
International English
Italian
International English
Portuguese
Spanish
Swedish
Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released
Finnish
Us English

Page:
21
Date:
August 15, 2001
Version: 1
International English
English

Note that within the ODW software common dialogues of the operating
system are used, which will be in English.
3.8.2.

Help
The ODW applications will have online help functionality meant for the
user of those applications. Win help and context sensitive help will be
used; no support for tool tips.

3.8.3.

Homepage
Every ODW server will be equipped with a set of web pages called
homepage. This homepage will be in the same language as all other
ODW applications. It will not be modifiable by the operator or system
administrator.
This homepage gives access to the web submitter, some general ODW
information and a download page, where the following topics can be
downloaded:
The ODW Client application (setup)
The ODW optimized Distiller options
The ODW PPD file and a description on how to set its default
settings
The Adobe PS driver (setup)
Adobe Acrobat reader

Copyright 2001

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released

3.9.
3.9.1.
3.9.1.1.

Page:
22
Date:
August 15, 2001
Version: 1

Service Aspects
Performance
Number of concurrent submissions

The server will be able to support 10 concurrent submissions. This holds


for both the client application and the web submitter. (e.g. 5 submissions
using the client application concurrent with 5 submissions using the websubmitter is ok, 10 submissions using the client application concurrent
with 10 submissions using the web-submitter is not supported)
The speed of the submission depends on:
Network speed, load and configuration
Used hardware for the client PC and ODW server
Processor and memory load on both PCs.
Note that distilling is done sequentially. This means that once a job is
distilling, other jobs (including preview requests) will have to wait.
3.9.1.2.

Number of concurrent print operations

Only one concurrent print operation is allowed. A second print operation


can be started when the first print job is under complete control of the NT
print spooler.
3.9.1.3.

Number of jobs

The number of jobs the system can handle depends on the size of the
jobs and is limited by the overhead of job ticket information and the size
of the data partition of the PC. The response of the system is reasonable
if the total number of jobs in the system dont exceed 500 for regular
office jobs. If more jobs should be handled then the response can be
decreasing.
3.9.1.4.

Pro only: Number of concurrent Import/Export operations

Only one job can be imported at a time and only one job can be exported
at a time. Import and export can work in parallel.
3.9.1.5.

Hardware

The overall performance depends on the used hardware.


Reasonable performance is only guaranteed when the minimum server
configuration is used and only the specified applications are running. So
no support given if other applications are running.
3.9.2.

3.9.3.
3.9.3.1.

Release identification
Each separate ODW application has an about box menu item which
describes the global release identification, current release version of that
application copyright notices and the serial number and license key.
Diagnostics
Standard diagnostics

Standard Microsoft NT diagnostics tools are used:


ODW logs events in the application part of the NT event log. The
Event Viewer is used to display the logged information. Logging
information will be in English only.
NT Diagnostics application is used to get an overall overview of the
server.
NT Regedit application is used to get a detailed overview of the
server.
For ODW no additional diagnostics tools are developed.

Copyright 2001

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released
3.9.3.2.

Page:
23
Date:
August 15, 2001
Version: 1

Remote diagnostics

Remote diagnostics is handled outside the scope of the project. Remote


diagnostics is meant for the helpdesk. Probably ControlIT will be used.
ControlIT is handled and installed separately by a service technician
and/or consultant
3.9.4.

Backup/restore
For ODW no backup/restore functionality for the server is taken into
account. Most companies do have already a backup procedure in place.
Within the contract the backup/restore is handled.
As an alternative, the Opco can decide to install locally a customer
preferred backup mechanism (i.e. DAT) on the ODW server.
The location of relevant data (i.e. job store) can be configured by means
of the System Administration application.

3.9.5.

Distribution

3.9.5.1.

Client

The ODW client application is distributed using a CD-ROM. This CDROM also contains a distribution package that allows for easy
distributions over a network (single setup file download; this is not equal
to SMS!).
No silent setup foreseen. Also no hardware distribution is foreseen.
3.9.5.2.

Server

The ODW server software is distributed using a CD-ROM.


No special distribution from the Web is available. No silent setup
foreseen.
Also no hardware distribution is foreseen.
3.9.6.
3.9.6.1.

Installation
Client

For the ODW client software, an InstallShield setup is used. This


installation should be performed on a system that complies with one of
the client target environments specified in paragraph Error! Reference
source not found..
The installation will have no options. An un-install option is available.
3.9.6.2.

Server

For the ODW server software, an InstallShield setup procedure for CDROM installation is used. This installation should be performed on a
system that complies with the server target environment specified in
paragraph Error! Reference source not found..
This implies that any old version of Desk or Pro should be removed
before this installation is activated.
The installation will have no options. An un-install option is available.
3.9.7.

Upgrades
There will be no upgrade from existing Desk 1.1 or Pro 1.1 systems to
Desk 1.2 and/or Pro 1.2 systems. To upgrade these systems to Desk/Pro
1.2 a clean system is required, which implies that formatting of the hard
disk is required.
There will be an upgrade tool for the jobs and ticket definition of an
existing Desk 1.1 or Pro 1.1 system. This tool should be used before the
conversion to Desk/Pro 1.2. It will store the information on a user
specified location (probable a network drive). After the installation of the

Copyright 2001

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released

Page:
24
Date:
August 15, 2001
Version: 1

Desk/Pro 1.2 system has been completed, this data can be imported
again.

Copyright 2001

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released

Page:
25
Date:
August 15, 2001
Version: 1

Confidential

August 15, 2001


Oc Technologies B.V.

BU-DPS

Internal report 01.DPS.1022

Author

T. van den Honert

Department

BU-DPS

Tittle

Product Specification Document


Oc Doc Works R1.2.1

Keywords

Oc Doc Works, Newton

Abstract

The PSD of Oc Doc Works defines the functionality and quality of the
product, on a user and quality assurance abstraction level. This PSD is
the specification reference for:
The development of the product (project targets),
The development of documentation and manuals for the operations
departments (marketing, service and consultancy mgt), and
For quality assurance purpose during operation of the released product.

o
o
o

Agreed

A. Habets

Signature

Total of pages

44

Reference

To

Copy

Project Committee Newton

PI(BIC) (EWIJ)
MI-DPS (GP)

(AHH, THO, YWI, EPR, DAAS,


FVDK, TW, BEUT, MRON)

Copyright 2001

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released

Page:
26
Date:
August 15, 2001
Version: 1

0. Table of contents
1.

THE PRODUCT ..................................................................................................................................... 4


1.1.
1.2.
1.3.

MARKET ............................................................................................................................................ 4
THE PRODUCT ................................................................................................................................... 4
POSITION IN PORTFOLIO .................................................................................................................... 5

2.

TECHNICAL LIFE TIME ....................................................................................................................... 6

3.

FUNCTIONALITY .................................................................................................................................. 7
3.1. INTRODUCTION .................................................................................................................................. 7
3.1.1. Changes with respect to R1.2................................................................................................ 7
3.1.2. Changes with respect to R1.1................................................................................................ 7
3.1.3. Abbreviations........................................................................................................................... 8
3.2. CLIENT JOB SUBMISSION .................................................................................................................... 8
3.2.1. File - Print - Oc Doc Works .................................................................................................. 8
3.2.2. PDF upload............................................................................................................................ 10
3.2.3. Web submission (Pro only) .................................................................................................. 10
3.3. O PERATOR CONSOLE...................................................................................................................... 11
3.3.1. Job overview frame............................................................................................................... 11
3.3.2. Jobs........................................................................................................................................ 12
3.3.3. Job Ticket Frame .................................................................................................................. 14
3.3.4. Printers................................................................................................................................... 14
3.3.5. Import job, PDF and ticket (Pro only) .................................................................................. 16
3.3.6. Export job, PDF and ticket (Pro only).................................................................................. 16
3.3.7. Ticket format (Pro only) ........................................................................................................ 17
3.3.8. Customer Communication.................................................................................................... 17
3.3.9. Joblog..................................................................................................................................... 17
3.3.10.
Preferences ....................................................................................................................... 17
3.4. SYSTEM ADMINISTRATION APPLICATION........................................................................................... 18
3.4.1. Oc Doc Works Station ........................................................................................................ 18
3.4.2. Licenses................................................................................................................................. 18
3.4.3. Automatic Import (Pro only) ................................................................................................. 18
3.4.4. Automatic Export (Pro only) ................................................................................................. 18
3.4.5. Advanced............................................................................................................................... 19
3.5. JOB TICKET EDITOR ........................................................................................................................ 19
3.5.1. Job ticket definition ............................................................................................................... 19
3.5.2. Job ticket items ..................................................................................................................... 19
3.5.3. Job ticket views ..................................................................................................................... 19
3.5.4. View and print........................................................................................................................ 19
3.5.5. Identification........................................................................................................................... 19
3.5.6. Open, Save, Import, Export.................................................................................................. 19
3.5.7. Factory defaults..................................................................................................................... 20
3.5.8. Software protection ............................................................................................................... 20
3.6. TIFF TO PDF CONVERTER .............................................................................................................. 20
3.7. COPY PROTECTION.......................................................................................................................... 20
3.7.1. Client side .............................................................................................................................. 20
3.7.2. Server side............................................................................................................................. 20
3.8. O THER ASPECTS ............................................................................................................................. 20
3.8.1. Language support ................................................................................................................. 20
3.8.2. Help ........................................................................................................................................ 21
3.8.3. Homepage ............................................................................................................................. 21
3.9. SERVICE ASPECTS .......................................................................................................................... 22
3.9.1. Performance .......................................................................................................................... 22
3.9.2. Release identification............................................................................................................ 22
3.9.3. Diagnostics ............................................................................................................................ 22
3.9.4. Backup/restore ...................................................................................................................... 23

Copyright 2001

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released

Page:
27
Date:
August 15, 2001
Version: 1

3.9.5. Distribution............................................................................................................................. 23
3.9.6. Installation.............................................................................................................................. 23
3.9.7. Upgrades ............................................................................................................................... 23
3.10.
OC DPS400 PAGE PROGRAMMER ......................................... ERROR! BOOKMARK NOT DEFINED.
3.10.1.
Scope Oc DPS400 Page Programmer...............................Error! Bookmark not defined.
3.10.2.
Functionality Oc DPS400 Page Programmer ....................Error! Bookmark not defined.
3.10.3.
Limitations Oc DPS400 Page Programmer .......................Error! Bookmark not defined.
3.10.4.
Commercial aspects Oc DPS400 Page Programmer .......Error! Bookmark not defined.
3.10.5.
Service aspects Oc DPS400 Page Programmer...............Error! Bookmark not defined.
3.11.
RELATED DOCUMENTS .............................................................. ERROR! BOOKMARK NOT DEFINED.
4.

OPEN INTERFACES................................................................ERROR! BOOKMARK NOT DEFINED.

5.

CONFIGURATIONS .................................................................ERROR! BOOKMARK NOT DEFINED.


5.1.
5.2.
5.3.
5.4.

G ENERAL ..................................................................................... ERROR! BOOKMARK NOT DEFINED.


PROTECTION OF NEWTON-SOFTWARE ......................................... ERROR! BOOKMARK NOT DEFINED.
INTERRELATIONS .......................................................................... ERROR! BOOKMARK NOT DEFINED.
O PTIONAL FUNCTIONALITY............................................................ ERROR! BOOKMARK NOT DEFINED.

6.

PRODUCTIVITY/PERFORMANCE ........................................ERROR! BOOKMARK NOT DEFINED.

7.

SITE REQUIREMENTS ...........................................................ERROR! BOOKMARK NOT DEFINED.


7.1.
7.2.
7.3.
7.4.
7.5.
7.6.
7.7.

CLIENT APPLICATION .................................................................... ERROR! BOOKMARK NOT DEFINED.


W EB SUBMITTER CLIENT ............................................................... ERROR! BOOKMARK NOT DEFINED.
SERVER SOFTWARE ..................................................................... ERROR! BOOKMARK NOT DEFINED.
NETWORK ENVIRONMENT ............................................................. ERROR! BOOKMARK NOT DEFINED.
PDF FILES.................................................................................... ERROR! BOOKMARK NOT DEFINED.
O THER APPLICATIONS .................................................................. ERROR! BOOKMARK NOT DEFINED.
RELATED DOCUMENTS ................................................................. ERROR! BOOKMARK NOT DEFINED.

8.

INTERDEPENDENCIES ..........................................................ERROR! BOOKMARK NOT DEFINED.

9.

CONSULTING...........................................................................ERROR! BOOKMARK NOT DEFINED.

10.

SERVICE AND SUPPORT...................................................ERROR! BOOKMARK NOT DEFINED.

10.1.
INTRODUCTION ......................................................................... ERROR! BOOKMARK NOT DEFINED.
10.2.
IMPLEMENTATION...................................................................... ERROR! BOOKMARK NOT DEFINED.
10.2.1.
Implementation Services .......................................................Error! Bookmark not defined.
10.2.2.
Upgrades.................................................................................Error! Bookmark not defined.
10.3.
SUPPORT ................................................................................. ERROR! BOOKMARK NOT DEFINED.
10.3.1.
Support Services ....................................................................Error! Bookmark not defined.
10.4.
SERVICE KEY FIGURES .............................................................. ERROR! BOOKMARK NOT DEFINED.
10.4.1.
Remote Services ....................................................................Error! Bookmark not defined.
10.4.2.
Repairable items.....................................................................Error! Bookmark not defined.
10.4.3.
Support tools...........................................................................Error! Bookmark not defined.
10.5.
DOCUMENTATION ..................................................................... ERROR! BOOKMARK NOT DEFINED.
10.6.
TRAINING.................................................................................. ERROR! BOOKMARK NOT DEFINED.
10.7.
PRINTING TABLES ..................................................................... ERROR! BOOKMARK NOT DEFINED.
11.

ENVIRONMENTAL AND SAFETY ASPECTS ..................ERROR! BOOKMARK NOT DEFINED.

12.

SOFTWARE LICENSES ......................................................ERROR! BOOKMARK NOT DEFINED.

12.1.
12.2.
12.3.
12.4.
12.5.

ADOBE ..................................................................................... ERROR! BOOKMARK NOT DEFINED.


DBITECH COMPONENT TOOLBOX OCX V4.0............................ ERROR! BOOKMARK NOT DEFINED.
MICROSOFT XML ..................................................................... ERROR! BOOKMARK NOT DEFINED.
ASPEMAIL................................................................................. ERROR! BOOKMARK NOT DEFINED.
OC QUITE PLUG-IN ................................................................. ERROR! BOOKMARK NOT DEFINED.

Copyright 2001

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released

4.

The Product

4.1.

Market

Page:
28
Date:
August 15, 2001
Version: 1

Oc Doc Works is targeted at small to medium sized DPC's that are


shifting to digital printing. Typical volumes are in the range of 100k to 1
mln prints per month. In Europe there are about 25.000 of these sites.
Oc is present in about 5000 of them.
Especially the small DPC's are in the process of becoming more
professional and going digital, or of being outsourced or decentralised. In
surviving this development, DPC's can be led into a new phase by
providing them with digital products and software. Oc Doc Works is an
important element in supporting this digital workflow of the DPC.
Oc Doc Works is not specifically targeted at the print-for-profit market.
However, the openness of the product will enable the application of Oc
Doc Works in selected cases via e.g. partner extensions.

4.2.

The product
Oc Doc Works is a client server product that supports the digital
workflow to and in the DPC. In the DPC it also supports advanced
document production processes.
The functionality will be extended by successively developing new
modules. The modules provide functionality to submit digital jobs to the
DPC and to empower the operator in preparing and printing jobs.
Job submission to the DPC
A major unique selling point of Oc Doc Works is the digital repro job
ticket that solves the issue of getting digital jobs from the office to the
DPC. The job ticket is a digital equivalent of the current job ticket in
paper form that DPC's and end users are used to . All the services of the
DPC can be ordered directly from the end-user desktop in the office.
Job submission to the DPC is a relevant topic in each DPC. Therefore
this will be available in both the Desk and the Pro configuration of Oc
Doc Works.
Next to digital jobs coming from the office, there can be jobs from
external customers or there can be paper jobs that have to be scanned
before they can be printed.
Alternative inputs to the Oc Doc Works server are possible in the Pro
version through the 'import robot' (automatic PDF import folders). With
R1.2 we can also submit PDF files from the Oc Doc Works client or with
the Web Job Submitter. Furthermore scans by the Oc 3165 SL can be
imported in to Oc Doc Works.
Job preparation by the operator
Jobs often need some preparation by the operator before they are ready
to be printed. Examples are: lay out previewing, booklet making, adding
a scanned page, adding page numbers, merging documents, page
programming. By using the standard of PDF and Adobe Acrobat
software, many of the mentioned examples can be addressed by
integrating 3rd party products into the Oc Doc Works server.

Copyright 2001

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released

Page:
29
Date:
August 15, 2001
Version: 1

Job preparation is a means by which the operator can add value to the
job. Therefore we will integrate some of this functionality in the Pro
version of Oc Doc Works (e.g. booklet making). Page Programming for
the Oc DPS400 is implemented in R1.2.
Job printing support for the operator
Ultimately the operator wants to prints the jobs. Therefore a print server
needs to support all printers that are available in the repro. Additionally
the operator is better supported if he can control the printers from the
server and if he can easily send a job to a certain printer.
In Oc Doc Works Desk basic printing support for all printers is offered.
In the Pro version the operator gets more extensive printing support by
the 'direct printing' mechanism for a selection of printers.

4.3.
Oc Doc Works/Dirac/

Position in portfolio
Oc Doc Works is targeted at manned production environments. As such
Prisma/ORC Oc Doc Works is the successor of Oc ReproCenter. The
year 2001 will be a phase in/phase out period.
Oc Doc Works is not targeted at EDP-environments or at processing
transaction documents. Prismaflow will address this market of
unattended output management, later on succeeded by Dirac.
Mixed environments: Oc ReproCenter was based on the Prismaflow
product. This means that mixed environments could be addressed by
one product. In the new situation, with Oc Doc Works and Dirac, these
environments need special consideration.

Printer/copiers

Oc Doc Works will, as part of Oc DPC solutions, mainly be sold at


customers that have other Oc products that are targeted at central
environments. It is essential that all our DPC products are part of one
integrated sales approach. Integration with Oc 3165 R4 (Scan Logic)
and Oc DPS400 are major attention points.
In 2001, the Oc DPS400 will be Oc's major offering in the DPC. From
then on Oc Doc Works will become the 'Digital Desk' of the DPC, with
the Oc DPS400 as main production machine.
Oc Doc Works, as server that supports the operator, is able to connect
with Oc 3165 Scan Logic through the Scan2PDF option.
Oc Doc Works is able to print to any DPS printer as it uses the NT
postscript driver of each specific printer.

Other software

Printer management applications like Print Logic and EFI Command


Workstation can be used next to Oc Doc Works on the same server.
Main application for Office Exec is in the office, offering a uniform driver,
routing and accounting. The positioning of the DPC version of the Oc
USA product Office Exec is however close to the positioning of Oc Doc
Works, with job submission and operator support.

Copyright 2001

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released

5.

Page:
30
Date:
August 15, 2001
Version: 1

Technical life time

Due to frequent changes in the software industry, the validity of the


ODW PSD has to be checked every year.
The PSD has to be checked every year on the following items:
A follow up PSD is implemented.
Operating systems or browsers are not supported anymore by its
suppliers.
e.g. MS support for Windows 95 stops completely.
Used applications are not supported anymore by its supplier
e.g. transition Acrobat 4 to 5.
The decision of changing the PSD is up to the PC Newton.

Copyright 2001

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released

Page:
31
Date:
August 15, 2001
Version: 1

6.

Functionality

6.1.

Introduction
This document specifies the functionality of Oc Doc Works R1.2.1. This
specification covers both the Desk and Pro configurations.
Oc Doc Works handles the job submission from the end users desk
towards the DPC and provides operator support for processing received
jobs.
For this, Oc Doc Works has a client side and a server side containing
the following groups of functionality:
Client
A submission client integrated with Windows print environments
A submission client for existing PDF files (integrated with the client
mentioned above)
A websubmitter for job submission via the Web
Server
An operator console for viewing, editing, printing and managing
incoming jobs
A Job Ticket Editor to configure the flexible job ticket definition
An administration module to administer and configure the system
A scan input for documents scanned on the Oc 3165
An open interface for import and export of jobs and ticket definitions
This document specifies the functionality of both the Desk and Pro
configurations. Topics only available in the Desk configuration will be
labeled Desk only, topics only available in the Pro configuration will be
labeled Pro only. All non-labeled topics are available in both
configurations.

6.1.1.

6.1.2.
6.1.2.1.

Changes with respect to R1.2


Windows 2000 support for ODW client.

Changes with respect to R1.1


Client side

Addition of PDF upload


Addition of web submitter

Only when using the original Client application (File- Print Oc Doc
Works), the ODW system is in control of the generated printable
document. With all other client side additions, the ODW system is not in
control and cannot guarantee the quality of the printable document.
This means that the promise of flawless printing cannot be
maintained for the total ODW system.
6.1.2.2.

Server side

Copyright 2001

Operator Console
o Addition of manual subset printing via Acrobat thumbnails

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released

6.1.3.

Page:
32
Date:
August 15, 2001
Version: 1
o List separator in log file based on regional settings
Job Ticket Editor
o Updated WYSIWYG user interface
o Import & export of ticket definitions
o Move of client bitmap selection to System Administration
application
Open interface
o Improvement of job ticket format for open interface (format
changed)
o Addition of open interface for ticket definitions
System Administration
o Move of logging settings to Job Ticket Editor
Printer Table Creator
o Completely updated user interface
o Change of printer tables file format
Installation
o Removal of NT, boot floppy and Acrobat installation
o Addition of full software only installation
o Addition of uninstall

Abbreviations
In this document the following abbreviations will be used.
ODW
PDF
DPC

6.2.

Oc Doc Works
Portable Document Format
Document Production Center

Client job submission


ODW offers three different ways of submitting jobs from a client towards
the ODW server:
File - Print Oc Doc Works (using a Client application)
PDF upload (integrated in the Client application)
Web submission (using a web-browser)
Only in the first option is the ODW system in control of the generated
printable document. With all other options the ODW system is not in
control and cannot guarantee the quality of the printable document.
This means that the promise of flawless printing cannot be
maintained for the total ODW system.

6.2.1.

Copyright 2001

File - Print - Oc Doc Works


The client application offers the user:
An easy way of submitting jobs from Windows office applications
towards the DPC. For the end-user the DPC is able to produce
documents in large quantities, enhance documents and/or offer
additional services.
A preview of the job to ensure that e.g. fonts and layout are correct.
A flexible digital job ticket to address the capabilities and services of
the DPC needed to produce the end-user job (note that these job
tickets are not comparable to device tickets as JEC or OJT). This
digital job ticket will be offered as a tree view of the settings. It is
also possible to install the Client on the ODW server.

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released

Page:
33
Date:
August 15, 2001
Version: 1
A separated message field is used to give additional information
from the DPC to the end-user (i.e. now duplex color printing
available).
A generic comment field is used to give the user the possibility to
provide additional information not covered in the job ticket settings.
(This depends on the ticket definition. A Comments field is included
in the default definition)

The progress of getting a connection to the server, retrieving the latest


job ticket settings, transferring the print data and job ticket are displayed
to the end-user.
6.2.1.1.

PDF

For each job a PDF file is generated to:


Describe the job contents in a device independent way.
Enable a preview of the document.
Adobe Acrobat Distiller R4.0, running on the Microsoft NT 4 server, is
used to generate PDF. Acrobat Distiller is configured in such a way that
the resulting output is optimised for printing. The resulting PDF is R1.3
compliant.
6.2.1.2.

Preview

The user has the possibility to preview the generated PDF file. On the
other hand a job can be submitted to the DPC without the need to wait
for the complete PDF file to be generated if the user doesnt want the
preview. To enable a preview of a job a PDF file is generated. Adobe
Acrobat Reader 4.0 is used to view the generated PDF.
Preview functionality is an optional feature.
6.2.1.3.

Notification

6.2.1.4.

Printer driver

See paragraph 3.3.8.


Adobe PS printer driver technology (latest available version) is used. An
ODW specific PPD file is used to optimize these PPD settings. The PPD
file will support the regular 43 Type 1 fonts (the same fonts as in our
engine products).
The PPD file is independently from which Microsoft Windows
environment (so the same for Windows 9x and NT and 2000
environment).
The Adobe PS printer driver depends on the Windows environment:
Driver for Windows 95/98
Driver for Windows NT 4
Driver for Windows 2000
The functional specifications of the printer driver are specified in a
separate document [DRIVER].
Note that the restrictions that hold for the Adobe PS driver also hold for
the ODW client job submission driver. The Windows 9x, NT and 2000
drivers cannot be shared (point & print) from the ODW server.
6.2.1.5.

Startup procedure

The client job submission application is installed as a generic process,


using the standard Windows mechanisms, so that it is always available.
If the job submission application is running, an icon is displayed in the
Windows system tray.
6.2.1.6.

Configuration

After installation there are two configurable items:


The IP address of the server is displayed and can be changed and or
extended. Instead of the IP address it is also possible to use the DNS
name. See also paragraph 3.4.1.
It is possible to change the name and/or location of the print file.

Copyright 2001

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released
6.2.1.7.

Page:
34
Date:
August 15, 2001
Version: 1

Remembered Job ticket items

Parts of the job ticket items are more or less static. This information is
stored on the client PC and is used as default value in the job ticket. The
job ticket items that are stored are defined with the Job Ticket Editor. If a
job ticket item is changed by the end-user, then this new value will be the
default value.
If possible to retrieve, the following fields are automatically filled in: login
name, computer name, company name, Client application version,
model name (extended/basic client), view name (fixed for now) and
definition identifier.
6.2.1.8.

Required job ticket items

Parts of the job ticket items are required (i.e. telephone number). Only if
the client fills in these job ticket settings with a correct value the job will
be accepted. Which job ticket items are required is defined with the Job
Ticket Editor.
6.2.1.9.

Language setting

Language is set during installation, choosing another language will mean,


install software again. The language setting must be the same as the
language used in the other ODW applications.
6.2.2.

PDF upload
The user has the possibility to submit existing PDF files towards the
ODW server.
The user will be asked to fill in a job ticket. This job ticket is equal to the
job ticket used for normal submission.
All sub paragraphs of paragraph 3.2.1 except 3.2.1.1, 3.2.1.4 also apply
to PDF upload.

6.2.2.1.

PDF file

The system will only be supported when used with valid PDF files. See
paragraph Error! Reference source not found.. Only one PDF file can
be submitted per job. So there is no support for multiple documents on a
single job.
The size of the PDF file will determine the submission speed. The
maximum file size depends on the available hardware of the ODW
server. The ODW server will not be able to accept files that are larger
then:
The available virtual memory on the ODW server or
Half the available disk space of the disk containing the storage
directory or
The available disk space of the disk containing the IIS ftproot
directory or
1Gb
6.2.2.2.

Ticket

The ticket that has to be filled in by the end-user is equal to the ticket
that is used in the client application (which is set using the Job Ticket
Editor).
The language of the ticket will be equal to the language used on the
ODW server software.
6.2.3.

Copyright 2001

Web submission (Pro only)


The web-submitter can be used to submit a combination of one existing
PDF file and a filled-in ticket to the ODW server, using a web-browser.

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released
6.2.3.1.

Page:
35
Date:
August 15, 2001
Version: 1

PDF file

The system will only be supported when used with valid PDF files. See
paragraph Error! Reference source not found.. Only one PDF file can
be submitted per job. So there is no support for multiple documents on a
single job.
The size of the PDF file will determine the submission speed. The
maximum file size depends on the available hardware of the ODW
server. The ODW server will not be able to accept files that are larger
then:
Half the available disk space of the disk containing the storage
directory or
The available disk space of the disk containing the Windows Temp
directory or
1Gb
6.2.3.2.

Ticket

The ticket that has to be filled in by the end-user is equal (the


presentation is comparable but not 100% equal) to the ticket that is used
in the client application (which is set using the Job Ticket Editor).
The language of the ticket will be equal to the language used on the
ODW server software.

6.3.
6.3.1.

6.3.1.1.

Operator Console
Job overview frame
In the job overview frame, all jobs in the system are shown. These jobs
are shown in a detailed view with several columns in which the main jobproperties are shown (Job number, user, status, ).
The jobs are stored in categories (folders), only one category is visible at
a time. Default there are two categories Unprocessed jobs and Ready
jobs. Only the user can move a job from Unprocessed jobs to Ready
jobs. A job can only be present in one category at a time.
Statuses of jobs in process

One of the main characteristics of a job in process is its status, which will
be displayed in the overview. The following statuses are automatically
detected and will change accordingly:
loading jobs, the ticket is present, the PDF document not.
new jobs, both ticket and PDF document are present, but not opened
yet
opened jobs
Opening a job means that the job is clicked and the ticket is shown,
comparable with e-mail programs.
jobs sent to printer
error jobs
The icons in the job overview list will represent the difference in status.
Furthermore a job can be marked ready, which will be done after
printing the job. The icons of all ready jobs will contain a ready mark.
6.3.1.2.

Announcement of new jobs

As stated, new jobs will be marked with a specific icon. Furthermore the
Operator is able to make the following settings for the announcement of
new jobs:
Pro only: Whether or not the ticket should be sent to a specific
printer automatically, as soon as a new job comes in

Copyright 2001

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released

Page:
36
Date:
August 15, 2001
Version: 1

Pro only: Whether or not a sound is played as soon as a new job


comes in. He is also able to choose the sound. (This depends on the
availability of a Sound card)
Furthermore the operator is able to automatically send an e-mail
message to the client, when a new job comes in.
Pro only: Announcement of news jobs can occur when the job comes in,
or when the operator first clicks on the jobs. This depends on an
Operator Console setting.
6.3.1.3.

Settings on the job list

An operator can make the following settings on his job list overview:
Pro only: Define the columns (number, content and order) of the
detailed view. All job ticket items and properties are available for
selecting them as the content of a column. The column settings will
be saved and restored, after, respectively, closing and opening the
application.
Pro only: Manage categories for jobs.
In order to manage the categories for jobs, it will be possible to
create new categories, delete categories and rename categories.
However, it will not be possible to make subcategories, i.e. nesting
categories in other categories. Furthermore, it is not possible to
delete the two default categories: Unprocessed jobs and Ready
jobs.
6.3.1.4.

Actions on the job list

An operator can perform the following actions on the job list:


Sort jobs on certain characteristics
It is possible to sort jobs on each property or settings shown in the
columns, by clicking the specific column. This mechanism is comparable
with the details view of Explorer.

6.3.2.
6.3.2.1.

Jobs
Actions on single job

When a job is selected in the job list, the job ticket frame shows the
settings of the job ticket. At that point the status of a document is
changed to opened. A number of actions on the selected job are
possible:

Copyright 2001

Desk only: Open document for viewing


Adobe Acrobat 4.0 is started, and the operator can view the
document. Saving of changes is not possible. (note: the print
function of Acrobat is directly integrated with the console).
Pro only: Open document for viewing and editing
Adobe Acrobat 4.0 is started, and the operator can perform all
actions supported by Adobe Acrobat and its plug-ins. After closing
Acrobat or the file, the changes are automatically saved to the PDF
file in the Operator Console. (note: the save and print function of
Acrobat are directly integrated with the console).
Acrobat makes a difference between plain edit functionality and, for
example, the booklet making of Quite. For simple editing the
document is modified, this in contrast with using Quite, which leads
to the creation of an extra document. Provisionally, only the
document with the focus, will be saved for ODW, when Acrobat is
closed.
Furthermore, a specific plug-in is be developed, by Quite on ODWs
specifications, for booklet making. This, in order to offer a simple
and easy-to-use user-interface for this functionality.

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released

6.3.2.2.

Page:
37
Date:
August 15, 2001
Version: 1
Pro only: Restore original file
With this function the original file is restored, only needed when the
operator accidentally saved the wrong file in Acrobat.
Print Job Ticket
Make a hardcopy of the job ticket that can be used for further
processing of the job or the ticket in the DPC. One printer can be
chosen to be the default ticket printer.
Pro only: Proof print
This function prints one copy of the document to a selected printer.
The settings of the job ticket will automatically be filled-in in the
printer driver, if possible. It will be made visible to the end user which
settings are not automatically handled. The operator can change
these, and other settings manually in the printer driver. The name of
the printer on which the proof print was made will be saved as an
extra job attribute.
Print Document
This function prints the whole job to the selected printer. Pro only:
The settings of the job ticket will automatically be filled in, in the
printer driver. Not all printers are totally supported, so it will be made
visible to the end user which settings are automatically handled and
which are not. The operator can change these non automatic and
other settings manually in the printer driver. Whether the driver
window is shown, depends on a per printer settings. For more
information about supported printers see also 4.2. The name of the
printer on which the print was made will be saved as an extra job
attribute.
Pro only: Move jobs to another category manually. It is not possible
to manually move jobs to the Ready jobs category. Use Mark jobs
as ready for this.
Mark jobs as ready.
When a job is marked ready, the icon will get a ready mark. As a
default the job is moved to the Ready jobs category. This can also
be turned off. It is also possible for the operator to automatically
send an e-mail to the client when he marks a job ready.
Delete jobs manually
Note: jobs that are in the Ready jobs category are deleted
automatically after a specified time frame.
Pro only: Export job manually,
The job, including the file and the ticket can be exported to any
directory the user wants, see also 5.1.
Save document as
The current PDF file of the document can be saved in any directory
the user wants.
Pro only: Send e-mail manually
As already mentioned, the operator is able to automatically send an
e-mail when a new job comes in or when a job is marked ready, see
also chapter 6. In addition it is also possible to send an e-mail
manually. In this case, the e-mail address of the client (of the
selected job) is used, and the Operator can type his own personal
message.

Actions on a multi-selection (Pro only)

It will be possible to select more then one job, using the standard button
combinations. In the menu is also a select all function available. The
following actions will stay available for a multi-selection of jobs:
Restore original file
Proof print, however this will only be convenient when the driver
window is set invisible by the operator, see also 4.2 Printer
configuration.
Copyright 2001

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released

6.3.2.3.

Page:
38
Date:
August 15, 2001
Version: 1
Print Document, just like proof print; this is only useful when the
operator sets the driver window invisible.
Print Job Ticket
Move jobs to another category manually
Mark jobs as ready
Delete jobs manually
Export jobs manually

New Jobs

Customers are sending jobs to the DPC; these are displayed as new in
the job overview. However there are two other ways of getting new jobs
into ODW:
Create new job
For creating a new job, the operator must select a PDF-file and fill in
a ticket. For this the same job ticket view is used as in the client
software. This function can be compared with PDF upload in the
client software.
Pro only: Import job manually
Single jobs can be imported manually, see for more information
paragraph 3.5.
6.3.3.

Job Ticket Frame


The settings shown in the job ticket frame are shown in the operator
view. This means that the settings do not have to be represented in the
same way as the end user sees them.
The operator can change the settings of the job ticket, but some of the
settings can be make read-only so that they cannot be changed. (e.g.
name owner, phone number, owner etc.). Furthermore some settings are
required, the operator must fill these in, before he is able to export,
delete or mark ready a job.
Making certain settings read-only and/or required, should be done in the
Job Ticket Editor.
Changes in the job ticket made by the operator are automatically saved.
Pro only: In the job ticket frame, the settings that are automatically
taken over into the printer driver of the selected printer can be
recognised by a small icons. Changing the values of a setting, or
selecting another printer could lead to a change in these icons.
Whether or not a setting can be taken over automatically is depending
on:
- the existence of a Printer Table for the driver of the selected printer.
This incorporates the capacities of the printer (an A4 printer will not
support the media size settings of an A3 job), see also paragraph
4.3.
- the existence of a mapping between a setting in the job ticket and a
setting in the printer driver. These mappings can be created in the
System Administration tool. The most frequently used mappings are
created by default.
The job ticket of the operator contains a notes field (this holds for the
default ticket. Customised tickets may not contain this field), where the
operator can enter comments to that specific job.

6.3.4.

Copyright 2001

Printers
In the printer overview, all the printers installed in the system (these are
all the printers installed under Windows NT) are visible except those that

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released

Page:
39
Date:
August 15, 2001
Version: 1

are Acrobat specific. The following information can be obtained from this
printer overview directly:
The currently selected printer
The default printer
The printer, to which all job tickets are sent
From this printer overview it is possible to reach the printer settings for
the several printers, in order to view or edit them, see paragraph 4.2. No
status feedback of the printers is offered.
6.3.4.1.

Printer overview

In the printer overview all available printers are visible. In the icons is
visualised, which printer is the default and which printer is the ticket
printer.
The currently selected printer has a blue or grey background (depending
on the PCs colour settings).
It is possible to:
Select another printer
Set another printer as ticket printer
Set another printer as the default.
6.3.4.2.

Printer configuration

An operator can configure individual printers in the printer Options menu:


Pro only: Set the visibility of the driver window on or off per printer. It
is only useful to hide the driver window, when a driver-translationtable is available.
Pro only: Availability and location of printer management tooling, like
Print logic.
When this field is filled in, it is possible to start up the printer
management application from within the operator console
In the printer options form also some special settings can be done, that
are required for printing with the help of Acrobat:
Set the Postscript level per printer.
Set binary printing on or off per printer.
Set truetype fonts on or off per printer
No NT printer settings can be done in the Operator Console. Limited load
balancing will be available via printer pools of NT. The number of
printers per pool is limited by NT specifications. Unfortunately the NT
specification is not clear on this. It states two or more print devices.
6.3.4.3.

Supported Printers

Only Oc DPS Postscript printers are supported, in combination with


their latest NT printer driver. Other printers may work, but are not
supported.
6.3.4.4.

Supported drivers for automatic takeover of settings (Pro only)

The settings of the job ticket can only be taken over in the printer driver,
when the following files are available on the Oc Doc Works system:
A printer-transformation-table for the driver of the selected printer
(each driver version needs a new table)
A mapping table, which contains information about the links between
ticket settings and driver items. A general mapping table will suffice.
In some cases a special mapping table for one specific printertransformation-table will be needed.
Oc R&D will only deliver the generic mapping table. All tables are
generated and tested by IS&S (partly outsource towards HWS DPS).
An application will be offered to Oc Support, in order to create and fill
new printer-transformation-tables, (see 3.3.4.5). Printer-transformationtables will be offered for the latest version of each DPS printer (these will
be created and released by IS&S). In the System Administration of Oc
Doc Works it is possible to edit or extend the links in the generic
Copyright 2001

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released

Page:
40
Date:
August 15, 2001
Version: 1

mapping table, or create printer specific mapping tables. This might be


needed when new printers are installed and/or when the ticket is changed
with the Ticket Editor, in order to rearrange the links between the values
of the ticket settings and the values of the driver items.
6.3.4.5.

Driver Table Creator (Pro only)

The Driver Table Creator assists IS&S (and HSW DPS) in the creation of
printer transformation tables. The driver for which the transformation
table is needed should be installed on the same NT 4 server system as
this application. A question-based discovery of possible printer settings
follows. This application will only be available in English and can be
installed with a regular setup application.
Using this application, printer transformation tables can be created for all
those drivers that store their document defaults information according to
the Win32 DEVMODE specification.
For those drivers that store their information outside the DEVMODE,
settings cannot be taken over into the driver.
6.3.4.6.

Printer feedback

6.3.4.7.

Banner page configuration

No printer feedback will be shown.


The operator console will not provide any banner page functionality
except for the banner page configuration that is possible in the Windows
NT printing mechanism.
6.3.5.
6.3.5.1.

Import job, PDF and ticket (Pro only)


Manually

Jobs can be imported manually by choosing the Import function in the


menu bar. In order to select a job, a PDF-file with corresponding ticket
file must be available in the same directory.
6.3.5.2.

Automatically

PDF files moved or copied into a so-called hot-folder are automatically


pulled into the ODW system using an Import Robot. For each PDF file
the default ticket is generated. This ticket can be overwritten with
settings from a per folder ticket file. After that this ticket can be
overwritten with a ticket file, belonging to that particular PDF file.
Hot-folders can be added and removed using the System Administration
application. For each hot-folder it can be specified if a ticket file is
required. If a ticket file is required, the PDF file is not imported before a
corresponding ticket file is available.
Files that are imported in ODW, will be deleted from the hot-folder
6.3.6.
6.3.6.1.

Export job, PDF and ticket (Pro only)


Manually

Jobs can be exported from the system manually by choosing the Export
function in the menu bar. This function will ask for a destination
elsewhere on the file system, copy the PDF file attached to the job to
that destination and create a ticket file with the same name (except for
its extension) in that destination. Note that both the original and the
edited PDF document (if available) are copied into the destination.
6.3.6.2.

Automatically

Jobs can be exported from the system automatically to a destination


specified in the ODW preferences. For each job that reaches the state
New and has a PDF file attached, the attached PDF file will be copied
to the destination, a ticket file will be created with the name (except for
its extension) in that destination.

Copyright 2001

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released

Page:
41
Date:
August 15, 2001
Version: 1

Optionally jobs that are exported can be removed from the ODW
system.
This option can be specified in the System Administration application.
6.3.7.

Ticket format (Pro only)


The format of the ticket file used for import and export is xml-based. See
[IMPEXP] for details.

6.3.8.

Customer Communication

6.3.8.1.

E-mail notification received

ODW offers the possibility to give an e-mail notification to the customer,


when the job is arrived at the DPC and the PDF-file is successfully
created. Only SMTP compliant mail-servers are supported.
For this, the customer should have filled in an e-mail address and
checked the box notify when arrived (when this option is in the client
ticket). In the Operator Console the operator is able to predefine the text
of these messages.
Pro only: As an extra the operator is able to attach the incoming PDF
file and the ticket to this e-mail.
6.3.8.2.

E-mail notification ready

The console application offers the possibility to give an e-mail


notification to the customer when his/her job is ready. Only SMTP
compliant mail-servers are supported.
Pro only: Furthermore he has the option to attach the current PDF-file
and/or the current ticket to his message. If the PDF is already changed
before an e-mail is sent, this edited version will be used.
When a job is marked ready and the customer has filled in an e-mail
address and checked the box notify when ready (when this option is in
the client ticket), an email message is send with the subject and a part of
the message filled in.
In the preferences the operator is able to set the predefined text for this
message. The operator is also able to switch off the preview of the email, so the e-mail can be send behind the scenes.

6.3.9.

Joblog
Joblog information on a job will be saved after:
deleting a job
marking a job ready
Pro only: printing a job
Pro only: proof printing a job
Pro only: exporting a job
Pro only: importing a job
See Job Log specification for details.
In the Job Ticket Editor can be set which settings must be logged and
which not.

6.3.10.

Preferences

6.3.10.1. Operator settings

The operator can set a lot of preferences. These will be offered at the
Option menu at the menu bar. For the following parts preferences can be
set:

Copyright 2001

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released

Page:
42
Date:
August 15, 2001
Version: 1
New jobs, including automatic notification e-mail to the customer,
see paragraph 3.3.1.2
Ready marked jobs, including automatic notification e-mail to the
customer, see paragraph 3.3.8.2
Pro only: Job overview; manage content of columns, manage
categories and sorting jobs, see paragraph 3.3.1.3 and 3.3.1.4
Printer configuration, see paragraph 3.3.4.1
The text of the client banner. This text will be displayed in the header
of the client ticket.

6.3.10.2. Implicit preferences:

The following aspects of the UI of the Operator Console can be changed


by the operator, and are automatically saved:
size and position of main window
size of Job window or frame
size of Printer window or frame
proportion of width between job ticket and job list within Job window
order, content and width of columns in the job list

6.4.

System Administration application


In the System administration application, the following items can be
configured.

6.4.1.

Oc Doc Works Station

6.4.2.

Licenses

6.4.3.

Import settings, like setting the import interval, see also paragraph
3.3.5.2

Automatic Export (Pro only)

Copyright 2001

View all available licenses.


Enter a license for an ODW option (all options, except the client
options)

Automatic Import (Pro only)

6.4.4.

Storage directory. Only directory on the hard disks of the ODW


system are supported. (So the storage directory may not be located
on a network drive)
ODW computer name (hostname or IP-address). This name must be
filled in, since it will be send to all clients. Each client will use this
address for the next submission. (This can e.g. be used to move all
client of an ODW system to a new system, without modifying all
client configurations)
Setting the time frame, after which the jobs from the Ready job
category will be deleted (no, 1 day, 7 days, )
Company logo. It is possible to specify a company logo.
Email settings
Mail server hostname & port number
Mail from address & name
Pro only: Mail CC address(es). Multiple addresses may be entered,
separated by a semicolon.
Pro only: Maximum size for mail attachments.

Export settings, like settings the target path, see paragraph 3.3.6.2

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released
6.4.5.

Advanced

6.5.

Page:
43
Date:
August 15, 2001
Version: 1

Pro only: As an advanced option, the mappings between job ticket


settings and settings in the printer drivers can be created within the
System administration, see also paragraph 3.3.4.5.
Update the query cache. The system uses a cache for fast searching
on job ticket items. This cache is maintained automatically, but may
become outdated when incomplete backups are performed.

Job Ticket Editor


The Job Ticket Editor enables an Oc consultant to maintain and change
the job ticket definition. This definition describes the capabilities and
services provided by the DPC. If desired, after some training, the
administrator can also use the Job Ticket Editor.

6.5.1.

Job ticket definition


A job ticket definition is a combination of a list of job ticket items and
multiple views on these items. Items may be present in multiple views.
For now two views are supported; one used for the submission clients
(Client application, Web submitter and New job in the Operator
Console), the second used in the Operator Console.

6.5.2.

Job ticket items


A job ticket item has an (English) identifier, a data type, a range of
possible values and (translated) captions. Items can be added or
removed.

6.5.3.

Job ticket views


A view specifies the presentation of (a subset of) the list of job ticket
items in a definition. Per view can be specified:
Which items are displayed
How these items are organized into a tree structure (both structure
and order can be specified)
Which items are required, read-only and remembered

6.5.4.

View and print


It is possible to view the resulting job ticket definition and/or to print out
the job ticket definition for a specific view.

6.5.5.

Identification
The system uses a (non-human readable) unique identifier to distinguish
between multiple definitions. For each definition a human readable
description can be entered.

6.5.6.

Open, Save, Import, Export


The Job Ticket Editor will load the current definition on start-up. From
this definition a copy will be made (with a new unique identifier) that can
be modified and can be saved. When a definition is saved, this definition
is set as the current definition that will be used by everyone that submits
a new job.
The Job Ticket Editor can also export a definition into a file to the file
system. This file can be imported on another system and set as the
current definition (or modified as new definition).

Copyright 2001

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released

Page:
44
Date:
August 15, 2001
Version: 1

6.5.7.

Factory defaults.
During the installation, a default definition will be installed, containing
default list of job ticket items and default views for the Client and the
Operator.
It is the intention that these factory defaults will cover the needs of a
large group of customers. The captions in the factory defaults depend on
the chosen language.

6.5.8.

Software protection
A software license key will protect the Job Ticket Editor.

6.6.

TIFF to PDF converter


The ODW system can be extended with a TIFF to PDF converter that
allows for scanned documents from an Oc 3165 (in TIFF format) to be
converted into PDF documents.

6.7.

Copy protection

6.7.1.

Client side
A software license key protects the job submission client. The preview
option is also protected with a software license key.

6.7.2.

Server side
The server is protected by a software license mechanism. The servers
will be serialised with a unique serial number. This serial number will be
distributed by M&L. Beside this serial number; each application will have
a software license key.
During start-up of the application it is checked if a valid license key is
available, if not a message dialog is presented to enter a valid license
key. These licenses can also be entered and viewed using the System
Administration application.
In this way the installed software is generic and the licenses can be
distributed separately.
The software licensing is detailed in [ODWLICENSE].

6.8.
6.8.1.

Other aspects
Language support
The language on the client and the server must be the same.
For the operating system for the server applications only Microsoft NT
English is supported.
The following table specifies the languages supported.
Language
UK English
Dutch
German
French
Danish
Italian
Norwegian
Portuguese
Spanish
Swedish

Copyright 2001

Oc-Technologies B.V.

Adobe Acrobat language


English
Dutch
German
French
International English
Italian
International English
Portuguese
Spanish
Swedish
Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released
Finnish
Us English

Page:
45
Date:
August 15, 2001
Version: 1
International English
English

Note that within the ODW software common dialogues of the operating
system are used, which will be in English.
6.8.2.

Help
The ODW applications will have online help functionality meant for the
user of those applications. Win help and context sensitive help will be
used; no support for tool tips.

6.8.3.

Homepage
Every ODW server will be equipped with a set of web pages called
homepage. This homepage will be in the same language as all other
ODW applications. It will not be modifiable by the operator or system
administrator.
This homepage gives access to the web submitter, some general ODW
information and a download page, where the following topics can be
downloaded:
The ODW Client application (setup)
The ODW optimized Distiller options
The ODW PPD file and a description on how to set its default
settings
The Adobe PS driver (setup)
Adobe Acrobat reader

Copyright 2001

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released

6.9.
6.9.1.
6.9.1.1.

Page:
46
Date:
August 15, 2001
Version: 1

Service Aspects
Performance
Number of concurrent submissions

The server will be able to support 10 concurrent submissions. This holds


for both the client application and the web submitter. (e.g. 5 submissions
using the client application concurrent with 5 submissions using the websubmitter is ok, 10 submissions using the client application concurrent
with 10 submissions using the web-submitter is not supported)
The speed of the submission depends on:
Network speed, load and configuration
Used hardware for the client PC and ODW server
Processor and memory load on both PCs.
Note that distilling is done sequentially. This means that once a job is
distilling, other jobs (including preview requests) will have to wait.
6.9.1.2.

Number of concurrent print operations

Only one concurrent print operation is allowed. A second print operation


can be started when the first print job is under complete control of the NT
print spooler.
6.9.1.3.

Number of jobs

The number of jobs the system can handle depends on the size of the
jobs and is limited by the overhead of job ticket information and the size
of the data partition of the PC. The response of the system is reasonable
if the total number of jobs in the system dont exceed 500 for regular
office jobs. If more jobs should be handled then the response can be
decreasing.
6.9.1.4.

Pro only: Number of concurrent Import/Export operations

Only one job can be imported at a time and only one job can be exported
at a time. Import and export can work in parallel.
6.9.1.5.

Hardware

The overall performance depends on the used hardware.


Reasonable performance is only guaranteed when the minimum server
configuration is used and only the specified applications are running. So
no support given if other applications are running.
6.9.2.

6.9.3.
6.9.3.1.

Release identification
Each separate ODW application has an about box menu item which
describes the global release identification, current release version of that
application copyright notices and the serial number and license key.
Diagnostics
Standard diagnostics

Standard Microsoft NT diagnostics tools are used:


ODW logs events in the application part of the NT event log. The
Event Viewer is used to display the logged information. Logging
information will be in English only.
NT Diagnostics application is used to get an overall overview of the
server.
NT Regedit application is used to get a detailed overview of the
server.
For ODW no additional diagnostics tools are developed.

Copyright 2001

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released
6.9.3.2.

Page:
47
Date:
August 15, 2001
Version: 1

Remote diagnostics

Remote diagnostics is handled outside the scope of the project. Remote


diagnostics is meant for the helpdesk. Probably ControlIT will be used.
ControlIT is handled and installed separately by a service technician
and/or consultant
6.9.4.

Backup/restore
For ODW no backup/restore functionality for the server is taken into
account. Most companies do have already a backup procedure in place.
Within the contract the backup/restore is handled.
As an alternative, the Opco can decide to install locally a customer
preferred backup mechanism (i.e. DAT) on the ODW server.
The location of relevant data (i.e. job store) can be configured by means
of the System Administration application.

6.9.5.

Distribution

6.9.5.1.

Client

The ODW client application is distributed using a CD-ROM. This CDROM also contains a distribution package that allows for easy
distributions over a network (single setup file download; this is not equal
to SMS!).
No silent setup foreseen. Also no hardware distribution is foreseen.
6.9.5.2.

Server

The ODW server software is distributed using a CD-ROM.


No special distribution from the Web is available. No silent setup
foreseen.
Also no hardware distribution is foreseen.
6.9.6.
6.9.6.1.

Installation
Client

For the ODW client software, an InstallShield setup is used. This


installation should be performed on a system that complies with one of
the client target environments specified in paragraph Error! Reference
source not found..
The installation will have no options. An un-install option is available.
6.9.6.2.

Server

For the ODW server software, an InstallShield setup procedure for CDROM installation is used. This installation should be performed on a
system that complies with the server target environment specified in
paragraph Error! Reference source not found..
This implies that any old version of Desk or Pro should be removed
before this installation is activated.
The installation will have no options. An un-install option is available.
6.9.7.

Upgrades
There will be no upgrade from existing Desk 1.1 or Pro 1.1 systems to
Desk 1.2 and/or Pro 1.2 systems. To upgrade these systems to Desk/Pro
1.2 a clean system is required, which implies that formatting of the hard
disk is required.
There will be an upgrade tool for the jobs and ticket definition of an
existing Desk 1.1 or Pro 1.1 system. This tool should be used before the
conversion to Desk/Pro 1.2. It will store the information on a user
specified location (probable a network drive). After the installation of the

Copyright 2001

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released

Page:
48
Date:
August 15, 2001
Version: 1

Desk/Pro 1.2 system has been completed, this data can be imported
again.

Copyright 2001

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released

Page:
49
Date:
August 15, 2001
Version: 1

Confidential

August 15, 2001


Oc Technologies B.V.

BU-DPS

Internal report 01.DPS.1022

Author

T. van den Honert

Department

BU-DPS

Tittle

Product Specification Document


Oc Doc Works R1.2.1

Keywords

Oc Doc Works, Newton

Abstract

The PSD of Oc Doc Works defines the functionality and quality of the
product, on a user and quality assurance abstraction level. This PSD is
the specification reference for:
The development of the product (project targets),
The development of documentation and manuals for the operations
departments (marketing, service and consultancy mgt), and
For quality assurance purpose during operation of the released product.

o
o
o

Agreed

A. Habets

Signature

Total of pages

44

Reference

To

Copy

Project Committee Newton

PI(BIC) (EWIJ)
MI-DPS (GP)

(AHH, THO, YWI, EPR, DAAS,


FVDK, TW, BEUT, MRON)

Copyright 2001

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released

Page:
50
Date:
August 15, 2001
Version: 1

0. Table of contents
1.

THE PRODUCT ..................................................................................................................................... 4


1.1.
1.2.
1.3.

MARKET ............................................................................................................................................ 4
THE PRODUCT ................................................................................................................................... 4
POSITION IN PORTFOLIO .................................................................................................................... 5

2.

TECHNICAL LIFE TIME ....................................................................................................................... 6

3.

FUNCTIONALITY .................................................................................................................................. 7
3.1. INTRODUCTION .................................................................................................................................. 7
3.1.1. Changes with respect to R1.2................................................................................................ 7
3.1.2. Changes with respect to R1.1................................................................................................ 7
3.1.3. Abbreviations........................................................................................................................... 8
3.2. CLIENT JOB SUBMISSION .................................................................................................................... 8
3.2.1. File - Print - Oc Doc Works .................................................................................................. 8
3.2.2. PDF upload............................................................................................................................ 10
3.2.3. Web submission (Pro only) .................................................................................................. 10
3.3. O PERATOR CONSOLE...................................................................................................................... 11
3.3.1. Job overview frame............................................................................................................... 11
3.3.2. Jobs........................................................................................................................................ 12
3.3.3. Job Ticket Frame .................................................................................................................. 14
3.3.4. Printers................................................................................................................................... 14
3.3.5. Import job, PDF and ticket (Pro only) .................................................................................. 16
3.3.6. Export job, PDF and ticket (Pro only).................................................................................. 16
3.3.7. Ticket format (Pro only) ........................................................................................................ 17
3.3.8. Customer Communication.................................................................................................... 17
3.3.9. Joblog..................................................................................................................................... 17
3.3.10.
Preferences ....................................................................................................................... 17
3.4. SYSTEM ADMINISTRATION APPLICATION........................................................................................... 18
3.4.1. Oc Doc Works Station ........................................................................................................ 18
3.4.2. Licenses................................................................................................................................. 18
3.4.3. Automatic Import (Pro only) ................................................................................................. 18
3.4.4. Automatic Export (Pro only) ................................................................................................. 18
3.4.5. Advanced............................................................................................................................... 19
3.5. JOB TICKET EDITOR ........................................................................................................................ 19
3.5.1. Job ticket definition ............................................................................................................... 19
3.5.2. Job ticket items ..................................................................................................................... 19
3.5.3. Job ticket views ..................................................................................................................... 19
3.5.4. View and print........................................................................................................................ 19
3.5.5. Identification........................................................................................................................... 19
3.5.6. Open, Save, Import, Export.................................................................................................. 19
3.5.7. Factory defaults..................................................................................................................... 20
3.5.8. Software protection ............................................................................................................... 20
3.6. TIFF TO PDF CONVERTER .............................................................................................................. 20
3.7. COPY PROTECTION.......................................................................................................................... 20
3.7.1. Client side .............................................................................................................................. 20
3.7.2. Server side............................................................................................................................. 20
3.8. O THER ASPECTS ............................................................................................................................. 20
3.8.1. Language support ................................................................................................................. 20
3.8.2. Help ........................................................................................................................................ 21
3.8.3. Homepage ............................................................................................................................. 21
3.9. SERVICE ASPECTS .......................................................................................................................... 22
3.9.1. Performance .......................................................................................................................... 22
3.9.2. Release identification............................................................................................................ 22
3.9.3. Diagnostics ............................................................................................................................ 22
3.9.4. Backup/restore ...................................................................................................................... 23

Copyright 2001

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released

Page:
51
Date:
August 15, 2001
Version: 1

3.9.5. Distribution............................................................................................................................. 23
3.9.6. Installation.............................................................................................................................. 23
3.9.7. Upgrades ............................................................................................................................... 23
3.10.
OC DPS400 PAGE PROGRAMMER ......................................... ERROR! BOOKMARK NOT DEFINED.
3.10.1.
Scope Oc DPS400 Page Programmer...............................Error! Bookmark not defined.
3.10.2.
Functionality Oc DPS400 Page Programmer ....................Error! Bookmark not defined.
3.10.3.
Limitations Oc DPS400 Page Programmer .......................Error! Bookmark not defined.
3.10.4.
Commercial aspects Oc DPS400 Page Programmer .......Error! Bookmark not defined.
3.10.5.
Service aspects Oc DPS400 Page Programmer...............Error! Bookmark not defined.
3.11.
RELATED DOCUMENTS .............................................................. ERROR! BOOKMARK NOT DEFINED.
4.

OPEN INTERFACES................................................................ERROR! BOOKMARK NOT DEFINED.

5.

CONFIGURATIONS .................................................................ERROR! BOOKMARK NOT DEFINED.


5.1.
5.2.
5.3.
5.4.

G ENERAL ..................................................................................... ERROR! BOOKMARK NOT DEFINED.


PROTECTION OF NEWTON-SOFTWARE ......................................... ERROR! BOOKMARK NOT DEFINED.
INTERRELATIONS .......................................................................... ERROR! BOOKMARK NOT DEFINED.
O PTIONAL FUNCTIONALITY............................................................ ERROR! BOOKMARK NOT DEFINED.

6.

PRODUCTIVITY/PERFORMANCE ........................................ERROR! BOOKMARK NOT DEFINED.

7.

SITE REQUIREMENTS ...........................................................ERROR! BOOKMARK NOT DEFINED.


7.1.
7.2.
7.3.
7.4.
7.5.
7.6.
7.7.

CLIENT APPLICATION .................................................................... ERROR! BOOKMARK NOT DEFINED.


W EB SUBMITTER CLIENT ............................................................... ERROR! BOOKMARK NOT DEFINED.
SERVER SOFTWARE ..................................................................... ERROR! BOOKMARK NOT DEFINED.
NETWORK ENVIRONMENT ............................................................. ERROR! BOOKMARK NOT DEFINED.
PDF FILES.................................................................................... ERROR! BOOKMARK NOT DEFINED.
O THER APPLICATIONS .................................................................. ERROR! BOOKMARK NOT DEFINED.
RELATED DOCUMENTS ................................................................. ERROR! BOOKMARK NOT DEFINED.

8.

INTERDEPENDENCIES ..........................................................ERROR! BOOKMARK NOT DEFINED.

9.

CONSULTING...........................................................................ERROR! BOOKMARK NOT DEFINED.

10.

SERVICE AND SUPPORT...................................................ERROR! BOOKMARK NOT DEFINED.

10.1.
INTRODUCTION ......................................................................... ERROR! BOOKMARK NOT DEFINED.
10.2.
IMPLEMENTATION...................................................................... ERROR! BOOKMARK NOT DEFINED.
10.2.1.
Implementation Services .......................................................Error! Bookmark not defined.
10.2.2.
Upgrades.................................................................................Error! Bookmark not defined.
10.3.
SUPPORT ................................................................................. ERROR! BOOKMARK NOT DEFINED.
10.3.1.
Support Services ....................................................................Error! Bookmark not defined.
10.4.
SERVICE KEY FIGURES .............................................................. ERROR! BOOKMARK NOT DEFINED.
10.4.1.
Remote Services ....................................................................Error! Bookmark not defined.
10.4.2.
Repairable items.....................................................................Error! Bookmark not defined.
10.4.3.
Support tools...........................................................................Error! Bookmark not defined.
10.5.
DOCUMENTATION ..................................................................... ERROR! BOOKMARK NOT DEFINED.
10.6.
TRAINING.................................................................................. ERROR! BOOKMARK NOT DEFINED.
10.7.
PRINTING TABLES ..................................................................... ERROR! BOOKMARK NOT DEFINED.
11.

ENVIRONMENTAL AND SAFETY ASPECTS ..................ERROR! BOOKMARK NOT DEFINED.

12.

SOFTWARE LICENSES ......................................................ERROR! BOOKMARK NOT DEFINED.

12.1.
12.2.
12.3.
12.4.
12.5.

ADOBE ..................................................................................... ERROR! BOOKMARK NOT DEFINED.


DBITECH COMPONENT TOOLBOX OCX V4.0............................ ERROR! BOOKMARK NOT DEFINED.
MICROSOFT XML ..................................................................... ERROR! BOOKMARK NOT DEFINED.
ASPEMAIL................................................................................. ERROR! BOOKMARK NOT DEFINED.
OC QUITE PLUG-IN ................................................................. ERROR! BOOKMARK NOT DEFINED.

Copyright 2001

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released

7.

The Product

7.1.

Market

Page:
52
Date:
August 15, 2001
Version: 1

Oc Doc Works is targeted at small to medium sized DPC's that are


shifting to digital printing. Typical volumes are in the range of 100k to 1
mln prints per month. In Europe there are about 25.000 of these sites.
Oc is present in about 5000 of them.
Especially the small DPC's are in the process of becoming more
professional and going digital, or of being outsourced or decentralised. In
surviving this development, DPC's can be led into a new phase by
providing them with digital products and software. Oc Doc Works is an
important element in supporting this digital workflow of the DPC.
Oc Doc Works is not specifically targeted at the print-for-profit market.
However, the openness of the product will enable the application of Oc
Doc Works in selected cases via e.g. partner extensions.

7.2.

The product
Oc Doc Works is a client server product that supports the digital
workflow to and in the DPC. In the DPC it also supports advanced
document production processes.
The functionality will be extended by successively developing new
modules. The modules provide functionality to submit digital jobs to the
DPC and to empower the operator in preparing and printing jobs.
Job submission to the DPC
A major unique selling point of Oc Doc Works is the digital repro job
ticket that solves the issue of getting digital jobs from the office to the
DPC. The job ticket is a digital equivalent of the current job ticket in
paper form that DPC's and end users are used to . All the services of the
DPC can be ordered directly from the end-user desktop in the office.
Job submission to the DPC is a relevant topic in each DPC. Therefore
this will be available in both the Desk and the Pro configuration of Oc
Doc Works.
Next to digital jobs coming from the office, there can be jobs from
external customers or there can be paper jobs that have to be scanned
before they can be printed.
Alternative inputs to the Oc Doc Works server are possible in the Pro
version through the 'import robot' (automatic PDF import folders). With
R1.2 we can also submit PDF files from the Oc Doc Works client or with
the Web Job Submitter. Furthermore scans by the Oc 3165 SL can be
imported in to Oc Doc Works.
Job preparation by the operator
Jobs often need some preparation by the operator before they are ready
to be printed. Examples are: lay out previewing, booklet making, adding
a scanned page, adding page numbers, merging documents, page
programming. By using the standard of PDF and Adobe Acrobat
software, many of the mentioned examples can be addressed by
integrating 3rd party products into the Oc Doc Works server.

Copyright 2001

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released

Page:
53
Date:
August 15, 2001
Version: 1

Job preparation is a means by which the operator can add value to the
job. Therefore we will integrate some of this functionality in the Pro
version of Oc Doc Works (e.g. booklet making). Page Programming for
the Oc DPS400 is implemented in R1.2.
Job printing support for the operator
Ultimately the operator wants to prints the jobs. Therefore a print server
needs to support all printers that are available in the repro. Additionally
the operator is better supported if he can control the printers from the
server and if he can easily send a job to a certain printer.
In Oc Doc Works Desk basic printing support for all printers is offered.
In the Pro version the operator gets more extensive printing support by
the 'direct printing' mechanism for a selection of printers.

7.3.
Oc Doc Works/Dirac/

Position in portfolio
Oc Doc Works is targeted at manned production environments. As such
Prisma/ORC Oc Doc Works is the successor of Oc ReproCenter. The
year 2001 will be a phase in/phase out period.
Oc Doc Works is not targeted at EDP-environments or at processing
transaction documents. Prismaflow will address this market of
unattended output management, later on succeeded by Dirac.
Mixed environments: Oc ReproCenter was based on the Prismaflow
product. This means that mixed environments could be addressed by
one product. In the new situation, with Oc Doc Works and Dirac, these
environments need special consideration.

Printer/copiers

Oc Doc Works will, as part of Oc DPC solutions, mainly be sold at


customers that have other Oc products that are targeted at central
environments. It is essential that all our DPC products are part of one
integrated sales approach. Integration with Oc 3165 R4 (Scan Logic)
and Oc DPS400 are major attention points.
In 2001, the Oc DPS400 will be Oc's major offering in the DPC. From
then on Oc Doc Works will become the 'Digital Desk' of the DPC, with
the Oc DPS400 as main production machine.
Oc Doc Works, as server that supports the operator, is able to connect
with Oc 3165 Scan Logic through the Scan2PDF option.
Oc Doc Works is able to print to any DPS printer as it uses the NT
postscript driver of each specific printer.

Other software

Printer management applications like Print Logic and EFI Command


Workstation can be used next to Oc Doc Works on the same server.
Main application for Office Exec is in the office, offering a uniform driver,
routing and accounting. The positioning of the DPC version of the Oc
USA product Office Exec is however close to the positioning of Oc Doc
Works, with job submission and operator support.

Copyright 2001

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released

8.

Page:
54
Date:
August 15, 2001
Version: 1

Technical life time

Due to frequent changes in the software industry, the validity of the


ODW PSD has to be checked every year.
The PSD has to be checked every year on the following items:
A follow up PSD is implemented.
Operating systems or browsers are not supported anymore by its
suppliers.
e.g. MS support for Windows 95 stops completely.
Used applications are not supported anymore by its supplier
e.g. transition Acrobat 4 to 5.
The decision of changing the PSD is up to the PC Newton.

Copyright 2001

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released

Page:
55
Date:
August 15, 2001
Version: 1

9.

Functionality

9.1.

Introduction
This document specifies the functionality of Oc Doc Works R1.2.1. This
specification covers both the Desk and Pro configurations.
Oc Doc Works handles the job submission from the end users desk
towards the DPC and provides operator support for processing received
jobs.
For this, Oc Doc Works has a client side and a server side containing
the following groups of functionality:
Client
A submission client integrated with Windows print environments
A submission client for existing PDF files (integrated with the client
mentioned above)
A websubmitter for job submission via the Web
Server
An operator console for viewing, editing, printing and managing
incoming jobs
A Job Ticket Editor to configure the flexible job ticket definition
An administration module to administer and configure the system
A scan input for documents scanned on the Oc 3165
An open interface for import and export of jobs and ticket definitions
This document specifies the functionality of both the Desk and Pro
configurations. Topics only available in the Desk configuration will be
labeled Desk only, topics only available in the Pro configuration will be
labeled Pro only. All non-labeled topics are available in both
configurations.

9.1.1.

9.1.2.
9.1.2.1.

Changes with respect to R1.2


Windows 2000 support for ODW client.

Changes with respect to R1.1


Client side

Addition of PDF upload


Addition of web submitter

Only when using the original Client application (File- Print Oc Doc
Works), the ODW system is in control of the generated printable
document. With all other client side additions, the ODW system is not in
control and cannot guarantee the quality of the printable document.
This means that the promise of flawless printing cannot be
maintained for the total ODW system.
9.1.2.2.

Server side

Copyright 2001

Operator Console
o Addition of manual subset printing via Acrobat thumbnails

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released

9.1.3.

Page:
56
Date:
August 15, 2001
Version: 1
o List separator in log file based on regional settings
Job Ticket Editor
o Updated WYSIWYG user interface
o Import & export of ticket definitions
o Move of client bitmap selection to System Administration
application
Open interface
o Improvement of job ticket format for open interface (format
changed)
o Addition of open interface for ticket definitions
System Administration
o Move of logging settings to Job Ticket Editor
Printer Table Creator
o Completely updated user interface
o Change of printer tables file format
Installation
o Removal of NT, boot floppy and Acrobat installation
o Addition of full software only installation
o Addition of uninstall

Abbreviations
In this document the following abbreviations will be used.
ODW
PDF
DPC

9.2.

Oc Doc Works
Portable Document Format
Document Production Center

Client job submission


ODW offers three different ways of submitting jobs from a client towards
the ODW server:
File - Print Oc Doc Works (using a Client application)
PDF upload (integrated in the Client application)
Web submission (using a web-browser)
Only in the first option is the ODW system in control of the generated
printable document. With all other options the ODW system is not in
control and cannot guarantee the quality of the printable document.
This means that the promise of flawless printing cannot be
maintained for the total ODW system.

9.2.1.

Copyright 2001

File - Print - Oc Doc Works


The client application offers the user:
An easy way of submitting jobs from Windows office applications
towards the DPC. For the end-user the DPC is able to produce
documents in large quantities, enhance documents and/or offer
additional services.
A preview of the job to ensure that e.g. fonts and layout are correct.
A flexible digital job ticket to address the capabilities and services of
the DPC needed to produce the end-user job (note that these job
tickets are not comparable to device tickets as JEC or OJT). This
digital job ticket will be offered as a tree view of the settings. It is
also possible to install the Client on the ODW server.

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released

Page:
57
Date:
August 15, 2001
Version: 1
A separated message field is used to give additional information
from the DPC to the end-user (i.e. now duplex color printing
available).
A generic comment field is used to give the user the possibility to
provide additional information not covered in the job ticket settings.
(This depends on the ticket definition. A Comments field is included
in the default definition)

The progress of getting a connection to the server, retrieving the latest


job ticket settings, transferring the print data and job ticket are displayed
to the end-user.
9.2.1.1.

PDF

For each job a PDF file is generated to:


Describe the job contents in a device independent way.
Enable a preview of the document.
Adobe Acrobat Distiller R4.0, running on the Microsoft NT 4 server, is
used to generate PDF. Acrobat Distiller is configured in such a way that
the resulting output is optimised for printing. The resulting PDF is R1.3
compliant.
9.2.1.2.

Preview

The user has the possibility to preview the generated PDF file. On the
other hand a job can be submitted to the DPC without the need to wait
for the complete PDF file to be generated if the user doesnt want the
preview. To enable a preview of a job a PDF file is generated. Adobe
Acrobat Reader 4.0 is used to view the generated PDF.
Preview functionality is an optional feature.
9.2.1.3.

Notification

9.2.1.4.

Printer driver

See paragraph 3.3.8.


Adobe PS printer driver technology (latest available version) is used. An
ODW specific PPD file is used to optimize these PPD settings. The PPD
file will support the regular 43 Type 1 fonts (the same fonts as in our
engine products).
The PPD file is independently from which Microsoft Windows
environment (so the same for Windows 9x and NT and 2000
environment).
The Adobe PS printer driver depends on the Windows environment:
Driver for Windows 95/98
Driver for Windows NT 4
Driver for Windows 2000
The functional specifications of the printer driver are specified in a
separate document [DRIVER].
Note that the restrictions that hold for the Adobe PS driver also hold for
the ODW client job submission driver. The Windows 9x, NT and 2000
drivers cannot be shared (point & print) from the ODW server.
9.2.1.5.

Startup procedure

The client job submission application is installed as a generic process,


using the standard Windows mechanisms, so that it is always available.
If the job submission application is running, an icon is displayed in the
Windows system tray.
9.2.1.6.

Configuration

After installation there are two configurable items:


The IP address of the server is displayed and can be changed and or
extended. Instead of the IP address it is also possible to use the DNS
name. See also paragraph 3.4.1.
It is possible to change the name and/or location of the print file.

Copyright 2001

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released
9.2.1.7.

Page:
58
Date:
August 15, 2001
Version: 1

Remembered Job ticket items

Parts of the job ticket items are more or less static. This information is
stored on the client PC and is used as default value in the job ticket. The
job ticket items that are stored are defined with the Job Ticket Editor. If a
job ticket item is changed by the end-user, then this new value will be the
default value.
If possible to retrieve, the following fields are automatically filled in: login
name, computer name, company name, Client application version,
model name (extended/basic client), view name (fixed for now) and
definition identifier.
9.2.1.8.

Required job ticket items

Parts of the job ticket items are required (i.e. telephone number). Only if
the client fills in these job ticket settings with a correct value the job will
be accepted. Which job ticket items are required is defined with the Job
Ticket Editor.
9.2.1.9.

Language setting

Language is set during installation, choosing another language will mean,


install software again. The language setting must be the same as the
language used in the other ODW applications.
9.2.2.

PDF upload
The user has the possibility to submit existing PDF files towards the
ODW server.
The user will be asked to fill in a job ticket. This job ticket is equal to the
job ticket used for normal submission.
All sub paragraphs of paragraph 3.2.1 except 3.2.1.1, 3.2.1.4 also apply
to PDF upload.

9.2.2.1.

PDF file

The system will only be supported when used with valid PDF files. See
paragraph Error! Reference source not found.. Only one PDF file can
be submitted per job. So there is no support for multiple documents on a
single job.
The size of the PDF file will determine the submission speed. The
maximum file size depends on the available hardware of the ODW
server. The ODW server will not be able to accept files that are larger
then:
The available virtual memory on the ODW server or
Half the available disk space of the disk containing the storage
directory or
The available disk space of the disk containing the IIS ftproot
directory or
1Gb
9.2.2.2.

Ticket

The ticket that has to be filled in by the end-user is equal to the ticket
that is used in the client application (which is set using the Job Ticket
Editor).
The language of the ticket will be equal to the language used on the
ODW server software.
9.2.3.

Copyright 2001

Web submission (Pro only)


The web-submitter can be used to submit a combination of one existing
PDF file and a filled-in ticket to the ODW server, using a web-browser.

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released
9.2.3.1.

Page:
59
Date:
August 15, 2001
Version: 1

PDF file

The system will only be supported when used with valid PDF files. See
paragraph Error! Reference source not found.. Only one PDF file can
be submitted per job. So there is no support for multiple documents on a
single job.
The size of the PDF file will determine the submission speed. The
maximum file size depends on the available hardware of the ODW
server. The ODW server will not be able to accept files that are larger
then:
Half the available disk space of the disk containing the storage
directory or
The available disk space of the disk containing the Windows Temp
directory or
1Gb
9.2.3.2.

Ticket

The ticket that has to be filled in by the end-user is equal (the


presentation is comparable but not 100% equal) to the ticket that is used
in the client application (which is set using the Job Ticket Editor).
The language of the ticket will be equal to the language used on the
ODW server software.

9.3.
9.3.1.

9.3.1.1.

Operator Console
Job overview frame
In the job overview frame, all jobs in the system are shown. These jobs
are shown in a detailed view with several columns in which the main jobproperties are shown (Job number, user, status, ).
The jobs are stored in categories (folders), only one category is visible at
a time. Default there are two categories Unprocessed jobs and Ready
jobs. Only the user can move a job from Unprocessed jobs to Ready
jobs. A job can only be present in one category at a time.
Statuses of jobs in process

One of the main characteristics of a job in process is its status, which will
be displayed in the overview. The following statuses are automatically
detected and will change accordingly:
loading jobs, the ticket is present, the PDF document not.
new jobs, both ticket and PDF document are present, but not opened
yet
opened jobs
Opening a job means that the job is clicked and the ticket is shown,
comparable with e-mail programs.
jobs sent to printer
error jobs
The icons in the job overview list will represent the difference in status.
Furthermore a job can be marked ready, which will be done after
printing the job. The icons of all ready jobs will contain a ready mark.
9.3.1.2.

Announcement of new jobs

As stated, new jobs will be marked with a specific icon. Furthermore the
Operator is able to make the following settings for the announcement of
new jobs:
Pro only: Whether or not the ticket should be sent to a specific
printer automatically, as soon as a new job comes in

Copyright 2001

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released

Page:
60
Date:
August 15, 2001
Version: 1

Pro only: Whether or not a sound is played as soon as a new job


comes in. He is also able to choose the sound. (This depends on the
availability of a Sound card)
Furthermore the operator is able to automatically send an e-mail
message to the client, when a new job comes in.
Pro only: Announcement of news jobs can occur when the job comes in,
or when the operator first clicks on the jobs. This depends on an
Operator Console setting.
9.3.1.3.

Settings on the job list

An operator can make the following settings on his job list overview:
Pro only: Define the columns (number, content and order) of the
detailed view. All job ticket items and properties are available for
selecting them as the content of a column. The column settings will
be saved and restored, after, respectively, closing and opening the
application.
Pro only: Manage categories for jobs.
In order to manage the categories for jobs, it will be possible to
create new categories, delete categories and rename categories.
However, it will not be possible to make subcategories, i.e. nesting
categories in other categories. Furthermore, it is not possible to
delete the two default categories: Unprocessed jobs and Ready
jobs.
9.3.1.4.

Actions on the job list

An operator can perform the following actions on the job list:


Sort jobs on certain characteristics
It is possible to sort jobs on each property or settings shown in the
columns, by clicking the specific column. This mechanism is comparable
with the details view of Explorer.

9.3.2.
9.3.2.1.

Jobs
Actions on single job

When a job is selected in the job list, the job ticket frame shows the
settings of the job ticket. At that point the status of a document is
changed to opened. A number of actions on the selected job are
possible:

Copyright 2001

Desk only: Open document for viewing


Adobe Acrobat 4.0 is started, and the operator can view the
document. Saving of changes is not possible. (note: the print
function of Acrobat is directly integrated with the console).
Pro only: Open document for viewing and editing
Adobe Acrobat 4.0 is started, and the operator can perform all
actions supported by Adobe Acrobat and its plug-ins. After closing
Acrobat or the file, the changes are automatically saved to the PDF
file in the Operator Console. (note: the save and print function of
Acrobat are directly integrated with the console).
Acrobat makes a difference between plain edit functionality and, for
example, the booklet making of Quite. For simple editing the
document is modified, this in contrast with using Quite, which leads
to the creation of an extra document. Provisionally, only the
document with the focus, will be saved for ODW, when Acrobat is
closed.
Furthermore, a specific plug-in is be developed, by Quite on ODWs
specifications, for booklet making. This, in order to offer a simple
and easy-to-use user-interface for this functionality.

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released

9.3.2.2.

Page:
61
Date:
August 15, 2001
Version: 1
Pro only: Restore original file
With this function the original file is restored, only needed when the
operator accidentally saved the wrong file in Acrobat.
Print Job Ticket
Make a hardcopy of the job ticket that can be used for further
processing of the job or the ticket in the DPC. One printer can be
chosen to be the default ticket printer.
Pro only: Proof print
This function prints one copy of the document to a selected printer.
The settings of the job ticket will automatically be filled-in in the
printer driver, if possible. It will be made visible to the end user which
settings are not automatically handled. The operator can change
these, and other settings manually in the printer driver. The name of
the printer on which the proof print was made will be saved as an
extra job attribute.
Print Document
This function prints the whole job to the selected printer. Pro only:
The settings of the job ticket will automatically be filled in, in the
printer driver. Not all printers are totally supported, so it will be made
visible to the end user which settings are automatically handled and
which are not. The operator can change these non automatic and
other settings manually in the printer driver. Whether the driver
window is shown, depends on a per printer settings. For more
information about supported printers see also 4.2. The name of the
printer on which the print was made will be saved as an extra job
attribute.
Pro only: Move jobs to another category manually. It is not possible
to manually move jobs to the Ready jobs category. Use Mark jobs
as ready for this.
Mark jobs as ready.
When a job is marked ready, the icon will get a ready mark. As a
default the job is moved to the Ready jobs category. This can also
be turned off. It is also possible for the operator to automatically
send an e-mail to the client when he marks a job ready.
Delete jobs manually
Note: jobs that are in the Ready jobs category are deleted
automatically after a specified time frame.
Pro only: Export job manually,
The job, including the file and the ticket can be exported to any
directory the user wants, see also 5.1.
Save document as
The current PDF file of the document can be saved in any directory
the user wants.
Pro only: Send e-mail manually
As already mentioned, the operator is able to automatically send an
e-mail when a new job comes in or when a job is marked ready, see
also chapter 6. In addition it is also possible to send an e-mail
manually. In this case, the e-mail address of the client (of the
selected job) is used, and the Operator can type his own personal
message.

Actions on a multi-selection (Pro only)

It will be possible to select more then one job, using the standard button
combinations. In the menu is also a select all function available. The
following actions will stay available for a multi-selection of jobs:
Restore original file
Proof print, however this will only be convenient when the driver
window is set invisible by the operator, see also 4.2 Printer
configuration.
Copyright 2001

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released

9.3.2.3.

Page:
62
Date:
August 15, 2001
Version: 1
Print Document, just like proof print; this is only useful when the
operator sets the driver window invisible.
Print Job Ticket
Move jobs to another category manually
Mark jobs as ready
Delete jobs manually
Export jobs manually

New Jobs

Customers are sending jobs to the DPC; these are displayed as new in
the job overview. However there are two other ways of getting new jobs
into ODW:
Create new job
For creating a new job, the operator must select a PDF-file and fill in
a ticket. For this the same job ticket view is used as in the client
software. This function can be compared with PDF upload in the
client software.
Pro only: Import job manually
Single jobs can be imported manually, see for more information
paragraph 3.5.
9.3.3.

Job Ticket Frame


The settings shown in the job ticket frame are shown in the operator
view. This means that the settings do not have to be represented in the
same way as the end user sees them.
The operator can change the settings of the job ticket, but some of the
settings can be make read-only so that they cannot be changed. (e.g.
name owner, phone number, owner etc.). Furthermore some settings are
required, the operator must fill these in, before he is able to export,
delete or mark ready a job.
Making certain settings read-only and/or required, should be done in the
Job Ticket Editor.
Changes in the job ticket made by the operator are automatically saved.
Pro only: In the job ticket frame, the settings that are automatically
taken over into the printer driver of the selected printer can be
recognised by a small icons. Changing the values of a setting, or
selecting another printer could lead to a change in these icons.
Whether or not a setting can be taken over automatically is depending
on:
- the existence of a Printer Table for the driver of the selected printer.
This incorporates the capacities of the printer (an A4 printer will not
support the media size settings of an A3 job), see also paragraph
4.3.
- the existence of a mapping between a setting in the job ticket and a
setting in the printer driver. These mappings can be created in the
System Administration tool. The most frequently used mappings are
created by default.
The job ticket of the operator contains a notes field (this holds for the
default ticket. Customised tickets may not contain this field), where the
operator can enter comments to that specific job.

9.3.4.

Copyright 2001

Printers
In the printer overview, all the printers installed in the system (these are
all the printers installed under Windows NT) are visible except those that

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released

Page:
63
Date:
August 15, 2001
Version: 1

are Acrobat specific. The following information can be obtained from this
printer overview directly:
The currently selected printer
The default printer
The printer, to which all job tickets are sent
From this printer overview it is possible to reach the printer settings for
the several printers, in order to view or edit them, see paragraph 4.2. No
status feedback of the printers is offered.
9.3.4.1.

Printer overview

In the printer overview all available printers are visible. In the icons is
visualised, which printer is the default and which printer is the ticket
printer.
The currently selected printer has a blue or grey background (depending
on the PCs colour settings).
It is possible to:
Select another printer
Set another printer as ticket printer
Set another printer as the default.
9.3.4.2.

Printer configuration

An operator can configure individual printers in the printer Options menu:


Pro only: Set the visibility of the driver window on or off per printer. It
is only useful to hide the driver window, when a driver-translationtable is available.
Pro only: Availability and location of printer management tooling, like
Print logic.
When this field is filled in, it is possible to start up the printer
management application from within the operator console
In the printer options form also some special settings can be done, that
are required for printing with the help of Acrobat:
Set the Postscript level per printer.
Set binary printing on or off per printer.
Set truetype fonts on or off per printer
No NT printer settings can be done in the Operator Console. Limited load
balancing will be available via printer pools of NT. The number of
printers per pool is limited by NT specifications. Unfortunately the NT
specification is not clear on this. It states two or more print devices.
9.3.4.3.

Supported Printers

Only Oc DPS Postscript printers are supported, in combination with


their latest NT printer driver. Other printers may work, but are not
supported.
9.3.4.4.

Supported drivers for automatic takeover of settings (Pro only)

The settings of the job ticket can only be taken over in the printer driver,
when the following files are available on the Oc Doc Works system:
A printer-transformation-table for the driver of the selected printer
(each driver version needs a new table)
A mapping table, which contains information about the links between
ticket settings and driver items. A general mapping table will suffice.
In some cases a special mapping table for one specific printertransformation-table will be needed.
Oc R&D will only deliver the generic mapping table. All tables are
generated and tested by IS&S (partly outsource towards HWS DPS).
An application will be offered to Oc Support, in order to create and fill
new printer-transformation-tables, (see 3.3.4.5). Printer-transformationtables will be offered for the latest version of each DPS printer (these will
be created and released by IS&S). In the System Administration of Oc
Doc Works it is possible to edit or extend the links in the generic
Copyright 2001

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released

Page:
64
Date:
August 15, 2001
Version: 1

mapping table, or create printer specific mapping tables. This might be


needed when new printers are installed and/or when the ticket is changed
with the Ticket Editor, in order to rearrange the links between the values
of the ticket settings and the values of the driver items.
9.3.4.5.

Driver Table Creator (Pro only)

The Driver Table Creator assists IS&S (and HSW DPS) in the creation of
printer transformation tables. The driver for which the transformation
table is needed should be installed on the same NT 4 server system as
this application. A question-based discovery of possible printer settings
follows. This application will only be available in English and can be
installed with a regular setup application.
Using this application, printer transformation tables can be created for all
those drivers that store their document defaults information according to
the Win32 DEVMODE specification.
For those drivers that store their information outside the DEVMODE,
settings cannot be taken over into the driver.
9.3.4.6.

Printer feedback

9.3.4.7.

Banner page configuration

No printer feedback will be shown.


The operator console will not provide any banner page functionality
except for the banner page configuration that is possible in the Windows
NT printing mechanism.
9.3.5.
9.3.5.1.

Import job, PDF and ticket (Pro only)


Manually

Jobs can be imported manually by choosing the Import function in the


menu bar. In order to select a job, a PDF-file with corresponding ticket
file must be available in the same directory.
9.3.5.2.

Automatically

PDF files moved or copied into a so-called hot-folder are automatically


pulled into the ODW system using an Import Robot. For each PDF file
the default ticket is generated. This ticket can be overwritten with
settings from a per folder ticket file. After that this ticket can be
overwritten with a ticket file, belonging to that particular PDF file.
Hot-folders can be added and removed using the System Administration
application. For each hot-folder it can be specified if a ticket file is
required. If a ticket file is required, the PDF file is not imported before a
corresponding ticket file is available.
Files that are imported in ODW, will be deleted from the hot-folder
9.3.6.
9.3.6.1.

Export job, PDF and ticket (Pro only)


Manually

Jobs can be exported from the system manually by choosing the Export
function in the menu bar. This function will ask for a destination
elsewhere on the file system, copy the PDF file attached to the job to
that destination and create a ticket file with the same name (except for
its extension) in that destination. Note that both the original and the
edited PDF document (if available) are copied into the destination.
9.3.6.2.

Automatically

Jobs can be exported from the system automatically to a destination


specified in the ODW preferences. For each job that reaches the state
New and has a PDF file attached, the attached PDF file will be copied
to the destination, a ticket file will be created with the name (except for
its extension) in that destination.

Copyright 2001

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released

Page:
65
Date:
August 15, 2001
Version: 1

Optionally jobs that are exported can be removed from the ODW
system.
This option can be specified in the System Administration application.
9.3.7.

Ticket format (Pro only)


The format of the ticket file used for import and export is xml-based. See
[IMPEXP] for details.

9.3.8.

Customer Communication

9.3.8.1.

E-mail notification received

ODW offers the possibility to give an e-mail notification to the customer,


when the job is arrived at the DPC and the PDF-file is successfully
created. Only SMTP compliant mail-servers are supported.
For this, the customer should have filled in an e-mail address and
checked the box notify when arrived (when this option is in the client
ticket). In the Operator Console the operator is able to predefine the text
of these messages.
Pro only: As an extra the operator is able to attach the incoming PDF
file and the ticket to this e-mail.
9.3.8.2.

E-mail notification ready

The console application offers the possibility to give an e-mail


notification to the customer when his/her job is ready. Only SMTP
compliant mail-servers are supported.
Pro only: Furthermore he has the option to attach the current PDF-file
and/or the current ticket to his message. If the PDF is already changed
before an e-mail is sent, this edited version will be used.
When a job is marked ready and the customer has filled in an e-mail
address and checked the box notify when ready (when this option is in
the client ticket), an email message is send with the subject and a part of
the message filled in.
In the preferences the operator is able to set the predefined text for this
message. The operator is also able to switch off the preview of the email, so the e-mail can be send behind the scenes.

9.3.9.

Joblog
Joblog information on a job will be saved after:
deleting a job
marking a job ready
Pro only: printing a job
Pro only: proof printing a job
Pro only: exporting a job
Pro only: importing a job
See Job Log specification for details.
In the Job Ticket Editor can be set which settings must be logged and
which not.

9.3.10.

Preferences

9.3.10.1. Operator settings

The operator can set a lot of preferences. These will be offered at the
Option menu at the menu bar. For the following parts preferences can be
set:

Copyright 2001

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released

Page:
66
Date:
August 15, 2001
Version: 1
New jobs, including automatic notification e-mail to the customer,
see paragraph 3.3.1.2
Ready marked jobs, including automatic notification e-mail to the
customer, see paragraph 3.3.8.2
Pro only: Job overview; manage content of columns, manage
categories and sorting jobs, see paragraph 3.3.1.3 and 3.3.1.4
Printer configuration, see paragraph 3.3.4.1
The text of the client banner. This text will be displayed in the header
of the client ticket.

9.3.10.2. Implicit preferences:

The following aspects of the UI of the Operator Console can be changed


by the operator, and are automatically saved:
size and position of main window
size of Job window or frame
size of Printer window or frame
proportion of width between job ticket and job list within Job window
order, content and width of columns in the job list

9.4.

System Administration application


In the System administration application, the following items can be
configured.

9.4.1.

Oc Doc Works Station

9.4.2.

Licenses

9.4.3.

Import settings, like setting the import interval, see also paragraph
3.3.5.2

Automatic Export (Pro only)

Copyright 2001

View all available licenses.


Enter a license for an ODW option (all options, except the client
options)

Automatic Import (Pro only)

9.4.4.

Storage directory. Only directory on the hard disks of the ODW


system are supported. (So the storage directory may not be located
on a network drive)
ODW computer name (hostname or IP-address). This name must be
filled in, since it will be send to all clients. Each client will use this
address for the next submission. (This can e.g. be used to move all
client of an ODW system to a new system, without modifying all
client configurations)
Setting the time frame, after which the jobs from the Ready job
category will be deleted (no, 1 day, 7 days, )
Company logo. It is possible to specify a company logo.
Email settings
Mail server hostname & port number
Mail from address & name
Pro only: Mail CC address(es). Multiple addresses may be entered,
separated by a semicolon.
Pro only: Maximum size for mail attachments.

Export settings, like settings the target path, see paragraph 3.3.6.2

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released
9.4.5.

Advanced

9.5.

Page:
67
Date:
August 15, 2001
Version: 1

Pro only: As an advanced option, the mappings between job ticket


settings and settings in the printer drivers can be created within the
System administration, see also paragraph 3.3.4.5.
Update the query cache. The system uses a cache for fast searching
on job ticket items. This cache is maintained automatically, but may
become outdated when incomplete backups are performed.

Job Ticket Editor


The Job Ticket Editor enables an Oc consultant to maintain and change
the job ticket definition. This definition describes the capabilities and
services provided by the DPC. If desired, after some training, the
administrator can also use the Job Ticket Editor.

9.5.1.

Job ticket definition


A job ticket definition is a combination of a list of job ticket items and
multiple views on these items. Items may be present in multiple views.
For now two views are supported; one used for the submission clients
(Client application, Web submitter and New job in the Operator
Console), the second used in the Operator Console.

9.5.2.

Job ticket items


A job ticket item has an (English) identifier, a data type, a range of
possible values and (translated) captions. Items can be added or
removed.

9.5.3.

Job ticket views


A view specifies the presentation of (a subset of) the list of job ticket
items in a definition. Per view can be specified:
Which items are displayed
How these items are organized into a tree structure (both structure
and order can be specified)
Which items are required, read-only and remembered

9.5.4.

View and print


It is possible to view the resulting job ticket definition and/or to print out
the job ticket definition for a specific view.

9.5.5.

Identification
The system uses a (non-human readable) unique identifier to distinguish
between multiple definitions. For each definition a human readable
description can be entered.

9.5.6.

Open, Save, Import, Export


The Job Ticket Editor will load the current definition on start-up. From
this definition a copy will be made (with a new unique identifier) that can
be modified and can be saved. When a definition is saved, this definition
is set as the current definition that will be used by everyone that submits
a new job.
The Job Ticket Editor can also export a definition into a file to the file
system. This file can be imported on another system and set as the
current definition (or modified as new definition).

Copyright 2001

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released

Page:
68
Date:
August 15, 2001
Version: 1

9.5.7.

Factory defaults.
During the installation, a default definition will be installed, containing
default list of job ticket items and default views for the Client and the
Operator.
It is the intention that these factory defaults will cover the needs of a
large group of customers. The captions in the factory defaults depend on
the chosen language.

9.5.8.

Software protection
A software license key will protect the Job Ticket Editor.

9.6.

TIFF to PDF converter


The ODW system can be extended with a TIFF to PDF converter that
allows for scanned documents from an Oc 3165 (in TIFF format) to be
converted into PDF documents.

9.7.

Copy protection

9.7.1.

Client side
A software license key protects the job submission client. The preview
option is also protected with a software license key.

9.7.2.

Server side
The server is protected by a software license mechanism. The servers
will be serialised with a unique serial number. This serial number will be
distributed by M&L. Beside this serial number; each application will have
a software license key.
During start-up of the application it is checked if a valid license key is
available, if not a message dialog is presented to enter a valid license
key. These licenses can also be entered and viewed using the System
Administration application.
In this way the installed software is generic and the licenses can be
distributed separately.
The software licensing is detailed in [ODWLICENSE].

9.8.
9.8.1.

Other aspects
Language support
The language on the client and the server must be the same.
For the operating system for the server applications only Microsoft NT
English is supported.
The following table specifies the languages supported.
Language
UK English
Dutch
German
French
Danish
Italian
Norwegian
Portuguese
Spanish
Swedish

Copyright 2001

Oc-Technologies B.V.

Adobe Acrobat language


English
Dutch
German
French
International English
Italian
International English
Portuguese
Spanish
Swedish
Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released
Finnish
Us English

Page:
69
Date:
August 15, 2001
Version: 1
International English
English

Note that within the ODW software common dialogues of the operating
system are used, which will be in English.
9.8.2.

Help
The ODW applications will have online help functionality meant for the
user of those applications. Win help and context sensitive help will be
used; no support for tool tips.

9.8.3.

Homepage
Every ODW server will be equipped with a set of web pages called
homepage. This homepage will be in the same language as all other
ODW applications. It will not be modifiable by the operator or system
administrator.
This homepage gives access to the web submitter, some general ODW
information and a download page, where the following topics can be
downloaded:
The ODW Client application (setup)
The ODW optimized Distiller options
The ODW PPD file and a description on how to set its default
settings
The Adobe PS driver (setup)
Adobe Acrobat reader

Copyright 2001

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released

9.9.
9.9.1.
9.9.1.1.

Page:
70
Date:
August 15, 2001
Version: 1

Service Aspects
Performance
Number of concurrent submissions

The server will be able to support 10 concurrent submissions. This holds


for both the client application and the web submitter. (e.g. 5 submissions
using the client application concurrent with 5 submissions using the websubmitter is ok, 10 submissions using the client application concurrent
with 10 submissions using the web-submitter is not supported)
The speed of the submission depends on:
Network speed, load and configuration
Used hardware for the client PC and ODW server
Processor and memory load on both PCs.
Note that distilling is done sequentially. This means that once a job is
distilling, other jobs (including preview requests) will have to wait.
9.9.1.2.

Number of concurrent print operations

Only one concurrent print operation is allowed. A second print operation


can be started when the first print job is under complete control of the NT
print spooler.
9.9.1.3.

Number of jobs

The number of jobs the system can handle depends on the size of the
jobs and is limited by the overhead of job ticket information and the size
of the data partition of the PC. The response of the system is reasonable
if the total number of jobs in the system dont exceed 500 for regular
office jobs. If more jobs should be handled then the response can be
decreasing.
9.9.1.4.

Pro only: Number of concurrent Import/Export operations

Only one job can be imported at a time and only one job can be exported
at a time. Import and export can work in parallel.
9.9.1.5.

Hardware

The overall performance depends on the used hardware.


Reasonable performance is only guaranteed when the minimum server
configuration is used and only the specified applications are running. So
no support given if other applications are running.
9.9.2.

9.9.3.
9.9.3.1.

Release identification
Each separate ODW application has an about box menu item which
describes the global release identification, current release version of that
application copyright notices and the serial number and license key.
Diagnostics
Standard diagnostics

Standard Microsoft NT diagnostics tools are used:


ODW logs events in the application part of the NT event log. The
Event Viewer is used to display the logged information. Logging
information will be in English only.
NT Diagnostics application is used to get an overall overview of the
server.
NT Regedit application is used to get a detailed overview of the
server.
For ODW no additional diagnostics tools are developed.

Copyright 2001

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released
9.9.3.2.

Page:
71
Date:
August 15, 2001
Version: 1

Remote diagnostics

Remote diagnostics is handled outside the scope of the project. Remote


diagnostics is meant for the helpdesk. Probably ControlIT will be used.
ControlIT is handled and installed separately by a service technician
and/or consultant
9.9.4.

Backup/restore
For ODW no backup/restore functionality for the server is taken into
account. Most companies do have already a backup procedure in place.
Within the contract the backup/restore is handled.
As an alternative, the Opco can decide to install locally a customer
preferred backup mechanism (i.e. DAT) on the ODW server.
The location of relevant data (i.e. job store) can be configured by means
of the System Administration application.

9.9.5.

Distribution

9.9.5.1.

Client

The ODW client application is distributed using a CD-ROM. This CDROM also contains a distribution package that allows for easy
distributions over a network (single setup file download; this is not equal
to SMS!).
No silent setup foreseen. Also no hardware distribution is foreseen.
9.9.5.2.

Server

The ODW server software is distributed using a CD-ROM.


No special distribution from the Web is available. No silent setup
foreseen.
Also no hardware distribution is foreseen.
9.9.6.
9.9.6.1.

Installation
Client

For the ODW client software, an InstallShield setup is used. This


installation should be performed on a system that complies with one of
the client target environments specified in paragraph Error! Reference
source not found..
The installation will have no options. An un-install option is available.
9.9.6.2.

Server

For the ODW server software, an InstallShield setup procedure for CDROM installation is used. This installation should be performed on a
system that complies with the server target environment specified in
paragraph Error! Reference source not found..
This implies that any old version of Desk or Pro should be removed
before this installation is activated.
The installation will have no options. An un-install option is available.
9.9.7.

Upgrades
There will be no upgrade from existing Desk 1.1 or Pro 1.1 systems to
Desk 1.2 and/or Pro 1.2 systems. To upgrade these systems to Desk/Pro
1.2 a clean system is required, which implies that formatting of the hard
disk is required.
There will be an upgrade tool for the jobs and ticket definition of an
existing Desk 1.1 or Pro 1.1 system. This tool should be used before the
conversion to Desk/Pro 1.2. It will store the information on a user
specified location (probable a network drive). After the installation of the

Copyright 2001

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released

Page:
72
Date:
August 15, 2001
Version: 1

Desk/Pro 1.2 system has been completed, this data can be imported
again.

Copyright 2001

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released

Page:
73
Date:
August 15, 2001
Version: 1

Confidential

August 15, 2001


Oc Technologies B.V.

BU-DPS

Internal report 01.DPS.1022

Author

T. van den Honert

Department

BU-DPS

Tittle

Product Specification Document


Oc Doc Works R1.2.1

Keywords

Oc Doc Works, Newton

Abstract

The PSD of Oc Doc Works defines the functionality and quality of the
product, on a user and quality assurance abstraction level. This PSD is
the specification reference for:
The development of the product (project targets),
The development of documentation and manuals for the operations
departments (marketing, service and consultancy mgt), and
For quality assurance purpose during operation of the released product.

o
o
o

Agreed

A. Habets

Signature

Total of pages

44

Reference

To

Copy

Project Committee Newton

PI(BIC) (EWIJ)
MI-DPS (GP)

(AHH, THO, YWI, EPR, DAAS,


FVDK, TW, BEUT, MRON)

Copyright 2001

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released

Page:
74
Date:
August 15, 2001
Version: 1

0. Table of contents
1.

THE PRODUCT ..................................................................................................................................... 4


1.1.
1.2.
1.3.

MARKET ............................................................................................................................................ 4
THE PRODUCT ................................................................................................................................... 4
POSITION IN PORTFOLIO .................................................................................................................... 5

2.

TECHNICAL LIFE TIME ....................................................................................................................... 6

3.

FUNCTIONALITY .................................................................................................................................. 7
3.1. INTRODUCTION .................................................................................................................................. 7
3.1.1. Changes with respect to R1.2................................................................................................ 7
3.1.2. Changes with respect to R1.1................................................................................................ 7
3.1.3. Abbreviations........................................................................................................................... 8
3.2. CLIENT JOB SUBMISSION .................................................................................................................... 8
3.2.1. File - Print - Oc Doc Works .................................................................................................. 8
3.2.2. PDF upload............................................................................................................................ 10
3.2.3. Web submission (Pro only) .................................................................................................. 10
3.3. O PERATOR CONSOLE...................................................................................................................... 11
3.3.1. Job overview frame............................................................................................................... 11
3.3.2. Jobs........................................................................................................................................ 12
3.3.3. Job Ticket Frame .................................................................................................................. 14
3.3.4. Printers................................................................................................................................... 14
3.3.5. Import job, PDF and ticket (Pro only) .................................................................................. 16
3.3.6. Export job, PDF and ticket (Pro only).................................................................................. 16
3.3.7. Ticket format (Pro only) ........................................................................................................ 17
3.3.8. Customer Communication.................................................................................................... 17
3.3.9. Joblog..................................................................................................................................... 17
3.3.10.
Preferences ....................................................................................................................... 17
3.4. SYSTEM ADMINISTRATION APPLICATION........................................................................................... 18
3.4.1. Oc Doc Works Station ........................................................................................................ 18
3.4.2. Licenses................................................................................................................................. 18
3.4.3. Automatic Import (Pro only) ................................................................................................. 18
3.4.4. Automatic Export (Pro only) ................................................................................................. 18
3.4.5. Advanced............................................................................................................................... 19
3.5. JOB TICKET EDITOR ........................................................................................................................ 19
3.5.1. Job ticket definition ............................................................................................................... 19
3.5.2. Job ticket items ..................................................................................................................... 19
3.5.3. Job ticket views ..................................................................................................................... 19
3.5.4. View and print........................................................................................................................ 19
3.5.5. Identification........................................................................................................................... 19
3.5.6. Open, Save, Import, Export.................................................................................................. 19
3.5.7. Factory defaults..................................................................................................................... 20
3.5.8. Software protection ............................................................................................................... 20
3.6. TIFF TO PDF CONVERTER .............................................................................................................. 20
3.7. COPY PROTECTION.......................................................................................................................... 20
3.7.1. Client side .............................................................................................................................. 20
3.7.2. Server side............................................................................................................................. 20
3.8. O THER ASPECTS ............................................................................................................................. 20
3.8.1. Language support ................................................................................................................. 20
3.8.2. Help ........................................................................................................................................ 21
3.8.3. Homepage ............................................................................................................................. 21
3.9. SERVICE ASPECTS .......................................................................................................................... 22
3.9.1. Performance .......................................................................................................................... 22
3.9.2. Release identification............................................................................................................ 22
3.9.3. Diagnostics ............................................................................................................................ 22
3.9.4. Backup/restore ...................................................................................................................... 23

Copyright 2001

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released

Page:
75
Date:
August 15, 2001
Version: 1

3.9.5. Distribution............................................................................................................................. 23
3.9.6. Installation.............................................................................................................................. 23
3.9.7. Upgrades ............................................................................................................................... 23
3.10.
OC DPS400 PAGE PROGRAMMER ......................................... ERROR! BOOKMARK NOT DEFINED.
3.10.1.
Scope Oc DPS400 Page Programmer...............................Error! Bookmark not defined.
3.10.2.
Functionality Oc DPS400 Page Programmer ....................Error! Bookmark not defined.
3.10.3.
Limitations Oc DPS400 Page Programmer .......................Error! Bookmark not defined.
3.10.4.
Commercial aspects Oc DPS400 Page Programmer .......Error! Bookmark not defined.
3.10.5.
Service aspects Oc DPS400 Page Programmer...............Error! Bookmark not defined.
3.11.
RELATED DOCUMENTS .............................................................. ERROR! BOOKMARK NOT DEFINED.
4.

OPEN INTERFACES................................................................ERROR! BOOKMARK NOT DEFINED.

5.

CONFIGURATIONS .................................................................ERROR! BOOKMARK NOT DEFINED.


5.1.
5.2.
5.3.
5.4.

G ENERAL ..................................................................................... ERROR! BOOKMARK NOT DEFINED.


PROTECTION OF NEWTON-SOFTWARE ......................................... ERROR! BOOKMARK NOT DEFINED.
INTERRELATIONS .......................................................................... ERROR! BOOKMARK NOT DEFINED.
O PTIONAL FUNCTIONALITY............................................................ ERROR! BOOKMARK NOT DEFINED.

6.

PRODUCTIVITY/PERFORMANCE ........................................ERROR! BOOKMARK NOT DEFINED.

7.

SITE REQUIREMENTS ...........................................................ERROR! BOOKMARK NOT DEFINED.


7.1.
7.2.
7.3.
7.4.
7.5.
7.6.
7.7.

CLIENT APPLICATION .................................................................... ERROR! BOOKMARK NOT DEFINED.


W EB SUBMITTER CLIENT ............................................................... ERROR! BOOKMARK NOT DEFINED.
SERVER SOFTWARE ..................................................................... ERROR! BOOKMARK NOT DEFINED.
NETWORK ENVIRONMENT ............................................................. ERROR! BOOKMARK NOT DEFINED.
PDF FILES.................................................................................... ERROR! BOOKMARK NOT DEFINED.
O THER APPLICATIONS .................................................................. ERROR! BOOKMARK NOT DEFINED.
RELATED DOCUMENTS ................................................................. ERROR! BOOKMARK NOT DEFINED.

8.

INTERDEPENDENCIES ..........................................................ERROR! BOOKMARK NOT DEFINED.

9.

CONSULTING...........................................................................ERROR! BOOKMARK NOT DEFINED.

10.

SERVICE AND SUPPORT...................................................ERROR! BOOKMARK NOT DEFINED.

10.1.
INTRODUCTION ......................................................................... ERROR! BOOKMARK NOT DEFINED.
10.2.
IMPLEMENTATION...................................................................... ERROR! BOOKMARK NOT DEFINED.
10.2.1.
Implementation Services .......................................................Error! Bookmark not defined.
10.2.2.
Upgrades.................................................................................Error! Bookmark not defined.
10.3.
SUPPORT ................................................................................. ERROR! BOOKMARK NOT DEFINED.
10.3.1.
Support Services ....................................................................Error! Bookmark not defined.
10.4.
SERVICE KEY FIGURES .............................................................. ERROR! BOOKMARK NOT DEFINED.
10.4.1.
Remote Services ....................................................................Error! Bookmark not defined.
10.4.2.
Repairable items.....................................................................Error! Bookmark not defined.
10.4.3.
Support tools...........................................................................Error! Bookmark not defined.
10.5.
DOCUMENTATION ..................................................................... ERROR! BOOKMARK NOT DEFINED.
10.6.
TRAINING.................................................................................. ERROR! BOOKMARK NOT DEFINED.
10.7.
PRINTING TABLES ..................................................................... ERROR! BOOKMARK NOT DEFINED.
11.

ENVIRONMENTAL AND SAFETY ASPECTS ..................ERROR! BOOKMARK NOT DEFINED.

12.

SOFTWARE LICENSES ......................................................ERROR! BOOKMARK NOT DEFINED.

12.1.
12.2.
12.3.
12.4.
12.5.

ADOBE ..................................................................................... ERROR! BOOKMARK NOT DEFINED.


DBITECH COMPONENT TOOLBOX OCX V4.0............................ ERROR! BOOKMARK NOT DEFINED.
MICROSOFT XML ..................................................................... ERROR! BOOKMARK NOT DEFINED.
ASPEMAIL................................................................................. ERROR! BOOKMARK NOT DEFINED.
OC QUITE PLUG-IN ................................................................. ERROR! BOOKMARK NOT DEFINED.

Copyright 2001

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released

10.

Page:
76
Date:
August 15, 2001
Version: 1

The Product

10.1. Market
Oc Doc Works is targeted at small to medium sized DPC's that are
shifting to digital printing. Typical volumes are in the range of 100k to 1
mln prints per month. In Europe there are about 25.000 of these sites.
Oc is present in about 5000 of them.
Especially the small DPC's are in the process of becoming more
professional and going digital, or of being outsourced or decentralised. In
surviving this development, DPC's can be led into a new phase by
providing them with digital products and software. Oc Doc Works is an
important element in supporting this digital workflow of the DPC.
Oc Doc Works is not specifically targeted at the print-for-profit market.
However, the openness of the product will enable the application of Oc
Doc Works in selected cases via e.g. partner extensions.

10.2. The product


Oc Doc Works is a client server product that supports the digital
workflow to and in the DPC. In the DPC it also supports advanced
document production processes.
The functionality will be extended by successively developing new
modules. The modules provide functionality to submit digital jobs to the
DPC and to empower the operator in preparing and printing jobs.
Job submission to the DPC
A major unique selling point of Oc Doc Works is the digital repro job
ticket that solves the issue of getting digital jobs from the office to the
DPC. The job ticket is a digital equivalent of the current job ticket in
paper form that DPC's and end users are used to . All the services of the
DPC can be ordered directly from the end-user desktop in the office.
Job submission to the DPC is a relevant topic in each DPC. Therefore
this will be available in both the Desk and the Pro configuration of Oc
Doc Works.
Next to digital jobs coming from the office, there can be jobs from
external customers or there can be paper jobs that have to be scanned
before they can be printed.
Alternative inputs to the Oc Doc Works server are possible in the Pro
version through the 'import robot' (automatic PDF import folders). With
R1.2 we can also submit PDF files from the Oc Doc Works client or with
the Web Job Submitter. Furthermore scans by the Oc 3165 SL can be
imported in to Oc Doc Works.
Job preparation by the operator
Jobs often need some preparation by the operator before they are ready
to be printed. Examples are: lay out previewing, booklet making, adding
a scanned page, adding page numbers, merging documents, page
programming. By using the standard of PDF and Adobe Acrobat
software, many of the mentioned examples can be addressed by
integrating 3rd party products into the Oc Doc Works server.

Copyright 2001

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released

Page:
77
Date:
August 15, 2001
Version: 1

Job preparation is a means by which the operator can add value to the
job. Therefore we will integrate some of this functionality in the Pro
version of Oc Doc Works (e.g. booklet making). Page Programming for
the Oc DPS400 is implemented in R1.2.
Job printing support for the operator
Ultimately the operator wants to prints the jobs. Therefore a print server
needs to support all printers that are available in the repro. Additionally
the operator is better supported if he can control the printers from the
server and if he can easily send a job to a certain printer.
In Oc Doc Works Desk basic printing support for all printers is offered.
In the Pro version the operator gets more extensive printing support by
the 'direct printing' mechanism for a selection of printers.

10.3. Position in portfolio


Oc Doc Works/Dirac/

Oc Doc Works is targeted at manned production environments. As such


Prisma/ORC Oc Doc Works is the successor of Oc ReproCenter. The
year 2001 will be a phase in/phase out period.
Oc Doc Works is not targeted at EDP-environments or at processing
transaction documents. Prismaflow will address this market of
unattended output management, later on succeeded by Dirac.
Mixed environments: Oc ReproCenter was based on the Prismaflow
product. This means that mixed environments could be addressed by
one product. In the new situation, with Oc Doc Works and Dirac, these
environments need special consideration.

Printer/copiers

Oc Doc Works will, as part of Oc DPC solutions, mainly be sold at


customers that have other Oc products that are targeted at central
environments. It is essential that all our DPC products are part of one
integrated sales approach. Integration with Oc 3165 R4 (Scan Logic)
and Oc DPS400 are major attention points.
In 2001, the Oc DPS400 will be Oc's major offering in the DPC. From
then on Oc Doc Works will become the 'Digital Desk' of the DPC, with
the Oc DPS400 as main production machine.
Oc Doc Works, as server that supports the operator, is able to connect
with Oc 3165 Scan Logic through the Scan2PDF option.
Oc Doc Works is able to print to any DPS printer as it uses the NT
postscript driver of each specific printer.

Other software

Printer management applications like Print Logic and EFI Command


Workstation can be used next to Oc Doc Works on the same server.
Main application for Office Exec is in the office, offering a uniform driver,
routing and accounting. The positioning of the DPC version of the Oc
USA product Office Exec is however close to the positioning of Oc Doc
Works, with job submission and operator support.

Copyright 2001

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released

11.

Page:
78
Date:
August 15, 2001
Version: 1

Technical life time

Due to frequent changes in the software industry, the validity of the


ODW PSD has to be checked every year.
The PSD has to be checked every year on the following items:
A follow up PSD is implemented.
Operating systems or browsers are not supported anymore by its
suppliers.
e.g. MS support for Windows 95 stops completely.
Used applications are not supported anymore by its supplier
e.g. transition Acrobat 4 to 5.
The decision of changing the PSD is up to the PC Newton.

Copyright 2001

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released

12.

Page:
79
Date:
August 15, 2001
Version: 1

Functionality

12.1. Introduction
This document specifies the functionality of Oc Doc Works R1.2.1. This
specification covers both the Desk and Pro configurations.
Oc Doc Works handles the job submission from the end users desk
towards the DPC and provides operator support for processing received
jobs.
For this, Oc Doc Works has a client side and a server side containing
the following groups of functionality:
Client
A submission client integrated with Windows print environments
A submission client for existing PDF files (integrated with the client
mentioned above)
A websubmitter for job submission via the Web
Server
An operator console for viewing, editing, printing and managing
incoming jobs
A Job Ticket Editor to configure the flexible job ticket definition
An administration module to administer and configure the system
A scan input for documents scanned on the Oc 3165
An open interface for import and export of jobs and ticket definitions
This document specifies the functionality of both the Desk and Pro
configurations. Topics only available in the Desk configuration will be
labeled Desk only, topics only available in the Pro configuration will be
labeled Pro only. All non-labeled topics are available in both
configurations.

12.1.1.

Changes with respect to R1.2


Windows 2000 support for ODW client.

12.1.2.

Changes with respect to R1.1

12.1.2.1. Client side

Addition of PDF upload


Addition of web submitter

Only when using the original Client application (File- Print Oc Doc
Works), the ODW system is in control of the generated printable
document. With all other client side additions, the ODW system is not in
control and cannot guarantee the quality of the printable document.
This means that the promise of flawless printing cannot be
maintained for the total ODW system.
12.1.2.2. Server side

Copyright 2001

Operator Console
o Addition of manual subset printing via Acrobat thumbnails

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released

12.1.3.

Page:
80
Date:
August 15, 2001
Version: 1
o List separator in log file based on regional settings
Job Ticket Editor
o Updated WYSIWYG user interface
o Import & export of ticket definitions
o Move of client bitmap selection to System Administration
application
Open interface
o Improvement of job ticket format for open interface (format
changed)
o Addition of open interface for ticket definitions
System Administration
o Move of logging settings to Job Ticket Editor
Printer Table Creator
o Completely updated user interface
o Change of printer tables file format
Installation
o Removal of NT, boot floppy and Acrobat installation
o Addition of full software only installation
o Addition of uninstall

Abbreviations
In this document the following abbreviations will be used.
ODW
PDF
DPC

Oc Doc Works
Portable Document Format
Document Production Center

12.2. Client job submission


ODW offers three different ways of submitting jobs from a client towards
the ODW server:
File - Print Oc Doc Works (using a Client application)
PDF upload (integrated in the Client application)
Web submission (using a web-browser)
Only in the first option is the ODW system in control of the generated
printable document. With all other options the ODW system is not in
control and cannot guarantee the quality of the printable document.
This means that the promise of flawless printing cannot be
maintained for the total ODW system.
12.2.1.

Copyright 2001

File - Print - Oc Doc Works


The client application offers the user:
An easy way of submitting jobs from Windows office applications
towards the DPC. For the end-user the DPC is able to produce
documents in large quantities, enhance documents and/or offer
additional services.
A preview of the job to ensure that e.g. fonts and layout are correct.
A flexible digital job ticket to address the capabilities and services of
the DPC needed to produce the end-user job (note that these job
tickets are not comparable to device tickets as JEC or OJT). This
digital job ticket will be offered as a tree view of the settings. It is
also possible to install the Client on the ODW server.

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released

Page:
81
Date:
August 15, 2001
Version: 1
A separated message field is used to give additional information
from the DPC to the end-user (i.e. now duplex color printing
available).
A generic comment field is used to give the user the possibility to
provide additional information not covered in the job ticket settings.
(This depends on the ticket definition. A Comments field is included
in the default definition)

The progress of getting a connection to the server, retrieving the latest


job ticket settings, transferring the print data and job ticket are displayed
to the end-user.
12.2.1.1. PDF

For each job a PDF file is generated to:


Describe the job contents in a device independent way.
Enable a preview of the document.
Adobe Acrobat Distiller R4.0, running on the Microsoft NT 4 server, is
used to generate PDF. Acrobat Distiller is configured in such a way that
the resulting output is optimised for printing. The resulting PDF is R1.3
compliant.
12.2.1.2. Preview

The user has the possibility to preview the generated PDF file. On the
other hand a job can be submitted to the DPC without the need to wait
for the complete PDF file to be generated if the user doesnt want the
preview. To enable a preview of a job a PDF file is generated. Adobe
Acrobat Reader 4.0 is used to view the generated PDF.
Preview functionality is an optional feature.
12.2.1.3. Notification

See paragraph 3.3.8.


12.2.1.4. Printer driver

Adobe PS printer driver technology (latest available version) is used. An


ODW specific PPD file is used to optimize these PPD settings. The PPD
file will support the regular 43 Type 1 fonts (the same fonts as in our
engine products).
The PPD file is independently from which Microsoft Windows
environment (so the same for Windows 9x and NT and 2000
environment).
The Adobe PS printer driver depends on the Windows environment:
Driver for Windows 95/98
Driver for Windows NT 4
Driver for Windows 2000
The functional specifications of the printer driver are specified in a
separate document [DRIVER].
Note that the restrictions that hold for the Adobe PS driver also hold for
the ODW client job submission driver. The Windows 9x, NT and 2000
drivers cannot be shared (point & print) from the ODW server.
12.2.1.5. Startup procedure

The client job submission application is installed as a generic process,


using the standard Windows mechanisms, so that it is always available.
If the job submission application is running, an icon is displayed in the
Windows system tray.
12.2.1.6. Configuration

After installation there are two configurable items:


The IP address of the server is displayed and can be changed and or
extended. Instead of the IP address it is also possible to use the DNS
name. See also paragraph 3.4.1.
It is possible to change the name and/or location of the print file.

Copyright 2001

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released

Page:
82
Date:
August 15, 2001
Version: 1

12.2.1.7. Remembered Job ticket items

Parts of the job ticket items are more or less static. This information is
stored on the client PC and is used as default value in the job ticket. The
job ticket items that are stored are defined with the Job Ticket Editor. If a
job ticket item is changed by the end-user, then this new value will be the
default value.
If possible to retrieve, the following fields are automatically filled in: login
name, computer name, company name, Client application version,
model name (extended/basic client), view name (fixed for now) and
definition identifier.
12.2.1.8. Required job ticket items

Parts of the job ticket items are required (i.e. telephone number). Only if
the client fills in these job ticket settings with a correct value the job will
be accepted. Which job ticket items are required is defined with the Job
Ticket Editor.
12.2.1.9. Language setting

Language is set during installation, choosing another language will mean,


install software again. The language setting must be the same as the
language used in the other ODW applications.
12.2.2.

PDF upload
The user has the possibility to submit existing PDF files towards the
ODW server.
The user will be asked to fill in a job ticket. This job ticket is equal to the
job ticket used for normal submission.
All sub paragraphs of paragraph 3.2.1 except 3.2.1.1, 3.2.1.4 also apply
to PDF upload.

12.2.2.1. PDF file

The system will only be supported when used with valid PDF files. See
paragraph Error! Reference source not found.. Only one PDF file can
be submitted per job. So there is no support for multiple documents on a
single job.
The size of the PDF file will determine the submission speed. The
maximum file size depends on the available hardware of the ODW
server. The ODW server will not be able to accept files that are larger
then:
The available virtual memory on the ODW server or
Half the available disk space of the disk containing the storage
directory or
The available disk space of the disk containing the IIS ftproot
directory or
1Gb
12.2.2.2. Ticket

The ticket that has to be filled in by the end-user is equal to the ticket
that is used in the client application (which is set using the Job Ticket
Editor).
The language of the ticket will be equal to the language used on the
ODW server software.
12.2.3.

Copyright 2001

Web submission (Pro only)


The web-submitter can be used to submit a combination of one existing
PDF file and a filled-in ticket to the ODW server, using a web-browser.

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released

Page:
83
Date:
August 15, 2001
Version: 1

12.2.3.1. PDF file

The system will only be supported when used with valid PDF files. See
paragraph Error! Reference source not found.. Only one PDF file can
be submitted per job. So there is no support for multiple documents on a
single job.
The size of the PDF file will determine the submission speed. The
maximum file size depends on the available hardware of the ODW
server. The ODW server will not be able to accept files that are larger
then:
Half the available disk space of the disk containing the storage
directory or
The available disk space of the disk containing the Windows Temp
directory or
1Gb
12.2.3.2. Ticket

The ticket that has to be filled in by the end-user is equal (the


presentation is comparable but not 100% equal) to the ticket that is used
in the client application (which is set using the Job Ticket Editor).
The language of the ticket will be equal to the language used on the
ODW server software.

12.3. Operator Console


12.3.1.

Job overview frame


In the job overview frame, all jobs in the system are shown. These jobs
are shown in a detailed view with several columns in which the main jobproperties are shown (Job number, user, status, ).
The jobs are stored in categories (folders), only one category is visible at
a time. Default there are two categories Unprocessed jobs and Ready
jobs. Only the user can move a job from Unprocessed jobs to Ready
jobs. A job can only be present in one category at a time.

12.3.1.1. Statuses of jobs in process

One of the main characteristics of a job in process is its status, which will
be displayed in the overview. The following statuses are automatically
detected and will change accordingly:
loading jobs, the ticket is present, the PDF document not.
new jobs, both ticket and PDF document are present, but not opened
yet
opened jobs
Opening a job means that the job is clicked and the ticket is shown,
comparable with e-mail programs.
jobs sent to printer
error jobs
The icons in the job overview list will represent the difference in status.
Furthermore a job can be marked ready, which will be done after
printing the job. The icons of all ready jobs will contain a ready mark.
12.3.1.2. Announcement of new jobs

As stated, new jobs will be marked with a specific icon. Furthermore the
Operator is able to make the following settings for the announcement of
new jobs:
Pro only: Whether or not the ticket should be sent to a specific
printer automatically, as soon as a new job comes in

Copyright 2001

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released

Page:
84
Date:
August 15, 2001
Version: 1

Pro only: Whether or not a sound is played as soon as a new job


comes in. He is also able to choose the sound. (This depends on the
availability of a Sound card)
Furthermore the operator is able to automatically send an e-mail
message to the client, when a new job comes in.
Pro only: Announcement of news jobs can occur when the job comes in,
or when the operator first clicks on the jobs. This depends on an
Operator Console setting.
12.3.1.3. Settings on the job list

An operator can make the following settings on his job list overview:
Pro only: Define the columns (number, content and order) of the
detailed view. All job ticket items and properties are available for
selecting them as the content of a column. The column settings will
be saved and restored, after, respectively, closing and opening the
application.
Pro only: Manage categories for jobs.
In order to manage the categories for jobs, it will be possible to
create new categories, delete categories and rename categories.
However, it will not be possible to make subcategories, i.e. nesting
categories in other categories. Furthermore, it is not possible to
delete the two default categories: Unprocessed jobs and Ready
jobs.
12.3.1.4. Actions on the job list

An operator can perform the following actions on the job list:


Sort jobs on certain characteristics
It is possible to sort jobs on each property or settings shown in the
columns, by clicking the specific column. This mechanism is comparable
with the details view of Explorer.

12.3.2.

Jobs

12.3.2.1. Actions on single job

When a job is selected in the job list, the job ticket frame shows the
settings of the job ticket. At that point the status of a document is
changed to opened. A number of actions on the selected job are
possible:

Copyright 2001

Desk only: Open document for viewing


Adobe Acrobat 4.0 is started, and the operator can view the
document. Saving of changes is not possible. (note: the print
function of Acrobat is directly integrated with the console).
Pro only: Open document for viewing and editing
Adobe Acrobat 4.0 is started, and the operator can perform all
actions supported by Adobe Acrobat and its plug-ins. After closing
Acrobat or the file, the changes are automatically saved to the PDF
file in the Operator Console. (note: the save and print function of
Acrobat are directly integrated with the console).
Acrobat makes a difference between plain edit functionality and, for
example, the booklet making of Quite. For simple editing the
document is modified, this in contrast with using Quite, which leads
to the creation of an extra document. Provisionally, only the
document with the focus, will be saved for ODW, when Acrobat is
closed.
Furthermore, a specific plug-in is be developed, by Quite on ODWs
specifications, for booklet making. This, in order to offer a simple
and easy-to-use user-interface for this functionality.

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released

Page:
85
Date:
August 15, 2001
Version: 1
Pro only: Restore original file
With this function the original file is restored, only needed when the
operator accidentally saved the wrong file in Acrobat.
Print Job Ticket
Make a hardcopy of the job ticket that can be used for further
processing of the job or the ticket in the DPC. One printer can be
chosen to be the default ticket printer.
Pro only: Proof print
This function prints one copy of the document to a selected printer.
The settings of the job ticket will automatically be filled-in in the
printer driver, if possible. It will be made visible to the end user which
settings are not automatically handled. The operator can change
these, and other settings manually in the printer driver. The name of
the printer on which the proof print was made will be saved as an
extra job attribute.
Print Document
This function prints the whole job to the selected printer. Pro only:
The settings of the job ticket will automatically be filled in, in the
printer driver. Not all printers are totally supported, so it will be made
visible to the end user which settings are automatically handled and
which are not. The operator can change these non automatic and
other settings manually in the printer driver. Whether the driver
window is shown, depends on a per printer settings. For more
information about supported printers see also 4.2. The name of the
printer on which the print was made will be saved as an extra job
attribute.
Pro only: Move jobs to another category manually. It is not possible
to manually move jobs to the Ready jobs category. Use Mark jobs
as ready for this.
Mark jobs as ready.
When a job is marked ready, the icon will get a ready mark. As a
default the job is moved to the Ready jobs category. This can also
be turned off. It is also possible for the operator to automatically
send an e-mail to the client when he marks a job ready.
Delete jobs manually
Note: jobs that are in the Ready jobs category are deleted
automatically after a specified time frame.
Pro only: Export job manually,
The job, including the file and the ticket can be exported to any
directory the user wants, see also 5.1.
Save document as
The current PDF file of the document can be saved in any directory
the user wants.
Pro only: Send e-mail manually
As already mentioned, the operator is able to automatically send an
e-mail when a new job comes in or when a job is marked ready, see
also chapter 6. In addition it is also possible to send an e-mail
manually. In this case, the e-mail address of the client (of the
selected job) is used, and the Operator can type his own personal
message.

12.3.2.2. Actions on a multi-selection (Pro only)

It will be possible to select more then one job, using the standard button
combinations. In the menu is also a select all function available. The
following actions will stay available for a multi-selection of jobs:
Restore original file
Proof print, however this will only be convenient when the driver
window is set invisible by the operator, see also 4.2 Printer
configuration.
Copyright 2001

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released

Page:
86
Date:
August 15, 2001
Version: 1
Print Document, just like proof print; this is only useful when the
operator sets the driver window invisible.
Print Job Ticket
Move jobs to another category manually
Mark jobs as ready
Delete jobs manually
Export jobs manually

12.3.2.3. New Jobs

Customers are sending jobs to the DPC; these are displayed as new in
the job overview. However there are two other ways of getting new jobs
into ODW:
Create new job
For creating a new job, the operator must select a PDF-file and fill in
a ticket. For this the same job ticket view is used as in the client
software. This function can be compared with PDF upload in the
client software.
Pro only: Import job manually
Single jobs can be imported manually, see for more information
paragraph 3.5.
12.3.3.

Job Ticket Frame


The settings shown in the job ticket frame are shown in the operator
view. This means that the settings do not have to be represented in the
same way as the end user sees them.
The operator can change the settings of the job ticket, but some of the
settings can be make read-only so that they cannot be changed. (e.g.
name owner, phone number, owner etc.). Furthermore some settings are
required, the operator must fill these in, before he is able to export,
delete or mark ready a job.
Making certain settings read-only and/or required, should be done in the
Job Ticket Editor.
Changes in the job ticket made by the operator are automatically saved.
Pro only: In the job ticket frame, the settings that are automatically
taken over into the printer driver of the selected printer can be
recognised by a small icons. Changing the values of a setting, or
selecting another printer could lead to a change in these icons.
Whether or not a setting can be taken over automatically is depending
on:
- the existence of a Printer Table for the driver of the selected printer.
This incorporates the capacities of the printer (an A4 printer will not
support the media size settings of an A3 job), see also paragraph
4.3.
- the existence of a mapping between a setting in the job ticket and a
setting in the printer driver. These mappings can be created in the
System Administration tool. The most frequently used mappings are
created by default.
The job ticket of the operator contains a notes field (this holds for the
default ticket. Customised tickets may not contain this field), where the
operator can enter comments to that specific job.

12.3.4.

Copyright 2001

Printers
In the printer overview, all the printers installed in the system (these are
all the printers installed under Windows NT) are visible except those that

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released

Page:
87
Date:
August 15, 2001
Version: 1

are Acrobat specific. The following information can be obtained from this
printer overview directly:
The currently selected printer
The default printer
The printer, to which all job tickets are sent
From this printer overview it is possible to reach the printer settings for
the several printers, in order to view or edit them, see paragraph 4.2. No
status feedback of the printers is offered.
12.3.4.1. Printer overview

In the printer overview all available printers are visible. In the icons is
visualised, which printer is the default and which printer is the ticket
printer.
The currently selected printer has a blue or grey background (depending
on the PCs colour settings).
It is possible to:
Select another printer
Set another printer as ticket printer
Set another printer as the default.
12.3.4.2. Printer configuration

An operator can configure individual printers in the printer Options menu:


Pro only: Set the visibility of the driver window on or off per printer. It
is only useful to hide the driver window, when a driver-translationtable is available.
Pro only: Availability and location of printer management tooling, like
Print logic.
When this field is filled in, it is possible to start up the printer
management application from within the operator console
In the printer options form also some special settings can be done, that
are required for printing with the help of Acrobat:
Set the Postscript level per printer.
Set binary printing on or off per printer.
Set truetype fonts on or off per printer
No NT printer settings can be done in the Operator Console. Limited load
balancing will be available via printer pools of NT. The number of
printers per pool is limited by NT specifications. Unfortunately the NT
specification is not clear on this. It states two or more print devices.
12.3.4.3. Supported Printers

Only Oc DPS Postscript printers are supported, in combination with


their latest NT printer driver. Other printers may work, but are not
supported.
12.3.4.4. Supported drivers for automatic takeover of settings (Pro only)

The settings of the job ticket can only be taken over in the printer driver,
when the following files are available on the Oc Doc Works system:
A printer-transformation-table for the driver of the selected printer
(each driver version needs a new table)
A mapping table, which contains information about the links between
ticket settings and driver items. A general mapping table will suffice.
In some cases a special mapping table for one specific printertransformation-table will be needed.
Oc R&D will only deliver the generic mapping table. All tables are
generated and tested by IS&S (partly outsource towards HWS DPS).
An application will be offered to Oc Support, in order to create and fill
new printer-transformation-tables, (see 3.3.4.5). Printer-transformationtables will be offered for the latest version of each DPS printer (these will
be created and released by IS&S). In the System Administration of Oc
Doc Works it is possible to edit or extend the links in the generic
Copyright 2001

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released

Page:
88
Date:
August 15, 2001
Version: 1

mapping table, or create printer specific mapping tables. This might be


needed when new printers are installed and/or when the ticket is changed
with the Ticket Editor, in order to rearrange the links between the values
of the ticket settings and the values of the driver items.
12.3.4.5. Driver Table Creator (Pro only)

The Driver Table Creator assists IS&S (and HSW DPS) in the creation of
printer transformation tables. The driver for which the transformation
table is needed should be installed on the same NT 4 server system as
this application. A question-based discovery of possible printer settings
follows. This application will only be available in English and can be
installed with a regular setup application.
Using this application, printer transformation tables can be created for all
those drivers that store their document defaults information according to
the Win32 DEVMODE specification.
For those drivers that store their information outside the DEVMODE,
settings cannot be taken over into the driver.
12.3.4.6. Printer feedback

No printer feedback will be shown.


12.3.4.7. Banner page configuration

The operator console will not provide any banner page functionality
except for the banner page configuration that is possible in the Windows
NT printing mechanism.
12.3.5.

Import job, PDF and ticket (Pro only)

12.3.5.1. Manually

Jobs can be imported manually by choosing the Import function in the


menu bar. In order to select a job, a PDF-file with corresponding ticket
file must be available in the same directory.
12.3.5.2. Automatically

PDF files moved or copied into a so-called hot-folder are automatically


pulled into the ODW system using an Import Robot. For each PDF file
the default ticket is generated. This ticket can be overwritten with
settings from a per folder ticket file. After that this ticket can be
overwritten with a ticket file, belonging to that particular PDF file.
Hot-folders can be added and removed using the System Administration
application. For each hot-folder it can be specified if a ticket file is
required. If a ticket file is required, the PDF file is not imported before a
corresponding ticket file is available.
Files that are imported in ODW, will be deleted from the hot-folder
12.3.6.

Export job, PDF and ticket (Pro only)

12.3.6.1. Manually

Jobs can be exported from the system manually by choosing the Export
function in the menu bar. This function will ask for a destination
elsewhere on the file system, copy the PDF file attached to the job to
that destination and create a ticket file with the same name (except for
its extension) in that destination. Note that both the original and the
edited PDF document (if available) are copied into the destination.
12.3.6.2. Automatically

Jobs can be exported from the system automatically to a destination


specified in the ODW preferences. For each job that reaches the state
New and has a PDF file attached, the attached PDF file will be copied
to the destination, a ticket file will be created with the name (except for
its extension) in that destination.

Copyright 2001

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released

Page:
89
Date:
August 15, 2001
Version: 1

Optionally jobs that are exported can be removed from the ODW
system.
This option can be specified in the System Administration application.
12.3.7.

Ticket format (Pro only)


The format of the ticket file used for import and export is xml-based. See
[IMPEXP] for details.

12.3.8.

Customer Communication

12.3.8.1. E-mail notification received

ODW offers the possibility to give an e-mail notification to the customer,


when the job is arrived at the DPC and the PDF-file is successfully
created. Only SMTP compliant mail-servers are supported.
For this, the customer should have filled in an e-mail address and
checked the box notify when arrived (when this option is in the client
ticket). In the Operator Console the operator is able to predefine the text
of these messages.
Pro only: As an extra the operator is able to attach the incoming PDF
file and the ticket to this e-mail.
12.3.8.2. E-mail notification ready

The console application offers the possibility to give an e-mail


notification to the customer when his/her job is ready. Only SMTP
compliant mail-servers are supported.
Pro only: Furthermore he has the option to attach the current PDF-file
and/or the current ticket to his message. If the PDF is already changed
before an e-mail is sent, this edited version will be used.
When a job is marked ready and the customer has filled in an e-mail
address and checked the box notify when ready (when this option is in
the client ticket), an email message is send with the subject and a part of
the message filled in.
In the preferences the operator is able to set the predefined text for this
message. The operator is also able to switch off the preview of the email, so the e-mail can be send behind the scenes.

12.3.9.

Joblog
Joblog information on a job will be saved after:
deleting a job
marking a job ready
Pro only: printing a job
Pro only: proof printing a job
Pro only: exporting a job
Pro only: importing a job
See Job Log specification for details.
In the Job Ticket Editor can be set which settings must be logged and
which not.

12.3.10.

Preferences

12.3.10.1. Operator settings

The operator can set a lot of preferences. These will be offered at the
Option menu at the menu bar. For the following parts preferences can be
set:

Copyright 2001

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released

Page:
90
Date:
August 15, 2001
Version: 1
New jobs, including automatic notification e-mail to the customer,
see paragraph 3.3.1.2
Ready marked jobs, including automatic notification e-mail to the
customer, see paragraph 3.3.8.2
Pro only: Job overview; manage content of columns, manage
categories and sorting jobs, see paragraph 3.3.1.3 and 3.3.1.4
Printer configuration, see paragraph 3.3.4.1
The text of the client banner. This text will be displayed in the header
of the client ticket.

12.3.10.2. Implicit preferences:

The following aspects of the UI of the Operator Console can be changed


by the operator, and are automatically saved:
size and position of main window
size of Job window or frame
size of Printer window or frame
proportion of width between job ticket and job list within Job window
order, content and width of columns in the job list

12.4. System Administration application


In the System administration application, the following items can be
configured.
12.4.1.

Oc Doc Works Station

12.4.2.

Licenses

12.4.3.

Import settings, like setting the import interval, see also paragraph
3.3.5.2

Automatic Export (Pro only)

Copyright 2001

View all available licenses.


Enter a license for an ODW option (all options, except the client
options)

Automatic Import (Pro only)

12.4.4.

Storage directory. Only directory on the hard disks of the ODW


system are supported. (So the storage directory may not be located
on a network drive)
ODW computer name (hostname or IP-address). This name must be
filled in, since it will be send to all clients. Each client will use this
address for the next submission. (This can e.g. be used to move all
client of an ODW system to a new system, without modifying all
client configurations)
Setting the time frame, after which the jobs from the Ready job
category will be deleted (no, 1 day, 7 days, )
Company logo. It is possible to specify a company logo.
Email settings
Mail server hostname & port number
Mail from address & name
Pro only: Mail CC address(es). Multiple addresses may be entered,
separated by a semicolon.
Pro only: Maximum size for mail attachments.

Export settings, like settings the target path, see paragraph 3.3.6.2

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released
12.4.5.

Page:
91
Date:
August 15, 2001
Version: 1

Advanced

Pro only: As an advanced option, the mappings between job ticket


settings and settings in the printer drivers can be created within the
System administration, see also paragraph 3.3.4.5.
Update the query cache. The system uses a cache for fast searching
on job ticket items. This cache is maintained automatically, but may
become outdated when incomplete backups are performed.

12.5. Job Ticket Editor


The Job Ticket Editor enables an Oc consultant to maintain and change
the job ticket definition. This definition describes the capabilities and
services provided by the DPC. If desired, after some training, the
administrator can also use the Job Ticket Editor.
12.5.1.

Job ticket definition


A job ticket definition is a combination of a list of job ticket items and
multiple views on these items. Items may be present in multiple views.
For now two views are supported; one used for the submission clients
(Client application, Web submitter and New job in the Operator
Console), the second used in the Operator Console.

12.5.2.

Job ticket items


A job ticket item has an (English) identifier, a data type, a range of
possible values and (translated) captions. Items can be added or
removed.

12.5.3.

Job ticket views


A view specifies the presentation of (a subset of) the list of job ticket
items in a definition. Per view can be specified:
Which items are displayed
How these items are organized into a tree structure (both structure
and order can be specified)
Which items are required, read-only and remembered

12.5.4.

View and print


It is possible to view the resulting job ticket definition and/or to print out
the job ticket definition for a specific view.

12.5.5.

Identification
The system uses a (non-human readable) unique identifier to distinguish
between multiple definitions. For each definition a human readable
description can be entered.

12.5.6.

Open, Save, Import, Export


The Job Ticket Editor will load the current definition on start-up. From
this definition a copy will be made (with a new unique identifier) that can
be modified and can be saved. When a definition is saved, this definition
is set as the current definition that will be used by everyone that submits
a new job.
The Job Ticket Editor can also export a definition into a file to the file
system. This file can be imported on another system and set as the
current definition (or modified as new definition).

Copyright 2001

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released

Page:
92
Date:
August 15, 2001
Version: 1

12.5.7.

Factory defaults.
During the installation, a default definition will be installed, containing
default list of job ticket items and default views for the Client and the
Operator.
It is the intention that these factory defaults will cover the needs of a
large group of customers. The captions in the factory defaults depend on
the chosen language.

12.5.8.

Software protection
A software license key will protect the Job Ticket Editor.

12.6. TIFF to PDF converter


The ODW system can be extended with a TIFF to PDF converter that
allows for scanned documents from an Oc 3165 (in TIFF format) to be
converted into PDF documents.

12.7. Copy protection


12.7.1.

Client side
A software license key protects the job submission client. The preview
option is also protected with a software license key.

12.7.2.

Server side
The server is protected by a software license mechanism. The servers
will be serialised with a unique serial number. This serial number will be
distributed by M&L. Beside this serial number; each application will have
a software license key.
During start-up of the application it is checked if a valid license key is
available, if not a message dialog is presented to enter a valid license
key. These licenses can also be entered and viewed using the System
Administration application.
In this way the installed software is generic and the licenses can be
distributed separately.
The software licensing is detailed in [ODWLICENSE].

12.8. Other aspects


12.8.1.

Language support
The language on the client and the server must be the same.
For the operating system for the server applications only Microsoft NT
English is supported.
The following table specifies the languages supported.
Language
UK English
Dutch
German
French
Danish
Italian
Norwegian
Portuguese
Spanish
Swedish

Copyright 2001

Oc-Technologies B.V.

Adobe Acrobat language


English
Dutch
German
French
International English
Italian
International English
Portuguese
Spanish
Swedish
Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released
Finnish
Us English

Page:
93
Date:
August 15, 2001
Version: 1
International English
English

Note that within the ODW software common dialogues of the operating
system are used, which will be in English.
12.8.2.

Help
The ODW applications will have online help functionality meant for the
user of those applications. Win help and context sensitive help will be
used; no support for tool tips.

12.8.3.

Homepage
Every ODW server will be equipped with a set of web pages called
homepage. This homepage will be in the same language as all other
ODW applications. It will not be modifiable by the operator or system
administrator.
This homepage gives access to the web submitter, some general ODW
information and a download page, where the following topics can be
downloaded:
The ODW Client application (setup)
The ODW optimized Distiller options
The ODW PPD file and a description on how to set its default
settings
The Adobe PS driver (setup)
Adobe Acrobat reader

Copyright 2001

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released

Page:
94
Date:
August 15, 2001
Version: 1

12.9. Service Aspects


12.9.1.

Performance

12.9.1.1. Number of concurrent submissions

The server will be able to support 10 concurrent submissions. This holds


for both the client application and the web submitter. (e.g. 5 submissions
using the client application concurrent with 5 submissions using the websubmitter is ok, 10 submissions using the client application concurrent
with 10 submissions using the web-submitter is not supported)
The speed of the submission depends on:
Network speed, load and configuration
Used hardware for the client PC and ODW server
Processor and memory load on both PCs.
Note that distilling is done sequentially. This means that once a job is
distilling, other jobs (including preview requests) will have to wait.
12.9.1.2. Number of concurrent print operations

Only one concurrent print operation is allowed. A second print operation


can be started when the first print job is under complete control of the NT
print spooler.
12.9.1.3. Number of jobs

The number of jobs the system can handle depends on the size of the
jobs and is limited by the overhead of job ticket information and the size
of the data partition of the PC. The response of the system is reasonable
if the total number of jobs in the system dont exceed 500 for regular
office jobs. If more jobs should be handled then the response can be
decreasing.
12.9.1.4. Pro only: Number of concurrent Import/Export operations

Only one job can be imported at a time and only one job can be exported
at a time. Import and export can work in parallel.
12.9.1.5. Hardware

The overall performance depends on the used hardware.


Reasonable performance is only guaranteed when the minimum server
configuration is used and only the specified applications are running. So
no support given if other applications are running.
12.9.2.

Release identification
Each separate ODW application has an about box menu item which
describes the global release identification, current release version of that
application copyright notices and the serial number and license key.

12.9.3.

Diagnostics

12.9.3.1. Standard diagnostics

Standard Microsoft NT diagnostics tools are used:


ODW logs events in the application part of the NT event log. The
Event Viewer is used to display the logged information. Logging
information will be in English only.
NT Diagnostics application is used to get an overall overview of the
server.
NT Regedit application is used to get a detailed overview of the
server.
For ODW no additional diagnostics tools are developed.

Copyright 2001

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released

Page:
95
Date:
August 15, 2001
Version: 1

12.9.3.2. Remote diagnostics

Remote diagnostics is handled outside the scope of the project. Remote


diagnostics is meant for the helpdesk. Probably ControlIT will be used.
ControlIT is handled and installed separately by a service technician
and/or consultant
12.9.4.

Backup/restore
For ODW no backup/restore functionality for the server is taken into
account. Most companies do have already a backup procedure in place.
Within the contract the backup/restore is handled.
As an alternative, the Opco can decide to install locally a customer
preferred backup mechanism (i.e. DAT) on the ODW server.
The location of relevant data (i.e. job store) can be configured by means
of the System Administration application.

12.9.5.

Distribution

12.9.5.1. Client

The ODW client application is distributed using a CD-ROM. This CDROM also contains a distribution package that allows for easy
distributions over a network (single setup file download; this is not equal
to SMS!).
No silent setup foreseen. Also no hardware distribution is foreseen.
12.9.5.2. Server

The ODW server software is distributed using a CD-ROM.


No special distribution from the Web is available. No silent setup
foreseen.
Also no hardware distribution is foreseen.
12.9.6.

Installation

12.9.6.1. Client

For the ODW client software, an InstallShield setup is used. This


installation should be performed on a system that complies with one of
the client target environments specified in paragraph Error! Reference
source not found..
The installation will have no options. An un-install option is available.
12.9.6.2. Server

For the ODW server software, an InstallShield setup procedure for CDROM installation is used. This installation should be performed on a
system that complies with the server target environment specified in
paragraph Error! Reference source not found..
This implies that any old version of Desk or Pro should be removed
before this installation is activated.
The installation will have no options. An un-install option is available.
12.9.7.

Upgrades
There will be no upgrade from existing Desk 1.1 or Pro 1.1 systems to
Desk 1.2 and/or Pro 1.2 systems. To upgrade these systems to Desk/Pro
1.2 a clean system is required, which implies that formatting of the hard
disk is required.
There will be an upgrade tool for the jobs and ticket definition of an
existing Desk 1.1 or Pro 1.1 system. This tool should be used before the
conversion to Desk/Pro 1.2. It will store the information on a user
specified location (probable a network drive). After the installation of the

Copyright 2001

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released

Page:
96
Date:
August 15, 2001
Version: 1

Desk/Pro 1.2 system has been completed, this data can be imported
again.

Copyright 2001

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released

Page:
97
Date:
August 15, 2001
Version: 1

12.10. System Administration application


In the System administration application, the following items can be
configured.
12.10.1.

Oc Doc Works Station

12.10.2.

Licenses

12.10.3.

Import settings, like setting the import interval, see also paragraph
3.3.5.2

Automatic Export (Pro only)

12.10.5.

View all available licenses.


Enter a license for an ODW option (all options, except the client
options)

Automatic Import (Pro only)

12.10.4.

Storage directory. Only directory on the hard disks of the ODW


system are supported. (So the storage directory may not be located
on a network drive)
ODW computer name (hostname or IP-address). This name must be
filled in, since it will be send to all clients. Each client will use this
address for the next submission. (This can e.g. be used to move all
client of an ODW system to a new system, without modifying all
client configurations)
Setting the time frame, after which the jobs from the Ready job
category will be deleted (no, 1 day, 7 days, )
Company logo. It is possible to specify a company logo.
Email settings
Mail server hostname & port number
Mail from address & name
Pro only: Mail CC address(es). Multiple addresses may be entered,
separated by a semicolon.
Pro only: Maximum size for mail attachments.

Export settings, like settings the target path, see paragraph 3.3.6.2

Advanced

Pro only: As an advanced option, the mappings between job ticket


settings and settings in the printer drivers can be created within the
System administration, see also paragraph 3.3.4.5.
Update the query cache. The system uses a cache for fast searching
on job ticket items. This cache is maintained automatically, but may
become outdated when incomplete backups are performed.

12.11. Job Ticket Editor


The Job Ticket Editor enables an Oc consultant to maintain and change
the job ticket definition. This definition describes the capabilities and
services provided by the DPC. If desired, after some training, the
administrator can also use the Job Ticket Editor.
12.11.1.

Copyright 2001

Job ticket definition


A job ticket definition is a combination of a list of job ticket items and
multiple views on these items. Items may be present in multiple views.

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released

Page:
98
Date:
August 15, 2001
Version: 1

For now two views are supported; one used for the submission clients
(Client application, Web submitter and New job in the Operator
Console), the second used in the Operator Console.
12.11.2.

Job ticket items


A job ticket item has an (English) identifier, a data type, a range of
possible values and (translated) captions. Items can be added or
removed.

12.11.3.

Job ticket views


A view specifies the presentation of (a subset of) the list of job ticket
items in a definition. Per view can be specified:
Which items are displayed
How these items are organized into a tree structure (both structure
and order can be specified)
Which items are required, read-only and remembered

12.11.4.

View and print


It is possible to view the resulting job ticket definition and/or to print out
the job ticket definition for a specific view.

12.11.5.

Identification
The system uses a (non-human readable) unique identifier to distinguish
between multiple definitions. For each definition a human readable
description can be entered.

12.11.6.

Open, Save, Import, Export


The Job Ticket Editor will load the current definition on start-up. From
this definition a copy will be made (with a new unique identifier) that can
be modified and can be saved. When a definition is saved, this definition
is set as the current definition that will be used by everyone that submits
a new job.
The Job Ticket Editor can also export a definition into a file to the file
system. This file can be imported on another system and set as the
current definition (or modified as new definition).

12.11.7.

Factory defaults.
During the installation, a default definition will be installed, containing
default list of job ticket items and default views for the Client and the
Operator.
It is the intention that these factory defaults will cover the needs of a
large group of customers. The captions in the factory defaults depend on
the chosen language.

12.11.8.

Software protection
A software license key will protect the Job Ticket Editor.

12.12. TIFF to PDF converter


The ODW system can be extended with a TIFF to PDF converter that
allows for scanned documents from an Oc 3165 (in TIFF format) to be
converted into PDF documents.

Copyright 2001

Oc-Technologies B.V.

Venlo, The Netherlands

PSD
Doc:
Status:

Oc Doc Works R1.2


IR 01.DPS.1022
Released

Page:
99
Date:
August 15, 2001
Version: 1

12.13. Copy protection


12.13.1.

Client side
A software license key protects the job submission client. The preview
option is also protected with a software license key.

12.13.2.

Server side
The server is protected by a software license mechanism. The servers
will be serialised with a unique serial number. This serial number will be
distributed by M&L. Beside this serial number; each application will have
a software license key.
During start-up of the application it is checked if a valid license key is
available, if not a message dialog is presented to enter a valid license
key. These licenses can also be entered and viewed using the System
Administration application.
In this way the installed software is generic and the licenses can be
distributed separately.
The software licensing is detailed in [ODWLICENSE].

12.14. Other aspects


12.14.1.

Language support
The language on the client and the server must be the same.
For the operating system for the server applications only Microsoft NT
English is supported.
The following table specifies the languages supported.
Language
UK English
Dutch
German
French
Danish
Italian
Norwegian
Portuguese
Spanish
Swedish
Finnish
Us English

Adobe Acrobat language


English
Dutch
German
French
International English
Italian
International English
Portuguese
Spanish
Swedish
International English
English

Note that within the ODW software common dialogues of the operating
system are used, which will be in English.

Copyright 2001

12.14.2.

Help
The ODW applications will have online help functionality meant for the
user of those applications. Win help and context sensitive help will be
used; no support for tool tips.

12.14.3.

Homepage
Every ODW server will be equipped with a set of web pages called
homepage. This homepage will be in the same language as all other
ODW applications. It will not be modifiable by the operator or system
administrator.

Oc-Technologies B.V.

Venlo, The Netherlands