CMMN Modeling of the Risk Management Process Extended Abstract

Total Page:16

File Type:pdf, Size:1020Kb

CMMN Modeling of the Risk Management Process Extended Abstract CMMN modeling of the risk management process Extended abstract Tiago Barros Ferreira Instituto Superior Técnico [email protected] ABSTRACT Enterprise Risk Management (ERM) is thus a very important activity to support the Risk management is a development activity and achievement of the organizations' goals. increasingly plays a crucial role in Risk management is defined as “coordinated organization´s management. Being very activities to direct and control an organization valuable for organizations, they develop and with regard to risk” [1]. ERM, as a risk implement enterprise risk management management activity, comprises the strategies that improve their business model identification of the potential events in the whole and bring them better results. Enterprise risk organization that can affect the objectives, the management strategies are based on the respective risk appetite, and thus, with implementation of a risk management process reasonable assurance, the fulfillment of the and supporting structure. Together, this process organization's goals [2]. and structure form a framework. ISO 31000 Many organizations nowadays have their standard is currently the main global reference risk management framework, including framework for risk management, proposing the activities to identify their risks, and their general principles and guidelines for risk prevention measures, documented. To this end, management, regardless of context. The most [1] is at this moment the main reference for risk recent revision of the standard ISO 31000:2018 management frameworks, proposing the [1] depicts the process of risk management as general principles and guidelines for risk a case rather than a sequential process. To that management, regardless of their context. end, it was explored the potential and limitations The guidelines for risk management of the conceptual modeling language “Case processes described in [1] suggest a process in Management Model and Notation” (CMMN) for which the flow is not always deterministic, the elaboration of the related diagrams, and the where the decision of which next activity to “Decision Model and Notation” (DMN) notation perform depends on the judgment of the case to model risk decisions. The application of the worker. Moreover, different techniques, such as model is also demonstrated for a real case. those described in [3], may be applied in risk identification and should consider several KEYWORDS factors such as causes, events, consequences Risk, risk management, enterprise risk and risk sources. These facts make the management, CMMN, DMN problem potentially relevant to be modeled with 1. Introduction CMMN, a modeling language that has been As described in [1], risk is the “effect of recently affirmed for this type of processes. uncertainty on objectives” an effect being “a This paper is structured in eight more deviation from the expected”. The effect can be sections. Section two describes the main positive, negative or both, and thus it can concepts of risk management related to ISO address, create or result in opportunities or 31000. Section three presents the concept of threats. Still according to [1], risk can be case management and the CMMN language. In expressed in terms of: (i) Risk sources: An section four a preliminary analysis of the element that, alone or in combination with problem is made where it is proposed a CMMN others, has the potential to cause the risk; (ii) modelling of the ISO 31000 risk management Potential events: Occurrence or change of a process. Section five presents the analysis and particular set of circumstances; (iii) solution for the problem with the resulting Consequences: Outcome of an event that CMMN models for the risk management affects the objectives; (iv) Likelihood: Chance of process defined in the INCM´s ERM framework something happening. [4]. Section six presents the UML models of the In an organization, every process, from the domain model and the use cases that will serve simplest to the most complex, is subject to risks as the basis for the construction of an and its consequences can have positive or application1 using the Outsystems2 negative effects on the organizations' goals. methodology. Section seven presents a 1 Work already started in another dissertation 2 https://www.outsystems.com/ 1 comparative analysis on the two CMMN models understand the basis for the decisions made that were modeled. Last section presents the and the reasons for the need for specific conclusions of the dissertation and define future actions. steps to continue this dissertation. I) Recording and reporting: aims to communicate risk management activities and 2. Risk management concepts – ISO results across the organization; support 31000:2018 standard interaction with those who have responsibility The risk management process described in [1] and accountability for risk management and illustrated in Figure 1, “should be an integral activities; provide information for decision- part of management and decision-making and making; and improve risk management integrated into the structure, operations and activities. processes of the organization. It can be applied at strategic, operational, programme or project 3. Case management and case levels” [1]. It is up to each organization to adapt management model and notation the risk management process to its goals and to Automating processes increases their the context in which it is inserted. However, the efficiency. But not all processes can be main references activities of this process should automated, and as such, for situations where be: they require more flexibility, a proper approach A) Scope, context and criteria: since the is required in building the process where flow process can be applied at different levels, it is control is not used to describe the process. essential for the organizations to clearly define Case management empowers workers by the scope of its risk management activities and providing them with access to all information to understand the internal and external context about the process and giving them autonomy in which it operates. For the definition of the risk and control over how a process evolves [5]. criteria, the organization shall specify the In this type of process, the main concepts magnitude and types of risk that it may or may are: (i) A set of unordered activities that can be not assume considering its goals, values and performed completely to solve a business resources. problem; (ii) Activities occur in an unpredictable B) Risk assessment: should be carried out in a order; (iii) Events determine the process; systematic, iterative and collaborative manner, therefore, the resulting case may vary using the best available information. This depending on the current event. The activities activity is composed of the sub-activities: risk are not linked to each other; (iv) External identification, risk analysis and risk evaluation. documents are a fundamental part of the C) Risk identification: aims to “find, recognize process. and describe risks that might help or prevent an The OMG (Object Management Group) organization achieving its objectives” [1]. introduced CMMN [6], a notation to model and D) Risk analysis: aims to “comprehend the graphically express these knowledge-intensive nature of the risk and its characteristics” [1]. and weakly-structured processes. Detailed consideration of the risk characteristics CMMN can be used in addition to BPMN. (uncertainties, sources, consequences, events, CMMN uses an event-centric and case file controls and their effectiveness) allow the risk concept approach, bringing new flexibility to level to be calculated where appropriate. business process. It can specify what can E) Risk assessment: results obtained in the risk happen in a process, but not how it should analysis are compared with the risk criteria happen. initially established in order to determine what From this perspective, a case has two action to take against the risks analyzed. distinct phases, the design-time phase and the F) Risk treatment: based on the outcome of the run-time phase. During the design-time phase risk evaluation activity, the process moves to the business analysts model the plan items that the treatment phase where risk treatment are always part of the case model and the options will be selected and implemented. discretionary items, that are modeled but are G) Monitoring and review: monitoring and not immediately added to the execution plan. review the risk management process and its During the run-time phase case workers results should be an integral part of all phases execute the plan executing the planned items of the process with the aim of improving its and optionally add, in current time, discretionary effectiveness and quality. items to the execution plan of the case instance. H) Communication and consultation: should The flow control of the case is thus exercised by take place throughout the process on a the case workers assigning them greater continuous basis. It allows stakeholders to responsibility in the case. 2 Figure 1 - Risk management process according to [1] The complete case behavior is modeled using execution (entry criteria) or when a case the elements illustrated in Figure 23 and is (case plan), stage, or task should terminate captured by the case plan model: abnormally (exit criteria). Criteria can be • Stage: It can be seen as an “episode” of the IfPart meaning that there is a Boolean case. It groups various language elements expression which is part of the criteria and including tasks, milestones, case file items, should evaluate to true for the criteria to be and events. satisfied, or OnPart which indicates which • Task: It is a unit of work. They can be divided standard event can satisfy the entry criteria into blocking and non-blocking human tasks, or exit criteria process-tasks, case-tasks, and decision- To represent certain dependencies and tasks. associations between non-discretionary • Discretionary element (only for tasks and elements of the plan, CMMN uses connectors. stages): An element that can be added, These connectors are illustrated by a line with optionally and in current time, to the the “dash-dot-dot-dash” sequence.
Recommended publications
  • Deliverable D7.5: Standards and Methodologies Big Data Guidance
    Project acronym: BYTE Project title: Big data roadmap and cross-disciplinarY community for addressing socieTal Externalities Grant number: 619551 Programme: Seventh Framework Programme for ICT Objective: ICT-2013.4.2 Scalable data analytics Contract type: Co-ordination and Support Action Start date of project: 01 March 2014 Duration: 36 months Website: www.byte-project.eu Deliverable D7.5: Standards and methodologies big data guidance Author(s): Jarl Magnusson, DNV GL AS Erik Stensrud, DNV GL AS Tore Hartvigsen, DNV GL AS Lorenzo Bigagli, National Research Council of Italy Dissemination level: Public Deliverable type: Final Version: 1.1 Submission date: 26 July 2017 Table of Contents Preface ......................................................................................................................................... 3 Task 7.5 Description ............................................................................................................... 3 Executive summary ..................................................................................................................... 4 1 Introduction ......................................................................................................................... 5 2 Big Data Standards Organizations ...................................................................................... 6 3 Big Data Standards ............................................................................................................. 8 4 Big Data Quality Standards .............................................................................................
    [Show full text]
  • A Quick Guide to Responsive Web Development Using Bootstrap 3
    STEP BY STEP BOOTSTRAP 3: A QUICK GUIDE TO RESPONSIVE WEB DEVELOPMENT USING BOOTSTRAP 3 Author: Riwanto Megosinarso Number of Pages: 236 pages Published Date: 22 May 2014 Publisher: Createspace Independent Publishing Platform Publication Country: United States Language: English ISBN: 9781499655629 DOWNLOAD: STEP BY STEP BOOTSTRAP 3: A QUICK GUIDE TO RESPONSIVE WEB DEVELOPMENT USING BOOTSTRAP 3 Step by Step Bootstrap 3: A Quick Guide to Responsive Web Development Using Bootstrap 3 PDF Book Written by a team of noted teaching experts led by award-winning Texas-based author Dr. Today we knowthat many other factors in?uence the well- functioning of a computer system. Rossi, M. Answers to selected exercises and a list of commonly used words are provided at the back of the book. He demonstrates how the most dynamic and effective people - from CEOs to film-makers to software entrepreneurs - deploy them. The chapters in this volume illustrate how learning scientists, assessment experts, learning technologists, and domain experts can work together in an integrated effort to develop learning environments centered on challenge-based instruction, with major support from technology. This continues to be the only book that brings together all of the steps involved in communicating findings based on multivariate analysis - finding data, creating variables, estimating statistical models, calculating overall effects, organizing ideas, designing tables and charts, and writing prose - in a single volume. Step by Step Bootstrap 3: A Quick Guide to Responsive Web Development Using Bootstrap 3 Writer The Dreams Our Stuff is Made Of: How Science Fiction conquered the WorldAdvance Praise ""What a treasure house is this book.
    [Show full text]
  • EMSCLOUD - an Evaluative Model of Cloud Services Cloud Service Management
    See discussions, stats, and author profiles for this publication at: https://www.researchgate.net/publication/277022271 EMSCLOUD - An evaluative model of cloud services cloud service management Conference Paper · May 2015 DOI: 10.1109/INTECH.2015.7173479 CITATION READS 1 146 2 authors, including: Mehran Misaghi Sociedade Educacional de Santa Catarina (… 56 PUBLICATIONS 14 CITATIONS SEE PROFILE All in-text references underlined in blue are linked to publications on ResearchGate, Available from: Mehran Misaghi letting you access and read them immediately. Retrieved on: 05 July 2016 Fifth international conference on Innovative Computing Technology (INTECH 2015) EMSCLOUD – An Evaluative Model of Cloud Services Cloud service management Leila Regina Techio Mehran Misaghi Post-Graduate Program in Production Engineering Post-Graduate Program in Production Engineering UNISOCIESC UNISOCIESC Joinville – SC, Brazil Joinville – SC, Brazil [email protected] [email protected] Abstract— Cloud computing is considered a paradigm both data repository. There are challenges to be overcome in technology and business. Its widespread adoption is an relation to internal and external risks related to information increasingly effective trend. However, the lack of quality metrics security area, such as virtualization, SLA (Service Level and audit of services offered in the cloud slows its use, and it Agreement), reliability, availability, privacy and integrity [2]. stimulates the increase in focused discussions with the adaptation of existing standards in management services for cloud services The benefits presented by cloud computing, such as offered. This article describes the EMSCloud, that is an Evaluative Model of Cloud Services following interoperability increased scalability, high performance, high availability and standards, risk management and audit of cloud IT services.
    [Show full text]
  • International Standard Iso 19600:2014(E)
    This preview is downloaded from www.sis.se. Buy the entire standard via https://www.sis.se/std-918326 INTERNATIONAL ISO STANDARD 19600 First edition 2014-12-15 Compliance management systems — Guidelines Systèmes de management de la conformité — Lignes directrices Reference number ISO 19600:2014(E) © ISO 2014 This preview is downloaded from www.sis.se. Buy the entire standard via https://www.sis.se/std-918326 ISO 19600:2014(E) COPYRIGHT PROTECTED DOCUMENT © ISO 2014 All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address below or ISO’s member body in the country of the requester. ISOTel. copyright+ 41 22 749 office 01 11 Case postale 56 • CH-1211 Geneva 20 FaxWeb + www.iso.org 41 22 749 09 47 E-mail [email protected] Published in Switzerland ii © ISO 2014 – All rights reserved This preview is downloaded from www.sis.se. Buy the entire standard via https://www.sis.se/std-918326 ISO 19600:2014(E) Contents Page Foreword ........................................................................................................................................................................................................................................iv Introduction ..................................................................................................................................................................................................................................v
    [Show full text]
  • Master Glossary
    Master Glossary Term Definition Course Appearances 12-Factor App Design A methodology for building modern, scalable, maintainable software-as-a-service Continuous Delivery applications. Architecture 2-Factor or 2-Step Two-Factor Authentication, also known as 2FA or TFA or Two-Step Authentication is DevSecOps Engineering Authentication when a user provides two authentication factors; usually firstly a password and then a second layer of verification such as a code texted to their device, shared secret, physical token or biometrics. A/B Testing Deploy different versions of an EUT to different customers and let the customer Continuous Delivery feedback determine which is best. Architecture A3 Problem Solving A structured problem-solving approach that uses a lean tool called the A3 DevOps Foundation Problem-Solving Report. The term "A3" represents the paper size historically used for the report (a size roughly equivalent to 11" x 17"). Acceptance of a The "A" in the Magic Equation that represents acceptance by stakeholders. DevOps Leader Solution Access Management Granting an authenticated identity access to an authorized resource (e.g., data, DevSecOps Engineering service, environment) based on defined criteria (e.g., a mapped role), while preventing an unauthorized identity access to a resource. Access Provisioning Access provisioning is the process of coordinating the creation of user accounts, e-mail DevSecOps Engineering authorizations in the form of rules and roles, and other tasks such as provisioning of physical resources associated with enabling new users to systems or environments. Administration Testing The purpose of the test is to determine if an End User Test (EUT) is able to process Continuous Delivery administration tasks as expected.
    [Show full text]
  • OWASP Top 10 - 2017 the Ten Most Critical Web Application Security Risks
    OWASP Top 10 - 2017 The Ten Most Critical Web Application Security Risks This work is licensed under a https://owasp.org Creative Commons Attribution-ShareAlike 4.0 International License 1 TOC Table of Contents Table of Contents About OWASP The Open Web Application Security Project (OWASP) is an TOC - About OWASP ……………………………… 1 open community dedicated to enabling organizations to FW - Foreword …………..………………...……… 2 develop, purchase, and maintain applications and APIs that can be trusted. I - Introduction ………..……………….……..… 3 At OWASP, you'll find free and open: RN - Release Notes …………..………….…..….. 4 • Application security tools and standards. Risk - Application Security Risks …………….…… 5 • Complete books on application security testing, secure code development, and secure code review. T10 - OWASP Top 10 Application Security • Presentations and videos. Risks – 2017 …………..……….....….…… 6 • Cheat sheets on many common topics. • Standard security controls and libraries. A1:2017 - Injection …….………..……………………… 7 • Local chapters worldwide. A2:2017 - Broken Authentication ……………………... 8 • Cutting edge research. • Extensive conferences worldwide. A3:2017 - Sensitive Data Exposure ………………….. 9 • Mailing lists. A4:2017 - XML External Entities (XXE) ……………... 10 Learn more at: https://www.owasp.org. A5:2017 - Broken Access Control ……………...…….. 11 All OWASP tools, documents, videos, presentations, and A6:2017 - Security Misconfiguration ………………….. 12 chapters are free and open to anyone interested in improving application security. A7:2017 - Cross-Site Scripting (XSS) ….…………….. 13 We advocate approaching application security as a people, A8:2017 - Insecure Deserialization …………………… 14 process, and technology problem, because the most A9:2017 - Using Components with Known effective approaches to application security require Vulnerabilities .……………………………… 15 improvements in these areas. A10:2017 - Insufficient Logging & Monitoring….…..….. 16 OWASP is a new kind of organization.
    [Show full text]
  • Recently Completed September October 2015
    Current Standards Activities Page 1 of 15 Browse By Group: View All New Publications | Supplements | Amendments | Errata | Endorsements | Reaffirmations | Withdrawals | Formal Interpretations | Informs & Certification Notices | Previous Reports Last updated: November 5, 2015 New Publications This section lists new standards, new editions (including adoptions), and special publications that have been recently published. Clicking on "View Detail" will display the scope of the document and other details available on CSA’s Online store. Program Standard Title Date Posted Scope Quality / Business Z710-15 Activités du Bureau du registre de la nation métisse 10/29/2015 View Detail Management Communications / CAN/CSA-ISO/IEC Identification cards - Test methods - Part 5: Optical memory cards 10/29/2015 View Detail Information 10373-5:15 (Adopted ISO/IEC 10373-5:2014, third edition, 2014-10-01) Communications / CAN/CSA-ISO/IEC Information technology - Programming languages, their 10/29/2015 View Detail Information 1989:15 environments and system software interfaces - Programming language COBOL (Adopted ISO/IEC 1989:2014, second edition, 2014-06-01) Communications / CAN/CSA-ISO/IEC Information technology - Magnetic stripes on savingsbooks 10/29/2015 View Detail Information 8484:15 (Adopted ISO/IEC 8484:2014, second edition, 2014-08-15) http://standardsactivities.csa.ca/standardsactivities/recent_infoupdate.asp 11/5/2015 Current Standards Activities Page 2 of 15 Electrical / Electronics C22.2 NO. 184.1-15 Solid-state dimming controls 10/22/2015 View Detail (Bi-national standard with UL 1472) Electrical / Electronics C22.2 NO. 295-15 Neutral grounding devices 10/22/2015 View Detail Electrical / Electronics C22.2 NO. 94.1-15 Enclosures for electrical equipment, non-environmental 10/22/2015 View Detail considerations (Tri-national standard with NMX-J-235/1-ANCE-2015 and UL 50) Electrical / Electronics C22.2 NO.
    [Show full text]
  • Strategic Change in Enterprise Risk Management
    Edinburgh Research Explorer Strategic change in enterprise risk management Citation for published version: Agarwal, R & Ansell, J 2016, 'Strategic change in enterprise risk management', Strategic Change, vol. 25, no. 4, pp. 427-439. https://doi.org/10.1002/jsc.2072 Digital Object Identifier (DOI): 10.1002/jsc.2072 Link: Link to publication record in Edinburgh Research Explorer Document Version: Peer reviewed version Published In: Strategic Change General rights Copyright for the publications made accessible via the Edinburgh Research Explorer is retained by the author(s) and / or other copyright owners and it is a condition of accessing these publications that users recognise and abide by the legal requirements associated with these rights. Take down policy The University of Edinburgh has made every reasonable effort to ensure that Edinburgh Research Explorer content complies with UK legislation. If you believe that the public display of this file breaches copyright please contact [email protected] providing details, and we will remove access to the work immediately and investigate your claim. Download date: 28. Sep. 2021 Strategic change in Enterprise Risk Management Strategic Change in Enterprise Risk Management Ruchi Agarwal and Jake Ansell1 University of Edinburgh Business School, UK Research Article This article is based on strategic change in theory and practice of Enterprise Risk Management and highlights four emerging risk strategies: ‘Rudimentary’, ‘Anticipatory’, ‘Resilience’ and ‘Transformation’ An empirical research has been carried out with over 50 CRO and senior management interviews in emerging and mature markets. The literature and practice of ERM strategies have been shown at different state of strategic change in developing and developed markets.
    [Show full text]
  • International Standard Iso 19600:2014(E)
    INTERNATIONAL ISO STANDARD 19600 First edition 2014-12-15 Compliance management systems — Guidelines Systèmes de management de la conformité — Lignes directrices Reference number ISO 19600:2014(E) --`,,,```,`,,,`,````,,``,,,,```-`-`,,`,,`,`,,`--- Copyright International Organization for Standardization © ISO 2014 Provided by IHS under license with ISO Licensee=University of Alberta/5966844001, User=gh, ramin No reproduction or networking permitted without license from IHS Not for Resale, 01/03/2015 08:41:27 MST ISO 19600:2014(E) COPYRIGHT PROTECTED DOCUMENT © ISO 2014 All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address below or ISO’s member body in the country of the requester. ISOTel. copyright+ 41 22 749 office 01 11 Case postale 56 • CH-1211 Geneva 20 FaxWeb + www.iso.org 41 22 749 09 47 E-mail [email protected] Published in Switzerland--`,,,```,`,,,`,````,,``,,,,```-`-`,,`,,`,`,,`--- Copyright Internationalii Organization for Standardization © ISO 2014 – All rights reserved Provided by IHS under license with ISO Licensee=University of Alberta/5966844001, User=gh, ramin No reproduction or networking permitted without license from IHS Not for Resale, 01/03/2015 08:41:27 MST ISO 19600:2014(E) Contents Page Foreword ........................................................................................................................................................................................................................................iv
    [Show full text]
  • Berntsen Mette.Pdf (1.974Mb)
    Summary In the oil and gas industry it has become a higher focus on risk and risk management the last years. It is higher expectation from stakeholders that organizations take full account for risks. It is important for Aibel as a leading service company and serious player in the industry to keep track and control of risk at all levels in the organization. Aibel has therefore established a risk management strategy for the company. In this thesis the objective is to discuss how to achieve good risk management. A review of the risk management in Aibel is performed along with a survey to map the employee’s knowledge and experience on the subject. Gaps between the present risk management and principles from ISO 31000 are identified. The risk management strategy is also compared to the PSA requirements to see if they comply. An evaluation and classification of the risk maturity level for the organization is done. This is based on a risk maturity model. The risk maturity level measures the current level of risk culture in an organization. In this case there are 4 defined levels, naïve, novice, normalized and natural. With natural as the highest achieved level. The overall impression made in this thesis is that many of the principles for achieving good risk management are implemented. Despite of this there have been revealed weaknesses and huge potentials for improvement. The findings are discussed and there are also suggested areas of improvements for the organization on how to achieve an even more effective risk management. There have been identified several benefits for improving the present risk management along with suggestions for further work.
    [Show full text]
  • Risk Management Software Utilization in the Singapore Construction
    KICEM Journal of Construction Engineering and Project Management (2011) www.jcepm.org Online ISSN 2233-9582 http://dx.doi.org/10.6106/JCEPM.2011.1.2.028 Risk Management Software Utilization in the Singapore Construction Industry: Evaluation and Improvement Bon-Gang Hwang1 and Pee Mee Chua2 Abstract: Risk management is popularly and widely used in various industries to handle uncertainty that can negatively affect their businesses. While in the current Information-Technology oriented age, software packages are designed to assist in carrying out risk management processes, the construction industry does not seem to have software that is tuned to its specific characteristics and processes. Therefore, this study first explores the types of software that are commonly used for risk management in the Singapore construction industry. Also, using one-sample t-test, it is tested if the software programs used in the construction industry have effectively catered the needs of the users. For the analysis, a survey questionnaire was developed and the representatives from 34 companies participated in the survey. Furthermore, this study also makes use of the current risk management framework defined in ISO31000 to design a risk management software algorithm that can suit the needs for the Singapore construction industry. The results from this study will contribute to identifying strategic areas, in terms of use of risk management software, on which the industry needs to focus, ultimately enhancing their performance of risk management. Keywords: Risk Management, Software, Construction Project, Project Management, Singapore I. INTRODUCTION improved. According to Roland (2008), with the aid of In today’s competitive and unpredictable technology, “companies can more easily incorporate risk circumstances, risk management is highly emphasized and management into critical business processes and improve utilized in businesses and projects in various industries.
    [Show full text]
  • Proposal for Implementation Risk Management According ABNT NBR ISO 31000 Standard Applied to Internal Audit Process of Integrated Management System of IPEN
    Proposal for implementation risk management according ABNT NBR ISO 31000 standard applied to internal audit process of Integrated Management System of IPEN Wilson S. Scapin Jr., Tereza C. Salvetti and Guilherme C. Longo Instituto de Pesquisas Energéticas e Nucleares (IPEN / CNEN - SP) Coordenadoria da Qualidade – Diretoria de Planejamento e Gestão Av. Professor Lineu Prestes 2242 05508-000 São Paulo, SP [email protected] Instituto de Pesquisas Energéticas e Nucleares (IPEN / CNEN - SP) Coordenadoria da Qualidade – Diretoria de Planejamento e Gestão Av. Professor Lineu Prestes 2242 05508-000 São Paulo, SP [email protected] Reator Multipropósito Brasileiro (RMB) Av. Professor Lineu Prestes 2242 05508-000 São Paulo, SP [email protected] ABSTRACT The paper objective is to establish a risk management methodology applied to internal audits processes of IPEN Integrated Management System (IMS). In continuous seeking of updating methodologies to assist effective management based on the constant changes in the organizational world, and the development of management tools used for decision making, risk management demonstrates trends to be a new tool with high efficiency. This trend is accentuated by the fact that risk management is being incorporated into the new revision of quality management standard ISO 9001, estimated conclusion in November 2015. The identification, evaluation and treatment of risks are present in eleven items of its ten requirements at new revision. From the conclusion of the review, all organizations certified by that standard should make the necessary changes in their systems to meet the new requirements. This proposal will provide anticipate the changes that will occur in the management system of IPEN in accordance with this new revision.
    [Show full text]