Link: http://www.etc-architect.com/?p=273
From ETC-Architect
I am not sure if you have worked on any global projects. I have worked on a lot and they usually show a key aspect where business, as well as application architecture is going wrong. Usually on a global project Business Architects will work on one country at time. When challenged to think more outside of small islands they say either its not their job, it does not work or that no one has done it before. Usually the last often is true (at least in the commercial sector) until an architect starts with it. The same is true for application architects.
Before going into a rather complex area such as a global HR schema, let me start with a simple example. If you look at https://en.wikipedia.org/wiki/Table_of_administrative_divisions_by_country you will see that the addresses and administrative functions are created very different in each country. You will also see that it is very easy to create a dynamic template where address validation can be done on a global level. The really strange thing however is that virtually all ERP systems and most global business processes and applications are still based on an individual country format.
As such it is always important for any architect to not only look at best practises or best business processes with the area he is investigating, but also on the potential globalisation of the area.
