FS 281363 New CTMS Execution Screen - Revision history

Anw at 10:07, 26 October 2011

2011-10-26T10:07:08Z

← Older revision		Revision as of 12:07, 26 October 2011
Line 335:		Line 335:

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

	{{Doc_Appendix		{{Doc_Appendix
	\|Appendix=A		\|Appendix=A

Anw: v0.2 Incorporated futher changes from One Network review with ES and PC

2011-10-26T08:51:17Z

v0.2 Incorporated futher changes from One Network review with ES and PC

← Older revision		Revision as of 10:51, 26 October 2011
Line 4:		Line 4:
	{{#vardefine:System\|''CALIDUS'' C-TMS}}		{{#vardefine:System\|''CALIDUS'' C-TMS}}
	{{#vardefine:Doc_Title\|New C-TMS Execution Screen}}		{{#vardefine:Doc_Title\|New C-TMS Execution Screen}}
	{{#vardefine:Version\|0.1}}		{{#vardefine:Version\|0.2}}
	{{#vardefine:Date\|~~25th~~ October 2011}}		{{#vardefine:Date\|26th October 2011}}
	{{#vardefine:Reference\|281363}}		{{#vardefine:Reference\|281363}}
	</div>		</div>

Anw: /* Scope */

2011-10-26T08:49:25Z

Scope

← Older revision		Revision as of 10:49, 26 October 2011
Line 42:		Line 42:
	== Scope ==		== Scope ==
	This is a prototype, showing the capability. There is a simplified database in use in the back-end, with demonstration data. It is unlikely that updating data will be required but, where possible, the prototype will incorporate this.		This is a prototype, showing the capability. There is a simplified database in use in the back-end, with demonstration data. It is unlikely that updating data will be required but, where possible, the prototype will incorporate this.


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

Anw at 08:48, 26 October 2011

2011-10-26T08:48:25Z

Show changes

Anw at 12:07, 25 October 2011

2011-10-25T12:07:52Z

← Older revision		Revision as of 14:07, 25 October 2011
Line 72:		Line 72:

	If change to next status, check that the General information has been entered – if not, popup validation forcing entry as below.		If change to next status, check that the General information has been entered – if not, popup validation forcing entry as below.

			In all tabs, when changing to next status, write Audit log entry and link to appropriate levels. See auditing later for details.

			At this stage, write an audit entry and link to Trip, Tractor, Driver.

	Accordion panel, general is displayed.		Accordion panel, general is displayed.
Line 102:		Line 106:
	*Cust Ref		*Cust Ref
	*Planned qty, weight and Volume		*Planned qty, weight and Volume
	*Load Number		*Load Number (a link to a Load screen - see later)
	All display only		All display only

Line 121:		Line 125:
	==Accepted==		==Accepted==
	Entry button to show status of trip, allowing change to next status only.		Entry button to show status of trip, allowing change to next status only.
			At this stage, write an audit entry and link to Trip, Driver.

	If change to next status, check that the Driver Brief and Despatched Quantities information has been entered – if not, popup validation forcing entry as below (automatically switching between tabs/accordions as necessary.		If change to next status, check that the Driver Brief and Despatched Quantities information has been entered – if not, popup validation forcing entry as below (automatically switching between tabs/accordions as necessary.
Line 156:		Line 161:

	Button under despatched quantities to allow all to be set to planned quantities (if not already entered).		Button under despatched quantities to allow all to be set to planned quantities (if not already entered).

			Save button.

	Panel (not part of accordion) with Grid of Stops under tab panel as above.		Panel (not part of accordion) with Grid of Stops under tab panel as above.
Line 164:		Line 171:
	History link will be available from this point, to call a separate screen with the Trip ID as a parameter.		History link will be available from this point, to call a separate screen with the Trip ID as a parameter.

			If change to next status, check that the Order Quantities and Trip Times have all been been entered – if not, popup validation forcing entry as below.

	~~If change to next status~~, ~~check that the Order Quantities~~ and Trip ~~Times have all been been entered – if not~~, ~~popup validation forcing entry as below~~.		At this stage, write an audit entry and link to Trip, Tractor, Driver.

	Accordion display		Accordion display
Line 179:		Line 187:

	Can add records at any time for any type.		Can add records at any time for any type.
			At this stage, write an audit entry and link to Trip, Tractor, Driver.

	Second accordion panel (open) with ability to see order details grid as above, plus Delivered quantities:		Second accordion panel (open) with ability to see order details grid as above, plus Delivered quantities:
Line 200:		Line 209:

	Once first entered, can save - that's OK.		Once first entered, can save - that's OK.
			At this stage, write an audit entry and link to Trip, Tractor, Driver.


			Can then continue entering against the following stops one by one.

	Button under Actual Dates/Times to set to Planned (if not already set)		Button under Actual Dates/Times to set to Planned (if not already set)
Line 207:		Line 220:
	==Completed==		==Completed==
	Entry button to show status of trip, allowing change to next status only.		Entry button to show status of trip, allowing change to next status only.

			History link will be available from this point, to call a separate screen with the Trip ID as a parameter.

	If change to next status, check that the Driver Debrief information has been entered – if not, popup validation forcing entry as below (automatically switching between tabs/accordions/popups as necessary.		If change to next status, check that the Driver Debrief information has been entered – if not, popup validation forcing entry as below (automatically switching between tabs/accordions/popups as necessary.
			At this stage, write an audit entry and link to Trip, Driver.

	Accordion display		Accordion display
Line 238:		Line 254:

	Entry button to show status of trip, allowing change to next status only.		Entry button to show status of trip, allowing change to next status only.

			History link will be available from this point, to call a separate screen with the Trip ID as a parameter.

	If change to next status, check that the POD information has been entered – if not, popup validation forcing entry as below (automatically switching between tabs/accordions/popups as necessary.		If change to next status, check that the POD information has been entered – if not, popup validation forcing entry as below (automatically switching between tabs/accordions/popups as necessary.
			At this stage, write an audit entry and link to Trip.

	Accordion display		Accordion display
Line 249:		Line 268:
	==Confirmed==		==Confirmed==

			History link will be available from this point, to call a separate screen with the Trip ID as a parameter.
	~~Entry button to show status of trip~~, ~~allowing change~~ to ~~next status only.~~

	~~If change to next status, confirm if no payment information entered~~.

	Accordion display		Accordion display
Line 260:		Line 276:

	Trips panel closed as part of the accordion.		Trips panel closed as part of the accordion.

			=Audit Screen=
			Audit records are written at one of three levels (Trip, Tractor, Driver) at various stages in the process above.
			This screen reports on them.

			Screen accepts parameters of Trip, Trailer or Driver.

			For Trip - display all records found.
			Any others, limit to 20 to a page.

			For Trip, get Audit Type records of Trip for the supplied Trip ID.
			For Tractor, get Audit Type records of Tractor for the supplied Tractor ID
			For Driver, get Audit Type records of Trip for the supplied Driver.

			The page should display the information in the audit record, plus links for whatever other levels this audit record links to.

			So, we have the following:

			Audit 1, with information "Driver Briefed" is linked to the Trip ID and the Driver ID

			Audit 2, with information "Trip En-Route" is linked to the Trip ID, Tractor ID and Trailer ID.

			etc.

			If we search for the Trip ID, we will return both audit records.

			If we search for the Tractor ID, we will get only audit 2.

			If the user clicks a link against an audit, call the same screen with the new parameter.

			=Load Screen=
			This screen shows all orders associated to the load ID passed in.

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

Anw: /* En Route */

2011-10-25T11:49:13Z

En Route

← Older revision		Revision as of 13:49, 25 October 2011
Line 161:		Line 161:
	==En Route==		==En Route==
	Entry button to show status of trip, allowing change to next status only.		Entry button to show status of trip, allowing change to next status only.

			History link will be available from this point, to call a separate screen with the Trip ID as a parameter.


	If change to next status, check that the Order Quantities and Trip Times have all been been entered – if not, popup validation forcing entry as below.		If change to next status, check that the Order Quantities and Trip Times have all been been entered – if not, popup validation forcing entry as below.

Anw: /* Solution Overview */

2011-10-25T11:47:46Z

Solution Overview

← Older revision		Revision as of 13:47, 25 October 2011
Line 37:		Line 37:

	An increased auditing level will be added, as well as Load ID visibility, to allow users to see how the new functionality would integrate into the existing process.		An increased auditing level will be added, as well as Load ID visibility, to allow users to see how the new functionality would integrate into the existing process.

			The styling of the product will approach DHL standards and colour schemes, to show the styling capability of the new product UI.

	== Scope ==		== Scope ==

Anw: /* Functional Overview */

2011-10-25T11:46:36Z

Functional Overview

← Older revision		Revision as of 13:46, 25 October 2011
Line 22:		Line 22:

	== Client Requirement ==		== Client Requirement ==
			A new UI for a new Drivers Execution screen. Functionality required has been agreed between Tony Walker and Pete Crane, working from the One Network requirements document.

	== Solution Overview ==		== Solution Overview ==
			A new Execution screen will be created.

			The screen will allow all of the functionality of the existing Trip Debrief screen, plus modifications to allow for:
			*Extended ODO entry
			*Driver Briefing
			*Driver Exception Handling

			The screen will be optimised for each trip status, showing the user the necessary data entries for each step, depending on the status of the order.

			Extensive use of popups will be used to ensure that the entry of the data is a seamless as possible, directing the user to enter the data in as close a way to the operational requirement as possible.

			An increased auditing level will be added, as well as Load ID visibility, to allow users to see how the new functionality would integrate into the existing process.

	== Scope ==		== Scope ==
			This is a prototype, showing the capability. There is a simplified database in use in the back-end, with demonstration data. It is unlikely that updating data will be required but, where possible, the prototype will incorporate this.


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

	= Set-up =		= Set-up =

Anw: v0.1 - draft version for review

2011-10-25T11:38:58Z

v0.1 - draft version for review

@@ Line 105: / Line 105: @@
 Entry button to show status of trip, allowing change to next status only.
-If change to next status, check that the Driver Brief and Despatched Quantities information has been entered – if not, popup validation forcing entry as below (automatically switching between tabs as necessary.
+If change to next status, check that the Driver Brief and Despatched Quantities information has been entered – if not, popup validation forcing entry as below (automatically switching between tabs/accordions as necessary.
 Accordion display
@@ Line 148: / Line 148: @@
 Accordion display
-First accordion panel (closed), two tabs, General, Driver Brief (from above) then:
+First accordion panel (closed), three tabs, General, Driver Brief (from above) then:
 Second accordion panel (open) with ability to see order details grid as above, plus Delivered quantities:
@@ Line 168: / Line 178: @@
 On entry of first stop's actual arrival/depart date and time, check whether delivered quantities entered for all orders to that stop. If not, pop open an entry grid for the orders only, forcing entry of quantities. When entered, update orders panel above.
 When all quantities and dates entered, prompt user whether they want to change status to Completed.
-==Delivered==
+==Completed==
 <!-- NEW PAGE -->

Anw at 11:11, 25 October 2011

2011-10-25T11:11:37Z

@@ Line 105: / Line 105: @@
 Entry button to show status of trip, allowing change to next status only.
-If change to next status, check that the Driver Brief information has been entered – if not, popup validation forcing entry as below.
+If change to next status, check that the Driver Brief and Despatched Quantities information has been entered – if not, popup validation forcing entry as below (automatically switching between tabs as necessary.
 Accordion display
@@ Line 127: / Line 127: @@
 Saving this will prompt the user to change the status to En Route.

← Older revision		Revision as of 10:51, 26 October 2011
Line 4:		Line 4:
	{{#vardefine:System\|''CALIDUS'' C-TMS}}		{{#vardefine:System\|''CALIDUS'' C-TMS}}
	{{#vardefine:Doc_Title\|New C-TMS Execution Screen}}		{{#vardefine:Doc_Title\|New C-TMS Execution Screen}}
	{{#vardefine:Version\|0.1}}		{{#vardefine:Version\|0.2}}
	{{#vardefine:Date\|~~25th~~ October 2011}}		{{#vardefine:Date\|26th October 2011}}
	{{#vardefine:Reference\|281363}}		{{#vardefine:Reference\|281363}}
	</div>		</div>