SysPhS zone (SysML Extension for Physical Interaction and Signal Flow Simulation)

Icon class
icon_class_computed
fas fa-book
NEWS: SysML Extension for Physical Interaction and Signal Flow Simulation (SysPhS): New technology assessment trail: TRAIL: SysPhS-1.1 specification body figures in MagicDraw/Cameo SysML vs Modelica [using Wolfram SystemsModeler]
NEWS: SysML Extension for Physical Interaction and Signal Flow Simulation (SysPhS): New technology assessment trail: TRAIL: SysPhS-1.1 Annex A examples in MagicDraw/Cameo SysML vs Modelica (Wolfram SystemsModeler)
NEWS: SysML Extension for Physical Interaction and Signal Flow Simulation (SysPhS): New technology assessment trail: TRAIL: SysML+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]
SysPhS stands for SysML Extension for Physical Interaction and Signal Flow Simulation. From the SysPhS-1.1 specification:

'SysPhS-1.1: This specification: Extends SysML with additional information needed to model physical interaction and signal flow simulation independently of simulation platforms.'

'SysPhS-1.1: This specification: Provides a human-usable textual syntax for mathematical expressions.'

'SysPhS-1.1: This specification: Includes a platform-independent SysML library of simulation elements that can be reused in system models.'

'SysPhS-1.1: This specification: Gives translations between SysML as extended above and two widely-used simulation languages and tools for physical interaction and signal flow simulation.'

The targeted simulation languages are Modelica (from the Modelica Association) and Simulink/Simscape/StateFlow (from MathWorks, developers of MATLAB).

The targeting of the Modelica and Simulink simulation language families by the SysML Extension for Physical Interaction and Signal Flow Simulation (SysPhS) encourages development of SysML models aligned with known practices for a wide class of problems!

See SysPhS in action for MagicDraw SysML and Cameo Systems Modeler with Modelica as simulation environment

Visit one of these technology assessment trails:
TRAIL: SysPhS-1.1 specification body figures in MagicDraw/Cameo SysML vs Modelica [using Wolfram SystemsModeler]
TRAIL: SysPhS-1.1 Annex A examples in MagicDraw/Cameo SysML vs Modelica (Wolfram SystemsModeler)
TRAIL: SysML+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

Getting started with SysPhS in MagicDraw SysML and Cameo Systems Modeler

