Currently the software is available on Windows version only.
We require minimum Windows Vista or later version, the RAM memory of 2GB is sufficient to use this software but we recomment 4GB of RAM
The easiest way we recommend is to take a component that is been machined on the shop floor start estimating the Cycle time and compare them. Highlight the area of differences like Safe Distance, Speed Feed, Machining Strategy and then again input the differences in VRiddhi and calculate the cycle time. if you do it for 4 to 5 components you yourself will come up with the accuracy of the software.
The difference of cycle time can be adjusted in the Mark-up of the setup, you will have to set a bandwidth of variation and start lowering the bandwidth.
We have prepared various videos on Costing Methodology and CRUD once you understand this then its just selecting the machining sequences. As mentioned the person needs to have a basic knowledge of machining, rest all is fill in the blanks kind of activity.
If you understand the Costing Methodology and CRUD then 2 days are just enough for you to start using the software to its fullest.
We strongly recommend you to watch all the videos even before downloading the trial version and going ahead with trials.
We provide training to new users and ensure they can use VRiddhi to the fullest.
One License is just sufficient unless you have to quote over 50 components per day.
We have a Solo and a multi user version too. if most of your components are 3D then you can do multi axis machining estimation in minutes.
You can share the VRiddhi over LAN is you have inhouse windows server or install it on a DaaS network some of our customers are using basic desktop connected to internet and sharing VRiddhi using winflector.
For 3D files you can use our Automated Feature recognition feature, the algorithm are designed such that it works like we do the programming using CAM but its much faster.
With CAM you will have to select feature, tools provide speed feed and toolpath strategy etc this is already incorporated in our algorithm concept.
Some of our user information suggests that with our software their estimation time is reduced to almost by 85%.
But if your choice is to use a CAM package its also fine.
There has been huge developments in tooling technology it becomes practically impossible to incorporate all the tooling information.
The Speed feed data provided by tool OEM is very rarely used by us so just dumping the OEM Speed Feed data is not going to help.
You will have to build your own tooling database information from the shopfloor, by this way you can reduce the bandwidth of the inaccuracies in estimation.
The speed feed selections also changes depending on the work and tool holding condition and machine capacity. At the end of the day your estimation should match the shop floor timings so use the data that is used on your shop floor.
You get total Fully Functional Trial of 14 days, like a calculator has a fixed working all the proprietary formula works identically the same. During this trial period if you feel the software does not meet your needs you need not subscribe it.
We do not restrict you on the number of PC you can install the Trial version on. So if you want to have more trials you can use a different PC or ask for an demo period extension
Try it before you decide to subscribe it.
The key factor is database, if your database is corrupted you will end up building the whole thing again.
We provide automatic backup for VRiddhi at 2 locations you can reinstall VRiddhi back
We also provide automated disk transfer and PC transfer functions with VRiddhi you can use the same if your system is corrupted.
We did our honest effort to bring everything we knew in this software, we too are eager to include everything that falls under machining in to this software, if something is missed out bring it to our notice and we will incorporate it in next version, after all this is the first roll out of VRiddhi and we are going to go along a long way.
We have tried our best to incorporate all the basic machining features but there have been our limitations too.
VRiddhi is good for 2D and 2.5D estimation for continues 3 and 3+ axis we are not ready at the moment, but are working on it.
We do not work on Gears as this is a complete engineering on its own, currently we cannot include grinding in our process but we are collecting information from users and in near future we will be incorporating more features.
We dont have a SAAS version of VRiddhi as we believe that estimation contains lot of company business operational knowhow no matter how secured the infrastructure is once shared online the information is uncontrollable. Prevention is better than cure.