Revision as of 16:26, 2 September 2020

ICM Sourcing Release Notes- Release 7.12

Overview of  Sourcing Release 7.12

The 7.12 Release introduces significant enhancements to the Icertis Contract Management (ICM) Sourcing Business Application. It strives to improve user experience and usability by continually improving ICM functionalities and the user interface.

The key enhancements of this release include:

• Revamping the workflow entities to be able to improve usability and support the flexibility required in Sourcing.
• Providing buyers the capability to copy RFx, thereby considerably reducing timelines to create similar RFx and also avoiding duplication of efforts.
• Allowing modification of RFx (adding, removing or editing parts of the RFx) which is in Approved or later status until the awarding is initiated, making it easier for buyers to make changes as all the required criteria or business requirement may not be available at a glance during RFx creation.
• Evaluating suppliers for an RFx by conducting a review, scoring suppliers on their capabilities to help in the awarding process, as well as providing feedback on their bid submissions.
• Selecting one or more currencies for an RFx or an item, defining one corporate currency, and providing Supporting usage of multiple currencies at an organization level that could be used in sourcing events.
• Allowing linking of existing RFx supplier contracts for all prerequisite, mandatory and associated contracts.
• Displaying the full name of the supplier.
• Displaying names of external and internal attachments as uploaded by the user.
• Providing the ability to use any masterdata for supplier and supplier contacts.
• Displaying bids of all suppliers to buyers throughout RFx lifecycle
• Availability of bid analysis attributes and values in the bid analysis Excel.
• Providing the ability to add bulk line items to the RFx.
• Allowing buyers to edit the round start and end date when the round is in Draft, Waiting for Approval, On Hold, Open or Approved statuses.
• Adding validations in prerequisite and mandatory contracts for shortlisted suppliers and also for linked agreements.
• Introducing the RFx Change History Report which provides a consolidated view to the procurement team of all actions for an entity.

Enhancing the RFx Summary Report and RFx Details Report to provide a consolidated view of data for RFx with various categorization, thus providing the visibility to top management on sourcing activities and helping them to take more informed decisions.

These release notes provide an overview of the enhancements to ICM Experience for Sourcing.

• Refer to the detailed Wiki documentation for the explanation and capabilities of these and all other ICM features and functionalities.
• Please refer to the Frequently Asked Questions for details specific to the Sourcing Application.
• Partners can access this documentation here.

Sourcing Application Enhancements

571048 – Displaying full names of supplier contacts

Previously, when selecting a supplier contact, only the first name of the supplier contact was displayed.

With this release:

• The Supplier Contacts window user interface has been improved.  
• The name of existing Supplier Contact Name column has been modified to Supplier Contact Full Name. For example, Tom Sibley instead of Tom.
• Buyers can remove a supplier contact from the Supplier Contact page. This updates the count of selected supplier contacts.
• The selected supplier contact’s full name is displayed on the new selected supplier contacts interface.
• The suppliers and supplier contacts saved earlier are now pre-selected when adding more suppliers and supplier contacts.

The supplier contact full name column will be displayed by default on the supplier contact selection page, supplier contact details page and grid view of the supplier contact association.

This makes it is easier for buyers and administrators to identify and select the correct supplier if there are multiple suppliers with the same first name.

Note: This is applicable for RFx, RFI, Rounds and Bulk Agreements.

Enhancements to Sourcing Entities Workflow

573430 – Sourcing entities workflow revamp

The workflow for Sourcing has been revamped to make it specific for Sourcing, in order to support the flexibility that is required in sourcing. The following enhancements have been made to the RFx, round, bid and awarding workflow respectively.

590362 – Displaying bids of all suppliers to buyers throughout RFx lifecycle

Previously, buyers could view bids only after they were submitted by the suppliers. However, it was not possible to know whether the supplier had submitted the bid (in case of open RFx), or if the supplier had submitted or declined it until it was closed (in case of sealed bid).

Now, buyers can now view the status of bids for each supplier, regardless of whether the RFx is an open or sealed envelope, depending on the status of the bid.

These statuses include:

• Submitted:

</ul>

</ul>

</ul>

