Specifications include, but are not limited to: Be able to work with the University of Oregon (UO) which will maintain its own transcript/document ordering system. 2.4. Contractor must be able to securely accept a transcript/document output from UO and apply it to a PDF template that allows UO branding. 2.5. The accepted transcript/document output must also be able to provide, at minimum, the requestor identity and the recipient destination email address. 2.6. The resultant PDF document must be secure (certified and protected from tampering) to maintain its authenticity. Provide the certificate authority. 2.7. Provide the option for UO to exercise document rights management (DRM) such as setting document expiration, recalling a document, controlling print, etc. 2.8. Provide a comprehensive administration interface for UO personnel that will: 2.8.1. a. Allow monitoring of orders and searching for orders. 2.8.1.1. Provide capability for UO resending of transcript delivery notifications. 2.8.1.2. Provide capability for UO to control number of document downloads per order and to reset the download counter. 2.8.2. Allow creation and administration of UO groups and users, as well as setting access levels for the same. 2.8.3. View billing statements. 2.8.4. Support; online ability to: 2.8.4.1. Submit support tickets 2.8.4.2. View and/or download, system documentation 2.8.4.3. Review knowledgebase, extensive FAQ’s, and/or “help” system. 2.8.5. e. Provide analytics or reports such as, but not limited to: 2.8.5.1. Order Volumes 2.8.5.2. Order status 2.8.5.3. Types of documents ordered...
