Resource Allocation for Provider
ijdoasjd
Document związany z providerm to OLA (link albo opis)
obrazek
1. Pool creation
Opis
link1 - metryki
link2 - resource pool
link3 - work instruction
filmik
2. OLA (re)negotiation
<style type="text/css">P { margin-bottom: 0.21cm; color: rgb(0, 0, 0); }P.western { font-family: "Times New Roman",serif; font-size: 12pt; }P.cjk { font-family: "DejaVu Sans","Arial",sans-serif; font-size: 12pt; }P.ctl { font-family: "Times New Roman",serif; font-size: 12pt; }A:link { color: rgb(0, 0, 255); text-decoration: underline; }</style>
Note: PARTY is the actor who operates the procedure; OTHER PARTY means: P in case B runs the actions, or B in case P runs the actions;
Input/condition:
OLA are IN-NEGOTIATION and proposal was received from OTHER PARTY
Actions:
PARTY can agree on the proposal; then the OLA is set AGREED
PARTY can reject the proposal; then the OLA is set to CANCELLED
PARTY can send a new proposal (offer changes); then the OLA remains in IN-NEGOTIATION, the new proposal is sent to OTHER PARTY
link do work instr
opis przycisków
filmik
3. OLA confirmation/rejection
<style type="text/css">P { margin-bottom: 0.21cm; color: rgb(0, 0, 0); }P.western { font-family: "Times New Roman",serif; font-size: 12pt; }P.cjk { font-family: "DejaVu Sans","Arial",sans-serif; font-size: 12pt; }P.ctl { font-family: "Times New Roman",serif; font-size: 12pt; }A:link { color: rgb(0, 0, 255); text-decoration: underline; }</style>
This procedure is valid only for the right-to-revoke scenario.
In case of no action, OLA is made AGREED automatically after revoke period.
Input/conditions:
- OLA is in the state AGREED-REVOKABLE
Action:
- provider can confirm OLA, which makes OLA AGREED
- provider can reject OLA, which makes OLA CANCELLED
- provider can propose changes to the OLA, which makes OLA IN-NEGOTIATION and proposal is sent to B