The master files stored by tracksys represent a large percentage of Library IT's billable storage.  Some of those files are irreplaceable artifacts that merit enormous expenditures to ensure their continued availability, while others may never be needed again and wouldn't be missed if they were gone. 

To address these divergent needs, we need to set up procedures to establish which files merit higher levels of preservation action, which files are infrequently used and could be stored on lower availability, cheaper storage and update tracksys to appropriately route and retrieve them from these various locations.