My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
VISIPHOR CORPORATION 1A-2009
Clerk
>
Contracts / Agreements
>
V
>
VISIPHOR CORPORATION 1A-2009
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
5/6/2020 11:02:15 AM
Creation date
7/31/2009 11:10:49 AM
Metadata
Fields
Template:
Contracts
Company Name
VISIPHOR CORPORATION
Contract #
A-2009-009
Agency
POLICE
Council Approval Date
1/5/2009
Expiration Date
7/31/2009
Destruction Year
2015
Notes
Amends A-2006-169 Amended by A-2009-157, A-2010-138(A-2010-228)
Document Relationships
VISIPHOR CORP 1 -2006
(Amends)
Path:
\Contracts / Agreements\V
VISIPHOR CORPORATION (KCC) KNOWLEGE OF COMPUTING (CANADA) 1B-2009
(Amended By)
Path:
\Contracts / Agreements\V
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
<br />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 /> <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 /> <br />19.4. <br /> <br />Each Incident submitted to VISIPHOR shall contain the following information <br /> <br />19.4.1. <br /> <br />Incident Information <br /> <br />. Date of incident <br /> <br />. User's Agency, Name and Contact Information <br /> <br />. VlSIPHOR Application Name, including version number <br /> <br />. Location of server/workstation <br /> <br />. Issue Details <br /> <br />. Describe the nature of the issue <br /> <br />. Is the issue sporadic, persistent, or is this the first time it has been <br />experienced? <br /> <br />. Describe how the issue impedes the user's ability to perform a specific <br />business process Gob function) <br /> <br />. For a persistent issue, describe the steps that lead to the problem <br /> <br />. Error Information (please provide screen captures, if possible) <br /> <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 />
The URL can be used to link to this page
Your browser does not support the video tag.