Prinect System Information

Prinect Prepress / Pressroom / Integration Manager 2011

System Information

© 2011 Heidelberger Druckmaschinen AG Page 1

Prinect System Information

Table of Content
Prinect Manager Installation.................................................................................................................... 3 
Shut down the License Manager before starting the Installation ........................................................ 4 
MS Windows XP Service Pack 3 ......................................................................................................... 4 
MS Windows Vista............................................................................................................................... 4 
Mac Systems ....................................................................................................................................... 4 
Service Control .................................................................................................................................... 4 
Synchronization ................................................................................................................................... 4 
PDF Toolbox ........................................................................................................................................ 5 
Rehosting............................................................................................................................................. 5 
Migration .............................................................................................................................................. 5 
Problems after installation or upgrade................................................................................................. 5 
New setting for JDF import in MIS integration ..................................................................................... 5 
Notes on the Prinect Prepress Manager ................................................................................................. 6 
Fonts .................................................................................................................................................... 6 
PDF Formats ....................................................................................................................................... 6 
Prinect Prepress Manager UNIX-Connection...................................................................................... 7 
Path Names ......................................................................................................................................... 7 
Image Handler ..................................................................................................................................... 7 
Service Control .................................................................................................................................... 7 
Prinect Cockpit .................................................................................................................................... 7 
Engines .............................................................................................................................................. 10 
Pixelproof Viewer ............................................................................................................................... 11 
Notes on Prinect Pressroom Manager .................................................................................................. 12 
Notes on the Prinect Postpress Manager ............................................................................................. 14 
Workflow................................................................................................................................................ 14 
Restrictions for Importing Jobs from Prinergy ................................................................................... 14 
Restrictions for Jobs from Management Information Systems.......................................................... 14 
Restrictions for Prinance Connections .............................................................................................. 14 
Restrictions for the PPF workflow ..................................................................................................... 14 
Restrictions for the new Versioning ................................................................................................... 14 
Accelerating the Workflow ................................................................................................................. 15 
Prinect Signa Station ......................................................................................................................... 15 
Prinect MetaDimension ..................................................................................................................... 15 

© 2011 Heidelberger Druckmaschinen AG Page 2

Prinect System-Information

Prinect Manager Installation

For detailed information on the installation procedure, please see the manual “Prinect Prepress Man-
ager – Installation”. If you need to upgrade an existing installation, please take a look at the “Prinect
2011 upgrade guide” (coming soon).
Before the installation procedure starts, the system is checked with respect to the requirements of a
standard Prepress Manager-system. This functionality depends on the operating systems and may
not always be correct. Please keep in mind that for notebooks the processor’s clock speed depends
on the energy management and may be lower than the system run on batteries. The check itself is
based on the standard Prepress Manager configuration and may lead to false warnings for systems
with fewer requirements.
If there is not enough free space on the hard disk, the installer will issue an error message, which may
contain a negative value for the required disk space. In this case, you must free the partition. The in-
staller scans continuously for available space and will continue its work if it has become available.
This may take some minutes after the cleanup took place.
The computer name of the server and of the Cockpit workstations should not have any special cha-
racters, blanks, or umlauts. Computer names with such characters are not suited for use in a network
environment. Follow our recommendation to be on the safe side: Even if you are able to enter any
kind of name in the text box for the computer name, you should keep to the DNS naming conventions
when you assign a name to your computer. This means that you may only use characters A thru Z, a
thru z or 0 thru 9 as well as the minus sign. In addition, the name must be maximum 12 characters
long.
The MetaDimension installer requires up to 3 GByte of disk space during installation or upgrade. It
does not check whether this space is available. This can lead to problems due to missing disk space,
especially if Prepress Manager and MetaDimension are installed on a common system. Therefore,
you should check before installation that enough disk space is available! Otherwise, it is recommend-
ed to save the MetaDimension configuration files, un-install the existing MetaDimension, reboot the
server, and install MetaDimension 11.0.
The installer may not always succeed in exiting all processes, and the installer cannot replace files
locked by these processes. For this reason, we strongly recommend that you reboot the server before
an installation takes place.
After each upgrade, existing jobs need an adaption to the present version. These jobs are flagged
with the adaption con. Please ensure that the adaption takes place before the next upgrade. If an
adaption is missed between two upgrades, the job will be unusable in all later versions! This holds
true for archived jobs, too.

© 2011 Heidelberger Druckmaschinen AG Page 3

Prinect System-Information

Shut down the License Manager before starting the Installation

