Business processes and integrated information systems
Why process thinking comes first
A business process is a set of linked activities that converts an input into an output of value to a customer. Information systems exist to make those processes faster, cheaper, more consistent or more visible. Candidates must be able to describe a process in terms of trigger, inputs, activities, decision points, controls and outputs, and to separate a functional view (what a department does) from a process view (how value flows end to end across departments).
Concepts to master
- Core vs support processes: core processes create customer value directly (order fulfilment, claims handling); support processes enable them (procurement, payroll, IT service management).
- Process hierarchy: value chain, then process group, then process, then activity, then task.
- Value stream mapping and swimlanes: show handoffs, queues and delays, which is where most waste sits.
- Process modelling notation: events, activities, gateways, pools and lanes. Know the difference between a parallel gateway (all paths run) and an exclusive gateway (one path chosen on a condition).
- Automation and control points: segregation of duties, approval limits, three-way match in purchasing, exception queues.
- Process performance measures: cycle time, throughput, first-time-right rate, cost per transaction, queue length.
Traps in questions
- Confusing a business process with an application. A single process usually spans several systems.
- Assuming automation always removes headcount. It often shifts effort to exception handling and monitoring.
- Treating a bottleneck as a capacity problem when it is a policy or approval problem.
- Forgetting that controls add cycle time; a question may ask for the control that minimises delay.
Worked rule of thumb
When asked where to improve a process, calculate the value-added ratio = value-added time divided by total lead time. For a supplied example of 10 minutes of work and 5 calendar days of 24 hours each, total lead time is 7200 minutes and the ratio is 10/7200, approximately 0.139 percent, so effort belongs on waiting time and handoffs, not on speeding up the 10 minutes of work.
An ERP system integrates related business functions using shared information and coordinated processes. A sales order can affect inventory, fulfillment and accounting records, but data consistency depends on process design, validation and access control. Integration is not a promise that all errors or organizational differences vanish. Master data such as product identifiers should be distinguished from transaction records. Evaluate a proposed improvement through the actual handoff, bottleneck, control objective and measured outcome rather than a product brand.