Any large business or organisation that wants to manage their workload effectively and with the least amount of room for error might choose the ActiveBatch Automation tool. Being a consultant I feel that It aids in task automation and has the flexibility to change in response to varying company requirements. It helps to save huge time by doing all the repetitive tasks on daily basis. During the patching activity the schedulers can be stopped. It also help by alerting us if any system/job is down so that SLA can be saved. Overall ActiveBatch Automation stands as a dependable cornerstone for ensuring the seamless operation of our tasks.
BMC Footprints is so well suited to keep the documentation easy to read and find, as same as typification. You can find specific documentation for an audit so fast and export a report using the specific criteria that you need to comply with your boss or audit needs. As I told before, BMC footprints need to be more friendly to the end users because they get lost many times trying to track some ticket or typing documentation.
Businesses can use ActiveBatch to plan tasks based on parameters like frequency, dependencies, and the time of day. By automating typical actions like backups and data transfers, businesses can make sure that crucial operations go off without a hitch.
Multiple systems and apps can be used in complicated workflows that ActiveBatch can automate. For instance, it can automate a workflow for processing orders from beginning to end, from the customer order through inventory control and delivery through the processing of invoices and payments.
Files can be sent between many platforms and systems safely with ActiveBatch. Transfers to cloud-based storage systems like Amazon S3 and Microsoft Azure are also included in this. SFTP and FTP transfers are also included.
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.
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 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 can easily add new plans/jobs in our batch schedules. Also, coordination with reporting and QA jobs is simple to do. Building schedules, restarting jobs, triggering dependencies is easy to understand. The system is very stable and allows us to easily see overall processing times.
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.
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.
The workload automation solution is based on the specific needs of an organization, as well as the features, capabilities, and costs of various solutions. A thorough evaluation process and consideration of these factors can help ensure the selection of a solution that aligns with overall business objectives and meets the specific needs of the organization.
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 process and expense.
I have not run numbers to determine hard impact, but a quick estimate is that at least one job is running for a average of about 6 hours per day - that 6 hours, if done by hand, would equate to about 30 - 40 hours per day (and in some cases, could not be duplicated manually, as the job repeats faster than a person could accomplish one cycle.)
