8.7

used for each route, and the driver must dock the pen in the proper docking station which
corresponds to his router number, at the end of the day.
As you may have figured out by now, we are still not actually printing more than 20,000
patterns. The only distinction here is that we are re-using patterns in separate "zones" (or, well,
sequences) and as long as pens and pages using capture patterns are not exchanged between
these zones, they act independently with their own 20,000 pattern limitation.
Note
The mobile phone application, "PlanetPress Mobile", which uses Bluetooth communication to
receive pen data and transmit it to PReS Workflow, can still be used with both pattern sequence
methods, as it is the equivalent of a docking station on the web. PlanetPress Mobile was added to
PlanetPress Capture in version 7.4.
Contamination
The single but critical danger with any implementation that deals with PlanetPress Capture is
"Contamination". Basically, contamination happens when an Anoto Digital Pen writes on a
"wrong" document or is docked in the wrong location. This can happen any number of ways
and in different situations, and can have devastating effects in some of those cases so please
pay special attention to this section.
First, contamination is not limited to implementations that extend their patterns through
methods 1) and 2) above. Any time that a pen writes on a "wrong" document, it is considered
contamination. A simple example in a basic implementation would be to print a document with
a pattern on it, put this paper aside (or lose it on a desk somewhere) and forget about it.
Assuming proper processes were put in place, this document would eventually be closed by a
manual or automatic procedure. However, the physical document with the pattern still exists
even if it is closed in regards to the PlanetPress Capture database. Contamination would
happen if a new document is printed with the same pattern, but somehow the "old" document
re-surfaces and someone writes ink on it and docks the pen. When this happens, neither the
pen nor PReS Workflow can understand that the data does not belong on that document and
will happily update the "current" document, possibly closing it. Because the "old" document
relates (presumably) to a different client, this means the "current" document has invalid
information.
Page 154