FS 305796 Partnerlink EPOD Agreed Product Changes

From Calidus HUB





Aptean Logo.png







OBS Logistics

Partnerlink EPOD Agreed Product Changes

CALIDUS EPOD

17th Jan 2013 - 0.4
Reference: FS 305796











































Functional Overview

Client Requirement

Various changes have been identified as part of the Partnerlink project that either

  • benefit the product or
  • add functionality that should be present in the product.

These items will be completed as part of Product Development.

The items are:

  • Android and Windows applications are different - they should be the same
  • View complete jobs on the PDA, indicate to the user the status of the job
  • Time of Arrival and Time of Departure to be recorded for a job
  • Load Assign by Vehicle ID

Solution Overview

The changes made shall be:

  • Windows PDA Client
    • Add a button to the Job List screen to allow the user to toggle between "Show All jobs" and "Show Outstanding Jobs"
    • Add functionality to mark a job as status I (In Progress) on the local database.
    • Alter the Job List screen to show the status and In Progress.
  • Android and Windows Clients
    • Configuration to alter the Start Job button to:
      • Change to an Arrive Button
      • When clicked as Arrived, to stamp the date/time of arrival onto the Job and send this to the server.
    • Add status "Complete with Amendments"
  • Server
    • Add Actual Arrival Date/Time to Jobs
    • Amend Export to include all new field.
    • Amend Import to allow Vehicle ID to be assigned
    • Amend PDA Load Request to assign Loads by Vehicle if no loads are assigned to the User.
  • Admin
    • Display Job status of "Complete with Amendments"
    • Display Arrival Date/Time fields against the Job

Scope

No changes will be entered into for:

  • Any further modification to the Windows client to add Android-specific functionality - the programming languages used for each client have different capabilities. Although all efforts will be made to ensure that the functionality set on the two clients is the same, it should be noted that some functionality may be impossible to achieve on one of the clients
  • Departure Times.


Set-up

Pre-requisites

Menu Structure

Data

EPOD_JOB:

  • EPL_AMENDED_FLAG, nvarchar(1), values 'Y' or 'N', default 'N'.
  • EPL_ARRIVAL_DATE, int.
  • EPL_ARRIVAL_TIME, int.

EPOD_CONTAINER:

  • EPL_AMENDED_FLAG, nvarchar(1), values 'Y' or 'N', default 'N'.

EPOD_SITE:

  • EPL_ARRIVAL_FLAG, nvarchar(1), values 'Y' or 'N', default 'N'.


Functional Description

Complete Amended Status

Note Note: Both the Windows and Android PDA clients will be modified in this change.

When a product is cancelled or had their quantity changed, the PDA client will mark the parent Container and Job records with a status showing that the job was completed with amendments, via a new flag held against the Container and Job records (EPL_AMENDED_FLAG).

When a container is cancelled, the PDA client mark the job record with a status showing that the job was completed with amendments, via a new flag held against the Job record (EPL_AMENDED_FLAG).

Note Note: The system may need to refresh the PDA_JOB object held by the screen that updates the Job to complete at the end. If not, the value of the EPL_AMENDED_FLAG will not be present in the original Job object and therefore and Update of the PDA_JOB object will reset the flag back to the original value BEFORE it was set in PDA_CONTAINER or PDA_PRODUCT

The new flag will be sent back to the Server and saved on the database there - the EPOD_JOB and EPOD_CONTAINER DAL objects will be modified to add the new flag, along with the database packages in both MSSQL and MYSQL formats.

The Admin Job and Job Product and Containers screens will be modified to display the new Complete Amended status.

Note Note: At this time, the Export process will not be modified to include this new flag.

Display In-Progress Status

The Windows PDA Client will be modified to mark the Job status as I (In Progress) when Locking the job (i.e. Clicking the Start button from the Job Details screen). There should only be 1 job set to I on the whole Load, so if there is one already set, this job should have its status set back to P.

Note Note: This should be achieved by writing a new method InProgress to the PDA_JOB DAL object, to:

  • If the status of the current job is not In Progress
    • loop through for any jobs in progress, and if found and not the job being set here, set back to Pending and exit the loop
    • set the status of the current job to "I"
    • Update the job.

This method should be called on completing the send of the Job Lock Request.

Lines on the Windows PDA Client Job List grid may be configured to have a job status added at the left of the grid row, showing a single character: C - Complete, A - Complete Amended, X - cancelled, I - in progress, P - Pending. The configuration of this will be added to the Admin Site configuration screen, allowing Status to be selected. The column heading and width will be set to that configured.

Show All Jobs

The Windows PDA Client will be modified to have a toggle button on the Job List screen to allow the user to show either just outstanding jobs or all jobs.

Initially, the screen will be shown showing only outstanding jobs (i.e. jobs at status P or I), with the button displaying the text "Show All Jobs". When in this mode, the screen will work as it does now.

When the button in pressed, the grid will be refreshed, showing all jobs at all statuses. The text of the button will then change to "Show Outstanding Jobs"

User will be able to click any job at any status and see it in the Job Details screen.

The PDA Job Details screen will be modified to display the status of the job.

