Almost every session I'm in, explaining the power of Fact Modeling, there are questions on how to deal with different departments having an entity called "Customer" while they all mean something else, or use a different identification for it. This little article will show a possible verbalization for this issue.

Temporal modeling is a hot topic in data warehouse and BI environments. The data vault approach or anchor modeling are an attempt to make those environments more manageable. From the information modeling perspective however, these are technical in nature. Though the information model could capture those technical requirements, it would be an information model with an implementation in mind, and not simply capture the business communication. We would be modeling the data warehouse implementation itself and not the way the business communicates about their data.

July 2018

With the recent rush for GDPR compliance, we wanted to show you how simple the extension of new data model requirements can be in CaseTalk. It's a simple two step procedure to mark all elements sensitive to privacy violations as such. But first of all, the GDPR definition:


The General Data Protection Regulation (GDPR) (EU) 2016/679 is a regulation in EU law on data protection and privacy for all individuals within the European Union (EU) and the European Economic Area (EEA). It also addresses the export of personal data outside the EU and EEA areas. The GDPR aims primarily to give control to citizens and residents over their personal data and to simplify the regulatory environment for international business by unifying the regulation within the EU.

Superseding the Data Protection Directive 95/46/EC, the regulation contains provisions and requirements pertaining to the processing of personally identifiable information of individuals (formally called data subjects in the GDPR) inside the European Union, and applies to all enterprises, regardless of location, that are doing business with the European Economic Area. Business processes that handle personal data must be built with data protection by design and by default, ... [source: wikipedia]


Apr 2018

After having FCO-IM described on the English Wikipedia pages, we felt the need to also present this Dutch product on the Dutch Wikipedia pages. Please feel free to add your contributions to it.

In case you use Wikipedia, and like it to continue offering you content, please thank about making a small donation.

Februari 2016

We've added a new section in our website where you can freely study published models. Please have a look and share your own examples under the Create Commons License.


15 september 2014

BCP Software is proud to announce that as of this summer, Guido Bakema, emeritus professor at the HAN University of Applied Science, will act as ambassador for CaseTalk. In addition, Guido Bakema will offer advice on the development of CaseTalk in his own capacity. Both parties have recently agreed on all this.

June 2003

Bommeljé Crompvoets en partners b.v. (BCP) and Four Points signed a letter of intent to co-operate in the area of promoting CaseTalk, a case-tool based on the FCO-IM method, also known as Object Role Modelling or NIAM.

April 2003

Bommeljé Crompvoets en partners b.v. (BCP) and the Informatica Communicatie Academie of the HAN University have signed a contract to cooperate in the area of FCO-IM research and tool development. The contract is the next step in formalising co-operations and strengthening the FCO-IM foundations. (See also: Cooperation HAN and ICT-companies)

April 2003

On Friday April 11th 2003, Atos Origin, Bommeljé Crompvoets en partners b.v. (BCP) and the Informatica Communicatie Academie of the HAN University have signed a Letter of Intent to strengthen their cooperation. It describes a tripartite cooperation between parties to supply complete customer solutions for Metadata Management and Datawarehousing.