-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Country of benefit (relevant to contracting processes by multilateral organizations) #1719
Comments
Beneficiaries in OCDS for PPPs, etc. are about, e.g., which community benefits from a new school or road. The government would not be considered the beneficiary; rather, the government acts for the benefit of residents. Whether the government achieves this benefit (like a school or road) with its own funds and procurements or via an MDB's funds and procurements – the beneficiaries will be the same (the people in that community). Generally speaking, the donor (e.g. the particular country that contributed funds to the MDB) has no authority over the procurement. They might have attached conditions to their funds (e.g. can be used for health and education, cannot be used for defence, etc.), which might even be very specific (e.g. "for a new water treatment plant in Camelot"), but they do not fill the role of buyer:
To lay out the facts that we're trying to model, let's be more specific. Example: The IADB loans funds to the Dominican Republic to improve the facilities of the Port of Manzanillo. Scenario 1: Let's say the IADB uses the DR's e-GP. This should be modelled with DR as the buyer and/or procuring entity (following OCDS definitions, depending on how they run the procurement). The finance extension can describe the loan. Indicating which country provided the funds to the IADB would be a new need, for which we have no field. We can discuss how to model that, but it would be among the budget/finance fields. Edit: Per next message, Scenario 2: Let's say the IADB runs the procurement through its own system. In this scenario, we need to know more about the procurement rules / how the contracting process is governed. Let's assume the IADB is performing the procurement on behalf of the buyer (which would then be the DR government), which makes them a procuring entity (see a useful analysis of procuring entity roles in #1180). We can then model the financing information the same as scenario 1. So, the only difference between the two scenarios is that in scenario 2, the IADB is the procuring entity. That makes sense, as there is only one change between the two. |
So: {
"buyer": {
"id": "1",
"name": "whatever relevant public body in the country's government, don't set buyer if unknown"
},
"tender": {
"procuringEntity": {
"id": "2",
"name": "the MDB ONLY IF the MDB takes responsibility for running the procurement, within its own system"
}
},
"planning": {
"budget": {
"finance": {
"id": "1",
"financingParty": {
"id": "2",
"name": "the MDB"
},
"financingPartyType": "multilateral",
"source": "this field can be used for the country that contributed funds to the MDB, if not otherwise needed"
}
}
}
} |
Thanks, but I think there is an additional scenario to consider:
Here is an example from UNOPS:
|
Like I said, this is not how the word "benefit" or "beneficiary" is used in procurement. For "Hotel rooms" on that page, the beneficiaries would be the people who sleep in those rooms. Beneficiaries are the target population for whom the intervention is designed. This, in general, is not an entire country. That said, if data quality is poor, it's possible that the only thing we know about the beneficiaries is the country in which they live. In that situation, we have two options: (1) add a field specifically for this purpose, e.g. The referenced extension hasn't been reviewed for inclusion in the extension registry, and from a quick review, I suspect it will not satisfy the wide variability in beneficiary information. open-contracting-extensions/public-private-partnerships#235 has a different model, for instance. Unless we want to do a deep dive on beneficiary information, the best option is to add a simple field like It looks like we are modelling UNOPS data (important context to share). This is a different context, than, for example, modelling Denmark's contracting processes, some of which might be funded by UNOPS. In this example, it matters to know what ICAT is. It turns out it is both an UNOPS project and an organization ("ICAT was created as a multi-stakeholder partnership and is governed by a Donor Steering Committee together with an Advisory Committee.") It appears as both project and partner on this page, for example. The project has a hyphen. I don't know how to get more detail on individual contracts, so I'll just assume that the partner is "the organization aiming to conclude a contract", i.e. the buyer. In many cases with MDBs, the partner is a government entity in a country. The model is mostly as before. The example shared has no donor information as far as I can see. This assumes that the "amount" in the table is both the amount financed and the amount awarded. {
"parties": [
{
"id": "XM-OCHA-HPC8",
"name": "United Nations Office for Project Services",
"roles": [
"procuringEntity",
"funder"
]
},
{
"id": "1",
"name": "ICAT Initiative for Climate Action Transparency",
"roles": [
"buyer"
]
},
{
"id": "2",
"name": "Klosterhof Hotel-Veranstaltungen GmbH",
"roles": [
"supplier"
],
"address": {
"countryName": "Germany"
}
}
],
"buyer": {
"id": "1",
"name": "ICAT Initiative for Climate Action Transparency"
},
"tender": {
"procuringEntity": {
"id": "XM-OCHA-HPC8",
"name": "United Nations Office for Project Services"
}
},
"awards": [
{
"id": "UNOPS-3175505",
"title": "Hotel rooms",
"suppliers": {
"id": "2",
"name": "Klosterhof Hotel-Veranstaltungen GmbH"
},
"value": {
"amount": 5000,
"currency": "USD"
}
}
],
"contracts": [
{
"id": "UNOPS-3175505"
"awardID": "UNOPS-3175505",
"status": "terminated"
}
],
"planning": {
"budget": {
"finance": {
"id": "11875-003",
"title": "ICAT - Initiative for Climate Action Transparency",
"description": "Initiative for Climate Action Transparency (ICAT) integrates guidance, capacity building and knowledge sharing to engage countries in the use of a common framework to assess the impacts of their policies and actions and report progress, fostering greater transparency, effectiveness and ambition. The Initiative will improve the availability and quality of data and enable countries to promote efficient, cost-effective policies. The Initiative will also provide a platform for countries to share lessons learned and build mutual confidence in their climate actions. The United Nations Office for Project Services (UNOPS) manages the trust fund through which the Initiative is funded. This structure allows new donors to join the trust fund, to expand its work and reach.",
"financingParty": {
"id": "XM-OCHA-HPC8",
"name": "United Nations Office for Project Services"
},
"financingPartyType": "multilateral",
"value": {
"amount": 5000,
"currency": "USD"
}
}
}
}
} |
Thanks, Another example is this one, where the country of benefit is Argentina, UNOPS is managing the procurement contract and one contract is financed by/the donor is the World Bank. The modeling would be as you described and in both examples, we could use |
In terms of word choice, I chose "country of benefit" based on its usage like at:
We also already have In the context of international aid, the term "recipient country" is often used (like in IATI). However, within some MDBs, "recipient country" has a special meaning (e.g. a country can have the status of being a "recipient country" or not). Since we are not trying to model whether a country belongs to such a list, but instead are just trying to model the country in which benefits are realized (which is of wider utility, outside the context of international aid), I chose to avoid that term. According to ChatGPT (I'm being lazy), other terms from international aid include:
Considering that last option, for some use cases, the country of benefit could be implied by the delivery location of items (if that level of details is provided); for example, if an EU institution procures something that benefits a specific country. I found the following to not be a good match for our desired semantics:
|
For future reference, I also checked the use of "beneficiaries" in different contexts. For co-occurrences with "procurement", I could only find things like EU funding instruments like this one and the OSS procurement rules, which describe recipients (which can be contracting authorities) of funding as "beneficiaries". This makes sense from the perspective of a funding program, as they are the first to "benefit" from the funding. That said, for compatibility with other contexts, I would prefer to call them the "recipients", because they "receive" the funding, but (unless there is corruption) they are not the ones who will benefit, ultimately. In other contexts like project beneficiaries, beneficiaries of social impact bonds, etc. the meaning is always along the lines of the people affected by a problem, "the ultimate recipients of the services or interventions provided by the project or program" [1], "people directly and indirectly affected by the project activities" [2], etc. – which is consistent with the meaning in this discussion. Many funders refer to beneficiaries in this sense, e.g. when a funder asks a recipient to report on the beneficiaries of a funded project. In the EU or other places with French influence, it's possible that "beneficiary" is more commonly used where we'd expect "recipient", because "bénéficiaire" is commonly used as the term for a recipient (like in this Canadian glossary). |
Sometimes, multilateral organizations are in charge of conducting the procurement process for a country (e..g in OCDS, the procuring entity is the multilateral procurement unit), the buyer could be the donor, e.g a country, and finally, they also have the information about the "Beneficiary Country". Neither the buyer nor the procuring entity covers the beneficiary of the procurement, therefore we need another place to disclose this information.
In open-contracting-extensions/public-private-partnerships#235 is discussed how to disclose data about beneficiaries, and in #1388 (comment) the beneficiaries extension was created (adding beneficiaries at the item level and without a location).
Using tender.items.location could be an option but the beneficiary country information is not available at the item level (and sometimes the item information is not available at all) but at the tender level.
So another option could be to change the existing beneficiaries extension to: Add the Address object and Beneficiaries at the tender level.
cc @allakulov
The text was updated successfully, but these errors were encountered: