About OnePart

Introduces the OnePart application and its terminology.

This page discusses:

What is OnePart?

OnePart is a Discovery Application built on the industry-leading, scalable SBA infrastructure and search engine, Exalead CloudView. This is a crucial concept to understand as you read this guide. Many of the statements which follow make reference to the Exalead CloudView technology which forms the basis of OnePart. Other statements refer to OnePart when describing elements specific to the OnePart application.

OnePart is used by design, engineering and manufacturing teams to find and reuse:

  • legacy parts,
  • 2D/3D designs, and
  • related documentation contained in CAD and file systems from across the enterprise.

The following screenshot illustrates the main features of OnePart.

If we search for the string “handle”, it returns the relevant parts in the search results. You can sort the search results by relevance, file name, most recent, or popularity.

For more details, see the Design features in the OnePart User's Guide.



The * indicates features only available in the OnePart standalone version.

How does it work?

OnePart locates, converts, and displays legacy parts & design data from selected source systems (Files, PDM, etc.), while integrating with existing workflow management solutions.



After installing OnePart, you can add your sources using the OnePart Console.

Note: Certain connectors must be configured using the Exalead CloudView Administration Console.

To start installing now, see Before you begin installing.

What connectors are available for OnePart?

OnePart has several standard connectors plus other optional purchased connectors.

  • Standard connectors - no extra license required:
    • Filesystems
    • XML
    • Database
    • CSV
    • HTTP
    • IMAP
    • LDAP
  • Optional connectors (for complete details, see the Optional connectors in the OnePart Connectors Guide):
    • Autodesk Vault
    • ENOVIA ER for 3DEXPERIENCE
    • ENOVIA SmarTeam
    • ENOVIA VPM V5
    • ENOVIA V6 Designer Central
    • ENOVIA V6 / 3DEXPERIENCE
    • Oracle Agile PLM
    • SolidWorks PDM + Web API

What formats are supported?

OnePart supports many file formats.

For complete details, see: the Supported File Formats in OnePart Reference Guide.

How to access OnePart?

All the entry points for OnePart are web-based: using a web browser such as Internet Explorer, Chrome or Firefox.

Make sure to replace "host" in the URLs below by the actual name of the server on which OnePart is installed.

For end-users

OnePart UI: the application used to search for parts. To access, go to http://host:10000

For administrators

OnePart Console is the recommended user interface for configuring data sources and importing your content. This console can be used in most cases needs except for connector scheduling and advanced configuration. As this is an alpha feature, the console does not support all of the currently supported OnePart connectors. Here you can also customize the OnePart login page with your company logo.

  • You must have OnePart Administrator rights to access the OnePart Console.
  • Go to the OnePart UI at http://host:10000, and then from the user menu (in the upper right), select OnePart Console.

OnePart Terminology

Below is a list of important terms used in this documentation.

OnePart Console is the recommended user interface for configuring data sources and importing your content. You must have OnePart Administrator rights to access the OnePart Console.

  • Go to the OnePart UI at http://<ONEPART_SERVERNAME>:<BASEPORT>

    For example, http://host:10000

  • Select OnePart Console from the user menu (in the upper right).
  • Log in with the user app-admin and password exalead.

CloudView Administration Console is the main interface for configuring data sources, indexing options and search processes in the Exalead CloudView platform on the which the OnePart application is built. To access:

  • Go to the product’s BASEPORT + 1

    For example, if the installation is at http://host:10000, admin will be at http://host:10001/admin.

  • Log in with the user app-admin and password exalead.

Corpus refers to the collection of documents, coming from one or several data sources that needs to be indexed.

The Data Model defines how documents are stored in the Exalead CloudView index. It provides a way to map the relevant document metas available in your corpus to specific properties grouped by classes. The data model defines how data will be stored in the index, and how it will be used at search time.

Documents can be defined as all the objects to be indexed by Exalead CloudView, regardless of file or entity type in the data source. For example, HTML, JPG or CSV files, database records are all considered documents within Exalead CloudView, since they are all converted into a Exalead CloudView-specific document format (also known as a PAPI document) after being scanned by a connector.

Items are the objects to be indexed by Exalead CloudView, regardless of file or entity type in the data source. For example, in OnePart, 3D CAD files, JPGs, PDFs are all considered items in the index.

Facets are used to narrow search results. Use them to drill-down into an area, such as language, author, or file type. They are typically used in dashboard analytics widgets, or in the Refinements panel for enterprise search.

Index is an efficient structure used by Exalead CloudView to store information about the items it has analyzed. When users issue search queries, Exalead CloudView quickly and easily finds the results within this structure.

Queries are the search requests sent to the Exalead CloudView search engine and processed according to a specified search logic.

Security in Exalead CloudView has different levels:

  • Document-level security ensures that documents which users are authorized to view are displayed as search results from the Exalead CloudView index.

    • Application-level security ensures a restricted access to features in the Administration Console and Business Console.

    • App security allows administrators to define a set of cumulative rules for groups of users, instead of relying on standard document ACLs for determining whether a given user has the right to see a specific document.
  • Parent/Children relationships are more severely constrained in OnePart than in the authoring software. In some cases, authoring software (such as SolidWorks or CATIA) may reconstruct children links where OnePart shows "unknown" children.