BMC Helix ITSM replaces Remedy. It is a broad suite of ITSM, tools with strong integrations to other BMC tools and in-built ITAM. The product is used mainly by global brands and is offered in on-premise and SaaS configurations.
N/A
osTicket
Score 7.7 out of 10
N/A
osTicket is an open-source help desk / ticketing platform that can create inquiries online, through email, and through phone calls.
Large complex organisation, with complex technology that needs to manage Technology Services. It is very flexible and able to manage a large complex environment but the knowledge required to set this up correctly (foundation data and configuration) is the key factor for success. It can integrate with many other systems and tools and integrate data from many sources - whether that be AWS cloud, or an on premises bespoke system. I would not recommend for a Small Organisation without the resources to set up and maintain the underlying foundation data and configuration.
For beginning smaller companies that are in need of partially automating their incoming requests this product is easy to set up and will assist in structuring these request[s]. These requests can come in via email/phone or web portal. For companies that are beginning to streamline their support procedures, this tool can be a first step into automating part of these processes. This is also how user[s] should see it. It is merely a tool that can assist in structuring the incoming request flow the rest still has to be fit into business processes.
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.
osTicket is extremely user friendly for end users and support agents. It's very easy for new end users to put in a service request. This aspect of simplicity is important because we don't have to train new users on how to put in service requests.
Feature wise osTicket has everything you need without being overly complicated or cluttered. This is important for us because it allows for faster support times and happier end users.
Lightweight and very reliable, osTicket uses PHP and MySQL. Setup is easy and it can be hosted internally or externally web hosed. Also, since it relies on PHP it gives you flexibility to use Apache, Nginx , Lighttpd , IIS, etc.
Thriving community: the community behind osTicket is feature-wise. Which is very helpful if you have any questions.
Best of all, osTicket is completely free and open source. While they do offer pair tier cloud-hosting and enterprise support. The free version offers all the features of the paid tiers (minus hosing and support).
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
At least Remedy is all contained in a single platform, so the interface is consistent. Also, the most heavily performed functions are generally usable. However, to use some of the more advanced modules can be a bit more cumbersome (such as Change Management and CMDB (Not Including ADDM)). So, overall BMC Remedy ITSM is better than some applications like CA SDM or HP SM, but not quite on par with ServiceNow.
I am familiar with osTicket and this allow me to teach all the staff and support them whenever they have any concern regarding the usability and following processes.
The support is good in overall resolving the issues and even in the deployment phase. We are able to use it in production without any trained in-house engineer as the support team gets the job done. We can say that experts completed the deployment for us, and now it is functional.
The decision to select BMC Remedy was made prior to my employment. We did conduct an RFC process for a new ITSM platform and BMC was considered but not selected. We looked at several platforms and ended up choosing Ivanti Service Desk (previously LANDESK) due to the features, ease of customization and price.
osTicket has proven to be a very useful tool for the team to help support the business. Open-source was the right price point and self-hosting as mentioned was quite important (however I believe that osTicket does have a hosting solution available if needed). Jitbit was a close contender but didn't like how it doesn't separate people submitting tickets from users acting as agents. So all in quite happy with the choice.
When I was in Management discussion calls, and all the team is happy while using BMC Remedy so I don't find any specific negative impact on our organization.
I really enjoy Smart IT as the tool of choice for our incident management team.
Visibility of tickets is key. All support staff users can see tickets in consoles they have access to.
When we had a hosted version of osTicket, we were saving some time by having them work on our setup, but we were spending a lot. Switching to our own osTicket build from their open sourcing not only saved us money upfront but we actually spent LESS time developing because we knew our ideas and didn't have to explain them to another (unrelated) party.
Creating our own ticketing infrastructure for institutional data requests has been a game changer for us. We have been able to interface with our enterprise email client and create a level of customization that meets our existing informational technology culture.
