Change 23.6 Release Notes

• Auto calculate cost items – Change can now calculate adjusted values using the difference between the current budget and current estimate from InEight Control. This lets changes to the current estimate in Control to quickly populate change order values, resulting in matching CE and CB values after the change order is completed. You can recalculate the cost item based on cost, quantity, or man-hours. Read more

  The auto calculate feature subtracts the current budget from Control from the current estimate in Control to update the adjusted CB cost in Change. The recalculation uses the values from Control regardless of the updates that have been made in Change. The values previously entered in Change are replaced by values from Control.

  The Auto calculate icon has been added to the Cost item pricing page. The icon is enabled after you select an existing cost item on the Cost item pricing grid.

  

  When you click the icon, a dialog box lets you select whether to match the current budget values with the current estimate values for the cost, quantity, or man-hours, or all.

  

  After you click Apply, Change automatically uses the values from Control to recalculate the cost item. If you selected Cost or All, Change recalculates the cost categories.

  When you auto calculate a value, other values associated with the value are also adjusted. For example, if you recalculate the adjusted quantity, the unit cost changes. When you recalculate man-hours adjusted manhours, man hours per unit, unit per man-hour, and labor cost per man-hours are updated.

  If you recalculate a detail cost item, Change shows a message saying it will change the detail cost item to a plug cost item.

  

  The auto calculate feature is valid for existing cost items only. It is not valid for new cost items, dependent cost items, or markups.

• Markup calculation levels – Change now supports markups at different calculation levels in the Grand total section in both cost item pricing and the pricing summary. Change adds the value of lower level markups to the grand total to calculate the next level markup. Read more Watch video

  You can now add multiple levels of markups to the grand total. Each markup is on a separate line. In cost item pricing the tiered markups show below the grand total. In the pricing summary, the Grand subtotal line has been added to accommodate tiered markups. The cost item tiered markups are included in the grand subtotal.

  Level 0 is considered the root level. It is based on the grand total in a cost item or grand subtotal in the pricing summary. Markups to other sections are also considered level 0. Markups for subsequent levels are calculated from the subtotal plus markups from lower levels. For example, if markups in cost item pricing are 1% for level 0, 2% for level 1, and so on, and the grand total is $1000, Change calculates the values as follows:

  • Level 0: $1000 x 1% = $10

  • Level 1: $1010 x 2% = 20.20

  • level 2: 1030.20 x 3% = 30.90

  • level 3: 1061.11 x 4% = 42.44

  • level 4: 1103.55 x 5% = 55.18

  The total markups to the grand total in cost item pricing is 158.73.

  

  The various markups from cost item pricing are shown in the grand subtotal in the pricing summary. When multiple markup levels are added to the grand total in the pricing summary, they show under the grand total. Markup levels can be added to the pricing summary at the issue, PCO, and CCO levels.

  The Grand subtotal section has been added to the pricing summary to accommodate the tiered markup lines from cost item pricing. Markups made to the pricing summary now show under the grand subtotal. Previously they had been under the grand total.

  

  The Markup level has been added to the markup configuration and the Add markup dialog box (project Settings > Configurations > Pricing markup). The markup level is enabled for the Grand total section only. Markups in all other sections are level 0, and the field is disabled.

  

• Advanced template settings – You can now define template settings based on template type. Read more

  The organization-level template settings tab (Settings > Change > Change templates > Template settings) has been redesigned so that you can set the template configurations toggles for each template type. Previously, the configurations applied to all template types.

  

  Because a change document might have templates defined at the issue, PCO, and CCO levels, Change uses the following to determine which setting has precedence when there is a difference in settings:

  • If the Allow users to edit the document during generation toggle is set to No for any of the templates, Change gives precedence to that setting, and no editing is allowed for any template.

  • If the Require watermark stamp upon document generation toggle is set to Yes for any of the templates, Change gives precedence to that setting, and a watermark is required for all templates.

  • If the Output as PDF only toggle is set to Yes for any of the templates, Change gives precedence to that setting, and only PDF output is available for all templates.

• Cost item pricing pay items – You can now view pay item information in cost item pricing. The Pay item field has been added to the Details tab for existing cost items. The Pay item column also has been added to the Cost item pricing grid. Read more

  The Pay item field shows the pay item number followed by a dash and the description. For existing cost items, the field and column are read-only and are populated with the pay item from Control. When the pay item assignment changes in Control, it is automatically updated in Change after you refresh the page.

  

• PCO start date and CCO start date – The PCO start date and CCO start date fields have been added to the PCO and CCO details, respectively . You can use a start date that is different from the created date when the day work on a PCO or CCO was started is different from when the PCO or CCO was created. Read more

  For example, if work started on a PCO on Saturday, but the PCO itself was not created until Monday, you could set the PCO start date to Saturday’s date.

  When you create a new PCO or CCO, the start date defaults to the created date. If you do not want to use the created date, you can change the date to a date in the past. The date format follows the user preferences.

  

  The PCO/CCO aging days open columns on the PCO and CCO logs now use the PCO or CCO start date to calculate the aging days instead on the created date to give a more accurate count.

  The PCO start date column has been added to the PCO log, and the CCO start date has been added to the CCO log.

• Supporting documents permissions – You can now restrict users from adding, editing, or deleting supporting documents. The Add supporting documents, Edit supporting documents, and Delete supporting documents permissions have been added to the Edit Change permissions in Suite administration> Roles and Permissions > Change > View Change. Existing roles have been updated to have all three options selected if the Edit Change permission is selected. Read more

  The check box for the Delete supporting documents permission is enabled only when the Edit supporting documents permission is selected.

  

• Grand total dependent cost items – You can now add dependent cost items to the Grand total section in cost item pricing. This lets you calculate dependent costs like insurance on the total cost and markups above.

• Markup % in Issue, PDO, and CCO headers – The Margin field in the Issue, PCO, and CCO headers is now called Markup % to describe the field more accurately. Change writer tags will be updated in the next release.