Properly classifying GitLab's CIs in CSDM

[ahbrook]

Hello everyone! I was hoping to get some feedback.

I'm currently going through by hand and determining our Service Instances here at the University - namely our Application Services. In doing so, I'm also trying to align them appropriately with either Business or Technology Management Services and their related offerings. 

I'm currently stuck a little bit on how to classify GitLab. In our environment in terms of service / offerings and business capabilities. I was hoping to get your thoughts on how you handle GitLab, and how you might approach our classification. 

At our institution, the following is true:

• GitLab is primarily used by the Administrative teams for code repository, artifact storage, and CI/CD pipeline functionality. 
• It is maintained by our central Enterprise Applications team, with access being granted to multiple College-based IT departments.
• It is NOT offered to our students or the general public (and if it were, we'd likely create a separate environment to protect any sensitive data).
• It is accessed through a singular endpoint URL, which other tools (like IDEs) access via APIs. 
• It is directly called by our Ansible playbooks for things like standing up containers, VMs, web sites, and other infrastructure. This is critical enough that we would consider it a foundational/infrastructure tier on our business criticality chart. 
• While we aren't the best at being consistent about it, GitLab's change and portfolio management functions are used by our teams. Some teams track their tasks/incidents inside it. Frankly, I'd love to see it hooked up to ServiceNow. 

I recognize that every business is going to have different definitions for their services and offerings. Heck, I'm still struggling with mapping what we do to the various education-based models out there. And all of this is made harder by how many functions GitLab can perform these days. So I just wanted to see what other people thought.

Currently, I'm leaning towards this:

• Portfolio: IT Portfolio
• Taxonomy node (Service Classification): Infrastructure
• Technology Management Service: DevSecOps Management or Code Development
• TMS Offering: Code Repository

I'm initially choosing a technology management service because GitLab provides the repository and CI/CD tools.. and it fits into the CSDM case where a Service Delivery domain element can also be part of the Service Consumption domain (because we maintain and offer it to other departments).

It is possible (and perhaps preferred?) that the Application Service would be tied to multiple services and offerings, given all the functions it supports. But for now, I'm trying to maintain a setup where each Application Service is tied to a singular Business / Technology Management Service. 

So where would you place this?