Sustainable IT Architecture
ABOUT - The Sustainable IT Architecture community is a neutral platform that rallies companies advocating a progressive restructuring of Information Systems to improve traceability and business governance of Reference/Master Data, Business Rules and key Processes. The community promotes a rating of Information Systems (IS Rating Tool) to evaluate enterprises on their abilities to manage the true value of their IS Assets: Reference and Master Data, Business Rules and Processes.
To achieve this goal, the Sustainable IT Architecture promotes an IS foundation based on a timely use of MDM, BRMS and BPM. Relying on a high level of matury, Master Data Management (MDM) and Business Rules Management System (BRMS) have already shown successes. Most importantly they do not require a big-bang approach, but progressive and planned change in compliance with Risk Management and IS Governance best practices such as CobiT, and programmes/projects management best practices such as CMMI.
Couping these repositories is decisive. Together they form the powerful concept called ACMS - Agility Chain Management System: no agile processes without agile rules, and no agile rules without a business management for Reference and Master Data. This is a chain of agility and traceability of Data, Business Rules and Processes. Each of these three would support advanced governance functions including Version Management, Rights Management, Traceability, Authoring, Querying, etc.
CIO's should focus on the management of core IS Assets based on Master Data (MDM), Business Rules (BRMS) and Processes (BPM)
"Today these assets are all too often hard-coded in Information Systems contributing to the level of opacity incompatible with the current need of the business both in terms of flexibility and visibility" sates Pierre Bonnet, founder of the Sustainable IT Architecture Community. Learn more.
Why should we continue to hard-code Master Data, Rules and Processes inside program codes and/or spreadsheets when we can establish MDM (Master Data Management), BRMS (Business Rules Management System) and BPM (Business Process Management) repositories? Maturity for these kinds of tools and methods are now enabling success, and it does not require a big-bang approach, but progressive and planned change in compliance with risk management.
Coupling these three repositories is decisive. Together they form the powerful concept called ACMS - Agility Chain Management System: no agile processes without agile rules, and no agile rules without a business management for reference data. Each of these three profits from advanced governance functions including version management, rights management, traceability management, authoring... of data, rules and processes. Find out more about the ACMS (Agility Chain Management System) foundation.
"Today these assets are all too often hard-coded in Information Systems contributing to the level of opacity incompatible with the current need of the business both in terms of flexibility and visibility" sates Pierre Bonnet, founder of the Sustainable IT Architecture Community. Learn more.
Why should we continue to hard-code Master Data, Rules and Processes inside program codes and/or spreadsheets when we can establish MDM (Master Data Management), BRMS (Business Rules Management System) and BPM (Business Process Management) repositories? Maturity for these kinds of tools and methods are now enabling success, and it does not require a big-bang approach, but progressive and planned change in compliance with risk management.
Coupling these three repositories is decisive. Together they form the powerful concept called ACMS - Agility Chain Management System: no agile processes without agile rules, and no agile rules without a business management for reference data. Each of these three profits from advanced governance functions including version management, rights management, traceability management, authoring... of data, rules and processes. Find out more about the ACMS (Agility Chain Management System) foundation.
Why should we continue to hard-code Master Data, Rules and Processes inside program codes and/or spreadsheets when we can establish MDM (Master Data Management), BRMS (Business Rules Management System) and BPM (Business Process Management) repositories?