SIPOC Methodology – A High-Level Process Map

The SIPOC methodology is one of the most useful concepts in the hand of a BPM expert. The idea behind the SIPOC methodology is to view each process as a different organization in itself. Each process therefore has its own suppliers, inputs and corresponding customers and outputs. The aggregation of all these processes is the system. This helps define each process with clarity. It also helps find what exactly is going wrong where.

For instance, if there is a system outage, then the process is not to blame. Corrective action must be taken to ensure that the infrastructure suppliers perform better. Here are some of the salient features of the SIPOC methodology.

High Level Process Map: A SIPOC methodology is in-effect a high level process map. It does not have details regarding who is supposed to be doing what. Rather it defines the working relationships between the various stakeholders. Some steps are required to effectively implement the SIPOC methodology. They are as follows:

Acquaint Suppliers: A large number of issues arise in the process because the suppliers are not well versed with the requirements. The suppliers could be internal or external to the organization but that is not the point of contention. The idea is orient the suppliers and make them aware of the rules, policies and procedures set for them. The Service Level Agreements must be explicitly stated to ensure that the suppliers know exactly what is expected of them.

Scheduling Inputs: Based on the negotiations and inputs from suppliers, one must carefully schedule inputs. Inputs can be in the form of men, money, material, machinery or information. The inputs must be provided to the process in the most optimum manner. There are many operations research techniques which can b e used in this regard to lower the cost levels and increase the service levels.

Process:

The SIPOC provided an effective methodology to get an in detail look at the process. Some things that are usually defined as the part of SIPOC are as follows:

• Boundaries: The process boundaries must be explicitly stated. Blurred boundaries lead to ambiguity which further leads to non performance of tasks.
• Sub Processes: The intermediate processes and inputs and outputs must be clearly defined as a part of the process definition.
• Process Owner: One person must be made accountable to see end to end execution of the process. This person will take care of any intermediate challenges that come in the way.

Outputs: Outputs must be expresses in terms of deliverables which can be verified. Therefore having outputs such as customer satisfaction is not correct. This can be the purpose of the process, however the output will be something like the best possible service (define using SLA) provided in the least possible time (Specify time in minutes). It is important to keep the outputs quantifiable because what cannot be measured cannot be managed.

Customer: The customer’s job is to consume the outputs of the process as well as provide feedback. The feedback could be related to the current performance of the process. It could also be regarding the future changes expected in the outputs of the process. For instance, the sales department is the customer of operations. They should communicate to operations if they see a period of slow sales so that production can be adjusted accordingly.