1977
DOI: 10.1080/00207547708943149
|View full text |Cite
|
Sign up to set email alerts
|

Toyota production system and Kanban system Materialization of just-in-time and respect-for-human system

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

6
558
0
40

Year Published

1994
1994
2016
2016

Publication Types

Select...
4
3
2

Relationship

0
9

Authors

Journals

citations
Cited by 1,065 publications
(631 citation statements)
references
References 0 publications
6
558
0
40
Order By: Relevance
“…Due to the sequencing constraints, the described problem is more complex than the multi travelling salesperson problem (MTSP) which is NP-complete [14]. Hence, being at least as hard as the MTSP, AGV routing problem is NPhard.…”
Section: Mathematical Modelmentioning
confidence: 99%
“…Due to the sequencing constraints, the described problem is more complex than the multi travelling salesperson problem (MTSP) which is NP-complete [14]. Hence, being at least as hard as the MTSP, AGV routing problem is NPhard.…”
Section: Mathematical Modelmentioning
confidence: 99%
“…The Toyota Production System enhanced the mass production paradigm of Fredrick Taylor and Henry Ford by adding an invariable customer perspective to all operations through the principles of just-in-time, jidoka, and waste elimination (Sugimori et al, 1977;Ohno, 1988).…”
Section: The Vrio-model Of Competitive Advantage Applied To Tpsmentioning
confidence: 99%
“…[17]. The core objective of the Kanban system is to minimise the amount of Work-InProgress (WIP), or inventory.…”
Section: Continuous Flowmentioning
confidence: 99%
“…For clarification, Table 4 shows a compilation of practices which have been categorised as having only lean origins [5]. Table 4 Lean (only) Software Development Practices  Jidoka (build quality in) [6]  Poka-Yoke (Defect detection and prevention) [9]  Kano analysis to link voice of the customer to requirements [40], [41]  Quality Function Deployment [41]  Value Stream Mapping [8], [6], [27], [42]  Transparency [8]  Make project status highly visible  Visualise all work items  Limit WIP (Work in Process), [43], [31]  Workload levelling "Heijunka" [6], [40]  Addressing bottlenecks [6], [44,45], [40], [27]  Deferring decision making [38], [27]  Moving variability downstream [27]  Reducing slack [22]  Measure and manage [46]  Employ Queuing Theory [25], [44,45] but measure the right things [11]  Employing Pull systems  Kanban, Limitied WIP, CONWIP (Sugimori et al, 1977;Bradley, 2007; Kniberg and Skarin, 2010), [31]  Batch control processing [47], [11]  Value stream Kaikaku [8]  Relentless reflection "Hansei" and continuous improvement "Kaizen" [6], [28],…”
Section: Agile and Lean Practicesmentioning
confidence: 99%