My latest presentation is now available on BrightTalk. The talk is about how organisations can use SAP PowerDesigner to help them ensure that their Business Transformation is effective. I cover the following topics:
– 6 simple questions businesses need to provide the answers to form a framework for enterprise architecture
– How PowerDesigner supports Enterprise Knowledge and Enterprise Governance
– How SAP PowerDesigner provides the essential impact analysis
– Real-world examples of PowerDesigner use
SAP PowerDesigner allows users to build a blueprint of their current enterprise architecture and visualise the impact of change before it happens.
Here’s the link to the webinar – https://www.brighttalk.com/webcast/18335/434347
Discover the history and key capabilities of SAP PowerDesigner (it’s more than just a data modelling tool), and how it can make life easier for you in Data Governance and Database Development.
This session will show you why you must not use Excel or Visio for data modelling, and find out just how easy it is to get started with PowerDesigner.
Also discover the hidden power of PowerDesigner’s unique customisation capabilities, such as automating the creation of audit tables.
Wednesday June 10th, from 13:00 to 15:00 British Summer Time
(12:00 to 14:00 GMT)
The first online PowerDesigner training course was released recently, covering the Excel Import Wizard that is supplied with PowerDesigner. This allows you to import practically anything from Excel into any PowerDesigner model without writing a single line of code – if you want to import content into a type of model object or property that does not exist yet, it can even define them for you.
A Canadian customer was kind enough to say that the course easily justifies the cost:
“I found it extremely useful and became aware of a lot more functionality that I was not aware of around how Excel can be utilised within PowerDesigner. This will apply directly to the work that we are doing as it will allow us to get stakeholders to populate Excel templates that our data modeling team can then develop into actual PowerDesigner data models.“
To find out more about this training, see https://metadatajunkie.wordpress.com/online/
My friend Dirk Lerner is speaking at the IRM UK data management conference this week (it has a longer title, but I’ll avoid using it today) on topics that are close to my heart, so I thought I’d share some related connections. Dirk has three sessions this week –
- Data, Data, Metadata – DNA of Data Architecture?
- From Conceptual to Physical Data Vault Data Model
- Send Bi-Temporal Data from Ground to Vault to the Stars
Why am I so interested in these sessions (especially the first two)? The answer is simple – he’s discussing the combination of metadata and automation to improve the efficiency and efficacy of data modelling. This is a message I’ve been banging on about for years to anyone who will listen – data models are not ‘just documentation’, they’re an essential part of application development.
There are tools out there to help you with automating the development of Data Warehouses, including Data Vaults. Some are commercial products which you can buy with services, others are part of a consultancy package (so you buy the service, and they use the tools to provide the service). All of the consultancy examples I know of have extended a data modelling tool to provide the automation (they all use SAP PowerDesigner).
If you want to build your own automation, there is an initiative (led by Roelant Vos) to build a generic metadata interface for you to use when integrating tools – find out more at http://roelantvos.com/blog/a-collaboration-for-a-common-metadata-model/, and you can contribute to this effort at https://github.com/RoelantVos/Data_Warehouse_Automation_Metadata_Interface.
In my last blog post I described my new method for building scripts. Well, last week I delivered my first script to a client in France – it’s a script to import source-to-target mappings (otherwise known as Data Lineage) from Excel. The client has been relying on Excel to document the movement of data up to now, and that’s not a very good way of providing real data lineage that you can enquire on. By linking the PDMs together they’ll be able to construct much more effective data lineage in PowerDesigner.
Anyway, the client loved the script, once I’d made a couple of changes to allow for the fact that (unsurprisingly) they’re using the French version of PowerDesigner. Using my model-driven approach, it was simple for me to update the affected components and re-generate the complete script. Voila, as they say in France.