i have our iw meeting scheduled for 3.30pm EST today
Paulo Pinheiro
Deborah L. McGuinness
i had suggested starting next week.
We had agreed last week to move to 2pm eastern on friday to avoid the 3:30 time on friday when you said you typically have conflicts.
i presume those conflicts are still in place.
also, is your gmail address the one on the iw google group mailing list? i am sending this response both to the mailing list and to your gmail address directly.
deborah
--
You received this message because you are subscribed to the Google Groups "inference-web" group.
To unsubscribe from this group and stop receiving emails from it, send an email to inference-we...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Paulo Pinheiro
So, do we have a 2pm EST meeting today?
Engineering team [create a purchase order] with a list of materials needed for a new project.
Purchase team [receives the purchase order] and [decompose the purchase order into several quote requests], one request for each vendor listed as a supplier of materials in the original purchase order. Quote requests have a stated deadline for vendors to respond. [Quote requests are sent] to suppliers.
[Responses to quote requests are collected] as they are received by mail, email or web application.
[Purchases are authorized] for quotes within an expected price range.
[Procurement team review original purchase orders] with engineering team for item with no quotes or classified as overpriced.
Purchase reviews can result in (1) [new purchase orders] with alternative materials, (2) decision of [canceling the order] of a specific material, or (3) with [review of expected price] for materials. For options (2) and (3), new [purchase orders may be issued], restarting a new procurement process for these specific items.
[Reconciliation of purchase invoices] for ordered items are eventually used to [trigger notifications engineering team].
Relevant events in this list are identified by []. The list of events above is just one possible scenario that can evolve in many different ways including a long list of new types of events not included in the scenario above.
Provenance-related questions for the scenario above: how to represent these events in an ERP system? Databases use Event-Condition-Action triggers to implement most of the triggers used to support the scenario above. Is there any benefit for the ERP system to have these events and corresponding actions encoded in PROV instead of a specific set of predicates? What are these benefits? How about PML3?
Many thanks,Paulo.