CALIDUS EPOD Overview - Revision history

Anw: Minor formatting changes.

2020-03-05T15:06:39Z

Minor formatting changes.

← Older revision		Revision as of 17:06, 5 March 2020
Line 8:		Line 8:
	* Database.		* Database.

	[[File:EPOD-Overview-1.PNG\|border]]		[[File:EPOD-Overview-1.PNG\|900px\|border]]
	<!-- NEW PAGE -->		<!-- NEW PAGE -->
	== Server ==		== Server ==

Anw: Minor correction

2020-03-05T15:04:11Z

Minor correction

← Older revision		Revision as of 17:04, 5 March 2020
Line 261:		Line 261:
	The system uses Microsoft SQL Server 2018.		The system uses Microsoft SQL Server 2018.

	~~Application is also compatible with~~
	* Oracle 11g databases.
	* Oracle MySQL 5.1 community and enterprise editions
	<noinclude>		<noinclude>
	[[Category: WI 287575 EPOD Development and Release Process\|010]]		[[Category: WI 287575 EPOD Development and Release Process\|010]]
	</noinclude>		</noinclude>

Anw: v4.5 - Rewrite.

2020-03-05T15:02:45Z

v4.5 - Rewrite.

Show changes

Anw at 09:45, 18 September 2014

2014-09-18T09:45:00Z

← Older revision		Revision as of 11:45, 18 September 2014
Line 29:		Line 29:
	* Microsoft .NET Framework 3.5/4.0		* Microsoft .NET Framework 3.5/4.0
	* Database (Recommended Microsoft SQL Server)		* Database (Recommended Microsoft SQL Server)
	{{Note}} The Express edition of Microsoft SQL Server can be used for the system, as ~~the~~ no enterprise-level components are used. However, there are size and connection limitations of the Express product that may limit the number of users or the amount of data that can be comfortably stored over time. OBS Logistics recommends the Web Server edition, which removes size and connectivity limitations without the full Enterprise level costs or tools.		{{Note}} The Express edition of Microsoft SQL Server can be used for the system, as no enterprise-level components are used. However, there are size and connection limitations of the Express product that may limit the number of users or the amount of data that can be comfortably stored over time. OBS Logistics recommends the Web Server edition, which removes size and connectivity limitations without the full Enterprise level costs or tools.

	Optional Software:		Optional Software:
Line 85:		Line 85:
	==PDA Client==		==PDA Client==
	The ''CALIDUS'' ePOD/eSERV PDA Client application handles all of the operational functionality for the ePOD system.		The ''CALIDUS'' ePOD/eSERV PDA Client application handles all of the operational functionality for the ePOD system.

	The system is available on the following platforms, with similar functionality across all:		The system is available on the following platforms, with similar functionality across all:
	* {{PDAType\|WinMo=Y}} Windows Mobile 6/6.5		* {{PDAType\|WinMo=Y}} Windows Mobile 6/6.5

Anw at 10:26, 11 June 2013

2013-06-11T10:26:01Z

← Older revision		Revision as of 12:26, 11 June 2013
Line 28:		Line 28:
	* Remote Support capability (Microsoft RDS over VPN recommended)		* Remote Support capability (Microsoft RDS over VPN recommended)
	* Microsoft .NET Framework 3.5/4.0		* Microsoft .NET Framework 3.5/4.0
	* Database (~~MySQL~~, ~~SQL~~ Server, ~~ORACLE)~~		* Database (Recommended Microsoft SQL Server)
			{{Note}} The Express edition of Microsoft SQL Server can be used for the system, as the no enterprise-level components are used. However, there are size and connection limitations of the Express product that may limit the number of users or the amount of data that can be comfortably stored over time. OBS Logistics recommends the Web Server edition, which removes size and connectivity limitations without the full Enterprise level costs or tools.

	Optional Software:		Optional Software:

Anw at 09:21, 20 May 2013

2013-05-20T09:21:39Z

← Older revision		Revision as of 11:21, 20 May 2013
Line 255:		Line 255:
	<noinclude>		<noinclude>
	[[Category: WI 287575 EPOD Development and Release Process\|010]]		[[Category: WI 287575 EPOD Development and Release Process\|010]]
	~~[[Category: OV 287575 CALIDUS ePOD Functionality\|010]]~~
	</noinclude>		</noinclude>

Anw at 09:18, 20 May 2013

2013-05-20T09:18:23Z

← Older revision		Revision as of 11:18, 20 May 2013
Line 253:		Line 253:
	* Oracle 11g databases.		* Oracle 11g databases.
	* Oracle MySQL 5.1 community and enterprise editions		* Oracle MySQL 5.1 community and enterprise editions
			<noinclude>
	[[Category: WI 287575 EPOD Development and Release Process\|010]]		[[Category: WI 287575 EPOD Development and Release Process\|010]]
	[[Category: OV 287575 CALIDUS ePOD Functionality\|010]]		[[Category: OV 287575 CALIDUS ePOD Functionality\|010]]
			</noinclude>

