a.
NORMAL MAINTENANCE HOURS:
LICENSOR’s regular maintenance hours are from 7 am to 4 pm Pacific Time Monday through
Friday except for the following United States designated days in any calendar year:
-
Memorial Day (last Monday of May)
-
Independence Day (July 4th)
-
Labor Day (first Monday in September)
-
Thanksgiving (fourth Thursday of November)
-
Christmas (December 25th)
-
New Years Day (January 1st)
LICENSOR support usually responds to maintenance calls beginning at 7 am Pacific
Time, taking into account Daylight Savings when applicable.
d.
TECHICAL SUPPORT LEVELS:
LEVEL 1. Initial call will be attempted to be fielded by a qualified tech support
representative within about twenty (20) to forty (40) minutes after the call is
made with identification of the problem. Problem identification is the first step.
LICENSOR’s experience is that a large percentage of problem issues may be resolved
by verifying and correcting software configuration of Microsoft SharePoint on server
and/or Microsoft InfoPath on client machines. For example, SharePoint can disable
other Web services installed on a server and there are known defect in Microsoft
InfoPath regarding form caching on client machines which require clearing the InfoPath
cache on the client machine. For another example and in addition, there are known
defects in Microsoft’s Vista operating systems (problems with support for WebDAV
protocol) that may require the installation and/or special configuration of software
applications on server machines. Please refer to Product Release Notes for details
on the most common configuration issues. A very common Qdabra Software Product issue
is an error in the mapping from XML to SQL. Please refer to the Qdabra event log
on server machines to confirm a Qdabra Software Product problem. While LICENSOR
anticipates that resolution can usually be found, sometimes a software issue in
the Software Product will be identified. If a “hot fix” or new version resolves
any such software issue, Licensee will be advised to download and update accordingly.
If no resolution is then available, Licensee will be advised of the current status,
such as by way of examples only (and without limitation), whether: (1) the problem
has been replicated; (2) the problem has been replicated and a programmatic fix
is underway; (3) the problem has been replicated, a fix programmed and is being
tested; (4) a workaround to the problem is available; or (5) no workaround is currently
available. If the problem is not readily apparent, it is common for a support representative
to ask Licensee to run the software after being advised to make setting changes
or to perform tests in order to receive additional information about the nature
of the problem. A level 1 diagnostic can take minutes to hours to days to weeks
depending on the nature of the problem, and how responsive a Licensee is in providing
supplemental information that is critical to an accurate diagnosis.
LEVEL 2. If the tech support representative cannot identify the nature of the problem,
a senior support representative will be consulted or will directly take over the
problem diagnosis. This can typically take two (2) to four (4) hours, but can be
much longer depending on LICENSEE delays in requested feedback. For problems that
are difficult to diagnose, LICENSOR uses an Internet-based remote control software
product. With this tool, a technical support representative can take control of
a LICENSEE machine and can quickly perform tests to aid in a correct diagnosis of
a problem, particularly when it is a network or software setting issue. If the nature
of the problem appears to be a LICENSOR software bug, user conditions must allow
the problem to be confirmed, as opposed to a one-shot occurrence or an intermittent
problem that cannot be made to occur through a set of known and reproducible actions.
Programmers cannot begin to work on a program resolution until a software problem
can be reliably replicated. Senior support representatives have extensive experience
at both solving very difficult issues within LICENSEE environments that are not
directly caused by LICENSOR Software’s products, and discovering hard-to-find or
obscure combinations of events that cause software failures. Upon discovering a
software product bug, deficiency or LICENSEE environment issue that a software fix
may resolve, an entry is made into LICENSOR’s Bug Tracking System. Depending on
the level of severity to the LICENSEE, the following actions may be taken: (1) a
programmer is assigned to work on a fix right away (critical bugs); (2) a programmer
is assigned to work on the bug in the order of assignment (important bug but not
critical); (3) a programmer is assigned to work on the bug as time permits (a work
around is available); or (4) the bug is not assigned to a programmer because it
is very low level or it is not a bug at all but rather a new feature request to
solve a LICENSEE environment issue or is simply a LICENSEE feature request.
LEVEL 3. A software problem has been identified, replicated and has been entered
into LICENSOR’s Bug Tracking System for a programmatic resolution. Critical bugs
are assigned top priority and a developer will be diverted from lower priority work
to program a fix. Programming a fix can be relatively very fast compared to the
time necessary to identify and determine the set of circumstances that will replicate
a LICENSEE problem. Forecasting the exact amount of time to discover a bug and program
a fix is impossible. What LICENSOR commits to is allocating the resources and the
best people available to find, solve and fix critical LICENSEE problems. LICENSOR
uses state of the art source code program debugging tools to expedite the discovery
of root problems.
LEVEL 4. A fix is compiled in the main source code tree of the software to fix a
reported problem. In the development of releases, new versions of the software are
generated from the main source code tree, and it is company policy to fix reported
bugs here first to keep “fixed bugs” from reappearing in subsequent releases. The
fixed version is tested against the set of circumstances that were known to replicate
the problem. The testing department also tests other software functions to guard
against the fix causing another problem that could be equal to or worse than the
problem solved.
LEVEL 5. Once the programmed fix has passed internal testing, the same programmatic
changes are made into a special “hot fix” version of the software that can be made
available to a LICENSEE immediately. The only exception would be if the changes
to the main source code tree coincide with a new general release. The hot fixed
version is then tested rigorously. This is because the source code changed is based
on the current release version. This process is followed so that the current version
and version under development both have the problem fixed. Upon passing internal
testing, the hot fix version is made available to the LICENSEE for download and
testing to validate the fix in the LICENSEE environment (which frequently cannot
be replicated in LICENSOR’s testing facility). If the fix solves the LICENSEE problem,
the hot fix version may become the new general release depending on the nature of
the LICENSEE problem (which can be very unique or which could affect every LICENSEE).
If the problem persists or other problems are discovered due to the fix, the cycle
is repeated until resolved.
LEVEL 3, 4 AND 5 SUPPORT:
Support as defined in Level 3, 4 and 5 shall be made in the discretion of LICENSOR
taking into account LICENSOR’s staffing and other then existing factors. Any expedited
services for these levels may be requested by a LICENSEE and may be provided only
on mutually agreed-upon terms and conditions of an additional executed written agreement
between LICENSOR and Licensing that contain among other terms, such consideration
that is acceptable to LICENSOR. In some such cases, LICENSEE may desire a custom
coding project, and in any such situation, a written agreement acceptable to both
LICENSOR and LICENSEE must be agreed upon and executed.