Reviews (1-25 of 43)
- Logical access requests.
- Network resource request.
- E-mail access request/issues.
- Quotation requests.
- Create/amend distribution list.
- Mailbox size issues.
- General faults and requests.
- User-interface and operations can be defined as per your companies requirement.
- Request/response time is faster and the whole ticket status can be viewed and modified at any point in time.
- End-to-end tracking and follow up makes it easy for the user to prioritize the incident.
- Duplication of incidents/requests.
- Stage by stage updates should be provided to the incident raiser.
- Create report templates in Smart Reporting Console for faster access to data.
- Quickly and easily search for incidents.
- Larger reports take a long time to complete and even longer to export.
- The smart reporting database fails over, but that's on the server and not a problem with the software.
- The ability to customise the tool to suit business needs.
- The range of options available within each ticket to relate others tickets, CI's and knowledge articles.
- Service Level Management console does not allow us to configure all SLA's in our complex environment.
- Reporting and dashboards could have additional options.
- Remedy tool is used for incident management and there are several categories bound with SLAs(Service level agreement) which ensures the closures.
- It is also used for change management across the organization for different environments which make sure all the processes are followed.
- It has a knowledge article section where KBs are generated for known issues which are handy for Business as usual.
- Sometimes it is hard to mention details when several other activities are happening and we need to refresh the page as by that time we lost the data we entered.
- It could use a light version like Angular JS or React JS so the server load gets reduce.
- There is no chat facility provided, if it is possible,I reckon it will better facilitate the incident management.
The system includes a notification system to issue email and SMS alerts based on the level of criticality. We integrated Remedy with other IT monitoring system, where alerts are translated to work orders and assigned to the specific team.
- Integration with monitoring software like SolarWinds. where Remedy can transform notifications to work orders and assign to respective teams.
- Detailed Customization capability to fit the exact needs of the organization.
- Change management calendar, which integrates change orders from all organization departments and facilitates the scheduling process of project managers.
- It can be offered as a cloud-based service, where you don't need to worry about server maintenance or database backup.
- Customization can be lengthy due to the numerous features included in the software.
- New staff members require some sort of hands-on training to get to know all the use capabilities.
- The analytics can be improved to include forecasts and trend analysis.
- Expensive compared to competitors.
I do not recommend it for managing banking and financial institution operations or supply chain and logistics operations.
I have personally used it at 2 different large scale IT departments operating in the higher education sector.
- It helps in reduce ticket volume and faster resolution of tickets with a lot of integration
- It helps create proper hierarchies and helps categorize the tickets properly
- It helps take advantage of all of our existing best practice reports, KPIs, and other artifacts
- I have found it to be a little slower in performance with some minor glitches sometimes
- Configurations can be complicated and to use it to the max, very good knowledge of tool integration is needed
- Support can be better at times (but has been good mostly)
- I like the auto update, the information in the ticket when we respond to the email looks and feels really good. And there are many different sections like, Incident details, Client details, Status details, Assignment details, date details and so on, which you can go to directly instead of searching within the whole page.
- It is easy to implement our business requirements In BMC Remedy.
- On the integration side, the implementation of the REST api has simplified integration to other systems like Salesforce CRM and Apttus CPQ...
- There is no advanced case management in BMC Remedy IT Service Management Suite, like auto closer and escalation process like we have in Salesforce, which needs to improve.
- BMC Remedy IT Service Management Suite is missing some key features that would make life easier, such as being able to more easily copy tickets and search for tickets.
- Technology is slow.
- Applications aligned to ITIL best practices with many of the most common needs covered out of the box.
- Integration between applications (Incident, problem and change management) makes it really easy create the relationships between these entities.
- Using the Action Requests (AR) system the application is highly customizable , assuming an appropriate level of knowledge of developing applications using AR System.
- In Remedy you can do many things but you need to built them first. Many of the Integrations depend on external components and the architecture used to implement the solution.
- The cloud-based solution should be improved to work in the same way as the on-premise solution.
- To accomplish minor changes on the appearance of the forms you need a lot of training.
- Notification of new ticket, group notifications and individual are of great helps to support personnel. Depending on ticket volume notifications need to be tweaked with a simple config change to reduce the amount.
- Ticket visibility/tracking by management/group leads for trending or volume down to groups or individual.
- Ease of modification of any ITSM module on the needs of the company or group or between modules for any functional need.
- Ease of integration with most third party vendors and external databases.
- Ease of creating standalone BMC applications for application need within extremely tight schedules.
- Part of the setup for Asset and CMDB is hard and time-consuming. But, is worth it.
- Most companies do not use the tool correctly as they do not want to go through the steps to set up CMDB, they say it is too hard and takes resources.
- Because of the openness of the system, it allows you to not use the system correctly. Example, many companies I have dealt with only want to use the Asset/CMDB as a placeholder for Assets, sort of like an expensive Excel document. BMC allows this.
- Documenting issues relating to Incident, Work Orders, Changes, Assets is the best.
- Tracking issues and identifying trends based on this tracking is extremely helpful to companies to reduce lost time. Tracking can be across Incidents, Work Orders, Changes, and Assets.
- Capability of access data from other databases and treating that data as local.
- Its adherence to ITIL standards, almost to a fault.
- Ease of customization. If it is desired to veer off the ITIL standards, it is a simple task. This is both a pro and a con.
- Interfacing to third-party applications and the open API is a strong bonus.
- Creating custom standalone applications in the BMC environment is fast and easy. Applications built within BMC be integrated with any BMC ITSM application. Once these applications are built almost anybody can maintain them and make changes to them.
- For service request management, we use the SRM product which gives a common interface for our customers to request services. We are able to easily add the services to the catalog and configure how the created request will be routed to the appropriate group for delivery. This has shown to reduce churn in the request process and reduce cycle time in delivery.
- Incident management has show to be effective at routing cases to the appropriate support group for resolution.
- Change management has proven to provide the mechanism for a change control process for organizing those changes and having affected stakeholders discuss the changes before implementation. This has headed off potential service outages from collisions.
- The quality control on the product from the vendor needs improvement. While upgrading to newer versions (9.1) has provided additional features which have been beneficial, the cycle of product defects uncovered and worked through to resolution has been tiring. Having this product without a good support agreement is not advisable.
- Technology is slow to evolve. The product is just now exposing mobile and REST interfaces, something the market has adopted some time ago.
- User interfaces that do not embrace effective bulk management. Most of the interfaces are driven from a manual perspective. When used in a global company with sites around the world, this becomes burdensome.
- Owner / other relationship values for hardware
- Great integration into the CMDB, Discovery, and other CI tools
- Audit log for hardware and configuration changes
- Poor interface, takes multiple clicks to manage simple things, looks like it was designed in late 90s
- CMDB takes years to learn / master, not a great amount of training available online (poor documentation on vendor site)
Not so easy if used as first point of entry to incidents from end users, I think usability has to be improved.
Is also good for a development team, as is easy to interact with third party software
We have in one of our companies used SMART IT and MYIT out of the box and it works great so far. We will be looking into Smart Reporting in the next few weeks to see what that can offer.
- Integrate well with other systems
- MYIT is a fantastic new interface for users
- I really enjoy SmartIT as the tool of choice for incident management
- Very robust system
- The ITSM suite has some really poor screens compared to the new SmartIT suite
- Upgrades could be a lot easier I think with a wizard type method used
- .Very customizable
- Based on ITIL so correct processes are there OOTB.
- Easy enough to implement with very little effort.
- Support can be a little slow at times.
- Some errors are very vague.
- Still very clunky look and feel but this is slowly being rectified with SmartIT.
- Visibility of tickets is key. All support staff users can see tickets in consoles they have access to.
- Remedy is a tool which empowers the company to streamline processes and implement a framework, such as ITIL in the case of Remedy.
- Some consoles are not built out as much as others. We do our own development and these bugs are more visible to us.
- Remedy integrates very well with many products so you can have incidents coming from many sources directly into Remedy.
- Service requests are something that Remedy does well. Once setup a user just has to answer some pre-determined questions and a work order/inicident/change request will automatically be created and populated based on the answers provided so business end users do not need a lot of training in order to open requests.
- Incident/problem management is a strong point in the Remedy system. Users can open problems directly from the incident ticket with the click of a button and it allows users to track incidents against problems fairly well.
- Service request creation needs some work. Some areas of service request creation like dealing with complex approvals need to be done better in future versions. Also, dealing with formatting of the service request screen needs to be improved.
- I found that reporting is a little lacking. For example, we have people requesting reports based on the audit log and we seem to be unable to do it as we did in a previous version of Remedy
- We also found that it is not easy to correct things once mistakes have been made. For example, if somebody happens to close an incorrect task there is no easy way to just go and open up the closed task.
- Rigid enforcement of processes rules and the ability to audit and report on them.
- Out of the box alignment with ITIL processes.
- Remedy is easy to customize to meet specific business needs.
- It is much better today, but I still think there is room to improve the upgrade and installation--it just seems to take forever.
- I'd like to see BMC provide more real world configuration out of the box. It is a little overwhelming to someone who is new to the system to have to configure it from scratch.
We currently use it just for our IT for change, incident, work order, problem and asset management. However, we are shortly rolling out MyIT for non-IT users to be onboarded for self service applications.
We are able to use it to tie in with our service vendor for changes and incident management via web and email services.
- Enterprise level configuration and power. Very customizable and adapts very well to changes in our infrastructure.
- Flexible ITIL solution. With the ability to customize rules and configurations, we can make it work well with how we currently implement ITIL in our corporation.
- Self service management. By using Atrium Integrator and Atrium Orchestrator, it can help reduce the amount of workload on the IT Service Desk.
- Custom applications can be made but they require a lot of work to maintain.
- You must take care when adding custom roles to the application. When you install things like Virtual Chat, it has pre-defined role IDs, which if you have inadvertently used, it overwrites your own roles. There is no comprehensive list of used role IDs, so it's "buyer beware" when you use them.
- Asset Management
- Integration with other software
- Easy to use interface
- The layout design of the interface could use upgrading
- The ability to generate alerts would also be nice
- The reporting system is now old and needs and easier way to write IFTTT scenarios
- Best aligned ITIL process - we were able to align our own process without much customization. Tight integration with all modules reduces the data redundancy and duplicate work.
- We can perform any kind of actions and intelligent work to be carried out by the tool such as validation, and enforcing the policies to be followed etc.
- You can develop any application on ARS platform which is an advantage.
- Users should be able to customize their home page as per their need.
- There are so many fields not being utilized properly. We need to understand the tool deeply to explore certain capabilities. Most of the valuable features and how to configure those are not available freely.
- When a customer purchases the application, there is a need for an expert team to come and do the implementation. There should be a possibility for customers to use features like pre-stack implementation with customer data so that it will reduce the implementation time line as well as enable certain features when required.
- Upgrade path should be configured as a wizard where all required steps should be followed with the upgrade utility. Current process is too complex.
We use BMC remedy across the organization. It basically coveres our service management portfolio activities:
- Working with customers and suppliers to reduce unnecessary ticket volumes
- Simplifying and standardizing processes, and rolling out best practices globally
- Streamlined organisation structure and operating model
- Deploying a toolset and supporting inventory that puts our organization ahead of the competition, and provides a faster, more automated journey for customers and radically reducing the cost base
- Can be easily implemented for huge organizations
- Scalability and simplification of processes
- Hassle free usage for end users
- Maintenance and operating costs are less
- Increase the flexibility for integration with external products
- Enhancing the UI
- Simplification of process w.r.t modules like Change and Release management
- Proactively managing service - through incident, problem, capacity, configuration and change management
- Continuously monitoring service - preventing failures and rapidly identifying those that do occur
- Reactively managing customer contact - ensuring resolution of incidents and service requests
- KCI - Keeping our customer fully informed at all times
Remedy ITSM Suite helps us with control. It has out-of-the-box functionalities and processes to aligns us with best practices for incidents, problems and change management. It also allows you to create new workflows, and new applications to match your organization’s procedures and needs.
We use BMC Remedy IT Service Management Suite in two major ways:
- Support our final customer with Remedy
- Internal requests between departments: 1.Our customers enter an online request management page where they select the request type, and the request goes to the defined support group where they review and answer our customer needs. They document this in the same Remedy system to notify the customer. 2. When someone needs helps with computers and systems they open a request.
- ITIL alligned process
- Web based
- Easy to install, easy to confiugre
- High computer resources needed, specially RAM
- Not easy to customize. A simple configuration method to enable a few of new fields would be great.
- There are always bugs, should test a little lot more.
- Easily customizable to meet business needs
- Rock solid reliability and performance
- Streamlines processes and requirements to assure auditing compliance
- Standard ITIL compliant processes out of the box
- Difficult to integrate via web services
- Reporting is weak without the use of third party tools
- Large infrastructure which may be difficult for smaller organizations to maintain
BMC Helix ITSM (Remedy) Scorecard Summary
Feature Scorecard Summary
What is BMC Helix ITSM (Remedy)?
BMC Helix ITSM (Remedy) Integrations
BMC Helix ITSM (Remedy) Competitors
BMC Helix ITSM (Remedy) Technical Details