The initial setup involved transitioning from our previous practice of following the HL methodology to adopting ITSM methodologies, specifically those associated with InfoSight technologies. Initially, this shift required some adjustment, as our previous approach did not adhere to such processes. It took some time to understand the workings of the new processes, but once acclimated, I recognized the significance of these methodologies in our current working model.

The initial setup of BMC Helix ITSM in our situation was complex because we were coming from a version that was over ten years old.

The initial setup of BMC Helix ITSM is straightforward.

The setup is straightforward so is rated an eight out of ten. 

I rate the product's initial setup phase an eight on a scale of one to ten, where one is a difficult setup phase, and ten is an easy setup phase.

The product's initial setup phase was easy.

The solution is deployed on the public cloud services offered by Amazon.

The solution can be deployed in a few hours to a week.

While I wasn't around when it was installed, my understanding is that it is pretty straightforward. 

The initial setup of BMC Helix ITSM is complex because it has different integrations with other tools. Additionally, it needs to be integrated with the active directory and have different databases. The environment will dictate how difficult the process is.

The ease of installation largely depends on your specific requirements when it comes to the initial installation of BMC Helix ITSM. If you're opting for a containerized deployment, it's not necessarily straightforward; I'd rate it around a six out of ten on a scale of difficulty. However, if you're leveraging cloud-based deployment, the tool manages everything, including instances and scalability. 

It's very difficult to set up the product. It's one of the most difficult solutions in the market to implement. It's time-consuming. It will take more than two months compared to something like ServiceNow, which is faster and easier. 

The number of people you need for deployment and maintenance is minimal, maybe four or five people. We can separate that into one project management, one architect, and three developers or analysts to implement the solution.

Implementation is easy and simple most of the time. The knowledge base is pretty good. The community pages are very good.

The amount of time it takes to deploy depends on the use cases. Typically, we take around two to three months for implementation, which covers at least six to seven processes of implementation, any incident problem, change, or configuration.

The initial setup of BMC Helix ITSM is straightforward.

I rate the initial setup of BMC Helix ITSM a nine out of ten.

Installing and upgrading are relatively straightforward even if the customer is updating from a really low version, like 4.1 or 7.6. So a customer should be able to upgrade to 20.02 or 20.08, but would need to do it step by step. For example, you would have to upgrade to either 9.1 or 18.05 and then from 18.05 to 20.02. That entire process will take around six months to one year for the customer to come up to the scale or start utilizing the new version. So if I get a database and it's the proper version, BMC should be able to handle it. When I do a fresh installation, it should be competent enough to identify the entire workflows or whatever has been designed in the database and start the process. It should be a quick start rather than taking a year to come up with all the integrations and everything.

Initial setup is straightforward, and if you follow best practices, then future enhancements will be smoother.

The initial setup is not simple. We require a skilled administrator to complete the deployment. Depending on the customer's requirements the solution can be deployed on-premises or cloud.

For the product itself the initial setup was relatively straightforward. The main complexity arose mainly in the project management aspect of the migration. This was due to the fact the coordination had to be done with both internal and external resources.

The initial setup for all involved was “discovery” as no one had the experience of the tool.

The initial setup of BMC Helix ITSM requires a technical expert. An expert is required for the configuration and management of the different servers.

The initial setup is complex. If you know what you are doing and what you want then it's straightforward. Most clients don't know what they want and it becomes complex.

I have worked with three or four consultants where you have small teams, and I have worked on larger teams where there is a huge undertaking to implement it.

Initial setup was like any other similar implementation. There are certain things that you have to do, tables that you have to build, configurations that you have to work with. There are a few modifications that you have to make so that it fits into your environment. We tried to stay as close as we could to the out-of-the-box solution. So it was fairly straightforward.

There are portions of BMC Remedy that are proprietary. One of those was attachments. If I attached an image, if I attached a project plan, if I attached a screen print, getting those out was very difficult when we moved servers to ServiceNow. So if you're not planning on moving, it's not an issue. It's when you move it the issue.

The initial installation of BMC Helix ITSM is fine.

The initial setup is pretty complex. 

It was a complex one, because our company was bought by another one and both companies had different versions of remedy installed which needed to be unified. The complexity was from the level of customizations each instance of Remedy needed.

Setting up Helix is complex, and it takes about a day to deploy. 

I haven't really done the installation, so I do not know how complex it is.

I was not at this client site when the implementation was done. But from experience, I would suggest that anyone embarking in this adventure does get at least the basic training

The initial setup was simple. It took around six months to one year.

For us, the initial setup was complex because we needed a lot of customization done.

As straightforward as it can get for someone who knows the system.

BMC Remedy is set up for a real production environment and can be quite complex depending on what you have. For normal DEV/TEST environments, it is fairly straightforward, but it certainly is nothing like MS Office or something, where you can blindly click next-next and then finish and forget about the installation! It is a complex enterprise application and needs proper administration on an ongoing basis.

The initial setup required an engineer for configuration, to load data on the system. The datasheet form isn't user friendly, a client wouldn't be able to fill it in, a tech savvy person is required.

It's straightforward for someone who knows what he or she is doing.

The set-up is pretty easy.

Initial, out-the-box setup was easy with no problems. The gathering of business data to import into the system was more complex.

For the needs that my company have the structure is complex, and so the setup is a little complex to, but if you only need one server, the setup is straightforward.

Initial setup is quite straightforward. You follow all the steps recommended and voila, you system is ready for use.

It was complex to setup.

I can't say much about the implementation because my team handles that, but I think it isn't complex.

It was quite complex from memory. It was over three years ago, but it was quite complex.

At first, the setup was complex, but we have evolved since then.

I don't know. I was not involved that time, it was long time ago :)

The deployment of BMC Helix ITSM is difficult. If you deploy it in a single-use enterprise it's probably fairly simple. A lot of the deployments of the solution we are doing are at a global level where there is a lot of consolidation. BMC Helix ITSM requires individuals that are doing the process to have a deep understanding of the solution.

A lot of people are moving from legacy on-premise systems to SaaS cloud versions. The most difficult element of doing this is data migration. This process could improve. There are good processes in place for migration, but it's having the level of understanding about what data do you need to migrate that can be difficult.

The initial setup is easy. Within a few hours, you are up and running.

It's straightforward to install and configure it.

You need to follow the installation steps during deployment of application.

It was complex. The older versions were complex to customize and create some workflows. It took a lot of time to deploy. I don't know about the latest versions.

The initial setup was straightforward.

The initial set-up was straightforward.

The initial setup is partially complex, but reading the install manual ahead of time is recommended to offset the complexity.

The implementation. was easy.

It takes a long-time to plan and deploy the on-premise solution.

The initial setup wasn’t straightforward.

Straightforward. Basic read, follow and flow.

Simple but the installation file is too big.