SysML Connector, Pinout, & Harness Modeling Methods

This example shows multiple methods to model both logical and physical ports at the connector/plug level and the pinout level. This video walks through how to build the different methods and explains why one method would be desirable over another.
This example will provide information regarding Digital Engineering (DE), Model Based Systems Engineering (MBSE), and SysML.
Video compatible with the following versions of SysML Tools
-Cameo Systems Modeler 19.0
-Cameo Systems Modeler 2021x
-Cameo Systems Modeler 2022x
-Cameo Enterprise Architecture 19.0
-Cameo Enterprise Architecture 2021x (used in this demo)
-Cameo Enterprise Architecture 2022x
-MagicDraw 19.0
-MagicDraw 2021x
-MagicDraw 2022x
Video relevant or similar to the following Tools
-IBM Rational Rhapsody
-Oracle Sparx Systems Enterprise Architect
-Genesys by Vitech
-Microsoft Vizio
#SysML #MetaChain #DigitalEngineering #MBSE #engineering #CameoSystemsModeler #MagicDraw #simulation #ModelBasedSystemsEngineering #UML #SystemsEngineering #SystemDesign #SystemArchitecture #design #methodology #digitaltransformation #StructuredExpression #DynamicLegend
SysML Diagrams:
SysML Structural Diagrams:
Block Definition Diagram: #bdd #blockdefinitiondiagram
-Block, Interface Block, Constraint Block, Value Type, Enumeration, Signal, Instance, Proxy Port, Full Port, Directed Aggregation, Directed Association, Directed Composition, Generalization, Usage,
Internal Block Diagram: #ibd #internalblockdiagram
-Part Property, Value Property, Reference Property, Constraint Property, Flow Property, Constraint Parameter, Binding Connector, Item Flow, Proxy Port, Full Port, Interface Block
Package Diagram: #pkg #packagediagram
-Package, Package Import, Element Import, Navigation, Start Here Page
Parametric Diagram: #par #parametricdiagram
-Rollup, Constraint Block, Part Property, Value Property, Reference Property, Constraint Property, Flow Property, Constraint Parameter,
SysML Requirement Diagram:
Requirement Diagram: #req #requirementdiagram
-Extended Requirement, Satisfy, Verify, Relationships, ID, Test Case Activity, Trace, Derive, Copy,
SysML Behavioral Diagrams:
Activity Diagram: #act #activitydiagram
-Allocation, Swim Lanes, Swimlanes, Activity Partitions, Actions, Activities, Call Behavior Action, Opaque Action, Control Flow, Object Flow, Send Signal Action, Accept Event Action, Time Event, Initial Node, Activity Final, Flow Final, Decision, Merge, Fork Horizontal, Join Horizontal, Input Pin, Output Pin
State Machine Diagram: #stm #statemachinediagram
Initial, Final State, Composite State, Orthogonal State, Submachine State, Deep History, Transition to Self, Entry Point, Exit Point, Junction, Choice
Sequence Diagram: #seq #sequencediagram
Lifeline, Alternatives, Loop, Option, Call Message, Send Message, Reply Message, Create Message, Delete Message, Diagonal Message, Message to Self, Recursive Message, Lost Message, State Invariant, Duration Constraint
Use Case Diagram: #uc #usecasediagram
-Actor, Use Case, Include, Extend, Association, Generalization, Block,
Visit our website for more available free resources at www.CameoMagic.com

[@MBSEReelz]

Excellent video! Pretty sure this is the most in depth video on this topic. Lots of detail and great examples as always. Thank you!

[@CameoMagic]

Thanks! Glad you enjoyed it!

[@57ashdot]

In my opinion, I find pinout level details very useful in practice working in engineering product development. Your job as the systems engineer is to make the working details of your system as easy to understand as possible. Makes it easy to reuse parts of the design in other models, adds a layer of verification for physical design of the harnesses in the system and can produce pinouts as an reference artifact, serves as a technical reference for the product, etc.. Also lets you tie FMEA to more specific details of the model for analysis, or showing particular parts of the system that fulfill a design requirement.
I use full ports for physical connectors so I can assign value properties (like a connector type, part #, etc.), and proxy ports at the pin level.
Great video, glad to see more detailed vids on methods like these on CZcams

[@CameoMagic]

Thanks for the comment and explaining your modeling method.
A couple questions just to understand further because we like your method:
1) Do you type the pinout level proxy ports?
2) Do you connect the pinout level proxy ports together in ibds? (Or just connector level?)
3) Do you have signals as item flows over the connector or pinout level? Or both?
4) Do you separate your logical and physical breakdown or have them all together?
5) How do you represent logical ports (proxy or full)?

[@abdulbasetatweri2866]

One of the most detailed video on the subject of connectors, pinouts and ICDs. Great job
Just out of curiosity, is it possible to share the project file . . . thanks

[@CameoMagic]

thanks for the positive comment. At this time we are not releasing the project files. That may change in the future but for now the videos are the only thing available.