UG 281363 New CTMS Execution Screen - Revision history

Anw: /* Planned */

2011-11-02T15:41:45Z

Planned

← Older revision		Revision as of 17:41, 2 November 2011
Line 129:		Line 129:
	Optionally, the user may enter and view Crew and Instructions information, by clicking on the appropriate button. These are entered and validated through a Modal pop-up screen, allowing dragging of the panels.		Optionally, the user may enter and view Crew and Instructions information, by clicking on the appropriate button. These are entered and validated through a Modal pop-up screen, allowing dragging of the panels.

	[[File:CTMS-UI-2.png\|border\|600px]]		[[File:CTMS-UI-2a.png\|border\|600px]]

	When a driver and vehicle have been entered, the user will be prompted to change the status to Accepted if required.		When a driver and vehicle have been entered, the user will be prompted to change the status to Accepted if required.

Anw: /* En Route */

2011-11-02T15:26:58Z

En Route

← Older revision		Revision as of 17:26, 2 November 2011
Line 177:		Line 177:
	The Actual Dates and Times can be from planned using the Planned button. Additionally, each stop can be edited or set from planned using the Hover Menu against each grid line. Editing a line will show a pop-up window with the information to enter, and a reason code if required. If orders are being delivered against the stop, a pop-up entry window will be shown to enter the delivered quantities against each order delivered.		The Actual Dates and Times can be from planned using the Planned button. Additionally, each stop can be edited or set from planned using the Hover Menu against each grid line. Editing a line will show a pop-up window with the information to enter, and a reason code if required. If orders are being delivered against the stop, a pop-up entry window will be shown to enter the delivered quantities against each order delivered.

	[[File:CTMS-UI-4.png\|border\|600px]]		[[File:CTMS-UI-4a.png\|border\|600px]]

	ETA dates and times are forecast from outside the CTMS system. If they are available, the screen will display these with RAG-colouration:		ETA dates and times are forecast from outside the CTMS system. If they are available, the screen will display these with RAG-colouration:

Anw at 15:03, 2 November 2011

2011-11-02T15:03:12Z

← Older revision		Revision as of 17:03, 2 November 2011
Line 1:		Line 1:
			__NOTOC__
	== Solution Overview ==		== Solution Overview ==
	A new Execution screen will be created.		A new Execution screen will be created.

Anw at 14:58, 2 November 2011

2011-11-02T14:58:36Z

← Older revision		Revision as of 16:58, 2 November 2011
Line 128:		Line 128:
	Optionally, the user may enter and view Crew and Instructions information, by clicking on the appropriate button. These are entered and validated through a Modal pop-up screen, allowing dragging of the panels.		Optionally, the user may enter and view Crew and Instructions information, by clicking on the appropriate button. These are entered and validated through a Modal pop-up screen, allowing dragging of the panels.

	[[File:~~CMTS~~-UI-2.png\|border\|600px]]		[[File:CTMS-UI-2.png\|border\|600px]]

	When a driver and vehicle have been entered, the user will be prompted to change the status to Accepted if required.		When a driver and vehicle have been entered, the user will be prompted to change the status to Accepted if required.
Line 140:		Line 140:
	A View Map button is provided, to show details of the stops on the trip and route planning.		A View Map button is provided, to show details of the stops on the trip and route planning.

	[[File:~~CMTS~~-UI-2c.png\|border\|600px]]		[[File:CTMS-UI-2c.png\|border\|600px]]

	==Accepted==		==Accepted==
	Example: MAN-00000012		Example: MAN-00000012

	[[File:~~CMTS~~-UI-3.png\|border\|600px]]		[[File:CTMS-UI-3.png\|border\|600px]]

	A Driver Brief panel is displayed and open for the user to confirm key information about the trip, vehicle and driver before the trip begins. The General tab is still visible if required.		A Driver Brief panel is displayed and open for the user to confirm key information about the trip, vehicle and driver before the trip begins. The General tab is still visible if required.
