Intellect BPM [EOL] Reviews

It's allowed us to quickly develop some basic applications or solutions to replace existing ones.

I think it's a good tool to use as a stepping stone. I can use the spreadsheets with something basic where they can keep track of all the information in a central location and control it with access control, user groups, things like that.

I'd like to have the ability to customize the look and feel of the system to more like HTML5/CSS where we can control the colors of the tables and match the logos.

We've used it for three years.

We've had issues with deployment, but more so with the upgrades. There have been a lot of nice changes, but they've caused troubles.

I'd say stability is 7 out of 10. Basic deployment and basic solutions are stable. For publishing and mobile apps, there's definitely improvement that's needed.

We haven't had any issues with scalability.

We have our own internal support, so to go to technical support it's usually an escalated issue. As long as the engineers get in, we've had a good response lately from them. I would say a 7/10 overall.

We provide it for our clients. It's a good application to get people moving along into the next generation of solutions.

The installation is straightforward.

The product is very powerful. You could automate any business process at any level of complexity, integrated with other solutions, send notifications, and generate any type of reports. The platform also allows you to create integrated iOS and Android mobile apps without custom coding.

Our approval processes are now automated and handled through Intellect, eliminating delays and unnecessary email communications.

There were some performance issues with some reporting features, but that has been fixed in the recent versions.

We've used it for about 3 years.

We've had no issues with deployment.

We've had no issues with stability.

We've had no issues with scalability.

Intellect customer service is excellent. They are knowledgeable, friendly, and overall great to work with.

Intellect technical support is very capable. They are available 24X7 and are very knowledgeable.

We didn't use a previous solution.

Yes, the setup of this product is very straightforward.

We implemented the product in-house.

We now have much faster and traceable approval processes.

I think the pricing is very competitive.

We did not evaluate other options.

I highly recommend Intellect!

• The ability to quickly develop a master-details relationship.
• Drill-down capability from anywhere, whether you are on the chart, table or screen.
• Develop a consolidated tables with summary reports, and the workflow structure and approval process.

Increased number of patients' participation by 300% in one year, and increased the number of providers 10 to 50. Increased revenue by two-fold and eliminated billing errors by 30%.

• Charting capability.
• Provide additional chart types and dimensions, and to allow more flexibility when using charts.
• In addition to importing flat files, allow dynamic use of imports

8 years

No issues at all. The platform is very robust and provides alternatives with ease of use for data conversion or importing data from other systems.

No issues at all. The platform is very solid and robust. I never lost data nor have compromised the integrity of the data.

No issues at all. My application grew by 500% since inception in functionality and data contents. I started with one module; four years later, I had more than eight modules.

Excellent. I had substantial support initially as I was developing the application. Interneer held my hand throughout the process whenever I needed help.

Excellent. I had substantial support initially as I was developing the application. Interneer held my hand throughout the process whenever I needed help.

Yes I used Oracle Express, but it was very complex and expensive. It takes longtime to develop any application.

It was very simple and straightforward setup. I used the cloud model or hosting solution by Interneer. Once you';re assigned a username and password, you can quickly begin developing screens and pages.

I used an in-house development. The entire application was developed in-house using internal team and the support of the Interneer technical support team.

Over 100%. The largest return on our investment was due to increased revenue which resulted in increase in patients' participation and reducing billing errors.

Use the hosting solution to get the best per user license. You do not have to worry about setting up your hardware and software licenses. The hosted per user license is the most cost effective solution.

I compared it with Oracle express, MS dynamics and Brio solutions; While these solutions provided large and complex capabilities, they fell behind on the business workflow process and total cost of ownership.

The best and most cost effective product available that provides a rapid development and stable solution. The platform has three concepts combined into one robust solution; Web application development, business analytics and business process workflow.

The capability to interface with other applications and systems is the most valuable feature for us. For example, Intellect built an interface to our online banking platform and core system. This gave our bank a tremendous advantage to add new features to the online banking system and have those transactions flow into Intellect where it's routed to the appropriate department and/or update the core system.

We used it to automate over 100 operational processes. The organization had embraced Intellect as the go-to method for implementing new processes. It's played a big part in the vision of end-to-end automation.

They need to offer more customization to the User Interface so that the native mobile app can be branded with the client’s logo/brand. Also, they should make it so that the custom/branded app can be download from the app stores.

I've used it for several years.