Errors may occur during installation, for example, if the Heidelberg License Manager is open for enter-
ing new license keys or checking the license status and if the installation is started with the License
Manager open. Therefore, on principle exit the License Manager before an installation or upgrade
installation.

MS Windows XP Service Pack 3

Windows XP is released only for use of the Prinect Cockpits. Therefore, these notes refer only to the
Cockpit:
1. The Prinect 10.0 Cockpit is installed on a computer with Windows XP Service Pack 3. In this con-
stellation, the Prinect Prepress Manager installer performs all required settings and nothing else
has to be taken into account.
2. The Service Pack 3 is installed subsequently on a computer where Prinect Cockpit is already in-
stalled. After a reboot and start of the Cockpit, a query may appear asking you whether the
"PTClient" program should continue to be blocked for the Windows firewall. Choose "Unblock” to
allow the Cockpit to continue working correctly.

MS Windows Vista
Windows Vista is no longer supported. We recommend to either downgrade to Windows XP or up-
grade to Windows 7.

Mac Systems
The Cockpit requires Mac Systems with 64 Bit Intel CPUs (Intel Core 2 or Intel Core-i) and OS X
v10.5.8 or v10.6.7 or later Systems with 32 Bit Intel CPUs (Intel Core, as used in the first Mac minis
and white iMacs) can be used, if the operating system is OS 10.6.7. The PowerPC architecture is no
longer supported.
Usage of Windows via Boot Camp or virtual machines like Parallels or VMware on a Mac will cause
network problems with the Prinect Cockpit and is therefore not supported!
With OS X v10.5 Apples has implemented a new SMB stack, which is restricted with respect to cha-
racters. Therefore the Mac Cockpit will not start if the user name contains blanks or special charac-
ters.
A bug in Mac OS X v10.6 may lead to data loss, because files moved on SMB-based network shares
might lose their resource forks.

Service Control
The Prinect Service Control is for administrative use only. Therefore, it cannot be started without ad-
ministrator permissions.
Beside “Start“and “Stop“the Service Control Module is able to "Restart“. To do this, press the <Ctrl>
key while clicking the "Stop“ button. This is the same functionality as with the MetaDimension Service
Control Tool.
Ensure before installation or upgrade, that the Service control module is not running anymore.

Synchronization
A time synchronization of all computers existing in the Prinect Prepress Manager environment (for
example server and Mac Cockpit) is required because internal processing steps are running time-
controlled and the coordination can only work correctly if the system time is the same on all comput-
ers. Prinect Manager 2011 contains the Tardis time server, which manages time synchronization if the
system is not a member of a network domain (in this case the domain server is automatically the time
server for all Windows computers within its domain). Tha Tardis software can be installed on any
compute rin the network. Please do not use the Prinect server as network time server, because the
Prinect server’s system time might be unstable on certain hardware platforms. Please do not forget to
configute Tardis after installation.

© 2011 Heidelberger Druckmaschinen AG Page 4

Prinect System-Information

On Mac systems a time server must always be specified during installation of the Cockpit software.
You can choose between the following alternatives:
• The time server for the Mac should not be changed.
• The Prinect Prepress Manager server should become the time server for the Mac.
• An arbitrary time server will be specified for the Mac.

PDF Toolbox
The PDF Toolbox is installed together with the Cockpit. For that reason, a PDF Toolbox installation is
not necessary. The PDF Toolbox setup programs are located on the Prinect server after installation.
This makes it possible to install the PDF Toolbox on computers without a Cockpit. Licensing of the
PDF Assistant, like the licensing of all other modules of the PDF Toolbox, is managed by the central
License Server. As a result, no PDF Toolbox dongle is required.

Rehosting
Before rehosting, please read the latest Service Information for details on this topic.

Migration
Migration is recommended only from a Printready 3.0 version or higher. A full installation should be
run with older Printready versions. Please also note the information about the Pressroom Manager
and the additional service documentation.

Problems after installation or upgrade

If a new installation causes problems after an uninstall took place, this may be due to leftovers from
older installations. If you cannot solve this problem, please contact your support. If the Cockpit does
not start after an upgrade the hardware requirements might not be met. Some-times a reboot might
help.
In case the Analyze Point should not work after installation, you should restart the system with the
Service Control module. You can check this in the log files of the Analyze Point (error message:
JDFStoreHelperException: JDFFS_11: The storage service was unreachable).

New setting for JDF import in MIS integration

After installation, please configure the new setting for JDF Import either as “Job description only” or
“All Data”. The parameter must definitely be set to “All Data”.

If a customer already has an Management Information System, the “Job description only” setting is
sufficient. 

© 2011 Heidelberger Druckmaschinen AG Page 5

