Skip to content
Case StudiesAgriculture and Grain Supply Chain

Scoular Brings Business and IT Together on IBM i with CoderFlow

A 14x productivity gain, by IT Manager Brad McDaniel’s measure, and business analysts querying IBM i directly inside

Case Study Highlights

  • Industry: Agriculture and Grain Supply Chain
  • Technology Legacy: IBM i (AS/400), RPG, with production code dating back to 1984

Core Operations:

  • Contract and Trade Risk Management (CTRM), covering 80 to 90 % of all company transactions
  • Grain scale ticket processing and contract settlement
  • Customer service and account management (MyScoular)
  • Technology Approach: Business and IT on one platform. Authorized business and data users can use CoderFlow to investigate IBM i data through a controlled, read-only environment, while IT maintains the development, security, and release guardrails.

Results at a Glance:

  • 14x productivity increase
  • Changes per deployment window: 4 or 5 before, 10 to 12 now
  • Business and data analysts now query IBM i directly
  • 1,800 tasks run through CoderFlow

The Challenge

Scoular is a 0 billion agricultural supply chain company built on more than a century of grain, feed, food, and biofuel expertise. Underneath that scale sits a Contract and Trade Risk Management (CTRM) system running on IBM i that handles 80 to 90 % of every transaction the company makes. Some of the RPG programs powering it were written in 19834, more than four decades ago, and they're still running the business today.

That longevity is a testament to the platform. It's also a growing risk. Like many organizations built on IBM i, the team led by Brad McDaniel, IT Manager for CTRM and Application Delivery, was watching the pool of experienced RPG developers shrink while the codebase kept aging. A nightly batch process moved grain scale ticket data through six or seven hops before landing on a reporting server, which meant customer service reps making decisions on a Tuesday afternoon were often working with Monday's numbers.

Scoular had already tried AI on the problem. An earlier experiment, an LLM answering questions directly against IBM i data, was inconsistent. "Any LLM you ask, you get a different answer every other time," McDaniel said. In an earlier desktop-based AI development experiment, the team had to manually copy IBM i source files to a local environment before the model could work with them.

The AI tools Scoular had evaluated at the time did not provide the controlled IBM i access the team needed. A server-based platform with read-only environments and no outbound network could.

Scoular has been a Profound Logic partner for more than a decade, running Profound AppDev. When the Profound Logic team demoed CoderFlow, the timing lined up with three other AI proof-of-concept efforts already underway within Scoular. CoderFlow stood out as the one built specifically for IBM i.

The Solution

The team used CoderFlow on two early proof-of-concept projects that addressed different parts of the IBM i application landscape.

The first was MyScoular, a web front end that gives customer service reps current contract and shipment information. It connects to IBM i through Profound Logic’s Profound API REST server, which cut out the multi-hop nightly process that had left the data a day old.

The second was the RPG-based scale-ticket processing that captures ticket weights in the field and feeds ticket data into CTRM. This was a rewrite of older RPG code, so it put CoderFlow to work inside the existing RPG environment rather than around it.

Together, the two projects showed that CoderFlow could support both web application development around IBM i and development within the existing RPG environment.

The business got access because IT stayed in control. CoderFlow operates within Scoular's existing software-development controls. Scoular's security processes include scanning pull requests and production releases, and the development and security teams created RPG-specific scanning rules to identify meaningful issues while reducing false positives.

Around that sits a set of guardrails IT holds:

  • A production-data environment accessed through an IBM i account with strictly read-only data permissions, allowing investigation and queries without the ability to update production data.
  • All code in Git, moved from development to test to production through Scoular's existing release tooling
  • Human review of the RPG areas where AI is weakest

Business users get answers on their own, inside limits IT sets and controls.

The Results

The Business Asks the System Directly

"Not only can your developers use it, but your business analyst or your project manager or your data analytics team can actually go in and ask the system and get the columns and all the characteristics they need."

Brad McDaniel, Scoular

At Scoular, that's already happening. A business analyst and a data analyst from the Power BI group query IBM i tables directly through the read-only environment, asking how the system works and getting answers themselves instead of waiting on a developer. McDaniel's director uses it for research too, tracing where employees repeat work or correct data by hand to find automation opportunities.

