AI-Powered Contract and Case Management System for LG for the establishment of a Long Term Agreement (3 years with an option for 2 additional years).
UNOPS
AI-Powered Contract and Case Management System for LG for the establishment of a Long Term Agreement (3 years with an option for 2 additional years).
Request for proposal
Reference:
RFP/2024/55120
Beneficiary countries or territories:
Multiple destinations (see 'Countries' tab below)
Registration level:
Basic
Published on:
17-Feb-2025
Deadline on:
26-Mar-2025 16:00 (GMT 0.00)
Description
UNOPS is hereby inviting suppliers to bid for the establishment of Long-Term Agreements (LTAs) for the supply of a SaaS-based AI-Powered Contract and Case Management System for UNOPS Legal Group, as further described in the Schedule of Requirements.
Based on the results of this competitive bidding exercise, UNOPS intends to enter into non-exclusive Long-Term Agreement(s) (LTA) with a single vendor capable of providing the full scope of the required solution and other associated services (as outlined in the Schedule of Requirements). UNOPS, therefore, strongly encourages vendors to bid accordingly.
The Long-Term Agreement (LTA) encompasses a duration of three (3) years, with the option to extend for an additional two years, subject to vendor performance and price competitiveness.
----
IMPORTANT NOTE: Interested vendors must respond to this tender using the UNOPS eSourcing system, via the UNGM portal. In order to access the full UNOPS tender details, request clarifications on the tender, and submit a vendor response to a tender using the system, vendors need to be registered as a UNOPS vendor at the UNGM portal and be logged into UNGM. For guidance on how to register on UNGM and submit responses to UNOPS tenders in the UNOPS eSourcing system, please refer to the user guide and other resources available at: https://esourcing.unops.org/#/Help/Guides
Interested in improving your knowledge of what UNOPS procures, how we procure and how to become a vendor to supply to our organization? Learn more about our free online course on “Doing business with UNOPS” here
Based on the results of this competitive bidding exercise, UNOPS intends to enter into non-exclusive Long-Term Agreement(s) (LTA) with a single vendor capable of providing the full scope of the required solution and other associated services (as outlined in the Schedule of Requirements). UNOPS, therefore, strongly encourages vendors to bid accordingly.
The Long-Term Agreement (LTA) encompasses a duration of three (3) years, with the option to extend for an additional two years, subject to vendor performance and price competitiveness.
----
IMPORTANT NOTE: Interested vendors must respond to this tender using the UNOPS eSourcing system, via the UNGM portal. In order to access the full UNOPS tender details, request clarifications on the tender, and submit a vendor response to a tender using the system, vendors need to be registered as a UNOPS vendor at the UNGM portal and be logged into UNGM. For guidance on how to register on UNGM and submit responses to UNOPS tenders in the UNOPS eSourcing system, please refer to the user guide and other resources available at: https://esourcing.unops.org/#/Help/Guides
Interested in improving your knowledge of what UNOPS procures, how we procure and how to become a vendor to supply to our organization? Learn more about our free online course on “Doing business with UNOPS” here
This tender has been posted through the UNOPS eSourcing system. / Cet avis a été publié au moyen du système eSourcing de l'UNOPS. / Esta licitación ha sido publicada usando el sistema eSourcing de UNOPS. Vendor Guide / Guide pour Fournisseurs / Guíra para Proveedores: https://esourcing.unops.org/#/Help/Guides
First name:
N/A
Surname:
N/A
This procurement opportunity integrates considerations for at least one sustainability indicator. However, it does not meet the requirements to be considered sustainable.
Climate change mitigation and adaptation
Environmental
The tender contains sustainability considerations for preventing or minimizing damage associated with climate change.
Examples:
Energy efficiency, greenhouse gas reporting and emission offsetting.
Gender issues
Social
The tender contains sustainability considerations addressing gender equality and women's empowerment.
Examples:
Gender mainstreaming, targeted employment of women, promotion of women-owned businesses.
| Link | Description | |
|---|---|---|
| https://esourcing.unops.org/#/Help/Guides | UNOPS eSourcing – Vendor guide and other system resources / Guide pour fournisseurs et autres ressources sur le système / Guía para proveedores y otros recursos sobre el sistema |
43231501
-
Helpdesk or call center software
43231503
-
Procurement software
43231505
-
Human resources software
43231506
-
Materials requirements planning logistics and supply chain software
43231507
-
Project management software
43231508
-
Inventory management software
43231509
-
Bar coding software
43231510
-
Label making software
43231511
-
Expert system software
43231512
-
License management software
43231513
-
Office suite software
43231514
-
Sales and marketing software
43231515
-
Mailing and shipping software
43231516
-
Audit software
43231517
-
Procedure management software
New amendment added #4: 1. Revision of the date of the Deadline. The relevant Contract provisions indicated below are amended to read as follows; Deadline under General section: 2025-03-26 16:00 UTC2. Under Qualification Criteria 3.9, the requirement has been updated to state: “The vendor must possess a valid SOC 2 Type 2 certification or ISO/IEC 27001:2022 certification (evidence shall be provided).” This update has also been reflected in Section III: Evaluation Criteria, including the Documents to Establish Compliance with the Criteria, as well as in RFP_Section_IV_Returnable Bidding Forms.3. Additionally, in Section III: Evaluation Criteria, updates have been made to Qualification Criteria 3.1 and the related Documents to Establish Compliance with the Criteria.4. Furthermore, RFP_Section_IV_Returnable Bidding Forms has been revised to correct the numbering error, updating 1.6 to 1.7 in Section 1: Technical Criteria.
Edited on:
18-Mar-2025 11:04
Edited by:
webservice@unops.org
New clarification added: Q43. Section/Document Section II: Schedule of RequirementsExisting Clause Section 6.5: Legal Function - Digital Solution The timeline is indicated as 19 months. Request for Clarification The duration of the LTA is specified as 3 years with an option for 2 additional years. Request you kindly clarify what is the significance of the 19 months duration mentioned in the Schedule of Requirements, and how does it impact the delivery schedule. A43. Please disregard the 19 moth reference. It is an internal timeline Q44. Existing ClauseAutomated reminders and alerts for renewals, expirations, and other critical events.Request for ClarificationWhat is the purpose of email and SMS generation within the contract management solution? Should they be used solely for transactional alerts and notifications?Additionally, if notifications are to be generated by AI modules as well, how many SMS/email gateways will be required? Will the cost of generating these messages be directly borne by UNOPS? Please specify.Requested by: Elise Salaun (elise.salaun@ch.ey.com)Requested on: 2025-03-03A44. UNOPS expects the system to provide email (and in-system) alerts and notifications as part of the contract management workflow. Q45. Which ITSM tool is used by UNOPS?A45: UNOPS fail to see the relevance for this information to be disclosed as part of this tender.Q46. Fitness of the product in relation to functional requirements. Requirement ID F03.Versioning and Change Tracking: The system must support version control, allowing users to track changes to documents over time, including comparison capabilities between documents.Above is mentioned in Technical criteria. What you mean by “comparison capabilities between documents” (e.g. contents’ comparison in terms of words and/or versioning, dimensions…).A46. The product should be able clearly display/highlight changes to a document over time. Ideally directly in the document or through a versioning feature. Q47. Financial Form Existing Clause The volume for the purposes of discount determination is understood as cumulative purchasing volume of UNOPS and any other UN agency, fund or programme that elects to order the services from the vendor with reference to the UNOPS’s resulting LTAs, or to any derivative LTAs/contract (s) put in place by that UN entity based on the outcome of this competitive bidding conducted by UNOPS.Request for Clarification The nature of any derivative LTAs/contract (s) that may be put in place by any UN entity based on the outcome of this competitive bidding conducted by UNOPS, is unknown. Hence request to relax this clause, and modify it as "The volume for the purposes of discount determination is understood as cumulative purchasing volume of UNOPS and any other UN agency, fund or programme that elects to order the services from the vendor with reference to the UNOPS’s resulting LTAs, based on the outcome of this competitive bidding conducted by UNOPS.Please also confirm, that if any such derivative contracts by other UN entities be applicable, there needs to be an exclusive agreement, to such an extent to use the current LTA for pricing purposes. The duration of such contracts should be within the contract period as defined by the current LTA. A47. The clause ensures that cumulative purchasing volume across UNOPS and other UN entities using this LTA is considered for discount determination. This remain unchanged. Regarding derivative LTAs/contracts, any such agreements should align with the original LTA pricing framework, and their duration should not exceed the contract period of the current LTA unless otherwise agreedQ48. With reference to UNOPS_eSourcing_Vendor Guide_EN, in case of Joint Venture’s response submission, kindly specify whether a) each member of the Joint Venture have to access its personal area, fill in the Questionnaires and Supplier forms’ sections and attach the documentation (Document checklist and Financial offer details sections) requested to vendors, or b) the leading partner of the Joint Venture has to fill in the Questionnaires and Supplier forms’ sections only its own data and upload the whole documentation, including the documents of the Joint Venture’s members.A48. b) the leading partner of the Joint Venture has to fill in the Questionnaires and Supplier forms’ sections only its own data and upload the whole documentation, including the documents of the Joint Venture’s members.
Edited on:
17-Mar-2025 14:12
Edited by:
webservice@unops.org
New clarification added: Q38. As the tender requires the vendor to hold a valid SOC 2 Type 2 certification, could you confirm whether ISO/IEC 27001:2022 and ISO/IEC 27701:2019 certifications would be considered acceptable alternatives?A39. ISO/IEC 27001:2022 will be is an acceptable alternative for the SOC 2 Type 2 requirement in this tenderQ39. Can you confirm whether an ISO 27001 certification, which covers many of the same security and compliance areas as SOC 2 Type 2 and is verified through annual external audits, would be accepted as an equivalent alternative to meet the requirements outlined in criterion 3.9?A39. ISO/IEC 27001:2022 will be is an acceptable alternative for the SOC 2 Type 2 requirement in this tenderQ40. With reference to the “RFP_Section III_ Evaluation Criteria” and in particular “Qualification Criteria”, please kindly specify whether the SOC2 Type 2 certification could be replaced by certification ISO 27001:2022 with extensions to Guidelines ISO/IEC 27018:2019 and ISO/IEC 27017:2015.A40. ISO/IEC 27001:2022 will be is an acceptable alternative for the SOC 2 Type 2 requirement in this tenderQ41. As the tender requires the vendor to hold a valid SOC 2 Type 2 certification, could you confirm whether ISO/IEC 27001:2022 and ISO/IEC 27701:2019 certifications would be considered acceptable alternatives?A41. ISO/IEC 27001:2022 will be is an acceptable alternative for the SOC 2 Type 2 requirement in this tenderQ42. With reference to the “RFP_Section III_ Evaluation Criteria” and in particular “Qualification Criteria”, please kindly specify whether the SOC2 Type 2 certification could be replaced by the SOC 1 Type 2 certification.A42. No. SOC 1 Type 2 is mainly for financial controls and given the nature of content, UNOPS seeks certification on the broader range of security and privacy controls.
Edited on:
17-Mar-2025 13:41
Edited by:
webservice@unops.org
New clarification added: Q31. Hi, We see from the Q&A that you had an RFI phase before. Is it possible for you to share with us the document you issued for the RFI?A31. This project has a distinct scope, entirely separate from the EOI you mentioned.Q32. Please kindly specify whether the 8-questions available in the section "Questionnaires" of the “Vendor Submission” section in the web portal must be filled out only by the Leading Company in case of Joint Venture or by all members of the Joint Venture.A32. Yes, it can be filled only by Leading company in case of a Join Venture Q33. Please kindly specify whether the forms available in the section "Supplier Forms" of the web portal must be filled out only by the Leading Company in case of Joint Venture or by all members of the Joint Venture.A33. Form A: Joint Venture Partner Information Form should be filled by Leading company and should be signed by both JV parties. Other forms can be filled by Leading company. If any information is required from both JV party we will reach out for clarificationQ34. Please kindly specify whether the forms required in the section "Document checklist" of the web portal must be filled out only by the Leading Company in case of Joint Venture or by all members of the Joint Venture.A34. Form A: Joint Venture Partner Information Form should be filled by Leading company and should be signed by both JV parties. Other forms can be filled by Leading company. If any information is required from both JV party we will reach out for clarificationQ35. With reference to RFP_III section_Evaluation criteria, please kindly specify what is the document to establish compliance with UNGM number criteria.A35. For this please mention the UNGM number in returnable formsQ36. With reference to RFP_III section_Evaluation criteria, please kindly clarify whether the proposal documents may be signed with digital signatures.A36. Digital signatures are acceptable Q37. With reference to the Technical Criteria, please confirm that the criteria to be considered for the preparation of the Technical Proposal are those present in the document “RFP_Section III_Evaluation Criteria”, as there are discrepancies compared to the table present in the document “Form D Technical Proposal Form” (example: criteria 1.6 is identical to the criteria 1.7, and so on).A37. Please consider the RFP_Section III_Evaluation Criteria as the correct criteria. We will revise the Form D Technical Proposal Form accordingly
Edited on:
11-Mar-2025 16:51
Edited by:
webservice@unops.org
New clarification added: Q28. Q6. API Integration - What Upstream and Downstream Integration is needed. For Example: UNGMA28. For Data integration, the core need is the contracts themselves, where Single/Batch upload features through the user interface is expected. Google Drive integration is ideal. In terms of APIs, it is expected that the solution offers API access to primary data and metadata objects. Q29. Is there a Systems Integration or Contracting Transformation RFP that will be published to accompany this RFP? The following is a list of some considerations when setting up a Contract Lifecycle Management tool (in addition to the software licenses): -Structuring of the data,-user access management,-repository structure,-workflows/ approvals,-template consolidation-intake forms & assembly logic,A29. Please refer to the meeting minutesQ30. I am writing to formally request an extension for the deadline of the present RFP scheduled for the 20th of March.A30. Please note that the deadline has already been extended by one week, and due to the project timeline, we are unable to grant any further extensions.
Edited on:
11-Mar-2025 15:31
Edited by:
webservice@unops.org
New clarification added: Q28. Q6. API Integration - What Upstream and Downstream Integration is needed. For Example: UNGMA28. For Data integration, the core need is the contracts themselves, where Single/Batch upload features through the user interface is expected. Google Drive integration is ideal. In terms of APIs, it is expected that the solution offers API access to primary data and metadata objects. Q29. Is there a Systems Integration or Contracting Transformation RFP that will be published to accompany this RFP? The following is a list of some considerations when setting up a Contract Lifecycle Management tool (in addition to the software licenses): -Structuring of the data,-user access management,-repository structure,-workflows/ approvals,-template consolidation-intake forms & assembly logic,A29. Please refer to the meeting minutesQ30. I am writing to formally request an extension for the deadline of the present RFP scheduled for the 20th of March.A30. Please note that the deadline has already been extended by one week, and due to the project timeline, we are unable to grant any further extensions.
Edited on:
11-Mar-2025 15:09
Edited by:
webservice@unops.org
New clarification added: Q27. Dear UNOPS eSourcing Responsible,we forward our request for clarification regarding the RFP/2024/55120 of a contract management solution, in particular:please specify where, in the web portal, it is possible to upload the Financial statements to prove what we entered in Form F: Bidder financial capacity.A27. There is a mandatory section in the tender document submission section named "Form F: Bidder financial capacity cover page" where supplier should be able to upload the relavant documents
Edited on:
11-Mar-2025 10:53
Edited by:
webservice@unops.org
New amendment added #3: 1. Revision of the date of the, Deadline for clarifications. The relevant Contract provisions indicated below are amended to read as follows; Clarifications under General section:2025-03-14 11:00 UTC2. Adding Pre bid meeting minutes under Documents section
Edited on:
10-Mar-2025 16:22
Edited by:
webservice@unops.org
New clarification added: Q26. Section/Document Section III: Evaluation CriteriaExisting Clause Qualification Criteria2. Required Experience: Demonstrated experience providing similar solutions for large organizations, comparable in size to UNOPS (approximately 5,000 personnel).Provide Details of Two Contracts: Include details of 2 past or current contracts held with organizations of similar size within the last 5 years.Alternative Option: Alternatively, provide two client references from organizations of a comparable size to UNOPS, along with relevant case studies. • Case studies should highlight:o Services providedo Project outcomeso Key performance indicators (KPIs) Confidential Information: Confidential details may be omitted from the case studies. Usage Duration: Clients must have used the products for more than two years.Request for Clarification Request to please delete the criteria on Usage Duration, that the clients must have used the products for more than two years.A26. Please note that the criteria cannot be deleted
Edited on:
09-Mar-2025 09:40
Edited by:
webservice@unops.org
New clarification added: Q15. Section 6.5, Legal Function - Digital Solution, II- Detailed Scope & objectivesExisting Clause All past engagements signed by UNOPS in the last 15 years are captured in an easy-to-access tool and can be searched by region, partner, contract type, variances to the norm, etc…Request for Clarification Please share the expected volume of documents over the last 15 years (number of documents, pages per document). Also, please confirm on what % of the documents would be computer readable format vs images, etc requiring OCR services. A15. Regarding the number of documents, please refer to our answer to question 1 above. We unfortunately don’t have an average number of pages per document to communicate. It is expected that the majority, if not the entirety of documents, will be in computer readable format, including pdfs.Q16. Section II - Detailed Scope & ObjectivesExisting ClauseContract Creation and AuthoringRequest for Clarification What formats are the historical documents available in (e.g., scanned PDFs, machine-readable text, handwritten, multilingual)? Will the documents or contracts to be covered include languages other than the six standard UN languages?A17. UNOPS will expect the system to allow for manual (through the UI) binary document upload/download as a minimum. UNOPS will evaluate the proposed system on existing APIs and integration flexibility, including Google Drive for potential collaboration and authoring. There is no specific ERP system integration requirement.Q17. Are you looking at managing the contracts at an enterprise level? E.g. procurement contracts, legal contracts, HR contracts, sales contracts, customer contracts, etc. If yes, can you specify the bifurcation of these contracts into procurement, legal, HR, sales, etc.?A17. No, We don’tQ18. In terms of migration of 20,000 contracts, are all of these paper/physical contracts? If yes, what is the average number of pages per contract?A18. These are digital formats and we currently don't have an average.Q19. Our assumption is that for this evaluation, we need to provide commercials keeping in mind the user count of 101 users across UNOPS. Is this assumption correct? If yes, please provide us some more details in the next two questions.How many users will create contracts, templates, invite stakeholders, manage supplier negotiations, and set up alerts and reminders?How many users will process only contract reviews and approval/rejection?A19. The question is not clear. No of users is put up at 20Q20. Is it expected to trigger a contract draft from an external system?A20. Question is not clear Q21. Is it expected to push contract award details to an external system?A21. Question is not clear Q22. Is it expected to fetch contract utilization (PO/Invoice spend) from an external system?A22. Question is not clear Q23. Regarding the requirement: "The solution should match clauses or terms in a document with historical precedents within the repository, showing how similar clauses were handled previously." Can you elaborate on this requirement to help us better understand the use case here?A23. It means the solution should be able to identify various deviations of the same language over time in different contracts of the same type.Q24. Do you have or use any preferred eSignature provider? If you are interested in a new eSignature solution, please answer the next four questions.What is the volume of electronic documents (e-Document initiated by a sender to one or more recipients for the purpose of electronically signing)?How many internal members will be conducting the e-signing?How many external signatures are anticipated? (External signatures: where at least one party as recipient of Wrapper is an external member to the Licensee organization.)How many internal signatures are anticipated? (Internal signatures: where all parties to the Wrapper are internal members to the Licensee organizationA25. Please consider the answer to be No Q25. Do you want the software vendor to conduct end-to-end implementation of the solution, or are you looking for a system integrator to do the implementation for this project?Are you also looking for an implementation plan and cost proposal for this project at this stage, or is only the licensing fee required as part of the submission? If you want an implementation plan and cost proposal as well, please answer the questions below.Is there a dedicated IT team whose members shall be available during integration activities?Will this IT team be responsible for establishing integrations from UNOPS' side?Does UNOPS need the software vendor to establish end-to-end integration? (For example, from software modules to UNOPS end systems.)Can we understand the number of end systems that need to be integrated and the number of integration events (touchpoints)?Can we understand the current IT landscape at UNOPS?Can we understand the middleware that is being used?Will the procurement solution only be used by a central procurement team/department that is present at one location? If not, in which geographical locations/countries will the solutions be implemented?Our assumption is that you are looking at a big bang implementation across all procurement teams and geographies, where all products shall be covered in a single go-live, all at once. If this is supposed to be phased or region-wise, kindly share more details.Do you have any customized support requirements, such as onsite support, value workshops, etc.?A25. Answer 1-11:UNOPS is looking for an existing SaaS solution - and not a custom implementation project - where UNOPS, upon the initial onboarding (licenses, org setup for SSO, etc.), would be in a position to internally roll it out to users and ingest and work on data. UNOPS will perform any integration activities (use of APIs, configuration of available connectors) internally, and the vendor would not have access to UNOPS systems. It is expected that the offer includes any required onboarding activities and available support.
Edited on:
09-Mar-2025 08:47
Edited by:
webservice@unops.org
New amendment added #2: Revision of the date of the Deadline. The relevant Contract provisions indicated below are amended to read as follows; Deadline under General section:2025-03-20 16:00 UTC
Edited on:
04-Mar-2025 15:40
Edited by:
webservice@unops.org
New clarification added: Q5. Contract Volume - What is the volume of the contracts (Number of Contracts) for the past 15 years. Could you please share the number of contracts as indicated below from 2010 – till date? Year wise - Region wise -Country wise - Contract Type - Number of Contracts - Contract StatusA5. The current number of active engagements (the main type of contracts to be managed with the future tool) is 7.000 and we are averaging circa 500 new engagements per year (2023). We expect the future tool to allow us to provide this breakdown easily. Q6. Supplier Information - What is the anticipated number of new suppliers on-boarding and new suppliers (service providers) expected this year or Year on Year?A5. The solution is not meant to manage supplier contracts, but rather contracts and agreements with governments, NGOs and other UNOPS clients (which we call “engagements”). In terms of volume, there would be around 500 new engagements per year and with a historical baseline of approx. 7000.Q7. Contract | Document Volume - On average, how many documents are typically processed per customer during the Sourcing process? Year-On-Year Contract Growth (Document Volume by Year on Year)A7. Please find our answer above to question 5 on the volume of contracts. We assume that what is meant by “customer” is the UNOPS counterpart in these contracts. Please be aware that the contracts that are meant to be managed by the solution are not the result of a sourcing process.Q8. Total Volume of Documents covering for the 15 years assumed to be 20001. Please clarify.A8. Please see answer to question 5 above.Q9. Can you please provide a flowchart or detailed breakdown of the CLM workflow process for?Service Providers - ApprovalCLM Process Workflow – Creation, Amendments, Renewals, Extension, Termination, CancellationA9. We cannot provide these informationQ10. Q5. Rollout Strategy - UNOPS plans a phased rollout for the CLM solution implementation. Can you share the prioritization of CLM Solution Rollout Priorities ((e.g., Historical Contract migration to new system, CLM, UNOPS countries, Contract Analysis, Contract Authoring, Multi Language Support)?A10. UNOPS LG plans to make use of the solution by first uploading a qualitative range of historical contracts for the required data foundation for AI insights and features. Following this, the internal focus will be on exploring the Analysis and Authoring features on UNOPS data as outlined in the requirements. Q11. What Upstream and Downstream Integration is needed. For Example: UNGMA11. For Data integration, the core need is the contracts themselves, where Single/Batch upload features through the user interface is expected. Google Drive integration is ideal. In terms of APIs, it is expected that the solution offers API access to primary data and metadata objects.Q12. Please could you also provide information on contract types (buy-side sell-side any specific inter-company/organisation agreements)For these contract types please indicate volumes/values, Geography/regions, and languages.A12. The contracts of interest for LG are funding and projects agreements between UNOPS and its funding partners (IFIs, governments) as well as clients and beneficiaries (Governments, UN agencies, other clients)The current number of active engagements is 7.000 and we are averaging circa 500 new engagements per year (2023 numbers).They cover all regions and in the English, French and Spanish languages with few exceptions. We are not able to provide a more specific breakdownQ13. During the session (especially Q&A), we understood things that seem to contradict with your documentation, and we would like to ask for clarifications on these points.We understood that UNOPS is only looking for a tool to have access and review legal contracts, and not to cover authoring of contracts.This information contradicts Section II of your RFP, which clearly states that Contract creation and Authoring is part of the scope UNOPS is looking for.Can you please come back to us on whether authoring should be considered?A13. Please note that if there is any such contradiction, the information recorded in RFP prevails. Q14. We also heard during the call that the selected solution should be “plug and play” and that no implementation time is expected. This also contradicts Section II of your RFP, which under “Implementation Roadmap” shows a “blue arrow” representing 7-9 months implementation time. Can you please tell us what is the reality, as some implementation time is necessary for our solution, and we want to ensure we would be relevant responding ?A14. As per the RFP and Schedule of requirements, authoring is indeed part of the scope of the solution and no indication to the contrary was shared during the meeting:“Contract creation and authoring:o A centralized platform for drafting, reviewing, and approving contracts.”2- UNOPS expects the solution to be a SaaS delivered solution, where the implementation time will be for UNOPS to configure the solution for initial use (upload contracts, configure workflows and repositories, integrate with existing APIs etc.). Aside from any required customer onboarding (organization configuration, authentication federation, administrator assignments and so on), UNOPS does not see any distinct services required.
Edited on:
04-Mar-2025 15:10
Edited by:
webservice@unops.org
New clarification added: Q3. Given that UNOPS have a large digital transformation agenda that goes beyond the scope of this RFP, will any part of the evaluation criteria take the other 2 lots (Supplier Management & Sourcing) from the 2024 EOI into account for the award?A3. It will not. This project is entirely separate from the Request for Expression of Interest (EOI) to which you are referring. This Request for Proposal (RFP) focuses exclusively on the procurement of a SaaS-based, AI-powered Contract and Case Management System for the UNOPS Legal Group, as outlined in the Schedule of Requirements.This specific RFP addresses a standalone requirement designed to meet the operational needs of the Legal Group. Its primary objective is to enhance efficiency, compliance, and visibility across legal operations by streamlining contract drafting, review, and negotiation, identifying key clauses, risks, and deviations, while centralizing documentation, monitoring progress, and automating workflows.The evaluation and award process will be conducted in strict accordance with the criteria outlined in the RFP.Q4. During RFI stage we got the impression that the scope was S2C (Sourcing, Contracts, Supplier) and where you during our visit to you specifically expressed interest in sourcing functionality.Now in RFP, the sole focus is on CLM. What is the rational behind these changes in scope? Who (which department) will make the decision on this project? Procurement/Legal/Finance/IT etcA4. Please refer to the answer above in Q3. This project has a distinct scope, entirely separate from the EOI you mentioned.The evaluation process will be conducted by an evaluation panel appointed in accordance with the UNOPS Procurement Manual, based on the proposals submitted in response to the RFP and evaluated against the criteria outlined therein
Edited on:
27-Feb-2025 09:46
Edited by:
webservice@unops.org
New amendment added #1: Adding the Pre-bid meeting link RFP/2024/55120 - Pre-Bid meeting Monday, February 24 1.00PM - 1.50PM in CPH TimeGoogle Meet joining infoVideo call link: https://meet.google.com/wqd-bqqo-nqmOr dial: (US) +1 352-612-1071 PIN: 417 926 960#More phone numbers: https://tel.meet/wqd-bqqo-nqm?pin=5379386068307
Edited on:
21-Feb-2025 08:23
Edited by:
webservice@unops.org
New clarification added: Q2. There are references in the received documents indicating that there should be 3 more forms which we can not find:Form D: Technical Proposal FormForm E: Performance Statement FormForm F: Bidder financial capacity cover pagePlease advise where to find these documents and extend response team with # days it takes to resolve thisA2. Please refer to the RFP_Section_IV_Returnable Bidding Forms in the Document sections. All the returnable document can be found in this word document.
Edited on:
19-Feb-2025 15:31
Edited by:
webservice@unops.org
New clarification added: Q1. Is it mandatory to have SOC2 Type 2 certification?A2. As per the criteria 3.9 The vendor must possess a valid SOC 2 Type 2 certification and evidence shall be provided
Edited on:
19-Feb-2025 15:26
Edited by:
webservice@unops.org