RFP Services/The provision of service related to the developing of a Solid Waste Management Information System (SWMIS) in Lebanon.
UNOPS
RFP Services/The provision of service related to the developing of a Solid Waste Management Information System (SWMIS) in Lebanon.
Request for proposal
Reference:
RFP/2024/54789
Beneficiary countries or territories:
Lebanon
Registration level:
Basic
Published on:
28-Nov-2024
Deadline on:
21-Jan-2025 09:00 (GMT 0.00)
Description
Tender description: The provision of service related to the developing of a Solid Waste Management Information System (SWMIS) in Lebanon.
-----
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
-----
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.
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.
Human rights and labour issues
Social
The tender contains sustainability considerations related to human rights, fundamental principles and rights at work, occupational health and safety, fairly traded goods, targeted employment of people with disabilities, etc.
| 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 |
77101801
-
Environmental information systems
New clarification added: Bidder's Questions:We acknowledge that UNOPS has previously extended the deadline for the tender submission. However, due to the significant importance of the project to our organization and our partners, and the need to fully address its objectives, we kindly request an additional extension of the submission deadline.We would greatly appreciate your consideration of this request and look forward to your response.Please find below an additional question that requires your clarification:When would we consider a commercial entity as becoming a user of the SWM system? Is this based on its size, industry type, revenue, number of employees?UNOPS Response:1- Please note that the extension is not applicable and the offers to be submitted before the deadline of January 21 20252- A commercial entity may be classified as a user of the SWMIS based on any or a combination of the following criteria but not limited to:• Industry Type: If the entity operates in industries that generate, collect, transport, treat, or dispose of waste (e.g., manufacturing, logistics, waste management services).• Size of Operations: Entities with significant waste generation or management responsibilities, regardless of revenue or number of employees.• Regulatory Scope: Entities subject to waste reporting obligations under applicable laws (e.g., Law 80/2018). Regards
Edited on:
16-Jan-2025 15:17
Edited by:
webservice@unops.org
New clarification added: Bidder's Questions:We acknowledge that UNOPS has previously extended the deadline for the tender submission. However, due to the significant importance of the project to our organization and our partners, and the need to fully address its objectives, we kindly request an additional extension of the submission deadline.We would greatly appreciate your consideration of this request and look forward to your response.Please find below an additional question that requires your clarification:When would we consider a commercial entity as becoming a user of the SWM system? Is this based on its size, industry type, revenue, number of employees?UNOPS Response:1- Please note that the extension is not applicable and the offers to be submitted before the deadline of January 21 20252- A commercial entity may be classified as a user of the SWMIS based on any or a combination of the following criteria but not limited to:• Industry Type: If the entity operates in industries that generate, collect, transport, treat, or dispose of waste (e.g., manufacturing, logistics, waste management services).• Size of Operations: Entities with significant waste generation or management responsibilities, regardless of revenue or number of employees.• Regulatory Scope: Entities subject to waste reporting obligations under applicable laws (e.g., Law 80/2018). Regards
Edited on:
16-Jan-2025 15:15
Edited by:
webservice@unops.org
New clarification added: Bidder's Questions:1. Regarding 6.15.7 Framework: Node.js with Express.js or Python with Django/Flask for building the server-sideapplication, and 6.15.8 Languages: JavaScript (Node.js), Django or Python. Are these BE frameworks a proposition of examples? Or do we have to restrict to these? We usually use Java Spring boot as BE. 2. How many APIs should we have for IoT devices? 3. Is UNOPS determining the number of sites for the deployment of IoT devices? Or should we include a unit price per device with the final quanity and cost to be agreed upon with UNOPS at a later stage?UNOS Answers:1- The Back-end frameworks mentioned are to be abided by. You could propose diffrent BE Franewaorks we will check it during evaluation phase.2- Include a preliminary list of APIs (5–10 core APIs) for IoT integration for real time monitoring and transmission of data, with the option to adjust based on final requirements.3- As stated before, please provide a unit price for the IoT devices.Regards,Thank you.Best regards,Business Development TeamSiren Analytics
Edited on:
16-Jan-2025 15:12
Edited by:
webservice@unops.org
New clarification added: Bidder's Question:How flexible is the pricing template? We are ready with all our numbers but the template only has rows for infra related artifacts. There is no place to add development effort/charges and this effort, in our understanding, should not be devided between the ifra related rows. Can we add more rows to show development charges? It will obviously impact your percentages.UNOPS Response: Please add any extra rows under the others expenses section in Form C and the payment percentage will not be affected as it will be 100% after completion of each deliverable please check the amended tender documents which were published previously under e-sourcing (Documents tab) Regards
Edited on:
16-Jan-2025 15:08
Edited by:
webservice@unops.org
New clarification added: Bidder's Questions:1. There are thousands of trucks in Lebanon. Some of them old, some of them with either IoT device installed, or compatible to integration. Are we expected to provide and install IoT devices on all trucks. If so, do we have an estimate number for this requirement or should the proposal include a unit price for IoT devices with the budget becoming based on a variable?2. Regarding Mobile Devices/Tablet for Field Operations (quantity: 5-10), is it fair to assume all devices will need to be purchased ? Who will be responsible for the purchase of the devices? Is the quantity finalized or should the proposal include a unit price for those devices with the budget becoming based on a variable?3. Could you elaborate on Fleet Management and Driver assignment requirements ? How are these requirements impacted by truck not having GIS/GPS integrated ?4. Regarding Citize Engagement, does the requirement include building an E2E Complaint Management System with complaints moving through the system, tracked and resolved on the tool; Integrate with an existing Complaint Management tool; or build a simple process for complaints submission only on the tool?UNOPS Answers:1- There are no estimates numbers for the trucks at the moment, as stated previousely please provide a unit price for the IoT devices.2- The Service provider is responsible for the purchase of the Mobile Devices/Tablets based on the solution provided, please provide a unit price as well under row related to other costs.3- Fleet Management and Driver Assignment Requirements:Basic Features:• Inventory of all trucks (e.g., make, model, capacity, operational status).• Assignment of drivers to specific trucks or routes.• Scheduling and maintenance tracking for fleet vehicles.For trucks without GIS/GPS devices:• Fleet location tracking will be limited.• Management will rely on manual updates from drivers or operators.Consider proposing a hybrid solution:• GPS-enabled trucks provide real-time tracking.• Manual data entry workflows for non-GPS-enabled trucks.4- For the citizen engagement, any option of the proposed is acceptable.Regards
Edited on:
16-Jan-2025 15:02
Edited by:
webservice@unops.org
New clarification added: Bidders' Question:Could you kindly confirm if the truck weights are expected to be taken from IoT sensors to be installed in each truck or from the weighbridges at the facilities?UNOPS Response:As indiacted previously, The information is not avilable yet so please price the IoT sensors seperatley.Regards,
Edited on:
16-Jan-2025 14:59
Edited by:
webservice@unops.org
New clarification added: Bidder's Questions:Are we expected to procure IoT devices? if so, what are the technical requirements for these devices? Considering the fact that it is a cloud solution, is offline access to the application a hard requirement?UNOPS Responses:1.Yes, IoT devices are expected to be procured by the service provider.Technical Requirements for IoT Devices as stated in the ToR:Connectivity: Devices must support communication protocols such as Wi-Fi, LTE, MQTT, or HTTP for cloud integration.Data Collection: Ability to collect relevant metrics, such as weight (for weighbridges), GPS coordinates (for vehicles), and environmental parameters.Accuracy and Reliability: Devices should meet industry standards for precision and operate reliably under environmental conditions typical for waste management facilities.Compatibility: Devices must integrate seamlessly with the system and support real-time data transmission.Durability: Ruggedized for long-term use in industrial environments.Power Supply: Options for continuous power or long-lasting batteries to ensure uninterrupted operation.2.Offline access to the application is not a hard requirement. However, it can be a beneficial feature, particularly for field operations in areas with unreliable internet connectivity.Offline functionality may be useful for mobile devices or tablets used by field agents to collect data in real-time. Data entered offline should be stored locally on the device. Automatic synchronization with the system should occur once connectivity is restored.Regards,
Edited on:
15-Jan-2025 11:28
Edited by:
webservice@unops.org
New clarification added: Bidder's Question:Please find below an additional query for your kind attention: - Could you kindly confirm if the existing weighbridges in the facilities are IoT-enabled? If they are not, is manual data entry expected as an alternative?UNOPS Responses:These informations will be reveiled to the winner contractor during the meetings with the MoE. If the existing weighbridges in the facilities are IoT-enabled:They can be integrated directly with the system using IoT protocols. Real-time data can be transmitted automatically, reducing manual effort and improving accuracy. If the weighbridges are not IoT-enabled:Manual Data Entry: Operators will need to manually input the recorded weights into the system via predefined forms or interfaces.Implementation Details:Develop user-friendly data entry screens on an external application.Include validation checks to ensure the accuracy of manually entered data.Regards,
Edited on:
15-Jan-2025 11:25
Edited by:
webservice@unops.org
New clarification added: Bidder's clarifications:Please find below questions that require your clarification.Payment Terms: Are you considering payment terms per deliverable (Form C) or per phase (RFP Section II p.30)?Form G -Statement Performance Form: We have delivered goods as a series of contracts. Can contracts be considered as goods?RFP Section III Section 4.1.3 p.10: Should the tools be aligned with those listed in the deliverables (p.5, Form C)?Eligibility: Siren Analytics Lebanon was founded in 2020. Are we eligible if we submit audited statements for 2020, 2021, 2022, and 2023?UNOPS Responses:1- Kindly note that the Payment Terms outlined in both Form C and RFP Section II (p. 30) are the same. Please refer to the amended documents, which have been previously uploaded under the "e-Sourcing Documents" tab.2- Please note that the Bidder is required to complete Form G with details of projects that meet the technical criteria specified under Point 3.2 (Financial Stability), specifically; "The Offeror should be in continuous business of successfully supplying similar services and solutions with a similar nature and complexity as specified in this TOR undertaking at least two major contracts exceeding 200,000 USD each in the last (3) three years" prior to the bid submission deadline."3- The Bidder may submit audited financial statements for the years 2020, 2021, 2022, and 2023, provided that the annual sales turnover in any one of these years was at least 500,000 USD, as mentioned specified under RFP_Section_III -Section 3:Qualification criteria - Point 3.2 (Financial Stability)Regards
Edited on:
15-Jan-2025 11:13
Edited by:
webservice@unops.org
New clarification added: Bidder's Question: .......formally express our interest in participating in the upcoming RFP/2024/54789 titled "The provision of service related to the developing of a Solid Waste Management Information System (SWMIS) in Lebanon". We believe that our solution not only meets but also has the potential to exceed your project’s requirements, offering features that could add significant value to your operations.We request an extension of the tender submission deadline to ensure a comprehensive proposal reflecting our capabilities and addressing your objectives. We are enthusiastic about the opportunity to submit a proposal that exceeds your expectations. Your consideration of this request would be greatly appreciated, and we look forward to your positive response.UNOPS Response:Please note that the tender closing date already extended till 21- Jan -2025 and further extension is not applicable.Best Regards
Edited on:
14-Jan-2025 07:13
Edited by:
webservice@unops.org
New clarification added: Bidder's Question:Please find below an additional query for your kind attention: - Could you kindly confirm whether the timeline mentioned in Section 9 refers to working days or calendar days? UNOPS Answer:Kindly find under e-sourcing document tab the amended document named (RFP_Section_II_Schedule of Requirements. (Amendement#3) - Para-9-Reporting Requirements Documentation) in which the durations in the table were identified and highlighted in Yellow.Regards,
Edited on:
13-Jan-2025 12:32
Edited by:
webservice@unops.org
New amendment added #8: This amendment#8 was raised to add the amended document named (RFP_Section_II_Schedule of Requirements. (Amendement#3)) para -9-Reporting Requirements and Documentation - Duration Table
Edited on:
13-Jan-2025 12:29
Edited by:
webservice@unops.org
New clarification added: Bidder Question:We are writing to kindly request an extension of the proposal submission deadline by two weeks. This additional time would allow us to prepare a competitive and comprehensive offer.We appreciate your understanding and consideration of this request.UNOPS Response:Please note that the tender closing date already extended till 21- Jan -2025 and further extension is not applicable.Best Regards
Edited on:
13-Jan-2025 10:04
Edited by:
webservice@unops.org
New amendment added #7: This amendment#7 was raised to add the amended documents named (RFP_Section_II_Schedule of Requirements. (Amendement#2))The amendment made to (section 10-Terms of Payment) to match payment terms mentioned in all documents.
Edited on:
09-Jan-2025 11:32
Edited by:
webservice@unops.org
New clarification added: Bidder's Question:Could you please confirm if the project durations mentioned in TOR "Section 9 Reporting Requirements and Documentation" are the correct ones to follow? There appear to be discrepancies with the durations mentioned in the Bid documents.UNOPS Answer:Confirmed the project durations mentioned Section 9 in the ToR is the correct project duration to follow as there are no other durations mentioned in the bid documents:Phase I: Assessment and Requirement Analysis 25 days / Phase II: Conceptualization and Design 25 days / Phase III: Development 65 days / Phase IV: Testing and debugging 20 days / Phase V: Deployment and Go Live 15 days / Phase VI: Training and Capacity Building 15 days / Phase VII: Warranty 365 days / Phase VIII Post Go Live On Site Support 120 days (remaining period of the contract estimate) / Phase IX Maintenance and Technical Support 365 days.However, you can clarify in which documents and paragraphs you noticed the discrepancies in the requested project durationsRegards,
Edited on:
09-Jan-2025 10:51
Edited by:
webservice@unops.org
New clarification added: Bidder's Question:Based on the TOR, the requirements point toward an ERP system built on an open-source platform. Considering this, we believe xxx is the most applicable choice. However, we would like to share the following concerns for your consideration:Yearly System Updates Impact on Customizations: xxx releases a new version annually. Updates in source code and functionalities may affect customizations from previous versions, requiring additional modifications and developments to maintain alignment with the new version's requirements.xxx Compatibility with RequirementsFunctional Coverage: xxx can address approximately 40% of the required functionalities related to fleet management, inventory, products, accounting, and manufacturing.Customization Needs: The remaining 60% will require significant customizations to tailor the system to your specific needs and workflows.Integration with GIS Customization Needs: Integrating xxx with GIS will require substantial customization efforts to ensure smooth functionality and data synchronization between the systems.IoT Sensors:Since the number of IoT sensors required is not specified, would it be acceptable to propose pricing on a per-unit basis? This approach provides flexibility as the project scope becomes clearer.We hope these points help clarify potential challenges and considerations, although we are fully capable of delivering the ERP platform customization as needed. Alternatively, we are still open to develop the platform as a standalone solution that is not built on the top of an ERP platform (as per the requirements of the original RfP - before the amendments). Please let us know if you would like to discuss this in more detail or schedule a meeting to address any questions. UNOPS Response:Annual updates to the ERP system may introduce changes to core functionalities, potentionally impacting customizations from previous version, the best approach is to design customizations to be modular and well-documented, allowing for easier alignment with updated system versions. Include provisions for regular system reviews and maintenance to evaluate and adjust customizations as needed. The ERP platform can address a significant portion of the requirements related to basic functionalities such as fleet management, inventory, and compliance tracking. Specific workflows and advanced functionalities will require customizations. The contractor can deploy the system's native features to meet immediate needs, then develop custom modules for advanced functionalities and integrations. GIS integration will require customization to synchronize spatial data and ensure smooth workflows between the ERP system and GIS tools, the contractor should use API's to facilitate seamless data exchange and integration, and ensure GIS-related requirements, such as mapping and spatial analysis, are prioritized in the customization roadmap. Yes it is acceptable to propose pricing on a per-unit basis for IoT sensors. Developping the platform as a standalone solution remains a viable option and the contractor will be evaluated based on requirements needed for the system.Regards
Edited on:
31-Dec-2024 11:22
Edited by:
webservice@unops.org
New amendment added #6: This amendment#6 was raised to extend the deadline for bidders' clarifications and the tender closing date as below:- The deadline for submission offers(tender closing date) will be on 21 January 2025- The deadline for Bidders ' carification is 16 January 2025
Edited on:
30-Dec-2024 12:07
Edited by:
webservice@unops.org
New clarification added: Bidder's Questions:We would like to clarify several questions:Users:In Section II: Schedule of Requirements 15,000 users is indicated, what number of users is expected to be:* internal сoncurrent users of ERP system* external users (clients) of ERP systemClient base:* Client base size* Number of Connections* Number of Metering pointsUNOPS Answers:Internal Users: About 20 internal users at MoE. External Users: All other external users , the contractor should provide an accessible interface for external users to input data, the application should support basic functionalities, such as secure data entry, user authentication, and submission tracking. The external application will automatically feed data into the open-source ERP system through API's.Estimated Size: 15,000 entities, as referenced in the ToR. This includes businesses, municipalities, waste management operators, and other entities directly involved in waste generation, collection, or treatment.Number of Connections:Estimated Number: Varies based on system architecture and stakeholder participation.Number of Metering Points:Estimated Number: Dependent on IoT device deployment. Anticipated initial deployment includes:Waste transport vehicles (e.g., GPS trackers): 500–1,000 points.Weighing scales or metering devices at collection and treatment sites: 100–300 points.Regards
Edited on:
30-Dec-2024 10:22
Edited by:
webservice@unops.org
New clarification added: Bidders' Questions:-We would like to request a two-week extension of the proposal submission deadline to allow us sufficient time to prepare and submit a competitive and comprehensive offer.-Q11. Deadline Extension: Given the end of year holidays, we are writing to request an extension of the deadline by at least two weeks.- -Taking into account the fundamental changes in the terms of reference and in light of the holiday season and vacation period, we kindly request a two-week extension for the tender proposal submission deadline. This additional time will enable us to prepare our proposal thoroughly, ensuring it meets all requirements and is presented effectively.UNOPS Responses:The deadline for submitting the offers will be extended till 21 January 2025 and the deadline for bidders' clarifications to be on 16 January 2025 , noting that the new dates will be published soon.Regards,
Edited on:
30-Dec-2024 10:14
Edited by:
webservice@unops.org
New clarification added: Bidder's questions:Q10. Key Personnel – University Degree: Is the “TS Information Technology” acceptable as “University degree in Computer Science or Computer Engineering or any related field” (generally the BS is equivalent to the TS with one- or two-years’ experience)? Q11. Key Personnel – Cloud Solutions Architect and Cybersecurity Specialist: Is it acceptable to have one CV for the roles of Cloud Solutions Architect and Cybersecurity Specialist (generally the two positions complement each other)? UNOPS Responses:10. TS in Information Technology is not acceptable as an equivalent to a university degree in Computer Science, Computer Engineering, or a related field.11. Yes, it is acceptable to have one CV covering both roles if the individual demonstrates expertise in both cloud solutions architecture and cybersecurity.Regards,
Edited on:
23-Dec-2024 11:45
Edited by:
webservice@unops.org
New clarification added: Bidder question:Please confirm if the deliverables outlined in the amended Section 7 supersede the deliverables specified in Section 9UNOPS Response:The deliverables outlined in the amended Section 7 are intended to go with those specified in Section 9. This ensures alignment with the updated project scope and methodology, particularly reflecting the ERP-based approach for the SWMIS.
Edited on:
23-Dec-2024 11:36
Edited by:
webservice@unops.org
New clarification added: Bidder's Question:Q9. Number of initial users for the ERP Platform: for subscription pricing, we would like to have the estimated number of internal users for the ERP Platform? UNOPS Response:The initial number of internal users for the ERP platform is estimated to be 20–30 users, covering key roles such as administrators, operators, and stakeholders from the Ministry of Environment and related entities. The Service Provider should ensure that the pricing model accommodates scalability to add more users in the future as the system expands. However, the Service Provider shall create an application to be used by multiple users designed to receive the data and to be compatable in feeding the ERP Platform.Regards,
Edited on:
23-Dec-2024 11:32
Edited by:
webservice@unops.org
New amendment added #5: This amendment#5 was raised due to the following:1. To amend Section 3:Qualification criteria-3.2 -Financial Stability.2 To Add the amended document RFP_Section_III_.Returnable Bidding Forms Amendment (3)3.To amend under criteria tab the Qualification criteria-3.2 -Financial Stability.
Edited on:
19-Dec-2024 14:13
Edited by:
webservice@unops.org
New clarification added: Bidder's clarifications: Q1. Financial Stability Criteria:We are a local Lebanese company; we suffered during the financial crisis as all companies of the Lebanese private sector especially during 2019 and 2020.Based on the above, we would like to suggest reviewing the “Financial Stability” criteria with:Annual sales turnover of minimum 500,000 USD in any one of the last three years andAt least two major contracts exceeding 200,000 USD each in the last (3) three years.Many thanks for your understanding. Q2. Any preference for the license type of products (Open Source, Subscription, Perpetual)?Q3. Should we provide a GIS system or integration with an existing GIS system? Q4. Should we provide a GPS system or integration with an existing GPS system? Q5. Should we provide the whole Infrastructure (networking, hardware) for the IoT integration (capturing, aggregation, analysis, and reporting) or integration with an existing IoT system? Q6. Is it mandatory to have the API Manager (which needs advanced management)? We suggest using the standard RESTful API for all API calls. Q7. Should we provide the list of cloud servers with their monthly subscriptions with their hosting services, monitoring, backup, updates, security, etc.? Q8. Should the cloud hosting services be done with the international companies as Google, Amazon, Microsoft or local ones could be accepted?UNOPS Responses: Q1: Please note that the first part of the criteria required the Offeror to have an annual sales turnover of at least USD 500,000 in any one of the last five years. This provision was intended to allow more Offerors to be eligible for success. However, the second part of the criteria has been amended as follows: Offeror should be in continuous business of successfully supplying similar services and solutions with a similar nature and complexity as specified in this TOR undertaking at least two major contracts exceeding 200,000 USD each in the last (3) three years prior to the bid submission deadline. Please find the amendment document (RFP_Section_III_.Returnable Bidding Forms Amendment (3)) that will be published shortly, along with the updated criteria, which can be accessed under the "e-sourcing Criteria" tab.Q2: A hybrid approach is preferd: Open Source: For cost-effectiveness and flexibility in areas like GIS and databases. Subscription: For ERP platforms and cloud hosting services to ensure scalability, support, and regular updates.Perpetual: Considered only for standalone tools with minimal ongoing costs.Q3: The Service Provider must propose a GIS solution that meets the technical specifications outlined in the ToR.Q4: The Service Provider should propose a GPS system for vehicle and asset tracking, ensuring compatibility with the ERP platformQ5:The Service Provider must provide the necessary IoT infrastructure, including:Sensors and devices for data capturing (e.g., smart scales, environmental sensors).Networking solutions for data transmission (e.g., Wi-Fi routers, gateways).Platforms for data aggregation, analysis, and reporting integrated into the ERP systemQ6:The use of a standard RESTful API for API calls is acceptable and simplifies integration and management. API manager tools can be avoided if not explicitly required by the ToR, but the service provider should ensure secure, scalable, and well-documented RESTful API's for interperability.Q7:Yes, the service provider should provide a list of recommended cloud servers with their monthly subscription costs. Details to include: Hosting services. Monitoring and logging tools. Backup and disaster recovery solutions. Security measures. Software updates and maintenance schedules.Q8:International cloud providers are preferred due to their established global standards for scalability, reliability, and security. Local cloud hosting services may be accepted.
Edited on:
19-Dec-2024 11:18
Edited by:
webservice@unops.org
New amendment added #4: This amendment#4 was raised due to the following:1. To add the below amended documents:1.1 Form C_ Financial Proposal Form in Excel format Amendment(2)1.2 RFP_Section_II_Schedule of Requirements (Amendment#1)1.3 RFP_Section_III_.Returnable Bidding Forms Amendment (2)2. To extend the deadline for bidders' clarifications to be on 29 December 2024
Edited on:
18-Dec-2024 14:06
Edited by:
webservice@unops.org
New clarification added: Dear Bidders,Please consider amendment#4 which is raised due to the following:1. To add the below amended documents:1.1 Form C_ Financial Proposal Form in Excel format Amendment(2)1.2 RFP_Section_II_Schedule of Requirements (Amendment#1)1.3 RFP_Section_III_.Returnable Bidding Forms Amendment (2)2. To extend the deadline for bidders' clarifications to be on 29 December 2024Regards,
Edited on:
17-Dec-2024 13:38
Edited by:
webservice@unops.org
New clarification added: Bidder Questions:With reference to the item 11.1.4 of RFP section ii, a maintained cloud based solution involves recurring cost.kindly confirm that this cost is funded from outside the budget after the completion of the project.UNOPS Response:All costs regarding the project will be transfered to MoE after December 31, 2026.
Edited on:
17-Dec-2024 13:26
Edited by:
webservice@unops.org
New clarification added: Bidder question#12 TOR 4.6.9-Environmental Compliance Please confirm if we will receive copies of the regulations and standards that we are expected to abide by?Bidder question#42 TOR "8.7 - Phase VII: Warranty 8.9 - Phase IX: Maintenance and Technical Support" Please clarify the duration of these phases. These sections state that the duration is 3 years. However, in the Reporting Requirements (Section 9) and Terms of Payment (Section 10), these phases are mentioned as lasting 1 year (365 days). Kindly advise which interpretation is correct.Bidder question#47 Form C_ Financial Proposal Form in Excel format Amendment(1) Please provide clarifications regarding the predefined weights in the financial proposal form. Are these weights fixed and mandatory, requiring strict alignment in our itemized pricing, or can deviations be accommodated as long as the total proposal aligns with overall requirements?Bidder question#48 Form C_ Financial Proposal Form in Excel format Amendment(1) Given that cloud services are typically priced on a subscription basis, our understanding is that cloud-related items should be priced to cover the development duration and one year after handover (covering one year support and maintenance). Please confirm if this understanding is correct or advise otherwise.UNOPS resposne:12. Yes, we will share with the winner bidder the legal document available.42.The warranty period should cover until the end of project which is 31 December, 2026. please find amended Form C_ Financial Proposal Form in Excel format Amendment(2) (that will be published soon) - in which the price of the Extended Warranty for three years is requested for information only, and will not be used during the evaluation.47. Please find amended Form C_ Financial Proposal Form in Excel format Amendment(2)- (That will be published soon) in which the (Weight for payment) is amended.48. Yes Correct.Regards,
Edited on:
17-Dec-2024 13:24
Edited by:
webservice@unops.org
New clarification added: UNOPS Responses:21. Light versions of data-intensive web pages are simplified interfaces optimized for faster loading, especially for low-bandwidth environments or mobile users. They should prioritize critical information and exclude heavy elements like detailed charts or large GIS maps.Expected Requirements: These versions must:Display essential metrics and summaries.Minimize large images, complex visualizations, and excessive data queries.Use paginated or lazy-loading data for better performance.22. All available data will be shared with the Contractor23. The system should integrate with the MOE website via Hyperlink.24. A maximum file size limit (e.g., 50 MB per document) can be imposed to manage costs and performance.Yes, documents should be scanned for malware or viruses before being stored in the repository.25. Validation criteria should include:Field-specific checks (e.g., numeric-only for waste quantities, dropdowns for predefined lists).Data consistency checks (e.g., matching waste source and type).Accuracy ranking mechanisms can include confidence levels or automated error detection for invalid entries.26. There is no specific preference for the cloud provider. However, the deployment region should align with data residency requirements and optimal performance for users in Lebanon27. No details on existing IoT sensors are currently provided. If they exist, their types and integration details will be shared later.28. The Service Provider need to build this functionality.29. If a unified IoT integration platform is already in use, its technical details will be shared to guide integration. If not, the Service Provider may need to build this functionality.30. Expected data sources include:Waste generation data from municipalities.Waste collection and transport logs.Fleet tracking systems (GPS-enabled).Waste treatment and disposal facility data.Sanitary landfill monitoring systems.Manual reports or spreadsheets.31.The Service Provider is expected to develop mobile applications compatible with Android/iOS. The devices/tablets (10 units) will be provided by the Service Provider.32.Open-source GIS software is preferred to avoid licensing costs, as specified in the TOR. However, if commercial GIS software is required, it must align with the technology stack policy.33.Yes, the Service Provider is responsible for covering all cloud-based environment costs (infrastructure, storage, compute) for the first year, starting from the Go-Live phase.34.Containerization is optional. The Service Provider may propose it for modularity and scalability but is not mandated to use it.35.Sharing should be restricted to registered users with permissions.Exporting dashboards (e.g., as PDFs) should be allowed for reporting purposes.36.Yes, a "saved favorites list" should be included. This feature should be scoped by individual users or stakeholder groups.37.Real-time refers to updates within a few seconds (e.g., <5 seconds).Configuration of data views should be flexible, either scoped by individual data sources or aggregated across all sources.38. While open-source platforms are preferred, cloud service licenses may be required. The Service Provider should clarify additional costs for proprietary tools or licenses.39.The timeline in Section 7 (19 weeks) is correct and should be followed. The 365 days is for the maintenance,updates, training,,, etc40.The prototype is expected to be functional for core workflows but not fully operational. It serves as a proof of concept for evaluating design and functionality before full development.41.International standards" refer to globally recognized frameworks and guidelines for software development. These include:Coding Standards: Use of secure, maintainable, and efficient coding practices (e.g., OWASP guidelines, ISO/IEC 25010 for software quality).Development Principles: Agile or DevOps methodologies for iterative and collaborative development.Additional Standards:ISO/IEC 27001 for information security.GDPR compliance for data protection.Standards for GIS and IoT integration protocols.43"On-Site Support" refers to the physical presence of technical experts to address critical issues, provide hands-on training, and support system deployment.44.For the demo session, bidders are expected to:Showcase their general software development capabilities.Present examples of previously developed digital solutions relevant to waste management, GIS, IoT, or government systems.The session can highlight methodology, tools, and frameworks to demonstrate technical expertise and experience.45.start date will be upon contract signature, end date is 31 Decemeber, 202646.mainly, considerable all data related to waste management will be provided by MoE and other stakeholders. however, if for any reason, the contractor needed any data that was not available and need field visit or contacting relevant parties, it is expected that the contractor should carry on with this task.49.Please note that no (section2) under form D and this numbering is to match the numbering generated by UNOPS system
Edited on:
15-Dec-2024 10:05
Edited by:
webservice@unops.org
New clarification added: Bidder questions:21 TOR 5-NON-FUNCTIONAL REQUIREMENTS It is mentioned that light versions of data-intensive web pages are needed. Could you clarify the expected level of detail or requirements for these light pages? 22 TOR 5.3-Usability Can you confirm if the MOE web systems guidelines for design, accessibility, and aesthetics will be shared with the Service Provider? 23 TOR 5.3-Usability It is mentioned that it must be accessible from the main MoE website. Please clarify if there is any specific method expected for integrating the solution into the main MOE website, such as via a link or other mechanisms? 24 TOR 5.3-Usability Please clarify if there should be a maximum limit for document storage sizes to manage costs effectively. Additionally, is there an expectation for a security implementation to scan documents before storing them in the repository? 25 TOR 5.3-Usability It is mentioned that "during data entry, integrate best practices in data collection such as including a mechanism to verify the validity and the accuracy of the entered data ". Can you specify the validation criteria and accuracy ranking mechanisms to be implemented? 26 TOR 6-TECHNICAL SPECIFICATIONS Is there any preference of cloud provider or a particular region of deployment? 27 TOR 6 - TECHNICAL SPECIFICATIONS Please clarify if there are any existing IoT sensors currently installed on-sites that the Service Provider is expected to integrate with. Please provide the types of these IoT sensors. 28 TOR 6 - TECHNICAL SPECIFICATIONS Please clarify if there are any IoT sensors planned to be installed on-sites, before the start of this Project, that the Service Provider is expected to integrate with. Please provide the types of these IoT sensors. 29 TOR 6 - TECHNICAL SPECIFICATIONS Please advise if the data from IoT sensors is being gathered in a unified IoT integration platform. If so, could you please share additional technical details about this platform to understand the integration requirements? 30 TOR 6 - TECHNICAL SPECIFICATIONS Please provide a list of the available data sources that the Service Provider is expected to integrate with, in terms of Waste Generation, Waste Collection, Waste Fleet, Waste Treatment, Waste Disposal, Sanitary Landfill Facility, and Waste Tracking. 31 TOR 6.1.6-Cloud-Based Hardware Requirements Please clarify the scope of work related to mobile devices and tablets. Our understanding is that the Service Provider is only expected to develop a mobile application with regards to mobile devices and tablets scope. Please confirm. Could you please confirm whether the Service Provider is expected to procure the smart mobile devices/tablets for field operations (10 units) as part of the scope, or if these will be provided by the client? 32 TOR "6.2 - Cloud-Based Software Requirements 6.3 - Summary of Quantiies" Please confirm whether commercial GIS software licensing is required or whether open-source GIS software should be used. This is based on Section 6.15 item 6.15.6 on page 21, which states that the technology stack must be based on an open-source platform with no license or subscription costs for any operating system, application, and databases. 33 TOR 6.4-Architecture It is mentioned that "The service provider shall incur all cloud-based environment costs and fees for a period of (1) one year expected to start with the deployment and Go-Live phase". Does this imply that the Service Provider is responsible for covering all expenses for the first year? 34 TOR 6.4-Architecture Our understanding is that containerization is an option. Please Confirm. 35 TOR 6.6-Dashboard Features It is mentioned "Ability to save and share dashboard configurations ". Should dashboard sharing only be restricted to registered users ? Also, should exporting dashboards be allowed? 36 TOR 6.6-Dashboard Features It is mentioned that "Quick access to recent dashboards and frequently used reports". Should this feature include a saved favorites list, and should it be scoped by user or stakeholder group? 37 TOR 6.6-Dashboard Features Please clarify if this is configured across all data or on a per-data-source? Please specify the definition of real-time in this context. Does it refer to immediate push? 38 TOR 6.15.6-Technology Stack It is mentioned “The technology stack must be based on an open-source platform with no license or subscription costs for any operating system, application, and databases. The below is a suggested list and not a required one.” However, in the context of cloud-based platforms, certain licenses such as cloud service licenses are typically required. Please elaborate on this section. 39 TOR 7 - METHODOLOGY AND WORK PLAN The total duration outlined in the Summary Timeline in Section 7 (19 weeks) and the total duration specified in the table in Section 9 (Phases 1 to 6 - 165 days) do not align. Could you please clarify which timeline should be followed. 40 TOR 8.2-Phase II: Conceptualization and Design It is mentioned that "The solution provider must provide a detailed working prototype model as a proof of concept that will allow UNOPS staff to evaluate and select design proposals." Could you confirm if this prototype will be fully functional? UNOPS Responses:Please find the responses below noting that questions#42,47,48 will be answered soon and you can find the responses under the below link for easy reading:https://drive.google.com/drive/folders/1Sf4DuLyq9fTMOIXInyMA5GFqRzfqS-nR?usp=sharing
Edited on:
15-Dec-2024 10:04
Edited by:
webservice@unops.org
New clarification added: UNOPS Responses:1. There is no data available to UNOPS.1.2. The unique ID should be structured (not random) and include meaningful attributes such as organization type, region, and a sequence number (e.g., ORG-LB-BEIRUT-001). Approval will involve verifying data validity and uniqueness. IDs should not duplicate existing entries. Additional validation can include correct formatting and required fields. The ID should act as a unique identifier for stakeholders. If stakeholders have multiple users, separate user IDs should reference the stakeholder ID.3. Sensitive data includes any personally identifiable information (PII), proprietary business information, and regulatory data. Examples include waste transport details, facility compliance data, and proprietary treatment methods. Permissions can be configured based on user roles and specific data sets. For example, landfill operators may access data only for their sites.4. Restrictions may include access control for sensitive reports. Templates can be pre-defined for consistency, such as CSV, Excel, or PDF formats. Acceptable templates should be standardized (e.g., predefined CSV/Excel formats) for compatibility with the system.5. Failed Logins: Notifications will be sent to both the admin and user. This allows admins to take action and users to verify the attempt. Audit Logs: Admins should have access to audit logs for all login attempts. The system should support pattern analysis for detecting suspicious login behaviors (e.g., brute force attacks).6. The system should support only local Lebanese numbers for notifications.7. The Contractor will be able to define the roles and permissions after stakeholders meetings and data gathering phase.8. Functional requirements include dropdowns for standardized inputs like waste types, facility names, and regions. These lists ensure data consistency and simplify data entry.9. Stakeholder data must be collected, validated, and entered into the system before the end of the design phase to ensure proper role-based configurations and system alignment.10. Types of Waste: Categories include municipal solid waste (MSW), hazardous waste, industrial waste, and medical waste. Subcategories may be defined by the Ministry.Automatic Monitoring: IoT devices or sensors will monitor waste weight, volume, and transport data automatically.11. Alerts will be preconfigured based on client-provided thresholds. Administrators will have tools to modify thresholds and recipients after deployment.13. No cost threshold.14. There is no predefined workflow15. Any KPIs will be discussed after signing the contract16. Users should be able to adjust views (e.g., filters, time ranges) and create custom dashboards based on their roles.17. MoE will decide later which reprots will be public and which will be restricted.18. Yes, it will be provided once the contract is signed.19. A centralized database will include GIS layers for POPs, chemicals, and contamination sites. Existing digital GIS data will be provided, and no site data collection is required.20. Any available data will be provided upon contract signature, however, any info that is not available and is essential to the system it will be contractor's responsibility to acquire this data
Edited on:
15-Dec-2024 10:02
Edited by:
webservice@unops.org
New clarification added: Bidders questions:1 TOR 2 - OBJECTIVE OF THE ASSIGNMENT Please provide the preferred database schema expected to be used by the SWMIS. Please confirm if any existing data is available to be populated for use by SWMIS. If so, could you share the date range and type of this data? 2 TOR 4.2 - Stakeholder Unique Identification Number For the stakeholder unique id number, can you please elaborate more or provide a sample of how should it look like? Our understanding is that it should be meaningful, not random (unlike a GUID). Also, it is mentioned that it requires approval once generated. Can you please confirm if there is any specific validation criteria, and whether this ID should also act as a group ID to which multiple users can be assigned. 3 TOR 4.3 - User Management If control to access to sensitive data is required, can you please specify how data is classified as sensitive? Also for user-data access, will we also control access of data based on the permissions on specific landfills for instance? 4 TOR 4.3 - User Management "Regarding data downloads, please clarify if there are any restrictions on information that can be downloaded. Should a specific form or template be used when downloading data? ; i.e. in a specifc template? Regarding data upload, please clarify if there should be a template that is acceptable by the system for data upload." 5 TOR 4.3 - User Management "For failed login attempt, please confirm our understanding that the email is sent to the admin to take action as well as the user for the user to verify that he was trying.On another note, should admins have some sort of audit log for login attempts? Possible to suggest detecting attacks due to login attempt patterns. " 6 TOR 4.3 - User Management For SMS notifications, should the system account for international numbers, or are the users expected to be Lebanese residents? 7 TOR 4.4-Stakeholder Role/Multi-Role Assignment Will a document defining roles, permissions for features, and data access preferences be shared with the Service Provider? 8 TOR 4.5 Predefined information lists and dropdowns Please clarify what is the functional requirement expected to be available on the SWMIS with regards this section. 9 TOR 4.6-Stakeholders Data Please clarify what is meant by "Stakeholder data must be finalized before the end of the design phase" 10 TOR 4.6- Stakeholders Data Please specify what is meant by "type of waste". What are the different categories of waste expected to be monitored. Please clarify how the types of waste are expected to be automatically monitored. 11 TOR 4.6.8-Monitoring Please clarify whether the service provider is expected to preconfigure alerts based on definitions provided by the client, or if this task will fall under the administrator's configuration responsibilities, including defining notification and alert conditions, thresholds, and recipient details 12 TOR 4.6.9-Environmental Compliance Please confirm if we will receive copies of the regulations and standards that we are expected to abide by? 13 TOR 4.6.9-Environmental Compliance Please specify if there is any level of details required or granularity for the audit trail? Should this be configurable? Additionally, please note that this might impact the cloud storage increase over time. Can you confirm if there is a cost threshold that should bo considered? 14 TOR 4.6.10-Citizen Engagement Please clarify if there is a predefined workflow for tracking the complaint form by the corresponding citizen? 15 TOR 4.6.12-Dashboard Please specify if there is a defined set of KPIs or metrics that are required? 16 TOR 4.6.12-Dashboard Please clarify the expected level of customization for dashboards and views. 17 TOR 4.6.12-Dashboard Please specify if the sharing of reports will be permitted with external users, or if this access be restricted only to registered users? 18 TOR 4.6.14-POPS, Chemicals, and Contaminated Sites Please confirm if the Service Provider will receive an inventory list of POPs, chemicals, and contaminated sites? 19 TOR 4.6.14 - POPS, Chemicals, and Contaminated Sites Please confirm our understanding that a centralized database should be established to include the various GIS layers (e.g., POPS, Chemical, Contamination Sites, etc.) in addition to other relevant information. Our understanding is that such data exist in digital format either in GIS or GIS-ready format that could be utilized by the Consultants and that no site data collection is required. 20 TOR 4.6.14- POPS, Chemicals, and Contaminated Sites Please confirm that spatial analysis will be performed to identify spatial relationships between different layers such as water bodies, forest, protected areas, population density, etc. Our understanding is that these layers will be provided by MOE or other relevant stakeholders and that data conversion or digitization will not be required .UNOPS Responses:Please find the responses below noting that question#12 will be answered soon and you can find the responses under the below link for easy reading:https://drive.google.com/drive/folders/1Sf4DuLyq9fTMOIXInyMA5GFqRzfqS-nR?usp=sharing
Edited on:
15-Dec-2024 10:01
Edited by:
webservice@unops.org
New clarification added: Bidder's question:With this letter, we would like to kindly ask you to extend the deadline for the tender proposal submission by two weeks. This extension would greatly assist us in diligently preparing our proposal and ensure it meets all requirements and is presented most effectively.We kindly ask for your understanding and support in considering this extension request.UNOPS Response:Please note that the deadline for bidders's clarifications and the tender closing date were extended as below :- The deadline for Bidders' carification is 23 December 2024- The deadline for submission the offers will be on 7 January 2025Regards
Edited on:
15-Dec-2024 09:02
Edited by:
webservice@unops.org
New amendment added #3: This amendment#3 was raised to extend the deadline for bidders' clarifications and the tender closing date as below:- The deadline for submission offers(tender closing date) will be on 7 January 2025- The deadline for Bidders ' carification is 23 December 2024
Edited on:
12-Dec-2024 15:38
Edited by:
webservice@unops.org
New amendment added #3: This amendment#3 was raised to extend the deadline for bidders' clarifications and the tender closing date as below:- The deadline for submission offers(tender closing date) will be on 7 January 2025- The deadline for Bidders ' carification is 23 December 2024
Edited on:
12-Dec-2024 15:37
Edited by:
webservice@unops.org
New clarification added: Bidder's question:Is the project subject to Value Added Taxes in Lebanon ?Is there a possibility of getting a time extension as the deadline is coincinding with the holiday season and the end of the year.UNOPS Response:1:No, The project is exempt from TVA.2: The tender closing date and the deadline for bidders' clarifications will be extended as below and the new dates will be published soon:- The deadline for bidders' clarification is 23 December 2024-The deadline for submitting the offers will be 7 January 2025Regards,,
Edited on:
12-Dec-2024 14:43
Edited by:
webservice@unops.org
New clarification added: Bidder's question:We are writing to request an extension of the deadline by two weeks to ensure we can submit a complete and well-prepared proposal. Your understanding and approval would be greatly appreciated.UNOPS Response:Please note that the deadline for bidders's clarifications and the tender closing date will be extended as below and the new dates will be published soon:- The deadline for submission the offers will be on 7 January 2025- The deadline for Bidders ' scarification is 23 December 2024Regards
Edited on:
12-Dec-2024 14:02
Edited by:
webservice@unops.org
New amendment added #2: This amendment#2 was raised to :1. Publish the pre bid meeting minutes.2. Publish the amended document: RFP_Section_III_Returnable Bidding Forms Amendment (1) The amendment highlighted in yellow in Form C: Financial Proposal Form-Table13. Publish the amended document: Form C_ Financial Proposal Form in Excel format Amendment(1)
Edited on:
10-Dec-2024 13:31
Edited by:
webservice@unops.org
New clarification added: Dear Bidders,UNOPS would like to thank bidders who confirmed attending today pre-bid meeting and this is to remind all bidders who did not confirmed their attendees that the pre bid meeting will be conducted today as per below details:Location: via Google Meet using Video call link:meet.google.com/qug-rsfh-udkDate & Time: Monday, 09 December 2024- 2:00 PM – 03:00 pm Amman - JordanParticipation in the clarification meeting is not mandatory but participation is strongly encouraged to avoid the risk of non-compliant bids.Bidders shall notify UNOPS using the eSourcing clarification tool to whether or not they intend to participate in the pre -bid meeting and shall give the details of their representatives who will attend.Regard
Edited on:
09-Dec-2024 07:09
Edited by:
webservice@unops.org
New amendment added #1: This amendment#1 was raised to postpone the pre bid meeting to enable all bidders to participate:Location: via Google Meet using Video call link:meet.google.com/qug-rsfh-udkDate & Time: Monday, 09 December 2024- 2:00 PM – 03:00 pm Amman - Jordan
Edited on:
04-Dec-2024 13:40
Edited by:
webservice@unops.org
New clarification added: Bidder question:We understand that the pre-bid meeting is postponed till Monday, the 9th of December from 1:00 till 2:00 Beirut time.UNOPS Response:Please note that the pre-bid meeting is postponed to enable all bidders to participate and the new dates will be published soon:Location: via Google Meet using Video call link:meet.google.com/qug-rsfh-udkDate & Time: Monday, 09 December 2024- 2:00 PM – 03:00 pm Amman - JordanParticipation in the clarification meeting is not mandatory but participation is strongly encouraged to avoid the risk of non-compliant bids.Bidders shall notify UNOPS using the eSourcing clarification tool to whether or not they intend to participate in the pre -bid meeting and shall give the details of their representatives who will attend.Regards,
Edited on:
04-Dec-2024 13:13
Edited by:
webservice@unops.org
New clarification added: Dear Bidders,Please note that the pre-bid meeting is postponed to enable all bidders to participate and the new dates will be published soon:Location: via Google Meet using Video call link:meet.google.com/qug-rsfh-udkDate & Time: Monday, 09 December 2024- 2:00 PM – 03:00 pm Amman - JordanParticipation in the clarification meeting is not mandatory but participation is strongly encouraged to avoid the risk of non-compliant bids.Bidders shall notify UNOPS using the eSourcing clarification tool to whether or not they intend to participate in the pre -bid meeting and shall give the details of their representatives who will attend.Regards,
Edited on:
04-Dec-2024 10:47
Edited by:
webservice@unops.org
New clarification added: Dear Bidders,Please note that the pre-bid meeting will be postponeded to enable all bidders to participate.The new dates will be published soon:Location: via Google Meet using Video call link:meet.google.com/qug-rsfh-udkDate & Time: Monday, 09 December 2024- 2:00 PM – 03:00 pm Amman - JordanParticipation in the clarification meeting is not mandatory but participation is strongly encouraged to avoid the risk of non-compliant bids.Bidders shall notify UNOPS using the eSourcing clarification tool to whether or not they intend to participate in the pre -bid meeting and shall give the details of their representatives who will attend.Regards,
Edited on:
04-Dec-2024 10:45
Edited by:
webservice@unops.org
New clarification added: Dear Bidders, Please note that tomorrow we will conduct the pre bid meeting as per below explanation. your attendances is recommended and appreciated:Location: via Google Meet using Video call link:meet.google.com/qug-rsfh-udkDate & Time: Wednesday, 04 December 2024- 2:00 PM – 03:00 pm Amman - JordanParticipation in the clarification meeting is not mandatory but participation is strongly encouraged to avoid the risk of non-compliant bids.Bidders shall notify UNOPS using the eSourcing clarification tool to whether or not they intend to participate in the pre -bid meeting and shall give the details of their representatives who will attend.Regards,
Edited on:
03-Dec-2024 08:48
Edited by:
webservice@unops.org