Catalog Model with XML?

[wproctorPG49C]

I have a very large model that I created 10 years ago.  I would like to use an XML file to create a catalog of the model and help me navigate how all of the objects are linked and, using an AI, determine the best way to make targeted changes.  There are complicated ways to do this with tools such as Claude-Code which can do some of this.  Does anyone have a suggestion on simpler tools that I could use?

[kavika_faleumu]

Hey @wproctorPG49C, I don't know if you've already looked into this, but FlexSim already can save as an XML file (.fsx). This is a more readable format that gives you all the nodes and their hierarchy.

[wproctorPG49C]

Yes - I've have created the XML file from FlexSim.  It is a very very large file, however (1.3Gb).   I would like a way to summarize the key information. - Bill

[amerloQ2XZU]

Hi,

For a large legacy model, an XML export could be useful as a starting point, but understanding how the model works may also require looking at object connections, Process Flow logic, labels, and FlexScript.

At Flexcon, we’ve developed Flexcon Eidos to connect AI agents to a running FlexSim model. It allows the agent to inspect the model directly, so you can ask questions about its structure and logic, explore how objects are connected and identify the parts potentially affected by a proposed change.

For example, you could start by asking it to map a specific area of the model and explain the relevant connections and logic, then discuss possible changes before applying and validating them.

Flexcon Eidos uses MCP and can work with tools such as Claude Code, ChatGPT or Github Copilot, but the model inspection happens through the FlexSim connection rather than relying on an XML catalog alone.