Change Archived Release Notes

General release is available starting 05-AUG-2024.

Updated 29-JUL-2024

• End watermark event – You can now specify the event at which a watermark is no longer required when generating a change document. You can also define template settings based on template type. Read more

  The End watermark requirement event field has been added for each template type.

  

  The field is enabled when the Require watermark stamp upon document generation toggle for a template type is set to Yes. You can then select the event that must occur before the watermark stamp is no longer required or to always require a watermark stamp.

  For Issue templates and Other templates, if the Require watermark stamp upon document generation toggle is set to Yes, only the Always required watermark event is enabled.

  For more information about setting up the watermark event, see Template settings subtab. For information about generating a document with a watermark, see Generate a change document.

• Delete issues from the Issue log – You can now delete issues from the Issue log that meet certain criteria. Issues can be deleted based on their status, PCO or CCO association, and origin. Read more

  The issue must be created in Change or added via API. The issue must have a status of New, Parked, Dropped, or a custom status. Other criteria include the following:

  • The issue cannot be associated with a PCO, CCO, or budget move

  • The issue cannot be a main issue

  • The issue cannot originate from another InEight product, such as Plan, Progress, Compliance, Contract, or Document

  The Delete icon has been added to the Issues page. You can select multiple items to delete.

  

  The permission Delete issues has been added. You must have the permission to delete issues from the Issues log.

  For more information about deleting an issue, see Issue Creation and Setup.

• Generated document name on Supporting documents register – When you generate a document from a template, and the Save in supporting documents toggle in the Generate contract wizard is set to Yes, the value in the Name of document file now shows in the Title column of the Supporting documents tab. Previously, the name of the template showed in the column. Read more

  Now, if you enter a document name, the title and the name of the file or link are the same. If you do not enter a document name, Change uses the template name. For more information about generating change documents, see Generate a change document.

• Limits on cost items and pay items in change orders and budget moves – The number of cost items and pay items are now limited in change orders and budget moves to be compatible with InEight Control. Change orders and budget moves are limited to 250 unique cost items or 100 unique pay items. For more information about limits in change orders, see Potential Change Order (PCO)and Client Change Order (CCO) Generation. For information about limits in budget moves, see Budget moves.

VIDEO | 24.5 Release Overview General release is available starting 03-JUN-2024.

Updated 28-JUN-2024

• Issue import API – You can now import issues via the Create Issues API. This new API can be used to consolidate all issues in one place by importing issues in bulk or connecting to a third- party issue creation tool. Refer to the updated API documentation for more information. For more information about importing issues, see Issue Import.

• Assign pay items to new cost items – You can now assign existing pay items to new cost items within cost item pricing. Read more Watch video

  From the Cost item pricing page Edit cost item or New cost item slide-out panel, you can select an existing pay item to assign to new cost items. This lets you see which pay items are impacted by a change before pushing the item to InEight Control.

  

  For more information about new cost items, see Cost item pricing tab.

• DocuSign Advanced Options – Change now supports DocuSign Advanced options for branding, reminders, expiration, and comments. The advanced options show in DocuSign when you are in the Sender view. Read more

  From the Sender view in DocuSign you can now go to the advanced options (Actions > Advanced Options) to access options for branding, reminders, expiration, and comments. You can see the advanced options based on your organization's DocuSign settings.

  

  • Branding options let you select a logo and brand colors that were set up by the DocuSign administrator, for the envelope.

  • Reminders options let you specify whether DocuSign sends reminders to signees, when to start sending them, and how often to send them.

  • Expiration options let you set the number of days until the envelope expires and how often to send alerts. After the envelope is expired, recipients can no longer view or sign the documents in the envelope.

  • Comments options let you allow senders and recipients to enter comments on documents in the envelope.

  Options for recipient privileges are also available. Refer to your DocuSign documentation for more information about advanced options.

  For more information about InEight DocuSign configuration, see DocuSign setup. For information about sending a document to DocuSign, see Send Change documents for eSignature via DocuSign.

• Add Request for information documents from the Issue Details page – You can now add documents to the Request for information section of the Issue Details page. Previously, you could only add documents from the Supporting documents page. Read more

  The Request for information section now includes the Add Request for information icon. You can click the Add icon to add a new document or one from InEight Document. After a document is added, it shows in the Supporting documents register.

  

  For information about the Request for information section, see Details tab.

• Open pending issues – You can now add detail information and supporting documents to pending issues while workflow is still active, so approvers can see the information they need before approving the issue. Read more

  To open the pending issue, click the Pending link in the Issue ID column of the New issue log. The Issue Details page opens, and you can then edit any field that is enabled. You can also go to the Supporting documents tab to add documents. Access to pending issues lets organizations using the new issues workflow to add additional detail before issues are accepted via the workflow. For information about issue workflow, see Issue Creation and Setup.

General release is available starting 08-APR-2024.

Updated 08-APR-2024

• Markups as values in cost item pricing – You can now add a specified value markup to a cost item. Previously, you could only add markups that were calculated as a percentage of the cost item. Read more

  The Markup value option has been added to the Add markup icon in cost item pricing.

  

  When you select the Add markup option, in the Add markup dialog box, you can specify the value of the markup and the section it is applied to. Value markups are always level 0.

  

  For more information about value markups, see Markups.

• Update temporary vendor in an executed CCO – You can now update a temporary vendor in the pricing summary after a CCO has been executed, which gives you more flexibility in the timing of selecting a permanent vendor. You can edit the vendor from the pricing summary at the issue, PCO, or CCO level. The temporary vendor in cost item pricing remains locked. For more information about editing a temporary vendor, see Edit vendor information. For more information about temporary vendors in CCOs, see Client Change Order (CCO) Execution

Updated 15-FEB-2024

• Cost item import enhancements – The cost item import process has been updated to be easier to use. The Man-hours per unit, Units per man-hour, and Labor cost per man-hour fields have been removed from the Cost item import template to prevent calculation errors in the cost item. The values for these fields are calculated upon import. Also, blank fields are now calculated based on instructions in the import files so that you do not have to enter values for every field for a successful import. For information about importing cost items, see Import cost items.

• Markup percentage update – The markup percentage configuration now allows three digits before the decimal, so you can use markups of 100% or greater. The three-digit markups apply to all levels of cost item and pricing summary markups and to dependent cost items. For information about configuring markups, see Configurations.

• Unit rate driver default for adding existing cost items – When you add an existing cost item to cost item pricing, the Unit rate driver field now defaults to Current Estimate to take advantage of the information that exists for plug and detail items. You can edit the Unit rate driver field value. For information about adding existing cost items, see Cost item pricing tab.

• Tags for Pay items Current price and Original price – The Sum of pay items original price and Sum of pay items current price tags have been added in Change. Read more

  Values for these tags are pulled from the Pay items Current price and Pay items Original price fields in InEight Control. You can use the new tags when you want to show the current or original price of a pay item that is associated to the cost item.

  For information about using template tags, see Tips for using template tags.

• Cost column subtotals on PCO and CCO logs – The total for the Cost column has been added to the footer of the PCO and CCO logs. Read more

  

  If you filter the column, the total in the footer considers only the filtered costs.

• Client custom labels – The Client custom label is now applied to correspondence fields and supporting document subtypes in all languages. Previously, the word Client in these fields did not carry the label defined for Client in the custom label settings. Read more

  The following issue Correspondence fields now use the Client custom label:

  • Date client notified

  • Date price to client

  The following supporting document type values in issues, PCOs, and CCOs now use the Client custom label:

  • Document type Correspondence, subtype Client

  • Document type Notice letter, subtype To client

  • Document type Proposal, subtype To client

• Issue log – The Issue log now loads first when navigating to Change. You can still access the New Issue Log via the associated tab.

• Workflow recall – The user that recalled a workflow is now shown in the project workflows page under workflow details. Read more

  

  For information about the document approval workflow, see Workflow Assignments.

• View locked cost item details – When a cost item is tied to an executed CCO, you can now view the details associated with that cost item. You can select the cost item, and then click Edit to view resources details and cost categories while the cost item is in a read-only state. Previously, you could not view this information after the CCO was executed. For information about executing CCOs, see Client Change Order (CCO) Execution.

In this release, no features were added, but technical improvements were made in the background to enhance your experience in Change.

• Budget move workflow – You can now send an issue budget move through approval workflow. Previously, budget moves were sent to InEight Control without approval on the Change side. Now if you are using the workflow, the budget move is not sent to Control until it has been approved in Change. Read more

  You can set up the workflow approval steps on the organization and project Settings > Workflow assignments > Budget move approval setup page.

  To start a workflow, select Submit budget move from the Actions menu in an issue. After a workflow has begun the issue is locked, and no edits can be made while the budget move is pending approval.

  You can reject or approve the budget move workflow from the email, the issue, or your action items page. If you want to make changes to the issue, you can recall the budget move from the issue page if the status is In approval. When the budget move is recalled or rejected, the issue becomes enabled.

  For more information about workflow assignments, see Workflow assignments.

  For more information about the budget move workflow, see Budget moves.

• Format large text boxes in Microsoft Word templates – You can now use Word's merge fields to format text boxes with multiple lines, such as the Description of change field, in a Word template instead of using a tag. Using a merge field ensures the text in the generated document is formatted as it is in the text field. Read more

  The merge field also lets you format the font as needed. The generated document uses the font specified in the template. Other formatting is taken from the text field.

  To use the merge fields in existing templates, you must delete the tag and then insert the merge field. You can then save the template as a new version.

  For an overview of formatting large text boxes see Maintain field formatting. Refer to the instructions in the General tags export for more detailed information about using merge fields.

• Tag updates – Markup % tags for issues, PCOs, and CCOs have replaced Margin % tags in the general tags to be consistent with the header field name change from Margin to Markup %. The Margin % tags no longer work in templates, and existing templates should be updated. Also, Grand subtotal tags have been added for issues, PCOs, and CCOs.

• Grand total dependent cost items – The Dependency tab of a grand total dependent cost item now shows all cost items used to calculate the value. This lets you see all cost items, dependent cost items, and markups used to arrive at the grand total. Read more

  

  For information about editing dependent cost items, see Dependent cost items

• Cost item pricing details in workflow notifications – The email notification sent for PCO and CCO approvals now includes cost item pricing information from the issue, if available, so you can compare the value in the change order to the value in InEight Control. Read more

  The pricing information includes the Adjusted billable amount, the Adjusted cost, and the Current budget.

  

  For information about PCO and CCO workflow approvals, see Workflow Assignments.

• RFI Number – You can now add your own RFI number when you add RFI documents with the source My computer. Previously RFI number was only available for items from InEight Document.

• PCO and CCO workflow absolute threshold support – Change now uses the absolute value of a threshold to start a workflow, so a pricing change in either direction starts the approval workflow. For example, if the threshold is $1000, a change of $1000 or -$1000 or more starts the workflow. For information about thresholds in PCO and CCO workflow, see Workflow Assignments.

• Budget move permission – A new permission View Change > Approve/Reject budget move has been added. For information about permissions, see Permissions.

• 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.

Updated 19-MAY-2023

• Template contact tags – New tags corresponding to the assigned contacts information have been added to the general tags. These tags let you select a contact to populate information in a generated document. For example, you could select a specific contact for a cover letter or notification letter. Read more

  The tags are called <<Template contact: field>>, where field corresponds to a field in the project contacts (project > Assigned contacts). These tags can be used to customize documents when you use standard or bulk template generation.

  When the document generator detects a template contact tag, it retrieves the information for the selected contact from the project's Assigned contacts (project > Assigned contacts).

  When you use the tags with Standard template processing, you can select one contact in the Select contacts step of the Change document wizard. When you use the tags with the new bulk template processing feature, you can select up to 10 contacts.

• Bulk templates – You can now generate change documents in bulk. The bulk template generation type lets you generate a separate change document for specified contacts in a single action. The bulk templates feature works in conjunction with template contact tags, so you can customize the documents for each contact. Read more

  The Template generation type field has been added to the Select a template step of the Change writer wizard. The field lets you select between standard generation, which gives you the option to generate merged or individual documents, or bulk generation, which generates a merged PDF for each contact specified, similar to a mail merge.

  

  When you select Bulk generation, and then click Next, Change detects whether the template contains template contact tags. If Change detects no template contact tags, the wizard takes you to the Review fields step. If Change detects template tags, the wizard takes you to a new step 2, Select contacts. This step lets you select up to 10 contacts.

  

  After you click Next, Change generates a document for each contact and customizes the document for each user. For example, if the template contact tags are used in a template that generates a cover letter and you have selected three contacts, Change generates three separate documents (one for each contact) with a customized cover letter.

  The Review templates drop-down list in the Review fields step has been updated to let you review the templates for each contact.

  

• Import existing plug cost items – You can now import new and existing cost items with a cost source of Plug into cost item pricing. Any plug cost item that is in the current project is eligible for import. Read more

  You can enter new and existing cost items on a single template.

  The WBS phase code column has been added to the cost item import template. To add an existing cost item, enter the phase code in the WBS phase code column. To add a new cost item, leave the WBS phase code column blank.

  

  When you import an existing cost item, the description that is configured in InEight Control is imported by default. If you want to change the how the description of the cost item is shown in Change, you can enter the new description in the Description field. If the Description field is blank, Change uses the description provided by Control. In the image above, the cost item with WBS phase code 1064 has no updates to the description, so the description from Control is imported. The item with phase code 1063 has a new description for this project. A new cost item has also been added on line 6.

  The following image shows the items after they have been imported into cost item pricing. The new cost item has been added, the item with phase code 1063 shows the new description, and the item with phase code 1064 shows the description from Control.

  

  You can also change the distributions by entering the value in the corresponding field of the template.

  When importing, if the phase code does not exist, the Import history page shows the status as Pending. The import details page shows an error in the WBS phase code column. You can use the drop-down list to select a valid WBS phase code.

  

• DocuSign certificate of completion and time stamp – After signing is completed, the certificate of completion is now available when you hover over the ellipsis in the DocuSign status field in Supporting documents. Also, the Modified on column has been added to the DocuSign status information. Read more Watch video

  The View certificate of completion link becomes available after a document is completed. The certificate of completion is stored in Supporting documents, but it does not take up a separate entry in the Supporting documents register. The certificate does not expire in Change.

  

  When you click View certificate of completion, a preview of the certificate from DocuSign opens in a new tab. You have the option to download the file if you want to store it separately.

  The Modified on date and time stamp is updated each time the DocuSign status changes.

  

• Issue details Field information enhancement – You can now add multiple Daily plan ID of impacted work entries to the Field information section on the Issue details page. Latitude and Longitude fields have also been added to the Field information section. Read more

  To add additional daily plan IDs, click the Add daily plan ID of impacted work icon.

  

• Cost item pricing adjusted man-hours – You now have the option to have Change recalculate the adjusted man-hours when you edit the Adjusted cost of a plug cost item with labor cost category value. Previously, Change did not offer a choice and would automatically update the labor cost per man-hour. Read more

  Now, when you change the adjusted cost, Change prompts you to select whether to proportionally adjust the Labor cost/Mhr or the Adjusted MHrs.

  

  The prompt shows only when there is a value in the labor cost category.

• Dependent cost items adjusted cost – When you add a quantity to a dependent cost item, Change now automatically calculates the unit cost based on the value of the adjusted cost. The unit cost is the quantity divided by the adjusted cost.

• Supporting documents preview – When you click to open a supporting document, the document now opens a preview in a new tab, so you can view the pages instead of automatically downloading. This feature is available on all Supporting documents pages. Read more

  The preview lets you view all pages of the document by clicking the Previous and Next buttons. If you want to download the document, click the Download file button.

  

Updated 16-MAR-2023

