Case Study : [Manufacturer]: Reducing Redundant Documentation

Case Study : [Manufacturer]: Reducing Redundant Documentation

Brief

The client needed to streamline accounting documentation and remove multiple instances of identical files with different file names and headers. Becoming Machinic created a PDF analysis process to arrest duplicate processes to minimize system load on the client’s IBM i system.

Problem

Client was experiencing high system loads due to duplicate processes running in their content management system. Their system generated PDFs that were often copies of PDFs already in their content management system, however, the PDFs had unique headers each time they were produced, but were not distinct. As such, you couldn’t simply compare the files themselves; you had to look at region content to distinguish. This was not possible on the IBM i. This problem affected the accounting department’s ability to invoice clients and track invoices as well. ERP integration was also needed.

Solution

An automated business process was created to arrest these duplicate processes as far upstream possible. This happens quickly and automatically, making our client’s process substantially more efficient, saving them time and effort while improving speed and accuracy.

Process

The client’s RPG code submits PDF documents to a Nomad API endpoint using the NAPTIME library. Parameters include the two files to compare, and the regions of the files that are to be compared. Nomad runs the PDFs through its classification system and reads the text from the regions identified, and returns a judgment as to whether the regions are identical or not for the client.

Highlights

IBM i, RPG, NAPTIME, document manipulation, business process automation, IBM i (AS/400), RPGLE

Industry

Manufacturing
SIC Code: 35
NAICS Code: 33,333131

Location

West Virginia, USA

Product

Nomad, NAPTIME

Business Process Optimized

PDF analysis from RPGLE on IBM i