TEST: Difference between revisions

From Calidus HUB
VisualWikitext
No edit summary
No edit summary
Line 21: Line 21:
<!-- TOC -->  
<!-- TOC -->  
<div class="noprint">
<div class="noprint">
=Requirements=
= Introduction  =
<!-- The introduction will detail the initial requirements supplied by the client -->
This document is the {{#var:Doc_Title}}.
 
 
== Objective  ==
The primary purpose of this document is to document the requirements gathered from {{#var:ClientName}}, at the following meetings:
* Initial meeting in Swindon - Demo provided with website data.
* Second meeting at Customer reference site (Brett Martin).
* Third meeting - Pre-Sales Workshop with detailed demo
* The document has been amended with feedback from the customer, culminating in a review meeting on 05/07/2017.
 
 
<!-- 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:ClientName}} 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 {{#var:ClientName}}, as well as information gleaned from site visits and workshops with {{#var:ClientName}}.
 
<!-- ANY scope or limitations, bulleted. -->
* The changes will be made in the latest version of the {{#var:System}} system, operating the Android version of the C-ePOD Client application.
* Changes relating to information passed through to {{#var:System}} from external systems (i.e. WMS/ERP) are subject to analysis and design, which may affect the other changes in this document or generate other work if the process described within this document cannot be followed by the external system.
* Modifications are required to the customer systems (WMS/ERP) to achieve the functionality described in this document.
* This document specifies changes for Lot Capture. It must be noted that this is ''not'' functionality for Lot Traceability, just the capture of the Lot numbers, to be passed back to the customer's WMS/ERP on Radial Deliveries only. None of the OBS systems included in this implementation will display or search for the captured Lot numbers.
* This document specifies Loading and Unloading being performed by warehouse staff, not the drivers. It must be noted that ''CALIDUS'' ePOD is not a replacement for an RF-enabled Warehouse Management/Control system. Existing functionality and creative load building within the customer's systems is being used so that C-ePOD may be used for this purpose, but this is not the primary purpose of the application.
* For Lot traceability, it would normally be expected that this be captured by the WMS/ERP and a unique item label produced for that order, identifying the Lot and Product implicitly. An item label has now been provided as part of the process, but this is not linked to the Lot number by the customer's systems.
 
<!-- ANY other systems? e.g. does this link to TTM, WMS, 414, 770, etc? -->
{{ #vardefine: SCR | 0 }}
<!-- NEW PAGE -->
 
= Client Requirements =
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.
 
 
 
 
 


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

Revision as of 18:11, 2 January 2019





Aptean Logo.png







JB Global

JB Global POD Note Changes

CALIDUS ePOD

21st December 2018 - 0.1
Reference: REQ 354567











































Introduction

This document is the JB Global POD Note Changes.


Objective

The primary purpose of this document is to document the requirements gathered from JB Global, at the following meetings:

  • Initial meeting in Swindon - Demo provided with website data.
  • Second meeting at Customer reference site (Brett Martin).
  • Third meeting - Pre-Sales Workshop with detailed demo
  • The document has been amended with feedback from the customer, culminating in a review meeting on 05/07/2017.


This document has been written in a manner such that it can be approved by non-technical representatives of JB Global 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 JB Global, as well as information gleaned from site visits and workshops with JB Global.

  • The changes will be made in the latest version of the CALIDUS ePOD system, operating the Android version of the C-ePOD Client application.
  • Changes relating to information passed through to CALIDUS ePOD from external systems (i.e. WMS/ERP) are subject to analysis and design, which may affect the other changes in this document or generate other work if the process described within this document cannot be followed by the external system.
  • Modifications are required to the customer systems (WMS/ERP) to achieve the functionality described in this document.
  • This document specifies changes for Lot Capture. It must be noted that this is not functionality for Lot Traceability, just the capture of the Lot numbers, to be passed back to the customer's WMS/ERP on Radial Deliveries only. None of the OBS systems included in this implementation will display or search for the captured Lot numbers.
  • This document specifies Loading and Unloading being performed by warehouse staff, not the drivers. It must be noted that CALIDUS ePOD is not a replacement for an RF-enabled Warehouse Management/Control system. Existing functionality and creative load building within the customer's systems is being used so that C-ePOD may be used for this purpose, but this is not the primary purpose of the application.
  • For Lot traceability, it would normally be expected that this be captured by the WMS/ERP and a unique item label produced for that order, identifying the Lot and Product implicitly. An item label has now been provided as part of the process, but this is not linked to the Lot number by the customer's systems.


Client Requirements

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




Appendix A: Document References

A.1 References

Ref NoDocument Title & IDVersionDate
1   


A.2 Glossary

Term Definition
EPOD Electronic Proof of Delivery. The OBS EPOD system is CALIDUS ePOD.
CALIDUS eSERV The OBS mobile system to complete Service functionality in the field. This is part of the CALIDUS ePOD system.
PDA The mobile device on which the C-ePOD system will run in the field. This can be a Phone, EDA or industrial PDA, running Android.
DAL Data Access Layer. A mechanism for accessing data by the system that is removed from the application, allowing for simplified access and providing protection to the data, as only approved DAL methods can be used to modify it.
GPS Global Positioning System. A mechanism of retrieving accurate positioning information in the form of Latitude and Longitude (Lat-Long) co-ordinates from a device.
GPRS, 3G, HSDPA, Data Service All terms referring to mobile device network connectivity, and the speed at which the device connects to the internet.


A.3 Authorised By


Barry Preece
OBS Project Manager		_____________________________
Retrieved from ‘https://calidusassist.adcservices.apteancloud.com/calidus-assist/OBS/index.php?title=TEST&oldid=6804’