• Dependent cost items – You can now add a dependent cost item to cost item pricing. Dependent cost items are cost items with values calculated based on a percentage of the cost of other items. Examples include insurance the company carries, bonds, labor overhead, and others. Read more

  The value of the cost item is calculated using the configured percentage and the adjusted cost of all items in a section. For example, if you add a dependent cost item that is configured at 2% for the Labor section, as shown in the image below as Insurance for labor, and the adjusted cost for all labor cost items is $4000, the dependent cost item value is $80.

  

  To add a dependent cost item, click the Add dependent cost item icon, and then select one or more cost items defined in the project settings from the dialog box, or click Add manual dependent cost item. After you select the applicable cost items, click Add.

  

  The Edit slide-out panel for the dependent cost item includes the Details, Dependency, and Cost categories tabs. The Cost percentage field on the Details tab is multiplied by the Adjusted billable amount on the Dependency tab to calculate the cost of the dependent cost item. The Cost categories tab shows the distribution percentage for the cost categories.

  

  Dependent cost items are configured in the project level Configurations (Settings > Configurations > Dependent cost items). The dependent cost item includes the cost item name, cost percentage, WBS, and the section to which the dependency applies.

  

• Cost item plug calculations – Change now recalculates the Labor cost/Mhr value in a cost item pricing plug item based on changes to the unit cost and the Labor cost category. Also, when you update the Labor cost category, you can now choose whether to recalculate the Labor cost/Mhr or Adjusted MHrs field. Read more

  When you update the unit cost, Change calculates the adjusted cost, and then spreads it out over the cost categories. The Labor cost/Mhr is then recalculated based on the new value of the Labor cost category.

  When you update the Labor cost category on the Cost Categories tab in the New cost item or Edit cost item slide-out panel, a dialog box now prompts you whether to proportionally adjust Labor cost/Mhr or Adjusted MHrs.

  

• eSign enhancements – You can now correct documents in the original eSign envelope, so you can avoid the expense of additional envelopes. Read more

  A new button, Correct, has been added to the DocuSign status that shows when you hover over the ellipsis for a document with the status of Sent.

  

  When you click Correct, DocuSign opens with the view of the original envelope instead of recalling the envelope and sending out a new one If the document has not been signed , you can edit it, change the order of recipients, and change whether they are to sign or receive a copy.

  A new permission, Correct eSignature, has been added. You must have the Correct eSignature permission to correct DocuSign documents.

• Package supporting documents – You can now quickly package documents from the Issue, PCO, or CCO Supporting documents register into a single document that you can send to InEight Document or send out for electronic signature.Read more Watch video

  Packaging documents lets you combine documents to create a single PDF file instead of downloading each one and combining them outside of Change. Only documents in Microsoft Word or Excel, PDF, or image format that come from the document source My computer can be added to the package.

  To package documents, go to the Supporting documents register for an issue, PCO, or CCO. Select one or more documents with the source My computer, and then click the Package documents icon.

  

  The Package supporting documents dialog box opens to the Selected documents step. You can then select additional eligible documents to be in the package or reorder the documents in the package.

  

  Click Next to go to the Package document details step where you can enter the title, document type, file or link name, and notes. The File/Link name field defaults to the value you enter in the Title field, but you can change it.

  

  Click Save to save the package as a PDF in the Supporting documents register.

• New Add markups icon – A new icon has been added for adding markups in cost item pricing and pricing summary. Read more

  The Add markups icon has been updated to be more consistent with other pages in Change.

  

• Pricing summary collection table – A new collection table called Pricing summary and tags are now available in the Change document templates. The collection table is available for any issue, PCO, or CCO template. Read more

  The Pricing summary collection table tags gather the information from the pricing summary page for an issue, PCO, or CCO and places them in the collection table. If a PCO has multiple issues or a CCO has multiple issues or PCOs, the collection table shows each issue or PCO on a separate line. When markup is applied to multiple issues, each markup shows on a separate line.

Updated 27-JAN-2023

• Cost item markups – You can now add markups to cost item pricing. The markup is then carried over to the pricing page and included in the subtotals for each section. They are also included in the Markup field in the header and removed from the cost calculation. Read more Watch video

  Markups for cost items can be applied to the same sections used for markups in the pricing summary, except for the subtotals. You can also add a markup to the Grand total.

  To add a markup to cost item pricing, click Add markups. The Add markup dialog box opens. You can select an available markup or add a manual markup.

  

  When you apply a markup in cost item pricing, the markup is shown in the grid on its own line.

  

  Once saved, the markup is carried over to the pricing summary. Cost item markups are shown above the subtotal line and are included in the pricing summary subtotal.

  

  After you convert the issue to a potential change order or client change order, both the cost item markup and the pricing summary markup are shown above the subtotal.

  

  The markups that populate the Add markups dialog boxes are now configured in the project configurations. Pricing markup has been added to the project settings (Settings > Configurations > Pricing markup). Previously markups for the Pricing summary page were configured in the Change project details.

  

  This new configuration lets you configure markups for the pricing summary and the cost item pricing pages.

• Decimal precision – You can now set the number of digits that trail the decimal point in values, quantities, and percentages shown in Change. Read more

  The Decimal precision settings have been added to the project level settings (Settings > Change > Configurations > Decimal precision). You can choose a separate value for values, quantities, and percentages. If you do not enter a value, it defaults to a value of 2.

  

  You can choose 0-11 digits. If you choose 11 digits, the decimal characters do not fit in the fields of the issue, PCO and CCO headers. An ellipsis is shown when the decimal is too long for the field.

  

  The issue, potential change order, and client change order logs and detail pages and the pricing pages have been updated to support decimal precision. Exports for the logs also support decimal precision.

  Tag output continues to use two decimal places.

• Launch new reporting dashboard from the Issue, PCO, and CCO log – You can now launch the InEight Explore reporting dashboard from the Issue, PCO, and CCO logs. Read more

  To go to the new Explore dashboard, expand the Actions menu, and then select Launch dashboard. The Explore dashboard opens. You then select your project to use the reporting functions.

  

• New current contract completion date tags – New tags have been added to account for the number of days the current client change order will extend the contract. Read more

  Previously, tags existed only for the revised completion date, which did not include the current CCO. When you were working in the CCO you could not see how the CCO would extend the contract.

  Now, the <<Current contract completion date>> and the <<Current contract completion date-words>> tags show the new date after the extension in your generated document.

• Cost item pricing template permissions – The Edit shared cost item template and Delete shared cost item template permissions have been added to ensure that only users with the applicable permissions can edit or delete a shared cost item pricing template.

• Action item description – The Description column has been added to the Action Items tab, so you can see a description of the item you are approving. Read more

  The Description field corresponds to the Description of change field in the issue, potential change order, or client change order.

  

• Cost item pricing Adjusted CB quantity – You can no longer set the Adjusted CB Qty field in cost item pricing to a value that makes the Updated CB Qty field less than zero. An error indicator shows for the field on the Cost item pricing grid and in the Edit slide-out panel if the value is less than zero.

• Budget move issue status – A new status has been added for issues that are converted to a budget move. These issues now automatically receive a status of Budget move similar to issues converted to a PCO and CCO.

• Pricing summary markups available at all levels – After you use a markup at the issue, PCO, or CCO level, you can now use the same markup at the other levels. Previously, you could not use a markup at more than one level.

• Markup tag updates – The cost item pricing markups are now used in the calculation markup tags. The markup tags, for example, <<Issue labor markup>> now show the sum of the cost item pricing markup and the pricing summary markup. This new calculation is not shown in the tag descriptions.

• Cost item pricing templates enhancement – You can now create cost item pricing templates, so you can quickly add frequently used cost items when pricing an issue. Read more

  If you have large projects with many cost items, or if you have a group of cost items that you use on a regular basis, you can create a cost item pricing template to quickly add cost items in cost item pricing. When you add an existing cost item, the Manage templates icon becomes enabled. Only existing cost items can be saved as a template.

  To create a cost item template, add an existing cost item, and then click the Manage templates icon, and select Create template.

  

  In the Create as template dialog box, enter the name of the template, and then select a value from the Sharing field drop-down list to indicate whether you are creating a private template or shared template. Click Save.

  

  When you save, Change validates to ensure that the template name and shared value is unique. The existing cost item dialog box opens. You can then select and group cost items. Click Save. Templates are not specific to an issue. You can manage templates from any issue and reuse them.

  You can also add a template from the Add cost item pricing dialog box. After you select existing cost pricing items, click Create template.

  

  The Create as template dialog box opens. Add the template name and indicate whether the template is private or shared. Click Save. Change creates the template, but the items are not added to the grid. To add the items to the grid, click Add in the Add cost item pricing dialog box.

  To manage a template, click the Manage template icon and then select Manage templates. The Manage templates dialog box opens where you can add, edit, delete, and copy templates and send a copy of a private template to another user.

  

  • Edit a template – When you edit a template, you can only edit one template at a time. If you edit a shared template that you did not create, you must create a new template with a unique name and then save it.

  • Delete a template – You can delete multiple templates at a time. When you delete a shared template, you delete it for all users. You can delete multiple templates at a time.

  • Copy a template – You can copy a template and save it with a unique name.

  • Send a copy – Select a template, and then click the Send a copy icon. The Send copy of template to dialog box opens.

    

    Select the name of one or more users, and then click Send. The recipients receive a notification in the Notifications area. When the user clicks on the notification, they are taken to the issue log where they can save the template.

  To use a template, select a template on the Manage templates dialog box, and then click Open template.

  

  The Add cost items dialog box opens. You can then use the template as is or add or remove items. Click Add to add the items to the cost item pricing grid.

  New permissions were added to allow users to edit and delete cost item pricing templates.

• Custom labels for project contacts and Change details – Change now supports the custom labels for project contacts that are set at the suite administration level. Custom labels have also been added for Change details fields. Read more

  When the Enable custom labels toggle in Suite administration > Custom labels is set to Yes, the custom labels for project contacts are shown in the DocuSign section of the PCO and CCO Details page. You can also use them when you create a document for signature in Supporting documents.

  For Change details, the custom labels for Source/cause, Change condition, Scope, and Allowance category have been added to organization Settings >Change > Custom labels. The custom labels can be enabled or disabled at the project level. The labels are used in the Issue description section of the Issue Details page.

• Project Construction area enhancements – Change custom construction areas are no longer an option for new projects after you upgrade to release 22.10. Existing projects can continue to use them. New projects now get construction area information from the InEight Platform Construction area configuration. Read more

  The Platform Construction area (project > Project values > Area) has been added.

  For existing projects, the Use the Construction area list created within Plan and its maintained updated list toggle in the Change project settings (project Settings > Change > Configurations > Construction area) has been changed to Use the Construction area list created within Configure CWA and project values and its maintained updated list.

  

  When the toggle is set to Yes, construction work area information configured in the Platform Construction Work area populates the Construction area drop-down list in the Field information section of the Additional details in an issue.

  The construction area configuration page has been removed for new projects. The construction area information configured at the Platform level is automatically used in the Construction area drop-down list.

• Notify controller of budget moves – You can now notify the controller of a budget move. The Project settings > Notification > Notify controller of adjustments setting has been updated to include budget moves. Read more

  The email notification includes an item type so you can see the executed CCOs and budget moves.

  The Control change register link has been added to the email notification, so you can go directly to the InEight Control change register from the notification.

• Add new or existing cost item with right-click – When you right-click on the cost item grid, you now have the option to add a new or existing cost item. All cost pricing types are available except vendor.

• Import template enhancement – Change now reads the page names in the import template when importing data. Because of this enhancement, import ing does not work if you change the name of the Template tab in the template.

Updated 04-OCT-2022

• Initiate Control budget move – When you have issues that are not going to result in client change orders, you can now initiate a budget move in InEight Control directly from the issue. Read more

  To create a budget move from an issue, click the Actions menu, and then select Create budget move.

  

  A budget move is sent to Control with a Draft status. After the budget move is sent, you can no longer associate the issue to a PCO or CCO, and the Pricing tab is disabled.

  When the budget move is in Control, the Control user can review, delete, or revise the budget move. Refer to the Control documentation for more information about budget moves.

  You can track the budget move from the Control budget change section in the Additional details section of the Issue details. The heading of the Control budget change section shows the Control icon representing the budget move status. The budget move in Control can have one of the following statuses: Approved, Draft, Revised, or Rejected.

  

  The expanded Control budget change section shows the control budget status and the Control change register ID.

  

  You can also revise the budget move from the issue. Click the Actions menu, and then select Revise budget move. Revising the budget move makes the issue available to edit. The status in the Control budget change section changes to Revised. You can then make changes to the pricing or associate the issue to a PCO or CCO. If you make a budget move that is nonzero for cost item pricing, a warning message asking if you want to proceed is shown. When you click Yes, the budget move is sent to Control, and the Control user can zero out the budget move.

• Cost item pricing enhancements – Enhancements have been made to simplify the use of cost codes in the Cost item pricing feature. In the Add cost item pricing dialog box, you can now select a parent WBS code that automatically selects all the cost codes underneath it. Also, If a cost code is assigned to only one contract, Change automatically brings in that contract association, so you don't have to look for the contract. WBS codes that have been assigned on the Details page can now be pushed to cost item pricing, so you do not have to add them again. Read more

  When you select a WBS that is assigned to only one contract, the cost pricing defaults to Vendor, but you can change it. After the cost item is added, Change automatically assigns the cost item to the vendor and contract number. The vendor is editable. Previously, the vendor defaulted to blank.

  The Push to cost item pricing link has been added to the Assigned WBS section of the Issue Details page.

  

  Click the Push to cost item pricing link to automatically add the WBS codes to the cost item pricing for the issue. The Push WBS to cost item pricing dialog box opens. You can then select one or more WBS codes, and then select the cost pricing. Click Add. When you go into the cost item pricing for the issue, the items are already added.

  

  Items that are manually added on the Cost item pricing tab are not automatically added to the details.

  An Info icon has been added to the Assigned WBS section on the Details page of an issue as a reminder that WBS codes can be assigned from InEight Plan or Control or from this section.

• DocuSign enhancements – The person who sends the document to DocuSign now receives an email notification when the document signatures have been completed. Also, you can now send a courtesy copy to recipients of documents sent for eSignature. The Action field has been added to the DocuSign recipient page of the Send for signature dialog box that lets you choose Needs to sign or Receives a copy. Read more

  When the action is Needs to sign, the recipient receives a document that is ready to sign. When the action is Receives a copy, the recipient receives a snapshot of the document in the signing order. For example, if the recipient marked Receives a copy is second in the signing order, they receive the document after those first in signing order, even though they are not signing.

  

• Use templates at higher levels – You can now use issue templates at the issue, PCO, and CCO levels. You can use PCO templates at the PCO and CCO levels. Having the templates available at higher levels lets you include issue and PCO details at higher levels. Read more

  When you generate a document from a template at the CCO level, you can now use issue and PCO template types.

  When you use an issue or PCO template type at a higher level and choose to generate the document as individual documents, Change generates a separate document for each issue or PCO. When you choose to merge the document into a single PDF, the document uses the template for each issue and merges it into the single document. When you review the templates, the project name and the fields are repeated for each issue. When you click Finish, multiple completion messages are shown.

• Option to show or suppress supported documents details in generated document - You can now specify whether supporting document details in an issue, PCO, or CCO is shown in a generated document. Read more

  Previously, when you used a supporting documents collection table tag in a template, all the documents in the register showed in the table in the generated document, even if they were not needed for the document.

  Now, a new toggle on the Supporting documents register, Show in generated document, lets you indicate whether the document is shown in a collection table based on the collection table type. When you have a supporting document that you do not want to show in a collection table in a generated document, set the toggle to No. When a document is generated, only the documents that were set to Yes are shown.

  

  A document that is available at more than one level, such as an issue-level document available on the issue, PCO, and CCO Supporting documents pages, can have a different setting at different levels. For example, you might set the toggle at the issue level to Yes to show in a generated document. You could set the toggle at the PCO level for the same document to No to not show in a PCO document. Change uses the setting that corresponds to the level of the collection table tags in the template. Using the previous example, Change shows the supporting document in a collection table as follows:

  • When you generate a document for an issue, the document is shown because the only collection table type in an issue document is an issue table.

  • When you generate a document for a PCO that has an issue-level collection table, the document is shown because it is part of an issue-level collection table.

  • When you generate a document for a PCO that has a PCO-level collection table, the document is not shown, because the document is suppressed at the PCO collection table level.

