Item: JAMS
Rating: 2
Author: Jeremy Myers

Use Cases and Deployment Scope

It schedules all of our custom jobs which take data in or out of our system. It also runs custom jobs to manipulate data in our system.

Pros and Cons

runs jobs

API documentation is poor
customer service is poor
native UI/UX

Return on Investment

contracting and licensing is a yearly pain point. the amount we pay is exorbitant

we use it for hundreds of jobs a day and it has scaled fairly well for that. But when it comes to making changes to values/configurations across our deployed jobs, in my experience it has been difficult.

Support Rating

In my opinion, it's pretty painful. For a simple configuration change, it took multiple rounds of back and forth with customer service. Almost like trial and error over the course of weeks if not months.

Alternatives Considered

As we grew dissatisfied and limited by Windows Task Scheduler, we selected JAMS because a senior Ops employee at the company had used it previously. We didn't do due diligence and run an RFP process against other providers at the time.

Key Insights

Do you think JAMS delivers good value for the price?

Are you happy with JAMS's feature set?

Yes

Did JAMS live up to sales and marketing promises?

Yes

Did implementation of JAMS go as expected?

Would you buy JAMS again?

Other Software Used

Jira Software, Slack

Likelihood to Recommend

it does the job and we tax it heavily. with our schedules and concurrent runs, including repeats multiple times a day. But we have had serious difficulty with documentation and also in the area of contracting where we have servers coming in and out dynamically.

managing global technology solutions for our clients.

Overall Satisfaction with JAMS