One way to organize information for the CM Baseline

data in our organizations properly to support the CM Baseline will improve efficiency, flexibility, and agility. People tend to fear structure as they see it as a bureaucratic, a hindrance, a slowdown. While in reality, when done right, the structure provides the opportunity to speed up, be more flexible, and be more efficient.?

When we would randomly put books on a library shelf, how long would it take for someone else to find that book? Finding a book becomes relatively easy if you use the classification system to put books on the right shelf.?

How an organization is broken down dictates how different groups of people need to collaborate. When done wrong, e.g., if it has not been aligned with how a product is broken down, it will lead to inefficiencies. When done right, it removes unclarity and creates a clear framework of reference. This is not only valid for organizational structures but also for structures or networks of information. The way we organize the information of an organization.

Structures or networks of information are just bits of information linked to other bits of information. The linkages between information dictate where interactions need to take place. If you process a change that impacts the Bill of Material and 3D Model of a part, the link from the part to the manufacturing process used for its assembly, the link to an operation, and work instruction as the part is also a spare part. The link to open production orders.All kinds of links to other information created/owned by others. In other words, these linkages lead you to the people that need to be involved in your change. Not just notified but genuinely engaged in an interactive, collaborative way.?

As described?in?Understanding the Impact of Changes , all the configuration relevant information is contained in multiple source systems. Often different roles do not have access to all these systems. Whether that is due to licensing costs, security reasons, or just function related.?

The?CM Baseline , through all the available linkages, brings people together. Assuming all the information has a creator or maintainer assigned.

Organize the relevant information

In this article, I propose* one way to break down all relevant information in an organization using three essential elements:

• Network Nodes,?
• Datasets, and
• Relationships.

Network Nodes

A Network Node is an object used to create networks/hierarchies of information. It does not contain any information other than its unique key. And is not versionable. All information that describes the Network Node is stored in Datasets linked to the Network Node.

Datasets

A Dataset is a set of information stored in digital form that must be released as a whole and can be released separately from other Datasets. There can be dependencies between Datasets, e.g., one needs to be released before another Dataset can be released. A Dataset is identified by Type, ID, and if it is not a record, it also has a revision or version. Some Datasets are used to maintain the networks or hierarchies, e.g., a Bill of Material or a Bill of Process. In other words, the source for the relationships are datasets, which can be easily controlled via the change process.?

Relationships

Relationships are the threads that weave all the information together.?The structures/networks you see are the results of information from the released Datasets.

The below graph is hugely simplified but shows the concept described in this article. It shows a parent Part 1 with a Bill of Material containing Part 2 and Part 3 at time = t1 and Part 3 and Part 4 at time = t2. The same is reflected in the operation that consumes the parts from the Bill of Material. At the bottom of this article, you can find a copy of the JSON content to use this graph yourself.?

Datasets in this example all have revisions/versions, which is solved by modeling a DataSetRoot node with a Has_Version relation to one or multiple DatasetVersion nodes.

Why this way?

This modeling provides an easy way to identify the various impacted deliverables that need to be planned when implementing a change. At the same time, it shows all the approved configurations over time. It can easily be extended to represent any future configurations based on the impact matrix as a result of the impact assessment.?

On the other hand, it still requires mapping how source tools model the data. This supports the concept of having different levels of collaboration, cross-functional and expert levels.?

*Note that this is just one way to model the information; there are other ways. However, from a CM perspective, trying to ensure the integrity of the configuration and the ability to analyze the impact and plan changes effectively. This way appears to match these requirements. Further investigation will be needed to understand the full impact of this way of modeling the information.?

Feel free to share your feedback on this way of modeling the information in an organization.??Or let's discuss it during a call.

To read more about the CM Baseline and its components, please check out the previous posts from the CM Baseline series:

• Understanding the Impact of Changes ?introduced the need for the CM Baseline.
• Connections tell the Story ?introduced the first component of the CM Baseline, the Business Object Graph.
• Intentions are the desire for new Stories , introduced the second component of the CM Baseline, the Impact Matrix.
• Dependencies limit the possible sequences of events , introduced the third component of the CM Baseline, Dependencies or a.ka. Change Dependencies.
• Timing is Everything , introduced the fourth and last component of the CM Baseline, Implementation Plans.
• 5 Ways a CM Baseline brings value

Header Photo by Bechir Kaddech on Unsplash .

This article was originally published on?mdux.net .

Disclaimer

The JSON Content of the graph used in this article, which you can use to load into the Arrows app (a free web-based tool by Neo4J Labs) can be found on mdux.net below the article.