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?
There will be more information as this feature approaches commercial release.
It is worth saying at this point that One Configuration is an optional feature that will be enabled by configuration, aimed at experienced admins in larger organizations who use multiple products and have to work with multiple sets of client standards.
Marc
Update 16 has been released, and I have it installed.
The installation created a new empty folder
and there is a new post here which is a very basic overview.
https://communities.bentley.com/products/microstation/b/microstation_blog/posts/new-in-microstation-connect-edition-update-16---one-configuration
I can find nothing else related to One Configuration in the documentation, or on the Bentley website.
As someone who manages a lot of configurations from different clients and different products I have a high level of interest in setting this up to see how it works.
Rod WingSenior Systems Analyst
In that article it mentions:
The main drawback of the configurations delivered in the previous updates of MicroStation is that all the products try to utilize the same WorkSpace and WorkSet.
How is this a drawback ? Isn't that the intent ?
Timothy Hickman
CADD Manager | CADD Department
timothy.hickman@colliersengineering.com
Main: 877 627 3772|
1000 Waterview Drive Suite 201 | Hamilton, New Jersey 08691
Thank you Tim, I've amended that paragraph as follows:
"Difficulties arise when different products, that are delivered with discipline specific datasets and configurations, try to utilize the same WorkSpace and WorkSet standards folders that may not provide the correct resources or configuration to each product."
Note that this is the stepping off point. The other products now have to carry out the work needed to align their configurations and datasets with OneConfiguration. However, those with sufficient configuration expertise should be able to make use of what has been done so far.
We have added a number of variables to msconfig.cfg to enable more granular control of configuration flow and resources based on product that can be used to specify paths by product:
_USTN_PRODUCT_ONE_GROUPNAME:$(_ENGINENAME)_USTN_PRODUCT_ONE_SUBGROUPNAME:$(_ENGINENAME)
There is also _USTN_PRODUCT_ONE_NAME, but it looks like we may not need that one, so it could be removed in a subsequent release.
More documentation on this will follow in due course.
I don't necessarily believe this is true. While you state "Difficulties arise when different products" try to utilize the same workspace/workset - I believe it is more like - Difficulties arise when "certain" products try to utilize the same workspace/workset.
and when I say this I mean the Building and Plant products.
All my civil products work just fine using the same workspaces and worksets, along with MicroStation.
So rather than change the products having difficulties, the decision was made to change the whole configuration.
It is stated that this will not disrupt my current configuration, but I am sure it will.
Has there been any thoughts on how Bentley is going to handle versioning of discipline specific datasets going forward ?
Possibly: _USTN_PRODUCT_ONE_GROUPNAME:$(_ENGINENAME)$(VERSION#) , _USTN_PRODUCT_ONE_SUBGROUPNAME:$(_ENGINENAME)$(VERSION#)
Hi Tim,
This is all optional. New variables have been added but One Configuraton is not enabled by default.
Marc Thomas said:However, those with sufficient configuration expertise should be able to make use of what has been done so far.
I've looked over the updated msconfig.cfg files and the new variable definitions. Unless I'm missing something, this really doesn't help those of us with "sufficient configuration expertise" as we already have our own structure in place that does the same thing.
I don't know what I was expecting, but it wasn't this.