Transaction systems maintain synchronization of the stages of their execution sequences. That is a fact; otherwise users would never trust that the results of the process (think about it – you would not want to incur a service fee at your bank because your withdrawal was inadvertently processed before the
A way of paraphrasing what I suggested in my last post was that as master data practitioners, we are often focused too much on pulling data from source systems to populate a master entity model and not focused enough on understanding how dependencies across business processes may influence the proper
Yesterday was one of the two times a year that an equinox occurs. From its Latin roots, the term equinox translates as equal night since, on the day of an equinox, daytime and night are of approximately equal duration. This occurs because during an equinox the Sun is aligned with the center of the
Last time we looked at some of the benefits to be derived form managing the metadata associated with reference data. Practically speaking, the first step in managing the metadata for reference data is to identify which reference data domains exist and document how those domains are used. That suggests taking
In my last set of posts I started to look at some of the challenges associated with enterprise management of reference data domains, especially as the scope of use for the same conceptual reference domains expands across databases, systems, and functional areas within the organizations. Recognizing the value of capturing
In physics, antimatter has the same mass, but opposite charge, of matter. Collisions between matter and antimatter lead to the annihilation of both, the end result of which is a release of energy available to do work. In this blog series, I will use antimatter as a metaphor for a factor
A general paradigm for a master data management solution incorporates three operational components: An identity resolution engine. A master index. A master entity data repository. Conceptually, the identity resolution engine satisfies two core capabilities: the creation and management of unique identifiers associated with uniquely identified entities, and a matching capability
If you have been following this thread for a while, you may notice a theme that I keep bringing up: data virtualization. I'm trying to rectify a potential gap in the integration plan involving understanding the performance requirements for data access (especially when the application and database services are expected
To a great extent, the data manipulation layer of our multi-tiered master data services mimics the capabilities of the application services discussed in the previous posting. However, the value of segregating the actual data manipulation from the application-facing API is that the latter can be developed within the consuming application’s
Last time we started to discuss the strategy for applications to transition to using master data services. At the top of our master data services stack, we have the external- or application-facing capabilities. But first, let’s review the lifecycle of data about entities, namely: creating a new entity record, reading
