Jargon Software - Customer Testimonials

Mobile software that integrates sales-order processing, inventory, field service, and inspections for small and large companies in any industry worldwide.

HOME

TECH

APPLICATIONS

What were the business drivers, requirements; i.e. the issues and business pain you needed to solve and how those issues were negatively impacting your company?

We needed to track pipe that was loaded on a truck in real time. Every second this process takes costs us money. We were originally using a telnet based system over a wireless link on handheld devices, but the problems with connectivity were terrible. If the user was behind a pile of pipe or a loader, they couldn’t get a signal. If a loader or truck drove in front of them, they lost the signal and possibly locked up the record in the database. Using the Jargon software, our users download their work orders and then upload the results as soon as they are done. This has streamlined the process considerably.

What was your decision criteria and process (how you made your decision/selection)?

Hmmm, nothing too complex, Jargon was the only company we found (researched on the internet) that could do what we wanted with our back end. There were some other products that appeared similar but they used generic ODBC drivers.

What were the most important issues that made you select Jargon vs. a competitor and what competitors had you looked at , and the specific reasons you selected Jargon over the competition at the end of the process?

Familiarity with our back end environment and experience doing similar projects . I’m afraid I don’t actually remember any of the competitors.

What were the positive results and benefits of implementing a Jargon solution and how did these things meet and exceed your expectations?

A complete absence of the lost connection issues that we had in the past. This results in a much smoother process for our outgoing truck loads. Basically they load up the truck with pipe, sync the handheld and when the trucker gets to the gate his bill of lading is waiting for him.

The ROI (return on your investment)?

We haven’t formally calculated it, but the money we spent was minor compared to the value of a days worth of truck loads of pipe. More importantly, the smoothness and efficiency of our trucking operations is a factor that customers take into account when awarding contracts, which are typically in the millions of dollars.

These contacts also often have late penalties which can be as high as $200,000/day. Obviously the more efficient we are the less chance we have of triggering these penalties.

What were the business drivers, requirements; i.e. the issues and business pain you needed to solve and how those issues were negatively impacting your company?

Our company was faced with decreased administrative fees from HUD. This means that our business income went down significantly. We needed to do more work with less people. We attacked the problem by thinking of ways that we could streamline out business processes. We are required to do physical inspections on more than 3,500 units per year. Traditionally, we would do these inspections on paper and then input (by hand) these inspections into our business systems upon returning to the office. We used Jargon software to write an inspection application that could be taken out into the field and then synchronized back at the office. Stage two should also allow us to upload/download inspection data remotely also.

What was your decision criteria and process (how you made your decision/selection)?

The IT department asked the business to do an analysis of time spent for the inspection process. It was determined that for each day of inspections it required the inspector a day before the inspections to get ready(schedule/map) and a day after the inspections to input all the data into the system and create letters. We developed an inspection mapping/scheduling system in Progress using Google maps to plot addresses and determine inspection routes to compliment to inspection system written in Jargon. We knew with these systems in place we could reduce the time it took to prepare for the inspection and the time it took to enter all the inspection data into our business system and create the letters (which we create automatically now). Our business criteria was to save inspector’s time and therefore allow us to do more inspections with less inspectors. Once we determined the effort required the business gave us the go ahead to spend the time and money to complete the project.

What were the most important issues that made you select Jargon vs. a competitor and what competitors had you looked at , and the specific reasons you selected Jargon over the competition at the end of the process?

When the challenge of the inspection system arose as a business priority we concluded that Jargon could be used to accomplish our goals. We liked Jargon’s understanding of our back office environment and the toolset they provided. It made programming much easier. We did not have to reinvent the wheel, we just needed to use the one already built by Jargon. Frankly, we were not aware of any Jargon competitors.

What were the positive results and benefits of implementing a Jargon solution and how did these things meet and exceed your expectations?

Using Jargon’s prewritten tools saved a ton of time. Working with Jargon support was great. The system infrastructure was easy to create using provided examples and some help from Jargon support. The cost of Jargon’s development environment was also very reasonable. I believe that if we had tried to create a similar solution without Jargon we would not have been successful.

