TEST: Difference between revisions

From Calidus HUB
VisualWikitext
No edit summary
No edit summary
Line 1: Line 1:
<div class="noprint">
<div class="noprint">
{{#vardefine:Client|TEST}}
{{#vardefine:Client|JBG}}
{{#vardefine:ClientName|Testing Customer}}
{{#vardefine:ClientName|Oak Furnitureland}}
{{#vardefine:System|''CALIDUS'' ePOD}}
{{#vardefine:System|''CALIDUS'' ePOD}}
{{#vardefine:Doc_Title|Test Document}}
{{#vardefine:Doc_Title|JB Global POD Note Changes}}
{{#vardefine:Version|0.1}}
{{#vardefine:Version|0.1}}
{{#vardefine:Date|25th January 2019}}
{{#vardefine:Date|25th February 2019}}
{{#vardefine:Reference|123456 TEST01}}
{{#vardefine:Reference|354567}}
{{#vardefine:Year|2019}}
{{#vardefine:Year|2019}}
{{ #vardefine: Figure | 0 }}{{ #vardefine: Example | 0 }}
{{ #vardefine: Figure | 0 }}{{ #vardefine: Example | 0 }}
Line 31: Line 31:
= FUNCTIONAL OVERVIEW  =
= FUNCTIONAL OVERVIEW  =
== Client Requirement  ==
== Client Requirement  ==
<!-- Include a statement describing the client’s work request requirement. -->
I have attached the new POD to this email. Please generate an estimate for the changes required and let me know when you can make them. Just to note, any config changes will need to be applied to all ePod sites, as we'd need these changes to be applied system wide.
Statement


== Solution Overview  ==
== Additional points confirmed ==
<!-- Include a summary of the solution explaining how the client’s requirement will be delivered. This might be as a result of software development or system configuration and implementation. -->
* Print images on a following page as with the current delivery note.
Statement
* ePOD has no telephone number 3 so this will be blank.
* Print the name and signature side by side to allow more vertical room for the signature.
* If the delivery has more than 14 lines then the report will throw a page after the 14th line (the footer area will be blank). The next page will include the header again, the rest of the lines and the footer. The third page will then be the disclaimer.
* Using multiple fonts for the T&Cs is not necessary if this requires the text to be hard-coded. It is more important that the T&Cs can be edited in future.
* To support the new POD design, corresponding changes will be required to the configuration of the User-defined Field (UDF) forms currently in use:
** The "Difficult Delivery" information dialogue will be on a new UDF form for "Arrivals Terms and Conditions for Deliveries".
*** This will include capture of the driver's Q&A and the customer's signature. The driver will answer the questions then hand the PDA to the customer to sign.
*** The difficult delivery disclaimer will appear as the terms & conditions below the signature box and the driver's Q&A below that (so the customer will sign against both the disclaimer and the driver's answers, which also both appear on the disclaimer page of the POD).
*** If there isn’t a problem with access then the driver can skip the form.
** The existing form for capturing the "Difficult Delivery" information is no longer required and will be removed. This is the "Job Details - When Amended" UDF form.
** The Returns disclaimer will be on a new UDF form for "Arrivals Terms and Conditions for Collections". This will include capture of the customer's signature with the disclaimer text below the signature box.
** The failure reason, return no. and card no. are entered on a "Job Cancellation" UDF form, which will remain in use.
* Collection jobs will show alternative text to delivery notes in these places:
** The document title will change from "DELIVERY NOTE" to "COLLECTION NOTE".
** The text against the customer signature will change from "I, the customer, acknowledge receipt of goods" to "I, the customer, acknowledge collection of goods".
** The text "FAILED DELIVERY CHECKLIST TO BE COMPLETED BY DRIVER" will become "FAILED COLLECTION CHECKLIST TO BE COMPLETED BY DRIVER"
 
[[File:JBG POD page 1.jpg|border|600px]]


[[File:JBG POD page 2.jpg|border|600px]]


== Scope  ==
<!-- This change will be applied to system version (enter the version) on (enter the test database e.g. CONTST) and once approved (enter the production database e.g.: CONPRD).


Describe the scope of work and be clear about what is included and what is excluded. -->
== Solution Overview  ==
Statement
The Configurable POD Report will be modified to match the requirements.




== Impact ==
== Scope ==
<!-- Identify the potential consequences of the changes described in this Functional Specification.
This change will be completed in the latest versions of ''CALIDUS'' ePOD server and mobile device software.  


Relating to the scope of work, document any identified dependencies necessary to maintain consistency of the solution.  Highlight those not addressed within this solution specification.


Include any considered and related opportunities for improvement not addressed within this solution specification. -->
== Impact ==
Statement
Once the new format and UDF is applied, any jobs completed without the new data will not produce a POD correctly. If this is required, the following is recommended:
* The POD note format is created as a new format, retaining the original.
* New job groups are created for collections and deliveries, configured to use the new report format.
* These job groups are used on any new jobs that require the new format.
This will require modifications to the interface passed to C-ePOD from the WMS/ERP.




Line 58: Line 76:
= CONFIGURATION SET-UP  =
= CONFIGURATION SET-UP  =
== Pre-requisites  ==
== Pre-requisites  ==
<!-- Think about dependent functionality or configuration that is required to support this deliverable and describe here. -->
A configured ''CALIDUS'' ePOD system connected to the WMS/ERP.
Statement




== Menu Structure  ==
== Menu Structure  ==
<!-- Describe how the menu system will change to accommodate this requirement if relevant. -->
N/A
Statement




== Data  ==
== Data  ==
<!-- Document any configuration data set up necessary to enable or control the solution e.g. the new report will be added to the standing data to allow it to be selected from the standard reports form. The selection criteria for the report will be (insert selection criteria). -->
The new POD format will be applied either to the existing (non-warehouse) collection and delivery job groups, or to the new job groups created for this purpose, using the Job Group Maintenance screen.
Statement
 
 
UDF configurations will be created for the following:
* Difficult Delivery - pre-job T&Cs for Deliveries.
* Returns Only - pre-job T&Cs for Collections.
{{Note}} These UDF configurations will be applied either to the existing (non-warehouse) collection and delivery job groups, or to the new job groups created for this purpose, using the UDF Maintenance screen.
 
 
=== Pre-job T&Cs for Deliveries ===
    <FORM NAME="Difficult Delivery" REQUIRED="N">
      <FIELD ID="SECTION1">
        <TEXT>SECTION 1: To be completed by the Oak Furniture Land Delivery Team</TEXT>
        <FORMAT>L</FORMAT>
        <SUBTEXT></SUBTEXT>
        <REQUIRED>N</REQUIRED>
        <GROUP></GROUP>
        <POST></POST>
      </FIELD>
      <FIELD ID="DIFFICULT_DELIVERY">
        <TEXT>Why is the delivery difficult? Please tick the relevant box(es) below.</TEXT>
        <FORMAT>L</FORMAT>
        <SUBTEXT></SUBTEXT>
        <REQUIRED>N</REQUIRED>
        <GROUP></GROUP>
        <POST></POST>
      </FIELD>
      <FIELD ID="NARROW_ACCESS">
        <TEXT>Narrow access issue</TEXT>
        <FORMAT>X</FORMAT>
        <SUBTEXT></SUBTEXT>
        <REQUIRED>N</REQUIRED>
        <GROUP></GROUP>
        <POST></POST>
        <ITEMS>
          <ITEM ID="NARROW_ACCESS__1" DEFAULT="N" VALUE="N">Property entrance (front door)</ITEM>
          <ITEM ID="NARROW_ACCESS__2" DEFAULT="N" VALUE="Y">Entrance to room of choice</ITEM>
          <ITEM ID="NARROW_ACCESS__3" DEFAULT="N" VALUE="N">Tight turn within the delivery route</ITEM>
        </ITEMS>
      </FIELD>
      <FIELD ID="OBSTRUCTION">
        <TEXT>Obstruction that can't be easily moved</TEXT>
        <FORMAT>X</FORMAT>
        <SUBTEXT></SUBTEXT>
        <REQUIRED>N</REQUIRED>
        <GROUP></GROUP>
        <POST></POST>
        <ITEMS>
          <ITEM ID="OBSTRUCTION__1" DEFAULT="N" VALUE="N">Low ceiling</ITEM>
          <ITEM ID="OBSTRUCTION__2" DEFAULT="N" VALUE="Y">Bannister that reduces space to move need to manoeuvre item</ITEM>
          <ITEM ID="OBSTRUCTION__3" DEFAULT="N" VALUE="N">Low hanging light fitting</ITEM>
          <ITEM ID="OBSTRUCTION__4" DEFAULT="N" VALUE="N">Existing large furniture</ITEM>
        </ITEMS>
      </FIELD>
      <FIELD ID="OTHER">
        <TEXT>OTHER</TEXT>
        <FORMAT>A</FORMAT>
        <SUBTEXT></SUBTEXT>
        <REQUIRED>N</REQUIRED>
        <GROUP></GROUP>
        <POST></POST>
        <VALUE></VALUE>
      </FIELD>
      <FIELD ID="SECTION2">
        <TEXT>SECTION 2: To be signed by the customer</TEXT>
        <FORMAT>L</FORMAT>
        <SUBTEXT></SUBTEXT>
        <REQUIRED>N</REQUIRED>
        <GROUP></GROUP>
        <POST></POST>
      </FIELD> 
      <FIELD ID="ACKNOWLEDGE">
        <TEXT>I acknowledge that there is not safe, clear and adequate access for delivery, as required under sections 9.8.1 and 9.8.2 of the JB Global Limited's terms and conditions. I wish to proceed with the delivery and have been advised of the risk of damage to property which might occur as a result.</TEXT>
        <FORMAT>L</FORMAT>
        <SUBTEXT></SUBTEXT>
        <REQUIRED>N</REQUIRED>
        <GROUP></GROUP>
        <POST></POST>
      </FIELD> 
      <FIELD ID="SECTION81">
        <TEXT>8.1 | Please check the measurements and delivery access to Your home. It is important to check the measurements of Your Products by visiting Our Website or by calling Our customer service team. Please ensure that there is adequate doorway and stair access. We cannot accept any liability for any extra costs incurred by You as a result of incorrect or incomplete measurements or information supplied by You</TEXT>
        <FORMAT>L</FORMAT>
        <SUBTEXT></SUBTEXT>
        <REQUIRED>N</REQUIRED>
        <GROUP></GROUP>
        <POST></POST>
      </FIELD> 
      <FIELD ID="SECTION82">
        <TEXT>8.2 | Please check that the route from the lorry to Your room of choice is safe and free from potential problems or hazards. As Our staff have not visited Your home and cannot advise whether Your Products will fit, We ask that You take reasonable steps to ensure that the Products can be successfully delivered to You. This includes making sure that the lorry can get to You and measuring any door or ceiling heights, plus twists and turns (including Your stair banister) that might cause difficulties when We deliver. Your order will typically be delivered via a large lorry, so please be sure Your property is accessible for this type of vehicle. If You think there may be an issue, please call Us prior to delivery.</TEXT>
        <FORMAT>L</FORMAT>
        <SUBTEXT></SUBTEXT>
        <REQUIRED>N</REQUIRED>
        <GROUP></GROUP>
        <POST></POST>
      </FIELD> 
    </FORM>
 
=== Pre-job T&Cs for Collections ===
    <FORM NAME="Returns Only" REQUIRED="Y">
      <FIELD ID="TITLE">
        <TEXT>RETURNS ONLY</TEXT>
        <FORMAT>L</FORMAT>
        <SUBTEXT></SUBTEXT>
        <REQUIRED>N</REQUIRED>
        <GROUP></GROUP>
        <POST></POST>
      </FIELD>
      <FIELD ID="TANDCS">
        <TEXT>I, the customer, confirm all delivery labels containing my personal details have been removed prior to the item being returned.</TEXT>
        <FORMAT>L</FORMAT>
        <SUBTEXT></SUBTEXT>
        <REQUIRED>N</REQUIRED>
        <GROUP></GROUP>
        <POST></POST>
      </FIELD>
    </FORM>




== Implementation Advice ==
== Implementation Advice ==
<!-- Include any relevant notes that will help OBSL or Client implementer to successfully enable the solution on delivery. -->
The changes to the POD require additional changes to the server and the mobile device application in order to populate the new back page. Both will be required to be released ''before'' the new POD report format can be implemented.
Statement




<!-- NEW PAGE -->  
<!-- NEW PAGE -->  
= FUNCTIONAL DESCRIPTION =
= FUNCTIONAL DESCRIPTION =
== Heading  ==
== Mobile Device Changes ==
=== Sub Heading  ===
Configurable UDF T&Cs will be used for the Difficult Delivery Disclaimer and Returns Only sections. Currently, the device does not return these values. This bug will be fixed.
<!-- Describe functionally how the solution will satisfy the client requirement. Include statements to define all of the new capabilities or changes to be developed. Include pictures to illustrate and support design.
 
 
== Mobile Device Process ==
After these changes are implemented, the mobile device process upon arrival to the customer's location will be as described below.
 
For deliveries:
* After arrival, the mobile device application will present the driver with the Arrival Signature process, displaying the Difficult Delivery Disclaimer form (both sections) in the T&Cs for the signature.
* The driver will determine whether the delivery will be difficult for any reason.
* If not, the driver will skip the signature and move on to the delivery.
* If the driver determines that the delivery will be difficult, the driver will check the appropriate boxes on section 1 of the T&Cs, or enter any other reason where prompted. The driver will then obtain the customer's signature.
* The driver will move on to the delivery, as now.
 
For collections:
* After arrival, the mobile device application will present the driver with the Arrival Signature process, displaying the Returns Only form in the T&Cs for the signature.
* The driver will then obtain the customer's signature - this process cannot be skipped.
* The driver will move on to the collection, as now.
 
 
== New POD Report Format ==
The new POD report will be formatted as described in the requirements.


Note that this section will usually be reviewed and signed off by the client.  Think about the audience and ensure the information documented is easy to read and understand.
A prototype has been created, resulting in the following:


Group the functional description into logical areas and use sub-headings where appropriate -->
[[File:FS_354567_POD1.PNG|border|800px]]
Statement
[[File:FS_354567_POD2.PNG|border|800px]]




Line 92: Line 240:
= TECHNICAL NOTES =
= TECHNICAL NOTES =
== Modules Changed ==
== Modules Changed ==
<!-- List the modules or objects that will be changed by this development -->
{| class="wikitable" border="1" width="100%"
{| class="wikitable" border="1" width="100%"
|-bgcolor="#FFFF99"
|-bgcolor="#FFFF99"
! Module Name !! Module Type !! Notes
! Module Name !! Module Type !! Notes
|-
|-
| 1 || 2 || 3
| ConfigPOD.aspx.cs || EPOD Server Report || &nbsp;
|-
| SystemUtilities.js || EPOD Mobile Device module || &nbsp;
|}
|}




== Table Updates ==
== Table Updates ==
<!-- Detail any changes to the data model including additional tables, columns, indexes etc -->
None.
{| class="wikitable" border="1" width="100%"
 
|-bgcolor="#FFFF99"
== Developer Notes ==
! Name !! Type !! Nullable !! Default !! Storage !! Comments
Config Report Changes:
|-
* Add function to extract UDF in one grab
| 1 || 2 || 3 || 4 || 5 || 6
* Change styling of UDF fields
|}
* Add standard CSS styles for UDF fields.
 
Data:
* New Products POD Report format for Oak Furnitureland
 
Mobile Device Changes:
* Send pre-job UDF T&Cs back to the server for printing on the POD note.
 
 
=== Configurable POD - New GetUDFForm Function ===
The following rules are followed:
* Form is a DIV classed as UDFForm , ID'd using the class and UDF type, for example:
** CONTAINER - UDFForm_CONTAINER
** CONTCANC - UDFForm_CONTCANC
** CONTCLAUSE - UDFForm_CONTCLAUSE
** DIAGNOSIS - UDFForm_DIAGNOSIS
** INFO - UDFForm_INFO
** JOBCANC - UDFForm_JOBCANC
** JOBDETS - UDFForm_JOBDETS
** LOADEND - UDFForm_LOADEND
** LOADSTART - UDFForm_LOADSTART
** pre-job - UDFForm_pre-job
** POSTWORK - UDFForm_POSTWORK
** PREWORK - UDFForm_PREWORK
** PRODCANC - UDFForm_PRODCANC
** PRODQTY - UDFForm_PRODQTY
** PRODUCT - UDFForm_PRODUCT
** SERVCANC - UDFForm_SERVCANC
** SERVITEMCANC - UDFForm_SERVITEMCANC
** TNCSC - UDFForm_TNCSC
** TNCSD - UDFForm_TNCSD
** TNCSDRIVERC - UDFForm_TNCSDRIVERC
** TNCSDRIVERD - UDFForm_TNCSDRIVERD
** TNCSDRIVERS - UDFForm_TNCSDRIVERS
** TNCSpre-jobC - UDFForm_TNCSpre-jobC
** TNCSpre-jobD - UDFForm_TNCSPREJOBD
** TNCSS - UDFForm_TNCSS
** TNCSVC - UDFForm_TNCSVC
** VEHICLECHECK - UDFForm_VEHICLECHECK
* Each field is a DIV classed as UDFField and by their field type:
** UDFFieldT - Text
** UDFFieldN - Numeric
** UDFFieldB - CheckBox
** UDFFieldX - Checkbox List
** UDFFieldTSC - Tri-state Check
** UDFFieldX2 - Tri-state Check List
** UDFFieldDDL - Drop-down List
** UDFFieldA - Text Area
** UDFFieldL - Label
** Button/Photo - omitted
* Each Text, Numeric, DDL and Text Area field will show the following in this order:
** The label classed as UDFFieldTitle.
** The value classed as UDFFieldValue.
** The subtext classed as UDFFieldSubtext, if present.
** The post text classed as UDFFieldPost, if present.
 
* Each field is strongly ID'd with the form ID and field ID, for example, for a UDF pre-job TNCs form:
** UDFFieldT - Text
        <div class="UDFField UDFFieldT" id="UDFForm_TNCSPREJOBD_TRAILER">
            <span class="UDFFieldTitle">Trailer ID</span>
            <span class="UDFFieldValue">TRAIL1</span>
            <span class="UDFFieldSubtext">Sub</span>
            <span class="UDFFieldPost">Post</span>
        </div>
** UDFFieldN - Numeric
        <div class="UDFField UDFFieldN" id="UDFForm_TNCSPREJOBD_WEIGHT">
            <span class="UDFFieldTitle">Weight</span>
            <span class="UDFFieldValue">123.456</span>
        </div>
** UDFFieldB - CheckBox
        <div class="UDFField UDFFieldB" id="UDFForm_TNCSPREJOBD_CHECKED">
            <span class="UDFFieldItem">
                <label><input type="checkbox" checked="checked" />Checked</label>
            </span>
        </div>
** UDFFieldX - Checkbox List
        <div class="UDFField UDFFieldX" id="UDFForm_TNCSPREJOBD_NARROW_ACCESS">
            <span class="UDFFieldTitle">Narrow access issue</span>
            <span class="UDFFieldItem">
                <label><input type="checkbox" checked="checked" />Property entrance (front door)</label>
            </span>
            <span class="UDFFieldItem">
                <label><input type="checkbox" checked="checked" />Entrance to room of choice</label>
            </span>
            <span class="UDFFieldItem">
                <label><input type="checkbox" checked="checked" />Tight turn within the delivery route</label>
            </span>
        </div>
** UDFFieldTSC - Tri-state Check
        <div class="UDFField UDFFieldTSC" id="UDFForm_TNCSPREJOBD_CHECKED">
            <span class="UDFFieldItem">
                <label><input type="checkbox" checked="checked" />Checked</label>
            </span>
        </div>
** UDFFieldX2 - Tri-state Check List
        <div class="UDFField UDFFieldX2" id="UDFForm_TNCSPREJOBD_NARROW_ACCESS">
            <span class="UDFFieldTitle">Narrow access issue</span>
            <span class="UDFFieldItem">
                <label><input type="checkbox" checked="checked" />Property entrance (front door)</label>
            </span>
            <span class="UDFFieldItem">
                <label><input type="checkbox" checked="checked" />Entrance to room of choice</label>
            </span>
            <span class="UDFFieldItem">
                <label><input type="checkbox" checked="checked" />Tight turn within the delivery route</label>
            </span>
        </div>
** UDFFieldDDL - Drop-down List
        <div class="UDFField UDFFieldDDL" id="UDFForm_TNCSPREJOBD_LEVEL">
            <span class="UDFFieldTitle">Enter Level</span>
            <span class="UDFFieldValue">Half</span>
        </div>
** UDFFieldA - Text Area
        <div class="UDFField UDFFieldA" id="UDFForm_TNCSPREJOBD_COMMENTS">
            <span class="UDFFieldTitle">Comments</span>
            <span class="UDFFieldValue">Some comments</span>
        </div>
** UDFFieldL - Label
        <div class="UDFField UDFFieldL" id="UDFForm_TNCSPREJOBD_SECTION1">SECTION 1:</div>
 
 
=== UDF Formatting ===
Example:
<code>
    <div class="UDFForm" id="UDFForm_TNCSPREJOBD">
        <div class="UDFField UDFFieldL" id="UDFForm_TNCSPREJOBD_SECTION1">SECTION 1: To be completed by the Oak Furniture Land Delivery Team</div>
        <div class="UDFField UDFFieldL" id="UDFForm_TNCSPREJOBD_DIFFICULT_DELIVERY">Why is the delivery difficult? Please tick the relevant box(es) below.</div>
        <div class="UDFField UDFFieldX" id="UDFForm_TNCSPREJOBD_NARROW_ACCESS">
            <span class="UDFFieldTitle">Narrow access issue</span>
            <span class="UDFFieldItem">
                <label><input type="checkbox" checked="checked" />Property entrance (front door)</label>
            </span>
            <span class="UDFFieldItem">
                <label><input type="checkbox" checked="checked" />Entrance to room of choice</label>
            </span>
            <span class="UDFFieldItem">
                <label><input type="checkbox" checked="checked" />Tight turn within the delivery route</label>
            </span>
        </div>
        <div class="UDFField UDFFieldX" id="UDFForm_TNCSPREJOBD_OBSTRUCTION">
            <span class="UDFFieldTitle">Obstruction that can't be easily moved</span>
            <span class="UDFFieldItem">
                <label>
                    <input type="checkbox" checked="checked" />Low ceiling</label>
            </span>
            <span class="UDFFieldItem">
                <label>
                    <input type="checkbox" checked="checked" />Bannister that reduces space to move need to manoeuvre item</label>
            </span>
            <span class="UDFFieldItem">
                <label>
                    <input type="checkbox" checked="checked" />Low hanging light fitting</label>
            </span>
            <span class="UDFFieldItem">
                <label>
                    <input type="checkbox" checked="checked" />Existing large furniture</label>
            </span>
        </div>
        <div class="UDFField UDFFieldA" id="UDFForm_TNCSPREJOBD_OTHER">
            <span class="UDFFieldTitle">Other, please give details</span>
            <span class="UDFFieldValue"></span>
        </div>
        <div class="UDFField UDFFieldL" id="UDFForm_TNCSPREJOBD_SECTION2">SECTION 2: To be signed by the customer</div>
        <div class="UDFField UDFFieldL" id="UDFForm_TNCSPREJOBD_ACKNOWLEDGE">I acknowledge that there is not safe, clear and adequate access for delivery, as required under sections 9.8.1 and 9.8.2 of the JB Global Limited's terms and conditions. I wish to proceed with the delivery and have been advised of the risk of damage to property which might occur as a result.</div>
        <div class="UDFField UDFFieldL" id="UDFForm_TNCSPREJOBD_SECTION81">8.1 | Please check the measurements and delivery access to Your home. It is important to check the measurements of Your Products by visiting Our Website or by calling Our customer service team. Please ensure that there is adequate doorway and stair access. We cannot accept any liability for any extra costs incurred by You as a result of incorrect or incomplete measurements or information supplied by You.</div>
        <div class="UDFField UDFFieldL" id="UDFForm_TNCSPREJOBD_SECTION82">8.2 | Please check that the route from the lorry to Your room of choice is safe and free from potential problems or hazards. As Our staff have not visited Your home and cannot advise whether Your Products will fit, We ask that You take reasonable steps to ensure that the Products can be successfully delivered to You. This includes making sure that the lorry can get to You and measuring any door or ceiling heights, plus twists and turns (including Your stair banister) that might cause difficulties when We deliver. Your order will typically be delivered via a large lorry, so please be sure Your property is accessible for this type of vehicle. If You think there may be an issue, please call Us prior to delivery.</div>
    </div>
    ...
    <div class="UDFForm" id="UDFForm_TNCSPREJOBC">
        <div class="UDFField UDFFieldL" id="UDFForm_TNCSPREJOBC_TITLE">RETURNS ONLY</div>
        <div class="UDFField UDFFieldL" id="UDFForm_TNCSPREJOBC_TANDCS">
            I, the customer, confirm all delivery labels containing my personal details have been removed prior to the item being returned.
        </div>
    </div>
</code>
 
 
       
The following standard styles will then be available to be used:
    .UDFForm {}
    .UDFForm > div {}
   
    .UDFField {}
    .UDFFieldL {}
    .UDFFieldT {}
    .UDFFieldN {}
    .UDFFieldB {}
    .UDFFieldX2 {}
    .UDFFieldTSC {}
    .UDFFieldDDL {}
    .UDFFieldX {}
    .UDFFieldA {}
   
    .UDFFieldTitle {}
    .UDFFieldValue {}
    .UDFFieldSubtext {}
    .UDFFieldPost {}
    .UDFFieldItem {}
 
 
The following style is recommended as a default:
    .UDFFieldA .UDFFieldValue {
        min-height: 3em;
    }
    .UDFFieldItem {
        padding: 0.2em;
    }
    .UDFFieldX > span {
        padding: 0.5em;
        display: block;
    }
    .UDFFieldSubtext {
        width: 65%;
        float: left;
        font-size: 0.5em;
    }
    .UDFFieldPost {
        width: 30%;
        float: right;
        font-size: 0.5em;
    }
 
 
==== Design considerations ====
Each field can be styled by ID or class, with class per field or class per field type.
 
Each element of a field type can be classed individually by chaining the styles. So, title can be styled generically through ".UDFFieldTitle", and specifically for Text Areas using ".UDFFieldA .UDFFieldTitle".
 
As forms are ID'd by the UDF type, each UDF form can be styled completely separately by chaining the the styles. So, a Pre-job field may have a black border, while a Job UDF field may have a red border. This would be styled as follows:
    div#UDFForm_TNCSPREJOBD .UDFField { border: solid black 1px;}
    div#UDFForm_JOBDETS .UDFField { border: solid red 1px;}
 
This allows for generic styling of all fields uniformly, with exceptions for certain forms, field types or specific fields.
 
 
=== Mobile Device Changes ===
On completion of a pre-job signature, the callback function will be modified to check the index of the T&Cs used (p_intTncId). If this index is non-0, then the T&Cs used are from the standards created against the job group - this functionality will remain unchanged.
 
If the index is 0, the completed T&Cs will be saved in SIG_TNC_CHECKS of the PDASIGNATURE record created.
 
 
=== New POD Report Format ===
The new POD report will be formatted as described in the requirements.
 
A prototype has been created in the development environment, as shown in the overview section.
 


Notes:
* "I, the customer"... - this is fixed text, formatted for job type i.e. "receipt" for deliveries and "collection" for collections.
* The Failed Delivery Checklist section will be displayed only if the job has been cancelled.
* The new back page and footer will be part of the final footer, not the page footer.
* The new back page will be sectioned in a div that will throw a page break when printed, repeating the header and populated from pre-job T&Cs.
* The Difficult Delivery Disclaimer (sections 1 and 2 and signature section on the back page) will be produced from the pre-job T&Cs for delivery jobs. This will be created from the UDF element directly i.e. EPOD_SIGNATURE.SIG_TNC_CHECKS.
* The Difficult Delivery Disclaimer signature section will be populated from the data on EPOD_SIGNATURE.
* The Returns Only section will be produced from the pre-job T&Cs for delivery jobs.
* The Returns Only signature section will be populated from the data on EPOD_SIGNATURE.
* The Difficult Delivery Disclaimer will only be present if there is a pre-job signature for a delivery job.
* The Returns Only section will only be present if there is a pre-job signature for a collection job.
* In the case where this is a delivery job and no difficult delivery disclaimer has been issued, the back page will be omitted (hidden).
* The pre-job T&Cs will be formatted using the new classes for styling UDF forms.


== Developer Notes ==
The report will be created as a new POD report, ''not'' over-writing the existing report.
<!-- Include technical notes and definitions to assist the developer where appropriate -->




Line 154: Line 560:
|Appendix=A
|Appendix=A
|Estimate=Y
|Estimate=Y
|Glossary=EPOD
|Glossary=EPOD2
|Ref1=Reference1
|Ref1=[[REQ 354567 JB Global POD Note Changes]]
|RefV1=0.1
|RefV1=1.1
|RefDate1=01/01/2011
|RefDate1=18/02/2019
|REQ=0
|REQ=3
|EST=0
|EST=0
|FS=0
|FS=1.5
|TS=0
|TS=0
|DEV=0
|DEV=2.0
|ST=0
|ST=0.75
|IMP=0
|IMP=0.5
|PM=0
|PM=0.5
|Client={{#var:Client}}
|Client={{#var:Client}}
|Year={{#var:Year}}
|Year={{#var:Year}}
|FSEST=Y
|FSEST=Y
|Rev1=Rev1
|Rev1=Barry Preece
|Rev1Title=OBS Project Manager
|Rev1Title=OBS Project Manager
|Rev2=Rev2
|Rev2=Nav Mohammed
|Rev2Title=Customer Representative
|Rev2Title=Customer Representative
}}</div>  
}}</div>  
[[Category:{{#var:Client}} FS]]
[[Category:{{#var:Client}} FS]]

Revision as of 13:09, 25 February 2019





Aptean Logo.png







Oak Furnitureland

JB Global POD Note Changes

Functional Specification

25th February 2019 - 0.1
Reference: FS 354567















FUNCTIONAL OVERVIEW

Client Requirement

I have attached the new POD to this email. Please generate an estimate for the changes required and let me know when you can make them. Just to note, any config changes will need to be applied to all ePod sites, as we'd need these changes to be applied system wide.

Additional points confirmed

  • Print images on a following page as with the current delivery note.
  • ePOD has no telephone number 3 so this will be blank.
  • Print the name and signature side by side to allow more vertical room for the signature.
  • If the delivery has more than 14 lines then the report will throw a page after the 14th line (the footer area will be blank). The next page will include the header again, the rest of the lines and the footer. The third page will then be the disclaimer.
  • Using multiple fonts for the T&Cs is not necessary if this requires the text to be hard-coded. It is more important that the T&Cs can be edited in future.
  • To support the new POD design, corresponding changes will be required to the configuration of the User-defined Field (UDF) forms currently in use:
    • The "Difficult Delivery" information dialogue will be on a new UDF form for "Arrivals Terms and Conditions for Deliveries".
      • This will include capture of the driver's Q&A and the customer's signature. The driver will answer the questions then hand the PDA to the customer to sign.
      • The difficult delivery disclaimer will appear as the terms & conditions below the signature box and the driver's Q&A below that (so the customer will sign against both the disclaimer and the driver's answers, which also both appear on the disclaimer page of the POD).
      • If there isn’t a problem with access then the driver can skip the form.
    • The existing form for capturing the "Difficult Delivery" information is no longer required and will be removed. This is the "Job Details - When Amended" UDF form.
    • The Returns disclaimer will be on a new UDF form for "Arrivals Terms and Conditions for Collections". This will include capture of the customer's signature with the disclaimer text below the signature box.
    • The failure reason, return no. and card no. are entered on a "Job Cancellation" UDF form, which will remain in use.
  • Collection jobs will show alternative text to delivery notes in these places:
    • The document title will change from "DELIVERY NOTE" to "COLLECTION NOTE".
    • The text against the customer signature will change from "I, the customer, acknowledge receipt of goods" to "I, the customer, acknowledge collection of goods".
    • The text "FAILED DELIVERY CHECKLIST TO BE COMPLETED BY DRIVER" will become "FAILED COLLECTION CHECKLIST TO BE COMPLETED BY DRIVER"

JBG POD page 1.jpg

JBG POD page 2.jpg


Solution Overview

The Configurable POD Report will be modified to match the requirements.


Scope

This change will be completed in the latest versions of CALIDUS ePOD server and mobile device software.


Impact

Once the new format and UDF is applied, any jobs completed without the new data will not produce a POD correctly. If this is required, the following is recommended:

  • The POD note format is created as a new format, retaining the original.
  • New job groups are created for collections and deliveries, configured to use the new report format.
  • These job groups are used on any new jobs that require the new format.

This will require modifications to the interface passed to C-ePOD from the WMS/ERP.


CONFIGURATION SET-UP

Pre-requisites

A configured CALIDUS ePOD system connected to the WMS/ERP.


Menu Structure

N/A


Data

The new POD format will be applied either to the existing (non-warehouse) collection and delivery job groups, or to the new job groups created for this purpose, using the Job Group Maintenance screen.


UDF configurations will be created for the following:

  • Difficult Delivery - pre-job T&Cs for Deliveries.
  • Returns Only - pre-job T&Cs for Collections.

Note Note: These UDF configurations will be applied either to the existing (non-warehouse) collection and delivery job groups, or to the new job groups created for this purpose, using the UDF Maintenance screen.


Pre-job T&Cs for Deliveries

   <FORM NAME="Difficult Delivery" REQUIRED="N">
     <FIELD ID="SECTION1">
       <TEXT>SECTION 1: To be completed by the Oak Furniture Land Delivery Team</TEXT>
       <FORMAT>L</FORMAT>
       <SUBTEXT></SUBTEXT>
       <REQUIRED>N</REQUIRED>
       <GROUP></GROUP>
       <POST></POST>
     </FIELD>
     <FIELD ID="DIFFICULT_DELIVERY">
       <TEXT>Why is the delivery difficult? Please tick the relevant box(es) below.</TEXT>
       <FORMAT>L</FORMAT>
       <SUBTEXT></SUBTEXT>
       <REQUIRED>N</REQUIRED>
       <GROUP></GROUP>
       <POST></POST>
     </FIELD>
     <FIELD ID="NARROW_ACCESS">
       <TEXT>Narrow access issue</TEXT>
       <FORMAT>X</FORMAT>
       <SUBTEXT></SUBTEXT>
       <REQUIRED>N</REQUIRED>
       <GROUP></GROUP>
       <POST></POST>
       <ITEMS>
         <ITEM ID="NARROW_ACCESS__1" DEFAULT="N" VALUE="N">Property entrance (front door)</ITEM>
         <ITEM ID="NARROW_ACCESS__2" DEFAULT="N" VALUE="Y">Entrance to room of choice</ITEM>
         <ITEM ID="NARROW_ACCESS__3" DEFAULT="N" VALUE="N">Tight turn within the delivery route</ITEM>
       </ITEMS>
     </FIELD>
     <FIELD ID="OBSTRUCTION">
       <TEXT>Obstruction that can't be easily moved</TEXT>
       <FORMAT>X</FORMAT>
       <SUBTEXT></SUBTEXT>
       <REQUIRED>N</REQUIRED>
       <GROUP></GROUP>
       <POST></POST>
       <ITEMS>
         <ITEM ID="OBSTRUCTION__1" DEFAULT="N" VALUE="N">Low ceiling</ITEM>
         <ITEM ID="OBSTRUCTION__2" DEFAULT="N" VALUE="Y">Bannister that reduces space to move need to manoeuvre item</ITEM>
         <ITEM ID="OBSTRUCTION__3" DEFAULT="N" VALUE="N">Low hanging light fitting</ITEM>
         <ITEM ID="OBSTRUCTION__4" DEFAULT="N" VALUE="N">Existing large furniture</ITEM>
       </ITEMS>
     </FIELD>
     <FIELD ID="OTHER">
       <TEXT>OTHER</TEXT>
       <FORMAT>A</FORMAT>
       <SUBTEXT></SUBTEXT>
       <REQUIRED>N</REQUIRED>
       <GROUP></GROUP>
       <POST></POST>
       <VALUE></VALUE>
     </FIELD>
     <FIELD ID="SECTION2">
       <TEXT>SECTION 2: To be signed by the customer</TEXT>
       <FORMAT>L</FORMAT>
       <SUBTEXT></SUBTEXT>
       <REQUIRED>N</REQUIRED>
       <GROUP></GROUP>
       <POST></POST>
     </FIELD>  
     <FIELD ID="ACKNOWLEDGE">
       <TEXT>I acknowledge that there is not safe, clear and adequate access for delivery, as required under sections 9.8.1 and 9.8.2 of the JB Global Limited's terms and conditions. I wish to proceed with the delivery and have been advised of the risk of damage to property which might occur as a result.</TEXT>
       <FORMAT>L</FORMAT>
       <SUBTEXT></SUBTEXT>
       <REQUIRED>N</REQUIRED>
       <GROUP></GROUP>
       <POST></POST>
     </FIELD>  
     <FIELD ID="SECTION81">
       <TEXT>8.1 | Please check the measurements and delivery access to Your home. It is important to check the measurements of Your Products by visiting Our Website or by calling Our customer service team. Please ensure that there is adequate doorway and stair access. We cannot accept any liability for any extra costs incurred by You as a result of incorrect or incomplete measurements or information supplied by You</TEXT>
       <FORMAT>L</FORMAT>
       <SUBTEXT></SUBTEXT>
       <REQUIRED>N</REQUIRED>
       <GROUP></GROUP>
       <POST></POST>
     </FIELD>  
     <FIELD ID="SECTION82">
       <TEXT>8.2 | Please check that the route from the lorry to Your room of choice is safe and free from potential problems or hazards. As Our staff have not visited Your home and cannot advise whether Your Products will fit, We ask that You take reasonable steps to ensure that the Products can be successfully delivered to You. This includes making sure that the lorry can get to You and measuring any door or ceiling heights, plus twists and turns (including Your stair banister) that might cause difficulties when We deliver. Your order will typically be delivered via a large lorry, so please be sure Your property is accessible for this type of vehicle. If You think there may be an issue, please call Us prior to delivery.</TEXT>
       <FORMAT>L</FORMAT>
       <SUBTEXT></SUBTEXT>
       <REQUIRED>N</REQUIRED>
       <GROUP></GROUP>
       <POST></POST>
     </FIELD>  
   </FORM>

Pre-job T&Cs for Collections

   <FORM NAME="Returns Only" REQUIRED="Y">
     <FIELD ID="TITLE">
       <TEXT>RETURNS ONLY</TEXT>
       <FORMAT>L</FORMAT>
       <SUBTEXT></SUBTEXT>
       <REQUIRED>N</REQUIRED>
       <GROUP></GROUP>
       <POST></POST>
     </FIELD>
     <FIELD ID="TANDCS">
       <TEXT>I, the customer, confirm all delivery labels containing my personal details have been removed prior to the item being returned.</TEXT>
       <FORMAT>L</FORMAT>
       <SUBTEXT></SUBTEXT>
       <REQUIRED>N</REQUIRED>
       <GROUP></GROUP>
       <POST></POST>
     </FIELD>
   </FORM>


Implementation Advice

The changes to the POD require additional changes to the server and the mobile device application in order to populate the new back page. Both will be required to be released before the new POD report format can be implemented.


FUNCTIONAL DESCRIPTION

Mobile Device Changes

Configurable UDF T&Cs will be used for the Difficult Delivery Disclaimer and Returns Only sections. Currently, the device does not return these values. This bug will be fixed.


Mobile Device Process

After these changes are implemented, the mobile device process upon arrival to the customer's location will be as described below.

For deliveries:

  • After arrival, the mobile device application will present the driver with the Arrival Signature process, displaying the Difficult Delivery Disclaimer form (both sections) in the T&Cs for the signature.
  • The driver will determine whether the delivery will be difficult for any reason.
  • If not, the driver will skip the signature and move on to the delivery.
  • If the driver determines that the delivery will be difficult, the driver will check the appropriate boxes on section 1 of the T&Cs, or enter any other reason where prompted. The driver will then obtain the customer's signature.
  • The driver will move on to the delivery, as now.

For collections:

  • After arrival, the mobile device application will present the driver with the Arrival Signature process, displaying the Returns Only form in the T&Cs for the signature.
  • The driver will then obtain the customer's signature - this process cannot be skipped.
  • The driver will move on to the collection, as now.


New POD Report Format

The new POD report will be formatted as described in the requirements.

A prototype has been created, resulting in the following:

FS 354567 POD1.PNG FS 354567 POD2.PNG


TECHNICAL NOTES

Modules Changed

Module Name Module Type Notes
ConfigPOD.aspx.cs EPOD Server Report  
SystemUtilities.js EPOD Mobile Device module  


Table Updates

None.

Developer Notes

Config Report Changes:

  • Add function to extract UDF in one grab
  • Change styling of UDF fields
  • Add standard CSS styles for UDF fields.

Data:

  • New Products POD Report format for Oak Furnitureland

Mobile Device Changes:

  • Send pre-job UDF T&Cs back to the server for printing on the POD note.


Configurable POD - New GetUDFForm Function

The following rules are followed:

  • Form is a DIV classed as UDFForm , ID'd using the class and UDF type, for example:
    • CONTAINER - UDFForm_CONTAINER
    • CONTCANC - UDFForm_CONTCANC
    • CONTCLAUSE - UDFForm_CONTCLAUSE
    • DIAGNOSIS - UDFForm_DIAGNOSIS
    • INFO - UDFForm_INFO
    • JOBCANC - UDFForm_JOBCANC
    • JOBDETS - UDFForm_JOBDETS
    • LOADEND - UDFForm_LOADEND
    • LOADSTART - UDFForm_LOADSTART
    • pre-job - UDFForm_pre-job
    • POSTWORK - UDFForm_POSTWORK
    • PREWORK - UDFForm_PREWORK
    • PRODCANC - UDFForm_PRODCANC
    • PRODQTY - UDFForm_PRODQTY
    • PRODUCT - UDFForm_PRODUCT
    • SERVCANC - UDFForm_SERVCANC
    • SERVITEMCANC - UDFForm_SERVITEMCANC
    • TNCSC - UDFForm_TNCSC
    • TNCSD - UDFForm_TNCSD
    • TNCSDRIVERC - UDFForm_TNCSDRIVERC
    • TNCSDRIVERD - UDFForm_TNCSDRIVERD
    • TNCSDRIVERS - UDFForm_TNCSDRIVERS
    • TNCSpre-jobC - UDFForm_TNCSpre-jobC
    • TNCSpre-jobD - UDFForm_TNCSPREJOBD
    • TNCSS - UDFForm_TNCSS
    • TNCSVC - UDFForm_TNCSVC
    • VEHICLECHECK - UDFForm_VEHICLECHECK
  • Each field is a DIV classed as UDFField and by their field type:
    • UDFFieldT - Text
    • UDFFieldN - Numeric
    • UDFFieldB - CheckBox
    • UDFFieldX - Checkbox List
    • UDFFieldTSC - Tri-state Check
    • UDFFieldX2 - Tri-state Check List
    • UDFFieldDDL - Drop-down List
    • UDFFieldA - Text Area
    • UDFFieldL - Label
    • Button/Photo - omitted
  • Each Text, Numeric, DDL and Text Area field will show the following in this order:
    • The label classed as UDFFieldTitle.
    • The value classed as UDFFieldValue.
    • The subtext classed as UDFFieldSubtext, if present.
    • The post text classed as UDFFieldPost, if present.
  • Each field is strongly ID'd with the form ID and field ID, for example, for a UDF pre-job TNCs form:
    • UDFFieldT - Text
           Trailer ID
           TRAIL1
           Sub
           Post
    • UDFFieldN - Numeric
           Weight
           123.456
    • UDFFieldB - CheckBox
           
               <label><input type="checkbox" checked="checked" />Checked</label>
    • UDFFieldX - Checkbox List
           Narrow access issue
           
               <label><input type="checkbox" checked="checked" />Property entrance (front door)</label>
           
           
               <label><input type="checkbox" checked="checked" />Entrance to room of choice</label>
           
           
               <label><input type="checkbox" checked="checked" />Tight turn within the delivery route</label>
    • UDFFieldTSC - Tri-state Check
           
               <label><input type="checkbox" checked="checked" />Checked</label>
    • UDFFieldX2 - Tri-state Check List
           Narrow access issue
           
               <label><input type="checkbox" checked="checked" />Property entrance (front door)</label>
           
           
               <label><input type="checkbox" checked="checked" />Entrance to room of choice</label>
           
           
               <label><input type="checkbox" checked="checked" />Tight turn within the delivery route</label>
    • UDFFieldDDL - Drop-down List
           Enter Level
           Half
    • UDFFieldA - Text Area
           Comments
           Some comments
    • UDFFieldL - Label
SECTION 1:


UDF Formatting

Example:

SECTION 1: To be completed by the Oak Furniture Land Delivery Team
Why is the delivery difficult? Please tick the relevant box(es) below.
           Narrow access issue
           
               <label><input type="checkbox" checked="checked" />Property entrance (front door)</label>
           
           
               <label><input type="checkbox" checked="checked" />Entrance to room of choice</label>
           
           
               <label><input type="checkbox" checked="checked" />Tight turn within the delivery route</label>
           

           Obstruction that can't be easily moved
           
               <label>
                   <input type="checkbox" checked="checked" />Low ceiling</label>
           
           
               <label>
                   <input type="checkbox" checked="checked" />Bannister that reduces space to move need to manoeuvre item</label>
           
           
               <label>
                   <input type="checkbox" checked="checked" />Low hanging light fitting</label>
           
           
               <label>
                   <input type="checkbox" checked="checked" />Existing large furniture</label>
           

           Other, please give details
SECTION 2: To be signed by the customer
I acknowledge that there is not safe, clear and adequate access for delivery, as required under sections 9.8.1 and 9.8.2 of the JB Global Limited's terms and conditions. I wish to proceed with the delivery and have been advised of the risk of damage to property which might occur as a result.
8.1 | Please check the measurements and delivery access to Your home. It is important to check the measurements of Your Products by visiting Our Website or by calling Our customer service team. Please ensure that there is adequate doorway and stair access. We cannot accept any liability for any extra costs incurred by You as a result of incorrect or incomplete measurements or information supplied by You.
8.2 | Please check that the route from the lorry to Your room of choice is safe and free from potential problems or hazards. As Our staff have not visited Your home and cannot advise whether Your Products will fit, We ask that You take reasonable steps to ensure that the Products can be successfully delivered to You. This includes making sure that the lorry can get to You and measuring any door or ceiling heights, plus twists and turns (including Your stair banister) that might cause difficulties when We deliver. Your order will typically be delivered via a large lorry, so please be sure Your property is accessible for this type of vehicle. If You think there may be an issue, please call Us prior to delivery.
   ...
RETURNS ONLY
           I, the customer, confirm all delivery labels containing my personal details have been removed prior to the item being returned.


The following standard styles will then be available to be used: 

   .UDFForm {}
   .UDFForm > div {}
   
   .UDFField {}
   .UDFFieldL {}
   .UDFFieldT {}
   .UDFFieldN {}
   .UDFFieldB {}
   .UDFFieldX2 {}
   .UDFFieldTSC {}
   .UDFFieldDDL {}
   .UDFFieldX {}
   .UDFFieldA {}
   
   .UDFFieldTitle {}
   .UDFFieldValue {}
   .UDFFieldSubtext {}
   .UDFFieldPost {}
   .UDFFieldItem {}


The following style is recommended as a default: 

   .UDFFieldA .UDFFieldValue {
       min-height: 3em;
   }
   .UDFFieldItem {
       padding: 0.2em;
   }
   .UDFFieldX > span {
       padding: 0.5em;
       display: block;
   }
   .UDFFieldSubtext {
       width: 65%;
       float: left;
       font-size: 0.5em;
   }
   .UDFFieldPost {
       width: 30%;
       float: right;
       font-size: 0.5em;
   }


Design considerations

Each field can be styled by ID or class, with class per field or class per field type.

Each element of a field type can be classed individually by chaining the styles. So, title can be styled generically through ".UDFFieldTitle", and specifically for Text Areas using ".UDFFieldA .UDFFieldTitle".

As forms are ID'd by the UDF type, each UDF form can be styled completely separately by chaining the the styles. So, a Pre-job field may have a black border, while a Job UDF field may have a red border. This would be styled as follows: 

   div#UDFForm_TNCSPREJOBD .UDFField { border: solid black 1px;}
   div#UDFForm_JOBDETS .UDFField { border: solid red 1px;}

This allows for generic styling of all fields uniformly, with exceptions for certain forms, field types or specific fields.


Mobile Device Changes

On completion of a pre-job signature, the callback function will be modified to check the index of the T&Cs used (p_intTncId). If this index is non-0, then the T&Cs used are from the standards created against the job group - this functionality will remain unchanged.

If the index is 0, the completed T&Cs will be saved in SIG_TNC_CHECKS of the PDASIGNATURE record created.


New POD Report Format

The new POD report will be formatted as described in the requirements.

A prototype has been created in the development environment, as shown in the overview section.


Notes:

  • "I, the customer"... - this is fixed text, formatted for job type i.e. "receipt" for deliveries and "collection" for collections.
  • The Failed Delivery Checklist section will be displayed only if the job has been cancelled.
  • The new back page and footer will be part of the final footer, not the page footer.
  • The new back page will be sectioned in a div that will throw a page break when printed, repeating the header and populated from pre-job T&Cs.
  • The Difficult Delivery Disclaimer (sections 1 and 2 and signature section on the back page) will be produced from the pre-job T&Cs for delivery jobs. This will be created from the UDF element directly i.e. EPOD_SIGNATURE.SIG_TNC_CHECKS.
  • The Difficult Delivery Disclaimer signature section will be populated from the data on EPOD_SIGNATURE.
  • The Returns Only section will be produced from the pre-job T&Cs for delivery jobs.
  • The Returns Only signature section will be populated from the data on EPOD_SIGNATURE.
  • The Difficult Delivery Disclaimer will only be present if there is a pre-job signature for a delivery job.
  • The Returns Only section will only be present if there is a pre-job signature for a collection job.
  • In the case where this is a delivery job and no difficult delivery disclaimer has been issued, the back page will be omitted (hidden).
  • The pre-job T&Cs will be formatted using the new classes for styling UDF forms.

The report will be created as a new POD report, not over-writing the existing report.


TEST PLAN

Test Script / Scenario ReferenceJB Global POD Note ChangesCall Number(s): 354567
Test Script / Scenario Descriptiondescription of what is to be achievedPASS / ISSUES / FAIL
Menu AccessWhere on the menus the item can be found 
Pre-requisitesThe prerequisites of the testTested By:
 
Test ObjectiveThe details of what each group of tests is to achieveDate:
 



Step Action Result Remarks P/F
1 Area being tested in this cycle      
  Any notes or prerequisites for the tests following.      
1.01 The actions to follow The expected result    
1.02 The actions to follow The expected result    
1.03 The actions to follow The expected result    


APPENDIX A: QUOTE & DOCUMENT HISTORY

Cost Details
Activity Estimate
No. of Days		 No. of Days Rate per Day (£) Cost (£ Exc. VAT)
Requirements 3.00 3.00 750 £2,250.00
Change Request Evaluation 0.00 0.00 750 £0.00
Functional Specification 1.50 1.50 750 £1,125.00
Technical Specification 0.00 0.00 750 £0.00
Development 2.00 2.00 750 £1,500.00
Testing and Release 0.75 0.75 750 £562.50
Implementation 0.50 0.50 750 £375.00
Project Management 0.50 0.50 750 £375.00
 
TOTAL 8.25 8.25   £6,187.50
Estimate excludes training, release to live and go live support.

References

Ref NoDocument Title & IDVersionDate
1REQ 354567 JB Global POD Note Changes1.118/02/2019


Glossary

Term or Acronym Meaning
General Definitions
EPOD Electronic Proof of Delivery. The OBSL EPOD system is CALIDUS ePOD. This also comprises the basis of the Service Completion system CALIDUS eServ.
Server The portion of the CALIDUS ePOD/eServ systems that controls all the data and sends information to and receives updates from the mobile device.
Mobile Device; PDA The device used by the driver to perform the jobs. Typically an Android mobile device or tablet.
Site The site usually defines the depot, business or the transport group (carrier). It can be set to any value required by the customer. All transactions data (for example, loads and jobs) and standing data (for example, vehicles and uses) belong to a site. An EPOD user, on a device or in the Admin screen, can only see data for one site at a time.
Load A single journey for the driver with a set of work attached. A load is identified by a unique load ID. This may also be referred to as a worklist or workload.
Job Also Consignment. A single task for the driver as a specific location. This could be the collection of goods or the delivery of goods. Jobs may also be Services (for example, servicing, installing or de-installing a boiler). A job is identified by a unique job ID but can also have other references held against the job (e.g. job code, SO number, customer reference and external reference).
Job Group Jobs must be tagged with a Job Group. All jobs tagged with a single job group are processed in the same way. The job group has configuration associated to it to control such items as: POD/POC Report settings; Pre-Job actions (such as signing at a gatehouse); Post-Job actions (such as who signs for the item, are photos required); configurable fields required for entry for the jobs; Terms and Conditions displayed and; driver/user process (such as photos required for cancellation, comments/notes allowed). The job group can be used for any or all Sites, and the configuration against the job group can be different in each site. Job Groups can also be restricted from Admin and Remote users, so that certain users only see jobs for certain groups.
Container A generic term for any object that contains the items being collected or delivered. Examples of containers are: Pallet; Package; Carton; Item; Cage. A special container "Loose Products" - see Product below. A container is identified by a container ID which is unique to this physical container.
Product A product is any goods that are being collected or delivered where the product has a 'Product Code' which identifies what the product is but which does not uniquely identify each individual item. A product will also have a quantity associated with it to indicate how many items of this 'Product Code' are being collected or delivered. Products can either be processed within a 'Container' or as 'Loose Products' without a 'Container'.
Owner The owner of the order that created the job. Typically this is the sales team that took the order and will be responsible for dealing with queries from the customer regarding the status.
Operator; Executor The Site (depot or carrier) that is executing the load or loads that are involved in the delivery of the items.
Item Related Definitions
Job Code A reference associated with a job or job(s). This reference is common to connected jobs, for example this would be the same on both the collection of goods and the associated delivery of the same goods. Typically this would be the transport unique reference.
SO Number A reference associated with a job which indicates the "Sales Order Number" this job is associated with.
Customer Reference A reference associated with a job which has been provided by and will be recognised by the customer.
External Reference A reference associated with a job which does not match any of the existing references, usually because it has been provided by an external system.
Pallet An alternative for 'Container'. The term pallet is used when the operation only uses portable platforms as the container for goods.
Package An alternative for 'Container'. The term package is used when the operation only uses boxes or wrapping as containers for goods.
Package Code A code representing the type of 'Container'.
Package Desc A description of the type of 'Container'.
Product Code A code which identifies what a product is.
Item A generic term for any individual item that can be collected or delivered. An item can represent a 'Container' or a 'Product'. This can also be used as an alternative for 'Container' when the operation only treats the goods as individual items, i.e. not as identifiable products.
Service Item An item which will be serviced by a service job. See action 'Service'.
Issue Life The time after which an item is no longer fit for purpose.
Pack Size; Case Quantity A product may consist of a full quantity of items, inside a pack. The Pack Size (or Case Quantity) defines the amount of this product contained in a single pack. For example, if there are 85 items to deliver, with a pack size of 24, the number of full packs is determined to be 3 (24 * 3, or 72), with the remaining (13) being 'loose' quantity. This is displayed as "3/13" on the mobile application.
UOM; Item Type Unit of Measure; The major (case) UOM. This can optionally be displayed on the mobile device when changing product quantities.
Product Type A classification of the product being delivered. For example, a company may deliver 7 different mortar products and 80 different concrete slab products. The Product Types may be set to "MORTAR" and "SLABS". This may be used to attach additional configuration, changing the data required when collecting or delivering these product types.
Status Definitions
Status An indicator of how far through the processing a 'Job', 'Container' or 'Product' has progressed.
Pending A status indicating that the processing has not yet started, but is required to be completed.
In Progress A status indicating that processing has started but not yet finished.
Complete A status indicating that the 'Job', 'Container' or 'Product' has been collected or delivered.
Complete (Amended) A status indicating that the 'Job', 'Container' or 'Product' has been collected or delivered but that some changes or amendments have been made. This means that not everything that was planned to be collected or delivered was collected or delivered, some items may have been cancelled or some products may only have had some of the planned quantities collected or delivered.
Complete (Claused) A status indicating that the processing has been finished but that a 'Clause' condition has been recorded for this item.
Claused See 'Complete (Claused)' and action 'Clause'.
Cancelled A status indicating that the processing of this item or job is no longer required.
Cancelled at Collection A status indicating that the delivery of a container or product is no longer required because the associated collection of this container or product was cancelled.
Submitted An optional status that applies only to a 'Job' and which occurs after the 'Job' has been completed. This indicates that any time and expenses information recorded for the 'Job' has been submitted back to the server and can no longer be altered.
Action Definitions
Start An action associated with a 'Job' meaning the driver is about to start the processing of this job or jobs. This action will mark the job(s) with a status of 'In Progress'.
Arrive A conditional action associated with a 'Job' meaning the driver has arrived at the location the goods should be collected from or delivered to.
Continue An action associated with a 'Job' meaning the driver has previously performed the 'Start' and/or 'Arrive' action and has exited the processing screen but is now going to continue the processing.
Collect An action associated with a specific 'Container' or a 'Product' meaning the driver has collected the 'Container' or 'Product'. This action will mark the 'Container' or 'Product' with a status of 'Complete' or 'Complete (Amended)'.
Collect Claused An action associated with a specific 'Container' or a 'Product' meaning the driver has collected the 'Container' or 'Product' but with a condition under which the collection was accepted. This action will accept the clause condition and then mark the 'Container' or 'Product' with a status of 'Complete (Claused)'.
Deliver An action associated with a specific 'Container' or a 'Product' meaning the driver has delivered the 'Container' or 'Product'. This action will mark the 'Container' or 'Product' with a status of 'Complete' or 'Complete (Amended)'.
Deliver Claused An action associated with a specific 'Container' or a 'Product' meaning the driver has delivered the 'Container' or 'Product' but with a condition under which the delivery was accepted. This action will accept the clause condition and then mark the 'Container' or 'Product' with a status of 'Complete (Claused)'.
Clause An action associated with a specific 'Container' or a 'Product' that has already been collected or delivered meaning the collection or delivery has been accepted with a condition. This action will accept the clause condition and then mark the 'Container' or 'Product' with a status of 'Complete (Claused)'.
Cancel An action associated with a 'Job', 'Container' or 'Product' meaning the collection or delivery will not be performed for this 'Job', 'Container' or 'Product'.
Submit An optional action which can conditionally be carried out after a 'Job' has been collection or delivered meaning that any/all required expense or time recording for this 'Job' has been completed and can be submitted back to the server.
Service A service of a service item or items. Typically, Installation, Deinstallation or Service. The process of a service usually encompasses Pre- and Port-work checks, information gathering and diagnosis and resolution notes. Additional references (MC Refs) may also be captured.
Actioned A general term describing completing a job. So, 'Actioned' may be used instead of 'Collected', 'Serviced', 'Delivered'.
Consolidate The action of taking several jobs and linking them together, so they are actioned at the same time with one start, arrive and signature.
Deconsolidate The action of taking a consolidation of jobs and breaking them down into the component jobs again.
Job Swap The action of selecting an existing load not assigned to the user, and picking jobs to transfer onto the user's load.
Signature Capture Usually the final action of a job, where the customer's name and signature are entered.
Other Definitions
Reason Code A code which represents the reason that a job was cancelled or an item was cancelled or claused.
Vehicle The vehicle used for transporting the goods.
Vehicle Checks Also Defect Checks. A series of questions representing the results of checks intended to ensure the vehicle is in an acceptable condition.
Metrics Entry A series of questions to capture information either at the start or end of a 'Load'.
Driver The person performing the collections or deliveries; the user of the device/application.
Engineer The person performing the services; the user of the device/application.
Customer The person/company the goods are being collected from or delivered to.
Signatory The name of the person providing a signature.
T&Cs Terms and Conditions. The T&Cs are shown when signatures are prompted for. The text of the T&Cs are defined in the system itself.
Transfer Load A load select from which to swap jobs to the user's load.
Base E.g. 'Return to Base'. Typically the depot from which the driver departed.
Unplanned Ad Hoc Collection A collection job that is created by the driver, usually after delivering to a customer.
Ad Hoc Container Entry/Scanning The process of adding containers (items) to a job that have not been pre-advised on the job.
Completion Report POD, POC, Service/Work Report.
Load Assignment The action of assigning a vehicle and/or a driver to a load.
Job Assignment The action of putting jobs onto a load.
Collection/Delivery Windows; Access Windows Periods of time between which it is acceptable to deliver or collect from that customer. This has limited use in the system, mostly for reporting purposes.
Location/Map Terms
Lat-Longs; GPS Co-ordinates, GPS Position Latitude and Longitude co-ordinates, specified together as a single entity, identifying the exact position of a location. There are multiple formats - CALIDUS ePOD uses decimal notation, for example "53.3490818,-2.8521498" identifies the OBS Logistics office building in Liverpool.
GPS Global Positioning System; the satellite system used to obtain a GPS position, for use with navigation and location positioning.
Geocode; Reverse Geocode Geocoding is the process of obtaining lat-longs from an address. Reverse Geocoding is the process obtaining an address from lat-longs.
Geofence; Geofence Break A Geofence is a perimeter around a location. A Geofence Break occurs when a device passes through this perimeter on entry or exit from the location.


Authorised By


Barry Preece
OBS Project Manager
_____________________________

Nav Mohammed
Customer Representative
_____________________________
Retrieved from ‘https://calidusassist.adcservices.apteancloud.com/calidus-assist/OBS/index.php?title=TEST&oldid=7001’