Binh Duong Province, 2024 December 06

Dear Mr. Ding,

I am writing to express my sincere admiration for your leadership and
innovative spirit. As a packaging department employee who joined the company
in early May, I have been deeply impressed by your youthful mindset and
forward-thinking approach to management. Your ability to incorporate new
technologies and creative solutions into our operations is truly inspiring.
As previously mentioned, I am currently working in the packaging
department and frequently use the company's ERP system. I went through the
process of upgrading the application's new features. During this process, I have
identified some limitations that still exist in the application. For this reason, I
would like to present more details in this letter.
"My English proficiency is limited, so I used Google's Gemini AI to
translate and structure the content above. However, I assure you that all ideas
and opinions expressed are my own."

Yours sincerely,

My information
Name: Lâm Vũ Linh.
Phone Numer: 087 87 02 2567.
Email: [email protected].
Zalo account: 0559 35 34 11.
I. There are too many steps involved in printing labels:

Printing a label for a work order requires over 9 clicks, 3 keystrokes, and opening 5
windows; the app is really cumbersome.
 II. Changing the customer name, the label template is very manual.
We have three different label templates for different customer segments.

The basic label template contains all the necessary information and is the most widely used.

The template without the Riken logo is replaced with detailed information from the customer.
Previously, we used it for Shengxin and LacVien. Now, we can also use it for Riken Central
Region.
In addition to the two templates mentioned above, we have a third, more complex template.
This template is specifically designed for the Riken Industrial customer group, which consists
of multiple sub-clients. Essentially, the template used by this customer group is similar to the
first template presented, but the customer name must be changed to reflect the specific sub-
client. However, the default customer name displayed in this case is "Riken Industrial".
Therefore, to modify the customer name, we must manually create numerous templates for
different sub-clients, leading to a labor-intensive printing process. This contradicts the
application's goal of automation and significantly increases printing time, making the
application more complex to use. In fact, I'm the only one in the production department who
can effectively use it.

In an ideal scenario, without any technical glitches (which, in reality, the application still has),
the label printing process would involve the following steps: searching for the production
order, clicking to print labels, entering the quantity per bundle, creating the label, selecting
the template, previewing, and finally, confirming the print job. This process is unnecessarily
complex. As a developer, I would streamline it to only require the user to input the production
order number, select the quantity, and initiate the print job.

This is a list of the label templates I created to temporarily solve the problem when dealing
with the Riken Industrial customer group.

The above solution is only a temporary fix. It has many drawbacks such as time-consuming
searches through a long list, a complex interface that few people can use, a high risk of errors
due to time pressure and workload, and a lack of professionalism and automation. Given the
above, I propose the following solutions.
 1. Soft solution (where there's a problem, fix it there)
Having joined the company only six months ago and having access to the
ERP system only from a production department perspective, my assessment
is limited to the production department's needs. Therefore, for this solution,
I suggest contacting the software vendor to modify the system as follows:

C# code :

public string GetCustomerName(string productionOrder)

switch (productionOrder)

case "T3039":

return this.note;

/*

That was filled by assistant when he/she create a productionOrder with

RikenIndustrial’s member name.+

*/

default:

return this.customerName; // This is customer’s shortname

}
 2. Hard solution

The current Erp application is written in C#, a programming language developed by Microsoft, built
upon the C/C++ foundation and utilizing the .NET Framework, also developed by Microsoft.
For the software development company (our ERP implementation partner), they have pre-built libraries and
modules for ready-to-use functions, which can be stored and reused later.
For the software development company (our ERP implementation partner), they have pre-built
libraries and modules for ready-to-use functions, which can be stored and reused later.
When they receive a custom application request from our partner that includes similar functions
already existing in their repository, they will extract and modify these functions to meet our specific needs
of customers (us).
Limited Customization:

 Not a perfect fit: Libraries and modules are designed to cater to a wide range of needs, which might
not perfectly align with the specific requirements of your project. Excessive customization can
degrade performance and introduce unexpected issues.
 Structural challenges: If the library's structure doesn't align with your project's architecture,
integration and customization become more complex.

Low Maintainability:

 Difficulty in understanding code: Without a deep understanding of the library's inner workings,
debugging or upgrading can be challenging.
 Vendor dependency: If the vendor ceases support or changes the library's structure, your project
will be adversely affected.

Performance Issues:

 Suboptimal performance: Libraries might include unnecessary features, leading to larger

application sizes and reduced performance.
 Resource conflicts: Using multiple libraries simultaneously can cause resource conflicts and impact
application stability.

Security Concerns:

 Security vulnerabilities: Libraries may contain undiscovered vulnerabilities, posing risks to your
application.
 External threats: If the library is developed by a third party, you have limited control over its
quality and security.

In conclusion, we should develop the application in-house by our own team. This will completely
address the aforementioned limitations.

III. Specific method: step by step:

Because ERP is a large application with many different functions and business processes, we need
to adopt a phased approach. We should develop each function individually and link it to the existing
application through APIs. This will allow the current application to leverage data from the new
application, thereby addressing its reporting issues. I'd be happy to give you a more detailed verbal
explanation of this approach if you're interested. Thanks for your readed.