There were no issues or surprises that I can recall. Deployment on-premise was easy and we started small with only a few workflows. The deployment issues we had were more related to our staff and training and not technical.

There were no stability issues that I can recall. There were some latency issues, but those were mostly due to network response on our side. The Intellect product is very stable itself.

We started with a few processes and grew to over 100; therefore, no scalability issues. My experience was at a bank for 200 internal users and 35,000 customers who access Intellect workflows externally.

This has been one of their greatest strengths. Their staff is professional, highly qualified and issues can be escalated easily if necessary.

They have many levels of technical staff. There are engineers and others that work at a higher level. Tech support appears to be organized and responsive.

Our previous application was a monster in terms of administration. It required staff with programming/scripting experience and took days to complete simple, straight-forward workflows.

The initial setup was painless. We had one IT administrator assigned to the project and he assisted on a part-time basis. The process is very turn-key to get up and running. Most time is spent on collaborating with others internally to design the workflows, make decisions etc. The technology has less of an impacted, as it should.

Implementation was in-house and vendor assisted. The vendor was supportive every step of the way. I would rate the vendor as excellent in terms of the implementation.

The ROI was significant. I can't remember the exact dollars, but with time and material savings plus soft savings such as reduction in errors and improved service quality, the payback on investment was about one year. More important and in retrospect, operating without BPM and Intellect was simply ridiculous.

The pricing model has changed over the last few years so I can't recommend anything specific other that opting for the enterprise version so that the product can eventually be deployed enterprise-wide.

Yes, one other was Adobe which we had used previously. I don't recall the others we looked at, but do recall getting the biggest bang-for-the-buck with Intellect.

I believe with the addition of mobile application support and being able to access workflows via a mobile device, it's a real game changer that organizations should take advantage.

It allows us to control and manage our non-conforming audits. We can then manage the workflow and get the right information back to the right decision makers.

I also like the reporting. By way of background, we previously managed our quality systems with an Atlassian solution. While it had a lot of the same functionalities as Intellect (workflows, assignments, data gathering), it was really lacking in the ability to do different integrations between tables. It was more of a flat file.

Intellect has the ability to duplicate the same type of functionality as far as the workflows, assignments and status with the added ability to have relational database where we can do better reporting.

What we do with that report is try to improve the quality of our product. Where we were only able to get in a single dimension of various non-conformance or corrective actions or business related, we're able to have multi-dimensional reports that give us an excellent picture of what's going on in our business. We have a large supply base that forms a product in our business, and being able to make good decisions, what to do with vendors, and identify gaps has been really valuable to us.

It is a very feature rich product. We haven't reached the limit of what we intend to do with it by any means, but certainly we desire and we've got pretty big imaginations here. We do want to do some pretty cool stuff, so there are some things that we've requested.

I think the one thing that's immediate right now is the ability to publish selective things instead of the entire application itself. Literally, at this very moment, in a situation where when I started making some major changes for another release, which impacts things that are in use right now very significantly.

I've got users out there that need me to make changes to the current setup that are fairly minor, but I have to make an archive of my design environment, put it off to the side, and adapt the environment to my design environment, make those changes, publish it, then right back and then duplicate everything I just did. I want to add a report, or I only want to publish a single app. I know it's standalone in and of itself, and it's been hard from a design standpoint.

We've used it for four years.

We haven't had any issues with deployment.

There were times that it was fairly unstable. Just last week, they moved us to a new server hosted by Amazon. There's been two instances in the last month or two where our design database disappeared completely and then magically reappeared, and we don't know why yet. We are working with Intellect to try to figure it out. There's the suspicion of one or two things may be self-inflicted.

There were times where our production site was slow, and we think that that might be fixed now with the hosting on the new server.

Scalability was one of the key decision in going with Intellect. We did look at quite a few different solutions. We considered external development and had some very competitive bids. We looked at some competing products, but Intellect stood out primarily because of it's scalability and the ease of development. I did a test case development over the period of a couple weeks where I was able to get familiar with the product, how to build an application and publish it over a couple weeks. For me, that's what really sold me on it -- its user friendliness and then also the fact that it really isn't limited to larger organizations or smaller. It's something that we can build out and it's going to be able to grow.

With scalability, I don't see as an issue. There isn't a user cap, with the exception of the number of licenses that we have available to us.

Holistically, I could see Intellect serving us for the next three to seven years with ease.