Line 155:		Line 155:
	Despatched quantities can be set from planned using the Planned button. Additionally, each order can be edited or set from planned using the Hover Menu against each grid line. Editing a line will show a pop-up window with the information to enter.		Despatched quantities can be set from planned using the Planned button. Additionally, each order can be edited or set from planned using the Hover Menu against each grid line. Editing a line will show a pop-up window with the information to enter.

	[[File:~~CMTS~~-UI-3a.png\|border\|600px]]		[[File:CTMS-UI-3a.png\|border\|600px]]

	Once all data has been entered, the user is able to change the status to En Route by using the button provided.		Once all data has been entered, the user is able to change the status to En Route by using the button provided.
Line 162:		Line 162:
	Example: MAN-00000006		Example: MAN-00000006

	[[File:~~CMTS~~-UI-4.png\|border\|600px]]		[[File:CTMS-UI-4.png\|border\|600px]]

	From this stage forward, a History button is available to show any audit history against the screen .		From this stage forward, a History button is available to show any audit history against the screen .
Line 175:		Line 175:

	The Actual Dates and Times can be from planned using the Planned button. Additionally, each stop can be edited or set from planned using the Hover Menu against each grid line. Editing a line will show a pop-up window with the information to enter, and a reason code if required. If orders are being delivered against the stop, a pop-up entry window will be shown to enter the delivered quantities against each order delivered.		The Actual Dates and Times can be from planned using the Planned button. Additionally, each stop can be edited or set from planned using the Hover Menu against each grid line. Editing a line will show a pop-up window with the information to enter, and a reason code if required. If orders are being delivered against the stop, a pop-up entry window will be shown to enter the delivered quantities against each order delivered.

			[[File:CTMS-UI-4.png\|border\|600px]]

	ETA dates and times are forecast from outside the CTMS system. If they are available, the screen will display these with RAG-colouration:		ETA dates and times are forecast from outside the CTMS system. If they are available, the screen will display these with RAG-colouration:
Line 181:		Line 183:

	The popup menu on a Red-coloured ETA stop pops up a window allowing the user to email all affected customers with their new ETA.		The popup menu on a Red-coloured ETA stop pops up a window allowing the user to email all affected customers with their new ETA.

			[[File:CTMS-UI-4b.png\|border\|600px]]

	When all quantities and dates have been entered, the user is prompted as to whether they can change the status to Completed. This can be done through the button at the top of the screen.		When all quantities and dates have been entered, the user is prompted as to whether they can change the status to Completed. This can be done through the button at the top of the screen.
Line 186:		Line 190:
	==Completed==		==Completed==
	Example: MAN-00000001		Example: MAN-00000001

			[[File:CTMS-UI-5.png\|border\|600px]]

	A Driver Debrief panel is displayed and open for the user to confirm key information about the trip, vehicle and driver after the trip ends. All other tabs are still visible if required.		A Driver Debrief panel is displayed and open for the user to confirm key information about the trip, vehicle and driver after the trip ends. All other tabs are still visible if required.
Line 192:		Line 198:

	The user is also able to display Driver Discrepancies here, which pops up a window showing all discrepancies (for example, late arrivals, departures, delivered quantity changes) in a grid. A comment can be added per discrepancy.		The user is also able to display Driver Discrepancies here, which pops up a window showing all discrepancies (for example, late arrivals, departures, delivered quantity changes) in a grid. A comment can be added per discrepancy.

			[[File:CTMS-UI-5a.png\|border\|600px]]

	When all information has been entered, the user is prompted as to whether they can change the status to Debriefed. This can be done through the button at the top of the screen.		When all information has been entered, the user is prompted as to whether they can change the status to Debriefed. This can be done through the button at the top of the screen.
Line 197:		Line 205:
	==Debriefed==		==Debriefed==
	Example: MAN-00000010		Example: MAN-00000010

			[[File:CTMS-UI-6.png\|border\|600px]]

	The Orders list now displays a POD check, to enter whether PODs have been received for each order.These are required to be checked before the Trip can be set to Confirmed - the user will be prompted to enter these if they haven't already been entered. All PODs can be set as received by using the POD All button.		The Orders list now displays a POD check, to enter whether PODs have been received for each order.These are required to be checked before the Trip can be set to Confirmed - the user will be prompted to enter these if they haven't already been entered. All PODs can be set as received by using the POD All button.
