Autodesk Inventor OEM. With Inventor OEM, developers have access to the same API supported by Inventor. Unlike the add-in approach, which extends Inventor, Inventor OEM allows developers to create their own branded products based on Inventor. Branded products present their own identity while at the same time being completely compatible with other Inventor applications.
Autodesk views Inventor OEM as a means to further extend Inventor technology into new markets and industries. Inventor OEM can be used as a platform by independent developers to create products to address unique market needs or respond to niche opportunities. The only limitations on applications that Inventor OEM cannot be used for are:
- pure data translation applications (applications that convert from one format to another), andapplications that emulate and therefore compete directly with Autodesk Inventor.
- Other than that, the range of applications that could be developed is pretty much only limited by imagination and ambition.
In building their branded product, developers can use part, assembly or drawing level functionality (assembly requires part, drawing requires assembly). Inventor’s extensive range of translators can also be included allowing data to be read into the branded application in a wide variety of proprietary and industry standard formats. The BIM Exchange and iLogic add-ins can also be included.
A key part of the Inventor OEM technology is the Configuration Wizard which allows customization of the branded application’s configuration. Aspects of the branded application which can be customized are: the splash screen and zero doc images, the application icon, and the various application ribbons. Through customization, the resulting application can be specifically tailored. Using the Configuration Wizard converting an existing Inventor add-in into a branded product is a fairly straightforward process.
- Full local install of Microsoft® Excel 2010, 2013 or 2016 for iFeatures, iParts, iAssemblies, Global BOM, Parts Lists, Revision Tables, spreadsheet-driven designs and Studio animation of Positional Representations.
- 64-bit Microsoft Office is required to export Access 2007, dBase IV, Text and CSV formats.
- Office 365 subscribers must ensure they have a local installation of Microsoft Excel 2016.
- Windows Excel Starter®, OpenOffice®, and browser-based Office 365 applications are not supported.