This months newsletter is a collection of posts from the Configuration Management is… series I have posted on LinkedIn. These posts are not intended to limit the scope of Configuration Management, but to create awareness of the breadth of CM.
Configuration Management is… #Baselines!
Let’s talk about Baselines.
Imagine building a house without a blueprint. Each contractor works from their own notes, making changes as they see fit. The result? A structure riddled with inconsistencies, unexpected failures, and costly rework and delays. This is exactly what happens when organizations lack baselines in Configuration Management (CM).
What is a Baseline?
A baseline is a formally approved configuration snapshot at a specific point in time. It acts as a reference for defining changes and is used as a basis to order parts, manufacture and maintain products.
Without baselines, there’s no control over changes, no accountability for decisions, and no reliable way to verify product integrity.
What is the difference with a CM2 Baseline a.k.a. As Planned/As Released Baseline?
The CM2 Baseline is a rolling or moving baseline and is updated with every released dataset and includes visibility on the planned changes to the datasets and items in the baseline.
In Configuration Management, baselines serve three critical roles:
– Control: They define what’s been agreed upon, preventing unauthorized changes.
– Traceability: They provide a historical record of approved configurations.
– Integrity: They enable verification and audit processes, ensuring compliance and consistency.
How does your organization manage baselines? Do you see them as a control mechanism or just a formality? Share your thoughts n LinkedIn.
Configuration Management is Quality!
Today let’s look at #Quality. Depending who you ask you will get a different definition of what quality is. Some would say it is whatever the customer says it is, but that makes it rather fuzzy. I prefer to state that Quality = Conformance to Requirements. Requirements are a good way to capture what the customer wants but also what your company wants to bring to the customer and what rules and regulations you have to deal with.
#ConfigurationManagement is essential in ensuring the requirements are captured, tracked, and implemented accordingly. Without #CM achieving a high quality standard efficiently is not possible.
CM also closes the loop when it comes to requirements, as #verification will ensure that we actually deliver per the requirements and when there is a non-conformance, that this non-conformance will be addressed accordingly.
In other words: Quality is the result of doing CM right.
What do you think? Join the discussion on LinkedIn.
#ConfigurationManagement is… #Efficiency!
The perception by many is that #CM adds bureaucracy and slows you down, while the opposite is true. CM done right, will make you go faster!
What often happens is that people perceive CM to be slowing them down, create work arounds or implement CM half-baked and cause mayhem. Guess who gets blamed for the mayhem? While a lot of the mayhem would have been prevented if they just followed a simple procedure.
CM can always be tailored to your organization’s needs. CM does not create the data, CM just ensures the data that is created is managed in a consistent and efficient way with the appropriate controls in place. Preventing issues and keeping the flow of work moving towards you deadline.
What do you think? Join the discussion.
Configuration Management is… Status Accounting!
Have you ever tried to manage a project without knowing where things stand? It’s like driving a car with no dashboard—no speedometer, no fuel gauge, no idea if you’re speeding or about to run out of gas.
That’s why Status Accounting is such a critical part of Configuration Management, as defined in the SAE-EIA-649 standard.
So, what is it?
Status Accounting is the process of tracking, recording, and reporting the current state of your configuration items. It gives you a clear picture of:
• Which items are in use and which are obsolete.
• What changes have been proposed, approved, or implemented.
• Whether all parts and documents are properly aligned.
Without Status Accounting:
• Teams waste time searching for the right revision of datasets.
• Decisions are made based on outdated information.
• Projects risk delays, budget overruns, or even failure.
Status Accounting turns confusion into clarity.
What’s your take? How do you track and report the status of your configuration items? Share your thoughts below! Join the discussion on LinkedIn.
Configuration Management is… Verification and Audit!
Imagine you’re managing a project – a new product introduction, a system upgrade, or just processing component end-of-life changes. Everything appears to be on track, but how can you be sure?
That’s where #Verification and #Audit step in, bridging the gap between confidence and chaos. Ensuring every component of your system is exactly where it should be, and it is documented to prove it.
In Configuration Management, verification ensures your #ConfigurationItems (CIs) are accurate, complete, and in compliance with established baselines. While audits validate that what’s on paper matches what’s deployed in reality. They’re not just about catching errors, they’re about building trust and ensuring #traceability.
But Verification and Audit requires #StatusAccounting to track, record, and report the current state of your configuration items.
How does your organization leverage Verification, Audit, and Status Accounting to maintain control and visibility over configurations? Share your thoughts on LinkedIn.
Header Photo by Pascal Bernardon on Unsplash