https://www.servicenow.com/community/cmdb-forum/what-cmdb-implementation-decisions-do-you-preserve/m-p/3566017#M21120 <P><STRONG>Question for the CMDB community.</STRONG></P><P>One thing I've noticed across CMDB implementations is that we spend a lot of time discussing <EM>how</EM> to model services, configure Discovery, tune IRE, and implement CSDM.</P><P>What I'm curious about is something a little different.</P><P><STRONG>What implementation decisions do you intentionally preserve?</STRONG></P><P>Not the configuration itself—but the reasoning behind it.</P><P>For example:</P><UL><LI><P>Why was one discovery source chosen as authoritative over another?</P></LI><LI><P>Why was a CI intentionally classified into a particular class?</P></LI><LI><P>Why was a specific normalization rule introduced?</P></LI><LI><P>Why does a transform behave the way it does?</P></LI><LI><P>Why was an exception made to the standard model?</P></LI></UL><P>A year later, those decisions often seem just as important as the configuration itself.</P><P>Do your teams have a formal way of preserving that operational knowledge, or is it mostly captured in project documentation, meeting notes, and consultant experience?</P><P>I'd be interested to hear how different organizations approach this.</P> Mon, 29 Jun 2026 14:45:55 GMT jrbockrath 2026-06-29T14:45:55Z https://www.servicenow.com/community/cmdb-forum/what-cmdb-implementation-decisions-do-you-preserve/m-p/3566017#M21120 <P><STRONG>Question for the CMDB community.</STRONG></P><P>One thing I've noticed across CMDB implementations is that we spend a lot of time discussing <EM>how</EM> to model services, configure Discovery, tune IRE, and implement CSDM.</P><P>What I'm curious about is something a little different.</P><P><STRONG>What implementation decisions do you intentionally preserve?</STRONG></P><P>Not the configuration itself—but the reasoning behind it.</P><P>For example:</P><UL><LI><P>Why was one discovery source chosen as authoritative over another?</P></LI><LI><P>Why was a CI intentionally classified into a particular class?</P></LI><LI><P>Why was a specific normalization rule introduced?</P></LI><LI><P>Why does a transform behave the way it does?</P></LI><LI><P>Why was an exception made to the standard model?</P></LI></UL><P>A year later, those decisions often seem just as important as the configuration itself.</P><P>Do your teams have a formal way of preserving that operational knowledge, or is it mostly captured in project documentation, meeting notes, and consultant experience?</P><P>I'd be interested to hear how different organizations approach this.</P> Mon, 29 Jun 2026 14:45:55 GMT https://www.servicenow.com/community/cmdb-forum/what-cmdb-implementation-decisions-do-you-preserve/m-p/3566017#M21120 jrbockrath 2026-06-29T14:45:55Z