Anw: Expanded Admin and Import Export functionality.

2013-05-20T08:59:53Z

Expanded Admin and Import Export functionality.

← Older revision		Revision as of 10:59, 20 May 2013
Line 45:		Line 45:
	* To create and maintain reference data for the system:		* To create and maintain reference data for the system:
	** '''Reason Codes''' - used for the exception process when cancelling Jobs or changing collected/delivered items or products.		** '''Reason Codes''' - used for the exception process when cancelling Jobs or changing collected/delivered items or products.
	** '''Service Products''' - ~~products~~ used during the Service processes.		** '''Service Products''' - Products used during the Service processes.
			** '''Service Activities''' - Activities that can take place during a Service
	** '''Vehicles''' - including Vehicle Check information, last used by, last checked, last location, etc.		** '''Vehicles''' - including Vehicle Check information, last used by, last checked, last location, etc.
	** '''Customers''' - address information can be stored against customers for reuse, or job addresses maintained ad-hoc.		** '''Customers''' - address information can be stored against customers for reuse, or job addresses maintained ad-hoc.
Line 52:		Line 53:
	** '''Sites''' - the basic grouping of jobs and loads. Multiple sites can be configured separately on the same system.		** '''Sites''' - the basic grouping of jobs and loads. Multiple sites can be configured separately on the same system.
	** '''Job Groups''' - grouping Jobs of similar settings or customer groups together.		** '''Job Groups''' - grouping Jobs of similar settings or customer groups together.
	** '''Users''' - both of the ePOD devices and Admin system itself.		** '''Users''' - both of the ePOD devices and Admin system itself, including the maintenance of which groups the user has access to view and amend. The Audit trail of communications from a device is also viewable.
			** '''Auto-Export''' - configuration of automatic import and export processes, for 3rd-party configuration. Supports a generic XML interface and many bespoke interfaces through flat-file and FTP transfer. The Audit trail of transactions is also viewable. Please see the details of import and export in a later section.
	* To create Jobs of all types and group them together onto Loads (worklists).		* To create Jobs of all types and group them together onto Loads (worklists).
	* To assign Loads to Users.		* To assign Loads to Users.
			* To Upload Loads and Jobs into the system from Spreadsheet files.
	* To view and edit the Jobs and Loads created.		* To view and edit the Jobs and Loads created.
	* To print or email a completion report in the configured style (POD, POC, Service/Work Report).		* To print or email a completion report in the configured style (POD, POC, Service/Work Report).
Line 60:		Line 63:
	* To see basic user tracking information, if available.		* To see basic user tracking information, if available.
	* To view results of Vehicle Checks.		* To view results of Vehicle Checks.
			* To view Vehicle and Site Product Levels.
			* Service-specific functionality includes:
			** Service Invoice flagging (to indicate invoicing has taken place).
			** Service Job screen with Service-specific search criteria.

	The system is built using Microsoft ASP.NET and is hosted on a Microsoft web server running Internet Information Services (IIS), backed by .NET 3.5/4.0.		The system is built using Microsoft ASP.NET and is hosted on a Microsoft web server running Internet Information Services (IIS), backed by .NET 3.5/4.0.
Line 69:		Line 76:
	The system has been tested on multiple versions of:		The system has been tested on multiple versions of:
	* Microsoft Internet Explorer (8 and above)		* Microsoft Internet Explorer (8 and above)
	* Mozilla Firefox (3~~-11~~)		* Mozilla Firefox (3 and above)
	* Google Chrome		* Google Chrome
	* Opera		* Opera
Line 176:		Line 183:

	==Import/Export==		==Import/Export==
	Import of data into the system can be through ~~two~~ mechanisms:		Import of data into the system can be through several mechanisms:
	* Web Services standard interface		* Web Services standard interface
	* Bespoke manual file upload, through CSV or Microsoft Excel file		* Bespoke manual file upload, through CSV or Microsoft Excel file
			* Bespoke automatic file upload, through CSV, XML or Microsoft Excel file

	The Web Services are hosted as part of the main ''CALIDUS'' ePOD server, are written in Microsoft C#.NET and run as SOAP or HTML Web Services. Data is formatted in a strongly-typed XML file, validated by a full XSD. Data can be passed either as a string or as an XML object.		The Web Services are hosted as part of the main ''CALIDUS'' ePOD server, are written in Microsoft C#.NET and run as SOAP or HTML Web Services. Data is formatted in a strongly-typed XML file, validated by a full XSD. Data can be passed either as a string or as an XML object.
