OMG SysML™ is a modeling language for specifying, analyzing, designing, and verifying complex systems. It is a general‐purpose graphical modeling language with computer‐sensible semantics. This Part 1 paper and its Part 2 companion show how SysML supports simulation‐based design (SBD) via tutorial‐like examples. Our target audience is end users wanting to learn about SysML parametrics in general and its applications to engineering design and analysis in particular. We include background on the development of SysML parametrics that may also be useful for other stakeholders (e.g, vendors and researchers). In Part 1 we walk through models of simple objects that progressively introduce SysML parametrics concepts. To enhance understanding by comparison and contrast, we present corresponding models based on composable objects (COBs). The COB knowledge representation has provided a conceptual foundation for SysML parametrics, including executability and validation. We end with sample analysis building blocks (ABBs) from mechanics of materials showing how SysML captures engineering knowledge in a reusable form. Part 2 employs these ABBs in a high diversity mechanical example that integrates computer‐aided design and engineering analysis (CAD/CAE). The object and constraint graph concepts embodied in SysML parametrics and COBs provide modular analysis capabilities based on multi‐directional constraints. These concepts and capabilities provide a semantically rich way to organize and reuse the complex relations and properties that characterize SBD models. Representing relations as non‐causal constraints, which generally accept any valid combination of inputs and outputs, enhances modeling flexibility and expressiveness. We envision SysML becoming a unifying representation of domain‐specific engineering analysis models that include fine‐grain associativity with other domain‐ and system‐level models, ultimately providing fundamental capabilities for next‐generation systems lifecycle management.

The past three decades have seen phenomenal growth in investments in the area of product lifecycle management (PLM) as companies exploit opportunities in streamlining product lifecycle processes, and fully harnessing their data assets. These processes span all product lifecycle phases from requirements definition, systems design/ analysis, and simulation, detailed design, manufacturing planning, production planning, quality management, customer support, in-service management, and end-of-life recycling. Initiatives ranging from process re-engineering, enterprise-level change management, standardization, globalization and the like have moved PLM processes to mission-critical enterprise systems. Product data representations that encapsulate semantics to support product data exchange and PLM collaboration processes have driven several standards organizations, vendor product development efforts, real-world PLM implementations, and research initiatives. However, the process and deployment dimensions have attracted little attention: The need to optimize organization processes rather than individual benefits poses challenging “culture change management” issues and have derailed many enterprise-scale PLM efforts. Drawn from the authors’ field experiences as PLM system integrators, business process consultants, corporate executives, vendors, and academicians, this paper explores the broad scope of PLM, with an added focus on the implementation and deployment of PLM beyond the development of technology. We review the historical evolution of engineering information management/PLM systems and processes, characterize PLM implementations and solution contexts, and discuss case studies from multiple industries. We conclude with a discussion of research issues motivated by improving PLM adoption in industry.

No abstract

One important aspect of product lifecycle management (PLM) is the computer-sensible representation of product information. Over the past 15 years or so, several languages and technologies have emerged that vary in their emphasis and applicability for such usage. ISO 10303, informally known as the Standard for the Exchange of Product Model Data (STEP), contains the high-quality product information models needed for electronic business solutions. By using STEP, the aerospace, automotive, and shipbuilding industries are saving $150M/yr primarily in areas related to geometric modeling. However, traditional STEP-based model information is represented using languages that are unfamiliar to most application developers, thus impeding widespread usage in other areas. This paper discusses efforts underway to make STEP information models available via mechanisms familiar to more business application developers, specifically XML and the Unified Modeling Language™ (UML®). We also present a vision and roadmap for STEP integration with XML, UML, and other technologies to enable enhanced PLM interoperability. Our conclusion is that STEP, XML, and UML are complementary technologies, where STEP provides significant standardized content models, while XML and UML provide enhanced implementation methods. Together, they are a powerful force to enable pervasive digital representation and sharing of diverse technical information.

These two companion papers present foundational principles of parametrics in OMG SysML™ and their application to simulation‐based design. Parametrics capabilities have been included in SysML to support integrating engineering analysis with system requirements, behavior, and structure models. This Part 2 paper walks through SysML models for a benchmark tutorial on analysis templates utilizing an airframe system component called a flap linkage. This example highlights how engineering analysis models, such as stress models, are captured in SysML, and then executed by external tools including math solvers and finite element analysis solvers. We summarize the multi‐representation architecture (MRA) method and how its simulation knowledge patterns support computing environments having a diversity of analysis fidelities, physical behaviors, solution methods, and CAD/CAE tools. SysML and composable object (COB) techniques described in Part 1 together provide the MRA with graphical modeling languages, executable parametrics, and reusable, modular, multi‐directional capabilities. We also demonstrate additional SysML modeling concepts, including packages, building block libraries, and requirements‐verification‐simulation interrelationships. Results indicate that SysML offers significant promise as a unifying language for a variety of models—from top‐level system models to discipline‐specific leaf‐level models.