When we talk about multi-domain Master Data Management (MDM) we usually recognize party (customer, supplier, employee) and product as the most predominant domains. The location domain is also widely understood as a separate domain. Further we can discus about assets as done in the post Where is the Asset.
Then there is the Calendar domain. In many industries calendar may just be seen as configuration data. However, in some industries calendar is a true master data domain.
One example is in postal services as mentioned in the post The Path to Multi-Domain MDM.
Another example is public transit, an industry I have worked with in the last 16 years. Managing calendar data has many challenges in running a business or authority in public transit. Some tricky points are:
- Keeping track of day types where different partners sees the week and public holidays differently, not at least when crossing borders.
- Changing the day not necessarily at midnight, but at various times.
- Assigning and monitoring services to a schedule under these circumstances.
In public transit managing calendar data has the same issues as the other more common master data domains, as calendar data may be represented differently in applications across the IT landscape stretching from back-office systems to mobile devices on-board vehicles, as examined in the post Going in the Wrong Direction.