Default list of fields per fact sheet - Meta Model 4 Transition

Hi ​@Nathan ,

the is no table. You can ask you success manager to provide a metamodel extracted from the api and look into the json produced by it. The easiest would be if they provide a prdefied api requerst to update your system via API pathfinde /metamoled/actions. I never used that but perhaps it may work.

Best regards,

Carsten

Hello Alex, 

Thanks for the information.

I’ve started the process of moving to meta model v4 (created Platform Fact Sheet, and converted the Project fact sheet into Initiatives and associated sub types (like Idea and Program). I was waiting to update the Process fact sheet into Business Context and associated Sub Types until after receiving more information. 

Question Background

The catalyst for my question was the lack of fields unique to a Fact Sheet and pertinent subtypes.  For example, an Idea, Program, Project, and Epic are the not the same things.  Therefore, they should have some unique variables associated with them (not just unique relations to other fact sheets).  The instructions called for renaming Projects to Initiatives but when I did that, I didn’t see anything different compared to the fields available in the Project Fact sheet.  If there is no difference between the Project Fact sheet in meta model V3 with the Initiatives Fact Sheet, and 4 “predefined subtypes” in meta model v4, then why upgrade to V4? 

To me, if something is Predefined, then it would have out-of-the box pre-defined fields and relationships, so a customer can hit the ground running with them. 

If not, then there is no difference between custom types/subtypes and out-of-the-box types/subtypes. 

The Context...behind Business Context

I was planning on meeting with some members of our product development and project management teams over the coming weeks about associated features of LeanIX, so I wanted to make sure I go into those meetings with great things to showcase. 

The four subtypes available under Business Context (Process, Value Stream, Customer Journey, and Product) have even more unique aspects among them than the 4 subtypes under Initiatives. That’s why I waited to learn more from the community.

For example, a key component of a customer journey map is a touchpoint. 

So, I would expect a customer journey sub type to have fields about touchpoints, such as email, web, social, phone calls, in-person, etc.  You also have different stages like awareness, consideration, and decision.  Given your explanation, those fields would be associated with the base Business Context factsheet, and the appropriate sections/fields can be activated using conditional attributes when configuring them.

For products, there are many different ways to manage product architecture information such as product mix concepts (product line width, depth, etc.) and associated branding architecture.  There are also high-level strategies for a given product portfolio to help with growth plans (expand into Market A with Product Line 1 but do line extensions for Product Line 2). Finally, there is product lifecycle management variables. 

Next Steps

I can create some of these myself as I wouldn’t expect LeanIX to have all of these, but I expected more than what I found.  The more you can create applicable content for the Strategy and Business Architecture part of the platform, the more non-IT adoption you will gain. I provided a long explanation to help with road mapping and to understand my “customer journey” behind the question. 

Having said all of this, I will work with our success manager per the feedback I received.