I said it little wrong.
It's customezed solution based on Navision platform, but some procedures moved to T-SQL to speed up posting and processing routines.
You can faced with some difficulties using standart Nav WMS for 3PL requirements:
1. It is very difficult to specify different procedures for handling of cargo for different clients or under different requirements of the shipping agent.
2. Standart Nav doesn't support internal warehouse transport labels and orders. consolidation. It necessary if you work with mixed palletes or pack articles (clothes for example) in mixed boxes.
3. It impossible to manage group activites, for example wave picking or crossdoc by different condolidation rules (for example you have to crossdoc container on box level - every box has unique number and you have to arrange it for future shipping. Some boxes should be placed on pallet by carrier, some boxes - by city or shipping address).
4. Standart Nav bin directory doesn't have warehouse analitycs, such as rack, section, position in section, level, so you can't define flexible rules for put-away (XYX, ZYX etc) for different customers - only bin ranking is available.
5. Standart Nav doesn't support different stock keeping units for one item. For example PCS is base unit of measure, but item usually receipts in boxes, which contains packs, which containts PCS.
6. Standart Nav picking templates doesn't support flexible picking - customized sorting and filtering rules, it can't work with SKU and flexible expiration rules. For exampe customer of your customer work with canned food. For some shipping addresses they must ship food not less than 50% of expiration date, for some - not less than 45%, also opening boxes is prohibited (for eample it contains 20PCS). FEFO is mandatory if you pick boxes, but if order qty are multily to whole pallet - you should pick whole pallet by FEFO even then you have boxes with early production date...
May be it can be helpful to define requirements list.
Hi.
I have been implemented WMS specific for 3PL provider.
It's customized solution with lot of T-SQL code - standart put-away and picking templates, posting speed didn't meet customer requirements.
I said it little wrong.
It's customezed solution based on Navision platform, but some procedures moved to T-SQL to speed up posting and processing routines.
You can faced with some difficulties using standart Nav WMS for 3PL requirements:
1. It is very difficult to specify different procedures for handling of cargo for different clients or under different requirements of the shipping agent.
2. Standart Nav doesn't support internal warehouse transport labels and orders. consolidation. It necessary if you work with mixed palletes or pack articles (clothes for example) in mixed boxes.
3. It impossible to manage group activites, for example wave picking or crossdoc by different condolidation rules (for example you have to crossdoc container on box level - every box has unique number and you have to arrange it for future shipping. Some boxes should be placed on pallet by carrier, some boxes - by city or shipping address).
4. Standart Nav bin directory doesn't have warehouse analitycs, such as rack, section, position in section, level, so you can't define flexible rules for put-away (XYX, ZYX etc) for different customers - only bin ranking is available.
5. Standart Nav doesn't support different stock keeping units for one item. For example PCS is base unit of measure, but item usually receipts in boxes, which contains packs, which containts PCS.
6. Standart Nav picking templates doesn't support flexible picking - customized sorting and filtering rules, it can't work with SKU and flexible expiration rules. For exampe customer of your customer work with canned food. For some shipping addresses they must ship food not less than 50% of expiration date, for some - not less than 45%, also opening boxes is prohibited (for eample it contains 20PCS). FEFO is mandatory if you pick boxes, but if order qty are multily to whole pallet - you should pick whole pallet by FEFO even then you have boxes with early production date...
May be it can be helpful to define requirements list.
Answers
I have been implemented WMS specific for 3PL provider.
It's customized solution with lot of T-SQL code - standart put-away and picking templates, posting speed didn't meet customer requirements.
Nav, T-SQL.
It's customezed solution based on Navision platform, but some procedures moved to T-SQL to speed up posting and processing routines.
You can faced with some difficulties using standart Nav WMS for 3PL requirements:
1. It is very difficult to specify different procedures for handling of cargo for different clients or under different requirements of the shipping agent.
2. Standart Nav doesn't support internal warehouse transport labels and orders. consolidation. It necessary if you work with mixed palletes or pack articles (clothes for example) in mixed boxes.
3. It impossible to manage group activites, for example wave picking or crossdoc by different condolidation rules (for example you have to crossdoc container on box level - every box has unique number and you have to arrange it for future shipping. Some boxes should be placed on pallet by carrier, some boxes - by city or shipping address).
4. Standart Nav bin directory doesn't have warehouse analitycs, such as rack, section, position in section, level, so you can't define flexible rules for put-away (XYX, ZYX etc) for different customers - only bin ranking is available.
5. Standart Nav doesn't support different stock keeping units for one item. For example PCS is base unit of measure, but item usually receipts in boxes, which contains packs, which containts PCS.
6. Standart Nav picking templates doesn't support flexible picking - customized sorting and filtering rules, it can't work with SKU and flexible expiration rules. For exampe customer of your customer work with canned food. For some shipping addresses they must ship food not less than 50% of expiration date, for some - not less than 45%, also opening boxes is prohibited (for eample it contains 20PCS). FEFO is mandatory if you pick boxes, but if order qty are multily to whole pallet - you should pick whole pallet by FEFO even then you have boxes with early production date...
May be it can be helpful to define requirements list.
Nav, T-SQL.