Best Approach for Modeling SWIFT in CMDB Using CSDM?

AjJomt
Tera Contributor

Hello everyone,
I work in banking IT, where some elements of our infrastructure are highly critical, including SWIFT. We are currently consolidating the SWIFT inventory in our ServiceNow CMDB, ensuring a structured and governed approach to its lifecycle, ownership, and certification.
We would like to leverage CSDM best practices, but so far, we haven't fully adopted Technical Services or technical Service Offerings,  in our CMDB. Currently, we have no concrete use cases relying on these concepts, although we would like to move in that direction.
Proposed Model in CSDM:
1. Technical Service: "SWIFT Infrastructure"
Represents the overall technical capability supporting SWIFT.
2. Service Offerings:
"SWIFT Core Hosting" → For servers and virtual machines.
"SWIFT Network infrastructure  → For security components like ip switch, firewall etc 
"SWIFT Database Services" → For database management.

etc. 
3. Business Applications:
"SWIFT Apps" → Linked to Application services
4. Application Services:
Created under each Business Application to manage instanciation (client, environment etc)

5. CI Dynamic group (and cmdb group) to catch CIs linked to Technical service offerings
6. CI Relationships:
Used to link all csdm items 

 

Key Questions:
Given that we are not yet mature in using Technical Services and Service Offerings, is this still the best approach?
Are there alternative ways to structure this in CMDB while keeping it manageable and aligned with best practices?
How do you track ownership and certification for critical environments like SWIFT in your CMDB?
Any feedback would be greatly appreciated!
Thanks in advance for your insights.

2 REPLIES 2

AjJomt
Tera Contributor

No opinion on this kind of topic? I'm taking the example of swift but it could be other use cases (sensitive apps, access management, etc ? @Mark Bodman maybe ? 

 

Ravi Peddineni
Kilo Sage

@AjJomt 

The approach you are follwing is correct as per the basic definitions of each element.

Alternative ways could be breaking the Technical Service down into multiple Services that could divide the Support & Maintenance groups further down and you will be able to track the availability of each service separately. But if the same group manages the Service or Offerings, I feel your Approach is the best.

For Owners, You can make use of Ownership data fields in APM and you can also make use of Data Certifications in APM that can help you trigger assessments from time to time to keep the data in check.