arclogistics routing error

[BradClay]

Can someone explain these errors, how to resolve please?

violated pair
unreachable

Thanks

[BertYagrich]

These messages mean that for some reason, some orders couldn't be reached.

For unreachable, this could occur because of the curb approach property or some restriction such as height, weight, or other violations.

For the violated pair, this typically means that due to routing constraints, you can pick up but not deliver a person or vice versa.  You either don't have enough time or capacity usually.

For unreachable orders, you could provide us with the address and identify the dataset you're using and we could have a look and see if anything obvious is preventing it from being reachable.

[BradClay]

If geocodes were placed in the property, off street or rooftop is this "unreachable"? Thanks

[BertYagrich]

It depends how far off a street they were place.  Rooftop geocodes should never be an issue.  If you've imported X/Y's or dropped a pin to locate something, it is possible. This occurs sometimes when trying to route to places that are typically off network like utility servicing.  (wells, towers, etc.)

[BradClay]

Can the user or administrator adjust pick up area tolerances around the street route path?

When I manually recode the geos some of these seem to route fine.

[BertYagrich]

You can try to manually relocate the orders and typically this is the best strategy.  Snapping tolerance is usually handled when the dataset is built and there are no settings to control this within ArcLogistics.  Otherwise, you can end up with orders snapping to incorrect streets or on the other side of a river, etc.

[BradClay]

Okay Bert,

and on a tangent,

When does the solve cap out? How many orders can it solve at one time? Thanks

[BertYagrich]

With ArcLogistics Desktop 9.3/10, there is no hard limit but over 2,500 orders will probably be pushing it on a 32 bit machine.  A 64 bit machine with 4+GB of RAM has done OK with 4,000-6,000 orders in testing but performance is pretty slow.  If your routing problem is much bigger, we recommend seeing if it can be broken down into smaller pieces.  ie.  Someone operating in a 5 state region can break the problem down into a few projects each serving a smaller area. 

If something like this doesn't work for you and you're still having problems with the size of the routing project, we can try to think of something else.

[BradClay]

okay,

let me seperate these into projects and see what happens

thanks