• DocuSign tag additions – You can now add DocuSign text, check box, drop-down, and radio button tags to your document templates. The tags let you set up placeholders for those field types in your template. You can then add values in the DocuSign Sender view. Read more

  The DocuSign tags have been added to the DocuSign template tags for eSign 1-10, and for each project contact. Adding the tags in the template ensures that the corresponding item is consistently placed. For text and drop-down lists, you only place one tag in the template. For check boxes, you place one tag for each option. For radio buttons, a single tag places two buttons in the document. You can add more radio button tags for additional buttons.

  When a document with these tags is opened in the DocuSign Sender view, the tags are present, but they do not have values. You can add the values from the Sender view. For example, if the template has three check box tags, when the document is opened in DocuSign, three empty check boxes are shown. You then add the value for each check box in DocuSign.

• Custom labels in DocuSign – When custom labels are used for contacts in InEight Platform project details, Change now uses the labels in the DocuSign section of the PCO and CCO Details pages and in the Send for signature dialog box.

• Supporting documents mail enhancement – When you create InEight Document mail from an issue, PCO, or CCO and you select documents before clicking Document > Create Mail, the documents are now automatically selected in the Select documents dialog box. If you do not select documents before clicking, no documents are selected. If a document selected is not of the type My computer, it is not available to be attached to mail, so it does not show in the Select documents list.

• Custom document types – Change now supports custom document types created in InEight Platform. The document types are used when adding a new supporting document.

• Request for information count – A counter has been added to the Request for information section heading on the Issue, PCO, and CCO Details pages, so you can easily see if the issue, PCO, or CCO has associated requests for information. Read more

  If there are no requests for information, the counter is not shown.

  

• Cost item pricing enhancements –Icons for navigating the pricing summary and cost item pricing were added to improve efficiency. Read more

  The Pricing summary tab icon is a pyramid shape. The Cost item pricing tab icon is three lines.

  

  You can still expand the sidebar to see the names of the tabs.

• Visual indicators for existing detail cost items – Visual indicators have been added so that you can see when exisitng resources are changed. Read more

  When a cost item is brought into Change from InEight Control, the resources on that cost item show with no indicator.

  When you add a resource, a yellow dot shows to the left of the row number to indicate that the resource has been added. When you remove a resource that had previously existed on a cost item, strike-through text is shown. The removed resource is not considered on the cost item, but it is not removed from Control. If you remove a resource that was added in Change, the line is removed from the Resources tab.

  

  When either of these happen, the unit rate driver changes to Manual to indicate that this cost item is no longer using current estimate resources from Control. When a Contract adjustment is executed, Control does not cosume any resource changes on the existing cost items. This functionality is meant for estimating changes only.

  When you undo a resource change, a dialog box prompts if you are sure you want to undo your changes. If you select Yes, the changes are removed, and Change recalculates the cost item. For example, if you remove an existing resource and then you undo the removal, the strike-through text is no longer shown.

• Cost item pricing current budget and current estimate – Current budget and Current estimate columns have been added to the column chooser on the Cost categories tab to provide visibility into the cost categories in InEight Control. Read more

  The columns have been added to the Cost categories tab on the Edit cost item slide-out panel. The columns are not selected by default.

  

• Cost item import – You can now import new Plug cost items into an issue cost item pricing. Read more

  The Import icon has been added to the Pricing tab.

  

  When you click the icon, the Import data from template dialog box opens, and the Import cost item Microsoft Excel spreadsheet template is available for download. The Excel spreadsheet includes instructions that should be read thoroughly before importing. The file size cannot exceed 5MB.

  The spreadsheet fields correspond to the fields in the Cost item grid. Drop-down fields are populated from the organization and project settings. The only required fields are UoM and Cost pricing. It is recommended to download a new template each time you import, so the fields and field values are current. After all information is entered, you can drag and drop the Excel file to the dialog box, and then click Import.

  After importing, you receive an email message listing status, the total cost items, the total imported, and number of errors. If the status is Pending, you can click the Review data link to see the cost items that have completed and those with errors.

  You can correct the cost items with errors from the Import history grid, select them, and then click Import to continue with the import process. The import is reprocessed, and Change sends you an email message when the import is completed.

  You can also view the import history for cost item pricing by selecting View import history from the Actions menu.

• Row density settings for all grids – Row density settings are now available for grids in pricing slide-out panels and dialog boxes. Read more

  Row density settings on a grid, such as the pricing summary, are applied to any slide-out panels or dialog boxes accessed from that page.

  

• Notify controller of adjustments – You can now notify a user when a contract adjustment has been sent to Control. Read more

  The Notify controller of adjustments subtab has been added to the Notifications tab in the project settings.

  

• Enhanced navigation breadcrumbs – The breadcrumb navigation now includes an issue, PCO, or CCO designation as the second breadcrumb. The ID and name of the issue, PCO, or CCO is the third breadcrumb. Read more

  

  When you click on the first- or second-level breadcrumb, you are redirected to the applicable log.

• PCO and CCO associations – Billing markups, deductions, and net value are now shown in the Associations section of PCOs and CCOs.

• Disable executed change order amount – New pricing configuration has been added to restrict the ability to modify the executed contract amount during the execution of a client change order. Read more

  New configuration settings let you specify if users can change the Executed Change order amount field on the Execute Client change order dialog box.

  The Allow users to edit the Executed change order amount upon execution toggle has been added to the Configurations settings at the organization level (organization > Settings > Change > Configurations > Pricing configuration > Client change order configuration > Allow users to edit the Executed change order amount upon execution).

  When you disable the organization setting, the setting at the project level is also disabled. When you enable the setting at the organization level, you can enable or disable the setting for each project.

  

• Template writer versioning – You can now create a new version of an exisitng Change writer template. This is helpful when you update templates with additional information. You can now update the version rather than inactivating it and then creating a new one. Read more

  The Create New Version button has been added to the Template details page. The button is enabled after you select a template from the register, and then click the Edit icon.

  

  When you create a new version, the version numbering starts after the previous version. The new template version starts in the draft state. You can edit any of the fields except the template type and language. You can then attach the new file.

  Only one version of a template can be active at a time. After you add a new version, the previous version becomes inactive and is removed from the Templates register.

  The Version column has been added to the Templates register, so you can see the version. When you click the version number the template version history is shown. The template names are linked to the Template details page, so you can quickly view the detail information.

  

  The Version history subtab has been added to the template details at both the organization and project levels. The version history shows all versions in descending order, including inactive versions.

  

  Versions of organization-level templates are available for use at the project level, but you can only create a new version of those templates at the organization level.

• New template tags – Collection table tags have been added to break out vendor addresses. Previously, one tag held the entire address. Now, each part of the address has its own tag. Collection table tags have also been added for the new fields in the Associations sections for PCOs and CCOs: Billing markups, Deductions, and Net value. You can now generate Cost item pricing collection tables on all templates.

• DocuSign updates – The Send for eSignature permission has been added. Previously, any user who had edit change document permission could send a document for eSignature. Also, when you send a document for eSignature, the name of the user who sent the document shows when you hover over the DocuSign status.

• Updated share view behavior – Views on the Issue, PCO, and CCO logs can now be shared only with users who have the View permission for the project from which you are sharing the viewset.

• Custom lists at the organization level – You can now define Custom lists 1 and 2 for issues, PCOs, and CCOs at the organization level. Read more

  The Custom lists tab has been added to the Configurations (Organization home > Settings > Change > Configurations > Custom list).

  Custom lists created at the organization level are applied to the project level and default to Active. Items defined at the organization level can only be deleted at the organization level, and only if they have not been used. If you do not want to use an item on a project, you can disable it at the project level. The custom lists are used in the Custom Fields section of the Issue, PCO, and CCO Details page.

• Cost item pricing enhancements – The size of the Add cost item dialog box has been increased, so you can see more information. The Resources section of the Resources tab in the cost item slide-out panel now retains the columns selected in the column chooser. A right-click context menu was added for easy edits. Read more

  When you right-click a cost item, a menu shows options for adding, editing, copying, and deleting the item. This saves you time from having to move your cursor to the top of the grid each time you want to work with cost items.

  

• Copy cost item – You can now copy a new or existing cost item, so you do not have to start over when adding a similar item. You can select Copy from the context menu or click the Copy icon in the toolbar. Read more

  

  You can select a new or existing cost item to copy. Only one cost item can be copied at a time. If you have selected more than one cost item, the Copy cost item option in the context menu is disabled. You cannot copy a copied cost item until it is saved. The copied cost item remains on the register when you click Save.

  Every copy is treated as a new cost item; therefore, a WBS phase code is not added because it is not yet in InEight Control. The phase code stays blank until the CCO is executed and the contract adjustment is approved.

• Existing cost item enhancements – The Cost item description is now editable for existing cost items. You can now change the cost source of an existing cost item from Plug to Detail or Detail to Plug. Current estimate unit driver becomes unavailable when resources are updated manually. Read more

  You can now modify the description on existing cost items. The updated description shows in the Cost item pricing grid. The updated description is not carried over to InEight Control. The updated description is available in collection table tags and in the Control description.

  If you add, edit, or delete a resource on an existing Detail cost item, the value of the Unit rate driver field changes to Manual. The option to return to the Current Estimate value becomes unavailable. The only way to go back to the current estimate is to delete the cost item and add it again.

• Issue log dynamic import – You can now export the issue log with data, make updates to existing issues, and re-import it. This can save you time if you want to make bulk changes. Also, the project display ID was added to the file name. The format for the import template name is IssueLog_YYYY-Month-DD_project display ID.

• CCO execution enhancement – When you execute a CCO, the Approved time extension field in step 1 of the Execute Client change order dialog box now defaults to the value 0. You can use the default value or change it. Previously, you had to enter the number of extension days before moving to the next step.

• Warranty allowance category update – You can now edit or delete the Warranty allowance category on the Change Project details page (Project home> Settings > Change > Project details). Previously, Warranty was a standard category that could not be edited or deleted. You can delete the warranty allowance category only if it is not used in an issue.

• Approval process for multiple supporting documents – Documents with group workflows can now be included in the approval process for multiple documents at the same time. This functionality is available at the issue, PCO, and CCO levels. Read more

  The Start Approval dialog box has been updated to show all the workflow steps for each document selected. For workflows with one or more group steps, you must select groups for each group step in each document. After you enter all information, you can click Start to start the approval process.

  

  Each approval workflow generates its own email notification to the first approver. If you start the approval workflow and you are the first approver, the step is automatically approved.

  The Start approval dialog box stays open until all workflows have successfully started.

• Edits to documents in approval – You can now make minor edits to documents that are in approval or already approved. Read more

  You can change the supporting document title or add or change notes and other metadata. You cannot change the document type or the file link. If you want to change the file link or the document type, you must recall the document from the approval, make the changes, and then start the approval again.

• Automatic approval for documents, PCOs, and CCOs – When you start the approval process for a document, PCO, or CCO and you are the first approver in the approval workflow, the document, PCO, or CCO is automatically approved for the first step of the workflow. Read more

  If you are the first approver, Change sends an email notification that the document, PCO, or CCO was approved. When you hover over the blue ellipsis in the approval status, step 1 shows as Approved, and step 2 shows as In approval, if there is a step 2.

• User date preference in import templates – Import templates now support the date format defined in your user preferences. Previously import templates only supported the MM/DD/YYYY format. Read more

  When you export the template, the date columns show the format as defined in your user preferences, so you can enter dates in your preferred format. When you import the template, the dates are read correctly.

  Change validates the dates based on the person who imports the data. If the dates do not match the preferences of that person, Change generates an error in the import history and deletes the date. You must then enter the dates manually before you can complete the import.

• Create a document form from InEight Document – When you create a form in Document, the Add supporting document type now defaults to Form.

• Issue bulk edit – The column for Does this impact the schedule was added to the issue bulk edit capabilities.

Updated 21-FEB-2022

• eSignature via DocuSign – You can now send PCO or CCO change documents directly to DocuSign for electronic signatures. Read more

  Change can now send change documents for eSignatures via DocuSign. You can embed common signees into your project templates or add signees at any time to take your project efficiency to next level.

  Link DocuSign account to the InEight cloud platform

  The DocuSign integration is configured in the eSignature tab of Suite administration > Application integration in InEight Platform. DocuSign accounts can be set up for the organization and for individual projects. Contact your InEight representative if you have questions about getting a DocuSign account.

  Project-level set up

  Recipients can be defined at the project level and then are available for use in every contract. The DocuSign setup page has been added to the Change templates tab in the project settings (Project settings > Change templates > DocuSign setup). You can enter the names of up to 10 recipients and their companies, titles, and email addresses.

  Recipients can be pulled from the project Assigned contacts list or free text. As you start to type a name, Change searches the project contact list. You can manually overwrite values.

  

  If you edit the DocuSign setup, the recipients are available for new projects only. You can override the DocuSign recipients in the DocuSign section of the PCO or CCO header details. Updates to settings can be refreshed at the PCO or CCO level.

  Recipient set up

  A DocuSign section has been added to the PCO and CCO details pages. You can use this section to view or add common recipients to be used as default signees. This section has subsections for DocuSign and Project contacts. All signees must be added to at least one section.

  

  • DocuSign recipients - Populated from the project DocuSign set up tab (Project settings > Contract > Contract templates >DocuSign setup) or manual entry.

  • Project contacts – Populated with contact information from Project Contacts added in Project details. This section is for reference only. If you want to add or change recipients, you must edit the Project Contacts.

  Change writer – tag embedding

  DocuSign eSignature tags for recipients have been added to Change writer General tags, so you can embed signee information to pull into your organization or project templates. DocuSign tags used in a template are read when sending the document for signature.

  When you insert the tags into a template, change the font to white so that the tags do not show when the contract document is generated.

  Send documents for eSignature

  Documents sent for eSignature must be in Microsoft Word, Microsoft Excel, or PDF format. Any user that has Edit change permission is able to send documents to DocuSign.

  To send a document for signatures from a PCO or CCO Supporting documents page, select one or more documents with the document source My computer, and then click the Send for signature icon.

  

  A wizard opens that lets you select signees, add a message, and send for signature.

  

  The Assigned section of the wizard is populated from the DocuSign recipient tags that were embedded into the document. Additional recipients can be added from the Unassigned section. When sending a document for signature if there are DocuSign tags in the Assigned section you can edit the recipient information in the first step of the Send for signature wizard. Any changes made in the wizard are saved in the DocuSign accordion on the header tab of the PCO or CCO. Signing order defaults to the order they were added but can be adjusted by overwriting the number order. You can duplicate a number if you want the recipients to receive or sign the document at the same time. All recipients in the Assigned section have ad-hoc signee tags that can be placed on the document in DocuSign.

  The Unassigned section is populated with any recipients that were filled out in the DocuSign section of the PCO or CCO details. These recipients can be added to the Assigned section.

  When you have all signees in the Assigned section, click Next. You can then enter an email subject and message to the recipients.

  After you click Send, a DocuSign window opens with the documents you chose. If you had any embedded tags, they show on the document. All assigned recipients are available in the upper left drop-down list to drag and place additional signature fields on any of the selected documents.

  

  After you click Send, the documents are routed for signature, and DocuSign sends an email message to each recipient based on the signing order. In Change, the DocuSign status column on the Supporting documents page is populated with the status of Sent, and a hover over showing the status of the signatures.

  

  When completed, the signed document is loaded as a new supporting document with the same document type and title. The DocuSign status is Signed. All fields can be edited except the file link cannot be removed or changed. Watch video

