My main use case for BiZZdesign HoriZZon is as a read-only content platform primarily for everyone. BiZZdesign HoriZZon was introduced to us as a read-only platform, and we have added value by targeting certain artifacts for specific stakeholders. The operations team has one set, finance another, and so on. This targeted stakeholder management is a big use case for BiZZdesign HoriZZon. Recently, BiZZdesign HoriZZon introduced data blocks and contributor roles, making it easier for stakeholders to engage with the platform. These are two primary value-addition use cases. A specific example is using the Explorer functionality to generate and share artifacts with targeted groups. For platform architecture, the DevOps and operations teams access relevant artifacts, aiding targeted stakeholder management. Additionally, senior stakeholders are interested in architecture decision logs, which are aggregates of architecture decision records. We are working on making BiZZdesign HoriZZon a future decision support system by aggregating data for stakeholders.

Another use case is the ServiceNow BiZZdesign HoriZZon integration. The objects from ServiceNow are imported or created on BiZZdesign HoriZZon, allowing bidirectional interface for modeling as-is and to-be architecture. This integration is helpful for companies, despite challenges. I use BiZZdesign HoriZZon for Dynamic Solution Intent. The dynamic solution architecture helps engage stakeholders outside the architecture community, allowing for unified engagement and solution development using repository components.

A system administration module for BiZZdesign HoriZZon would make user management simpler. Overall system management activities, such as tracking the growth of the repository, would add value to customers. Previously, I used a different solution called System Architect.

View full review »

There was a merger that the client entered into, and following that merger, we inherited a large technology inventory from the acquired organization. The acquired inventory from the organization had a separate technology landscape, and the technology landscapes from both companies post-merger needed to become one. The challenge was to reconcile the inventory without freezing the ongoing architecture work.

The task at hand was to continue with the solution design and the architecture for ongoing projects and new projects while the collaboration and the inventory consolidation was happening. We used BiZZdesign HoriZZon's central repositories into a single source of truth. The architects needed to model new solutions. As an architect, I referenced the same shared reconciled inventory in BiZZdesign HoriZZon in real time and collaborated with other architects rather than working in spreadsheets or relying on tribal knowledge from legacy people from both companies to come back into my solution design and model with the latest version which was approved for the company's new company version of technology and was to be kept. This helped the inventory rationalization and active architecture design both happen in parallel instead of sequentially.

View full review »

As a consultant, my main use case for BiZZdesign HoriZZon involves working with clients to determine their needs. Either they have certain tools like Spark or ARIS and want to migrate into BiZZdesign, or they don't have any tools at their end and want to adopt new tools to maintain their architecture. BiZZdesign HoriZZon is where this process comes into the picture.

A specific project where I used BiZZdesign HoriZZon involved a medical client who didn't have an architecture tool at their end. We went and tried to understand their infrastructure and their applications, and then we designed their application architecture, enterprise architecture, and brought their solutions into BiZZdesign.

Normally, I use BiZZdesign HoriZZon by suggesting my clients go with TOGAF and ArchiMate standards. This gives the cross-modeling and knowledge graph, highlighting the strengths, cloud-native web access alongside local designs. BiZZdesign helps to do that flawless implementation within it. We adopt the standard and also implement that in BiZZdesign, which helps the clients with their transformation projects or with their cloud migrations.

View full review »

Our main use case for BiZZdesign HoriZZon is to maximize our architecture end-to-end. We have many approaches to make architectural drawings and to try and link these to our CMDB, and our architecture was a bit of a mess. So what we try to do here is to get rid of Draw.io, to get rid of creating in Excel and Word and Visio, and to try and put everything into one tool, to have our whole business capabilities shown in one place where I can click and I can open up and I can see the integrations, and I can see which applications are connected to each other. I can see what integrations are connected, what they are doing, who owns them, who's responsible, when the next update is available, etc. So for me, everything is in one place instead of being on SharePoint and in 100 different places.

We have daily meetings within the business to understand how things are working; when we bring a new project out or have a new application, I need to document that application. I need to understand who is using it, who is owning it, who is responsible for any changes, and what the integrations within that application are. Here, I can draw a box, I can put a user, an endpoint within that box, I can put the data object; for example, an application like Workday has finance, procurement, and an HCM module. I can break down the specific domains and objects within that application and then help to build that application outwards. If someone logs in and doesn't know the application, they can make one click to open another screen or click on that integration, which tells them all the information about that integration. Everything is in one place, linked to our CMDB, which contains all information about who owns it, who is the business manager responsible for it, who is the support team, and everything is there, including when it should be end of life or when it needs an upgrade or how much it costs and how much the licenses are. Everything is in one place, making our life within the business a lot easier without having to go to multiple departments and worrying about people on vacation.

