Best practice Data Modelling?

Wed, 03 Jun 2015 11:05:40 GMT

Hello everyone!

I'm trying to set up a new QlikView Environment for a company manufacturing different parts.
QlikView will be used as their primary tool for analyzing quality assurance data, such as performance, stability etc.

I'm now in the good position that I may form their whole DWH setup and I want to make the best possible job for this.

I'm fairly new to QlikView however, and after reading some Best Practice Guides (this community seems to be really awesome), it seems that most examples are based on retail markets and such.

But to get to the point and my specific problem:

We have multiple production lines with different products, and within each line we have multiple testing stations that test different parts of our product.

F.E

Table Line1.S1.S

TIdent

Force_Target_Min

Force_Target_Max

Distance_Target_Min

Distance_Target_Max

Table Line1.S1.I

Ident

Date

TolIdent

ShiftIdent

SerialID

LastCycle

CycleTime

Cycle

Imported

Force_Actual

Distance_Actual

That's all the Data I get from 1 Station

However there are 5 other stations within that line, with over 7 other lines from which most are even bigger and deliver more data.

How should I group this?

My solution would be to create one QVD per Line. I understand that building the base for what we're trying to achive is going to take a while, but I think I'm missing something.

Any help regarding this is really appreciated.

Thank you!

Re: Best practice Data Modelling?

Thu, 04 Jun 2015 09:46:29 GMT

I've put more thought into this and first I'd like to share more Detail to the Situation atm.

Right now all the tables are based on single modules. A module could be f.e a testing Station, checking voltage, Rotation, or something like this.

A module is integrated into 1 Station

A Station is integrated into 1 production line.

So in conclusion: 1 Production line(no table) has multiple stations(no table). 1 Station has multiple modules.

With all the data being stored at the lowest Level, I'm thinking of creating 1 fact table for the production line to link module data through that table.
Does that make any sense or should I try another approach?

TYVM!

topic Best practice Data Modelling? in QlikView

Best practice Data Modelling?

Re: Best practice Data Modelling?