Prinect System-Information

Notes on the Prinect Prepress Manager

Special Characters
Special characters, which are likely to cause trouble, will be detected when input and a warning will
be issued. These warnings should be taken seriously, because these characters may cause problems
later in the workflow. Although it is possible to work, they may lead to inconsistent states, which can
only be resolved by deleting the jobs in the file system. Generally, problems are caused by those cha-
racters that are not allowed in the Windows file system ("\*/:<>?|), UNIX control characters (';^`{}~)
and the “Escape” character %.
Spot Colors
The following characters will be rejected during the definition of spot colors: / \ < > ^ { } `
OPI
The OPI engine which is implemented in Prinect Prepress Manager (and in Prinect MetaDimension)
can only embed those high-resolution images of a HELIOS server, which are referenced via regular,
alphanumerical characters of the common character set, as defined above. Characters as German
Umlauts, blanks, punctuation marks or other special characters are not allowed. The same is valid for
a Xinet OPI server.
Because Prinect MetaDimension runs on a Windows platform, in theory it is possible to use a greater
character set if Prinect MetaDimension is used as OPI server. For pragmatic reasons this has not
been realized. At least the following characters will not display correctly: „ * / < > ?.

Fonts
"Bad" fonts may cause that the text displayed depends on the resolution. In Acrobat, you can view this
by zooming into the text. As a result, there are differences between your low-resolution proof and your
high-resolution final output. You should notes such fonts or their manufacturers in a PitStop profile to
be able to recognize them in time in later jobs. Automatic detection by the Prinect Prepress Manager
cannot be implemented as the problem lies with the internal font description. Such problems can be
recognized early if the ROOM proof functionality is used (option for ROOM proof required).
The TrueType format allows the manufacturer to prevent fonts from being embedded in the PDF. This
protection mechanism is respected by the Prinect Prepress Manager System; such fonts are not em-
bedded into the PDF.
If font search folders with a huge number of fonts (more than 50,000) are set in the Preflighter or
Normalizer, this may cause the Preflighter or the Normalizer to "hang" (in particular if the search paths
are located on other computers in the network). In this case, the Preflighter or the Normalizer process
must be ended via the Windows Task Manager. The process is automatically restarted and must be
ended a second time via the Windows Task Manager. After a third, restart of the process the job is
aborted.
Font problems during the flattening of transparencies are reduced considerably. However, there are
still some issues that are not yet solved. In these cases, transparencies should be passed unchanged
to MetaDimension. It does not matter where the flattening takes place.
A Kanji font installer is also shipped as of Prinect Printready 3.0 SP2. This installer is intended for the
five Japanese base fonts, which are available as options for Prepress Manager. It can run on the
server only and replaces the “width-only” Adobe fonts in the Normalizer’s Kanji environment. An un-
install will restore the original Adobe fonts.

PDF Formats
Prepress Manager accepts all PDF formats. The PDF information will pass the system unchanged.
Exceptions are:
• -PDF files of version 1.2 or earlier, in this case PDF 1.3 is named.
• Use of PitStop profiles and Action Lists by the Preflighter.
• Transparency reduction or embedding of CJK fonts.

If possible, a PDF/X tag is issued:

© 2011 Heidelberger Druckmaschinen AG Page 6

Prinect System-Information

• PDF/X-1a:2003 if the PDF has the format version 1.4 and no transparent objects. Further-
more, there are no device independent colors. This is the normal case if Color Carver is
enabled.
• PDF/X-3:2003 if the PDF has the format version 1.4 and no transparent objects bus device
independent colors.
• PDF/X-4 id the PDF has a format version from 1.4 to 1.6

An existing PDF/X tag will not be changed. If PDF/X-3 has been imported, the tag will not be changed
to PDF/X-1a. Wrong tags will be deleted.

Prinect Prepress Manager UNIX-Connection

The supported UNIX connection of a Prinect Manager 2011 server is implemented via Samba 3.0.0
(or later). This means that for all new released Prinect Manager network services like for example
"Content Manager Archiving" and "Remote UNIX JobLocation" only Samba 3.0.0 (or later) is sup-
ported. This means also that PCShare3.x and NFS are not supported!
PCShare3.x solutions which were already used with the Prepress Manager 1.0, like for example for
the ImageHandler of the 1.0 (PDF OPI functionality with a Helios OPI), can be used further with the
Prinect Prepress Manager 2011. But you cannot use a Unix/Helios server for the Prinect Prepress
Manager 2011 "Remote Job Store" and for content data such as PostScript/PDF simultaneously.
These data are subject to archiving and can only be managed reliably with Samba 3.0.0 or later.
The Prinect Integration Layer (PIL) JDF storage service, which is used by the Prepress Manager,
must always be installed locally on the Prinect Prepress Manager server.
Samba and PCShare3.x both implement the SMB/CIFS protocol stack for UNIX platforms and there-
fore exclude each other on one UNIX computer!

Path Names
File names must obey the Windows conventions – even on UNIX and Mac systems. File names
whose length exceeds MAX_PATH (255 characters) or which end in blanks or a line feed, cause
problems if the corresponding files are sent via SMB to the Prinect Prepress Manager server. Addi-
tionally, names should not only be distinguished by uppercase and lowercase because this distinction
feature may be lost during transmission.

Image Handler
The following applications are recommended for creating OPI layout files for the Prinect Prepress
Manager 2011: Prinect MetaDimension, Delta Technology, and HELIOS OPI. The Xinet FullPress
program is not recommended.
Data format restrictions:
• CorelDraw EPS is not released
• DCS2 single file format with JPEG in a separated workflow is not released.

Service Control
The window of Prinect Services Control has a menu function that lists all the tools with their respective
status (running, stopped, not licensed).

Prinect Cockpit
Starting the Prinect Cockpit
When the Cockpit starts, a delay may occur without an "hour glass" displaying.
If a Cockpit does not start correctly or if it "hangs" during startup, the computer should be rebooted.
The background is that a previously opened Cockpit has not finished completely. This can be recog-
nized in the Task Manager, which displays more than one version of the "PTClient.exe" entry.
Performance
For maximum performance, the following items should be noted.

© 2011 Heidelberger Druckmaschinen AG Page 7

Prinect System-Information

Each running job with a hot folder consumes system resources. An upper limit is difficult to define. It is
highly recommended to stop jobs after successful processing and never have more than 1000 running
jobs in the system. The same applies to jobs that are waiting for approval.
Documents may be processed in groups if they are added via a hot folder. The default setting is one
document, this means that every document is recognized in the progress bar. If there are hundreds of
documents, increasing this number is recommended. For example, if there are a hundred documents,
a grouping by two will still leave enough resolution for the progress bar, but increase the processing
speed by a factor of two. The speed up is even more significant for more than thousand documents
and a grouping by ten.
In general, there is no upper limit for the processing of huge jobs. The following parameters are
impotant:
• Number of documents (these can contain one, several or even all pages)
• Number of pages
• Number of layouts
• Number of corrected pages
• Number of correction cycles
• Number of outputs (page proofs, imposition proofs, Hires output)
• File size of the job’s JDF (for Cockpit performance)
In the worst case (single page documents, nearly all pages are corrected in multiple cycles, in all cor-
rection cycles proofs are generated) some hundred pages may be sufficient to make the job’s JDF too
large for efficient operation. In the best case (a few documents containing the whole job, only a few
correction pages, only one output) thousands of pages may be processed without problems.
Menu Operation via Keyboard Shortcuts
On Mac systems, keys F9 thru F12 are predefined, and cannot be used by applications. If F9 will be
used for the display of assignments, the administrator must use the Mac tool Expose to change this
preset.
Deleting Jobs
The deletion of jobs via multiple selections is done via the Cockpit server. It is now possible to close
the Cockpit even the jobs are not fully deleted. Jobs are deleted completely only if they do not display
any longer in the job finder. Please make sure after deletion that the jobs are no longer displayed.
Depending on the number of jobs to be deleted, it may take some time until deletion starts. If very
many jobs are deleted, first, the deletion process is very slow, but it becomes increasingly faster. You
can continue to operate the Cockpit during deletion. If a job has not been deleted, this may be caused
by the operating system, because another application is accessing the job; normally this is the Win-
dows Explorer. Please make sure that no other application is trying to access the files and folder be-
longing to the job.
Import/Export
The import and export functionality is meant for job exchange between Prinect Prepress Manager
Systems of the same version. It is no replacement for an Archiver. Especially, it cannot be ensured
that jobs, which were exported by an older version, can be imported by an actual version. With regard
to Prinect Prepress Manager 11.0 the following must be considered:
• Jobs exported from Prinect Printready 2.x and 3.x can be imported.
• Jobs exported from Printready 1.x are imported with the following restrictions:
- During import, a warning is issued.
- The layout is checked and, if necessary, imported with restrictions. Old PPF data are not im-
ported.
- If possible, sequences are imported. They keep their rose color and can be opened as read
only. Their settings can be used manually.
- The links between sequences are preserved.
- The page lists are preserved and can be used further.
- Product parts are preserved; versioning can be used further with new sequences.
- Color mappings are preserved.
Additional information is ignored.

© 2011 Heidelberger Druckmaschinen AG Page 8

Prinect System-Information

Jobs imported from older Printready versions cannot be used as templates for automatic job genera-
tion.
Job import from Prinergy systems was tested for versions 2.1.0.0 thru 2.1.0.23 only. Older versions
down to Prinergy 2.0 may work, but we cannot say anything about their completeness and correct-
ness. Jobs from versions older than Prinergy 2.0 cannot be imported.
Color Tables
If color tables are modified by other applications than the Prinect Cockpit (Prinect MetaDimension,
ImportMDS, MDS WebUI), the tables are not automatically updated in the Cockpit. This means that
these modifications are only applied if the server is rebooted, if the printing order is changed, and/or if
color tables are enabled/disabled in the Prinect Cockpit.
The Lab values of a color table do not affect the color display or the CMYK values of the color table.
This is intended; because the Lab values describe what the color looks like there as the CMYK values
give the recipe of the color.
In the case of multiple definitions of a spot color within a page, the system will automatically map all
definitions to one of the separations with the same name. You should check whether this might be in-
tended by the page’s designer. This is especially important for HKS colors; there the default definition
is “N”, which differs significantly from “K”.
Imposition
The functionality of page handling has been improved. Page selection followed by drag and drop will
lead to a repositioning while a selecting of a page while the <ctrl>-key is pressed will move a copy of
the page to a new position. This is due to the functionality of file handling in operating systems and
many applications.
ImposedPDF and BookletProof
Double pages are not always created properly when double pages are output with ImposedPDF or
ImposedProof. You can unexpectedly have single pages in saddle stitching. In perfect binding with
pagination in ascending order, in some cases the order of the double pages is not correct. Complex
layouts that can have fold-out pages, for example, also cannot be considered at the moment.
Prinect User Account on Mac Systems
A user-specific file with preferences like window positions etc. is written for every Prinect Cockpit user.
If Cockpits with the same user account are opened on several computers, this one file is also edited
by several computers. In rare cases, this may lead to inconsistent states of this file if a Mac Cockpit
tries to edit it. For that reason, especially on Mac systems, different user accounts should always log
on to different Cockpits..
Network Connections to Mac Systems
When a Cockpit starts, a network connection test is run. If an error results, please consult your net-
work administrator. Normally this problem is found in the Domain Naming Service (DNS). If no error
message is displayed after the test, this does not mean that the network connection is faultless!
An energy-saving mode is enabled by default on the Mac. For that reason, the Mac switches to
standby after 10 minutes if there is no operation during that time. Furthermore, the Mac in standby is
soon disconnected from the PIL services and this in turn disconnects it from up-dates. The Cockpit
then no longer shows any job progress. To prevent this, please disable the stand-by mode. Or choose
a much greater time interval for standby or exit the Cockpits in the evenings.
If Mac files are filed within the job folder structure, remember that, when created, the resource forks
depend on the protocols and that only the SMB protocol provides the necessary reliability. Further-
more, AFP will no longer be supported as of Windows 2008. The simultaneous mounting of shares in
AFP and SMB can cause your data to be destroyed and should be avoided in all cases.
Problems with illegal share names for Mac OS X accesses
Share names which exceed 12 characters or which contain blanks cause problems with Mac OS X
accesses.

© 2011 Heidelberger Druckmaschinen AG Page 9

Prinect System-Information

Engines
Load Balancing
The load balancing functions depend on the number of tasks in the queues of the engines involved.
This means that the sub-JDF is sent to the engine with the "shortest" queue. If tasks with very differ-
ent processing time are available in individual queues, this may lead to a situation where one engine
has nothing to do while several tasks are to be processed with another engine.
Normalizer
The Normalizer will use the flat compression instead of JPEG2000 if this will lead to smaller files. This
behavior is similar to that of Adobe Distiller and is without any shortcomings.
Recombiner
If the Recombiner was used, the colors in the icons are not always displayed correctly. The problem is
found in the Adobe PDF library that creates icons without considering the overprinting properties of
individual objects.
It may occur that individual separations contain colored objects. This leads to termination of
processing.
Spot colors with transfer curves will not display correctly in Acrobat. Nevertheless, the created PDF
files contain correct data as can be determined by a proof.
Preflighter
Transfer curves are not included if separated data and spot colors are processed. As a result, objects
in spot color channels, which were masked out via transfer curves, are visible again.
The Preflighter can process a maximum of 100 spot colors. More than 100 spot colors will lead to an
error message.
The handling of overprinting white in the generation of thumbnails and Signa Station previews was
already enhanced in Printready 3.0 to show all outlines. As a side effect, colors may appear less satu-
rated in the page thumbnails and previews.
ImposePDF
The PDF Imposer is used for output of PDF sheets on other RIPs than Prinect MetaDimension as well
for the generation of PDF sheets for sending them as soft proofs to customers. The generation of
high-resolution sheets is subject to license. Without this license, the PDF Imposer only generates low-
resolution PDF documents for approval use.
AutoSheet
Since version 4.0, AutoSheet can automatically add pages to layouts via the Signa server. The
layouts must be marked appropriately for this in the Signa Station and must not be too old. Layouts
that are too told (8/2005) are aborted only after a timeout of three minutes. Please save these layouts
again in the Signa Station and repeat the action.
Backup
Note that including large amounts of job data from external servers into Prinect backups will cause
long backup times. Therefore, it is not possible to use the backup for Remote Access. Saving the Re-
mote Access server has to be done by means of an external backup solution.
There is now the option of creating a backup of job folders on external servers. Please note that this
can lead to larger data volumes and result in longer backup times.
Archiver
The “removal” of archived jobs does not work in all cases. This can be caused by files whose names
do not comply with the Windows naming conventions or have a date beyond the year 2037. In gener-
al, these files stem from UNIX or Mac systems and may not be visible within the Windows Explorer.
Another reason may be that another application has opened the file. These applications may be
background processes like the MS Indexing Service.

© 2011 Heidelberger Druckmaschinen AG Page 10

Prinect System-Information

SendAssembledPDF
The files created with this sequence have a medium JPEG quality. This may cause that the input data
are smaller than the result produced by the Prinect Prepress Manager.
Remote Approval
A "POP3 before SMTP" authentication for mail servers is not implemented.
Remedy: Use a "POP before SMTP" proxy software (for example, available at
http://people.freenet.de/ingos_pages/german.htm).
Job names may not be changed within a remote approval workflow. If a remote approval, e-mail is
sent and if the job name is changed subsequently, the reply mail attachment (XFDF file) can no long-
er be assigned to the job.
Remote Approval has only been tested with Acrobat and Outlook. On Windows 2008 systems we
have experienced problems with Email clients as Windows Live Mail and Thunderbird.
Note: The comment text in the Remote Approval comment PDF form may not be too long. In Prinect
Prepress Manager 2011, the comment text displays in the "Customer Approval Comment" column in
the "Job > Elements" tab.
With versioned layouts, the approval following SendAssembledPDF may be incomplete. Only the
pages of the versioned layers will be approved, the base layer gets no approval. Remedy: Manual
approval of base layer.

Pixelproof Viewer
The Pixelproof Viewer is used for checking the order of pages and the screening. The display is not
true-color. For that reason, only a default profile is used for the conversion from CMYK to the monitor
color space.
The process colors are not listed with an 8-bit proof (but are shown in the proof). In addition, the color
recipes of all three spot colors are missing and replaced by black.

© 2011 Heidelberger Druckmaschinen AG Page 11

Prinect System Information

Notes on Prinect Pressroom Manager

Configuration
The Mac Cockpit offers no access to the PPF Import configuration. This is only possible with the PC
Cockpit.
Restrictions for Japan
Prinect Pressroom Manager 2011 supports no Japanese localization. The Japanese version will be
available later via service pack.
Restriction for the Scheduler functionality
Rescheduling of interrupted worksteps not available in the overall system
One sheet on several presses (for rescheduling between presses)
• Presses may be only in just one cluster.
• Printing sequences may only be set up with clusters.
• Presses can be rescheduled only within the ONE MDS cluster.
If a workstep gets started on another machine as originally intended, the workstep will still appear on
the first machine but will not be started.
The existing workstep quality protocol is limited to 55 releases. This limitation is necessary to prevent
display problems. Printing the workstep protocol will show all releases.
Restrictions with Related Jobs
The printing machine defaults, which have been stored with preceeding jobs, are only available at the
machine if plates have been exposed in the workflow. The option “Plates from Store” is not supported.
With Prinect 2011 the takeover of settings from a base job has to be done manually. Automatic take
over with transfer of the related job to Prinect is actually not available.
Hints for use of DataTerminal
For Data Terminal with PPF generation the following has to be taken into account:
• Data Terminal must be used in Start-Stop-Mode.
• No defaults for unplanned tasks.
• Stored defaults for related jobs have to be administrated locally at the printing machine.
Hints for use of PPF Generation
With direct PPF connection, the following has to be taken into account:
• Data Terminal must be used in Start-Stop-Mode.
• No work in cluster with online printing machines possible. This means that all jobs send to a PPF
engine will be finished directly by the system and are no longer accessible by the online printing
machine. We therefore recommend the connection via Data Terminal with PF generation.
• No re-calculation of data from the prepress system in case of late changes, because the process
is stopped with generation of PPF.
• Stored defaults for related jobs have to be administrated locally at the printing machine.
• No feedback to Analyze Point from the printing processes of these machines.
• No feedback to Management Information Systems from the printing processes of these ma-
chines.
• Future system enhancements will not take these machines and processes into account (this
means that no planning will be possible).
Hints for Embedding of 3rd Party Printing Machines
For Data Terminal with Komori connection PIT has to be switched on and the special procedure has
to be followed.

© 2011 Heidelberger Druckmaschinen AG Page 12

Prinect System-Information

Hints for Analyze Point

Available reports from Analyze Point have been extended for Prinect 2011 An Additional report al-
lows to display the mean set-up time as well as the mean production speed due to various parame-
ters. With appropriate configuration it is possible to show measured variables according to operators.
We like to point out, that your company’s employment and privacy protection laws should be res-
pected.
In case you do not want to use these possibilties of Nalayze Point for representation, please call the
Heidelberg Service. We will give hints, how to configure your system with de-activated reports.

© 2011 Heidelberger Druckmaschinen AG Page 13

Prinect System-Information

Notes on the Prinect Postpress Manager

The Installer for the Stahlfolder Connector is not integrated into the Prinect Installer. After installation
of the Postpress Manager, you must install the Installer separately from the Prinect DVD so that an
online connection to the folders is possible.

Workflow
Restrictions for Importing Jobs from Prinergy
Import of Prinergy jobs: PPF admin data, cut data, and fold data from the Signa Station are ignored
during the conversion of job tickets into the JDF format during import. When jobs that were exported
from Prinergy are imported to the Prinect Prepress Manager, CIP3 data, cut data, and fold data, which
were created by SignaStation 7, or 8 are ignored, i.e. not imported. Therefore, cut and fold are not
possible because of the missing information about paper size.
Imported Prinergy jobs with two or more layouts may cause erroneous assignments for spot colors or
marks colors. For spot colors or marks colors which are defined as "Do not output" in Prinergy, they
may be displayed and processed as "Convert to Process Colors" in the Prinect Prepress Manager.
This occurs only if the Prinergy job contains two or more layouts.
Remedy: Check and correct the color settings for this kind of job in the Prinect Prepress Manager.

Restrictions for Jobs from Management Information Systems

If a MIS sends a job, the Customer ID will be used to identify the customer. If this customer ID is iden-
tical to a customer, ID within the Prinect Master Data this job will be assigned automatically to the cus-
tomer associated with this ID. If the customer ID is ambiguous, e.g., multiple MIS from different loca-
tions sending jobs; the IDs have to be made non-ambiguous by dedicated means, e.g. a local prefix.
Repeat jobs are sent from the MIS to Prinect and elements from the source job can be added to them
there via the Cockpit. The layout from the source job is one of the items that can be used. However,
this is done only if the "pseudo layout" from the MIS job has the same structure (number of sheets,
sheet name, etc.) as the layout that will be used. If the structure are the same the layout gets re-
placed. Otherwise the layout of the source job will be imported. This import may be suppressed by the
operator from within the Cockpit.

Restrictions for Prinance Connections

A JDF Connector runs on the Prinance computer to create the connection to the Prinect System. Only
once instance of this JDF Connector may run on the Prinance computer. Each Remote Desktop con-
nection for this computer, however, causes a multiple start of the JDF Connector and results in a faul-
ty connection to Prinect. For that reason, disable Remote Desktop for this computer.
You must note the following restrictions if a Gang Run Form Manager is used in Prinance 4.70:
• All of a customer job is always shown in Prinect; this means including all job elements that
may be printed as part of a gang job.
• When a gang job is used, the elements of the gang job have no reference to their customer
job.

Restrictions for the PPF workflow

If an ImposePDF is submitted via PageOutput to a Meta Tiff-B device with PPF, no PPF information is
sent on principle because no layout is involved. The name and ID of the Printready job are also not
copied to the PPF data.

Restrictions for the new Versioning

The new versioning needs layouts that are written by Signa Station 4.0.8115 or later.
Output of several plates by changing the "Print Amount" during an output is possible only for second-
ary sheet variants but not for the main sheet variants. For example, with Print Amount 3, three plate

© 2011 Heidelberger Druckmaschinen AG Page 14

Prinect System-Information

sets (of the versioned plates) are imaged correctly for the secondary sheet variants, but by mistake
only one plate set is imaged for the main sheet variants.
If print amount and planed waste have been entered for a sheet in a versioned job and the operator
switches to another sheet and back again, the print amount will show zero. Ih this procedure is re-
peated the print amount will stay. The same will happen for the Press and Postpress views.
When using data from a related job, the print amount may be wrong.
Even if all plates of a job have been exposed it may happen that the „Plate ready“ state is not set
within the system and therefore not communicated to the management information system.

Accelerating the Workflow

It is not possible to specify a general upper limit for the amount of pages per job. Obviously, an upper
limit of pages does exist - but there are many different conditions that will influence this limitation.
There are technical influences like e.g. the amount of input files, the amount of messages that will be
written into the JDF, or the amount of language layers. If a technical or human condition will be an
issue in large jobs, it can be a good idea to split the job into a number of smaller jobs. Some general
things that can help in the case of huge jobs:
• avoid switching the "splitter" to “on” in the Qualify sequence
• minimize the number of PDF input files per job
• minimize the number of layers per job
• minimize the number of sequences within a job (e.g. add only the sequences that you need to
the job)
• minimize the amount of messages that will be written to the JDF (e.g. switch off all unneces-
sary options in the Normalizing or Prepare sequences)
• minimize the number of correction cycles per job

Prinect Signa Station

Import Layout
JDF layouts which were created by the SignaStation 7/8/9 and the interactively operated SignaStation
_7/8/9 are not released for versions as of the Prepress Manager 4.0.
JDF layouts which were created by the SignaStation 7/8/9
• in the “JDF Output” mode (Printready 1.2) are no longer imported.
• in the "JDF Output" mode (Printready 2.0 or later) can be imported after an appropriate warning
was confirmed. Remember that this functionality has not been tested and therefore its reliable op-
eration is not guaranteed.
The import of JDF layouts that were created with Prinect Signa Station versions older than 1.5 is only
released if the layout was written in the "Printready 2.0 (per JDF)" mode.
The import of JDF layouts that were created with Prinect Signa Station versions 1.5 and 2.0, is re-
leased. Both versions create JDF layouts at least in the "Printready 2.0 (per JDF)" mode.

Prinect MetaDimension
Termination with different spot color names
In a softproof display, processing aborts if same spot colors are defined several times in different no-
tations (uppercase/lowercase) in one job. You can avoid this problem by defining one spelling version
only of the color in the job settings (Target). Remember that the notation for PANTONE colors should
be uppercase only! Example: "PANTONE 102 U" instead of "Pantone 102 u" or "pantone 102 U".
Softproof
If in a "Prinect Prepress Manager 4.5 > Prinect MetaDimension 7.5 > Prinect MetaShooter 4.5" output
configuration the Tiff-B files created by Prinect MetaDimension are saved directly in the hot folder of
the Prinect MetaShooter workstation, the halftone softproof Tiff-B files are saved there as well besides
the high-resolution Tiff-B files. This causes an error message because the resolution (600 dpi) nor-
mally is too low for an imagesetter. In such a workflow, the halftone softproof should be disabled.

© 2011 Heidelberger Druckmaschinen AG Page 15

Prinect System-Information

R.O.O.M Proof
In the R.O.O.M Proof workflow, only one Tiff-B output directory is allowed for each job.
Dyeline separations are not suppressed in the high-resolution output in the R.O.O.M Proof.
The Secure Reprint Assistant doesn’t work for the high-resolution Tiff-B output.
Older Process Control Strips from the CTP Tools CD Cause Abort
Processing can abort with errors in Prinect MetaDimension if process control strips that were created
by an older CTP Tools version are output via Prinect MetaDimension. The process control strips as of
version 2.1 (Mac/PC) work correctly.
Page Proof
In page proofs of documents with different sized pages, MetaDimension always selects the media box
of the first page in the document as the page size. Remedy: Split double pages into single pages in
Printready. This also simplifies the Printready workflow. If you don't, you must send single pages for
proofing to MetaDimension.
Pathnames
JDF documents are converted to the PJTF format for further processing with Prinect MetaDimension.
Some text will be stored as "string". This format allows Unicode, which is introduced by a "0xfeff" bit
combination. Therefore, no such text is allowed to start with "ÿþ" which will be the case rarely. Other
text will be stored as "name", and this format is limited to one byte per character (ISO-8859-1 with
extensions for Windows). This type is e.g. used for color names.

© 2011 Heidelberger Druckmaschinen AG Page 16