What is an item fork in a graph?
I’m resuming our series of blog post about configuration management concepts. The last one was about non-interchangeable revision. This week we cover the fork concept. Fork...
Filter by Category
Filter by Author
I’m resuming our series of blog post about configuration management concepts. The last one was about non-interchangeable revision. This week we cover the fork concept. Fork...
Posted by Yoann Maingon
I’m a little bit late on the marketing trend to write a post about low-code. But I was recently asked how “low-code” was Ganister PLM? I realized that you could...
Posted by Yoann Maingon
As an enterprise-wide data management platform, one of the main PLM goal is to provide the users with the right data at the right moment. The digital thread should provide a...
Posted by Yoann Maingon
There is a debate on cloud PLM stack. Some would argue that cloud PLM = SaaS PLM = Multi-tenant. Any discussion on this topic becomes quickly technical and looses 80% of the...
Posted by Yoann Maingon
As I’m now in the business of editing PLM software with Ganister. I have been involved in defining what would be a correct way of dealing with configuration management (CM)...
Posted by Yoann Maingon
Now that we have seen the most simple change in my previous blog post, let’s talk about the revision mechanical engineers will hate : THE NON-INTERCHANGEABLE REVISION !!!...
Posted by Yoann Maingon
On my french blog I wrote a blog post about some suggestions for a flexible configuration management solution. I’ll reproduce the article in English soon for a broader...
Posted by Yoann Maingon
Wow, this blog took a dramatic 180° turn. Don’t worry, this is still talking about PLM and more precisely about the Fit, Form, Function (and Safety for some companies)...
Posted by Yoann Maingon
When it comes to PLM, it is difficult to have a clear opinion on business models. These last few days I have seen multiple business models and pricing configuration from PLM...
Posted by Yoann Maingon
I wish you all a happy new year. My blog colleagues all came up with predictions for either the coming years or like oleg and Jos, for 2030. There are some very interesting...
Posted by Yoann Maingon
I’m resuming our series of blog post about configuration management concepts. The last one was about non-interchangeable revision. This week we cover the fork concept.
First let’s make sure we don’t confuse Fork and Branch.
A branch is typically copying data to work on an alternative in order to ultimately merge the benefits of this alternative, back in the initial version. It allows to work on multiple alternatives at the same time.
Fork, is closer to basic configuration management practices. You have a product, and you decide to create a new version. But this version is different enough to not keep the same product number and start a new product reference, not just a revision.
Historically in PLM, Fork, is copying a folder. Whatever the PLM data you are working on (mechanical, electronic design, or service definition). You create an alternative by copying and renaming a folder.
PLM is a graph, and in a graph, the limits of your folder don’t exist. Therefore we need to understand what is the impact of a fork on a few nodes of the PLM graph.
Here is a simple example with PRTC being forked.
The consequence of such operation is:
The difference with a non-interchangeable revision is that you don’t supersede the initial part (or any type of node). In our case PRTF starts from the latest state of PRTC but from now on it will live its own life.
The following example is an actual automated test script from Ganister PLM. It show that part C1.0 is forked and in the same Engineering Change Order (ECO) D and F are revised (from 1.0 to 1.1) in order to consume the result of the fork. Part C1.0 doesn’t change its state. It is still a released Part. Thanks to the graph we easily add a “fork” link to keep the traceability of the fork.
The next step will be to cover the case of a superseding fork. Pretty similar to this fork but changing the state of the former object.
As usual feel free to comment your objections !
Last June (June 17th 2021), Neo4j raised $325 millions. Last week ( october 5th 2021), Memgraph raised $9.34 millions. Tigergraph raised $105 millions last winter (February 17th...
What is the language your PLM solution has been built with? It is something that barely comes up in PLM evaluation. Does it matter? I think so, but in order to know why it matters...
Don’t miss any post by subscribing