Cant we use DPR for hardware model changes ?

[kkcommunity]

Hi

Cant we use DPR (Digital product Review(rel mgmt)) for hardware model changes ? Like Server patch related changes ?

Should we use only for SW or service applications ?

[Itallo Brandão · Accepted solution]

Hi there,

The short answer is: Technically yes, you can, but it depends on your delivery method.

Digital Product Release (DPR) is primarily optimized for the Software Development Lifecycle (SDLC), tracking things like user stories, commits, build artifacts, and automated test results.

Here is the breakdown of when to use it for Hardware/Server changes:

1. When NOT to use DPR (Traditional Patching) If your "Server Patch" process involves running a standard update (like WSUS, SCCM, or manual patching), DPR will introduce unnecessary complexity.

• Best Practice: Use standard Change Management or Patch Management flows.

• Reason: You typically don't have "commits" or "build versions" for a physical hardware swap or a standard OS patch.

2. When TO use DPR (Infrastructure as Code) If you manage your server infrastructure using a DevOps approach (e.g., Infrastructure as Code using Terraform, Ansible, or Docker containers), then DPR is an excellent fit.

• In this scenario, your "Hardware/OS" is defined as code.

• A "Patch" is actually a new Version/Build of your server image.

• You can track the pipeline, automated tests, and deployment of that "Infrastructure Product" exactly like a software app.

Summary: Unless you are treating your infrastructure as a software product (IaC), I would recommend sticking to Change Management for hardware and patching to keep the process streamlined.

Hope this clarifies the best use case!

If this response helps you choose the right path, please mark it as Accepted Solution.
This helps the community grow and assists others in finding valid answers faster.

Best regards,
Brandão.