BMC FootPrints is an IT service management (ITSM) solution featuring workload automation.
N/A
JAMS
Score 8.3 out of 10
N/A
JAMS is a centralized workload automation and job scheduling solution that runs, monitors, and manages jobs and workflows. Reliably orchestrate the critical IT processes that run your business from a single pane of glass.
Both are developed from the same vendor but Footprints is so complete for all the configurations that we need (we are a medium business company). BMC Remedy has a little more friendly interface but it doesn't meet our needs. We prefer a product that fits better our needs to a …
I did not chose the program it was chosen and implemented by our IT team. Based on verified reviews from real users in the IT Service Management Tools market.
We haven't used any others besides this one, but we did evaluate BMC Remedyforce, SysAid, and ServiceNow. Remedyforce and ServiceNow seem much more advanced and difficult to use, though I'm sure they are probably much more feature-rich once you get used to them, but the …
I was not involved in the selection process but in my opinion either SQL or Access databases would have worked just as well without the same amount of cost. These two systems would have been much easier to manage and would have tracked the same information in a less convoluted …
We have evaluated multiple including HEAT and ServiceNow. Their older versions gave us more to play with and able to use more, but since going to version 11, it has been very unfavorable. We have had to adapt and work with what was provided. We have understood that ServiceNow …
BMC offers vast functionality, that also can be overwhelming. If proper training and execution of its bolts and parts are completed properly, this tool can provide the efficiency and tracking that a Enterprise Business requires.
Verified User
Anonymous
Chose BMC FootPrints
If you are looking for something for a large corporation, BMC Footprints may be the fit for any department that needs to communicate/resolve issues across other departments. It is great for a large amount of users, but because of its focus on issue logging, it is limited when …
Our developers found it easier to get going with JAMS and there seemed to be better calendar and scheduling options available in JAMS. JAMS also supported legacy OS versions that were unsupported and did not work in Automic. This was a vital requirement in selecting a solution …
Tidal is a very good scheduler but very expensive and customers can't budget for this. REvScheduler is a lot cheaper but the interface isn't very aesthetics and functionality is lacking compared to JAMS. Out of all of them I'd recommend JAMS.
In my opinion, while JAMS is useful for point and click like developers, Astro is more useful for software developers, whole like to see "scheduling as code". in the long run, I think Astro might overtake JAMS in terms of usage and use cases that it satisfies across the tech …
JAMS was much more cost-effective and easier to use. JAMS allowed us to centralize our job scheduling more fully. Converting from our previous, very limited scheduler to JAMS would be far more accessible than Automox.
N/A. I don't have any experience with different Job Management Software. Since JAMS is capable of doing most of our daily operations, we didn't look for other software. I can say that JAMS perfectly fits with us and with our clients. I've only heard about Direct M, which, based …
We switched from Automic Automation. JAMS is so much easier to implement, patch, upgrade, and push agents. It takes more steps to conduct activities in JAMS than in UC4.
I had evaluated 2 others in 2010/2011, but I do not remember their names. This was the easier one to work with and had a better looking, sometimes more professional looking UI than what I was evaluating. JAMS was more scaleable and had the ability to make custom interfaces to …
Mainly i've been using SQL Agent jobs in my career. JAMS takes scheduling a bit further. For instance, i would rather not have SQL Server run a job that is performing an SFTP step. Waste of resources and a job like that is well suited for JAMS
JAMS is easier to use, provides more features and was easier to manage form a central location. simple features in JAMS were missing from VisualCron such as a projected daily schedule. The install setup with a client and agents was better suited for us too
It's just different. The views are different, how you set it up is different. It's not good or bad, just different. I think JAMS offers more options when it comes to how jobs run. Like you can use sequence, or setup a job to run based on a number of different dependencies.
While Redwood offers a modern UI, JAMS is much easier to use. For basic operations, it's simple to create a job and schedule it. For those with more experience, JAMS offers much more robust features to take advantage of.
We use Kace also because it has an agent on every machine, so tasks that push out installations tend to go there. I'm not sure if Jams can do that, but if it does it's not clear that it does.
While visualcron provided more guardrails and user centric GUI, JAMS had a better resiliency functions with their clustering and service polling and failovers. We tested this and were able to maintain a large library of jobs and data the seamlessly switches between data …
Tracing any maintenance requests, so you don't forget any requests, it also sends an email to the requestor once the project is completed. Keeping status of projects in progress and the current state they are in. Allowing anyone with access to know the current state of any project. Generating a useful report is a bit more difficult then I would like.
It's currently one of the best of the lower entry cost options out there, as it currently is a set license cost, not based on the number of jobs executed. In the hands of a good script writer and users with workflow experience, it's a powerful tool to accomplish just about any process that you have a need to complete.
Documentation. We try to reduce the amount of paperwork needed for staff to do their job, so by automating certain tasks, we are able to speed up the resolution process for trouble tickets.
Reporting. We'll use the reporting tool to get the number of tickets opened, response times and can go into granular reports.
Surveys. When tickets are closed, we automatically send out surveys to end users to get valuable feedback on how we did and what we can improve.
The Activity Monitor clearly shows the Running Jobs, and Jobs that are to run soon. Successful Jobs can be viewed as well. The Refresh of this monitor is completely customizable to your liking.
Job Definitions are very well organized by use of Folders. This simplifies the structure of how to best Implement JAMS Jobs, including the ability to provide specific properties on each folder - whereby Jobs will inherit these properties.
Connectivity to servers is well thought out by having Shortcuts to include Credentials and Connection Store for server information.
JAMS Jobs can be controlled via System Resources. This is very powerful and is a very useful configuration found in JAMS.
Purpose based configuration- It would be beneficial to see a more purposed based, out of the box, configuration option. For example, if you need PCI compliance, more intuitive reporting would make managing compliance much easier.
Initial design and implementation- Don't think that your experience as an IT professional will allow you to stand this system up on your own. To properly configure Footprints and set yourself up for success down the road, get Professional Services with this one.
Somewhat behind the times- Service Core is making a huge leap forward with the latest version, 12, but Asset Core is far behind. There are quite a few quirks to how the application works and how it is used.
It would be very helpful if the application had the ability to display help text based on where the cursor is hovering on the screen. There are many times when a brief explanation of an on-screen prompt would be very handy. For example, when you attempt to Cancel a job from the Monitor, you are presented with the checkbox that says "Reprocess completion?" It would be very nice if you could hover over the prompt and see a pop-up help screen that explains what happens if you check this checkbox. The same applies to all the checkbox options presented when you attempt to "Release" a job from the Monitor.
It has been the business decision to go with them and that is what we will do. Going back, this would have not been the choice, but nothing can be done about it now. We are stuck with this application for years to come. Wish there were other possibilities that could be done.
We have built JAMS into our scheduling process. Its a great scheduling tool. I'm not 100% on the execution side as we have had issues with what i'll refer to as compatibility issues with ssis variables, but it executes sql agent jobs perfectly, so when i have an issue i create a sql agent job and have JAMS execute the sql agent job on the schedule from JAMS
It's so simple to use and customize however you want. You can create new workspaces and workflows with ease, set up new users, incoming email rules, customize the layout of the forms, and even change the colors and logos. It's just very easily customizable overall. It's also really straightforward to figure out how to use, you really almost don't have to show somebody how to use it. If you just sit them down in front of it and let them look it over, they could figure it out themselves easily.
9/10 as there are so many features I have not tried as of yet. It is easy to get started but as jobs become more complex you tend to employ more and more features - Some of which can be complicated at first. This all comes down to experience using the system. Out first setup and current setup are vastly different as we learn how to use the full power.
We didnt really encounter any downtime, no issues encountered during 2 years of use of JAMs also our client barely raise an issue with JAMS, mostly the issues is on the batch jobs that jams executes. So I would gave it a perfect 10, very reliable hardly encounters any error and bug
JAMS performance is very great, there are no issues raised with the performance, it just like nothing happens on the job after integration it gives you this monitoring capability, no reports and bugs raised on the performance, we didnt do integration with other software only database and with use of JAMS agent to different servers
I've had no issues with the support for FootPrints. We haven't really had to use them all that much over the years, but when needed they have always been prompt and knowledgeable at dealing with any issue. I've worked with a lot of different support teams over the years, and they have been one of my favorites to work with.
I am giving support an 11, the turn around time is insane. At times I get a reply in minutes. The directions to fix are precise and easy to follow. They are personable and friendly and never treat me less than they would a fortune 500 company (which I am not one of).
People that were involved in the POC found the training a lot easier to follow. I think most people would have preferred to just get the training material and run through themselves.
I Was not part of the original Implementation, and the persons did that are no longer with the Organization. But I was part of the recent Upgrade process a year ago and I am the JAMS admin and was very pleased
Both are developed from the same vendor but Footprints is so complete for all the configurations that we need (we are a medium business company). BMC Remedy has a little more friendly interface but it doesn't meet our needs. We prefer a product that fits better our needs to a product that could have other features that we are not going to use.
We chose JAMS because it was the best solution for our business needs, a major factor being the licensing model and the simplicity of the app. We needed to migrate things fast too and this was simply plug and play without too much headache
By installing Agents on servers throughout the organizations, you can run a DB Script on a DB Server, move files around the network and kick off jobs on servers in different parts of the organization: JAMS Runs on its own server, isolated from others. Through an agent on a Processing Server (work Server) files can be picked up, processed and moved to a destination server to be processed into another application on another server. You don't need an agent if you are just moving files around, you need an agent if you want to run a process or API Call on the destination server.
SOX auditing has been part automated saving days of work for the people involved.
The ability for jobs to react to different failure values has enabled us to do away with overnight human monitoring ultimately contributing to saving us in the 6 figures.