Nest Grouping

The nesting system supports 2 types of grouping methods:

Physical Grouping

Jobs are being send to a nest group of a certain material but are not allowed to be printed together. This happens when for example is printed on vinyl on the same printer with the same conditions, however during the finishing one job needs to be laminated and the other not. In this case there would be a grouping parameter related to lamination.

The nesting system accepts any string as grouping ID and will do a case-sensitive match to see if items belong to the same group. This will allow simple labels like:

Laminate

or stringified JSON objects like:

{ "Laminate":true }

The Nesting system will dynamically create buckets for each grouping ID by copying the manually created buckets within that nest group and assign the newly received grouping ID to them. Jobs without a grouping ID will go in the manually created buckets. The jobs with a grouping ID will be placed in the dynamically created buckets for that grouping ID.

Logistic Grouping

Jobs are identical in processing but kept together based on their destination. For example when there a multiple shops of a chain are to be provided with new signage we need to prevents that all the parts from all the jobs are scattered over the nest which makes collating/picking very hard. In this case the nesting first nests everything of destination 1, then of destination 2 and so on. Stacking the individual nests so for the operators it is very easy to collect all items of a destination.

The method of grouping is using a string a grouping ID in the same fashion as the Physical Grouping is doing. For example:

{ City: Nottingham }

The stacking of the logistic groups is determined by their alphabetical order. For example a group ID “Amsterdam” will be placed earlier in the nest than “London”.

Another way of using it is by filling the logistic grouping ID with the order number, this will keep all parts of the same order together.

In all these cases it is recommended to send a multi-part/multi-document job to the nester to avoid that halfway submitting individual parts a nest is triggered and the group is broken up.

XML format

The grouping IDs are to be added to the Part section of the Imposition information. The labels to be used are “PhysicalGroupID” and “LogisticGroupID” respectively. So the above example (in case both are used) could look like:

<Job>
    ... other job content ...
    <Imposition>
        <Parts>
            <Part>
                ... other part content ...
                <PhysicalGroupID>Laminate</PhysicalGroupID>
                <LogisticGroupID>Nottingham</LogisticGroupID>
            </Part>
        </Parts>
    </Imposition>
</Job>
Updated on August 18, 2019

Was this article helpful?

Related Articles