Line 204:		Line 214:
	==Confirmed==		==Confirmed==
	Example: MAN-00000011		Example: MAN-00000011

			[[File:CTMS-UI-7.png\|border\|600px]]

	A Finance panel is displayed and open for the user to enter Payments information. All previous tabs are still visible if required.		A Finance panel is displayed and open for the user to enter Payments information. All previous tabs are still visible if required.
Line 211:		Line 223:
	=Audit Screen=		=Audit Screen=
	Example: MAN-00000011		Example: MAN-00000011

			[[File:CTMS-UI-8.png\|border\|600px]]

	Audit records will written at one of three levels (Trip, Tractor, Driver) at various stages in the process.		Audit records will written at one of three levels (Trip, Tractor, Driver) at various stages in the process.
Line 221:		Line 235:
	=Load Screen=		=Load Screen=
	Example: LOAD5		Example: LOAD5

			[[File:CTMS-UI-9.png\|border\|600px]]

	This screen shows all orders associated to the Load ID passed in or selected from the provided auto-complete list.		This screen shows all orders associated to the Load ID passed in or selected from the provided auto-complete list.

Anw: /* C-TMS Execution Screen */

2011-11-02T14:41:35Z

C-TMS Execution Screen

← Older revision		Revision as of 16:41, 2 November 2011
Line 99:		Line 99:
	The screen begins by requesting the user to find a trip. This can be through the traditional CTMS mechanism of choosing a schedule and a trip from the drop-down lists provided, or by directly entering a trip in the provided box. Simply typing part of the Trip ID will match all similar trips, which can be selected from the list. This is an example of an Auto-complete entry box.		The screen begins by requesting the user to find a trip. This can be through the traditional CTMS mechanism of choosing a schedule and a trip from the drop-down lists provided, or by directly entering a trip in the provided box. Simply typing part of the Trip ID will match all similar trips, which can be selected from the list. This is an example of an Auto-complete entry box.

	[[File:~~CMTS~~-UI-1.png\|border\|600px]]		[[File:CTMS-UI-1.png\|border\|600px]]

	Once selected (by clicking the provided button), the screen displays the trip details.		Once selected (by clicking the provided button), the screen displays the trip details.
Line 122:		Line 122:
	Example: MAN-00000013		Example: MAN-00000013

	[[File:~~CMTS~~-UI-2.png\|border\|600px]]		[[File:CTMS-UI-2.png\|border\|600px]]

	A General tab is displayed and open for the Trip, showing general data and allowing the user to enter and view Vehicle and Driver. Drop-down lists are used for these elements. Validation is performed and displayed in-line through Validator Call-outs.		A General tab is displayed and open for the Trip, showing general data and allowing the user to enter and view Vehicle and Driver. Drop-down lists are used for these elements. Validation is performed and displayed in-line through Validator Call-outs.
Line 207:		Line 207:
	A Finance panel is displayed and open for the user to enter Payments information. All previous tabs are still visible if required.		A Finance panel is displayed and open for the user to enter Payments information. All previous tabs are still visible if required.

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

	=Audit Screen=		=Audit Screen=

Anw at 14:39, 2 November 2011

2011-11-02T14:39:03Z

← Older revision		Revision as of 16:39, 2 November 2011
Line 98:		Line 98:
	= C-TMS Execution Screen =		= C-TMS Execution Screen =
	The screen begins by requesting the user to find a trip. This can be through the traditional CTMS mechanism of choosing a schedule and a trip from the drop-down lists provided, or by directly entering a trip in the provided box. Simply typing part of the Trip ID will match all similar trips, which can be selected from the list. This is an example of an Auto-complete entry box.		The screen begins by requesting the user to find a trip. This can be through the traditional CTMS mechanism of choosing a schedule and a trip from the drop-down lists provided, or by directly entering a trip in the provided box. Simply typing part of the Trip ID will match all similar trips, which can be selected from the list. This is an example of an Auto-complete entry box.

			[[File:CMTS-UI-1.png\|border\|600px]]

	Once selected (by clicking the provided button), the screen displays the trip details.		Once selected (by clicking the provided button), the screen displays the trip details.
