Pattern Based System Engineering (PBSE)- Product Lifecycle Management (PLM) Integration and Validation

dc.contributor.advisorEl-Mounayri, Dr. Hazim
dc.contributor.authorGupta, Rajat
dc.contributor.otherAgarwal, Dr. Mangilal
dc.contributor.otherLi, Dr. Shuning
dc.date.accessioned2018-01-29T19:08:40Z
dc.date.available2018-01-29T19:08:40Z
dc.date.issued2017-11-17
dc.degree.date2017en_US
dc.degree.disciplineMechanical Engineeringen
dc.degree.grantorPurdue Universityen_US
dc.degree.levelM.S.en_US
dc.descriptionIndiana University-Purdue University Indianapolis (IUPUI)en_US
dc.description.abstractMass customization, small lot sizes, reduced cost, high variability of product types and changing product portfolio are characteristics of modern manufacturing systems during life cycle. A direct consequence of these characteristics is a more complex system and supply chain. Product lifecycle management (PLM) and model based system engineering (MBSE) are tools which have been proposed and implemented to address different aspects of this complexity and resulting challenges. Our previous work has successfully implemented a MBSE model into a PLM platform. More specifically, Pattern based system engineering (S* pattern) models of systems are integrated with TEAMCENTER to link and interface system level with component level, and streamline the lifecycle across disciplines. The benefit of the implementation is two folded. On one side it helps system engineers using system engineering models enable a shift from learning how to model to implementing the model, which leads to more effective systems definition, design, integration and testing. On the other side the PLM platform provides a reliable database to store legacy data for future use also track changes during the entire process, including one of the most important tools that a systems engineer needs which is an automatic report generation tool. In the current work, we have configured a PLM platform (TEAMCENTER) to support automatic generation of reports and requirements tables using a generic Oil Filter system lifecycle. There are three tables that have been configured for automatic generation which are Feature definitions table, Detail Requirements table and Stakeholder Feature Attributes table. These tables where specifically chosen as they describe all the requirements of the system and cover all physical behaviours the oil filter system shall exhibit during its physical interactions with external systems. The requirement tables represent core content for a typical systems engineering report. With the help of the automatic report generation tool, it is possible to prepare the entire report within one single system, the PLM system, to ensure a single reliable data source for an organization. Automatic generation of these contents can save the systems engineers time, avoid duplicated work and human errors in report preparation, train future generation of workforce in the lifecycle all the while encouraging standardized documents in an organization.en_US
dc.identifier.doi10.7912/C27H3X
dc.identifier.urihttps://hdl.handle.net/1805/15094
dc.identifier.urihttp://dx.doi.org/10.7912/C2/2612
dc.language.isoenen_US
dc.subjectMBSE (Model Based System Engineering)en_US
dc.subjectPBSE (Pattern Based System Engineering)en_US
dc.subjectSystem Engineeringen_US
dc.subjectPLM (Product Lifecycle Management)en_US
dc.subjectTeamcenteren_US
dc.subjectIntegration and Validationen_US
dc.titlePattern Based System Engineering (PBSE)- Product Lifecycle Management (PLM) Integration and Validationen_US
dc.typeThesisen
Files
Original bundle
Now showing 1 - 1 of 1
Loading...
Thumbnail Image
Name:
Gupta_Rajat_Thesis.pdf
Size:
4.58 MB
Format:
Adobe Portable Document Format
Description:
Gupta_Rajat_Thesis
License bundle
Now showing 1 - 1 of 1
No Thumbnail Available
Name:
license.txt
Size:
1.99 KB
Format:
Item-specific license agreed upon to submission
Description: