On Mouse Over
On Mouse Over
On Mouse Over
On Mouse Over
On Mouse Over
     
 

COMMERCIAL & HEDGE ACCOUNTS

Through RCG's Guaranteed Introducing Broker, RCI Advisory Services,
Sweet Futures has the ability to provide it's new Commercial clients with Informa Economics Research.

 

Click on one of the many report below for a historical example of what we can offer you as a Sweet Future's Commercial Customer.

Topic/Content
Daily
Weekly
Morning Comments
X
 
Energy Comments
X
 
Dairy Weekly   
X

 

Click here to view other available reports

Each Monday, beginning in April and continuing throughout the Northern Hemisphere growing season, Informa Economics updates its crop progress and condition tables to keep you informed of the latest developments in major US field crops. The current year crop progress is compared with historical normals and then summarized by crop and major growing regions. The condition tables contain an index computed from USDA's weekly condition ratings. Please choose one of the crops from the list above to view tables (in pdf format) for the week ending the previous Sunday. ( Note that not all tables will be available during the same week, dependent upon the time of the season and the crop's normal growing cycle.)

Corn Progress Tables ( © Informa Economics, Inc. )
Planted Dent
Emerged Mature
Silked Harvested
Dough Condition
 
Rice Progress Tables ( © Informa Economics, Inc. )
Planted Headed
Emerged Harvested
Condition  
Dough  
 
Spring Wheat Progress Tables ( © Informa Economics, Inc. )
Planted Open Bolls
Emerged Harvested
Condition Condition
 
Cotton Progress Tables ( © Informa Economics, Inc. )
Planted Headed
Squaring Harvested
Set Bolls  
Oats Progress Tables ( © Informa Economics, Inc. )
Planted Headed
Emerged Harvested
Condition  
 
Winter Wheat ( © Informa Economics, Inc. )
Planted Headed
Emerged Harvested
Condition  
 
Soybeans Progress Tables ( © Informa Economics, Inc. )
Planted Set Pods
Emerged Drop Leaves
Blooming Harvested
Condition  
 
 

* Required Field

 

First Name:*

E-mail Address: *

Daytime Phone: *

Best time to call : *
 

 

Risk Management for Commercial users.  We provide clearing / execution and daily research for Grains, Livestock, Pork, Pigs, Cattle, Natural gas Crude oil and Weather.

 

Risk management From Wikipedia

Risk management is activity directed towards the assessing, mitigating (to an acceptable level) and monitoring of risks. In some cases the acceptable risk may be near zero. Risks can come from accidents, natural causes and disasters as well as deliberate attacks from an adversary. The main ISO standards on risk management include [1], [2]. In businesses, risk management entails organized activity to manage uncertainty and threats and involves people following procedures and using tools in order to ensure conformance with risk-management policies.
The strategies include transferring the risk to another party, avoiding the risk, reducing the negative effect of the risk, and accepting some or all of the consequences of a particular risk.
Some traditional risk management programs (e.g., health risk assessment) are focused on risks stemming from physical or legal causes (e.g. natural disasters or fires, accidents, ergonomics, death and lawsuits). Financial risk management, on the other hand, focuses on risks that can be managed using traded financial instruments.

Introduction

This section provides an introduction to the principles of risk management. The vocabulary of risk management is defined in ISO Guide 73, "Risk management. Vocabulary" [1]. In ideal risk management, a prioritization process is followed whereby the risks with the greatest loss and the greatest probability of occurring are handled first, and risks with lower probability of occurrence and lower loss are handled in descending order. In practice the process can be very difficult, and balancing between risks with a high probability of occurrence but lower loss versus a risk with high loss but lower probability of occurrence can often be mishandled.
Intangible risk management identifies a new type of risk - a risk that has a 100% probability of occurring but is ignored by the organization due to a lack of identification ability. For example, when deficient knowledge is applied to a situation, a knowledge risk materializes. Relationship risk appears when ineffective collaboration occurs. Process-engagement risk may be an issue when ineffective operational procedures are applied. These risks directly reduce the productivity of knowledge workers, decrease cost effectiveness, profitability, service, quality, reputation, brand value, and earnings quality. Intangible risk management allows risk management to create immediate value from the identification and reduction of risks that reduce productivity.
Risk management also faces difficulties allocating resources. This is the idea of opportunity cost. Resources spent on risk management could have been spent on more profitable activities. Again, ideal risk management minimizes spending while maximizing the reduction of the negative effects of risks.

Principles of risk management