Line 184:		Line 192:
	The data defined in this XSD can be modified by development for customers who require additional data sent to and from the ''CALIDUS'' ePOD system.		The data defined in this XSD can be modified by development for customers who require additional data sent to and from the ''CALIDUS'' ePOD system.

	The Bespoke manual file ~~upload is~~ written on demand for customers who require it.		The Bespoke automatic and manual file uploads are written on demand for customers who require it.

			The standard Web Services import interface supports:
			* Loads
			* Jobs (stand-alone or within a Load)
			** Collections
			** Deliveries
			*** Containers (Pallets, boxes, etc)
			*** Products (both within containers and loose products)
			** Services
			* Standing Data
			** Users
			** Vehicles
			** Service Products
			** Customers
			** Reason Codes

	Export of data from the system can be through several mechanisms:		Export of data from the system can be through several mechanisms:
Line 192:		Line 215:

	Web Services are supplied for external systems to request information on Loads and Jobs, by ID or Date Since. The Web Services are hosted as part of the main ''CALIDUS'' ePOD server, are written in Microsoft C#.NET and run as SOAP or HTML Web Services. Response Data is formatted in a strongly-typed XML file, validated by a full XSD.		Web Services are supplied for external systems to request information on Loads and Jobs, by ID or Date Since. The Web Services are hosted as part of the main ''CALIDUS'' ePOD server, are written in Microsoft C#.NET and run as SOAP or HTML Web Services. Response Data is formatted in a strongly-typed XML file, validated by a full XSD.

			Standard requested data to export supports:
			* Loads (including all Jobs underneath) by ID or Date
			* Jobs by ID or Date
			* Current Vehicle information

	Auto-export of data can be configured to push the XML data automatically to the client system, via 2 mechanisms:		Auto-export of data can be configured to push the XML data automatically to the client system, via 2 mechanisms:
Line 200:		Line 228:

	This process can also (if configured) automatically produce and email Completion Documents (defined POD, POC or Service reports) to customers, on successful completion of a job.		This process can also (if configured) automatically produce and email Completion Documents (defined POD, POC or Service reports) to customers, on successful completion of a job.

			The Auto-export process supports:
			* Automatic emailing of Completion reports to customers (if configured)
			* Load (header or with all Job information)
			* Jobs (Completed or Cancelled) with all details
			* Palletforce
			* OEM bespoke interfaces
			* Other OBS Logistics products

	The Auto-Export process is run as a scheduled task on the main ''CALIDUS'' ePOD server and are written in Microsoft C#.NET as a Windows Executable Application.		The Auto-Export process is run as a scheduled task on the main ''CALIDUS'' ePOD server and are written in Microsoft C#.NET as a Windows Executable Application.

Anw at 11:21, 23 April 2013

2013-04-23T11:21:45Z

← Older revision		Revision as of 13:21, 23 April 2013
Line 78:		Line 78:
	The ''CALIDUS'' ePOD/eSERV PDA Client application handles all of the operational functionality for the ePOD system.		The ''CALIDUS'' ePOD/eSERV PDA Client application handles all of the operational functionality for the ePOD system.
	The system is available on the following platforms, with similar functionality across all:		The system is available on the following platforms, with similar functionality across all:
	* Windows Mobile 6/6.5		* {{PDAType\|WinMo=Y}} Windows Mobile 6/6.5
	* Android (2.1 and above)		* {{PDAType\|Android=Y}} Android (2.1 and above)
	* iOS devices (in development)		* {{PDAType\|iOS=Y}} iOS devices (in development)
			{{Note}} Device-specific functionality is noted below with these tags.

	The PDA client allows users to connect and receive load data, consisting of a load (worklist) and a series of associated jobs. It provides the functionality to process and complete these jobs electronically in the field. The PDA Client allows processing of Services, Collections and Deliveries. The PDA Client is reliant on a network connection either GPRS or Wi-Fi to retrieve load data, but is not reliant on a connection to complete them, as once jobs are complete, data will be stored on the device until the next time the device has a connection and the application is running. Static data (such as site information) will be stored locally – this is downloaded once during the login process, if a connection is present and the data requires updating.		The PDA client allows users to connect and receive load data, consisting of a load (worklist) and a series of associated jobs. It provides the functionality to process and complete these jobs electronically in the field. The PDA Client allows processing of Services, Collections and Deliveries. The PDA Client is reliant on a network connection either GPRS or Wi-Fi to retrieve load data, but is not reliant on a connection to complete them, as once jobs are complete, data will be stored on the device until the next time the device has a connection and the application is running. Static data (such as site information) will be stored locally – this is downloaded once during the login process, if a connection is present and the data requires updating.
