My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
25I - MAINT AND SUPPORT OF BOOKING SOFTWARE
Clerk
>
Agenda Packets / Staff Reports
>
City Council (2004 - Present)
>
2009
>
01/05/2009
>
25I - MAINT AND SUPPORT OF BOOKING SOFTWARE
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
1/3/2012 4:25:05 PM
Creation date
12/29/2008 2:41:00 PM
Metadata
Fields
Template:
City Clerk
Doc Type
Agenda Packet
Item #
25I
Date
1/5/2009
Destruction Year
2014
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
16
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
19.2. When reporting incidents to VISIPHOR, the Customer must provide sufficient detail <br />to enable the Technical Support Analyst to reproduce and diagnose the problem or difficulty, <br />including revision level information, problem documentation and any media containing data. <br />19.3. Each incident reported to VISIPHOR should be properly defined to ensure timely <br />acknowledgement of the support call. An incident is defined as a single support issue that cannot <br />be broken down into subordinate problems. <br />19.4. Each Incident submitted to VISIPHOR shall contain the following information <br />19.4.1. Incident Information <br />• Date of incident <br />• User's Agency, Name and Contact Information <br />• VISIPHOR Application Name, including version number <br />• Location of server/workstation <br />• Issue Details <br />• Describe the nature of the issue <br />• Is the issue sporadic, persistent, or is this the first time it has been <br />experienced? <br />• Describe how the issue impedes the user's ability to perform a specific <br />business process (job function) <br />• For a persistent issue, describe the steps that lead to the problem <br />• Error Information (please provide screen captures, if possible) <br />• What steps, if any, were taken by the user to recover from the incident? (E.g., <br />Application restart, computer reboot, closing and reopening of module, etc.) <br />251-16 <br />
The URL can be used to link to this page
Your browser does not support the video tag.