Over 10 years of maintaining the GRANDIT ERP system

GRANDIT is a Web-based ERP software tailored to meet the specific cultural and operational needs of Japanese enterprises.​

• Region: Japan
• Industry: ERP
• Solution: GRANDIT ERP
• Duration: From October 2012 to Present
• Size: 1900MM (PEAK PERIOD: 6/2023 ~ 9/2023, averaging 40MM​)
• Service: IT Management Services

  – System maintenance​

  – Version upgrades (Database migration + UI updates)​

  – Migration (UI adjustments)​

  – New feature development​

  – Source code standardization

• Technology:

  – Framework: GRANDIT​

  – Backend: C# – SQL Server​

  – Frontend: Asp.Net

• – During the use of the ERP GRANDIT system, end users may encounter business logic errors. Additionally, there may be a need to add features to meet new business requirements.​
• – Furthermore, after a period of use, as the volume of data increases, the system may experience slow processing speeds and reduced efficiency, requiring improvement.
• – For each end user, to meet the operational needs of the business as well as the specific business requirements of each industry or sector, in addition to using the system’s standard features, there is always a need for customization or the addition of add-on features.
• – Due to the discontinuation of the Internet Explorer browser, GRANDIT has upgraded to a new version to ensure the program can be used on multiple browsers.​​
• – Companies using Grandit version 1 and version 2 will need to upgrade to the latest version if they wish to continue receiving support from GrandIT.​​To meet the specific business needs of the end user, it may sometimes be necessary to explore and integrate technologies that are not part of the system’s core.
• – When large corporations complete the development and deployment of the GRANDIT system for one subsidiary, they often hope that other subsidiaries developed later can leverage the shared common components of the system. However, with the current method of directly modifying the standard source code, this is not achievable.​

• – Provide personnel with technical experience as well as an understanding of the ERP-Grandit system’s business processes, capable of handling complex technical tasks such as tuning SQL to improve performance or addressing requests that require a deep understanding of the system’s business logic.
• – Assign personnel who understand the business processes of the ERP-Grandit system and have experience in tasks ranging from design to UT testing and IT to carry out development.​
• – ​Assign a member with experience working as a BA to meet with the customer, gather their requirements, and create a definition of the requirements, building functional requirements that can integrate with the standard ERP-Grandit system.​
• – Assign experienced members to study the rules provided by GRANDIT and organize them into categories to make the upgrade process easier and more accurate.
• – It is proposed to the customer to separate the current source code into two sets: one containing Addon Customize processing and the other equivalent to the standard source code.​
• – After the customization processing is separated, the customer wishes to conduct NUnit testing to ensure that the source code separation is error-free.
•  
• Example: Method of migration:​
• Download PDF file to see more.

1. Maintenance Achievements:

• Investigation and detection of potential errors in standards: Conduct investigations and detect standard errors during system upgrades, and tax changes, and report them to GRANDIT.
• External system integration​:
  • – Successfully investigate and resolve integration issues with external systems like Paples.​​
  • – Customize the system to enable the use of its functions on mobile web platforms.
• ​​Performance improvement​:
  • – Improve the time for generating payment request forms for BO* customers from over 3 hours to under 10 seconds.
  • – Make adjustments so that TM* customers can generate payment request forms for over 100 processes simultaneously within 5 minutes, a task that previously took nearly 2 hours.

2. development Achievements:

• * Develop many new features to meet the needs of various businesses.​
  • – Develop a transaction feature for users to allow the creation of 4 forms (Order, Purchase Order, Purchase, Sales) on the same screen simultaneously.​
  • – Develop the Quotation and Request for Quotation (RFQ) features for JPC users to allow supplier selection based on various business criteria.​
  • – Develop an additional feature for creating supplementary costs for multiple Purchase forms to minimize the time spent on creating supplementary costs when purchasing goods from overseas.
• * ​Use technologies outside of the standard technology to develop new features.
  • – Use SVF to develop report features (Invoice forms, Profit forms, etc.) for KBK users.​
  • – Use EDI XML Translator to convert data from XML to CSV and perform import into the system.

3. Version-up Achievements:

• * Successfully created the DB migration tool: Successfully developed a DB migration tool that ensures data accuracy and integrity.
• * Based on the provided UI modification guide, the tool was created to identify the positions for editing: Successfully created a tool to identify the positions that need modification, ensuring that no rules are overlooked in the Addon and Customize screens.
• * ​Developed a testing framework to ensure quality: After completing the first Trailer project, LUVINA proposed a set of criteria to verify the accuracy of the modifications.

4. Migration achievements:

• * ​Modify the system to run on multiple browsers: Update the UI to ensure the system operates on browsers other than IE without requiring a version upgrade to GRANDIT version 3.
• ​* Cost savings for End Users: Compared to upgrading to GRANDIT version 3, the cost of performing the migration is reduced by 50%.​​​​

​5. Standardization source code achievements:

• * Successfully separated the customized source, enabling easier source code management: The user’s development source was successfully divided into two sets: one containing the GRANDIT standard source and another with the Customize source. This separation facilitates the application of GRANDIT’s standard patches and simplifies the development of new features.​
• ​* The amount of reusable functionality is 30%: The number of reusable common features exceeds 30%.​
• * The smoke test duration during development was reduced by 80%: The amount of reusable NUnit code reached 80%, thereby reducing the smoke test time to only 20% of the time required for testing the first company.​