From ICIHelp7.16
Jump to: navigation, search
 
(70 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
= 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 [http://int-wiki.cloudapp.net:8085/ICMHelp7.12/index.php?title=ICM_Help 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 [https://icertis365.sharepoint.com/sites/PartnerPortal/Shared%20Documents/Forms/AllItems.aspx?newTargetListUrl=/sites/PartnerPortal/Shared%20Documents&viewpath=/sites/PartnerPortal/Shared%20Documents/Forms/AllItems.aspx&viewid=29700541-b0d8-4150-b240-6aee2bc1cd05&id=/sites/PartnerPortal/Shared%20Documents/ICM%20Platform/Release%20Management/SDK here].
 
  
 
 
 
 
  
=== Sourcing Application Enhancements ===
 
  
'''571048 – Displaying full names of supplier contacts'''
+
= ICI Proposal Management App =
  
Previously, when selecting a supplier contact, only the first name of the supplier contact was displayed.
+
== Overview of Release 7.15 ==
  
With this release:
+
In the 7.15 Release , Icertis is expanding its market coverage by introducing the Proposal Management application and increasing the value to the sales and marketing functions in the enterprise set up. 
  
*The ''Supplier Contacts'' window user interface has been improved.  
+
With the App, Icertis has devised an opportunity to introduce out-of-the-box entities, drive the lifecycle and entire business process that begins with the inputs from an RFx, qualifies them, plans and reverts with a proposal, and finally facilitates the completion of the proposal. In addition, Icertis gives the flexibility to configure the Proposal Management App as per the customer requirement, making it a truly enterprise App.
*The name of existing Supplier Contact Name column has been modified to ''Supplier Contact Full Name''. For example, Tom Sibley instead of Tom.
+
<div class="image-green-border">[[File:7.15 PM App Release Notes Screenshot 01.png|720px|7.15 PM App Release Notes Screenshot 01.png]]</div>
*Buyers can remove a supplier contact from the ''Supplier Contact ''page. This updates the count of selected supplier contacts.  
+
These release notes provide an overview of the ICI Proposal Management App.
*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.
+
== The Terminology ==
  
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.
+
Here are some terms that will help you better understand the Proposal Management process:
 +
<div class="image-green-border">[[File:7.15 PM App Release Notes Screenshot 02.PNG|720px|7.15 PM App Release Notes Screenshot 02.PNG]]</div> <div class="image-green-border">[[File:7.15 PM App Release Notes Screenshot 03.PNG|720px|7.15 PM App Release Notes Screenshot 03.PNG]]</div> <div class="image-green-border">&nbsp;</div>
 +
== The Challenge ==
 +
<div class="image-green-border">Some key challenges to overcome in order to set and mature your sell side practice include:</div> <div class="image-green-border">&nbsp;</div>
 +
*Absence of a mature proposal management setup
 +
**The proposal management process is not structured and is run ad-hoc. Dashboards to get an insight to metrics such as win rate or capture ratio are not available. Also, as organizations mature, they need insights to devise their strategy (for example, if win rate has decreased over time) and the tools to enforce business processes.&nbsp; 
 +
*No single platform for seamless collaboration
 +
**Enterprises rely on system of systems and expect seamless interplay of data across systems. As a result of disparate systems, data is fragmented across systems or entities which does not let leadership have insights on win rate, capture ratio, etc. 
 +
*Nightmare to manage, track and compile tasks
 +
**Identifying and managing tasks between cross-functional stakeholder teams and completing proposals on stringent timelines are arduous.&nbsp; 
 +
*Cumbersome content and knowledge management
 +
**Reviewing, managing and reusing content is time consuming in addition to the challenges of quality and compliance that are critical for the business. Content and knowledge management repository is not present. For example, the organization receives multiple RFPs of similar nature. If a library of similar, reusable content is maintained, then it will save time by utilizing the same answers and using a qualitative template. Due to the lack of such a repository, the user has to give the same responses repetitively and recreate new proposals each time using non-standard or non-qualitative templates, which is time-consuming and results in duplication of efforts. 
 +
<div class="image-green-border"><br/> These challenges help shape the solution framework for the ICI Proposal Management App.</div> <div class="image-green-border">&nbsp;</div>
 +
== The Opportunity ==
 +
<div class="image-green-border">For businesses, responding to Requests for Proposals (RFPs) is a regular process. However, each RFP is a sales opportunity which contributes to growth. It is, thus, imperative for the RFP to be successful as its execution will have a significant impact on the final outcome.&nbsp;</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">Keeping this in mind, Icertis introduces the Proposal Management App, which is built on the ICI platform that presents out-of-the-box entities to drive the entire business process. This essentially consists of creating and qualifying RFx, and responding to the buyers with the bid proposal.&nbsp;</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">The App provides the ability to track KPI metrics such as Win Rate, Value Capture Ratio, etc. that help in executing incoming solicitation types efficiently and improving response processes paving the way for a mature proposal management team over time.&nbsp;</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">ICI allows creating a contract-centric proposal process connected with Sourcing and Obligation Management to flexibly drive the end-to-end business process for enterprise needs.</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">[[File:7.15 PM App Release Notes Screenshot 04.png|720px|7.15 PM App Release Notes Screenshot 04.png]]</div> <div class="image-green-border">&nbsp;</div>
 +
== The Solution Framework ==
 +
<div class="image-green-border">The functional decomposition of how the overall solution framework from capturing the Sell Side RFx to initiating a contract followed by knowledge management through configuration, integration, and usage of entities includes the following:</div> <div class="image-green-border">&nbsp;</div>
 +
*'''Sell Side RFx Capture Management'''
 +
**Capture Sell Side RFx
 +
**Sign an NDA to participate in the RFx event
 +
**Capture RFx schedule, line items, key requirements, and terms
 +
**Qualify RFx and perform go/no-go decision to bid 
  
'''Note''': This is applicable for RFx, RFI, Rounds and Bulk Agreements.
+
*'''Proposal Management'''  
<div class="image-green-border">[[File:R1.png|720px|R1.png]]</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">
+
**Develop solution and proposal strategy
'''571053 – Displaying names of external and internal attachments as uploaded by the user'''
+
**Plan a bid schedule
 +
**Enrich proposal line items with quotes
 +
**Assemble proposal package
 +
**Approve proposal and submit 
  
Previously, when downloading the RFx package, the name of the downloaded package displayed names that were not the same as the folder structure of the RFx, and also created duplicate files. This made it difficult to identify the file that was uploaded and downloaded.
+
*'''Post-Win Management'''
 +
**Negotiate proposal with customer
 +
**Record proposal outcome
 +
**Obligation extraction and tracking
 +
**Initiate customer and supplier contracts post win 
  
Now,&nbsp;
+
*'''Knowledge Management'''
 +
**Update content&nbsp;
 +
**Tagged content for search and reuse
 +
**Historical proposals search 
 +
<div class="image-green-border"><br/> Based on this framework, the solution includes:</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">[[File:7.15 PM App Release Notes Screenshot 05.png|720px|7.15 PM App Release Notes Screenshot 05.png]]</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">&nbsp;</div>
 +
== The Benefits ==
  
*The file names will be the same when downloading or uploading them to ICM.
+
Icertis’ end-to-end solution connected with the ICI contract-led proposal management has several benefits including:
*The files will be downloaded as per the defined folder structure and folder naming conventions which helps users to easily identify files under individual folders of the RFx and avoid any discrepancies.
+
*The duplication of files being created has been handled by appending a numeric value to the file name.
+
  
'''Note''': This is applicable to both RFx and RFI.
+
*Increased speed-to-market and proposal quality by using strengths of the ICI platform to create proposals quickly and effectively using templates based on the nature of products and services in a proposal&nbsp;
 +
*Improved deal quality and profitability by building the right proposal with the right products, prices, and terms and conditions
 +
*Standard and customizable KPI tracking (win rate, capture ratio analysis), post-win contract and obligation tracking
 +
*Seamlessly connected experience with Sourcing, Contracting and Obligation Management
 +
*Increased ROI by realizing revenue and margins through proper governance on deal approvals
  
[[File:R2.png|720px|R2.png]]
+
== The Users ==
  
'''627740 – Ability to use any masterdata for supplier and supplier contacts'''
+
ICI Proposal Management typically involves the following set of users:
  
Previously, to add supplier contacts, the buyer could select them from a list of supplier and supplier contacts in the ''Supplier'' window. This list of contacts belonged to a particular masterdata contract type. The customers had their own masterdata contract type for maintaining supplier and supplier contacts.
+
*'''Capture Management Team:''' Includes members from the sales, business development, pre-sales teams, who would be involved in the process of capture management. This team will quickly capture the RFx, ensure right fidelity of the input to make a bid/ no-bid decision, get the downstream proposal qualification process as quickly as possible, and improve the quality of the proposal.
 
+
*'''Proposal Management Team:''' Includes members from the delivery, IT, legal, or product teams, who would be involved in the process of proposal management. This team will take a qualified RFx, plan and create a proposal with a winning strategy that covers all the requirements of the incoming RFx.&nbsp;
Now, buyers can use any supplier and supplier contact masterdata contract type to add suppliers.
+
*'''Sourcing/Procurement Team:''' Includes members who would be involved in the overall view of the inventory, state of vendor deliverables, etc. They are a common function which can plan for any procurement that might need to be planned for the case that bid proposal converts into actual contract and the entity needs to engage with vendors for respective deliverables.  
 
+
*'''Contracting (Legal) Team:''' Includes the standard legal function in an organization that helps qualify the RFx, convert the won proposal to appropriate customer/ supplier contracts.
'''Note:''' This is applicable to RFx and RFI.
+
*'''Knowledge Management Team:''' Includes members from the senior leadership within the sales and proposal teams who would be involved in the planning, curation, and baseline content reuse across bid proposal.  
  
 
&nbsp;
 
&nbsp;
</div>
 
=== Enhancements to Sourcing Entities Workflow ===
 
  
'''573430 – Sourcing entities workflow revamp'''
+
= The Proposal Management Process =
 +
<div class="image-green-border">[[File:7.15 PM App Release Notes Screenshot 06.png|720px|7.15 PM App Release Notes Screenshot 06.png]]</div>
 +
The Proposal Management process has the following stages:
  
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.
+
*'''Setting up and Configuring the App'''
 +
**The ICI Proposal Management App must be enabled on the customer environment.
 +
***Identify seeded configuration for the Proposal Management App
 +
***Use ICI platform navigation tiles to view and create proposal management entities
 +
***Extend the configuration for seeded proposal entities, attributes, workflows, rules that are necessary for the proposal management workflow
 +
***Set up templates, metadata, and clauses for Bid Proposals as per company policy   
  
[[File:R3.png|720px|R3.png]]
+
*'''Capture Management'''&nbsp;
 +
**Manually create Sell Side RFx (solicitation types such as RFP, RFQ, RFI, Tender)
 +
**Capture RFx details for Sell Side RFx (documents, key requirements, terms, templates, etc.), capture the RFx schedule/key dates or milestones of an event that occur on a selected date
 +
**Support API integration use cases out-of-the-box to create and capture Sell Side RFx
 +
**Sign NDAs while participating in RFx cycle
 +
**Manually extract and create RFx line items
 +
**Capture the audit history for changes to Sell Side RFx 
  
[[File:R4.png|720px|R4.png]]
+
*'''Qualifying Sell Side RFx'''
 +
**Qualify Sell Side RFx with a Go/No-Go decision to bid
 +
**Ability to set up questionnaires to assist the qualification process
 +
**Set up departmental approvals as part of the Sell Side RFx workflow 
  
'''590362 – Displaying bids of all suppliers to buyers throughout RFx lifecycle'''
+
*'''Creating and Planning Bid Schedule'''  
 +
**Create a bid proposal for a qualified Sell Side RFx
 +
**Inherit attributes and associations from Sell Side RFx to bid proposal record
 +
**Plan, create, and allocate tasks to cross-functional teams for proposal responses&nbsp; 
  
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).
+
*'''Managing the Bid Proposal Workflow'''
 +
**Use Own templates instead of third-party paper for assembly of clauses, template-variables, etc.
 +
**Track tasks for proposal responses that need to be fulfilled by one or more cross-functional team members
 +
**Set reminders and notifications to keep in the know and prevent missed deadlines
 +
**Send bid proposals for one-off reviews
 +
**Set up approval rules for various departmental approvals before finalizing the bid proposal and sending for signatures
 +
**Collaborate on various topics using the ICI platform between multiple stakeholders instead of using external tools such as email
 +
**Make amendments to submitted bid proposals 
  
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.
+
*'''Tracking Win/Loss Outcome'''
 +
**Capture the bid proposal outcome as win or loss
 +
**Capture win/loss attributes for better KPI tracking
 +
**Track the KPI metrics such as Win Rate, Capture Ratio, etc. on the ICI dashboard 
  
These statuses include:
+
*'''Knowledge Management'''
 +
**Have a common repository of knowledge (ICI masterdata) that includes content and framing for specific questions/sections in the bid proposal
 +
**Keep content updated (templates and clauses) at all times for reuse and reference
 +
**Use the advanced search (metadata and in-document) capability of the ICI platform to search for relevant historical proposals 
  
*''Submitted'': <ul style="list-style-type:circle;">
+
&nbsp;
</ul>  </ul>
+
  
</ul>
+
&nbsp;
  
</ul>
+
= Working with the Proposal Management App =
  
*Buyers and the user assigned as surrogate buyer can view the bids until the round is in ''Open'' status for open RFx.  
+
When implementing the Proposal Management App, some entities such as contract types and rules, necessary for the flow, are seeded. Using these seeded entities, proposal owners can populate an initial set of data imperative to the entity workflow.&nbsp;
*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 style="list-style-type:circle;">
+
A dedicated “Proposal Management” tile is introduced on the ICI Home page for customers who have the license for the App. Users having either “View” or “Manage” access to the proposal management contract types can access this tile and use the available options such as Sell Side RFx, Bid Proposal, to create and manage them. Here, you can work with existing Sell Side RFx and bid proposals, or create new ones.
</ul>  </ul>
+
<div class="image-green-border">[[File:7.15 PM App Release Notes Screenshot 07.png|720px|7.15 PM App Release Notes Screenshot 07.png]]</div>  
 +
The navigation tiles support localization and theming and can be configured by implementation teams.
  
</ul>
+
&nbsp;
  
*Buyers and the user assigned as a surrogate buyer can view the bids in ''Submitted ''status when the rounds are closed.
+
&nbsp;
  
*''Not Submitted and Closed: '' <ul style="list-style-type:circle;">
+
== Sell Side RFx Workflow ==
</ul>  </ul>
+
  
*The user assigned as a surrogate buyer can view the round till it is in ''Open ''status, similar to the supplier''.''
+
Proposal Management contract types must be configured as agreement contract type with Business Application Type as “Proposal Management” and Business Application Category as “Sell Side RFx”. It is controlled through role action mapping.
*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>
+
'''411748/749462 – Capture Management'''
  
</ul>
+
Sell Side RFx helps in converting incoming solicitation types efficiently and improving response processes paving the way for mature proposal management. &nbsp;
 +
<div class="image-green-border">[[File:7.15 PM App Release Notes Screenshot 08.png|720px|7.15 PM App Release Notes Screenshot 08.png]]</div>
 +
*'''Sell Side RFx:''' Selecting this option navigates the user to the “Advanced Search” page where a pre-defined saved search is rendered. This page acts as a Sell Side RFx index page that displays all the current Sell Side RFx. Details related to Sell Side RFx such as Sell Side RFx ID, Sell Side RFx Name, RFx Type, Business Status, Created Date, RFx Source, RFx Reference No., RFx Capture Date, RFx Capture Complete Date, are displayed along with the actions that can be taken on them.
 +
<div class="image-green-border">[[File:7.15 PM App Release Notes Screenshot 09.png|720px|7.15 PM App Release Notes Screenshot 09.png]]</div>
 +
*'''Create Sell Side RFx:''' Clicking this navigates the user to the “Create Agreement-Sell Side RFx” page to create a new Sell Side RFx.&nbsp;
 +
<div class="image-green-border">[[File:7.15 PM App Release Notes Screenshot 10.png|720px|7.15 PM App Release Notes Screenshot 10.png]]</div>  
 +
*'''Capture Management:''' In ICI, it is basically an association which may require approval from various business functions. The capturing process is typically performed by the sales teams of the organization which helps in qualifying the Sell Side RFx to be able to make the decision to bid or not. Some of these include Line Items, RFx Qualification, RFx Documents, and Proposal Templates.
  
</ul>
+
Sell Side RFx comprises of the incoming solicitation types that the suppliers receive including:
  
'''Note''': The bid responses are displayed or hidden based on whether the bid was submitted or not submitted by the suppliers.
+
*Invitation for Bid&nbsp;
 +
*Request for Quote&nbsp;
 +
*Request for Information
 +
*Tender
 +
*Request for Proposal&nbsp;
  
*''Declined: '' <ul style="list-style-type:circle;">
+
The solicitation types are converted into successful businesses after winning the contract. For example, a supplier may place a bid for a firm fixed price.&nbsp;
</ul>  </ul>
+
  
</ul>
+
The Sell Side RFx workflow is as follows:&nbsp;
  
</ul>
+
*'''Create Sell Side RFx:'''
 +
**Create a Sell Side RFx by capturing all RFx details such as line items, templates, etc. The RFx is now in the “Draft state”. 
  
*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.  
+
*'''Send for Approval:'''
 +
**Send the RFx for approval; it moves to the “Waiting for Approval” state.
 +
**If approved, the RFx qualification association will have to be created. The RFx moves to the “Awaiting Qualification” state.
 +
**If there is no approver, the Sell Side RFx is auto-approved; the status of the RFx moves to “Awaiting Qualification”.
 +
**If rejected or recalled, the RFx moves back to the “Draft” state.  
  
</ul>
+
Here is the workflow for Sell Side RFx at a glance:
 +
<div class="image-green-border">[[File:7.15 PM App Release Notes Screenshot 11.png|720px|7.15 PM App Release Notes Screenshot 11.png]]</div> <div class="image-green-border">[[File:7.15 PM App Release Notes Screenshot 12.png|720px|7.15 PM App Release Notes Screenshot 12.png]]</div>  
 +
&nbsp;
  
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.
+
'''412214 – Performing a bid/no-bid decision (RFx Qualification)'''
  
*''Open RFx'': <ul style="list-style-type:circle;">
+
RFx Qualification in ICI is basically an associated document with an approval workflow. Depending upon the type of RFx, the qualification may need approval from various business functions that help in making the decision about placing the bids.&nbsp;
</ul>  </ul>
+
  
</ul>
+
The capture management or the sales team of the organization may or may not revert to every RFx, but the team has to ensure that it meets the business objective, and then make the decision to bid or not. There can be only one RFx qualification for a Sell Side RFx.
 +
<div class="image-green-border">[[File:7.15 PM App Release Notes Screenshot 13.png|720px|7.15 PM App Release Notes Screenshot 13.png]]</div>
 +
The RFx Qualification workflow is as follows:&nbsp;
 +
<div class="image-green-border">[[File:7.15 PM App Release Notes Screenshot 14.png|720px|7.15 PM App Release Notes Screenshot 14.png]]</div>
 +
*'''Select Sell Side RFx for Qualification:'''
 +
**Go to “Proposal Management” > “RFx Qualification” and select a record on the index page. The status of the RFx Qualification is “Draft” and of the Sell Side RFx is “Awaiting Qualification” till a bid decision is made. 
  
</ul>
+
*Make a Bid Decision:
 +
**If the bid decision is made, the RFx qualification is sent for approval; the status of the Sell Side RFx moves to “Bid”, once the RFx Qualification is approved.
 +
**If the bid decision is rejected, the RFx qualification can be sent for approval; the status of the Sell Side RFx moves to “No Bid”, once the RFx Qualification is approved.&nbsp;
 +
**For any reason/rationale, if the bid decision cannot be made, the RFx qualification can be put on hold; the status of the Sell Side RFx moves to “No Bid”, once the RFx Qualification is approved.&nbsp; 
 +
<div class="image-green-border">[[File:7.15 PM App Release Notes Screenshot 15.png|720px|7.15 PM App Release Notes Screenshot 15.png]]</div>
 +
*'''Send RFX Qualification for Approval:'''
 +
**If the decision to bid is made, send the RFx Qualification for approval from the “Details” page. The RFx Qualifications moves to the “Waiting for Approval (from the Approver)” state.
 +
***If approved, the status of the RFx qualification moves to “Approved”.&nbsp;
 +
***If there is no approver, the RFx qualification is auto-approved; the status of the RFx qualification moves to “Approved”.
 +
***If rejected or recalled, the status of the RFx qualification moves back to “Draft”.   
 +
<div class="image-green-border">[[File:7.15 PM App Release Notes Screenshot 16.png|720px|7.15 PM App Release Notes Screenshot 16.png]]</div>  
 +
&nbsp;
  
*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.
+
&nbsp;
*The surrogate buyer can also view the bid response.
+
  
*''Sealed Envelope: '' <ul style="list-style-type:circle;">
+
== Bid Proposal Workflow ==
</ul>  </ul>
+
  
</ul>
+
Proposal Management contract types must be configured as agreement contract type with Business Application Type as “Proposal Management” and Business Application Category as “Bid Proposal”. It is controlled using role action mapping.
  
*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.
+
&nbsp;
*The suppliers who''Declined'' the bid will not be shortlisted for upcoming rounds nor can they revert decline to participate in the round again.
+
  
</ul>
+
'''412207/749476 – Bid Proposal Management'''
  
</ul>
+
Bid proposal comprises of the response provided by the supplier against the qualified RFx received such as Request for Quote, Request for Information, and so on. The Proposal Management team of the organization is typically responsible for creating the bid proposal based on the qualified RFx. A thorough review of the bid proposal is performed by the reviewer team ensuring that the proposal meets the business requirements, quality, and compliance standards.&nbsp;
<div class="image-green-border">[[File:R5.png|720px|R5.png]]</div> <div class="image-green-border">
+
'''572078 – Availability of bid analysis attributes and values in the bid analysis Excel'''
+
  
The bid analysis Excel will contain all the bids, for all the suppliers, for all the rounds. The bid analysis will also contain currency information of bid currency and RFx primary currency, along with bid analysis attributes converted to RFx primary currencies.
+
A typical bid proposal has the following associations:
  
An attribute for bid analysis is defined in the masterdata. Users can add the bid analysis attribute for each RFx item and specify its value while creating an RFx or associated document. This helps the buyer to get all the information in the Excel sheet to be able to easily analyze a bid for a supplier.
+
*Sell Side RFx – Associate a Sell Side RFx with a bid proposal if not already inherited while creating a bid proposal. A Bid Proposal can have only one Sell Side RFx Association.
 +
*Proposal Line Items&nbsp;
 +
*RFx Documents
 +
*Supporting documents, if any
 +
*Templates
 +
<div class="image-green-border">[[File:7.15 PM App Release Notes Screenshot 17.png|720px|7.15 PM App Release Notes Screenshot 17.png]]</div>
 +
While assembling the bid proposal, all ICI platform constructs such as templates, clauses, template variables, and functionalities such as deviation, agreement clauses, clause approver and so on work as per standard ICI behavior.
  
Buyers can now:
+
The bid proposal workflow is as follows:&nbsp;
  
*Download bid analysis excel at the bid and round levels. When bid analysis is performed at bid level, the downloaded bid analysis Excel will include the responses for a specific supplier whose bid was chosen. However, when bid analysis is performed at Round level, the downloaded bid analysis Excel will include the bid responses data for all the suppliers present in the round.  
+
*'''Create Bid Proposal'''
*Enter the values for bid analysis attributes and upload the bid analysis Excel sheet. The value of bid analysis attributes will be updated in the bid response.  
+
**After the Sell Side RFx is received and qualified, the proposal management team works on creating the bid proposal and tracking its progress until it is won or lost.&nbsp;
 +
**Go to “Proposal Management” > “Create Bid Proposal” to create the bid proposal in the “Draft” state.&nbsp;
 +
**The set of attributes allow capturing important elements for the bid proposal such as Customer or RFx Information (point of contact, key requirements, communication method, etc.), Bid Proposal Schedule (submission date, due diligence date, awarding date, etc.), Proposal Details (proposal manager, review dates, status, etc.), Authorization, and Outcome Tracking (win, loss, closed, etc.). 
 +
<div class="image-green-border">[[File:7.15 PM App Release Notes Screenshot 18.png|720px|7.15 PM App Release Notes Screenshot 18.png]]</div>
 +
*'''Request Review'''
 +
**Send the bid proposal for review; it moves to the “Review Pending (from Reviewer)” state. Whether approved or rejected, the bid proposal moves back to the “Draft” state.  
  
'''Note:''' Minimum one round has to be completed for any bid analysis.
+
*'''Send for Approval'''
 +
**Send the bid proposal for internal approval to the Proposal Manager or to the final approvers such as Head of Sales team. it moves to the “Waiting for Approval” state.
 +
***If approved by all approvers, the bid proposal moves to the “Approved” state.
 +
***If rejected by any approver, the RFx moves back to the “Draft” state.   
 +
<div class="image-green-border">[[File:7.15 PM App Release Notes Screenshot 19.png|720px|7.15 PM App Release Notes Screenshot 19.png]]</div>
 +
*'''Send for Signature'''
 +
**The bid proposal is sent for internal or external signature based on the selected signature sequence once the bid proposal is approved. The status of the bid proposal is “Waiting for Internal/External Signature from Signatory”.
 +
***When signed by all signatories, the business status is “Bid Proposal Submitted”.   
 +
<div class="image-green-border">[[File:7.15 PM App Release Notes Screenshot 20.png|720px|7.15 PM App Release Notes Screenshot 20.png]]</div>
 +
*'''Tracking the Bid Proposal'''&nbsp;
 +
**Based on the submission, the proposal team tracks the bid outcome (the attributes and data that capture the win or loss for the bid proposal). This helps in establishing and measuring the benchmarks for win or loss tracking.
 +
***Depending on the selected bid outcome, the bid proposal status can be “Awaiting Outcome”, “Won”, “Lost”, “No Bid”, or “Closed”.   
 +
<div class="image-green-border">[[File:7.15 PM App Release Notes Screenshot 21.png|720px|7.15 PM App Release Notes Screenshot 21.png]]</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">[[File:7.15 PM App Release Notes Screenshot 22.png|720px|7.15 PM App Release Notes Screenshot 22.png]]</div>
 +
*'''Collaborating through Proposal Process'''&nbsp;
 +
**A key aspect of the ICI Proposal Management App is the ability to use the “Collaboration” tab on the platform, at any stage, which is a dedicated space available within the proposal itself, to communicate between multiple stakeholders.&nbsp;
 +
***Create a New Topic from the “Collaboration” tab on the bid proposal “Details” page. Specify details such as Participants, Confidentiality, Message, etc.   
 +
<div class="image-green-border">[[File:7.15 PM App Release Notes Screenshot 23.png|720px|7.15 PM App Release Notes Screenshot 23.png]]</div>
 +
*'''Managing Bid Proposal using Commitments'''&nbsp;
 +
**Commitments can be added to the proposal which can serve as reminders of the tasks and actions that need to be taken for tracking bid proposals to ensure that the necessary obligations are completed on time.
 +
***Add Commitments from the “Commitments” tab on the bid proposal “Details” page. Specify details such as Commitment Type (Clause, Meta Data, Risk, Transaction), Due Date, Instructions, Reminder, etc.   
 +
<div class="image-green-border">[[File:7.15 PM App Release Notes Screenshot 24.png|720px|7.15 PM App Release Notes Screenshot 24.png]]</div>
 +
*'''Amending Bid Proposal'''
 +
**Submitted bid proposals can be edited only through amendments. For example, a supplier can submit changes while a round is still open, or when a supplier is shortlisted in a round and needs to provide additional details. The amendment is created in the “Draft” state.  
  
[[File:R6.png|720px|R6.png]]
+
Here is the workflow for Bid Proposal at a glance:
 +
<div class="image-green-border">[[File:7.15 PM App Release Notes Screenshot 25.png|720px|7.15 PM App Release Notes Screenshot 25.png]]</div> <div class="image-green-border">&nbsp;</div>
 +
&nbsp;
  
=== Copy RFx Workflow ===
+
&nbsp;
</div>
+
'''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.&nbsp;
+
 
+
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.
+
 
+
[[File:R7.png|720px|R7.png]]
+
 
+
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.
+
<div align="left" class="image-green-border">[[File:R8.png|720px|R8.png]]</div> <div align="left" class="image-green-border">&nbsp;</div> <div align="left" class="image-green-border">
+
When RFx modification is initiated:
+
 
+
*The RFx status changes to ''In Modification.''
+
*The status of rounds changes to On ''Hold'' (except rounds in ''Closed'''', Evaluation Started, Evaluation Closed'''''<b>statuses).</b>
+
*Buyers can: <ul style="list-style-type:circle;">
+
</ul>  </ul>
+
</ul>
+
</ul>
+
 
+
*Modify Line Items:
+
**
+
***Add line items for rounds in any status, except ''Closed'' or ''Evaluation'' related statuses.
+
***Edit line item attribute values for rounds in ''Draft'' or ''Waiting for Approval'' statuses, and for any round that might be created in future post RFx modification approval.
+
***Remove the line items through shortlisting. User can mark them as not selected for rounds in ''Draft'' and ''Waiting for Approval'' statuses, and for any round that might be created in future post RFx modification approval.   
+
 
+
*
+
**Modify Supplier and Supplier Contacts:
+
***Add new suppliers for rounds in any status, except ''Closed'' and ''Evaluation'' related statuses.
+
***Add new supplier contacts to existing supplier for rounds in any status, except ''Closed'' and ''Evaluation'' related statuses.
+
***Remove supplier through shortlisting. User can mark them as not selected for rounds in ''Draft'' and ''Waiting for Approval'' statuses, and for any round that might be created in future post RFx modification approval. 
+
**Modify Questionnaires:
+
***Add new questionnaires for rounds in any status, except ''Closed'' and Evaluation related statuses.
+
***Add new questions to existing questionnaire for rounds in any status except ''Closed ''and Evaluation related statuses. 
+
**Modify External Attachments:
+
***Buyer can add, edit and remove external attachments.
+
***When new attachments are added or existing attachments are modified, then the supplier will get the access once RFx modification is approved and at least one round is in ''Open'' status. However, suppliers will still have access to other attachments that have not been modified. 
+
**Update Selective RFx Attributes:
+
***Buyers can selectively edit attributes, except those that have been configured by the Administrator as non-editable.
+
***The attribute changes are displayed in the audit history.   
+
'''&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Note''': Modifying selective attributes is a specific solution when RFx is ''In Modification'' status which is not a standard framework across the sourcing application. &nbsp; <ul style="list-style-type:circle;">
+
<li>Enable or Disable Configuration Keys (''Allow Line Item changes in RFx/ Allow Supplier Attachment changes in RFx/ Allow New Question/ Allow New Supplier During RFx Phase''):</li>
+
<li>''Allow Line Item changes in RFx'': If this key is enabled, then buyers can add/edit line items through UI or Excel when RFx is ''in modification''. If key is disabled, then add/ edit will not be allowed when RFx is ''in modification''.</li>
+
<li>''Allow New Supplier During RFx Phase/ Allow Supplier Attachment changes in RFx/ Allow New Question:''</li>
+
</ul>
+
 
+
If any of the keys is enabled, then buyers can make changes to supplier/ supplier attachment/ questions respectively when RFx is in modification. If the key is disabled, then respective changes will not be allowed when RFx is ''in modification''.&nbsp;
+
 
+
*The supplier cannot take actions such as ''Submit'', ''Recall'', and''Decline RFx ''on bids''.''&nbsp;
+
 
+
For RFx modification approval, the ''Administrator'' can configure rules to set the Approver. Approver can approve or reject the changes:
+
<ul style="list-style-type:circle;">
+
<li>If the buyer recalls the modification approval or approver rejects the changes, then RFx moves to the ''In Modification'' status.</li>
+
<li>If the changes are approved, then the round and RFx status recalculation is done. For example, when RFx is in ''Bidding Open'' status, and round is in ''Open ''status, and buyer initiates modification, then the round will move to ''On Hold'' and RFx will move to ''In Modification'' status. When the buyer makes the required changes, and the changes are approved, then status recalculation is done based on round end date.</li>
+
</ul>
+
 
+
*If the round end date has passed, then round status will move to ''Closed ''and corresponding RFx status will move to ''Bidding Closed.''&nbsp;
+
*If the round end date has not passed, then round status will move to ''Open'', and corresponding RFx status will move to ''Bidding Open.'' In this case, the supplier will then be able to access bid and can perform actions such as ''Submit, Decline and Recall.''
+
 
+
When no Approver has been added, the RFx is auto-approved.
+
 
+
=== &nbsp;RFx Evaluation Workflow ===
+
 
+
'''567274 – Ability to evaluate suppliers for RFx'''
+
 
+
Users require a provision to evaluate the RFx for various suppliers on their capabilities. Also, they want to provide the scores for better information that will help them in the awarding process.&nbsp;
+
 
+
Now, buyers and administrators can conduct a review, and evaluators can score the suppliers as well as provide feedback upon the supplier submissions.
+
 
+
Buyers can now:
+
 
+
*Create evaluation types.
+
*Define evaluation criteria.&nbsp;
+
*Enable or disable evaluation in round.&nbsp;
+
*Add evaluation type and evaluation criteria to the round.
+
*Add users or a team as evaluators.
+
*View different statuses during evaluation process such as ''Evaluation Started'' and''Evaluation Closed.''
+
*Close the Evaluation, and view/ analyze ratings given by evaluators.
+
 
+
Assigned evaluators will now:
+
 
+
*Receive notification about the evaluation that needs to be performed.
+
*View evaluation type and evaluation criteria assigned to them.
+
*Perform an evaluation and submit the ratings.
+
 
+
The ''Start Evaluation'' button will be available only after the round is closed.
+
</div> <div class="image-green-border">[[File:R9.png|720px|R9.png]]</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">&nbsp;</div>
+
=== 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 style="list-style-type:circle;">
+
</ul>  </ul>
+
 
+
</ul>
+
 
+
</ul>
+
 
+
*Add currencies to the currency masterdata that contains a list of currencies that can be used in an RFx event.
+
*Manage currencies from the currency master by adding new currency and currency symbol.
+
*Set a single currency as a corporate currency for the organization to be used in Sourcing reporting.
+
*Restrict the option to delete the currency and only allow making it inactive.
+
 
+
'''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: <ul style="list-style-type:circle;">
+
</ul>  </ul>
+
 
+
</ul>
+
 
+
</ul>
+
 
+
*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.
+
 
+
</ul> '''Note''': Duplication of exchange rates for same currency and same validation is not allowed.
+
 
+
*Select the primary and allowed currency for the RFx: <ul style="list-style-type:circle;">
+
</ul>  </ul>
+
 
+
</ul>
+
 
+
</ul>
+
 
+
*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.
+
 
+
</ul> 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 style="list-style-type:circle;">
+
</ul>  </ul>
+
 
+
</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 style="list-style-type:circle;">
+
</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.
+
<ul style="list-style-type:circle;">
+
<li>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.</li>
+
</ul>
+
 
+
*Use conversion rates in bid analysis Excel: <ul style="list-style-type:circle;">
+
</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.   
+
<ul style="list-style-type:circle;">
+
<li>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.  </li>
+
 
+
 
+
*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.&nbsp;
+
*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.
+
<div class="image-green-border">[[File:R10.png|720px|R10.png]]</div>
+
'''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 a''Enable 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''
+
<div class="image-green-border">''[[File:R11.png|720px|R11.png]]''</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">'''566709 – Prerequisite and mandatory contract validations for shortlisted suppliers'''</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">Previously, the prerequisite and mandatory contract validations were being displayed for all suppliers despite not being shortlisted in RFx.</div> <div class="image-green-border">
+
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'''
+
</div> <div class="image-green-border">
+
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.
+
 
+
=== <span style="font-size: 1.17em; font-weight: bold;">Sourcing Reports</span> ===
+
</div>
+
'''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. &nbsp;
+
 
+
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: <ul style="list-style-type:circle;">
+
</ul>  </ul>
+
 
+
*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: <ul style="list-style-type:circle;">
+
</ul>  </ul>
+
 
+
</ul>
+
 
+
*The RFx status displayed as ''Bidding Closed, Bidding Scheduled, Bidding Open'' in conjunction with the revamped RFx workflow.
+
*&nbsp;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: <ul style="list-style-type:circle;">
+
</ul>  </ul>
+
 
+
</ul>
+
 
+
*''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 in''Open, On Hold, Closed'', ''Evaluation Started ''or''Evaluation Closed ''status''.'' The round details are not displayed otherwise. For non-submitted bids, submission status will be ''Not Submitted and Closed.''
+
**
+
***For bids with statuses''Draft or Submitted, NA or ''a blank screen will be displayed for Supplier''Quote Currency, Base Price and ''Total''Price.''
+
***For bids with statuses''Not Submitted and Closed, Submitted and Closed, ''the actual value will be displayed for ''Supplier Quote Currency, Base Price ''and''Total 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.&nbsp;&nbsp;
+
***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.&nbsp;&nbsp;&nbsp;''
+
***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 Open''RFx'', ''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 *''. &nbsp;&nbsp;&nbsp;
+
**For the bid in ''Draft'' status, NA or a blank screen will be displayed for ''Supplier Quote Currency, Base Price ''and''Total 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 ''and''Total 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.&nbsp; 
+
  
 
&nbsp;
 
&nbsp;
Line 512: Line 271:
 
&nbsp;
 
&nbsp;
  
= &nbsp; =
+
'''Related Topics:'''&nbsp;[[Agreement_Management|Agreement Management]]&nbsp;| [[Association_Management|Association Management]] | [[Compliance_Management|Compliance Management]] | [[Template_Management|Template Management]] | [[Clause_Management|Clause Management]] | [[Configuration|Configuration]] | [[Reports|Reports]]&nbsp;| [[Advanced_Analytics|Advanced Analytics]] | [[User_Administration|User Administration]] | [[ICI_Tools|ICI Tools ]]|&nbsp; [[Icertis_Business_Apps|Icertis Business Apps]] | [[AI_Apps|AI Apps]]&nbsp;| [[ICI_Add-ins|ICI Add-ins]] | [[ICI_Mobile_App|ICI Mobile App]] | [[Release_Notes|7.15&nbsp;Release Notes]]&nbsp;|

Latest revision as of 13:42, 19 February 2021

 


ICI Proposal Management App

Overview of Release 7.15

In the 7.15 Release , Icertis is expanding its market coverage by introducing the Proposal Management application and increasing the value to the sales and marketing functions in the enterprise set up. 

With the App, Icertis has devised an opportunity to introduce out-of-the-box entities, drive the lifecycle and entire business process that begins with the inputs from an RFx, qualifies them, plans and reverts with a proposal, and finally facilitates the completion of the proposal. In addition, Icertis gives the flexibility to configure the Proposal Management App as per the customer requirement, making it a truly enterprise App.

7.15 PM App Release Notes Screenshot 01.png

These release notes provide an overview of the ICI Proposal Management App.

The Terminology

Here are some terms that will help you better understand the Proposal Management process:

7.15 PM App Release Notes Screenshot 02.PNG
7.15 PM App Release Notes Screenshot 03.PNG
 

The Challenge

Some key challenges to overcome in order to set and mature your sell side practice include:
 
  • Absence of a mature proposal management setup
    • The proposal management process is not structured and is run ad-hoc. Dashboards to get an insight to metrics such as win rate or capture ratio are not available. Also, as organizations mature, they need insights to devise their strategy (for example, if win rate has decreased over time) and the tools to enforce business processes. 
  • No single platform for seamless collaboration
    • Enterprises rely on system of systems and expect seamless interplay of data across systems. As a result of disparate systems, data is fragmented across systems or entities which does not let leadership have insights on win rate, capture ratio, etc.
  • Nightmare to manage, track and compile tasks
    • Identifying and managing tasks between cross-functional stakeholder teams and completing proposals on stringent timelines are arduous. 
  • Cumbersome content and knowledge management
    • Reviewing, managing and reusing content is time consuming in addition to the challenges of quality and compliance that are critical for the business. Content and knowledge management repository is not present. For example, the organization receives multiple RFPs of similar nature. If a library of similar, reusable content is maintained, then it will save time by utilizing the same answers and using a qualitative template. Due to the lack of such a repository, the user has to give the same responses repetitively and recreate new proposals each time using non-standard or non-qualitative templates, which is time-consuming and results in duplication of efforts.

These challenges help shape the solution framework for the ICI Proposal Management App.
 

The Opportunity

For businesses, responding to Requests for Proposals (RFPs) is a regular process. However, each RFP is a sales opportunity which contributes to growth. It is, thus, imperative for the RFP to be successful as its execution will have a significant impact on the final outcome. 
 
Keeping this in mind, Icertis introduces the Proposal Management App, which is built on the ICI platform that presents out-of-the-box entities to drive the entire business process. This essentially consists of creating and qualifying RFx, and responding to the buyers with the bid proposal. 
 
The App provides the ability to track KPI metrics such as Win Rate, Value Capture Ratio, etc. that help in executing incoming solicitation types efficiently and improving response processes paving the way for a mature proposal management team over time. 
 
ICI allows creating a contract-centric proposal process connected with Sourcing and Obligation Management to flexibly drive the end-to-end business process for enterprise needs.
 
7.15 PM App Release Notes Screenshot 04.png
 

The Solution Framework

The functional decomposition of how the overall solution framework from capturing the Sell Side RFx to initiating a contract followed by knowledge management through configuration, integration, and usage of entities includes the following:
 
  • Sell Side RFx Capture Management
    • Capture Sell Side RFx
    • Sign an NDA to participate in the RFx event
    • Capture RFx schedule, line items, key requirements, and terms
    • Qualify RFx and perform go/no-go decision to bid
  • Proposal Management
    • Develop solution and proposal strategy
    • Plan a bid schedule
    • Enrich proposal line items with quotes
    • Assemble proposal package
    • Approve proposal and submit
  • Post-Win Management
    • Negotiate proposal with customer
    • Record proposal outcome
    • Obligation extraction and tracking
    • Initiate customer and supplier contracts post win
  • Knowledge Management
    • Update content 
    • Tagged content for search and reuse
    • Historical proposals search

Based on this framework, the solution includes:
 
7.15 PM App Release Notes Screenshot 05.png
 
 

The Benefits

Icertis’ end-to-end solution connected with the ICI contract-led proposal management has several benefits including:

  • Increased speed-to-market and proposal quality by using strengths of the ICI platform to create proposals quickly and effectively using templates based on the nature of products and services in a proposal 
  • Improved deal quality and profitability by building the right proposal with the right products, prices, and terms and conditions
  • Standard and customizable KPI tracking (win rate, capture ratio analysis), post-win contract and obligation tracking
  • Seamlessly connected experience with Sourcing, Contracting and Obligation Management
  • Increased ROI by realizing revenue and margins through proper governance on deal approvals

The Users

ICI Proposal Management typically involves the following set of users:

  • Capture Management Team: Includes members from the sales, business development, pre-sales teams, who would be involved in the process of capture management. This team will quickly capture the RFx, ensure right fidelity of the input to make a bid/ no-bid decision, get the downstream proposal qualification process as quickly as possible, and improve the quality of the proposal.
  • Proposal Management Team: Includes members from the delivery, IT, legal, or product teams, who would be involved in the process of proposal management. This team will take a qualified RFx, plan and create a proposal with a winning strategy that covers all the requirements of the incoming RFx. 
  • Sourcing/Procurement Team: Includes members who would be involved in the overall view of the inventory, state of vendor deliverables, etc. They are a common function which can plan for any procurement that might need to be planned for the case that bid proposal converts into actual contract and the entity needs to engage with vendors for respective deliverables.
  • Contracting (Legal) Team: Includes the standard legal function in an organization that helps qualify the RFx, convert the won proposal to appropriate customer/ supplier contracts.
  • Knowledge Management Team: Includes members from the senior leadership within the sales and proposal teams who would be involved in the planning, curation, and baseline content reuse across bid proposal.

 

The Proposal Management Process

7.15 PM App Release Notes Screenshot 06.png

The Proposal Management process has the following stages:

  • Setting up and Configuring the App
    • The ICI Proposal Management App must be enabled on the customer environment.
      • Identify seeded configuration for the Proposal Management App
      • Use ICI platform navigation tiles to view and create proposal management entities
      • Extend the configuration for seeded proposal entities, attributes, workflows, rules that are necessary for the proposal management workflow
      • Set up templates, metadata, and clauses for Bid Proposals as per company policy
  • Capture Management 
    • Manually create Sell Side RFx (solicitation types such as RFP, RFQ, RFI, Tender)
    • Capture RFx details for Sell Side RFx (documents, key requirements, terms, templates, etc.), capture the RFx schedule/key dates or milestones of an event that occur on a selected date
    • Support API integration use cases out-of-the-box to create and capture Sell Side RFx
    • Sign NDAs while participating in RFx cycle
    • Manually extract and create RFx line items
    • Capture the audit history for changes to Sell Side RFx
  • Qualifying Sell Side RFx
    • Qualify Sell Side RFx with a Go/No-Go decision to bid
    • Ability to set up questionnaires to assist the qualification process
    • Set up departmental approvals as part of the Sell Side RFx workflow
  • Creating and Planning Bid Schedule
    • Create a bid proposal for a qualified Sell Side RFx
    • Inherit attributes and associations from Sell Side RFx to bid proposal record
    • Plan, create, and allocate tasks to cross-functional teams for proposal responses 
  • Managing the Bid Proposal Workflow
    • Use Own templates instead of third-party paper for assembly of clauses, template-variables, etc.
    • Track tasks for proposal responses that need to be fulfilled by one or more cross-functional team members
    • Set reminders and notifications to keep in the know and prevent missed deadlines
    • Send bid proposals for one-off reviews
    • Set up approval rules for various departmental approvals before finalizing the bid proposal and sending for signatures
    • Collaborate on various topics using the ICI platform between multiple stakeholders instead of using external tools such as email
    • Make amendments to submitted bid proposals
  • Tracking Win/Loss Outcome
    • Capture the bid proposal outcome as win or loss
    • Capture win/loss attributes for better KPI tracking
    • Track the KPI metrics such as Win Rate, Capture Ratio, etc. on the ICI dashboard
  • Knowledge Management
    • Have a common repository of knowledge (ICI masterdata) that includes content and framing for specific questions/sections in the bid proposal
    • Keep content updated (templates and clauses) at all times for reuse and reference
    • Use the advanced search (metadata and in-document) capability of the ICI platform to search for relevant historical proposals

 

 

Working with the Proposal Management App

When implementing the Proposal Management App, some entities such as contract types and rules, necessary for the flow, are seeded. Using these seeded entities, proposal owners can populate an initial set of data imperative to the entity workflow. 

A dedicated “Proposal Management” tile is introduced on the ICI Home page for customers who have the license for the App. Users having either “View” or “Manage” access to the proposal management contract types can access this tile and use the available options such as Sell Side RFx, Bid Proposal, to create and manage them. Here, you can work with existing Sell Side RFx and bid proposals, or create new ones.

7.15 PM App Release Notes Screenshot 07.png

The navigation tiles support localization and theming and can be configured by implementation teams.

 

 

Sell Side RFx Workflow

Proposal Management contract types must be configured as agreement contract type with Business Application Type as “Proposal Management” and Business Application Category as “Sell Side RFx”. It is controlled through role action mapping.

411748/749462 – Capture Management

Sell Side RFx helps in converting incoming solicitation types efficiently and improving response processes paving the way for mature proposal management.  

7.15 PM App Release Notes Screenshot 08.png
  • Sell Side RFx: Selecting this option navigates the user to the “Advanced Search” page where a pre-defined saved search is rendered. This page acts as a Sell Side RFx index page that displays all the current Sell Side RFx. Details related to Sell Side RFx such as Sell Side RFx ID, Sell Side RFx Name, RFx Type, Business Status, Created Date, RFx Source, RFx Reference No., RFx Capture Date, RFx Capture Complete Date, are displayed along with the actions that can be taken on them.
7.15 PM App Release Notes Screenshot 09.png
  • Create Sell Side RFx: Clicking this navigates the user to the “Create Agreement-Sell Side RFx” page to create a new Sell Side RFx. 
7.15 PM App Release Notes Screenshot 10.png
  • Capture Management: In ICI, it is basically an association which may require approval from various business functions. The capturing process is typically performed by the sales teams of the organization which helps in qualifying the Sell Side RFx to be able to make the decision to bid or not. Some of these include Line Items, RFx Qualification, RFx Documents, and Proposal Templates.

Sell Side RFx comprises of the incoming solicitation types that the suppliers receive including:

  • Invitation for Bid 
  • Request for Quote 
  • Request for Information
  • Tender
  • Request for Proposal 

The solicitation types are converted into successful businesses after winning the contract. For example, a supplier may place a bid for a firm fixed price. 

The Sell Side RFx workflow is as follows: 

  • Create Sell Side RFx:
    • Create a Sell Side RFx by capturing all RFx details such as line items, templates, etc. The RFx is now in the “Draft state”.
  • Send for Approval:
    • Send the RFx for approval; it moves to the “Waiting for Approval” state.
    • If approved, the RFx qualification association will have to be created. The RFx moves to the “Awaiting Qualification” state.
    • If there is no approver, the Sell Side RFx is auto-approved; the status of the RFx moves to “Awaiting Qualification”.
    • If rejected or recalled, the RFx moves back to the “Draft” state.

Here is the workflow for Sell Side RFx at a glance:

7.15 PM App Release Notes Screenshot 11.png
7.15 PM App Release Notes Screenshot 12.png

 

412214 – Performing a bid/no-bid decision (RFx Qualification)

RFx Qualification in ICI is basically an associated document with an approval workflow. Depending upon the type of RFx, the qualification may need approval from various business functions that help in making the decision about placing the bids. 

The capture management or the sales team of the organization may or may not revert to every RFx, but the team has to ensure that it meets the business objective, and then make the decision to bid or not. There can be only one RFx qualification for a Sell Side RFx.

7.15 PM App Release Notes Screenshot 13.png

The RFx Qualification workflow is as follows: 

7.15 PM App Release Notes Screenshot 14.png
  • Select Sell Side RFx for Qualification:
    • Go to “Proposal Management” > “RFx Qualification” and select a record on the index page. The status of the RFx Qualification is “Draft” and of the Sell Side RFx is “Awaiting Qualification” till a bid decision is made.
  • Make a Bid Decision:
    • If the bid decision is made, the RFx qualification is sent for approval; the status of the Sell Side RFx moves to “Bid”, once the RFx Qualification is approved.
    • If the bid decision is rejected, the RFx qualification can be sent for approval; the status of the Sell Side RFx moves to “No Bid”, once the RFx Qualification is approved. 
    • For any reason/rationale, if the bid decision cannot be made, the RFx qualification can be put on hold; the status of the Sell Side RFx moves to “No Bid”, once the RFx Qualification is approved. 
7.15 PM App Release Notes Screenshot 15.png
  • Send RFX Qualification for Approval:
    • If the decision to bid is made, send the RFx Qualification for approval from the “Details” page. The RFx Qualifications moves to the “Waiting for Approval (from the Approver)” state.
      • If approved, the status of the RFx qualification moves to “Approved”. 
      • If there is no approver, the RFx qualification is auto-approved; the status of the RFx qualification moves to “Approved”.
      • If rejected or recalled, the status of the RFx qualification moves back to “Draft”.
7.15 PM App Release Notes Screenshot 16.png

 

 

Bid Proposal Workflow

Proposal Management contract types must be configured as agreement contract type with Business Application Type as “Proposal Management” and Business Application Category as “Bid Proposal”. It is controlled using role action mapping.

 

412207/749476 – Bid Proposal Management

Bid proposal comprises of the response provided by the supplier against the qualified RFx received such as Request for Quote, Request for Information, and so on. The Proposal Management team of the organization is typically responsible for creating the bid proposal based on the qualified RFx. A thorough review of the bid proposal is performed by the reviewer team ensuring that the proposal meets the business requirements, quality, and compliance standards. 

A typical bid proposal has the following associations:

  • Sell Side RFx – Associate a Sell Side RFx with a bid proposal if not already inherited while creating a bid proposal. A Bid Proposal can have only one Sell Side RFx Association.
  • Proposal Line Items 
  • RFx Documents
  • Supporting documents, if any
  • Templates
7.15 PM App Release Notes Screenshot 17.png

While assembling the bid proposal, all ICI platform constructs such as templates, clauses, template variables, and functionalities such as deviation, agreement clauses, clause approver and so on work as per standard ICI behavior.

The bid proposal workflow is as follows: 

  • Create Bid Proposal
    • After the Sell Side RFx is received and qualified, the proposal management team works on creating the bid proposal and tracking its progress until it is won or lost. 
    • Go to “Proposal Management” > “Create Bid Proposal” to create the bid proposal in the “Draft” state. 
    • The set of attributes allow capturing important elements for the bid proposal such as Customer or RFx Information (point of contact, key requirements, communication method, etc.), Bid Proposal Schedule (submission date, due diligence date, awarding date, etc.), Proposal Details (proposal manager, review dates, status, etc.), Authorization, and Outcome Tracking (win, loss, closed, etc.).
7.15 PM App Release Notes Screenshot 18.png
  • Request Review
    • Send the bid proposal for review; it moves to the “Review Pending (from Reviewer)” state. Whether approved or rejected, the bid proposal moves back to the “Draft” state.
  • Send for Approval
    • Send the bid proposal for internal approval to the Proposal Manager or to the final approvers such as Head of Sales team. it moves to the “Waiting for Approval” state.
      • If approved by all approvers, the bid proposal moves to the “Approved” state.
      • If rejected by any approver, the RFx moves back to the “Draft” state.
7.15 PM App Release Notes Screenshot 19.png
  • Send for Signature
    • The bid proposal is sent for internal or external signature based on the selected signature sequence once the bid proposal is approved. The status of the bid proposal is “Waiting for Internal/External Signature from Signatory”.
      • When signed by all signatories, the business status is “Bid Proposal Submitted”.
7.15 PM App Release Notes Screenshot 20.png
  • Tracking the Bid Proposal 
    • Based on the submission, the proposal team tracks the bid outcome (the attributes and data that capture the win or loss for the bid proposal). This helps in establishing and measuring the benchmarks for win or loss tracking.
      • Depending on the selected bid outcome, the bid proposal status can be “Awaiting Outcome”, “Won”, “Lost”, “No Bid”, or “Closed”.
7.15 PM App Release Notes Screenshot 21.png
 
7.15 PM App Release Notes Screenshot 22.png
  • Collaborating through Proposal Process 
    • A key aspect of the ICI Proposal Management App is the ability to use the “Collaboration” tab on the platform, at any stage, which is a dedicated space available within the proposal itself, to communicate between multiple stakeholders. 
      • Create a New Topic from the “Collaboration” tab on the bid proposal “Details” page. Specify details such as Participants, Confidentiality, Message, etc.
7.15 PM App Release Notes Screenshot 23.png
  • Managing Bid Proposal using Commitments 
    • Commitments can be added to the proposal which can serve as reminders of the tasks and actions that need to be taken for tracking bid proposals to ensure that the necessary obligations are completed on time.
      • Add Commitments from the “Commitments” tab on the bid proposal “Details” page. Specify details such as Commitment Type (Clause, Meta Data, Risk, Transaction), Due Date, Instructions, Reminder, etc.
7.15 PM App Release Notes Screenshot 24.png
  • Amending Bid Proposal
    • Submitted bid proposals can be edited only through amendments. For example, a supplier can submit changes while a round is still open, or when a supplier is shortlisted in a round and needs to provide additional details. The amendment is created in the “Draft” state.

Here is the workflow for Bid Proposal at a glance:

7.15 PM App Release Notes Screenshot 25.png
 

 

 

 

 

Related Topics: Agreement Management | Association Management | Compliance Management | Template Management | Clause Management | Configuration | Reports | Advanced Analytics | User Administration | ICI Tools Icertis Business Apps | AI Apps | ICI Add-ins | ICI Mobile App | 7.15 Release Notes |