Skip to main content

The EU branch of our organization has adopted LeanIX as their EAM.

We have used both XLS and Google sheets for shape-object meta-data management in the past.

This is limiting in several ways. One may apply the same row of a data source to varied objects, thus “unifying” them as a single reference, yet they are still different objects.

LeanIX uses “Fact-Sheets” to describe each asset that is represented in the EA. 

For example I may create a Fact-sheet to represent a PLM service within the organization. Any time i need to represent the PLM service, regardless of representation, it is the same object (like Archi/TOGAF).

If I create a Fact-sheet in LeanIX, can i reference it as a data-source in LucidChart, so that I always refer to the exact same architectural representation, and not a copy?

Thanks

Hi @john.a.lopez, thanks for your question! 

Unfortunately, data import from LeanIX isn’t currently supported in Lucid, but we’re very interested in your feedback and committed to continually improving our products. If you’re willing to share, we’d love to hear more details about your use case or what you’d like to see in this experience within this thread. I’ve also converted this post to an idea so that it’s visible to others within the Product Feedback section of the community - from here, they can upvote it and add details of their own.

Finally, for more information on how Lucid manages feedback via this community, take a look at this post:

https://community.lucid.co/welcome-to-the-lucid-community-15/feedback-and-feature-requests-5439 

 

As a workaround, you could add a weblink of Fact-sheet to any relevant shape as a reference instead, as described in this Help Center article.

Hope this helps!


Thanks.

For LucidChart to become more than “echa-sketch” for adults, integrations with key platforms and services is a necessity. I’ve made numerous post on variations of this topic.

meta-data management via Google sheets or XLS import is not an enterprise solution.

Tools like Sparx EA, Cameo NoMagic, etc. provide capabilities for analytics, simulations, etc. with integrations to support environments such as MATHCAD, Mathematica, etc. Even being able to connect an object with structured metadata to a python service could be huge.

Regarding an EAM like LeanIX, coelecing architectural or process elements in the repository so that all instances of a given object in any context or viewpoint, have referential integrity to a singular object definition. The Fact-Sheet in LeanIX is the means to accomplish this. Another group internally has implemented the Capgemini IAF meta-model in Orbis/Infinity. With the Visio integration, referential integrity is maintained. 2 viewpoints of a PLM service are not copies … but referentially singular. 

Since LeanIX/Signavio are SAP products (along with an internal diagram editor for LeanIX), one might presume that the potential to provide a more capable and scalable tool would be an entry point into a potentially huge market for Lucid. 

A URL to the fact sheet is not sufficient for referential integrity.

LeanIX already has a repository linkage to LucidChart as both support articles from Lucid and LeanIX describe. Consider expanding this capability via integration to an object mgmt. level.

My thoughts.


alt idea:
what if Lucid creates their own EAM? rather than https://lucid.com/data/junkyard ?

you could then actually implement a meta-model for:

  • EA / TOGAF
  • BPMN 2.0
  • SysML
  • etc.

???