Line 119:		Line 121:
	==Planned==		==Planned==
	Example: MAN-00000013		Example: MAN-00000013

			[[File:CMTS-UI-2.png\|border\|600px]]

	A General tab is displayed and open for the Trip, showing general data and allowing the user to enter and view Vehicle and Driver. Drop-down lists are used for these elements. Validation is performed and displayed in-line through Validator Call-outs.		A General tab is displayed and open for the Trip, showing general data and allowing the user to enter and view Vehicle and Driver. Drop-down lists are used for these elements. Validation is performed and displayed in-line through Validator Call-outs.

	Optionally, the user may enter and view Crew and Instructions information, by clicking on the appropriate button. These are entered and validated through a Modal pop-up screen, allowing dragging of the panels.		Optionally, the user may enter and view Crew and Instructions information, by clicking on the appropriate button. These are entered and validated through a Modal pop-up screen, allowing dragging of the panels.

			[[File:CMTS-UI-2.png\|border\|600px]]

	When a driver and vehicle have been entered, the user will be prompted to change the status to Accepted if required.		When a driver and vehicle have been entered, the user will be prompted to change the status to Accepted if required.
Line 133:		Line 139:

	A View Map button is provided, to show details of the stops on the trip and route planning.		A View Map button is provided, to show details of the stops on the trip and route planning.

			[[File:CMTS-UI-2c.png\|border\|600px]]

	==Accepted==		==Accepted==
	Example: MAN-00000012		Example: MAN-00000012

			[[File:CMTS-UI-3.png\|border\|600px]]

	A Driver Brief panel is displayed and open for the user to confirm key information about the trip, vehicle and driver before the trip begins. The General tab is still visible if required.		A Driver Brief panel is displayed and open for the user to confirm key information about the trip, vehicle and driver before the trip begins. The General tab is still visible if required.
Line 144:		Line 154:

	Despatched quantities can be set from planned using the Planned button. Additionally, each order can be edited or set from planned using the Hover Menu against each grid line. Editing a line will show a pop-up window with the information to enter.		Despatched quantities can be set from planned using the Planned button. Additionally, each order can be edited or set from planned using the Hover Menu against each grid line. Editing a line will show a pop-up window with the information to enter.

			[[File:CMTS-UI-3a.png\|border\|600px]]

	Once all data has been entered, the user is able to change the status to En Route by using the button provided.		Once all data has been entered, the user is able to change the status to En Route by using the button provided.
Line 149:		Line 161:
	==En Route==		==En Route==
	Example: MAN-00000006		Example: MAN-00000006

			[[File:CMTS-UI-4.png\|border\|600px]]

	From this stage forward, a History button is available to show any audit history against the screen .		From this stage forward, a History button is available to show any audit history against the screen .

Anw: /* Technology */

2011-11-02T14:25:50Z

Technology

← Older revision		Revision as of 16:25, 2 November 2011
Line 18:		Line 18:

	==Technology==		==Technology==
	The ~~system~~ is written ~~with~~ Visual Studio ~~2008~~, utilising the following functionality:		The Web Application is written using the Visual Studio development environment, utilising the following functionality:
	*ASP.NET (for forms design)		*ASP.NET (for forms design)
	*Database access tools (access to any database type, including Oracle)		*Database access tools (access to any database type, including Oracle)
Line 27:		Line 27:

	The system has been written accessing a demo database created in Microsoft SQL Server 2008, the design of which is based on the CTMS Trips and Order tables.		The system has been written accessing a demo database created in Microsoft SQL Server 2008, the design of which is based on the CTMS Trips and Order tables.

			The system is hosted on a Microsoft Windows 2003 server, through IIS 8.

	==UI Features==		==UI Features==

Anw: /* Technology */

2011-11-02T14:22:55Z

Technology

← Older revision		Revision as of 16:22, 2 November 2011
Line 24:		Line 24:
	*JavaScript		*JavaScript
	*AJAX Tool-kit		*AJAX Tool-kit
			*Web Services

	The system has been written accessing a demo database created in Microsoft SQL Server 2008, the design of which is based on the CTMS Trips and Order tables.		The system has been written accessing a demo database created in Microsoft SQL Server 2008, the design of which is based on the CTMS Trips and Order tables.

Anw: /* Technology */

2011-11-02T14:22:14Z

Technology