I checked in with the helpdesk, with the technical people there, in particular I've been working with a particular employee a lot, calling him up in a panic a couple of time, and he's been incredibly helpful and very responsive.

The setup was pretty straightforward. I've been managing software development groups for twenty plus years and used all sorts of different kinds of applications that you have to do all sorts of configurations, and it was very easy for me because I could tell it was based off of the net UL database with and afp.net interface. I've worked in that environment before, several times, so a lot of this is familiar to me.

We considered our own custom development. We really never considered any out-of-the-box solution before. The two options were self-implementation and a customized solution that we had developed externally. This definitely seemed like the right route to go. It was very competitive in terms of cost. 

The time for us to develop was reasonable. In other words, while we build our apps, we're the experts on how our business works and we can go in and fine-tune the apps to work with the people that actually use them. For us to develop it here internally made a lot more sense.

Know your business and have a plan. I would say that you should really try to establish some realistic expectations for implementation. You need to have your processes somewhat formalized. If you do that, then building out a workflow and trying to decide user groups and users, that really comes down to the way the business works. Knowing your business is a really significant first step.

The most valuable feature for us is the workflow aspect of it because it's extremely powerful and completely flexible. You build your own workflows so it's got full, customizable workflows with all the features like branching and loop-backs and things that you'd expect a workflow to have. Secondly, it's versatile because it's a sort of build-your-own-application, completely customizable to meet your needs and you can do it really fast.

We wrote it specifically for a major 10-year waste water treatment plant construction project. But we also manage a whole range of construction contracts totaling $2 billion.

All of these construction contracts have processes for handling different types of information -- technical submissions, requests for information, management of financial change, pay applications, correspondence, and many other different types of documents. There are rules in the contracts about how they get handled and Intellect enabled us to systematize how we handle and process all this information.

It's allowed us to enforce and audit everything -- and scale it as well. There's now accountability because you always know where you are in the process, who owns what, and it's reduced the number of people required to administer it.

And because it's customizable, we've configured it to match the way we already work.

In the eight years I've used Intellect, it has improved dramatically. Four years ago, I would have suggested improvements to the way it handles printouts, but that's been improved by the integration with PDFs. I also would have suggested integration with other databases, but that's been done as well.

Two years ago, I would have requested a mobile version, but now there is one. At the time, I also wanted a hyperlink that could link to any record anywhere in the system irrespective of which template is was. But they added that upon my request.

Also, there were cursive queries that involved parent-child and parent-parent relationships, but the data in the system got very large. Those queries would then take exceptionally longer and slow down the system, resulting in performance issues. So Intellect developed a new way of avoiding cursive queries altogether.

I struggle to think of a big new feature that I'd like added because I've built it out to be very big and very stable. It just works. As our big project is winding down, we're considering whether to market it more generally for our company. Because we've built it out, we can use it in the future.

Actually, one of the big things that they could have improved is the visual interface of the project, but even that's just being revamped, so I can't complain about that now.

I've used it since 2007.

We haven't encountered any issues with deploying it.

When we began using it in 2007, we had some stability issues with the very early implementations, which were partly due to the platform and partly because it was a custom application. But since then, stability has been very, very good. The platform is sufficiently mature and the stability issues have been dealt with.

We have 400 concurrent licenses with many more users than that. I know that Intellect has done implementations for tens of thousands of licenses, so I don't think scalability is an issue. You can have many people logging in and your internet speed will govern how fast the application runs, not the application itself.

Realistically, you have to support your application because you wrote it for your users and Intellect doesn't necessarily know how it works. If there's an issue with the platform, they'll provide support as well as professional services for an extra charge.

They have the ability to support you at every level, but for the key issue of supporting problems with the platform, they're very, very responsive. I'm able to pick up the phone and talk collaboratively with a person. They've really helped us build out our platform.

When we were starting the construction project, so we had a very tight timeline. So we scooped out what we wanted the system to do and we accepted that it had to be built in a modular fashion. We built the backbone of the system in 8 weeks with the first two key modules. We brought in two Intellect professional services people for eight weeks. During this time, the trained us and worked with us to develop and work the application.

The setup wasn't completely painless. As soon as it went live, we realized we hadn't quite designed it the way we wanted it and it wasn't quite right, but it was working, so we carried on with it. Afterwords, I planned out a larger design three weeks later and, without taking down the system, with the help of the professional services people made the changes overnight. So in the first three months, we had some wobbles, but we were on course to build out the system smoothly over the next two-and-a-half years.

