REQ 314432 Greene King ePOD Requirements - Revision history

Anw: Updated Aptean styling

2022-02-10T10:47:40Z

Updated Aptean styling

← Older revision		Revision as of 12:47, 10 February 2022
Line 9:		Line 9:
	{{#vardefine:Year\|2015}}		{{#vardefine:Year\|2015}}
	</div>		</div>
	{{~~Doc_Title~~		{{Doc_TitleNew
	\|Client={{#var:ClientName}}		\|Client={{#var:ClientName}}
	\|System={{#var:System}}		\|System={{#var:System}}
Line 17:		Line 17:
	\|Date={{#var:Date}}		\|Date={{#var:Date}}
	\|Year={{#var:Year}}		\|Year={{#var:Year}}
			\|Type=SDD
	}}		}}

Anw: v0.6 - Modifications after Aurora/WMS Interface meeting 26/02/2016

2016-03-01T15:26:20Z

v0.6 - Modifications after Aurora/WMS Interface meeting 26/02/2016

Show changes

Anw: v0.5 - Final review of included changes

2016-02-18T14:47:21Z

v0.5 - Final review of included changes

← Older revision		Revision as of 16:47, 18 February 2016
Line 4:		Line 4:
	{{#vardefine:System\|''CALIDUS'' ePOD}}		{{#vardefine:System\|''CALIDUS'' ePOD}}
	{{#vardefine:Doc_Title\|''CALIDUS'' ePOD/TTM Solution Design}}		{{#vardefine:Doc_Title\|''CALIDUS'' ePOD/TTM Solution Design}}
	{{#vardefine:Version\|0.4}}		{{#vardefine:Version\|0.5}}
	{{#vardefine:Date\|~~26th January~~ 2016}}		{{#vardefine:Date\|18th February 2016}}
	{{#vardefine:Reference\|314432}}		{{#vardefine:Reference\|314432}}
	{{#vardefine:Year\|2015}}		{{#vardefine:Year\|2015}}
Line 1,185:		Line 1,185:
	}}{{REQ_SCR_Line		}}{{REQ_SCR_Line
	\|SCR=2\|System=ePOD/Aurora\|Area=Integration\|Description=Aurora-ePOD Interface for Order and Product Details.\|Estimate=2.25\|Notes=		\|SCR=2\|System=ePOD/Aurora\|Area=Integration\|Description=Aurora-ePOD Interface for Order and Product Details.\|Estimate=2.25\|Notes=
	~~}}{{REQ_SCR_Line~~
	~~\|SCR=4\|System=ePOD\|Area=Look and Feel\|Description=Correctly identify Collection jobs from DiPS.\|Estimate=4.5\|Notes=~~
	}}{{REQ_SCR_Line		}}{{REQ_SCR_Line
	\|SCR=5\|System=ePOD\|Area=Look and Feel\|Description=Create customer-specific style on device. \|Estimate=0.5\|Notes=		\|SCR=5\|System=ePOD\|Area=Look and Feel\|Description=Create customer-specific style on device. \|Estimate=0.5\|Notes=
	}}{{REQ_SCR_Line		}}{{REQ_SCR_Line
	~~\|SCR=6\|System=ePOD\|Area=Job List\|Description=Alert pop-up for customer contact.\|Estimate=11.75\|Notes=~~		\|SCR=7\|System=ePOD/Portal\|Area=Tracking\|Description=Multiple Time Windows.\|Estimate=18.75\|Notes=2: Product Change
	~~}}{{REQ_SCR_Line~~
	\|SCR=7\|System=ePOD/Portal\|Area=Tracking\|Description=Multiple Time Windows.\|Estimate=18.75\|Notes=
	}}{{REQ_SCR_Line		}}{{REQ_SCR_Line
	\|SCR=8\|System=ePOD\|Area=Exception\|Description=Allow Over-Delivery/Collection of Product.\|Estimate=0\|Notes=2: Product Change		\|SCR=8\|System=ePOD\|Area=Exception\|Description=Allow Over-Delivery/Collection of Product.\|Estimate=0\|Notes=2: Product Change
Line 1,211:		Line 1,207:

	<!-- NEW PAGE -->		<!-- NEW PAGE -->
	== ~~Optional~~ Changes ==		== Additional Changes ==
	This section shows the changes that are not required to fulfil the primary goal of operating Home Fleet Secondary movements.		This section shows the changes that are not required to fulfil the primary goal of operating Home Fleet Secondary movements, or that are required because the external systems will/can not be changed to achieve necessary functionality.
	{{REQ_SCR_Header}}{{REQ_SCR_Line		{{REQ_SCR_Header}}{{REQ_SCR_Line
	\|SCR=3\|System=ePOD\|Area=Integration\|Description=Increase special instructions to 300 characters.\|Estimate=2.25\|Notes=1: Not Required		\|SCR=3\|System=ePOD\|Area=Integration\|Description=Increase special instructions to 300 characters.\|Estimate=2.25\|Notes=1: Not Required
			}}{{REQ_SCR_Line
			\|SCR=4\|System=ePOD\|Area=Look and Feel\|Description=Correctly identify Collection jobs from DiPS.\|Estimate=4.5\|Notes=
			}}{{REQ_SCR_Line
			\|SCR=6\|System=ePOD\|Area=Job List\|Description=Alert pop-up for customer contact.\|Estimate=11.75\|Notes=
	}}{{REQ_SCR_Line		}}{{REQ_SCR_Line
	\|SCR=9\|System=ePOD\|Area=Exception\|Description=Enforce Image Capture by Reason Code.\|Estimate=4.75\|Notes=2: Optional		\|SCR=9\|System=ePOD\|Area=Exception\|Description=Enforce Image Capture by Reason Code.\|Estimate=4.75\|Notes=2: Optional

Anw: v0.4 - Added Primary, Customer Collect, Store Sales and 3rd-party Carriers.

2016-01-26T15:58:51Z

v0.4 - Added Primary, Customer Collect, Store Sales and 3rd-party Carriers.

Show changes

Anw: v0.3 - Amended after meetings with the customer between 31/11/2015 and 14/12/2015

2015-12-24T13:41:58Z

v0.3 - Amended after meetings with the customer between 31/11/2015 and 14/12/2015

Show changes

Anw: v0.2 - Removed Vehicle Checks, added Time Windows, added return of items onto delivery

2015-11-27T10:28:55Z

v0.2 - Removed Vehicle Checks, added Time Windows, added return of items onto delivery

Show changes

Anw: Removed some non-required functionality

2015-11-25T15:57:28Z

Removed some non-required functionality

← Older revision		Revision as of 17:57, 25 November 2015
Line 603:		Line 603:

	The Terms and Conditions are configurable, but will appear in the same place on the screen (under the signature). Unlimited T&Cs text can be configured, along with check-boxes and data entry. This may be configured at any time.		The Terms and Conditions are configurable, but will appear in the same place on the screen (under the signature). Unlimited T&Cs text can be configured, along with check-boxes and data entry. This may be configured at any time.

	~~It is expected that this process will be modified to allow the user to confirm the email of the contact for POD purposes. To achieve this, the Email will be added to the Terms and Conditions tab.~~


Line 631:		Line 629:


	The device will prompt the driver after all planned deliveries and collections for a customer are complete, asking whether an unplanned collection is required at this location. If the driver confirms this, the device will generate an unplanned collection and this can be used to add returned packaging, as described above.		The device will prompt the driver after all planned deliveries and collections for a customer are complete, asking whether an unplanned collection is required at this location. If the driver confirms this, the device will generate an unplanned collection and this can be used to add returned packaging, as described above. Note that the last location visited can be used to create an unplanned collection at any time, from the Job List menu.


Line 868:		Line 866:
	[[file:REQ_324746_TTM_GPSTrack.PNG\|border\|600px]]		[[file:REQ_324746_TTM_GPSTrack.PNG\|border\|600px]]
	<br />''GPS Tracking Parameters''<br />		<br />''GPS Tracking Parameters''<br />

	[[file:REQ_324746_TTM_GPSTrackResults.PNG\|border\|600px]]		[[file:REQ_324746_TTM_GPSTrackResults.PNG\|border\|600px]]
	<br />''GPS Tracking Results''<br />		<br />''GPS Tracking Results''<br />

	[[file:REQ_324746_TTM_GPSTrackMap.PNG\|border\|600px]]		[[file:REQ_324746_TTM_GPSTrackMap.PNG\|border\|600px]]
	<br />''GPS Tracking Map''<br />		<br />''GPS Tracking Map''<br />


	=== Tracking Emails ===		=== Tracking Emails ===

Anw: Minor formatting corrections

2015-11-25T15:22:56Z

Minor formatting corrections

Anw: v0.1 - Initial draft.

2015-11-25T15:17:22Z

v0.1 - Initial draft.

Show changes

← Older revision		Revision as of 17:22, 25 November 2015
Line 838:		Line 838:

	Details can be found of the following:		Details can be found of the following:
	* Events – the messages received by the LOTS system via WMS, TMS and other systems.		* Events - the messages received by the LOTS system via WMS, TMS and other systems.
	* Info – Details of all of the header information stored on the system		* Info - Details of all of the header information stored on the system
	* Route – Details of the trips/stops that the order is currently assigned to.		* Route - Details of the trips/stops that the order is currently assigned to.
	* SO Details – the Stock details received from the TMS or WMS.		* SO Details - the Stock details received from the TMS or WMS.
	* Reasons – Details of the Order level reasons placed against the order.		* Reasons - Details of the Order level reasons placed against the order.
	* Map – A map of the current location of the order (if co-ordinates have been supplied by an external system). The Mapping page will only be available to groups where the ~~‘Mapping’~~ parameter against the User Group is set to ~~‘Available’~~ and where licensing is available.		* Map - A map of the current location of the order (if co-ordinates have been supplied by an external system). The Mapping page will only be available to groups where the 'Mapping' parameter against the User Group is set to 'Available' and where licensing is available.
	* Notes – Allows the entry of user notes against the order. These are only kept on the Portal system.		* Notes - Allows the entry of user notes against the order. These are only kept on the Portal system.


Line 938:		Line 938:
	If the order being checked is out for delivery, the screen displays a map showing:		If the order being checked is out for delivery, the screen displays a map showing:
	* The last known location of the vehicle making the delivery.		* The last known location of the vehicle making the delivery.
	* The ~~customer’s~~ delivery location		* The customer's delivery location
	{{Note}} The last known location of the vehicle making the delivery could be the address of another customer receiving a delivery on that trip. However, no address information or labels are shown against the locations displayed in the map and no information is divulged regarding the reason the vehicle is currently at that location.		{{Note}} The last known location of the vehicle making the delivery could be the address of another customer receiving a delivery on that trip. However, no address information or labels are shown against the locations displayed in the map and no information is divulged regarding the reason the vehicle is currently at that location.

Line 954:		Line 954:

	= Appendix A: Table of SCRs and Ballpark Estimates =		= Appendix A: Table of SCRs and Ballpark Estimates =
	<!-- If ~~there’s~~ only one system being discussed here, the system column can be removed.		<!-- If there's only one system being discussed here, the system column can be removed.
	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		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
	The description should be the description from the text in the main sections.		The description should be the description from the text in the main sections.