Template:REQ: Difference between revisions

From Calidus HUB
VisualWikitext
No edit summary
m (Categorisation of document pages)
 
(6 intermediate revisions by the same user not shown)
Line 1: Line 1:
<div class="noprint">
<div class="noprint">
{{#vardefine:Client|The Client}}
{{#vardefine:Client|The Supimix Client Code}}
{{#vardefine:System|Calidus Mobile/WMS/TMS}}
{{#vardefine:ClientName|The Client Name}}
{{#vardefine:System|''CALIDUS'' Mobile/WMS/TMS/ePOD}}
{{#vardefine:SystemCode|WCS/WMS/TMS/EPOD/MCS/Portal}}
{{#vardefine:Doc_Title|Description}}
{{#vardefine:Doc_Title|Description}}
{{#vardefine:Version|0.1}}
{{#vardefine:Version|0.1}}
{{#vardefine:Date|16th June 2011}}
{{#vardefine:Date|16th June 2011}}
{{#vardefine:Reference|Supimix References}}
{{#vardefine:Reference|Supimix References}}
{{#vardefine:Year|Year}}
</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}}
|Reference=FS {{#var:Reference}}
|Reference=REQ {{#var:Reference}}
|Version={{#var:Version}}
|Version={{#var:Version}}
|Date={{#var:Date}}
|Date={{#var:Date}}
|Year={{#var:Year}}
}}  
}}  


Line 23: Line 27:


== Objective  ==
== Objective  ==
The primary purpose of this document is to document the requirements gathered from {{#var:Client}}, at X, Y, Z
The primary purpose of this document is to document the requirements gathered from {{#var:ClientName}}, at X, Y, Z


<!-- 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 site visits and 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 site visits and workshops with {{#var:ClientName}}.


<!-- 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 4.14 of the Calidus 3pl system.
*The changes will be made in the latest version of the {{#var:System}} system.
 
<!-- ANY other systems? e.g. does this link to TTM, WMS, 414, 770, etc? -->
{{ #vardefine: SCR | 0 }}
<!-- NEW PAGE -->  
<!-- NEW PAGE -->  


= Client Requirements =
= Client Requirements =
Listed below are the proposed processes that will be followed by the warehouse operatives using Calidus 3pl-Mobile. Also shown are the SCRs required for this to be achieved.  
Listed below are the proposed processes that will be followed by the operatives using {{#var:System}}. Also shown are the SCRs required for this to be achieved.  


<The current operational process flow has been described in documents produced by X of Y.>  
<The current operational process flow has been described in documents produced by X of Y.>  
Line 54: Line 59:
<!-- A description of the operational flow for this functional area, as it will be. Reference any operational flow documents produced for the way it is now.
<!-- A description of the operational flow for this functional area, as it will be. Reference any operational flow documents produced for the way it is now.
A functional area isn’t ‘Warehousing’, it’s a sub-section of warehousing. For example, Receipt, Picking, Packing, etc.
A functional area isn’t ‘Warehousing’, it’s a sub-section of warehousing. For example, Receipt, Picking, Packing, etc.
It is important to keep the flow of the text, so that it can be easily understood. So, if an SCR has been identified, reference the SCR here, in bold. Keep the description snappy. Also, include a cross-reference to the SCR numbers in the table at the end of the document, and include the supimix number from the Reference Docproperty. When you identify a gap, put the text ‘SCR :’ in bold in front of it. Then, add the line in the table in appendix A.
It is important to keep the flow of the text, so that it can be easily understood. So, if an SCR has been identified, reference the SCR here, in bold. Keep the description snappy. Also, include a cross-reference to the SCR numbers in the table at the end of the document, and include the supimix number from the Reference Docproperty. When you identify a gap, use the template 'SCR' as follows:
 
{{SCR
|Reference={{#var:Reference}}
|SCRNo={{ #vardefineecho: SCR | {{ #expr: {{ #var: SCR }} + 1 }} }}
|Definition=The description of the change required
}}
Then, add the line in the table in appendix A with:
{{REQ_SCR_Line
|SCR={{ #vardefineecho: SCR | {{ #expr: {{ #var: SCR }} + 1 }} }}
|System=System Affected
|Area=Area Affected
|Description=Description of change
|Estimate=Cost
|Notes=Any notes, numerically listed
}}
There may be many SCRs for each section. Keep numbering and referencing them. Keep the table in Appendix A updated as you go along. If you re-order the SCR’s in the table, or insert new ones, don’t forget to update the document references. -->
There may be many SCRs for each section. Keep numbering and referencing them. Keep the table in Appendix A updated as you go along. If you re-order the SCR’s in the table, or insert new ones, don’t forget to update the document references. -->


Line 106: Line 124:
|Rev1Title=Rev1 Title
|Rev1Title=Rev1 Title
}}</div>  
}}</div>  
[[Category:Test]]
[[Category:{{#var:Client}} REQ]]
[[Category:{{#var:SystemCode}}]]

Latest revision as of 11:48, 29 November 2019





Aptean Logo.png







The Client Name

Description

CALIDUS Mobile/WMS/TMS/ePOD

16th June 2011 - 0.1
Reference: REQ Supimix References











































Introduction

This document is the Description.

Objective

The primary purpose of this document is to document the requirements gathered from The Client Name, at X, Y, Z


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

Scope and Limitations

This document is based on the documentation provided by The Client Name, as referred to in the appendices, as well as information gleaned from site visits and workshops with The Client Name.

  • The changes will be made in the latest version of the CALIDUS Mobile/WMS/TMS/ePOD system.


Client Requirements

Listed below are the proposed processes that will be followed by the operatives using CALIDUS Mobile/WMS/TMS/ePOD. Also shown are the SCRs required for this to be achieved.

<The current operational process flow has been described in documents produced by X of Y.>


Operational Information

Standard Processing

Process 1

Functional Area 1

Functional Area 2

Appendix A: Table of SCRs and Ballpark Estimates

SCR#SystemAreaDescriptionEstimate (Days)Notes
1 System Affected Area Affected Description of change  First argument to "number_format" must be a number.  Any notes, numerically listed


Notes:

  1. Any high level ballpark estimates for development are based on the basic information provided and are subject to detailed design and creation of an SCR.
  2. <Further notes, referenced in the notes column of the grid above>


Appendix B: Document References

B.1 References

Ref NoDocument Title & IDVersionDate
1Reference10.101/01/2011


B.2 Glossary

Term or Acronym Meaning
Ad Hoc A task instigated on the device (spec. Ad Hoc Pallet Move), rather than a task instigated from the WMS and Stock Control.
Advice Note Number An external reference linked to a Goods Receipt.
Aisle A component of a location; usually a space through rows of racking or storage locations; a collection of locations;
Anchor Point A starting location for a search for a suitable storage location; auto-putaway location suggestion start point.
Area A collection of aisles; an area in the warehouse for a particular purpose.
Batch A production batch of a product; a quantity of product that is considered to have the same characteristics;
Bay (Warehouse) A physical loading or unloading point for the warehouse.
Bay A component of a location; usually a space between uprights in racking, comprising several levels (horizontal beams).
Block Stack A stable stack of pallets.
Bulk Bulk storage; Usually full-pallet storage areas, racked or stacked.
Cancellation The facility to cancel a task due to some problem, identified by the user when performing the task.
Check Digit A short code, usually randomly generated and stored against a location, used to help identify that a user is at the right location before they proceed with a warehouse task.
CSV Character-separated values; a text file with multiple rows and values, usually separated with commas.
C-WCS CALIDUS WCS, the name of the OBS Logistics Warehouse Control system
C-WMS CALIDUS WMS, the name of the OBS Logistics Warehouse Management system
Dead Leg A movement of a truck without a pallet; wasted resource.
Despatch The final physical stage of an order; handover of goods to the haulier.
Drive-In A drive-in location, typically multi-level, multi-deep location.
Dual Cycling Processes utilizing P&D locations for interleaving tasks in and out of specific areas, reducing dead leg movements.
Exchange Specifically Pick Exchange or Task Exchange. The process of allowing a user to select a different pallet in a multi-pallet location and exchanging the expected pallet for this one. If the pallet is planned for another task, task exchange will complete this task instead of the expected one first. If the pallet is not planned, pallet exchange will swap the pallet (if suitable).
GR; GRN Goods Receipt; Goods Receipt Number or Note
High Bay Typically tall (greater than 5 level) racking, usually full pallet storage, usually Narrow Aisle.
JIT Just In Time; processes designed to trigger at the last instant.
KPI Key Performance Indicator.
Level A component of a location; usually the vertical compartments of an area, delineated by horizontal beams.
Loading The act of loading pallets onto a vehicle.
Location A uniquely identified space in the warehouse for storage of product. There are many types, most commonly Floor locations (for example, Marshalling, Inbound), Racking or Bulk Storage Locations and Pick faces.
Manifest The contents of a vehicle or container.
Marshalling The act of bringing pallets for an order or load together; an area to do so.
Multi-deep A location with 2 or more pallets stored sequentially i.e. only one can be accessed at a time.
NA Narrow Aisle; usually any area in the warehouse that is restricted access due to space limitations, Narrow Aisles have associate P&D locations.
P&D Pick-up and Drop-off locations; locations used to control the handover of pallets between distinct areas, for example between chambers and the wider area of the warehouse.
PI; Perpetual Inventory The act of continuously checking locations in a warehouse, identifying and correcting product quantity issues. Usually used in Bulk environments rather than Pick Faces. In pick faces, this process is called is called Residual Stock Balance and usually takes place after picking from a pick face.
Pick Face A location designed for picking part of a pallet of stock. Usually a low- or ground-level location.
Pick List (order) The instructions to pick pallets or cases from locations; the paper report associated to this; the stage of preparing these instructions; the sending of these instructions to WCS.
PO Purchase Order.
Pre-advice; Goods Receipt Pre-advice An advanced notification of what is being received. Part of a manifest. Pre-advices can be stock and quantity, or individual pallet level.
Putaway The physical move of a pallet to a storage location as a result of receiving it into the warehouse.
RAG Acronym for Red/Amber/Green, a traffic light colouration system depicting (in sequence) Errors, Warnings or Informational messages. Usually used in operational monitoring to effectively display when certain processes are not working as expected.
RDT Radio Data Terminal.
Replen; Replenishment The act of moving product (usually a pallet) from bulk storage to a pick face.
Reposition The facility to change the location of a movement or putaway when at the final destination, sue to some issue discovered when performing the task.
RF Radio Frequency; An RF device is an RDT, typically used by CALIDUS WCS for executing warehouse tasks.
SCR; CR Software Change Request.
Short Pick The process of not fulfilling an order due to failure to identify sufficient product when picking. May also be used as a term to indicate Short Allocation.
SO Sales Order.
Truck Types Plants, Mechanical Handling Equipment. For example, Reach trucks, Counter-balance trucks, pallet riders, etc.
UOM Unit of Measure.
WA Wide Area; usually any area in the warehouse that is not restricted access due to space limitations, for example, floor areas, not Narrow Aisle.
WCS Warehouse Control System
WMS Warehouse Management System


B.3 Authorised By


Rev1
Rev1 Title		_____________________________
Retrieved from ‘https://calidusassist.adcservices.apteancloud.com/calidus-assist/OBS/index.php?title=Template:REQ&oldid=8165’