Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Show only
|
Search instead for
Did you mean:
This page has been translated for your convenience with an automatic translation service. This is not an official translation and may contain errors and inaccurate translations. Autodesk does not warrant, either expressly or implied, the accuracy, reliability or completeness of the information translated by the machine translation service and will not be liable for damages or losses caused by the trust placed in the translation service.Translate
Don't Let the Job Processor Consume an Inventor License
The job processor also pulls an Inventor license when it is processing Inventor files meaning that I can not have it running during business hours. To me there should be a method for it to update DWF files without consuming an Inventor license
Currently to use the Job Processor reliably when bumping revisions on the way to a released state you need the following requirements to be in place:
A dedicated license of Autodesk Inventor
A dedicated Vault license.
A dedicated workstation with a support GPU for Inventor
Frankly, these additional costs which amount due to the simple need of bumping revisions on the way to a Released/Locked state is ridiculous. Not to mention a nasty surprise for unwitting Vault Workgroup & Professional customers.
In New Zealand, that adds up to nearly $15,000 plus assocaited on going costs! When you have a site of 30 CAD users, you can almost swallow that. But when you have a design office of less than 5 users, it's almost impossible to justify.
Please work with the Inventor team to rectify this.... AutoCAD users aren't affected by this issue, which most certainly makes Inventor users feel like they are being ripped off.
Ideally, the job processor would just run server side. Customers already make a significant investment in Vault and generally continue to do so in various forms. Either make the JP a separate bolt on cost (which kind of already exists based on the requirement of a dedicated license for it!!), so there are no hidden costs, or make it work properly within a reasonable and transparent framework (with no additional costs).
As a reseller I am a little embarrassed to have to tell customers they need not only an additional license of vault to process jobs but also inventor, and potentially revit.
This is probably another request altogether but improving the stability and performance of the job processor too. At a customer site we have had to configure the job processor to process 1 job at a time because it falls over so frequently, the problem with this is they have 20+ users utilizing vault, changing lifecycles, submitting visualizations to queue, properties syncing and viz updates on state changes. The list grows quickly when it can only process one job at a time, and what often happens is the state changes before it can sync properties or create viz.
The only option is to tell them to setup another job processor which leads me to my second point.... Oh wait thats this post....