← Older revision		Revision as of 16:22, 2 November 2011
Line 18:		Line 18:

	==Technology==		==Technology==
	The system is written in Visual Studio 2008, utilising the following functionality:		The system is written with Visual Studio 2008, utilising the following functionality:
	*ASP.NET (for forms design)		*ASP.NET (for forms design)
	*Database access tools		*Database access tools (access to any database type, including Oracle)
	*C#		*C# (for server access)
	*JavaScript		*JavaScript
	*AJAX Tool-kit		*AJAX Tool-kit

Anw at 14:17, 2 November 2011

2011-11-02T14:17:25Z

← Older revision		Revision as of 16:17, 2 November 2011
Line 115:		Line 115:

	==Planned==		==Planned==
			Example: MAN-00000013

	A General tab is displayed and open for the Trip, showing general data and allowing the user to enter and view Vehicle and Driver. Drop-down lists are used for these elements. Validation is performed and displayed in-line through Validator Call-outs.		A General tab is displayed and open for the Trip, showing general data and allowing the user to enter and view Vehicle and Driver. Drop-down lists are used for these elements. Validation is performed and displayed in-line through Validator Call-outs.
Line 131:		Line 132:

	==Accepted==		==Accepted==
			Example: MAN-00000012

	A Driver Brief panel is displayed and open for the user to confirm key information about the trip, vehicle and driver before the trip begins. The General tab is still visible if required.		A Driver Brief panel is displayed and open for the user to confirm key information about the trip, vehicle and driver before the trip begins. The General tab is still visible if required.
Line 143:		Line 145:

	==En Route==		==En Route==
			Example: MAN-00000006

	From this stage forward, a History button is available to show any audit history against the screen .		From this stage forward, a History button is available to show any audit history against the screen .

Line 164:		Line 168:

	==Completed==		==Completed==
			Example: MAN-00000001

	A Driver Debrief panel is displayed and open for the user to confirm key information about the trip, vehicle and driver after the trip ends. All other tabs are still visible if required.		A Driver Debrief panel is displayed and open for the user to confirm key information about the trip, vehicle and driver after the trip ends. All other tabs are still visible if required.
Line 174:		Line 179:

	==Debriefed==		==Debriefed==
			Example: MAN-00000010

	The Orders list now displays a POD check, to enter whether PODs have been received for each order.These are required to be checked before the Trip can be set to Confirmed - the user will be prompted to enter these if they haven't already been entered. All PODs can be set as received by using the POD All button.		The Orders list now displays a POD check, to enter whether PODs have been received for each order.These are required to be checked before the Trip can be set to Confirmed - the user will be prompted to enter these if they haven't already been entered. All PODs can be set as received by using the POD All button.
Line 180:		Line 186:

	==Confirmed==		==Confirmed==
			Example: MAN-00000011

	A Finance panel is displayed and open for the user to enter Payments information. All previous tabs are still visible if required.		A Finance panel is displayed and open for the user to enter Payments information. All previous tabs are still visible if required.

			<!-- NEW PAGE -->

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

	~~Screen accepts parameters~~ of Trip, ~~Trailer or~~ Driver.		Audit records will written at one of three levels (Trip, Tractor, Driver) at various stages in the process.
			This screen reports on those records.

	~~For~~ Trip ~~- display all records found.~~		The screen allows the user to select through multiple parameters, although only Trip is currently enabled.
	~~Any others, limit to 20 to a page~~.

	~~For Trip~~, ~~get Audit Type records of Trip for the supplied Trip ID.~~		When selected, the grid displays all audit records associated to that trip.
	~~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.~~		=Load Screen=
			Example: LOAD5
	~~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~~.		This screen shows all orders associated to the Load ID passed in or selected from the provided auto-complete list.

	~~If we search for~~ the ~~Trip ID, we will return both audit records~~.		When selected, the grid displays all orders and trips which are marked against that load.

	~~If we search for~~ the ~~Tractor ID, we will get only audit 2.~~		The grid is configurable (through the Config button and pop-up) and sortable through the column titles.

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

	~~There should be a capability to click an audit record~~ and ~~see all the details, showing comments entered against the audit,~~ and ~~an ability to add more comments.~~

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