Master reference data management
Implementing a service oriented architecture (SOA) also leads to the move to set up master reference data management services.I am sure that there are no real best practices around at the moment, so therefore this is a bit like exploring undiscovered territory. The big step is that you start to de-couple data from functionality. With other words - the management of data becomes a business process in itself.
So how do we get this done? Some people start straight away with developing the best possible data model, but I think that this is not a good idea. Don't develop a data model that would meet everybody's requirements from the start, but follow the steps, as laid out earlier in ... http://infomgr.blogspot.com/2007/06/data-management-fundamentals.html and the best is to start small. So in short do the following:
- Pin down the scope & keep this as small as possible to start
- Define the ownership, including the operational responsibilitie
- Define the process / data flow, including the operational roles
- Set up the data model & keep this as flexible
- Finally - set up the 'service'
The service itself should contain the following:
- The canonical data model + optionally the container for the data (and keep the scope limited to start!)
- A messaging service; to transport the ins/upd/del transactions
- A routing service; to move the data to the right place
- A key mapping service; to know how to translate keys, if required
- And optionally a user interface for power users
This all looks a bit daunting, but by starting small it is a feasible feat. Let's see if I can convince my colleagues of this wisdom as well!
Labels: master reference data, SOA
posted by Evert Ruijs @ 12:37 PM
0 Comments:
Post a Comment
<< Home