The initial setup was very straightforward. It was very easy.

We had to install a couple of outlets coming from the UPS systems. That was very easy. And then the Eaton technicians came in and it only took them a day to install the routers and ethernet switches for our three units. So it took no time at all. It was very fast.

It was a absolute major pain to set up in the organization, but that was not PredictPulse, that was our IT department.

If you take a new system and go online with it, it is absolutely horrible because PredictPulse has to send an email out, and it is incredibly difficult to get our IT security to allow the solution to send an email out. We hook it up with Eaton, then it's ready to go. I can immediately ping and pull it up with the web browser and look at the system, but then IT blocks it for the next three months while we try to convince them to let it out.

The setup is really easy. Eaton's technical department was really helpful in teaching us how to set things up and to register each unit.

The setup of PredictPulse took about a week because we had internal problems with our network. As a government agency we're required by law to isolate and set up firewalls and have a lot of security. All of our networks are highly secured from the outside. Each new network has to be separated from the others. That makes it very difficult because there is so much security in the design of the system, because the government doesn't want cross-contamination, or if one system goes down that it doesn't bring down the enterprise system. PredictPulse needs internet access to talk to the computer and all that has to be isolated in its own network and firewall. I have a big challenge, internally, setting it up and it's in process at this time. It's very difficult to get permission to get outside access to the world. It's not PredictPulse's problem, it's just the way we're required by government to operate.

The initial setup is mostly straightforward once they get you set up. It's a little complex to get additional people setup. I have to go through Eaton to get it setup. Letting me manage users and access would be helpful.

The deployment was super fast. The long part was us getting our network card installed and getting it on the network. 

Setting up PredictPulse is pretty straightforward. We assign an IP to the UPS, the engineer sets it all up, we log in, and it's live. Then we set up the remote notifications to the different responsible teams, and I activate PredictPulse on the web interface. That's about it on our side.

The initial setup was fairly straightforward, once we got the white paper. I provided that to our firewall engineer. As soon as they had that part, it helped immensely in getting the reports sent out. At that point we fixed how the reports were set up because I did not set that up correctly. 

It took about four days, but it wasn't four days of trying real hard. It was something on my plate that needed to get done and I worked on it for about two hours a day over those four days. And that included getting people on my side to get it allowed through.

In addition to me, the firewall person and a networking person were involved to make sure that we had the right VLAN set up for it. At this point, it only requires me for maintenance. There's nobody else involved in that. The radiology manager is the only other person who uses it.

When it was initially set up, we built a new building. This solution was spec'd to be put in the building when it was built. Before we took significant completion, they trained us, but it was installed before the building was active.

The initial setup was straightforward.

The initial setup was a complex project, but the install was pretty straightforward. It was handled well. An electrician was used as part of the install and there were people from Eaton here. It was a positive experience. They were fine.

The deployment took a few days. Once they had the equipment in there it was a few days until they had it up and running.

We were converting how the power is distributed to all parts of our building. We had to take down the old UPS system and bring up the new one to supply areas of our property, in sections. We would do it overnight to lessen the impact on our guests and team members.

The initial setup was straightforward. We set up an email server and PredictPulse sends emails out every few minutes with the status of UPS. The biggest thing is that you have to have an email server that can handle the number of daily emails that it's generating. We have several UPS units so there are a lot of emails, but the setup wasn't a problem. It's not complex. You just need to understand that the system will generate a lot of emails on a daily basis.

If you're not a technical guy, you're not going to understand that. You have to be an IT person to understand how to set up PredictPulse. So different customers might give a different answer than I have.

For us, the setup of PredictPulse took a few minutes. It was pretty simple. You just set up the firmware and the UPS system has an email address and then you just turn it on.