• Cost item pricing – You can now create new detail cost items using resources from InEight Control’s resource project library. You can also edit resources on existing detail cost items. Cost categories have been added to cost item slide-out panel. Read more Watch video

  Edit existing Detail cost items

  When you go to the Resources tab on the Edit cost item slide-out panel, you can now edit resources in the Resources section. Each resource has a Cost driver of Fixed, CI Duration, or CI Qty as in Control. Cost driver and resource type determine which fields are editable for any given resource. If any resource with a Cost driver of CI Duration exists, Productivity and overall settings becomes editable.

  Additionally, each resource will have costs distributed across the different cost categories that are displayed in the new Cost categories tab. For Detail cost items, the Cost category tab is read-only.

  

  After you change a value in the Resources section, a blue dot is shown to indicate in that someone has changed the value of the resource in Change. If you make changes to the Productivity and overall settings section, a yellow indicator shows the last field that was updated.

  

  If the update to the Productivity and overall settings affects resources, the blue dot is shown in resources.

  Create New Detail cost items

  When creating a new Cost item, you can change the Cost source to Detail. You can add and remove resources on the Resources tab and modify fields based on resource type and cost driver. This behavior works as described above. The Cost categories tab reflects the distributions applied at the resource level to give you the overall total of each category.

  Cost categories

  A new tab labeled Cost categories is now present in the Cost item slide-out panel for New and Existing Plug cost items. Cost is automatically assigned to a cost category based on cost pricing selected. For example, Cost pricing is Materials, the adjusted cost is shown in the cost category of Materials. You can manually distribute costs across individual cost categories. It is important to note that all cost categories are summed into a Total adjusted cost for the cost item. The name of each Cost category shown here can be modified using custom labels.

• New issue import – You can now import multiple new issues at one time. An import template, via Microsoft Excel, is available to enter data. After all information is entered into the spreadsheet, you can import it into Change. Read more Watch video

  The Import icon has been added to the Issue log.

  

  When you click the icon, the Import data from template dialog box opens, and the Import Issue template spreadsheet is available for download. The Excel spreadsheet includes instructions that should be read thoroughly before importing.

  The spreadsheet fields correspond to the fields in the Issue details. Drop-down fields are populated from the organization and project settings. The only required fields are Issue name and Issue start date. It is recommended to download a new template each time you import, so the fields and field values are current. After All information is entered, you can drag and drop the Excel file to the dialog box, and then click Import.

  

  After importing, you receive an email message listing status, the total issues, the total imported, and number of errors. If the status is Pending, you can click the Review data link to see the issues that have completed and those with errors.

  

  You can correct the issues with errors from the Import history grid, select them, and then click Import to continue with the import process. The import is reprocessed, and Change sends you an email message when the import is completed.

  If workflow is turned on, issues come into Change with the status In approval, and they do not get issue IDs until they are approved; the issue ID is Pending. Workflow emails are sent for each new issue included in import. If workflow is turned off, issue IDs are assigned upon import, and the status is Not applicable.

• Automatic approval for new issues – When you create an issue and you are the first approver in the approval workflow, the issue is automatically approved for the first step of the workflow, and continues with the next step, if applicable. Read more

  When creating a new issue and you are the first-step approver in the approval workflow, either as a user or a member of a role or group, Change automatically approves the first step upon creation.

  An email is still generated requesting approval, but is auto-approved in the system so it can be ignored. If you hover over the Issue approval status in the Issue log, step 1 shows that it was approved and is in step 2, if there is a step 2. If you are the only step in the approval, you receive a second email confirming the new issue has been approved.

  

• Link a Change vendor proposal to an InEight Contract – When you add a supporting document of type Proposal and subtype From vendor and associate it to a Contract ID, the document is now visible in Contract as read-only on the main supporting document register and the Contract supporting document tab. A VCO ID field has been added. If a VCO ID is associated, it also shows on the VCO supporting document tab. Read more

  In the 21.2 release, a supporting document of Proposal with subtype From vendor could be associated to a Contract ID, if the vendor or contract was associated in the pricing summary.

  Now a VCO ID field has been added to Proposal with subtype From vendor. When a vendor or contract is associated to a VCO, the VCO ID is also available to associate the document.

  When an association to a contract or VCO is made, the supporting document shows in the Contract or VCO supporting document page.

  The action Contract takes depends on the action taken in Change:

  • When you add add a pricing item without a VCO ID to the Vendor section of the pricing summary and then add a supporting document with type Proposal and subtype from vendor, a new field, Vendor Change order ID is shown in the New supporting document dialog box. If you click Add without adding the VCO ID, the document is added to the contract's Supporting documents page and the main Supporting documents page in Contract.

  • When you create a new VCO from the pricing item, a vendor ID is associated to the pricing item. When you add a new supporting document Proposal from vendor, you can select the VCO ID. When you add the document, it is added to the VCO's Supporting documents page, the Contract's supporting documents page, and the main Supporitng documents page in Contract.

  • When no contract ID is entered, Change sends the proposal to Contract. The document shows in the Contract main Supporting document register until you add a contract ID in Change.

  The document is read-only in Contract because it came from Change. If the documents are updated in Change, the updates come over to the document in Contract. For example, if you change title, Contract updates the title. If you change the document type or subtype, Contract deletes the document.

• Task enhancements – The task log has been updated to allow exporting. Improvements were also made for filtering and sorting. Read more

  The Export icon has been added to the task log.

  

  The log has been improved with filters for searching and sorting and row density control. You can also change the view between All tasks and My tasks.

  The Name column now contains the Name of the issue, PCO, or CCO. Previously the column contained the task Name. You can click the Name to go directly to the issue, PCO, or CCO.

  The counter in the Task log has been updated to include scheduled tasks as well as overdue and pending tasks.

  Collection table tags have been added for tasks.

• Issue, PCO, and CCO log updates – The Deductions and Net value columns have been added to the Issue, PCO, and CCO logs. You can also generate a change document from the logs, so you do not have to open an issue, PCO, or CCO first. Read more

  Generate change document has been added to the Actions menu on the logs.

  

  To generate a document, select one issue, PCO, or CCO, and then expand the Actions menu and click Generate change document. The Generate change document wizard opens, and you can follow the procedures for generating a change document.

• Template tag updates – A tag for the generated date , <<Generated date>>, was added to the general tags list. The tag shows the date that the contract was generated. Tags for Tasks have been added to the collection table tags. Tags now revalidate if you change template type on an unpublished template.

• Permission name update – The Close out/Reopen change orders permission has been renamed to Execute/reopen change order.

Updated 01-APR-2022

• Mass VCO creation from CCO execution – You can now create multiple vendor change orders in InEight Contract for any vendor pricing associated to a CCO upon execution of the CCO. Read more Watch video

  A new setting at the project level Pricing configuration (project Settings > Change > Configurations > Pricing configuration > Automatically create vendor change orders) lets Change automatically create new vendor change orders from vendor pricing items that are not already associated to a VCO.

  

  A new step has been added to the CCO Execution wizard that shows the vendor pricing items. When set to Yes, you must the select vendor change order type, and Change creates VCOs from the vendor pricing items upon execution of a CCO. When set to No, you can see which vendor pricing items are not associated with a VCO, and you have to manually associate them.

  

  The VCOs are in the Contract Vendor change order log with the value and Service account in the Created by column.

• CCO execution wizard – The CCO execution wizard now uses the net value in the Executed Change order amount field by default. Previously, the the Executed change order amount field used the Current value. You can now attach the executed change order in step 2 of the wizard. Previously you had to attach before executing.

• Single sign-on to InEight Document – The sign-on to Document from Change now enables single sign-on. When you use Change to Document features (such as creating mail or a form), you are taken directly to the Document sign-on page, where you can enter your Document credentials. This creates a sign-on token that lets you remain signed on until the session ends. The first time you sign in to Document, a black secondary window and the Document Home window are shown. After you close these windows, they are not shown again, and single sign-on is activated.

• Create mail in Document – You can now initiate mail in the Document Mail module, and it saves the mail and creates a link in the Change Supporting documents tab. This feature improves integration between Change and Document. Read more Watch video

  The option to create mail has been added to the Actions menu for Issues, PCOs, and CCOs. This feature lets you create mail from Change into Document's Mail module.

  

  To create mail, go to Actions > Create document > Mail. If you have not already signed on to Document you are prompted to sign in. The Create Document Mail dialog box opens, and you can choose the Mail type from a list of types defined in Document that are specific to the project's mail types. You then can add an attachment from the Change supporting documents tab, add an attachment in Document, or send the mail without an attachment.

  • To add an attachment from the Supporting documents tab, click Next. The Select documents dialog box opens. You can choose documents from the Supporting documents tab with the Document source My computer.

    

    After you attach your documents, click Create. The Mail module opens in Document with your attachments included.

  • To add an attachment in Document, click Create. The Mail module in Document opens. You can attach files from Document in the Attachments section of the Mail page.

    

    The Attach documents dialog box opens, where you can search for the document. After you select a document, click Save.

  • To send mail without an attachment, click Create. The Mail module in Document opens.

  The To and Subject fields on the Mail module document page are required. After you have completed the fields and added documents, if needed, click Send. A summary page opens in Document, where you can edit links and notes. The mail is added in Document.

  After you close the Document window you are prompted to add the mail as a supporting document in Change. The document type defaults to Correspondence, but you can change it. Click Save to save it to the Supporting documents page.

• Upload document to Document – You can now upload a saved supporting document to Document. This feature eliminates extra steps of having to load the document in Document then link it back in Change. Read more Watch video

  You can now upload a document to the Document module directly from Change, eliminating extra steps. To upload the document, select it and then click the Upload icon. You are taken to the upload screen in the Documents module of Document. Follow the procedures as you would in Documents module for adding a document. The document you selected in Change is already attached, but you can add more documents. Click Save and Transmit. The document is now saved in the Document Documents module. After you close the Document window, Change shows the Edit supporting document dialog box. The file link is replaced with the document link from Document. Click Save. The Supporting Documents register refreshes with the file link to the Documents module. The Document source is replaced with InEight Document, and the External document type and status are now populated.

  Only documents added via My Computer are allowed to be uploaded

• Create a task –You can create and assign tasks to be completed in an issue, PCO, or CCO using InEight Compliance. Read more Watch video

  You can now create and assign tasks within any Issue/PCO/CCO using InEight Compliance.

  Set up

  Existing customers, when implementing Release 21.12, now have a default Compliance task template already in place. If you want a different template, refer to the Compliance documentation for information about how to create and register a new template.

  New customers must refer to the Compliance documentation for information about how to set up a standard task template.

  Permissions

  Before tasks can be created, you must have permissions to create tasks in Compliance and a task template. You must configure permissions in Compliance for all Change users who are allowed to create tasks. The permissions include the following:

  • The project or organization
  • The category for the template the organization uses
  • The reporter role for creating and editing tasks

  Template

  The tasks you create in Change follow the default task template. An administrator can create a different template in Compliance (Compliance > Change (Module) > Templates manager > Create new task). The template task must have the following:

  • Task title
  • Change ID
  • Description
  • Task person
  • Due date
  • Assign button
  • Notes
  • Complete button
  • Cancel button

  You must publish the template before it can be used in Change. Refer to the Compliance topics for more information about setting up templates.

  Change configuration

  The template must be selected in the organization settings (organization Settings > Change >Configurations > Task type setup). The selected template is used for all projects in the organization.

  

  Create a task in an issue, PCO, or CCO

  To create a task, open the Actions menu on the Issue, PCO, or CCO Details page, and then select Create Task. The task templates opens in a Compliance window. You can then fill out the fields. After you enter the required fields, click Assign. The person named as the task person receives an email notification. The task person can use the link in the email to go directly to the task in Compliance. They can either complete the task or cancel the task.

  Upon creation of a task, the task is loaded to the Task details section of the issue, PCO, or CCO and the task log.

  If there is no task template defined at the organization level, the Action is disabled, and you must add the template. Click the Setup task type (gear) icon to go to the Task Type setup page in the organization settings (organization Settings > Configurations > Task type setup), where you can select the task template. After you save, the Create Task action is enabled.

  Track project tasks

  After work has started on a task, it is available in the Task log.

  

  The task log shows all tasks that have been assigned on the project. Values in the ID column are links to the originating issue, PCO, or CCO. TheTask title is a link to the task in Compliance. The Due date and State columns highlight tasks that are past due in red.

  The number next to the tab title shows the number of tasks that are pending or overdue.

  You also can view tasks from the issue, PCO, or CCO in the Task section of the Additional details. The Task heading shows the number of tasks that are pending or overdue. When you expand the section, you can view the task title, task person, due date, and state.

  

• Weather enhancement – An option to create a historical weather record for up to one week has been added to the Weather section of Additional details on the Issue details page. You can add the historical weather record as a supporting document. Icons have also been added to the section heading, so you can see the Weather condition at a glance without expanding the section. Read more

  The historical weather record uses the longitude and latitude from the project details to give a precise report of the weather conditions for the specified period. You can specify a start date that is up to one year before the current date. The end date can be up to seven days after the start date.

  To create a historical weather record, open the Weather section under the Additional details on the Issue Details page, and then click Create historical weather record .

  

  In the dialog box, enter a start date and time and an end date and time, and then click Search. Change makes a call to a weather API, and then returns hourly weather conditions for each hour. The conditions include the temperature, weather condition, wind speed in meters per second and miles per hour, and precipitation. If you want to create a supporting document of the weather record, click Create. Change creates a PDF and places it in the Supporting documents tab for the issue.

• Pricing updates – You can no longer associate closed contracts and vendor change orders to issues, PCOs, and CCOs on the Pricing tab. Read more

  The Associate to VCO icon in the pricing item is now disabled when the vendor contract is closed, and you can no longer edit the pricing item.

  

• Issue log update – The Approval status column has been added to the Issue log, so you can see the approval status at a glance without having to open the issue.

• Row density settings – You can now choose the row density for all registers in Change. Read more

  You can choose from relaxed, narrow, or tight density. The default is narrow.

  

• Contract and Forecast milestone dates – Contract and Forecast fields for Extension/reductions, Revised duration, and Revised completion date are now sent to Project details page.

• Change template Market assignment – Organization-level templates now default to On in a project when neither the organization template nor the project have a market assigned. If the organization-level template has a market added, it is automatically turned off for all projects that do not have a matching market in the Project details but stays turned on for any project with a matching market. If the project adds a market to the Project details, any organization-level Change writer templates that were set to Off are automatically set to On.

• New general and collection table tags – New tags for Company legal name, Markets, and Issue/PCO/CCO Pricing summary have been added to the General tags. The new Issue/PCO/CCO Pricing summary tags generate the entire pricing summary table. Tags for creating tasks in Change have been added to the Collection table tags.

• Cost categories for new cost items – After a CCO is executed, the cost item cost category in Control for new cost items added in Change corresponds to the cost pricing section in Change to which the item was assigned. If there are any man-hours on the new cost item, that portion of the value is allocated to the Labor cost category, and the remaining value to the category mapped to the cost pricing selected.

• VCO creation in InEight Contract – You can now associate a vendor pricing item to an existing VCO in Contract, or you can create a new VCO. Previously, the only way to associate a pricing item to a VCO was in Contract. Vendor pricing information has also been enhanced to show whether multiple vendor change orders (VCOs) have been associated to it. Read more

  You can now associate a vendor pricing item on the Pricing summary tab from the Edit Vendor and pricing information slide-out panel to a VCO in Contract. Previously the only way to associate a pricing item to a VCO was in Contract.

  If the pricing item is not yet associated to a VCO, the Associate pricing item icon in the Add or Edit Vendor and pricing information slide-out panel is enabled.

  

  Click the icon to associate the pricing item to a VCO. The Associate to Vendor Change order dialog box opens. You can choose to associate the pricing item to a new or existing VCO.

  

  At the issue level, all pricing items get associated to the VCO. Pricing items added at the PCO and CCO levels can be associated individually to a VCO.

  The Edit Vendor and pricing information slide-out panel on the Pricing tab has been updated to include information about Contract VCOs that are associated with the vendor.

  

  The heading section of the slide-out panel shows the Vendor change order ID, status, and back charge ID for any VCOs assigned to the vendor. You can click the vendor change order ID to go directly to the VCO in Contract. If there are multiple VCO s associated with the vendor, the Vendor change order ID header field is set to Multiple. Click the arrow to see a list of all VCOs associated to the vendor.

  The following columns have been added for VCOs to the Pricing item grid:

  • ID – Name

  • Vendor Change order ID – Description

  • Status

  • Responsible party

  • Back charge ID

  If the vendor change order ID field is empty, a VCO has not yet been created.

