REQ 304784 ACME eServ Requirements - Revision history

Anw: v0.6 - After customer feedback

2013-04-15T14:42:15Z

v0.6 - After customer feedback

Anw: v0.5 - Spell-checked

2013-01-15T16:43:11Z

v0.5 - Spell-checked

← Older revision		Revision as of 18:43, 15 January 2013
Line 4:		Line 4:
	{{#vardefine:System\|''CALIDUS'' ePOD}}		{{#vardefine:System\|''CALIDUS'' ePOD}}
	{{#vardefine:Doc_Title\|Acme eSERV Requirements}}		{{#vardefine:Doc_Title\|Acme eSERV Requirements}}
	{{#vardefine:Version\|0.4}}		{{#vardefine:Version\|0.5}}
	{{#vardefine:Date\|15th January 2013}}		{{#vardefine:Date\|15th January 2013}}
	{{#vardefine:Reference\|304784}}		{{#vardefine:Reference\|304784}}
Line 35:		Line 35:
	<!-- ANY scope or limitations, bulleted. -->		<!-- ANY scope or limitations, bulleted. -->
	* The changes will be made in the latest version ''CALIDUS'' ePOD/eSERV system.		* The changes will be made in the latest version ''CALIDUS'' ePOD/eSERV system.
	* No NAV functionality is specified in this document, although it is referenced. This will all be specified ~~elsewehere~~.		* No NAV functionality is specified in this document, although it is referenced. This will all be specified elsewhere.
	* It is assumed that the standard NAV-ePOD interface is in place, with the following eSERV-specific additions:		* It is assumed that the standard NAV-ePOD interface is in place, with the following eSERV-specific additions:
	** Service Jobs interface		** Service Jobs interface
Line 47:		Line 47:
	** Share Job functionality.		** Share Job functionality.
	** Installation Job Functionality.		** Installation Job Functionality.
	** ~~Micellaneous~~ Image Messaging		** Miscellaneous Image Messaging
	{{ #vardefine: SCR \| 0 }}		{{ #vardefine: SCR \| 0 }}
	<!-- NEW PAGE -->		<!-- NEW PAGE -->
Line 66:		Line 66:
	The current system logs a call, then allocates it to a user and makes it available for the device to pick up.		The current system logs a call, then allocates it to a user and makes it available for the device to pick up.

	All Service jobs of all types will be generated from the NAV system. The exact functionality for this is specified elsewhere, but is mentioned throughout this document to show when ''CALIDUS'' eSERV will be updated with jobs to be completed and will update NAV with jobs completed, audit ~~histoiry~~, etc.		All Service jobs of all types will be generated from the NAV system. The exact functionality for this is specified elsewhere, but is mentioned throughout this document to show when ''CALIDUS'' eSERV will be updated with jobs to be completed and will update NAV with jobs completed, audit history, etc.

	Service jobs are allocated to a user, not a load or vehicle. Therefore the standard ePOD functionality of Load is irrelevant.		Service jobs are allocated to a user, not a load or vehicle. Therefore the standard ePOD functionality of Load is irrelevant.
Line 77:		Line 77:
	}}		}}

	{{Note}} It is possible for parts to be picked specifically for the ~~fulfillment~~ of a Service job. In this instance, it is required that these be passed through to the ''CALIDUS'' eSERV application when the Service is sent to the device.		{{Note}} It is possible for parts to be picked specifically for the fulfilment of a Service job. In this instance, it is required that these be passed through to the ''CALIDUS'' eSERV application when the Service is sent to the device.
	{{SCR\|Reference={{#var:Reference}}\|SCRNo={{ #vardefineecho: SCR \| {{ #expr: {{ #var: SCR }} + 1 }} }}		{{SCR\|Reference={{#var:Reference}}\|SCRNo={{ #vardefineecho: SCR \| {{ #expr: {{ #var: SCR }} + 1 }} }}
	\|Definition=Send Picked Service Products to the PDA.		\|Definition=Send Picked Service Products to the PDA.
Line 111:		Line 111:
	A call is raised against specific equipment, not just a customer.		A call is raised against specific equipment, not just a customer.

	Helpdesk raising the call can process payments over the phone from March/April onwards. A text message will be sent to the engineer with the details of the customer and the contact details. The engineer will contact the customer.		{{Note}} The Helpdesk raising the call can process payments over the phone from March/April onwards. A text message will be sent to the engineer with the details of the customer and the contact details. The engineer will contact the customer.

	The engineer chooses an option to create a new job.		The engineer chooses an option to create a new job.
Line 293:		Line 293:
	[[File:ACME-304784-11.PNG\|border]]		[[File:ACME-304784-11.PNG\|border]]

	Clicking on one of the products in the grid will show the details in a ~~popup~~ screen:		Clicking on one of the products in the grid will show the details in a pop-up screen:
	* Product + description - Display fields only.		* Product + description - Display fields only.
	* Condition - A drop-down List of Conditions Code. Required entry.		* Condition - A drop-down List of Conditions Code. Required entry.
Line 354:		Line 354:
	{{Note}}This has been marked as out of scope of this project.		{{Note}}This has been marked as out of scope of this project.

	{{Note}} Should an installation job be allocated directly to an Engineer, rather than being completed through Job Sharing, the job ~~conpletion~~ process will function identically to the Service type jobs.		{{Note}} Should an installation job be allocated directly to an Engineer, rather than being completed through Job Sharing, the job completion process will function identically to the Service type jobs.

	In normal operation:		In normal operation:
Line 468:		Line 468:
	The NAV system will be modified to provide functionality based on this information. This is specified elsewhere.		The NAV system will be modified to provide functionality based on this information. This is specified elsewhere.

	==~~Logoff~~ System==		==Log-off System==
	A user can choose to exit the system at any time, by clicking Exit from the Job List screen. If they do, they will be prompted to confirm.		A user can choose to exit the system at any time, by clicking Exit from the Job List screen. If they do, they will be prompted to confirm.

	If there is any unsent information at this time, the unit will keep attempting to send the information before it exits. It will also add a ~~Logoff~~ message to the server.		If there is any unsent information at this time, the unit will keep attempting to send the information before it exits. It will also add a Log-off message to the server.
	{{SCR\|Reference={{#var:Reference}}\|SCRNo={{ #vardefineecho: SCR \| {{ #expr: {{ #var: SCR }} + 1 }} }}		{{SCR\|Reference={{#var:Reference}}\|SCRNo={{ #vardefineecho: SCR \| {{ #expr: {{ #var: SCR }} + 1 }} }}
	\|Definition=~~Logoff~~ Audit Message.		\|Definition=Log-off Audit Message.
	}}		}}
	This message will be used to audit the date and time the user logged off the ~~syste~~, will be sent to NAV and will be used as part of the Timesheet system. This is specified elsewhere.		This message will be used to audit the date and time the user logged off the system, will be sent to NAV and will be used as part of the Timesheet system. This is specified elsewhere.

	==Service Report==		==Service Report==
	The service report will be written in NAV and will require invoicing information. This is specified elsewhere.		The service report will be written in NAV and will require invoicing information. This is specified elsewhere.

	However, a simple generic Service Report format will be available within ~~EPOD~~ to show:		However, a simple generic Service Report format will be available within ''CALIDUS'' eSERV to show:
	* Engineer information		* Engineer information
	* Customer information		* Customer information
Line 493:		Line 493:
	All configuration within ''CALIDUS'' eSERV regarding automatic production and emailing of these reports will be disabled, as they are being produced through NAV.		All configuration within ''CALIDUS'' eSERV regarding automatic production and emailing of these reports will be disabled, as they are being produced through NAV.

	==~~Micellaneous~~ Image Messaging==		==Miscellaneous Image Messaging==
	Add miscellaneous imaging to any job.		Add miscellaneous imaging to any job.

	{{SCR\|Reference={{#var:Reference}}\|SCRNo={{ #vardefineecho: SCR \| {{ #expr: {{ #var: SCR }} + 1 }} }}		{{SCR\|Reference={{#var:Reference}}\|SCRNo={{ #vardefineecho: SCR \| {{ #expr: {{ #var: SCR }} + 1 }} }}
	\|Definition=~~Micellaneous~~ Image Messaging.		\|Definition=Miscellaneous Image Messaging.
	}}		}}
	{{Note}}This has been marked as out of scope of this project. There are several ex-app solutions that already have this functionality (e.g. MSN Messenger, MMS messaging, etc).		{{Note}}This has been marked as out of scope of this project. There are several ex-app solutions that already have this functionality (e.g. MSN Messenger, MMS messaging, etc).
Line 631:		Line 631:
	{{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=Services		\|Area=Services
	\|Description=~~Logoff~~ Audit Message.		\|Description=Log-off Audit Message.
	\|Estimate=0		\|Estimate=0
	\|Notes=		\|Notes=
Line 645:		Line 645:
	{{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=Services		\|Area=Services
	\|Description=~~Micellaneous~~ Image Messaging		\|Description=Miscellaneous Image Messaging
	\|Estimate=18.25		\|Estimate=18.25
	\|Notes=1		\|Notes=1

Anw: Changed Survey functionality.

2013-01-15T16:34:36Z

Changed Survey functionality.

← Older revision		Revision as of 18:34, 15 January 2013
Line 426:		Line 426:
	* Replace Sell Price		* Replace Sell Price
	* Distance to Tee		* Distance to Tee

	{{note}} Certain of the fields may require drop-down list entry. These may be either hard-coded into the system, maintained as reason codes within NAV and passed to ''CALIDUS'' eSERV, or new descriptive lookups maintained by the user.

	{{note}} These survey fields will be maintained and stored as XML data within the database (i.e. CALIDUS eSERV can pass the data on, but not access the data directly), allowing the items requested during a survey to be quickly changed without a product modification.		{{note}} These survey fields will be maintained and stored as XML data within the database (i.e. CALIDUS eSERV can pass the data on, but not access the data directly), allowing the items requested during a survey to be quickly changed without a product modification.

Anw: Changed Survey functionality.

2013-01-15T16:18:23Z

Changed Survey functionality.

← Older revision		Revision as of 18:18, 15 January 2013
Line 91:		Line 91:

	If the vehicle being used has not been checked recently, the unit will direct the user to complete the Vehicle Checks. {{Note}} It is expected that Vehicle Checks will be in use and configured as always being required, at every logon. However, the configuration of the Vehicle Checks are part of the standard system, and can removed or modified as required. Please see the Admin and PDA user guides for details of what may be configured.		If the vehicle being used has not been checked recently, the unit will direct the user to complete the Vehicle Checks. {{Note}} It is expected that Vehicle Checks will be in use and configured as always being required, at every logon. However, the configuration of the Vehicle Checks are part of the standard system, and can removed or modified as required. Please see the Admin and PDA user guides for details of what may be configured.

			{{Note}} If configured and used, the information is stored in ''CALIDUS'' eSERV only and not interfaced to NAV. If this is required, further NAV development will be required, specified elsewhere.

	If no load has been assigned to your user, the unit will display a message and ask if you want to recheck.		If no load has been assigned to your user, the unit will display a message and ask if you want to recheck.
Line 427:		Line 429:
	{{note}} Certain of the fields may require drop-down list entry. These may be either hard-coded into the system, maintained as reason codes within NAV and passed to ''CALIDUS'' eSERV, or new descriptive lookups maintained by the user.		{{note}} Certain of the fields may require drop-down list entry. These may be either hard-coded into the system, maintained as reason codes within NAV and passed to ''CALIDUS'' eSERV, or new descriptive lookups maintained by the user.

	{{note}} ~~It is possible that these~~ survey fields ~~could~~ be maintained and stored as XML data within the database (i.e. ''CALIDUS'' eSERV can pass the data on, but not access the data directly)~~. Although this would take longer to develop~~, ~~it would lead~~ to a ~~system that allowed for fully~~-~~configurable fields to be entered by~~ the ~~users, different for each Site or Job Group.~~		{{note}} These survey fields will be maintained and stored as XML data within the database (i.e. CALIDUS eSERV can pass the data on, but not access the data directly), allowing the items requested during a survey to be quickly changed without a product modification.

			This data will be passed and stored in NAV - this is specified elsewhere.

			{{Warning}} What functionality is required within the NAV system utilising this information?

	== Timesheet Functionality==		== Timesheet Functionality==

Anw: /* Maintenance Jobs Types Process */

2013-01-15T15:48:02Z

Maintenance Jobs Types Process

← Older revision		Revision as of 17:48, 15 January 2013
Line 308:		Line 308:
	The user will not be able to finish the job unless all products have been marked as checked.		The user will not be able to finish the job unless all products have been marked as checked.

	All other functionality regarding completion of the job (including Signatures) ~~remain~~ unchanged.		All other functionality regarding completion of the job (including Signatures) remains unchanged.

	==Share Job Functionality==		==Share Job Functionality==

Anw: /* Maintenance Jobs Types Process */

2013-01-15T15:45:07Z

Maintenance Jobs Types Process

← Older revision		Revision as of 17:45, 15 January 2013
Line 280:		Line 280:
	* ''Overview''		* ''Overview''
	* ''Maint''		* ''Maint''
	{{Note}} It is possible ~~througfh~~ configuration that there may be a ''Site Survey'' tab added here, if enabled.		{{Note}} It is possible through configuration that there may be a ''Site Survey'' tab added here, if enabled.

	The ''Maint'' tab will display a list of products to be checked, showing:		The ''Maint'' tab will display a list of products to be checked, showing:

Anw at 15:09, 15 January 2013

2013-01-15T15:09:03Z

← Older revision		Revision as of 17:09, 15 January 2013
Line 506:		Line 506:

	{{ #vardefine: SCR \| 0 }}		{{ #vardefine: SCR \| 0 }}
	{{REQ_SCR_Header}}		{{REQ_SCR_Header}}{{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=Services		\|Area=Services
	\|Description=Create Service Loads automatically.		\|Description=Create Service Loads automatically.

Anw: v0.4 - Added images and finished text.

2013-01-15T14:59:07Z

v0.4 - Added images and finished text.

Show changes

Anw: v0.3 - reworked Estimate section

2013-01-15T12:36:24Z

v0.3 - reworked Estimate section

Show changes

Anw: v0.2 - identify out of scope changes

2013-01-15T12:21:06Z

v0.2 - identify out of scope changes

Show changes