Note firstly that:
MagicDraw SysML/Cameo: You do not always need to load the entire SysPhS ModelLibrary for simpler black box exports to Modelica or Simulink/Simscape/Stateflow (sometimes the sysphs_profile within the MD Customization for SysML is enough)
If you decide you do need full SysPhS with non-normative libraries:
MagicDraw SysML/Cameo: For export of more complex physical interaction and flow cases to Modelica or Simulink/Simscape/Stateflow load the SysPhS ModelLibrary using SysPhSLibrary.mdzip as a shared project.
MagicDraw SysML/Cameo: For export of more complex physical interaction and flow cases to Modelica or Simulink/Simscape/Stateflow load the SysPhS ModelLibrary using SysPhSLibrary.mdzip as a shared project.
Notes
[TIP] MagicDraw SysML/Cameo: You do not always need to load the entire SysPhS ModelLibrary for simpler black box exports to Modelica or Simulink/Simscape/Stateflow (sometimes the sysphs_profile within the MD Customization for SysML is enough)
[TIP] MagicDraw SysML/Cameo: For export of more complex physical interaction and flow cases to Modelica or Simulink/Simscape/Stateflow load the SysPhS ModelLibrary using SysPhSLibrary.mdzip as a shared project.
Relevant snippets (from other sources)
Visit also
Modelica zone
OpenModelica zone
Wolfram SystemModeler zone
Visit also (backlinks)
Examples of applications of Systems Modelling Language (SysML) and Model-Based Systems Engineering (MBSE)
TIP/GOTCHA: MagicDraw SysML/Cameo: In Parametric Diagrams create BindingConnectors involving part properties by selecting the constraint parameter symbol first and use the smart manipulator (otherwise you might accidentally create a regular Connector)
MagicDraw/Cameo v19SP3: UML/SysML: HOWTO Set an OpaqueExpression on a Slot that seems to be stuck on a numerical value.
The targeting of the Modelica and Simulink simulation language families by the SysML Extension for Physical Interaction and Signal Flow Simulation (SysPhS) encourages development of SysML models aligned with known practices for a wide class of problems!
TRAIL: SysML+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]
SysML+SysPhS: Flows: If you intend to use a Classifier to type the itemProperty of an ItemFlow on a Connector for a physical interaction you MUST use a Block (not a ValueType or Signal) so your can extend ConservedQuantityKind.
IBD: Context for SimpleDomesticInverterAirCon - detailed
IBD: Context for SimpleDomesticInverterAirCon
Overview of two SysPhS-style physical interaction Port types
TRAIL: SysML: Simple model of an air conditioner with a refrigerant cycle and StateMachine driven by Activities in MagicDraw/Cameo
TRAIL: SysPhS-1.1 Annex A examples in MagicDraw/Cameo SysML vs Modelica (Wolfram SystemsModeler)
Figure 36: Elements for vector signal flow
Figure 35: Simulation platform stereotypes
Figure 34: Value types and units for physical quantities
Figure 33: Value types and units for electrical quantities [including additional]
Figure 32: Elements for signal flows of electrical quantities [additional]
11.3 Component behavior - Electrical components
Modelica: Naming convention: Why does the OnePort family of electrical components have 2 Pins? Where is the "one port"?
11.3 Component behavior - Logical components
11.3 Component behavior - Routing components
SysPhS-1.1: p.60: table for routing components: row for Switch: equivalents Modelica.Blocks.Logical.Switch (for Modelica) and Switch (for Simulink) missing
11.3 Component behavior - Sources and sinks
11.3 Component behavior - Real.Mathematical
11.3 Component behavior - Real.NonLinear
11.3 Component behavior - Real.Discrete
11.3 Component behavior - Real.Continuous
Figure 31: Elements for physical interaction
Figure 30: Elements for signal flow
External simulation: Languages and tools: SysML vs SysPhS vs Modelica vs Simulink
MBSE: Languages and tools: NoMagic/Dassault vs SysML
MINI TRAIL: Some recommended tools for getting started with Model-Based Systems Engineering with SysML and simulation with Modelica and/or Simulink
Model-Based Systems Engineering (MBSE) zone
SysML: HOWTO Use an explicit converter between different Unit systems
SysML: HOWTO Safely incorporate ConstraintBlock equations from a library into a project with local ValueType variants: CASE: SysPhS vs ISO-80000 ModelLibrary
GOTCHA: MD SysML/Cameo 19SP3 vs SysPhS-1.1: Export to Modelica does not see a 'doActivity' on a State (does not write it to a Modelica algorithm), you MUST use an 'entry'!
Figure 29: State machine in SysML
Figure 28: Units in SysML
Figure 27: Default values and initial value in SysML
Figure 26: Constraint block for physical interaction in SysML
Figure 25: Constraint block for signal flow in SysML
Figure 24: Connectors in SysML
SysPhS-1.1: [TRIVIAL] p.11: If property 'm:Mass' is named then ':Ground' should also be named for consistency in 'Figure 2: Association block with internal structure and connector properties in SysML'
Figure 23: Ports for physical interaction in SysML
Figure 22: Ports for signal flow in SysML
SysPhS-1.1: p.28: 10.6.3 Modelica modeling: An assigned value “...” is shown for v3 in the Modelica code but none is shown in the SysML model in 'Figure 21: PhSVariables and PhSConstant in SysML' (and “...” is not compatible with Real).
Figure 21: PhSVariables and PhSConstant in SysML
Figure 17: Package and model in SysML
Figure 18, 19, 20: Block, Part, Generalization, Redefinition.
Figure 2: Association block with internal structure and connector properties in SysML (and Figure 3)
Figure 1: Simulation stereotypes
TRAIL: SysPhS-1.1 specification body figures in MagicDraw/Cameo SysML vs Modelica [using Wolfram SystemsModeler]
MagicDraw SysML/Cameo: SysPhS: Export to Modelica: It does not seem to matter whether you give the language of Constraints as 'Modelica' or 'sysphs' (although SysPhS specifies a restricted SysPhS expression grammar)
MagicDraw SysML/Cameo: GOTCHA: Export to Modelica only includes owned Constraints (not just applied Constraints) under the 'equation' export
SysPhS-1.1: p.32: 10.7.8 Modelica modeling, physical interaction: Type Real for 'f' and 'lV' in example Modelica code for Spring do not correspond to 'Figure 23: Ports for physical interaction in SysML', should be Force and Velocity.
SysPhS-1.1: p.30: 10.7.4 Modelica modeling, signal flow: Example Modelica code for Spring corresponding to 'Figure 22: Ports for signal flow in SysML' is invalid [should probably be 'input Real u;' and 'output Real y;' not 'in ...' and 'out ...']
SysPhS: GOTCHA: By default PhSConstant maps to a Modelica parameter (not to a Modelica constant)
Webel Best Practice: SysML/SysPhS: DO NOT use overlapping Connector lines from/to one Port (can be misunderstood as "summed" flow and/or physical node/fork/junction).
Topic outline for Full SysML Workshop (5-Day) course version: 'Model-Based Systems Engineering with the OMG's Systems Modeling Language v1 (SysML®) and the MagicDraw/Cameo (CATIA Magic™) tools for SysML'
Flags