The credit watch report shows what that access replaces. A colleague in credit couldn't get customers onto the report, so McDaniel, who isn't a developer, handed the problem to CoderFlow before leaving on a Thursday. When he got back, the full writeup was waiting. CoderFlow had found that the colleague was using the wrong menu option, flagged 83 recent deletions from a related file that were worth a second look, and confirmed that the six customers he'd been trying to add were sitting in a daily file and would reach the night run once added the right way. The same investigation would have cost a developer 30 to 45 minutes.

"I did not have to go to a developer and pull them off project work."

Brad McDaniel, Scoular

MyScoular changed what the business sees, too. Customer service reps now work from current data, because Profound API REST server connects straight to IBM i instead of routing through the old overnight run.

14x Productivity

McDaniel puts Scoular’s overall productivity gain at 14x, and the project timelines point the same way. Two projects planned at roughly 14 months of combined traditional development were finished in under 2 months with CoderFlow, more than a 7x reduction in calendar time alone. Those were planning estimates, not a controlled benchmark, but the gap is hard to ignore.

The day-to-day numbers tell the same story. Scoular used to push four or five changes through each Tuesday and Thursday deployment window. Now it pushes 10 to 12.

The backlog moves faster too. Small items that once sat waiting now get cleared as they come up. One developer on McDaniel’s team hands her nagging little fixes to CoderFlow and stays focused on the bigger project.

"Our turnaround has gone from weeks to days."

Brad McDaniel, Scoular

The Bottleneck Moved

As development throughput increased, testing increasingly became the constraint in the delivery process.

"It used to be IT development time, we were the funnel bottleneck," McDaniel said. "Now it's testers. We're able to put so much out." It's a good problem to have, and a clear sign of what happens when a development constraint disappears.

Scale That Speaks for Itself

The developer-side numbers back it up. Scoular has run approximately 1,800 tasks through CoderFlow, touching more than 5,200 files across its use of the platform.

Comparing that output to the cost of outside help, McDaniel said: “There’s no consultant or human that’s going to get you that much benefit, unless you’ve got 10 or 12 of them on tap at over 100 bucks an hour.”

Team Adoption

A team of nine uses CoderFlow, including nearshore developers in Costa Rica and newer hires still learning IBM i. "We haven't had to spend hours and hours on training," McDaniel said. "It's been pretty intuitive." The team's application source is now maintained in Git, and when one developer moved to another project mid-stream, a teammate picked up her tasks and finished the work.

The Partnership Experience

McDaniel points to direct access to Profound Logic's team, including founder and CEO Alex Roytman, as a real differentiator. When Scoular sent over a list of ten CoderFlow enhancement requests, including task swim lanes and colorization, Profound shipped one in a day.

"Bigger companies like IBM can’t turn on a dime. With a smaller partner like Profound, you get a team that’s ahead of the curve, and they keep updating and improving the product on a very regular basis."

Brad McDaniel, Scoular

Looking Ahead

Scoular's next phase is proactive monitoring: having CoderFlow scan menus, night runs, and error logs on its own and surface problems before an end user ever files a ticket. The team is also exploring CoderFlow's QA mode and and looking at CoderFlow's development capabilities beyond IBM i

Scoular's IBM i system has run the business for four decades without a rewrite, and CoderFlow gave the team a way to keep building on it instead of around it. What started as two developer proof-of-concept projects became a platform where business and IT work from the same system, with IT holding the guardrails.

For McDaniel, that changes the question Scoular used to ask about the platform's future. Where the team once worried about finding RPG talent and whether it was time to rewrite the system, he now sees a way to futurize IBM i in place.

"CoderFlow changes how we think about the future of IBM i. We don't have to choose between preserving 40-plus years of business logic and updating the applications around it. AI gives us another way to understand that code, build APIs around it, and continue evolving the platform with a broader development team."

Brad McDaniel, Scoular

For Scoular, the value goes beyond generating code faster. CoderFlow provides another way to understand decades of IBM i business logic, making that knowledge accessible to newer developers and selected business and data users. That reduces dependence on a small number of people who understand the legacy environment and allows Scoular to futurize incrementally while preserving proven business logic.

Ready to bring business and IT onto the same IBM i system? Contact us at to get started.