</ul>

• Buyers and the user assigned as surrogate buyer can view the bids until the round is in Open status for open RFx.
• The surrogate buyer can view the round after it is closed, similar to a normal buyer.
• The View icon is not displayed for the buyer until the round is closed for Sealed Envelope.

• Submitted and Closed:

</ul>

</ul>

</ul>

• Buyers and the user assigned as a surrogate buyer can view the bids in Submitted status when the rounds are closed.

• Not Submitted and Closed:

</ul>

</ul>

• The user assigned as a surrogate buyer can view the round till it is in Open status, similar to the supplier.
• The surrogate buyer can view the round the way the normal buyer can after the round is closed.
• The View icon is not displayed to the buyer for Open RFx and Sealed Envelope.

</ul>

</ul>

</ul>

Note: The bid responses are displayed or hidden based on whether the bid was submitted or not submitted by the suppliers.

• Declined:

</ul>

</ul>

</ul>

</ul>

• The bid status changes to Declined when the RFx is declined by the supplier. The suppliers declining the bid cannot participate in the upcoming rounds.

</ul>

Buyers can view the status of the RFx depending on the status of the round, bid and the type of RFx. They can view the status of the bid at any time, but cannot view the bid response until it is submitted by the supplier.

• Open RFx:

</ul>

</ul>

</ul>

</ul>

• Buyers and the user assigned as a surrogate buyer can view the round in Open and Closed state and can view the bid status at any time.
• The surrogate buyer can also view the bid response.

• Sealed Envelope:

</ul>

</ul>

</ul>

• Buyers can view the bid response when the status of round changes to Closed status. Buyer can also view the bid status at all times.
• The suppliers whoDeclined the bid will not be shortlisted for upcoming rounds nor can they revert decline to participate in the round again.

</ul>

</ul>

560481 – Ability to copy RFx/RFI

Procurement team often uses the same template, line items, questions and attachments for repetitive procurement of similar category items. Previously, as RFx/ RFI could not be copied, buyers had to create multiple sourcing events manually with different suppliers several times using the same line items, questions, attachments, etc.

Buyers now have the capability to copy the RFx which helps reduce the timelines and avoids duplication of efforts for similar RFx creation. Additionally, as procurement involves globally distributed buyers’ team, they clone the sourcing event at the regional level and link them to one another. Linking the copied RFx to the original RFx can be achieved by enabling the Link To RFx flag on the Copy Record window. 

Along with the RFx, users also have the ability to select any associated documents (line items, questions, attachments, etc.) where the Allow Copy with Associations flag is enabled at the contract type level. By default, the flag is disabled, hence only the RFx is copied without its associations.

Now:

• Sourcing events can be copied along with the selected associations such as line items, questions, questionnaires, suppliers, supplier contacts, internal and external attachments, and commitments.
• Some associations such as rounds, awarding, etc. may be configured to be excluded from being copied. These associations are not displayed in the Copy Record window.
• Automatic attachments will be excluded from being copied. These attachments are not displayed in the Copy Record window.
• Validations are provided to ensure supplier and related supplier contacts, questionnaire and related questions, are selected to be copied.
• Some RFx and associations’ attributes may be configured to be excluded from being copied. The attribute values will not be present in the copied RFx.

When copying the RFx:

• All or some user roles are copied in same or different role based on the configuration.
• The user who copies the RFx (based on user authorization) then becomes the primary owner of the respective RFx.

The changes can be viewed in the History audit log on the RFx Details page.

Note:

• Rule based users will not be copied to the new RFx.
• Based on the requirement, the configurator must check if the external users should be copied or not.

This is applicable for RFx and RFI.

Modify RFx Workflow

560526 – Modify RFx

Buyers require a provision to add, remove or edit certain parts of the RFx, as all the required criteria or business requirements may not be available at a glance during the RFx creation.

With this release, ICM provides the ability to modify a RFx which is in Approved or later status until the awarding is initiated.

Multi-Currency Support

567584 – Introducing Currency Support in Sourcing

Previously, ICM did not support using multiple currencies at an organization level that could be used in sourcing events.

With this release, ICM Administrators can now:

