LOGO

产品中心

/
/
/
Model Based Systems Engineering
1/1
浏览量:
1000

Model Based Systems Engineering

Teamcenter 中的系统驱动型产品开发 (SDPD) 融合了多领域产品开发(机械、电气和软件)以及成本、可靠性和工艺性等考虑事项。
1
产品描述

MBSE and SDPD bring together the cross-product lifecycle in Teamcenter

1

Model Based Systems Engineering

 

MBSE(基于模型的系统工程)是 Teamcenter® 产品生命周期管理 (PLM) 的关键部分。 我们用于实现 MBSE 的方法称作“系统驱动型产品开发 (SDPD)”,因为 Teamcenter 融合了多领域产品开发(机械、电气和软件)以及成本、可靠性和工艺性等考虑事项。 借助 Teamcenter,可以定义将要构建什么、指示员工如何去做,并协调下游开发过程;这些构成了维系整个跨产品生命周期的关键凝聚因素。

通过 SDPD,Teamcenter 可以掌握各个部分是如何配合工作,始终确保做出特定领域的决策时不会脱离大局。  该流程从定义需求、制定项目计划、运行整个产品架构流程、排除接口、设立目标/属性、识别技术风险以及建立/捕捉系统决策模型开始。 SDPD 推动了整个下游开发/交付流程,从而实现了工程在整个跨产品生命周期内的连续性。

MBSE is a critical part of the Teamcenter Systems Driven Product Development solution. Read more below.

Enterprise Model Management

 

目前我们正在通过 1D 模型生成产品内容,因此,作为产品模型管理目标的一部分,与 1D 模型保持同步与在构建产品时紧跟二维/三维模型同等重要。 从现在开始,我们需要认真对待这些 1D 模型。 Teamcenter 可以对 1D 模型以及其他产品模型进行高效管理,从而加快创新速度,更透彻地了解跨领域的数据和流程。

 

1
1

Product Architecture and System Modeling

 

PLM 带来的完整产品架构为所有下游产品生命周期学科建立了联系纽带,方便各学科展开通力合作。  借助 Teamcenter Systems Engineering 完整架构和系统建模功能,您可以获取产品生命周期中的产品架构数据,从而全面把握设计决策。 这样,产品生命周期中的各个领域(软件、电子、机械等)就可彼此衔接。

 

Technical Risk Management

 

Teamcenter MADe 产品线引入了基于模型的完整产品安全性和可靠性方法;这种方法为产品生命周期添加了可靠性建模,可预测可靠性问题,避免发生产品召回。 该方法使各组织得以弃用孤立的产品安全和可靠性分析流程(即隔离的 RAMS、相互脱节的 FMEA、故障树等),转而采用可靠性模型来主动影响产品开发,进而打造安全可靠的产品。

1
1

Change Management

 

With integrated MBSE, Systems Engineering components are included in the overall PLM process.  Requirements, functions, logical, physical, processes, interfaces, targets/parameters, and more can participate in standard change management practices either as a product architecture/system model change process or included in product level changes.   So, changes no longer have to be managed separately but can be included with global product change planning and management-—no more disconnects between product architecture and the current product baseline.


 

Product Requirements Engineering

 

The value of requirements isn't in capturing them, but in driving the product development process from the customer's perspective. Since requirements are a part of Teamcenter, you can allocate requirements to various downstream functions, features,  and product architectures (and vice versa) -- all while generating the reports, documentation, and dashboards to manage the requirements process. 

You can create, view and edit requirements directly from the web or familiar Microsoft Office applications, including Microsoft Word and Excel.

 

1

Program planning and systems engineering

 

Integrated program planning is driven by Systems Engineering architecture and requirement decisions. Resources, schedules, and more are committed by these decisions. Requirements, functions, interface definitions, etc. can be tied directly to program milestones and project tasks. Once established, as programs execute, requirements, functions, test cases, and resources have visibility into what needs to happen, when it needs to happen, potential issues, etc. allowing you to continuously assess program risk.

 

 

 
未找到相应参数组,请于后台属性模板中添加
暂时没有内容信息显示
请先在网站后台添加数据记录。
暂时没有内容信息显示
请先在网站后台添加数据记录。
搜索
搜索