Setting Up Procedure (BIM Manager)

As a BIM (Building Information Modeling) manager, you can follow this procedure to conduct a set up of your Building and Civil Assemblies project using Data Setup. Data Setup allows you to put together resources and share them with all the actors in the project within one or several collaborative workspace.

To help you find the reference information you need to use the content delivered along with your app, you can consult the 3DEXPERIENCE Native Apps Content User's Guide.

This task shows you how to:

Before you begin:
  • You or your administrator must have installed the app content. For more information, see Native Apps Installation: Installing Native Apps.
  • You need to familiarize yourself with the sample files which are provided for you by default from win_b64\resources\. The files include:
    • CRS 3DXML resources
    • Geolocation Resources files
    • Building & Civil Resources
    • Building & Civil Data Exchange Resources
    • You are granted the rights to use data setup (Owner role) import and create CRS, associate the resources to a collaborative space and add extensions (Leader role).
The app optional content is not automatically installed along with the code. Contact your administrator if you must install the files you need. For more information, see Install Optional Content. You can also see Installation and Setup:Install: 3DEXPERIENCE Platform: Installing 3DEXPERIENCE Platform Services for the First Time: Installing Services One-by-One: Native Apps: Installing Native Apps: Installing a Native App.
See Also
Creating Objects with Building and Civil Types
About Types
Adding and Editing BIM Attributes

Identify and Choose the Coordinate Reference System

This section describes how to identify the CRS to be used for the collaborative space. Two situations are described in the table.

If... Procedure
you know the CRS code to be used for a collaborative space, start by searching it in the CRS 3DXML resources provided along with Building and Civil Assemblies

See Quick Start Procedure.

you know the code but could not find it in the samples or if you do not know the CRS code to be used for a collaborative space, search for it in the EPSG registry.

See Standard Procedure.

Quick Start Procedure

If you know the CRS code to be used for a collaborative space, you can start by searching it in the CRS 3DXML resources provided along with Building and Civil Assemblies.

  1. Select the EPSG-9.1.0-CRS-3dxml.zip which is located in \win_b64\resources\geolocation.
  2. Extract the .3dxml file that contains the CRS of interest. All CRS resources provided with Building and Civil Assemblies are originated from the online Epsg registry.
  3. Launch 3DEXPERIENCE using Leader role.
  4. From the Compass, click Data Setup.
  5. As a BIM manager, you are granted the Leader role and can import the CRS resource file. To do so, select Add > Import > 3D XML... and select the 3D XML file.
  6. In the Import Option area of the dialog box, ensure that Import As Ref is selected.

    Notes:
    • Alternatively, you can automatically forbid the modification of the CRS after import by using an opening ID located in resources\knowledge\scripts\GeolocationCoordinateReferenceSystem_BLAttributesMapping.CATRule. Make sure the policy and the maturity values comply with the database configuration.
    • For full instructions, see 3DEXPERIENCE Native Apps: Importing and Exporting: Importing 3D XML Files.

    The 3D XML resource file is imported into the database.
  7. Ask your Data Setup manager who is granted the Owner role to create, associate the resource table to the collaborative space, and save it.

    Alternatively, you can perform the Data Setup steps yourself. In this case, log out and log in again with the Owner role.

  8. Log out from 3DEXPERIENCE.
  9. Log in again to benefit from the Data Setup modifications. All changes made through Data Setup will be shared with all actors working in the same collaborative space.

Standard Procedure