View full review »

My main use case for BiZZdesign HoriZZon is setting up and implementing the platform together with Enterprise Studio and laying down the blueprint for how to conduct enterprise architecture with different customers.

A specific example of how I implemented BiZZdesign HoriZZon for a customer is my work with DSB, where I set up BiZZdesign HoriZZon for building an enterprise architecture repository for the transition program between the Danish rail infrastructure company called BaneDanmark and DSB.

I have worked with BiZZdesign HoriZZon for multiple customers, and one project I would like to highlight is what we did with Maersk Line. That was a huge investment from Maersk Line about eight or nine years ago, and it provided huge benefits as they advanced their enterprise architecture.

View full review »

We usually go for ArchiMate, and using that language, we do the business process engineering. We also create a capability map and heat map there. We also do the application portfolio management there.

The business process one is the most important one because in one of my last experiences, we had more than 700 business processes and we need to optimize them as time passes because they become obsolete. Highlighting the current flows, and then creating the target flows, and then having the discrepancies highlighted, and then the removal of those discrepancies by minimizing the hops of APIs is critical. In that sense, BiZZdesign HoriZZon really helped us a lot.

View full review »

I am in charge of the application portfolio of the HR department, so I use BiZZdesign HoriZZon every day to check and get details about applications. I have many use cases, and I use it on a daily basis. It is not just one use case, but rather many use cases, and it is truly a tool that is very important and relevant for my role.

View full review »

BiZZdesign HoriZZon is primarily used as a repository for Enterprise Architecture and is also utilized in broad portfolio management including project management and other applications, but the main focus is on implementing the EA and running the ADM using the tool.

View full review »

My main use case for BiZZdesign HoriZZon is enterprise architecture and solution architecture.

A quick specific example of how I use it for enterprise or solution architecture is creating an overview of processes using business process notation language.

I also handle showing what technology is used in doing business processes and the supporting technology, and seeing the consequences of technology choices coming ahead, such as integrations, typical data we need to have available, and the quality of data and so forth.

View full review »

My main use case for BiZZdesign HoriZZon is for enterprise architecture and capability mapping.

View full review »

My main use case for BiZZdesign HoriZZon is to edit the meta-model, and I am able to model epics on this design.

A quick specific example of how I use it to analyze epics or edit the meta-model is the recent work on the meta-model for the technical layer, and I use it to publish.

View full review »

My main use case for BiZZdesign HoriZZon is to architect most of our ERP integrations, which includes all the business-to-business connections, transformations, and automations included. This maps out the entire ERP architecture.

Within our organization, BiZZdesign HoriZZon is particularly useful for creating a connected view of a large and complex technology landscape, as we operate across multiple business functions and use a combination of SAP and non-SAP applications, different integration platforms, APIs, and messaging systems. Without an architecture platform, this creates an information matrix that can easily become fragmented across spreadsheets, presentations, and technical documentations. BiZZdesign HoriZZon has helped us keep all of that in one place. For example, when assessing the future of SAP PO integrations, we need to understand how much more the number of interfaces can be in the future architecture. We need visibility into the business process supported by each integration, the source and the target applications, communication protocols, criticality, dependencies, ownership, and downstream impact. BiZZdesign HoriZZon helps connect these different architecture layers and allows us to relate business capabilities and processes to applications, integrations, and underlying technologies. This makes it easier to understand how a technical change could affect an actual business operation, such as procurement, finance, HR, manufacturing, or logistics.

Another valuable use case is impact analysis, where before changing or retiring an application or middleware component, it is really important to assess what all systems it is actually affecting when you take it out. This reduces the risk of overlooking indirect dependencies, so we have used BiZZdesign HoriZZon to understand what all downstream systems will be impacted.

View full review »

My main use of BiZZdesign HoriZZon in my organization is for enterprise architecture and transformation management as an information systems urban planner.

As an example of how I use this tool as part of my missions as an information systems urban planner, I engage in transformation management, transformation modeling, and mapping in the context of changing a CRM tool, managing obsolescence, and moving to the cloud, particularly with Salesforce.

