https://calidusassist.adcservices.apteancloud.com/calidus-assist/Portal/index.php?action=history&feed=atom&title=Template%3AREQTemplate:REQ - Revision history2026-05-08T15:53:27ZRevision history for this page on the wikiMediaWiki 1.39.8https://calidusassist.adcservices.apteancloud.com/calidus-assist/Portal/index.php?title=Template:REQ&diff=46&oldid=prevPortal owner: 1 revision2011-12-23T10:21:54Z<p>1 revision</p>
<table style="background-color: #fff; color: #202122;" data-mw="interface">
<tr class="diff-title" lang="en-GB">
<td colspan="1" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td>
<td colspan="1" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 12:21, 23 December 2011</td>
</tr><tr><td colspan="2" class="diff-notice" lang="en-GB"><div class="mw-diff-empty">(No difference)</div>
</td></tr></table>Portal ownerhttps://calidusassist.adcservices.apteancloud.com/calidus-assist/Portal/index.php?title=Template:REQ&diff=45&oldid=prevAnw at 14:12, 19 August 20112011-08-19T14:12:11Z<p></p>
<p><b>New page</b></p><div><div class="noprint"><br />
{{#vardefine:Client|The Supimix Client Code}}<br />
{{#vardefine:ClientName|The Client Name}}<br />
{{#vardefine:System|''CALIDUS'' Mobile/WMS/TMS}}<br />
{{#vardefine:Doc_Title|Description}}<br />
{{#vardefine:Version|0.1}}<br />
{{#vardefine:Date|16th June 2011}}<br />
{{#vardefine:Reference|Supimix References}}<br />
</div><br />
{{Doc_Title<br />
|Client={{#var:ClientName}}<br />
|System={{#var:System}}<br />
|Title={{#var:Doc_Title}}<br />
|Reference=FS {{#var:Reference}}<br />
|Version={{#var:Version}}<br />
|Date={{#var:Date}}<br />
}} <br />
<br />
<!-- TOC --> <br />
<div class="noprint"><br />
= Introduction =<br />
<!-- The introduction will detail the initial requirements supplied by the client --><br />
This document is the {{#var:Doc_Title}}.<br />
<br />
== Objective ==<br />
The primary purpose of this document is to document the requirements gathered from {{#var:ClientName}}, at X, Y, Z<br />
<br />
<!-- 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 --> <br />
<br />
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.<br />
<br />
== Scope and Limitations ==<br />
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}}.<br />
<br />
<!-- ANY scope or limitations, bulleted. --><br />
*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.<br />
<br />
<!-- NEW PAGE --> <br />
<br />
= Client Requirements =<br />
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. <br />
<br />
<The current operational process flow has been described in documents produced by X of Y.> <br />
<br />
<!-- Any standard processes should be referenced here and in the references section --><br />
<br />
== Operational Information ==<br />
<!-- Any general information about the operation (site, system, users, customers, limitations) should be listed here --><br />
<br />
== Standard Processing ==<br />
=== Process 1 ===<br />
<!-- Any overriding requirement here, such as warehouse/depot, labelling requirements, each as a sub-section. --><br />
<br />
== Functional Area 1 ==<br />
<!-- 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.<br />
A functional area isn’t ‘Warehousing’, it’s a sub-section of warehousing. For example, Receipt, Picking, Packing, etc.<br />
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.<br />
<br />
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. --><br />
<br />
== Functional Area 2 ==<br />
<br />
<br />
<!-- MEDIA LANDSCAPE YES --> <br />
<br />
= Appendix A: Table of SCRs and Ballpark Estimates =<br />
<!-- If there’s only one system being discussed here, the system column can be removed.<br />
Ballpark estimates may not be required to be included in this document. If they are, include the column, and note 1. Estimates should be rounded up, and should be produced using the standard mechanism of estimates (i.e. any standard spreadsheet designed to automate the production of estimates). The total line need only be added if the estimates are being produced at this point<br />
The description should be the description from the text in the main sections. <br />
The Notes column can be used for many things: grouping optional changes, showing whether the client or OBS originated the gap, etc. --><br />
<br />
{{ #vardefine: SCR | 0 }}<br />
{{REQ_SCR_Header}}<br />
{{REQ_SCR_Line<br />
|SCR={{ #vardefineecho: SCR | {{ #expr: {{ #var: SCR }} + 1 }} }}<br />
|System=System Affected<br />
|Area=Area Affected<br />
|Description=Description of change<br />
|Estimate=Cost<br />
|Notes=Any notes, numerically listed<br />
}}<br />
{{REQ_SCR_Footer}}<br />
<br />
Notes:<br />
#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.<br />
#<Further notes, referenced in the notes column of the grid above><br />
<br />
<!-- MEDIA LANDSCAPE NO --> <br />
{{Doc_Appendix<br />
|Appendix=B<br />
|Estimate=N<br />
|Glossary=WCS<br />
|Ref1=Reference1<br />
|RefV1=0.1<br />
|RefDate1=01/01/2011<br />
|REQ=0<br />
|EST=0<br />
|FS=0<br />
|TS=0<br />
|DEV=0<br />
|ST=0<br />
|IMP=0<br />
|Client=<br />
|Year=<br />
|FSEST=Y<br />
|Rev1=Rev1<br />
|Rev1Title=Rev1 Title<br />
}}</div> <br />
[[Category:{{#var:Client}} REQ]]</div>Anw