Enterprise Architect at Ecobank Transnational Incorporated
Real User
Jan 17, 2023
The refresh cycles for our dashboards could be better. I keep complaining about that. The refresh is supposed to be once a day, but I would love it if it was real-time so that if I make a change to the data in iServer, I should see those changes immediately reflected in the dashboards. They use Power BI, and it seems they've scheduled their refresh to be once a day, which is not that good for us. We've had some issues with the integration between Visio and iServer because sometimes the add-in that allows you to do that integration takes a lot of memory and then your Visio crashes. However, I've not experienced this issue for some time, so it was probably fixed in the recent version. Also, if I copy a large amount of data and I want to copy from one Visio file to another, I have had a case where it suddenly just closes Visio without saving. So, that integration could be more smooth. There should be ease of integration with other systems in our environment such as SysAid. I understand that there is an integration to ServiceNow, but we use SysAid. We need to be able to say that when there's an incident that impacts or requires a change in a particular component, ServiceNow or SysAid should be able to communicate to Orbus that this component is about to change. Similarly, when it comes to discovery or when a new architecture change has happened in the enterprise, we should be able to detect the change in the baseline Enterprise Architecture. There should be such advanced automation. The visibility of our models is limited to those to whom we have assigned licenses. I would've loved it if everyone in the organization could at least see the diagrams. The licensing should be there for those who need to make updates or changes.
ICT Architect at a energy/utilities company with 5,001-10,000 employees
Real User
Jan 17, 2022
We found a few issues with importing data and all the manipulation of data, especially when it came to the BI side of things because it utilized a particular template to be able to get certain reports. The user administrators could not manipulate it to get the right reports. With iServer 365, they have said that those things were resolved but to fully test it because we only migrated it in late December. I can't tell you all the defects that we have found within iServer 365, but a major issue was that we won't go to fully customize it without the intervention of the team to do any kind of customization or dashboards. That was our major problem with the old system. If you're coming from the 2019 on-premise version, the report packs are grouped in the same manner as in the old 365. If they review one pack, the on premise pack, and there are five dashboards in a pack, that same pack would now only have four, or three dashboards in some cases. The other two that you're missing are now within other dashboard packs that you have to find or you have make switches to find. In that case, I would like them to make it easier to find old dashboards that you would've had configured in the previous system, so at least you can start back from where you last left off, or from a familiar area. We had five dashboards in one particular application portfolio pack, and when we re-installed the new application portfolio pack, we were missing two, only to find out that those two were now part of a different pack, which we did not have a license for because there is a limited amount of packs available to use. We weren't aware of those types of inconsistencies.
Enterprise Architecture Management (EAM) is a strategic discipline that outlines a comprehensive framework to manage and align an organization’s structure, processes, and information systems to achieve its goals and objectives efficiently.Enterprise Architecture Management provides organizations with the methodologies and tools necessary to effectively map out their current structures and future states. This discipline helps navigate the complexities of aligning IT strategies with business...
The refresh cycles for our dashboards could be better. I keep complaining about that. The refresh is supposed to be once a day, but I would love it if it was real-time so that if I make a change to the data in iServer, I should see those changes immediately reflected in the dashboards. They use Power BI, and it seems they've scheduled their refresh to be once a day, which is not that good for us. We've had some issues with the integration between Visio and iServer because sometimes the add-in that allows you to do that integration takes a lot of memory and then your Visio crashes. However, I've not experienced this issue for some time, so it was probably fixed in the recent version. Also, if I copy a large amount of data and I want to copy from one Visio file to another, I have had a case where it suddenly just closes Visio without saving. So, that integration could be more smooth. There should be ease of integration with other systems in our environment such as SysAid. I understand that there is an integration to ServiceNow, but we use SysAid. We need to be able to say that when there's an incident that impacts or requires a change in a particular component, ServiceNow or SysAid should be able to communicate to Orbus that this component is about to change. Similarly, when it comes to discovery or when a new architecture change has happened in the enterprise, we should be able to detect the change in the baseline Enterprise Architecture. There should be such advanced automation. The visibility of our models is limited to those to whom we have assigned licenses. I would've loved it if everyone in the organization could at least see the diagrams. The licensing should be there for those who need to make updates or changes.
We found a few issues with importing data and all the manipulation of data, especially when it came to the BI side of things because it utilized a particular template to be able to get certain reports. The user administrators could not manipulate it to get the right reports. With iServer 365, they have said that those things were resolved but to fully test it because we only migrated it in late December. I can't tell you all the defects that we have found within iServer 365, but a major issue was that we won't go to fully customize it without the intervention of the team to do any kind of customization or dashboards. That was our major problem with the old system. If you're coming from the 2019 on-premise version, the report packs are grouped in the same manner as in the old 365. If they review one pack, the on premise pack, and there are five dashboards in a pack, that same pack would now only have four, or three dashboards in some cases. The other two that you're missing are now within other dashboard packs that you have to find or you have make switches to find. In that case, I would like them to make it easier to find old dashboards that you would've had configured in the previous system, so at least you can start back from where you last left off, or from a familiar area. We had five dashboards in one particular application portfolio pack, and when we re-installed the new application portfolio pack, we were missing two, only to find out that those two were now part of a different pack, which we did not have a license for because there is a limited amount of packs available to use. We weren't aware of those types of inconsistencies.