• New issue workflow – You can now add multiple steps for a new issue workflow. Previously, the workflow for a new issue was a single step for users or roles. The new issue log has been also been enhanced. Read more

  The New issue approval setup tab in the project settings now lets you add steps. This is consistent with other workflows in Change. For each step you can assign users or roles.

  

  Changes have also been made to the issue logs. The Pending issue log is now the New issue log, regardless of whether workflow is turned on. Pending issues have the value Pending as the Issue ID. If you have at least one step in the workflow, then any new issues go into In approval status, and an email notification is sent to the approver. Approvals of pending issues now have to be approved from the Action items tab.

  New issue summary emails are no longer sent.

  If you add an issue from a VCO in Contract and the project has new approval workflow configured, the issue automatically goes to the New Issue log in Change with a Issue ID of Pending. It does not get an issue ID until it is approved. Approvers get an email notification to approve or reject the issue.

  If you do not have a new issue approval workflow configured, the issue goes to both the New Issue log and Issue log with an issue status of New and an Issue approval status of Not applicable.

  If workflow was turned on prior to release 21.10, any issue that was pending prior to release 21.10, is now in the New issue log with a status of Pending, but no email notifications are sent. The items are in the Action Items tab, and approvers can approve the issues from there.

• Issue, PCO, and CCO Correspondence – The Correspondence subsection has been added to the Additional details section. This section lets you track the supporting documents without having to go to the Supporting documents tab and search for the document types. Read more

  The correspondence section shows supporting documents that need to be attached.

  You can track the following correspondence for an issue:

  • Issue Date client notified

  • Issue Date price to client

  You can track the following correspondence for a PCO:

  • PCO Date client notified

  • PCO Date price to client

  • PCO Client approval date

  • Executed change order

  • Document date

  You can track the following correspondence for a CCO:

  • CCO date client notified

  • CCO date price to client

  • Executed change order

  • Document date

  The following image shows the Correspondence section in a CCO.

  

  Information icons show you the specific supporting document that must be attached to populate the date. You add the document on the Supporting documents page Change uses the Document type and Subtype of the supporting document and adds the link and date automatically. The PCO Client approval date field on the PCO Details tab and the Executed lets you enter a date.

• Revenue category in Additional details – The Revenue category section has been added to the Additional details sections of the Issue details, PCO details, and CCO details. Read more

  New fields include Revenue category, Revenue change status, and Probability percentage.

  

• Issue/PCO/CCO navigation – You can now go from one Issue, PCO, or CCO to another Issue, PCO, or CCO from the Details page. This provides quick navigation between issues, so you do not have to go back to the log to get to another issue. Watch video

• Create new Plug cost item – You can now create a new Plug cost item from the Cost item pricing tab. Previously you could only add an existing Plug cost item. Read more

  You now have the option to add a new Plug cost item from the Cost item pricing tab. To add a new cost item, click the Add icon on the Cost item pricing tab, and then select Add new cost item. The New cost item slide-out panel opens.

  The Cost source field is set to Plug. You can add values to the fields on the Details tab only. The Unit rate driver field is set to Manual and cannot be changed. After the item is applied and saved, Change sends it to InEight Control. The WBS phase code is set to New. After the CCO is executed, you can see the newly created cost item in the Control contract adjustment. When the contract adjustment is approved in Control, a WBS is assigned. You can see the WBS phase code in the CBS and the WBS number is reflected in the executed issue cost item pricing.

• Cost item pricing enhancements – You can now select and resize columns in the Add cost item pricing dialog box. There have also been improvements to the cost item pricing grid and collection tables. Read more

  Cost item pricing columns

  The first three columns in the Cost item pricing (Cost item description, WBS phase code, and the Labor check box) are now locked for horizonal scrollilng. This lets you keep your place visually as you scroll through the columns on each line. You cannot remove the first three columns from the column chooser.

  Add cost item pricing enhancement

  The Add cost item pricing dialog box now has column choosers, so you can select the columns that help you identify cost items. You also can resize the columns in the dialog box, so you can see lengthy descriptions and remove the columns that you do not want to see. If all of the columns do not fit in the dialog box, you can scroll to see columns.

  Cost item pricing collection table

  You can now include a cost item pricing collection table in a Change document, so you can re-create the cost item pricing tab. The cost item pricing collection table tags have their own tab in the Collection table tags list.

• Vendor proposal supporting documents – When you add a supporting document type of Proposal and subtype From vendor, you now can select a vendor from a list of all contracts on the issue. This lets you specify which contract the supporting document is related to and gives visibility into which contract to associate the proposal to. Read more

  The New supporting document dialog box in the image below shows the Document type Proposal and the Subtype From vendor. You can select a Vendor from the Vendor drop-down list.

  

• Workflow approval tile – A new tile has been added to the user landing page for Workflow pending approvals. The tile lets you see the project ID, workflow type, PCO or CCO ID and description, and value.

• Log density enhancements – You can now adjust the row density on the Issue log, PCO log, and CCO log. Click the Row density icon in the toolbar to select from Relaxed, Narrow, or Tight density.

• New template tags – Tags for Company legal name and Markets have been added to the general tag list. These fields are in the InEight Platform project details.

• Issue log bulk edit – You can now perform a bulk edit on the Revenue category field.

• Change templates – New organization templates now default to Off for Project use. These templates can be manually switched to On in individual projects.

• PCO and CCO ID customization – You can now configure a prefix and starting number for your PCO and CCO numbering schemes to ensure consistent numbering. Read more

  At the organization level, you can set a standard prefix and starting number using the ID customization configuration list (Settings > Configurations > ID customization).

  

  The Generate PCO/CCO IDs sequentially setting indicates whether Change generates numbers sequentially. When set to No, you can enter any number as the PCO or CCO ID. When set to Yes, you can specify a prefix and a starting number in their respective fields.

  You can enforce the numbering scheme at the project level by ensuring that the Allow projects to edit settings check box is unchecked. When unchecked, the organization numbering ID is carried to the project level and cannot be changed. When the box is checked, the organization level settings are defaulted at the project level, but the project has the ability to override. You can then use the ID customization list at the project level (Settings > Configurations > ID customization) to configure the prefix and starting number for a project.

  After you establish a starting number, and the first PCO or CCO is created, you cannot change the starting number at the project level. You can change the prefix.

  If projects are allowed to edit the ID, you can override the organization level numbering at the project level by setting the Generate Potential Change order IDs sequentially field to Yes. If set to No, IDs will function as free text.

  

  When the Generate Potential Change order IDs sequentially field is set to Yes, the Allow users to edit generated IDs field is shown. Set this field to Yes to allow users to edit the generated IDs when creating a PCO or CCO or for a PCO or CCO that has been generated.

  When you convert an issue to a PCO or CCO, you get a choice between starting a new PCO or CCO or using an existing one.

  

  When you choose to use a new PCO or CCO, The PCO ID or CCO ID field uses the numbering scheme from the settings, but you can edit it. If the Allow users to edit generated IDs field is set to No, you cannot edit the number when you convert to a new PCO or CCO.

  When changes are made at the organization level, they take effect in the next new project (existing projects have already inherited the old scheme).

• Issue/PCO/CCO details enhancements – The layouts have been updated on the Issue, PCO, and CCO Details pages for easier viewing. A new section for custom fields has been added at the PCO and CCO levels, and Forecast days have been added to the Schedule impact sections. You can now define the impact on both contract and internal schedules. PCO and CCO change order term fields have been enhanced added to let you define additional contract terms associated to the change . Read more

  A new Additional details section has been added to the Issue, PCO, and CCO Details pages. All information has been moved to “accordion” sections that expand and collapse so you can find the fields without scrolling.

  On the Issue Details page the Shedule impact, Client notification (now called correspondence), Request for information, Weather, Field information, Design information, and Split issues sections have moved to the new Additional details section.

  

  New subsections for PCOs and CCOs include Schedule impact, Request for information and Custom fields.

  For PCOs, the Schedule impact subsection includes the Time extension field, which moved from another location on the page. A new column has been added so you can add the schedule impact to the forecast days.

  

  For CCOs, the Schedule impact section includes the Approved time extension field, Requested days, and Approved days, which were moved from another location on the page. A new column has been added for forecast time. Upon execution of CCO, these delay days will be shown in the Project summary slide-out panel.

  

  Sections for change order terms have been added to the PCO details and CCO details pages. You can use the terms sections to add up to two terms. The fields are free-text and allow formatting.

  

• Expand multiline text boxes – You can now expand the size of multiline text box for selected fields, so it is easier to enter and read information. Read more

  The Maximize icon in the Description of change and each Potential change order term text box lets you expand the text area to the size of the whole page so you can easily add your text.

  

  The expand icon changes to the collapse icon when expanded. Use the collapse icon to collapse the text box when you are done.

  

• Pricing tab miscellaneous enhancements – Improvements have been made to CBS code colors, the Cost source column, and inconsistent pricing warnings. Read more

  If your system is configured for manual syncing (that is, the automatic updates in the project settings configurations are set to Off) and you make a change to the pricing at any level, the Pricing pages at the other levels show a banner warning that the updated values are not reflected at all levels. For example, if a pricing change is made at the issue level, the banner shows at the PCO and CCO levels. To update values, go to the Actions menu. Then select whether to push values down or pull values up.

  

• Cost item pricing enhancements – To improve productivity, you can now edit cost item Plug fields and export the cost item grid to Microsoft Excel. Read more

  General enhancements

  When you add an existing cost item, the CBS codes on the Add cost item pricing page now use the same colors as InEight Control. Colors are dimmed after they have been selected.

  

  A column for Cost source has been added to the Cost item pricing grid and is now available in the column chooser. The value Plug or Detail is shown based on existing cost item in Control.

  Export cost item grid to Microsoft Excel

  Cost item pricing is now included when you export pricing. The Cost item pricing tab has been added to the export Excel spreadsheet.

  You can now do the following to increase productivity and flexibility.

  Edit existing Plug cost item

  You can now edit the following fields when the cost source from Control is Plug: Adjusted cost, Unit cost, Adjusted Mhrs, Mhrs/Unit, Unit/Mhr. These fields are available for edit in the Edit cost item slide-out panel only when the cost source is Plug. These fields can only be modified in the Edit cost item slide-out panel. The Adjusted CB Qty column can still be edited from the Cost item pricing grid.

  

  The fields work interactively. If you change the value of a field, Change calculates the values of the related fields.

  If no quantity has been entered, you can enter an adjusted cost. The Mhrs, Mhrs/Unit, and Unit/Mhr fields are disabled. After you enter an Adjusted CB Qty, all fields are enabled. Adjusting the man-hours maintains the Labor cost/Mhr from Control to calculate the overall adjusted cost. After you make a change, the Unit rate driver field changes to Manual. The manual changes are saved as an additional unit rate driver when they are applied and saved to the grid.

  Upon execution of CCO, Control consumes the updated quantity, cost, and man-hours in the Contract adjustment.

• Updated field names – The following fields have new names: Ball in court is now Responsible party, Ball in court person is now Responsible party person, Client CO is now CCO, Potential CO is now PCO, and Agreed CO is now Agreed. The CCO and PCO fields are now available in the custom labels settings. The custom labels lists have been reordered to make them more user friendly.

• Workflow enhancements – You can now copy a workflow from supporting document to supporting document. You also can now approve or reject multiple items at the same time from the Action items tab. A new workflow wizard with options to include text and to link supporting documents for email review has been added. Read more

  The multiple select enhancement lets you select multiple items on your Action items tab to approve or reject. If you reject multiple items and enter a note, the note is attached to all items selected. CCO execution approval is not available for multiselection approval.

  The Workflow wizard now has three steps. The first step is the existing workflow step where you see the approval steps. The second step lets you enter and format a customized message for the workflow email notification.

  

  The third step lets you add supporting documents. Any supporting document that is associated with the PCO or CCO can be added.

  

  The steps to customize the email and to add supporting documents are optional.

  The email notification has been updated to include the links for the supporting documents. The recipient can click a link to download the document.

• Issue log bulk edit – You can now select multiple items on the Issue log and then edit selected columns for those items at the same time. Read more

  The following columns are available for bulk edit:

  • Issue start date

  • Source/Cause

  • Change condition

  • Scope

  • Allowance category

  • Assigned to

  • Construction area

  • Daily plan ID of impacted work

  • Field contact

  • Has work started

  • Does this impact schedule

  • Delay days

  • Have you verbally notified the Client

  • Issue custom fields 1-4

  • Pricing status

  • Proposal status

  • Responsible party person

  To edit fields in bulk, select issues on the Issue log, and then click the Edit icon. The new Bulk Edit dialog box opens. You can then select a column and enter the value. To add another field, click the Add icon. You can select up to five columns at a time. The value of thte field overrides any information currently in the field. Click Save to update the selected fields.

  

• Project contract summary updates – Forecast information has been added to the Milestones section of the Project contract summary slide-out window and the Change milestones tile on your dashboard. Read more

  Click the View project contract summary icon to see the Project contract summary slide-out window. The forecast information columns have been added to the milestones.

  

  The Forecast start date, Duration, and Completion date must be entered on the Project details page, similar to Contract dates. Extension/Reductions are updated and populated from the CCO schedule impact dates upon execution of the CCO, and the revised completion date is updated accordingly. The Estimated float is the difference between the Forecasted revised completion date and the Contract revised completion date.

  Information icons provide the formula for the Completion date and the Revised completion date.

  The Change milestones tile on the Project home page has also been updated.

  

• Change writer enhancements – You can now use tags in the header and footer of a document template.

