โมเดล SIPOC
SIPOC เป็นคำย่อมาจาก: Suppliers – Inputs – Process – Outputs – Customers
เป็นการระบุ กระบวนการทำงานในภาพใหญ่ ในรูปแบบตาราง ก่อนเริ่มเขียนแผนภาพ วัดผล หรือทำการพัฒนา
โดยมากใช้ในการพัฒนาหรือปรับปรุงกระบวนการทำงาน ตามแนวทาง TQM, Kaizen, Lean หรือ Six Sigma (define ใน DMAIC)
SIPOC จะใช้เมื่อมีความต้องการปรับปรุงกระบวนการทำงาน เพราะต้องเข้าใจขอบเขตของการทำงานก่อน
การทำ SIPOC จะทำให้เจ้าของกระบวนการและผู้ปฏิบัติงาน สามารถตกลงกันได้เป็นฉันทามติ ในเรื่องขอบเขตของงาน ว่ามีอะไร หรือส่วนใดมาเกี่ยวข้องด้วย ก่อนเขียนแผนภาพการทำงาน
ขั้นตอนการทำ:
1. ระบุชื่อกระบวนการ
2. ระบุผลลัพธ์ของกระบวนการ (เช่นรายงาน หรือหนังสือ)
3. ระบุลูกค้า (เป็นผู้รับผลงาน ทุกงานต้องมีผู้รับผลงานต่อ)
4. ระบุปัจจัยนำเข้า (สิ่งที่ทำให้กระบวนการเริ่มต้น เช่นคำร้องของลูกค้า)
5. ระบุผู้ส่งมอบปัจจัยนำเข้านั้น (ปัจจัยนำเข้าทุกชนิดต้องมีผู้ส่งมอบ บางครั้งผู้ส่งมอบและลูกค้าอาจเป็นบุคคลเดียวกันได้)
6. ระบุขั้นตอนย่อยของกระบวนการ (เป็นกิจกรรมที่เปลี่ยนปัจจัยนำเข้าเป็นผลผลิตของกระบวนการ)
SIPOC is a high-level picture of the process that depicts how the given process is servicing the customer. It is an acronym for Suppliers - Inputs - Process - Outputs - Customers.
The document discusses key concepts in process management including defining systems and processes. It provides examples of how to map processes using tools like SIPOC diagrams and flowcharts. The document emphasizes that determining customer requirements and designing processes to meet those requirements is important. Process management is about understanding how work gets accomplished and innovating systems and key processes to deliver value to customers.
The document discusses the differences between ISO/TS 16949 and QS-9000 quality standards for the automotive industry. It notes that ISO/TS 16949 has fewer registrars and aims for a more process-based audit approach compared to QS-9000. Key differences highlighted include strengthened product realization integration, additional supplier development requirements, and new organization performance metrics. The ISO technical committee views ISO/TS 16949 as improving oversight of certification bodies and helping marginal organizations through its emphasis on process audits over checklists.
โมเดล SIPOC
SIPOC เป็นคำย่อมาจาก: Suppliers – Inputs – Process – Outputs – Customers
เป็นการระบุ กระบวนการทำงานในภาพใหญ่ ในรูปแบบตาราง ก่อนเริ่มเขียนแผนภาพ วัดผล หรือทำการพัฒนา
โดยมากใช้ในการพัฒนาหรือปรับปรุงกระบวนการทำงาน ตามแนวทาง TQM, Kaizen, Lean หรือ Six Sigma (define ใน DMAIC)
SIPOC จะใช้เมื่อมีความต้องการปรับปรุงกระบวนการทำงาน เพราะต้องเข้าใจขอบเขตของการทำงานก่อน
การทำ SIPOC จะทำให้เจ้าของกระบวนการและผู้ปฏิบัติงาน สามารถตกลงกันได้เป็นฉันทามติ ในเรื่องขอบเขตของงาน ว่ามีอะไร หรือส่วนใดมาเกี่ยวข้องด้วย ก่อนเขียนแผนภาพการทำงาน
ขั้นตอนการทำ:
1. ระบุชื่อกระบวนการ
2. ระบุผลลัพธ์ของกระบวนการ (เช่นรายงาน หรือหนังสือ)
3. ระบุลูกค้า (เป็นผู้รับผลงาน ทุกงานต้องมีผู้รับผลงานต่อ)
4. ระบุปัจจัยนำเข้า (สิ่งที่ทำให้กระบวนการเริ่มต้น เช่นคำร้องของลูกค้า)
5. ระบุผู้ส่งมอบปัจจัยนำเข้านั้น (ปัจจัยนำเข้าทุกชนิดต้องมีผู้ส่งมอบ บางครั้งผู้ส่งมอบและลูกค้าอาจเป็นบุคคลเดียวกันได้)
6. ระบุขั้นตอนย่อยของกระบวนการ (เป็นกิจกรรมที่เปลี่ยนปัจจัยนำเข้าเป็นผลผลิตของกระบวนการ)
SIPOC is a high-level picture of the process that depicts how the given process is servicing the customer. It is an acronym for Suppliers - Inputs - Process - Outputs - Customers.
The document discusses key concepts in process management including defining systems and processes. It provides examples of how to map processes using tools like SIPOC diagrams and flowcharts. The document emphasizes that determining customer requirements and designing processes to meet those requirements is important. Process management is about understanding how work gets accomplished and innovating systems and key processes to deliver value to customers.
The document discusses the differences between ISO/TS 16949 and QS-9000 quality standards for the automotive industry. It notes that ISO/TS 16949 has fewer registrars and aims for a more process-based audit approach compared to QS-9000. Key differences highlighted include strengthened product realization integration, additional supplier development requirements, and new organization performance metrics. The ISO technical committee views ISO/TS 16949 as improving oversight of certification bodies and helping marginal organizations through its emphasis on process audits over checklists.
This document provides an overview of business process management and process mapping. It discusses why organizations should shift from a functional view to a process view. The key aspects covered include:
- Explaining the difference between functional management and business process management
- Discussing the types of business processes like core, key sub, and enabling processes
- Outlining the 7 steps to process mapping like determining boundaries, listing steps, and finalizing the flowchart
- Providing examples of process mapping for order entry and manufacturing
- Discussing how to identify inputs, outputs, and classify variables in a 6 Sigma process mapping approach
The document advocates that organizations should understand customer-centric processes rather than individual functions in order
Presented by Netlighter Till Krullmann at the first Edge X event in Berlin. Till goes through what it takes to implement devops in your business from strategic value to who and how to hire.
DevOps in the Amazon Cloud – Learn from the pioneersNetflix suroGaurav "GP" Pal
DevOps helps accelerate the delivery of software applications through automation and by removing Development & Operations silos. The Netflix Platform Engineering team has developed a robust data pipeline solution called SURO that has been open sourced. Come learn from the experiences of pioneers like Netflix how they are leveraging the data pipeline for new and innovative use cases. This is the presentation by Danny Yuan, Netflix Platform Engineering Team on operational and monitoring aspects of applications on cloud platforms.
This document discusses the need for continuous delivery in software development. It defines continuous delivery as making sure software can be reliably released at any time. The document outlines some key aspects of continuous delivery including automated testing, infrastructure as code, continuous integration, and blue/green deployments. It provides an example of implementing continuous delivery for a large retail company using tools like Jenkins, Puppet, Logstash and practices like infrastructure as code and automated testing.
This document discusses using games to teach Agile concepts in a hands-on way. It introduces several games that have been used successfully for Agile training, including the Snow Flake game for teaching Lean Startup concepts, the Ball Point game for continuous improvement, the Flow game for limiting work-in-progress, and the Kanban game for the Kanban methodology. These games make complex Agile ideas more concrete and accessible while adding an engaging, fun element to training. The document advocates for hands-on learning through games and sharing experiences using various Agile games for training with startups, students, and enterprises.
DevOps aims to bridge the gap between development and operations by fostering collaboration. Key aspects of DevOps include establishing a collaborative culture through open communication and engagement between teams, automating processes like builds, deployments, testing and system configuration, and implementing monitoring of applications and infrastructure through metrics and logging to ensure stability and enable issues to be quickly identified and addressed. Tools like Puppet, Munin, Graphite, Logstash and Graylog can help operationalize these aspects of DevOps.
This document explains risk-based thinking as established in ISO 9001:2015. It defines risk-based thinking as a systematic approach to identifying, considering, and controlling risks throughout a quality management system. The revision builds risk-based thinking into the entire system rather than treating prevention as a separate component. Risk-based thinking involves identifying risks and opportunities, understanding their impacts, planning actions to address risks, implementing plans, checking effectiveness, and improving based on experience. The document provides examples and guidance on applying risk-based thinking to establish a proactive culture of continuous improvement.
The Rise of the Container: The Dev/Ops Technology That Accelerates Ops/DevRobert Starmer
This document discusses the rise of containers and their use with OpenStack. It defines containers as a lightweight virtualization method using namespaces and cgroups for process isolation. Containers accelerated DevOps by allowing developers to build applications in the same environment from development to production. While containers simplified deployment, they still require management at scale. The document outlines using containers on OpenStack via VMs or bare metal. It also discusses running OpenStack as containers and related projects like Magnum, Murano, HEAT, Higgins, Kuryr, and Kolla that integrate containers and OpenStack.
This document provides an introduction to continuous integration using Jenkins. It discusses installing Jenkins and PHP tools like xUnit and Clover PHP. It demonstrates how to set up plugins for Git, code quality plugins like PMD and Checkstyle, and templates for PHP projects. Benefits of continuous integration mentioned include quick feedback, automation, and metrics that increase confidence. Links are provided for rating the talk, slides, code examples, and following the author on Twitter and blog.
This document provides an overview of business process management and process mapping. It discusses why organizations should shift from a functional view to a process view. The key aspects covered include:
- Explaining the difference between functional management and business process management
- Discussing the types of business processes like core, key sub, and enabling processes
- Outlining the 7 steps to process mapping like determining boundaries, listing steps, and finalizing the flowchart
- Providing examples of process mapping for order entry and manufacturing
- Discussing how to identify inputs, outputs, and classify variables in a 6 Sigma process mapping approach
The document advocates that organizations should understand customer-centric processes rather than individual functions in order
Presented by Netlighter Till Krullmann at the first Edge X event in Berlin. Till goes through what it takes to implement devops in your business from strategic value to who and how to hire.
DevOps in the Amazon Cloud – Learn from the pioneersNetflix suroGaurav "GP" Pal
DevOps helps accelerate the delivery of software applications through automation and by removing Development & Operations silos. The Netflix Platform Engineering team has developed a robust data pipeline solution called SURO that has been open sourced. Come learn from the experiences of pioneers like Netflix how they are leveraging the data pipeline for new and innovative use cases. This is the presentation by Danny Yuan, Netflix Platform Engineering Team on operational and monitoring aspects of applications on cloud platforms.
This document discusses the need for continuous delivery in software development. It defines continuous delivery as making sure software can be reliably released at any time. The document outlines some key aspects of continuous delivery including automated testing, infrastructure as code, continuous integration, and blue/green deployments. It provides an example of implementing continuous delivery for a large retail company using tools like Jenkins, Puppet, Logstash and practices like infrastructure as code and automated testing.
This document discusses using games to teach Agile concepts in a hands-on way. It introduces several games that have been used successfully for Agile training, including the Snow Flake game for teaching Lean Startup concepts, the Ball Point game for continuous improvement, the Flow game for limiting work-in-progress, and the Kanban game for the Kanban methodology. These games make complex Agile ideas more concrete and accessible while adding an engaging, fun element to training. The document advocates for hands-on learning through games and sharing experiences using various Agile games for training with startups, students, and enterprises.
DevOps aims to bridge the gap between development and operations by fostering collaboration. Key aspects of DevOps include establishing a collaborative culture through open communication and engagement between teams, automating processes like builds, deployments, testing and system configuration, and implementing monitoring of applications and infrastructure through metrics and logging to ensure stability and enable issues to be quickly identified and addressed. Tools like Puppet, Munin, Graphite, Logstash and Graylog can help operationalize these aspects of DevOps.
This document explains risk-based thinking as established in ISO 9001:2015. It defines risk-based thinking as a systematic approach to identifying, considering, and controlling risks throughout a quality management system. The revision builds risk-based thinking into the entire system rather than treating prevention as a separate component. Risk-based thinking involves identifying risks and opportunities, understanding their impacts, planning actions to address risks, implementing plans, checking effectiveness, and improving based on experience. The document provides examples and guidance on applying risk-based thinking to establish a proactive culture of continuous improvement.
The Rise of the Container: The Dev/Ops Technology That Accelerates Ops/DevRobert Starmer
This document discusses the rise of containers and their use with OpenStack. It defines containers as a lightweight virtualization method using namespaces and cgroups for process isolation. Containers accelerated DevOps by allowing developers to build applications in the same environment from development to production. While containers simplified deployment, they still require management at scale. The document outlines using containers on OpenStack via VMs or bare metal. It also discusses running OpenStack as containers and related projects like Magnum, Murano, HEAT, Higgins, Kuryr, and Kolla that integrate containers and OpenStack.
This document provides an introduction to continuous integration using Jenkins. It discusses installing Jenkins and PHP tools like xUnit and Clover PHP. It demonstrates how to set up plugins for Git, code quality plugins like PMD and Checkstyle, and templates for PHP projects. Benefits of continuous integration mentioned include quick feedback, automation, and metrics that increase confidence. Links are provided for rating the talk, slides, code examples, and following the author on Twitter and blog.