How hands-on experience affects quality of final model.
Once a business user came to a BIM team member with a query regarding certain attribute. They wanted to know where the attribute came from because it is not possible to source it from any system. The BIM team member told him: “I do not care about data and how you source it. We put it there to make the model nicer.”
Business Information Modelling (aka BIM or Business Data Modelling) is a methodology we helped to create and develop. BIM is a foundation of the data intensive projects we deliver. Result of the modelling exercises is a glossary (often implemented utilising our Glossary) what then becomes the central point, the only source of truth for all further phases of the project including physical implementation of the data pumps, the data warehouse, the analytical engine etc.
The BIM phase of the project or programme is the most critical one. It sets up expectations of the business users, it defines terms and scope, it (from its nature) involves many business people and it is very intensive and there are usually many streams running in parallel. One of the challenges for the modelling team is to produce the model which could be easily used in following phases (source-to-target mapping, logical data modelling, development). And this usually creates conflict of interests. Business users wants to create a model which describes the business, is simple and generic enough to be able to accommodate all future changes, and do not take into consideration the pain of implementation of such model. On the other hand, people responsible for implementation don’t usually see overall picture and do not understand all nuances of the business processes, therefore they want precise, detailed and specific model.
Companies usually hire management and business consultancy companies because they rightfully expect these consultancies have experience and business consultants and analysts to help them. They usually hire different companies or utilise internal resources for the technical implementation. It might not be that obvious there can be a catch. The catch is hidden at the interface between the BIM team and the implementation teams. There can be a communication barrier between the parties, there can be also some time gap and there usually is lack of experience with technical implementation within the BIM team. It is usually much later in the process when implementation teams come up with questions about some specific issues, changes or requests for more details where the model is not clear or specific enough. It is quite often that the BIM team is long gone when this happens.
One of biggest advantages of Simplity is that we combine knowledge and experience from both worlds. It enables us to deliver high quality BIM because we took into consideration also the implementation because we understand that data must be sourced from somewhere, what customer unification means, and how the final report looks like. We never say “We do not care about source data”