WO2019232957A1 - Procédé et système de liaison de risque opérationnel, dispositif informatique et support de stockage - Google Patents

Procédé et système de liaison de risque opérationnel, dispositif informatique et support de stockage Download PDF

Info

Publication number
WO2019232957A1
WO2019232957A1 PCT/CN2018/104704 CN2018104704W WO2019232957A1 WO 2019232957 A1 WO2019232957 A1 WO 2019232957A1 CN 2018104704 W CN2018104704 W CN 2018104704W WO 2019232957 A1 WO2019232957 A1 WO 2019232957A1
Authority
WO
WIPO (PCT)
Prior art keywords
module
risk
linkage
field
rcsa
Prior art date
Application number
PCT/CN2018/104704
Other languages
English (en)
Chinese (zh)
Inventor
朱丽莎
谭志荣
魏尧东
Original Assignee
平安科技（深圳）有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 平安科技（深圳）有限公司 filed Critical 平安科技（深圳）有限公司
Publication of WO2019232957A1 publication Critical patent/WO2019232957A1/fr

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
    • G06Q10/063—Operations research, analysis or management
    • G06Q10/0635—Risk analysis of enterprise or organisation activities
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management
    • G06Q10/103—Workflow collaboration or project management

Definitions

  • the present application relates to the field of data processing technology, and in particular, to a method, a system, a computer device, and a storage medium for operating risk linkage.
  • Operational risk refers to risks caused by imperfect or problematic internal procedures, employees and information technology systems, and external events. There are four main forms of operational risk, namely operational errors, subjective violations, internal fraud and external fraud.
  • the three major management tools for operational risk that are very popular internationally are: Risk and Control Self-Assessment (RCSA), Operational Risk Event and Loss Data Collection (LDC), and Key Risk Indicators (KRI).
  • RCSA Risk and Control Self-Assessment
  • LDC Operational Risk Event and Loss Data Collection
  • KRI Key Risk Indicators
  • the above three management tools can identify, evaluate, monitor and control the same object from different dimensions and perspectives when dealing with operational risks, so that their respective results are consistent in a certain sense, but the three tools
  • Each tool has its own advantages and disadvantages when dealing with operational risks.
  • the data of some tools are affected by subjective judgments, and there are certain inaccuracies and imperfections.
  • An operational risk linkage method includes: setting a preset field as an operational risk identifier for establishing an association relationship among multiple risk management modules, the multiple risk management modules including a risk and control self-assessment RCSA module, and an operational risk event And loss data collection LDC module and key risk indicator KRI module; at least one linkage mark is set in each of the RCSA module, the LDC module and the KRI module, and after triggering any linkage mark, the corresponding linkage mark is extracted
  • the risk management module all fields in the operational risk identification are set to correlation information, and the corresponding data in the other two modules are called. According to the linkage rules, the data matching the correlation information is extracted in the form of a list.
  • a first association list is generated in the risk management module corresponding to the linkage identifier.
  • An operation risk linkage system includes: a preset unit configured to set a preset field as an operation risk identifier for establishing an association relationship among multiple risk management modules, and the multiple risk management modules include self-assessment of risk and control RCSA module, operational risk event and loss data collection LDC module and key risk indicator KRI module; linkage unit is set to set at least one linkage mark in the RCSA module, the LDC module and the KRI module, respectively, to trigger any After a linkage ID is extracted, all fields in the risk management module corresponding to the linkage ID are extracted, and all fields in the operational risk ID are set to associated information. The corresponding data in the other two modules are called, and the data matching the associated information is extracted according to the linkage rules. In the form of a list, a first association list is generated in the risk management module corresponding to the linkage identifier.
  • a computer device includes a memory and a processor.
  • the memory stores computer-readable instructions.
  • the processor causes the processor to perform the following steps:
  • preset fields are set as operational risk identifiers for establishing an associated relationship.
  • the multiple risk management modules include a risk and control self-assessment RCSA module, an operational risk event and loss data collection LDC module, and a key risk indicator KRI module.
  • At least one linkage identifier is set in each of the RCSA module, the LDC module, and the KRI module.
  • the risk management module corresponding to the linkage identifier is extracted, and all fields in the operational risk identifier are set as related information.
  • the corresponding data in the other two modules is called, and the data matching the association information is extracted according to the linkage rules, and a first association list is generated in the risk management module corresponding to the linkage identifier in the form of a list.
  • a storage medium storing computer-readable instructions.
  • the one or more processors execute the following steps:
  • the field is set to identify the operational risk associated with the relationship.
  • the multiple risk management modules include a risk and control self-assessment RCSA module, an operational risk event and loss data collection LDC module, and a key risk indicator KRI module.
  • the LDC module and the KRI module respectively set at least one linkage identification, and after triggering any linkage identification, extracting all the fields in the risk management module corresponding to the linkage identification, and setting all fields in the operational risk identification to association information,
  • the corresponding data in the other two modules are called, and the data matching the association information is extracted according to the linkage rules, and a first association list is generated in the risk management module corresponding to the linkage identifier in the form of a list.
  • the above-mentioned operational risk linkage method, device, computer equipment and storage medium are respectively set in a plurality of risk management modules with preset fields as operational risk identifiers for establishing an associated relationship.
  • the multiple risk management modules include a risk and control self-assessment RCSA module, Operational risk event and loss data collection LDC module and key risk indicator KRI module; at least one linkage mark is set in the RCSA module, LDC module and KRI module respectively. After triggering any linkage mark, the risk management module corresponding to the linkage mark is extracted. All fields in the operational risk identification are set to correlation information, and the corresponding data in the other two modules are called.
  • the linkage rules the data matching the correlation information is extracted, and the list is generated in the risk management module corresponding to the linkage identification.
  • An association list By adopting the above technical solution, the present application cross-uses multiple risk management modules in the three operational risk tool systems, fully utilizes the advantages of the three major tools, makes up for the shortcomings of the three, and improves the total use of the three major tools. effectiveness.
  • FIG. 1 is a flowchart of an operation risk linkage method according to an embodiment of the present application
  • FIG. 2 is a schematic diagram of a business process interface of the RCSA module of this application.
  • FIG. 3 is a schematic diagram of a risk identification interface of the RCSA module of this application.
  • FIG. 5 is a schematic interface diagram of a KRI module of the present application.
  • FIG. 6 is a schematic diagram of a test interface of the present application.
  • FIG. 7 is a structural diagram of a linkage verification system in an embodiment of the present application.
  • FIG. 1 is a flowchart of an operation risk linkage method according to an embodiment of the present application.
  • the method includes the following steps: Step S1: Establishing a unified operation risk identifier: The preset fields are set in multiple risk management modules as Established the relationship of operational risk identification, multiple risk management modules include risk and control self-assessment RCSA module, operational risk event and loss data collection LDC module and key risk indicator KRI module. This step is used to establish a unified operational risk identification.
  • the operational risk identification includes a main process identification, a sub-process identification, a risk point identification, a control activity identification, a risk incentive identification, and an event type identification.
  • the main process ID and sub-process ID are mandatory fields, and at least one of the risk point identification, control activity identification, risk incentive identification, or event type identification is optional.
  • the RCSA module, LDC module, and KRI Once a preset field is established in the module and set as the operational risk identifier, all preset fields are required. Before the preset fields in the RCSA module, LDC module, and KRI module, set "*" as a reminder of required fields.
  • Step S2 Establish a linkage mechanism: Set at least one linkage identifier in the RCSA module, LDC module, and KRI module. After triggering any linkage identifier, extract all the fields in the risk management module corresponding to the linkage identifier and operate the settings. For the association information, the corresponding data in the other two modules are called, and the data matching the association information is extracted according to the association rules, and the first association list is generated in the risk management module corresponding to the association identifier in the form of a list.
  • the above linkage rules are: when the RCSA module is called, the following fields are set to match the data: serial number, risk code, risk name, main business process, sub-business process, risk incentive, event type, probability, severity, risk rating Or at least one of the fields of overall control effectiveness.
  • the LDC module When the LDC module is called, the following fields are set to match the data: sequence number, event code, event name, event department, attribution month, whether major event, actual loss amount, financial impact severity, non-financial impact severity, comprehensive At least one of the fields of impact severity, risk incentive, event type, whether rectification is required or the situation.
  • the following fields are set to match the data: sequence number, indicator code, indicator name, indicator level, monitoring frequency, main business process, sub-business process, risk incentive, event type, early warning status of the indicator within one year, or Correct at least one field in the situation.
  • the extraction test identifier is set to the associated information, and the corresponding data in the RCSA module is called.
  • the linkage rule is to extract the data set as the following fields to match: serial number, risk code, risk name, main business process, sub-business At least one of the fields of process, risk incentive, event type, probability, severity, risk rating, or overall control effectiveness.
  • the linkage rule is to extract the data set as the following fields to match: sequence number, event code, event name, event department, attribution At least one of the fields of month, whether major event, actual loss amount, financial impact severity, non-financial impact severity, comprehensive impact severity, risk incentive, event type, whether rectification or rectification is required.
  • the extraction test identifier is set to the associated information, and the corresponding data in the KRI module is called.
  • the linkage rule is to extract the data set as the following fields to match: serial number, indicator code, indicator name, indicator level, monitoring frequency Field, at least one of the main business process, sub-business process, risk incentive, event type, indicator warning or rectification within one year.
  • the preset field is set as the operation risk identifier for establishing the association relationship in step S1
  • the following method is adopted: As shown in FIG. 2, in the business process interface of the RCSA module, the main business process field is set to The main process ID is set as the sub process ID with the business process name field. As shown in Figure 3, in the risk identification interface of the RCSA module, the main business process field is set as the main process ID, the business process field is set as the sub process ID, and the risk name field is set as the risk point ID to control the activity field.
  • the risk inducement directory is set, the risk inducement directory field is set as the risk inducement identifier, the event type directory is set, and the event type directory field is set as the event type identifier.
  • the main business process field is set as the main process identifier, and a new business subprocess directory field is added. All options in the business subprocess directory field are in the RCSA business process.
  • the event type directory field is set as the event type identifier, and the risk factor directory field is set as the risk factor identifier.
  • the main business process field is set as the main process ID
  • the sub business process field is set as the sub process ID
  • the associated risk point field, associated control activity field, and risk inducement directory are added.
  • At least one of a field or an event type directory field, wherein an associated risk point field is set as a risk point identifier, an associated control activity field is set as a control activity identifier, a risk inducement directory field is set as a risk inducement identifier, and an event is The type directory field is set to the event type identifier.
  • the above risk inducement directory field can set two sub-drop-down menus of risk inducement (first-level directory) and risk inducement (second-level directory).
  • first-level directory risk inducement
  • second-level directory risk inducement
  • the system automatically generates according to the risk inducement table.
  • Risk inducement (secondary category) menu option If the user directly selects the risk incentives (secondary directory), all the second-level directories under the risk incentives (first-level directory) will be displayed. After the user completes the selection of the risk incentives (secondary directory), the risk incentives (first-level directory) will be displayed. )Automatic generated.
  • the event type directory can set three sub-drop-down menus of event type (first-level directory), event type (second-level directory), and event type (third-level directory).
  • first-level directory event type
  • second-level directory event type
  • third-level directory event type
  • a status field can also be added to indicate whether the status is in use or disabled, and the status field is set to identify the current use status of the business process.
  • a query condition field is added to be used. Or Disabled Set as option to query all business processes.
  • the main process can be disabled when all the sub-processes under the main process are disabled; when the main process is enabled, all the sub-processes under the main process can be enabled.
  • the indicator list pops up to complete the linkage mechanism with the KRI module.
  • the corresponding KRI indicator field displays a prompt word. Among them, the word "prompt" is highlighted in red, and the indicator list is shown in Table 1 below:
  • the main business process field is set to another linkage identifier.
  • the corresponding data in the RCSA module is called to pop up the list of risk points to complete the linkage mechanism with the risk points in the RCSA module.
  • the corresponding list of risk points pops up.
  • the list of risk points is shown in Table 2 below:
  • the associated risk point field is set as the linkage ID. After the associated risk point field is triggered, the corresponding data in the RCSA module is called to pop up the list of risk points and complete the connection with For the linkage mechanism of the RCSA module, the list of risk points here is the same as shown in Table 2.
  • an additional RCSA association information field is set as the linkage identifier. After the RCSA association information field is triggered, the corresponding data in the RCSA module is called to pop up a list of risk points and complete the linkage mechanism with the RCSA module.
  • the list of risk points is shown in Table 2 above.
  • the operational risk identifier may use the preset fields shown in Table 3:
  • the additional business process field is set as the test identifier
  • the view associated risk field, the view associated LDC event field, and the view associated KRI indicator field are respectively set as linkage identifiers.
  • the extraction test identifier is set to Relevant information, call the corresponding data in the RCSA module, LDC module or KRI module, and extract the data that matches the associated information according to the linkage rules, and generate a second association list in the form of a list.
  • the business process field of this embodiment may be a test interface after a linkage mechanism is established between the RCSA module, the LDC module, and the KRI module. In the test interface, an additional business process field is set as the test identifier.
  • a second association list is generated in the test interface.
  • the second association list in this embodiment uses the same linkage rules as the first association list in step S2, but because the extracted association information is different between the two, the first association list is set by all fields in the extracted operation risk identifier It is obtained for the association information, and the second association list is obtained by setting the extracted test identifier as the association information, so the two exist independently of each other. In this way, users can get the required association list according to different fields in different situations.
  • the content of the added business process field should be the same as the content of the sub-process field in the RCSA module.
  • the test includes: After correlating the linkage identification of the risk field, extract the test identification and set it as the correlation information, call the corresponding data in the RCSA module, and extract the data that matches the correlation information according to the linkage rules, and display the above-mentioned correlation Table 2 in the test interface in the form of a list. .
  • the test ID is extracted and set to the relevant information.
  • the corresponding data in the LDC module is called.
  • the association list is the statistical information of LDC events, as shown in Table 4 below:
  • the above table 4 is displayed on the test interface.
  • the matching data corresponding to all associated LDC events within one year are extracted and pushed forward at the time of the test day, and the average calculation script is inserted.
  • the average calculation script is used to calculate the The mean value of the comprehensive impact severity field in the matching data.
  • a prompt is displayed after viewing the associated LDC event field.
  • the prompt word is preferably in red font, “there may be a higher risk”, reminding the evaluator to refer to historical data information.
  • the preset value is preferably greater than or equal to 3, that is, the average value of the comprehensive impact severity is above level 3. After viewing the associated LDC event field, a red “probably higher risk” prompt is displayed.
  • the test identifier After triggering to view the linkage identifier of the associated KRI indicator field, the test identifier is extracted and set to the correlation information. The corresponding data in the KRI module is called. According to the linkage rules, the data matching the correlation information is extracted.
  • the test interface displays the same as the above. Table 1 shows the same association list. While displaying the same correlation list as in Table 1 above on the test interface, it also extracts the matching data corresponding to all related KRI indicators for a period of one year and pushes forward on the test day, inserts a calculation sum script, and uses the calculation sum The script counts the number of warnings that light up in the matching data in this one year.
  • the prompt When the number is greater than the preset number, the prompt will be displayed after viewing the associated KRI indicator field.
  • the prompt word is preferably in red font, "there may be a higher risk", to remind assessors to refer to historical data information.
  • the warning conditions of the indicators in Table 1 within one year can be divided into four situations: red light, yellow light, green light, and unreported.
  • the calculation and summation script preferably calculates the number of warnings that light up red or yellow.
  • the preset number of times is 2 red lights or 3 yellow lights, that is, the total number of red lights in the warning situation within a year exceeds 2 times or the yellow light exceeds 3.
  • a red "probable risk" prompt is displayed in red.
  • an operation risk linkage system including: a preset unit configured to set preset fields as operation risk identifiers for establishing an association relationship among multiple risk management modules.
  • the multiple risk management modules include risk and control self-assessment RCSA module, operational risk event and loss data collection LDC module and key risk indicator KRI module.
  • the linkage unit is set to set at least one linkage mark in the RCSA module, the LDC module and the KRI module, and after triggering any linkage mark in any module, extract all of the operational risk marks in the risk management module corresponding to the linkage mark.
  • the field is set to association information, corresponding data in the other two modules are called, and data matching the association information is extracted according to the linkage rule, and a first association list is generated in the risk management module corresponding to the linkage identifier in the form of a list.
  • the preset unit is further configured to add a status field in the business process interface of the RCSA module to be used or disabled, and the status field is set to identify the use status of the current business process. Add a query on this page Condition field to query all business processes with active or disabled set as option.
  • the linkage rules in the linkage unit and the test unit are: when the RCSA module is called, the following fields are set to match the data: sequence number, risk code, risk name, main business process, sub-business process, risk incentive , Event type, likelihood, severity, risk rating, or overall control effectiveness.
  • the LDC module When the LDC module is called, the following fields are set to match the data: sequence number, event code, event name, event department, attribution month, whether major event, actual loss amount, financial impact severity, non-financial impact severity, comprehensive At least one of the fields of impact severity, risk inducement, event type, whether rectification is needed or the situation.
  • the following fields are set to match the data: sequence number, indicator code, indicator name, indicator level, monitoring frequency, main business process, sub-business process, risk incentive, event type, early warning status of the indicator within one year, or Correct at least one field in the situation.
  • the linkage unit when setting the linkage identifier, includes: adding a KRI indicator field module, which is set to the business process interface of the RCSA module, adding a KRI indicator field to set the linkage indicator, and triggering the KRI indicator field, and calling the KRI module.
  • the corresponding data pops up the indicator list and completes the linkage mechanism with the KRI module.
  • the corresponding KRI indicator field displays a prompt, and the main business process field is set to another linkage identifier.
  • Call the corresponding data in the RCSA module pop up the list of risk points, and complete the linkage mechanism with the risk points in the RCSA module.
  • Add an associated risk point field module set it to the operation risk event interface of the LDC module, set the associated risk point field to be a linkage ID, and trigger the associated risk point field, then call the corresponding data in the RCSA module to pop up the risk point List to complete the linkage mechanism with the RCSA module.
  • Add the RCSA correlation information field module set it in the KRI module, add the RCSA correlation information field to set the linkage ID, trigger the RCSA correlation information field, call the corresponding data in the RCSA module, pop up the list of risk points, and complete the linkage with the RCSA module mechanism.
  • the linkage unit further includes a test module, which is set to add a business process field as a test identifier, and respectively add a view associated risk field, a view associated LDC event field, and a view associated KRI indicator field to a linkage identifier to trigger any
  • the test identification is extracted and set as the correlation information, and the corresponding data in the RCSA module, the LDC module or the KRI module is called, and according to the linkage rule, the data matching the correlation information is extracted, and a second correlation list is generated in the form of a list.
  • the linkage unit further includes a comprehensive impact severity calculation module, which is configured to, when triggering to view the linkage ID of the associated LDC event field, extract the time point on the day of the test and push forward the corresponding LDC events for one year. Match data, insert the calculation average script, and use the average calculation script to calculate the average value of the comprehensive impact severity field in the matching data within one year. If the average value is greater than the preset value, a prompt is displayed after viewing the associated LDC event field .
  • a comprehensive impact severity calculation module which is configured to, when triggering to view the linkage ID of the associated LDC event field, extract the time point on the day of the test and push forward the corresponding LDC events for one year. Match data, insert the calculation average script, and use the average calculation script to calculate the average value of the comprehensive impact severity field in the matching data within one year. If the average value is greater than the preset value, a prompt is displayed after viewing the associated LDC event field .
  • the linkage unit further includes an early-warning calculation module, and the early-warning calculation module is configured to, when triggered to view the linkage identifier of the associated KRI indicator field, extract the corresponding KRI indicator corresponding to all related KRI indicators during the time point of the test day.
  • the calculation data is inserted into the calculation sum script, and the calculation sum script is used to calculate the number of warnings for lighting in the matching data within one year. When the number is greater than the preset number, a prompt is displayed after viewing the associated KRI indicator field.
  • a computer device which includes a memory and a processor.
  • the memory stores computer-readable instructions, and when the computer-readable instructions are executed by the processor, the processor is caused to implement the foregoing when the computer-readable instructions are executed. The steps in the method of operating risk linkage in the embodiment.
  • a storage medium storing computer-readable instructions.
  • the computer-readable instructions are executed by one or more processors, the one or more processors are caused to perform the operation risk linkage in the foregoing embodiments. Steps in the method.
  • the storage medium may be a non-volatile storage medium.
  • the program may be stored in a computer-readable storage medium.
  • the storage medium may include: Read-only memory (ROM, Read Only Memory), random access memory (RAM, Random Access Memory), magnetic disks or optical disks, etc.

