open bugs in software

1
Open bugs: 1. 2015.06.25 - Resetting service times to zero is not accurate – service time should not be set to zero if the adjacent orders are not served at the same time: [INFO ] 2015-06-26 17:56:55.481 - /------ROUTE-[1]----------------------- [INFO ] 2015-06-26 17:56:55.481 - [driver:] 1 [vehicle:] 1: 73 km, 18853 min [INFO ] 2015-06-26 17:56:55.482 - >> [pos:] 0: [nodeId:] 0: [entityId:] 0: [orderType:] TERM [arrive:] 2014.12.11 22:38, [load:] [totValue=0.0, totVolume=0.0, totWeight=0.0] [INFO ] 2015-06-26 17:56:55.482 - >> [pos:] 1: [nodeId:] 1676: [entityId:] 1: [orderType:] PICK [arrive:] 2014.12.12 00:00, [load:] [totValue=0.0, totVolume=0.1, totWeight=25.0] [INFO ] 2015-06-26 17:56:55.482 - >> [pos:] 2: [nodeId:] 3393: [entityId:] 1: [orderType:] PICK [arrive:] 2014.12.25 00:00, [load:] [totValue=0.0, totVolume=1.67, totWeight=251.0] [INFO ] 2015-06-26 17:56:55.482 - >> [pos:] 3: [nodeId:] 0: [entityId:] 0: [orderType:] TERM [arrive:] 2014.12.25 00:51, [load:] [totValue=0.0, totVolume=1.67, totWeight=251.0] [INFO ] 2015-06-26 17:56:55.482 - ---------------------------------------/ 2. Refactor TimeAllocation (~row 93) The calculation of available vehicle & driver free intervals around the order serving date currently calls terminal goods stock to determine ealiest time goods are available. Additionally, there is a fixed time of 15 days imposed for delivery. Validations in this procedure should be limited to the driver’s / vehicle’s availability related to the order serving time (i.e. absolute if a pickup; absolute if a delivery independent of any pickups; relative if a delivery following a former pickup).

Upload: lucianmol

Post on 04-Sep-2015

218 views

Category:

Documents


4 download

DESCRIPTION

Open bugs in software

TRANSCRIPT

Open bugs:

1. 2015.06.25 - Resetting service times to zero is not accurate service time should not be set to zero if the adjacent orders are not served at the same time:

[INFO ] 2015-06-26 17:56:55.481 - /------ROUTE-[1]-----------------------

[INFO ] 2015-06-26 17:56:55.481 - [driver:] 1 [vehicle:] 1: 73 km, 18853 min

[INFO ] 2015-06-26 17:56:55.482 - >> [pos:] 0: [nodeId:] 0: [entityId:] 0: [orderType:] TERM [arrive:] 2014.12.11 22:38,

[load:] [totValue=0.0, totVolume=0.0, totWeight=0.0]

[INFO ] 2015-06-26 17:56:55.482 - >> [pos:] 1: [nodeId:] 1676: [entityId:] 1: [orderType:] PICK [arrive:] 2014.12.12 00:00,

[load:] [totValue=0.0, totVolume=0.1, totWeight=25.0]

[INFO ] 2015-06-26 17:56:55.482 - >> [pos:] 2: [nodeId:] 3393: [entityId:] 1: [orderType:] PICK [arrive:] 2014.12.25 00:00,

[load:] [totValue=0.0, totVolume=1.67, totWeight=251.0]

[INFO ] 2015-06-26 17:56:55.482 - >> [pos:] 3: [nodeId:] 0: [entityId:] 0: [orderType:] TERM [arrive:] 2014.12.25 00:51,

[load:] [totValue=0.0, totVolume=1.67, totWeight=251.0]

[INFO ] 2015-06-26 17:56:55.482 - ---------------------------------------/

2. Refactor TimeAllocation (~row 93)

The calculation of available vehicle & driver free intervals around the order serving date currently calls terminal goods stock to determine ealiest time goods are available. Additionally, there is a fixed time of 15 days imposed for delivery.

Validations in this procedure should be limited to the drivers / vehicles availability related to the order serving time (i.e. absolute if a pickup; absolute if a delivery independent of any pickups; relative if a delivery following a former pickup).