Because it's so flexible, we were able to make major changes to the system even after going live. We weren't stuck with our initial implementation.

Designing workflow using Intellect and implementing everything in Intellect proves that you have a process because it's there built into the system. And because it's built into the system, you're constrained to follow the process, so by definition you're following the process that's in the audit trail.

Every time the auditors came along and said, "Prove that you're following these processes," you just pull up a few records in the system. So there's a huge reduction in effort required to meet quality assurance requirements.

This is but one way that we achieve ROI with Intellect.

I've done this lots of times. I've been asked by many people about what licensing is and there are some key things. The first thing is, you want something like Intellect if you have information to manage and you have processes and rules that have to be gone through to manage the lifecycle of information. If you're managing 10 pieces of information, you don't need Intellect. If you've got thousand pieces of information and they all have to go through the same process, the same routing, then you want something like Intellect. Therefore decide if you need it, and then if you do go down the road to having a system like this, the first thing you have to do is decide what you want the information system to do, and it's equally important to decide what you don't want it to do.

You decide what you want the system to do and not do and then you come up with an implementation plan. You put a lot of thought into the shape of the system and you design the backbone of the system to be big enough or flexible to meet your current and future needs. You produce a plan like that, but it's really important from the outset to decide what it's going to do and what it's not going to do. What are the boundaries of your system?

I'd probably rate it 8-and-a-half out of 10 because it's not perfect and there's always room to improve something.

Business Automation at the speed of thought which is 100% aligned with your business! Empowered knowledge workers - anyone can be use the tool with very little training. Accelerated time to market for web and mobile solutions.

There are a few different ways my clients have improved the way they function using Intellect. First and foremost, Intellect can be deployed as an enterprise BPMS platform with automated workflow across departments, the organization, and outside business partners. This solution provides for a scalable and extendable platform that doesn't require additional licenses - you can build as many apps as you'd like without increasing your costs. From an investment standpoint, it becomes one platform across the organization instead of many single-purpose solutions, reducing not only disparate applications, but also minimizing the number and types of skills required to maintain the solutions and platform.

Secondly, anyone with spreadsheets can EASILY replace them and add workflow in very little time. All data becomes searchable immediately and access controls can be added to ensure data security and integrity.

Another example of how clients have improved their business functions is by replacing e-mail as a data repository. They now capture BUSINESS information that previously got "lost" in emails. In many organizations, e-mail serves as communication tool as well as a way to share business information. Unfortunately, e-mail data is typically unstructured and valuable business data may never be turned into usable information. Intellect leverages e-mail (SMTP) to communicate key information (e.g. a work activity requiring an approval), but the email routes the user back to the business application to perform the function and capture the business data (including things that might typically be lost such as comments associated with the approval). This is invaluable when you are dealing with business processes such as Contracts Management.

A final example of how Intellect has been successfully leveraged is using it as a "Requirements gathering and application design" tool ... rapid modeling for applications. It's so easy and quick to build forms and workflow that you could add the forms, model the workflow and quickly represent the application functionality you'd like to automate. If you determine it's not the best solution-fit for that particular business need, you at least have the requirements gathered, processes modeled and you know what you now need to seek out in other solutions. Additionally, you can use the model and the workflow, to actually communicate your needs to other solutionvendors. What we find in actuality is that Intellect remains the solution once it's configured

A recent improvement was a re-vamped configuration management function referred to as a "publish" feature and a completely new web 2.0 look and feel. The usability with version 8 is incredible.

I would like to see more re-use through "modularization". By that I mean developing a more object-oriented view of things. Currently, everything reside on one platform. In order to implement an object-orientated environment, you would need multiple installs of the product, which is doable. But then you create multiple databases, so you have multiple administration. There's many benefits to doing that too. You might have a sandbox environment for one set of users that want rapid deployment.

If you have a mission critical app, you might want a user-base to go through structured changes, change control stipulation management, and have more business insurance/disaster recovery/business continuity planning behind that. You can do that now, but I would like to see as the business grows and builds on the platform, that you could create objects and basically call out those objects for use.

5 years.

It really depends on the deployment. The stability has gotten better, especially with the new releases of version 8, but there are some inconsistencies that happen because the product is so robust. It has a lot of complexity behind the scenes to make it easier for the analysts and people designing. There's a lot of things that have to happen behind the scenes to keep the databases normalized, to keep the integrity in check. Sometimes something might happen in the backend. It's so invisible to the end-users, it's geared as an element of inconsistency or instability but there's a reason for it. Again, the power of the tool is its biggest benefit but also its biggest detriment. It's so complex on the back-end.