Landscapes

  • Business, Economics & Management (AREA)
  • Human Resources & Organizations (AREA)
  • Engineering & Computer Science (AREA)
  • Strategic Management (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Economics (AREA)
  • Tourism & Hospitality (AREA)
  • Marketing (AREA)
  • Operations Research (AREA)
  • Quality & Reliability (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Game Theory and Decision Science (AREA)
  • Development Economics (AREA)
  • Educational Administration (AREA)
  • Data Mining & Analysis (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

L'invention concerne un procédé et un dispositif de liaison de risque opérationnel, un dispositif informatique et un support de stockage qui appartiennent au domaine technique du traitement des données. Le procédé de liaison de risque opérationnel consiste à : établir des identifiants de risque opérationnel dans une pluralité de modules de gestion de risque, régler au moins un identifiant de liaison et déclencher un identifiant de liaison quelconque pour produire une première liste d'associations. Le procédé utilise transversalement une pluralité de modules de gestion de risque dans trois systèmes d'outil de risque de fonctionnement majeur, ce qui déploie totalement les avantages des trois outils majeurs, remédie aux inconvénients des trois outils majeurs et améliore l'efficacité d'application totale des trois outils majeurs.
PCT/CN2018/104704 2018-06-04 2018-09-08 Procédé et système de liaison de risque opérationnel, dispositif informatique et support de stockage WO2019232957A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810561286.9 2018-06-04
CN201810561286.9A CN109190862B (zh) 2018-06-04 2018-06-04 操作风险联动方法、系统、计算机设备和存储介质

Publications (1)

Publication Number Publication Date
WO2019232957A1 true WO2019232957A1 (fr) 2019-12-12

Family

ID=64948563

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/104704 WO2019232957A1 (fr) 2018-06-04 2018-09-08 Procédé et système de liaison de risque opérationnel, dispositif informatique et support de stockage

Country Status (2)

Country Link
CN (1) CN109190862B (fr)
WO (1) WO2019232957A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117593140A (zh) * 2024-01-17 2024-02-23 亿海蓝（北京）数据技术股份公司 航运保险累积风险识别方法及系统、电子设备及存储介质

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111178719A (zh) * 2019-12-20 2020-05-19 中国建设银行股份有限公司 操作风险内部损失数据的收集方法、装置、电子设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140244342A1 (en) * 2013-02-25 2014-08-28 Microsoft Corporation Accounting for contract formation and fulfillment activities
CN104796738A (zh) * 2015-04-01 2015-07-22 乐视致新电子科技（天津）有限公司 信息联动方法、装置、服务端和系统
CN106572336A (zh) * 2016-11-09 2017-04-19 国网浙江省电力公司 一种智能电网的视频联动系统及智能电网的视频联动方法
CN108038142A (zh) * 2017-11-24 2018-05-15 平安科技（深圳）有限公司 实现多级联动下拉框的方法、电子装置及存储介质

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10453142B2 (en) * 2009-02-11 2019-10-22 Johnathan Mun System and method for modeling and quantifying regulatory capital, key risk indicators, probability of default, exposure at default, loss given default, liquidity ratios, and value at risk, within the areas of asset liability management, credit risk, market risk, operational risk, and liquidity risk for banks
CN101714273A (zh) * 2009-05-26 2010-05-26 北京银丰新融科技开发有限公司 一种基于规则引擎的银行异常业务监控方法和系统
CN103092997B (zh) * 2013-02-21 2016-03-30 用友网络科技股份有限公司 用于报表分析的联动查询系统和联动查询方法
CN106779411A (zh) * 2016-12-16 2017-05-31 华迪计算机集团有限公司 一种基于企业管理关键风险指标的预警方法和系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140244342A1 (en) * 2013-02-25 2014-08-28 Microsoft Corporation Accounting for contract formation and fulfillment activities
CN104796738A (zh) * 2015-04-01 2015-07-22 乐视致新电子科技（天津）有限公司 信息联动方法、装置、服务端和系统
CN106572336A (zh) * 2016-11-09 2017-04-19 国网浙江省电力公司 一种智能电网的视频联动系统及智能电网的视频联动方法
CN108038142A (zh) * 2017-11-24 2018-05-15 平安科技（深圳）有限公司 实现多级联动下拉框的方法、电子装置及存储介质

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117593140A (zh) * 2024-01-17 2024-02-23 亿海蓝（北京）数据技术股份公司 航运保险累积风险识别方法及系统、电子设备及存储介质

Also Published As

Publication number Publication date
CN109190862A (zh) 2019-01-11
CN109190862B (zh) 2022-07-15

Similar Documents

Publication Publication Date Title
US20120207286A1 (en) Anti-social protocol for emergency dispatch
CN108170580A (zh) 一种基于规则的日志报警方法、装置及系统
US8332503B2 (en) Message abnormality automatic detection device, method and program
US20110125746A1 (en) Dynamic machine assisted informatics
US9443244B2 (en) System and method for utilizing customer data in a communication system
WO2019232957A1 (fr) Procédé et système de liaison de risque opérationnel, dispositif informatique et support de stockage
US11507674B2 (en) Quantifying privacy impact
CN111582771A (zh) 风险评估方法、装置、设备及计算机可读存储介质
CN105376223A (zh) 网络身份关系的可靠度计算方法
US8090994B2 (en) System, method, and computer readable media for identifying a log file record in a log file
US20060106651A1 (en) Insurance claim monitoring
JP5581498B2 (ja) 罹災状況管理システム
CN117273429A (zh) 事件监测方法、系统、电子设备及存储介质
WO2007143020B1 (fr) Appareil, système, procédé et programme informatique pour la gestion de transactions impliquant des actifs de l'aviation
US20140156340A1 (en) System and method for identifying outlier risks
CN110502529B (zh) 数据处理方法、装置、服务器及存储介质
CN109598485A (zh) 一种突发事件报事方法及装置
CN111143325A (zh) 一种数据采集的监测方法、监测装置及可读存储介质
EP2929473A1 (fr) Système et procédé pour déterminer, par une entité externe, la structure hiérarchique humaine d'un organisme, à l'aide de réseaux sociaux publics
KR20210086833A (ko) Sns 데이터를 이용한 재난 정보 제공 시스템 및 그 방법
CN112752256A (zh) 客户画像标签确定方法、装置、设备及存储介质
Omweri et al. Using a mobile based web service to search for missing people–a case study of Kenya
CN110601875B (zh) 信息输出方法、装置、管理设备及计算机可读存储介质
WO2019041532A1 (fr) Système et procédé de gestion d'informations de conservation du sang
JP7490689B2 (ja) 予防貢献度管理装置及び予防貢献度管理方法

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18921518

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 17/03/2021)

122 Ep: pct application non-entry in european phase

Ref document number: 18921518

Country of ref document: EP

Kind code of ref document: A1