Enterprise Risk Management (ERM) Consulting × Technical integration & enterprise governance

ERM Technical Integration: From KRIs and Risk Appetite to Control Effectiveness

Updated 2026-11-09

The short answer

Technical integration of ERM means turning risk appetite into KRI thresholds, control effectiveness into KCIs, and strategic and operational risks into one picture the board can read — embedded in your existing strategic planning, internal control and management systems. Winners plans it as one piece against the TWSE Best Practice Principles, COSO ERM and ISO 31000; Ahura (POC) keeps the evidence on-premises and records every sign-off in its evidence chain.

Companion page: service overview: Enterprise Risk Management (ERM) ConsultingWhat this service is, who it is for and what we deliver are on the service overview page.

Which existing processes does ERM plug into — strategic planning, budgeting, internal control and the board agenda?

The most common way ERM fails is a risk report updated once a year that nobody opens again. To avoid that, ERM has to grow on processes the company already runs:

  • Annual strategy and budgeting: the core of COSO ERM 2017 is putting risk next to strategy and performance. Strategy meetings discuss not only targets but how much risk the company is willing to take to reach them — the risk appetite of Article 22 of the TWSE Risk Management Best Practice Principles.
  • Board and committee agendas: Article 14 of the Principles has the risk management committee report to the board at least once a year. We put this on the existing agenda and annual calendar instead of calling ad-hoc meetings.
  • Internal control self-assessment and internal audit: the self-assessment and audit already running under Taiwan's Regulations Governing Establishment of Internal Control Systems by Public Companies are exactly the tools for checking whether controls work; ERM does not build a second set.
  • Risk assessments in each management system: security, business continuity and AI programmes each assess risk. ERM supplies the common method and categories (Article 18) so the results can be added up.
  • Procurement, finance and operations: supplier concentration, FX and capacity data already sit in the ERP and finance systems and become KRI data sources directly.

We establish the risk management policy, risk appetite, three lines of defence and board reporting, starting from the management system you already run and building the requirements into it instead of setting up a separate one, cutting duplicated effort now and maintenance cost later.

Which technologies make ERM real — KRIs, KCIs, risk appetite and risk aggregation?

The technical side of ERM is not buying a system; it is giving every requirement of the Principles data, a threshold and a record. The table lists the seven items we implement most often; article numbers follow the TWSE Risk Management Best Practice Principles for TWSE/TPEx Listed Companies, mapped to COSO ERM 2017 principles and ISO 31000:2018 clauses.

Requirement (article / control)Implementing technologyEvidence left behind
Principles Art. 15(2), Art. 21: qualitative and quantitative measurement standardsA single risk scoring matrix (impact × likelihood) and a KRI dictionary defining each indicator's data source, calculation and update frequencyApproved scoring criteria, KRI dictionary
Principles Art. 22: risk appetite; COSO Principle 7Breaking the appetite statement into measurable limits and KRI thresholds, with automatic breach alertsCommittee-approved appetite statement, breach notification records
Principles Art. 18: risk categories; COSO Principle 14 portfolio viewOne risk register with common categories (strategic, operational, financial, information, compliance, integrity, emerging), aggregated bottom-up into an enterprise risk portfolioRisk register, portfolio heat map
Principles Art. 23: risk evaluationAnalysis results compared automatically with appetite; anything above it is prioritisedRisk evaluation records, priority list
Principles Arts. 24, 25: response plans, monitoring and review; ISO 31000 clauses 6.5, 6.6Treatment-plan tracking and control self-assessment, with key control indicators (KCIs) measuring control effectivenessTreatment-plan progress, control test and KCI records
Principles Art. 26: record keeping; ISO 31000 clause 6.7A record repository that traces every step of the risk process, with versions and approvalsRetrievable risk management records
Principles Art. 14(5), Arts. 27, 28: reporting and disclosureBoard reports compiled automatically from the register and KRIs; disclosures organised around the three items of Art. 28Board and committee minutes, disclosure page on the company website or MOPS

KRIs show early warning that a risk is rising, KCIs show whether controls are working, and KPIs show whether targets are met. Only with all three on one dashboard can the board tell whether good performance comes from effective controls or simply from luck.

We do not start by buying a system. In most companies the raw data for KRIs already sits in the ERP, finance and security systems; what is missing is the indicator definitions, who approves the thresholds and who is notified when a threshold is breached. Settle those three things first, then decide whether a spreadsheet, an existing business-intelligence tool or a dedicated platform should carry them.

The article numbers in the table are where the mapping starts, not where it ends: after each item goes live, we check back that operating units are actually using it rather than leaving it on paper.

How does a risk travel through the Principles to technical controls and monitoring metrics?

Take a critical raw material sourced from a single supplier and follow the risk from identification to the board report:

  1. Risk identification: an operating unit flags single-source risk in its annual assessment (operational risk under Article 18); a security incident at that supplier could also stop deliveries, which is an information risk.
  2. Framework and Principles requirements: risk assessment under ISO 31000 clause 6.4; comparison with the committee-approved appetite under Article 22 — for example a cap on the share of any single supplier; and, under COSO Principle 14, a portfolio view of whether it coincides with capacity or FX risk.
  3. Technical controls: ERP purchasing data calculates a supplier-concentration KRI every month; progress on qualifying a second source is set as a KCI; the supplier's security assessment result is pulled from the security system into the same risk record.
  4. Monitoring and reporting: a KRI breach notifies the execution unit and the committee; treatment progress is tracked under Articles 24 and 25; the annual report goes to the board under Article 14(5), and disclosure follows Article 28.

