How to add #Erwin Extended Notes to a #PowerDesigner model

Recently I was looking at the list of new features in Erwin Data Modeler 2020, and one feature caught my eye – Extended Notes.

https://learndatamodeling.com/blog/new-features-in-erwin-release-2020-r1/

I knew that I could add a very similar feature to any object in PowerDesigner in less than 10 minutes, with absolutely no programming.

Here’s a simple Logical Data Model – the Entity “Contact Type” has four Extended Notes (one of those has its own Extended Note)

Here’s one of those notes. The properties are all standard, except for Status , Author, and Importance, which I defined in a Model Extension.

These Extended Notes can be compared and merged using the standard PowerDesigner Merge / Compare utility, and I can include them in Reports, List Reports, and Dependency Matrices

Want to see how it’s done? Watch this video.

To discuss how you can the best out of SAP PowerDesigner, go to www.metadatajunkie.wordpress.com/contact/

From ontology to data model, with the #PowerDesigner Glossary

The Glossary is one of the key enterprise resources provided by SAP PowerDesigner – it helps you capture and manage the terminology to be used when naming your models and objects in your models.

What if you want to use your Glossary in a different way – as an ontology? What if you want to use the Glossary to generate content in your models?

That’s exactly what I was asked recently – the good news is that PowerDesigner is designed to be extended. We can meet our objective in several ways:

  • write a script – Design and build all the logic yourself
  • define a simple ‘Object Generation’ – Simple to set up, limited in scope
  • define an ‘Extended Object Generation’ – Simple to set up, will need some scripting to tailor the results

I created a couple of demonstrations for my client, and decided to share them with the world via YouTube.

This video has three parts:

  • the Introduction at 00:22
  • a demonstration of the capabilities of a script at 06:21
  • a demonstration of Object Generation and Extended Object Generation at 08:48.

To discuss how you can the best out of SAP PowerDesigner, go to www.metadatajunkie.wordpress.com/contact/

When your processes or business rules aren’t up to the job, don’t blame the customer #BusinessRules

Defining and implementing processes and business rules can be a complicated task, as I know from years of experience of data and process modelling.  I’ve been on the receiving end of some incompletely-defined processes and business rules recently, and was made to feel as if it was my fault, and that’s not a good feeling.

This isn’t intended to be a rant against the supplier, though it’s very tempting to go on at length about what went wrong, the promises that were broken, and the amount of time we had to spend on the phone to get it sorted (at a cost of 5 pence per minute).

The topic is the unwritten assumptions that lie behind some process and business rules, and what happens when those assumptions prove to be false.

Here’s the scenario – a family have an integrated dishwasher, built-in to a line of cupboards in the kitchen. The dishwasher has a major fault, so the family decide to replace it, and order a new machine from the web site of one of the biggest electrical retailers in the country. The unusual step they take is to order a free-standing dishwasher to replace the existing integrated machine; they pay extra for the new machine to be installed, and for the old one to be removed.

Here’s the supplier’s description of the service that they paid for.

Insstalling free standing dishwashers

That’s a straightforward process – it says quite simply that they will install the new dishwasher and remove the old one. No conditions specified.

The following morning, the delivery / installation team turned up with the new dishwasher, took one look at the existing one, and refused to touch it. Apparently, removing and installing integrated dishwashers is the job of a specialist team, and it costs the customer a lot more money – 4.5 times as much for installation. The fact that they weren’t being asked to install an integrated dishwasher, just to disconnect it and take it away, was irrelevant.

The family were not impressed – the installation team promised to call the office when they had a mobile signal to arrange a visit by a suitably-qualified team, but the family left nothing to chance, and called Customer Support themselves straight away. They were promised a call back which never came, so they called again in the evening. During that call they were told about the additional cost for installing an integrated appliance, and accused of not reading the terms and conditions when they ordered the installation service. These are the terms and conditions shown above, the ones which don’t mention the assumption that the installers would be replacing like with like.

By the time the family made the evening call to Customer Support, they had discovered how to detach the integrated dishwasher – there were three screws attaching the dishwasher to the worktop, which took about a minute to remove. Now it’s no longer integrated, it’s free-standing; why didn’t the professional installers know how to do that?

If the family had ordered a new integrated appliance, here’s what the installation service would consist of.

Insstalling integrated dishwashers

Again, a straightforward process, and you can see the additional tasks necessary to remove and replace the plinth and the panel door. In the family’s case, none of these tasks were necessary, as they had already removed the plinth and didn’t want to keep the old panel door.

Anyway, as the dishwasher had been converted from ‘integrated’ to ‘free-standing’ by the family, the supplier agreed to honour the original installation agreement and send a new team of installers.

At the time of writing, the family are waiting for the installation team to arrive, with all fingers crossed.

What lessons are there in this unfortunate story, apart from making sure you become an expert in somebody else’s job before they turn up?

  • When defining business processes, document your assumptions, and work on the exceptions (use cases are a great technique for doing this)
  • Make sure that the affected parties (in this case, the customers paying for the service) are aware of the assumptions and exceptions – include them in the definition of the service, perhaps asking the customer to call Customer Support before placing an order if the assumptions aren’t true.
  • Make sure that Customer Support staff don’t blame the customer for the supplier’s own lack of information
  • Let installers use judgement –the original team could have worked out how to remove the existing machine if they’d looked at it instead of just saying “Not my job, mate”

Essential reading for data modellers – new book by Ross and Lam

Check the book reviews page for a review of a must-read volume for data modellers – “Building Business Solutions: Business Analysis with Business Rules” by Ron Ross and Gladys Lam.