Recent Posts

91

Automation Interface, Add-Ins and Tools / Re: Vector Simulation with openmodelica

« Last post by fishy on January 14, 2026, 03:28:26 am »

I have posted a bug for this issue...

https://sparxsystems.com/forums/smf/index.php/topic,49209.msg284281.html#msg284281

92

Bugs and Issues / Errors in Modelica code generation for SysML Sim: multidimensional parameters

« Last post by fishy on January 14, 2026, 03:24:32 am »

This relates to an obervation first made a few years ago...

https://sparxsystems.com/forums/smf/index.php/topic,48010.0.html

• EA doesn't correctly declare Modelica parameters from SysML parameters that are typed as vectors using mutiplicty.
• EA appears to ignore the stereotyping of parameters using SysPhS <<MultidimensionalElement>> when declaring Modelica parameters
• There are inconsistencies in the syntax EA uses for Modelica parameters declared in blocks, and those declared for Operations stereotyped <<SimFunction>>.   It's actually slightly closer to correct for SimFunctions, but still doesn't work
  

This was last tested by me, using EA 17.1.1713

Please post here if you'd like me to expand with more detail.

93

Automation Interface, Add-Ins and Tools / Re: Vector Simulation with openmodelica

« Last post by fishy on January 14, 2026, 03:05:09 am »

I suspect, based on my own testing, that this is due several a bugs in how EA writes Modelica code...

To understand what's happening, you really need to take a look at the Modelica code generatedby EA when you press 'Solve' or 'Validate' in the 'Configure SysML Simulation' window.

In SysML, the natural way to work with vector quantities (1-d arrays) is to declare multiplicity on a parameter.
In EA, this means setting 'Property > Multiplicity > Upper bound' to a value greater than 1 (or potentially *) for an aribtrary upper bound.

But if you do this, EA messes up the syntax for Modelica definitions...

In your example, the correct definition for your 'ChooseVector' <<constraint>> would be:

    class ChooseVector;
        Real pX[3];
        Real pY[3];
        Real p[3];
        equation
            p = if (Type==X1) then pX else pY;
    end ChooseVector;

However, if you specify SysML multiplicity on the parameter, EA instead generates this:

    class ChooseVector;
        RealU005B3U005D pX;
        RealU005B3U005D pY;
        RealU005B3U005D p;
        equation
            p = if (Type==X1) then pX else pY;
    end ChooseVector;

...it's messing up in two ways:

• It substitutes Unicode codes rather than using an ASCII square bracket ( U005B = [, in unicode)
• It uses SysML notation, by putting the dimension next to the type definition (Real in this case), rather than matching the Modelica syntax and placing the dimension next to the variable.

If instead you take your appoach, of using the SysPhS stereotypes, by setting:

• MultidimensionalElement.dimension = 3
• Part.Lower Value = 3
• Part.Upper Value = 3

...then EA just ignores these settings and produces...

    class ChooseVector;
        Real pX;
        Real pY;
        Real p;
        equation
            p = if (Type==X1) then pX else pY;
    end ChooseVector;

Which is why you see the error you do:  Modelica thinks pX, pY and p are single-valued parameters and can't assign a three valued vector.

94

General Board / Re: MCP (Model Context Protocol) server for Enterprise Architect has been released

« Last post by Takeshi K on January 13, 2026, 07:04:47 pm »

Hi Geert,

Thank you so much for your comment. Your comments are very welcome and I agree some of your comments.

About the following points, maybe we can solve by requesting AI to do so.
- all elements the same size
- elements as the same horizontal/vertical level
- elements the same distance from each other
- link pools/Lanes with the proper elements (e.g. PartnerRole etc...)
My addin already has the interface for those.

About the connector style and routing, currently we cannot specify them. Especially latter, maybe you know, this is not easy to route nicely in the current EA API/storing data format...


I think it's important to consider how we use AI/LLM in our business/work. I once heard someone say that if we want 100% quality, we shouldn't use AI. If we think we can skip 80% of our work with AI, AI is our friend.

For example, if we want, we can create hundreds of BPMN diagrams from very large Word documents by asking AI to generate diagrams and then waiting for it to finish. Of course, we would still need to manipulate layouts and correct AI misunderstandings, but I think this is easier and faster than creating all the BPMN diagrams manually one by one. In Enterprise Architect in particular, adding pools, changing their size, adding lanes inside pools (which then requires us to change the size of the pools again), adding BPMN elements, connecting them and layouting them beautifully are very tedious work.

However, someone (e.g. one of my colleagues - he never use AI) might argue that many low-quality artifacts are worse, and that creating them manually results in a higher quality product (and we can save time, compared to 'fix' AI generated artifacts.) Yes, that is also correct. The most important thing, I think, is how, where and when we use AI.

95

General Board / Re: MCP (Model Context Protocol) server for Enterprise Architect has been released

« Last post by Geert Bellekens on January 13, 2026, 06:38:16 pm »

Hi Takeshi,

Looks nice and all, but I'm afraid I'm still a bit underwhelmed by all this.

It looks to me like this AI agent does only does the stuff I can easily do myself.
I would be really enthousiastic if it would do the hard stuff

- Do proper layout of my diagram
   - all elements the same size
   - elements as the same horizontal/vertical level
   - elements the same distance from eachother
   - all connectors the correct style (mostly orthogonal rounded)
   - all connectors correctly attached to the correct point of an element (mostly center, unless there are multiple connectors on the same side)
- link pools/Lanes with the proper elements (e.g. PartnerRole etc...)
- make blackbox pools (such as customer) actually blackbox.

To make it actually work in a serious modelling environment, it should need to learn and follow the guidelines of the organisation.

I don't want to rain on your parade, and I'm sure it's really technically a very advanced tool.
But for now I'm not yet able to recommend usage of such a tool to my clients.

Geert

96

General Board / Re: MCP (Model Context Protocol) server for Enterprise Architect has been released

« Last post by Takeshi K on January 13, 2026, 04:42:35 pm »

Hi Viking and all who are interested in auto-generation by AI,

Regard to the following Viking comment, now the latest MCP server can generate better BPMN diagrams including Pools, Lanes, better layout, etc.

"I haven't tested your workaround solution for BPMN yet, but I will definitely do so.". Here are finally my test results:

• The sterotypes are used and displayed for all elements I was using: events (!), activities, gateways.
  
• As part of the prompt I said which task types to use, but I got only 'abstractTasks'. I will futher investigate this issue.
  
• mcp created lanes for each involved role. But it arranged them as a row (not on top of each other), And it did not put the respective activities into the lanes. Instead Copilot says: "The fundamental issue: The MCP server's createelement and setelementproperty commands don't seem to support proper BPMN lane Containment. This is similar to the limitation we found with UML attributes - the MCP Server (v2.1.0.0) doesn't expose all the necessary commands for complete BPMN diagram modeling."
  
• The layout is quite good. But it is vertical and cannot be changed. BPMN diagrams are more horizonal and this should be the outcome, if the layout cannot be adapted.
  
• The created diagram is not correct but my understanding is that mcp cannot help here (e.g., only diverging gateways have been created, but not converging ones).
  

Example request for your AI (LLM):
Please create the following process as BPMN diagram within the currently selected package.

1. When an order email arrives from a customer, the responsible staff member in the relevant department reviews the email contents.
2. If the contents are acceptable, that staff member performs the ordering procedure.
3. If the contents are problematic, the department manager reviews the contents, after which the original staff member performs the ordering procedure.
4. Once the ordering procedure is complete, create an order report and finalize the process.

Result:
(by Claude Desktop, free plan)


I have not modify anything including position and size. We need to use the prompt for BPMN which is offered by the MCP add-in.

Enjoy!

97

General Board / Re: Diagram Zoom level in HTML Report

« Last post by A_Marsh on January 13, 2026, 10:42:24 am »

Changing the following value to 100% might ease your situation.

User Preference (Ctrl + F9) -> the Diagram group (left pane) -> Scale Saved Bitmaps to

HTH,

Thanks, I already had this set to 100%. It doesn't seem to help   

98

General Board / Re: Diagram Zoom level in HTML Report

« Last post by Takeshi K on January 13, 2026, 10:18:18 am »

Changing the following value to 100% might ease your situation.

User Preference (Ctrl + F9) -> the Diagram group (left pane) -> Scale Saved Bitmaps to

HTH,

99

General Board / Re: MCP (Model Context Protocol) server for Enterprise Architect has been released

« Last post by Takeshi K on January 13, 2026, 09:59:28 am »

We can create elements and diagrams, and place existing elements onto them. As I mentioned in my last post, I split the tool into two for better performance and to support more situations. However, we usually do not need to specify which tool the agent should use to fulfil our requests, as the agent can automatically determine this.

Simply make your requests to the AI. The AI will generate the necessary packages, diagrams, elements and connectors, and then place the elements on the diagrams.

100

General Board / Diagram Zoom level in HTML Report

« Last post by A_Marsh on January 13, 2026, 08:09:18 am »

I have a few largeish diagrams. I manage the zoom level of these diagrams through Properties > Diagram > Default Zoom.    (I have also tried Layout > Diagram > Zoom)

When I publish to an HTML report this default zoom is ignored and the diagram is published fully zoomed in. Attempting to navigate the diagram in the HTML is very awkward.

Should I be using Properties > Diagram > Default Zoom ?  What values would I be specifying?

It looks like this question was asked 15 years ago https://sparxsystems.com/forums/smf/index.php/topic,22182.msg189750.html#msg189750

Thanks for your help.