g. Contract approval - Laserfiche WebLink

SCHEDULE 1-A: APS SERVICE JURISDICTION ADMINISTRATOR APS Service Jurisdiction Administrator The Licensee's APS Service Jurisdiction Administrator is responsible for the day-to-day operation of APS within the Licensee's jurisdiction. She (or he) is the point of contact for technical and operational questions from Licensee's investigators and pawn dealers (Data Contributing Licensees Only). This person will interact regularly with the APS Administrator at the Minneapolis Police Department (MPD) on issues and questions regarding operations and policy which are system-wide (not just Licensee-specific). Primary functions include: • Provide focal point for all APS Service operational and policy activity for Licensee, • Provide end user support as a "first call for help" when questions or incidents occur regarding APS Service usage within Licensee's jurisdiction, • Maintain dialogue with APS Administrator at MPD for questions and support issues, Startup Tasks (All Licensees) 1. Define a process or series of steps to receive, log, process and track APS support calls (e.g. who gets called, what information to take, how to forward or close contact, how to accumulate statistics and track open contacts, etc.). 2. Gain familiarity with APS administrative screens to set up new users. Startup Tasks (Data Contributing Licensees) 1. Gain familiarity with APS administrative screens to set up new dealers and support billing functions (Data Contributing Licensees). 2. Gain familiarity with the APS Service upload process and directory structure used for dealer upload files, logs, archived transactions (Data Contributing Licensees). Daily Tasks (All Licensees) 1. Respond to APS support calls. Log contacts, respond or refer contact to APS Administrator (MPD), monitor resolution and ensure requester is contacted with resolution. Daily Tasks (Data Contributing Licensees) 1. Review upload activity from previous evening to ensure all Licensee's dealers submitted a transaction file. 2. Review administrator upload log for each store to assess whether file was successfully processed or not 3. Contact dealers who have not submitted transaction files or refer to Licensee's investigators/regulators for follow-up. 4. Review error history to ensure dealers are submitting corrections to previous transactions flagged as errors. 5. Perform random spot checks on uploaded data items using APS queries or reports to verify overall data quality. 6. Periodically run queries or reports on categories, items and brands where 'OTHER' is specified. 7. Work with Licensee's police and civilian investigators and regulators to ensure that ordinance-specified data reporting and quality is maintained. 8. Consult with Licensee's investigators/regulators on data quality issues to refer back to dealers for resolution or additional training. c:\users\gabrielsons\appdata\local\microsoft\windows\temporary iernet files\content.outlook\09t14ah0\a psuserag reecasscsond2013.doc