The chain holds together because one team does all four things: risk management first, then international standards and regulatory compliance, then data integration and controls, and finally process improvement. We have supported the Taiwan Stock Exchange (TWSE) — internal control system integrated with ISO 9000 and ISMS — and the Joint Credit Information Center (JCIC) — internal control system integrated with ISO 27001 and TPIPAS — work that is precisely about internal control and several management systems sharing one set of evidence. We map against the TWSE Principles article by article, and every deliverable is tied to an article number and an evaluation indicator.

Which departments, systems, data and evidence need to be integrated vertically into one ERM?

Articles 10 to 16 of the Principles divide responsibilities among the board, the risk management committee, the risk management promotion and execution unit, and the operating units. Even with clear roles, if the data stays scattered, the board still receives a patchwork report. Vertical integration means a single risk travels from an operating unit's system all the way to the board minutes.

DepartmentSystemDataEvidence
Board / risk management committeeBoard meeting and document systemRisk policy, appetite, annual reportApproval records, minutes (Principles Arts. 13, 14)
Risk management promotion and execution unitRisk register and KRI dashboardRisk portfolio, KRIs, breachesAnnual execution report (Art. 15), breach notification records
Operating units (procurement, production, sales)ERP, production and CRM systemsSupplier concentration, capacity, customer concentrationRisk identification and response records (Art. 16)
FinanceFinance and treasury systemsFX exposure, liquidity, credit riskFinancial-risk KRI records
IT / securityVulnerability scanning, security monitoring (SIEM), existing ISMS toolsUnpatched high-risk vulnerabilities, security incidentsSecurity KRI and incident records
Internal auditAudit management and control self-assessment toolsControl test results, deficiencies and remediationAudit reports, KCI records

Security, business continuity and AI management systems handle only the risk sources and treatment in their own domain; ERM supplies the common policy, appetite, method and board reporting. The business impact analysis under ISO 22301 and the security risk assessment under ISO 27001 both feed the same enterprise risk map.

Success hinges on three handover points: when an operating unit raises a new risk, the execution unit registers it under the common categories; when a KRI is breached, the notification reaches both the risk owner and the committee; when internal audit finds a control deficiency, the related KCI and treatment plan are updated at the same time. With records at all three points, what the board sees is one consistent data set.

What does Ahura do in an ERM engagement, and how does the data flow?

The Ahura enterprise risk management platform is a Taiwan-native RegTech platform for enterprise risk management and compliance, developed by Winners Consulting and currently at proof-of-concept (POC) stage. Everything below refers to the POC version. In an ERM engagement, data flows like this:

  1. In: consultant deliverables (risk management policy and procedures, appetite statement, scoring criteria, risk register) and records produced by your systems (KRI measurements, breach notifications, control self-assessment results, committee resolutions) are brought into Ahura.
  2. Kept: Ahura is 100% on-premises; client documents and data never go to the cloud or leave the client environment. Board-level risk data is highly sensitive business information in its own right.
  3. Signed: a full-process evidence chain records every sign-off — policy approval, appetite approval, breach handling — and is compatible with EU eIDAS certificates. This matches Article 26 of the Principles, which calls for records to be kept, reviewed, reported and retained for inspection.
  4. Retrieved: internal audit, external auditors or regulators retrieve evidence from one place.

A group-style distributed architecture lets headquarters set one risk policy and appetite while each site complies locally; the interface supports Traditional Chinese, English and EU languages such as German, French, Dutch and Czech, which suits groups with European sites.

To be clear: an ERM-specific module is planned under the modular extension design; for now the focus is the evidence chain, sign-off and on-premises retention. Gap analysis from uploaded documents, cross-standard comparison and regulatory change tracking (monitoring EU and Taiwan regulatory developments) are in development and will open as the POC progresses.

Learn about the Ahura enterprise risk management platform

What verifiable governance, risk, efficiency and compliance gains does ERM integration produce?

ERM results should be more than "better risk awareness". We list only changes that can be checked after implementation:

  • Governance: the risk management policy and procedures are approved by the board (Principles Art. 13); the risk management committee reports to the board at least once a year (Art. 14); disclosures cover the three items of Art. 28 — policy and procedures, governance and organisational structure, and operations including the frequency and dates of reports to the board.
  • Risk: risk appetite has measurable limits; material risks have KRIs and thresholds with an escalation path for breaches; control effectiveness is tracked through KCIs rather than only the annual self-assessment.
  • Efficiency: security, business continuity and AI management systems share one set of scoring criteria and categories, so risk assessments are not redone; board reports are compiled automatically from the register and KRIs instead of from scratch each quarter.
  • Ongoing compliance: every approval, notification and treatment leaves a record and sign-off, meeting the retention expectation of Art. 26; review continues under ISO 31000 clause 6.6.

Metrics you can accept the work against include: share of material risks with KRIs, share of KRI breaches resolved within the deadline, on-time completion of treatment plans, number of controls failing their KCIs, and whether board risk reports are delivered on the scheduled dates.

VP- and director-level consultants lead the work end to end, never outsourced; our consultants hold ISO Lead Auditor qualifications. To find out which part your company should address first under the Principles, contact us.

Continuous assurance & trusted supply chain: ERM Internal Audit Outsourcing & Supplier Risk Audits

Technical integration for related services

Official sources

Ask a consultant on LINE

No forms: the button opens LINE with the page you are reading filled in. Send it and a Winners Consulting consultant will reply. The first diagnosis is free.

Winners Consulting track record

Winners Consulting Services is a Taiwan RegTech platform provider and enterprise risk management consultancy.

Trusted long-term by 20+ companies, we work as an industry-focused, long-term partner to our clients.

Named client engagements, published with client permission:

See case studies

ERM Technical Integration