Sustainable IT Architecture
[Materials] [CEO and CIO] [ACMS] [ACMS and ERP] [MDM and BRMS] [Data Flow management] [Enterprise Architecture] [Assess your IS] [IS Governance] [Crisis] [Books]
Business Rules repository (BRMS) must be associated with Data repository (MDM)
Business Rules must be established without any hard-coding, including their Reference and Master data. This is not the case when using a BRMS without Master Data Management. In other words, when Reference and Master Data utilized by Business Rules are hard-coded and don't benefit from data governance features, then these Rules are not agile enough. They are too difficult to manage at the whole scale of the Information System: this is the BRMS failure when lacking Data Quality.
Business Rules must be established without any hard-coding, including their Reference and Master data. This is not the case when using a BRMS without Master Data Management. In other words, when Reference and Master Data utilized by Business Rules are hard-coded and don't benefit from data governance features, then these Rules are not agile enough. They are too difficult to manage at the whole scale of the Information System: this is the BRMS failure when lacking Data Quality.
BRMS failure when lacking Data Quality
When new Business Rules are authored within BRMS, IT specialists must either establish IT connectors from the BRMS to existing databases or copy Reference and Master Data values into the BRMS repository directly, with help from enumeration types and decision tables.
Unfortunately, these approaches are unsustainable because connectors are too complicated to maintain and data replication is not reliable. Then, the quality of Reference and Master Data is still reliant on the quality of existing systems, which is most of the time too poor.
Findings: Low Data Quality means low Business Rules quality!
When new Business Rules are authored within BRMS, IT specialists must either establish IT connectors from the BRMS to existing databases or copy Reference and Master Data values into the BRMS repository directly, with help from enumeration types and decision tables.
Unfortunately, these approaches are unsustainable because connectors are too complicated to maintain and data replication is not reliable. Then, the quality of Reference and Master Data is still reliant on the quality of existing systems, which is most of the time too poor.
Findings: Low Data Quality means low Business Rules quality!
Linking Value of "MDM and BRMS"
To take benefit from the BRMS at the whole scale of the IS, Master Data Management (MDM) must be established first.
The MDM provides companies with a central data repository managing Reference and Master Data. This solution enhances data quality and brings a full data governance: one version of the truth for Reference and Master Data, shared Common Information Model (CIM), data versioning, user friendly UI to author and check data by contexts (data may have several values according to contexts of utilization: versions, dates, organizations, channels, etc.), right and security, management, etc.
Once the MDM is ready to use, BRMS can be deployed with a single point of contact to retrieve Reference and Master Data utilized by rules. Moreover, with help from the context management featured by the MDM, Business Rules may handle different values of Reference and Master Data depending on contexts of execution (version, data, organization, channel…).
Findings: MDM leverages BRMS at the whole scale of information systems. Point-to-Point connections to get Reference and Master Data are no longer required.
To take benefit from the BRMS at the whole scale of the IS, Master Data Management (MDM) must be established first.
The MDM provides companies with a central data repository managing Reference and Master Data. This solution enhances data quality and brings a full data governance: one version of the truth for Reference and Master Data, shared Common Information Model (CIM), data versioning, user friendly UI to author and check data by contexts (data may have several values according to contexts of utilization: versions, dates, organizations, channels, etc.), right and security, management, etc.
Once the MDM is ready to use, BRMS can be deployed with a single point of contact to retrieve Reference and Master Data utilized by rules. Moreover, with help from the context management featured by the MDM, Business Rules may handle different values of Reference and Master Data depending on contexts of execution (version, data, organization, channel…).
Findings: MDM leverages BRMS at the whole scale of information systems. Point-to-Point connections to get Reference and Master Data are no longer required.
According to the ACMS foundation: no Processes (BPM) without Rules (BRMS) and no Rules without Reference and Master Data management (MDM).