Modelling Tramped Pairs

What is a tramped pair?

A tramped pair links a collection stop and its delivery stop so ROCL keeps them together on the same vehicle, in the correct order - collection first, delivery second. There are two ways to build one in the import file.

Method 1: PAIR column (two rows)

Import the collection and delivery as two separate, standard rows, and give both the same value in the PAIR column. Pair numbers don't need to be sequential, can go up to 9999, and just need to be unique to that pair within the profile.

Method 2: single row, ORDERTYPE B with C-suffix headers

Instead of two rows, import the whole tramped pair as one row. Set ORDERTYPE to B ("Both" - the row represents both a collection and a delivery). The standard headers on that row (ADDRESS1, OPEN1, CLOSE1, CALLNAME, etc.) describe the delivery side. To describe the collection side, add a parallel set of headers with a C on the end - for example ADDRESS1C, OPEN1C, CLOSE1C, CALLNAMEC.

Tip: Fields that belong to the order as a whole, not to one side of it - such as ORDERREF and PROD1 - are not duplicated. They use the standard header and appear only once.

Available C-suffix collection fields

These headers can be added to the interface to carry collection-side data when using ORDERTYPE B:

Example single-line tramped record

Choosing between the two methods

Common pitfalls

• Mismatched PAIR values in Method 1: a typo on one row silently breaks the pair - no error, the stops just get planned separately.
• Forgetting the C suffix in Method 2: without it, ROCL has no way to tell delivery-side data from collection-side data.
• Duplicating shared fields: ORDERREF, PROD1, and other whole-order fields should appear once, not twice with a C-suffix version.

Quick reference