Skip to content
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

Purchase orders #897

Closed
jpmckinney opened this issue Jul 25, 2019 · 3 comments
Closed

Purchase orders #897

jpmckinney opened this issue Jul 25, 2019 · 3 comments
Labels
Extensions - Drafted Relating to a drafted extension Focus - Extensions Relating to new or proposed extensions, or the governance and maintenance of extensions

Comments

@jpmckinney
Copy link
Member

Splitting from #396 and copying questions in issue description:

  • Should purchase orders fall within the scope of OCDS?

Yes. They can provide important details on the fulfillment/implementation of the contract.

  • How should purchase orders be modelled in OCDS, e.g. should these be modelled using contract.implementation.transactions or do they represent a contract in themselves?

Semantically, purchase orders are not transactions.

@georgneu wrote:

A brief look at a purchase order seems to indicate that most of the information is covered in the contract data so it could be integrated there.

@chrisalexsmith wrote:

Would suggest that purchase orders do represent contracts but are linked to the head contract.

Indeed, the acceptance of a purchase order forms a legal contract. However, per #896, they do not belong in the contracts array. The proposal is instead to author a purchase orders extension, e.g. contracts.implementation.purchaseOrders, and to include guidance on how to model the contract under which the purchase orders are issued, per the discussion in #896.

  • What are the use cases for disclosure of purchase order level data?

@georgneu wrote:

Just flagging that purchase orders (orden de pago) is information that Argentinean civil society would be looking for. They see this as the key document that provides them with the information on who and what.

  • Is data on purchase orders typically captured in the same information systems as data on contracts (framework contracts in particular) or does it exist in separate systems?

@chrisalexsmith had indicated the integration of both types of data in some systems. However, as is often the case, this is not how e-GP systems are universally implemented.

@jpmckinney jpmckinney added the Focus - Extensions Relating to new or proposed extensions, or the governance and maintenance of extensions label Jul 25, 2019
@duncandewhurst
Copy link
Contributor

The proposal is instead to author a purchase orders extension, e.g. contracts.implementation.purchaseOrders, and to include guidance on how to model the contract under which the purchase orders are issued, per the discussion in #896.

From @yolile: Paraguay has a purchase orders extension (example data)

@jpmckinney jpmckinney added the Extensions - Drafted Relating to a drafted extension label May 8, 2020
@jpmckinney jpmckinney added this to the Extension Explorer milestone May 8, 2020
@jpmckinney
Copy link
Member Author

Closing as the extension is published.

@duncandewhurst
Copy link
Contributor

duncandewhurst commented Oct 17, 2021

Edit: Wrong issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Extensions - Drafted Relating to a drafted extension Focus - Extensions Relating to new or proposed extensions, or the governance and maintenance of extensions
Projects
None yet
Development

No branches or pull requests

2 participants