Regulator requirements field for SW Assets
These regulatory requirements could be an entirely new class to make it easy to create views based on it and the fact that a SW could be connected to multiple variants. To have them connected as related CI's would be an acceptable setup even though a separate field would be preferable..
This to make it easy to identify which software that supports what of those, which may have effect on Change Management processes, audits, etc.
Comments
This field or class could also be used to control authorization of software base don ITAR rules so users from certain Geolocations could not install certain software etc.
Reject service requests for software depending on who is requesting the type of software.
Audit computers with ITAR controlled software and alert when it is outside of spec.
While this is not important to many of our customers, it is VERY important to those who need it.
I'll get this post changed to a feature request so others can vote.
https://community.cireson.com/discussion/654/regulator-requirements-field-for-sw-assets