Sunday, January 08, 2006

Risk Management




RISK MANAGEMENT


Termenul de „risk managment”, este un termen relativ nou, domeniul de activitate fiind recunodcut abia prin anii 1929, 1930, cind conceptul de risc management si termenii de referinta asociati au fost definiti pentru prima data. Sa fi avut oare ceva de a face cu profunda criza economica ce a cupris toate economiile in acea perioada? Nu credem ca necesitatea dezvoltarii acestei ramuri de management a afacerilor a fost direct influentata de crizele economica ale anilor 30. Abia atunci, majoritatea celor care si-au vazut afacerile decimate sau pornite pe calea dezastrului, au inceput sa caute cai de diminuare a pierderilor. Cu toate ca acea catastrofa economica a reusit sa modifice hrta economica a lumi, in urme ei a lasind oameni pe ginduri si a nascut o noua metoda de a negocia cu si pentru recuperarea pagubelor ne asteptate.
In cautare unei atmosfere de relaxare si liniste economica, s-a nascut si s-a dezvoltat managementul riscului ca stiinta noua, menita pentru inceput sa elibereze gindirea agentului economic de teroare unei pierderi iminenete. Deci putem spune ca, necesitatea cimpului de activitate a luat nastere din nevoia de a avea functionalitate exclusiv economica, cu o singura grija, si anume profitul. In acest scop, mai toate societatile comerciale si-au angajat consultanti de risc, sau au infiintat dupa caz , departamente de „management al asigurarilor”. Pina si astazi , cuvintul risc provoaca fiori si nu ne putem abtine sa nu zimbim cind vedem ca marile antreprize economice aseza acast capitol sub jurisdictia departamentelor de resurse umane sau de marketing. La urma urmei…trebuie sa avem o atitudine pozitiva relativ la afacere si la derularea ei, iar elementele de risc ne pot deturna gindirea „pozitiva” de la activitatile de zi ci zi. Zimbim cu condescendetza si recunoastem aceasta deficienta, dar pe de alta parte ne pozitionam in afara riscurilor ne acoperite. Cu referirre la Romania, trebuie sa facem observatia ca managementul asigurarilor, nu prea exista…despre cel a riscuroilor nici nu poate fi vorba comparati cu alte tari Europene de vest, deci, masurind fatorii de risc ai teritoriului ca si ai mediului de afaceri , gasim lacune serioase in gindirea contemporanilor nostri care noi consideram ca vor trebui sa se aseze si ei in rindul afaceristilor de anvergura externi. De asemenea , consideram ca economia romanesca a ajuns la un plafon suficient de inalt si la o stabilitate relativ solida, astfel incit pierderile datorate crizelor sa poata da nastere unor traume sociale de proportii.
Mircea Halaciuga, Esq. Presedinte

3 comments:

Managementul Riscurilor Globale said...

Designing Your Training
The questions below were created to guide you through the process of designing training for your organization.
What are your organization's usual practices for staff training? Many organizations have on-going staff training programs. Your risk management training should be incorporated into other existing organizational training practices.
Who will do the training? Selection of instructors will influence the nature of your training program. Training might be delivered by a staff member, outside consultant, or in some cases a law enforcement officer or other government official (e.g., child protective services worker).
How will the training be delivered? Will individuals undertake training individually or in a group session? Must participants gather in a single location or can they be trained from remote locations? A growing number of organizations are choosing online and video-based training programs to ensure consistency of content and lower costs. Keep in mind that if training costs are prohibitive to the nonprofit the risk of untrained staff increases; some staff may not be trained as dollars run out to continue a costly training program.
When will the training be provided? Your organization may begin training staff in child abuse prevention before applicants are placed. One national mentoring organization conducts program orientation sessions for applicants. The orientation stresses the organization's position on child abuse, thereby setting a tone for subsequent training and perhaps inducing potential abusers to withdraw their applications. Always consider the audience when scheduling training—if your volunteers are busy professionals, consider how you can offer meaningful training without taxing their busy schedules.
How will training be evaluated and documented? When your staff is trained, how will you measure the fulfillment of the training objectives? Good training includes oral, written, or performance tests at the end to measure the trainees' retention of knowledge and ability to perform the skills they were taught. Your organization may need to maintain training records that document participation in training and post-training test results.

Managementul Riscurilor Globale said...

Risk Management Classroom Now Available
Finally. Affordable risk management training tailored for nonprofit personnel. Available 24/7. On site and well within your reach. Designed for busy nonprofit staff by the Nonprofit Risk Management Center, the brand-new Risk Management Classroom courses are easy to navigate and include final tests with immediate scoring. Users who successfully complete a course may generate a Certificate of Completion to show their mastery of the material.

Featured courses include:
Risk Management Basics
Volunteer Risk Management
Insurance Basics
Managing Your Insurance Program
Contracting with Care
Managing Governance Risks
Managing Employment Practices
Effective Staff and Volunteer Screening
Principles of Youth Development
Principles of Youth Protection
Driver and Vehicle Safety
Special Event Safety
Managing Facility Risks
Risk Management for Sports and Recreation Programs

Managementul Riscurilor Globale said...

Risk Management




