The Blueprint for Lean IT Processes are a Lean / Just in Time Manufacturing Process.
The implications for IT architecture are:
1. Single Piece Flow.
a. A messaging architecture facilitates single piece flow.
b. Messages should be published as soon as they are available. No batch processes holding up messages.
2. Standard Parts to reduce complexity of process.
a. The Producer (Publisher) and the Consumer (Subscriber) should agree the specification of standard parts. A single process cannot specify a standard. All publishers and subscribers should agree the Common Messages critical features (Shape, Objects, Relationships).
3. No Batches.
a. No overnight batch processes. Assemble the parts when they arrive and pass them on to the next process. Do not assemble in batches.
4. No redundent Processes
a. Do not paint something before you know what colour the customer wants. Paint the part when needed, do not paint everything a common colour. Mapping of Cross Reference data should occur in the Subscribers.
5. Pull.
a. Build components on demand of the customer.
b. Combine standard parts just prior to the process that needs them assembled. Not before.
6. No Inventory.
a. No components (data warehouses, systems, functions) built in case someone might need it.
7. Do not pre-assemble parts. (No redundant processes).
a. This creates inventory of part assembled parts. These parts may need to be de-assembled into constituent parts to be used to assemble a separate product. Double muda!
8. Fix failures immediately otherwise flow is interrupted.
a. Monitor the entire process for failure on a real time basis. A single process to reconcile all sytems on a real time basis. Fix exceptions immediately. A realtime reconciliation system is required.
9. Focus on the Goal
a. Only measure of success is Business Value, i.e.
i. Protect / Increase P&L
ii. Protect / Increase ROI
iii. Improve / Protect Cash-Flow
b. Ensure localised performance measures do not focus on wrong goal.
c. Optimise the delivery of business value, not the local process.
d.Management by Constraint. Identify bottlenecks and plan around them to achieve flow.