Isolate: Difference between revisions
No edit summary |
No edit summary |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
[[Category:Commander4j]] | |||
There are always instances where problems occur during the manufacturing process and when this happens you may want to isolate any finished goods which are effected - pending quality control investigation. | There are always instances where problems occur during the manufacturing process and when this happens you may want to isolate any finished goods which are effected - pending quality control investigation. | ||
[[file:MHN1.png|800px]] | [[file:MHN1.png|link=|800px]] | ||
Commander4j has an Isolation screen which allows you to record a quality control concern/incident and associate all the pallets which are affected. On the above screen you will see an example Isolation and the system generated unique id which is referred to as a MHN (Master Hold Notice). | Commander4j has an Isolation screen which allows you to record a quality control concern/incident and associate all the pallets which are affected. On the above screen you will see an example Isolation and the system generated unique id which is referred to as a MHN (Master Hold Notice). | ||
| Line 7: | Line 8: | ||
If you add/edit a MHN you will see all the Pallets (SSCC's) which have been assigned to it along with the [[Quality Control Reasons]] for it. | If you add/edit a MHN you will see all the Pallets (SSCC's) which have been assigned to it along with the [[Quality Control Reasons]] for it. | ||
[[file:MHN2.png|800px]] | [[file:MHN2.png|link=|800px]] | ||
Each SSCC attached to the MHN can then be checked and a [Quality Control Decision](https://github.com/C4J/Commander4j/wiki/Quality-Control-Decisions) applied to it. | Each SSCC attached to the MHN can then be checked and a [Quality Control Decision](https://github.com/C4J/Commander4j/wiki/Quality-Control-Decisions) applied to it. | ||
[[file:MHN3.png|800px]] | [[file:MHN3.png|link=|800px]] | ||
Adding Pallets to an Isolation (MHN) is done by clicking on the Add button and then using the screen shown below to select the Pallets in the database using whatever criteria you want. | Adding Pallets to an Isolation (MHN) is done by clicking on the Add button and then using the screen shown below to select the Pallets in the database using whatever criteria you want. | ||
[[file:MHN4.png|800px]] | [[file:MHN4.png|link=|800px]] | ||
Assigning a decision to a SSCC in the Isolation module will also update the Pallet Status. This means that a Pallet can be blocked from moving or despatching. | Assigning a decision to a SSCC in the Isolation module will also update the Pallet Status. This means that a Pallet can be blocked from moving or despatching. | ||
[[file:MHN_Decisions2.png|500px]] | [[file:MHN_Decisions2.png|link=|500px]] | ||
This decision is associated with a status of Unrestricted. | This decision is associated with a status of Unrestricted. | ||
[[file:MHN_Decisions3.png| | [[file:MHN_Decisions3.png|link=|500px]] | ||
This decision is associated with a status of Restricted. | This decision is associated with a status of Restricted. | ||
[[file:MHN_Location_Status.png|400px]] | [[file:MHN_Location_Status.png|link=|400px]] | ||
The Location record can be setup to permit or block pallets from being moved into it depending on the Pallet and Batch Status | The Location record can be setup to permit or block pallets from being moved into it depending on the Pallet and Batch Status | ||
[[file:MHN5.png|800px]] | [[file:MHN5.png|link=|800px]] | ||
In the above screen a pallet which is blocked is prevented from being added to a despatch. | In the above screen a pallet which is blocked is prevented from being added to a despatch. | ||
[[file:MHN6.png|800px]] | [[file:MHN6.png|link=|800px]] | ||
In this screen a pallet was added to the despatch while unrestricted and then its status changed to restricted. It was then impossible to confirm the despatch with a blocked pallet on it. The solution would be to remove the pallet or change its status. | In this screen a pallet was added to the despatch while unrestricted and then its status changed to restricted. It was then impossible to confirm the despatch with a blocked pallet on it. The solution would be to remove the pallet or change its status. | ||
Latest revision as of 11:33, 23 August 2024
There are always instances where problems occur during the manufacturing process and when this happens you may want to isolate any finished goods which are effected - pending quality control investigation.
Commander4j has an Isolation screen which allows you to record a quality control concern/incident and associate all the pallets which are affected. On the above screen you will see an example Isolation and the system generated unique id which is referred to as a MHN (Master Hold Notice).
If you add/edit a MHN you will see all the Pallets (SSCC's) which have been assigned to it along with the Quality Control Reasons for it.
Each SSCC attached to the MHN can then be checked and a [Quality Control Decision](https://github.com/C4J/Commander4j/wiki/Quality-Control-Decisions) applied to it.
Adding Pallets to an Isolation (MHN) is done by clicking on the Add button and then using the screen shown below to select the Pallets in the database using whatever criteria you want.
Assigning a decision to a SSCC in the Isolation module will also update the Pallet Status. This means that a Pallet can be blocked from moving or despatching.
This decision is associated with a status of Unrestricted.
This decision is associated with a status of Restricted.
The Location record can be setup to permit or block pallets from being moved into it depending on the Pallet and Batch Status
In the above screen a pallet which is blocked is prevented from being added to a despatch.
In this screen a pallet was added to the despatch while unrestricted and then its status changed to restricted. It was then impossible to confirm the despatch with a blocked pallet on it. The solution would be to remove the pallet or change its status.