Abstract
A major focus of many implementation discussions on Systems Engineering revolves around developing a large database of information, to be reused later, benefiting the company's product development process. Business needs for agile and flexible responses place pressure on the maintenance of the database during Sustaining Engineering of the product. The business needs of the product management functions are discussed to frame the problem of maintaining the Systems Engineering database. This paper focuses on the maintenance of the Systems Engineering database during Sustaining Engineering activities. The process for ensuring the 'Systems Engineering Documentation Set' is being kept current is analyzed and described. Experiences regarding the dynamics of a Matrix Organization for Sustaining Engineering are discussed.
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
