06.14
It is this day Back to basics that I have a 4 umpteenth time asked the management of interchangeability and the rise of evidence in a BOM. As indicated in my summary of the day in question is at the presentation of Jean-Jacques Urban-Galindo who had taken the management of indices depending on the capabilities of interchangeability that I am therefore intervened by not understanding why we did not go back to the top of the index nomenclature. I now have clearer ideas about this process, not necessarily the implementation method perfect, but at least the principles seem well placed.
As part of the exhibition of the proposed principle
First of all I want to remind the scope of this article. I think it is and / or hopefully as part of the reflection PLMLab. While there may be two trends in the PLMLab he will have to discern. There are current initiatives to provide solutions simple, practical and relevant to SMEs and another current of thought that works on the basis of PLM, which potentially are not applicable in the industrial world today because the tools do can not, but that should be applied in future solutions. And in this role we intended to supply companies that provide these tools as the fact that they CMII to provide tools to their customers incorporating clear principles and proper management and not managements somehow "doctored" to Because of technological limitations of their tools. The risk principle in the relationship between management and implementation tools is that there is a loop back to the principles because of limitations of the tools or management human behavior rather than because of an error of definition of these principles .
So here I am speaking to establish a universal principle of managing interchangeability whatever industry, whatever the scope of application and which is perhaps not applicable to the present day with methods and tools currently available.
The issue of interchangeability
As I indicated in the heading of this article, in absolute terms, there is no interchangeability. When replacing one thing with another in a series we obtain a different set. And different word here is defined in absolute terms.
On the site www.qualiteonline.com, interchangeability is defined as "the ability of an entity to be used without modification to the place of another to meet the same requirements. "And this is a third element is through the notion of requirement. Requirements are not carried by the product itself. A requirement is defined as the "expression of a documented need of what a product or service should be or do." And this requirement is defined by an individual or individuals, which is assimilated to an identity as part of PLM. It therefore becomes important to integrate the identity object to introduce the principle that an item is exchangeable for a data or identities "
interchangeability may be true for a limited number of people
If we can identify these two groups, one is able to define who must be impacted by the change, and so, who needs to have visibility. And that is exactly what we practice between suppliers and customers when it is considered that the change has not made to be visible to the customer. So we can see in the diagram below, if we take a modification of an electronic component in a car that does not affect vehicle operation, the model will not have to evolve to the client, however this vehicle has evolved and if he returns it will be important for the maintenance crew knows the identity of the component used.
If one accepts the previous observation we can reach a data model of information system that will incorporate a change in the dependence of identities. Could be linked identities for which there is interchangeability or otherwise bind those for whom there is no interchangeability, to ensure they have access to information of the change.
Then illustrate the case of a product incorporating the changes made by different teams.
Above one can imagine that transition to the second line, the provider has changed a delivery method that directly impacts the purchases. Then it was an evolution of R & D that does them. But every time you change the index is incremented by the Service to be sure you have the greatest accuracy in determining the cause of any return. Finally it is only when a significant change impacting the end user, he will then see the difference in index.
Taking index and its spread
Given the previous finding, the result is direct. If there is no interchangeability, the slightest modification of a section shall impact the tree systematically rising.
As part of PLM that are highly integrated with the ERP or in the case of a management solution maintained in operational condition, we will even identify each physical element taking into account again that each product is unique in its design and potentially permanently by his experience.
The example of Subversion is an example of this systematic ascent. In managing that provides Subversion source item was always the top most significant revision of the entire tree because any changes to a file back until top node.
The fear that exists in organizations is the weight of the upwelling index. And that's where the challenge lies. As presented in the demonstration with the successive changes, it is important to know who must be impacted in its work by each change.
Conclusion
Before concluding with a summary of some clear management that I have presented so far I want to remind that are quite questionable. It should however understand that the goal is not whether it is simple to apply or not with the current tools but whether it is conceptually the right way to ask the question and risk management methods current .
So I think it is important in a concept of proper management of changes that every change at any level of a classification is reflected in all its tree rising. This point may not speak of absolute interchangeability.
It is recommended for the proper management of resources around the management process of a product, not to reflect the consequences of this change on people for whom the change has no impact. It is therefore referred to an identity and interchangeability in a given context (project product).
I'm listening to all your comments!
Yoann Maingon