You can search for the appropriate CRS in EPSG registry.

  1. Go to the online EPSG Geodetic Parameter Dataset registry (http://www.epsg-registry.org/)
  2. In the Type box, select Coordinate Reference System for your search.
  3. Select a type of CRS to narrow the search:
    • Projected CRS
    • Geodetic CRS
    • Vertical CRS
    • Engineering CRS
    • Compound CRS


  4. Click Show Map to determine accurately the zone of interest.
  5. Click the rectangle in the map to define a zone.

  6. Close the map.
    The coordinates values are updated accordingly:

  7. Click Search.
    The list of matching CRS is displayed.
  8. Select the required CRS code and search it in the provided CRS 3DXML resources. See Quick - Start Procedure.

Import a CRS

After identifying the required CRS for your collaborative space for geolocation purposes, you can import it with the As Reference option selected.

  1. Select the EPSG-8.5.3-CRS-3dxml.zip which is located in \win_b64\resources\geolocation
  2. Import the CRS resource file; select Add > Import > 3D XML... and select the 3D XML file.
  3. In the Import Option area of the dialog box, ensure that Import As Ref is selected.

    Note: For full instructions, see 3DEXPERIENCE Native Apps: Importing and Exporting: Importing 3D XML Files.

  4. Ask your Data Setup manager who is granted the Owner role to create, associate the resource table to the collaborative space, and save it.

    Alternatively, perform the Data Setup procedure yourself, log out and log in again as Owner.

    The CRS resource is displayed under the .

Define Geolocation Resources

You can define geolocation resources to specify administration preferences for geolocation that consist in:

  • Defining a default CRS used to geolocate new and existing objects
  • Allowing or forbidding the selection of a CRS other than the CRS defined by default.
  • Listing all objects to be geolocated at creation.

Before you begin: See Geolocation Resources
  1. Select the sample file in \win_b64\resources\standard\Geolocation.
  2. Perform the modifications according to your needs.
    • If you want to let your users change the CRS defined by default, specify No for the following property <Property Name="UseOnlyMapCRSFromDataSetup" Value="No"/>
    • If you want objects to be geolocated at creation, specify Yes. By default objects are not geolocated at creation. As an example, if you want bridge to be geolocated at creation: <BusinessObject LocateAtCreation="Yes" Name="Bridge"/>.
  3. Save the file.
  4. Reference the file in Data Setup so as it is available for all users working in the collaborative space.

Define Building & Civil Resources

Defining building & civil resources consists in specifying how property sets should be added to AEC types (building & civil objects). You can also add new sets of attributes. This is done through the edition of XML document, to determine which object types should be available at creation and/or could be edited. These objects for which you define attributes will be shared across the BIM structure around a single platform with all stakeholders. See Building & Civil Resources

  1. From the BIM section of the action bar, click BIM Manager Editor to define BIM attributes and extensions and specify base extensions. For more information, see Using the BIM Manager Editor.
  2. The modifications are taken into account and are reflected in the GUI when creating objects (Add > Content) and when editing BIM attributes by using the BIM Attributes command.
  3. Check the modifications made are accounted for. In the action bar, click BIM Attributes .
    The BIM Attributes panel appears. A list of extensions that matches the type of object is displayed. Only the listed extensions in the XML file and further defined in the table can be added and/or replaced.

Defined Building & Civil Resources in the GUI



Define Building & Civil Data Exchange Resources

You need to secure the data exchanges during export and import phases. To do so, you will define the mapping between IFC entities and AEC entities. For more information, see Format Converter for IFC Resources.

  1. Customize IFC entities mapping as explained in Mapping IFC Entities onto 3DEXPERIENCE PLM Objects.
  2. Ask your Data Setup manager who is granted the Ownerrole to create, associate the resource table to the collaborative space, and save it.

    Alternatively, if you can perform this procedure yourself, log out and log in again as Owner.

    1. From the Compass, click Social and Collaborative Apps and select Data Setup.
    2. Specify rules for the BIM extensions by attaching a Engineering document that embeds an XML file.
    3. Drag and drop the table under the dedicated collaborative space so as all users can benefit from these rules.
    4. Save.
    5. Log out and launch 3DEXPERIENCE again.

Define Visu Dynamic Assistant

Defining the visu dynamic assistant object list consists in editing the VisuAssistant_Dynamic.xml sample file located at ...\startup\EquipmentAndSystems\SpaceReferenceSystem. This document contains a set of groups that enables to organize and generate the dynamic tree nodes. The tree structure with AEC object component nodes is available by default in the Visu Assistant panel to extend further the customization. The tree structure can be defined in a dedicated resource (XML) managed in Data Setup.

  1. Open the VisuAssistant_Dynamic.xml file.
  2. Modify the XML by adding the required customized extensions. See Add Extensions for an example.
    You can hide or show these customized extensions in the Dynamic Assistant area of the Visu Assistant panel.

Add Extensions

You can create new xml files by adding customized extensions to be available at creation or in edition. Pset/Qto IFC standards are delivered along with 3DEXPERIENCE. You can extend the list of BIM attributes through the non standard Pset/Qto that are supported in Building and Civil Assemblies. To do so, create packages with the Ifc prefix and ensure that the attributes comply with the following the naming pattern: <Complete attribute name in ENOVIA> =Ifc<name of Pset/Qto in ENOVIA>_<attribute identifier>.

As an example a Pset_Flooding ENOVIA attribute whose identifier is Height should be named: IfcPset_Flooding. Similarly for a Qto, the <name of Qto in ENOVIA> is Qto_XXX (as an example: Qto_Quantity) and should be named IfcQto_XXX (IfcQto_Quantity in our example).

You should be familiar with Model Specialization Management. For more information, about adding customized extensions, see Model Specialization Management User Guide: Creating and Editing an Extension. Also see About Adding Customized Extensions.

Before you begin: You must specify ifc as package prefix. The attribute names must comply with the pattern Ifc<ExtensionName>_<AttributeID>.
  1. Launch 3DEXPERIENCE using the Owner role.
  2. From the Compass, click Social and Collaborative Apps and select Data Setup.
  3. Create a Building and Civil resource table.
  4. Specify the customized XML file for the required BIM definition.
  5. Modify the XML file:
    1. Open the AECCommonSpatialStructureElement.xml
    2. Add a new line with the extension name, for example: 
      <BusinessObject name = "AecSite">
  <BaseExtensions>
    <BaseExtension default = "true" exposed = "true" name = "IfcSite"/>
  </BaseExtensions>
  <Extension deletable = "true" level = "300" name = "IfcPset_Flooding"/>
</BusinessObject>
    3. Save the file and reference it in the Building & Civil table.
    4. Save the resource set and associate it to the relevant project.

    You can define BIM attributes and extensions and, specify base extensions with the BIM Manager Editor accessible from the BIM section of the action bar. For more information, see Using the BIM Manager Editor.

  6. Save your session.