Regarding my use of BiZZdesign HoriZZon in this context, I would add that it facilitates strategic alignment with the portfolio and execution which is easy to use.

View full review »

BiZZdesign HoriZZon is primarily used for enterprise architecture processes. My clients mostly use it for architecture modeling and planning.

View full review »

The typical use case with BiZZdesign HoriZZon is basically for enterprise architecture and also for business process modeling.

View full review »

I use the solution in my company for all sorts of things, like enterprise and solution architecture. As part of our design process, BiZZdesign HoriZZon is used for road mapping. We also use it for project governance, so all the project designs we do are subject to governance and are done using BiZZdesign. THe quality data from Bizzdesign is then fed into our CMDB, in order to keep the data synchronised across the two tools. We also import operational data from the CMDB back into Bizzdesign, and use this to enable us to check that the required changes to the CMDB have been carried out correctly.

View full review »

Our clients deal directly with BiZZdesign. They use it, but what we do is we have some experts who have hands-on experience, and we use that knowledge to implement solutions for them. We don't use any separate licenses for HoriZZon ourselves.

View full review »

I used BiZZdesign HoriZZon at two organizations. At Manchester Metropolitan University, I used it with a small team for architectural modeling of the student record system. We modeled teams, process objects, and their interactions with applications. We also used it to model a gradual rollout with plateaus showing migration over time. At the BBC, I used it to model software services for publishing content online. I showed key model views to senior stakeholders using Horizon, allowing them to modify and score applications and services.

View full review »

I've used the solution for business architecture.

View full review »

We use it primarily for architecture and capability-based modelling. We plan to use it more as an analysis rather than a modelling tool.

View full review »

We use it as our enterprise architecture tool, for keeping our enterprise architecture documentation. That not only includes infrastructure components but everything else as well. For example, what are the different components that we have, enterprise-wide? What are the technologies being used? What are the technology services being used? Who are the business actors and what are the business departments? What are the business capabilities that we have in the organization? We keep everything in BiZZdesign. 

We are also using the tool for architecture governance and the gating process, and all the different business-view needs. Whenever they're implementing any application, they document the solution architecture of that application in BiZZdesign. It then goes through our weekly governance process in front of our architecture review board. Based on the documentation quality and on certain standards, we evaluate whether this application is fit for implementation. If not, we provide feedback: what the corrections are that need to be done. Once again it goes through that feedback process and, once approved by all the relevant stakeholders, the application is ready for implementation.

There are certain applications that are transformation-type projects. We use BiZZdesign Enterprise Studio to document the current architecture, the transition architecture, the future architecture, as well as the network, monitoring, infrastructure, and security views. These are the things that we usually cover as part of the governance process.

It is running on AWS cloud. We don't use the desktop version.

View full review »

We are thinking of making BiZZdesign as a single source of truth for the entire American Century organization. We have found out a lot of information through their enterprise architect, scattered here and there, and it is very difficult to track. Our aim is to consolidate all the information and do something with that data/information, where meaningful insight can be extracted and presented to the executive level and other departments at American Century.

People have created many artifacts or system architecture diagrams for different American Century systems. These are now scattered here and there. We are currently working to load the architecture diagrams into BiZZdesign, which can't just be copied and pasted because of PPT. The way things do not work exactly in the same way with HoriZZon. So, we are redrawing all those artifacts and putting them systematically into the BiZZdesign system. This is the use case that I have been working on for the last month and a half to two months. Two people besides me are working on this.

View full review »

We use it for enterprise architecture information, with the main purpose today being to analyze our IT investment portfolio and the architecture related to it. That includes process, data, applications, and infrastructure. We collect all of that information by each of our initiatives or projects and we analyze it there. It gives us a single source of data.

We're using the latest cloud version.

View full review »

We use this solution to publish our customers' enterprise models.

View full review »

Our customers' primary use cases include application portfolio, information, and data architecture.

View full review »

Our primary use case of this solution is for enterprise architecture diagrams. We are working with ArchiMate and we have several hundred diagrams for specific purposes, like current state architecture, future state architecture, capability maps, and road maps. 

View full review »

Our primary use for this solution was architecture modeling and ArchiMate. We have now switched and are no longer using this solution.

It was deployed on-premises.

View full review »

My primary use cases are for consulting on enterprise architecture and support of digital transformation, and I also use BiZZdesign as a tool.

View full review »