You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 3, 2022. It is now read-only.
Much of the software purchased by the government is done separately by separate departments and sometimes separately within a single department. Purchasers are rarely aware that a software product has already be bought by someone else. The ESCT needs to create a database that contains lists all the software purchased along with dates, version and related technical specifications. Before anyone purchases new software, the protocol should require them to check this database to see if they can use the existing licenses. Additionally, it may be advantageous to purchase additional license based on existing purchases rather than initiate independent procurement.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Much of the software purchased by the government is done separately by separate departments and sometimes separately within a single department. Purchasers are rarely aware that a software product has already be bought by someone else. The ESCT needs to create a database that contains lists all the software purchased along with dates, version and related technical specifications. Before anyone purchases new software, the protocol should require them to check this database to see if they can use the existing licenses. Additionally, it may be advantageous to purchase additional license based on existing purchases rather than initiate independent procurement.
The text was updated successfully, but these errors were encountered: