BiZZdesign has a lot of issues with deployment. It is web-based and can get a little complicated. It had to go through multiple streams such as Amazon and Virtual PC, which makes things pretty complex. 

The initial setup was straightforward because we are using the cloud version. The part that took us slightly longer, but it was not that bad, was to ensure that our IT directory was connected to BiZZdesign. We used the same security setup that we have in the company. But that was okay.

We did the whole implementation within three months. It only took a couple of weeks to have the system running, and after that it was more up to us to decide and define how we were going to start using the tool. The tool is really open to whatever you are using in your company. So there's some work to do in defining your metamodels and what kind of data you want in it, and around how to implement or define the processes that you want around management of data.

The initial setup is quite simple but time-consuming.

I rate the initial setup an eight out of ten, and I rate the features available a five out of ten. When we were implementing the solution, the product itself was being evolved. So the implementation was not that difficult, and it was relatively easy. However, many features you would expect from an enterprise architecture tool were still missing. I think a lot of the missing features are covered now, but a lot of them are still on their roadmap.

BiZZdesign technical support was primarily involved in the setup. There were third parties involved, and the documentation provided by BiZZdesign was helpful. The deployment took about three months, and it was not complicated. A lot of the challenges were post-implementation, and not everything is mastered in BiZZdesign. At the core team, four people from our organization were involved in the deployment comprising three consultants and the account manager from BiZZdesign. In addition, there is a support organization that looks after maintenance.

HoriZZon is a cloud platform, and we need to install it for our customers due to certain regulations. Thus, an easier implementation process would definitely help. If it is on-premises, it usually takes at least two days. Two dedicated staff can handle the implementation.

Implementation was fairly complex because of constraints on resources when it comes to architects. Layers get implemented at various speeds, so there are gaps, which creates problems because the core layers are supposed to be addressed in parallel. The documentation is also not up to standard, and we would expect better support material in general.

The first time I set it up years ago, it was really difficult for me to customize it because I am more of a business guy than a technician. Now it's much easier because of the metamodel editor that this solution now has so now it's much easier. 

Deployment takes about a few days or weeks. It's easy to use and adapt it, but it's a little bit difficult to negotiate with the client in terms of what to implement, what to be modeled, what kind of methodological backgrounds will be used. 

Straight forward. You have to tune to get the best practice results out of the tool. A course is highly recommended.

The deployment took one month. 

The initial setup of this solution was very straightforward.

The deployment took perhaps half an hour when we were installing locally, and then using a file server. When we switched to a database, we needed the organizational procedures. So, this takes a little longer. Overall, it is not a problem for BiZZdesign.