• Change writer tag additions and updates – New general tags have been added for Forecast days, contract terms and custom lists. Other tags have been updated. Read more

  The following tags have been added to all templates

  • <<Forecast start date>>

  • <<Forecast start date-words>>

  • <<Forecast duration>>

  • <<Forecast completion date>>

  • <<Forecast completion date-words>>

  • <<Forecasted extension/reductions>>

  • <<Forecasted extension/reductions-words>>

  • <<Forecast revised duration>>

  • <<Forecast revised completion date>>

  • <<Forecast revised completion date-in words>>

  The following tags have been updated for all templates:

  Old tag	New tag
  <<Contract number>>	<<Project contract number>>
  <<Date project started>>	<<Project contract start date>>
  <<Date project started-words>>	<<Project contract start date-words>>
  <<Original contract completion date>>	<<Project contract completion date>>
  <<Original contract completion date-words>>	<<Project contract completion date-words>>
  <<Original duration>>	<<Project contract duration>>
  <<Original project value>>	<<Project original contract amount>>
  <<Extended/rejected duration>>	<<Contract extension/reductions>>
  <<Revised contract completion days>>	<<Contract revised duration>>
  <<Revised contract completion date>>	<<Contract revised completion date>>
  <<Revised contract completion date-words>>	<<Contract revised completion date-in words>>
  <<Prime contract: Owner: First Name>>	<<Project contact: Owner: First Name>>
  <<Prime contract: Owner: Last Name>>	<<Project contact: Owner: Last Name>>
  <<Prime contract: Owner: Company>>	<<Project contact: Owner: Company>>
  <<Prime contract: Owner: Email>>	<<Project contact: Owner: Email>>
  <<Prime contract: Owner: Contact type>>	<<Project contact: Owner: Contact type>>
  <<Prime contract: Owner: Department>>	<<Project contact: Owner: Department>>
  <<Prime contract: Owner: Position>>	<<Project contact: Owner: Position>>
  <<Prime contract: Owner: Title>>	<<Project contact: Owner: Title>>
  <<Prime contract: Owner: Office number>>	<<Project contact: Owner: Office number>>
  <<Prime contract: Owner: Mobile number>>	<<Project contact: Owner: Mobile number>>
  <<Prime contract: Owner: Fax number>>	<<Project contact: Owner: Fax number>>
  <<Prime contract: Owner: Address 1>>	<<Project contact: Owner: Address 1>>
  <<Prime contract: Owner: Address 2>>	<<Project contact: Owner: Address 2>>
  <<Prime contract: Owner: Country/Region>>	<<Project contact: Owner: Country/Region>>
  <<Prime contract: Owner: City>>	<<Project contact: Owner: City>>
  <<Prime contract: Owner: State>>	<<Project contact: Owner: State>>
  <<Prime contract: Owner: Postal code>>	<<Project contact: Owner: Postal code>>
  <<Prime contract: Designer: First Name>>	<<Project contact: Designer: First Name>>
  <<Prime contract: Designer: Last Name>>	<<Project contact: Designer: Last Name>>
  <<Prime contract: Designer: Company>>	<<Project contact: Designer: Company>>
  <<Prime contract: Designer: Email>>	<<Project contact: Designer: Email>>
  <<Prime contract: Designer: Contact type>>	<<Project contact: Designer: Contact type>>
  <<Prime contract: Designer: Department>>	<<Project contact: Designer: Department>>
  <<Prime contract: Designer: Position>>	<<Project contact: Designer: Position>>
  <<Prime contract: Designer: Title>>	<<Project contact: Designer: Title>>
  <<Prime contract: Designer: Office number>>	<<Project contact: Designer: Office number>>
  <<Prime contract: Designer: Mobile number>>	<<Project contact: Designer: Mobile number>>
  <<Prime contract: Designer: Fax number>>	<<Project contact: Designer: Fax number>>
  <<Prime contract: Designer: Address 1>>	<<Project contact: Designer: Address 1>>
  <<Prime contract: Designer: Address 2>>	<<Project contact: Designer: Address 2>>
  <<Prime contract: Designer: Country/Region>>	<<Project contact: Designer: Country/Region>>
  <<Prime contract: Designer: City>>	<<Project contact: Designer: City>>
  <<Prime contract: Designer: State>>	<<Project contact: Designer: State>>
  <<Prime contract: Designer: Postal code>>	<<Project contact: Designer: Postal code>>
  <<Prime contract: Contact 1: First Name>>	<<Project contact: Contact 1: First Name>>
  <<Prime contract: Contact 1: Last Name>>	<<Project contact: Contact 1: Last Name>>
  <<Prime contract: Contact 1: Company>>	<<Project contact: Contact 1: Company>>
  <<Prime contract: Contact 1: Email>>	<<Project contact: Contact 1: Email>>
  <<Prime contract: Contact 1: Contact type>>	<<Project contact: Contact 1: Contact type>>
  <<Prime contract: Contact 1: Department>>	<<Project contact: Contact 1: Department>>
  <<Prime contract: Contact 1: Position>>	<<Project contact: Contact 1: Position>>
  <<Prime contract: Contact 1: Title>>	<<Project contact: Contact 1: Title>>
  <<Prime contract: Contact 1: Office number>>	<<Project contact: Contact 1: Office number>>
  <<Prime contract: Contact 1: Mobile number>>	<<Project contact: Contact 1: Mobile number>>
  <<Prime contract: Contact 1: Fax number>>	<<Project contact: Contact 1: Fax number>>
  <<Prime contract: Contact 1: Address 1>>	<<Project contact: Contact 1: Address 1>>
  <<Prime contract: Contact 1: Address 2>>	<<Project contact: Contact 1: Address 2>>
  <<Prime contract: Contact 1: Country/Region>>	<<Project contact: Contact 1: Country/Region>>
  <<Prime contract: Contact 1: City>>	<<Project contact: Contact 1: City>>
  <<Prime contract: Contact 1: State>>	<<Project contact: Contact 1: State>>
  <<Prime contract: Contact 1: Postal code>>	<<Project contact: Contact 1: Postal code>>
  <<Prime contract: Contact 2: First Name>>	<<Project contact: Contact 2: First Name>>
  <<Prime contract: Contact 2: Last Name>>	<<Project contact: Contact 2: Last Name>>
  <<Prime contract: Contact 2: Company>>	<<Project contact: Contact 2: Company>>
  <<Prime contract: Contact 2: Email>>	<<Project contact: Contact 2: Email>>
  <<Prime contract: Contact 2: Contact type>>	<<Project contact: Contact 2: Contact type>>
  <<Prime contract: Contact 2: Department>>	<<Project contact: Contact 2: Department>>
  <<Prime contract: Contact 2: Position>>	<<Project contact: Contact 2: Position>>
  <<Prime contract: Contact 2: Title>>	<<Project contact: Contact 2: Title>>
  <<Prime contract: Contact 2: Office number>>	<<Project contact: Contact 2: Office number>>
  <<Prime contract: Contact 2: Mobile number>>	<<Project contact: Contact 2: Mobile number>>
  <<Prime contract: Contact 2: Fax number>>	<<Project contact: Contact 2: Fax number>>
  <<Prime contract: Contact 2: Address 1>>	<<Project contact: Contact 2: Address 1>>
  <<Prime contract: Contact 2: Address 2>>	<<Project contact: Contact 2: Address 2>>
  <<Prime contract: Contact 2: Country/Region>>	<<Project contact: Contact 2: Country/Region>>
  <<Prime contract: Contact 2: City>>	<<Project contact: Contact 2: City>>
  <<Prime contract: Contact 2: State>>	<<Project contact: Contact 2: State>>
  <<Prime contract: Contact 2: Postal code>>	<<Project contact: Contact 2: Postal code>>
  <<Prime contract: Contact 3: First Name>>	<<Project contact: Contact 3: First Name>>
  <<Prime contract: Contact 3: Last Name>>	<<Project contact: Contact 3: Last Name>>
  <<Prime contract: Contact 3: Company>>	<<Project contact: Contact 3: Company>>
  <<Prime contract: Contact 3: Email>>	<<Project contact: Contact 3: Email>>
  <<Prime contract: Contact 3: Contact type>>	<<Project contact: Contact 3: Contact type>>
  <<Prime contract: Contact 3: Department>>	<<Project contact: Contact 3: Department>>
  <<Prime contract: Contact 3: Position>>	<<Project contact: Contact 3: Position>>
  <<Prime contract: Contact 3: Title>>	<<Project contact: Contact 3: Title>>
  <<Prime contract: Contact 3: Office number>>	<<Project contact: Contact 3: Office number>>
  <<Prime contract: Contact 3: Mobile number>>	<<Project contact: Contact 3: Mobile number>>
  <<Prime contract: Contact 3: Fax number>>	<<Project contact: Contact 3: Fax number>>
  <<Prime contract: Contact 3: Address 1>>	<<Project contact: Contact 3: Address 1>>
  <<Prime contract: Contact 3: Address 2>>	<<Project contact: Contact 3: Address 2>>
  <<Prime contract: Contact 3: Country/Region>>	<<Project contact: Contact 3: Country/Region>>
  <<Prime contract: Contact 3: City>>	<<Project contact: Contact 3: City>>
  <<Prime contract: Contact 3: State>>	<<Project contact: Contact 3: State>>
  <<Prime contract: Contact 3: Postal code>>	<<Project contact: Contact 3: Postal code>>
  <<Prime contract: Contact 4: First Name>>	<<Project contact: Contact 4: First Name>>
  <<Prime contract: Contact 4: Last Name>>	<<Project contact: Contact 4: Last Name>>
  <<Prime contract: Contact 4: Company>>	<<Project contact: Contact 4: Company>>
  <<Prime contract: Contact 4: Email>>	<<Project contact: Contact 4: Email>>
  <<Prime contract: Contact 4: Contact type>>	<<Project contact: Contact 4: Contact type>>
  <<Prime contract: Contact 4: Department>>	<<Project contact: Contact 4: Department>>
  <<Prime contract: Contact 4: Position>>	<<Project contact: Contact 4: Position>>
  <<Prime contract: Contact 4: Title>>	<<Project contact: Contact 4: Title>>
  <<Prime contract: Contact 4: Office number>>	<<Project contact: Contact 4: Office number>>
  <<Prime contract: Contact 4: Mobile number>>	<<Project contact: Contact 4: Mobile number>>
  <<Prime contract: Contact 4: Fax number>>	<<Project contact: Contact 4: Fax number>>
  <<Prime contract: Contact 4: Address 1>>	<<Project contact: Contact 4: Address 1>>
  <<Prime contract: Contact 4: Address 2>>	<<Project contact: Contact 4: Address 2>>
  <<Prime contract: Contact 4: Country/Region>>	<<Project contact: Contact 4: Country/Region>>
  <<Prime contract: Contact 4: City>>	<<Project contact: Contact 4: City>>
  <<Prime contract: Contact 4: State>>	<<Project contact: Contact 4: State>>
  <<Prime contract: Contact 4: Postal code>>	<<Project contact: Contact 4: Postal code>>

  The following tags have been added to the issue template:

  • <<Issue responsible party person>>

  • <<Issue custom list 1>>

  • <<Issue custom list 2>>

  The following tags have been updated for Issue templates:

  Old tag	New tag
  <<Issue ball in court>>	<<Issue responsible party>>
  <<Issue executed CO document date>>	<<Issue executed change order document date>>
  <<Issue executed CO document date-words>>	<<Issue executed change order document date-words>>

  The following tags have been added to the PCO template:

  • <<PCO contract term 1>>

  • <<PCO contract term 2>>

  • <<PCO forecast time extension>>

  • <<PCO responsible party person>>

  • <<PCO custom list 1>>

  • <<PCO custom list 2>>

  The following tags have been updated for PCO templates:

  Old tag	New tag
  <<PCO contract requested time extension>>	<<PCO time extension days requested>>
  <<PCO ball in court>>	<<PCO responsible party>>
  <<PCO executed CO document date>>	<<PCO executed change order document date>>
  <<PCO executed CO document date-words>>	<<PCO executed change order document date-words>>

  The following tags have been added to the CCO template:

  • <<CCO contract term 1>>

  • <<CCO contract term 2>>

  • <<CCO requested contract time extension>>

  • <<CCO requested forecast time extension>>

  • <<CCO approved forecast time extension>>

  • <<CCO responsible party person>>

  • <<CCO custom list 1>>

  • <<CCO custom list 2>>

  The following tags have been updated for CCO templates

  Old tag	New tag
  Old tag	New tag
  <<CCO approved time extension days>>	<<CCO approved contract time extension>>
  <<Client CO execution status>>	<<CCO execution status>>
  <<CCO ball in court>>	<<CCO responsible party>>
  <<CCO executed CO document date>>	<<CCO executed change order document date>>
  <<CCO executed CO document date-words>>	<<CCO executed change order document date-words>>

• Add notes enhancements – The Add notes icon has been updated with a new look to be consistent among products. You can now see all notes as the issue moves up to a PCO and then CCO. The Add notes function on the Supporting documents page has been enhanced to include a supporting documents subtab in the notes. This subtab lets you add notes that are specific to the documents and you no longer have to edit the supporting documents to see the supporting document notes. Read more

  The new notes icon is shown below.

  

  When you add notes for supporting documents, they are now visible in the Supporting documents notes subtab as you move from an issue to a PCO and then CCO.

  

  Supporting document approval or rejection notes from the issue level are also visible in the notes at the PCO and CCO levels.

  The Notes column has been removed from the Issue, PCO, and CCO logs. Now you can highlight a row and click the Notes icon, to view the notes and add new ones with a single click.

  Notes are now automatically included when you export.

• Change writer – Watermarks and other editing controls have been added to the organization level template. A market attribute setting has been added to template details. You can now generate and merge multiple documents in PDF. Read more

  The Change Templates tab in the organization settings is now divided into subtabs. The Templates subtab contains the templates register. From here you can add or edit template details. The Market attribute has been added to the template details. This setting lets you assign one or more markets to the template type to provide additional ways to filter templates.

  

  The Template settings subtab lets you configure characteristics for templates at the organization level.

  

  The Allow users to edit the document during generation setting indicates whether a user can edit the Review fields tab during document generation.

  The Require watermark stamp upon document generation setting indicates whether users must include one of the defined watermarks when generating a contract document. The Watermark stamp section lets you specify the watermark text and layout. All watermarks are semitransparent in opacity. Change automatically removes the watermark when the document is approved.

  The Output as PDF only setting indicates whether you can generate a PDF only. When set to Yes, you cannot generate a Microsoft Word or Excel document, and any changes to the document must be made in Change.

  The Change template details section has been added to the first page of the Generate change document wizard.

  

  The Generate document as field lets you select whether to generate the document as a merged PDF or as individual documents. When set to individual documents, the Generate document file type as field shows in the details. If the Output as PDF only setting is set to Yes, the Generate document file type as field defaults to Download as PDF and cannot be changed. If the Output as PDF only setting is set to No, you can choose to download as a PDF or as a the template file type (that is, Word or Excel).

  The Save in supporting documents field is now in the Change template details section. When you save a document in supporting documents, you can now specify the name of the file in the Name of document file field. If you are generating multiple documents, the first one uses the specified name and the subsequent document use the name plus a number. If the field is blank, Change names the file with the issue, PCO, or CCO ID, template name, and a date and time stamp.

  You also can select a watermark stamp from the Contract template details area. If the Require watermark stamp on the document generation setting is Yes, you must select one of the defined watermarks before you can click Next.

• Change writer tag additions – New general tags have been added for weather, schedule impact, project information, and project details. Additional tags have been added to the Issue, PCO, and CCO templates to support cost item pricing. Read more

  The following tags have been added to the issue template:

  • <<Schedule impact comments>>

  • <<Weather>>

  • <<Conversation summary>>

  • <<Issue billing rate markup>>

  • <<Issue deductions>>

  • <<Issue net value>>

  The following tags have been added to the PCO template:

  • <<PCO billing rate markup>>

  • <<PCO deductions>>

  • <<PCO net value>>

  The following tags have been added to the CCO template:

  • <<CCO billing rate markup>>

  • <<CCO deductions>>

  • <<CCO net value>>

• Date in words tags – New tags have been added to let you specify the date in words, such as Wednesday September 1, 2021. Read more

  The following new tags were added:

  • <<Project contract date-words>>

  • <<Prime contract project start date-Words>>

  • <<Original contract completion date-Words>>

  • <<Contract effective date-Words>>

  • <<Vendor change order effective date-Words>>

• Collection table additions – New collection tags have been added for supporting documents and a collection table for notes. Read more

  The following collection table tags have been added for the supporting document approvers:

  • <<Supporting documents: Approval status>>

  • <<Supporting documents: Approved/Rejected by>>

  • <<Supporting documents: Approved/Rejected on>>

  • <<Supporting documents: Approved/Rejected on - words>>

• Custom fields – Issue, PCO, and CCO custom lists configuration have moved from InEight Platform to Change project settings. New custom lists 1-2 for issue, PCO, and CCO have also been added. Read more

  Configure custom lists from Project > Settings > Change > Configurations > Custom lists. The custom list configuration lets you select values for the Custom list drop-down fields at the issue, PCO, and CCO levels. Previously these fields were defined in the Platform project settings (General > Custom lists).

  The custom fields and lists are available in the Column options on the issue, PCO, and CCO logs.

  

  After a custom field or list has been added, you can enter information or choose a list value directly from the log.

  

  The custom fields and lists are not available on the Issue, PCO, or CCO Details pages.

  You can use custom labels (Project > Settings > Change > Custom Labels) to customize the names of the fields and lists.

  Existing data from custom fields 1 - 2 migrate to custom lists 1 - 2 for issue, PCO, and CCO.

• Organization workflow user assignments at the project level – You can now assign a user as required at the organization level when you edit a threshold at the project level. This view lets you can see the whole organization step at one time. Read more

  When a threshold has a project-level step and one or more organization-level steps that must be edited, you can now edit the organization-level steps when you edit the project-level step.

  

  Organization steps that require editing are marked with a red triangle. When you edit a project-level step in the same threshold, the organization-level steps are now available in the Edit approval slide-out panel.

  If there are no project-level steps, you can edit the organization-level steps individually.

