Periodically, the software must be reviewed for continued applicability. Software that is functionally obsolete (e.g. might not run on current hardware) or no longer relevant should be removed from normal distribution.
Although removed from distribution, backups of the software are maintained, and if conditions warrant (e.g. regulatory submittals or legal action) the software can still be retrieved.
Key Considerations
- Is the software truly to be retired or should it be legally transferred to a commercial entity?
- e.g., software that is still useful but not a part of EPRI's core values
- Consider open source
- At any time, in consultation with you management, you can initiate the retirement process.
- Formally communicate software retirement plans with all stakeholders (several years in advance when possible)
- Similar, but simpler process is used when a new version is released and the older version is archived
- In addition, Customer and Product Access (CAPA) will periodically distribute a list of software for retirement consideration with specific criteria
- 2 year review — Determine if it should continue to be orderable or for download only
- 5 year review — intended to identify high value work (like software) that cannot be made public
- Evaluation
- Stop the distribution of software by notifying Electric Power Software Center (EPSC)
- Review who has downloaded the software and who has access to the software
- Determine if the software is connected to any other business process or software
- Software developed under Billable Service Agreements (BSA) require consideration of the contract requirements
- Be sure that all obligations are being met (e.g., Third Party Licensing Agreements)
- For vendor-developed
- Look at access rights to EPRI resources and discontinue as appropriate
- Terminate access to EPRI servers and resources as applicable
- Should older versions be retired or is there a need to keep them active for some subset of users?
- How is it removed from distribution?
- Deactivated in SAP
- Removed from the web
- Where is it stored?
- Software, source code, test and product/project documentation are currently maintained permanently
Communicate the Need to Archive
In order to communicate the need to archive software, the applicable Software Distribution fields in Section B of the Software Acceptance Form (SAF) need to be completed. Fields shown below.
Additionally, you may send an archive request including product number and name to the Software Distribution Lead (EPSC).