In order to provide a level of service that meets the repository's contracted obligations, SP selects and implements hardware technologies based on a clear and comprehensive understanding of the needs and expectations of its Designated Community. The repository's Designated Community Definition supports decision-making by providing an overview of the repository's user communities.
SP staff work closely with members of the Designated Community to identify system requirements and test components. Representatives from the Designated Community sit on SP's advisory committees, giving them a direct channel to the repository's directors and systems administrators. In addition, SP receives ongoing feedback about system behaviour from its Designated Community. For example, see the Feedback Forum incorporated into SP's journals interface. Feedback from the Designated Community provides valuable information about response times, page loading, and overall system performance. Generally, the close relationship between SP and its Designated Community means that SP staff are aware of new needs and expectations at an early stage.
Systems administrators at SP and the University of Toronto Libraries' Information Technology Services department receive information about system behaviour and usage from automated monitoring programs. These programs warn administrators about events and loads that exceed predetermined levels. Please see 188.8.131.52.2 for more information.
The repository has an inventory of hardware and software to help staff carry out long-term technology planning.
Digital Preservation Policy Librarian
The primary risk to SP's compliance with this point is a disconnect with the Designated Community such that SP is not aware that the system is no longer meeting the community's needs, or that the community has needs that have not been communicated or anticipated.
SP has procedures, commitments, and financial resources for regular hardware replacement and media refreshment. See 184.108.40.206.4 for details.