HighCoordination’s Ralph Ginzinger chats about NodeGraph and data lineage
We spoke to Ralph Ginzinger, CEO of HighCoordination Schweiz about NodeGraph and data lineage. Enjoy the full interview.
“So I’m Ralph I’m with HighCoordination. I’m actually Managing Director and Chief of Operations for HighCoordination and I’ve been with and around Qlik for the last ten years – so I call myself a Qlik veteran so to speak.”
What was your first impression of NodeGraph?
“My first impression was okay, after five minutes of showing me, I said okay this is too good to be true because I’ve been looking for something like this for basically ten years.
And what you guys were showing is exactly what I was looking for – data lineage on field-level from one side to the other, customizable, easy to adapt and yeah. So my first impression was so positive that I was not trusting it to be working properly. And yeah, you promised and you delivered and we have been a happy partner ever since.”
You mentioned that you have been looking for a tool like this. Why?
“You get a question from the business how is this field calculated, are we directly sourcing this from SAP or is there any other file that we source in and do some workarounds? To answer this question in a basic or in an average application of ours took half an hour to an hour – opening all the scripts, going through, find, look at it, took forever.
The other way around – [within] impact analysis we get information that something in the source system is changing. What is impacted? Is it two applications, who should we contact, what do we need to prepare for, what’s the amount of work that’s coming up to us? This took so long that most of the time it was not even done. So there was a change in the ERP or in let’s say in the SAP field that we were using or in the table and there was just no impact analysis. So it was just changed in development and we just looked what failed afterward.
So what we can do now and [what] our customers can do that is they can just select whatever is changing and then see the flow through everything to the front-end.
That was the game-changer for us, especially in large installations. Of course, I mean the larger the company, the larger the installation, the more useful the product gets.”
Can you give us an example of NodeGraph in action?
What’s probably not so obvious in the beginning but we found a lot of positive feedback, or we collect a lot of positive feedback from our clients, is the knowledge sharing component of it. So in our setup, we as consultants often go to a customer, help them create the application, but we don’t run the application – for simple cost reasons. So what happens is when we hand over the application to the operations team, to the internal operations team, we have a hard time explaining what exactly happens within the application – what’s going on where.
So we use NodeGraph, also as a kind of knowledge transfer between teams to get them to know what’s happening – what data sources are affected, how is the transformation working.
So when a script is crashing, or when information is not recent, or not properly working the first address to go to is to NodeGraph and see ok, how is this application working in general, where’s the data coming from, what transformations are affecting the field that I’m having a problem with? And then I go into the script or to the data source.
If you are new to NodeGraph, first of all – welcome. We are a data quality platform for QlikView and Qlik Sense. To find out how we can help you take control of your data, get started today.