> For the complete documentation index, see [llms.txt](https://help.besmart.software/erpp/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.besmart.software/erpp/system-requirements.md). # System Requirements ## General system requirements ### Be.Smart ERP Picker (add-on for Autodesk Inventor) Be.Smart ERP Picker is an add-on to Autodesk Inventor, and its system requirements are essentially the same as Autodesk Inventor. * [Autodesk Inventor 2022](https://www.autodesk.com/support/technical/article/caas/sfdcarticles/sfdcarticles/System-requirements-for-Autodesk-Inventor-2022.html) System Requirements * [Autodesk Inventor 2023](https://www.autodesk.com/support/technical/article/caas/sfdcarticles/sfdcarticles/System-requirements-for-Autodesk-Inventor-2023.html) System Requirements * [Autodesk Inventor 2024](https://www.autodesk.com/support/technical/article/caas/sfdcarticles/sfdcarticles/System-requirements-for-Autodesk-Inventor-2024.html) System Requirements It is also necessary to access the required data source (txt|csv|xlsx files, Access database, MS SQL, etc.). ### Be.Smart ERP Picker (standalone application) * Operating system Windows 7, 10, 11. * Access to the required data source (txt|csv|xlxs files, Access database, MS SQL, etc.). ## Licensing Requirements * To make sure the licensing of the ERP Picker works flawlessly, whitelist the following addresses in your firewall on port 443: * (web portal); * (services). * The website IP is 13.107.253.67, the service IP is 13.107.253.45. * Also, if multiple Holixa-licensed add-ons are to be run on the same machine (this is especially valid for job servers where Publisher4VLT and ERP Connector may run side by side), it is recommended to use a separate user (Holixa) account (e-mail) for each add-on running on the machine. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.besmart.software/erpp/system-requirements.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.