• Document approval workflow – You can now establish approval workflows by document type at an organization, project, or change order level. Read more

  You can set up document approval for each document type by contract type. At the organization or project level, go to Settings > Change > Workflow Assignments > Document approval setup.

  

  At the change order level, you set up document approval workflows on the Document approval page of the Workflow Assignments tab.

  

  At all three levels, you can select a document type and then select the approver roles. At the organization level, approval is always role-based, but you can specify whether projects must select specific users based on assigned roles. At the project and change order levels, you can add steps for roles, users, and groups.

  At the project level, the configuration page shows steps that have already been configured at the organization level. Steps you set up at the project level come before the steps at the organization level. The contract-level configuration page shows the steps set up at the project and organization levels. Any steps you set up at the contract level come first, followed by steps set up at the project level and the organization level. At the change order level, you see all steps regardless of whether the change order has that type of document. For example, if the document approval process has a step for draft contracts, the approval steps show for the draft contract regardless of whether there is that document type in the contract.

  You can copy approval workflows in the organization and project settings. You can copy from a PCO to a CCO or vice versa. The document type must be unique. For example, if you have a checklist type already, you cannot bring in another checklist.

  To start an approval workflow for a supporting document, select a document from the Supporting documents register, and then click Start approval.

  

  The Start approval dialog box shows all the steps in the approval workflow. If there are group steps, you can select the group for the workflow. The approval process for documents must be started individually.

  If you have permission to approve a document, you can see them marked with a blue ellipsis in the Supporting documents register, and they are available from the Action items register. Hover over the ellipsis to see the steps of the current approval and the current approval step.

  When you approve or reject a document, any notes you add are shown in the notes. The note is named Document [document name][status - step][approver]. Any notes captured in that level are shown in the Notes slide-out panel.

  You can now recall a document that has already been approved if you have the permission. To recall a document, click Recall approval in the Edit supporting document dialog box.

  

  You can view document approval workflow progress and history on the Platform Workflows page.

  A new permission, Set back to pending, has been added for recalling a document after it has been approved.

• Cost item pricing – You can now build an estimate using existing cost items from InEight Control and calculate an adjustment value based on an adjusted quantity using existing current budget or current estimate rates. This provides easier estimating and continuous contract adjustment in Control. Read more Watch video

  You can now estimate pricing using cost items from InEight Control. This pricing detail is only available in an issue.

  Cost item pricing tab

  When you go to the Pricing tab in an issue, the Pricing summary page opens. Click the expansion arrows to go to the Cost item pricing page.

  

  To add a cost item, click the Add cost item pricing icon. The Add cost item pricing dialog box opens with the CBS structure from Control. Only active terminal cost items are available for selection.

  

  To select a WBS code, click the Add icon next to the code. After you have selected one or more codes, you must assign the cost pricing category (for example, labor or materials) to populate on the pricing summary page. When there are multiple cost items that are in the same category, you can select them, and then click Group cost pricing. You only have to assign the cost pricing category one time. After all cost items have a pricing category, the Add button becomes available and you can add the items. These cost items are then added to the grid.

  Upon adding of the cost item, Change pulls the following fields from Control:

  • WBS

  • Description

  • UoM

  • Forecast (T/O) qty

  • Current CB Qty

  • Mhrs/Unit

  • Unit/Mhr

  • Unit cost

  • Cost source

  • Resources

  • Billing rate markup % (Calculated based on resource billing rates)

  After you enter an adjusted CB quantity, Change calculates the values for the Adjusted cost, Updated CB qty, and Adjusted man-hours fields, if applicable, based on the current budget or current estimate rates. Each cost item defaults to current budget rates. If you change the Unit rate driver field to current estimate, Change calculates the adjusted cost and adjusted man-hours based on those unit rates.

  A negative quantity can be entered if it is smaller than the Current CB Qty column. You can use negative numbers in deductions so that Change calculates a true negative deduction.

  The Billing rate markup % column and values are based on cost source detail cost items that have resources assigned with billing rate markups.

  If you want to see more detail, select an item, and then click the Edit cost pricing summary icon. The Resources tab shows resources assigned to that cost item in Control.

  

  Cost item sync

  Change takes a snapshot of the cost item from Control at the time it is added. Any updates made to the cost item in Control are not automatically reflected in the pricing. This is to ensure pricing is not changing without the Change user knowing or completing an action. If you want to update cost items from Control, you can sync each cost item individually or in groups.

  To sync an individual cost item, click the Edit icon, and then click Get cost itemin the slide-out panel. The cost item is updated with any changes made in Control. Updates are also reflected in the Issue log.

  

  To sync multiple items, go to Actions > Sync > Get cost items. The Get cost item dialog box shows a list of cost items that have changed in Control since they were originally added to the Cost item pricing page. This dialog box shows before and after comparisons based on the current unit rate driver.

  

  Not all fields show in this dialog box as fields that have been modified. For example, if current estimate rates have been updated in Control, and you are using the current budget rates for your pricing, the changed fields would not be listed.

  The Synced date column on the cost item pricing grid shows when information was pulled from Control.

  Pricing summary tab

  Watch video

  Upon clicking Save from the cost item pricing tab, the values show on the pricing summary page per the assigned Cost pricing section (that is, labor, equipment, materials, small tools and supplies, vendor, time related overhead, fixed indirect cost, nonbillables, deductions). The summary value shown in each category is read-only in the Estimate column, as these values are only editable from the cost item pricing summary page. As the values roll up to PCOs and CCOs, the values cannot be edited.

  

  Cost items that have a cost pricing of Vendor, come in as individual lines in the Vendor section as temporary vendors. When you click Edit, you can assign the temporary vendor to an existing contract vendor. If that vendor already exists on the pricing summary page, the pricing items are combined under the vendor.

  The new Deductions cost pricing section lets you reduce or allocate value to one or more specific cost items. The Deduction value can only be populated from the cost item pricing tab and produces a net value of overall change issue. For example, for a Current value of $10,000 with Deductions of -$7,500, the Net value is $2,500.

  CCO Execution/Control contract adjustment

  Upon execution of a CCO, the cost pricing information goes to Control as a contract adjustment. Assigned cost items automatically populate the contract adjustment to provide a more continuous experience. Refer to the Control documentation for more information about budget and revenue details from Change.

  Additional enhancements

  Tags for billing rate markup, deductions, and net value have been added to the issue, PCO, and CCO templates to support cost item pricing.

  If you include pricing when you copy an issue, the cost item pricing is also copied.

• Pricing summary roll-up calculation – In a CCO-level pricing summary, a PCO row is now the sum of the pricing items in the PCO and the issue pricing items. Individual markups are not included in the PCO row, but are shown below it. This reporting lets you see value when collapsed.

• VCO Issue association – All vendor pricing items for an issue are now shown in the VCO detail in InEight Contract when the issue is associated with a VCO.

• InEight Control status and register ID – The Control status and register ID on an executed CCO are now hyperlinks to the Control Change register.

• Create issue from InEight Document –You can now generate an issue in Change from a form in Document and link the two items. This lets you create and track issues that result from processes in the Document Forms module.

• Norwegian – Change is now available in the Norwegian (Bokmål) language.

• Common navigation – The common navigation used across all InEight cloud platform applications has been enhanced for ease of use. For more details, refer to InEight Platform release notes.

• New Pricing tab – An update to the Pricing page lets you add more detail when pricing issues, potential change orders, and client change orders. New functionality has been added to give more flexibility in pricing and new sections have been added for indirect costs, such as fixed indirect cost and non-billable pricing items. Read more

  The new Pricing tab replaces the Pricing & Proposal tab in previous releases. If you have used the previous release, you still have access to the Pricing and Proposal tab for reference for release 21.3. Information on the Pricing & Proposal page is read-only.

  After implementation, your data is migrated to the new Pricing tab. Entries from the Pricing & Proposal tab have the description Migrated from Pricing & Proposal. Items on migrated lines are editable. The migrated lines are a starting point for you. You can edit or delete lines as necessary.

  

  At higher levels, all lower-level migrated pricing and their adjusted offset amounts are shown, so you can verify that their amounts are added to the higher level contributed value only one time. Adjustments have the description Adjustment from issue migration or Adjustment from issue/PCO migration.

  The Pricing tab has the following enhanced functions.

  Pricing section updates

  • You can now add multiple lines within sections to break pricing down into further detail. Free text is now available within each line to provide further description of the item you are pricing.

  • The Self perform subtotal section has been replaced by the Direct cost total. This pricing section maintains the separate subsections for Labor, Equipment, Materials, and Small tools & supplies.

    

  • A new pricing section for Indirect cost total has been added. This pricing section includes the time-related overhead and new subsections for fixed indirect cost and nonbillables.

    

  Pricing configurations

  • There is no more lock or unlock in a PCO or CCO. You can edit a PCO or CCO at any time.

  • You can add or update pricing at any level. Therefore, all pricing items are shown and editable. Additional pricing items can be added at PCO or CCO levels.

  • Since all pricing items are editable, a new Pricing configuration has been added to settings. Previously, all edits made at lower levels had to be manually updated from the higher level.

  • The Pricing configuration setting at the project level (Settings > Change > Configurations > Pricing configuration) lets you specify whether future edits will automatically or manually update values between issue, PCO, and CCO levels. If set to manually update, more options are available to push to higher levels from a lower level. See the Pricing tab information in online help for details about automatic and manual update functionality.

  Pricing section calculations

  • Each subsection subtotals the lines in the section.

  • The Labor, Equipment, Materials, and Small tools & supplies summaries are added together, or rolled down, to get the Direct cost subtotal.

  • The Time related overhead, Fixed indirect, and Non billables summaries are added together, or rolled down, to get the Indirect cost subtotal.

  • Markups have the following updates:

    • The Add Markups icon has been moved to the top of the page.

    • Markups apply to the subtotal of each selected section, then roll up to an overall section total. For example, if there is a 1% markup for labor, and a 10% markup for the direct total cost, a $15,000 line in the labor section has a markup of $150, which makes the labor contributed value $15,150. The direct cost markup is 10% of the $15,150, so $1,515 is added to the direct cost subtotal for a total of $16,665.

      

    • All markups are directly underneath the subsection and apply to the level (that is, Issue, PCO, or CCO) you are applying them in. In a PCO, the markups from the issue are above the PCO subtotal line, and the markup added at the PCO is below the subtotal. This is because multiple issues can be collected into a PCO, and then a PCO level markup is applied to all the associated issues. The following image shows the issue-level markups and new markups at the PCO level.

      

      In a CCO, the markups from the issue and the PCO are above the CCO subtotal line, and the markups added at the CCO is below the subtotal, so you can collect multiple PCOs into a CCO and then apply a CCO level markup to all the associated PCOs.

    • When you hover over markups in a PCO or CCO, the markups are shown at the level the where the markup has been added to give you visibility. Markups are indicated by orange arrows. If you hover over the arrow, you can see the type of markup, the name or ID, and the markup amount.

      

    • After a markup is used, you cannot use it again. For example, if a markup is used at the issue level, it is not available at the PCO or CCO level. You can add a manual markup, if necessary.

  Vendors

  • Vendor pricing no longer takes the roll-up value type of the highest pricing item. Each pricing item is treated individually as a contributed value and they are added together to get the total amount per vendor. The following image shows how the values for three different pricing items for a vendor (one at the ROM level and two at the Estimate level) form the vendor total amount.

    

  • Vendor amounts are added together to get the vendor subtotal. The subtotal plus any markups, roll up into the Vendor total.

  • When assigning a temporary vendor to a Contract vendor, you can now select a vendor already associated to that Issue, PCO, or CCO. The pricing items of the temporary vendor then merge with the associated Contract vendor.

  New functionality

  • The Row density button lets you change the spacing between rows of the grid. You can have relaxed, narrow, or tight spacing to help with readability or to allow the maximum number of rows on a screen.

  • The Jump to button lets you skip to another section in the grid.

  • The Export button provides ability to export the pricing summary.

• Workflow approval and thresholds – You can now establish workflow approval steps for potential change orders and client change orders. Read more

  You can establish workflow approval of PCOs and CCOs based on value thresholds. Workflow steps and values are defined at the organization, project, and PCO or CCO levels.

  Steps in a workflow are defined based on settings and value of the PCO or CCO. For example, if you have a PCO organization level threshold of 100,000 value and the PCO being started for approval exceeds 100,000, it is required to go through the organization steps.

  Approval steps set at the organization level are assigned approver roles rather than specific users. When setting up a threshold, the Project must select specific users based on assigned roles checkbox is selected by default. When this option is selected, you must edit the threshold at the project level to select specific users within the assigned roles.

  Approval steps set at the project level can be assigned to roles, users, or groups. An approval group is a set of users or roles in steps. For example, you could have a group that flows through your entire approval process or a group that is just the business manager. You can set up multiple groups, and you can assign multiple groups to an approval step.

  You set up a group on the Group approver setup tab (Settings > Change > Workflow Assignments > Group approver setup). Each group can have one or more steps that represent the approval process.

  

  To use a group step when setting up a workflow in a PCO or CCO, go to Settings > Workflow Assignments > Potential CO Approval Setup or Client CO Approval setup, and then click the Add Approval icon to add a threshold amount. Select Groups in the Assigned approvers section. The drop-down list shows a list of all groups.

  

  In the PCO or CCO workflow, the steps are shown based on value of the PCO or CCO. If the PCO or CCO is above the thresholds set at the organization and project level, those steps are shown, and you cannot edit or delete them. You can add additional steps that are performed before those at the organization and project levels. PCOs can be converted to CCOs at any time; however, all PCOs that require approval must be approved before the CCO approval can be started. If the CCO requires approval, it must be in Approved status before it can be submitted for execution.

  At the project level, the functions on the Client CO approval tab have moved to the Client CO execution setup tab.

  The Approval status of the PCO has been added to the PCO log and the Associated items section of a CCO. The approval status of the CCO has been added to the CCO log.

• Change templates new functions – You can now load a Microsoft Excel template as a change order template. Collection table tags have been added to enhance your template options. When you are in a template, you can preview a template with sample data, so you can check your formatting before using the template. Read more

  A Change template can now be an Excel spreadsheet, not just a Microsoft Word document type. The Download icon now gives you a menu that lets you select Word or Excel sample example to review. The Tag list icon also gives you a menu to select general tags list or collection table tags list.

  To see a preview of a template with sample data after you have loaded your template, click Preview with sample data in the template details. You can select multiple templates.

• Change writer collection table tags – New collection tables tags have been added. You can now create customizable tables in change templates specific to vendors, supporting documents, and associations. Read more

  Collection table tags enable you to enter one tag that collects all similar items into a table. For example, if a client change order has 20 vendors, you could specify the related collection tags for all of the vendors at one time in a formatted Word or Excel table. When you generate the template, the Change writer collects all 20 items into the table. Without collection tags, you cannot enter the items into the change document.

  When you add a new template at the organization level, you now specify the template type (that is, Issue, Potential change order, Client change order, or Other), so you can view the appropriate table tags. A template type can have multiple table tag types. Each table can use tags for one table tag-type only. You can include multiple tables in a single template.

  The new Tags section of the Change Template Details page contains links to general and collection table tags.

  

  After you create your template, you can preview it with sample data, so you can see if it looks the way you want it to look.

• Change writer general tags additions – New general tags have been added to the Change writer to accommodate notes, deductions, and approval statuses.

• Delay days and time extension functionality – Changes have been made to the Delay days field of the Issue Details page and the Time extension field of the PCO/CCO Details page. Read more

  The Delay days field has moved from the issue header to the Schedule impact section of the Issue Details page.

  

  When there is only one issue associated to a PCO or CCO, and the PCO or CCO has delay days, the issue delay days now populate the Time extension field on the PCO Details page or CCO details page. When there is more than one issue associated, the Time extension field is blank. The Time extension field has been moved from the PCO or CCO header to the Details section.

  

  The Delays column has been added to the Associations section of the PCO Details. When there is more than one issue associated with the PCO, you can use the value in the Delay days column for each issue to calculate the time extension.

  

  The Time extension field on the CCO Details page has been removed from the header. It has been renamed Requested time extension and moved to the CCO Details section.

  

  If there is only one PCO associated with a CCO, the Time extension field of the PCO populates the Requested time extension field of the CCO details. If there are multiple PCOs, the Requested time extension field is blank. A Time Extension column has been added to the Associations section. You can use the values for each PCO to calculate the Requested time extension when there are multiple PCOs.

