ER/Studio conversion service for the FIB-DM Model is nearly ready #FIBO

The free version of the Financial Industry Business Data Model has been downloaded many times – it’s managed using the SAP PowerDesigner modelling tool, and users of other data modelling tools need to import the PowerDesigner Logical Data Model that is supplied. There are two concerns here:

  • FIB-DM is a very big model with some deep super/subtype hierarchies
  • even if your tool can import a PowerDesigner model, the chances are that the import doesn’t work perfectly

If your tool of choice is Idera ER/Studio Data Architect, you can use the built-in metadata import feature to import the PowerDesigner model, but I know that you won’t be happy with the result, so I’m building a new service to help you make the transition a happy one! In addition I’ll be providing some useful features for ER/Studio, similar to those in The CDM LDM Productivity model extension.

The left-hand side of the following image is the model created when you import the FIB-DM PowerDesigner model into ER/Studio Data Architect; the right-hand side is the model after it has been improved. Use the slider to see the difference!

You can see a couple of key differences here.

  • the PowerDesigner package hierarchy is flattened by the ER/Studio import, and all the package names have been changed. This is a big deal in a model with over 260 packages.
  • the fonts and line styles in the diagram need to be changed to make the diagram more readable. This is also a big deal, as there are over 260 diagrams.

There’s much more below the surface that needs to be fixed, such as:

  • the attachment names in the Data Dictionary
  • incorrect conversion of data types

I suspect that I have an advantage over most organisations that need an ER/Studio version of the FIB-DM model – I also have access to PowerDesigner. I can make changes to the FIB-DM model before importing it, such as renaming the packages using a bespoke model extension, then use a macro in ER/Studio to rename the resulting submodels. I can export details of the Attributes from PowerDesigner, and use that information to correct the data types in ER/Studio.

If you’re interested in finding out more about this new conversion service, please go to the contact page and get in touch.

An informal introduction to PowerDesigner Web – 30th of September, 2020

I’m keeping the numbers low for this session, partly to keep it informal, and partly due to platform limitations. I’m pleased to say that it’s now fully booked. I’m sure I’ll repeat it sometime in the near future.

PowerDesigner Web has been around for some time now, exposing the content of the PowerDesigner repository to a wider audience and giving users the ability to create and edit some types of model. With the introduction of PowerDesigner 16.7, the types of model that can be created and edited has grown, and has started to get George interested.

In this session, George  will take you through the background to PD Web and show you some of the interesting features he’s found, focusing mainly on the things you can do in PD Web that you can’t do in the PowerDesigner client application:

  • Reverse-engineering JSON documents and Schemas
  • Productivity aids when editing Conceptual and Physical Data Models
  • Structured data types in the Conceptual Data Model
  • Exporting a diagram to PowerPoint as symbols that can be individually edited
  • A new diagram in the Requirements Model
  • and more

Watch this space for news of the ER/Studio conversion service for the FIB-DM Model #FIBO

The free version of the Financial Industry Business Data Model has been downloaded many times – it’s managed using the SAP PowerDesigner modelling tool, and users of other data modelling tools need to import the PowerDesigner Logical Data Model that is supplied. There are two concerns here:

  • it’ s a very big model with some deep super/subtype hierarchies
  • even if your tool can import a PowerDesigner model, the chances are that the import doesn’t work perfectly

If your tool of choice is Idera ER/Studio Data Architect, you may be able to use the built-in metadata import feature to import the PowerDesigner model, but I know (because I’ve tried it) that you won’t be happy with the result, so I’m building a new service to help you make the transition a happy one! In addition I’ll be providing some useful features for ER/Studio, similar to those in The CDM LDM Productivity model extension.

That was a great presentation today at DAMA SA on “Semantics for Data Architects” with the FIB-DM model in PowerDesigner

It overran quite a lot today, but most people attending didn’t seem to mind. I’m talking about Jurgen Ziemer’s presentation for DAMA South Africa, talking about the FIB-DM data model he’s built from the FIBO ontology – you can see his presentation here. It’s a very large model, some of which is available for free – click on the Download link at https://fib-dm.com/ to ask for the free version.

The FIB-DM makes a lot of use of inheritance hierarchies, with some multiple inheritance in there as well, so it can take a while to get to grips with the model.

For example, I might be interested in knowing how the model handles Deposit Accounts. If I right-click the entity name in the object browser, I can use the context menu to find the diagram that contains the Deposit Account entity – it’s called “FIBO Finance, Business and Commerce – Products and Services, Clients and Accounts”, and it’s three levels down inside the package hierarchy within the model. Here’s what that diagram looks like – I’ve highlighted the Deposit Account entity:

The only diagram containing the Deposit Account entity

I can see that the entity is in one of those inheritance hierarchies, and that it’s got relationships to a couple of child entities. What I can’t see here are any connections to other objects that the modeller decided NOT to include on this diagram. That could be another parent or child entity, traceability links, or other relationships. What I’d like to see is a diagram that shows me the complete context for that entity – everything in the ‘proximity’ of the entity.

I could carefully work through the dependencies the entity has, and then select them for inclusion in a diagram, but I’d like a quicker way of doing it.

That’s where the CDM LDM Productivity model extension comes in – it can create that ‘Proximity’ diagram for me with a single click (I can also refresh it with a single click to make sure it’s up to date). Here it is:

Proximity diagram for Deposit Account

There isn’t much there that isn’t on the other diagram, just an extra parent entity – Banking Product. Crikey, that changes my understanding a little bit, I didn’t know about that, and I’d like to find out more. To start with, I’d like to see the inheritance hierarchies in more detail. This is also provided by the CDM LDM Productivity model extension – with one click I can create an Inheritance diagram for the entity, which can also be refreshed whenever I want:

Inheritance diagram for Deposit Account

I’ve hidden all the child entities from the diagram, as I’m primarily interested in the entity’s parentage – I can see that the entity is a great-grandchild of Product, and also a great-grandchild of Account.

These are just two of the features provided by the CDM LDM Productivity model extension – it also includes configurable naming standards, diagram completeness, and other features to improve the productivity of anyone working with Conceptual or Logical Data Models in PowerDesigner.