The International Organization for Standardization identifies the following principles of risk management: [1]

  • Risk management should create value.
  • Risk management should be an integral part of organizational processes.
  • Risk management should be part of decision making.
  • Risk management should explicitly address uncertainty.
  • Risk management should be systematic and structured.
  • Risk management should be based on the best available information.
  • Risk management should be tailored.
  • Risk management should take into account human factors.
  • Risk management should be transparent and inclusive.
  • Risk management should be dynamic, iterative and responsive to change.
  • Risk management should be capable of continual improvement and enhancement.
  •  

    Process

    According to the standard ISO/DIS 31000 "Risk management -- Principles and guidelines on implementation" [2], the process of risk management consists of several steps as follows

    :Establishing the context

    Establishing the context involves

      1. Identification of risk in a selected domain of interest
      2. Planning the remainder of the process
      3. Mapping out the following:

      • the social scope of risk management
      • the identity and objectives of stakeholders
      • the basis upon which risks will be evaluated, constraints.

       

      4. Defining a framework for the activity and an agenda for identification.
      5. Developing an analysis of risks involved in the process
      6. Mitigation of risks using available technological, human and organizational resources.

    Identification

    After establishing the context, the next step in the process of managing risk is to identify potential risks. Risks are about events that, when triggered, cause problems. Hence, risk identification can start with the source of problems, or with the problem itself.

    • Source analysis Risk sources may be internal or external to the system that is the target of risk management. Examples of risk sources are: stakeholders of a project, employees of a company or the weather over an airport.
    • Problem analysis Risks are related to identified threats. For example: the threat of losing money, the threat of abuse of privacy information or the threat of accidents and casualties. The threats may exist with various entities, most important with shareholders, customers and legislative bodies such as the government.

    When either source or problem is known, the events that a source may trigger or the events that can lead to a problem can be investigated. For example: stakeholders withdrawing during a project may endanger funding of the project; privacy information may be stolen by employees even within a closed network; lightning striking a Boeing 747 during takeoff may make all people onboard immediate casualties.
    The chosen method of identifying risks may depend on culture, industry practice and compliance. The identification methods are formed by templates or the development of templates for identifying source, problem or event. Common risk identification methods are:

    • Objectives-based risk identification Organizations and project teams have objectives. Any event that may endanger achieving an objective partly or completely is identified as risk.
    • Scenario-based risk identification In scenario analysis different scenarios are created. The scenarios may be the alternative ways to achieve an objective, or an analysis of the interaction of forces in, for example, a market or battle. Any event that triggers an undesired scenario alternative is identified as risk - see Futures Studies for methodology used by Futurists.
    • Taxonomy-based risk identification The taxonomy in taxonomy-based risk identification is a breakdown of possible risk sources. Based on the taxonomy and knowledge of best practices, a questionnaire is compiled. The answers to the questions reveal risks. Taxonomy-based risk identification in software industry can be found in CMU/SEI-93-TR-6.
    • Common-risk checking In several industries lists with known risks are available. Each risk in the list can be checked for application to a particular situation. An example of known risks in the software industry is the Common Vulnerability and Exposures list found at http://cve.mitre.org.
    • Risk charting (risk mapping) This method combines the above approaches by listing Resources at risk, Threats to those resources Modifying Factors which may increase or decrease the risk and Consequences it is wished to avoid. Creating a matrix under these headings enables a variety of approaches. One can begin with resources and consider the threats they are exposed to and the consequences of each. Alternatively one can start with the threats and examine which resources they would affect, or one can begin with the consequences and determine which combination of threats and resources would be involved to bring them about.

    Assessment

    Once risks have been identified, they must then be assessed as to their potential severity of loss and to the probability of occurrence. These quantities can be either simple to measure, in the case of the value of a lost building, or impossible to know for sure in the case of the probability of an unlikely event occurring. Therefore, in the assessment process it is critical to make the best educated guesses possible in order to properly prioritize the implementation of the risk management plan.
    The fundamental difficulty in risk assessment is determining the rate of occurrence since statistical information is not available on all kinds of past incidents. Furthermore, evaluating the severity of the consequences (impact) is often quite difficult for immaterial assets. Asset valuation is another question that needs to be addressed. Thus, best educated opinions and available statistics are the primary sources of information. Nevertheless, risk assessment should produce such information for the management of the organization that the primary risks are easy to understand and that the risk management decisions may be prioritized. Thus, there have been several theories and attempts to quantify risks. Numerous different risk formulae exist, but perhaps the most widely accepted formula for risk quantification is:
    Rate of occurrence multiplied by the impact of the event equals risk
    Later research has shown that the financial benefits of risk management are less dependent on the formula used but are more dependent on the frequency and how risk assessment is performed.
    Later research has shown that the financial benefits of risk management are less dependent on the formula used but are more dependent on the frequency and how risk assessment is performed.
    In business it is imperative to be able to present the findings of risk assessments in financial terms. Robert Courtney Jr. (IBM, 1970) proposed a formula for presenting risks in financial terms. The Courtney formula was accepted as the official risk analysis method for the US governmental agencies. The formula proposes calculation of ALE (annualized loss expectancy) and compares the expected loss value to the security control implementation costs (cost-benefit analysis).

    Risk transfer

    IIn the terminology of practitioners and scholars alike, the purchase of an insurance contract is often described as a "transfer of risk." However, technically speaking, the buyer of the contract generally retains legal responsibility for the losses "transferred", meaning that insurance may be described more accurately as a post-event compensatory mechanism. For example, a personal injuries insurance policy does not transfer the risk of a car accident to the insurance company. The risk still lies with the policy holder namely the person who has been in the accident. The insurance policy simply provides that if an accident (the event) occurs involving the policy holder then some compensation may be payable to the policy holder that is commensurate to the suffering/damage.
    Some ways of managing risk fall into multiple categories. Risk retention pools are technically retaining the risk for the group, but spreading it over the whole group involves transfer among individual members of the group. This is different from traditional insurance, in that no premium is exchanged between members of the group up front, but instead losses are assessed to all members of the group.

    Create a risk-management plan

    Select appropriate controls or countermeasures to measure each risk. Risk mitigation needs to be approved by the appropriate level of management. For example, a risk concerning the image of the organization should have top management decision behind it whereas IT management would have the authority to decide on computer virus risks. The risk management plan should propose applicable and effective security controls for managing the risks. For example, an observed high risk of computer viruses could be mitigated by acquiring and implementing antivirus software. A good risk management plan should contain a schedule for control implementation and responsible persons for those actions.
    According to ISO/IEC 27001, the stage immediately after completion of the Risk Assessment phase consists of preparing a Risk Treatment Plan, which should document the decisions about how each of the identified risks should be handled. Mitigation of risks often means selection of security controls, which should be documented in a Statement of Applicability, which identifies which particular control objectives and controls from the standard have been selected, and why.

    Implementation

    Follow all of the planned methods for mitigating the effect of the risks. Purchase insurance policies for the risks that have been decided to be transferred to an insurer, avoid all risks that can be avoided without sacrificing the entity's goals, reduce others, and retain the rest.

    Review and evaluation of the plan

    Initial risk management plans will never be perfect. Practice, experience, and actual loss results will necessitate changes in the plan and contribute information to allow possible different decisions to be made in dealing with the risks being faced.
    Risk analysis results and management plans should be updated periodically. There are two primary reasons for this:

  • to evaluate whether the previously selected security controls are still applicable and effective, and
  • to evaluate the possible risk level changes in the business environment. For example, information risks are a good example of rapidly changing business environment.
  •  

    Risk-management activities as applied to project management

    In project management, risk management includes the following activities:

  • Planning how risk will be managed in the particular project. Plan should include risk management tasks, responsibilities, activities and budget.
  • Assigning a risk officer - a team member other than a project manager who is responsible for foreseeing potential project problems. Typical characteristic of risk officer is a healthy skepticism.
  • Maintaining live project risk database. Each risk should have the following attributes: opening date, title, short description, probability and importance. Optionally a risk may have an assigned person responsible for its resolution and a date by which the risk must be resolved.
  • Creating anonymous risk reporting channel. Each team member should have possibility to report risk that he foresees in the project.
  • Preparing mitigation plans for risks that are chosen to be mitigated. The purpose of the mitigation plan is to describe how this particular risk will be handled – what, when, by who and how will it be done to avoid it or minimize consequences if it becomes a liability.
  • Summarizing planned and faced risks, effectiveness of mitigation activities, and effort spent for the risk management.
  • Risk management and business continuity

    Risk management is simply a practice of systematically selecting cost effective approaches for minimizing the effect of threat realization to the organization. All risks can never be fully avoided or mitigated simply because of financial and practical limitations. Therefore all organizations have to accept some level of residual risks.
    Whereas risk management tends to be preemptive, business continuity planning (BCP) was invented to deal with the consequences of realized residual risks. The necessity to have BCP in place arises because even very unlikely events will occur if given enough time. Risk management and BCP are often mistakenly seen as rivals or overlapping practices. In fact these processes are so tightly tied together that such separation seems artificial. For example, the risk management process creates important inputs for the BCP (assets, impact assessments, cost estimates etc). Risk management also proposes applicable controls for the observed risks. Therefore, risk management covers several areas that are vital for the BCP process. However, the BCP process goes beyond risk management's preemptive approach and moves on from the assumption that the disaster will realize at some point.

    References

    1. ^ "Committee Draft of ISO 31000 Risk management" (PDF). International Organization for Standardization. http://www.nsai.ie/uploads/file/N047_Committee_Draft_of_ISO_31000.pdf. 
    2. ^ Dorfman, Mark S. (2007). Introduction to Risk Management and Insurance (9th Edition). Englewood Cliffs, N.J: Prentice Hall. ISBN 0-13-224227-3. 
    3. ^ Roehrig, P (2006) Bet On Governance To Manage Outsourcing Risk. Business Trends Quarterly

    General references

    • ISO/IEC Guide 73:2002 (2002). Risk management -- Vocabulary -- Guidelines for use in standards. International Organization for Standardization. http://www.iso.org/iso/catalogue_detail?csnumber=34998.  ISO/DIS 31000 (2009). Risk management -- Principles and guidelines on implementation. International Organization for Standardization. http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=43170. 
    • Crockford, Neil (1986). An Introduction to Risk Management (2nd ed.). Woodhead-Faulkner. ISBN 0-85941-332-2.