The user will not be able to start any jobs that are not status I or P - a message should be displayed informing that the job can't be started, as the job is already at status {status description}.

Arrival Date/Time

Note Note: Both the Windows and Android PDA clients will be modified in this change.

The EPOD_JOB DAL object, database table and packages will be modified to add EPL_ARRIVAL_DATE and EPL_ARRIVAL_TIME.

The EPOD_SITE DAL object, database table and packages will be modified to add EPL_ARRIVAL_FLAG.

The Admin Load maintenance screen will be modified to add the maintenance of the EPL_ARRIVAL_FLAG to the PDA tab group. This will have a label of "Capture Arrival Times".

The Admin Job Details screen will be modified to display the Arrival Date and Time, if the site is configured for this.

The EPOD Logon webservice will be modified to add the new flag to the message.

The PDA_SITE DAL object and database table will be modified to store the new EPL_ARRIVAL_FLAG flag.

The PDA client Log-on Response message will be changed to add the new flag to the database.

If the new flag's value is "N", no functionality will change.

If the new flag's value is "Y", the functionality of the current Start button will be modified.

When the button is clicked, currently a job lock message is sent and the status will be set to "I". This will not change.

At this time (or when a job is started at status "I" and the Arrival Time is not yet set), the button will have its text modified to "Arrived".

When the button is clicked is this state:

  • the PDA Job Arrival Date and Time will be updated
  • another Job Lock message will be sent, with a new parameter ARRIVAL being set to "Y" showing that this is an arrival message). Note Note: no update is required on this message, so this can be sent on the queue, not immediately.
  • the screens required to process the job (i.e. Collection, Delivery or Service) will be shown.

The Server Job Lock Request processor will update the Arrival Date and Time of the Job.

At this time (or when a job is started at status "I" and the Arrival Time is set), the button will have its text modified to "Continue Job".

The PDA Job List and Job Details screens will be modified to not allow the user to start another job until this job (with a status of In Progress and an Arrival Time) is cancelled or completed.

The PDA Job Update message will be modified to include the Arrival Date and Time, and the Server Job Update processor will also be modified to save this information to the Job.

The Job Export processes will be modified to include these new fields.

Note Note: the Export XSD and mapping spreadsheets must be modified to reflect the changes described.

Load Assign by Vehicle ID

The Import process will be modified to allow a now optional tag EPL_VEHICLE_ID to be specified in EPOD_LOAD tags.

Note Note: If the Vehicle ID does not exist, this should be created - see further specs for details on this.

The Response to a PDA Load Request message should check for Loads assigned to the user, as normal. If none are found, this should check for loads assigned to the Vehicle that are unassigned to any other user. If found, these should be assigned to the user and returned on the message, as per normal.


Appendix A: Table of SCRs and Ballpark Estimates

SCR#SystemAreaDescriptionEstimate (Days)Notes
1 EPOD PDA/Admin Complete Amended Status  3.50 
2 EPOD PDA Display In-Progress Status  1.25 
3 EPOD PDA Show All Jobs  1.50 
4 EPOD PDA/Server/
Admin/Export		 Arrival Date/Time  8.00 
5 EPOD Server/Import Load Assign by Vehicle ID  1.00 


Notes:

  1. Any high level ballpark estimates for development are based on the basic information provided and are subject to detailed design and creation of an SCR.


Appendix B: Quote & Document References

Cost Details
Activity No. of Days Rate per Day (£) Cost (£ Exc. VAT)
Requirements 0.00 0 £0.00
Change Request Evaluation 0.00 0 £0.00
Functional Specification 1.00 0 £0.00
Technical Specification 0.00 0 £0.00
Development 15.25 0 £0.00
Testing and Release 3.00 0 £0.00
Implementation 0.00 0 £0.00
Project Management First argument to "number_format" must be a number. 0 £First argument to "number_format" must be a number.
 
TOTAL First argument to "number_format" must be a number.   £First argument to "number_format" must be a number.
Estimate excludes training, release to live and go live support.

B.1 References

Ref NoDocument Title & IDVersionDate
1   


B.2 Glossary

Term Definition
EPOD Electronic Proof of Delivery. The OBS EPOD system is CALIDUS ePOD.
CALIDUS eSERV The OBS mobile system to complete Service functionality in the field. This is part of the CALIDUS ePOD system.
PDA The mobile device on which the C-ePOD system will run in the field. This can be a Phone, EDA or industrial PDA, running Android.
DAL Data Access Layer. A mechanism for accessing data by the system that is removed from the application, allowing for simplified access and providing protection to the data, as only approved DAL methods can be used to modify it.
GPS Global Positioning System. A mechanism of retrieving accurate positioning information in the form of Latitude and Longitude (Lat-Long) co-ordinates from a device.
GPRS, 3G, HSDPA, Data Service All terms referring to mobile device network connectivity, and the speed at which the device connects to the internet.


B.3 Authorised By


Phil Harding
OBS Project Manager		_____________________________
Retrieved from ‘https://calidusassist.adcservices.apteancloud.com/calidus-assist/OBS/index.php?title=FS_305796_Partnerlink_EPOD_Agreed_Product_Changes&oldid=978’