From typical support in other vendors I've experienced, their support is incredibly accessible and you can get to very knowledgeable people, and that's just in my personal experience.

If I need to get to people who actually built the application, I can get to them. I know the owner personally and I've been doing work with them for a long time, so they are very accessible. As they grow, that's going to be the biggest challenge for them and continuing to afford that level of customer service, but yet scale up.

I found them in an interesting way. I came out of a big organization that, we did a lot of consulting with process re-engineering, process-improvement type work. I had done a lot of, in my younger days, a lot of modeling with business processes to understand how the processes work and then do the improvement and then, as a subsequent step we would automate. What I was seeking out years ago, I was looking at what could model in a way of business office redesign. Instead of using Visio for example, we used what could model but may be that automation tool. I backed into the tool. Most people look at it from a basic forms management tool first, and then workflow is second.

I wanted workflow automation first and then I looked at it from what forms or what business areas you could actually automate, and then I model the process, make the process work, and then pick apart the form. There was a big chance for me to pass through that. It's a little bit of different approach, I see the workflow as most valuable or most powerful aspects of the tool.

I come from a technical background, so from a technical perspective it's very easy. It's very easy to install, very easy to set up in a new environment to the point where I could set up an entire new environment in an hour. That's from the ground up. Database configured everything. That's as easy as it is.

In terms of administering it, once the application is running, in terms of the administration, it's relatively simple. There's an administration consult that allows you to do the things you need to do to administer and actually configure the files to the associations. In terms of relative ease of installation, I would give a 11 out of 10 relative to other products I've used.

Every time that I look to use the tool, there's an easily identifiable return on investment, and that's due to a couple different things. I don't know if I could give you an actual number, but it deals with a couple different things. One is the power that comes with automating an existing manual process. The returns, in terms of intangible benefits I find are the power of the performance, the productivity definitely increases when you get to automation. Intangible benefit of accountability and transparency into processes, that's hard to measure. It's incredible.

Taking and reducing risk is another. You could actually make it a tangible benefit by looking at the probability impact at the risk of time, but the fact that you're getting non-structured data in emails, in spreadsheets and you're actually putting a process, a strict process around what then happens to that data. In terms of who sees it, accessibility, controls, and you're actually storing it in a database for recording purposes. Those are huge benefits and reduce risk dramatically.

A couple of different advice points. First of which is, start with something that you know you could show value quickly. A business process, you know there's pains, you know you can measure those pains, and it gets you used to the product itself. Once you start using the product you can see the value of it, so get used to using it so you can see the value everywhere else, but be able to measure that value. In terms of stakeholders, in terms of who's making investments, they want to see value in anything they invest in, so show that value quickly.

The second thing is, don't forego thinking big, but yet implementing in a structure, in a phased way. Meaning, don't just start to model every process you can to throw it together. Think how it will be done in a system in a larger context, and this goes back to some of the object orientation and the marginalization.

Think about it in a broader context and then create a road map to bite off pieces that you can then implement and there are some reasons for that down the road that only somebody experienced with the tool would know. You can just plug away. You can build and build and build and build and build, but if you don't have an end game or some type of long term view of what the platform might be when you start to implement many business processes and include other business users, you would be best served to design it as you would traditional design and then implement rapidly.

I would say the valuable features are the form design. The form design is extremely, extremely intuitive, and also the dashboard design. I also love the drill-down capabilities and so forth. I would say it's some of the two best assets in those features in the product.

I think in terms of complication backlog, for us, our customers were a consulting outfit so any organization, any customers that have a very small or short, small IT staff and they have a backlog of work that needs to be done in terms of developing applications, I think this is a great fit for that kind of a model where you go in with no coding. You can develop applications as well as workflows very quickly.

One of the areas that I'd like to see improved, or actually it could be added in, is integration with some of the other platforms. For instance Microsoft Office, SharePoint, CRM and all other platforms. One other thing that they really need to put in is that BPM is central to everything and that you are integrating right into your line of business applications, your line of business applications can be written in C-sharp, can be written in Java. You want to access that information and then create a workflow or create an application.

