WHAT’S NEW IN INTEGRITY MODELER 9 - PTC€¦ · –Design constraints and parameterized requirements are defined in the Integrity Modeler model –ModelCenter takes inputs from

WHAT’S NEW IN INTEGRITY MODELER 9.2

Hedley Apperly & Patrick OllertonWindchill Systems & Software Engineering

October 2019

22

AGENDA• Contemporary user interface

• Diagramming productivity

• OSLC integration with Windchill

• OSLC integration with Integrity Lifecycle Manager

• Static model analysis

• Installation and deployment

3

• Integrity Modeler 9.2 provides a contemporary PTC Desktop user experience

– Microsoft Office style ribbon toolbars

– Modern, large icons

– Task-oriented tabs

– User configurable toolbar

– Icons on context menus

– Welcome page

• Value

– Easier navigation to toolbars and functions• Increasing user productivity

– More appealing design environment• Increasing user satisfaction

– Easier to learn and get started• Improving adoption for new users

CONTEMPORARY USER INTERFACE

4

• Microsoft Office style ribbon toolbars


5

• Home tab– High-frequency model editing functions

• Manage tab– Easy access to all model management functions


6

• Task and diagram specific toolbars ensure a focused user experience


7

• Configurable quick access toolbar– Rapid access to favorite functions


• Icons on context menus make it easier to locate functions

8

• Welcome page for access to quick links, recent models and user help

9.2 CONTEMPORARY USER INTERFACE

What’s

New and

Getting

Started

Guide

Recent

models

Quick

links

99







10

• Diagram view options– More consistent across all

types of diagrams

– Increasing efficiency when creating diagrams

• Profile diagram style settings

– Integrated with view options

– Simpler & more logical

• Pasting options and styles

– Including compartments

– More consistent, increasing

productivity when editing

diagrams

DIAGRAMMING PRODUCTIVITY

11

• Diagram templates can

now be created for any

type of diagram– Improving model

consistency and increasing productivity when creating diagrams

• You can now drag and

drop symbols from profile

diagrams to non-profile

diagrams

– Making it easier to re-use

model items

DIAGRAMMING PRODUCTIVITY

Set existing

diagram to

be a

template

Select template to use when

creating new diagram

1212







13

SYSTEMS OF RECORD

Windchill, Integrity Lifecycle Manager, Integrity Modeler, SAP…

eBOM mBOM

Options

& Choices

sBOM

R

R

R

R

R

R

R

R

R

T

T

T

V

V

S

V

T

T

T

V

V

Tests

Sim

Results

3rd Party…

F

F

Your Best-of-Breed Toolchain

14

SINGLE (VIRTUAL) SYSTEM OF RECORD

Digital Thread for Design Abstraction, Compliance Traceability and Impact Analysis

eBOM mBOM

Options

& Choices

sBOM

R

R

R

R

R

R

R

R

R

T

T

T

V

V

S

V

T

T

T

V

V

Tests

Sim

Results

F

F

Persistent Inter-System of Record Links using Product UIs & UXs

Link-Not-Sync

In Context

e.g. Trace Requirements ‘implemented’ by Parts without Duplicating Data

OSLC / OData REST

15

EXTENDED PLM LINKING & TRACING

Systems of Engagement Role Based Apps Extending PLM

Systems of Record Digital Thread

Digital

Requirements

R

R

R

R

R

R

R

R

R

Functions

F

F

Product Structure

eBOM mBOM

Options

& Choices

logical Structure Validation

T

T

T

V

V

S

V

T

T

T

V

V

Tests

Simulation

Results

Others…

sBOM

Software Structure

SCM

3rd Party…

Crosscutting Link & Context - OSLC/OData REST

16

• Business challenges:– System engineering designs in Integrity Modeler are disconnected from detailed

designs in Windchill• E.g. Requirements, Functions, Use Cases & Blocks are not linked to Parts

– Regulatory compliance - lack of traceability between Systems Engineering and PLM means design data is siloed

– Dependencies between designs are unclear, pushing design changes downstream or upstream is hard to manage, costly and inefficient

• Value:– Establish product traceability between software/systems engineering and PLM design

data to enable the digital thread & tool ‘qualification’

– Capture design dependencies to better understand impact of change and improve how design changes are implemented

OSLC INTEGRATION WITH WINDCHILL

17

• Ensures design dependencies between Systems & Software engineering and PLM are defined and managed

• Enables Systems & Software Engineering and PLM digital product traceability & impact analysis

• Provides visibility of design changes across the product development lifecycle


18

• You can now create and view links to Windchill Parts

• Search queries ensure optimum performance

• Windchill Part properties are displayed

• Preview UI


Part properties

Specify query

Preview UISearch results

displayed in

OSLC browser

19

• All Windchill Part versions are available for linking– OSLC Links created using ‘parts’

will be version-independent• i.e. always point to the latest

version

– OSLC Links created using ‘part versions’ will be static and version-specific• i.e. always point to a certain

version


Part

(defaults to

latest

version)

All part

versions

2020







21

• Integrity Modeler OSLC client can now access and create links to requirement versions and branches in Integrity Lifecycle Manager

OSLC INTEGRATION WITH INTEGRITY LIFECYCLE MANAGER

Live, versioned and

branched items in

Integrity Lifecycle

Manager

Live, versioned and

branched items

displayed in Integrity

Modeler

22

• You can now link to versioned and branched requirements as well as live requirements

• Versions and branches are clearly labelled

OSLC INTEGRATION WITH INTEGRITY LIFECYCLE MANAGER

Live, versioned and branched items

shown in Integrity Modeler OSLC client

2323

AGENDA

• Contemporary user interface






24

• Powerful capabilities for simulating, analyzing and verifying static model behavior– Design constraints and parameterized requirements are defined in the Integrity

Modeler model

– ModelCenter takes inputs from the model, performs mathematical calculations and then returns the result to the model, indicating Requirement pass or fail status

• Value– Increase design quality with early validation and optimization of system designs

– Extend the value of MBSE by enabling analysis and simulation throughout the design lifecycle

– Performa mathematical MBSE Trade Study analysis

STATIC MODEL SIMULATION WITH PHOENIX INTEGRATION® MODELCENTER®

25

• Use SysML Parametrics to define equations– With of inputs,

calculations and outputs

• Constraint properties define the calculations to be performed by ModelCenter®

• Requirements can be linked to simulation for verification of model behavior

(X * 2 + 6) / 2 – X = 3

In linked requirement, specify

result comparison type and

performance targets

(acceptable max/min values)


26

• Run the calculation in ModelCenter® MBSE

• Results are calculated & compared against initial value

• Pass or fail verification of results against requirements

• Modify input values to run trade-off and optimization analysis

Execution plan

and results

Results passed back to

requirements in model

for verification

Results passed

back to blocks

in model


2727







28

• Installation & deployment are now more flexible with an optional location for the ModelerATFiles directory– The location can be a local or network drive, defined using a UNC path

• e.g. \\servername\path

• Performance improvements for:– Create model, delete model

– Package clone, package import, clone diagram

– Update profiles, delete large package

– Reconcile, rebase

– Populate• These performance improvements are greater for large models

INSTALLATION AND DEPLOYMENT

29

• Contemporary user interface



• OSLC integration improvements for Integrity Lifecycle Manager

• Static model analysis and simulation

• More flexible installation and deployment

INTEGRITY MODELER 9.2 SUMMARY

Documents

WHAT’S NEW IN INTEGRITY MODELER 9 - PTC€¦ · –Design constraints and parameterized requirements are defined in the Integrity Modeler model –ModelCenter takes inputs from