|
|
## WDT Technical Debts
|
|
## WDT Technical Debts
|
|
|
|
|
|
|
|
There are many causes that the technical debts have accumulated especially in clearance module.
|
|
There are many causes that the technical debts have accumulated in the WDT module.
|
|
|
|
|
|
|
|
* Required to implement the module as soon as possible (due to pandemic).
|
|
|
|
|
* Some specific AMTI departments have specific way of dealing with clearance routed to them.
|
|
|
|
|
* Some specific AMTI Approvers have specific timeline to process the clearance.
|
|
|
|
|
* Routes are dynamic and varies to employee application.
|
|
|
|
|
* Unforeseen specification that was eventually needed and was not advised early on regarding such scenario.
|
|
|
|
|
* **I'm partly to blame as I haven't expected such features to be requested.**
|
|
|
|
|
|
|
|
|
|
However, this is not a wiki to discuss the reasons why I have technical debts.
|
|
|
|
|
|
|
|
|
|
|
* There was a previous developer that created the WDT module.
|
|
|
|
* Most code logic of the WDT module has been deprecated and was replaced.
|
|
|
|
* Some code functions used in the WDT is impossible to leave as it relies heavily on the oracle database which I am not very familiar of.
|
|
|
|
* I am assigned to develop the WDT mobile app. Not the web module
|
|
|
|
|
|
|
|
----------
|
|
----------
|
|
|
|
|
|
|
|
|
|
|
|
|
## Tech Debt 1: WDT SMS/Email notification
|
|
## Tech Debt 1: WDT SMS/Email notification
|
|
|
|
|
|
|
|
|
SMS and Email notification relies heavily on the Email [AIS > SMS Gateway](https://ais.amti.com.ph/sms) module. However due to the intricacy of this module I wasn't able to recycle their work as a basis for the notification. I have only copied the wdt.php functions into the `application/libraries/Mobile_wdt.php`.
|
|
|
|
|
|
|
|
I have no solution over this tech debt was only hoping to have a better standardized Notification module.
|
|
|
|
|
|
|
|
----------
|
|
----------
|
|
|
|
|
|
|
|
|
|
|
|
|
## Tech Debt 2: Implementation of WDT Mobile App Ver 2021.
|
|
|
|
|
|
|
|
During my tenure. I had many features created to the WDT App Ver 2019 that I wasn't able to push to production due to different concern.
|
|
|
|
* A Warehouse delivery personnel I closely worked to regarding the module resigned
|
|
|
|
* We are unable to collect all company warehouse mobile phones as drivers schedule is always moving and strict.
|
|
|
|
* Requiring to demo the new features to the drivers
|
|
|
|
|
|
|
|
However, implementing the **WDT App Ver 2021** will reduce a the bug that usually occurs in the old version. Not only that there are bug fixes. There are many new features that can be proved useful to our drivers and better user interface and dialogs that are not only informative and reliable.
|
|
|
|
|
|
|
|
## Tech Debt 3: WDT Modules that are not prioritized
|
|
|
|
|
|
|
|
There are a lot of WDT Modules that is requested but not prioritized as it is considered only as a **"Nice to have"** causing its delay even further.
|
|
|
|
|
|
|
|
---
|
|
|
|
|
|
|
|
**WDT Realtime location:** Get the realtime location of the delivery using their mobile phones as tracking device.
|
|
|
|
- This is a mobile app feature that was included,removed, and then re-included and again removed. I have proposed different solutions on this feature but would all take time to develop and implement so it was not prioritized as it does not generate revenue nor hasten the delivery process.
|
|
|
|
- One fast possible solution to implement this feature is to use **Google's Firebase API** in the GeoLocation section. But due to the requirements of google by the time is priced per API call and the threshold that could be consume might exceed to the free package of the API plan.
|
|
|
|
- Another solution that I have considered is to ask the **Service Desk** to host an empty server that contains a Map like GoogleMaps using the **OpenStreet Open source Project**. So API calls will be unlimited as we own the map and server in the first place. I have seen the feasibility of this project, and it is feasible. I have also considered doing this OpenStreet project as it could be used by other AIS modules that requires a dependency to geo location.
|
|
|
|
|
|
|
|
> But again, due to the lack of usefulness and resource to exert to this project. It has been abandoned for a year now.
|
|
|
|
|
|
|
|
---------
|
|
|
|
|
|
|
|
**WDT Survey:** Get the customer survey with the AMTI's delivery service.
|
|
|
|
|
|
|
|
- This is a mobile app feature that will be present after the delivery personnel tags the delivery status. This survey will be visible to the WDT Module in the AIS and could generate a summary of information regarding to customer inputs.
|
|
|
|
|
|
|
|
> This feature can be easily implemented however the feature is not prioritized due to other concerns and the warehouse team requested a decent **stylus** that could be used as a signing pen for the **WDT App Signature capture feature**.
|
|
|
|
>
|
|
|
|
> According to the warehouse team:
|
|
|
|
> > *"nakakahiya kung yung client papapirmahin natin sa mobile device tapos wala namang pen. Napaka hirap pumirma ng daliri lang gamit"*.
|
|
|
|
>
|
|
|
|
> Another reason that this feature is not implemented is that drivers tend to not use the mobile app's feature. Image capture and Signature capture is not used by our fellow delivery personnel and the only reason we are getting at is:
|
|
|
|
> >*"Hassle at di marunong"*.
|
|
|
|
>
|
|
|
|
> So in case of implementing this feature. It is first advisable to confront them what is their workflow in delivering the parcel to our customers.
|
|
|
|
|
|
|
|
----
|
|
|
|
|
|
|
|
**WDT Client Notification**: Notify not only the Sales, Logistics and Warehouse team. But also the customer to the delivery.
|
|
|
|
- This is also an action based according to the drivers inputs and the warehouse and logistics personnel as well. This is will be based according to the current status of the delivery from the **PO (Purchase Order)** up to the **SI (Sales Invoice)**.
|
|
|
|
- It was initially planned to avail an **SMS service** to have **custom Sender ID** for AMTI. This will be budgeted by the company and has been discussed for a long time.
|
|
|
|
> This is requested only recently by the warehouse team but was scheduled to be discussed and developed officially by the end of 2021.
|
|
|
|
>
|
|
|
|
> I advice that when implementing this feature. It is required to fix the [AIS > SMS Gateway](https://ais.amti.com.ph/sms) module first as it should be used as a management module for this kind of features. Not only the WDT Module can benefit from this module but all AIS Modules.
|
|
|
|
|
