Pando as a cloud product is capable of hosting and running various operations at the same time. However, the speed and capacity at which records can be fetched and operations be run is a function of the number of parallel ongoing operations and depends on loads currently on the system. As a safe practice, it is recommended that the following limits are adhered to when uploading masters or running calculations to keep the Pando experience seamless and prevent any lag while accessing records:
            

  • Procure: For the Freight Procurement module, the average runtime of the product depends on the number of transporters and lanes present in the excel file. As a best practice, it is recommended that the total number of records in a procure event file does not exceed 100,000 records. Say, for example, there are 500 transporters, it is recommended that the number of lanes being floated for auction be set at 200 and not higher. Any higher, the system may face slowdowns and will also impact loading times when accessing the contracts after the event. 

  • Optima: For Delivery Planning and Optimization, an Optima run uses computation and configured constraints to identify the most efficient way of delivering all materials from the sales order. Based on constraints, a scheduled optima run provides an output of a delivery pick list everyday based on all the lanes that have been set up and fleet availability for the said lanes. However, the time taken for an Optima run is a function of the number of materials that have been added to the run. A shipment can contain any number of materials/line items. The load on the system is dependent on the number of materials uploaded. Furthermore, the load is also dependent on the type of movement. The number of combinations run by Pando varies with available routes, contracts, and destination.
    • For primary movement, the load on the system is generally low. Thereby, it is suggested that up to 10000 materials can be included for a Primary Optima run.

    • For secondary movements, however, the number of combinations that Pando will have to run is higher owing to the spread of consignees and drop-off locations. While there is no restriction to set the number of materials higher, it has been observed that when the number of materials added to a single Optima run crosses 200, the time taken for the run and for results to be generated may take more than a few minutes. To avoid this, it is recommended that the number of materials added to the run is kept at 200 or lower.

  • Manage: The number of materials added to an indent determines the loading time for a single record. A higher number of materials uploaded to a shipment would translate into slower loading for the page. To reduce such instances, it is recommended that the number of materials added to an indent are does not exceed 1000.

  • Pay: In the Pay module there is no upper limit on the number of shipments that can be combined to raise an invoice. However, it is recommended that a total of only 100 indents be clubbed together when raising an invoice. Combining a higher number of indents is not recommended as it can significantly slow down the time taken to compute the charges and generate the invoice. Additionally, with our latest release, we have also enabled admins to cap the age within which the indents can be combined. Admins can opt to block indents from the previous month from being added to create an invoice.