Skip to tutorial content
Rate module Not yet rated

Designing CMDB and Identification Decisions

4 min read
On this page

In this lesson, you will learn:

  • Which CMDB decisions a Discovery design needs
  • How readiness findings drive them
  • SNWR’s decisions DD-D05 and DD-D06

🔁 Quick look back: Last time: Designing Schedules and Scan Windows. You learned how SNWR chose when each part of the network is scanned.

1 The Problem: CMDB Choices Were Still Open

The CMDB readiness review left two open questions:

  • Who owns which fields on server CIs?
  • Does the SNWR Mail Archiver need its own class?

🎯 The problem: Key CMDB choices were still open when design began.

👉 The fix: Decide them now, in writing, before any configuration.

Two cards: DD-D05 precedence and DD-D06 classes.
Figure 1. SNWR’s CMDB design decisions.

2 The decisions to make

  • Which classes are in scope.
  • Whether any new class is needed.
  • Which identification rules apply.
  • Which source owns which fields.

💡 Good to know: Prefer baseline classes and rules. Every custom one is something the client must maintain.

3 How findings drive them

Readiness finding Decision
Import still writing to CIs Switch it off; lowest priority until then
People set support groups People own those fields
In-house archiver New class with its own rule

4 Project Clear View: How We Implemented It

📍 Situation: Two CMDB topics came from the readiness review.

🧭 Decision: Decide both and record them as DD-D05 and DD-D06.

🛠️ Steps we took:

  1. Turned the field ownership table into DD-D05.
  2. Checked that no existing class fits the archiver well.
  3. Wrote DD-D06: a new class under Application, with its own identification rule.
  4. Kept baseline rules for everything else.

✅ What we verified:

  • Hana approved both decisions.
  • Riya agreed to maintain one custom class.

📁 Evidence: DD-D05 and DD-D06 in the design document.

5 Quick recap

  • Design decides classes, identification and field ownership.
  • Readiness findings drive the decisions.
  • Prefer baseline classes and rules.
  • SNWR adds only one class: the SNWR Mail Archiver.

6 Check yourself

Think of your answer first. Then tap to check.

1 What does DD-D05 decide? Show answer

Which source owns which fields on server CIs.

2 Why prefer baseline classes? Show answer

Custom classes are extra work for the client to maintain.

3 What new class does SNWR create? Show answer

SNWR Mail Archiver, under Application.

Nice work! SNWR’s CMDB decisions are made. 🎉
Next up: Planning Environments: Dev, Test and Production

Was this lesson helpful?

Have a question or doubt?

Ask here and get help from instructors and fellow learners.

0 / 300

Only logged-in learners can post.