MSCE Update 16 - One Configuration

The MSCE Update 16 Help document now online introduces something called One Configuration.

"You can now manage your project standards with One Configuration. You will have the flexibility to execute projects with the choice of using your organization's standards, your organization's standards in combination with your client's standards, or client-only standards. One configuration works with WorkSpaces utilizing Configuration Sets that use various combinations of standards to meet your organization's needs. These Configuration Sets can be easily adopted by other organizations that you work with."

docs.bentley.com/.../GUID-68262C6B-CCE5-4FFE-8BCC-EF0175D82D46.html

Will there be more information forthcoming about how this works?

Parents
  • Rod,

    Here's how it will ideally work:

    One Configuation:

    The variaous products will eventually establish the _USTN_PRODUCT_ONE_GROUPNAME as a  predefined variable.  These will be something like Building, Civil, Plant, Structural.  These variables can naturally group the product configuration into subfolders of the "Standards" folder at Organization, Workspace, and Workset levels.  (e.g. .\Standards\Building\, .\Standards\Civil\, .\Standards\Plant\, etc.)   New "group standards" variables and include syntax were added in Update 15 to help eliminate the need for "if engnename" statements.  The _USTN_PRODUCT_ONE_GROUPNAME:$(_ENGINENAME is only there to establish a variable if the product has not yet defined it.  This is still in the process of being adopt by the various products, but  the ground work is being laid in the update msconfig file.  You may also notice that the misconfig file has version information so that you can detect which version of the msconfig is being processed.   

    Configuration Sets:

    Configuraiton Sets are really just sets of configurations.  Think of them as "Standards that can be shared across workspaces".  Building products already do this with building dataets.  Civil does this with Organization-Civil.   One of the ideas of Configuation Sets is to have the product deliver these types of things in a more consistent manner.  Configuration Sets are extensions of workspace that are incorporated though include statements.  A Configuration Set could be a mirror of a workspace standards folders, but with specific variables.  This Configuration Set could then be included as an option in a workspace.  This then becomes an ideal way for client or agencies to deliver full sets of standards outside a workspace allowing the design firm the ability to add resources to the workspace separately from the client/agency standards.

    If you can get access to the USACE workspace, this has been configured with both the OneConfiguration and Configuration Set methodologies.  This uses a concept called OneMapping, to estabish the One Configuration variables, prior to the products actually adding them.  This allows for immediate implementations on existing product versions.  Note also that care should be taken if trying to use this technique as it is the intent that these variable be established by the products themselves (similar to the other _USTN_PRODUCT... variables) so it is not recommended at this point to create your own.

    Please note however, the we are still working on finalizing/improving this methodology.   Blogs and white paper are forthcoming.

    You may want to view my presentation at last years PW Accelerate conference.  (Session 10: Streamline Your ProjectWise Workspaces with One Configuration)

    This quickly covers both the above topics and some of the things we are doing with managed workspaces.   I am not quite sure where the link is to the recorded session, but you should be able to find it in the learn content.

    Answer Verified By: Rod Wing 

Reply
  • Rod,

    Here's how it will ideally work:

    One Configuation:

    The variaous products will eventually establish the _USTN_PRODUCT_ONE_GROUPNAME as a  predefined variable.  These will be something like Building, Civil, Plant, Structural.  These variables can naturally group the product configuration into subfolders of the "Standards" folder at Organization, Workspace, and Workset levels.  (e.g. .\Standards\Building\, .\Standards\Civil\, .\Standards\Plant\, etc.)   New "group standards" variables and include syntax were added in Update 15 to help eliminate the need for "if engnename" statements.  The _USTN_PRODUCT_ONE_GROUPNAME:$(_ENGINENAME is only there to establish a variable if the product has not yet defined it.  This is still in the process of being adopt by the various products, but  the ground work is being laid in the update msconfig file.  You may also notice that the misconfig file has version information so that you can detect which version of the msconfig is being processed.   

    Configuration Sets:

    Configuraiton Sets are really just sets of configurations.  Think of them as "Standards that can be shared across workspaces".  Building products already do this with building dataets.  Civil does this with Organization-Civil.   One of the ideas of Configuation Sets is to have the product deliver these types of things in a more consistent manner.  Configuration Sets are extensions of workspace that are incorporated though include statements.  A Configuration Set could be a mirror of a workspace standards folders, but with specific variables.  This Configuration Set could then be included as an option in a workspace.  This then becomes an ideal way for client or agencies to deliver full sets of standards outside a workspace allowing the design firm the ability to add resources to the workspace separately from the client/agency standards.

    If you can get access to the USACE workspace, this has been configured with both the OneConfiguration and Configuration Set methodologies.  This uses a concept called OneMapping, to estabish the One Configuration variables, prior to the products actually adding them.  This allows for immediate implementations on existing product versions.  Note also that care should be taken if trying to use this technique as it is the intent that these variable be established by the products themselves (similar to the other _USTN_PRODUCT... variables) so it is not recommended at this point to create your own.

    Please note however, the we are still working on finalizing/improving this methodology.   Blogs and white paper are forthcoming.

    You may want to view my presentation at last years PW Accelerate conference.  (Session 10: Streamline Your ProjectWise Workspaces with One Configuration)

    This quickly covers both the above topics and some of the things we are doing with managed workspaces.   I am not quite sure where the link is to the recorded session, but you should be able to find it in the learn content.

    Answer Verified By: Rod Wing 

Children
No Data