Track and Manage REST Services Where?

I'm trying to populate a system for our sub-group to handle service requests.

We are a GIS group and we manage GIS documents (filename.mxd) that are used to create REST Services (domainname.com/rest/service/name) that are used by web-based map applications (domainname.com/webmap_name).

Would I create CI's for all of these and just relate them?

I'm wanting to create tickets that would be similar to the following:

Webmap X isn't working.
Customer can select the webmap from a list of Assets / CI's?
Webmap X is displaying bad data?
Customer can select the webmap which will then list the REST Services it uses to generate layers so they can pick the layer that isn't displaying correctly.
REST Service X which is used to populate an internal application isn't working
Customer can select which REST Service isn't working

This way, when the tech gets a report on a faulty webmap, he will automatically know what webmap to check, which REST services it consumes, and what MXD was used to create those services.

Any ideas?