370 likes | 494 Views
D&C Manager Quantities. Chris Collins. Generating Quantities in Design & Computation Manager. Display settings Design settings Compute settings Computation units Creating DDB items for computing Generating plan quantities Output options for quantities
E N D
D&C Manager Quantities Chris Collins
Generating Quantities in Design & Computation Manager • Display settings • Design settings • Compute settings • Computation units • Creating DDB items for computing • Generating plan quantities • Output options for quantities • Reviewing the quantities in Quantity Manager
Display GEOPAK Attributes Configuration Variable: GPK_ACCUSNAP_IDENTIFY_ELEMENTS_AUTOMATICALLY = 1 Displays GEOPAK attributes when mousing over an element. This behavior is enabled by default if AccuSnap’sIdentify ElementsAutomatically is turned on.
Enhance Display Options in MS v8i • Apply priority and transparency to levels to enhance the display of elements in MicroStation. This is a great visual aid for quantities.
Display Settings • One color display shows everything that is not the selected items in one color in the view. • Highlight in computation displays all selected items in the design file highlight color. • These options do not work with the view attribute level overrides on.
Design Settings • Maximum Gap Tolerance defines the distance used to determine if two elements are a continuation of the same element or separate instances of the same item. • DeductionTolerance is used when computing quantities with deductions. The measurement is based on the cell origin. For example inlets within the range of curb. gap
Compute Settings • These settings are applied during the computation process and impact the resulting output. • Baseline Chain Reference • CSV Export Properties • DBMS Properties • Project Specific Supplemental Descriptions.
Compute Settings – Baseline Chain Reference When quantities are computed only a single baseline can be referenced in the plan quantity computation dialog. If an Adhoc Attribute Name is assigned in this field, and an adhoc with this name and the corresponding chain is attached to elements, this chain will be referenced during computation for those elements. Ex: ramps or side streets.
Compute Settings – DBMS Properties • Driver – Supported databases are Access, Oracle and SQL Server. • Purge Quantities - if an element is deleted, GEOPAK does not delete the quantity unless this option is toggled on. • Update Quantities for Designated Phase Only – When toggled on an element appears in only the selected phase. • Create Adhoc Attribute Table - When toggled on, adhocs attached to computed elements are stored in the adhoc table in the QM database. DBMS Properties are applied when exporting to QM.
Compute Settings – Project Specific Supplemental Descriptions By default, multiple items with the same name are summed into a single quantity when computed and exported to QM. Supplemental descriptions allow multiple items with the same name to be treated as separate items during quantity computation. Ex: Item = "123-456" Description = "Removal {Conc.}" Item = "123-456" Description = "Removal {Pavt}" The two items above are separate items, with the same item ID. The description is composed of two parts: a "general" description and a "supplemental" description.
Computation Units • A standard unit file is supplied for both English and Metric. The unit definitions are stored in CSV files contained in the product installation folder. • The file names are: ComputationUnitDefinitionEnglish.csv ComputationUnitDefinitionMetric.csv. • If additional units are needed, these files can be modified to add custom units. Note: These files can reside anywhere and be pointed to by the variable: GPK_COMPUTATION_ENGLISH_UNIT_DEF_FILE
Creating Custom Units • Example: Bale is a custom unit for measuring hay bales based on a 3’ increment measured along the length of the element. • There are several intrinsic variables. • A unit equation can also reference an adhoc.
Item Preferences For an element to compute, it must match the search criteria for the item, this includes the symbology, the attribute information and the supplemental search criteria. If it meets this evaluation then it is quantified according to the item’s compute parameters.
Item Preferences – Attaching Adhocs • Adhocs can be placed on elements to be used during computation. • This allows the user to modify the variable and the value is maintained with the element.
Compute Parameters There are 4 compute options: • Standard Unit • Criteria File • Example:LF = typeF.x The left side prefix "LF" will be used for this pay item when exporting to Comp Book. • Equation • Example: (0.75*(element_area/9)) • Adhoc Attribute Note: adhocs can be used in all 4 computation options.
Using Adhocs in Equations • Adhocs can be attached to elements and then used to compute the quantities. • Ex: a tonnage item can have adhocs attached to the elements to define thickness and weight. These values are then used when the element is computed via an equation or standard unit. • The benefit to using the equation option is that the computation method is defined as part of the database and not referenced from an external file.
Computing by Adhocs Or… the computed quantity can be attached to the element and the compute parameters defined as Adhoc Attributes.
Defining Adhoc for Quantities • An adhoc requires 3 pieces of information for each adhoc: • Name - An identifier. • Type - Defines the nature of the information. • The options are: Numeric, String, Unit, Quantity, and Remarks. • Value – What the name equates to. The value is restricted by the Type. For example, if the Type is set to Numeric then the Value must be a number. • To set up a predefined quantities using adhocs, 1 to 3 adhocs are needed per item: Unit, String (for description) and Quantity.
Plan Quantity Computations • The Extents option determines which elements are included in the set. Range and defined station limits also affects the selection. If Range and/or station limits are defined, then the constraints for both must be met for the element to be computed. • There are 8 options for the “Extents” in which the quantities are computed. Each of these are then applied according to the limitation of inside, overlap or clip.
Computing Quantities - Extents • Active Design File - all selected items in the current file. • View - the selected items that are visible in the MicroStation view. • Fence - All items which are inside the fence. • Boundary Element - All selected items contained in a selected Boundary Element. • Station Range - All selected items within a selected Station Range. • Sheet Range - All selected items in a selected Plan Sheet Clip Boundary. • Selection Set - All selected items in a MicroStation Selection Set. • Boundary Selection Set - All selected items within a selected boundary element and a Selection Set.
Computing Quantities for Adhocs with Clip When adhocs are used to calculate the quantity of an element, the adhoc represents the entire quantity. If the element is clipped by sheet, fence or boundary mode when computing, D&C Manager will modify the expression by inserting a clip multiplication factor. Ex: if 75% of an element is used in the compute boundary, the expression will be modified to reflect this. If calculating an area the equation would be modified as: {element_area} * {clip factor = 0.75}
Computation Results – Export Format The generated quantities are displayed in the computation results dialog. Several export format options are available: • Comp Book • Item Report • Item Table • DBMS • CSV By Item • CSV By Element • Table The dialog box changes dynamically according to the selected export format.
Computation Results – Export Format CSV • The information exported to the CSV file is defined by a column definition style. This format can be saved and defined as standard by a configuration variable.
Computation Results – Export Format Table • This option creates a quantity summary table in the design file. • The text parameters can be defined and saved to a file for future use. • The file can be automatically selected via a configuration variable.
Computed Quantities – Export Format DBMS • The DBMS format is used to export the quantities to database formatted for Quantity Manager. When this option is selected the user has two additional information fields; Run and Phase. • In addition the Project information can be added by toggling on the Advance Project Settings icon.
Quantity Content • This includes the computation method, boundary definition and adhoc information.
Boundary Properties • In addition to grouping quantities by phases, quantities can now be grouped by a “boundary”. • This is normally defined when computing quantities in the D&C Manager. Whenever sheet, fence, station range, view, or boundary element is used as the “extents” this boundary information is now maintained passed to Quantity Manager.
Quantity Properties - Adhocs • Adhoc attributes can be added to quantities generated by D&C Manager or manually entered quantities. • Adhoc attributes can be used to store information for reports.
Graphic Viewer The quantities can be graphically reviewed by selecting the pay item and/or specific quantities then activating the Graphic viewer from the tools menu. Available via the Tools > Graphic Viewer pulldown.
Creating Quantity Reports There are many sample reports delivered with QM.
QM Reports Report formats: • PDF • HTML • CSV • Text
Contact Information • Esther Barwick • Email: esther.barwick@bentley.com • Phone #: 850-942-0603