2026-09-19T14:40:07Zhttps://dspace.mit.edu/server/oai/request

oai:dspace.mit.edu:1721.1/447012022-01-13T07:55:19Zcom_1721.1_7582com_1721.1_7581col_1721.1_131023

Daniel Whitney and Maria Yang. Aquaro, Matthew System Design and Management Program. System Design and Management Program. 2009-03-16T19:31:30Z 2009-03-16T19:31:30Z 2008 2008 http://hdl.handle.net/1721.1/44701 297411209 Thesis (S.M.)--Massachusetts Institute of Technology, System Design and Management Program, 2008. Includes bibliographical references (p. 71). Product development in the automotive industry has evolved around the design of components. The organization is established around components and people have a very component centric perspective on problem solving. This has led to local optimization of individual components, while the larger system spirals out of control. The penalty is often measured in terms of development time and cost. New programs are given autonomy to make independent choices without regard for what other programs are doing, which leads to a wide variety of architectures put into place. Program managers and functional managers have different prioritizations. Furthermore, new designs are provided by a separate organization from the group responsible for implementation. They have a very different value system and are unaware of the difficulties experienced in the implementation phase. This type of practice leads to programs nearing production deadlines with poorly optimized systems. Engineers must relearn due to the lack of standardization across program. The team absorbs additional resources from within to fix issues prior to launch. The robbing of resources leads to delays in subsequent programs and the cycle repeats itself. These issues are partly cultural, part organizational, part due to lack of understanding of systems engineering. A new organization is designed, which strengthen the systems perspective and give power to a new role in the organization, the Systems Engineer. The Systems Engineer is chartered with global optimization of the entire system, which includes both functional aspects as well as business aspects like resource availability, development cost and time. They are responsible for developing the complete system, from concept to final implementation. The Design Structure Matrix (DSM) shows the boundaries of the system and reveals new areas where the Systems Engineer can influence the design at lower cost to the organization. (cont.) The Robustness Checklist, standardization and Systems Architecture provide Systems Engineers tools to change from a component mindset to a systems mindset and to optimize the system as a whole. by Matthew J. Aquaro. S.M. 71 p. eng Massachusetts Institute of Technology 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. http://dspace.mit.edu/handle/1721.1/7582 System Design and Management Program. Systems engineering in practice : the application of systems engineering principles to the development of a hydraulic control system for an automatic transmission Application of systems engineering principles to the development of a hydraulic control system for an automatic transmission Thesis application/pdf Publication unknown unknown <Publication xmlns="https://www.openaire.eu/cerif-profile/1.1/" id="b14a1bfe-e30e-448f-b67c-821ee64cd592"> <Type xmlns="https://www.openaire.eu/cerif-profile/vocab/COAR_Publication_Types">http://purl.org/coar/resource_type/c_1843</Type> <Language>eng</Language> <Title>Systems engineering in practice : the application of systems engineering principles to the development of a hydraulic control system for an automatic transmission</Title> <Subtitle>Application of systems engineering principles to the development of a hydraulic control system for an automatic transmission</Subtitle> <PublishedIn> <Publication> </Publication> </PublishedIn> <PublicationDate>2008</PublicationDate> <Authors> <Author> <DisplayName>Aquaro, Matthew</DisplayName> <Affiliation> <OrgUnit> </OrgUnit> </Affiliation> </Author> </Authors> <Editors> </Editors> <Publishers> <Publisher> <DisplayName>Massachusetts Institute of Technology</DisplayName> <OrgUnit /> </Publisher> </Publishers> <License>http://dspace.mit.edu/handle/1721.1/7582</License> <Keyword>System Design and Management Program.</Keyword> <Abstract>Product development in the automotive industry has evolved around the design of components. The organization is established around components and people have a very component centric perspective on problem solving. This has led to local optimization of individual components, while the larger system spirals out of control. The penalty is often measured in terms of development time and cost. New programs are given autonomy to make independent choices without regard for what other programs are doing, which leads to a wide variety of architectures put into place. Program managers and functional managers have different prioritizations. Furthermore, new designs are provided by a separate organization from the group responsible for implementation. They have a very different value system and are unaware of the difficulties experienced in the implementation phase. This type of practice leads to programs nearing production deadlines with poorly optimized systems. Engineers must relearn due to the lack of standardization across program. The team absorbs additional resources from within to fix issues prior to launch. The robbing of resources leads to delays in subsequent programs and the cycle repeats itself. These issues are partly cultural, part organizational, part due to lack of understanding of systems engineering. A new organization is designed, which strengthen the systems perspective and give power to a new role in the organization, the Systems Engineer. The Systems Engineer is chartered with global optimization of the entire system, which includes both functional aspects as well as business aspects like resource availability, development cost and time. They are responsible for developing the complete system, from concept to final implementation. The Design Structure Matrix (DSM) shows the boundaries of the system and reveals new areas where the Systems Engineer can influence the design at lower cost to the organization.</Abstract> <Abstract>(cont.) The Robustness Checklist, standardization and Systems Architecture provide Systems Engineers tools to change from a component mindset to a systems mindset and to optimize the system as a whole.</Abstract> <Access xmlns="http://purl.org/coar/access_right" > </Access> </Publication>