REQ 305796 Partnerlink EPOD Solution - Revision history

Anw: Categorisation of document pages

2019-11-29T09:54:37Z

Categorisation of document pages

← Older revision		Revision as of 11:54, 29 November 2019
Line 3:		Line 3:
	{{#vardefine:ClientName\|Partnerlink}}		{{#vardefine:ClientName\|Partnerlink}}
	{{#vardefine:System\|''CALIDUS'' ePOD}}		{{#vardefine:System\|''CALIDUS'' ePOD}}
			{{#vardefine:SystemCode\|EPOD}}
	{{#vardefine:Doc_Title\|Partnerlink ePOD Solution}}		{{#vardefine:Doc_Title\|Partnerlink ePOD Solution}}
	{{#vardefine:Version\|0.2}}		{{#vardefine:Version\|0.2}}
Line 822:		Line 823:
	}}</div>		}}</div>
	[[Category:{{#var:Client}} REQ]]		[[Category:{{#var:Client}} REQ]]
			[[Category:{{#var:SystemCode}}]]

Anw: Added reason codes

2013-02-21T09:22:36Z

Added reason codes

@@ Line 787: / Line 787: @@
 <!-- MEDIA LANDSCAPE NO -->
 {{Doc_Appendix
-|Appendix=B
+|Appendix=C
 |Estimate=N
 |Glossary=EPOD

Anw: Confirmed System and Area across the list of SCRs

2013-02-14T10:28:39Z

Confirmed System and Area across the list of SCRs

← Older revision		Revision as of 12:28, 14 February 2013
Line 643:		Line 643:
	\|SCR={{ #vardefineecho: SCR \| {{ #expr: {{ #var: SCR }} + 1 }} }}		\|SCR={{ #vardefineecho: SCR \| {{ #expr: {{ #var: SCR }} + 1 }} }}
	\|System=EPOD		\|System=EPOD
	\|Area=~~Client~~		\|Area=All
	\|Description=Resequence Jobs		\|Description=Resequence Jobs
	\|Estimate=0		\|Estimate=0
Line 697:		Line 697:
	\|SCR={{ #vardefineecho: SCR \| {{ #expr: {{ #var: SCR }} + 1 }} }}		\|SCR={{ #vardefineecho: SCR \| {{ #expr: {{ #var: SCR }} + 1 }} }}
	\|System=EPOD		\|System=EPOD
	\|Area=~~Client~~		\|Area=All
	\|Description=Allow Customer to Clause delivery items		\|Description=Allow Customer to Clause delivery items
	\|Estimate=0		\|Estimate=0
Line 706:		Line 706:
	\|SCR={{ #vardefineecho: SCR \| {{ #expr: {{ #var: SCR }} + 1 }} }}		\|SCR={{ #vardefineecho: SCR \| {{ #expr: {{ #var: SCR }} + 1 }} }}
	\|System=EPOD		\|System=EPOD
	\|Area=~~Client~~		\|Area=Admin
	\|Description=Create POD Formats (Generic and Palletforce)		\|Description=Create POD Formats (Generic and Palletforce)
	\|Estimate=0		\|Estimate=0
Line 715:		Line 715:
	\|SCR={{ #vardefineecho: SCR \| {{ #expr: {{ #var: SCR }} + 1 }} }}		\|SCR={{ #vardefineecho: SCR \| {{ #expr: {{ #var: SCR }} + 1 }} }}
	\|System=EPOD		\|System=EPOD
	\|Area=~~Client~~		\|Area=Export
	\|Description=Export POD document as TIFF through the existing Partnerlink processes		\|Description=Export POD document as TIFF through the existing Partnerlink processes
	\|Estimate=0		\|Estimate=0
Line 724:		Line 724:
	\|SCR={{ #vardefineecho: SCR \| {{ #expr: {{ #var: SCR }} + 1 }} }}		\|SCR={{ #vardefineecho: SCR \| {{ #expr: {{ #var: SCR }} + 1 }} }}
	\|System=EPOD		\|System=EPOD
	\|Area=~~Client~~		\|Area=Export
	\|Description=Export POD document as TIFF to Palletforce system		\|Description=Export POD document as TIFF to Palletforce system
	\|Estimate=0		\|Estimate=0
Line 732:		Line 732:
	{{REQ_SCR_Line		{{REQ_SCR_Line
	\|SCR={{ #vardefineecho: SCR \| {{ #expr: {{ #var: SCR }} + 1 }} }}		\|SCR={{ #vardefineecho: SCR \| {{ #expr: {{ #var: SCR }} + 1 }} }}
	\|System=EPOD		\|System=EPOD/TTM
	\|Area=~~Client~~		\|Area=I/F
	\|Description=Changes to ePOD-TTM interface		\|Description=Changes to ePOD-TTM interface
	\|Estimate=0		\|Estimate=0
Line 742:		Line 742:
	\|SCR={{ #vardefineecho: SCR \| {{ #expr: {{ #var: SCR }} + 1 }} }}		\|SCR={{ #vardefineecho: SCR \| {{ #expr: {{ #var: SCR }} + 1 }} }}
	\|System=EPOD		\|System=EPOD
	\|Area=~~Client~~		\|Area=Server
	\|Description=Automatically email on cancellation of a job only		\|Description=Automatically email on cancellation of a job only
	\|Estimate=0		\|Estimate=0
Line 751:		Line 751:
	\|SCR={{ #vardefineecho: SCR \| {{ #expr: {{ #var: SCR }} + 1 }} }}		\|SCR={{ #vardefineecho: SCR \| {{ #expr: {{ #var: SCR }} + 1 }} }}
	\|System=TTM		\|System=TTM
	\|Area=~~Client~~		\|Area=Server
	\|Description=Display and recalculate ETA		\|Description=Display and recalculate ETA
	\|Estimate=0		\|Estimate=0
Line 760:		Line 760:
	\|SCR={{ #vardefineecho: SCR \| {{ #expr: {{ #var: SCR }} + 1 }} }}		\|SCR={{ #vardefineecho: SCR \| {{ #expr: {{ #var: SCR }} + 1 }} }}
	\|System=TTM		\|System=TTM
	\|Area=~~Client~~		\|Area=All
	\|Description=Add Clause functionality to CALIDUS TTM		\|Description=Add Clause functionality to CALIDUS TTM
	\|Estimate=0		\|Estimate=0
Line 769:		Line 769:
	\|SCR={{ #vardefineecho: SCR \| {{ #expr: {{ #var: SCR }} + 1 }} }}		\|SCR={{ #vardefineecho: SCR \| {{ #expr: {{ #var: SCR }} + 1 }} }}
	\|System=TTM		\|System=TTM
	\|Area=~~Client~~		\|Area=Admin
	\|Description=Add additional search criteria to CALIDUS TTM		\|Description=Add additional search criteria to CALIDUS TTM
	\|Estimate=0		\|Estimate=0
Line 777:		Line 777:
	{{REQ_SCR_Line		{{REQ_SCR_Line
	\|SCR={{ #vardefineecho: SCR \| {{ #expr: {{ #var: SCR }} + 1 }} }}		\|SCR={{ #vardefineecho: SCR \| {{ #expr: {{ #var: SCR }} + 1 }} }}
	\|System=EPOD		\|System=EPOD/TTM
	\|Area=~~Client~~		\|Area=All
	\|Description=Trailer ID changes		\|Description=Trailer ID changes
	\|Estimate=0		\|Estimate=0

Anw: v0.2 - draft version for review

2013-01-31T16:12:56Z

v0.2 - draft version for review

← Older revision		Revision as of 18:12, 31 January 2013
Line 4:		Line 4:
	{{#vardefine:System\|''CALIDUS'' ePOD}}		{{#vardefine:System\|''CALIDUS'' ePOD}}
	{{#vardefine:Doc_Title\|Partnerlink ePOD Solution}}		{{#vardefine:Doc_Title\|Partnerlink ePOD Solution}}
	{{#vardefine:Version\|0.1}}		{{#vardefine:Version\|0.2}}
	{{#vardefine:Date\|~~30th~~ January 2013}}		{{#vardefine:Date\|31st January 2013}}
	{{#vardefine:Reference\|305796}}		{{#vardefine:Reference\|305796}}
	{{#vardefine:Year\|2013}}		{{#vardefine:Year\|2013}}
Line 168:		Line 168:
	Upon logging in, the user will be prompted to enter the User ID, Vehicle and Password that they have been provided with. If there is any error regarding the values entered, the application will inform the user of the error. A pop-up keyboard will be displayed for entry of the details.		Upon logging in, the user will be prompted to enter the User ID, Vehicle and Password that they have been provided with. If there is any error regarding the values entered, the application will inform the user of the error. A pop-up keyboard will be displayed for entry of the details.

	[[File:REQ-305796-1.PNG]]		[[File:REQ-305796-1.PNG\|border\|250px]]

	{{Note}} If the device has never been configured before, a configuration screen will be displayed. It is however expected that the device will be configured in advance.		{{Note}} If the device has never been configured before, a configuration screen will be displayed. It is however expected that the device will be configured in advance.
Line 203:		Line 203:
	This screen shows all the jobs on the load that has been assigned to the driver.		This screen shows all the jobs on the load that has been assigned to the driver.

	[[File:REQ-305796-2.PNG]]		[[File:REQ-305796-2.PNG\|border\|250px]]

	The screen displays a grid displaying details of each pending job. This will be modified for the bespoke styling as follows:		The screen displays a grid displaying details of each pending job. This will be modified for the bespoke styling as follows:
Line 243:		Line 243:
	This screen will be displayed regardless of job type. The translated job type will be displayed on the top (i.e. COLLECTION, DELIVERY), along with the status (PENDING, COMPLETE, CANCELLED, COMPLETE AMENDED). The descriptive job code, as configured by the system, will be displayed in here as well.		This screen will be displayed regardless of job type. The translated job type will be displayed on the top (i.e. COLLECTION, DELIVERY), along with the status (PENDING, COMPLETE, CANCELLED, COMPLETE AMENDED). The descriptive job code, as configured by the system, will be displayed in here as well.

	[[File:REQ-305796-3a.PNG]]		[[File:REQ-305796-3a.PNG\|border\|250px]]
	[[File:REQ-305796-3b.PNG]]		[[File:REQ-305796-3b.PNG\|border\|250px]]

	The screen has several Tabs:		The screen has several Tabs:
Line 312:		Line 312:
	If the job type is a Delivery, the driver will be shown this screen. They will be initially presented with the information about the job.		If the job type is a Delivery, the driver will be shown this screen. They will be initially presented with the information about the job.

	[[File:REQ-305796-4a.PNG]]		[[File:REQ-305796-4a.PNG\|border\|250px]]

	{{Note}} As mentioned previously, the system will be modified to display the word 'Pallet' where the word 'Container is used in the description below.		{{Note}} As mentioned previously, the system will be modified to display the word 'Pallet' where the word 'Container is used in the description below.
Line 333:		Line 333:
	* A configurable ''Notes'' tab, to allow the user to enter notes about the job.		* A configurable ''Notes'' tab, to allow the user to enter notes about the job.

	[[File:REQ-305796-4b.PNG]]		[[File:REQ-305796-4b.PNG\|border\|250px]]

	To mark containers as delivered, the driver can:		To mark containers as delivered, the driver can:
Line 357:		Line 357:
	The driver also has the option to enter any notes they want on the ''Notes'' tab.		The driver also has the option to enter any notes they want on the ''Notes'' tab.

	[[File:REQ-305796-4c.PNG]]		[[File:REQ-305796-4c.PNG\|border\|250px]]

	Once all containers have been delivered, the device will automatically take the driver to the Job Confirmation screen.		Once all containers have been delivered, the device will automatically take the driver to the Job Confirmation screen.
Line 400:		Line 400:
	It is expected that this will be configured only for Customer signature, for both collections and deliveries.		It is expected that this will be configured only for Customer signature, for both collections and deliveries.

	[[File:REQ-305796-5.PNG]]		[[File:REQ-305796-5.PNG\|border\|250px]]

	The ''Customer Signature'' box defaults to the customer's contact name - as this will not be sent to {{#var:System}}, this will be blank and must be entered by the driver.		The ''Customer Signature'' box defaults to the customer's contact name - as this will not be sent to {{#var:System}}, this will be blank and must be entered by the driver.
Line 597:		Line 597:
	<!-- MEDIA LANDSCAPE YES -->		<!-- MEDIA LANDSCAPE YES -->

	= Appendix A: Table of SCRs ~~and Ballpark Estimates~~ =		= Appendix A: Table of SCRs =
	<!-- 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

Anw: Added table of changes

2013-01-31T16:04:17Z

Added table of changes

Show changes

Anw: Added Trailer requirements and TTM requirements

2013-01-31T15:48:20Z

Added Trailer requirements and TTM requirements

← Older revision		Revision as of 17:48, 31 January 2013
Line 48:		Line 48:
	\|Definition=Change "Container" to "Pallet" on the device		\|Definition=Change "Container" to "Pallet" on the device
	}}		}}
	* The Login screen will ~~also~~ be modified to display the Partnerlink logo rather than the OBS logo. {{SCR		* The Android Client Login screen and ''CALIDUS'' TTM will be modified to display the correct Partnerlink logo rather than the OBS logo. {{SCR
	\|Reference={{#var:Reference}}		\|Reference={{#var:Reference}}
	\|SCRNo={{ #vardefineecho: SCR \| {{ #expr: {{ #var: SCR }} + 1 }} }}		\|SCRNo={{ #vardefineecho: SCR \| {{ #expr: {{ #var: SCR }} + 1 }} }}
	\|Definition=Ensure that the correct Partnerlink logo is displayed ~~on the device~~.		\|Definition=Ensure that the correct Partnerlink logo is displayed.
	}}		}}

	This style can be set from the devices Settings screen and will be labelled as "Partnerlink" on the list of styles.		This style can be set from the Android devices' Settings screen and will be labelled as "Partnerlink" on the list of styles, and will be set as default in ''CALIDUS'' TTM.

	== Importing Data ==		== Importing Data ==
Line 539:		Line 539:
	}}		}}
	{{Note}} Emails being sent from {{#var:System}} require that the server has connectivity to a mail server. This is normally provided by the client, but is to be confirmed.		{{Note}} Emails being sent from {{#var:System}} require that the server has connectivity to a mail server. This is normally provided by the client, but is to be confirmed.

			== Tracking the Jobs ==
			''CALIDUS'' TTM will show all jobs and manifests sent through to be executed. The standard functionality in place regarding enquiries, extracts,departure boards and user configuration is seen to be sufficient to run the operation. The system will also show all audit trails of activity as they happen in the system.

			The activity enquiries on orders will be extended in the system to add:
			* Resequencing
			* Order In Progress
			* Order Arrived

			It was noted that that the styling of ''CALIDUS'' TTM would also require some changes to labels in the system, to closer match the client terminology, for example, "Trip" will be displayed as "Manifest", "Exception" as "Clause".

			The system will be configured so that partners can see the jobs that they own (through the Owner parameter) and see and select those partners who are executing a shared job (through the Haulier).

			The system calculates and displays ETAs, as follows:
			* The original ETA of jobs will be set based on the Planned information sent to {{#var:System}}, if provided.
			* When an In Progress message is received (when a Job is started), the system will then recalculate all ETAs forwards from that point, by requesting mapping drive times between each stop as they are planned. Each stop will have a minimum unload time associated with it, expected to be half an hour, but this will be configurable.
			* A system user can request the latest ETA from the system, which will query the last known position and time of the vehicle, and recalculate the ETA from that position at that time. This will also pass forward to all subsequent jobs on that manifest.
			{{SCR
			\|Reference={{#var:Reference}}
			\|SCRNo={{ #vardefineecho: SCR \| {{ #expr: {{ #var: SCR }} + 1 }} }}
			\|Definition=Display and recalculate ETA
			}}

			The system will ensure that the new functionality for Claused deliveries are seen as Exceptions in TTM, and displayed with the amber colouration. Additionally, the descriptions against the Claused items will be visible in the system
			{{SCR
			\|Reference={{#var:Reference}}
			\|SCRNo={{ #vardefineecho: SCR \| {{ #expr: {{ #var: SCR }} + 1 }} }}
			\|Definition=Add Clause functionality to ''CALIDUS'' TTM
			}}

			The existing Order "Enquiry by Client Order No" screen will be modified to allow searching by customer name and Customer PO Code.
			{{SCR
			\|Reference={{#var:Reference}}
			\|SCRNo={{ #vardefineecho: SCR \| {{ #expr: {{ #var: SCR }} + 1 }} }}
			\|Definition=Add additional search criteria to ''CALIDUS'' TTM
			}}

	== Out of Scope Changes ==		== Out of Scope Changes ==
Line 544:		Line 580:

	=== Trailer IDs ===		=== Trailer IDs ===
			It was noted that it would be necessary to track Trailer IDs throughout the process, where the vehicle being used by the driver is a tractor type. Multiple changes must be made to the processes and the system to accommodate this.
	{{SCR		{{SCR
	\|Reference={{#var:Reference}}		\|Reference={{#var:Reference}}
Line 549:		Line 586:
	\|Definition=Trailer ID changes		\|Definition=Trailer ID changes
	}}		}}
			It has been determined that this is out of scope of the project, but a description of the processes follow for documentation purposes.

			* When an Manifest or a Job is sent to {{#var:System}}, it may contain Trailer information. If this is the case, and the vehicle does not already exist, the Vehicle will be updated to show that it requires the entry of Trailers. The generic maintenance of vehicles within the system will also change to allow this flag to be maintained.
			* When the Job List is displayed, if there is a trailer associated to the Load, this will be displayed on the screen. If the trailer does not exist on the load but exists on the job, the trailer required to complete the first job will be displayed.
			* If neither exist, the driver will be prompted to enter the Trailer used against the Load.
			* The driver will have an option of changing the Trailer used at any time.
			* Where a trailer has not been defined, the driver's entry will be stored against the job and the load. This will be returned to the ''CALIDUS'' TTM and TMS systems for traceability.
			It should also be noted that there is a requirement to report this information through ''CALIDUS'' TTM, as an attempt to provide some asset tracking to the trailers. It is assumed that the existing data extract is suitable, as it can be imported into Microsoft Excel for processing, and the trailer ID can be queried directly the existing screens.








	<!-- MEDIA LANDSCAPE YES -->		<!-- MEDIA LANDSCAPE YES -->
Line 573:		Line 604:

	{{ #vardefine: SCR \| 0 }}		{{ #vardefine: SCR \| 0 }}
	{{REQ_SCR_Header}}		{{REQ_SCR_Header}}{{REQ_SCR_Line
	{{REQ_SCR_Line
	\|SCR={{ #vardefineecho: SCR \| {{ #expr: {{ #var: SCR }} + 1 }} }}		\|SCR={{ #vardefineecho: SCR \| {{ #expr: {{ #var: SCR }} + 1 }} }}
	\|System=System Affected		\|System=System Affected

Anw: /* Importing Data */

2013-01-31T14:27:00Z

Importing Data

← Older revision		Revision as of 16:27, 31 January 2013
Line 61:		Line 61:
	* Mandata		* Mandata
	* Stirling		* Stirling
	The exact formats of the data uploads from the various systems are still being decided. However, there is a requirement that certain data items are passed into the system:		The exact formats of the data uploads from the various systems are still being decided. However, there is a requirement that certain data items are passed into the system.

	A basic list of all the fields in the interface for Load (Manifest) and Job follows. A full spreadsheet of all the import flows and fields containing all the limitations on length and defaulted values is provided separately and issued to all TMS suppliers.		A basic list of all the fields in the interface for Load (Manifest) and Job follows. A full spreadsheet of all the import flows and fields containing all the limitations on length and defaulted values is provided separately and issued to all TMS suppliers.

Anw: Added details of Signature, Load Completion and POD formats

2013-01-31T14:25:48Z

Added details of Signature, Load Completion and POD formats

Show changes

Anw: Added Delivery information

2013-01-31T11:44:44Z

Added Delivery information

@@ Line 26: / Line 26: @@
 == Objective  ==
-The primary purpose of this document is to document the requirements gathered from {{#var:ClientName}}, at meetings held in the Kinghts of Old offices on 22-24th January, 2012
+The primary purpose of this document is to document the requirements gathered from {{#var:ClientName}}, at meetings held in the Knights of Old offices on 22-24th January, 2012
 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.
@@ Line 247: / Line 247: @@
 The screen has several Tabs:
-* Address & Contact:
+* ''Address & Contact'':
 ** Customer Name
 ** Customer Address
@@ Line 253: / Line 253: @@
 ** Contact Telephone
 ** Date and Time
-* Instructions - any special instructions for the job.
+* ''Instructions'' - any special instructions for the job.
 The driver can click on the tabs to see the information contained.
@@ Line 277: / Line 277: @@
 {{Note}} If the job is at any status other than "Pending" or "In Progress", the device will display an error informing them that the job can't be started again.
-The partners require the users to be forced to view the Special Instructions before starting a job. The application will be changed to force this, through configuration. If this is the case, and if the job is allowed to be started by the device, the device will check to see whether the Special Instructions tab has yet been viewed. If not, the device will display a pop-up message that these must be viewed before starting the job, and force the tab to be displayed.
+The partners require the users to be forced to view the Special Instructions before starting a job. The application will be changed to force this, through configuration. If this is the case, and if the job is allowed to be started by the device, the device will check to see whether the ''Special Instructions'' tab has yet been viewed. If not, the device will display a pop-up message that these must be viewed before starting the job, and force the tab to be displayed.
 {{SCR
@@ Line 299: / Line 299: @@
 }}
-If the driver wishes to cancel the job, they can press the '''Cancel''' button. The unit will take the driver to an Exception screen and prompt them to enter a reason code explaining why this job was cancelled. An image can be captured if required.
+If the driver wishes to cancel the job, they can press the '''Cancel''' button. The unit will take the driver to an Exception screen and prompt them to enter a reason code explaining why this job was cancelled. An image can be captured if required. {{Note}} The reason codes offered to the driver will be those configured within the system for the cancellation of a job, rather than those relevant to the cancellation of a deliverable item. The Reason Codes will be maintained manually within {{#var:System}} by the users.
 This cancellation process is not desired by some of the partners, so the application will be amended to control whether Job Cancellation is allowed at this stage.
@@ Line 310: / Line 310: @@
 == Delivery ==
 {{SCR
 |Reference={{#var:Reference}}
 |SCRNo={{ #vardefineecho: SCR | {{ #expr: {{ #var: SCR }} + 1 }} }}
-|Definition=Allow back-out of a job after Arrival
+|Definition=Allow Postponement of a job after Arrival
 }}
@@ Line 370: / Line 430: @@
 <tr><td>EPL_CUST_SIGNATORY</td><td>The name of the customer signatory on the job.</td><td>&nbsp;</td><td>&nbsp;</td></tr>
 <tr><td>EPL_SIGNED_UNCHECKED</td><td>An indication whether the customer signed for the goods without checking them first. Note that this field can be used for any check-box entry, as this is configurable.</td><td>&nbsp;</td><td>&nbsp;</td></tr>
 <tr><td>'''EPL_TRAILER_ID'''</td><td>To be used if the vehicle being used to fulfil the job is a Tractor unit, and a trailer ID has been entered by the user.</td><td>&nbsp;</td><td>&nbsp;</td></tr>
 <tr><td>EPL_LAST_CHANGED_DATE</td><td>&nbsp;</td><td>&nbsp;</td><td>N/A</td></tr>

Anw: Added details of Job List and Job Details

2013-01-31T10:43:41Z

Added details of Job List and Job Details

@@ Line 53: / Line 53: @@
 |Definition=Ensure that the correct Partnerlink logo is displayed on the device.
 }}
 == Importing Data ==
@@ Line 199: / Line 201: @@
 == Job List ==
 {{SCR
 |Reference={{#var:Reference}}
@@ Line 204: / Line 217: @@
 |Definition=Layout changes to the Job List screen
 }}
 {{SCR
@@ Line 210: / Line 229: @@
 |Definition=Allow force updating of a Load from the Job List screen
 }}
 {{SCR
@@ Line 217: / Line 270: @@
 }}
 {{SCR
 |Reference={{#var:Reference}}
 |SCRNo={{ #vardefineecho: SCR | {{ #expr: {{ #var: SCR }} + 1 }} }}
-|Definition=Remove facility to Cancel a Job
+|Definition=Force viewing of Special Instructions on Starting Job
 }}
 {{SCR
 |Reference={{#var:Reference}}
 |SCRNo={{ #vardefineecho: SCR | {{ #expr: {{ #var: SCR }} + 1 }} }}
-|Definition=Force viewing of Special Instructions on Starting Job
+|Definition=Allow force updating of a Job while in progress
 }}
 {{SCR
 |Reference={{#var:Reference}}
 |SCRNo={{ #vardefineecho: SCR | {{ #expr: {{ #var: SCR }} + 1 }} }}
-|Definition=Allow force updating of a Job while in progress
+|Definition=Remove facility to Cancel a Job
 }}
 == Delivery ==