Communicating the responsibility of software POCs

The person submitting the initial software review request (SRR) is the person who is ultimately listed as the POC for that software, which means they will be contacted for action related to that software either going EoL or reaching its expiration date (currently set at 2 years from the software approval). This person is not made aware, though, that they will be on the hook for this. The software POC should be made aware that they will need to approve the further use of this software if it reaches its expiration date and should also have a finger on the pulse of the software version's EoL date.

Start by locating the API documentation section that describes software review requests and software POCs. Update the relevant documentation to explain the POC's responsibility for approval at expiration and awareness of the software version's EoL date; done means these obligations are clearly communicated.

Written by the indexing model from the issue text.