Working of Radius based routing along with Node capacity - a new feature in 9.2

In product release 9.2 we have a new feature introduced, Radius based routing along with node capacity.

Working of Radius based routing along with Node capacity - a new feature in 9.2

In product release 9.2 we have a new feature introduced, Radius based routing along with node capacity.
Follow the below mentioned configurations :

Additional Configurations required :
Have a region schema implemented (US based region schema is provided out of the box)
Have a resource pool associated for the nodes.
Application Manager --> DOM --> Order promising --> Sourcing and Scheduling --> Product being shipped --> Sourcing Rules
Enable the below mentioned 2 properties and supply appropriate values :
- Consider only those nodes that are within 10 miles radius and
- Consider only those nodes that have a minimum available capacity of 10 % within the next 2 days.
Adjust inventory (inventory console) and capacity (SBC - Sterling business center) for the desired nodes.

Procedure:
Create an order with a 5 digit zip code passed in the biilTo address field.
Confirm the order and schedule it.

Product calculations :
First our product would extract the 5 digit zip code passed in the billTo address field and look for its corresponding longitude and latitude details in the database.
If no corresponding longitude and latitude details are fetched from the database then no calculations happen and the order backorders.
If a corresponding longitude and latitude detail is fetched for the 5 digit zip code, then the product would calculate and look out for all the node within 10 miles of radius.
Once a few nodes have been shortlisted within 10miles radius range, then the inventory is checked for this particular item.
Upon further filtering, product would proceed to apply the capacity constraint.
It would check if a minimum of 10% capacity is available in the next 2 days for each of the node that has been filtered so far.
If any of the node qualifies, passing all the filtration, then the product would be scheduled against that node.

Thus the above mentioned rule ensures radius based routing and also the capacity availability in such nodes.