REQ 309371 Lanemark eSERV Requirements - Revision history

Anw: v0.5 - Updated with FS estimates; Added feedback and clarification from the customer.

2013-10-04T14:11:21Z

v0.5 - Updated with FS estimates; Added feedback and clarification from the customer.

← Older revision		Revision as of 16:11, 4 October 2013
Line 4:		Line 4:
	{{#vardefine:System\|''CALIDUS'' eSERV}}		{{#vardefine:System\|''CALIDUS'' eSERV}}
	{{#vardefine:Doc_Title\|Lanemark eSERV Requirements}}		{{#vardefine:Doc_Title\|Lanemark eSERV Requirements}}
	{{#vardefine:Version\|0.4}}		{{#vardefine:Version\|0.5}}
	{{#vardefine:Date\|~~28th August~~ 2013}}		{{#vardefine:Date\|4th October 2013}}
	{{#vardefine:Reference\|309371}}		{{#vardefine:Reference\|309371}}
	{{#vardefine:Year\|2013}}		{{#vardefine:Year\|2013}}
Line 139:		Line 139:
	** FD/FDB		** FD/FDB
	** Non-Lanemark		** Non-Lanemark
	* Burner Model - ~~New field.~~ Entered by Admin and Engineer?		* Burner Model - Entered by Admin and Engineer.
	* Burner Serial No - New Field. Entered by Admin rather than Engineer.		* Burner Serial No - New Field. Entered by Admin rather than Engineer.
	* Lanemark Service Item Number - Service ID. Entered by Admin, displayed here.		* Lanemark Service Item Number - Service ID. Entered by Admin, displayed here.
	* Application - ~~{{Warning}}~~ New field. Entered by Engineer.		* Application - New field. Entered by Engineer.
	* Location On Site - ~~{{Warning}} New field.~~ Entered by ~~Admin and~~ Engineer?		* Location On Site - Entered by Engineer.
	* Reason For Site Visit - ~~{{Warning}} New field~~. Entered by Admin, displayed here?		* Reason For Site Visit - Service Type. Entered by Admin, displayed here.

	~~{{Warning}} All may potentially be pre-populated by the office staff, so proper fields against the Service~~.

	If there are multiple serviceable items on the job, the screen also would have navigation buttons left and right of the title (sections 1 and 2), to allow the user to switch between serviceable items. A label showing the record being processed (e.g. "1 or 6") would be shown, allowing the user to see how many there are. The Service ID (LS Number) of the serviceable item will be displayed on the top of the form.		If there are multiple serviceable items on the job, the screen also would have navigation buttons left and right of the title (sections 1 and 2), to allow the user to switch between serviceable items. A label showing the record being processed (e.g. "1 or 6") would be shown, allowing the user to see how many there are. The Service ID (LS Number) of the serviceable item will be displayed on the top of the form.
Line 248:		Line 246:
	* '''Customer Reference No''' - Customer Reference		* '''Customer Reference No''' - Customer Reference
	* '''Site Name''' - Placed in Owner Name		* '''Site Name''' - Placed in Owner Name
	* '''Site Reference Number''' - ~~{{Warning}} Unknown. Could use~~ External Reference?		* '''Site Reference Number''' - External Reference
	* '''Customer Order No''' - Sales Order Number		* '''Customer Order No''' - Sales Order Number
	* '''Site Contact Name''' - from the Customer/Job Address information		* '''Site Contact Name''' - from the Customer/Job Address information
	* '''Site Contact Tel. Number''' - from the Customer/Job Address information		* '''Site Contact Tel. Number''' - from the Customer/Job Address information
	* '''Site Contact Mobile Number''' - {{Warning}} ~~Unknown~~		* '''Site Contact Mobile Number''' - {{Warning}} Awaiting confirmation that this is required. Will be added as part of a {{#var:System}} product modification in the future, but this modification may not be available before go-live.
	* '''Burner Model''' - System Type~~. {{Warning}}~~ Entered by Admin and Engineer?		* '''Burner Model''' - System Type - Entered by Admin and Engineer?
	* '''Burner Serial No''' - ~~{{Warning}} New Field.~~ Entered by Admin rather than Engineer.		* '''Burner Serial No''' - Entered by Admin rather than Engineer.
	* '''Lanemark Service Item Number''' - Service ID. Entered by Admin.		* '''Lanemark Service Item Number''' - Service ID. Entered by Admin, displayed here.
	* '''Application''' - ~~{{Warning}} Unknown~~. Entered by Engineer.		* '''Application''' - New field. Entered by Engineer.
	* '''Location On Site''' - ~~{{Warning}} Unknown.~~ Entered by ~~Admin and~~ Engineer?		* '''Location On Site''' - Entered by Engineer.
	* '''Reason For Site Visit''' - ~~{{Warning}} New field~~		* '''Reason For Site Visit''' - Service Type. Entered by Admin, displayed here.
	* '''Office Instruction''' - Office Instructions		* '''Office Instruction''' - Office Instructions
	* '''Details of Parts/Materials Used During Visit''':		* '''Details of Parts/Materials Used During Visit''':
Line 273:		Line 271:
	* '''Is Burner System Safe For Use''' - New flag for entry against Service.		* '''Is Burner System Safe For Use''' - New flag for entry against Service.
	* Travel Time		* Travel Time
	** '''Day''' - ~~{{Warning}} Mon~~, ~~Tue, etc?~~		** '''Day''' - This is name of the day of the week, from the Arrival Date (below).
	** '''Date''' - Arrival Date		** '''Date''' - Arrival Date
	** '''Start Time''' - Arrival Time		** '''Start Time''' - Arrival Time
Line 285:		Line 283:
	Each will be configurable with the post-work Test Results that are required.		Each will be configurable with the post-work Test Results that are required.

	{{~~Warning~~\|The ~~only check that appears difficult to achieve would be on the~~ TX format~~, where this appears to require a graphic. Could this~~ be a Drop-down List instead, with options Fully Open/Fully Closed~~/Set?}}~~		{{Note\|The TX format field "Position of Exhaust Damper" will be replaced with a Drop-down List instead, with options "Fully Open", "Fully Closed" and a series of percentages. This will be confirmed by the customer. Regardless, this text will be collated into the rest of the test results in a more standard format.}}
	~~{{Warning\|~~"~~Comp~~. ~~Air: Yes" on all formats - Should this~~ be ~~displayed on~~ the ~~device for the user to see? Should it be on the form instead?}}~~		{{Note\|On all formats - strike-through choices (e.g. Yes/No, 1ph/3ph)will display only the value chosen by the engineer.}}
	~~{{Warning\|Test 8 on TX - label error - should this be "Air Pressure Switch Setting at Test Point"?}}~~
	~~{{Warning\|Test 12 on DB - label error - should this be °C/Min/Max? or does this belong to Spray/Bake/Economy?}}~~
	~~{{Warning\|DB range format - as this is different to the others~~, ~~should~~ this be ~~consolidated~~ into the ~~same~~ format?}}
	{{~~Warning~~\|~~All~~ formats - strike-through choices (e.g. Yes/No, 1ph/3ph) ~~- would you just like~~ the value chosen by the engineer ~~to be displayed?~~}}

	<!-- NEW PAGE -->		<!-- NEW PAGE -->
Line 313:		Line 307:
	* '''Date:''' Job Actual Start Date		* '''Date:''' Job Actual Start Date
	* '''Site''' - Site Name		* '''Site''' - Site Name
	* '''Service Job''' - The Service ID {{Warning}} This means that, if there were 6 items to be serviced, there would be 6 Risk Assessments, but they would all have the same (Job-level) service ID? What then is the Lanemark Service Item Number, and why wouldn't this be the item on the Service Risk Assessment form?		* '''Service Job''' - The Service ID
	* '''Date''' - Job Actual Start Date		* '''Date''' - Job Actual Start Date
	* '''Engineer Print''' - User Name		* '''Engineer Print''' - User Name
Line 319:		Line 313:
	* '''Customer Print''' - The Customer Signatory (rather than Customer Contact Name)		* '''Customer Print''' - The Customer Signatory (rather than Customer Contact Name)
	* '''Customer Sign''' - Customer Signature		* '''Customer Sign''' - Customer Signature
			{{Note\|The format will be modified to include the Service Item Number, as the the Risk Assessment form will be produced per each serviceable item.}}

	The definable fields will not be manipulated in any other way than to format it for the report. Note that this means that, if the items are not present in the configuration for the report, this could break the layout of the report and make reports not work. This will affect only jobs completed after the configuration is changed.		The definable fields will not be manipulated in any other way than to format it for the report. Note that this means that, if the items are not present in the configuration for the report, this could break the layout of the report and make reports not work. This will affect only jobs completed after the configuration is changed.
Line 324:		Line 319:
	The signatures on this screen will be taken from the standard Job signatures. If the Risk Assessment passes, only the Engineer signature will be populated.		The signatures on this screen will be taken from the standard Job signatures. If the Risk Assessment passes, only the Engineer signature will be populated.

	If no Risk Assessment was entered into for this Serviceable Item (because the user chose to indicate that they have already been completed through a Method Statement), this section will be ~~empty~~.		If no Risk Assessment was entered into for this Serviceable Item (because the user chose to indicate that they have already been completed through a Method Statement), this section will not be completed by the Engineer - a label will be displayed showing that a method statement has been produced instead.

	<!-- MEDIA LANDSCAPE YES -->		<!-- MEDIA LANDSCAPE YES -->

	= Appendix A: Table of SCRs =		= 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.
Line 333:		Line 327:
	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.
	The Notes column can be used for many things: grouping optional changes, showing whether the client or OBS originated the gap, etc. -->		The Notes column can be used for many things: grouping optional changes, showing whether the client or OBS originated the gap, etc. -->

	~~{{Warning}} This section has not yet been updated to reflect additional developments required since the new version (0.4) was created.~~

	{{ #vardefine: SCR \| 0 }}		{{ #vardefine: SCR \| 0 }}

Anw: /* Appendix A: Table of SCRs */

2013-09-19T15:26:18Z

Appendix A: Table of SCRs

← Older revision		Revision as of 17:26, 19 September 2013
Line 412:		Line 412:
	\|Area=PDA		\|Area=PDA
	\|Description=Allow Cancellation of entire Service Job		\|Description=Allow Cancellation of entire Service Job
	\|Estimate={{#expr: 1.5*1 }}		\|Estimate={{#expr: 4.5*1 }}
	\|Notes=		\|Notes=
	\|Days=Y		\|Days=Y
Line 418:		Line 418:
	\|Area=PDA/Server		\|Area=PDA/Server
	\|Description=Allow Cancellation of single Serviceable Item		\|Description=Allow Cancellation of single Serviceable Item
	\|Estimate={{#expr: 3.0*1 }}		\|Estimate={{#expr: 0*1 }}
	\|Notes=		\|Notes=2
	\|Days=Y		\|Days=Y
	}}{{REQ_SCR_Line\|SCR={{ #vardefineecho: SCR \| {{ #expr: {{ #var: SCR }} + 1 }} }}\|System=eSERV		}}{{REQ_SCR_Line\|SCR={{ #vardefineecho: SCR \| {{ #expr: {{ #var: SCR }} + 1 }} }}\|System=eSERV

Anw at 08:21, 19 September 2013

2013-09-19T08:21:04Z

← Older revision		Revision as of 10:21, 19 September 2013
Line 388:		Line 388:
	\|Area=PDA		\|Area=PDA
	\|Description=Configurable Post-work Checks (for Test Results)		\|Description=Configurable Post-work Checks (for Test Results)
	\|Estimate={{#expr: 3.25*1 }}		\|Estimate={{#expr: 2.75*1 }}
	\|Notes=		\|Notes=
	\|Days=Y		\|Days=Y

Anw at 12:54, 11 September 2013

2013-09-11T12:54:12Z

← Older revision		Revision as of 14:54, 11 September 2013
Line 346:		Line 346:
	\|Area=All		\|Area=All
	\|Description=Multiple Serviceable Items Per Service Job		\|Description=Multiple Serviceable Items Per Service Job
	\|Estimate={{#expr: 10.75*1 }}		\|Estimate={{#expr: 13.75*1 }}
	\|Notes=		\|Notes=
	\|Days=Y		\|Days=Y
Line 352:		Line 352:
	\|Area=PDA		\|Area=PDA
	\|Description=New Info tab fields required (configurable and key data)		\|Description=New Info tab fields required (configurable and key data)
	\|Estimate={{#expr: 3.75*1 }}		\|Estimate={{#expr: 5.25*1 }}
	\|Notes=		\|Notes=
	\|Days=Y		\|Days=Y
Line 358:		Line 358:
	\|Area=PDA		\|Area=PDA
	\|Description=Configurable Pre-work Checks (for Risk Assessment)		\|Description=Configurable Pre-work Checks (for Risk Assessment)
	\|Estimate={{#expr: 5~~.75~~*1 }}		\|Estimate={{#expr: 4.5*1 }}
	\|Notes=		\|Notes=
	\|Days=Y		\|Days=Y
Line 364:		Line 364:
	\|Area=PDA		\|Area=PDA
	\|Description=Complete Pre-work checks before data entry on that Serviceable Item		\|Description=Complete Pre-work checks before data entry on that Serviceable Item
	\|Estimate={{#expr: ~~1.75~~*1 }}		\|Estimate={{#expr: 0*1 }}
	\|Notes=		\|Notes=2
	\|Days=Y		\|Days=Y
	}}{{REQ_SCR_Line\|SCR={{ #vardefineecho: SCR \| {{ #expr: {{ #var: SCR }} + 1 }} }}\|System=eSERV		}}{{REQ_SCR_Line\|SCR={{ #vardefineecho: SCR \| {{ #expr: {{ #var: SCR }} + 1 }} }}\|System=eSERV
Line 394:		Line 394:
	\|Area=PDA		\|Area=PDA
	\|Description=Display Status of Pre-work and Post-work checks on form		\|Description=Display Status of Pre-work and Post-work checks on form
	\|Estimate={{#expr: 0~~.75~~*1 }}		\|Estimate={{#expr: 0*1 }}
	\|Notes=		\|Notes=2
	\|Days=Y		\|Days=Y
	}}{{REQ_SCR_Line\|SCR={{ #vardefineecho: SCR \| {{ #expr: {{ #var: SCR }} + 1 }} }}\|System=eSERV		}}{{REQ_SCR_Line\|SCR={{ #vardefineecho: SCR \| {{ #expr: {{ #var: SCR }} + 1 }} }}\|System=eSERV
	\|Area=All		\|Area=All
	\|Description=Diagnosis to be modified for additional check fields		\|Description=Diagnosis to be modified for additional check fields
	\|Estimate={{#expr: 4.0*1 }}		\|Estimate={{#expr: 3.5*1 }}
	\|Notes=		\|Notes=
	\|Days=Y		\|Days=Y
Line 432:		Line 432:
	Notes:		Notes:
	# All ballpark costs in this document are provided as-is, are legally non-binding and subject to raising a formal change request with OBS Logistics.		# All ballpark costs in this document are provided as-is, are legally non-binding and subject to raising a formal change request with OBS Logistics.
			# These elements have been combined into other SCRs.

	<!-- MEDIA LANDSCAPE NO -->		<!-- MEDIA LANDSCAPE NO -->

Anw: /* Service PDA Process */

2013-09-09T14:53:13Z

Service PDA Process

← Older revision		Revision as of 16:53, 9 September 2013
Line 102:		Line 102:
	Selecting a job from the Job List will show the user the job report and customer contact details, allowing the user to contact the customer (through text or phone), or navigate to the customer's address.		Selecting a job from the Job List will show the user the job report and customer contact details, allowing the user to contact the customer (through text or phone), or navigate to the customer's address.

	The engineer can then choose to start the job, and when they arrive at the site, can ~~being~~ entering the details.		The engineer can then choose to start the job, and when they arrive at the site, can begin entering the details.

	{{Note}} All process up to and including the engineer starting and arriving at the job are generic and described in detail in the user guides, as referenced in the appendices.		{{Note}} All process up to and including the engineer starting and arriving at the job are generic and described in detail in the user guides, as referenced in the appendices.

Anw at 14:46, 9 September 2013

2013-09-09T14:46:31Z

← Older revision		Revision as of 16:46, 9 September 2013
Line 112:		Line 112:
	* Diagnosis		* Diagnosis

	{{Note}} ~~A 'Refresh Job' option will be available within the Service tabs, to allow the user to pick up the latest information, after they have confirmed they are starting the job. This is~~ to pick up any changes on the job made by NAV users after the job has started. Note ~~also~~ that using this option after the user has started processing the job will result in the loss of any entered data up until that point, so care must be taken when using this.		{{Note}} In order to pick up any changes on the job made by NAV users after the job has started, the users can exit the Service (by using the Back key) then click the '''Continue Job''' button. The application will check for any updates on the service and inform the user of any changes. Note that using this option after the user has started processing the job will result in the loss of any entered data up until that point, so care must be taken when using this.

	===Job Details===		===Job Details===
Line 351:		Line 351:
	}}{{REQ_SCR_Line\|SCR={{ #vardefineecho: SCR \| {{ #expr: {{ #var: SCR }} + 1 }} }}\|System=eSERV		}}{{REQ_SCR_Line\|SCR={{ #vardefineecho: SCR \| {{ #expr: {{ #var: SCR }} + 1 }} }}\|System=eSERV
	\|Area=PDA		\|Area=PDA
	\|Description=New Info tab fields required		\|Description=New Info tab fields required (configurable and key data)
	\|Estimate={{#expr: 2.75*1 }}		\|Estimate={{#expr: 3.75*1 }}
	\|Notes=		\|Notes=
	\|Days=Y		\|Days=Y
Line 363:		Line 363:
	}}{{REQ_SCR_Line\|SCR={{ #vardefineecho: SCR \| {{ #expr: {{ #var: SCR }} + 1 }} }}\|System=eSERV		}}{{REQ_SCR_Line\|SCR={{ #vardefineecho: SCR \| {{ #expr: {{ #var: SCR }} + 1 }} }}\|System=eSERV
	\|Area=PDA		\|Area=PDA
	\|Description=Complete Pre-work checks before ~~any other~~ data entry		\|Description=Complete Pre-work checks before data entry on that Serviceable Item
	\|Estimate={{#expr: 1.75*1 }}		\|Estimate={{#expr: 1.75*1 }}
	\|Notes=		\|Notes=
	\|Days=Y		\|Days=Y
	}}{{REQ_SCR_Line\|SCR={{ #vardefineecho: SCR \| {{ #expr: {{ #var: SCR }} + 1 }} }}\|System=eSERV		}}{{REQ_SCR_Line\|SCR={{ #vardefineecho: SCR \| {{ #expr: {{ #var: SCR }} + 1 }} }}\|System=eSERV
	\|Area=PDA		\|Area=PDA/Server
	\|Description=Products filtered based on available Vehicle stock		\|Description=Products filtered based on available Vehicle stock
	\|Estimate={{#expr: 1.5*1 }}		\|Estimate={{#expr: 2.25*1 }}
	\|Notes=		\|Notes=
	\|Days=Y		\|Days=Y
	}}{{REQ_SCR_Line\|SCR={{ #vardefineecho: SCR \| {{ #expr: {{ #var: SCR }} + 1 }} }}\|System=eSERV		}}{{REQ_SCR_Line\|SCR={{ #vardefineecho: SCR \| {{ #expr: {{ #var: SCR }} + 1 }} }}\|System=eSERV
	\|Area=PDA		\|Area=PDA
	\|Description=User-filterable Products based on ~~Group/~~Model		\|Description=User-filterable Products based on Model
	\|Estimate={{#expr: 2.5*1 }}		\|Estimate={{#expr: 2.5*1 }}
			\|Notes=
			\|Days=Y
			}}{{REQ_SCR_Line\|SCR={{ #vardefineecho: SCR \| {{ #expr: {{ #var: SCR }} + 1 }} }}\|System=eSERV
			\|Area=PDA/Server
			\|Description=Product Search/Other Product functionality
			\|Estimate={{#expr: 8.25*1 }}
	\|Notes=		\|Notes=
	\|Days=Y		\|Days=Y
Line 388:		Line 394:
	\|Area=PDA		\|Area=PDA
	\|Description=Display Status of Pre-work and Post-work checks on form		\|Description=Display Status of Pre-work and Post-work checks on form
	\|Estimate={{#expr: .75*1 }}		\|Estimate={{#expr: 0.75*1 }}
	\|Notes=		\|Notes=
	\|Days=Y		\|Days=Y
	}}{{REQ_SCR_Line\|SCR={{ #vardefineecho: SCR \| {{ #expr: {{ #var: SCR }} + 1 }} }}\|System=eSERV		}}{{REQ_SCR_Line\|SCR={{ #vardefineecho: SCR \| {{ #expr: {{ #var: SCR }} + 1 }} }}\|System=eSERV
	\|Area=~~PDA~~		\|Area=All
	\|Description=Diagnosis to be modified for additional check fields		\|Description=Diagnosis to be modified for additional check fields
	\|Estimate={{#expr: 1.75*1 }}		\|Estimate={{#expr: 4.0*1 }}
	\|Notes=		\|Notes=
	\|Days=Y		\|Days=Y
	}}{{REQ_SCR_Line\|SCR={{ #vardefineecho: SCR \| {{ #expr: {{ #var: SCR }} + 1 }} }}\|System=eSERV		}}{{REQ_SCR_Line\|SCR={{ #vardefineecho: SCR \| {{ #expr: {{ #var: SCR }} + 1 }} }}\|System=eSERV
	\|Area=PDA		\|Area=PDA/Server
	\|Description=Diagnosis narrative to become unrestricted field		\|Description=Diagnosis narrative to become unrestricted field
	\|Estimate={{#expr: 0.75*1 }}		\|Estimate={{#expr: 1.5*1 }}
	\|Notes=		\|Notes=
	\|Days=Y		\|Days=Y
	}}{{REQ_SCR_Line\|SCR={{ #vardefineecho: SCR \| {{ #expr: {{ #var: SCR }} + 1 }} }}\|System=eSERV		}}{{REQ_SCR_Line\|SCR={{ #vardefineecho: SCR \| {{ #expr: {{ #var: SCR }} + 1 }} }}\|System=eSERV
	\|Area=PDA		\|Area=PDA
	\|Description=Allow Cancellation of Service Job		\|Description=Allow Cancellation of entire Service Job
	\|Estimate={{#expr: 1.5*1 }}		\|Estimate={{#expr: 1.5*1 }}
			\|Notes=
			\|Days=Y
			}}{{REQ_SCR_Line\|SCR={{ #vardefineecho: SCR \| {{ #expr: {{ #var: SCR }} + 1 }} }}\|System=eSERV
			\|Area=PDA/Server
			\|Description=Allow Cancellation of single Serviceable Item
			\|Estimate={{#expr: 3.0*1 }}
	\|Notes=		\|Notes=
	\|Days=Y		\|Days=Y

Anw at 07:32, 6 September 2013

2013-09-06T07:32:32Z

← Older revision		Revision as of 09:32, 6 September 2013
Line 112:		Line 112:
	* Diagnosis		* Diagnosis

	{{Note}} ~~In order~~ to pick up any changes on the job made by NAV users after the job has started~~, the users can exit the Service (by using the Back key) then click the '''Continue Job''' button. The application will check for any updates on the service and inform the user of any changes~~. Note that using this option after the user has started processing the job will result in the loss of any entered data up until that point, so care must be taken when using this.		{{Note}} A 'Refresh Job' option will be available within the Service tabs, to allow the user to pick up the latest information, after they have confirmed they are starting the job. This is to pick up any changes on the job made by NAV users after the job has started. Note also that using this option after the user has started processing the job will result in the loss of any entered data up until that point, so care must be taken when using this.

	===Job Details===		===Job Details===
Line 139:		Line 139:
	** FD/FDB		** FD/FDB
	** Non-Lanemark		** Non-Lanemark
	* Model - text entry
	* S/No - text entry
	* Burner Model - New field. Entered by Admin and Engineer?		* Burner Model - New field. Entered by Admin and Engineer?
	* Burner Serial No - New Field. Entered by Admin rather than Engineer.		* Burner Serial No - New Field. Entered by Admin rather than Engineer.
Line 353:		Line 351:
	}}{{REQ_SCR_Line\|SCR={{ #vardefineecho: SCR \| {{ #expr: {{ #var: SCR }} + 1 }} }}\|System=eSERV		}}{{REQ_SCR_Line\|SCR={{ #vardefineecho: SCR \| {{ #expr: {{ #var: SCR }} + 1 }} }}\|System=eSERV
	\|Area=PDA		\|Area=PDA
	\|Description=New Info tab fields required ~~(configurable and key data)~~		\|Description=New Info tab fields required
	\|Estimate={{#expr: 3.75*1 }}		\|Estimate={{#expr: 2.75*1 }}
	\|Notes=		\|Notes=
	\|Days=Y		\|Days=Y
Line 365:		Line 363:
	}}{{REQ_SCR_Line\|SCR={{ #vardefineecho: SCR \| {{ #expr: {{ #var: SCR }} + 1 }} }}\|System=eSERV		}}{{REQ_SCR_Line\|SCR={{ #vardefineecho: SCR \| {{ #expr: {{ #var: SCR }} + 1 }} }}\|System=eSERV
	\|Area=PDA		\|Area=PDA
	\|Description=Complete Pre-work checks before data entry ~~on that Serviceable Item~~		\|Description=Complete Pre-work checks before any other data entry
	\|Estimate={{#expr: 1.75*1 }}		\|Estimate={{#expr: 1.75*1 }}
	\|Notes=		\|Notes=
	\|Days=Y		\|Days=Y
	}}{{REQ_SCR_Line\|SCR={{ #vardefineecho: SCR \| {{ #expr: {{ #var: SCR }} + 1 }} }}\|System=eSERV		}}{{REQ_SCR_Line\|SCR={{ #vardefineecho: SCR \| {{ #expr: {{ #var: SCR }} + 1 }} }}\|System=eSERV
	\|Area=PDA~~/Server~~		\|Area=PDA
	\|Description=Products filtered based on available Vehicle stock		\|Description=Products filtered based on available Vehicle stock
	\|Estimate={{#expr: 2.25*1 }}		\|Estimate={{#expr: 1.5*1 }}
	\|Notes=		\|Notes=
	\|Days=Y		\|Days=Y
	}}{{REQ_SCR_Line\|SCR={{ #vardefineecho: SCR \| {{ #expr: {{ #var: SCR }} + 1 }} }}\|System=eSERV		}}{{REQ_SCR_Line\|SCR={{ #vardefineecho: SCR \| {{ #expr: {{ #var: SCR }} + 1 }} }}\|System=eSERV
	\|Area=PDA		\|Area=PDA
	\|Description=User-filterable Products based on Model		\|Description=User-filterable Products based on Group/Model
	\|Estimate={{#expr: 2.5*1 }}		\|Estimate={{#expr: 2.5*1 }}
	~~\|Notes=~~
	~~\|Days=Y~~
	~~}}{{REQ_SCR_Line\|SCR={{ #vardefineecho: SCR \| {{ #expr: {{ #var: SCR }} + 1 }} }}\|System=eSERV~~
	~~\|Area=PDA/Server~~
	~~\|Description=Product Search/Other Product functionality~~
	~~\|Estimate={{#expr: 10*1 }}~~
	\|Notes=		\|Notes=
	\|Days=Y		\|Days=Y
Line 396:		Line 388:
	\|Area=PDA		\|Area=PDA
	\|Description=Display Status of Pre-work and Post-work checks on form		\|Description=Display Status of Pre-work and Post-work checks on form
	\|Estimate={{#expr: 0.75*1 }}		\|Estimate={{#expr: .75*1 }}
	\|Notes=		\|Notes=
	\|Days=Y		\|Days=Y
	}}{{REQ_SCR_Line\|SCR={{ #vardefineecho: SCR \| {{ #expr: {{ #var: SCR }} + 1 }} }}\|System=eSERV		}}{{REQ_SCR_Line\|SCR={{ #vardefineecho: SCR \| {{ #expr: {{ #var: SCR }} + 1 }} }}\|System=eSERV
	\|Area=~~All~~		\|Area=PDA
	\|Description=Diagnosis to be modified for additional check fields		\|Description=Diagnosis to be modified for additional check fields
	\|Estimate={{#expr: 4.0*1 }}		\|Estimate={{#expr: 1.75*1 }}
	\|Notes=		\|Notes=
	\|Days=Y		\|Days=Y
	}}{{REQ_SCR_Line\|SCR={{ #vardefineecho: SCR \| {{ #expr: {{ #var: SCR }} + 1 }} }}\|System=eSERV		}}{{REQ_SCR_Line\|SCR={{ #vardefineecho: SCR \| {{ #expr: {{ #var: SCR }} + 1 }} }}\|System=eSERV
	\|Area=PDA~~/Server~~		\|Area=PDA
	\|Description=Diagnosis narrative to become unrestricted field		\|Description=Diagnosis narrative to become unrestricted field
	\|Estimate={{#expr: 1.5*1 }}		\|Estimate={{#expr: 0.75*1 }}
	\|Notes=		\|Notes=
	\|Days=Y		\|Days=Y
	}}{{REQ_SCR_Line\|SCR={{ #vardefineecho: SCR \| {{ #expr: {{ #var: SCR }} + 1 }} }}\|System=eSERV		}}{{REQ_SCR_Line\|SCR={{ #vardefineecho: SCR \| {{ #expr: {{ #var: SCR }} + 1 }} }}\|System=eSERV
	\|Area=PDA		\|Area=PDA
	\|Description=Allow Cancellation of ~~entire~~ Service Job		\|Description=Allow Cancellation of Service Job
	\|Estimate={{#expr: 1.5*1 }}		\|Estimate={{#expr: 1.5*1 }}
	~~\|Notes=~~
	~~\|Days=Y~~
	~~}}{{REQ_SCR_Line\|SCR={{ #vardefineecho: SCR \| {{ #expr: {{ #var: SCR }} + 1 }} }}\|System=eSERV~~
	~~\|Area=PDA/Server~~
	~~\|Description=Allow Cancellation of single Serviceable Item~~
	~~\|Estimate={{#expr: 3.0*1 }}~~
	\|Notes=		\|Notes=
	\|Days=Y		\|Days=Y

Anw at 15:24, 5 September 2013

2013-09-05T15:24:43Z

← Older revision		Revision as of 17:24, 5 September 2013
Line 354:		Line 354:
	\|Area=PDA		\|Area=PDA
	\|Description=New Info tab fields required (configurable and key data)		\|Description=New Info tab fields required (configurable and key data)
	\|Estimate={{#expr: 2.75*1 }}		\|Estimate={{#expr: 3.75*1 }}
	\|Notes=		\|Notes=
	\|Days=Y		\|Days=Y

Anw at 14:36, 29 August 2013

2013-08-29T14:36:46Z

← Older revision		Revision as of 16:36, 29 August 2013
Line 400:		Line 400:
	\|Days=Y		\|Days=Y
	}}{{REQ_SCR_Line\|SCR={{ #vardefineecho: SCR \| {{ #expr: {{ #var: SCR }} + 1 }} }}\|System=eSERV		}}{{REQ_SCR_Line\|SCR={{ #vardefineecho: SCR \| {{ #expr: {{ #var: SCR }} + 1 }} }}\|System=eSERV
	\|Area=~~PDA~~		\|Area=All
	\|Description=Diagnosis to be modified for additional check fields		\|Description=Diagnosis to be modified for additional check fields
	\|Estimate={{#expr: 1.75*1 }}		\|Estimate={{#expr: 4.0*1 }}
	\|Notes=		\|Notes=
	\|Days=Y		\|Days=Y
	}}{{REQ_SCR_Line\|SCR={{ #vardefineecho: SCR \| {{ #expr: {{ #var: SCR }} + 1 }} }}\|System=eSERV		}}{{REQ_SCR_Line\|SCR={{ #vardefineecho: SCR \| {{ #expr: {{ #var: SCR }} + 1 }} }}\|System=eSERV
	\|Area=PDA		\|Area=PDA/Server
	\|Description=Diagnosis narrative to become unrestricted field		\|Description=Diagnosis narrative to become unrestricted field
	\|Estimate={{#expr: 0.75*1 }}		\|Estimate={{#expr: 1.5*1 }}
	\|Notes=		\|Notes=
	\|Days=Y		\|Days=Y

Anw at 12:57, 29 August 2013

2013-08-29T12:57:12Z

← Older revision		Revision as of 14:57, 29 August 2013
Line 112:		Line 112:
	* Diagnosis		* Diagnosis

	{{Note}} ~~A 'Refresh Job' option will be available within the Service tabs, to allow the user to pick up the latest information, after they have confirmed they are starting the job. This is~~ to pick up any changes on the job made by NAV users after the job has started. Note ~~also~~ that using this option after the user has started processing the job will result in the loss of any entered data up until that point, so care must be taken when using this.		{{Note}} In order to pick up any changes on the job made by NAV users after the job has started, the users can exit the Service (by using the Back key) then click the '''Continue Job''' button. The application will check for any updates on the service and inform the user of any changes. Note that using this option after the user has started processing the job will result in the loss of any entered data up until that point, so care must be taken when using this.

	===Job Details===		===Job Details===
Line 421:		Line 421:
	\|Description=Allow Cancellation of single Serviceable Item		\|Description=Allow Cancellation of single Serviceable Item
	\|Estimate={{#expr: 3.0*1 }}		\|Estimate={{#expr: 3.0*1 }}
	~~\|Notes=~~
	~~\|Days=Y~~
	~~}}{{REQ_SCR_Line\|SCR={{ #vardefineecho: SCR \| {{ #expr: {{ #var: SCR }} + 1 }} }}\|System=eSERV~~
	~~\|Area=PDA~~
	~~\|Description=Allow Refresh of Service Job within Job itself~~
	~~\|Estimate={{#expr: 2.0*1 }}~~
	\|Notes=		\|Notes=
	\|Days=Y		\|Days=Y