If you want to access other platforms such as SharePoint, and/or integrate with them. Whether it be create folders, writing data to it and so forth via Intellect, or Microsoft CR communicating with CRM, that is also very important. Getting data as well as updating data from the CRM and SharePoint is very important because if you look in any organization data is all over the place.

So where the BPM platform comes in, a true BPM platform is not only workflow. It should be able to extract data, get data from multiple platforms, and then interact. So the way I see it is that a true good BPM platform is, BPM is central to everything to your organization.

3 years.

We have had no issues, I've been very, very impressed with it.

So for our need it has been very sufficient, very adequate. We don't have all the implementations you have done. We don't have a huge, large number of users. What's important to us is the process, in terms of that's more important to us. In terms of scalability we have had no issues so far.

I would say they have been knowledgeable and proactive. They're all very supportive and very good because one of the things that I always look for in a product is support. I've been with other organizations where support has been very lackluster, so this, Intellect is one of the better ones out there.

I would say the Intellect product is probably one of the most straightforward set up I have been exposed to. There are other products which I still work on a day-to-day basis which is a whole lot harder, learning curve is a lot more steeper. This is one of the better ones out there.

In-house.

My advice would be to use the product, I mean it's funny though. If you show this product to a hardcore developer thery're going to say no-no, because it's job security.

Programmers like to write code and in Intellect you don't write code; you configure, so that's a big difference in there.

The people that we talk to are the CIOs and those kind of folks because if they want you to improve productivity in a given organization in terms of making the backlog, application backlog shorter, then I would say this is a great, great tool. So that's the advice that I would give. It alleviates or shortens your development cycle many, many fold.

I think the licensing model has been very, very clear. Obviously the price has gone up so no one would like to see that, which is good for them. The licensing pricing model for us and the vendors to implement this was great. Still really it doesn't matter because I think as far as customers are concerned any time when you convey the message that this is cheap usually there's a psychological barrier that cheap means they're not necessarily good.

Sometimes when things are a little bit more expensive the notion is okay, this has got to be a good product, so it works both ways.

I’ll tell you why we approached Intellect and why we brought it on board: The US Department of Transportation has a very large IT department and I had an annual budget of $4 billion, 3000 employees, 10,000 contractors, and 200 major systems. I oversaw the Federal Aviation Administration's traffic control system, which was one of the largest systems. As CIO, I got requests from all kinds of folks in the DoT.

There are various bureaus within the DoT, the FAA being the largest. We were getting continuous requirements for developing new systems from various bureaus, our sections, managers, etc. Money in the government is never enough. We would get these requests but we didn’t have the resources to complete the tasks. I really had two options.

One option was to tell these folks that I don’t have the resources and I can’t do anything for them. What that would have done is these guys would’ve then gone and tried to get money from somewhere and tried to build the solution themselves. If they did the development themselves, that would create a problem for me somewhere in the future. That was option number one. The second option was to say that I'll do it, knowing that I never had the resources. I would either not get to doing it or would do it poorly.

I was really looking at a third option. I wanted to have an option where I would say, I am going to give you a resource or a platform which is simple enough that the business user can use and build the system out the way they like it because it is very simple. Then once you decide to operationalize it, we are going to quickly test it. Then once you do the testing, we will just add it to our entire platform and it will be operational across the entire DoT.

I was really looking at that kind of platform which was plug-and-play. We searched and searched and really never came up with a good solution. We looked at everything from SharePoint to Dynamic CRM to Salesforce. They were too complicated for the average user to actually build solutions. We were looking at Intellect to be that particular solution.

It helps in two ways: One is if you want to quickly prototype something, you can very quickly prototype and build the system out, so that's very cool for an operational system. Secondly, if you want to give your business users something to use very quickly, the system allows you to do that.

I think their help feature is significantly PDF-based. I would love it to be more search-based and context-based and give sensitive results. There's potentially an opportunity for problems. That's one thing.

The other part that I’ve seen is that you need to be using Internet Explorer to actually start building this product. I personally use Mac, so I can’t use Internet Explorer so I potentially need to have a simulator to go out and do that. Maybe there is a workaround for that, but those were the two things that I came across.

I've used it for one-and-a-half years.

We've encountered no issues deploying it.

It's been a stable solution for us.

The way we have been using it has been perfectly fine. Now, have I used it for tens of thousands of people? I have not, so I would not be able to say that, but for all practical purposes it seems to be scaling well. Essentially it is very, very simple. It has built fairly complex solutions very quickly, so I really like that.

