Genovation MiniTerm 904 - keypad - dark gray
$247.99
Mfg # 904-RJ
CDW # 1280447
| UNSPSC 43211706
Know your gear
The Genovation MiniTerm 904 is a fully programmable LCD mini-terminal. The MiniTerm 904 supports simple and complex re-programmable key macros and system configurations. Includes detachable serial (RS232) and USB cables for easy setup and different applications.
Add to Compare
Enhance your purchase
Genovation MiniTerm 904 - keypad - dark gray is rated
4.20 out of
5 by
5.
Rated 5 out of
5 by
Maria Irimias from
Advance automation with user-friendly no-code platform templates
What is our primary use case?
Our primary use case for Microsoft Power Automate is in the direction of citizen developers, mainly small automations built by business people themselves. We also use it for automations in finance departments with Power Apps.
How has it helped my organization?
Hyperautomation strategies are built around UiPath and Microsoft Power Platform, improving service delivery. It is easy to learn for business users, facilitating quick setup of automations.
What is most valuable?
Microsoft Power Automate is a no-code platform which is very easy to learn, allowing businesses to build their own small automations. Templated flows enhance automation capabilities, and document understanding is also highly valuable. The integration with AI in process automation is anticipated.
What needs improvement?
The licensing model could be improved to make it easier to understand and follow, as it is difficult to determine if the embedded license provides all functionalities or if additional licenses are needed.
For how long have I used the solution?
I have been working with Microsoft Power Automate since 2020, about four years.
What do I think about the stability of the solution?
Once you know how to build automations and bypass limitations, they are stable and work correctly.
What do I think about the scalability of the solution?
Microsoft Power Automate is best suited for citizen developers. Managing it at the enterprise level with more complex business processes can be more challenging.
How are customer service and support?
I am satisfied with Microsoft's customer support as we are a partner and receive fast responses.
How would you rate customer service and support?
Positive
How was the initial setup?
The setup requires time for configuration and may require an administrator. It is time-consuming.
What was our ROI?
Our customers have seen return on investment with Microsoft Power Automate. However, it's important to consider licensing limitations to avoid high costs.
What's my experience with pricing, setup cost, and licensing?
Costs depend on the automation complexity. Licensing can be based on per user or per flow, with the potential for high costs if not carefully managed. The cost for licensing can increase due to licensing fees.
Which other solutions did I evaluate?
When evaluating, it depends on needs. UiPath is more mature for enterprise-level automation but more expensive, while Microsoft Power Automate is a good start for small automations and for those already using Microsoft products.
What other advice do I have?
I recommend trying Microsoft Power Automate. It is a low-code platform and is easy to learn, allowing quick start to automation.
I'd rate the solution eight out of ten.
Which deployment model are you using for this solution?
Hybrid Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Other
Disclaimer: My company has a business relationship with this vendor other than being a customer:
Date published: 2024-11-08T00:00:00-05:00
Rated 5 out of
5 by
Ray Ozone from
Fairest licensing, high ROI, excellent support, and easy deployment
What is our primary use case?
We were a partner with Softomotive before they were acquired by Microsoft, and now, we are a partner with Microsoft. We have quite a bit of expertise in WinAutomation. Microsoft has depreciated it, and it's now a part of Power Automate, but we still help out clients with it even though it's deprecated.
Its use cases were the same as any other RPA product. It was basically used for automating any repetitive process, which could be anything from filings to transferring data between software to triggering different processes via email or databases and so on and so forth.
What is most valuable?
Triggering and scheduling were pretty good. There was no real commitment with WinAutomation because the licensing was very fair and you could trigger bots very easily.
What needs improvement?
They've already improved it, but I guess a testing suite would be nice to be able to test your automations in real time.
What do I think about the stability of the solution?
It's pretty stable.
What do I think about the scalability of the solution?
They had a second piece of software called ProcessRobot, which was kind of WinAutomation's big brother. That was a scalable solution, but all that is depreciated now.
How are customer service and support?
At the time, the tech support was excellent.
How was the initial setup?
Deployment was very easy. You just installed the software, and then you installed a couple of plug-ins and browsers, and you were ready to go.
The number of people required for maintenance depends on the size of the deployment. You can have one bot, you can have ten bots, or you can have a thousand bots.
What was our ROI?
It provided an extremely high return on investment. When you automate processes, you're oftentimes being able to scale very easily, and you have a very high ROI.
What's my experience with pricing, setup cost, and licensing?
It had by far the fairest licensing on the market. For the money, you got a very good value.
What other advice do I have?
If you're planning on implementing the product, start off with simple automations and take your time to learn, understand best practices, and understand error handling. A lot of issues come out of improper error handling and no best practices. Start simple and don't be afraid to ask questions.
There are a lot of different products out there that are competitors to this. Microsoft now has Power Automate, which is basically WinAutomation with a lot more web connectivity and a much larger ecosystem. It's extremely powerful, and you have lots of UIs, front ends, chatbots, AI, and so on and so forth. I highly recommend it, and then you have UiPath, which is geared toward enterprises. The licensing structure is much more expensive, and they have some powerful tools over there. You have Automation Anywhere, which seemed to have been a direct competitor. It was more expensive, but it was also very powerful. You have Blue Prism. You have Robocorp. There are a lot of them.
Back in the day, I would rate it a 9 out of 10. For the money, it was an excellent deal. It was very low cost compared to the competitors, and it performed 75% of what the competitors did. If your use case could fit within its capabilities, it was an excellent deal.
Disclaimer: My company has a business relationship with this vendor other than being a customer:Partner
Date published: 2023-02-05T00:00:00-05:00
Rated 5 out of
5 by
Shaik Abdul Waseem from
Affordable and capable of interacting with multiple systems, but should support orchestration and cognitive AI
What is our primary use case?
I was in an insurance company prior to joining this new company, and I developed complex robots for claims processing and policy insurance. I also worked on several other processes such as interacting with APIs and downloading SharePoint reports. It was difficult to download the SharePoint report, but I did an integration in SharePoint to download the data and upload it into the local database system. So, I have created complex robots with WinAutomation.
What is most valuable?
WinAutomation is very handy to use, and it has the power to interact with multiple systems, such as SAP, Oracle, or .NET systems. It's very useful for API integration. We can also interact with the data by using wildcards and other patterns. So, there are plenty of things that are good.
What needs improvement?
There should be a comprehensive or enterprise level of application to provide the cognitive AI, and there should be orchestration so that I can control all the robots on one station. The other tools are currently providing these features. So, hyper-automation integration should be done, and it should have cognitive AI.
One drawback of WinAutomation is that it doesn't work properly on the Internet Explorer or Edge browser. On the older version of Internet Explorer or Edge, it sometimes doesn't give proper selectors while selecting the fields. I had a lot of difficulty in that area, and I want them to improve that in WinAutomation.
They should have a comprehensive platform to help the community. They should have blogs. They had a community before, but they discontinued that. Microsoft has developed a community for any support required for its product. WinAutomation should also have that.
For how long have I used the solution?
I've been using this solution since 2015, so it has been about eight years.
What do I think about the stability of the solution?
It's stable. It's very good. We had been running this product for seven years, and we had developed around 300 and more processes within one organization. So, there was stability.
How are customer service and support?
Initially, in 2016 or 2017, when WinAutomation was not yet acquired by Microsoft, we were having some technical issues for which I sought support from their technical team. Later on, we didn't require any support from them. We used to handle any technical problems with it from our side. I'd rate their support an eight out of ten. They were good.
How would you rate customer service and support?
Positive
How was the initial setup?
It was very good. It has been very handy, and it didn't take much time for the setup. It was very easy to set up various things.
The deployment duration completely depends on the process. It depends on how long a process is. When we were developing robots in production, it didn't take much time for us to deploy them. It was very easy for us.
We had around four people at the time, and the number kept increasing. We were providing comprehensive services, so we were managing the development and engineering jobs all together at once.
What's my experience with pricing, setup cost, and licensing?
Comparatively, WinAutomation is cheaper than the other automation tools. When we purchased the license, it was around $50 or $60 per user most probably per month.
What other advice do I have?
I'd definitely recommend using WinAutomation. It's very affordable, and it's durable. It gives the long-term usage scope in the organization.
Overall, I'd rate WinAutomation a seven out of ten. They have to work hard on this one. Right now, there is no competition for WinAutomation in the market. They should work on the product more.
Which deployment model are you using for this solution?
On-premises
Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2023-02-08T00:00:00-05:00
Rated 5 out of
5 by
Shiv Chandra from
Simple to implement, but on the governance side, there isn't enough documentation
What is most valuable?
My client used it for very basic Excel file manipulation. The data was sent through the API to an ERP system. For that purpose, it worked fine, but I don't think it's the right type of solution for those things. It comes as a part of the Microsoft suite, which makes it an easy sell.
What needs improvement?
On the governance side, there isn't enough documentation on how to govern Power Automate. People just build bespoke automation, which then becomes a problem point for different companies. You might have heard lots of horror stories about Power Automate where people didn't develop according to the standards, and then it came back and gave them grief. There should be more documentation on governance and how to control it at the enterprise level.
For how long have I used the solution?
I've been using it for a couple of years. I last worked with it about six months ago.
What do I think about the stability of the solution?
I'd rate it an eight out of ten in terms of stability.
What do I think about the scalability of the solution?
I'd rate it a six out of ten in terms of scalability. I find other tools easier.
It suits small, medium, and enterprise customers. It's a part of your Microsoft suite anyway.
How are customer service and support?
I didn't have to call anyone.
How was the initial setup?
It's simple.
What's my experience with pricing, setup cost, and licensing?
It comes with the Microsoft suite. I'd rate it an eight out of ten in terms of pricing.
What other advice do I have?
It's more suited for localized automation rather than enterprise automation. It doesn't have the right governance to do enterprise automation. It's more suited for individuals, not for groups.
Overall, I'd rate it a seven out of ten.
Which deployment model are you using for this solution?
Public Cloud
Disclaimer: My company has a business relationship with this vendor other than being a customer:Partner
Date published: 2023-03-21T00:00:00-04:00
Rated 5 out of
5 by
Shakir Mohammed from
Good document reading, and is scalable, but has complex reporting
What is our primary use case?
The primary use cases we are focusing on are applying automation to processes and integrating systems with API uploads. We have developed a module to handle private information related to the applications and API uploads to ensure the process is feasible without any challenges.
What is most valuable?
I believe document reading has been beneficial when dealing with Microsoft.
What needs improvement?
There have been some challenges. We have struggled to take advantage of the power of the program due to the complexity of the reports we want to send to Microsoft. This includes client complaints, large discrepancies, and delays from data centers to solve the issues. As a result, we have faced both advantages and disadvantages. After some time, I believe Microsoft may have made changes to the backend that we are not aware of. This could cause issues, and the client has experienced instability in the current process. To address this, we need to make sure that any changes to the backend are documented and communicated clearly to avoid any potential issues.
The technical support has room for improvement.
For how long have I used the solution?
I have been using the solution for six years.
What do I think about the scalability of the solution?
I give the scalability of the solution a seven out of ten. The licensing is not bad but scaling requires additional work on the solution.
The solution is intended more for small and medium-sized organizations, not for large more complex companies.
We have 5,000 people using the solution.
How are customer service and support?
The technical support attempts to address any queries, but their knowledge is limited. They try to come up with solutions for new problems and document them if they yield results so that if someone else has the same issue, they can get the same solution. However, they are technically struggling. To resolve the issues, Microsoft created a system where their internal technical team works with a mediator who understands the problem but may not understand the technical details. This mediator then takes the ticket up to the technical team analyzes the issue and provides a resolution. This system has saved them time in responding to and resolving the issue.
What about the implementation team?
The initial setup is great. We're currently building with the connectors. However, automating the process may require additional hardware, which can take time to implement. We have to apply the policy and see how their applications access information. To accommodate the additional hardware, our plan has to be adjusted, but if we don't involve any alternatives, we can deploy more easily.
The automation portion if required is a different department but for the basic setup, we only require two to four people.
What's my experience with pricing, setup cost, and licensing?
The license is 20 million rupees per month. The cost is okay but we are paying per month. Microsoft is providing a license that is automatic which is very helpful. But we know that of the solution, we don't have any annual subscriptions. We pay monthly, otherwise, we choose another solution.
Microsoft is providing an automatic license with a cost of $20 million per month, which is reasonable. However, we don't have any annual subscription options, so we must pay monthly or choose another solution.
What other advice do I have?
I give the solution a seven out of ten.
Microsoft is predicting that improvements will come in the future which will be better than what's currently available in the market. Even if they can build simple and medium processes, they still need to add certain elements and acquire certain licenses in order to run the machine from one place to another. We need to let go of the keys, such as a community rotation which we are automating. I don't believe updates should be pushed for those who are happy with the version they are using because that version is capable and we have fixes for any issues that may come up. Microsoft is now focused on automating development processes. It is important that Microsoft give the community rotation back to users, as we are all users. Regardless of size, we need to be aware of the upgrades that are being made.
We don't believe additional personnel is required for maintenance. We currently have adequate processes in place and automation. In total, there are fifty processes running, two for every system. Therefore, we do not anticipate needing to increase personnel for maintenance purposes.
The other departments have implemented the AP60 and are currently working on it. In my department, we are using Power Automate which is working but I need to check what progress the other departments have made and if they are facing any challenges to determine if it is easier to build with AP60 or with Power Automate.
There are many alternative solutions to Power Automate that also are cloud-based that I believe offer an annual subscription but I am not sure.
I would suggest starting with simple or medium processes, rather than complex ones. Begin with a pilot project to determine if it is profitable or not. We should also try to find a way to automate the process, as it could otherwise become stuck. Additionally, it is important to consider any issues that could arise with the elements that are currently working; the same elements may fail tomorrow. Ultimately, if we can handle these issues in the development phase, the solution will function great.
Which deployment model are you using for this solution?
On-premises
Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2023-02-06T00:00:00-05:00