• Configure the corporate currency in the currency master:

</ul>

Note: Every currency added to the currency master must have a validity period that allows using currencies in different entities.

• Configure the exchange rate of different currencies:

• Add, remove or edit the exchange rates in the currency masterdata. The specified currency exchange rate must have a defined validity period.
• Set currency exchange rates for supported currencies.

Note: Duplication of exchange rates for same currency and same validation is not allowed.

• Select the primary and allowed currency for the RFx:

• Select one currency as the RFx primary currency which is selected from the list of currencies available in the currency master including the expired currencies. Buyers can also select multiple currencies to be allowed in the RFx. It is mandatory to select a primary and allowed currency for the RFx that will be used in bid analysis excel sheet to convert bid currency to RFx primary currency.
• Select the primary and allowed currency that can be used by the supplier to bid for the RFx.
• Restrict editing the currency attributes used in RFx other than the one that is set as RFx primary currency. When RFx primary currency is updated, ICM uses the currency for all other currency attributes automatically, until the RFx is in Draft state.

The activities performed by the buyer relevant to the currency selected for an RFx are logged in the RFx History.

• Select currencies from list of allowed currencies:

</ul>

</ul>

• Allowed currencies for RFx can be used as the bid currency.
• All currency attributes for a line item are restricted to the RFx currency.
• The modified allowed currencies for RFx are displayed to suppliers as bid currencies for all items.

• Configure the exchange rate for the RFx:

</ul>

</ul>

</ul>

• Specify the exchange rates that can be used in the RFx.
• Specify if the applicable exchange rate is based on round start and end date and user selected date.
• View the applicable exchange rate for the RFx and the history of the exchange rate specified for the selected RFx.

</ul>

</ul>

Note: The applicable RFx exchange rate is available to both the buyers and suppliers.

• Download the bid analysis excel at any time that includes all bids from all suppliers for all rounds along with the bid currency and RFx primary currency. The bid analysis file contains details such as line items, bids, and so on. You can download the bid analysis at RFx, Round, Bid level in the Sourcing lifecycle.

• Use conversion rates in bid analysis Excel:

</ul>

</ul>

</ul>

</ul>

• Buyers can now:
  • • Download the bid analysis Excel file that allows to view all the bids received from multiple suppliers.
    • Download the flexible bid analysis Excel file for each round after it is closed that allows viewing bids received and converted to RFx primary currency. This file contains information for specific rounds only.

