Charlie;
Upon further questioning on 2003-04 PPO contracts, the CWB now appears to be removing the “pool basis” part of the pricing calculation. If I have this correct, the CWB is inserting a “projected futures price” in the place of the “pool basis” which I am told will make the basis between PRO’s “less volatile” .
What does all this mean, Charlie?
Now, regarding CWB handling of the futures transacted on behalf of PPO contract holders...
I am told CWB hedges the producer pricing options by selling the futures when producers lock-in a FPC or when they lock-in the futures component of a Basis Price Contract (BPC). Then CWB takes this hedge off by buying back (unwinds) the futures as the CWB does pool sales, instead of taking the hedge off as the specific PPO contracted grain is delivered to fill the PPO contract held by a specific producer.
Producer Timing of PPO contract deliveries are optional to the grain producer WHEN a PPO contract is filled.
PPO contracts can be any time during the crop year… from the first deliveries made (in August for instance)… to the option of the producer to be the last delivered wheat to the CWB in the last month of the crop year.
This is what Adrian Measner wrote me on February 24th, 2003;
"As you may be aware, the CWB hedges the producer pricing options by selling the futures when producers lock-in a FPC contract or when they lock-in the futures component of a Basis Price Contract (BPC). THE CWB UNWINDS THIS HEDGE BY BUYING BACK THE FUTURES AS THE CWB PUTS SALES ON THE BOOKS (ESSENTIALLY THE CWB IS BUYING THESE PRODUCERS OUT OF THE POOL ACCOUNT OR OUT OF ALL SALES). THEREFORE, MOST OF THE FUTURES BOUGHT BACK TO DATE WOULD HAVE BEEN PURCHASED AT VALUES HIGHER THEN THE CURRENT MARKET." (EMPHASIS ADDED)
How does this CWB risk management strategy actually mitigate risk?
How can a specific PPO contract be tracked, to actually determine real costs of liquidating a PPO contract?
If the CWB manages to create such a web of chaos in PPO contracts, what strategy is used with Pooling risk mitigation?
Has anyone got answers?
Upon further questioning on 2003-04 PPO contracts, the CWB now appears to be removing the “pool basis” part of the pricing calculation. If I have this correct, the CWB is inserting a “projected futures price” in the place of the “pool basis” which I am told will make the basis between PRO’s “less volatile” .
What does all this mean, Charlie?
Now, regarding CWB handling of the futures transacted on behalf of PPO contract holders...
I am told CWB hedges the producer pricing options by selling the futures when producers lock-in a FPC or when they lock-in the futures component of a Basis Price Contract (BPC). Then CWB takes this hedge off by buying back (unwinds) the futures as the CWB does pool sales, instead of taking the hedge off as the specific PPO contracted grain is delivered to fill the PPO contract held by a specific producer.
Producer Timing of PPO contract deliveries are optional to the grain producer WHEN a PPO contract is filled.
PPO contracts can be any time during the crop year… from the first deliveries made (in August for instance)… to the option of the producer to be the last delivered wheat to the CWB in the last month of the crop year.
This is what Adrian Measner wrote me on February 24th, 2003;
"As you may be aware, the CWB hedges the producer pricing options by selling the futures when producers lock-in a FPC contract or when they lock-in the futures component of a Basis Price Contract (BPC). THE CWB UNWINDS THIS HEDGE BY BUYING BACK THE FUTURES AS THE CWB PUTS SALES ON THE BOOKS (ESSENTIALLY THE CWB IS BUYING THESE PRODUCERS OUT OF THE POOL ACCOUNT OR OUT OF ALL SALES). THEREFORE, MOST OF THE FUTURES BOUGHT BACK TO DATE WOULD HAVE BEEN PURCHASED AT VALUES HIGHER THEN THE CURRENT MARKET." (EMPHASIS ADDED)
How does this CWB risk management strategy actually mitigate risk?
How can a specific PPO contract be tracked, to actually determine real costs of liquidating a PPO contract?
If the CWB manages to create such a web of chaos in PPO contracts, what strategy is used with Pooling risk mitigation?
Has anyone got answers?
Comment