Overview

ENOVIA Team BOM Editor (TBE) provides a solution to a multi-industry need for designer-oriented products, which specifically address early product development and working BOM requirements versus enterprise / production requirements. TBE allows VPM users to work with parts and assemblies in a development bill of materials.

A bill of materials (BOM) is a list of all subassemblies, parts, raw materials and respective quantities that comprise a parent assembly, describing the product structure of the manufactured item. TBE enables easy editing of part structures and provides capabilities for efficient maintenance of BOMs.

TBE provides the following capabilities:


  • Authoring
    • Development Part Management
    • Development/Working EBOM Management
    • Development Change for Working EBOM
    • Synchronization of Working EBOM to VPM/DEC
    • Add existing Document/CAD Model documents
    • Part classification to existing part families (from Library Central)
  • Reporting
    • Part Where Used
    • EBOM Reports: Multi Level, As Stored, Latest, Consolidated, Compare
    • 3D Visualization of Part / EBOM

Before Reading This Guide

All ENOVIA products install common components that are shared, providing consistency of features across all applications. Common features allow the products to manage information such as user and company profiles, documents, and routes, based on company roles rather than on the application used. These are described in the Common Components User's Guide as well as in Common Components Help.

Other common features are provided by the framework. These include IconMail, generic searching, collections, and preferences and are described in the Application Exchange Framework User's Guide and AEF Help.

Getting Help

You can get help on the page you are working with by clicking on the page. A separate help window will appear that displays the help topic for the page along with a navigable table of contents for the user guide.

Role Mapping

TBE roles have certain access permissions. Some VPM roles inherit specific TBE roles so they can share those permissions. The inherited VPM roles are added to the Development Part policy states with project and organization filters. The existing filter mechanism is used from the VPM product policy VPLM_SMB_Definition. For details, see the ENOVIA Rapid Application Configured Environment (RACE) for VPM Guide.

Team Environment Role Hierarchy:

Global User, Project User
 

VPLM Matrix User
   

VPLMViewer
     

VPLMExperimenter
       

VPLMCreator (self-created data in the project)
         

VPLMProjectLeader (views project-specific data)
           

VPLMProjectAdministrator (views organization data)

Image Column Support in Team BOM Editor

The Image column/field is shown in the BOM PowerView, part search results, and part Properties pages in TBE when DEC or VPM is installed.

After thumbnail generation in VPM Navigator, when you sync the part to TBE, all the created thumbnails are copied to the the parts. You can click the image to open the Image Manager page, where you can view and upload the images. See Images Page.