• Buyers can take the following actions when the bid is created:
  • Select the bid currency that allows submitting surrogate bid on behalf of the supplier.
  • View the changes made to the bid that are logged in RFx History.
  • Suppliers can take the following actions when bidding in multiple currencies:
    • View the supported currencies for RFx that allows viewing the applicable exchange rates.
    • Select the currency from the list of quote currency that allows submitting the bid in the selected currency.
    • Submit the bids for items in selected currencies.
    • Upload or download the bidding template that allows adding bid information in excel sheet and upload to ICM.
    • Update the bid currency using ICM and Microsoft Excel.
  • Buyers can take the following actions when updating the awarding object for the RFx using multiple currencies:
    • Download the awarding decision template that will allow awarding the desired suppliers and upload the awarding decision.
    • Include the bid currency in the awarding decision that allows including the bid currency and other bid information in the contract.
  568737 – Capability to link existing contracts in RFx Previously, linking existing supplier contracts with the RFx was not possible. This created duplication of contracts and the user had to go through the complete contract lifecycle again. An enhancement has been made to allow linking existing RFx supplier contracts for all prerequisite, mandatory and associated contracts. Buyers can now:
  • Link existing supplier contracts (prerequisite, mandatory or associated contracts) allowing buyers to leverage existing contracts with suppliers. 
  • View the contracts of the supplier when creating the bulk agreement that allows assigning any supplier contact as a signatory for the agreement.
  • View the signatory of the prerequisite contracts that allows the suppliers to connect with the signatory if the contracts are not executed.
  • Send the agreements for approval in bulk that helps avoiding sending the agreements for approval individually.
  Select the new signature type Click to Sign allowing suppliers to participate in the sourcing event by previewing, accepting or declining the contractual terms set by the buyer.
  

  573435/573436 – Ability to add bulk line items to RFx

  The bulk associations capability has enabled ICM to handle a large number of associations in the tune of thousands, by presenting itself as a lightweight association as well as tremendously improving performance. The Sourcing event can include many line items for an RFx ranging from 500 to 50,000 maximum. In Sourcing, line items are considered as associations.

  The bulk association configuration has now been simplified by providing aEnable Bulk Processing flag at contract type definition level which triggers a set of defaults that has been intentionally restricted. The end user experience for the bulk association has not changed from the way that the conventional association is handled from the UI, rather the underlying data structure has been further enhanced to make it go the distance.

  Performance has been the key while introducing and designing this new association, which has given way to the new type of instance, namely the Proxy Instance, which is retrieved in every GET call. The actual instances are referred by using this proxy instance, thereby reducing the load on the GET APIs. Specialized GET and SET APIs have also been introduced for bulk associations to improve its adaptability and ease-of-use.

  Bulk associations have very effectively consumed the Elastic Search Bulk API to sync a large set of data at one go, rather than the traditional way of one instance at a time, adding to the boost in performance.

  Bulk association is enhanced to be able to address the large volume of data that Sourcing apps require. These enhancements include:

  • The associations not having a workflow.
  • Simplifying the association team by maintaining single team at proxy level for all instances, instead of each instance having its own team.
  • Restricting document assembly, for individual instances, but the instances can be assembled in the parent agreement as a table or saved search.
  • Reducing the attributes to be indexed in the parent, so as to cater a greater number of instances driven by the configuration key.

  404532 – Ability to edit round start and end dates

  Previously, when the round was scheduled or open, buyers could not change the round start and end dates. However, in Sourcing, timelines are likely to change for various reasons, internal or external, which could not be achieved earlier.

  Buyers can now edit the round start and end date when the round is in Draft, Waiting for Approval, On Hold, Open or Approved statuses.

  You can make changes only to the round end date when the round is in Open state. The changes made to the round start and end date are captured in the History on round Details page.

  It is not mandatory to run the approval workflow for the round after changing the Planned Start Date and Planned End Date

  
   
  566709 – Prerequisite and mandatory contract validations for shortlisted suppliers
   
  Previously, the prerequisite and mandatory contract validations were being displayed for all suppliers despite not being shortlisted in RFx.

  Now, buyers will be able to view the validations for the prerequisite and mandatory contracts for the shortlisted suppliers only. For a shortlisted supplier, if all the prerequisite contracts are inactive, or if any one of the contracts is active but not in Approved or later state, then the validations will be displayed. For example, if there is one shortlisted supplier with two prerequisite contracts NDA 1 (in Draft state) and NDA 2 (in Waiting for Approval state), then validations will be displayed.

  The validations will not be displayed for shortlisted suppliers when at least one active prerequisite contract exists, and all such contracts are in Approved or later state. For example, if there is one shortlisted supplier with two prerequisite contracts NDA 1 (in Approved state) and NDA 2 (in Expired state), no validations will be displayed since one of the two prerequisite contracts (NDA 1) is in Approved or later state.

  625383 – Prerequisite and mandatory contract validations for linked agreements

  Buyers have the option to select mandatory and prerequisite contracts while creating the RFx. The attributes for mandatory and prerequisite contracts are interlinked. The prerequisite contracts are derived from the mandatory contracts. So, if the buyers select the following contracts – NDA, Warranty Agreement, Fixed Cost Agreement as mandatory, then they have the option to select one, more than one or all as prerequisite contracts.

  For example, if an NDA is the prerequisite contract for accessing the RFx, then the validations are done such that ICM expects that the instance of an NDA contract type for all the suppliers is associated with the RFx and contract should be in Approved status. Similarly, if contract types are made mandatory, then the instances of these should exist before RFx is sent for approval.

  Sourcing Reports

  576084 – Addition of the RFx Change History Report

  Previously, the Sourcing application provides the change history of rounds, bids and awarding separately for rounds and bids within the RFx.

  Now, the Change History Report has been introduced, which provides a consolidated view of all actions for entity. This will help the procurement team to view the entire history of rounds, bids and awarding within a RFx, at a glance for auditing purposes.

  This report is accessible only to buyers (not suppliers), from within a RFx transaction, hence only authorized users with access to a RFx can view this report. All the latest updated information captured at the point of time when the report is generated will be displayed in it.  

  The Change History Report can be generated by applying the following filters - Entity Type, User Name, User Role and Supplier Name. By default, the report is filtered on Entity Type as RFx/RFI. Based on the requirement, users can change filters. The report provides details with columns such as Date & Time, Event, Entity Type, Entity Name, User Name, User Email, User Role, Supplier Name, Notes, Attribute Name, Previous Value and New Value.

  Note:

  • This applies to RFx and RFI.
  • If the RFx is in Pre-Draft state the No Data Found message is displayed.

  573599 – Enhancements to Sourcing reports

  The RFx Summary Report and RFx Details Report provide a consolidated view of data for RFx with various categorizations, thus providing the visibility to top management on sourcing activities and helping them to take more informed decisions.

  • The RFX Summary Report now displays:

