<?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet type="text/xsl" href="static/style.xsl"?><OAI-PMH xmlns="http://www.openarchives.org/OAI/2.0/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/ http://www.openarchives.org/OAI/2.0/OAI-PMH.xsd"><responseDate>2026-09-18T23:37:44Z</responseDate><request verb="GetRecord" identifier="oai:dspace.mit.edu:1721.1/35111" metadataPrefix="dim">https://dspace.mit.edu/server/oai/request</request><GetRecord><record><header><identifier>oai:dspace.mit.edu:1721.1/35111</identifier><datestamp>2022-01-13T07:55:19Z</datestamp><setSpec>com_1721.1_7582</setSpec><setSpec>com_1721.1_7581</setSpec><setSpec>col_1721.1_131023</setSpec></header><metadata><dim:dim xmlns:dim="http://www.dspace.org/xmlns/dspace/dim" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:doc="http://www.lyncode.com/xoai" xsi:schemaLocation="http://www.dspace.org/xmlns/dspace/dim http://www.dspace.org/schema/dim.xsd">
   <dim:field mdschema="dc" element="contributor" qualifier="advisor" lang="en_US">Daniel Whitney.</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="author" lang="en_US">Krishnaswami, Ram N. (Ram Narian)</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="other" lang="en_US">System Design and Management Program.</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="department" lang="en_US">System Design and Management Program.</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="accessioned">2006-12-18T20:42:26Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="available">2006-12-18T20:42:26Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="copyright" lang="en_US">2006</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="issued" lang="en_US">2006</dim:field>
   <dim:field mdschema="dc" element="identifier" qualifier="uri">http://hdl.handle.net/1721.1/35111</dim:field>
   <dim:field mdschema="dc" element="identifier" qualifier="oclc" lang="en_US">71437397</dim:field>
   <dim:field mdschema="dc" element="description" lang="en_US">Thesis (S.M.)--Massachusetts Institute of Technology, System Design and Management Program, 2006.</dim:field>
   <dim:field mdschema="dc" element="description" lang="en_US">Includes bibliographical references (p. 100-102).</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="abstract" lang="en_US">Organizations strive continuously to become efficient. Over the years many of them have tried to attain this through streamlining or reengineering their product development practices. 'While some of them succeed others are less successful. Product development organizations within automotive enterprises are not different in this regard. Most reengineering efforts seem to concentrate on tasks and schedule. Detailed schedules are cascaded while the identification of enablers on delivering to the new schedule is left to individual teams in the organization. At the working level, the reengineering process is misunderstood as abandonment of things gone right from past practices. This sometimes results in teams reinventing solutions to similar problems from the past. The purpose of this thesis is to demonstrate that a key enabler for success in any reengineering effort is to understand existing knowledge management practices and reuse them in the context of proposed changes. To do so, existing practices would have to be captured in usable formats. Proposed changes to existing product development process within an automotive product development organization are studied.</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="abstract" lang="en_US">(cont.) Comparisons are made between existing and proposed product development process. To focus this comparison and understand the changes better, the development tasks undertaken by a safety attribute team within the product development group is studied in detail. An analysis of the development process undertaken by the safety team to existing schedule is performed through case studies. Based on this analysis scenarios are developed for the proposed changes. From the case studies it is apparent that formalized knowledge management practices in formats usable by development teams will help in reducing iteration time through cascade of robust targets. Recommendations are made to build upon and sustain recently implemented knowledge management practices within the safety attribute team. An implementation roadmap for the new knowledge management frame work is provided.</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="statementofresponsibility" lang="en_US">Ram N. Krishnaswami.</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="degree" lang="en_US">S.M.</dim:field>
   <dim:field mdschema="dc" element="format" qualifier="extent" lang="en_US">102 p.</dim:field>
   <dim:field mdschema="dc" element="format" qualifier="extent">6061312 bytes</dim:field>
   <dim:field mdschema="dc" element="format" qualifier="extent">6067619 bytes</dim:field>
   <dim:field mdschema="dc" element="format" qualifier="mimetype">application/pdf</dim:field>
   <dim:field mdschema="dc" element="format" qualifier="mimetype">application/pdf</dim:field>
   <dim:field mdschema="dc" element="language" qualifier="iso" lang="en_US">eng</dim:field>
   <dim:field mdschema="dc" element="publisher" lang="en_US">Massachusetts Institute of Technology</dim:field>
   <dim:field mdschema="dc" element="rights" lang="en_US">M.I.T. theses are protected by copyright. They may be viewed from this source for any purpose, but reproduction or distribution in any format is prohibited without written permission. See provided URL for inquiries about permission.</dim:field>
   <dim:field mdschema="dc" element="rights" qualifier="uri">http://dspace.mit.edu/handle/1721.1/7582</dim:field>
   <dim:field mdschema="dc" element="subject" lang="en_US">System Design and Management Program.</dim:field>
   <dim:field mdschema="dc" element="title" lang="en_US">Knowledge management practices in automotive safety attribute development</dim:field>
   <dim:field mdschema="dc" element="type" lang="en_US">Thesis</dim:field>
   <dim:field mdschema="dc" element="format" qualifier="mimetype">application/pdf</dim:field>
   <dim:field mdschema="dspace" element="authorsordered">false</dim:field>
   <dim:field mdschema="dspace" element="entity" qualifier="type">Publication</dim:field>
   <dim:field mdschema="others" element="access-status">unknown</dim:field>
   <dim:field mdschema="others" element="access-status">unknown</dim:field>
   <dim:field mdschema="cerif" element="openaire" authority="" confidence="-1">&lt;Publication xmlns="https://www.openaire.eu/cerif-profile/1.1/" id="520511c5-d4b6-49ad-a415-85d8d9fb1648">
	&lt;Type xmlns="https://www.openaire.eu/cerif-profile/vocab/COAR_Publication_Types">http://purl.org/coar/resource_type/c_1843&lt;/Type>
	&lt;Language>eng&lt;/Language>
   	&lt;Title>Knowledge management practices in automotive safety attribute development&lt;/Title>
   	&lt;PublishedIn>
    	&lt;Publication>
      	&lt;/Publication>
   	&lt;/PublishedIn>
   	&lt;PublicationDate>2006&lt;/PublicationDate>
   	&lt;Authors>
      	&lt;Author>
        	&lt;DisplayName>Krishnaswami, Ram N. (Ram Narian)&lt;/DisplayName>
         	&lt;Affiliation>
         		&lt;OrgUnit>
         		&lt;/OrgUnit>
         	&lt;/Affiliation>
      	&lt;/Author>
	&lt;/Authors>
   	&lt;Editors>
	&lt;/Editors>
    &lt;Publishers>
        &lt;Publisher>
            &lt;DisplayName>Massachusetts Institute of Technology&lt;/DisplayName>
            &lt;OrgUnit />
        &lt;/Publisher>
    &lt;/Publishers>
    &lt;License>http://dspace.mit.edu/handle/1721.1/7582&lt;/License>
    &lt;Keyword>System Design and Management Program.&lt;/Keyword>
   	&lt;Abstract>Organizations strive continuously to become efficient. Over the years many of them have tried to attain this through streamlining or reengineering their product development practices. &amp;apos;While some of them succeed others are less successful. Product development organizations within automotive enterprises are not different in this regard. Most reengineering efforts seem to concentrate on tasks and schedule. Detailed schedules are cascaded while the identification of enablers on delivering to the new schedule is left to individual teams in the organization. At the working level, the reengineering process is misunderstood as abandonment of things gone right from past practices. This sometimes results in teams reinventing solutions to similar problems from the past. The purpose of this thesis is to demonstrate that a key enabler for success in any reengineering effort is to understand existing knowledge management practices and reuse them in the context of proposed changes. To do so, existing practices would have to be captured in usable formats. Proposed changes to existing product development process within an automotive product development organization are studied.&lt;/Abstract>
   	&lt;Abstract>(cont.) Comparisons are made between existing and proposed product development process. To focus this comparison and understand the changes better, the development tasks undertaken by a safety attribute team within the product development group is studied in detail. An analysis of the development process undertaken by the safety team to existing schedule is performed through case studies. Based on this analysis scenarios are developed for the proposed changes. From the case studies it is apparent that formalized knowledge management practices in formats usable by development teams will help in reducing iteration time through cascade of robust targets. Recommendations are made to build upon and sustain recently implemented knowledge management practices within the safety attribute team. An implementation roadmap for the new knowledge management frame work is provided.&lt;/Abstract>
	&lt;Access xmlns="http://purl.org/coar/access_right" 
    >
    &lt;/Access>
&lt;/Publication>
</dim:field>
</dim:dim>
</metadata></record></GetRecord></OAI-PMH>