Background | SEI Risk Statement | Risk Examples
Software Risk Evaluation | Continuous Risk Management Guidebook
Risk Process Check | For More Information

Background
The term risk management is applied in a number of diverse disciplines. People in the fields of statistics, economics, psychology, social sciences, biology, engineering, toxicology, systems analysis, operations research, and decision theory, to name a few, have been addressing the field of risk management.

Kloman summarized the meaning of risk management in the context of a number of different disciplines in an article for Risk Analysis:

"What is risk management? To many social analysts, politicians, and academics it is the management of environmental and nuclear risks, those technology-generated macro-risks that appear to threaten our existence. To bankers and financial officers it is the sophisticated use of such techniques as currency hedging and interest rate swaps. To insurance buyers and sellers it is coordination of insurable risks and the reduction of insurance costs. To hospital administrators it may mean 'quality assurance.' To safety professionals it is reducing accidents and injuries."

Kloman Paraphrase of Rowe
Risk management is a discipline for living with the possibility that future events may cause adverse effects.

Return to top

SEI Risk Statement
For a risk to be understandable, it must be expressed clearly. Such a statement must include

a description of the current conditions that may lead to the loss
a description of the loss
Risk Example
A company has introduced object-oriented (OO) technology into its organization by selecting a well-defined project "X" with hard schedule constraints to pilot the use of the technology. Although many "X" project personnel were familiar with the OO concept, it had not been part of their development process, and they have had very little experience and training in the technology's application. It is taking project personnel longer than expected to climb the learning curve. Some personnel are concerned, for example, that the modules implemented to date might be too inefficient to satisfy project "X" performance requirements.

The risk is: Given the lack of OO technology experience and training, there is a possibility that the product will not meet performance or functionality requirements within the defined schedule.

Non-Risk Example
Another company is developing a flight control system. During system integration testing the flight control system becomes unstable because processing of the control function is not quick enough during a specific maneuver sequence.

The instability of the system is not a risk since the event is a certainty - it is a problem.

Continuous Risk Management Example
When using Continuous Risk Management, risks are assessed continuously and used for decision-making in all phases of a project. Risks are carried forward and dealt with until they are resolved or they turn into problems and are handled as such.

Non-Continuous Risk Management Example
In some projects, risks are assessed only once during initial project planning. Major risks are identified and mitigated, but risks are never explicitly looked at again.

This is not an example of Continuous Risk Management because risks are not continuously assessed and new risks are not continuously identified.

Return to top

Software Risk Evaluation
The SEI Software Risk Evaluation (SRE) Service is a diagnostic and decision-making tool that enables the identification, analysis, tracking, mitigation, and communication of risks in software-intensive programs. An SRE is used to identify and categorize specific program risks emanating from product, process, management, resources, and constraints. The program's own personnel participate in the identification, analysis, and mitigation of risks facing their own development effort.

An SRE provides a program manager with a mechanism to anticipate and address program risks. The SRE introduces a set of activities that, when initiated, begin the process of managing risk. These activities can be integrated with existing methods and tools to enhance program management practices.

For more information, see Software Risk Evaluation Service Web page.

Return to top

Risk Process Check
A Risk Process Check is the SEI's most recently developed risk management service. It is combination of tutorial, survey instrument, interviews, and feedback session conducted on-site to determine how effective the project or program's risk management process is. It is based on the SEI's Seven Principles of Risk Management, and, being principle-based rather than model-based, it can evaluate any risk management process, whether it follows the guidelines of the SEI's Continuous Risk Management course or some completely different model.

The Risk Process Check has been used on one major DoD program (DoD program office, prime contractor, and two subcontractors to the prime) and two contractor organizations to a non-DoD government agency. There are many areas of opportunity to refine and further define this service with the SEI.

Continuous Risk Management Guidebook
The Continuous Risk Management Guidebook was written with professionals in mind who are directly involved in software-intensive projects (program managers, lead engineers, software engineers, etc.). It may also be of interest to professionals from other disciplines (e.g., quality assurance, hardware engineering, testing) involved in software-intensive projects, and sponsors, change agents, technology transition agents, and software engineering process group members in organizations that want to improve.

The Continuous Risk Management Guidebook describes the underlying principles, concepts, and functions of risk management and provides guidance on how to implement it as a continuous practice in your projects and organization. Risk management can be used to continuously assess what can go wrong in projects (i.e., what the risks are), determine which of these risks are most important, and implement strategies to deal with these risks. The guidebook is based on proven practices confirmed through research, field testing, and direct work with clients.

The Continuous Risk Management Guidebook was developed to help a project or organization establish continuous risk management as a routine practice and then continue to improve this process. It is organized so that different users can read different parts of the book and get different benefits. For example, technical managers and lead engineers can read the book to learn how to build a risk management process that is tailored to their specific project or organization; software engineers can use it to understand how to perform the risk management methods and use the tools described in the guidebook; and change agents (such as members of software engineering process groups) can read it to understand why continuous risk management should be used and how to get projects to tailor it and start using it. In addition, all users of this guidebook will gain a greater understanding of continuous risk management.

Although the Guidebook deals primarily with performing continuous risk management in a software development environment, it can easily address systems, hardware, and other domains.

For more detailed information, visit the CRM Guidebook Web page.