EST 339969 LFS Control POD Email Send

From Calidus HUB
Revision as of 17:18, 14 March 2017 by Anw (talk | contribs) (v0.4 - adding time for multiple branches; clarifying emails on each job)
Aptean Logo.png
STATEMENT OF WORK
CHANGE REQUEST ESTIMATE
ClientLFSProjectAUSSiteAUS-MEL
Client ReferenceNO REFAptean Reference339969Estimate Version0.4
Prepared ByAN WalkerEstimate Date14/03/17
Invoice Reference Priority3
Customer System Version1.4


Client Request
The auto-email POD at Customer level is sending through POD's for both the scan onto the van and for delivery to the final delivery legs. However, the scan onto the van time is not something that the customer should know.


Aptean Solution
A customer-level, location-level and location type-level configuration will be added to C-TMS, used when sending jobs to C-ePOD.

The Settings for all levels will be:

  • POD Only
  • POC Only
  • Both
  • Neither

The configuration will be added to the EPOD tab on the Customers, Locations and Business Data/Location Types maintenance screens.

For Locations only, there will also be an option 'Default', which will then default to the setting against the Location Type.

All email addresses sent through on the jobs would then be set against the origin job and/or final delivery job based on these settings.

Email addresses are configured against contacts linked to locations or orders.

For Customer emails:

  • Link a location to a customer
  • Add a contact against this location with an email address.

For Location emails:

  • Add a contact against this location with an email address.

For Order emails:

  • Add a contact against the from and/or to locations with an email address.


For example:


In this example, the jobs sent through (in normal configuration) would be as follows:


So the rules are:

  • Never populate email if the job being sent is not an origin or final destination location.
  • Only add customer email to origin if configuration is Both or POC.
  • Only add customer email to final destination if configuration is Both or POD.
  • Only add address email to origin if location configuration is Both or POC or Default and location type configuration is Both or POC.
  • Only add address email to final destination if configuration is Both or POD or Default and location type configuration is Both or POD.
  • Add order From Loc email to origin if present.
  • Add order To Loc email to final destination if present.
  • Add order general email to final destination if present.

The email lists will be curated when created to ensure that only one entry per email is generated.


For Job Swaps, the systems will be configured to remove the emails from the job at the swap point, and will be copied to the new jobs, ensuring that the emails will only be sent at final destination.


This mechanism will be used in preference to the Job Group mechanism is C-ePOD. The C-ePOD Site email address (for LFS contact information) will still be used to send emails to LFS contacts.


Cost Details
Activity No. of Days Rate per Day ($ SGD) Cost ($SGD Exc. GST)
Requirements 0.00 0 $0.00
Change Request Evaluation 1.00 0 $0.00
Functional Specification 1.75 1313 $2,297.75
Technical Specification 0.00 1313 $0.00
Development 7.50 1111 $8,332.50
Testing and Release 1.50 1313 $1,969.50
Implementation 0.50 1313 $656.50
Project Management 1.00 1515 $1,515.00
 
TOTAL 13.25   $14,771.25


Copyright © OBS Logistics 2017.
This estimate has an expiry date of 30 days from the specified Estimate Date.
The information contained herein is supplied without liability for errors or omissions.

Retrieved from ‘https://calidusassist.adcservices.apteancloud.com/calidus-assist/OBS/index.php?title=EST_339969_LFS_Control_POD_Email_Send&oldid=4191’