• Notes enhancement – You can now add notes to an issue, PCO, or CCO at any time, regardless of status. The general tag for notes includes just the last note that was added.

• Integration with InEight Control – Available WBS codes for selection have been expanded to include all terminal cost items from Control, including As-built = Cost and As-built lock . WBS codes can now be assigned to an issue in Control. When a WBS is assigned in Control, the WBS is shown in read-only format in the issue and cannot be removed in Change.

• Project reimport – When a project is reimported into Control, the InEight Contract and Change cost items table is deleted, and the project cost items are replaced. If an issue was associated with a cost item that was deleted from Control, the field is blank, and you must update it manually.

• Issue WBS code enhanced search– When adding a WBS code to the issue details, you can now search for a code using a description keyword. Previously, you had to know the WBS ID number to search for a WBS code. Read more

  To search for a description, start typing the description in the WBS field. The WBS field with a sample text search is shown below.

  You can select multiple codes from the search results.

  

• Construction area configuration– The construction area configuration is now available in project Settings > Configurations > Construction area. Previously the configuration had been in the project details.

• User email address in approval setup– You can now see user email addresses when selecting users for approvals, so you can ensure that you are selecting the right account for a user. Read more

  You can also search for a user by email address. The User field search box is shown below.

  

• Removal of empty tags in template – Change now removes tags that do not have field information from a change order document. Previously the empty tag would be included in the final draft of the document. Read more

  Empty tags are still shown in the review fields to allow users with the permissions to edit tag information. If Change is not configured to allow users to edit, you must go to the change order to add information or make changes.

• Integration with InEight Compliance and InEight Plan – A hyperlink has been added to the Issues detail page that links you to the product that created the issue, so you can easily move from Change to other InEight products. Read more

  If you have permissions in the other products, you can click the link to go to the formin InEight Compliance or daily plan in InEight Plan where the issue was created.

  

• Notes included in export – Notes now export from Issue, PCO, and CCO logs if the Notes column is shown in the view when it is exported.

• Enable or disable custom labels at the project level– If the organization has custom labels configured, you can now choose to enable or disable them at the project level. Read more.

  If custom labels are set at the organization level but they are not applicable to your project, you can disable them. On the Change Custom Labels tab , the Enable custom labels toggle indicates whether custom labels are enabled at the project level. Set the toggle to No to use the standard labels from InEight. Set the toggle to Yes to use the organization-level custom labels. The toggle is enabled only when custom labels are enabled at the organization level.

• Issue log References column– The References column has been added to the Issues log register. The References column shows the number of requests for information (RFIs) are tied to the issue. Read more.

  When you click on the value, a dialog box shows the RFIs associated with the issue.

  

  Click the file link to see RFI details.

• Custom label additions– Read-only view of organization custom labels has been added at the project level for you to reference against for reporting and change writer tags. Read more.

  The read-only view is in Project settings > Change > Change Custom Labels.

  

  You can use the read-only view as a reference, so you can see where tag information is mapped in a contract. Default text is dimmed. The custom labels list can be useful when using change order documents, as tags are not dynamic, and tag names are not affected by custom labels.

• Dashboard widgets custom labels– Custom labels are now shown in Change widgets. Previously, the default name would show.

• Organization custom labels– Organizations can customize field names in the application to align with their business terminology. Read more.

  The following fields are included in Custom labels to be renamed to suit or define your organizations business needs:

  • Change order

  • Client change order

  • Client CO

  • CCO

  • CO

  • Potential change order

  • Potential CO

  • PCO

  • Vendor

  Organization settings have a new tab, Change Custom Labels (Organization > Settings > Change > Change Custom Labels), where you can set custom labels in all languages supported in the InEight product.

  

  The Enable custom labels setting indicates whether the custom values are shown throughout the application. When Enable custom labels is set to On, Change uses the custom labels throughout the application and in notifications and emails. If you leave a field blank, the default label is used. When set to Off, the default field names are used.

  Change writer tags continue to display as default names.

• Change templates new functions– When you are in a template, you can preview a template with sample data, so you can check your formatting before using the template. You can see the preview by clicking Preview with sample data in the template details.

• Change writer template type – Change template types have been defined for issue, potential change order, client change order, and other. Template types help filter the choices among templates and tags, so you can quickly find the templates and tags for your business needs. Read more.

  The Change template Details page has been updated to include the Template type field.

  The Other template type lets you add project-specific supplemental and exhibit information.

• Change writer View general tags– Available tags have been renamed to General tags and updated to include any new fields or changes. The General tags page has been updated to include the location source and example data to help you see where the tag information comes from and what it looks like. Read more.

  Click View available tags, and then select General tags to see the tag list.

  

  The Available tags list is now the General tags list. Columns have been added for Location source, Example, and Applicable for.

  

  The Location source column shows the name of the page that Change pulls the information from when building the template. You can see an example of how this information might look in the template, as shown in the Example column. The Applicable for column indicates the template type that can use the tag. A template can use only the tags specific to its type plus those marked All templates.

  You can now download a sample template from the Change templates register. Previously, the Download sample template button was on the Template Details page. The sample template has been updated with the example data from the tag list.

• Change writer language type and localization– Template language selection has been defined for all supported languages so that organizations or projects can define in which language the template is generated. General tags have been localized to support all languages for the template languages. Read more.

  The language of the template is defined in the Select template language field in the Change template details.

  Selecting a template language narrows the tags available. For example, if you select Spanish as the template language, you can use only Spanish tags in the template even if the language of your application is English. Upon generation, template and tags are generated in Spanish.

  You cannot use tags in multiple languages in a single template. During template validation, the application only searches the tags of the selected language instead of all languages.

  

  If you have seeded scripts or anything else for which Change offers localization, Change writer pulls the selected language as the seed.

• Add supporting documents – You can add a document from InEight Document upon adding a supporting document. Being able to add from Document saves you configuration steps. Previously, you would specify whether the supporting document is from Document in the Add supporting document dialog box, and then fill in the information when you returned to Change. Read more.

  When you click the Add document icon from the supporting documents tab, the PCO Details tab, or the CCO Details tab, you have the option to add a new document or one from InEight Document.

  

• Scope status configuration – The scope status is now configurable at the organization level in settings, where it is named Scope. This change lets your organization set a default list that automatically populates all project drop-down lists. Read more

  In previous releases, project scope was limited to In scope or Out of scope. You can now add and maintain scope definitions that are unique to your organization.

  Because scopes are now custom, Change no longer validates the scope when closing an issue.

• Message configuration – You can now turn confirmation messaging on or off at the project level throughout the application and indicate whether messages are required. This configuration can streamline business processes. Read more

  The project settings Configurations tab has a new option for message configuration that lets you specify whether each custom list field shows a confirmation message when a change is made to the list and if notes are required.

  

  For example, if the Source/cause field is configured to show a confirmation message with notes, you would get a notification when you change the value of the Source/cause field.

• Construction area configuration – Language localization has been enabled for the construction area project setting. This enables you to customize this area based on your business processes. The localization function is now in line with other lists.

• New change order columns– Alternate CCO, CCO name, and PCO name columns have been added to CCO Log enterprise views.

• Terminology update –The Subcontractors and Number of subcontractors fields have been renamed Vendors and Number of vendors to provide more inclusive terminology.

• Name and description separation– The Name and Description fields are now separate on the Action Items tab to give you more flexibility in describing the change.

• Project contract summary– Prime contract summary has been updated to Project contract summary. You can now update the project contract summary by clicking the Save button instead of having to refresh the page. Read more

  Projected project value now includes all non-executed PCO and CCOs except dropped. Click Save from any page will update the prime contract summary.

• Cost, Markup, and Margin pricing breakdown – The Issue, Potential CO, and Client CO now show breakdown of Cost, Markup, and Margin fields. The fields can give you visibility into the profit you are making on an issue or change. Read more

  The Cost is the total of all priced items, the Markup is the total of all markups, and the Margin is the markup divided by the cost. Current value is costs plus markups.

  To accommodate the new fields, the Delay days to to issue field was renamed Delay days.

• Pricing & Proposal markup– The Markup percentage on the Pricing & Proposal grid now supports three decimal places. The final calculation amount remains with two decimal places, rounded to the penny.

• Allowance category WBS association – You can now associate a WBS phase code to the allowance category within project settings. The WBS defaults in the issue details when allowance category is selected. Read more

  If the WBS has an OB total cost or CB total cost associated with it in InEight Control, it is automatically populated. The values are for reference or comparison purposes only. The following image shows the new fields in project settings:

  

  After you add a WBS code to an allowance category, the WBS field on the Issue detail page is automatically populated with the WBS when you select that allowance category.

  You can use the WBS field to add additional WBS codes or delete a WBS code that does not apply. The View icon associated with the WBS field lets you view the as-built totals summary from Control. The icon functions the same way as the View as-built totals summary option from the Actions menu. The WBS field and View icon are shown below.

  

• Request for information– New boxes on the PCO and CCO details pages indicate whether a change order has an RFI associated with it. This box was previously available only on the issue details page. Read more

  When you add a request for information (RFI) type of supporting document to an issue, PCO, or CCO, a new Request for information section shows a list of all RFIs added to the PCO and CCO. When you add an RFI to an issue, the RFI also shows with any PCO or CCO associated with the issue. When you add an RFI to a PCO, it also shows with any CCO associated with it.

  The new Request for information section appears on the right side of the Details tab for both PCOs and CCOs. The following image shows the box on the PCO Details tab .

• Client change order execution date field– The Client CO Execution date field has been added to the CCO details. The value is system generated. Read more

  The new field is shown below.

  

• InEight Contract integration– When an issue is assigned to a back charge in Contract, the vendor is added to the Pricing & Proposals tab in the issue. When there is no assigned vendor, the vendor is blank, and the contract number is displayed. If the issue is linked to a PCO or CCO, it is also shown in the Contract VCO. Read more

  When an issue is assigned to a back charge, the vendor is added to the Pricing & Proposal page of the issue. If a vendor is associated with the issue in InEight Contract, a new section, Vendor subtotal is shown on the page.

  

  Because Contract has been enhanced to allow contracts to be started without a vendor, there might be an occasion when the vendor name is not available. When the vendor is blank, you can add it to the Pricing & Proposal page, but only the contract number is shown. Change associates the vendor after the vendor has been added in Contract.

• Change writer View available tags – General tags have been updated to include any new fields or changes. The Available tags window has been updated to include the location source and example data. Read more

  The Location source shows the name of the page from which Change pulls the information when building the template. You can see an example of how this information might look in the change order in the Example column.

  

  The sample template has been updated with example data. If there are blanks in the template, the finished change order also shows blanks.

• Blank tags in Change writer templates – The <<Blankn>> tag, where n is a number from 1-15, has been added as a placeholder for text that does not appear in a field in the Change application. Read more

  The <<Blankn>> tag appears in the downloaded tag list. The tag serves as a placeholder in your template where the text can be entered to appear in the fields when you review the template. When you generate the word document, the text is replaced with what you entered in the review. You must enter text each time you generate the Word document. If you do not enter values in the Review fields, the <<Blankn> tag is shown in the Word document.

• Text editor and formatting– Description fields at the issue, PCO, and CCO levels now have text editing to let you format description information. Read more

  Formatting options include bold, italics, underlining, and lists. You can also format text as paragraphs, quotations, or headings. The following graphic shows the updated Description of change field.

  

• Request for information – Request for information documents are now shown in a new box on the issue details page. This box provides a quick indication that an issue has an RFI associated. Read more.

  When you add a request for information (RFI) type of supporting document to an issue, PCO, or CCO, a new Request for information section shows a list of all RFIs added to the issue. This new section appears on the right side of the Details tab for an issue. If you manually upload an RFI, only the Title column is filled. The RFI No. and Status columns are only filled when you add an RFI from InEight Document.

  

  Although you can add an RFI to a PCO or CCO, the Request for information section only appears for issues.

• Create an RFI/form in InEight Document – You can now initiate an RFI/form in InEight Document and show the link within an issue/PCO/CCO. This feature improves integration between Change and Document. Read more.

  In the Supporting Documents tab of an issue, you can select Create new form from the Actions drop-down menu and then select the form type in the pop-up window. If you select Request For Information, the RFI you pull from Document will populate the Request for information box in the Details tab of the issue.

  

  If Create new form is inactive, you can select the cogwheel icon to set up integration with InEight Document.

  You are then taken to InEight Document’s Forms module to fill out the form. If you save and/or complete the workflow, you are shown a pop-up window in Change, and the form is loaded in Supporting Documents.

• Allowance category summary – In the Prime contract panel, allowance categories now track issues against original value to give you quick visibility. Read more.

  When you open the Prime contract summary panel with the sum icon, an Allowance category section is now at the bottom of the panel. This section shows all of your project’s allowance categories and their calculated amounts. Color-coded bars show how much of each category’s amount is actual, potential, or remaining. These amounts are defined as:

  • Actual– Sum of closed and executed issues
  • Potential– Sum of all issues except closed, dropped, and executed
  • Remaining– Allowance value minus the sum of actual and potential

  

• configurations lists – Configuration lists that were previously their own subtabs in Settings are now organized in one tab to allow for expansion of configurations lists. Read more.

  In Settings at both the organization and project levels, the Custom Lists tab has been renamed Configurations. Unlike the old tab, Configurations is not split into sub-tabs, but contains one table with links to all of the lists that were previously in Custom Lists.

  

• Actions added to Supporting Documents– An Actions drop-down list has been added to the Supporting Documents tab to give you the same options available in the Details and Pricing & Proposal tabs. Previously, these actions weren’t available in that tab.
• PCO/CCO Name field– A Name field has been added to PCOs and CCOs to differentiate the name from the ID and Description of change fields.
• Main issue view– A new view has been added to show only main issues and sub-issues, so you now have a way to hide standard issues from your view.
• Prime contract fields– Prime contract fields have been moved to Project details from Change Settings.
• Dutch language localization– Language settings have been added for Dutch, expanding the options for localization.

• Project allowance categories – Projects can now customize allowance categories and values based on the project prime contract agreement. This gives you further categorization by tagging issues to an allowance. Read more.

  You can now create customized allowance categories in project settings to then apply to issues through the Allowance category field. You can optionally set a specific value to each allowance category.

  In projectSettingsfor Change, Allowance category is located under the Project Details tab.

  

• Contingency scope now an allowance category– Contingency is now an allowance category instead of a scope. This change gives you the ability to customize categories based on a contract. Existing contingency data will be migrated.

• Issue status configuration at organization level – The Issue status is now configurable at the organization level in custom list settings, where it has been named General status. This change lets your organization set a default list that automatically populates all project drop-down lists. Read more.

  In organization Settings for Change, there is a new sub-tab under Custom Lists called General status.

  In this sub-tab, you can create custom statuses that will then be available for all projects in your organization. These general statuses can then be selected in the Issue, PCO or CCO status fields and drop-down menus.

  You can use the General status type menu on the left side of the page to open the lists for issues, PCOs or CCOs.

  

• New PCO approval date– A new approval date field has been added to the PCO details page and added as a column to the log. This field lets you mark when a client has given their approval.
• New columns in logs– The following columns have been added to the Issue, PCO and CCO logs to give you added visibility into data already in the application but absent from the logs:
  • Allowance category
  • Closed date
  • PCO creation date
  • CCO creation date
  • Client CO execution date
  • Executed CO document date – Renamed from Executed CO date
• Added column in Change templates – A new Created by column has been added to make it easier to see who created each template.
• Change writer template names– The names of Change writer templates can now be the same at the organization and project levels. Previously, all template names had to be unique, even between the organization and project levels.
• New triggers to send payloads to Control– All changes to issues now trigger sending payloads to Control and a WBS is no longer required to send the payload. This change eases communication of changes between Change and Control.