All Member Open Forum

Hi Alwaleed,

I would caution mixing the analysis/Display functionality and the work conduct. Dashboards are good for pulling information from a lot of sources and compiling them. When done well it can help drill down to some driving factors to guide next actions. To integrate the "doing work" part of this would be a significant system development, which might not be the best use of assets/resources.

Rather than focusing on a dashboard, I recommend focusing on where the data feeding the dashboard is being generated and standardize that first.  Rationale: a dashboard is only as good as its data. If there are structural issues with the data / compilation of the data then the dashboard reports will be fragile.

In the first  statement, you ask about having 1 place where all engineers can "do their work", what work are you referring to? FMEAs, FRACAS, Trend analysis, Statistical process control, Root cause analyses?

Regards,

Cerel

Hi Alwaleed,

I would caution mixing the analysis/Display functionality and the work conduct. Dashboards are good for pulling information from a lot of sources and compiling them. When done well it can help drill down to some driving factors to guide next actions. To integrate the "doing work" part of this would be a significant system development, which might not be the best use of assets/resources.

Rather than focusing on a dashboard, I recommend focusing on where the data feeding the dashboard is being generated and standardize that first.  Rationale: a dashboard is only as good as its data. If there are structural issues with the data / compilation of the data then the dashboard reports will be fragile.

In the first  statement, you ask about having 1 place where all engineers can "do their work", what work are you referring to? FMEAs, FRACAS, Trend analysis, Statistical process control, Root cause analyses?

Regards,

Cerel

Alwaleed, you said the purpose of the dashboard is "to give the engineers a one place where they can do all their work".  I'd like to re-frame this by suggesting that the dashboard is a place for the engineers to CHECK their work.  The dashboard should answer a simple question, "if the engineers were successful at executing their work, how would we know?"  

If this is what you're looking for, I could offer some useful suggestions.

Hi Alwaleed,

I would caution mixing the analysis/Display functionality and the work conduct. Dashboards are good for pulling information from a lot of sources and compiling them. When done well it can help drill down to some driving factors to guide next actions. To integrate the "doing work" part of this would be a significant system development, which might not be the best use of assets/resources.

Rather than focusing on a dashboard, I recommend focusing on where the data feeding the dashboard is being generated and standardize that first.  Rationale: a dashboard is only as good as its data. If there are structural issues with the data / compilation of the data then the dashboard reports will be fragile.

In the first  statement, you ask about having 1 place where all engineers can "do their work", what work are you referring to? FMEAs, FRACAS, Trend analysis, Statistical process control, Root cause analyses?

Regards,

Cerel

Alwaleed, you said the purpose of the dashboard is "to give the engineers a one place where they can do all their work".  I'd like to re-frame this by suggesting that the dashboard is a place for the engineers to CHECK their work.  The dashboard should answer a simple question, "if the engineers were successful at executing their work, how would we know?"  

If this is what you're looking for, I could offer some useful suggestions.

Hi Alwaleed,

I would caution mixing the analysis/Display functionality and the work conduct. Dashboards are good for pulling information from a lot of sources and compiling them. When done well it can help drill down to some driving factors to guide next actions. To integrate the "doing work" part of this would be a significant system development, which might not be the best use of assets/resources.

Rather than focusing on a dashboard, I recommend focusing on where the data feeding the dashboard is being generated and standardize that first.  Rationale: a dashboard is only as good as its data. If there are structural issues with the data / compilation of the data then the dashboard reports will be fragile.

In the first  statement, you ask about having 1 place where all engineers can "do their work", what work are you referring to? FMEAs, FRACAS, Trend analysis, Statistical process control, Root cause analyses?

Regards,

Cerel

Excellent.  I would enjoy that also.  I am able to meet you from around 16:00 Muscat time.  Please give me a day and time that suits you and I will send you a Teams invite.

Warmly,

Marc

Alwaleed, you said the purpose of the dashboard is "to give the engineers a one place where they can do all their work".  I'd like to re-frame this by suggesting that the dashboard is a place for the engineers to CHECK their work.  The dashboard should answer a simple question, "if the engineers were successful at executing their work, how would we know?"  

If this is what you're looking for, I could offer some useful suggestions.

Hi Alwaleed,

I would caution mixing the analysis/Display functionality and the work conduct. Dashboards are good for pulling information from a lot of sources and compiling them. When done well it can help drill down to some driving factors to guide next actions. To integrate the "doing work" part of this would be a significant system development, which might not be the best use of assets/resources.

Rather than focusing on a dashboard, I recommend focusing on where the data feeding the dashboard is being generated and standardize that first.  Rationale: a dashboard is only as good as its data. If there are structural issues with the data / compilation of the data then the dashboard reports will be fragile.

In the first  statement, you ask about having 1 place where all engineers can "do their work", what work are you referring to? FMEAs, FRACAS, Trend analysis, Statistical process control, Root cause analyses?

Regards,

Cerel

Excellent.  I would enjoy that also.  I am able to meet you from around 16:00 Muscat time.  Please give me a day and time that suits you and I will send you a Teams invite.

Warmly,

Marc

Alwaleed, you said the purpose of the dashboard is "to give the engineers a one place where they can do all their work".  I'd like to re-frame this by suggesting that the dashboard is a place for the engineers to CHECK their work.  The dashboard should answer a simple question, "if the engineers were successful at executing their work, how would we know?"  

If this is what you're looking for, I could offer some useful suggestions.

Hi Alwaleed,

I would caution mixing the analysis/Display functionality and the work conduct. Dashboards are good for pulling information from a lot of sources and compiling them. When done well it can help drill down to some driving factors to guide next actions. To integrate the "doing work" part of this would be a significant system development, which might not be the best use of assets/resources.

Rather than focusing on a dashboard, I recommend focusing on where the data feeding the dashboard is being generated and standardize that first.  Rationale: a dashboard is only as good as its data. If there are structural issues with the data / compilation of the data then the dashboard reports will be fragile.

In the first  statement, you ask about having 1 place where all engineers can "do their work", what work are you referring to? FMEAs, FRACAS, Trend analysis, Statistical process control, Root cause analyses?

Regards,

Cerel