Operations data environment
Operations is a big process (Our_Company.operations) which is composed of sub processes for inputs (materials, leads, orders, applications...), outputs (shipments, prescriptions, graduates, arrivals...) and production (assemble, underwrite, teach, build consist, emplane, deplane...).
Each of these process, in turn may be composed of sub processes. Each has inputs and outputs, many of which are data and all of which must meet certain specifications in order for the process to run smoothly and produce results of consistent quality.
Already you may be seeing a need to take action to make sure that the data required is pre-validated for each process. Clearly there is significant saving in non-productive time that could be realized. In fact, if you conduct an informal survey within your organization you will find that the people who are at the input point for your processes will claim that as much as 60% of their time is spent verifying data or fixing data problems.
If you dig deeper, you will find cases where processes continue, turning out defective product even when it is known that the product will have to be re-worked by someone else. Along with this, you may well find that the amount of time spent making sure that the process output meets the established specification is non-existent. When you recognize that this output becomes someone else's input the true scope of the cost to your company starts to come into focus.
When those involved in Process B begin to talk to those from Processes A and C, a community begins to form around common problems and solutions. This is a critical first step in quality management that will eventually lead to Data Management.
The best information for the best decision.