Click here to upload file | |
File Size: | 126 kb |
File Type: |
|
To enforce a better management of ERP upgrades, all customizations must be pushed to business repositories outside ERP, in other words within MDM, BRMS and BPM. To achieve this approach a Model-driven MDM must be deployed first. Software packages, such as ERP and CRM, are seen by the MDM as legacy systems. The shared data model managed at the level of the MDM defines all business data, regardless physical descriptions existing within ERP, CRM and other legacy systems. This is a Common Information Model. Obviously, when designing this model, Data Architects can benefit from existing data models within ERP to avoid a blank page effect. As is usual, the MDM repository is synchronized with ERP Reference and Master Data repositories either in a one-way communication and/or a bidirectional one, depending on requirements. The same approach must be applied at the level of Business Rules as well. Most of rules can be authored and executed within BRMS rather than hidden within rigid and opaque ERP customizations. To achieve that, two points must be ensured: - Mastering and governing shared data used by business rules: this is why you need to deploy MDM and Data Governance first. - ERP must allow to implement a communication with the BRMS, in other words relevant API and triggers must be published by software packages. Best practices exist to support and drive this architecture, including data modeling procedures to guarantee that the shared data model built for the MDM is fully reusable when Business Rules are added. A progressive and iterative development lifecyle is used to avoid a tunnel effect. To get more information about these best practices, please visit our sister community MDM Alliance Group. |
|