Service risk management method and device, electronic equipment and storage medium
The service risk management method using FMEA evaluates and mitigates risks in service processes, addressing the challenge of simultaneous production and consumption in services, thereby reducing failure risks and enhancing monitoring capabilities.
Patent Information
- Application Number
- CN202411067295.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-08-06
- Publication Date
- 2024-12-06
AI Technical Summary
Existing service management systems lack effective methods for pre-management of service risks, which can lead to significant remediation costs and failures due to the intangible nature of services, where production and consumption occur simultaneously.
A service risk management method using Failure Mode and Effects Analysis (FMEA) to evaluate risks based on risk source data, determining risk levels, and implementing mitigation measures for risks above a threshold, with dynamic re-evaluation and adjustment of mitigation strategies.
Enables proactive management of service risks, improving automatic monitoring capabilities and reducing the likelihood of service failures by identifying and addressing potential issues before they occur.
Smart Images

Figure CN119090258A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of artificial intelligence technology, and more specifically, to a service risk management method, a service risk management device, an electronic device, a computer-readable storage medium, and a computer program product. Background Art
[0002] Service can be understood as the delivery process of intangible products. The production and consumption of services are carried out simultaneously. Once a service occurs, the service recipient will have an evaluation of the quality of the service; if the service fails, it will take a very large remediation cost to recover the consequences of the service failure.
[0003] Therefore, there is an urgent need for a "pre-management" service risk management method to control the risks of the entire service process before the service occurs. While realizing dynamic management of service risks, it can also improve the automatic monitoring capabilities of the entire service process and reduce the risk of service failure. Summary of the invention
[0004] The present application provides a service risk management method, a service risk management device, an electronic device, a computer-readable storage medium, and a computer program product that can at least partially solve the above-mentioned problems or other problems.
[0005] On the one hand, the present application provides a service risk management method, the method comprising: determining risk source data in the process of the service; evaluating the risks in the process of the service based on failure mode and effect analysis and the risk source data, and determining the risk level based on the evaluation results; and implementing risk mitigation measures for risks whose risk levels are greater than a preset threshold, wherein the evaluation results include a risk detection degree, and the risk detection degree represents the difficulty of discovering the risk.
[0006] In one embodiment of the present application, the method further includes: based on the failure mode and effect analysis, re-evaluating the risk after implementing the risk mitigation measure, and determining the risk level of the risk after implementing the risk mitigation measure based on the re-evaluation result; and in response to the risk level of the risk after implementing the risk mitigation measure being less than the preset threshold, continuing to implement the risk mitigation measure.
[0007] In one embodiment of the present application, the method further includes: in response to the risk level of the risk after the risk mitigation measure is implemented being greater than or equal to the preset threshold, modifying the risk mitigation measure.
[0008] In one embodiment of the present application, the evaluation result also includes risk severity and risk occurrence, wherein the risk severity represents the severity of the risk after it occurs; and the risk occurrence represents the possibility of the risk occurring.
[0009] In one embodiment of the present application, the method also includes: decomposing the service into multiple service processes, and determining service departments related to the service processes, wherein the service departments include direct service departments and indirect service departments; the direct service departments include departments that have a direct relationship with the service object in the service process; and the indirect service departments include departments that have an indirect relationship with the service object in the service process.
[0010] In one embodiment of the present application, decomposing the service into a plurality of service processes and determining a service department related to the service process includes: utilizing a conceptual blueprint to decompose the service into a plurality of service processes; and the service department utilizing a detailed blueprint to compile details of the service process corresponding to the service department.
[0011] In one embodiment of the present application, the risk source data includes legal and regulatory data, industry requirement specification data, service process demand data and historical service process data, wherein the historical service process data includes external evaluation data of historical service processes given by the service objects and internal evaluation data of historical service processes given by the service departments related to the service processes.
[0012] In one embodiment of the present application, based on the failure mode and effect analysis and the risk source data, the risk in the service process is evaluated, including: determining the risk detection level based on the failure mode and effect analysis, the external evaluation data of the historical service process, the internal evaluation data of the historical service process, and the industry requirement specification data.
[0013] In one embodiment of the present application, the evaluation result also includes risk severity and risk occurrence, and determining the risk level based on the evaluation result includes: determining the risk level based on the risk detection level, the risk severity and the risk occurrence level.
[0014] In one embodiment of the present application, determining the risk level based on the evaluation result further includes: determining the risk level based on a weight of the risk detection degree, a weight of the risk severity degree, and a weight of the risk occurrence degree.
[0015] In one embodiment of the present application, the method also includes: using a subjective weight method or an objective weight method to determine at least one of the weight of the risk detection degree, the weight of the risk severity, and the weight of the risk occurrence degree, wherein the subjective weight method includes at least one of the direct evaluation method, the hierarchical analysis method, and the Delphi method; and the objective weight method includes at least one of the ordered weight operator method, the data envelopment method, and the minimum cut set method.
[0016] In one embodiment of the present application, based on the failure mode and effect analysis and the risk source data, the risk in the service process is evaluated, including: determining the detectability of the risk detection level based on the maturity of the risk detection method and at least one of the risk detection opportunities; and determining the risk detection level based on the detectability of the risk detection level.
[0017] In one embodiment of the present application, based on the failure mode and effect analysis and the risk source data, the risk evaluation in the service process also includes: determining the possibility of the risk occurrence based on at least one of the qualitative analysis and the quantitative analysis of the risk occurrence; and determining the risk occurrence based on the possibility of the risk occurrence.
[0018] In one embodiment of the present application, the evaluation result also includes risk severity. Based on the failure mode and effect analysis and the risk source data, the risk evaluation in the service process also includes: determining the risk severity determination criteria based on the external evaluation data of the historical service process given by the service object, the loss or compensation corresponding to the historical service process, and at least one of the negative impacts corresponding to the historical service process; and determining the risk severity based on the risk severity determination criteria.
[0019] On the other hand, the present application provides a service risk management device, which includes: a risk source analysis module, configured to determine risk source data in the service process; a risk level determination module, configured to evaluate the risks in the service process based on failure mode and effect analysis and the risk source data, and determine the risk level based on the evaluation result; a judgment module, configured to implement risk mitigation measures for risks whose risk level is greater than a preset threshold, wherein the evaluation result includes a risk detection degree, and the risk detection degree represents the difficulty of discovering the risk.
[0020] In one embodiment of the present application, the risk level determination module is further configured to re-evaluate the risk after the implementation of the risk mitigation measure based on the failure mode and effect analysis, and determine the risk level of the risk after the implementation of the risk mitigation measure based on the re-evaluation result; and the judgment module is further configured to continue implementing the risk mitigation measure in response to the risk level of the risk after the implementation of the risk mitigation measure being less than the preset threshold.
[0021] In one embodiment of the present application, the judgment module is further configured to modify the risk mitigation measure in response to the risk level of the risk after the risk mitigation measure is implemented being greater than or equal to the preset threshold.
[0022] In one embodiment of the present application, the evaluation result also includes risk severity and risk occurrence, wherein the risk severity represents the severity of the risk after it occurs; and the risk occurrence represents the possibility of the risk occurring.
[0023] In one embodiment of the present application, the risk source analysis module is further configured to decompose the service into multiple service processes and determine the service departments related to the service processes, wherein the service departments include direct service departments and indirect service departments; the direct service departments include departments that have a direct relationship with the service object in the service process; and the indirect service departments include departments that have an indirect relationship with the service object in the service process.
[0024] In one embodiment of the present application, the risk source analysis module is further configured to use a conceptual blueprint to decompose the service into multiple service processes; and the service department uses a detail blueprint to compile details of the service process corresponding to the service department.
[0025] In one embodiment of the present application, the risk source data includes legal and regulatory data, industry requirement specification data, service process demand data and historical service process data, wherein the historical service process data includes external evaluation data of historical service processes given by the service objects and internal evaluation data of historical service processes given by the service departments related to the service processes.
[0026] In one embodiment of the present application, the risk level determination module is further configured to determine the risk detection degree based on the failure mode and effect analysis, the external evaluation data of the historical service process, the internal evaluation data of the historical service process, and the industry requirement specification data.
[0027] In one embodiment of the present application, the evaluation result also includes risk severity and risk occurrence, and the risk level determination module is further configured to determine the risk level based on the evaluation result, including: determining the risk level based on the risk detection level, the risk severity and the risk occurrence level.
[0028] In one embodiment of the present application, the risk level determination module is further configured to determine the risk level based on the weight of the risk detection degree, the weight of the risk severity degree, and the weight of the risk occurrence degree.
[0029] In one embodiment of the present application, the risk level determination module is further configured to use a subjective weight method or an objective weight method to determine at least one of the weight of the risk detection degree, the weight of the risk severity, and the weight of the risk occurrence degree, wherein the subjective weight method includes at least one of the direct evaluation method, the hierarchical analysis method, and the Delphi method; and the objective weight method includes at least one of the ordered weight operator method, the data envelopment method, and the minimum cut set method.
[0030] In one embodiment of the present application, the risk level determination module is further configured to determine the detectability of the risk detectability based on the maturity of the risk detection method and at least one of the detection opportunities for the risk; and determine the risk detection level based on the detectability of the risk detection level.
[0031] In one embodiment of the present application, the risk level determination module is further configured to evaluate the risk in the service process based on the failure mode and effect analysis and the risk source data, and also includes: determining the possibility degree of the risk occurrence based on at least one of the qualitative analysis and the quantitative analysis of the risk occurrence degree; and determining the risk occurrence degree based on the possibility degree of the risk occurrence degree.
[0032] In one embodiment of the present application, the risk level determination module is further configured to determine the risk severity determination criteria based on the external evaluation data of the historical service process given by the service object, the loss or compensation corresponding to the historical service process, and at least one of the negative impacts corresponding to the historical service process; and determine the risk severity based on the risk severity determination criteria.
[0033] On the other hand, the present application provides an electronic device, which includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the service risk management method provided in any embodiment of the first aspect of the present application.
[0034] On the other hand, the present application provides a computer-readable storage medium storing a computer program, characterized in that when the computer program is executed by a processor, it implements the service risk management method provided in any implementation method in one aspect of the present application.
[0035] On the other hand, the present application provides a computer program product storing a computer program, characterized in that when the computer program is executed by a processor, it implements the service risk management method provided in any implementation method in one aspect of the present application.
[0036] According to the service risk management method, service risk management method device, electronic device, computer-readable storage medium and computer program product provided in at least one embodiment of the present application, the risk of the entire service process is evaluated by using the service risk source data and FMEA (Failure Mode and Effects Analysis) in the entire service process before the service occurs. The evaluation result includes a risk detection degree that characterizes the difficulty of discovering the risk, and based on the risk level determined by the evaluation result being greater than a preset threshold, risk mitigation measures are implemented for the risk. The risk of the entire service process can be managed before the service occurs, and risk mitigation measures can be performed on the service process with higher risks, thereby realizing dynamic management of service risks, improving the automatic monitoring capability of the entire service process, and reducing the risk of service failure. BRIEF DESCRIPTION OF THE DRAWINGS
[0037] Other features, objects and advantages of the present application will become more apparent by reading the detailed description of non-limiting embodiments made with reference to the following drawings, in which:
[0038] Figure 1 is a flow chart of a service risk management method according to one embodiment of the present application;
[0039] Figure 2 is a working process diagram of a service risk management method according to an implementation method of the present application;
[0040] Figure 3 is an example table of risk detection level determination criteria according to one embodiment of the present application;
[0041] Figure 4 is an example table of risk severity determination criteria according to one embodiment of the present application;
[0042] Figure 5 This is an example table of risk occurrence determination criteria according to one embodiment of the present application;
[0043] Figure 6This is an example table of risk level determination criteria in a service process according to an implementation method of the present application;
[0044] Figure 7 This is an example diagram of the FMEA of the check-in process according to an implementation method of the present application;
[0045] Figure 8 is a schematic diagram of a framework of a service risk management device according to an embodiment of the present application; and
[0046] Fig. 9 It is a structural diagram of a computer system suitable for implementing an electronic device according to an embodiment of the present application. DETAILED DESCRIPTION
[0047] In order to better understand the present application, a more detailed description will be made of various aspects of the present application with reference to the accompanying drawings. It should be understood that these detailed descriptions are only descriptions of exemplary embodiments of the present application, and are not intended to limit the scope of the present application in any way. Throughout the specification, the same reference numerals refer to the same elements. The expression "and / or" includes any and all combinations of one or more of the associated listed items.
[0048] It should be noted that in this specification, the expressions first, second, third, etc. are only used to distinguish one feature from another feature area, and do not represent any limitation on the features, especially do not represent any order of precedence. Therefore, without departing from the teaching of this application, the first process discussed in this application can also be referred to as the second process, and vice versa.
[0049] As used herein, the terms "substantially," "approximately," and similar terms are used as terms of approximation, not degree, and are intended to account for the inherent variations in measurements or calculations that would be recognized by those of ordinary skill in the art.
[0050] It should also be understood that expressions such as "include", "including", "have", "contain" and / or "comprising" are open rather than closed expressions in this specification, which indicate the presence of the stated features, elements and / or components, but do not exclude the presence of one or more other features, elements, components and / or combinations thereof. In addition, when expressions such as "at least one of..." appear after a list of listed features, they modify the entire list of features rather than just the individual elements in the list. In addition, when describing embodiments of the present application, "may" is used to mean "one or more embodiments of the present application". And, the term "exemplary" is intended to refer to an example or illustration.
[0051] Unless otherwise specified, all words (including engineering terms and scientific and technological terms) used in this article have the same meaning as those commonly understood by ordinary technicians in the field to which this application belongs. It should also be understood that, unless clearly stated in this application, words defined in common dictionaries should be interpreted as having the same meaning as their meaning in the context of the relevant technology, and should not be interpreted in an idealized or overly formal sense.
[0052] It should be noted that, in the absence of conflict, the embodiments and features in the embodiments of the present application can be combined with each other. In addition, unless explicitly limited or contradictory to the context, the specific steps included in the method described in the present application are not necessarily limited to the order described, but can be performed in any order or in parallel. The present application will be described in detail below with reference to the accompanying drawings and in conjunction with the embodiments.
[0053] In addition, in the present application, when “connected” or “coupled” is used, it may indicate direct contact or indirect contact between corresponding components, unless otherwise clearly defined or inferred from the context.
[0054] Figure 1 FIG. 1 is a flow chart of a service risk management method 1000 according to an embodiment of the present application. Figure 1 As shown, the present application provides a service risk management method 1000 including:
[0055] S1, determine the risk source data in the service process.
[0056] S2, based on failure mode and effect analysis and risk source data, evaluates the risks in the service process and determines the risk level based on the evaluation results, where the evaluation results include the risk detection degree that characterizes the difficulty of risk discovery.
[0057] S3: Implement risk mitigation measures for risks whose risk levels are greater than the preset threshold.
[0058] The following will be combined Figures 2 to 7 The specific steps of the above service risk management method 1000 are described in detail.
[0059] Step S1
[0060] Figure 2 It is a working process diagram of a service risk management method 1000 according to one embodiment of the present application.
[0061] like Figure 1 and Figure 2As shown, in some embodiments of the present application, step S1 of determining the risk source data in the service process may, for example, include: decomposing the service into multiple service processes, and determining the service departments related to the service processes, wherein the service departments include direct service departments and indirect service departments, the direct service departments include the departments that have a direct relationship with the service objects in the service process, and the indirect service departments include the departments that have an indirect relationship with the service objects in the service process.
[0062] In addition, in some embodiments of the present application, step S1 of determining the risk source data in the service process may also include, for example: collecting the risk source data belonging to each service process from multiple dimensions or channels.
[0063] Specifically, take the service provided by civil aviation to passengers that allows them to quickly reach their destination as an example. Civil aviation is a typical service, which is the delivery process of an intangible product, and the production and consumption of services are carried out simultaneously. Once the service occurs, the service recipients will have an evaluation of the quality of the service; if the service fails, it will take a very large remediation cost to recover the consequences of the service failure.
[0064] In addition, unlike other services, civil aviation transport services involve many service departments in the entire service process due to their long chain, high technical requirements and changing operating environment. These service departments may include airlines, ticket agents, airport management agencies, ground agents and other departments that have direct relationships with the service recipients in the service process. In addition, service departments may also include information, maintenance, and other departments that have indirect relationships with the service recipients in the service process.
[0065] The operation of such a huge service system is highly uncertain. Any problem in any link may bring risks to service quality and even induce unsafe incidents. Reasons such as unprofessional communication, inappropriate service standards, and inadequate maintenance may be important reasons for passenger (understood as the service recipient) complaints, passenger property losses, personal injuries, etc.
[0066] Therefore, according to the service risk management method provided by at least one embodiment of the present application, the risk of the entire service process can be evaluated by using the service risk source data and FMEA in the entire service process before the service occurs, wherein the evaluation result includes the risk detection degree that characterizes the difficulty of risk discovery, and the risk level determined based on the evaluation result is greater than the preset threshold, and risk mitigation measures are implemented for the risk. Therefore, before the service occurs, the risk of the entire service process is managed and controlled, and the risk mitigation is performed on the service process with higher risks, which can realize the dynamic management of service risks, improve the automatic monitoring capability of the entire service process, and reduce the risk of service failure.
[0067] A service blueprint is a graphic tool that converts service processes and ideas into service flows in a direct and clear form. From a functional perspective, a service blueprint can include a conceptual blueprint and a detailed blueprint. The conceptual blueprint can describe the service as a whole, while the detailed blueprint can provide a detailed description of specific departments in the service.
[0068] Therefore, as an option, the service can be decomposed into multiple service processes using the conceptual blueprint. In addition, the service department can also use the detailed blueprint to compile the details of the service process corresponding to the service department.
[0069] Taking civil aviation transport services as an example, the concept blueprint can sort out the service process from a macro perspective and decompose the service into multiple service processes, such as the first process, the second process, etc. Using the concept blueprint to decompose the service can enable different personnel involved in the service process, such as personnel belonging to different service departments, to understand and become familiar with the entire process distribution of the service in an interactive and visible way, thereby reducing the difficulty of work caused by the intangible nature of the service product.
[0070] In addition, the service department can also use the detailed blueprint to compile the details of the service process corresponding to the service department. The drawing of the detailed blueprint is particularly important. Drawing the details of the service process can more clearly understand the service process and facilitate a more comprehensive identification of risks that may arise in the service process.
[0071] It should be noted that the service department related to the service process may include the process department that actually performs the service. In addition, the service department related to the service process may also include other cross-functional related departments and expert teams related to the service process, etc., and this application does not limit this.
[0072] After decomposing the services and obtaining the processes of multiple services, the risk source data of each service process can be collected. For example, the risk source data of each service process can be collected from multiple dimensions or channels. Taking civil aviation transportation services as an example, the risk source data of each service process can be fully identified from multiple dimensions such as people, machines, objects, and laws.
[0073] As an option, the risk source data in the service process may include legal and regulatory data, industry requirements and specifications data, service process demand data, and historical service process data, among which the historical service process data may include external evaluation data of historical service processes given by service recipients and internal evaluation data of historical service processes given by service departments related to the service process. Taking civil aviation transport services as an example, external evaluation data may include complaints and complaints from previous passengers, customer satisfaction evaluations, etc., and internal evaluation data may include feedback from service department staff, inspection reports on services conducted by cross-departments, etc.
[0074] Optionally, the service risk management method provided by at least one embodiment of the present application may consider the following service quality risk sources: risk sources that cause various problems in service products, risk sources that cause service quality to decline, risk sources that trigger complaints from service recipients, risk sources that affect the corporate brand image, and any risk sources that may cause service quality failure during the service process, etc.
[0075] Therefore, in the service risk management method provided in at least one embodiment of the present application, historical service process data representing process facts and actual situations can be used, and legal and regulatory data related to the service or service process, industry requirement specification data, service process demand data, etc. can also be used to evaluate the risks in each process of the service, so as to comprehensively identify and confirm the risk situations that may arise in the entire process of the service.
[0076] Taking civil aviation transport services as an example, the risk source data in the service process may include: complaints and complaints from previous passengers, external data such as customer satisfaction evaluation, feedback from service department staff, internal data of cross-department inspections of services, legal and regulatory data, industry requirements and specifications data, customer needs, etc. In addition, a risk source database may be established, so that in the subsequent steps of the service risk management method 1000, the regularity of event occurrence can be judged by data-driven, and the risk sources and consequences in the service process can be systematically identified.
[0077] Step S2
[0078] Figure 3 This is an example table of risk detection level determination criteria according to one embodiment of the present application. Figure 4 This is an example table of risk severity determination criteria according to one implementation of the present application. Figure 5 This is an example table of risk occurrence determination criteria according to one embodiment of the present application.
[0079] Step S2 evaluates the risks in the service process based on the failure mode and effect analysis and risk source data, and determines the risk level based on the evaluation results, wherein the evaluation results include a degree of difficulty in characterizing the risk being discovered. The risk detection (Detection, hereinafter referred to as D) may include: confirming the risk failure modes that may occur in the process of each service; analyzing each risk failure mode to determine the risk factors for the occurrence of each failure mode, wherein the risk factors include the risk detection level; evaluating the risks in the service process; and determining the risk level based on the evaluation results.
[0080] Specifically, the key to the service risk management method 1000 is to perform failure mode analysis and evaluate the risks in the service process. In the process of using FMEA to manage the risk of services, the related art usually does not consider the risk detection degree. This is because the related art believes that there is an essential difference between service products and physical products. Service products have the characteristics of synchronization, and their production and consumption are carried out simultaneously. Therefore, the risk detection degree is not suitable for the method of risk management of services.
[0081] However, the service risk management method 1000 provided in the embodiment of the present application evaluates the risk using the risk detection degree that characterizes the ease with which the risk is discovered, and determines the risk level using the evaluation result including the risk detection degree result.
[0082] As an option, the risk detection level of the service can be determined based on FMEA, external evaluation data of historical service processes, internal evaluation data of historical service processes, and industry requirement and specification data.
[0083] Taking civil aviation transport services as an example, the determination of risk detection can be considered at least from the external evaluation data of historical service processes. For example, a part of the data can be obtained from passenger satisfaction to determine the risk detection. It is true that passenger satisfaction can only be used as a dimension for risk source identification, and the risk level cannot be considered only from the dimension of passenger satisfaction. However, considering that the relationship between satisfaction and risk level is not an equal relationship, but an inclusive relationship, the service risk management method 1000 provided in the embodiment of the present application can obtain a part of the data from passenger dissatisfaction to determine the risk detection level.
[0084] In addition, service is a process provided to customers, which may include service facilities, service staff skills, service attitude and other aspects, so service satisfaction indicators can also be converted into internal control indicators. For example, whether the light in the terminal building is comfortable can be converted into whether the lighting control standards in the building are qualified. Therefore, the determination of risk detection can also be considered from at least the internal evaluation data of historical service processes, industry requirements and norms data and other aspects.
[0085] refer to Figure 3As an option, the detectability of the risk detection level may be determined based on at least one of the maturity of the risk detection method and the detection opportunity of the risk; and the risk detection level may be determined based on the detectability.
[0086] For example, taking civil aviation transport services as an example, if the service risk detection method has been verified in practice and can always detect failure modes or causes of failure, then the maturity of the service risk detection method can be considered to be very high. If the service product or service process will not have a failure mode, for example, the design review of the service product and the service management review confirm that error-proofing measures can be implemented or that failure modes will not occur. Then it can be considered that the chance of detecting the service risk is very high. Optionally, in at least one of the cases where the maturity of the service risk detection method is very high and the chance of detecting the service risk is very high, the detectability of the service risk detection can be considered to be very high. In this case, based on the very high detectability, the risk detection level in the service process can be set to "1".
[0087] For example, if a detection method for service risk has not been established, or there is no known test or inspection method, or the test (or inspection) method cannot detect the failure mode, then the maturity of the detection method for service risk can be considered to be very low. If the failure mode cannot or cannot be detected; or it is difficult to detect the failure mode through random or irregular audits, then the chance of detecting the service risk can be considered to be very low. Optionally, in at least one of the cases where the maturity of the detection method for service risk is very low and the chance of detecting the service risk is very low, the detectability of the service risk detection can be considered to be very low. In this case, the risk detection level in the service process can be set to "5" based on the very low detectability.
[0088] like Figure 1-Figure 5 As shown, in some embodiments of the present application, the evaluation results also include risk severity (Severity, hereinafter referred to as S) and risk occurrence (Occurrence, hereinafter referred to as O), where risk severity can characterize the severity of the risk after it occurs, and risk occurrence can characterize the possibility of the risk occurring.
[0089] Therefore, optionally, step S2 evaluates the risks in the service process based on the failure mode and effect analysis and risk source data, and determines the risk level based on the evaluation results, wherein the evaluation results include the degree of difficulty of characterizing the risk being discovered. The risk detection level may include determining the service risk level based on the risk detection level, risk severity, and risk occurrence level. This can simplify the process of determining the risk level, so as to facilitate real-time dynamic risk management.
[0090] In other words, step S2 may include: confirming the risk failure modes that may occur in the process of each service; analyzing each risk failure mode to determine the risk factors for the occurrence of each failure mode, where the risk factors include risk detection, risk severity and risk occurrence; evaluating the risks in the service process; and determining the risk level based on the evaluation results.
[0091] In addition, in order to improve the accuracy and precision of the service risk management method 1000, the service risk level can also be determined based on the risk detection degree, risk severity, risk occurrence degree, and the weight of the risk detection degree, the weight of the risk severity, and the weight of the risk occurrence degree.
[0092] As an option, a subjective weight method or an objective weight method can be used to determine at least one of the weights of risk detection, risk severity, and risk occurrence, wherein the subjective weight method may include at least one of the direct evaluation method, the analytic hierarchy process, and the Delphi method, and the objective weight method may include at least one of the ordered weight operator method, the data envelopment method, and the minimum cut set method.
[0093] Specifically, refer to Figure 4 As an option, the criteria for determining the severity of service risk can be determined based on the external evaluation data of the historical service process given by the service object, the loss or compensation corresponding to the historical service process, and at least one of the negative impacts corresponding to the historical service process; and the severity of service risk can be determined based on the criteria for determining the severity of service risk.
[0094] For example, taking civil aviation transport services as an example, if the service causes complaints from individual customers through on-site communication and satisfaction surveys, then the level of external evaluation data on the historical service process can be considered to be minor; if the amount of loss or compensation corresponding to the historical service process is less than 1,000 yuan, then the level of loss or compensation corresponding to the historical service process can be considered to be minor; if the negative impact corresponding to the historical service process is extremely small or has no impact, then the level of negative impact corresponding to the historical service process can be considered to be minor. Optionally, in the case of at least one of the level of external evaluation data on the historical service process being minor, the level of loss or compensation corresponding to the historical service process being minor, and the level of negative impact corresponding to the historical service process being minor, the level of risk severity of the service can be considered to be minor. In this case, the risk severity in the service process can be set to "1" based on the "minor" level of service risk severity.
[0095] For example, if the service causes the death of a customer or the customer files a petition or reports the passenger's opinions through the central government channel, then the level of the external evaluation data of the historical service process can be considered to be extremely serious; if the amount of loss or compensation corresponding to the historical service process is 50,000 yuan or less, then the level of loss or compensation corresponding to the historical service process can be considered to be extremely serious; if the negative impact corresponding to the historical service process is to attract media attention and reports, causing national or foreign media attention, or attracting the attention of national leaders, then the level of the negative impact corresponding to the historical service process can be considered to be extremely serious. Optionally, in the case where the level of the external evaluation data of the historical service process is extremely serious, the level of loss or compensation corresponding to the historical service process is extremely serious, and the level of the negative impact corresponding to the historical service process is extremely serious, at least one of the following, the level of the service risk severity can be considered to be extremely serious. In this case, based on the "extremely serious" level of the service risk severity, the risk severity in the service process can be set to "5".
[0096] refer to Figure 5 As an option, the likelihood of the risk occurrence can be determined based on at least one of a qualitative analysis and a quantitative analysis of the risk occurrence; and the risk occurrence can be determined based on the likelihood of the risk occurrence.
[0097] For example, taking civil aviation transport services as an example, if a qualitative analysis finds that the risk in the process of the service has not occurred within 5 years, then the qualitative analysis result of the risk occurrence can be considered to be extremely unlikely. If a quantitative analysis finds that the risk in the process of the service is foreseeable and basically will not occur, then the quantitative analysis result of the risk occurrence can be considered to be extremely unlikely. Optionally, in the case where the qualitative analysis result of the risk occurrence is extremely unlikely and the quantitative analysis result of the risk occurrence is extremely unlikely, the degree of possibility of the risk occurrence can be considered to be extremely unlikely. In this case, the degree of risk occurrence in the service process can be set to "1" based on the degree of possibility of "extremely unlikely".
[0098] For example, if the qualitative analysis finds that the risk in the service process occurs more than once a week, then the qualitative analysis result of the risk occurrence can be considered as frequent. If the quantitative analysis finds that the risk in the service process is foreseeable and will occur soon, then the quantitative analysis result of the risk occurrence can be considered as frequent. Optionally, in the case where at least one of the qualitative analysis result of the risk occurrence is frequent and the quantitative analysis result of the risk occurrence is frequent, the probability degree of the risk occurrence can be considered as frequent. In this case, the risk occurrence degree in the service process can be set to "5" based on the probability degree of "frequent".
[0099] After determining the levels of risk detection, risk severity and risk occurrence for the risk situation in the service process, the service risk level can be determined based on the risk detection, risk severity and risk occurrence.
[0100] Optionally, the FMEA method can use the risk factor RPN to judge the risk level. The risk factor RPN is shown in formula (1):
[0101] RPN i =S i ×O i ×D i (1)
[0102] Among them, RPN i Characterizes the risk factor in the current service process; S i Characterize the level of risk severity in the current service process; i Characterize the level of risk occurrence in the current service process; and D i Characterizes the level of risk detection in the current service process.
[0103] Figure 6 This is an example table of risk level determination criteria in a service process according to one implementation of the present application.
[0104] As an option, Figure 2-Figure 6 As shown, the risk level in the service process can be mainly defined from the aspects of compliance with legal and regulatory requirements, service policies, service quality goals, and the general acceptance of service recipients. Optionally, the risk level in the service process can include: first-level service risk, second-level service risk, and third-level service risk, and the risk acceptability corresponds to acceptable, acceptable to a certain extent, and unacceptable, respectively.
[0105] For example, the risk coefficient RPN of the first-level service risk is 1 point ≤ RPN < 30 points, which represents an acceptability level of "acceptable" and can be used for a "green" warning, where the critical values of the risk coefficient of the risk coefficient RPN of the first-level service risk are 1 and 30; the risk coefficient RPN of the second-level service risk is 30 points ≤ RPN < 40 points, which represents an acceptability level of "acceptable to a certain extent" and can be used for a "yellow" warning, where the critical values of the risk coefficient of the risk coefficient RPN of the second-level service risk are 30 and 40; and the risk coefficient RPN of the third-level service risk is 40 points ≤ RPN, which represents an acceptability level of "unacceptable" and can be used for a "red" warning, where the critical value of the risk coefficient of the risk coefficient RPN of the third-level service risk is 40.
[0106] Therefore, the FMEA method uses the risk coefficient RPN to judge the risk level. The RPN value can be the product of risk detection, risk severity and risk occurrence. RPN indicates the level of risk caused by the failure mode. The higher the risk coefficient, the higher the risk in the current service process. The FMEA method has the advantages of simple calculation, easy understanding and easy operation. It can simplify the process of determining risk levels and facilitate real-time and accurate dynamic risk management.
[0107] Step S3
[0108] Reference again Figure 1 and Figure 2 In some embodiments of the present application, step S3 of implementing risk mitigation measures for risks whose risk levels are greater than a preset threshold may, for example, include: formulating risk mitigation measures based on higher values among risk detection, risk severity, and risk occurrence; and implementing risk mitigation measures in the service process to reduce at least one of the risk detection, risk severity, and risk occurrence in the service process.
[0109] Optionally, the preset threshold may be defined based on legal and regulatory requirements, service policies, service quality objectives, and the general acceptance level of the service recipients.
[0110] In addition, in some embodiments of the present application, the risks in the service process after the implementation of the risk mitigation measures can be re-evaluated, and the risk level of the risks in the service process after the implementation of the risk mitigation measures can be determined based on the re-evaluation results. In response to the risk level of the risks in the service process after the implementation of the risk mitigation measures being less than a preset threshold, the risk mitigation measures can continue to be implemented in the service process.
[0111] In addition, in some embodiments of the present application, the risks in the service process after the implementation of the risk mitigation measures can be re-evaluated, and the risk level of the risks in the service process after the implementation of the risk mitigation measures can be determined based on the re-evaluation results. In response to the risk level of the risks in the service process after the implementation of the risk mitigation measures being greater than or equal to a preset threshold, the implementation of the risk mitigation measures in the service process can be modified to reduce at least one of the risk detection, risk severity, and risk occurrence in the service process.
[0112] Figure 7 This is an example diagram of FMEA of the check-in process according to an implementation method of the present application.
[0113] like Figure 7 As shown, taking the FMEA application example of the passenger check-in process of a southern airport as an example, each specific step of the service risk management method 1000 is described in detail.
[0114] In this embodiment, two failure modes are selected for analysis to illustrate how to evaluate the risks in the service process based on FMEA and risk source data, determine the risk level based on the evaluation results, and implement risk mitigation measures for risks with risk levels greater than a preset threshold.
[0115] exist Figure 7 In the table shown, for the check-in queue process, the risks in the service process (which can also be understood as failure modes) include: passengers queue for a long time, delaying passengers' time and causing passengers to be impatient. A potential cause of the risk in the service process is that the flow of people is concentrated and not dispersed. The current preventive measure is to set up boundary points in the queue. The risk detection method includes: mobile personnel patrol and inspect, and determine whether to add check-in counters or guide passengers to other counters according to the situation. According to the risk coefficient RPN shown in formula (1), the current risk coefficient RPN if It can be expressed as:
[0116] RPN if =S if ×O if ×D if =3×4×4=48 (2)
[0117] Among them, failure mode i can represent long queuing time; S if It can represent the delay of passengers' time, causing passengers to be impatient, and passengers complain to the Civil Aviation Administration, so S if Possible values: 3; O if It can characterize the current preventive measures, including: queuing and setting up warning points; frequency of occurrence, frequent occurrence, O if Possible value: 4; D if Can characterize detection methods, such as visual inspection by mobile personnel, D if The possible value is 4.
[0118] according to Figure 6 and Figure 7 , risk factor RPN if 48 is greater than the critical value of 40 for the risk factor of the second-level service risk. This risk level belongs to the third-level service risk, which is an unacceptable risk and requires risk mitigation measures. The risk mitigation measures formulated may include at least one of increasing electronic system monitoring, counting the number of people in line, and warning passengers of the queuing time. In addition, if an early warning occurs, the service system can alert the alarm, and the staff of the service process can open additional check-in counters or divert passengers to other counters. After implementing the risk mitigation measures, the risk factor RPN is calculated. ib :
[0119] RPN ib =S ib ×O ib ×D ib=2×3×3=18 (3)
[0120] Among them, S ib It can represent that the equipment has effectively warned, the delay time for passengers has been shortened, and some passengers have complained to the airport. ib Possible values: 2; O ib Can characterize electronic system monitoring, statistics and early warning; Occurrence frequency Occasionally, O ib Possible value: 3; D ib It can characterize electronic system monitoring, statistics and early warning, which belongs to semi-automatic monitoring, D ib The possible value is 3.
[0121] according to Figure 6 and Figure 7 After the implementation of risk mitigation measures, the risk coefficient of 18 is less than the critical value of 30 of the risk coefficient of the first-level service risk. The risk level is reduced to the first-level service risk, which is an acceptable risk. Therefore, before the service occurs, the service risk source data and FMEA in the whole process of the service are used to evaluate the risk of the whole process of the service. The evaluation results include the risk detection degree that characterizes the difficulty of risk discovery. Based on the risk level determined by the evaluation results being greater than the preset threshold, risk mitigation measures are implemented for the risk. Before the service occurs, the risk of the whole process of the service can be managed and controlled, and the risk of the service process with higher risk can be mitigated, thereby realizing the dynamic management of service risks, improving the automatic monitoring capability of the whole process of the service, and reducing the risk of service failure.
[0122] Figure 8 It is a schematic diagram of the framework of a service risk management device 2000 according to an implementation mode of the present application.
[0123] like Figure 8 As shown, another aspect of the present application also provides a service risk management device 2000. The service risk management device 2000 includes: a risk source analysis module 100, a risk level determination module 200, and a judgment module 300. The risk source analysis module 100 is configured to determine the risk source data in the service process. The risk level determination module 200 is configured to evaluate the risks in the service process based on failure mode and effect analysis and risk source data, and determine the risk level based on the evaluation results, wherein the evaluation results include risk detection, and the risk detection represents the difficulty of the risk being discovered. The judgment module 300 is configured to determine the association rules between topic keywords and complaint problem classification labels. The improvement module 400 is configured to implement risk mitigation measures for risks whose risk levels are greater than a preset threshold.
[0124] Therefore, according to the service risk management device provided by at least one embodiment of the present application, before the service occurs, the service risk source data and FMEA in the entire service process are used to evaluate the risks of the entire service process. The evaluation results include a risk detection degree that characterizes the difficulty of discovering the risk, and based on the risk level determined by the evaluation result being greater than a preset threshold, risk mitigation measures are implemented for the risk. Before the service occurs, the risk of the entire service process can be managed and controlled, and risk mitigation can be performed on the service processes with higher risks, thereby realizing dynamic management of service risks, improving the automatic monitoring capabilities of the entire service process, and reducing the risk of service failure.
[0125] Specifically, in one embodiment of the present application, the risk level determination module 200 is further configured to re-evaluate the risk after the risk mitigation measures are implemented based on FMEA, and determine the risk level of the risk after the risk mitigation measures are implemented based on the re-evaluation results. The judgment module 300 is further configured to continue to implement the risk mitigation measures in response to the risk level of the risk after the risk mitigation measures are implemented being less than a preset threshold.
[0126] In addition, the judgment module 300 is further configured to modify the risk mitigation measure in response to the risk level of the risk after the risk mitigation measure is implemented being greater than or equal to a preset threshold.
[0127] Optionally, the evaluation result also includes risk severity and risk occurrence, wherein risk severity represents the severity of the risk after it occurs; and risk occurrence represents the possibility of the risk occurring.
[0128] In one embodiment of the present application, the risk source analysis module 100 is further configured to decompose the service into multiple service processes and determine the service departments related to the service processes, wherein the service departments include direct service departments and indirect service departments; direct service departments include departments that have a direct relationship with the service object in the service process; and indirect service departments include departments that have an indirect relationship with the service object in the service process.
[0129] It should be noted that the service department related to the service process may include the process department that actually performs the service. In addition, the service department related to the service process may also include other cross-functional related departments and expert teams related to the service process, etc., and this application does not limit this.
[0130] In addition, the risk source analysis module 100 is further configured to use the concept blueprint to decompose the service into multiple service processes; and the service department uses the detail blueprint to compile the details of the service process corresponding to the service department. Decomposing the service using the concept blueprint allows different personnel involved in the service process, such as personnel belonging to different service departments, to understand and become familiar with the entire process distribution of the service in an interactive and visible manner, thereby reducing the difficulty of work caused by the intangibility of the service product. In addition, the drawing of the detail blueprint is particularly important. Drawing the details of the service process can more clearly understand the process of the service, which is convenient for more comprehensive identification of risks that may occur in the process of the service.
[0131] As an option, risk source data includes legal and regulatory data, industry requirement and specification data, service process demand data, and historical service process data, wherein the historical service process data includes external evaluation data of historical service processes given by the service recipients and internal evaluation data of historical service processes given by service departments related to the service processes.
[0132] Therefore, in the service risk management device provided in at least one embodiment of the present application, historical service process data representing process facts and actual situations can be used, and legal and regulatory data related to the service or service process, industry requirement specification data, service process demand data, etc. can also be used to evaluate the risks in each process of the service, so as to comprehensively identify and confirm the risk situations that may arise in the entire process of the service one by one.
[0133] In one embodiment of the present application, the risk level determination module 200 is further configured to determine the risk detection degree based on FMEA, external evaluation data of historical service processes, internal evaluation data of historical service processes, and industry requirement specification data.
[0134] In addition, the evaluation result also includes risk severity and risk occurrence, and the risk level determination module 200 is further configured to determine the risk level based on the risk detection level, risk severity and risk occurrence.
[0135] Therefore, the FMEA method uses the risk coefficient RPN to judge the risk level. The RPN value can be the product of risk detection, risk severity and risk occurrence. RPN indicates the level of risk caused by the failure mode. The higher the risk coefficient, the higher the risk in the current service process. The FMEA method has the advantages of simple calculation, easy understanding and easy operation. It can simplify the process of determining risk levels and facilitate real-time and accurate dynamic risk management.
[0136] In one embodiment of the present application, in order to improve the accuracy and precision of the service risk management device 2000, the risk level determination module 200 is further configured to determine the risk level based on the weight of risk detection, the weight of risk severity and the weight of risk occurrence.
[0137] Optionally, the risk level determination module 200 is further configured to determine at least one of the weights of risk detection, risk severity and risk occurrence using a subjective weight method or an objective weight method, wherein the subjective weight method includes at least one of a direct evaluation method, a hierarchical analysis method and a Delphi method, and the objective weight method includes at least one of an ordered weight operator method, a data envelopment method and a minimum cut set method.
[0138] As an option, the determine risk level module 200 is further configured to determine the detectability of the risk detectability based on at least one of the maturity of the risk detection method and the detection opportunity of the risk; and determine the risk detection level based on the detectability of the risk detectability.
[0139] As an option, the risk level determination module 200 is further configured to determine the likelihood of the risk occurrence based on at least one of a qualitative analysis and a quantitative analysis of the risk occurrence, and determine the risk occurrence based on the likelihood of the risk occurrence.
[0140] As an option, the risk level determination module 200 is further configured to determine the risk severity criteria based on the external evaluation data of the historical service process given by the service object, the loss or compensation corresponding to the historical service process, and at least one of the negative impacts corresponding to the historical service process, and determine the risk severity based on the risk severity criteria.
[0141] Fig. 9 It is a structural diagram of a computer system according to one embodiment of the present application, which is suitable for implementing the electronic device of the embodiment of the present application.
[0142] refer to Fig. 9 , which shows a schematic diagram of the structure of an electronic device 600 suitable for implementing the embodiments of the present application. The terminal device in the embodiments of the present application may include but is not limited to mobile terminals such as mobile phones, laptop computers, digital broadcast receivers, PDAs (personal digital assistants), PADs (tablet computers), PMPs (portable multimedia players), vehicle-mounted terminals (such as vehicle-mounted navigation terminals), etc., and fixed terminals such as digital TVs, desktop computers, etc. Fig. 9 The electronic device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.
[0143] like Fig. 9As shown, the electronic device 600 may include a processing device (e.g., a central processing unit, a graphics processing unit, etc.) 601, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 602 or a program loaded from a storage device 608 into a random access memory (RAM) 603. In the RAM 603, various programs and data required for the operation of the electronic device 600 are also stored. The processing device 601, the ROM 602, and the RAM 603 are connected to each other via a bus 604. An input / output (I / O) interface 605 is also connected to the bus 604.
[0144] Typically, the following devices may be connected to the I / O interface 605: an input device 606 including, for example, a touch screen, a touch pad, a keyboard, a mouse, a camera, a microphone, an accelerometer, a gyroscope, etc.; an output device 607 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, etc.; a storage device 608 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 609. The communication device 609 may allow the electronic device 600 to communicate with other devices wirelessly or by wire to exchange data. Although Fig. 9 The electronic device 600 is shown with various devices, but it should be understood that it is not required to implement or possess all the devices shown. More or fewer devices may be implemented or possessed instead. Fig. 9 Each block shown in the figure may represent one device, or may represent multiple devices as required.
[0145] In addition, according to the embodiment of the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, the embodiment of the present application includes a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from the network through a communication device 609, or installed from a storage device 608, or installed from a ROM 602. When the computer program is executed by the processing device 601, the above-mentioned functions defined in the method of the embodiment of the present application are executed. It should be noted that the computer-readable medium described in the embodiment of the present application can be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium can be, for example, but not limited to, a system, device or device of electricity, magnetism, light, electromagnetic, infrared, or semiconductor, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to, an electrical connection with one or more conductors, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In an embodiment of the present application, a computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, an apparatus, or a device. In an embodiment of the present application, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, in which a computer-readable program code is carried. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. A computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium, which may send, propagate, or transmit a program for use by or in combination with an instruction execution system, an apparatus, or a device. The program code embodied on the computer readable medium may be transmitted using any appropriate medium, including but not limited to: wire, optical cable, RF (radio frequency), etc., or any suitable combination of the foregoing.
[0146] The computer-readable medium may be included in the electronic device; or it may exist independently without being installed in the electronic device. The computer-readable medium carries one or more programs. When the one or more programs are executed by the electronic device, the electronic device: determines the risk source data in the service process; evaluates the risk in the service process based on the failure mode and effect analysis and the risk source data, and determines the risk level based on the evaluation result; and implements risk mitigation measures for risks whose risk level is greater than a preset threshold, wherein the evaluation result includes a risk detection degree that characterizes the difficulty of discovering the risk.
[0147] The computer program code for the operation of the embodiments of the present application can be written in one or more programming languages or a combination thereof, and the programming language includes an object-oriented programming language, such as Java, Smalltalk, C++, and also includes a conventional procedural programming language, such as "C" language or similar programming language. The program code can be executed completely on the user's computer, partially on the user's computer, as an independent software package, partially on the user's computer and partially on the remote computer, or completely on the remote computer or server. In the case of a remote computer, the remote computer can be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or can be connected to an external computer (e.g., using an Internet service provider to connect through the Internet).
[0148] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present application. In this regard, each square box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two square boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.
[0149] The units involved in the embodiments described in the present application may be implemented by software or hardware. The units described may also be set in a processor, for example, it may be described as: a processor includes a risk source analysis unit, a risk level determination unit, and a judgment unit. The names of these units do not constitute limitations on the units themselves in certain circumstances, for example, the judgment unit may also be described as a "risk level judgment unit".
[0150] The above description is only a preferred embodiment of the present application and an explanation of the technical principles used. Those skilled in the art should understand that the scope of the invention involved in the embodiments of the present application is not limited to the technical solutions formed by a specific combination of the above technical features, but should also cover other technical solutions formed by any combination of the above technical features or their equivalent features without departing from the above invention concept. For example, the above features are replaced with (but not limited to) technical features with similar functions disclosed in the embodiments of the present application.
Claims
1. A service risk management method, characterized in that: include: Identify risk source data in the service process; Based on the failure mode and effect analysis and the risk source data, the risk in the process of the service is evaluated, and the risk level is determined based on the evaluation result; as well as Implement risk mitigation measures for risks whose risk levels are greater than the preset threshold. The evaluation result includes a risk detection degree, which represents the degree of difficulty in detecting the risk.
2. The method according to claim 1, wherein: The method further comprises: Based on the failure mode and effect analysis, re-evaluate the risk after the risk mitigation measures are implemented, and determine the risk level of the risk after the risk mitigation measures are implemented based on the re-evaluation result; and In response to the risk level of the risk after implementing the risk mitigation measure being less than the preset threshold, continue to implement the risk mitigation measure; in response to the risk level of the risk after implementing the risk mitigation measure being greater than or equal to the preset threshold, modify the risk mitigation measure.
3. The method according to claim 1, wherein: The evaluation result also includes risk severity and risk occurrence, wherein the risk severity represents the severity of the risk after it occurs; and the risk occurrence represents the possibility of the risk occurring; but, Determining the risk level based on the evaluation result includes: determining the risk level based on the weight of the risk detection degree, the weight of the risk severity degree, and the weight of the risk occurrence degree.
4. The method according to claim 3, wherein: The method further comprises: Determine at least one of the weight of the risk detection degree, the weight of the risk severity degree, and the weight of the risk occurrence degree by using a subjective weight method or an objective weight method, Wherein, the subjective weight method includes at least one of a direct evaluation method, a hierarchy analysis method and a Delphi method; and The objective weight method includes at least one of an ordered weight operator method, a data envelopment method and a minimum cut set method.
5. The method according to claim 1, wherein: The method further comprises: Decompose the service into multiple service processes and determine the service departments related to the service processes; Then, decomposing the service into a plurality of service processes and determining a service department related to the service process comprises: decomposing the service into a plurality of service processes using a concept blueprint; and the service department compiling details of the service process corresponding to the service department using a detail blueprint; The service department includes a direct service department and an indirect service department, wherein the direct service department includes a department that has a direct relationship with the service object in the service process; and the indirect service department includes a department that has an indirect relationship with the service object in the service process.
6. The method according to claim 1, wherein: The risk source data includes legal and regulatory data, industry requirement and specification data, service process demand data, and historical service process data, wherein the historical service process data includes external evaluation data of historical service processes given by service objects and internal evaluation data of historical service processes given by service departments related to the service processes; then, Based on the failure mode and effect analysis and the risk source data, the risk in the service process is evaluated, including: based on the failure mode and effect analysis, the external evaluation data of the historical service process, the internal evaluation data of the historical service process, and the industry requirement specification data, determining the risk detection level.
7. The method according to claim 1, wherein: Based on the failure mode and effect analysis and the risk source data, evaluating the risk in the process of the service includes: determining the detectability of the risk detectability based on at least one of the maturity of the risk detection method and the detection opportunity of the risk; and determining the risk detectability based on the detectability; and / or, The evaluation result also includes a risk occurrence degree, and based on the failure mode and effect analysis and the risk source data, evaluating the risk in the process of the service further includes: determining the possibility degree of the risk occurrence degree based on at least one of a qualitative analysis and a quantitative analysis of the risk occurrence degree; and determining the risk occurrence degree based on the possibility degree of the risk occurrence degree; and / or, The evaluation result also includes risk severity. Based on the failure mode and effect analysis and the risk source data, the risk evaluation of the service process also includes: determining the risk severity determination criteria based on the external evaluation data of the historical service process given by the service object, the loss or compensation corresponding to the historical service process and at least one of the negative impacts corresponding to the historical service process; and determining the risk severity based on the risk severity determination criteria.
8. A service risk management device, characterized in that: The device comprises: A risk source analysis module is configured to determine risk source data in the process of the service; a risk level determination module configured to evaluate the risk in the service process based on the failure mode and effect analysis and the risk source data, and determine the risk level based on the evaluation result; and The judgment module is configured to implement risk mitigation measures for risks whose risk level is greater than a preset threshold, The evaluation result includes a risk detection degree, which represents the degree of difficulty in detecting the risk.
9. An electronic device, characterized in that: include: at least one processor; as well as, A memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor so that the at least one processor can execute the service risk management method described in any one of claims 1-7.
10. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the service risk management method according to any one of claims 1 to 7 is implemented.
