The Need For Data

By: Mauricio RIVERA — Posted 2021 Apr 16 under ARTICLES

We keep seeing buzzwords like BIG DATA and DATA SCIENCE in the news — but what data do we need in order to make better decisions?

Assigned Tags: Headline / Operations-Management /

In this — our first installment of our PRAGMATIC MANAGEMENT series — we discuss the various process and systems data types needed by organizations, and how this data can be used to make better decisions.

So we all know that you need data in order to manage processes and systems. Compliance data — in various forms, e.g. Weekly On Time Deliveries — is a basic metric used to check how well we (or our processes / systems) are performing. But surely there must be other, more compelling reasons as to why we need data.

Why do you need Data?
You need data in order to make Informed Decisions.

Any process or system that is not providing you with data is a blind spot — and thus, when problems arise with that process or system, or any other processes or systems they interact with, your actions will be more reactive or remedial; rather than preventive or predictive.

Many things that we take for granted these days — like weather predictions, GOOGLE MAPS / WAZE routes and arrival estimates — are only possible due to large amounts of analyzed data.

With enough data, you will be able to create models of the processes and systems you are studying, with potentially mind-blowing results. Predictions and trends can be determined, and actions to address expected issues can be taken — all before any issues arise.

Here is one example — the National Oceanic and Atmospheric Administration (NOAA) Forecast for Hurricane Laura. The NOAA forecast not only indicated the current location of Hurricane Laura (as of August 26, 7AM), but it then went on to indicate the expected path of the hurricane for the next five days.

Photo credit: NJ.com

With enough data, you will also be able to create data models of your processes and systems, and make similar mind-blowing analyses and predictions (like accurately predicting product sales for the next five days, and highlighting potential shortfalls in supplies on a per location basis), at a simple click of a button.

Processes and Systems can generate different types of data — not only data models — and these provide different insights into how the Processes and Systems are functioning. Let's quickly look at the various types of data we can gather and how they can be used to help make decisions.

Process and System Data Types

Noncompliance Data
  • Definition: Data on anything (e.g. input, process parameters, output) that did not meet defined specifications.
  • Examples: Failed deliveries / Rejected output / Customer complaints.
  • Main Use: To see problems / To determine problems that need action.
  • Other Uses: Can be used to (1) Trigger creation of Issue Reports (e.g. Problem Reports, Punchlists, Nonconformity Reports), (2) Trigger remedial or corrective actions, and; (3) Determine TOP 3 CONCERNS for priority actions.
Compliance Data
  • Definition: Data on anything (e.g. input, process parameters, output) that met defined specifications.
  • Examples: Successful (e.g. on-time) deliveries / Good output (as tested).
  • Main Use: To see good results or output / To determine if output(s) are meeting targets and objectives.
  • Other Uses: Can be used to (1) Generate Compliance Statistics for trend analysis, (2) Provide feedback when determining effectivity of remedial and corrective actions taken, and; (3) Determine TOP 3 COMPLIANT PROCESSES / SYSTEMS for best practice reviews.
Capability Data
  • Definition: Data on the process' (or system's) measured variability over a defined period of time — which can be used to determine its ability to meet defined specifications.
  • Examples: Potential Process Capability (Cp) and Actual Process Capability (Cpk).
  • Main Use: To see process abnormalities / To determine if any processes or systems need action / To determine trends and patterns via statistical methods.
  • Other Uses: Can be used to (1) Determine if Processes / Systems are in control 1 or are capable 2 (i.e. how well it is performing), (2) See if Process / System data is abnormal, (3) Determine if some actions need to be taken to (preventively) fix the process / system, (4) Generate MODELS of the Processes / Systems for predictive purposes, and; (5) Provide feedback when determining effectivity of preventive and predictive actions taken.

1 In Control means the process / system is free of assignable (special) causes, and is behaving as expected, based on analyzed data.
2 Capable means that the process / system is able to consistently and successfully meet defined specifications, based on analyzed data.

Efficiency Data
  • Definition: Key Process / System Input and Output data — which can be used to determine its efficiency converting input into output.
  • Examples: All data pertinent to defined LEAN WASTES, such as Activity Ratios (Value-added Time / Actual Time) / Inventory Turns / OTIF Deliveries / OEE
  • Main Use: To see opportunities for saving resources / To determine if any process or system wastes need action.
  • Other Uses: Can be used to (1) Determine and Reduce Operational Wastes — thus improving productivity and profitability, (2) Establish an appropriate PULL system to trigger workflows and tasks, (3) Trigger actions to preemptively address potential wastes (prior to the actual event), (4) Generate additional MODELS of the Processes / Systems for predictive purposes, (5) Provide feedback when determining effectivity of waste reduction actions taken, and which issues to prioritize, and; (6) Determine which products / services are consistently profitable.

Whenever we talk about using data for decision-making, it must be stressed that the data to be used must be of “ impeccable quality” — that is, we are confident that the data is correct, accurate, true and valid, and was gathered using the correct methodology.

On Data Integrity and Availability
Data Integrity 1 and Data Availability 2 are prerequisites for Timely and Informed Decisions.

1 Data Integrity = Ensuring that data is correct / valid / gathered properly
2 Data Availability = Ensuring that data can be accessed by authorized parties when they need it, in the format needed.

After ensuring that the data is fit for use, we must then ensure it is available for use by authorized parties (in the required form or format) when needed.

The Process and System Data Types (i.e. Noncompliance / Compliance / Capability / Efficiency) above also reflect the general stages (i.e. changes in focus and priorities) that data management programs go through, over time. Each data type is a prerequisite for the succeeding type, thus ensuring the natural progression through the stages.


Photo credit: Army Staff Sgt. Brendan Stephens (Public Domain via Wikimedia Commons)Server Wire connections


During the initial phases of implementing a data management system, data gathered focuses more on non-compliance and compliance to requirements. As the data management system matures (and the data management efforts gain support from management and stakeholders), it moves on to gathering data on process and system capability — for use in appropriate improvement efforts.

At this stage, data management starts relying on statistical techniques in order to make sense out of the chaos and amount of data available. Various statistical techniques can be used to analyze data, and reveal insights that are not visible to the naked eye — like Process mean and standard deviation, correlations between variables and Process Capability indices. These insights are the basic building blocks for building process capability and efficiency.

Then, after building up enough expertise in providing the required capability data, focus is then moved to providing the efficiency data needed to support the waste reduction programs of the organization.

At some point in time, the data management system will then start looking outward — towards customer / supplier / stakeholder data — as these will become more important (especially when making Strategic Decisions) to the organization as it grows larger, and its processes and systems mature.

Conclusion

Since decision making drives the need for data, the data needs of an organization are (by nature) tightly interconnected with its current concerns and challenges.

Evaluating your organizations' systems and processes — and determining current challenges — will allow you to define and establish a data management system that addresses your needs directly. Focusing on data that does not address your current needs or match your maturity level will not be productive — as the data provided will either not be actionable (or appropriate) at that point in time.

As processes and systems mature, so must the data management systems, evaluation techniques, managers and employees needed to support them and implement them.

Building up and improving data systems require time, money, knowledge, manpower and most of all; commitment — but properly implemented and maintained data management systems will provide benefits that far outweigh any investments made — either in the form of reduced problems, increased customer + stakeholder satisfaction, increased market share and / or bottom-line profitability.