MBOM in traditional data model

I would appreciate the opinion of experienced 3DEXPERIENCE/ENOVIA users.

We are using 3DEXPERIENCE R2022x HF11 (on-premise) with the classic Engineering model (CAD + Part + EBOM), not the newer Engineering Item / Model-Based approach.

Our environment includes the Manufacturing BOM Management Foundation module, and we also have the Manufacturing BOM Manager (MBO) license.

Our implementation partner claims that although the classic MBOM functionality still exists, it has been significantly limited, with some commands disabled, and that it is kept mainly for backward compatibility. They recommend migrating to the Model-Based architecture before implementing MBOM.

My question is:

Can the classic architecture in R2022x still be used to fully manage MBOM in a production environment?

By "fully manage MBOM," I mean capabilities such as:

  • Creating and maintaining MBOMs
  • Defining and modifying manufacturing structures
  • Reorganizing components (merge, split, reorder, etc.)
  • Managing EBOM-to-MBOM relationships
  • Supporting engineering changes
  • Maintaining manufacturing-specific views and structures for ERP integration

I understand that some of the latest DELMIA Process Planning and Manufacturing Item capabilities are available only in the newer Model-Based architecture. My question is specifically whether the classic Part/EBOM-based approach is still a practical and complete solution for MBOM management in R2022x, or whether there are functional limitations that make migration effectively necessary.

I would especially appreciate feedback from anyone who has implemented or maintained MBOM on the classic architecture in R2022x or a similar release.