REL C-MCS v2.00.03.000: Difference between revisions
m (Test) |
(Updated with more detailed information.) |
||
(One intermediate revision by the same user not shown) | |||
Line 3: | Line 3: | ||
{{#vardefine:SystemCode|MCS}} | {{#vardefine:SystemCode|MCS}} | ||
{{#vardefine:Version|2.00.03.000}} | {{#vardefine:Version|2.00.03.000}} | ||
{{#vardefine:Date| | {{#vardefine:Date|16th October 2019}} | ||
__NOTOC__ | __NOTOC__ | ||
</div> | </div> | ||
Line 39: | Line 38: | ||
'''Related Documents''' | '''Related Documents''' | ||
All functionality in this release has been subject to full specification. These documents are available on request. | |||
== User notes == | == User notes == | ||
This is a release | {{Warning}} This is a combined release of all new functionality for MCS. This release makes significant changes to all aspects of MCS functionality. The changes have been made to be configurable. However, existing customers using MCS ''must'' fully system test the changes to ensure that their required processes still work as expected. | ||
Line 49: | Line 48: | ||
This release contains the following fixes/changes: | This release contains the following fixes/changes: | ||
;359675; MCS Display Product Type & Vehicle | |||
The MCS UI has been changed to be configurable as to what information can be displayed in various screens: | |||
* Pallet Building can be configured as to whether product type, commodity code and hazardous status. | |||
* Receipt and despatch item lists may now be configured to display the product type, commodity code and hazardous status against the scannable items, and will always display the trip ID and vehicle at the top of the screen. The screen can also be configured to display the C-TMS DU type instead of the default "PACKAGE" for individual items (i.e. packages, non-palletised). | |||
;359671; Pallet Closure and Pallet Building changes. | |||
MCS has been changed to add functionality to pallet building: | |||
* A Pallet Closure function has been added, accessible from the menu for locations that are configured to have this functionality. This allows the users to close a pallet that has been built at that location. This process can also be configured to require the users to enter a seal number when closing the pallet, which is stored in the AWB/Consignment number fields. | |||
* New pallet building criteria has been added that allows the location to be configured to build pallets based on: | |||
** "By Final ROC" - pallets can only contain packages that are planned to be delivered from the same final delivery depot. | |||
** "By Final ROC Trip" - pallets can only contain packages that are planned onto the same final delivery trip. | |||
** Existing functionality is still supported as the default option of "To Next RDC" | |||
* Suggested pallets for pallet building now takes into account the pallet building criteria. | |||
* Creating a new pallet at pallet building can now be through entry of a pre-printed pallet ID label. | |||
Additionally, the following functionality can also be configured: | |||
* Control specific actions when MCS functionality is completed at TENDERED status rather than at ACCEPTED status. | |||
* Prevent prompts for AWB/Consignment number through out the product. | |||
;359674; Trans Ship functionality. | |||
MCS has been modified to support trans-ship functionality when receiving at configured locations: | |||
* If the pallet or package has been planned on a despatching trip from this configured location, the process will display the trip details (including assigned resources), confirming through entry of the vehicle. | |||
* Pallets and packages that have been trans-shipped will be marked as received ''and'' despatched in C-TMS. | |||
* Packages and packages on pallets that have been trans-shipped can still be seen on the MCS Despatch screen as Loaded items. | |||
* {{Note}} Packages that have not been planned out of this location, or pallets where all packages have not been planned out this location on the same trip cannot be trans-shipped - the system will inform the user and these packages must be manually scanned for despatch. | |||
* {{Note}} Enabling this functionality means that receipt at the location can no longer be run without an internet connection. | |||
;359670; Read in ADM_SYSTEM_PARAMS etc. | |||
MCS has been modified to read in multiple system and location parameters to control all new functionality described on this release. | |||
;359755; Add styles; add terms; style menu control; change publish settings update version; fix menu icons. | |||
The MCS UI has been updated to a more modern customisable theme. | |||
;349100; Added bulk locations functionality. | |||
;359670; Check system type. | |||
Work has begin to extend MCS to work with WMS. By default, the system is configured to TMS system type and therefore excludes this prototype functionality. | |||
<!-- NEW PAGE --> | <!-- NEW PAGE --> | ||
Line 62: | Line 98: | ||
! By!! Reference !! Description | ! By!! Reference !! Description | ||
|- | |- | ||
| | | Client || 359671 || Product type incompatibility should be maintained to support pallet building validation. | ||
|- | |||
| Client || 359671 / 359674 / 359670 || Location configuration should be maintained to support the following functionality: | |||
* Pallet Label Pre-printed. | |||
* Pallet Building validation. | |||
* Pallet Closure. | |||
* Trans-ship enabled. | |||
* Pallet Seal Required. | |||
* Debrief Stop Times. | |||
|- | |||
| OBS || 359671 / 359675 || The system can be configured to support the following functionality: | |||
* MCS_PALLET_LABEL_FORMAT | |||
* MCS_AWB_REQUIRED | |||
* MCS_DISPLAY_PROD_TYPE | |||
* MCS_DISPLAY_COMMTYPE_HAZ | |||
* MCS_ITEM_DISPLAY_DU | |||
* MCS_TENDERED_ITEMS | |||
|} | |} | ||
== User Instructions == | == User Instructions == | ||
{{Note}} Due to the wide-ranging nature of these changes, it is ''strongly'' recommended that you contact your OBS support team for details on how these changes can affect your MCS implementation. It is also recommended that the functional specifications describing these processes be obtained for detailed process change information. | |||
== Performance Notes == | |||
{{Note}} Enabling this functionality means that receipt at the location can no longer be run without an internet connection. | |||
It is not expected that this release will have any positive or adverse impact on system performance. | |||
It is not expected that this | |||
== Related Releases == | == Related Releases == | ||
The following C-TMS Emergency Releases are required for this functionality to be enabled: | |||
* ER CTMS 034-052 | |||
* ER CTMS 034-031 | |||
* ER CTMS 034-018 | |||
These are also included in the following C-TMS patch: | |||
* PATCH C-TMS P035 | |||
{{Note}} The full patch update is ''strongly'' recommended in this case. | |||
== Technical Changes & Special Notes == | == Technical Changes & Special Notes == | ||
{{Note}} Due to the wide-ranging nature of these changes, it is ''strongly'' recommended that you contact your OBS support team for details on how these changes can affect your MCS implementation. It is also recommended that the functional specifications describing these processes be obtained for detailed process change information. | |||
Latest revision as of 13:40, 10 February 2020
CALIDUS MCS
User Release Notes
CALIDUS MCS 2.00.03.000
16th October 2019
Introduction
This document describes the contents of this CALIDUS MCS release.
Platforms/Database
The release will be tested against & supported only for the following platform/database combinations:
- Chrome version 32 (and above)
Related Documents
All functionality in this release has been subject to full specification. These documents are available on request.
User notes
Warning: This is a combined release of all new functionality for MCS. This release makes significant changes to all aspects of MCS functionality. The changes have been made to be configurable. However, existing customers using MCS must fully system test the changes to ensure that their required processes still work as expected.
Released Incidents / Changes
This release contains the following fixes/changes:
- 359675; MCS Display Product Type & Vehicle
The MCS UI has been changed to be configurable as to what information can be displayed in various screens:
- Pallet Building can be configured as to whether product type, commodity code and hazardous status.
- Receipt and despatch item lists may now be configured to display the product type, commodity code and hazardous status against the scannable items, and will always display the trip ID and vehicle at the top of the screen. The screen can also be configured to display the C-TMS DU type instead of the default "PACKAGE" for individual items (i.e. packages, non-palletised).
- 359671; Pallet Closure and Pallet Building changes.
MCS has been changed to add functionality to pallet building:
- A Pallet Closure function has been added, accessible from the menu for locations that are configured to have this functionality. This allows the users to close a pallet that has been built at that location. This process can also be configured to require the users to enter a seal number when closing the pallet, which is stored in the AWB/Consignment number fields.
- New pallet building criteria has been added that allows the location to be configured to build pallets based on:
- "By Final ROC" - pallets can only contain packages that are planned to be delivered from the same final delivery depot.
- "By Final ROC Trip" - pallets can only contain packages that are planned onto the same final delivery trip.
- Existing functionality is still supported as the default option of "To Next RDC"
- Suggested pallets for pallet building now takes into account the pallet building criteria.
- Creating a new pallet at pallet building can now be through entry of a pre-printed pallet ID label.
Additionally, the following functionality can also be configured:
- Control specific actions when MCS functionality is completed at TENDERED status rather than at ACCEPTED status.
- Prevent prompts for AWB/Consignment number through out the product.
- 359674; Trans Ship functionality.
MCS has been modified to support trans-ship functionality when receiving at configured locations:
- If the pallet or package has been planned on a despatching trip from this configured location, the process will display the trip details (including assigned resources), confirming through entry of the vehicle.
- Pallets and packages that have been trans-shipped will be marked as received and despatched in C-TMS.
- Packages and packages on pallets that have been trans-shipped can still be seen on the MCS Despatch screen as Loaded items.
Note: Packages that have not been planned out of this location, or pallets where all packages have not been planned out this location on the same trip cannot be trans-shipped - the system will inform the user and these packages must be manually scanned for despatch.
Note: Enabling this functionality means that receipt at the location can no longer be run without an internet connection.
- 359670; Read in ADM_SYSTEM_PARAMS etc.
MCS has been modified to read in multiple system and location parameters to control all new functionality described on this release.
- 359755; Add styles; add terms; style menu control; change publish settings update version; fix menu icons.
The MCS UI has been updated to a more modern customisable theme.
- 349100; Added bulk locations functionality.
- 359670; Check system type.
Work has begin to extend MCS to work with WMS. By default, the system is configured to TMS system type and therefore excludes this prototype functionality.
Setup
Details of any system setup required by either OBS or Client:
By | Reference | Description |
---|---|---|
Client | 359671 | Product type incompatibility should be maintained to support pallet building validation. |
Client | 359671 / 359674 / 359670 | Location configuration should be maintained to support the following functionality:
|
OBS | 359671 / 359675 | The system can be configured to support the following functionality:
|
User Instructions
Note: Due to the wide-ranging nature of these changes, it is strongly recommended that you contact your OBS support team for details on how these changes can affect your MCS implementation. It is also recommended that the functional specifications describing these processes be obtained for detailed process change information.
Performance Notes
Note: Enabling this functionality means that receipt at the location can no longer be run without an internet connection.
It is not expected that this release will have any positive or adverse impact on system performance.
Related Releases
The following C-TMS Emergency Releases are required for this functionality to be enabled:
- ER CTMS 034-052
- ER CTMS 034-031
- ER CTMS 034-018
These are also included in the following C-TMS patch:
- PATCH C-TMS P035
Note: The full patch update is strongly recommended in this case.
Technical Changes & Special Notes
Note: Due to the wide-ranging nature of these changes, it is strongly recommended that you contact your OBS support team for details on how these changes can affect your MCS implementation. It is also recommended that the functional specifications describing these processes be obtained for detailed process change information.