The ROI (return on your investment)?

We are still in the process of rolling out these systems throughout our entire company. Once we are completed we should see a substantial time savings. We have four full time inspectors. We should be saving at least two days a week per inspector. (Four inspectors) x (Two days per week savings) x (Fourty Five week work year) = 360 days saved per year. That’s huge!

What were the business drivers, requirements; i.e. the issues and business pain you needed to solve and how those issues were negatively impacting your company?

In our segment our competitors had a mobile wireless solution and we did not. It turned from a nice to have into a must have which was causing Osprey to lose business. We had no choice but to add a wireless module to our product mix. We wsere late to the game in comparison to our competitors and we acknowledged this by bringing this product into the mix. We choose Jargon Software as a software partner and took a stance of equal to or best functionality at a price point 30 to 40 percent under the industry leader (StoreNext) – we have very similar functionality at a much better price point. The goal was to bring a product out that they would not cut price on.

What was your decision criteria and process (how you made your decision/selection) ?

We needed a development environment that would allow our business application developers s to focus on the business logic. After evaluating (writing some test programs) it was clear to us that the fastest and easiest way to get to where we wanted to be was by using Jargon mobile tools.

What were the most important issues that made you select Jargon vs. a competitor and what competitors had you looked at , and the specific reasons you selected Jargon over the competition at the end of the process?

Jargon mobile tools allows us to focus on what we know best. Jargon mobile technology calls 4GL business logic seamlessly. This is unlike Embedded VB or VB.NET which requires either using an ODBC connection or a call to ASP to retrieve the data from the database. The deployment of the application to the mobile devices is also an ease with Jargon mobile.

The ROI (return on your investment)?

By adding a wireless module to our product mix we are now able to secure business that we were losing in the past. It also opens up other business opportunities that we could not chase prior to having a mobile wireless module.

We were placed into a position to react since the marketplace for this product had been fairly well defined and the ROIs done that tell retailers mobile is the way to go for increased productivity and improved store level efficiency.

Based upon the business we have brought in with the mobile products we have several retailers that we would not have received orders/commitments from without it so the investment has clearly been a valuable one for the company.

What were the business drivers, requirements; i.e. the issues and business pain you needed to solve and how those issues were negatively impacting your company?

We needed a development product that worked with the Progress database and allowed flexible coding options to fit our primary application. Prior to Jargon, we found plenty of PDA application development products, but all of them were designed as primary application generators. We needed the PDA to act as feeder into our larger database application. Jargon not only had the knowledge, they also were also very receptive to our needs.

What was your decision criteria and process, (how you made your decision/selection) ?

We looked at a number of PDA application development packages over the course of a year. Jargon was the last package that we reviewed and the decision to proceed with Jargon was really very easy. They had knowledge of the environment of our back office solution; the product interfaced directly to our database; and the pricing allowed us to provide a secondary application to our customers at a reasonable cost.

What were the most important issues that made you select Jargon vs. a competitor and what competitors had you looked at , and the specific reasons you selected Jargon over the competition at the end of the process?

We looked at roughly six other PDA application development packages over the course of a year. We chose Jargon for two primary reasons. The product was filled with features that the other packages could not match and it worked natively with the our database which we use exclusively with our customers.

What were the positive results and benefits of implementing a Jargon solution and how did these things meet and exceed your expectations?

We are very happy with the product and the customer service. They were always receptive to our needs and have put in a number of enhancements that have help us deliver a better product to our end users.

Did you have a business case, if so briefly describe the requirements and decision?

We did not have a business case. We made our decision based on features and “feel”. Part of any success is the working relationship between two companies and we found a company that was willing to work with us to create a very workable solution for our end users.

The ROI (return on your investment)?

We were looking at mobility to separate us from our competition so our ROI on the PDA could not be looked at strictly as a bottom line evaluation. While we make money on each PDA deal, its primary value is giving a customer one more reason to buy our solution versus the competition.

Home |