| 1. Identity statement | |||||||
| Reference Type | Conference Paper (Conference Proceedings) | ||||||
| Site | mtc-m16b.sid.inpe.br | ||||||
| Holder Code | isadg {BR SPINPE} ibi 8JMKD3MGPCW/3DT298S | ||||||
| Repository | dpi.inpe.br/ce@80/2007/01.16.17.27 (restricted access) | ||||||
| Last Update | 2007:04.10.17.14.52 (UTC) administrator | ||||||
| Metadata Repository | dpi.inpe.br/ce@80/2007/01.16.17.27.41 | ||||||
| Metadata Last Update | 2021:02.03.17.57.14 (UTC) administrator | ||||||
| Secondary Key | INPE--PRE/ | ||||||
| Citation Key | PessôaLourAlve:2007:ApLePr | ||||||
| Title | An approach to lean product development planning  | ||||||
| Format | CD-ROM; On-line. | ||||||
| Year | 2007 | ||||||
| Access Date | 2024, Apr. 27 | ||||||
| Secondary Type | PRE CI | ||||||
| Number of Files | 3 | ||||||
| Size | 567 KiB | ||||||
| 2. Context | |||||||
| Author | 1 Pessôa, Marcus Vinicius Pereira 2 Loureiro, Geilson 3 Alves, João Murta | ||||||
| Resume Identifier | 1 2 8JMKD3MGP5W/3C9JH57 | ||||||
| Group | 1 2 LIT-INPE-MCT-BR | ||||||
| Affiliation | 1 Departamento de Controle do Espaço Aéreo - DECEA 2 Instituto Nacional de Pesquisas Espaciais - INPE 3 Instituto Tecnológico de Aeronáutica | ||||||
| Author e-Mail Address | 1 mvppessoa@gmail.com 2 geilson@lit.inpe.br 3 murta@ita.br | ||||||
| Editor | Loureiro, Geilson Curran, Ricky | ||||||
| e-Mail Address | mvppessoa@gmail.com | ||||||
| Conference Name | ISPE International Conference on Concurrent Engineering, 14 (CE 2007). | ||||||
| Conference Location | São José dos Campos | ||||||
| Date | 2007, July 16-20 | ||||||
| Publisher | Instituto Nacional de Pesquisas Espaciais (INPE) | ||||||
| Publisher City | São José dos Campos | ||||||
| Pages | 223-231 | ||||||
| Book Title | Proceedings | ||||||
| Organization | Instituto Nacional de Pesquisas Espaciais (INPE) | ||||||
| History (UTC) | 2007-03-07 15:19:20 :: mvppessoa@gmail.com -> ce2007 :: 2007-03-29 12:42:14 :: ce2007 -> mvppessoa@gmail.com :: 2007-04-10 18:24:53 :: mvppessoa@gmail.com -> ce2007 :: 2007-04-12 21:44:13 :: ce2007 -> administrator :: 2007-05-18 15:21:20 :: administrator -> ce2007 :: 2007-05-21 19:34:36 :: ce2007 -> administrator :: 2007-12-04 15:45:55 :: administrator -> mvppessoa@gmail.com :: 2007-12-04 19:49:57 :: mvppessoa@gmail.com -> marciana :: 2007-12-06 12:02:00 :: marciana -> administrator :: 2021-02-03 17:57:14 :: administrator -> marciana :: 2007 | ||||||
| 3. Content and structure | |||||||
| Is the master or a copy? | is the master | ||||||
| Content Stage | completed | ||||||
| Transferable | 1 | ||||||
| Keywords | development planning product development lean philosophy | ||||||
| Abstract | A product development system (PDS) is based on two pillars: "do the thing right" and "do the right thing". While the former leads to operational efficiency and waste reduction, the latter guarantees the fulfillment of all stakeholders needs. On this context, Toyota's PDS has a superior performance. The lack of formalization of the Toyota PDS system, though, makes it difficult to replicate. Research on this system has resulted in the identification of several principles, tools and techniques, but did not present a way to make them systematic. This paper aims to propose and demonstrate a systematic way to make the lean engineering products development planning. The method allows the creation of an activity network, which provides at the same time value creation and waste reduction. To achieve this objective the method is divided into four processes: (1) Value determination: having the product vision as an input, this process defines the Value Breakdown Structure VBS. The VBS differs from the usual WBS, where the latter decompose the work, to make major project deliverables or perform project phases, into smaller and more manageable chunks, and the former deploys the stakeholders' value into unequivocal and verifiable parameters, called value items. (2) Set-based Concurrent Engineering SBCE prioritization: determines the most critical product modules or organizational processes, which will be developed through a set of alternatives. During SBCE, the development team does not establish an early system level design, but instead establishes sets of possibilities for each subsystem or process, many of which are carried far into the product and process design. (3) Pull events determination: No process along the value flow should produce an item, part, service or information without direct request from the following processes. The pull events arte associated to physical progress evidences (i.e., models, prototypes, start of production, etc.) and are important moments to knowledge capture. Differently from tall gates where information batches are created, pull events guarantee the value flow, make quality problems visible and create knowledge. (4) Value creation activities sequencing: the activities to be performed are defined and sequenced based on the pull events. This work consists of three parts: (1) the identification of the needs to the lean development planning; (2) the method conception; and (4) the method evaluation against the identified needs and improvement opportunities observed on an aerospace product development example. Conclusions are that the developed method: (1) fits the product development environment; (2) adheres to the lean principles; (3) faces the traditional planning deficiencies; (4) exploits the improvement opportunities from the studied example. | ||||||
| Area | ETES | ||||||
| Type | Concurrent innovative product engineering | ||||||
| Arrangement | An approach to... | ||||||
| doc Directory Content | access | ||||||
| source Directory Content |
| ||||||
| agreement Directory Content | there are no files | ||||||
| 4. Conditions of access and use | |||||||
| Language | en | ||||||
| Target File | paper.pdf | ||||||
| User Group | administrator marciana mvppessoa@gmail.com | ||||||
| Visibility | shown | ||||||
| Read Permission | deny from all and allow from 150.163 | ||||||
| 5. Allied materials | |||||||
| Next Higher Units | 8JMKD3MGPCW/444BQ9E | ||||||
| Host Collection | lcp.inpe.br/ignes/2004/02.12.18.39 cptec.inpe.br/walmeida/2003/04.25.17.12 | ||||||
| 6. Notes | |||||||
| Mark | 1 | ||||||
| Empty Fields | archivingpolicy archivist callnumber contenttype copyholder copyright creatorhistory descriptionlevel dissemination documentstage doi edition identifier isbn issn label lineage mirrorrepository nextedition notes numberofvolumes orcid parameterlist parentrepositories previousedition previouslowerunit progress project readergroup rightsholder schedulinginformation secondarydate secondarymark serieseditor shorttitle sponsor tertiarymark tertiarytype url versiontype volume | ||||||
| 7. Description control | |||||||
| e-Mail (login) | marciana | ||||||
| update | |||||||