I would advise others that are wanting to implement TIBCO EBX they should try to build the data model from the beginning until the end. Take the time that they need, try to build as much as possible in the data model. It is best to build the workflow that they want at the beginning. They have to decide if they want history or data governance, or exactly which other part they want. It is important to build what they have and want on paper regarding the functionality of their core system before implementing it into TIBCO EBX. I rate TIBCO EBX a ten out of ten.
Sr Technical Architect at a computer software company with 10,001+ employees
Real User
2021-10-22T14:29:22Z
Oct 22, 2021
We're a customer and an end-user. Currently, we are one version behind. We're going to upgrade to the latest version maybe in two months, however, I'm not sure of the exact date. I'd advise new users to ensure they understand the scope of their implementation and applicability in their observation. I'd rate the solution at a seven out of ten.
Data Architect at a pharma/biotech company with 10,001+ employees
Real User
2021-07-24T16:25:44Z
Jul 24, 2021
We're just customers and end-users. Whether I would advise another company to choose this solution or not depends a bit on the use case they are going to develop. I would say that, if a company has a basic use case, a basic means of getting data from a few sources like Oracle, SQL Server, Teradata etc., then maybe it is sufficient. However, if you are having an enterprise-level situation for SAP or Oracle Apps , it might scale up that well. Performance is also an issue as it does not optimize the underlying clusters to a great extent as compared of its competitors. One good thing is that, with the data model, you can just go and see the data model very well, to the most granular level and identify if there are any gaps. It also has a rich compare data model feature. However, again, for the workflow, you cannot edit it in the visual editor. You have to go back to that tree setup and there after complete editing during compile only one would be able to see if any errors has crept in or not. Having said that I would say the Workflows once created are very robust. There are some competing tools that allow the editing of workflows in the visual setup itself. That is very easy for users. If you can edit it in the visual setup, you can directly see the impacted upstream and downstream tasks or jobs in that workflow and conflicts if any. This speeds up the updating of the workflows by the data engineers or data stewards. I'd rate the solution at a six out of ten. The solution is average from an enterprise standpoint.
Lead Data Modeler - Enterprise Data Strategies and Services at a financial services firm with 10,001+ employees
Real User
2021-04-01T09:39:00Z
Apr 1, 2021
We aren't using the latest version of the solution. We're a few minor versions behind. There are some questions coming up, of what our direction is going organizationally. There are some new directions that may include moving to the cloud from on-premises. That could have an impact. There's also an appetite for high availability and scalability and all of that as we are a very large organization. On the other hand, some of the competition that is using the same tool, are some of the really big banks and such. There are other organizations, other financial institutions that use it. Their typical complaints are concern over scalability but they're using it, so it's not so surmountable. The advice I give to others is if it's the first time you're doing data governance, you're not just implementing what you're doing manually today. You want to improve the process. There has to be some practice and awareness of the process design and the rules about governance. I'd rate the solution at an eight out of ten.
Head of Architecture at a insurance company with 5,001-10,000 employees
Real User
2020-02-16T08:27:00Z
Feb 16, 2020
I would advise interested people that you need to understand what it is used for, what the use cases are. It takes money and effort, but it could be very good for you. On a scale of one to ten I would rate TIBCO MDM a nine.
TIBCO EBX™ software helps organizations avoid silos with an all-in-one approach to managing data assets across the enterprise.
When you can manage and share all your data assets, you thrive. Data fuels mission-critical operations, analytical processes, and customer experience. With constantly evolving data from diverse channels and sources, business teams can no longer rely on simple office automation or outdated data management tools. EBX™ software, a recognized leader in Master Data...
I rate TIBCO EBX an eight out of ten. We have four administrators that maintain the solution.
I would advise others that are wanting to implement TIBCO EBX they should try to build the data model from the beginning until the end. Take the time that they need, try to build as much as possible in the data model. It is best to build the workflow that they want at the beginning. They have to decide if they want history or data governance, or exactly which other part they want. It is important to build what they have and want on paper regarding the functionality of their core system before implementing it into TIBCO EBX. I rate TIBCO EBX a ten out of ten.
We're a customer and an end-user. Currently, we are one version behind. We're going to upgrade to the latest version maybe in two months, however, I'm not sure of the exact date. I'd advise new users to ensure they understand the scope of their implementation and applicability in their observation. I'd rate the solution at a seven out of ten.
We're just customers and end-users. Whether I would advise another company to choose this solution or not depends a bit on the use case they are going to develop. I would say that, if a company has a basic use case, a basic means of getting data from a few sources like Oracle, SQL Server, Teradata etc., then maybe it is sufficient. However, if you are having an enterprise-level situation for SAP or Oracle Apps , it might scale up that well. Performance is also an issue as it does not optimize the underlying clusters to a great extent as compared of its competitors. One good thing is that, with the data model, you can just go and see the data model very well, to the most granular level and identify if there are any gaps. It also has a rich compare data model feature. However, again, for the workflow, you cannot edit it in the visual editor. You have to go back to that tree setup and there after complete editing during compile only one would be able to see if any errors has crept in or not. Having said that I would say the Workflows once created are very robust. There are some competing tools that allow the editing of workflows in the visual setup itself. That is very easy for users. If you can edit it in the visual setup, you can directly see the impacted upstream and downstream tasks or jobs in that workflow and conflicts if any. This speeds up the updating of the workflows by the data engineers or data stewards. I'd rate the solution at a six out of ten. The solution is average from an enterprise standpoint.
We aren't using the latest version of the solution. We're a few minor versions behind. There are some questions coming up, of what our direction is going organizationally. There are some new directions that may include moving to the cloud from on-premises. That could have an impact. There's also an appetite for high availability and scalability and all of that as we are a very large organization. On the other hand, some of the competition that is using the same tool, are some of the really big banks and such. There are other organizations, other financial institutions that use it. Their typical complaints are concern over scalability but they're using it, so it's not so surmountable. The advice I give to others is if it's the first time you're doing data governance, you're not just implementing what you're doing manually today. You want to improve the process. There has to be some practice and awareness of the process design and the rules about governance. I'd rate the solution at an eight out of ten.
I would advise interested people that you need to understand what it is used for, what the use cases are. It takes money and effort, but it could be very good for you. On a scale of one to ten I would rate TIBCO MDM a nine.