REQ 290107 Nightfreight RF Requirements - Revision history

Anw: Edited to clarify categories

2011-08-18T07:59:40Z

Edited to clarify categories

← Older revision		Revision as of 09:59, 18 August 2011
Line 1:		Line 1:
	<div class="noprint">		<div class="noprint">
	{{#vardefine:Client\|Nightfreight}}		{{#vardefine:Client\|PACE}}
			{{#vardefine:ClientName\|Nightfreight Pacemaker}}
	{{#vardefine:System\|Calidus Mobile}}		{{#vardefine:System\|Calidus Mobile}}
	{{#vardefine:Doc_Title\|Nightfreight RF Requirements}}		{{#vardefine:Doc_Title\|Nightfreight RF Requirements}}
Line 8:		Line 9:
	</div>		</div>
	{{Doc_Title		{{Doc_Title
	\|Client={{#var:~~Client~~}}		\|Client={{#var:ClientName}}
	\|System={{#var:System}}		\|System={{#var:System}}
	\|Title={{#var:Doc_Title}}		\|Title={{#var:Doc_Title}}
Line 23:		Line 24:

	== Objective ==		== Objective ==
	The primary purpose of this document is to document the requirements gathered from {{#var:~~Client~~}}, at the OBS Logistics offices in Liverpool, on 6-7th July 2011.		The primary purpose of this document is to document the requirements gathered from {{#var:ClientName}}, at the OBS Logistics offices in Liverpool, on 6-7th July 2011.

	<!-- List all amendments to the requirements here, and reference in final section, e.g. The document also encompasses the follow-up meeting held at X, with Y and Z attending, where the requirements were modified. See the minutes of the meeting referenced as item X in appendix B -->		<!-- List all amendments to the requirements here, and reference in final section, e.g. The document also encompasses the follow-up meeting held at X, with Y and Z attending, where the requirements were modified. See the minutes of the meeting referenced as item X in appendix B -->

	This document has been written in a manner such that it can be approved by non-technical representatives of {{#var:~~Client~~}} whilst also being of sufficient detail to allow the Functional or Technical Specification phase for this area to begin.		This document has been written in a manner such that it can be approved by non-technical representatives of {{#var:ClientName}} whilst also being of sufficient detail to allow the Functional or Technical Specification phase for this area to begin.

	== Scope and Limitations ==		== Scope and Limitations ==
	This document is based on the documentation provided by {{#var:~~Client~~}}, as referred to in the appendices, as well as information gleaned from workshops with {{#var:~~Client~~}}.		This document is based on the documentation provided by {{#var:ClientName}}, as referred to in the appendices, as well as information gleaned from workshops with {{#var:ClientName}}.

	<!-- ANY scope or limitations, bulleted. -->		<!-- ANY scope or limitations, bulleted. -->
Line 958:		Line 959:
	\|Rev2Title=Client Representative		\|Rev2Title=Client Representative
	}}</div>		}}</div>
	[[Category:REQ]]		[[Category:{{#var:Client}} REQ]]

Anw: v1.0 - Issued after review by Julie Scott

2011-07-15T10:11:38Z

v1.0 - Issued after review by Julie Scott

← Older revision		Revision as of 12:11, 15 July 2011
Line 3:		Line 3:
	{{#vardefine:System\|Calidus Mobile}}		{{#vardefine:System\|Calidus Mobile}}
	{{#vardefine:Doc_Title\|Nightfreight RF Requirements}}		{{#vardefine:Doc_Title\|Nightfreight RF Requirements}}
	{{#vardefine:Version\|0.4}}		{{#vardefine:Version\|1.0}}
	{{#vardefine:Date\|15th July 2011}}		{{#vardefine:Date\|15th July 2011}}
	{{#vardefine:Reference\|290107}}		{{#vardefine:Reference\|290107}}

Anw: /* Scope and Limitations */

2011-07-15T10:06:41Z

Scope and Limitations

← Older revision		Revision as of 12:06, 15 July 2011
Line 33:		Line 33:

	<!-- ANY scope or limitations, bulleted. -->		<!-- ANY scope or limitations, bulleted. -->
	*The changes will be made in the latest version 3.4 of the Calidus 3pl-Mobile system, and version 7.70 of the Calidus WMS system.		* The changes will be made in the latest version 3.4 of the Calidus 3pl-Mobile system, and version 7.70 of the Calidus WMS system.
			* The client has decided that the initial implementation will be for Goods In processes only.

	<!-- NEW PAGE -->		<!-- NEW PAGE -->

	= Client Requirements =		= Client Requirements =

Anw: v0.4 - Minor changes and changed format to Calidus Assist

2011-07-15T08:18:07Z

v0.4 - Minor changes and changed format to Calidus Assist

← Older revision		Revision as of 10:18, 15 July 2011
Line 3:		Line 3:
	{{#vardefine:System\|Calidus Mobile}}		{{#vardefine:System\|Calidus Mobile}}
	{{#vardefine:Doc_Title\|Nightfreight RF Requirements}}		{{#vardefine:Doc_Title\|Nightfreight RF Requirements}}
	{{#vardefine:Version\|0.1}}		{{#vardefine:Version\|0.4}}
	{{#vardefine:Date\|~~8th~~ July 2011}}		{{#vardefine:Date\|15th July 2011}}
	{{#vardefine:Reference\|290107}}		{{#vardefine:Reference\|290107}}
	</div>		</div>

Anw: v0.4 - Minor changes and changed format to Calidus Assist

2011-07-15T08:17:31Z

v0.4 - Minor changes and changed format to Calidus Assist

← Older revision		Revision as of 10:17, 15 July 2011
Line 910:		Line 910:
	\|Description=A new RF Loading process is required by the operation.		\|Description=A new RF Loading process is required by the operation.
	\|Estimate=7500		\|Estimate=7500
			\|Notes=
			}}
			{{REQ_SCR_Line\|SCR=
			\|System=
			\|Area=
			\|Description='''Total'''
			\|Estimate=51200
	\|Notes=		\|Notes=
	}}		}}

Anw at 08:14, 15 July 2011

2011-07-15T08:14:16Z

Show changes

Anw at 08:09, 15 July 2011

2011-07-15T08:09:49Z

← Older revision		Revision as of 10:09, 15 July 2011
Line 39:		Line 39:
	= Client Requirements =		= Client Requirements =
	Listed below are the proposed processes that will be followed by the warehouse operatives using ''Calidus'' Mobile. Also shown are the SCRs required for this to be achieved.		Listed below are the proposed processes that will be followed by the warehouse operatives using ''Calidus'' Mobile. Also shown are the SCRs required for this to be achieved.


	== Operational Information ==		== Operational Information ==
Line 111:		Line 110:

	The locations in the warehouse will be barcodes with a CODE-128 barcode containing the location code only. This will also be human-readable. The printing of the barcodes and subsequent labelling of the locations will be undertaken by the operation.		The locations in the warehouse will be barcodes with a CODE-128 barcode containing the location code only. This will also be human-readable. The printing of the barcodes and subsequent labelling of the locations will be undertaken by the operation.


	== Goods In ==		== Goods In ==
Line 238:		Line 236:

	It was noted that there may be potential to receive stock through a reduced number of barcode scans, by combining the scans of the delivery labels' UCC/EAN barcodes and extracting all the information as possible in one process. This functionality is being produced within the product at this time, but is not yet available. Once this is available, the process will be checked by the operation to see if it is suitable without modification.		It was noted that there may be potential to receive stock through a reduced number of barcode scans, by combining the scans of the delivery labels' UCC/EAN barcodes and extracting all the information as possible in one process. This functionality is being produced within the product at this time, but is not yet available. Once this is available, the process will be checked by the operation to see if it is suitable without modification.


	=== RF Putaway Process ===		=== RF Putaway Process ===
Line 271:		Line 268:

	'''SCR-290107-4: Ensure that the ''Calidus'' WMS Receipt and putaway processes correctly de-palletise stock.'''		'''SCR-290107-4: Ensure that the ''Calidus'' WMS Receipt and putaway processes correctly de-palletise stock.'''


	=== Loose Wood Goods In Process ===		=== Loose Wood Goods In Process ===
Line 324:		Line 320:

	'''SCR-290107-5: Ensure that combination of RF receipt and manual putaway correctly de-palletises the product received.'''		'''SCR-290107-5: Ensure that combination of RF receipt and manual putaway correctly de-palletises the product received.'''


	=== Rolled up Mattresses Goods In Process ===		=== Rolled up Mattresses Goods In Process ===
Line 334:		Line 329:

	'''Note:''' If this supplier labelling issue cannot be resolved, rolled up Mats will not be RF received.		'''Note:''' If this supplier labelling issue cannot be resolved, rolled up Mats will not be RF received.


	=== Cross-Dock ===		=== Cross-Dock ===
Line 342:		Line 336:

	The putaway will then be confirmed using the ''Calidus'' WMS Goods Receipt Putaway Confirmation process.		The putaway will then be confirmed using the ''Calidus'' WMS Goods Receipt Putaway Confirmation process.


	=== Returns ===		=== Returns ===
	At this time Returns are not processed through the ''Calidus'' WMS or RF system.		At this time Returns are not processed through the ''Calidus'' WMS or RF system.


	== Stock Control ==		== Stock Control ==
Line 406:		Line 398:


	It is also possible to allow RF users the ability to move stock from one location to another using a RF process called Ad-Hoc Stock Moves.		It is also possible to allow RF users the ability to move stock from one location to another using a RF process called Ad-Hoc Stock Moves. The process for this is as follows:

	The user will enter Stock Move Function on the RF unit.		:The user will enter Stock Move Function on the RF unit.

	The module will request the user to enter or scan a location.		:The module will request the user to enter or scan a location.

	Once there, the RDT will request the user to confirm a SKU. The WCS will check the availability of the stock for a movement at this time with the WMS. If the stock is unavailable for movement (i.e. it is already on a move, or any stock is allocated), the RDT will display an error.		:Once there, the RDT will request the user to confirm a SKU. The WCS will check the availability of the stock for a movement at this time with the WMS. If the stock is unavailable for movement (i.e. it is already on a move, or any stock is allocated), the RDT will display an error.

	'''Note:''' Only one user will be able to move stock from one location at one time - if stock is already held for ad hoc move by another user, the RDT will display an error.		:'''Note:''' Only one user will be able to move stock from one location at one time - if stock is already held for ad hoc move by another user, the RDT will display an error.

	If the stock is available, the WMS process will reserve the stock for Ad Hoc Moves (with a predefined system reason code) and tell the RDT how much stock is available.		:If the stock is available, the WMS process will reserve the stock for Ad Hoc Moves (with a predefined system reason code) and tell the RDT how much stock is available.

	The RDT will prompt for the user to enter the amount of stock to be moved, validating against the available quantity.		:The RDT will prompt for the user to enter the amount of stock to be moved, validating against the available quantity.

	Once entered, the RDT will prompt the user to take the stock collected to its destination.		:Once entered, the RDT will prompt the user to take the stock collected to its destination.

	Once confirmed, a message will be sent to the WMS to confirm all the reserved stock into this location.		:Once confirmed, a message will be sent to the WMS to confirm all the reserved stock into this location.

	It was decided that this process may be enabled in a later phase if required but was not part of the project at this time.		It was decided that this process may be enabled in a later phase if required but was not part of the project at this time.
Line 485:		Line 477:

	It was decided that this process may be enabled in a later phase if required but was not part of the project at this time.		It was decided that this process may be enabled in a later phase if required but was not part of the project at this time.


	== Order Process ==		== Order Process ==
Line 565:		Line 556:

	Once all items on their allocated pick sheets are complete, the paperwork is returned to the office and the system is updated: all completed picks are confirmed, whilst all incomplete picks are left. '''Note:''' This process of leaving incomplete picks must be confirmed by the operation.		Once all items on their allocated pick sheets are complete, the paperwork is returned to the office and the system is updated: all completed picks are confirmed, whilst all incomplete picks are left. '''Note:''' This process of leaving incomplete picks must be confirmed by the operation.


	=== RF Picking Process ===		=== RF Picking Process ===
Line 763:		Line 753:

	These are manual (i.e. non-RF) tasks.		These are manual (i.e. non-RF) tasks.


	== Loading ==		== Loading ==

Anw: /* Appendix A: Table of SCRs and Ballpark Estimates */

2011-07-15T08:03:02Z

Appendix A: Table of SCRs and Ballpark Estimates

← Older revision		Revision as of 10:03, 15 July 2011
Line 894:		Line 894:
	\|Description=Remove the Marshalling prompt from the RF Picking dialogue.		\|Description=Remove the Marshalling prompt from the RF Picking dialogue.
	\|Estimate=1750		\|Estimate=1750
	\|Notes=1		\|Notes=
	}}		}}
	{{REQ_SCR_Line\|SCR={{ #vardefineecho: SCR \| {{ #expr: {{ #var: SCR }} + 1 }} }}		{{REQ_SCR_Line\|SCR={{ #vardefineecho: SCR \| {{ #expr: {{ #var: SCR }} + 1 }} }}
Line 901:		Line 901:
	\|Description=Delete any unconfirmed pick tasks if there are any exceptions.		\|Description=Delete any unconfirmed pick tasks if there are any exceptions.
	\|Estimate=1750		\|Estimate=1750
	\|Notes=1		\|Notes=
	}}		}}
	{{REQ_SCR_Line\|SCR={{ #vardefineecho: SCR \| {{ #expr: {{ #var: SCR }} + 1 }} }}		{{REQ_SCR_Line\|SCR={{ #vardefineecho: SCR \| {{ #expr: {{ #var: SCR }} + 1 }} }}
Line 908:		Line 908:
	\|Description=Delay confirmation of picked items until the whole order is picked.		\|Description=Delay confirmation of picked items until the whole order is picked.
	\|Estimate=5750		\|Estimate=5750
	\|Notes=1		\|Notes=
	}}		}}
	{{REQ_SCR_Line\|SCR={{ #vardefineecho: SCR \| {{ #expr: {{ #var: SCR }} + 1 }} }}		{{REQ_SCR_Line\|SCR={{ #vardefineecho: SCR \| {{ #expr: {{ #var: SCR }} + 1 }} }}
Line 915:		Line 915:
	\|Description=Create Loading Tasks.		\|Description=Create Loading Tasks.
	\|Estimate=3500		\|Estimate=3500
	\|Notes=1		\|Notes=
	}}		}}
	{{REQ_SCR_Line\|SCR={{ #vardefineecho: SCR \| {{ #expr: {{ #var: SCR }} + 1 }} }}		{{REQ_SCR_Line\|SCR={{ #vardefineecho: SCR \| {{ #expr: {{ #var: SCR }} + 1 }} }}
Line 922:		Line 922:
	\|Description=A new RF Loading process is required by the operation.		\|Description=A new RF Loading process is required by the operation.
	\|Estimate=7500		\|Estimate=7500
	\|Notes=1		\|Notes=
	}}		}}
	{{REQ_SCR_Footer}}		{{REQ_SCR_Footer}}
Line 944:		Line 944:
	\|Estimate=N		\|Estimate=N
	\|Glossary=WCS		\|Glossary=WCS
	\|Ref1=		\|Ref1=
	\|RefV1=		\|RefV1=
	\|RefDate1=		\|RefDate1=
	\|REQ=0		\|REQ=0
	\|EST=0		\|EST=0

Anw: /* RF Picking Process */

2011-07-15T08:00:58Z

RF Picking Process

← Older revision		Revision as of 10:00, 15 July 2011
Line 583:		Line 583:


	{\| ~~class~~="~~prettytable~~"		{\| width="100%" border="1px"
	! Aisle		! Aisle
	! colspan="6" \| Orders with picks in the aisle		! colspan="6" \| Orders with picks in the aisle
Line 642:		Line 642:

	\|}		\|}
	# Picking in Aisle A will pick, in this sequence:		1 Picking in Aisle A will pick, in this sequence:

	* Order 1 from aisle A		* Order 1 from aisle A
Line 656:		Line 656:
	'''Note''' that the picking sequence is by order, not by location efficient sequencing.		'''Note''' that the picking sequence is by order, not by location efficient sequencing.

	# Picking in aisle B will pick, in this sequence:		2 Picking in aisle B will pick, in this sequence:

	* Order 6 from aisle B		* Order 6 from aisle B
Line 664:		Line 664:
	* Order 7 from aisle B (second product)		* Order 7 from aisle B (second product)

	# Picking in aisle C will pick, in this sequence:		3 Picking in aisle C will pick, in this sequence:

	* Order 8 from aisle C		* Order 8 from aisle C
Line 670:		Line 670:
	'''Note''' that the task for order 2 will not be given to the users in aisle C, even if they start first, as the task has been marked for completion by the users in aisle B.		'''Note''' that the task for order 2 will not be given to the users in aisle C, even if they start first, as the task has been marked for completion by the users in aisle B.

	# There is no picking available from aisle D at all, even if they start first, as the task in aisle D is to be completed by the users picking aisle A.		4 There is no picking available from aisle D at all, even if they start first, as the task in aisle D is to be completed by the users picking aisle A.
	# There is no picking available from aisle M at all, even if they start first, as the tasks in aisle M are to be completed by the users picking aisle A and B.		5 There is no picking available from aisle M at all, even if they start first, as the tasks in aisle M are to be completed by the users picking aisle A and B.
	# Picking in aisle Z will be:		6 Picking in aisle Z will be:

	* Order 1		* Order 1
Line 715:		Line 715:

	'''SCR-290107-10: Remove the Marshalling prompt from the RF Picking dialogue.'''		'''SCR-290107-10: Remove the Marshalling prompt from the RF Picking dialogue.'''


	=== Pick Exceptions ===		=== Pick Exceptions ===

Anw: /* Operational Information */

2011-07-15T07:55:51Z

Operational Information

← Older revision		Revision as of 09:55, 15 July 2011
Line 52:		Line 52:

	* MTO - Made to Order		* MTO - Made to Order
	* Stocked - Of-the-shelf products		* Stocked - Off-the-shelf products

	MTO items are expensive, manufactured on demand and shipped to the warehouse, for a specific customer order. This Buyer's Ref/Item Ref/Manufacturer's PO is stored in ''Calidus'' WMS as the Customer Rotation or Batch.		MTO items are expensive, manufactured on demand and shipped to the warehouse, for a specific customer order. This Buyer's Ref/Item Ref/Manufacturer's PO is stored in ''Calidus'' WMS as the Customer Rotation or Batch.
Line 95:		Line 95:

	OBS recommend the Motorola MC9000 series of units, although many other hardware makes and models are available and supported.		OBS recommend the Motorola MC9000 series of units, although many other hardware makes and models are available and supported.


	== Standard Processing ==		== Standard Processing ==

← Older revision		Revision as of 12:11, 15 July 2011
Line 3:		Line 3:
	{{#vardefine:System\|Calidus Mobile}}		{{#vardefine:System\|Calidus Mobile}}
	{{#vardefine:Doc_Title\|Nightfreight RF Requirements}}		{{#vardefine:Doc_Title\|Nightfreight RF Requirements}}
	{{#vardefine:Version\|0.4}}		{{#vardefine:Version\|1.0}}
	{{#vardefine:Date\|15th July 2011}}		{{#vardefine:Date\|15th July 2011}}
	{{#vardefine:Reference\|290107}}		{{#vardefine:Reference\|290107}}

← Older revision		Revision as of 10:18, 15 July 2011
Line 3:		Line 3:
	{{#vardefine:System\|Calidus Mobile}}		{{#vardefine:System\|Calidus Mobile}}
	{{#vardefine:Doc_Title\|Nightfreight RF Requirements}}		{{#vardefine:Doc_Title\|Nightfreight RF Requirements}}
	{{#vardefine:Version\|0.1}}		{{#vardefine:Version\|0.4}}
	{{#vardefine:Date\|~~8th~~ July 2011}}		{{#vardefine:Date\|15th July 2011}}
	{{#vardefine:Reference\|290107}}		{{#vardefine:Reference\|290107}}
	</div>		</div>