BMC Remedy: A first look at an ITIL Implementation from an IT professional who uses it constantly
August 20, 2018

BMC Remedy: A first look at an ITIL Implementation from an IT professional who uses it constantly

Anonymous | TrustRadius Reviewer
Score 5 out of 10
Vetted Review
Verified User
Review Source

Overall Satisfaction with BMC Remedy Asset Management

Currently, Remedy is used by the entire IT department to capture the entire ITIL Landscape. What this means in layman terms is that Remedy is responsible for CRUD against everything from Asset Management, to Incident and Change Management.

I say that Remedy is used by the IT department, but other departments also use Remedy- Client Services (the spear-tip of the IT department), the help desk, and other internal departments (power, scheduling, etc) also use remedy to manage their workflow, thought IT is Lion's share of the load.
  • Remedy is great for housing much of the ITIL process in one System: if you want a complete package with every bell and every whistle, Remedy is for you
  • Remedy breaks down the functions of ITIL into "consoles": separate areas of the System, that allow one to focus on Changes, Incidents, Assets, etc
  • The interface is VERY compatible with legacy web browser tech: The last surviving member of the browser wars is still the favorite for remedy users: IE 11
  • The interface (ironically). My company has made an attempt to replace the "classic" Remedy interface with some more functional, modern, but Remedy set to a particular look and feel (and consequently, functionality)
  • The API is hidden from the user: There exists an API for Remedy, that would make my job TONS easier, as I like to perform actions on Remedy in bulk (and therefore - programmatically). Exposing a user API is very much mainstream these days, so Remedy relying on its interface to perform ITIL is very limiting
  • By extension- the result of Remedy's interface is that it becomes very "click-happy": little buttons, and links stuffed into every corner of the screen, with options API logically together. API is old, but it still feels very rushed.
  • The primary tool for most of my ITIL operations is: searching. API of searching goes into finding assets, checking in equipment, finding users, tickets, etc. What Remedy could very much benefit from a "Google" -like interface
  • Positive: an introduction to ITIL and viewing Asset, User Management from the perspective of ITIL, and how BMC has implemented those processes
  • Negative: The development team needs to communicate better with the sales and support side, and they need offer an open API
  • Negative: Currently the Asset Management side has little security and validation of Asset input: anyone can make API (mostly), at any item, which is a problem that I am apart of solving.
  • The UX needs updating, badly. Its quality is poor: it functions, but it is cumbersome, click-heavy and requires several hours to understand how to function with it. Also, it needs to ditch IE11 support, altogether.
I did not select Remedy myself, so I am coming in from someone who is apart of the story, from somewhere in the midway. That being said: Remedy has begun a journey of understanding the problems associated with the implementation of ITIL, and indeed ITIL itself (it is a top-down process for management of an IT department). there are many alternatives out there. One, in particular, I am keen to investigate: Redmine. But in doing so, It will be evaluated via my experience with Remedy.
Remedy is a solid implementation for an ITIL environment: it processes change tickets, incident tickets very nicely. However, there are a lot of features it lacks: Asset Management, development, batch (bulk/programmatic) actions and UX are severely lacking.

The current context I interface with Remedy is in the helpdesk scenario: an End User submits a ticket, that ticket is routed to the appropriate department, I solve the problem, then close that ticket, all from Remedy. However, processes such as Asset Management are wholly unsuitable to the task, in my opinion, and even my Company uses SAP for the bulk of the purchasing management, thus making it necessary to use two tools, instead of having a central system for purchasing and inventory.