I have found it very convenient to not have any local packages on my machine, and just load up a template file that lives on Orkestra whenever I need to create a script. This ensures that the packages that our scripts are built with are the same that the user will be running them with through Orkestra. I think the biggest thing is whenever I open the analytics tab and see that a new person is using Orkestra. Most of the people currently using our scripts have never actually been inside dynamo and I doubt many of them would be using the scripts without Orkestra.

Myself and our whole design team are very happy with Orkestra and how it functions. It is utilized everyday by different design groups from the start of projects through the end. Not sure how we functioned a few years ago without being able to seamlessly use the Dynamo scripts we have created across our design teams.

Orkestra has significantly improved our workflow by addressing many of the technology challenges we have had in the past. Our team’s user adoption of automation has also risen due to the ease of access and reliability, and gone are the days of frustrating technology issues. Our biggest firmwide improvements are in reliability due to package controls in the cloud, tracking and minimizing errors/failures, and having documentation all in one place. I am certain we would not have our current efficiencies without the Orkestra Platform and integration into our current workflows.

Dynamo Deployment, both graph and package distribution, are seamless and painstakingly easy with Orkestra. No longer do I have to track down who has what version of “xyz” package(s) or if the cause of an errored workflow is due to missing packages or knowing if everyone has the most up to date workflow. No more! All of that is easily controlled with the management fighting super power of Orkestra! Did I mention package distribution for users building workflows is done just as easily as it is with users running workflows? With the recent advancements in 1.7.1, we can now deploy code snippets! This adds that extra bit of help and support for both our senior and novice Dynamo developers having access to boiler plate node logic readily available!

You can also track analytics and marry that with PowerBI to make justifying your need for Automation and Orkestra just that much easier. Track how many times a workflow has been ran, what projects have used that workflow, who ran the workflow, how long it took to run the workflow and even associate a time savings number to each time the graph has been ran. The story you tell is easier to convey with Orkestra analytics!

With Orkestra and its recent enhancements, we’re able to afford more time and resources to our Dynamo developers to help with our push to make Dyanmo a normal part of our everyday lives as architects and engineers.

Orkestra helped a lot since the major obstacles like installation of packages and user friendliness of Dynamo were completely solved by Orkestra. All the users, despite the level of competence in Dynamo, may now use Orkestra without even knowing that there is any Dynamo behind. Which is definitely helping to gain productivity on modeling execution. Modeling in Revit got more productive because everyone now may benefit from Dynamo scripts created by smaller group of users (Dynamo developers).

I have found it very convenient to not have any local packages on my machine, and just load up a template file that lives on Orkestra whenever I need to create a script. This ensures that the packages that our scripts are built with are the same that the user will be running them with through Orkestra. I think the biggest thing is whenever I open the analytics tab and see that a new person is using Orkestra. Most of the people currently using our scripts have never actually been inside dynamo and I doubt many of them would be using the scripts without Orkestra.

Myself and our whole design team are very happy with Orkestra and how it functions. It is utilized everyday by different design groups from the start of projects through the end. Not sure how we functioned a few years ago without being able to seamlessly use the Dynamo scripts we have created across our design teams.

Orkestra has significantly improved our workflow by addressing many of the technology challenges we have had in the past. Our team’s user adoption of automation has also risen due to the ease of access and reliability, and gone are the days of frustrating technology issues. Our biggest firmwide improvements are in reliability due to package controls in the cloud, tracking and minimizing errors/failures, and having documentation all in one place. I am certain we would not have our current efficiencies without the Orkestra Platform and integration into our current workflows.

Dynamo Deployment, both graph and package distribution, are seamless and painstakingly easy with Orkestra. No longer do I have to track down who has what version of “xyz” package(s) or if the cause of an errored workflow is due to missing packages or knowing if everyone has the most up to date workflow. No more! All of that is easily controlled with the management fighting super power of Orkestra! Did I mention package distribution for users building workflows is done just as easily as it is with users running workflows? With the recent advancements in 1.7.1, we can now deploy code snippets! This adds that extra bit of help and support for both our senior and novice Dynamo developers having access to boiler plate node logic readily available!

You can also track analytics and marry that with PowerBI to make justifying your need for Automation and Orkestra just that much easier. Track how many times a workflow has been ran, what projects have used that workflow, who ran the workflow, how long it took to run the workflow and even associate a time savings number to each time the graph has been ran. The story you tell is easier to convey with Orkestra analytics!

With Orkestra and its recent enhancements, we’re able to afford more time and resources to our Dynamo developers to help with our push to make Dyanmo a normal part of our everyday lives as architects and engineers.

Orkestra helped a lot since the major obstacles like installation of packages and user friendliness of Dynamo were completely solved by Orkestra. All the users, despite the level of competence in Dynamo, may now use Orkestra without even knowing that there is any Dynamo behind. Which is definitely helping to gain productivity on modeling execution. Modeling in Revit got more productive because everyone now may benefit from Dynamo scripts created by smaller group of users (Dynamo developers).