• Sorting capability on RFx Information and Supplier Information columns.
• The name of column Submitted Status is changed to Bidding Status, and the name Submission Date is now changed to Bidding Status Update Date.

• The RFx Details Report now displays:

• The RFx status displayed as Bidding Closed, Bidding Scheduled, Bidding Open in conjunction with the revamped RFx workflow.
•  The Bidding Details (within RFx Details Report) displays:
  • • Supplier View: Supplier ID, Supplier Name, Round Name, Shortlisted status.
    • Round View: Round Name, Supplier ID, Supplier Name, Shortlisted status.
    • Line item View: Line Item Name, Round Name.

• • The Supplier Information section (in RFx Summary, RFx Details Report) displays contracts such as NDA, MSA, and so on. The contract names will now also display the classification such as prerequisite, mandatory or associate for ease of use. For example, if Warranty Agreement is added as a prerequisite contract, then it will be displayed as Warranty Agreement (Prerequisite).

• The Bidding Details Report now includes:

• Quote Currency column next to Quantity, that displays currency specified by supplier for each line item while bidding for a round.
• For Sealed Bid, Bidding Details will be visible only when the round is inOpen, On Hold, Closed, Evaluation Started orEvaluation Closed status. The round details are not displayed otherwise. For non-submitted bids, submission status will be Not Submitted and Closed.
  • • For bids with statusesDraft or Submitted, NA or a blank screen will be displayed for SupplierQuote Currency, Base Price and TotalPrice.
    • For bids with statusesNot Submitted and Closed, Submitted and Closed, the actual value will be displayed for Supplier Quote Currency, Base Price andTotal Price.
    • When the round is in On Hold status, bid object may or may not exist. If bid object exists, then entry will be displayed in bidding details. Otherwise, no entry will be displayed.  
    • When round will be in Closed, Evaluation Started, Evaluation Closed status and when bidding status will be Declined, then actual value will be displayed for Supplier Quote Currency, Base Price and Total Price.   
    • When round will be in On Hold or Open status, and bidding will be in Declined status, then NA or a blank screen will be displayed for Supplier Quote Currency, Base Price and Total Price.

• For OpenRFx, Bidding Details will be visible when the round is in Open, On Hold, Closed, Evaluation Started or Evaluation Closed status. The round details are not displayed otherwise.
  • When the bid is Surrogate, then the actual values will be displayed for Supplier Quote Currency, Base Price and Total Price. Also, to highlight that the bid is surrogated, the Bidding Status column will be marked with * symbol. For example, Submitted *.    
  • For the bid in Draft status, NA or a blank screen will be displayed for Supplier Quote Currency, Base Price andTotal Price.
  • When the bid will be in Not Submitted and Closed, Declined, Submitted, Submitted and Closed status, then actual values will be displayed for Supplier Quote Currency, Base Price andTotal Price.
  • When the round will be On Hold status, bid object may or may not exist. If bid object exists, then entry will be displayed in bidding details. Otherwise, no entry will be displayed.