Continuous Improvement

Data- and processoptimalization 

Okay, we get some data in an application or viewer and we are missing some stuff. How is that possible? It was one of the source systems! The software works correctly and has no errors, all the unit states tested that. But where did the data go?

Setting up a process that will deliver the data which is needed in the end. So at the end of the process we start by analyzing what the demands on the data are. When we fully understand what is needed, we can look at the sources we have to determine if the data sources will be sufficient to deliver the demands. For this we can write test on the source that implement the demands on the end of the process. The data that isn’t sufficient will be reported and can be updated to meet the requirements.

The next step is to determine and design the steps that will be necessary to take to get to the end result. For each step we can report the data that came true or didn’t comply so that data can be upgraded to match the criteria the next time. When we look at this we already have the basics we need to fulfill the task. Very important is to know the status of the data in each step and report on it at the end of the process so the data owner knows what to do to correct it or state it as an expectance.

My experience is that the focus is mostly on the software and testing if that is working correct. But then you miss the most important thing in my and most of your profession’s, and that is the outcome of that piece of code. Does it help getting my data to meet the demands? So continuously testing my data and knowing the status of it quality and quantity wise will do the job for me.

Helping to get the result we need is mapping from begin to end with all objects and used attributes including transitional states. This gives insight in the states and where the data falls out the process.

If someone is triggered by this story and want to know more please contact me.