I certainly think they have been proactive with us, so I don’t know what the case is with other customers, but with us they have been very proactive.The interesting part that we found is because the solution is so easy, one of the things that we are going to do with Intellect is we are going to have these workshops with Intellect where a business user can come with an idea in the morning and within 5 days learn the platform and actually build that particular application.

We are creating a program like that. We think that's going to be very successful for government users. When they get trained, they will spend the 3-4 days that they are in training building the platform that they want and can then use.

The company I am running finds major areas of needs or challenges within the government sector, then we try to find disruptive technologies which can actually address those problems or challenges.

If we think that that solution is good, then we do some preliminary due diligence on it, and once that is done, we onboard this on to our GOVonomy program. We have a process to introduce these products into government, so that government becomes more efficient. It was in that regard that we came across Intellect and that's how we on-boarded Intellect onto GOVonomy.

It is not complex. It became a little bit complex for us because I was using Mac and when I tried to use the system on Chrome, it wasn’t working. Then I went to the help and then that's where I found that the help wasn’t that searchable, but then that's where I found that you need a simulator. Once I used the simulator, it was fairly simple. Once you get to know that, it's pretty simple. It takes a couple of hours for you to figure out what philosophy this thing is based on and how you even build it out, but once you get that, it is simple to use.

It can save you tons of time building fairly complex systems, but initially obviously you need to understand how the system is set up and what kind of drag-and-drop features you have and where exactly those features are located.

There is some learning curve there, as with any other kind of system. Even a tool like Word or Excel you still need to know which features are embedded where. It takes a little bit of time for that, but that is not really a particular issue with this software. It is with any software, but once you get to know that things are very, very good.

I want to give this as an advantage and something for potential users: If you are in a situation where you don’t have really high-tech programming or engineering staff to build out applications, and you want to still build out very robust applications, this might be a very, very good tool to use. That's one area.

The second area, as I mentioned, maybe you have the technical folks but they are all occupied and you want your business users to build it out.

Third, if you want to build something but you want to prototype and run it and build something which is massively scalable again, this might be a good application.

Those are the 3 areas which might be worthwhile about the solution.

It's been the customer support, the direct interaction, it's been members of the technical staff and also account management. Even their executives have been available if we needed them.

All companies grow and expand, there's a need to re-engineer processes to make sure that you are providing operational procedures that are efficient and effective and this is one way of doing it in a very value-centric manner.

The value that Intellect BPM Platform in comparison to the other products that are out there, while still allowing you to provide a very effective BPM applications, is huge. Especially for businesses in our market, that small to medium size business.

The full HTML five support is key for us, so that we can start to utilize it outside of more than just in our standard browsers. I know it's something they're working on but it'll be great to see it in place once it finally is. So full support directly from a mobile phone without any type of application installed and full accessibility to all the applications would be great.

It has been very stable. We've stayed on the front side of all of the releases and so far it's been pretty stable. Obviously, it's like any platform, we've had to do our fair share of testing to make sure that everything is the right quality for what we want for users, but stability-wise, we haven't had any downtime with the product yet.

Initially, we bought the product and put it in place for roughly fifteen to twenty users and now it's in place for about two hundred and sixty and that required very minimal scaling on our end. We did increase the amount of web servers that we had in place by double, but it was very easy to scale.

They are knowledgeable and proactive. We've had a few issues that the direct customer support team has taken on and the tier one support doesn't really answer, which is rare. They have been able to get us in contact with a member of the technical staff pretty quickly that was able to answer our questions and resolve things for us.

I think if you're comfortable with setting up any type of web application or any similar type of infrastructure, it was pretty straightforward.

I think it's something we're still looking for down the road. With all these platforms, there's somewhat of a substantial investment that you have to make as an organization, but as we continue to expand it's user base, as with any organization, we're going to start to see more and more return on the investments, but at least in these first year to eighteen months, it's been a learning opportunity for us and kind of setting the foundation for that long-term ROI.

We did consider other options. We evaluated five other products ranging from some of the more expensive ones like Appian all the way down to some of Intellect's closer competitors and at the end of the day, we decided to this was the best value for us.

Just engage with the technical staff. They have been very helpful in getting us in place and up and working and I was very surprised at how efficient they were in the professional services that we did purchase from them. Sometimes, you can find that organizations are very spend-happy with your money, but Intellect has actually been very frugal with the professional service hours that we've purchased, so I would say utilize the professional services.