Line 109:		Line 110:
	*** Instructions (force view)		*** Instructions (force view)
	** Allow Call		** Allow Call
	** Allow Navigation		** Allow Navigation (software-dependant)
	** Allow SMS		** {{PDAType\|Android=Y}} Allow SMS
	** Allow navigation to another job ~~(WinMo only)~~		** {{PDAType\|WinMo=Y}} Allow navigation to another job
	** Cancel Job		** Cancel Job
	** Auto-refresh		** Auto-refresh
Line 126:		Line 127:
	*** Container and Product		*** Container and Product
	*** Loose products		*** Loose products
	*** Ad-hoc Collection		*** {{PDAType\|WinMo=Y}} Ad-hoc Collection
	** Forced positive action against Containers/Products (i.e. must scan, must cancel)		** Forced positive action against Containers/Products (i.e. must scan, must cancel)
	** Configurable Container and Product Grid (not Windows Mobile)		** Configurable Container and Product Grid (not Windows Mobile)
Line 132:		Line 133:
	* Service		* Service
	** Configurable Tabbed processes:		** Configurable Tabbed processes:
	*** Activities ~~Tab~~		*** Activities
	*** Pre- and Post-work Checks		*** Pre- and Post-work Checks
	*** Info - key data for that service		*** Info - key data for that service
	*** Installed/Removed Products		*** Installed/Removed Products
	*** MC References Entry ~~tab~~ (e.g. serial number capture, up to 5 with dialogue)		*** MC References Entry (e.g. serial number capture, up to 4 with dialogue)
	*** Diagnosis entry, plus configurable check box entry (up to 4, dependant on client)		*** Diagnosis entry, plus configurable check box entry (up to 4, dependant on client)
	** Validation on entered details		** Validation on entered details
Line 144:		Line 145:
	** Configurable Engineer and Driver Signature		** Configurable Engineer and Driver Signature
	** Enter Signatory		** Enter Signatory
	** Configurable T&Cs display, with up to 3 configurable ~~checkboxes~~ for customer entry.		** Configurable T&Cs display, with up to 3 configurable check boxes for customer entry.
	** Summary of actioned goods ~~(not Windows Mobile)~~		** {{PDAType\|Android=Y\|iOS=Y}} Summary of actioned goods
	** Enter signature and confirm		** Enter signature and confirm
	** Claused Delivery ~~(not Windows Mobile)~~		** {{PDAType\|Android=Y\|iOS=Y}} Claused Delivery
	* Job Completion Photo		* Job Completion Photo
	** Configurable entry of paper document or other job photo		** Configurable entry of paper document or other job photo
Line 157:		Line 158:
	** Qty entry on Product exception		** Qty entry on Product exception
	* Device-specific configuration options available, such as		* Device-specific configuration options available, such as
	** Orientation change		** {{PDAType\|Android=Y\|iOS=Y}} Orientation change
	** Scrolling screens		** {{PDAType\|Android=Y\|iOS=Y}} Scrolling screens
	** GPS-Tagging		** GPS-Tagging
	** GPS-Tracking		** {{PDAType\|Android=Y\|iOS=Y}} GPS-Tracking

	{{Note}} Bespoke functionality has been added regarding vehicle collection and delivery.		{{Note}} Bespoke functionality has been added regarding vehicle collection and delivery.

	The system is written in a variety of languages, depending on platform:		The system is written in a variety of languages, depending on platform:
	* Windows Mobile 6/6.5		* {{PDAType\|WinMo=Y}} Windows Mobile 6/6.5
	** Microsoft .NET Compact Framework, with the intended device configuration of Microsoft Windows Mobile 6.x, and multiple screen resolutions, from 320*240 pixels (QVGA) upwards, in portrait mode only.		** Microsoft .NET Compact Framework, with the intended device configuration of Microsoft Windows Mobile 6.x, and multiple screen resolutions, from 320*240 pixels (QVGA) upwards, in portrait mode only.
	* Android (2.1 and above)		* {{PDAType\|Android=Y}} Android (2.1 and above)
	** Appcelerator Titanium, for all device configurations.		** Appcelerator Titanium, for all device configurations.
	* iOS devices (in development)		* {{PDAType\|iOS=Y}} iOS devices (in development)
	** Appcelerator Titanium, for all device configurations up to iOS 6.0.		** Appcelerator Titanium, for all device configurations up to iOS 6.0.


	The PDA communicates with the main system through Web Services, hosted by the main server. These Web Services are written in C#.NET.		The PDA communicates with the main system through Web Services, hosted by the main server. These Web Services are written in C#.NET.

Anw: Expanded with full feature list

2013-04-22T11:09:21Z

Expanded with full feature list

Show changes