Folks:
I would like to know how the members are assigning multiple Item Types to a singular conduit feature definition in OpenRoads Drainage and Utilities.
Some background: We have- for instance- a single feature definition- "RCP" (Reinforced Concrete Pipe) which is tied to the Hydraulic Prototype (RCP) which is accessing the Conduit Catalog for various sizes related to this feature definition (18", 24", 30", etc.). Because we have different Pay Items that need to be assigned to different sizes of pipe- and as I have only the feature definition "RCP" which I can assign an Item Type to- how can I get the software to understand different Pay Items based upon the size of the conduit I need? I was hoping that there would be a place in the Conduit Catalog where such an Item Type could be assigned, but it does not seem to exist there. The absurd solution of creating feature definitions for each size and type of pipe comes to mind?
How are you folks handling this "issue"?
OpenRoads Designer CE - 2021 Release 2 - Version 10.10.21.04
Best Regards,
Mark
Mark,
Do you know if there are item type expressions to pull information from the catalogs or other data that you could then set up a LookUp file for your bid items? The strings that it looks up must be identical to these so if you have RCP 24" it must be RCP 24" in the LookUp table along with your bid items.
Thanks,
Erika
Erika:
I had done a bit of research into this method, and- apparently- I need to do more of it. Thanks so much for your reply!
I agree that it's no fun trying to work out the syntax that you need to retrieve information, especially from the drainage and utilities databases. This Wiki article - Video: Item Type Syntax for Nodes and Conduits - OpenRoads | OpenSite Wiki - OpenRoads | OpenSite - Bentley Communities provides the syntax for some data, and also describes how to find the syntax for anything in the drainage and utilities databases. Please note the suggestion that you keep your data as simple as possible when you do this.
We intend to have an Expression Builder in 2022 Release 1 to make this process easier.
You should be able to get the material and the size values, and do what you need from there. Depending on how your bill items work, you may also want to look at the amount of cover that a conduit has, as this is a factor in some countries.
This table is very useful. Thanks
Sorry for the late reply, Jonathan, and indeed this table is quite useful. I will be diving into the Expression Builder in 2022 R1 quite soon. The video presentation of this function is quite promising. Now, I need to make a note to set CIVILPROPERTYECEXPRESSION TO "1"; just another variable to remember!
If you have a spreadsheet with all of your pay items, descriptions, sizes, etc., you could return values from that pay items spreadsheet utitilizing the LookUp.GetEntry() expression. Might require create a couple item type properties to filter related information related to the FD, but should be worth the effort. In the June Coffee Corner for ORD, they cover item types and this look up function. Worth a look if you have the time.
Justin Guiliano, PE
Justin:
Thank you for your input. The issue is not with the item types, per se. It is with automatically assigning differing pay items to one feature definition automatically (when the conduit is placed). When I place the conduit, I have the list of conduit sizes/ pay items for a particular conduit type (RC Pipe. Metal Pipe, etc.) that I may assign (a filtered group).There does seem to be an awareness from those in the community- and Bentley- that such pay items are better assigned after placing the conduit. For nodes (or points), the LookUp.GetEntry() works as it should.
I have not yet downloaded 2022 R1, and am interested how the CIVILPROPERTYECEXPRESSION=1 may help with further developing item type expressions.