HomeMy WebLinkAboutC2006-116 - 3/28/2006 - Approved
AGREEMENT
BETWEEN
INTERGRAPH CORPORATION
AND
CITY OF CORPUS CHRISTI, TEXAS
-'r'~ f' '
rhis Agrcl'ment IS dTeeti\l' as of this ~~_ day of Jl~~t~, 200~ between Intergraph
Corporation., a Delaware torporatlon with its principal office at 170 Graphics Drive, Madison,
.\L acting through ItS Security, Government, and Infrastructure division (hereinafter referred to
as "Intergraph") and (Ity i)f Corpus Chn sti, Texas (hereinafter referred to as "City"),
Whereas, the City issued a Requesl for Proposal for Police and Fire CAD and Police Records
Management and Field Mobile ComputIng System, RFP # BI-0019-06, C'RFP");
\Vbereas, lhe City and [ntcrgraph acknowledge that the City's purpose in issuing the RFP was to
()btain a sottware and hardware solution \\hich satisfies the requirements identified in the RFP;
Whereas, lntergraph has offered in thc Proposal dated October 14, 2005 ("Proposal") to provide
the City wIth certain hard\\ arc, sott\vare. and services (collectively hereafter referred to as the
'SYSTFT\r'), which arc identitied In Exhibit A Pricing and Detail Summary, which Intergraph
represents and \\arrants shall meet the City's requirements outlined in the RFP, Proposal, and
this Agret'ment:
NOW THEREFORE, kr the considerations hereinafter written, the parties agree to the
follOWing
1.0 INDEPENDENT CONTRACTOR
Intergraph shall at all times act as an independent contractor in the performance of this
Agreement. Neither lntergraph nor ib employees or agents shall represent themselves to be, or
he deemed to he. employees of City and City shall have no control over the detaiL manner, or
methods oj Intergraph' s performance under this Agreement.
2.0 PERIOD OF PERFORMANCE
This Agrl'cmcnt shall he effective as of the above date and shall extend until all services defined
in the Agreement are completecL unless terminated as provided for herein, Upon termination of
this Agreement, the proviSIons hereof. \vhich by their express terms survive termination, shall
remain In full forcl' and effect.
3.0 EXHIBITS
rhe following documents are Fxhibits to and incorporated into this Agreement:
I. E"hiblt /\ PricinL'. Detail and Summary
, "iothvare license Agreement
2006-\ 16
03/28/06
M2006-095
Intergrapb Corporation
1 '.. L: 1.. _, r
Page I
3. ~',xhibit C - S YSTI \1 Configuration
4 ExhIbit D Storage area network configuration
:" f'xhibit I. Statement of'Nork
6. I.xhlbit F Pro1ect Schedule
7 E"hibit (i - Intergraph Proposal
8. ExhIbit II - RFP Amendment No 1 dated September 16, 2005
\) E"hibit I - ('it\ s kFP
10. E"hibit./- Certifil'ate of Insurance
",0 ORDER OF PRECEDENCE
In the event of any inconsistency between the various documents comprising this Agreement, the
order 01 precedence shall he the body of this Agreement then the Exhibits, in descending order as
listed abo\t,.
lnless specifically referenced by the RIP Amendment. the Proposal, or this Agreement, all
requirements. terms. and conditions stated in the original RFP still remain in effect.
5.0 'JOTICES
c\ll notIce" given bd\\een parties shall be in writing and shall be considered properly sent by
postage prepaid United States Mail or Country of Origin Mail to the persons identified below:
For: Intergraph Corporatil1n
Additional Information:
Contracts \;lanager
leIephone: (256) 730-8141
170 Graphics [)me
Facsimile: (256) 730-8989
\1adison. \Iabama ~:" 75R
[-mail: angela.k.loote({V.intergraph.com
For: City df Cl)rpUS Chrisll. Texas
Additional Information:
City Director of \;luniclpai Information
ServIces
r elephone:
1201 Leopard
Facsimile: (361) 880-3741
Corpus Christi. Te"as 784111
E-mail:
Intergraph Curporatlon
Pro Formd\;!rel'lTlt'flt
Page 2
6.0 PRODLCTS AND SERVICES PROVIDED
i) 1 Data Conversion SlTvices. Interface and Project Management services
Intergraph shall pertlmn all data conversion services. mterface programming services, project
management services. and other services as described in this Agreement, for not-to-exceed prices
iJsted in [,hibit\.
Intergraph travel expenses under this Agreement shall not exceed those listed in Exhibit
/\.
Both parties' project management staff shall be experienced and qualified to fulfill their
respectIve duties under this Agreement. The City may require Intergraph to promptly
provide replacement prolect management staff
62 Solt\\are
lntergraph shall prO\ ide the software products described in Exhibit A, Pricing Detail and
Summary m accordance \\ ith Exhibit !~. Statement of Work. for amounts not to exceed amounts
identified tn Exhibit A Additionally. Intergraph agrees to make all Intergraph software products
listed in f ,hihit L\ avaIlahle for purchase by City. for up to three years from the effective date of
this Agreement. at the "aOle prices as identified on Exhihit i\.
h 3 Hardv\ an.'
Intergraph shall provide the hardware products described in Exhibit A, Pricing Detail and
Summary. tn accordance v\ ith 1-xhlhit E. Statement of Work. for amounts not to exceed amounts
Identified If1 1-,hiblt A
7.0 FORCE MAJEURE
\ieither party shall he deemed to he in detault of any provision of this Agreement or be liable for
any delay. failure in performance. \)r interruption of service resulting from acts of war, acts of
terrorism. acts ot'God. ach of civil IX military authority. civil disturbance. or any other cause
beyond its reasonable conlrol.
8.0 INDEM~IFI(A TION
Inter2raph covenants to fullv indemnifv, save and hold harmless the Citv of Corpus
C_risti, its officers, employees, and ae:ents ("Indemnitees ") ae:ainst allliabilifv, damae:e,
101s. claims. demands and actions of anv kind on account of personal iniuries (includine:,
without limitine: the foree:oine:. workers' compensation and death claims). or propertv loss
or d..ae:e of anv kind. which is caused bv reason of Intere:raph's nee:lie:ent acts. omissions.
or willful misconduct. Intere:raph must. at its own expense, investie:ate all those claims and
demands, attend to their settlement or other disposition, defend all actions based on those
I ntergraph ( orporat ion
Pro Forma \;.'-rel'llll nl
Page 3
cl~ and demands with counsel of their choice. and pay all chare:es of attorneys and all
otkr cost and expenses of any kind arisine: from the liabilitv. damae:e. loss. claims.
demands. or actions deemed appropriate bv a court of competent iurisdiction. The City
ae:rees to cooperate with Intere:raph and Intere:raph's counsel.
In no event shall either party be liable to the other for any incidental. consequential. or
special damae:es. Neither party's totalliabilitv for any and all damae:es whatsoever arisine:
out of or in any way related to this Ae:reement from any cause shall not exceed the value of
this Ae:reement.
This section shall survive termination or expiration of this Ae:reement.
9.0 WARRANTY
9.1 Fitness for Particular Purposes Warranty
Intergraph services and products are \\arranted. when properly installed. to operate in accordance
vvith product speci ficatlOns during the initial warranty period and the extended warranty period.
as defined in Fxhibit G.. Intergraph ProposaL and for any additional extended warranty or
maintenance penods that may be purchased thereafter
lntergraph also warrants that all features and capabilities of the SYSTEM. including all hardware
and software components provided to the City under this Agreement. are tit for their intended
purposes. Such purposes are those speci tically defined by this Agreement.
lntergraph also warrants that it is prO\lding to the Cit: a software and hardware solution to meet
the requlrl'ments of this Ac!reemenl.
[ntergraph also warrants that if the SYS rFM fails to perform to meet the requirements of this
AgreemenL then lntergraph shall be responsible for taking such corrective actions, and paying
the costs associated therev\ Ith that ,ue necessary to arrive at the solution which meets the
requirements of this Agrel.ment.
Ihe warranties described l!1 this sedion shall be described collectively as the "Fitness for
Particular Purposes Warranty".
J'he Fitness for Particular Purposes Warranty shall be etTective up to and including one (1) year
after the S YSTE'v1 Cutover Date.
One of thl' mtended consequences of the Fitness for Particular Purposes Warranty is that
Intergraph shall be bound under thIS warranty even i I' there has been no violation of
manufacturers' warranties It shall be no defense for Intergraph to assert that the products are
operating m accordance \\ Ith manufacturers' vvarranties.
I ntergraph (orporatlon
f'ro Forma\;crecllwnt
Page 4
9.2 Intergraph SYSTEM Warranty
lntergraph provides SYSTi M coverage by offering the following Programs (see Exhibit G for a
more detalled descriptIon (If such cdverage). This Section shall survive termination or expiration
llfthis Agreement \\ith respect to those products purchased by the City.
9.2.1 Warrant)
lntergraph products are pwvided \\ ith a non-mission critical warranty (5 days per week, 8 hours
per day) up to the point tht' SYSTEM IS being operated in a live environment ("Cutover'} The
l:Ost of this warranty is mCluded in the pnce of the SYSTEM.
9.2.2 Extended Warran~
fhe Cit: is purchasing an ,-'xtended warranty that include mission critical support (7 days per
\veek. 24 hours per da:). ihe extended warranty is to begin immediately at the point of
SYSTEM cutover to live uperation. and \\ ill expire one year thereafter. The cost for the
extended warrant v IS retlected in Fxhihit\.
9.2.3 Maintenance
\t the conclusion of the extended warranty. the City may purchase maintenance that also
mcludes critical support (! days per v"ed.. 24 hours per day). The maintenance period begins at
the conclusion of extendeli warranty. and expires in one year increments thereafter. The cost of
the maintenance lS retleckd in Exhibit ,\ Ninety (90) days prior to the conclusion of
extended warranty. Intergraph \\ ill submit to the City a quote. which includes pricing for
the upcoming twelve ( I::' ) month period based on the pricing reflected in Exhibit A.
Intergraph will prorate sllch maintenance to coincide with the City's budget year.
currently August to August. to be paid October 1'1 of each year.
9.2.4 Third-par~' Warranty Coverage
Ihird-partv products are provided with a pass-thru-warranty from the original manufacturer.
Ihe terms and conditions \)1' the manufacturers' warranties shall be those in effect on the date a
particular Item is delivered to a representative of the Municipal Intormation Systems Department
at Corpus ('hristl Police Department (or other location designated by the City). The duration of
the warranty pen ods is spt'cified in Exhibit G. Intergraph Proposal
9.2.5 Single Point of Contact Status
\s part ot Its responsibilities. and 111 the event of any problems with any component or element
of the System. lntergraph agrees to serYl..' as the single point of contact to resolve any System
lssues. Intergraph agrees It) serve as the City's resource for identifying and assessing System
problems ,md recommendll1g solutions. If corrective action involves the retention of third
parties. then Intergraph shall assist the City in contacting such service providers. These services
shall be provided by Intergraph for as long as the City utilizes the software or hardware provided
hy Intergraph and procure', maintenance services from Intergraph
!ntergraph (orporatloll
"ro Forma \;:rec'IlKnt
Page 5
9.3 Warranty Disclaimer
INTERGRAPH DISCI AIMS (TO THE EXTEN'T PERMITTED BY LAW) ALL
WARRANTILS ON PRODUCTS FURNISHED HEREUNDER. EXCEPT THOSE
SPECIHC ALLY STATED ABOVE. INCLUDING ALL WARRANTIES OF
\1ERCI IANTABILl ry A '\JD FITNESS FOR A PARTICULAR PURPOSE (OTHER THAT
WHAT IS ST/d ED IN SECTION 9,1 L THE ABOVE WARRANTY IS IN LIEU OF ALL
OTHER WARRANTIl:S. EXPRESSED OR IMPLIED. AND REPRESENTS THE FULL AND
10TAI OBLIGATION A \iD/OR LIABII (TY OF (\JTERGRA.PR
10.0 SOFTWARE LICENSES
Intergraph software is licensed to City pursuant to the Software License Agreement attached
hereto as lxhibit B Third-party software is licensed to City pursuant to the Software License
\greemem delivered \\ ith the sothvare product
11.0 DELIVERY A~D INSTALLATION
11.1 Statement of Work
Intergraph shall pro\ ide and deliver all services and products in accordance with mutually
developed Statement of \\ ork. Exhibit I. Intergraph shall perform all of its obligations under the
:\greement in accordance with the Statement of Work. The terms of the final Statement of Work
and the Protect Schedule. I ,xhibit I. shall be negotiated by the City and Intergraph after the
:\greemenl is signed b~ b(\lh parties,\n initial draft Statement of Work is attached as an Exhibit
~.. to this Agreement\n) additional \\ork added to the final Statement of Work will be at the
then market rate prIces unkss other\vise provided in this Agreement It is the intent of both
parties that thL' SYSTFM will he in productive use hy the City as defined in the project schedule.
11.2 Shipment
Items shipped via commercial carner are FOB destination at the price stated herein. City is
responsible for facility preparation (such as appropriate and adequate power, janitorial services,
air conditioning. space all electrical drops. cabling. City furnished items. security, etc.) not
provided III Exhibit \. but necessary to accommodate equipment before. during, and after
installation
11.3 Site Access
City agrees to allcm Inlergraph personnel reasonahle access to City's site and facilities
(telephone. facsimile. parkIng. etc,) dUrIng normal business hours and at other times as agreed.
City understands and agrees that em-site Intergraph personnel may need to work Saturdays and
Sundays during the installation period and will have the work areas accessible to them on those
days as req uired
Intergraph Corporation
Pro FOnl13 \~.reelllult
Page 6
11.4 lJser Qualifications
City willt'nsure that all persons operating the SYSTEM shall be properly qualified, supervised,
trained. and have demonstrated eft\:ctivd) that the operator is proficient in its use.
12.0 TAXES
[he SYS'I EM purchase price is exclUSive of all Federal. State, or Local taxes. Any taxes applied
10 this sak by Federal. State or Local Taxmg Authority will be the responsibility of the City. If
the Cit) is claiming a tax-exempt status, It must submit the proper certificates to Intergraph.
13.0 TOTAL AMOUl'iT AND TERMS OF PAYMENT
[he total 01 payments to b,,' made by ('it) to Intergraph under this Agreement shall not exceed
($4,247.226.00), which is the total indicated on the Pricing Detail and Summary. Exhibit A, and
IS indus!\(' of the S YS [E\1 and one year of Extended Warranty ("'total purchase price"). The
City will not be respon'iibk for an) pncing mistakes made by Intergraph on Exhibit A.
Prior to Imoicing. Intergraph will obtain acceptance from the City for each milestone listed
helmv. Ih: City shall hah' ten (10) City business days to either certify that the milestone
objectives haw been achined. or provide Intergraph a detailed statement of the City's position
,1S to why apprO\ al IS deni..:d. Upon approval to be invoiced. Intergraph shall submit invoices to
the Cit) Director of 'vluniupal Inf(lrmation Systems. City agrees to pay the invoices within thirty
( ,0) day s ,>t'recelPt
\ I\\enty pen.:enl (2000) ot'the total purchase price due upon contract signing.
Ii [en percent ( 111%) of the total purchase price due upon lIC AD System setup
i excluding Lustom interfaces) at customer site.
(. Five percent (:'''/0) ot'the total purchase pnce due upon I/LEADS System setup
I excluding custom interfaces) at customer site.
D [en percent (10%) of the total purchase price due upon [lCAD Cutover.
F Five percent (~%) of the total purchase price due upon completion of30 day
reliabilit) peripd as specified in the SOW for Level One and Level Two failures after
I/CAl) Cutovc'
Five percent (~%) of the t()tal purchase pnce due upon I!Mobile Cutover.
(J Five percent (~u/o) of the total purchase price due upon completion of30 day
reliability period as specitied in the SOW for Level One and Level Two failures after
I!Mobile Cutm cr.
~.
,
H fen percenl (I (j%) of the t\)tal purchase price due upon I!LEADS RMS Cutover.
L Five percent (5%) of the total purchase price due upon completion of30 day
reliability period as specified in the SOW for Level One and Level Two failures after
1/1.E1\DS RMS Cutover
Five percent (~%) of the total purchase price due upon ULEADS JMS Cutover
I ntergraph ( orporat Ion
?ro FOr1ll~1\C'reCIlll"nt
Page 7
K. Five percent (5%1) ofth.: total purchase price due upon completion of30 day
reliability period as specified in the SOW for Level One and Level Two failures after
IILEADS JMS ('utover
Fiw percent (50/0) of th.: total purchase price due upon AFR Cutover.
VI rive percent (50'0) ofth.: total purchase price due upon completion of30 day
reliability period as specified in the SOW for Level One and Level Two failures after
\FR CutOVer.
\i Five percent (5"'0) ofth.: total purchase price due upon completion of final system
~lcceptance as ~pecitied in the SOW.
\n interest charge of one and (me-halt percent ( 15%)) per month (or the maximum amount
allowed b\ rexas lavv against mUllIcipalities. whichever is less). prorated on the basis of a thirty
iiO) day month. may be assesscd on delmquent payments.
14.0 INFRINGEMENT
In the nent of any proceeding (sui1. claim or action) against City arising from allegations that the
SYSTI. \1. ur a portIOn thereof furnished by Intergraph infringes US. patent. copyright, trade
secret. lir other proprietary right of any third-party. Intergraph will. if such suit does not result
from muddications made hy City. defend City. at Intergraph's expense. provided City promptly
notities Intergraph In vHitll1g of the allegation. Intergraph shall make such defense by counsel of
Its own choosing and ( it) "hall cooperate with said counsel. This section shall survive
lerminatinn or expiration lot'this Agreement with respect to those products purchased by the City.
15.0 TERMINATION
( ity mav lermmate thiS Agreement f()r any reason by providing the other party with thirty (30)
days wnttcn notice [n the event or' termination under this provision. City agrees to pay
Intergraph tor \\ork performed up to the effective date of termination. Each party shall take steps
to bring the work tn a close and to reduce its expenditures to a minimum. Each party shall also,
upon request and in a omcly manner. return all documents supplied to it by the other party and
"hall hand over t() nther pariy all documentation prepared by it for purposes of the work.
[em1inati(ln or expiration "fthis ,\gn:ement for any reason shall not release either party from
dny liabilities or obligatiolls set forth in this Agreement that (i) the parties have expressly agreed
"hall survl\e an) such 1ermination ur expiration. (ii) that have heen paid for but remain to be
rerfomled or (iil) by their nature would he intended to he applicable following any such
termll1ati(ln or expiratll1n.
16.0 Il\SlJRANCE
[ntergraph shall maintain. ,.luring the pert()[mance of this Agreement. the insurance coverages
lI1dicated 111 the Certificate of Insurance attached hereto as Exhibit J.
I ntergraph C orporallon
Pro F0rt11:J ,\~rel'lllenl
Page 8
17.0 CHANGES
Lither part: may request a change 10 the scope of work required under this Agreement on any
lask including but not limned to, alteratIons. additions. deviations. and omissions from or to the
scope (If \\ork lntergraph shall provide City with a \\Titten assessment within a reasonable time
ldentifying the price and schedule Impact of implementing the change. Neither party shall be
obligated to commence work on the n.-quested change until they have agreed in writing to an
equitable ,ldjustment.
18.0 W\IVER
Ihe waIver by either part: of any (If its nghts or remedies in enforcing any action for breach
under this Agreement in a particular instance shall not be considered as a waiver of the same or
different nghts. remedies, ur actions for breach in subsequent instances.
19.0 SEVERABILITY
If any pro\ Ision llf this Agreement is \oid. voidable. unenforceable. or illegal in its terms, but
would not he so if it were rewritten to eliminate such terms that were found to be voidable,
unenforceahle. or illegal and such rewrite would not effect the intent of the provision, then the
provision must be rewritten to be enforceable and legal.
20.0 ASSIGNMENT
'\leither party shall assign' lr transfer this Agreement nor any rights or obligations thereunder
without the express wntten consent of the other party Such written consent shall not be
unreasonably \vithheld
21.0 APPROPRIATION OF FlNnS
,\11 partIe., recognize that the continuation of any contract after the close of any fiscal year of
City. which fiscal year ends on Julv 31 ot"each year. shall be subject to appropriations and budget
approval providing for CO\ ering such contract item as an expenditure in said budget. City does
not represent that the nudget item \vill be actually adopted. said determination being within the
sole discretIon of the City ('ouncil at the tIme of adoption of such nudget. Upon non-
appropnatilms. the City \\ ill provide written termination notice to Intergraph. Intergraph will
cease \\ork. and the City \\ ill pay lntergraph for \\ork performed up to the effective date of
termmalWIl
22.0. Sl BCONTRACTORS
Intergraph may use subcontractors in connection with the work performed under this Contract.
When using subcontractors. however. lntergraph must obtain prior written approval from the
City In using subcontractors. Intergraph agrees to be responsible to the City for all their acts and
omissions to the same extent as if the subcontractor and its employees were employees of
Intergraph. All perf~mllance requirements set f~)fth as part of this Contract shall be applicable to
I ntergraph (orpurat Ion
Pro Form.! \>2reL:ll1ent
Page 9
all subcontractors and their employees to the same extent as if the Intergraph and its employees
had perti)nl1ed the sen!ce'
23.0 VFNI'E AND .\PPLICABLE LAW
rhe parties agree that li)r all purposes. this Agreement shall be governed and interpreted in
accordance with the la\\s l.fthe United States and the State of Texas. The venue for any legal
dIsputes shall be the appropriate court in '\Jueces County. rexas.
24.0 COUNTERPARTS
rhis Agreement may be e",ecuted in one or more counterparts. each of which shall be deemed to
he original. and all of which together shall constitute one and the same Agreement. A signature
delivered hy facsimile shall be deemed to be an original signature and shall be effective upon
receipt thereof by the other party.
25.0 WHOLE AGREE MENT
Ihis Agreement ~ets forth the entire agreement and understanding between the parties relating to
the subject matter containl'd herein and supersedes all other agreements, oral or written,
heretof()re made between the parties relating to the subject matter.
IN WITNESS WHEREOF, the Pdrties hereto have executed this Agreement on the date
specified helov"
Bv:
t ) I
~'.
Inte~tph cor[)iL ~
By. "ijV~. : \
'lame: .~_~~Q.-\ R. i;jQ '""'
litk: t: 'fQ.c.v;+ : lie... b :\cht "',
City
Iltle
j ':
f .\ '
h2fu_1~{_~~~_1\J-t, 5-_
i '
+L].. {X ~..~t'1~~_i
'lame:
I late
,~ L ~Jl- \>
~0
~'~N.tNDU l)!-W-'A
an SiCRETAAY
Date: -2-- \ M. 0.. Ie.,,", ~oo lo
-
IJ.
" '''''S'';
Approyed as to form:
".l:':;'
\~ 2000~(.s. AU I hUt\I'-I..
) I.
~ -~i. I ni.
If l>>UNCll ._.._..2I.J..~~
A
It(: .
SECiiTA~ ~
. ~,_/,_J_"-;/
Usa Aguilar ,
Assistant City Attorney
For City Attorney
Intergraph Corporation
I'ro Form.! /\'-'ret:lllent
Page 10
EXHIBIT A - PRICING DETAIL AND SUMMARY
Intergraph CorporatIOn
Pro Forma \!i.reerneJlt
rJ:J.
~
....
..Q
~
~
rJ:J.
~
-
rJ:J.
....
<
-
Q
<
U
~
s..
~
~
~
~
....
-
~
=-
~
Eo-<
c
C
'"
;;-";
C .".
ri
(-'" ~
'" l'
v
C ~
:v
':.J .-'"
'j',
';:
1:-
~
,:- /'
er
g ,z
("1
v
o ~
C .-.
OJ
if c:
(f, r-
;;.- '-
~~
C ;;-
::: r
c ,/
or <'
oc
c:r:.
OJ c:
CJ) r-
"0 '-
~OC
CJ i.::
~ '/
c: ~
CJ ;::
C~
~
o
-.DO
~
or.
er
<A \A
-.D 8,
or.
<A \A
ClC
<r: ...,-
...;
~
~
v
i::
v
1) J:
:;;
:::
~ rJ
J: -3
1) ~
C .L
V
v: :;:::
'1)
<./) ~
E ;;;
~ J:
~
eLf.
:.:: v
~ J":
~ ,...; v
~ :J
- ~ --:
'"
;.-
1:: 3
o v
g; ~
::l -
Vl _
o
C
.".,
cr,
Vi
;::;:
Vi
~'-,
L.
~
..."
...;
v
-'f;
v
:v
:v
<f'
v
;-
~
;:;
:v
r.
r.
V
'J
'J
....
::;
"I
::;
C
'J
:.r:
r.
:<-
-"
~
::::
r.
~
'J
2
'"
"'0
"'0
...,-
"""
:u:
...
E
Jj
i
~
~
C :v
<f'
:.::
c:
'-'
:;:-~
./
<f'
:.::
c:
'-'
rl
v .,.
;;-
..... ~
c:=:: .-
("'J
"1"
,-...
~
r,
"1"
r--
'd"
...-:
....
'J
f
OJ
r.
~
~
...,.
Q
<:
"J;
'/".
OJ
'J
:v
<
V
Vl
~
.ro
~
C5
::J
::J
<
".,
--'
~
V
C.
J'
~
::;
'J
:v
:v
V
c.
:/'
c.
c.
...,-
"0
~
'"
"0
'"
7:
~
..
e
t
Jj
==
~
.I
-
-<
~
~
Conon
-.Do,-",o-
0,0, "'1-
on
('I
000
000
000
000
If) Vi ('fj
\A \A \A \A V7V7 \AV7V7
v~
v,
rl
lrl Ifj
,-... 0'
~"'1-
00000
~~~~~
If'; ('1 rr- 01 M
\A\A\AV7V7V7\AV7V7V7
c
o ~
'" ..c
><:";
C ""1'
(I"'" r)
r.
3 ~
c: :)
::.J '/.
'J';-
';:
E- f.
'J
C /
:.L
(r, :'C
~
rl
I.... I;
~ ~
c ,-..
'J
J::::c
s ~
"0"1"
;..'
3 rl
./
~ <f
:.::
5i; ;
"0 .....,
~ oc
OJ 'J:
6 'f:
0.... ~
1; 2
::J ~
- - - - - ("'J - - - -
8::J0000
<<<<<(<(
...":""G:""c..,c..,,
~
:::
0::::
5J
~
1)
r:
V
J:
'"
Vl
-2
'"
c;:;
o c -3
~~-~
-g '1) ~
::l ,2:
~ g g
c:r::: rJ: '..f)
::) C C
~ E E
-~"< ~
t ::l
o :.J
g;~
:::] ~
C/'i _
55
7:7:
>>
22
~
:::l
"0
o
2
.....
V
;>
.....
V
(/]
,
oJl~
C :::l
't -g
8.2
~ E
E ~
E~
~g-
.~ ~ ~
~ ~ ~
22CO
oJlv
c -
,- ::l
c:@-g
'g. [2
~ en _
'~ i5 ~
~ 0,) ~
C Z g
co
<( <(
~~
.....
V
C
V
(/]
~
8
en
^
(/]
~
c
t
o
0.
V
:.::
o<l
..... ~ en
~ ~ rJj
.8-o~
~ ~ ~
0."::; Co.
c5 :3 < ~ E
v~~~
;;Z:~Lfe
o c;:;
<(I
:'::"'2
CO:.::
o
'-D
.".
0.
:::l
-'"
o ~
.ro
2 ~
<(,::
~
CO rl
00
r-l f-;
r:.
g ~
V 0
><
N >
I 0..
:.J OIl
o "0
.....
M ~
.,t, U
0':':
o (:;
~ :::
OJ 0)
ifZ
~~
~ c5
o vi'
0..-",
'"
0:;0
o
00
or~
'-D
M
V7
V7
~
~
V
>''0
on u..l
"0
.....
~
"0
C
~
7:
V
'"
~
~
~
c;:;
o
C
:E
"0
u..l
X
::l
C
....l
V
,~
0. Jl)
ti U
C ~
CJ..l 0
00
IF)
~
M
o
o
o
r-f
"'1-
V7
o
o
IF)
o
V7
"'1-
o
<(
U
o
<(
U
'"
'"
Jl)
U
U
<(
Jl)
OIl
~
.ro
~
~
o
c
~
"0
C
:::l
"0
Jl)
oc
o
<(
~
.....
V
0.
t
o
0.
0.
::l
'"
.....
..c
"'1-
x
"'1-
r-l
x
,-...
'"
Jl)
'"
C
Jl)
,~
....l
u
t;:
u
Jl)
0.
(/]
0..
0.
<(
C
o
-
-
-
'-
o
-
<l,j
ell
eo:
~
=
.S:
....
eo:
e
l.
..s
=
-
C.
eo:
....
<l,j
OJ:;
Q.
o
l.
~
"0
=
eo:
-;
;:
:::
<l,j
"0
I.;:
=
o
U
.c:
Q.
eo:
l.
ell
l.
~
....
=
-
00.
~
-
.-
.Q
=
~
00.
~
00.
..
<
.......
Q
<
U
~
'""
~
~
~
C',J
.-
-
=
~
~
E--
:J' \f',
r--
r--
.0
~'l
::A 'A
::;--. 'f,
e-
C)
..-,: <'
-'
...
v
;>
...
v
cr
C",
o
o
<',
~
-;
!
E-t
r4
=
!
.!
=
Q,J
s
i
I
....
r
.-
"IS
::J
;: -,r
~
."'0
Vi
"E
0::
U
v
u
<.f:! ...
~ ~
t: :::l
f>
....
...
C =t ;;)
::> X
Q) -j'" ....
z ~)
r--
0::
:::I ~ .......,
o :;:j '"
1) (".,....,
r.r:. >, ('I
~ 'n C,/';
'" 0:::
o - :"_J
2 '
f
::J
-" 1
:E::'~
(J... 8
f> J!
e..:>o .'
; B
3::: oS
/
/
/
--
/
oc
'"
,f,
oc
~
v'
.--
J
Z
L
c:;
OJ
OJ
,~
OJ
"..) ::::
<
0-
::: "'D
o
o
~
<r.
'"
5 5c5
0, 0 ~ ~
If. f""--. o-~ ,...,-, If)
rl 1" \0 rj rf"',
<A
\A -./'; V't ;./: EA
'-
~
o 0
o 0
::. 0 ~
If, r- 0- Ir.
rj -:t.."c) rj r"".
<r.
'"
iA
CAA <A cF, Vt
<
,"'- .
<<0..-,:<
~ :::;,
v
"5 u
/. -g
2'
<-
OJ
~
~
t: OJ
:JJ :::
~ u
= 0
E ::>:
OJ
(J
~
;j ~
'f>
0::
~~
-0 t:
.... E
~~
<' ~
.... ~ ~
~ ~ ~ ~
t.o/:-l
~ 0 ~ >
...-:.....<
OJ
~
OJ
~
-"
.r
'i:
3
OJ
co _ oj
~e-g:JJJ
::J .- 0:: 0...
:.r Et-o
~~~; ~
7: .... ~
;f; 0 _ :..L.
~ ~ OJ
.~.2-g
.~ /.
:::l
:.r
v
:;::
V:
C
.-r"
~
~
""
,.
v
...
,7 ~
~ 2
0000
0000
~ 0,00
if'l ('--I r--: r-:
("'1 ("I "'1""'0
'l)
-0
:::l
'J
c:
Vi iA <A <A
~. g g;5
-~OOU
lrj 1'1 r--: r---: 1)
r I r-l ""1" ""'Cl
:::l
g
.p iA (/', <A
V1 V1
..-,:~~~~~~
0- ~~Ug:
L-
V
c ~
<~
~ ~
.;;
...
-'
(l.) V
.-- :::l
1.1 -g
.~ ~
(l.) V1
....~;:
... ... 0:::
,~ ~ 2 z
(f.. <(
w..
~
~ 2:
.;.<:
c:
-::::
(l.)
;>
'b ~ S
~<.-JO
!.;::]O....
...
~-5
~ C) r,
c.wo
0:::<
OJ
~
~
OJ
j;
z"
0..
:.r
:::
-'
-'
:3
'.t:
t .-"'",
o 0..
o....;..c:: C
c~:--~
JJOv;~
.;.<: ~ ~ C ~
c(/) <-:
o ~ (j) ''1::
<:5~~~
::- <(
00
00
0,0
"'"
~
iA <A
00
00
~o
"'"
~
<A <A
~
~
:::l
-0
o
~
OJ
(J
~
OJ
'i:
V1
o
<
W
....l
...
OJ
..t:
(5
t
C
0..
~
~
~
-2 ~
1)
" '6
0..
'- X
~ W
o v
... (J
2~
V v
(J E
;>
v V1
Ow...
~ <
o V1
~o
V <
a:iw
'-",J
.=
c.t
&I
"IS
"S
~
'""
~
t
~
Q,J
u
J!
'""
.a
=
~
=
=
.-:
-
~
.a
=
a
I
<.:'I
U
'-0
N
0- or,
r--
r--
<A <A
0- or,
r--
r--
'-0
<'l
<A <A
c
<
~
...
, V
('"'1 C:
~~
< C".
C::5
co <',
O~
~ c.n
~"'2
o ~
~ 0,)
'-' u
u <.f:!
o ...
... V
0- 'i:
t:
o .;.<:
'-' ...
>< 0
N Z
:c '-'
OZ
o '"
r') :::l
..,t 0
o u;
or,....
00 u;
'-00
V
:>1)-
~9
t <
~ 0:::
rfCO
V
0:;'-0
O~
t
o
0..
0..
:::l
V>
...
..t: ...
~~
x 0
~ ...
';.) c
I"- 0
V> U
...
ro <'1
v r')
>. <'1
<r, ~
g g K:
- >.-
u u; U
W < C)
v t ~
~~~
~ 00 ~
c: u
~ 0-
...
, Q)
<'1 ;>
...
~ ~
<M
0:::5
co <'1
o ~
~ '"
"']
o u
Vl <l)
~ u
u<.f:!
o ...
0: E
5....
v ...
>< 0
N ::>
:c '0
CJz
~ ~ ~
..,t, 0 ~
c vl ~
or,....or,
00 V>
'-00
v
en -
Z39
ii <
::> c::
C CO
0-0
0:;'-0
O~
0- 0 0
1"-00
- 0 0
--DOO
N ('~ -
<A <A <A
0- 0 0
r--oo
0,0
'-D 0 0'
<'I N
~<A<A
V1 V1 VJ
~~~
C::C::C::
0-0-0-
Q)
'3
u
o
~ '-'
v'3
U;u
ro 0
co~
VJ V1
~~
c::c::
v v
.~ u
00
0-0-
t
o
0..
0..
:::l
U;
..c
~
x
~
<'I
:><
I"-
c a
.g t ~
;> :>I)
"'0 t ::s
w'1~
~VJV1
";:: 0 0
1:- < <
~:J:J
w::::.::o
-
-
....
o
M
QJ
ell
~
~
=
o
".;:
~
e
I.
~
=
-
c
~
-
QJ
"i:
Q.
o
I.
~
"0
=
~
]
-
=
QJ
"0
l;:
=
o
U
.c
Q.
~
I.
OJ)
I.
QJ
-
=
-
,::!
....l
...
v
u;
:::l
E
~
u;
>.
r/)
v
::;
E-
o::
u
(/)
2
a:::
e..
o
o
23
';;j
t:
'"
,..
.;:;;
<
OJ
00
o
.....
e..
~
o
u...
(;j
::I
'"
:.>
,-
o
'"
2
.~
2
~
("'I ".;
~ 2:)
L f
-<r" -r
X =:
:c '-J
'-" "'$
C')
or
t. ~
'J
~ ()
:; '..J
~ ~ :
...
t
cJ
.
.&- v ~
- '/ ::;:
~ ..,-
~1J-r
- Z ~)
r-
oo
r-r, [.
.J: ,-, ~
(f:, ;;'-,
lr, ~
~ ~
u
OJ]
-0
f
a.; <
1 ~
I
I
v
~ ~
~C/:
~ :I
.;:: ::::
2-4
aJ~~=
c:::
0-
r-
'"
'"
-0-0-0'"
Q) (lJ Q)
-g"g-g
~ g g g
-0
'" OJ
('j -0
::I
,f.
r~
-0 -0
:; Q)
rj -0 U
'....J U
J, .-- t:
fC/:C/:./l(/)(/)
:>::;;2222
~~g:g:g:g:
:"
::::J(/)
< 0
~ -<
-E
;$
..;..: 2
C 1) _u
-l U
~-6
:jj O.J 0
2 C 2
~
/~
OJ
~ "'0
X 0
2
f (/) )j
L 22
xx a:::
'l.J CJ 1)
'-...I .~ ~
&6::
'.J
.....
OJ
'J',
,..
~
:.r:
,.,."
C/:[
~i
~i
,~I
vi..;..:
a .::
-'= -l
~J 0
::I <
2"...J
r} JJ ~;::~ ~
o 0 ~
:5 :3 <E c
~ -l:- ,:::!
/.
tA
\C
,~
\C
tA
"" (/)
ti 2:
::I a:::
o OJ
o (J
< ~
vet
D
00
2
e..
:;;
'JJC::
o ~
<( 0
wu...
"J~
'"
2>
;::
oo
] .;
~ '" ~ cI
"0 ""2 ~
F~ l~1
~~!~[!
~ ,.
". )t':
/. U ~
< / >'
x r--
r-j
,..".., /"""'0. ~
OJ
'-'
C')
~ ~ 1'"'.
J1
J1
:.;~"'O
"..J __ __
,...,1-. """T ,.
a.,
G
j
=
4
.!
&
I
:::So
-t
2) r J
'/ 'J ~
..::: ;!j ~
r_ :::" e-
8
~ ,..
.~ :J..:
,....
.".
f-
Ir, -J:. ""0
::'.10 /) 1)
..c ,.... a:::
'-'
~~
-"
/0
/ lr,
"1"
9:
r--
C')
'h
g
r--
C',
',/'.
C/:
L
a:::
e..
.;,
oo
~
Vl
If;
Vl
-t
/J
::;;
a:::
~
J1
J1
OJ
U
U
<(
OJ
J1
OJ
..0
OJ
:;:;
o
/J
L,
/J
.,..
L
a:::
.~
c.
./'
~
u
'.)
'J
'J
5-
J'
c.
c.
..-r:
-0
-'-
...
E
~
j
a
&
..;..: .....
,-IJ C ~
:: ~
2: aJ rl
<( Z (:
0::: C; if;
:c ::I l-.
.:= 0 ~
("I t.f. ?
< if,
t: co
o J:
<f.
:G ~
g ~
,..
23
-
-0
:.J.J
..... ;...-:
.:0 ::I
,. :::
OJ rl
~ .~ ~
C c..
::; 0 ti
- C
S ~ LLl
~ 0 ce
o :.rl.......
~~~
\C0a:::
OJ
~J - :/1
~O;::
- ,I:"::
OJ -< .~
~ a::: C
O::CQ~ 0 CJ
O.....a.u
~ :;: ~ 0.. ro
o ..... '" 0
"1"
~~
r--
('I
CA
fA
"T
a-
D
r--
C')
J::
2
a:::
'"
'"
u
(J
(J
<(
OJ
'"
OJ
..0
OJ
:;:;
o
(/)
2
-.
cJj
2
a:::
V
a.
'"
Q)
'"
:::
OJ
u
-l
u
,-
....
u
OJ
a.
/J
a.
a.
<(
:::
:;;
-0
:.J.J
;::
(Ij
;1
(iJ
~
OJ
Of,
(Ij
..0
(Ij
';;j
o
a.,
E
r.X
=
~
:
8
.-:
...
:::
o .....
Q)-'=
><-;:
D"1"
~! ~
(Ij r--
::I ~
::::J (Ij
Q)
,; ;>,
. i: If)
a.",
v U
]z
,~, ~
80
('J
..... '"
Q)~
c
Q) 0
VlCO
~ 0
o \C
-o=:
::: ><
;:::N
02
on <(
00 a:::
Q) co
~o
WOO
ti v)
;$ (:;
o '"
a. ~
u
Q) 0
00':
.(
-
n
t
II
"....
II
"!
E-t
- 0 0
\0 0 0
- 0 0
. 0 0
<A {A <A
00
\C 00
o. o.
00
OVlO
<(2<(
ug:u
OJ '"
:; ~
-0 (Ij
0..0
2 ~
Q)-O
'" ...
(Ij Q)
co-'=
o
Vl
2 2
a::: 1:l
Q)";::
.S? ~
~ c
.....
Q)
>
.....
Q)
Vl
~ ~
tOE
~~02
g- ~ ~
'"
-
-
....
o
!")
~
OJ)
~
Q..
=
o~
-
~
E
J.
.$
=
-
c
~
-
~
oj:;
Q.
o
J.
Q..
"0
=
~
~
-.::
=
~
"0
l,::
=
o
U
.c
Q.
~
J.
ell
J.
~
-
=
-
rJJ.
~
-
:.Q
Q
~
rJJ.
~
-
rJJ.
-
<
-
Q
<
U
~
l.
~
~
~
~
.-
-
Q
~
;;<
~
a;
~' 'f
c.. if
;:; l-
E ;;
~
""
c
.... 'J:
a;-'""
>- if
;:; C
C/': cr:.
C
'.S
""'t
>'
::: r 1
;::
<"
Q::
a; 0:
.gfc
w.;OC
...
~ ~
C 'J:
0... ~
(.J
c
C:.
o
-c 0
'r~
r-.
l;F4 (A.
o
~ 0
.n
r-.
.r::
""'t
,
""'t
rl
,
r-
~
0.>
OJ
;.
t: ::;
,.... 'j
;?-~
S-~
v: ....:..
1)
~
:$
'.:::
:J
:./1
U
;.
"
:.11
OJ
n
:<l
..0
:<l
;;;
c.::l
c.::l
~
...)
"-t ,=
:::: /'
L ::; ~
<1" 7 "
rl
~
== ~ ~
'J
rl
~ :::
r
~f
i: ::c "":J
; ~
.:t
1) r"_ J
/'
..
~
to;
~
Q.l- ,-~f 3
I ~ ~
.:::l c' "
S..J-
!
....
~
'-
>r-
oc
~
a;
':J)
~
=
'i
...
E!
r-
1:; ..-f -/
~ :; :~ ~
0: '~
~ 2 t
::<~
/C
,-' f
'J
OJ
;!~ r.
f
-:;. "B
x
""'t
g
F-
e
V'
-;
'"
./
'"
:::
=-
,
(.J
~
(.J
OJ
c-
:r.
c-
c-
<"
/C
""
"0
:L
'2
'"
;2
(;3
:;
OJ
<f
'"
.r::
'"
;;; ...
C: J:
v rJ:
OJ
U U
e 2
c c...
c
~,
r-l
""'t
SA
If.
.-:
'h
""'t
:r.
L
X
C:-.
f
'f
0.>
'J
'J
<"
'J
~
.c
~
;:;
c-
<f
~
V
(.J
c
~ 1)
o
~ C/)
l. 0 ~JJ
-.,..
!~
~~
Q!t
=
,S
-
s
.f
~
l.
=
,~
to;
=
rLJ
I:;
~
S
-
-
'"
o
I:;
~
.=
~
'"
.~
=
'i
=
:s
a
=r,
u
00
00
0,0
o
oc
{;A V':
~~
'./', E
:::J :::J
w..
O'lf'.QOO
0' rl 00
r--- lr, V)
~ 00 ('#"',
rl
r-l c
~ 2
C/) v
0::::--.:
r') rl 0 ""'t 0
t'-O'""'too""'t
":\f)NNrt
oor-: ."tr')
r')
o
o
0,
lr,
~_-oC'~'0g:~
<_~ r-lfJrlM
rJ". --T oc
'f
:::J :;
1j
<f
1:
<1"
X
x
..-.
L
OJ
~
'J
~
<
'-D 0 r-. 0
-..0 0~ IF, r-
"'T~ ,.-r-, rl
('I rl ("I r~
o
<"<"
v
0000000
</<<<<<
vvvv
:L
:[)
""'t
'r.
r-J
~
"0
a;
-0
::l
U
C
i=A-&AV}'6A~-{;F;ti"7VAr.A
0'
-00'
a;N
~
::l
u
C
- - - :;.c. ("",
'h cA iF, cA cA cA cA Vl Vl
a;
~
:$
Q:::
o
'"
...
IlJ
.:.:
~
OJ
V
C/)
0.
OJ
c
.S::
tl
c
<2
OJ)
c
:E IlJ
~:;
"'-0
0..0
.~ 2
o c
-g .!!:!
~u
c OJ)
~ .::
]g ~
OJ 0..
U IlJ
~O:::
V1 v.
r-I
o
< ..-r
l-
~..J /'
~
Cf.
... ..-.
~ ~
.8 ~
'"
0..
'"
'J
:::J
~
~
c.
v
X
::.::;
1)
;r
~'.
:.r
OJ)
t:
c-
O.>
X
<
!.
~Jj
;;
..c.
g ~ :.0
~~--
:;1)c-c-
==~~
.;::; 2. 2.
'-
o r'"'I ,........
c..~~
C.J < --<
xGv
o
'f>
c/)
.v
'-
~
2: /. :;:
:?
:?
~~
1[, c;-
o-
<(
0::
f-
c[J
.!!:! ;.-.
u2
IlJ
E ;;;
~ E
",.c
>. u
C/) B
01)<(
c ~
'E c
[.,g
v '"
x:;
Cd E
'" w
"Vi ce
>. c
OJ 'E
c '-
'" <( IlJ
o....;f-
,~ OJ) R
02 r1
::::::;::::::;("rj
o v
0- ~
0..
~ IlJ
g.:;
-0-0
<( 0
0..2
o .:.:
~~
Oeo
00
rr; 0
00
rr; M
C C
o 0
... '-
t) t)
NN
\D
0'
... -0
IlJ IlJ
E .c
o '"
t; c::
:J ...
u~
~
'- -0
IlJ IlJ
E .c
8 '"
'" C
:J :;
Vw..
~
c
.g
'"
c
OJ
'"
OJ
'-
0.
-
-
.....
o
~
~
ell
~
~
o
<C
v
c
o
"':
C':
E
l-
..s
c
-
"0
o
f-
OJ)
c
'E
o
0..
IlJ
0:::
c.
C':
-
~
OJ;;
Q.
o
l-
~
"=
c
C':
C':
:;::
C
~
"=
!.,:
c
o
U
.c
Q.
C':
l-
ell
l-
~
-
c
-
OJ
c
,S::
<f
'"
~
o
'-
0.
r'.
o
o
r~
IlJ
u
~
"-
o
a::
o
'"
o
...
.~
2
fA fA
trj5t-o
::::o,~~
of. C
....
iF; iA
j)
j)
~
~ g
~<
'-
OJ
:::l
-0
:2
/.
.~
:....;
~
....
.:>
0.
u
0:::
u
;-
u
'j;
~
:r.
~
....
:>
0.
u
0:::
~
'5iJ
~
:..-
.....
g
~
t
o
0.
OJ
0:::
:;j
:>
j)
j)
(j
~
cr,
o
::0
r.
(j
OJ
,-
,.-.
-
8
,-
-
:>
j)
2
'j
./.
V': fA iA
c 0-,
g~ ~ ~
V': V': iA
;:;:-;!~
vc...:....;
000
L22
v
C
t.J 2:
:::l t::
-g .~
/. c... 0
V; .0
1:; ::?:
v 0::: ~
'- ij ~
1:: ~
/~C5
t
.
&
~
f
.2
::J
=-
S
c:>
U
s
!
.i~
:S-g
~-;:
("'I oo'nQO lr'i(".l 0
O'Nt'--ooNO'oo
~ 0'. 00 ~, \0 ("I ~
~C:lr:~oOl.J5r<'")
r'; r"1 r"; 00
fA V': lA fA fA fA fA
~~~
DC
'::' C
or, DC
"T'~
,r
00 If,
00 r~
r'"'. \C~
'r; r-. 00
rj ~i
DC .XJ OC
0000 OC
<P 'A EFJ 'r fA fA <P <A fA
00
00
'--.)v'-'v:....;0v.'-'
000000000
::>:;;:;;::>22::;2:;;
~
:::l
'J
'l) ':.J
OJ
-2.~
~ ~-
..-r
~
i)
C
J: ~
CL t:
'-' 0.
'::; v
f v crO OJ
_~.'~ ~2
.. U s::;:J 0...
= Co .- c
:0 0..
f1 ~
v~
t: V
~ ~
;:! v
5 ~
c oIl
< 0:::
c...
0:::
I..l-
< 0
, N
V; or,
::?r-
0::: ~
J: 0
o ~
<..::
u..; en
e
:....;
I -~
d~
.I~
" ~
.I:':
AL
<III E
=~
'"
'J
<1"
~
.... ::l
~ ei)
OJ t;:
,;>,
c
~ U
~ '-'
c;
::s ==
-0 .E
~ .~
c..:r.
o.CL
::l ,~
v: v ..0
l-. "- 1) :)
_r-, _2S ~'~;
'-"C:,..:;G~~O
.~ ~ ~ ~ ::I ~
:::ij'"O~~-
::l gf..e-"E v >
Ir. :::: c.J .,g ::: ...J
4-ce...t:: ~""'O
;. 2 ,::: ~ oIl ~
::3 U == '';:: .:: ...:...
~ .~ ~ 5 ~ ~
~2o.2:'<:~
:r. CL L V;
c...CL
vv
< <1"
.~ CLCLCLc...CL
:"";:"";:"";:"";0:"";
<<<<<<
000
000
c::. 0, c:
~trjO
r'l
(')
fA fA (,A
ggg
If) ~ C,
fA fA fA
~ If, c-I
:r.(/;V;
2.,...:;;
0:::""0:::
CL-'CL
V;
::;
~ ~ 0:::
~ ::l OJ
-0 -0 ::l
C 0 v
:;; :;; c
~ C 2:
:....; ,~ .~
U
:r.Vlc...
L L ':JJ
0:::-,
1.) U lo-.
U U ~
o 0 OJ
c...0..0:::
c v
v
~
~
,..
<<
&
~ ~ ~
c VI ..,.,
a v >>r/)
<III - VJ :;IJ
;:c...ct:
S .9 1(~
!d~~e-
...C)~o:::
~~~~
~ ~ ~~'
~~ ~ ~J
o
.... -0
0) v
E ..::
2 en
'Jl E
:::l :::l
'-' :..-
or,
VJ
2
0:::
0..
.:.-.
~
;::::.
'-'
o
.0
oIl
t:
'E
o
0.
C)
0:::
'-
'"
o
o
(')
0)
.~
,....
o
<t::
o
en
o
....
,~
L
~
C)
>
....
C)
<f>
....
C)
C
v
U
en
is
c;
.~
t:
:::l
E
E
o
u
.2
....
.g ~
\0 5 ~
-62-6
o 0 0
~<~
ouo
;Z:w;Z:
_<f> Vl
-::::J
(ij >.. 0
~(ij:c
>.2~
~~I..l-N
o
o
o
00
'"
"T
fA
o
o
0,
00
M
"T
fA
2
o
u
c
C)
E
C)
OIl
~
t:
~
2
-
U
C)
'0'
....
0..
-
-
.....
o
~I
QJ
eJI
~
~
=
o
;::::
~
e
l.
..:
=
"
~
-
~
.i:
Q.
o
l.
Q.
"0
=
~
-
.:::
-
=
QJ
"0
lo:
=
o
U
.c
Q.
~
l.
eJI
l.
QJ
-
=
-
I 0 0 0 0 0 0 0 0 0 M -.0 :=0 0 Q 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 ~ 0 0 -.0 or, ~ 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
C!- or, q 0 0, 0, c. q Of) "'1", 0, ~ q 0, 0, q q 0, 0, 0, 0, 0 0, 0, 0 0 0 0 0 0 0 0 0, 0
l'-} ~ V) n or, a:: r-- n r; c ~ -i ,-, ~I -.0 lr. '" 00 "'1" ,r; -c '" or. 'r. 00 ...: or, V) ~ ~ ~ ~ ...: ~ -i ~ r-- "'1"'
'J'1 V) - <'1 0 <'I rl - - <'I -
N - rl -
:J I 0
i
liA <A Vl fA VI VI Vl eA 'F fA I"" fA ,A fA .A "" fA Vl Vl Vl fA VI Vl Vl Vl VI fA fA Vl VI fA VI fA Vl Vl Vl fA
~ 0 0 0 0 g, 01'" -c 0 0 0 0 0 ~ 0 0 0 r-- 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 or; 0 0 0 0 0 0 ~ 0 0 '" 0 0 0 0 0 0 0 0 0 0 0
l'-} o. or, 0 q '- c~ ~ "'1", q 0 0 0 o. q q "1; >0, 0, 0 0 0 0, 0 0, 0, q 0 0
'J'1 g V) <'I or d- r-- <'I o!"""1' ,- ~I ~) .r -i n - '.':; -.0 If"; or 00 - - or, ~ ~ ~ \0 ...: \0 "'1" \0 ...: -i
V) '.':; -- <'I '" r, r; - -
~ N - r-] -
liA Vl fA tA VI "" Vl iF 'F ""IA VI A <A ,F Vl Vl Vl Vl Vl Vl Vl VI Vl VI Vl Vl fA Vl Vl VI Vl Vl Vl Vl fA fA
cr
~
- - - -. - - - -' - - - - :.r; - -.., - - r-- ~~ ,r -, - - - - or, ,~ - - - - - - - - - - -
:'::
~
~ Cl 'J: C 0 J: J: (/; :/: (/; J: (/; C C :: c 0 0 0 C v 0 0 0 0 v v 0 0 Cl C 0 (/J (/J (/J (/J
2 2 2 ;; 2 2 2 2 (/J 2 2 2
0 <t: <r' <t: L --1" <( --1" ...,-: ...,-: ...,-: <( <r: 0 ...,-: ...,-: ...,-: ...,-: 0 Cl ...,-: ...,-: ...,-: ...,-: <t: 2
u u ::.:: v c:: c:: c:: ::.:: c:: ::.:: c:: ',-"" ~ v v v v ::>: ~ v v u 2 2 u u u u u c:: -, 0:: 0:: 0::
0- v ~ 0- 0- ~ 0- ~ ,.. -' -' 0- 0-. 0-. 0-.
-- I
N I
~
'4
'=
'= I
N
f'f'l
'=
01
-
~ $:
- .e
0 tii
= I
I
e c:: I
-
~ .. I
- ~
~
\J'J. i - - or, "'1" r, ,3 or. -c r-- C' 0 <'I - - <'~ - M "'1" r-- M M or, 00 0- 0
C 0 0 0 ~ 0 0 - 0 0 0 0 0 0 0 0 0 0 0 0 0 -
~ <: -' c -' 0 0 0 0 0 0 0 - "'1" Of) Of) - - - - 0 N <'I N N N
- - - - - <'I n <'I ~ <'I ~ <'I 2 <'I <'I N M M M M Of) N ('1 N ('1 ~
.. '!::l - f- - f- - f- e- f- f- f- >- f- f- f- f- f- f- f- f- f- f-
.Q ~ (/; (/J ;j: V1 (/J V1 VJ ;j: (/J VJ (/J V1 VJ V1 VJ VJ VJ VJ VJ VJ (/J VJ VJ VJ VJ
0 0- 0- 0.. 0.. 0-. 0.. 0-. 0.. 0-. 0.. 0-. 0-. 0-. 0-. 0-. 0-. 0-. 0-. 0-. 0-. 0-. 0.. 0-. 0.. 0-.
~ - - - - -
\J'J.
~ -
or,
0
\J'J. - ('I
- - n <'I
< .- - 9: 0 - f-
- g c Of) M VJ
-- - ('1 0 0-.
~ - - rl - f- 0 -
- f- n VJ Of) -
< <Il t: I if: 0 0- f- '-
.llC C 0- f. 0- - - VJ <l) -
~ I - - C
U Co - - - r'1 - 0-. '~ - 0-
Co - - - - Co "'1" 0
::l =: r - V1 c 0 ~ '- 00
... N
~ V) if: - Co ... ~ - Vl f-;" 0 N
... - C 'lJ Vi e: N
- ,r; f- -
.. 00 '- - ..c: - -t f- ,2 OJ N 0
~ M <l) ~ - - f '- v; ... ~ f- VJ -
> I ~ ~ -g - - C - VJ ~ 0-.
.. ; I ;I) <l) 0 - - VJ t"1
~ <E ::; 'lJ - - 8 - ;- C ~ 0 0.. - e: 0-. - t"1
::l - or, IU - ~
>. r, ::: ~ ~ r-- '~ f-
I :.r,. :$ 0 c - "'1" ~ - 0. M ~ 0.
1 .~ ;:; - C ~ <'I 0 fo 0 n 0 M en 0 0 0 '- 0 VJ
~ '- - .~ - cr. 0 <'I - en f- f- E - N f- ..c: 0-.
:3 ::l :r. - n - Q M ~
~ or 'lJ -" 0 J: C e: if: (=E VJ <l) 0 N ~ Vl -
f. I ~ C' ~ ~ - f- r-- f- ~ ~ ~
.. ~ ~ ~ VJ - 0. <'I 0-. e: - f- ~
- ..c 'JC C. e: ~ -0 e if: c f- E - :; en VJ ...,-: ~ 0 -
0 .. OJ ~ - 0- g <l) >> VJ '- 0::
u 1 ~ t"l < C c e: - 0:: - OIl - 0-. ~ or
Cl.t c. ,~ ! U - - :':: ;n - <'I v: -a c v: 0-. >> 0 3: u..
~ ~ ~ - en - f- 0- <t: V t;:: - ~
~ 1) OJ :r f- :oJ) -0 0 0 ~ Vl <(
~ V ... en ~ - ~ -
~ ... u ~ > ~ ~ 0 v: e: t;:: en '" ~ VJ - ..c: 0 M V <l) ... ::: ~
0. 0-. ::; 1) - 0- ~ ~ c.. ;a -a u - g 0 ...,-: u .~ V C <Jl
~ on ~ u 0 0:: - c VJ - OIl e: (;j - v e: e: ,~ OIl
~ - ..: -g 'lJ ~ ~ - C 0 ;:; ~ ::L - '" C '" - ~ '" -l IU e: e:
;a .::1 ~ v c 0. 0 en M '(;j E >
.- V t: ~ 0 Q g- :':: OJ v; (j - e: v; Of) ~ f- e: E '- 't
... ::.:: > c > $: v; en - ~ e: V 3 ,:: 1) V
.. e: / ~ 0.. -a en ~ V ::l .2 <'I (; 2
- t;j ~ ~ 0 0 0 c 0- ii:; ~ 'c :3: en ~ en en 0 f- VJ C OIl -a > 0
0 '5 D.. Vi ;a w w ~ (=E E 0-. ... v '" 0 D..
~ ~ '3 -< ~ C V OJ ~ JJ '; C gJ e: u C OJ JJ ~ - '(; <l) e: ...,-: V
.. ~ 1) ~ u ..:.: Q en VJ 0 ... -a <l) > ~
... ci'; v OJ 0:: v; 0:: l- e: OJ ::: OIl en ::l ~ 0-. 0 - 2 '" E E 0::
> ;:; t: u E- O E c en <Jl OJ <l) V <:;: <r: ... u 0 2
-= '~ e: ::?: :.:; <Jl g ~ V ~ '" 0 ~ ,- <Jl en en OIl ~ v I:: '5 e: ~ ~ -a
V V Z ~ ~ a ~ 5' <:;: ..:.: C v en '" t; t;:: ..:.: E v; '" 1=
U -, OJ - , '- 0 "e - <Jl Vl ~
E 0. OJ V u ~ <Jl '" .D C V ~ I:: E u
V5 ~ v -a OJ OJ v ..:.: OJ e: ... ~ ';a >> >>
0 ~ '" D.. or OJ '" 0 en OJ
GI'l v ::L :.:: :.r. ;;: M B ~ 0. 0 v; 0. '" 0:: ~ "e v ~ :3: en <Jl C <Jl '- -, Vl VJ u..
~ Q. .,.. - ... "" u OJ c;; V v ::: c2
= t 2 E ~ u v: f 0 ell 0:: ~ ::l >, "0 >> VJ Vl VJ VJ VJ
.5 0:: ~j < c ,..., v ~ ,r [I) C C. v 0 VJ :.:: '-J 0 f- JJ v ~ ~ VJ 0 '(; VJ 0 0 Cl Cl 0
~ 0 - c:: .- 2 t:
... '-J D.. 'JJ <( <' c ...,-: ~ .:: 0 c c 0 0 c. 0 C. :E 0 0 > .D .D Cl t- O 0 <r: ...,-: <t: <t: ...,-:
Cl .;d ,..., Vl '" 0- 2 :c 0 ...,-: OJ 0 c C D..
0 0. ..... .,.. ~ l..L.: - ...,-: ...,-: <( <1' ...,-: < ..-:: ...,-: <' <( ...,-: ...,-: D.. ...,-: D.. W W W W :J.l
U <t: ? <I: 2, 'lJ ....; - (,..; f ';J = v ,.., ~ v ~ v v ~, 2- V l,; ~ '7 2 ~ ~ ...,-: '" ~ ::l ~ ",J ~ ~ ~
U ./ V 0:: N Q., ~ V 2 VJ
e- - - - - - - - - - - - - - - - - - -
-
-
.....
o
'C
~
0lI
~
~
=
.2
....
~
e
l-
.E
=
-
~.
l-
~
....
~
'i:
Q.
o
l-
~
"0
=
~
-;
'';:
=
~
"0
!,:
=
o
U
.c
Q.
~
l-
Oll
l-
~
....
=
-
t 0 0 0 0 on ; 0' 0 0 0 11)< orl 0 orl - '-&I ~ - - ..- ..- - ..-
0 0 0 0 I"- '<t 0 0 0 = 0 = N N - N ('I ('~ N ... N ... N ...
0 O. O. 0 - 0', O. 'r; ('~ orl 0 orl 1"-. N r- l"- I"- l"- I"- -a I"- -a I"- -a
~ ~ ~ c: = -a r-: r-: -a -a -a ~ -a ~ ~ ~ ~ ~ ~ ~ ~ ~
fiiI7 - '<t .... .n ('] 00 I"- ~ >.D ~ >.D ~ >.D ~ ~ E ..c: E ..c: E ..c:
rJ1 - >.D ....... - 00 ,." -a - ~ ~ -a - -a - -a ..- -a - 0 '" ..- .8 ,~ ..- .8 ,~
,." r, ~ ::l r, N = ::l r, ::l r, ::l M ::l M ..... M M
~ '. I ..; - .-i ..; r--~ U '" ~ '" l:: '" l::
u ~ u U ::l ;:: ::l ... ::l ...
I ! l:: l:: l:: .= U ::l U ::l U ::l
- - ..- - '"- '"- u..
~ <A V'; Vl V'; Vl V'; V'; if; V'; Vl V'; Vl V'; Vl V': Vl Vl <A <A <A V';
~ > ~
0 ~ 52 0 'n 0' 0 0
0 0 0 0 I"- '<t 0 0
fiiI7 0 0 0 - Or ~ .r ('l
rJ1 ..- >.D" -i .... ..0 Ir, ('] 00 r-:
~ - >.D
~ lA V'; Vl Vl Vl V'; Vl V'} <A
- - - - - - -.- .. - -- - - - - - - - - ..- - ..- - - ..- -
I
......
~ r/J v: r/J V; - - ..- - ~ :- ~ ~ ~ ~ ~ f- ~ ~ ~
:::f Vl :::f ~ L ~ / ~ / ~ .2. Z Z Z z Z ~ ~ Z Z Z Z ~ Z
~ / ,..... 9 ,.... 0 .,.... 0 0 -
f 0:: n::: 0:: n::: '-' '-' ~ <( <( <( <( <( <( <( <( <( <( -< -< -<
0... -, " 0... 0... V '-' '- G G V V ..,... ~ ..,... :;:; ~ :::f ~ ~ ~ ~ ~ ~ ~
/. /
I
]
-. I
M
]
'-= I
~ -a
~ I rIJ
= ~
M 0
f'f') ''': :;
~ ] <r.
Q. C/O
I ~
I ,-.
-- -'
c
Qi I "0 0..
- i =
= I ~ E
= ~. rIJ ~
= X
~ .2
~
I ~ - X
a fo- Q. ~
I 0 ,-
Qi ~
- I "0
rn ~
= =
rJ:J. - N r-r, "1" I"- ~ ~
- - - - - = ~
Qi N ('l rI ('] ~
- N ('] fl ('] - ~
... ~ - - '- = ~
.Q r/J .~ :r; C/J .; :I:l
= e: c- o... ..... fo-
~ - - :;
]i. - ~
i- ~ -.
rJ:J. f! = ~
~ :I:l I
.. = -
; ~ = .>> >.
"" ~ "" E ~ >. E
- >- >. E >.
"" >. E >. >. e
= >. ~ e E >. E >.
rJ:J. ~ E >. ... E ~ E E ...
-Q ~ .- - E ... ~ ... e E ~ ~
..-01 ~ '" = ~ ~ ::a '" ::a ... ~ '" ... e ~
~ II: :; ~ -; ~ ~ ~ '" t: ~ '" ... ::a ...
C) ...: ~ '" ~ '" ~ '" ... '"
-a '" ~ ~ ~ ~ -a
~ = c ~ ~ :; ::: ::: -a -::l -a ~ ~ '"
,C, fo- ~ '" -a ~ -a -a -a
-< ~ t ~ rIJ -a -a "':2 ~ -a -a '" -a -a ~ -a l::
~ c.. = ~ OJ U C ~ ~ c -a ~ ~ ~ ~ '"
u - ..: ~ "0 -a ~ OJ 3 -a c ~ -a X
N rr "0 -a x ~ -a
- c = "" = B l:: X '" V V l::
- 0 = V l:: X ~ X l:: Q) UJ
~ ,-. ('~ rl (,I :::l :.. ~ - .... !I) W LJ x ..... W ..... ~ x .....
N X X ...
... = rl ~ 'i'O 0 'f.. ~ ~ ~ x >< t w..; w x W x OJ
.. f- - !:;ril E ~ - ~ 'J'l ~ = ..;... ~ UJ .... ... w..; UJ W q::
tJ r/J rr 'r.. q:: 2 OJ Q) ....
~ ./0 rIJ -5 = - t t q:: '" t .... OJ .... '"
0... ., OJ ~ Q - .... '" q:: ~ q:: q:: OJ
~ II: "0 c E ~ .~ ~ q:: C) C)
~ ~ - .... ~ U 0 '" 't:: OJ ~ '" 't:: ~ 't:: u
t - 0 .... v ~ ::a ~ = '" OJ '" OJ '" '"
l:: E ~ ~ '@ ~ ~ OJ U C) '" OJ l::
,:2 ~ - c.. E "0 ~ ~ u <a ~ C) C U C) C) ~ C) ~
Qi '-" .~ ~ .! ~ L = ('] - U '" ~ U '" l:: u u u l::
e;j ~ ~ = ~ U c <a l:: ~ C ~
~ C. r- ~ .- - ~ ~ - ('] fo- ;a c OJ 3 ~ c '" C l:: E
... 0 E - - Do. - - 0; OJ V ~ '"
- ('] l'C 0 ;;; ~ rIJ 2 ~ .... .... '" E ~ l:: E ~ ~ C
C 'fj; ~ .~ ('] - r-l .... <2 <2 :; ... ~ C '(;j ~ E v C) '(;j
~ ~ 'i: - f- ~ ce :r. ';:: 'J1 OJ ~ e 3 ':;i l:: '(;j t: E ~
.... II: ~ .D ~ L ~ .-
0 ,.... -r C/J .- ~ eo.. eo.. >.. eo.. ~ c: ..- ~ '(;; L ~ ';;j
, - ..... "3 ~ .... '" L ~ ~ .-
~ -....) 0... -a 0 0 l:: E 0 , .~ ~ '" ~ C)
~ ('I ~ i::: ~ C) ~ ~ :::f ~ ...
rI - or '" >. e 0; ~ ... ~ ~ '"
Eo- <;; - E ~ ~ ... ~ '" ~ ::a ~ OJ 3:
~ Q) ,- E C"l - -::l , - , '" ... , = ~ 3: '" OJ '" ~ OJ ... ~
~ C) U < ~ ~ ~ ~ ::: ~ ::a 3: ... '" "E
., ." !- :J; OJ II: u ~ 'r;: ~ 'r;: ~ 'r;: 7:i ~ -a 3: 3: ~ 3: ~
... ~ f' c ::: ;:: ~ ... c::: ;:: -a ;:: '" 3:
- ~ v - E e c:a ~ ::a m = ::l = = ~ 3: ~ -a ::a c::: 3: -a '"
... ~ v 0 "E :r:
rn 0 (; - '" 0 ~ 7:i ... ~ ~ ~ "E 't:: :r: Vl ... c::: 0 c::: ... q::
... = r. '" = ::l ~ .... ~ ~ '" ~ 0 :r: r/J '" '" 0
... '< U V '3 Il) ~ V1 'J ~ Oil ~ 3: '" ~ .. '" 0 ... :r: r/J 0 :r: r/J ::a
-= '" ~ C Jl ~ ;:: -; ~ :r: c./) '" ,~ ::a .... :r: r/J
I r/J c./) '" =! - oJ) W ~ ~ ~ "E ~ ~ Il) '" ::a ... '" ... .... C)
U :::f c.. '" .....' '" '" q:: - .... .... '" Q) v .... ... '" '" >-
~ ':oJ ~ C -a '" '" 3: '" 0 = '" '" >- >- OJ C) >- >- '" '" '-' C)
0:: n::: n::: .~ :i c Vi ~ -; -; :r: 0 e; :I:l OJ Il) >- >- C) C) ..c:
~ -, '" ::) q:: ~ - c;::: - c./) - fo- = >- >- -a ~ ..c: ..c: >- >- >- >- E
= !S r/J c./) v: r/J ~J OJ 0 0 0 -a -a 0 0 ~ c :3 "E "E t t ..c:
::a '-' r/J .... 0 ..c: ..c: OJ
0 0 C: 0 Ja c fo- f0- ol Il) fo- "0 - ~ ~ U '... ::l ::l 't:: q:: .B x ;;.
< ;:: '" OJ ::l -::l -a = = C) ..c: ..c: 0 0 C)
- iIll: -< <( < <( '0. u e.- o ::) I l:: I .- .- '-'
~ LU UJ 0 c.. "E ... u .c u .c v v .c :I:l .- u... - I./l c./) ~ ~ '"- u... '"- '"- r/J r/J r/J
C .... -: ::l '" 0 "" ~
S , ~ ~ ~ '" = V1 = ;; x =
U - ..c: ;:, 0 e.- .'fJ ,.., 'J1 'J1 ," :;
- - (/) - l.:..l w..; IW
-
-
...
o
r-
Qj
eL
~
p...
=
.2
-
~
E
""
.;;
=
-
C'
~
-
Qj
'i:
Q.
o
""
~
"0
=
~
]
-
=
Qj
"0
!;:
=
o
U
.:
Q.
:I:l
""
OJ;
""
Qj
-
=
-
I' ..0 C I' ..0 >Q 0 a- or, 0 0 0 0 0 -
rl N 0 """ C I' a- M 0 I' ;:::: 0 0 0 0 0 -
-0 t'- t -0 I' I' 00 C """. M O. - -0 00 00 00 """ 00 ....
OJ <U v:5 -i r...: r-:- -.0
..c ~ E ..c I' ("-#"'; ,. or, <U \D 0
'" 8 '" .n """ ..0 ..0 ,. ('l -0 N N N
C", M 'r. I' ?- M ::l 00
E CJl ...; U
::l <lJ
::l c...., t: eJj
~ eo:
<A A A fA cA C/. ~ fA fA fA fA r.A fA r.A r.A =-.
~ a- or. 0 0 0 0 0
~ I' 0 0 0 0 0
I' 00 00 ~ """ 00
lr, -.0 \D
('I N N N
<A fA fA r.A fA fA r.A r.A
i
--I -1- - - - - - - - -
i
c- I- 0 V) V :? VJ VJ VJ U
7- "/ Z z :? :./'; 2 0 0 0 2 2 2 0
<:: :? 0 .-. ,-. <( <( <( 0 <(
..-r < <( < V 0::: :? ..... :-' U U U 0:: 0:: 0:: 2 u
;;;: ::>. ::l.. -, 0.. 0.. 0..
...- /.
Qi
..
0:1
CJl C
Qi
.... ,~
'i: ..:.<:
Q. OJ -
OJ eo:
... ::: e
....
:: ~ I-
"'0 ~ oS
0
.. C
Q. 0.. OJ
.-. 0 u -
... 'T:i <@
... OJ "
.. Qi
... ;> OJ
0:1 ... OJ C eo:
Q. Qi -0 ~ <U ~ -
G:i <lJ
"'0 -0 ::l ::l ::l VJ 'j:;
.. '" C -0 -0 -0
:c Qi oj 0 0 0 2 Q.
f- .. ~ 2 2 2 OJ 0:: 0
0:1 C :; I-
oci '" OJ <U OJ -0 '" =-.
E u u u C
Qi ~ ~ ~ ~ 0
= Qi ~ 2 ::l "e
,-= c;j ..... ..... ..... 0 c
E OJ <U OJ .....
;; ~ C E .~ c U eo:
;;: 0 .:':! '" -
'" = 0.. OJ
Qi .S VJ VJ VJ U u ,::
0 0 0 OJ
Qi ... ~ ::l -
.. Q. <( <( <( <( z C
0:1 0 u.J u..: u.J 0 <lJ
'" = ;;:; .....l .....l 0.. 8 "e
Qi Qi .~ r..=
... t ..... t E-
';:: -= 0.. <U 0 C
~ 0.. ..c ..<: ..c 0 <( 0
.. 6 6 6 2
Qi Qi < U U
'" ...
= 0 .c
::
.S ~ Q.
= "'0 ..... eo:
... Qi . OJ I-
= .. (', c eJj
/. /. Qi l;:: OJ I-
~' /. E 0:1 2 VJ <lJ
e ~ c Qi <( r". -
..... Qi C
:;; ~ C. 0::: 0
'- "'0 0 -
oj .5 .;::
~ ~ ~ oj IJ:J ('I
::::: 0 c; ::::: OJ
-0 "'0 .. OJ <U U
OJ -0 -0 -0 = Q. (', vi u u ~
;2 ':J <U r". ~ ~
-0 ~ OJ 0:1 = '2 .....
g -0 .:J'i ..... '- <U
OJ ~ C "'0 0:1 ..... oj OJ <U C
" ~ Qi .... I- 0 u E E
" " "'0 VJ <lJ '"
- ~ , '" OJ '" E
.. '- - Ll :: Cl. ] OJ U U E E
I.l '- c::: u <@ t:: ~
4:: ,3 OJ OJ .... .S <lJ 0 0 ::l ~ ~ CJl
0:1 "" c: ,- OJ <Ii 'J'1 C: ~ 0.. -0 '" CJl '"
+- c: 0
I.l oj '0 ... 0.. '" '" CJl
"J oj 0 - ::l C: VJ '"
0 'J '-' OJ 0:1 '" C '" 0..
- ii '-' 'J OJ = "'0 i5.. <lJ 0 ..:.<: <U 0 '" 0
;j u OJ '- t::
fi a Qi eo f- .... ..... ..... ..c
a .. a-. 8 x 0 ~ ~ oj ..c oj '"
g 0:1 ::: ::: '" c- t:
... 2 ~ ~ ... ~ ~ <lJ '" >< ~ :::
c:: ~ ~ '" ~ :r: OJ ,. 2 ~ ::l -0 '"
'lij Qi = -0 ,eo: Z ('I E 0 2 ..... oj OJ
2 - ('C oj '" ... 0 1) - v ;.< VJ rr: c..
/. (l:l .... .~ -0 I. (;j I' 0 E E E c..
~ ...- L. 2 :F: .. .. ::l <lJ 0 c...., OJ 0
'" ~ - ::l ~ U 0 0 0 c..;
OJ OJ E ~ Qi M ~
~ ~ E ~ '" u C .,;.. 0 (l:l ('I ..;: ..;: ..;:
~ ~ ~ ~ ~ ... ;g - OJ M ..... (;j
::: ::: (l:l ~ c. -- vi '" OJ t:: t:: t:: c
~ '" = C ('I
0 c: '2 ::: ... '" ~ E Qi 0:1 ~ '" or, ..:.<: or, if] c 0 0 oS 0
VJ 0 ~ VJ ... ... E ;.- c oc '" 0:: c- o. 0.0 .....
(l:l :F: ~ 0 ,~ C E E E '"";'
;; if: :r: 0 E .6 ..6 Qi \D 0 u VJ -0
VJ ~ '" J; '-' ell /J - OJ 0 c := - -0
I.l .~ :;; ..... .... :: ::l >. E .. 0:1 v eo: OfJ - ..... '" VJ VJ VJ <(
>- 'J ('j ('j '" VJ :F: u
'1) :F: ~ ::: .S:: -0 0 '" -0 2 2 2
.- ;..- OJ OJ .... ..6 ~ 0:1 ?> 't: -0 <( <U <(
-e ;.- ;.- :F: VJ :F: C u.J <fl 0:: 0:: 0
.6 ~ ... E v <( 0::: 0
c: ... ::l '" = OJ OJ t:: oj 0..
-5 ""- if] 5 0 VJ ::: 0::: ..c VJ VJ {/] <(
t ~ ..<: :: IX ... '" e '" 0 ~
::iJ ~Jj C - .., ~ "" .... ~ (;j 0 e- o.. u 0 0 0 c.::
1) E Qi IJ:J ..... :.0
~ ~ .~ t e 0.. ::l <( <( <(
Ul L Z 7- Q .~ .... :.Q ~ 0:1 '-' c.J 00 0.. 0 0)
0 .. OJ u.J u.J u.J C
#f' '0 '0 0 '0 .. .. v 0 OJ \D E u = ~ ~ s ~
::. Cl. ~ U """
'...I c.. c.. "" '-' VJ c; 0 l.:..l 0.. <( ~.
00
~
-
.-
..Q
Q
~
-
00
~
-
00
.....
~
~
<
u
~
-
~
~
~
<:.I
.-
-
Q
~
~
~
000
00
o If'J rt
0("1
r1
I
i
i
<A "A CA
5o=i
elf', r-;
C 01
r1
<A CA V>
C/J J; :J;
~~:;;
0:::'::0::
0.. :L "
;a
'J
J;
'-'
"
<1J ~ 8
.g.g ~
o c :0
:2 2 ~
C/J J; iJ
2:2:"
O::::Z::~
ilJ ilJ
UUC/)
00:;
0..:L0::
~
...
CIS
~
o
~
~
...
CIS
~
"C
...
CIS
=
,.V]
:~
-.
.r,T)
;)~ ,~
'_ v
:ch
00
;::~
Q. ,
os
~
;a
'J
Po
'-'
X
OJ) ;J
.:: ~
E ~ en
Q) 0..-5
'0, ~ .~
Vi,,>
</) ilJ 0
r.r, Vl 0
1j~00
2 E ~
0.. ilJ
-o:L
u ~
t: 'J
c}~
o 1)
Z2 E
::::- E
55g55c;c;
o,~o,~o,oo 0,
o 0 r---- 1~ ..q- ........., r I
lr', If', .-r-, 7
8c555g555
c, C; ~ 0,0,00,00,
DC ("'-I rl If) r--: r- r--: r----
rr- 'r rl r-l r-I r-l
V1 fA .A i./': V7 t/} V1
V! ,f: r.A EFt V't E;A fA tA- f.A
505 555 gg58g55
~~='~=,c:.:)OC) :::::c:.~c~~c,,~
00 ,.--.... r ~ r I oc !r r-l rl l./'"'. r--- r- r- r-
if, \r;"-, ""1" /,~'-, r-- '-' ('I rl II rl
I
CA CA -A 'JC <A V> if> V> -r V> <A <A <A CA <A fh
::J ~
..-r:<</c;2
'-' ...)'-'0..::"
~
~
,
~
I.
f-
c:<s
=
.=
-
~
-
=
~
e '-'
~ 'J
Q. '.e
e ~
t).[)
.S
"0
=
e;
=
'-'
'J
~
'-
~
~
~ ~
'/1 ~
.> , ..0
VJ ~
__~ :il
::::::
:;.[)
t:
..:G
:)
::;, :::?;
:.r C: C:
~ /' <'
'-'
v: :r.
o ,....,
< <
'-'
~
'-
'-'
J ~
~
'-'
'J
:o:l
'J
3 ~ ,2
C '{j 3
;>
'-
;
~
'f. r
......
./; t:
~ ~ /
'J ~ Q
g <
~ co
Cj
=
"0
o --
I.
Q.
~
~\)~~"
~ .~ .2 .0 ,~
-
=
-
::;-
-: ~
ilJ 5
-5 0
::: '-...)
... ... '-
. '-' ..3 ...;:::
t:
~ '-'
:::- ~ 2
w..: ~
v; .~
..".
~ ~ :P
v: :;
o fl I:- ~
~~~'~::
o 0 :r. 0
<"<..-r::;<<
c.,g:v~
~
::J
..."
:J
/.
'J
J
1
~'j
oj)
~
"3
a.
;:
x
J
"
~
"
Z
-0
;
;::
....
'-
~ ~
,ro
... 1:
~ ~-
:o:l
ilJ
0::
\)
"E- -g
-" :;; ~
c
OJ
~
;n ...
~ :e
;:: :0
"
'J
ro
'-'
'J
~
~ ~)
~
~ ct
~
~ c
......, 0
v (/) ';j
"5 ~) Vi
'-'
00
<<(
00
~
::J
-0
:;
u 2:
g v rJ
~ ~ ::I
... -0 -0
:l) 0 0
c:;:;
:lJ) ilJ ~
.5 cE c$
t:: '- _
~ ~ ;
";j) ~
:o:l ,-
E 1:-'-
...
~
o ,..:;G .~
cL.V:~
-.
ro
:$
ilJ
0:;
::.J
Cj
I.
~
~
o
'J1
'"
...
~
-
=
Q.
e
Oc
U ("1
eo: or.
-
~r--
Q ~
~N
:E~
o e
~0
or,
o
...-,
or,
<A
0'
trj
or.
<A
or,
0'
,
V
o
?
r=:
~)
:$
~
o
I. </)
~ '--,<
, ~ '"
~ ;;; 0
'J1 C/J CO
= ~ 0
.= 0 ~
_ "0
~ c:: X
.::! :3: ("J
Q..
c..
~
c..
=
..::.::
Cj
~
=
Q
~
U
t:
:) '-
ilJ ~
X 00;:;
C!;:!;
rl) ><':
o;r--
:::s ~
o ro
'-'
ilJ ;>,
(jJ If'l
'i:
c...vl
;;; V
~Z
c'" ~
50
<"'1
o~
V)<(
000::
~n CO
-O'c
IJ.lOO
~ v: ~
:$ (;
~ ~ ~ B
() 0.. ~
o2g.~
o c.. '"
\0
<A
'D
<A
o
<(
'-'
-0
ilJ
-0
::l
()
t:
o
<(
u
ilJ
~
:$
<t:
o
C/J
V
C
ilJ
C/J
ilJ
</)
:o:l
~
ro
0:;
o
o
<(
~
...
~
C
~
'J1
~
'"
~
.Q
~
-
~
Q
Q.
=
..:.:
Cj
~
~
Q
~
U
00
V)
.,0
M
<A
00
V)
.,0
...-,
<A
o
<(
u
o 0:;
<( :r:
0::-0
ilJ
CO cL.
o
\0 0-
"T~
o ~
~
ilJ
L 0..
<( ro
cL.f-
CO C-;1
00
("1 f-
f"'J -l
i3 ~
ilJ 0
X
t::
o
0..
0..
::l
'"
l:
"T
><
"T
("1
><
r--
:fl
~ "E If'j
c'" ro
.,t, V g
O..:G_
o '-
00 0
\0 :$
() V
.gpZ
~~
ilJ -'
:$ 0
o ~
0..-,<
</)
00
-0
u.l
><
::l
,:::
-l
ilJ
</)
e.
ilJ
c
IJ.l
-
-
....
o
0\
~
011
~
Q.
=
.=
-
~
e
I.
~
=
-
c
~
-
~
'i:
c..
o
I.
Q.
"t:l
C
~
-;
:;::
=
~
't:l
l.;:
=
o
U
.c
c..
~
I.
t).[)
I.
~
-
=
-
rJ'J.
~
==
.c
~
~
rJ'J.
~
rJ1
-
<
-....
~
<
u
~
""
~
~
~
~
.-
-
~
~
~
~
Vl
OJ
Vl
C
OJ
.~
......
~
U
OJ
a.
rj)
a.
a.
~
c
.=>
"'0
W
""2
o:l
"'0
C
o:l
C;;
OJ
Vl
o:l
..0
o:l
<;; ~
o 70
OJ Vl
g ~
~ 0 C
0 8
c;
rl ...;-
.....
fA Vl fA
0 g
- 0
.r c;
- ...;-
V> Vl CF',
...;-
~ if) 'J:
~ ..". :?'
.- L
0::: 0:::
0.. :L
r
'J)
'J
'J
'J
~
':J
P-
o:l
L
:@
o
C:
..,-
~
~
0)
a.
~
.,.
E ~
..... rl
, l"l
OJ)f-
CVJ
:;=3
.: OJ);:::
eo. C f-
.S c v:
'(;i :L
~
OJ
""
~
.:
.,. E
s.. ~ 2
~~,~
OJ)~~
= L-. ~
__ 0 t:
= a. ,-
"; ~ e
-
~
~
OJ
Vl
o:l
CO
,
c
Q..g~,
e ':J OJ
... !: 2
:L
e~
OJ):;~
:; .~ C
_zv:
~;;;C:
.... 0::: <1:
e ~ LL.:
c..z
\C 'Ct
C
('" I (')
r1 rl
f-'-
v: if.
0.. 0..
E
v
>.
J:
-
=
.9
-
Q.
o
\C ~ ,,0 0 \C 0 \C 0
0 0 0 r; 0 N 0
l"l r-~ c; - o. - o.
. .
rl l"l - l"l - l";
rl ..... rl ...;- r'l ...;- N "T
- - - -
fA V> Vl CA tA CA "'" "'"
'E. \C 0 \C 0
~ ~ r'l 0 N 0
N lr-, rl 'r, - '0 -. or;
- - - 0 - 0
rl -- rl - (",1 - N -
- - - -
V; Vl iA V; fA "'" Vl "'"
- - - 'Ct - "T - "T
0 C: ~ ~ VJ VJ VJ rj)
- - :2 ..". ::;;: ::;;:
<: ~ < <1: 2-
V ~ ~ '-' 0::: 0::: " 0:::
r 0.. 0.. 0..
'" '"
'" '"
... ...
'-i '-i
v '" '-i '-i
p. '" < <
... ...
'-i '-i ... ...
'-i '-i '" '"
.... .... 0: 0:
... ... .Q .Q
p. '" ,;s 0:
-. 0: 0: ~
.c .Q Q Q
0:
- ;; rj) rj)
0:
0 Q ::; ::;
0 Q "":l :::
~ < (jj rj)
~ ~ ::; ::;
cz::: cz:::
- L ~
/- <: <1:
.-
~ - 0::: 1:: ... 0::: 1:: ...
'- t ~ 1) 1)
.. ::c c::J :; 0. CO :; -= -
- 0. - 0 0.
- - - - ~ 0. - a. =
/ --' / = Vl = if) .9
/, ':J 'x 1.) .9 ex:; ::l OJ .9 00 ::l OJ
f. /. Vl if) Vl if) -
- -:J - ~ C - :J .c C Q.
1.) = 0:: .c OJ OJ
- 'J .9 - 'J Q. "T u Q. 0.. "T ,~ 0
- .- 0 v 0 v
" ~ x ...l x ...l
- - -. 'Ct "T ""
. 'J Q. -r J "" -r rJ U "" "T N u =
- ,-, = .:j x ,- = v x t;:; -
,:; .....
, - '-" J - :/':. r-- U - if) r-- '(3 ~
- 'J - ~ ~ -
':J "" 1J ~ if) v .~ if) OJ
- ~ c. = r ~ C. - 2- ~ 0. - ~ 0. -
- f - ~ Of - rj) - ~ rj) rJ1
~ 0. ~ ~ c. rJ1 1J 1J rJ1 v OJ --
;;-. C >-.
- a. - - r - -- 0.. -
- c. - 'r. a. :D or;
c. - c: - ~ a. N a. ~
~ ':.1'1 --- 'J'J. / f. / / <1: x ~ C
= ~ -- ::l ~ - =- <( - ::l <(
-'= - CO CO
., 'Ct - N ::: 'Ct ~ ::: ::: ~ C ~
x :; :u:: - x .,. .- ::: :; .,. :r: :~ rJ1
- .- ...l
'Ct ~ - 'Ct - - - -
- - ,- U ,- U ~
~ rl ~ ~ C':l rl "'0 ~ .~ "'0 ~ OE '@) "'0 ""
x - .,. - / - rJ1 - OJ) :D rJ1 :r: w ~
r-- - r-- - :; .2
;f1 - "'0 C "2 ~ "'0 0 ""2 ~ -0 0 -0 .Q
j ~ ~ 'J "" 'lJ "" OJ ... ~
... C':l o:l o:l
" C':l 'J'J. 0::: C':l ~ ~ 0::: t=3 -0 ~ 0::: t=3 -0 -
,,'- 1J U .Q c .Q C ~
h ~ ,r, ::l C ::l
--=- "" ~ 0 o:l ~ C 0 o:l ~
lr, 7- ~ lrj :.; - \C ,J) - \C C;;
Vl ..Q -c f. ~ -c vi ~ \C vi' -
.. ~ 'lJ Q ~ 'lJ Q ... 'lJ ""
-'" ~ ~ -'" (f) -'" if) ..:G if) ~
., Vl - 1.) Vl C':l 1) Vl o:l 'lJ Vl o:l ~
, -g c: .- L rJ1 > ..0 rJ1 ;;- 0 ..0
- 0 ~ C: V 0 ...
~ Q 1.) (':j ~ o:l ~ 'lJ o:l OJ)
CO - J: X e;; - Of ::c <;; rr. co <;;
- ~ .- ,- 0 0 ~ q;: 0 0 .S
.. 0 - Q 0 C: ~ 0 0
VJ 'f. -- Vl if) =
\C U './1 ~ f. -c 2! p. rJJ ./1 >D 2! p. rJJ if) \C 2! Vl
"T - :.J =- ...;- Q) "T 'lJ 3 "T 'lJ .;
- 'J 2 - 'J u ~ 2 - u u ~ - u u
~ U ~ C':l o:l ~ o:l
X ~ X ~ x ,8 0 >< ... 0 -
-- :.; ~ Q:: 7: c.. Q:: C;; 0 c.. E-o
r >C - C. - -c rI N
'"
=
-
~
-
-
'J'J.
-
-
:u::
-
~
t
~
z
~
'"
~
.Q
~
-
~
Q
Q
~
W
--
-
:....
J
-
-
.....
o
Q
~
0Jj
~
c..
=
.9
-
~
e
-
~
=
-
c
~
-
~
"i:
Q.
o
-
c..
"0
=
~
';
"';:
=
~
"0
'-=
=
o
U
-=
Q.
~
-
0Jj
-
QJ
....
=
-
0 0 c CO -
0 0 c r-- -
0 o. c or, .....
"l ...; r l N 0
") -r -
~ -
-
~
OJ)
\A \A v; \A iF fFj ~
Q..
-0 0 a 0 c
("1 0 0 0 C
or. a ~ c
a -r r l
"-'1
Vt v; v; iF
...,.
Cl 0 Cl C
< < -1" <"
'--' ,~ G ~
=
.~
....
~
S
l.
~
=
-
C
~
...
~
oC
Q.
0
l.
Q..
"0
=
or. ~
or.
~
'" 0::
'"
~ ...
~ r~. -r or =
or. C C C ~
Oil 0 0 "0
..c ,l ("1 f'J "=
~ VJ f- ,..... =
Oil if) if. 0
Q 0... 0... ~ U
.c
Q.
~
2 l.
OJ)
<( - l.
Cl:: ~ = ~
CCl (:; .~ -
0.. =
0 0.. ... -
0.. f> Q.
00 ::l OJ
f> f> 0
;:; .... u -
...c -
0... -r 'J =
U :.< --' ~
~ -r S
rl ',.>
iii ;.< -
'" t- 'J l.
.... CfJ ~ ~
"- ~ 0- Q.
.... :/)
Q) :.> ~ ::!
E ^ Q M (:) or,
0.. 0 c
LJ.J .r. n C
0.. ~ 0
~ <( ..-( .:= n f- n
::l f- ~ f-
c:: CCl :; '0 Vl cr
...J Q.. 0... 0...
t;; c.> fJ
;,j) -0 ~ J1 ~ 'J.
:I: 0 LJ.J ";:j ~
-0 6- "2 .;; E Q) E
II)
Cl:: ~ "-l II) '" V
:; -0 OJ) ./J C/l
0 = f> -,' C/l
::l (;i C/l
0 Cl ~ LJ.J ::l) I.l,;
'l:> c7l ::l) c:: ....
'l:> Ji 0 "-l
... .;.: v l. ~:g C/l =
VJ
II) '" ~ .s c 0
~ Cl ..c ~ ~ 0'::
~ 0.. v
II) t;; OJ) = V1 0.. Q.
Vl CCl = .~ if: 0
<t:: 0 0 (3 ._ v Cl
'" :..n =
'l:> v C/l Cl Cl C
::: ~ v .; ~
t;; <J c.> <( < <r: -
.... X ~ 0 l. ;.; c..- O
c7l 0 c.. Eo-< '-' Eo-<
C'1
EXHIBIT B -INTERGRAPH SOFTWARE LICENSE AGREEMENT
I ntergraph ( orporat Ion
f)ro Forl1la \~reL'I1ll'nt
Software License Agreement
1 hf Security, (,ovanment and Infrastructure division of Intergraph Corporation, hereinafter referred to as "INTERGRAPH"
a~ree~ to grant hereby and ______ hereinafter referred to as "CUSTOMER," agrees to accept a
n;lntransferabk and nonexclusive license under applicable copyrights and/or trade secrets to use each Software Package
pro\ "led bv I~ n RGRAPH ;11 it- authorized dealel 111 decrypted form under the following terms and conditions:
I erm of License
I he Softvvare Package(s) shall be licensed lmder this Agreement etTective from the date of delivery in decrypted form. This
Ag,reement shall remain in force until CUSTOMER dIscontinues the use of such Software Package(s) and returns the Software
Paei--age(s) to INl f:RC,RAPII or this \greement is llthcrwise terminated as provided herein.
2. LIcense Coverage
'. t STOM LR shall have the light to use each Snftware Package m any portion thereof on the specific Local Area Network
(! ,~\; I for which It is lIcensed. either locked on a singk computer node (as determined by a specific LAN address), or
con, urrently on a number of compute nodes so long as the number of concurrent uses does not exceed the number licensed for
the 1\ '\J, or on one or more backup umputer nodes. '\Jo other use is licensed CUSTOMER shall permit INTERGRAPH
reas,mable access in the IAN tor licC'1se administratIon audit purpose'
3. "'ccurity
( ('rtain Softv\are Package., ale rquired to ;lperak In conjunction with a hardware lock device or in conjunction with
Iicells<.' administration software and a license authOrIzatIOn key provided by INTERGRAPH or its representative. CUSTOMER
sha! take no steps to avoiJ or defeat Ihe purpose of an~ required lock device or authorization key_ Use of any Software Package
V\ Ithout a reqUIred lock devin' or authorization ~ey ,hall he unlicensed under this Agreement.
( l STOMLR agrees that he dnd IllS emplo~ees vvill not make available the software, or portions thereof, or documentation
related thereto to ,lilY persons other than CUSTOMER or INTERGRAPH employees or other persons authorized to use the
l .\\' for which the ,oftware is licensnJ without pri(lr \Hltten approval of INTERGRAPH. CUSTOMER will not copy the
sulhvare or documentation e'\cepl as i]ecessar~ for use under this Agreement. CUSTOMER will not decrypt without
authorization, reverse compile or Jis<lssemble the spfh\are. ClSTOMER will not export or re-export the software or
dpclllllentation wllhout the appropriall' United "tates and foreign government licenses Furthermore. CUSTOMER agrees to
abide all applicable Federal and SLlte Trademark and Copyright lavh
4. Title
! Itle and (lWnerShlp pftht sottvvdle shall at all limes remain with INTERGRAPH or relevant third parties.
5. Warranties
<\" warranties are stated in the INTERGRAPH Contract Agreement to which this license is an Exhibit thereto.
6. lermination
in the event the Cl is TOM ER ne~lects or t:lils (i) to pay the appropriate license fee(s), or (ii) to adhere to any of its
ohilgatlons hereunder. this License A:2,reement ,halltrnlllediately terminate. and all software licensed hereunder and all
encrypted softwan' will be- returned tl INTFRGRAPH \vithin ten (10) days.
in the evelll 01' any proceeding. v ,duntar~ ur im olllntary. in bankruptc~ or insolvency by or against CUSTOMER, or in the
event of the appollltment. with or withuut the CI 'Sl OM ER's consent. or an assignee tor the benefit of creditors. or of a
ren'l\ er. INTf- RC, RAPH ma\ elect t\ cance! am unfiIlti lied part of thts Agreement
In tile event of <1m proceeding. volutllary or involuntar~ in bankrllptc~ or insolvency by or against INTERGRAPH. or in the
even! of the appointment with or without the INTERG RAPH' s consent. or an assignee for the benefit of creditors, or of a
recel\er. CUSTO\1ER ma~ elecl to c-mcel an~ unfulfilled part of this .\greement.
RESERVI!)
Corpus Christi, Texas
Exhibit B: Software License Agreement
Page 1 of 2
8. c\greement Limitation
It IS understood and agreed tllat this License Agreement. the applicable part of any agreement form that may
accompan: a Software Package, and IPS Contract Agreement to which this licenses is an Exhibit thereto, together
contam the entire and only understanding betv.een the parties relating to subject matter hereof and that any
representation. proml'ie llr c,mdition not contained therein 'ihallnot be binding on either party.
The pro\ ISlons oi'rhl' A.>.!.reernent shall contrOl and have precedence over the terms of any purchase order from
Cl JSTOMER with respect t( the licensed programs. Receipt h: CUSTOMER of the licensed program, updated
program or optional materia Is. such as source tapes. decrypting information or listings from INTERGRAPH, shall be
deemed l onclusive l'\ idc'nce \If Cl STt)\1 ER' 'i agreement that the license for such licensed program or optional
matenal" is governed b\ this .\greement
If an: of the pro\ isions (,I' till' Agreement are II1valid under any applicable statute or rule of law, such provisions are, to
that e\tent. deemed omItted. ,lIld thts Agreement shall remam otherwise in effect.
This '\gll~ement ,hall be i2.O\l'fned by the lav.s ufthe State 01 Iexas
Corpus Christi, Texas
Exhibit B: Software License Agreement
Page 2 of 2
EXHIBIT C - SYSTEM CONFIGURATION
Intergraph Curporation
Pro Fomla :\c>reement
EXHIBIT D- STORAGE AREA NETWORK CONFIGURATION
intergraph ( ()rporatlon
Pro Fom;,i ,\~reelllelll
EXHIBIT E - STATEMENT OF WORK
lntergraph C,>rporatiol1
f>rn Form" A"reemcnt
INTERG
INTERGRAPH PUBLIC SAFETY
Statement OF WORK
FOR THE CITY OF CORPUS CHRISTI
~////\
( \
II~
--
- -
- -
~
(~itv ()f
(~() 1-') II S
(~h rist i
Public Safety Information System
Computer Aided Dispatch, Mobile Computing, Police Records
Management, Jail Management System, and Automated Field
Reporting
20 March, 2006
Version I A
INTERGRAPH
CHANGE HISTORY
2/28/06
"' 'Ofl::O()()
Original
Added text to Task # 6 for TLETS securit re uirements
(Jeneral updates for Final System Acceptance Criteria
(Task It 4)), and edited the PM assignment for Intergraph
and the Executive S onsors
Edits made to Task Ii 7 at City's request for mutual
agreement on hardware ordering: added contact info for
Deane Dayton: removed "Draft" watermark; added text to
state Mark Matter as Primary Pro'ect Mana er;
Added text to task # 9. page 14, stating that Intergraph will
install 5 G PS sets of hardware,
-,,- +
.. 3,' Im'16..t-'OIll Iline~--- .-
i
. !
+
I
.---t.- -'.-..--
: 2() 2(J()() Tom Hines
II
STATEMENT OF WORK ACCEPTANCE
The Intergraph prepared Statement of Work for the City of Corpus Christl has been reviewed and
approved
APPROVED:
Date
Debby Studer
Project Manager
City of Corpus Christi
APPROVED:
Date
Mark Matter
Program Manager - Primary Intergraph project contact
Intergraph
APPROVED:
Date
Clint Griggs
Project Manager - Secondary Intergraph project contact
Intergraph
City of Corpus Christi - Project Statement of Work
Table of Contents
General Project Information ...... ........ .......... ...... .... ............
General Project Management Responsibilities .... ....... .........
Escalation Procedures. .............
Task 1
Task 2
Task 3
Task 4
Task 5
Task 6
Task 7
Task 8
Task 9
Task 10:
Task 11:
Task 12:
Task 13:
Task 14:
Task 15:
to CAD ..
Task 16:
Task 17'
Task 18:
Task 19:
Task 20:
Task 21:
Task 22:
Task 23:
Task 24:
Task 25:
Task 26:
Task 27:
Task 28:
Task 29:
Task 30:
Task 31:
Task 32:
Task 33:
Task 34:
Task 35:
Task 36:
Task 37:
........... ..... ...... ...... ....... ..... ..... 1
.... ........... ............ ..... ............. 1
.... ........... ...... ........................ 2
Project Kickoff ...... . ............. . ........ ........ ............................................. 3
Project Schedule Review and Update... ........ ......... ............................................. 4
Project Documentation Deliverables ..... .............................................4
Review of CAD Configuration Requirements............ .............................................5
Map Development and Refinement....... ...............................................................7
Interface Control Documents (lCD's) for I/CAD and I/LEADS-RMS ................... 9
Hardware and Software Installation and Deliverables......................................... 11
CAD Interfaces ....... . ........................... ...........................................13
Mobile Data System Product Installation................... ........................................... 13
Mobile Data System Customization to MDS Requirements............................. 14
Mobile Data System - Train the Trainer Training.. ........................................... 15
Mobile Data System Acceptance Testing ... ........................................... 16
Final CAD Equipment Installation. ........... ........ ........................................... 17
CAD System Train the User Training ................ ........................................... 17
CAD Integration Testing of MDS and Acceptance Testing of Other Interfaces
........................................... 19
CAD I Mobile Acceptance Testing ............................................... 20
CAD I Mobile Cutover Final Preparations .... ........................................... 21
CAD I Mobile System Production Cutover.. ........................................... 22
CAD I Mobile Performance and Reliability Testing............................................ 23
I/LEADS-RMS Software Installation.... ........................................... ............. ..... 25
Build I/LEADS-RMS Data Information Required for Production...................... 26
I/LEADS-RMS Data Conversion ......... ............................................................. 27
Install and Perform Accepting Testing of I/LEADS-RMS Interfaces............... 27
I/LEADS-RMS System - Train the Trainer Training........................................... 29
I/LEADS-RMS Acceptance Testing..... ........ ..... .... ........................................... 30
I/LEADS-RMS Cutover Final Preparations.. ......... ........................................... 31
I/LEADS-RMS Cutover to Production. ................. ........................................... 31
I/LEADS-RMS Performance and Reliability Testing.......................................... 32
I/LEADS-AFR Implementation ............. ................... ........................................... 34
I/LEADS-AFR System - Train the Trainer Training............................................ 35
I/LEADS-AFR Acceptance Testing..... ... ...................................................36
I/LEADS-AFR Cutover..... . . ................ ..............................................................37
I/LEADS-AFR Performance and Reliability Testing........................................... 37
I/LEADS-JMS Software Installation ..... ......... .......... ...........................................39
I/LEADS-JMS Acceptance Testing.... . ................... ........................................... 40
I/LEADS-JMS System - Train the Trainer Training........................................... 41
I/LEADS-JMS Cutover Final Preparations... ....................................................42
City of Corpus Christi - Project Statement of Work
Task 38: I/LEADS-JMS Cutover to Production .................... ...........................................43
Task 39: I/LEADS-JMS Performance and Reliability Testing........................................... 44
Task 40: I/CAD Reassessment... . ..... ......... ........ ........................................... 45
Task 41: I/Mobile Reassessment.... .......... .... ............ ...........................................46
Task 42: I/LEADS Reassessment.. . . ............ ............ ...........................................47
Task 43: Final System Acceptance Testing. ... ........ ...........................................48
Task 44: Project Closure ........ ........ ... ........................................... 49
Attachment A-1 - System Reliability Test Criteria...... ........................................... 50
Attachment A-2 - Training Plan ..... . .......... .... ........................................... 50
Attachment A-3 - Interface Control Documents.......................................... 50
Attachment A-4 - System Performance Test Criteria .... ........................................... 50
City of Corpus Christi - Project Statement of Work
ii
STATEMENT OF WORK
General Project Information
The following Statement of Work (SOW) defines the principal activities and responsibilities of Intergraph
Corporation (Intergraph) and the City of Corpus Christi (City) resources for the implementation of an
Integrated Computer Aided Dispatch (CAD) System, Mobile Computing System (1/Mobile), Police Records
Management (RMS) System Jail Management Subsystem (JMS), and Automated Field Reporting (AFR)
System to support the City's !aw enforcement and record-keeping operations
The 'system (used to refer to the subsystems, interfaces, and ancillary systems) to be provided to the
City IS composed of the follOWing primary software components
~ Computer Aided Dispatch Subsystem (I/CAD)
~ Mobile Computing System (1/Moblle) - for all Mobile communications
~ Records Management Subsystem (I/LEADS RMS and AFR) - for police records keeping
~ Jail Management Subsystem i1/LEADS JMS)
General Project Management Responsibilities
Project management occurs throughout the prOject and is Involved in every task Please note that both the
City and Intergraph Will provide Executive Sponsors for the system implementation. These sponsors will
communicate on an as-needed basis and Will act as escalation paths for their team members, if needed
They will not be involved In the day-to-day project details
The overall project management actiVities are listed here for reference
Intergraph Responsibilities
~ Maintain project communications With the City's Project Manager
~ Manage the efforts of the Intergraph staff and coordinate Intergraph activities with the City's
Project Manager
~ Manage the efforts of the subcontractors being utilized by Intergraph in the performance of the
project
~ Conduct on site status meetings With the City's Project Manager on a monthly basis, or when
reasonably required at the discretion of City to discuss project status.
~ Conduct project review meetings via telephone conference calls with the City's Project Manager
on a weekly baSIS
~ PrOVide responses to Issues raised by the City'S Project Manager within ten (10) business days.
~ Prepare and submit a monthly status report by the 10th business day of each month that includes:
the accomplishments of the previous month, activities planned for the current month and an
update to the project schedule In MS Project 2003 format
~ Prepare and submit project Change Orders to the City's Project Manager as necessary.
~ Ensure that Intergraph personnel have ample time, resources. and expertise to carry out their
respective tasks and responsibilities
City Responsibilities
~ Maintain project communications With the Intergraph Project Manager.
~ Manage the efforts of City staff and coordinate City activities with the Intergraph Project Manager.
~ Ensure that City personnel have ample time. resources, and expertise to carry out their respective
City of Corpus Christi - Project Statement of Work
Page 1
tasks and responsibilities
~ Participate In the status meeting with the Intergraph Project Manager on a monthly basis or as
may otherwise be reasonably required to discuss project status
~ Participate in the project review meetings via telephone conference calls with the Intergraph
Project Manager on a weekly basIs
~ Provide responses to issues raised by the Intergraph Project Manager within ten (10) business
days
~ Liaison with all City-provided third-party vendors and associated systems.
~ Ensure that acceptable Change Orders are approved by authorized signature(s)
~ Ensure timely payment of inVOices
~ Ensure Intergraph access to server and network equipment and work areas on a 24x7 basis, with
pre-authorization for off-hours
~ ProVide workspace for Intergraph personnel as reasonably requested.
The Executive Sponsor for the Intergraph team is:
Deane Dayton
Executive Manager Program Management Services
Security. Government & Infrastructure (SG&I) Division
Phone: 256- 730-8852 email deane dayton@intergraph com
The City Executive Sponsors are
. Ken Bung. Police Chief (Primary Sponsor)
· Commander Brian Uhler, Administrative Assistant (Secondary Sponsor)
Escalation Procedures
During the course of the Implementation of this project City will have access to various Intergraph
resources to assist them on any issues that may need attention. A single point of contact at Intergraph is
assigned and empowered to handle any situation before, during, and extending to after the deployment.
City will be provided with an "escalation' list, of pager numbers, cell phone numbers, office phone
numbers. and fax numbers, for the Project Manager, his/her Project Coordinator/Supervisor, up to and
ncluding a Vice President level Senior Executive, in addition to the Executive Sponsor noted above.
City of Corpus Christi - Project Statement of Work
Page 2
SOW Format
Each task Includes the following Task. Objective, Description, and Responsibilities. All parties recognize
that the SOW is not formatted chronologically, and the actual project implementation tasks and time lines
Will follow the mutually agreed to Project Schedule, unless otherwise noted
Task 1: Project Kickoff
Task Description:
The Project Kickoff is a meeting conducted on site by the Intergraph Project Manager, along with key
intergraph project team participants This will be conducted at the City's designated facility. During this
meeting there will be high-level discussions of the following
~ Contract Review
~ A review of lntergraph project team roles, assignments. and support levels
~ Identification of City project team reqUirements
~ Process review of how the system will be implemented
~ Change Order process
~ Communication to other personnel who will be Involved with utilizing the system
~ Facility access (during and after normal business hours)
~ Work space requirements for Intergraph personnel while on site
~ Facility tour to be conducted by the City Project Manager
~ Any known schedule constraints
~ DiSCUSSion of Interfaces and the Information needed from the City for special interface
development
~ Review of hardware being supplied by lntergraph. and the City (if any)
~ Review of software being supplied by lntergraph and the City (if any) plus a clarification of the
operating system Oracle Database version to be implemented, and a review of third-party
products specified in the contract pnclng.
i ntergraph shall
Provide Project Manager on-site
2 Work with City personnel In designing and approving of the format of an action item log to be used
In conjunction with the Project Schedule. The purpose of the log is to identify outstanding issues,
proVide continual status updates on specific tasks and to Identify responsibilities of the parties.
City shall
Provide Project Manager and any other resources that are recommended by the City and
lntergraph Project Managers
City of Corpus Christi - Project Statement of Work
Page 3
Completion Criteria:
This task is considered complete when the Project Kickoff Session has been held with Intergraph
'epresentatlves In attendance and an action Item log has been developed by both Intergraph and the City.
Task 2: Project Schedule Review and Update
Task Description:
After the completion of the Project Kick-off meeting, Intergraph will commence work on the Project
Schedule. Upon completion of the initial schedule, the Intergraph and City Project Managers will review
the schedule. and any mutually agreeable updates will be made by the Intergraph Project Manager. It is
anticipated that Intergraph will have a draft final schedule ready for review within five days of completing
'he project kick-off meeting.
The schedule will be updated as required dUring the course of the project implementation. All changes to
the schedule will be mutually agreed upon and, if required, will be documented via the mutually agreed
upon Change Order process Any schedule changes that occur will be a part of the weekly project status
'eport prOVided by the Intergraph Project Manager The Project Schedule will be created and maintained
with Microsoft Project 2003
Responsibilities:
ntergraph shall
ReView with City personnel the identified implementation tasks. priorities, inter-dependencies and
other requirements needed to establish the final Project Schedule
2 Prepare the final Project Schedule document and deliver It to the City.
3 ReView the Project Schedule with City personnel and make changes and/or corrections that are
mutually agreed upon
::::Ity shall
Analyze with Intergraph project personnel the identified requirements and make such
Implementation decisions as are reasonably required to finalize the Project Schedule.
2 ReView the final Project Schedule and Identify In writing any specific deficiencies found within ten
10! bUSiness days
Completion Criteria:
This task is conSidered complete upon mutual agreement of the finalized project schedule.
Task 3: Project Documentation Deliverables
Task Description:
Intergraph shall
City of Corpus Christi - Project Statement of Work
Page 4
Provide a Project Schedule---1dentifies all tasks to be completed during the life cycle of the
proJect, the responsible party for each task and the project milestones defined in the schedule.
A draft sample Project Schedule for the City document is provided as Exhibit F of the Contract
Agreement
2 Provide a Training Plan-all documents utilized In the training classes are left with the City SO they
can be used for new operators or for refresher training as needed
3 Provide an Acceptance Test Plan- mutually developed document between Intergraph and the
C:ity This document IS defined to a level that verifies the intent of system functionality is met.
4 Provide a Cutover Plafl----{:Jescribes the tasks that will be handled by Intergraph and City personnel
dunng the Initial time the system is cutover to "live operations"
5 Provide an Interface Control Document~escribes each Interface in the system.
6 ProVide CAD and Mobile System Documentatlon--provided on-line and includes system
administration procedures
7 Provide RMS. JMS and AFR Documentatlon~-provided on-line and includes system
administration procedures
Completion Criteria:
This task is considered complete upon submittal of the finalized and City accepted Plans and as-built
specification and interface control documents
Task 4: Review of CAD Configuration Requirements
Task Description:
The Intergraph Project Team will be on site to conduct a 4 day Project and Workflow Analysis Workshop
Course # ISPT1000) ThiS multl-facted VISit is Intended to aid the Intergraph team members in
understanding the City's eXisting tools and environment so that Intergraph can better recommend
configuration changes that Will assist in reducing the learning curve and encouraging end user product
acceptance ThiS viSit IS also designed to provide the City core team with an overview of the project plan
[what to expect) and With an understanding of the data that will be needed to set up the system. As with all
major system replacements there Will likely be significant paradigm shifts for users moving from the
current enVIronment to the new Intergraph environment This visit will assist the Intergraph team in
identifying potential challenges so that the Joint project teams can plan together on how to meet the
challenges effectively
The Intergraph Project Manager, CAD Implementation Lead. Mapping Lead, and Training Lead will attend
the Project and Workflow Analysis Workshop
The result of the workflow Information gathering Will be the production of a "Project Workflow Analysis
Report," which will be prepared by the Intergraph Project Manger with input from the Intergraph team
members The report will be presented to the City Project Manager for further discussion and planning.
Configuration refinements WI!I occur on the system and throughout the project as the City team becomes
more familiar with the software and fine tunes the system via configuration changes. Additional changes
are made in the follOWing Intervals
The I/CAD Implementation Lead Will attend the IICAD Workflow and Configuration Workshop
II PST1 004) held with the City's CAD core team (members of which are defined below). During this
City of Corpus Christi - Project Statement of Work
Page 5
training workshop, many configuration issues and questions will be raised as users begin to
understand the system more deeply The Implementation Lead will make configuration changes
throughout the training class, allowing the core team to quickly see the result of their requests and
to ensure that explanations and requests are well understood and executed (as well as the results
of those requests)
2 Shortly before "go live" and before the designated system change freeze, the implementer will
make final configuration adjustments per the Citys requests, during a Design Freeze visit. This
allows an opportUnity to incorporate requests that were revealed during system testing.
3 City staff can receive additional training on the configuration and make changes themselves
Responsibilities:
Intergraph shall
Be Involved In the follOWing actiVities
Intergraph team complete site tour of all areas affected by the new system.
2 CAD Implementation Lead Sitting with Calltakers, Dispatchers Supervisors, and all other City
designated personnel in the Communications Center to understand how the existing system is
used They will also ride along with Field Personnel for the same reason.
3 DISCUSSion of eXisting environment. Including Inputs and outputs, interfaces, and standardized
reports
4 Gathenng of map data information from City GIS
5 ReVieWing the network and secunty concerns including Domain setup, security policies, port
allocations, remote site considerations, Wireless Connectivity. All Intergraph staff that will access
the Citys system must fulfill the TLETS security requirements and meet the minimum standards
as reqUired by the State of Texas
6
7 DISCUSSion of VPN access and VPN connectivity for both CAD and RMS systems, During system
Implementation, unrestricted VPN access is expected for Intergraph developers and
Implementers This requirement allows for rapid development and testing of interfaces that
cannot be tested oy lntergraph In-house, resolVing system configuration issues, and for
troubleshooting purposes After system cutover, Intergraph Will VPN into the live system only at
the specific request by the CltV
8 Present and diSCUSS the following
~ ReqUirements for data collection, mapping, and training
~ lntergraph and City Team Roles.
City shall
PrOVide the following CAD Core Team personnel to support the Process Workflow Analysis
Workshop. The Core Team will be intimately involved in the system implementation from the City's
perspective, making system configuration deciSions, and procedural and policy change
recommendations It is understood that one IndiVidual may fulfill more than one of the below
mentioned roles
City of Corpus Christi - Project Statement of Work
Page 6
PrOject Manager
2 System Administrator
3 GIS person(s)
4 End users (Calltakers. Dispatchers, Communications supervisor representative, or a
representative from each)
5 Training representative
6 Remote user representative (for I/NetViewer and I/NetDispatcher)
7 Radio System representative
8 Field personnel representative
9 Command staff and any other Agency personnel that will be utilizing the system
10. Personnel involved in data collection Including a database administrator
The above City personnel will assist Intergraph in understanding and collecting the following
information
Workflow overview of eXisting enVIronment
2 Technical information of the Interfaces
3 Sample reports and output
4 Any electronic CAD data available
5 Complete mapping data
6 Answers to specific policy and procedure questions that will assist Intergraph in system
configuration deCisions
7 ASSign a core team of Dispatcher and Calltaker representatives (end users and supervisors) , as
well as IT staff who will have the organizational authority and experience to make these decisions
for the City This team will act as the approval board for these actions since the process naturally
lends itself to real time changes The Project Manager will make ultimate decisions regarding
which changes will be undertaken
Completion Criteria:
This task IS considered complete upon completion of the Project and Workflow Analysis Workshop
Course # ISPT1 000) and submittal by Intergraph of the "Project /Workflow Analysis Report"
Task 5: Map Development and Refinement
Task Description:
fhe map and related database attnbutes (geofile) are key components of the system, the heart of real-
time responsiveness and the basis for accurate downstream reporting. Intergraph assumes that the City
will use the local City GIS data as the platform for the map data for the CAD, RMS and Mobile solution.
Intergraph recognizes that there will always be necessary law enforcement requirements and accuracy
specifications to uphold, and will work with the City to ensure that this source suits the needs for the City's
Integrated solution
City of Corpus Christi - Project Statement of Work
Page 7
The map and related database attributes (geofile) are key components of the system, the heart of real-
time responsiveness and the basis for accurate downstream reporting Map development is an iterative
process that IS the responsibility of the City, guided by training and consultation provided by IPS.
Responsibilities:
Intergraph shall
Work with the City to review the City GIS data to ensure suitability for use by City
2 Provide a Mapping Lead to gUide the map development process
3 Provide mapping data specifications for source map development
4 Analyze data programmatically, making recommendations for improvements.
5 Import (roll) mapping source data Into Intergraph format up to three times.
6 Lead classes / workshops as noted above
7 Provide instruction on testing methodology
8 Provide consultation throughout the map development process
City shall
Be responsible for providing the mapping source data and for the thoroughness and integrity of
that data
2 Provide a Mapping Lead to gUide Citys mapping data development
3 Provide a System Administrator or other designated person to learn how to roll the map into the
system and to be map-focused, learning how the map interrelates with the other system
components so that mapping data problems can be recognized and corrected quickly.
4 Test the map Integrity
5 Make data corrections, based on the provided specifications and on recommendations provided
as a result of data analysis
6 Verify that the final CAD map that IS delivered prior to CAD system cutover contains all required
data corrections
7 Attend training classes I workshops
8 Assume responsibility for map rolls after training / consultation
9 Assume responsibility for all data corrections. updates and map rolls after training I consultation,
and CAD system cutover
Completion Criteria:
This task IS considered complete when the City has reviewed and accepted the final CAD map prior to
system cutover
City of Corpus Christi - Project Statement of Work
Page 8
Task 6: Interface Control Documents (lCD's) for IICAD and IILEADS-RMS
Task Description'
Initial requirements for I/CAD and I/CAD-related interfaces are obtained through the Project Workflow
Analysis session (IPST1000), and for I/LEADS and It's related interfaces, are obtained through the
!/LEADS System Overview Workshop (IPST2209) . The goal is to obtain essential information needed to
configure the interfaces and Identify data Information needs for the highly customized interfaces. This will
be followed by three separate workshops designed to finalize remaining interface requirements. These
workshops are as follows
. CAD Interface ReqUirements Workshop
. RMS Interface ReqUirements Workshop
. I/Mobile Configuration Workshop
During the CAD and RMS Interface ReqUirements Workshops, Intergraph technical personnel will meet
on site with the appropriate City personnel to review each of device or external system that will be
Interfaced to (as listed belowl, the type of connection and protocol to be utilized (serial, TCP/IP), the type
of data to be transferred, and definition of the interface screen layouts and formats (if applicable).
Intergraph will also prOVide questionnaires to assist in Identifying basic configuration needs for each
interface
Interface Control Documents (ICDs) Will be developed for all interfaces to be developed and implemented
based upon the Information shared within the workshops
Interfaces Include
CAD Interfaces
. I/Informer for TCIC/NCICITLETS/TDLD/PPD/DMV/Pawn Interface
. I/lnformer for Municipal Court System Interface
. I/MDT - I/Mobile Data Terminal
. I/Flre Station Alerting
. I/Tracker
. I/CADLink file transfer to CrimeView Web
. I/FRMS - CADLink (Link with FIREHOUSE FireRMS)
. I/InterCAD to DECCAN Live MUM Interface
. Interface to ANI-All E911
. !!TDD - Telephone Device for the Deaf - Zetron
RMS Interfaces
. I/LEADS RMS Import from Pawn Shop System Interface
Responsibilities:
Intergraph shall
ProVide questionnaires to assist in identifying basic interface expectations
2 Prepare draft lCD's, based on the Project Workflow Analysis and questionnaires.
3 Lead Requirements Workshops, Identifying remaining open items and expectations
City of Corpus Christi - Project Statement of Work
Page 9
4 Wnte lCD's for City review and approval.
5 For I/Mobile
a) Dunng the I/Mobtle Workflow and Configuration Workshop (IPST2502), the I/Mobile Trainer
and I/Mobile implementer will spend two days demonstrating all of the basic I/Mobile
capabilities and showing how the City's configuration has already been modified to meet the
Identified needs of the agency (based on observations during the Project Workflow Analysis).
t,) DUring these two days, the Cltys I/Mobile Core Team will make recommendations/requests
for additional configuration changes, to ease user training and encourage system adoption.
The City team Will prioritize requests
C I DUring the follOWing three days, the I/Mobile Implementer will remain on site, completing all
changes that can be made within that time period As changes are made, the core team
members will be asked to review and approve them
d) At the end of the week, the implementer Will review the completed changes and any additional
requests with the City I/Mobile Core Team An additional two days of configuration time will be
done remotely Thus. the priOritization of the remaining items will be critical. If the City
requires additional time to review and evaluate the desired I/Mobile configuration
requirements for the police configuration. the City will document these final configuration
changes to Intergraph at least 30 days prior to the scheduled I/Mobile go live date, at which
time Intergraph will configure the finall/Mobile software image
e) Approximately two months follOWing the cutover to live operations, the I/Mobile Implementer
will return on site. DUring this Visit. the I/Mobile Implementation Lead identifies additional
configuration opportunities, based on City feedback and on observation. After conferring with
City staff configuration requests requiring up to two days of labor will be completed, if
needed
:Ity shaH
Provide detailed schema. protocol query specifications as needed, and as available per
interface
2 Provide a POint of Contact for each interface who is knowledgeable of the workflow and data
requirements and who has authOrity to make deSign decisions
3 Answer Intergraph questionnaires thoroughly and timely
4 Act as the primary pOint of contact with third parties, Including other vendors, state agencies, and
local agencies that control products and/or databases with which Intergraph products are to be
Interfaced
5 Ensure that open questions and deSign decisions are made conclusively and in a timely fashion
6 ReView and approve rCDs
7 Discuss Interfaces to be accessed by the system for both CAD and RMS and provide City specific
Interface data concerning the radio or wireless system, WAN, IP addressing scheme, and
interface protocols for both CAD and RMS
Completion Criteria:
This task IS considered complete when the City has reviewed and accepted the Interface Control
Documents (lCD's)
City of Corpus Christi - Project Statement of Work
Page 10
Task 7: Hardware and Software Installation and Deliverables
Task Description:
The following activities will take place dUring the course of Implementing the system:
. Install hardware and software (at the locations identified In the Intergraph's response to the City's
RFP and the contract pricing detail summary, unless otherwise mutually agreed).
. Install initial complete hardware and software
. Install final software versions prior to system cutover to live operations
. Assist City In configuring the CAD Mobile, RMS and JMS systems to the City's workflow and
reqUirements
Responsibilities:
intergraph Shall
PrOVide the hardware and software as defined In contract pricing detail summary, Exhibit A
2 Hardware that is to be purchased by Intergraph under the Agreement shall be ordered at a time
mutually agreeable to both the City and Intergraph
3 Install the servers and workstations at the City site. Servers will be rack-mounted. All Server
Software purchased under this contract will be Installed on the servers by Intergraph personneL
4 Install the system client software as follows
a CAD on all CAD Dispatcher Workstations
b Mobile on 5 City-supplied MDC's, proViding instructions and training to City on the Mobile
client software installation process
RMS / JMSup to five (5) of the RMS I JMS client workstations, providing instructions and
training to City on the RMS I JMS client software Installation process
AFR up to five (5) of the AFR client software on MDC's, providing instructions and
training to City on the AFR client software Installation process
d
5 Install Initial Complete Hardware and Software
The Intergraph Project Manager and Hardware Implementation Lead will arrive on site to install
the hardware Identified in contract pricing detail summary Exhibit A
The database, CAD and Interface software, and map will be installed and configured on the
servers and client workstations based on the information collected from the Project Workflow
Analysis The Implementers will ensure the system is ready for training. At this point, the initial
CAD system IS considered to be initially Installed and available for the subsequent training
workshops starting With IICAD Data Workshop (IPST1 001)
6 Further Installations/modifications
As With any major technology proJect, configuration refinements will occur on the system and
throughout the project as the City team becomes more familiar with the software and fine tunes
the system via configuration changes
Interfaces requIring Significant customization. such as the I/Informer-based interfaces will be
Installed remotely (Via VPN) as part of the development process. These products will use a
City of Corpus Christi - Project Statement of Work
Page 11
City shall
server-based product that establishes communications with the remote systems and cannot be
tested to allow further development until the communication lines have been established between
the City and the remote agencies. If possible. these will be ready upon initial installation, but may
lag depending on the timeframe in which test lines can be established and communications can
be confirmed All Interface software will be installed and fully configured prior to end user training
and system go live
-,
Install additional products not purchased under this contract such as third-party backup software,
and any telephony software
Install the RMS j JMS client software on the RMS / JMS workstations after receiving instruction
from Intergraph on the client software installation process
Install the Mobile client software on the MDC's after receiving Instruction from Intergraph on the
client software installation process
install the AFR client software on the MDC's after receiving instruction from Intergraph on the
client software installation process
Confirm that the initial hardware and software Installation and delivery has been completed by
Intergraph
Configure the Active Directorl (Native Mode) domain, if desired Intergraph recommends that a
separate server be used as a domain controller
PrOVide two twist-lock receptacles per server Receptacles for primary and secondary CAD
servers should be or separate circuits of a UPS
8 Receive and store the hardware delivery untillntergraph personnel arrive on site
C) ASSist the Intergraph team as they install the hardware (City Project Manager, System
Administrator and Network specialist)
,1
..j
.;;;
o
-:
After the hardware Installation, the City Project Manager, System Administrator, and Network
speCialist will confirm the site IS ready for software Installation. The following must be confirmed
a) All hardware IS Ir place and on the network and ready for interface and CAD install
b) All Interface connections are complete in accordance with the check list supplied
c) Sufficient senal ports are I'eady to support all RS232 type communication for interfaces
d) City System Administrator is available for the duration of the Installation
Once the Intergraph team arrives to Install all software and interfaces, the City Project Manager
and Network specialist must be available to assist
Confirm the site IS ready for hardware Installation; the City Project Manager, System
Administrator, and Network specialist will perform thiS task The following must be confirmed:
a) New hardware (servers) has been received
b) Network IS ready
C) Power requirements have been met
d) Serial port requirements have been met
Completion Criteria:
This task IS considered complete when the hardware and software as defined in contract pricing detail
summary Exhibit A are installed on the Cltys premises and verified by the City's Project Manager to be
City of Corpus Christi - Project Statement of Work
Page 12
()perating in accordance with standards as set forth within the agreement and this SOW.
Task 8: CAD Interfaces
Task Description:
The Implementation of the Interfaces IS performed In conjunction with the CAD implementation and is
based on the lCD's described above in Task # 6 After initial Interface installation and configuration,
described under prevIous tasks, the expectation IS that the interfaces will be exercised during user
training. and system testing Additional configuration changes can be made based on City requests. The
Intergraph Interfaces Implementation Lead will, where appropriate, provide one-on-one training to the City
System Administrator on how to make common configuration changes and on general software
architecture and operation
Responsibilities:
Intergraph Shall
Install and configure Interfaces as described in the Interface Control Documents.
2 Provide one-on-one instructions on common configuration changes.
3 Make minor additional configuration changes after Installation Note that major changes after ICD
approval such as change in protocol communication type will require additional funding.
C::lty Shal!
Ensure that preparatory work has been done to establish authorized access to systems to which
CAD is to Interface (TCIC NCIC, etc I
2 Verify that phYSical connectivity has been achieved from City's communication server to remote
agency servers
3 Provide the following values to Intergraph
a) IP address for remote databases
b) Socket value for remote systems
c) Operator ID's, ORis, terminal mnemonics. as needed by remote systems
4 The System Administrator must work closely with the Intergraph team for the duration.
Completion Criteria:
This task IS considered complete when each CAD interface is installed and tested. The operation or
availability of the external system or third-party software is necessary for task completion.
Task 9: Mobile Data System Product Installation
Task Description:
Install and configure MDS functionality
Responsibilities:
Intergraph shall
City of Corpus Christi - Project Statement of Work
Page 13
Provide mobile data terminal software (I/MDT) to provide message routing, logging, syntax
translation and security capabilities for MDCs
2 Provide I/Mobile client licenses for mobile units
3 Configure I/Moblle user interface per the ICD as described above
4 Provide I/Tracker server license to support City's automatic vehicle location functionality.
5 Configure !Tracker.
6 Provide one-on-one training on I/Tracker and I/MDT to the City's System Administrators.
7 Installl/Moblle on 5 of the MDCs dUring initial hardware installation
8 Train City personnel on the proper Installation and configuration of the I/Mobile client software.
9 Install GPS equipment in five representative City vehicles and train the City to install the GPS
equipment on remaining vehicles
City shall
Provide a complete and accurate description of the wireless interface protocol.
2 Participate In the relevant training and workshops as described elsewhere
3 Installl/Mobile on the balance of the MDC's
4 Provide a strong end user based core team to ensure that configuration options are understood
and are designed for optimum end user acceptance
5 Ensure that designated City administrative personnel receive training on the proper installation
and configuration of the I/Mobile client software
6 Provide Radio infrastructure utilizing the TCP/I P protocol for software interface.
Completion Criteria:
This task is considered complete when all mobile data terminal software has been installed and tested.
Task 10: Mobile Data System Customization to MDS Requirements
Task Description:
During the Process Workflow AnalYSIS VISit, the I/Mobile implementer and Trainer will participate in
Interviews of the City field management and staff, to gain an understanding of the City's desires for site
specific mobile screen configurations A questionnaire will also be reviewed to ensure that specific
information IS obtained Based on interviews conducted during this visit the I/Mobile Implementer will pre-
configure I/Mobile prior to on site Installation
Responsibilities:
Intergraph shall
1 Conduct interviews
2 ProVide questionnaires to assist in Identifying basic configuration needs.
3 Conduct the I/Mobile Configuration Workshop
4 Make configuration changes per City requests
a) Following the I/Mobile Configuration Workshop
b) Between the I/Mobile Configuration Workshop and final MDC software loading prior to live
operations
City of Corpus Christi - Project Statement of Work
Page 14
City shall
Assign a core team of future I/Mobile users (Police Field Staff primarily, not just command staff),
as well as IT staff who will have the organizational authority and experience to make these
decisions for the City This team will act as the approval board for these actions since the process
natuarally lends Itself to real-time changes
2 Provide an approveD priontized list of configuration change requests to the I/Mobile implementer
3 Test configuration changes as they are delivered. providing feedback to the I/Mobile Implementer
Completion Criteria:
This task IS considered complete when all mobile data terminal configuration changes have been
completed
Task 11: Mobile Data System - Train the Trainer Training
Task Description:
A Train the Trainer program will be developed and scheduled for the City and then conducted to
thoroughly train City training and administrative personnel on the use of the I/Mobile client subsystem, and
City technical personnel on the operation and support of the I/MDT and I/Mobile software. One (1)
electronic set of user and technical documents plus one (1) hardcopy for each student will be provided for
each installed system The training will be provided by members of Intergraph training personnel (unless
some other arrangement is made by mutual agreement of Intergraph and the City).
Responsibilities:
! ntergraph shall
Provide three (3) I/Mobile User (IPST2501) training classes for City Technical and Training staff
members, as presented below and on a mutually agreed to schedule. Training will be provided on
all standard shifts not to exceed 8 hours per 24-hour period
2 Provide one complete set of pnnted training matenals In the form of reproducible black and white
masters and machine-readable documents In Microsoft Word 2003 or higher format, based upon
Intergraphs documentation standard at the time of delivery.
3 Provide technical and user manuals for alllntergraph subsystems In the form of on-line Help.
City shall
DeSignate and assign personnel to receive training in groups not to exceed the maximum class
size of 12 students
2 ProVide the necessary classrooms facilities, matenals, copies of documentation, networks and
lines to data terminals, personal computers and PC operating system software, and related
equipment to support training classes Set up the workstations per Intergraph instruction
ThiS includes one full-function workstation per student one full-function workstation for the
instructor. an LCD. a projection screen. a whiteboard, and connectivity to the server.
3 Ensure that appropnate City personnel are available to actively participate in the scheduled
training programs and that they attend the classes In their entirety.
City of Corpus Christi - Project Statement of Work
Page 15
4 Ensure that City personnel to receive training are proficient In the use of Microsoft Windows
functionality
5 Assume responsibility for travel and per diem expenses for the City staff for any off-site training
classes selected by the City
Completion Criteria:
This task is considered complete when all sCheduled Mobile Data System Training has been completed.
Task 12: Mobile Data System Acceptance Testing
Task Description:
Demonstrate the applicable functions and features of the MDS functionality as defined in the Intergraph
Acceptance Test Plan, the baseline documentation and the Intergraph response to the City's RFP. City
staff will perform functional testing of the Intergraph subsystem. with Intergraph assistance.
it should be understood that testing is an Iterative process As problems are identified and resolutions
provided retesting will occur
Responsibilities:
Intergraph shall
Provide a draft Acceptance Test Plan This test plan will be functionally based and will include the
commands included In City's configuration
2 Review and approve the final Acceptance Test Plan. which should be modified by City to include
City s unique workflows
3 Certify all applicable software. subsystems. and ancillary systems as ready for functional testing.
4 Demonstrate the tailored and configured functions of the Installed subsystem. This is done in the
context of training classes
5 Review any discrepancies In functionality identified by the City
6 Correct software or documentation In a mutually agreed upon manner prior to system cutover.
Minor issues that are mutually deemed to be non-Impactive will be logged for future correction.
City shall
Expand the functional testing documentation to include City-specific workflows.
2 ReView and approve the final Acceptance Test Plan, ensuring that the A TP includes functionality
from the Intergraph baseline documentation and RFP response
3 Execute the approved Acceptance Test Plan
4 Document each discrepancy of functionality located between tested criteria and Acceptance Test
Plan and provide such documentation to Intergraph for resolution
5 Provide final approval for cutover to live operations
Completion Criteria:
This task IS considered complete when the mobile data system has been demonstrated to operate in
accordance with the Intergraph specification documents. the City's configuration requirements and the
City of Corpus Christi - Project Statement of Work
Page 16
'.\cceptance Test Plan on five (5) City-supplied MDCs (the installation of the mobile software on the
remaining City-supplied MDCs is not required for task completion)
Task 13: Final CAD Equipment Installation
Task Description:
The servers will be delivered into their final location upon initial system installation. Intergraph-provided
workstations will be Installed by Intergraph Into a training/test environment where they will be used until
immediately before cutover to live operations City personnel will be responsible for physically moving the
City-supplied workstations from the training/test environment to the communications center with
assistance from Intergraph Exact timing will be determmed well in advance and documented in the
Cutover Plan
Responsibilities:
intergraph shall
Develop a detailed Cutover Plan, In conjunction with the City
City shall
If required physically move the Intergraph-supplied workstations from the training/test area into
the communications center
2 Verify that network connectivity has been achieved follOWing the movement of workstations.
3 Provide. configure, and Install all remaining equipment not provided by Intergraph prior to
Intergraphs arrival for monitoring subsystem integration testing
4 Complete any required console and related modifications
5 Perform any site modifications to allow successful equipment installation such as power or
network outlets
Completion Criteria:
This task is complete when the complete CAD hardware configuration is tested and validated by City
personnel
Task 14: CAD System - Train the User Training
Task Description:
A.. full-scale Train the User training program will be provided for the City This training is conducted in a
classroom setting, and is deSigned to thoroughly train City Core Team, Training personnel, all of the City's
calltakers, dispatchers supervisors, and administrators on the use of the CAD subsystem and City
technical personnel on the operation and support of CAD subsystem. In addition, one-on-one
opportunities Will be provided, particularly for the CAD System Administrator, to work with the
implementation Leads as the system is Installed and supported throughout the implementation process.
Intergraph Will also provide consulting support to those personnel responsible for training of future I/CAD
Jsers. This consulting session (IPST201 0) Will cover topics of interest to a customer's designated trainers,
to help them reach maximum comfort ievel with teaching their future employees.
City of Corpus Christi - Project Statement of Work
Page 17
Responsibilities:
intergraph shall
Provide Core Team CAD training for City Technical and Training staff members for all installed
CAD software Courses include
· I/CAD Project and Workflow Analysis (IPST1 000)
· I/CAD Data Workshop (IPST1001)
· I/CAD Deployment Planning and Configuration (IPST1003)
· I/CAD Workflow and Configuration Workshop (IPST1004)
· I/CAD Calltaklng Essentials (IPST2003)
· I/CAD Dispatching Essentials (IPST2004)
· I/CAD Supervisor (IPST2005)
· I/CAD Database Schema and Reports Overview (IPST2009)
· I/CAD Trainer Consulting (IPST2010)
· I/MARS Configuration and Administration (IPST2102)
· I/Netvtewer. I/NetDispatcher (IPST2401)
· I/Skill Administrator (IPST2402)
· I/Skill User (IPST2403)
· I/CAD System Administration (IPST3101)
· I/CAD CADTools User (IPST3103)
· Map Maintenance for I/CAD Systems (I PST31 04)
· I/CAD System Maintenance (I PST31 07)
· I/CAD Advanced System Administration (IPST3108)
2 Provide Train the User training for all of the City'S calltakers, dispatchers, supervisors in the use of
the CAD Calltaklng and Dispatcher client software Courses include
· I/CAD Calltaklng Essentials (IPST2003)
· I/CAD Dispatching Essentials (IPST2004)
· IleAD Supervisor (IPST2005)
3 All CAD Training will be provided on two shift structures (not within the same week), with 8 hours
of class time each day and a one-hour lunch break Training will occur Monday through Friday.
4 Provide machine-readable documents in Microsoft Word 2003 or higher format for each student,
based upon Intergraph's documentation standard at the time of delivery. Documentation files will
not be password protected
5 Provide documentation In the form of on-line Help files, providing the user quick and easy access.
ThiS Includes application user and administrator documentation. Operators can access on-line
Help files both inside an application (while the application is running) and outside an application
(through the Start menu or Microsoft Explorer). Third-party documentation is pass-through from
the manufacturer Delivery of off-the-shelf and as-built documentation will be provided before
training System administrator and user training manuals are provided as is appropriate for the
type of class being taught
City of Corpus Christi - Project Statement of Work
Page 18
City shall
Designate and assign personnel to receive training In groups not to exceed the class size listed in
the training plan
2 The City will provide the necessary classrooms. facilities, materials, copies of documentation,
networks and lines to data terminals. personal computers and PC operating system software, and
related equipment to support training classes This includes one full-function workstation per
student. one full-function workstation for the instructor, an LCD. a projection screen, a whiteboard
and connectivity to the server
3 Provide sufficient copies of the documentation supplied by Intergraph to support all students in the
training classes
4 Ensure that appropriate City Training, system administrator, and calltaker and dispatcher
personnel are available to actively participate In the scheduled training programs and attendees
attend scheduled training classes in their entirety
5 Ensure that City personnel to receive CAD training are proficient in the use of Microsoft Windows
functionality
6 Assume responsibility for travel and per diem expenses for City staff for any off-site training
classes selected by the City
Completion Criteria:
This task .s considered complete when the scheduled CAD technical and user training has been
completed
Task 15: CAD Integration Testing of MDS and Acceptance Testing of Other Interfaces to CAD
Task Description:
After interfaces have been configured and Installed, the lntergraph CAD Training Lead and
Implementation Leads Will facilitate a Workflow/Configuration Workshop. The intent of this week-long
exercise is to have the core team exercise the full configuration, including all interfaces in realistic
scenarios. The City will bring real-life scenarios to this event These may be in the form of scenarios that
already eXist and are used to train new employees, or they may be written especially for this workshop, by
the City. and also used for formal testing as well. This workshop will. in essence, be both a learning
experience and a "pre-test" experience for full system testing
This expenence IS extended in a formal. methodical way after functional unit testing of I/CAD and the
MDS system. as these same (or expanded) scenanos are used to fully exercise the system, including all
)f its interfaces City Will be responsible for ensuring that the full system workflow testing includes all
cequired capabilities per the ,t\cceptance Test Plan and the I nterface Control Documents,
':;Ity and lntergraph staff Will conduct the Integration testing
Responsibilities:
Intergraph shall
Certify the interfaces are properly Installed, fully configured per the lCD's, and are ready for
Integration testing
City of Corpus Christi - Project Statement of Work
Page 19
2 Demonstrate all Inter-system communications between installed Intergraph systems and between
lntergraph and non-Intergraph systems, according to the Acceptance Test Plans and the Interface
Control Documents
3 Assist the City in testing each interface
4 Assist the City in making any final system configuration changes
5 Review and correct any discrepancies that are identified by the City prior to final system
acceptance and payment
6 Software or documentation shall be corrected In a mutually agreed upon manner prior to system
cutover Minor issues that are mutually deemed to be non-impactive will be logged for future
correction
7 Correct software or documentation in a mutually agreed upon manner prior to system cutover.
City shall
Conduct test procedures and verify all inter-system communications between installed Intergraph
systems and between Intergraph and non-Intergraph systems, according to the Acceptance Test
Plans and the Interface Control Documents
2 Identify In writing each discrepancy between subsystem and ancillary system functionality and the
Interface Control Documents within ten (10) business days of problem identification.
3 Work with Intergraph to Identify the type of correction needed to ensure that each subsystem and
ancillary system conforms to the Interface Control Documents
Completion Criteria:
This task is considered complete when the CAD Integration Testing of MDS and all CAD Interfaces has
been completed
Task 16: CAD I Mobile Acceptance Testing
Task Description:
Demonstrate the applicable functions and features of the CAD / Mobile functionality as defined in the
Intergraph Acceptance Test Plan, the baseline documentation and the Intergraph response to the City's
RFP City staff will perform functional testing of the Intergraph subsystem, with Intergraph assistance.
it should be understood that testing's an Iterative process As problems are identified and resolutions
provided retesting Will occur
Responsibilities:
I ntergraph Shall
Certify the basIc functionality as part of Intergraph standard software certification procedures.
2 ProVide a draft CAD I Mobile Acceptance Test Plan for the I/Calltaker and I/Dispatcher product.
ThiS test plan will include functional and performance testing
3 Review and approve the final Acceptance Test Plan. which should be modified by the City to
inClude City's unique workflows
4 Certify all applicable software. subsystems and ancillary systems as ready for functional testing.
5 Demonstrate the tailored and configured functions of the Installed subsystem.
City of Corpus Christi - Project Statement of Work
Page 20
6 Review any discrepancies in functionality identified by the City.
7 Correct software or documentation In a mutually agreed upon manner prior to system cutover.
Minor issues that are mutually deemed to be non-impactive will be logged for future correction.
City Shall
Expand the functional testing documentation to Include City-specific workflows.
2 Review and approve the final Acceptance Test Plan
3 Execute the approved Acceptance Test Plan with assistance from Intergraph personnel,
4 Provide final approva, for cutover to live operations Review and approve the City test plans.
Completion Criteria:
This task is considered complete when the CAD / Mobile System has been demonstrated to operate in
accordance with the Intergraph Acceptance Test Plan, the baseline documentation and the Intergraph
response to the Citys RFP
Task 17: CAD I Mobile Cutover Final Preparations
Task Description:
Intergraph and the City will JOintly develop a CAD / Mobile Cutover Plan, detailing steps necessary to move
from the Implementation environment to live operations The Cutover Plan will assign tasks and
responsibilities for both Intergraph and City personnel during the final month before cutover, to ensure that
the move to live operations goes as smoothly as possible This Plan will include such things as City
staffing, movement of equipment into final location, final database clean out of test events, issue reporting
procedures and planned sequence of events for the cutover day
Responsibilities:
Intergraph shall
Create a draft CAD I Mobile Cutover Plan
2 Work With City personnel to refine the Cutover Plan
3 ReView and approve the final Cutover Plan
4 Manage Intergraph operations per the final Cutover Plan
City shall
ReView and comment on the draft CAD / Mobile Cutover Plan
2 Work With Intergraph personnel to refine the Cutover Plan
3 ReView and approve the final Cutover Plan
4 Manage City operations per the final Cutover Plan
Completion Criteria:
This task is considered complete when the City has reviewed and approved the final CAD / Mobile
Cutover Plan
City of Corpus Christi - Project Statement of Work
Page 21
Task 18: CAD I Mobile System Production Cutover
Task Description:
Once testing is complete. Intergraph will certify the CAD 1 Mobile subsystems as operational and ready for
production operation A Readiness Review meeting will be held with members of the Intergraph and City
teams The final decision to cut over to live operations is ultimately a City decision; however, both
intergraph and City will review system status and jointly make a recommendation to move into production.
lntergraph personnel will assist the City in placing the system Into productive use. Intergraph personnel will
8e on site at least 2 days prior to live operations and will proVide post-live cut on-site 24/7 support for 5
jays dUring the week of cutover On-going focused Helpdesk phone support will follow on site support.
f=ollow-up reassessment visits will be planned as well
fhe cutover operation Will be supported by the following Intergraph staff
. Prolect Manager
. CAD Implementation Lead
. CAD Interfaces Implementation Lead
. CAD Training Lead
intergraph personnel will fine-tune the CAD I Mobile software application for optimal performance. City
technical personnel will be present to proVide support for the system City training personnel and core
team members will be scheduled so as to provide knowledgeable City support to all shifts during the first
few days after cutover to live operations In conjunction with the scheduled Intergraph staff, who will also
provide support to all shifts
After live cut over to production operations the 3D-day CAD Performance and Reliability Test period will
begin and the CAD and Mobile Extended Software Warranty for 12 months begins.
Responsibilities:
!ntergraph shall
ASSist the City staff in plaCing CAD j Mobile into a production status
2 ProVide technical support 24/7 for 5 days during the week of cutover.
3 Monitor the initial operation of CAD Mobile and answer any operational questions raised by the
City
4 ASSist the training staff in utiliZing the subsystem and the computer operations staff in supporting
the subsystem
City shall
Place the software into production within ten (10) calendar days following certification and begin
operational use In consultation with Intergraph and in accordance with the Project Schedule.
2 ProVide technical staff to support the system
3 PrOVide training staff to answer end user questions In conjunction with the Intergraph staff.
4 PrOVide a detailed list of questions and issues that still require explanation or resolution by
Intergraph at the end of each day
City of Corpus Christi - Project Statement of Work
Page 22
Completion Criteria:
This task IS considered complete when CAD / Mobile IS placed into production operation.
Task 19: CAD I Mobile Performance and Reliability Testing
Task Description'
Verify that the CAD I Mobile subsystem demonstrates reliable operation in a production environment prior
to the start of the application software warranty period
CAD and Mobile will demonstrate Critical subsystem availability levels of 99.99% or better for a thirty (30)
calendar day Performance and Performance and Reliability Testing period
At the end of thiS test period, if subsystem availability has not met or exceeded this required level, the
Performance and Performance and Reliability Testing period will continue until this level of reliability has
been demonstrated for at least thirty (30) consecutive calendar days.
The CAD subsystem will be considered "down" if there is a failure of any CAD redundant or fault-tolerant
computer hardware or software module or component that prevents critical event entry, dispatch or status
monitoring functions to operate at a level that allows operation to continue. Functional problems that do
'lot prevent productive use Of the subsystem are not considered downtime. Software problems of this type
are documented by the City on an "action item list" to be fixed during this phase. Downtime will begin at
the time that the designated Intergraph contact person has been notified of the failure.
The subsystem shall not be considered down during any manual or automated fail-over process, or if it is
Jperational In a backup mode or Via replacement with spares. pending the receipt of replacement
:::omponents and repair of the failed component
f=ailures In IndiVidual communication lines terminals, workstations, PCs. non-Intergraph PC licensed
software modems. data communications or problems that involve non-redundant or fault-tolerant
'lardware or remote workstation or terminal sites do not constitute downtime. They will be repaired as
expediently as possible, and operations will then continue
CAD Performance and Perfmmance and Reliability Testing will not be delayed or interrupted if there are
failures in systems that are not the responsibility of Intergraph (communication lines, external databases,
etc.) Also. the Performance and Reliability Test and subsystem certification will not be delayed if any
user-provided peripheral components encounter a failure or have not been made available for implemen-
tation and testing according to the project schedule Scheduled subsystem unavailability for purposes of
software update, performance tuning, file backups and other processes typical in a production
environment is not considered as downtime
In the event that the subsystem IS considered to be 'down dUring thiS test period, one of the following will
)ccur
· Subsystem operation will be suspended, the problem IS considered "major," and immediately
diagnosed and corrected After installation of the appropriate corrections, the test period will
resume. logging the time since Intergraph was notified of the failure as downtime, or
· Subsystem operation will continue. the problem will be logged and then corrected, tested and
demonstrated during the Performance and Reliability test period. In this case, the problem is
documented as a "minor" system problem, the subsystem not removed from on-line operation,
and the subsystem is not conSidered down
City of Corpus Christi - Project Statement of Work
Page 23
No software. related subsystem changes or enhancements shall be made to any subsystem undergoing
subsystem certification unless they are directly related to addressing a "major" failure.
The Performance and Performance and Reliability Testing process can be temporarily suspended upon
agreement between City and Intergraph for scheduled changes, software corrections or upgrades. In this
event the test period will resume when the subsystem is again operational. without logging downtime.
During the test period, Intergraph will develop a list of 'minor" subsystem problems as described above.
This list will be completed and delivered to the City Within five (5) business days following the completion
of the subsystem certification phase These items, plus any others that are found as the subsystem moves
nto full production operation will be addressed and corrected in a timely manner (according to an agreed-
to schedule) during thiS period of operation or as part of the extended warranty period. The resolution of
minor" subsystem problems will not delay the completion of this task Any further subsystem problem or
nconsistency With the functional requirements will be addressed under the provisions of the warranty.
When Intergraph has corrected and demonstrated all significant functional and operational errors and
areas of non-compliance that have oeen Identified on the action item list during the test period, the
.ndividual subsystems will be accepted and made available for continuing productive use. Any additional
problems or areas of non-compliance identified following this Performance and Reliability Testing period,
'ncluding those related to any subsystems or ancillary systems that have not yet been placed in productive
operation will not prevent subsystem certification and will be addressed as part of the standard software
Extended Warrantv
Responsibilities:
ntergraph shall
Identify a pOint of contact for logging system Interruptions that is available 24/7 during the
Performance and Reliability Testing period Develop and complete a list of "minor" subsystem
problems for delivery to the City within five (5) business days following the completion of
Performance and Performance and Reliability Testing
2 Address and/or correct the 'minor" subsystem problems either during this period or as a part of
the Extended Software Warranty period
City shall
Utilize and monitor the CAD / Mobile subsystem in a production environment
2 Prepare the site aSlecessary (i e ensure communication lines are installed and available, any
City-prOVided equipment and external systems are operational, etc.).
3 log all functional problems on an 'action Item list' with detailed information as to the sequence of
events leading up te the problem time of day node name or unit involved, and other such
pertinent details
4 Contact Intergraph personneln a timely manner In the event of subsystem problems or failures
5 Begin subsystem monitoring In support of the Extended Warranty period.
Completion Criteria:
fhis task IS considered complete after CAD / Mobile has demonstrated critical system availability levels
during the test period for a thirty (30) day Subsystem Performance and Performance and Reliability Test
period, commencing at the CAD / Mobile Production Cutover
City of Corpus Christi - Project Statement of Work
Page 24
Task 20: I/LEADS-RMS Software Installation
Task Description:
At the I/LEADS portion of the project kickoff requirements will be provided to the City regarding data that
rnust be gathered and provided to Intergraph m advance of system staging This data includes such things
as
~ Statute mformatlon
. Configuration for system code-listed values (drop downs In the GUI)
~ Employee information
City will be provided with a format m which to provide the information at least 90 days before such
Information IS due to Intergraph This data is required to be received by Intergraph at least one month prior
to system staging Intergrapr will import the provided data into the system as part of the initial staging.
All applicable I/LEADS application software. as well as equipment vendor's operating system software
necessary for this phase of the project to be completed will be loaded on the City's server equipment.
Oracle Database. and any other special database setup, Will take place as part of this task.
As a part of the system staging, Intergraph will present Informal (whiteboard) training to the City personnel,
who will participate m the system staging Following this basic system introduction, City personnel will
actually perform much of the hands-on staging of the database and application software, under the
continuous direction and gUidance of the Intergraph RMS Implementation Lead. This begins the training
process for the City I/LEADS System Administrator
Responsibilities:
intergraph shall
PrOVide requirements for mitlal configuration data gathenng by the City.
2 Install the required equipment vendor operating system software on the server and associated
equipment located at Intergraph
3 PrOVide I/LEADS RMS client license per contract pncmg detail summary, Exhibit A
4 I nstall the RMS client software on up to five (5) of the RMS client workstations, providing
instructions and training to City on the RMS client software installation process.
5 fram the City I/LEADS Admmistrator to configure I/LEADS RMS, including the field reporting
client, so that City can make their desired configuration changes
6 PrOVide consultation on desired Field Reporting changes, advising City as needed on best
methodologies to make changes
7 ASSist City personne in installmg licensed I/LEADS software withm this configuration.
8 Import the provided City-specific data
9 T est the initial operation of the baseline I/LEADS subsystem
City of Corpus Christi - Project Statement of Work
Page 25
City shall
Provide the required City-specific configuration data for initial system configuration.
2 Install the RMS client software on the RMS workstations after receiving instruction from Intergraph
on the client software installation process
3 Be active participants in the staging process, performing hands-on portions of the staging, under
the guidance of the IILEADS Implementation Lead
4 Be available to address and answer questions that arise during the tailoring and configuration of
the subsystem
Completion Criteria:
This task is considered complete when the I/LEADS RMS baseline application modules have been
,nstalled tested and verified to meet specifications by the City
Task 21: Build IILEADS-RMS Data Information Required for Production
Task Description: City-provided Statute Data (statutes employee data, code lists) is imported into the
system that will be installed Initially at the City site.
Responsibilities:
intergraph shall
Provide City with InstruCtion on data needed for initial data import
2 Import City-provided data into the system
3 Provide City with training on how to modify the data
4 Provide consultation and support when questions arise regarding data modification.
5 Spot check the City provided data for accuracy
City shall
Provide Intergraph with the required data in soft-copy format.
2 Participate fully In related training
3 Test data thoroughly and make deSired modifications
4 Modify data based on any deficiencies noted by Intergraph personnel
Completion Criteria:
This task IS considered complete when Intergraph has Installed the City-provided Statute Data (statutes,
employee data, code listsl and the City has verified same
City of Corpus Christi - Project Statement of Work
Page 26
Task 22: I/LEADS-RMS Data Conversion
Task Description:
Task Description:
intergraph will convert and Import the Citys existing data from the City's existing RMS system into the
intergraph I!LEADS RMS system
Responsibilities:
intergraph shall
Provide the City a separate Data Conversion and Test plan prior to the start of the data
conversion process
2 Convert and Import Into the Intergraph I/LEADS RMS system the City's existing data from their
eXisting RMS systems. The data is defined as
. Incident !Offense Reports
· Arrest Records
· Case Management
· Master Name Index
City shall
Supply to Intergraph in electronic format (spreadsheet or Access database files) the City's
eXisting RMS data Data types defined above
2 Verify and validate the imported data in the Intergraph I/LEADS RMS system
Completion Criteria:
This task is considered complete after City validation of the imported data
Task 23: Install and Perform Accepting Testing of IILEADS-RMS Interfaces
Task Description:
The Implementation of the Interfaces is based on the Interface Control Documents (lCD's) described
previously. Interfaces will be developed while the core system is being implemented and trained. Although
Intergraph will endeavor to thoroughly document all details in the lCD, it is not unusual for questions to
arise dUring the development process The assigned City point of contact will be available for clarification
and will ensure that third parties provide details and timely responses
Responsibilities:
Intergraph Shall
Design develop, Install, and unit test the I/LEADS-RMS interfaces listed in the Interface Control
Documents portion :)f this document These will be developed per the Interface Control
City of Corpus Christi - Project Statement of Work
Page 27
Documents
2 Certify the interfaces as ready for integration testing.
3 Demonstrate all Inter-system communications between installed Intergraph systems and between
Intergraph and non-Intergraph systems, according to the Acceptance Test Plans and the Interface
Control Documents
4 Provide technical support dUring the Initial Installation and testing cycles. Typically, this support will
be provided remotely However. thiS work may need to be conducted on site at the mutual
agreement of the project managers
5 Review and correct any discrepancies that are identified by the City prior to final system
acceptance and payment
6 Correct software or documentation In a mutually agreed upon manner prior to system cutover.
Minor issues that are mutually deemed to be non-impactive will be logged for future correction.
f Identify any necessary certifications, approvals of the lCD's, and other related issues requiring the
City to provide information at least thirty (30) calendar days prior to scheduled interface work,
::Ity shall
Provide VPN (preferred) or dial-up access to allow remote Installation and testing of custom
interfaces
2 Assume responsibility for any modifications or additions to any existing or non-Intergraph supplied
systems reqUired to enable them to support the interfaces, as defined in the interface control
documents
3 Provide and Install all communications lines and equipment not provided by Intergraph as
dellverables according to the contract documents
4 ProVide all required liaison support with the agencies and vendors required to support the
interfaces
5 Ensure that necessary certifications, approvals of the lCD's. and other related issues are
completed by City at least thirty (30) calendar days prior to scheduled interface work.
6 Ensure that the necessary technical support IS made available for installation, testing, and
demonstration of the interfaces
7 Conduct test procedures and verify all inter-system communications between installed Intergraph
systems and between Intergraph and non-Intergraph systems according to the Acceptance Test
Plans and the Interface Control Documents
8 Identify In writing each discrepancy between subsystem and anCillary system functionality and the
Interface Control Documents within ten (10) business days of problem identification.
9 Work with Intergraph to identify the type of correction needed to ensure that each subsystem and
anCillary system conforms to the Interface Control Documents
Completion Criteria:
This task is considered complete when each I/LEADS RMS interface has been installed and tested. The
operation or availability of the external system or third-party software is necessary for task completion
City of Corpus Christi - Project Statement of Work
Page 28
Task 24: IILEADS-RMS System - Train the Trainer Training
Task Description.
A Train the Trainer program will be developed and scheduled exclusively for the City and then conducted
to thoroughly train City training staff personnel on the use of the I/LEADS RMS subsystem, and City
Technical personnel on the operation and support of the installed subsystem One (1) master set of user
and technical documents plus one (1) hardcopy for each student will be provided for all installed
subsystems The training WII: be provided by Intergraph Training Personnel on a mutually agreed upon
schedule Training will be provided on first Shift, unless prior arrangements have been made in advance,
with eight hours of class time each dav and a one-hour lunch break
Responsibilities:
Intergraph shall
ProVide Train the Trainer training In the follOWing courses
· I/LEADS Train the Trainer (IPST2203)
· I/LEADS Admlnistrator/GUI (IPST2208)
· I/LEADS System Overview Workshop (IPST2209)
· I/LEADS Core Team Orientation (IPST2212)
· I/LEADS Reports (IPST2214)
· I/LEADS Civil Process System Train-the-Trainer (IPST2204)
2 PrOVide machine-readable documents In Microsoft Word 2003 or higher format for each student,
based upon Intergraph's as-bUilt documentation standard at the time of delivery. Documentation
files will not be password protected
3 PrOVide documentation In the form of on-line Help files, providing the user quick and easy access.
This includes application user and administrator documentation Operators can access on-line
Help files both inside an application (while the application is running) and outside an application
(through the Start menu or Microsoft Explorer) Third-party documentation is pass-through from
the manufacturer Delivery of off-the-shelf and generic documentation, such as or Visual FoxPro
will be prOVided before training System administrator and user training manuals are provided as
is appropriate for the type of class being taught
::;ity shall
Designate and assign personnel to receive training in groups not to exceed the class size listed in
the training plan
2 Provide the necessary classrooms facilities, materials, copies of documentation, networks and
lines to data terminals, personal computers and PC operating system software, and related
equipment to support training classes This Includes one full-function workstation per student, one
full-function workstation for the Instructor. an LCD. a prOjection screen, a whiteboard, and
connectivity to the server
3 ProVide suffiCient copies of the documentation supplied by Intergraph to support all students in the
training classes
4 Ensure that appropriate City Training personnel are available to actively participate in the
scheduled training programs and attendees attend scheduled training classes in their entirety.
City of Corpus Christi - Project Statement of Work
Page 29
5 Ensure that City personnel to receive training are proficient in the use of Microsoft Windows
functionality
6 Provide complete and on-going training for all remaining City personnel on a schedule that allows
subsystem cutover and production operation on the schedule as documented in the Project
Schedule
7 Assume responsibility for travel and per diem expenses for City staff for any off-site training
classes selected by the City
Completion Criteria:
This task is considered complete when the I/LEADS training listed above has been completed.
Task 25: I/LEADS-RMS Acceptance Testing
Task Description:
Demonstrate the applicable functions and features of IILEADS RMS functionality as defined in the
Intergraph Acceptance Test Plan, the baseline documentation and the Intergraph RFP response. City staff
will perform functional testing of the IlL EADS subsystem with assistance from Intergraph personnel.
Responsibilities:
i ntergraph shall
Provide a draft RMS Acceptance Test Plan based on the baseline documentation and the
Intergraph RFP response ThiS test plan will be functionally based and will include the commands
Included in City's configuration
2 Review and approve the final Acceptance Test Plan, which should be modified by City to include
Citys unique workflows
3 Certify all applicable software, subsystems, and ancillary systems as ready for functional testing
4 Demonstrate the tailored and configured functions of the Installed subsystem. This is done in the
context of training classes
5 Facilitate the development of workflows via the Data Entry Workflow Workshops.
6 Review any discrepancies In functionality identified by the City
7 Correct software or documentation in a mutually agreed upon manner prior to system cutover.
Minor issues that are mutually deemed to be non-impactive will be logged for future correction.
City shall
Expand the functional testing documentation to Include City-specific workflows.
2 Review and approve the final Acceptance Test Plan
3 Execute the approved Acceptance Test Plan
4 Document each discrepancy of functionality located between tested criteria and Acceptance Test
Plan and provide such documentation to Intergraph for resolution
5 Provide final approval for cutover to live operations
City of Corpus Christi - Project Statement of Work
Page 30
Completion Criteria:
This task IS considered complete when I/LEADS has been demonstrated to operate in accordance with
the Intergraph Acceptance Test Plan the baseline documentation and the Intergraph RFP response.
Task 26: I/LEADS-RMS Cutover Final Preparations
Task Description:
Intergraph and the City will Jointly develop an I/LEADS Cutover Plan, detailing steps necessary to move
from the implementation environment to live operations. The Cutover Plan will assign tasks and
responsibilities for both Intergraph and City personnel during the final month before cutover to ensure that
the move to live operations goes as smoothly as possible This Plan will include such things as City
staffing, moving of equipment into final location, loading software onto all user machines, final database
clean out of test events Issu,ng reporting procedures, and planning the sequence of events for the cutover
day
Responsibilities:
Intergraph shall
Create a draft I/LEADS Cutover Plan
2 Work with City personnel to refine the Cutover Plan
3 Review and approve the final Cutover Plan
4 Manage Intergraph operations per the final Cutover Plan
City shall
Review and comment on the draft I/LEADS Cutover Plan
2 Work With Intergraph personnel to refine the Cutover Plan
3 Review and approve the final Cutover Plan
4 Manage City operations per the final Cutover Plan
Completion Criteria:
This task is considered complete when the City has reviewed and approved the final LEADS RMS Cutover
Plan
Task 27: I/LEADS-RMS Cutover to Production
Task Description:
Once functional and Integration testing are complete, Intergraph will certify the I/LEADS subsystem is
operational and ready for production operation and assist the City In plaCing the subsystem into productive
use. The City can delay the actual cutover of specific modules (ie, Crime Analysis, Case Management)
until other modules have been in use and are being used satisfactorily. A Readiness Review meeting will
be held with members of the Intergraph and City teams The final decision to cut over to live operations is
ultimately a City decision however. both Intergraph and City will review system status and jointly make a
recommendation to move into production Intergraph personnel will assist the City in placing the system
into productive use Intergraph personnel will be on site at least 2 days prior to live operations and will
orovide post-live cut on-site 24/7 support for 5 days during the week of cutover. On-going focused
City of Corpus Christi - Project Statement of Work
Page 31
Helpdesk phone support will follow on site support
The cutover operation will be supported by the Intergraph Project Manager, I/LEADS Implementation Lead
and Training Lead
After live cut over to production operations the 3D-day RMS Performance and Reliability Test period will
begin and the RMS Extended Software Warranty for 12 months begins
Responsibilities:
Intergraph shall
Assist the City staff in placing I/LEADS into a production status
2 Monitor the initial operation of I/LEADS and answer any operational questions raised by the City
3 Provide technical support 24/7 for 5 days during the week of cutover
4 Assist the training staff in utilizing the subsystem and the computer operations staff in supporting
the subsystem
City shall
Place the software into production within 10 calendar days following certification and begin
operational use In consultation with Intergraph and in accordance with the Project Schedule.
Completion Criteria:
This task is considered complete when I/LEADS RMS is placed into production operation.
Task 28: I/LEADS-RMS Performance and Reliability Testing
Task Description:
Verify that the I/LEADS RMS subsystem demonstrates reliable operation in a production environment prior
to the start of the application software warranty period
I/LEADS RMS will demonstrate Critical subsystem availability levels of 99.9% or better for a thirty (30)
calendar day Performance and Reliability Testing period
At the end of thiS test period, if subsystem availability has not met or exceeded this required level, the
Performance and Reliability Testing period Will continue until this level of reliability has been demonstrated
for at least thirty (30) consecutive calendar days
The I/LEADS RMS subsystem Will be considered "down" If there IS a failure of any IILEADS redundant or
fault-tolerant computer hardware or software module, or component that prevents critical event entry,
dispatch or status monitoring functions to operate at a level that allows operation to continue. Functional
problems that do not prevent productive use of the subsystem are not considered downtime. Software
problems of this type are documented by the City on an "action item list" to be fixed during this phase.
Downtime will begin at the time that the designated Intergraph contact person has been notified of the
failure
The subsystem shall not be considered down during any manual or automated fail-over process, or during
operational !n a backup mode
City of Corpus Christi - Project Statement of Work
Page 32
Failures In Individual communication lines. terminals. workstations, PCs, non-Intergraph PC licensed
software. modems. and data communications, as well as problems that involve non-redundant or fault-
tolerant hardware or remote workstation or terminal sites do not constitute downtime. They will be repaired
as expediently as possible, and operations will then continue
I/LEADS RMS Performance and Reliability Testing will not be delayed or interrupted if there are failures in
systems that are not the responsibility of Intergraph (communication lines, external databases, etc.), Also,
the Performance and Reliability Test and subsystem certification will not be delayed if any user-provided
peripheral components encounter a failure or have not been made available for implementation and
testing according to the project schedule Scheduled subsystem unavailability for purposes of software
update, performance tuning file backups and other processes typical In a production environment is not
::onsldered as downtime
in the event that the subsystem is considered to be "down during this test period, one of the following will
JCcu r
~ Subsystem operation Will be suspended The problem IS considered "major" and immediately
diagnosed and corrected. After installation of the appropriate corrections, the test period will
resume logging the time since Intergraph was notified of the failure as downtime
~ Subsystem operation will continue The problem will be logged and then corrected, tested, and
demonstrated during the Performance and Reliability Test penod. In this case, the problem is
documented as a "mlno( system problem and the subsystem is not removed from on-line opera-
tion and is not considered down
No software related subsystem changes. or enhancements shall be made to any subsystem undergoing
subsystem certification unless they are directly related to addreSSing a "major" failure
The Performance and Reliability Testing process can be temporanly suspended upon agreement between
City and Intergraph for scheduled changes software corrections, or upgrades. In this event, the test
oeriod will resume when the subsystem IS again operational. without logging downtime.
During the test period, Intergraph will develop a list of minor" subsystem problems as described above.
This list will be completed and delivered to the City Within five business days following the completion of
the subsystem certification phase. These Items, plus any others that are found as the subsystem moves
'lto full production operation will be addressed and corrected in a timely manner (according to an agreed-
to schedule) dunng this period of operation or as part of the extended warranty period. The resolution of
minor" subsystem problems will not delay the completion of this task. Any further subsystem problem or
nconsistency With the functional requirements will be addressed under the provisions of the warranty.
When Intergraph has corrected and demonstrated all Significant functional and operational errors and
areas of non-compliance that have been Identified on the action item list during the test period, the
ndividual subsystems Will be accepted and made available for continUing productive use. Any additional
problems or areas of non-compliance identified follOWing this Performance and Reliability Testing period,
''lcluding those related to any subsystems or ancillary systems that have not yet been placed in productive
operation Will not prevent subsystem certification and will be addressed as part of the standard software
warranty
Responsibilities:
Intergraph shall
Identify a pOint of contact for logging system interruptions that is available 24/7 during the
Performance and Reliability Testing period
City of Corpus Christi - Project Statement of Work
Page 33
2 Develop and complete a list of minor" subsystem problems for delivery to the City within five
business days following the completion of Performance and Reliability Testing.
3 Certify to the City In wntlng that the RMS subsystem is ready for Performance and Reliability
Testing
4 ASSist the City with the RMS Performance and Reliability Testing as described in the Project Plan.
5 Address and/or correct punch list Items either during this penod or as a part of the Extended
Software Warranty period
City shall
Provide Intergraph with a list of outstanding problems. Issues. documentation, or other information
needed for Performance and Reliability Testing
2 Log system downtime on an "action Item list ..
3 Contact Intergraph personnel In a timely manner In the event of system problems or failures
Completion Criteria:
This task IS considered complete after I/LEADS RMS has demonstrated critical system availability levels
juring the test penod for a thirty (30) day Subsystem Performance and Reliability Test period,
commencing at the I/LEADS Production Cutover
Task 29: I/LEADS-AFR Implementation
Task Description:
Install and configure AFR System
Responsibilities:
intergraph shall
PrOVide I/LEADS AFR client license
2 Intergraph to Install AFR client licenses on up to five (5) MDC's. providing instructions and training
to City on the AFR cltent software installation process
3 Train the City I/LEADS Administrator to configure I/LEADS AFR field reporting client, so that City
can make their desired configuration changes
4 ProVide consultation on deSired Field Reporting changes, advising City as needed on best
methodologies to make changes
5 Train City personnel on the proper Installation and configuration of the IILEADS AFR client
software for maintenance of the mobile computers
City shall
PrOVide the reqUired City-specific configuration data for initial AFR system configuration.
2 Be active partiCipants in the staging process, performing hands-on portions of the staging, under
the guidance of the I/LEADS AFR Implementation Lead.
3 Be available to address and answer questions that arise during the tailoring and configuration of
the AFR subsystem
City of Corpus Christi - Project Statement of Work
Page 34
4 Install the AFR client software on the balance of MDC's after receiving instruction from Intergraph
on the client software installation process
Completion Criteria:
This task ;s considered complete when the I/LEADS AFR baseline application modules have been
,nstalled tested and verified to meet specifications by the City
Task 30: I/LEADS-AFR System - Train the Trainer Training
Task Description:
A. Train the Trainer training program will be developed and scheduled exclusively for the City and then
conducted to thoroughly train City training staff personnel on the use of Automated Field Reporting (AFR)
and City Technical personnel on the operation and support of the installed subsystem. One (1) master set
of user and technical documents plus one (1) hardcopy for each student will be provided for all installed
subsystems The training will be provided by Intergraph Training Personnel.
Responsibilities:
ntergraph shall
Provide I/LEADS Field Reporting (IPST2210) training for City Technical and Training staff
members on a mutually agreed upon schedule Training will be provided on first shift, unless prior
arrangements have been made in advance, With eight hours of class time each day and a one-
hour lunch break
2 Provide machine-readable documents in Microsoft Word 2003 or higher format for each student,
based upon Intergraph's as-built documentation standard at the time of delivery. Documentation
files will not be password protected
3 Provide documentation in the form of on-line Help files, providing the user quick and easy access.
This includes application user and administrator documentation Operators can access on-line
Help files both inside an application (while the application is running) and outside an application
(through the Start menu or Microsoft Explorer). Third-party documentation is pass-through from
the manufacturer Delivery of off-the-shelf and generic documentation, such as or Visual FoxPro
will be provided before training System administrator and user training manuals are provided as
IS appropriate for the type of class being taught
C;lty shall
Designate and assign personnel to receive training In groups not to exceed the class size listed in
the training plan
2 PrOVide the necessary classrooms facilities. materials, copies of documentation, networks and
lines to data terminals, personal computers and PC operating system software, and related
equipment to support training classes This includes one full-function workstation per student, one
full-function workstation for the Instructor. an LCD. a projection screen, a whiteboard, and
connectivity to the server
3 PrOVide suffiCient copies of the documentation supplied by Intergraph to support all students in the
training classes
4 Ensure that appropriate City Training personnel are available to actively participate in the
scheduled training programs and attendees attend scheduled training classes in their entirety.
City of Corpus Christi - Project Statement of Work
Page 35
5
Ensure that City personnel to receive training are proficient in the use of Microsoft Windows
functionality
Provide complete and on-going training for al! remaining City personnel on a schedule that allows
subsystem cutover and production operation on the schedule as documented in the Project
Schedule
Assume responsibility for travel and per diem expenses for City staff for any off-site training
classes selected by the City
6
!
Task 31: I/LEADS-AFR Acceptance Testing
Task Description:
Demonstrate the applicable functions and features of AFR functionality as defined in the Intergraph
Acceptance Test Plan, the baseline documentation and the Intergraph RFP response. City staff will
perform functional testing of the AFR subsystem with assistance from Intergraph personnel.
Responsibilities:
intergraph shall
Provide a draft AFR Acceptance Test Plan based on the baseline documentation and the
Intergraph RFP response This test plan will be functionally based and will include the commands
Included in City'S configuration
2 Review and approve the final Acceptance Test Plan, which should be modified by City to include
Citys unique workflows
3 Certify all applicable software. subsystems. and ancillary systems as ready for functional testing
4 Demonstrate the tailored and configured functions of the Installed subsystem. This is done in the
context of training classes
5 Facilitate the development of workflows via the Data Entry Workflow Workshops
6 Review any discrepancies In functionality identified by the City.
7 Correct software or documentation !n a mutually agreed upon manner prior to system cutover.
Minor issues that are mutually deemed to be non-impactive will be logged for future correction.
City shall
1 Expand the functional testing documentation to Include City-specific workflows.
2 Review and approve the final Acceptance Test Plan
3 Execute the approved Acceptance Test Plan
4 Document each discrepancy of functionality located between tested criteria and Acceptance Test
Plan and provide Such documentation to Intergraph for resolution
5 Provide final approval for cutover to live operations
Completion Criteria:
This task is considered complete when AFR has been demonstrated to operate in accordance with the
Intergraph Acceptance Test Plan. the baseline documentation and the Intergraph RFP response.
City of Corpus Christi - Project Statement of Work
Page 36
Task 32: I/LEADS-AFR Cutover
Task Description:
Once functional and integration testing are complete, Intergraph will certify the AFR subsystem is
operational and ready for production operation and assist the City in placing the subsystem into productive
use. A Readiness Review meeting will be held with members of the Intergraph and City teams. The final
decision to cut over to live AFR operations is ultimately a City decision, however, both Intergraph and City
will review system status and Jointly make a recommendation to move into production. Intergraph
personnel will assist the City In plaCing the AFR system into productive use. Intergraph personnel will be
on site at least 1 days pnor to live operations and will provide post-live cut on-site 24/7 support for 5 days
during the week of cutover On-going focused Helpdesk phone support will follow on site support.
The cutover operation will be supported by the I/LEADS AFR Implementation Lead and Training Lead.
A.fter live cut over to productIOn operations the 3D-day AFR Performance and Reliability Test period will
begin, and the AFR Extended Software Warranty for 12 months begins
Responsibilities:
Intergraph shall
Assist the City staff In plaCing AFR Into a production status
2 Monitor the Initial operation of AFR and answer any operational questions raised by the City.
3 Provide technical support 24/7 for 5 days during the week of cutover
4 Assist the training staff in utiliZing the subsystem and the computer operations staff in supporting
the subsystem
City shall
Place the AFR software into production within 10 calendar days following certification and begin
operational use In consultation with Intergraph and in accordance with the Project Schedule.
Task 33: I/LEADS-AFR Performance and Reliability Testing
Task Description:
'verify that the Automated Field Reporting subsystem demonstrates reliable operation In a production
environment prior to the start of the application software warranty period
AFR will demonstrate critical subsystem availability levels of 99 9% or better for a thirty (30) calendar day
Performance and Performance and Reliability Testing period.
At the end of thiS test period if subsystem availability has not met or exceeded this required level, the
Performance and Reliability Testing period will continue until thiS level of reliability has been demonstrated
for at least thirty (30) consecutive calendar days
The AFR subsystem Will be considered "down" if there IS a failure of any AFR redundant or fault-tolerant
computer hardware or software module. or component that prevents critical event entry, dispatch or status
monitoring functions to operate at a level that allows operation to continue. Functional problems that do
not prevent productive use of the subsystem are not considered downtime. Software problems of this type
are documented by the City on an "action Item list" to be fixed during this phase. Downtime will begin at
the time that the designated Intergraph contact person has been notified of the failure.
City of Corpus Christi - Project Statement of Work
Page 37
The subsystem shall not be considered down during any manual or automated fail-over process, or during
operational in a backup mode
Failures In Individual communication lines. terminals. workstations, PCs, non-Intergraph PC licensed
software modems, and data communications, as well as problems that involve non-redundant or fault-
tolerant hardware or remote workstation or terminal sites do not constitute downtime. They will be repaired
as expediently as possible. and operations will then continue
AFR Performance and Reliability Testing Will not be delayed or interrupted if there are failures in systems
that are not the responsibility of Intergraph (communication lines, external databases, etc.). Also, the
Performance and Reliability Test and subsystem certification will not be delayed if any user-provided
peripheral components encounter a failure or have not been made available for implementation and
testing according to the project schedule Scheduled subsystem unavailability for purposes of software
Jpdate, performance tuning. file backups and other processes typical In a production environment is not
considered as downtime
In the event that the subsystem is considered to be "down dunng this test period, one of the following will
occur
. Subsystem operation Will be suspended The problem IS considered "major" and immediately
diagnosed and corrected After installation of the appropriate corrections, the test period will
resume logging the time since Intergraph was notified of the failure as downtime
. Subsystem operation will continue The problem will be logged and then corrected, tested, and
demonstrated during the Performance and Reliability Test period. In this case, the problem is
documented as a "minor" system problem and the subsystem is not removed from on-line opera-
tion and is not considered down
No software related subsystem changes. or enhancements shall be made to any subsystem undergoing
subsystem certification unless they are directly related to addreSSing a "major" failure.
The Performance and Reliability Testing process can be temporarily suspended upon agreement between
City and Intergraph for scheduled changes software corrections, or upgrades. In this event, the test
period Will resume when the subsystem is again operational. without logging downtime.
During the test penod. Intergraph will develop a list of "minor" subsystem problems as described above.
This list will be completed and delivered to the City within five business days following the completion of
the subsystem certification phase These items, plus any others that are found as the subsystem moves
into full production operation will be addressed and corrected in a timely manner (according to an agreed-
to schedule) during this period of operation or as part of the extended warranty period The resolution of
minor" subsystem problems will not delay the completion of thiS task Any further subsystem problem or
nconsistency With the functional requirements will be addressed under the provisions of the warranty.
When Intergraph has corrected and demonstrated all Significant functional and operational errors and
areas of non-compliance that have been Identified on the action item list during the test period, the
ndivldual subsystems Will be accepted and made available for continuing productive use. Any additional
oroblems or areas of non-compliance identified follOWing thiS Performance and Reliability Testing period,
ncluding those related to any subsystems or ancillary systems that have not yet been placed in productive
operation will not prevent SUbsystem certification and will be addressed as part of the standard software
warranty
City of Corpus Christi - Project Statement of Work
Page 38
Responsibilities:
intergraph shall
Identify a pOint of contact for logging system Interruptions that is available 24/7 during the
Performance and Reliability Testing period
2 Develop and complete a list of 'minor" subsystem problems for delivery to the City within five
business days following the completion of Performance and Reliability Testing.
3 Certify to the City In writing that the subsystem is ready for Performance and Reliability Testing.
4 Assist the City with Performance and Reliability Testing as descnbed in the Project Plan.
5 Address and/or correct punch list Items either during this period or as a part of the Extended
Software Warranty period
City shall
Provide Intergraph With a list of outstanding problems, Issues, documentation, or other information
needed for Performance and Reliability Testing
2 Log system downtime on an action Item list"
3 Contact Intergraph personnel In a timely manner In the event of system problems or failures.
Completion Criteria:
ihls task IS considered complete after AFR has demonstrated critical system availability levels during the
30) day Subsystem Performance and Reliability Test period, commencing at the AFR Production
Cutover
Task 34: I/LEADS-JMS Software Installation
Task Description:
At the IILEADS JMS portion of the project kiCkoff, requirements will be provided to the City regarding data
that must be gathered and provided to Intergraph in advance of system staging This data includes such
things as
~ Configuration for system code-listed values (drop downs In the GUI)
~ Employee Information
~ Celi locations
~ Jail questionnaires
~ Jail faCility codes
~ Commissary tables (if needed!
City will be proVided With a format In which to prOVide the information at least 90 days before such
information IS due to Intergraph ThiS data IS required to be received by Intergraph at least one month prior
to system staging Intergraph will import the provided data Into the system as part of the initial staging.
All applicable I/LEADS JMS application software, as well as equipment vendor's operating system
software necessary for this phase of the project to be completed will be loaded on the City's server
equipment Oracle Database and any other special database setup, will take place as part of this task.
City of Corpus Christi - Project Statement of Work
Page 39
As a part of the system staging, Intergraph will present informal (whiteboard) training to the City personnel,
"",ho will participate in the system staging. Following this basic system introduction, City personnel will
actually perform much of the hands-on staging of the database and application software, under the
continuous direction and gUidance of the Intergraph RMS Implementation Lead. This begins the training
Drocess for the City I/LEADS JMS System Administrator
Responsibilities:
Intergraph shall
Provide requirements for initial configuration data gathering by the City.
2 Provide I/LEADS JMS client license per contract pricing detail summary, Exhibit A
3 Install the JMS client software on up to five (5) of the JMS client workstations, providing
instructions and training to City on the RMS client software installation process.
4
"-
oJ
Train the City I/LEADS JMS Administrator to configure I/LEADS JMS so that City can make their
deSired configuration changes
Direct City personnel in installing licensed I/LEADS JMS software within this configuration.
Import the provided City-specific JMS data
Test the initial operation of the baseline I/LEADS JMS subsystem
6
City shall
Provide the required City-specific configuration data for initial system configuration.
2 Install the JMS client software on the balance of JMS workstations after receiving instruction from
Intergraph on the client software installation process
3 Be active participants in the staging process, performing hands-on portions of the staging, under
the guidance of the I/LEADS JMS Implementation Lead
4 Be available to address and answer questions that arise during the tailoring and configuration of
the JMS subsystem
Completion Criteria:
This task IS considered complete when the I/LEADS JMS baseline application modules have been
nstalled. tested and verified to meet specifications by the City
Task 35: I/LEADS-JMS Acceptance Testing
Task Description:
Demonstrate the applicable functions and features of I/LEADS JMS functionality as defined in the
Intergraph Acceptance Test Plan, the baseline documentation and the Intergraph RFP response. City staff
Will perform functional testing of the I/LEADS JMS subsystem with assistance from Intergraph personnel.
Responsibilities:
Intergraph shall
Provide a draft Acceptance Test Plan based on the baseline documentation and the Intergraph
RFP response This test plan will be functionally based and will include the commands included in
City s configuration
City of Corpus Christi - Project Statement of Work
Page 40
2 Review and approve the final Acceptance Test Plan, which should be modified by City to include
City s unique workflows
3 Certify all applicable software, subsystems, and ancillary systems as ready for functional testing,
4 Demonstrate the tailored and configured functions of the Installed subsystem, This is done in the
context of training classes
5 FaCIlitate the development of workflows via the Data Entry Workflow Workshops
6 Review any discrepancies In functionality identified by the City
7 Correct software or documentation In a mutually agreed upon manner prior to system cutover.
Minor issues that are mutually deemed to be non-impactive will be logged for future correction,
C:lty shall
Expand the functional testing documentation to include City-specific workflows,
2 Review and approve the final Acceptance Test Plan
3 Execute the approved Acceptance Test Plan
4 Document each discrepancy of functionality located between tested criteria and Acceptance Test
Plan and provide such documentation to Intergraph for resolution
5 ProVide final approval for cutover to live operations
Completion Criteria:
This task is considered complete when I/LEADS JMS has been demonstrated to operate in accordance
Nlth the Intergraph Acceptance Test Plan the baseline documentation and the Intergraph RFP response,
Task 36: I/LEADS-JMS System - Train the Trainer Training
Task Description:
.6" Train the Trainer training program will be developed and scheduled exclusively for the City and then
conducted to thoroughly train City training staff personnel on the use of the I/LEADS JMS subsystem and
City Technical personnel on the operation and support of the installed JMS subsystem. One (1) master set
of user and technical documents plus one (1) hardcopy for each student will be provided for all installed
subsystems The training will be provided by Intergraph Training Personnel
Responsibilities:
intergraph shall
ProVide IILEADS JMS Core Team Orientation (IPST2213) and I/LEADS JMS Train the Trainer
(IPST2205) training for City Technical and Training staff members on a mutually agreed upon
schedule Training will be provided on first shift, unless prior arrangements have been made in
advance. with eight hours of class time each day and a one-hour lunch break.
2 PrOVide machine-readable documents In Microsoft Word 2003 or higher format for each student,
based upon Intergraph's as-built documentation standard at the time of delivery. Documentation
files will not be password protected
3 PrOVide documentation in the form of on-line Help files, providing the user quick and easy access.
ThiS Includes application user and administrator documentation Operators can access on-line
Help files both Inside an application (while the application is running) and outside an application
City of Corpus Christi - Project Statement of Work
Page 41
(through the Start menu or Microsoft Explorer). Third-party documentation is pass-through from
the manufacturer Delivery of off-the-shelf and generic documentation, such as or Visual FoxPro
will be provided before training System administrator and user training manuals are provided as
is appropnate for the type of class being taught
;':::Ity shall
Designate and assign personnel to receive training In groups not to exceed the class size listed in
the training plan
2 Provide the necessary classrooms facilities, materials, copies of documentation, networks and
lines to data terminals. personal computers and PC operating system software, and related
equipment to support training classes This Includes one full-function workstation per student, one
full-function workstation for the Instructor an LCD. a projection screen, a whiteboard, and
connectivity to the server
3 PrOVide suffiCient copies of the documentation supplied by Intergraph to support all students in the
training classes
4 Ensure that appropriate City Training personnel are available to actively participate in the
scheduled training programs and attendees attend scheduled training classes in their entirety.
5 Ensure that City personnel to receive training are proficient In the use of Microsoft Windows
fu netlonality
6 PrOVide complete and on-going training for all remaining City personnel on a schedule that allows
subsystem cutover and production operation on the schedule as documented in the Project
Schedule
7 Assume responSibility for travel and per diem expenses for City staff for any off-site training
classes selected by the City
Completion Criteria:
rhis task is considered complete when the I/LEADS JMS training listed above has been completed.
Task 37: I/LEADS-JMS Cutover Final Preparations
Task Description:
Intergraph and the City will JOintly develop an I/LEADS JMS Cutover Plan, detailing steps necessary to
move from the implementation environment to live operations The Cutover Plan will assign tasks and
responsibilities for both Intergraph and City personnel during the final month before cutover to ensure that
the move to live operations goes as smoothly as possible This Plan will include such things as City
staffing, moving of equipment into final location, loading software onto all user machines, final database
clean out of test events. Issuing reporting procedures, and planning the sequence of events for the cutover
day.
Responsibilities:
Intergraph shall
1 Create a draft I/LEADS JMS Cutover Plan
2 Work with City personnel to refine the Cutover Plan
3 ReView and approve the final Cutover Plan
4 Manage Intergraph operations per the final Cutover Plan
City of Corpus Christi - Project Statement of Work
Page 42
City shall
Review and comment on the draft I/LEADS JMS Cutover Plan
2 Work with Intergraph personnel to refine the Cutover Plan
3 Review and approve the final Cutover Plan
4 Manage City operations per the final Cutover Plan
Completion Criteria:
This task is considered complete when the City has reviewed and approved the final LEADS JMS Cutover
Plan
Task 38: IILEADS-JMS Cutover to Production
Task Description:
Once functional and integration testing are complete, Intergraph will certify the I/LEADS subsystem is
operational and ready for production operation and assist the City in placing the subsystem into productive
else. A Readiness Review meeting will be held with members of the Intergraph and City teams. The final
decision to cut over to live operations is ultimately a City decision; however, both Intergraph and City will
review system status and jOintly make a recommendation to move into production. Intergraph personnel
will assist the City in placing the JMS system into productive use Intergraph personnel will be on site at
least 2 days prior to live operations and will provide post-live cut on-site 24/7 support for 5 days during the
week of JMS cutover On-going focused Helpdesk phone support will follow on site support.
The cutover operation will be supported by the Intergraph Project Manager, I/LEADS Implementation Lead
and Training Lead
After live cut over to production operations the 30-day JMS Performance and Reliability Test period will
begin and the JMS Extended Software Warranty for 12 months begins.
Responsibilities:
ntergraph shall
ASSist the City staff in plaCing I/LEADS JMS Into a production status
2 Monitor the Initial operation of I/LEADS JMS and answer any operational questions raised by the
City
3 Provide technical support 24/7 for 5 days during the week of cutover
4 ASSist the training staff in utilizing the subsystem and the computer operations staff in supporting
the subsystem
City shali
Place the software IOta production within 10 calendar days following certification and begin
operational use In consultation with Intergraph and in accordance with the Project Schedule.
Completion Criteria:
This task IS considered complete when I/LEADS JMS is placed into production operation.
City of Corpus Christi - Project Statement of Work
Page 43
Task 39: I/LEADS-JMS Performance and Reliability Testing
Task Description:
Verify that the I/LEADS JMS subsystem demonstrates reliable operation in a production environment prior
to the start of the application software warranty period
ilLEADS JMS will demonstrate critical subsystem availability levels of 999% or better for a thirty (30)
calendar day Performance and Reliability Testing period
At the end of this test period, if subsystem availability has not met or exceeded this required level, the
Performance and Reliability Testing period will continue until this level of reliability has been demonstrated
for at least thirty (30) consecutive calendar days
The I/LEADS JMS subsystem will be considered "down" If there is a failure of any I/LEADS JMS
redundant or fault-tolerant computer hardware or software module, or component that prevents critical
event entry dispatch or status monitoring functions to operate at a level that allows operation to continue,
Functional problems that do not prevent productive use of the JMS subsystem are not considered
downtime, Software problems of this type are documented by the City on an "action item list" to be fixed
juring thiS phase Downtime will begin at the time that the designated Intergraph contact person has been
notified of the failure
fhe subsystem shall not be considered down during any manual or automated fail-over process, or during
Gperational in a backup mode
Failures In individual communication lines, terminals, workstations, PCs, non-Intergraph PC licensed
software, modems, and data communications, as well as problems that involve non-redundant or fault-
tolerant hardware or remote workstation or terminal sites do not constitute downtime, They will be repaired
as expediently as pOSSible, and operations Will then continue
ilLEADS JMS Performance and Reliability Testing will not be delayed or interrupted if there are failures in
systems that are not the responsibility of Intergraph (communication lines, external databases, etc,), Also,
the Performance and Reliability Test and subsystem certification will not be delayed if any user-provided
peripheral components encounter a failure or have not been made available for implementation and
testing according to the project schedule Scheduled subsystem unavailability for purposes of software
update, performance tuning, file backups and other processes typical In a production environment is not
:~onsldered as downtime
n the event that the subsystem is conSidered to be 'down dUring thiS test period, one of the following will
)Ccu r
~ Subsystem operation will be suspended The problem is conSidered "major" and immediately
diagnosed and corrected After installation of the appropriate corrections, the test period will
resume, logging the time since Intergraph was notified of the failure as downtime
~ Subsystem operation will continue, The problem will be logged and then corrected, tested, and
demonstrated during the Performance and Reliability Test period, In this case, the problem is
documented as a "minor" system problem, and the subsystem IS not removed from on-line opera-
tion and is not considered down
No software, related subsystem changes, or enhancements shall be made to any subsystem undergoing
subsystem certification unless they are directly related to addressing a "major" failure,
The JMS Performance and Reliability Testing process can be temporarily suspended upon agreement
between City and Intergraph for scheduled changes, software corrections, or upgrades. In this event, the
City of Corpus Christi - Project Statement of Work
Page 44
test penod will resume when the subsystem IS again operational, without logging downtime.
During the test penod, Intergraph will develop a list of "minor" subsystem problems as described above.
This list will be completed and delivered to the City within five business days following the completion of
the subsystem certification phase These items, plus any others that are found as the subsystem moves
,nto full production operation will be addressed and corrected in a timely manner (according to an agreed-
to schedule) during this penod of operation or as part of the extended warranty period The resolution of
minor" subsystem problems will not delay the completion of this task. Any further subsystem problem or
nconsistency with the functional reqUirements will be addressed under the provisions of the warranty.
When Intergraph has corrected and demonstrated all significant functional and operational errors and
areas of non-compliance that have been Identified on the action item list during the test period, the
individual subsystems Will be accepted and made available for continuing productive use. Any additional
problems or areas of non-compliance Identified following this Performance and Reliability Testing period,
including those related to any subsystems or ancillary systems that have not yet been placed in productive
Dperation will not prevent subsystem certification and will be addressed as part of the standard software
warranty
Responsibilities:
I ntergraph shall
Identify a pOint of contact for logging system interruptions that IS available 24/7 during the JMS
Performance and Reliability Testing period
2 Develop and complete a list of 'minor" JMS subsystem problems for delivery to the City within five
business days follOWing the completion of Performance and Reliability Testing.
3 Certify to the City In wnting that the subsystem IS ready for JMS Performance and Reliability
Testing
4 Assist the City with JMS Performance and Reliability Testing as described in the Project Plan.
5 Address and/or correct punch list Items either dunng thiS penod or as a part of the Extended
Software Warranty penod
::Ity shall
PrOVide Intergraph with a list of outstanding problems, Issues, documentation, or other information
needed for Performance and Reliability Testing.
2 Log system downtime on an action Item list'
3 Contact Intergraph personnel In a timely manner In the event of system problems or failures.
Completion Criteria:
This task IS considered complete after I/LEADS JMS has demonstrated critical system availability levels
for a thirty (30) day JMS Subsystem Performance and Reliability Test period, commencing at the I/LEADS
JMS Production Cutover
Task 40: IICAD Reassessment
Task Description:
The IICAD Reassessment session is deSigned to bring the users and managers of the I/CAD system
together with Intergraph system consultants experienced in center operations The consultant will conduct
City of Corpus Christi - Project Statement of Work
Page 45
structured group sessions to clanfy the onginal goals of the project, and will then review present
operations on-site and assess how goals and objectives are being met. This information is the core of
additional group sessions to determine if progress is satisfactory or if adjustments must be made to goals
and priorities Recommendations will be made as to any configuration changes that should be made to
accomplish the goals and objectives, or other requests as they arise These recommended system
modifications may be accomplished during the week. depending on the scope and complexity of each
item Further implementatior work may be required to perform more complicated recommendations, and
these wll! be part of follow-or work provided during subsequent viSits or contact.
fhis 4 day CAD Reassessment (IPST20061 visit will be scheduled for two to three months after cutover to
I!ve operations
Responsibilities:
Intergraph shall
Rev!ew of eXisting utilities
2 Instruction to City on any new utilities
3 Review use of existing CAD functionality to optimize the operation of the dispatch center
4 Review use of eXisting CAD GUI, Command line, or other configuration changes
5 Customized training or retraining of specific areas
City shall
Support the CAD Reassessment activities and reViews, with the CAD System Administrator, Key
!/CAD Users Training, and Management personnel in attendance
2 Provide Intergraph with a list of outstanding configuration problems, or configuration changes
deSired
Completion Criteria:
This task is considered complete after the CAD Reassessment visit by Intergraph personnel
Task 41: I/Mobile Reassessment
Task Description:
The I/Mobile Reassessment session IS deSigned to bring the users and managers of the I/Mobile system
together with Intergraph system consultants experienced in field Mobile operations. The consultant will
conduct structured group sessions to clarify the original goals of the project, and will then review present
operations on-site and assess how goals and objectives are being met. This information is the core of
additional group sessions to determine if progress is satisfactory or if adjustments must be made to goals
and prionties Recommendations will be made as to any configuration changes that should be made to
accomplish the goals and objectives, or other requests as they arise These recommended system
modifications may be accomplished during the week, depending on the scope and complexity of each
item Further implementation work may be required to perform more complicated recommendations, and
these will be part of follow-on work provided during subsequent visits or contact.
This 4 day I/Moblle Reassessment t1PST2007) visit will be scheduled for two to three months after
I/Mobile cutover to live operations
City of Corpus Christi - Project Statement of Work
Page 46
Responsibilities:
!ntergraph shall
1 Review of eXisting utilities
2 Instruction to City on any new utilities
3 Review use of eXisting lIMo bile GUI and other configuration changes
4 Customized training or retraining of specific areas
City shall
Support the I/Mobile Reassessment activities and reviews, with the IIMobile Administrator, Key
I/Mobile Users Training, and Management personnel in attendance
2 PrOVide Intergraph with a list of outstanding I/Mobile configuration problems, or configuration
changes desired
Completion Criteria:
This task is considered complete after the I/Mobile Reassessment visit by Intergraph personnel
Task 42: I/LEADS Reassessment
Task Description:
The I/LEADS Reassessment session is designed to bring the users and managers of the I/LEADS RMS
system together with Intergraph system consultants experienced in center operations. The consultant will
conduct structured group sessions to clarify the original goals of the project, and will then review present
operations on-site and assess how goals and objectives are being met. This information is the core of
additional group sessions to determine if progress is satisfactory or if adjustments must be made to goals
and priorities Recommendations will be made as to any configuration changes that should be made to
accomplish the goals and objectives, or other requests as they arise. These recommended system
modifications may be accomplished dUring the week, depending on the scope and complexity of each
item Further implementation work may be required to perform more complicated recommendations, and
these will be part of follow-on work provided during subsequent visits or contact.
This 4 day I/LEADS Reassessment (I PST2217) VISit will be scheduled for two to three months after
cutover to live operations
Responsibilities:
intergraph shall
1 ReView of eXisting utilities
2 Instruction to City on any new utilities
3 ReView use of eXisting CAD functionality to optimize the operation of the dispatch center
4 ReView use of eXisting CAD GUI, Command line, or other configuration changes
5 Customized training or retraining of specific areas
City of Corpus Christi - Project Statement of Work
Page 47
:Ity shall
Support the CAD Reassessment activities and reviews, with the CAD System Administrator, Key
IICAD Users. Training, and Management personnel in attendance
2 Provide Intergraph with a list of outstanding configuration problems, or configuration changes
desired
Completion Criteria:
This task is considered complete after the CAD Reassessment visit by Intergraph personnel
Task 43: Final System Acceptance Testing
Task Description:
A.t an appropriate time determined in accordance with Exhibit E, Statement of Work, and as part of its
project management services. Intergraph shall provide written certification to the City Director of Municipal
Information Systems that it has delivered all items required under the Agreement. At this time, Intergraph
shall also certify that It has completed all services required under the Agreement other than those services
which entail continuing obligations of Intergraph (for example, maintenance services, and warranty
obligations) At thiS time. Intergraph shall further certify that it has devised and performed functionality
tests of ItS chOOSing which are sufficient to allow Intergraph to verify that the System performs the
functions as required under this Agreement Upon request, Intergraph shall provide to the City documents
jescribing the nature and results of such Intergraph functionality testing of the System.
A.s part of its project management services, Intergraph shall then assist the City in performing an inventory
during which the City shall confirm these certifications Once the City has confirmed these certifications,
the Director of MuniCipal Systems shall designate In writing the starting date for a thirty (30) day final
system acceptance testing period (the 'Final Acceptance Testing Period)
if dunng the Final Acceptance Testing Penod the System is not performing in a manner which indicates
that it will pass Final Acceptance Testing critena defined below, then the City may
a continue the Final Acceptance testing Penod and evaluate the System performance at the
end of that period or
b terminate the Final Acceptance testing Penod Thereafter, the City has the option of
starting one or more subsequent thirty (30)-day Final Acceptance testing Periods. If the
SYSTEM performs the functionality tests and meets the performance criteria in
Attachment A-4 of the Statement of Work, Exhibit E, then the SYSTEM shall be deemed
to have passed Final Acceptance Testing
n the event the Final Acceptance Testing Penod is continued or terminated because of a system
performance defiCiency, then the City may require Intergraph to correct the performance deficiency at
intergraph's expense either before or after the Final Acceptance Period concludes. The City may require
intergraph to procure promptly additional or substitute hardware. software. interfaces or other services
which are necessary to render the System operational to the full extent contemplated under the
Agreement. RFP Amendment and RFP The City may but need not, designate the additional or
substitute items or services to be proVided
Intergraph's Fitness for Particular Purposes Warranty (as defined In the Agreement) shall continue for one
1) year after each subsystem Cutover
City of Corpus Christi - Project Statement of Work
Page 48
During the Final Acceptance Testing Penod, the System will be evaluated by the City to determine
whether the System meets he following performance critena
SYSTEM must provide a minimum of 99.99% up time or better for the CAD I Mobile subsystems, and
999% up time or better for the RMS, JMS, AFR subsystem, with no single point of failure;
Should the SYSTEM meet the performance criteria In Attachment A-4 of the Statement of Work, Exhibit E,
then the SYSTEM shall be deemed to have passed Final System Acceptance Testing. The City's Director
of Municipal Information Systems shall certify the date In writing to Intergraph ("Final Acceptance Date")
Task 44: Project Closure
Task Description.
This task involves the Intergraph and City project managers agreeing that all items purchased under the
Contract have been delivered as proposed by Intergraph. At this point, all tasks are completed, major
Issues identified in use of the system in production have been corrected, all payment milestones have
been met, and City has made the final milestone payment
Responsibilities:
Intergraph shall
Review with the City Project Manager the overall state of the project This review will verify that all
tasks have been completed as committed to in the Contract, all products have been delivered and
are operational, major production issues have been resolved, and final payment milestone invoice
has been received by City
2 Upon receipt of the final payment from City, the Intergraph Project Manager will then close the
flies on the project and ensure that all project paperwork has been sent to Intergraph Contracts for
final filing
City shall
Verify that all products and services contracted for have been delivered and will ensure the
payment of any and all outstanding project payment milestones At this point, City will ensure they
follow the Intergraph Software Maintenance Agreement for reporting any software issues
discovered plus the filing of any software changes that might be desired in future releases of
Intergraph-provided software
Completion Criteria:
ThiS task IS considered complete upon verification by the Intergraph and City project managers that all
Items purchased under the Contract have been delivered At thiS point all project tasks are completed,
major issues identified In use of the system In production have been corrected, all payment milestones
have been met and City has made the final milestone payment
City of Corpus Christi - Project Statement of Work
Page 49
Attachment A-1 - System Reliability Test Criteria
Attachment A-2 - Training Plan
Attachment A-3 - Interface Control Documents
Attachment A-4 - System Performance Test Criteria
City of Corpus Christi - Project Statement of Work
Page 50
INTERGRAPH
Attachment A-1
System Reliability Test Criteria
Upon cutover to production each sub system will enter a thirty (30) day Performance and Reliability
Testing by which the system will perform in a live environment and the Extended Warranty period will
begin At the successful completion of this thirty (30) day Performance and Reliability Testing period, the
sub system will be deemed accepted and payment will be made as outlined in section 13.0 of the
Agreement Successful completion of the thirty (30) day Performance and Reliability Testing period will be
achieved thirty (30) days from Cutover based on the stipulations outlined below. Final Acceptance of the
System will not be unreasonably withheld for errors noted below as P3 and P4
Error Level 1 (P1) - Critical system errors which are defined as, Loss of Data, Corruption of Data, or
Loss of Productive Use of the System In the event thiS type of error occurs, the City will immediately
notify Intergraph and the thirty (30) day Performance and Reliability period will be cancelled.
Intergraph personnel shall promptly resolve the problem at no additional cost to City and a new thirty
(30) day Performance and Reliability period will begin Once the system operates for 30 consecutive
days Without an Error Level 1. the thirty (30) day Performance and Reliability test will be completed.
Loss of Productive use of the System IS defined as when basic functionality is lost. Examples of this
are a CAD calltaker cannot enter or process a call, a CAD dispatcher can't dispatch a unit or units to
an event an RMS user cannot enter or save an RMS accident report, or an interface (such as ANI-
All 91 ~ or NCIC query capability) IS non-operational
Error Level 2 (P2)- Critical errors which are defined as the primary purpose of the Intergraph
Application Software (or Module) is compromised productive use of the System is significantly
impacted, or a procedural workaround IS not immediately and readily available. In the event this type
of error occurs, the City will immediately notify Intergraph and the thirty (30) day Performance and
Reliability period will be cancelled Intergraph personnel shall promptly resolve the problem at no
additional cost to City, and a new thirty (30) day Performance and Reliability period will begin. Once
the system operates for thirty (30\ consecutive calendar days without an Error Level 2, the thirty (30)
day Performance and Reliability test Will be completed
Error Level 3 (P3) - Non-critical errors which are defined as Incomplete operation of system where a
procedural workaround is readily and immediately available at no additional cost to City, and
productive use of the system is not significantly impacted. In the event this type of error occurs, the
City Will immediately notify Intergraph but the thirty (30) day Performance and Reliability period will
continue If possible Intergraph shall resolve the problem dUring the thirty (30) day Performance and
Reliability period but If necessary resolve In a future bug fixes release of the product.
Error Level 4 (P4) - Cosmetic errors which are defined as configuration issues that can be corrected
by the City, data Integrity Issues that must be addressed by the City helpfile documentation errors, or
enhancements that can be made in the future to the presently installed System.
if during the thirty (30) day Performance and Reliability period, the system is deemed non-operational by
the City due to P1 or P2 errors, the Extended Warranty period will cease The City may choose to stop
Jse or use whatever operational portion that may be available The Extended Warranty period will restart
Jpon the resolution of the P1 or P2 error
Corpus Christi, Texas SOW
Exhibit E: Attachment A-1 Reliability Test Criteria
Page 1 of 1
INTERGRAPH
Attachment A-2
Training Plan
Each Intergraph project Includes the training necessary to ensure that personnel operating the Intergraph
software and systems have a full understanding and working knowledge of those respective systems. In
turn, this also ensures success for the daily operation within a communications center emergency
agency's office To accomplish this goal. both informal and formal training courses are provided to the
appropriate agency personnel
Course durations are listed In days assuming an eight hour day
System Preparation Training
Before the Initial hardware Installation when training typically begins, the Intergraph personnel will begin
the education and configuration process with agency personnel by conducting introductory workshops.
These workshops are structured to begin the data and information gathering process with the intent of
expediting the installation process In an apprenticeship approach, the City's System Administrator(s) and
Dther key personnel will be ,ntroduced to system data requirements as well as data management and
configuration tools and will learn the steps necessary to organize and gather the data needed for the
I/CAD system ThiS data Will, In turn, be used to setup and maintain all applications
Operations Training
Operations training Includes courses that teach CAD and RMS/JMS users in the proper use of a particular
application Two options are available for this training Train-the-Trainer approach or the more traditional
Train-the-User approach These training programs are conducted at a mutually agreed upon location and
facility. If the hardware has been installed on-Site, and the necessary City data prepared in the system, the
,Jsual approach IS to teach these courses at the City site
The City has chosen Train the User approach for CAD Calltaking / Dispatching / Supervisor training. All
other operations training will be Traln-the-Tralner approach
Usually, the class size should not exceed a total of 12 persons Each student should be allocated one
workstation for the duration of the class If thiS specification is not adequate for your site, please consult
With your Project Manager and Trainer before the class begins
. Traln-the-Tralner
The Traln-the- Trainer approach IS the most logical training solution for most large public safety
projects This method seeks to train the most computer-literate and supervisor-level employees
who learn all functions of each IPS application as well as new techniques for the best way to
teach user-level employees
HaVing completed the Traln-the-Tralner program and armed with a full understanding and
knowledge of the system. the City's trainers will then have the ability to provide their own agency-
specific training, which may Include some policy or procedural changes in addition to application
functionality Due to the vast functionality of the system, there may be some commands or
functions of the application that may not be of benefit to the City's operation. The Train-the-Trainer
approach permits the City's Core Team, System Administrator(s) and Trainers to learn the full
capabilities of the respective systems and determine what commands and/or functions within the
system will be utilized as part of their operation
Corpus Christi, Texas SOW
Exhibit F: Attachment 1\-2 Training Plan
Page 1 of 32
I NTERGRAPH
lA soft copy of Intergraph user documentation will be provided to the City's trainers, from which
thev are allowed to modify and customize as they see fit to meet their own training needs.
. Traln-the-User
TO ensure full understanding of the system as a whole, many customers may choose to have all
users go through full end-user training (Train-the-User) provided by Intergraph training personnel,
rather than by City-designated trainers
The CAD user training program designed for Train-the-User training, as performed by Intergraph
Instructors includes I/CAD Core Essentials classes (Calltaking, Dispatching, Supervisor), which
cover all commands and functions for essential operations in I/CAD. This 5-day program is
designed to provide ,nstruction in the basic and essential functions that every operator should
know before cutting over to live operations with the Intergraph IICAD system. Focus is given to
those commands and workflows that are used most frequently in the Communications Center.
System Administration Training
Several System Administrator-level courses are offered to provide the necessary training to persons who
will be responsible for system configuration and maintenance Operating system-level courses are
provided to ensure the low-level knowledge needed to support and maintain the system configuration.
There are also courses designed to teach the use of available configuration tools and techniques, as well
as a site-specific administration session designed around the City's configuration
::;Iass size for these often highly technical sessions will usually not exceed six persons, unless prior
arrangements are made with the instructor It is preferred that each student be allocated one workstation
for the duration of the class however. the maximum number of trainees per workstation should not
exceed two
Corpus Christi, Texas SOW
Exhibit f: Attachment A-2 Training Plan
Page 2 of 32
INTERGRAPH
Training Course Summary
~ __+-I/CAD Project and Workflow Analysis (IPST1 000)
~._Li/CAD Data Workshop l!?STJ 001)
_~._+I/CAD Deployment Plann~ and Configuration (IPST1 003)
_4 i I/CAD Workflow and Configuration Workshop (IPST1004)
~~ i I/CAD Calltaking Essentials (IPST2003) ______
l_~_LI/CAD Dispatching Essentials (IPST20~___
f_7__t-I/CAD Supervisor (IPST20051__ ____ .... ____.
~-~--.+-I/CAD Reassessment (IPST2006) '.'___
~_.j..!/MObile Reassessment (IPST2007l____
~..2.9_j..I/CAD Database Schema and Reports Overview (IPST2009
l-~ !/CAD Trainer Consulting (IPST2010)
~..2.2. i I/MARS Configuration and Administration (IPST2102)
13 : I/Mobile User Training (IPST2501)
. I
i 14-i-I/LEADS Traln-the-Tralner (IF'ST2203)
i-..2.~ i I/LEADS Jail Management System Train-the- Trainer IPST2205
I .
I 16 i I/LEADS Administrator/GUI (IPST2208)____
l~_+-l/LEADS System Overview Workshop (IPST2209)
~~_~I/LEADS Field Reporting (AFR) (IPST2210) ____.__
I 19 i/LEADS Data Analysis Workshop (IPST2211~______
,..~ I/LEADS RMS Core Team Orientation (IPST2212)
21 I I/LEADS JMS Core Team Orientation (IPST2213)
. 22-UJLEADS Reports (IPST2214
~ 23 _.UPS I/NetViewer - NetDispatcher TraJn~ST2401)
~ 24-+-I/Mobile Workflow and Configuration Worksho IPST2502
L~-+_I!CAD System Administrator I (IPST31Q1L.
I 26 i i/CAD CADTools User (IPST3103)
I
. 27 i I/CAD Map Maintenance (IPST3104)_
. 28.+YCAD System Maintenance ( IPST31 OlL.____
29 J Support for Cutover to Live I/eAD Operations (IPST5003)
I 1
----~
. 1
1
1
7
7
3 I
1
1 1
1
1
1
3
1
1
1
1
1
1
1
1
1
5
1
1
1
1
1
1
Open 4
12 4
12 3
Open 4
12 2
12 2
12 1
Open 4
Open 4
6 3
12 3
12 2
12 1
12 4
12 2
12 4
12 5
12 2
12 1
12 4
12 2
12 3
12
Open 3
6 4
6 4
6 3
6 4
N/A 5
Corpus Christi, Texas SOW
Exhibit E: Attachment A-2 Trainin~ Plan
Page 3 of 32
INTERGRAPH
1 ~ IICAD Project and Workflow Analysis (IPST1000)
IfcfPtrojectand Workflow Inalysis (IP8T1000)
The Project and Workflow AnalysIs session provides a forum for IPS personnel to obtain information
needed to begin the Implementation of the City's CAD system. This information includes details of the
City'S current operations and workflow, to Identify initial system configuration settings and target areas of
concentration for future training Interfaces are a significant part of any CAD implementation and details
needed for the successful and timely configuration concerning a City's specific Interface needs are also
gathered dUring this session All these aspects are crucial to ensure a progressive and successful result to
what is essentially change management"
Also key to the Implementation IS efficient and thorough data gathering and definition, therefore, another
'mportant task accomplished dUring this week IS to provide guidance to the City's implementation team in
the tasks necessary to design define, and gather the data necessary for the effective and efficient building
of the I/CAD database and map Critical data components that must be supplied by the City are introduced
and discussed so that the impending data collection process occurs with ease and the necessary data is
ready for input during the CAD Data workshop. Managerial, technical support, and operations personnel
should all be partiCipants In thiS seminar to ensure that all essential input IS received for successful system
jefinitlon
Mapr Topics
c~ Project Team Introductions
c: Workflow/Resource Allocation and Information Exchange
c: Overview of Project Process
c~ City Workflow Discussion
c: interface DiSCUSSion
c:: System Setup and Training Environment Overview
c) Introduction to Required CAD Data
c:; Introduction to Map Data and Functionality
P""'isites
c:; Management. deciSion making, or data collection/data entry position
Melt. Conducted on-site by IPS personnel
Tat't (JIassifieations System Administrator, Mapping Support, Database Support, Senior User
and/or Supervisor, Training and Management personnel
P"... Phase Immediately after design acceptance
DuII.n 4 days
Sttlletlt Capacity Based on the City's requirements
Corpus Christi, Texas SOW
Fxhibit E: Attachment 0\-2 Training Plan
Page 4 of 32
I NTERGRAPH
2. I/CAD Data Workshop (IPST1001)
I/QlD'J)ata Workshop (IPST1OO1)
The I/CAD Data Workshop will begin the CAD implementation process by building data using CADDBM.
Required and optional database tables will be reviewed, along with specifics regarding data characteristics
such as data type and length A detailed overview of the system components is also included, along with a
diSCUSSion of available configuration and custom Ization options. Finally. an overview of basic CAD
functions IS covered to allow for the adequate testing as data design and entry continues. For those Cities
requlnng extensive deployment plans and unit recommendation data, the IleAD Deployment Planning and
Configuration workshop will oe dedicated to covering tables and data required to achieve successful unit
recommendations
Mapr'Topics
I System Components and Terminology Overview
Configuration Tools and Process Overview
I r:: Database Structure Including Table BuildinglTable Functions
I Data Entry and Maintenance with CADDBM
Map Table Overview (if needed)
BaSIC CAD Commands Necessary for Testing of Data
P.......isites
Management, deciSion making, or data collection/data entry position
~ Appropnate delivery and setup of minimall/CAD hardware, as arranged with the instructor
M.. Conducted on-site by IPS personnel
Tatk Cllassiflcations System Administrator, Mapping Support Database Support, Senior User
and/or Supervisor, Training, and Management personnel
p.... Phase Immediately after design acceptance
D_.n 4 days
S....t Capacity 12, based upon the Citys requirements and available hardware
Corpus Christi, Texas SOW
Fxhibit E: Attachment A-2 Training Plan
Page 5 of 32
INTERGRAPH
3, IICAD Deployment Planning and Configuration (IPST1003)
~Io_ent Planning tnd Configuration (IPST1003)
The IICAD Deployment Planning and Configuration workshop, as a continuation of the I/CAD Data
Workshop, Will focus exclusively on those tables and configuration elements that support unit
recommendation and deployment functions In IICAD Deployment plans, which define primary and backup
coverage areas. along with any overriding response needs for specific areas, are covered in detail.
Response requirements and f'esponse plans make up the elements recommended by unit recommend,
and will be discussed and designed This session is cntical for Fire agencies in particular, or any other
agency that plans to have Involved deployment and unit recommendations
M""opics
~ Deployment Plans
c~, ESZs and Polygons
c; Response Plans
[:~ Response Requirements
c;:. Unit Recommend Parameters and Configuration Considerations
P....,isites
c~ IICAD Data Workshop, with completion of Unit Vehicle, Personnel, Event Type tables data entry
c~ Complete gathenng of response requirements including any unique responses based upon
location
M.. Conducted on-site by Intergraph personnel
Ta4k dlassiflcations System Administrator, Mapping Support, Database Support, Senior User
andlor Supervisor, Training, and Management personnel
.:
p.... Phase Following the IICAD Data Workshop with adequate time to achieve
pre req u isites
Du..n 3 days
St"'.. Capacity 12
Corpus Christi, Texas SOW
Exhibit E: Attachment A-2 Training Plan
Page 6 of 32
INTERGRAPH
4. I/CAD Workflow and Configuration Workshop (IPST1004)
"*\Iv~and Config.tion WOrkshop (IPST1084)
During the IICAD implementation, accomplishing certain parts of a City's workflow with I/CAD may not be
,mmediately evident to the City themselves This session dedicates IPS consultants to helping the City
define their workflows uSing the IICAD suite of applications Before and during this process, specific
configuration needs will become apparent, Including graphical user Interface adjustments, parameter
settings and other special configuration tasks that may be required to accomplish the City's operational
requirements These configuration tasks will be identified and possibly designed and completed during this
week When the session is finished, the Intent is for the City to proceed to their user training with the
c:onfiguration and workflow definition as close as possible to the final. to ensure their users are
:omfortable and competent with the system and ready for live operations
M.r Topics
City IICAD Workflow Definition
Identification of Necessary GraphiC User Interface (GUI) Modifications, Parameter Setting
Changes, Command Line Definitions and Other Configuration Specifics
-, Execution of Configuration Changes if time allows
P.....isites
~ Completion of IICAD Essentials (for Trainers) training
" Identification and documentation of all workflows requiring special attention
M._ Conducted on-site by IPS personnel
T. Classifications System Administrator, Senior User andlor Supervisor, Training, and
Management personnel
Prctect Phase After IICAD Essentials for Trainers is complete, but with adequate time to
accomplish all necessary configuration changes before user training
commences
D..n 4 days
St...... Capacity Based on the City's requirements and available hardware
Corpus Christi, Texas SOW
Exhibit E: Attachment A-2 Training Plan
Page 7 of 32
INTERGRAPH
5. IICAD Calltaking Essentials (IPST2003)
"* 'alltakillgEssentials (PST2003)
..
The I/eAD Calltaklng Essentials training course is presented directly to personnel responsible for public
safety call processing It familiarizes telecom m u n icatlons personnel with the basic features of
workstations terminology forms. navigation and event processing, as well as map utilization and
nquines Laboratory exercises are included with each module to provide additional experience in
workstation operation ThiS course is required for proper system operation and must be taken before a
student may progress to IICAD Dispatching and IICAD Supervisor to complete the IICAD Core Essentials
training program ThiS course IS required for proper system operation and can also be taught by
designated City trainers having completed the appropriate IICAD Essentials and Trainer Consulting
courses
Maltr Topics
-. Introduction to Windows
c: BasIc Workstation Functions
~, Calltaking Operations - Entering Events, Verifying Locations, Updating Events
~ Map View Control
~ Interfaces for Users (as needed. If Installed interfaces are applicable for calltakers)
P.....isites
-' Knowledge of basIc public safety terminology
c.,
~, Responsibility for calltaking andlor dispatching
c:- An Introduction to Windows course or equivalent knowledge and familiarity with the Windows user
In te rface
M.04I Conducted on-site by IPS personnel
T", Cilassifications CAD Dispatcher CAD Supervisor System Administrator, and Training
personnel
P"'" Phase Should be complete With adequate time to prepare for cutover
Du".n 2 days
St", Capacity 12, With a maximum of one student per workstation
Corpus Christi, Texas SOW
Exhibit E: Attachment A-2 Training Plan
Page 8 of 32
INTERGRAPH
6. IICAD Dispatching Essentials (IPST2004)
II.D-~ispaffhlng Esaentiallra (IPST2004)
The I/CAD Dispatching Essentials course IS presented directly to personnel responsible for public safety
dispatching This course follows I/CAD Calltaking Essentials (IPST2003), with emphasis on handling field
units and personnel Advanced inquIries and updates to events and units are also covered. Several
agency specific operations are included, to Include Fire, Law Enforcement and EMS related updates. An
introduction to the use of Interfaces to such things as NCIC, State crime databases, Mobile units, and Fire
station printers IS also presented This course is required for proper system operation and can also be
taught by designated City trainers having completed the appropriate I/CAD Essentials and Trainer
Consulting courses If biG along with IICAD Calltaking Essentials and I/CAD Supervisor, the three together
comprise the IICAD Core Essentials training program
M.rTopic8
I Recommending and Dispatching Units
1
! . ' Updating Unit Statuses
'I
~
I ~ Modifying Unit Properties
c. Updating Unit Related Event Information
! _.._~ Querying Unit and Event Data
c~ Performing Fire Specific Operations - Update Alarm, Relocate (Move Up) Units
["~ Performing Law Enforcement Specific Operations - Traffic Stop, Subject Stop
~ Performing EMS Specific Operations - Divert Hospital
-.,. Interfaces for Users !11lnformer. I/Page, I/FST. and I/MDT for example)
P......isites
c. Knowledge of basic public safety terminology
~ I/CAD Calltaking Essentials (IPST2003)
M.~ Conducted on-site by IPS personnel
T. Classifications CAD Dispatcher CAD Supervisor System Administrator, and Training
personnel
P1"t Phase Should be complete with adequate time to prepare for cutover
DUII.n 2 days
St...... Capacity 12, with a maximum of one student per workstation
Corpus Christi, Texas SOW
Exhibit E: Attachment '\-2 Training Plan
Page 9 of 32
INTERGRAPH
7 IICAD Supervisor Essentials (IPST2005)
I/_upervtsorEssentlaIS4fIPST2005)
The IleAD Supervisor course is presented directly to personnel having supervisory or managerial capacity
i and responSibility The course familiarizes students. with more advanced I/CAD commands and report
I writing utilities required to effectively supervise the dally activities of a public safety answering point. Focus
is placed upon both the I/CAD System functionality and how this functionality can best be utilized as a
management tool This course is required for proper system operation and can also be taught by
designated City trainers having completed the appropriate I/CAD Essentials and Trainer Consulting
:::ourses
M.rtopics
Freeing Locked Records
~. Advanced Graphic Manipulations
c: Back Filling Event Information
Possible additional tOpiCS if deemed necessary and time allows
r:::;. Running Reports and Queries with CAD Reporting utilities
c~ I/NetViewer-I/NetDispatcher Operations (if necessary as part of the City's system)
[~ System-related Supervisor Tasks, such as Database Recovery and Troubleshooting
c:~ Interfaces for Users (1/lnformer I/Page, I/FST and I/MDT for example)
PI4Jrtlisites
c_~ Supervisory or managerial position; knowledge of basic public safety terminology
I/CAD Calltaklng Essentials (IPST2003)
-, IICAD Dispatching Essentials (IPST2004)
M.~ Conducted on-site by IPS personnel
T. QlassiflOattons CAD Supervisor System Administrator, and Training personnel
PI.... Phase Should be complete with adequate time to prepare for cutover
Dufatiitn 1 day
St....e. Capacity 12. with a maximum of one student per workstation
Corpus Christi, Texas SOW
Exhibit F: Attachment A-2 Training Plan
Page 10 of 32
I NTERGRAPH
8. I/CAD Reassessment (IPST2006)
I/~easstssment (IPST*6)
The I/CAD Reassessment session IS designed to bring the users and managers of the I/CAD system
together with IPS system consultants experienced In center operations The consultant will conduct
structured group sessions to clarify the anginal goals of the project and will then review present
operations on-site and assess how goals and objectives are being met. This information is the core of
additional group sessions to determine if progress is satisfactory or if adjustments must be made to goals
and priorities Recommendations will be made as to any configuration changes that should be made to
accomplish the goals and objectives, or other requests as they arise. These recommended system
modifications may be accomplished during the week. depending on the scope and complexity of each
Item Further implementation work may be required to perform more complicated recommendations, and
these will be part of follow-or work provided during subsequent visits or contact.
MtPr1fopics
!I Review of EXisting Utilities
r
~
~I instruction on New Utilities
I [~:: Use of Existing Functionality to Optimize the Operation of the Center
! c'; Creation of a Current and Functional Computer Utilization Plan
',' GUI. Command Line or Other Configuration Changes
c~ Customized Training or Retraining of Specific Areas
p.ctUisites
~.. ., I/CAD System In live operation for a minimum of two months
M.. Conducted on-site by IPS personnel
T.4lassiftOatlons System Administrator, Key I/CAD Users, Training, and Management
personnel
:;.'
p." Phase Ideally, two months after cutover to live operations
Ducat_n 4 days
St",,, Capacity N/A
Corpus Christi, Texas SOW
Exhibit E: Attachment A-2 Training Plan
Page 11 of 32
INTERGRAPH
9, IIMobile Reassessment (IPST2007)
I.. ReallSessment CIPS"2007)
The I/Mobile Reassessment session IS designed to bring the users and managers of the I/Mobile system
together with IPS system consultants experienced in field Mobile operations The consultant will conduct
structured group sessions to clarify the original goals of the project, and will then review present
operations on-site and assess how goals and objectives are being met This information is the core of
additional group sessions to determine if progress is satisfactory or if adjustments must be made to goals
and priorities Recommendations will be made as to any configuration changes that should be made to
accomplish the goals and objectives, or other requests as they arise. These recommended system
modifications may be accomplished during the week depending on the scope and complexity of each
item Further implementatior, work may be required to perform more complicated recommendations, and
these will be part of follow-or work provided during subsequent visits or contact.
M.r 1'I"0pics
:j ReView of EXisting Utilities
,
1 Instruction on New Utilities
GUI or Other Configuration Changes
" Customized Training or Retraining of Specific Areas
P....isites
I/Mobile in use In live operations for a minimum of two months
M.OII Conducted on-site by IPS personnel
-'"
Tatk Ilassiflcations System Administrator, Key I/Mobile Users and/or Supervisors, Training, and
Management personnel
PI" Phase Immediately after design acceptance
O"'n 4 days
sujl_ Capacity N/A
Corpus Christi, Texas SOW
Exhibit E: Attachment A-2 Training Plan
Page 12 of 32
INTERGRAPH
10. IICAD Database Schema and Reports Overview (IPST2009)
I/e..a.baSe Schema andReports Overview (IPST2009)
!/CAD Database Schema and Reports Overview is presented to personnel responsible for collecting CAD
statistics Including call center event and unit history information This intensive course familiarizes City-
selected staff With features of the l/eAD schema and the skills required to create custom reports for data
collection
M.r Topics
'--,. Understanding the lie AD database schema
~. Creating reports using Microsoft Access and/or SQL Plus
~
~ Queries and Reports
P,..isites
r-' Responsibility for CAD system administration and/or training
~ Familiarity with CAD and associated functions
c: Knowledge of Microsoft Access and/or SQL
M.ot Conducted on-site by IPS personnel
".
T4 "ssifiCations System Administrator, and Data Analysts
P...- Phase Should be complete with adequate time to create and customize needed
reports for live operations
Du...,n 3 days
St..... Capacity 6, unless prior approval obtained from instructor
Corpus Christi, Texas SOW
Exhibit F: Attachment A-2 Training Plan
Page 13 of 32
INTERGRAPH
11. IICAD Trainer Consulting (IPST2010)
110. 'rain8f COl1$ulting (IPlT201 0)
i/CAD Trainer Consulting will focus on areas of concern to those personnel responsible for training of
!lCAD users in preparation for cutover to live operations This consulting session will cover topics of
nterest to a customer's designated trainers, to help them reach maximum comfort level with teaching their
own users A review of basic I/CAD concepts features and functions will be conducted to ensure
competency of the trainers Specific training Issues and areas of attention will be identified and discussed,
along with the design and preparation of training documentation as needed.
M.r Topics
t , Review of I/CAD Essentials
I Advanced I/CAD Commands
Training Concepts for CAD
L Training Documentation consulting and modification
[,.; Workflow Examination
~ Gap AnalysIs
Possible additional tOpiCS. If deemed necessary
c~ I/NetViewer-I/NetDispatcher Operations (if necessary as part of the customer's system)
System-related Supervisor Tasks, such as Database Recovery and Troubleshooting
Interfaces for Users (1/lnformer I/Page. I/FST and I/MDT for example)
L, Configurable System Options
Pui'lu"isites
PrevIous completion of I/CAD Core Essentials (Calltaking, Dispatching, Supervisor) training
program
Mef,hott Conducted on-site by Intergraph personnel
Ta4k tlassifications Training personnel
P"" Phase At least one month following the I/CAD Core Essentials training, but with
adequate time for necessary preparation before User training is to begin
Du__n 3 days
St",. Capacity 12
Corpus Christi, Texas SOW
Exhibit r: Attachment ;\-2 Training Plan
Page 14 of 32
INTERGRAPH
12. I/MARS Configuration and Administration (IPST2102)
I," Oor41uration and Alfministration (IPST2102)
I/MARS Configuration and Administration is presented to personnel responsible for the administration and
support of the I/MARS sUite of applications The course familiarizes administrative personnel with the
maintenance. support. and customization of the I/MARS product, plus the maintenance of the various data
used by the system Configuration of I/MARS with I/Adminlstrator and I/Analyst is covered, along with the
customizatlon of applications for use with INlewer This course will also familiarize the attendees with the
basics of analyzing data with the INiewer module of I/MARS. the component used to create and view
report output
M.r'ropics
I ," Installation and Setup of I/MARS
k.,
Configuring I/MARS
", USing I/Analyst to Customize Applications
-. Managing Security for Users and Topics
~ Managing Software Upgrades and Version Control espeCially with respect to the database
-.v Creating Map Chart. Spreadsheet and Report Output
c~ Customizing Output
~ Saving Viewer Options
Pr....Jisites
L~ Familiarization of CAD/CAD/RMS database model and data
c: Training in or eqUivalent knowledge of I/CAD or I/CAD System Administrator, Oracle SQL,
ODBC/SQLNet concepts, Microsoft Access, Microsoft Excel, and Microsoft Windows
M." Conducted on-site by Intergraph personnel
;
T. 'lassifiCations System Administrator, Database Support, or other personnel responsible for
reporting and analysis requirements definition and management
p.. Phase Approximately one month or later after live CAD/RMS operations
O..n 2 days
Sbldett Capacity Six
Corpus Christi, Texas SOW
Exhibit E: Attachment .'\-2 Training Plan
Page 15 of 32
INTERGRAPH
13. IIMobile User Training (IPST2501)
1/ftllIi!I6 User,(IPST2501)
I/Mobile User training IS designed to train field users In the use of the I/Mobile product.
(Note: I/Moblle Administration is Included during the System Administrator training, and pertinent topics
covered dunng the regular l/eAD or I/CAD Train-the-Trainer and Operator/User courses. This session is
for field users who have not been trained as I/CAD operators)
M.r Topics
Use of I/Moblle on MDCs, or laptops
Untt Status Changes
Inquiries
Sending and Receiving Messages
Updating Unit Properties
c: Updating Events
P.....isites
~, Responsibility for mobile computing operations
Assignment of at least one person who has been through I/CAD Essentials training, to perform
necessary dispatching and other I/CAD functions
Availability of customer specific Mobile configuration
Availability of test or training Mobile PCs for use in class
MeIh. Conducted on-site by Intergraph personnel
TaWt Class_ations Field User personnel
pr., Phase After I/CAD Core Essentials training is complete, and before cutover
O_tton 1 day but could be changed dependent upon customer needs
Stljl..t Capacity 12, with a maximum of one student per workstation
Corpus Christi, Texas SOW
Exhibit F: Attachment A-2 Training Plan
Page 16 of 32
I NTERGRAPH
14. I/LEADS Train-the-Trainer (IPST2203)
1/ &;j Tram-the-Trainer (I.T2203)
1"7
I/LEADS Traln-the-Tralner is presented to personnel responsible for local agency training, This intensive
course familiarizes customer selected training staff with all features of the I/LEADS applications, and the
skills required to Impart this knowledge to others
M.r'opics
I c' BasIc System Components
~ <.-.."
n c-:: Master Indexes (Name, VehiCle. Property. and Location)
Involvement Subsystem
c; Data Entry
L< Quenes and Reports
c::__ Training Considerations
P..JiSites
L~ Responsibility for RMS supervision or training
M.. Conducted on-site by IPS personnel
T. tlassifiOations I/LEADS Operator, System Administrator, and Training personnel
p.... Phase After the database has been created Following any site-specific
configuration and/or GUI changes This class is recommended to be
conducted a minimum of two weeks before operator training commences to
allow the customer's trainers adequate time to prepare,
Ouptifn 4 days
St.... Capacity Twelve with a maximum of two students per workstation
Corpus Christi, Texas SOW
Exhibit E: Attachment A-2 Training Plan
Page 17 of 32
INTERGRAPH
15. IILEADS Jail Management System Train-the-Trainer (IPST2205)
~ JaUllanagement Slftem (JMS)Train- The-Trainer (IPST2205)
if LEADS JMS Train-the- Trainer is presented to personnel responsible for local agency training. The
course IS designed to supplement the basic I/LEADS Train-the-Tralner course to familiarize correctional
personnel with the basIc features of the I/LEADS JMS product and the skills required to impart this
knowledge to others
M4>>' Topics
c::. BasIc System Components
c~, Master Indexes (Name, Vehicle, Property, and Location)
c:: Involvement Subsystem
c:: Data Entry
c:: Queries and Reports
c~ Training Considerations
P....isites
c:: Responsibility for JMS supervision or training
M~ Conducted on-site by Intergraph personnel
""
Ta. .ss~tions Operator. System Administrator, and Training personnel
p.... Phase After the database has been created Following any site-specific
configuration and/or GUI changes This class is recommended to be
conducted a minimum of two weeks before operator training commences to
allow the customer's trainers adequate time to prepare
D 2 days
pc
St.... Capacity Twelve. with a maximum of two students per workstation
Corpus Christi, Texas SOW
Exhibit [: Attachment A-2 Training Plan
Page 18 of 32
INTERGRAPH
16. IILEADS Administrator/GUI (IPST2208)
Il~ System Adminlatr_rJGUI Training (tPST2208)
I/LEADS System Administrator Training is designed for individuals responsible for the technical
administration, management or support of the I/LEADS System The system administrator should be
designated early in the project, as their full time involvement in the installation and implementation of the
system IS critical to each agency's success and the overall success of the I/LEADS system. Students
receive both classroom training and hands on experience enabling them to perform the basic functions
associated with the day-to-day operation and support of the I/LEADS system
A special emphasIs on System Graphical User Interface (SYSGUI) enhances this training. This portion of
the training provides the system administrator with methods to modify the I/LEADS product to conform to
local requirements and needs
Note: Material covered during this session affects the product and database directly and can have a
negative Impact if Improperly performed
.....Topics
BasIc System Components
I/Leads Site and Agency Configuration
Controlling Access
Lookup Tables
L, Defining Case Management Rules
c'::;:- BasIcs of Field Reporting Configuration & Administrative Tasks
c~, System Add-Ins
c~ System Administrator Configuration Tools
~ Documentation of Changes Made to the System
P....isites
[::~ Responsibility for the installation and local implementation of the I/LEADS System
~... Responsibility for supporting and administering an Oracle or SOL Server database
Working knowledge of Windows. Working knowledge of major networking components, including
clients, servers, drivers, protocols. and network operating systems
c: Knowledge of basIc computer hardware components
L~ Proficiency using the Windows interface, including the ability to use Windows Explorer to locate,
create, and manipulate folders and files, create shortcuts. map network drives, and configure the
desktop environment
M._ Conducted on-site by IPS personnel
Tatk tlassifiCations System Administrator, and Management personnel
pr,,- Phase Following I/LEADS Core Team training and before any User or Train-the-
Trainer sessions
DuilllltiDn 4 - 4.5 days Sites with JMS may require an additional Y2 day to cover JMS
speCific configurations, questionnaires and facility codes.
5t..,. Capacity Six. one student per workstation
Corpus Christi, Texas SOW
Exhibit F Attachment .\-2 Training Plan
Page 19 of 32
INTERGRAPH
17. IILEADS System Overview Workshop (IPST2209)
"LP1s Sy.m Overview .rkshop (IPST2209)
The I/LEADS System Overview Workshop provides a system preview and guidance to system
administrators, core team members, and managers of the customer's implementation team, Data
collection and local configuration of the I/LEADS database is vital to ensure the system is ready for future
training classes and Initial set up and Installation of I/LEADS This seminar provides the customer's
Implementation team with the information needed to begin data collection and configuration of the
database pnor to training courses such as System Administrator and Traln-the- Trainer,
The course Includes an overview of basic components, essential data collection and an overview of the
I/LEADS modules
M.tJfopics
Understanding Requirements for Implementing I/LEADS
BasIc system components
Basic System Configuration and Tools
UCR to Statutes Table
System Plcklist Tables
,..'.., System Modules and Master Indexes
L~' Overview of System Modules and Components
P......i.it..
Core Team Member System Administrator, Management Supervisor, Key User or Stakeholder,
Trainer or decIsion-making position
Set-up of minimall/LEADS hardware and software
_. Conducted on-site by IPS personnel
is
TaIk"assifltalions Core Team Personnel. System Administrator, Management, Supervisor,
Agency Stakeholder, and Training Personnel
P" Phase Following the customer kickoff meeting, Note: This is typically several
weeks after the Initial kickoff meeting
O.tfJ>n 4 days
S",_t Capacity Based on the customer's reqUirements, available hardware and projection
systems
Corpus Christi, Texas SOW
Exhibit F.: Attachment .\-2 Training Plan
Page 20 of 32
I NTERGRAPH
18. IILEADS Field Reporting (AFR) (IPST2210)
I/LIfA$ Field Reporting (AFt) (IPST2210)
i/LEADS Field Reporting training is presented to personnel responsible for entering data or querying
ilLEADS In a field environment. The course familiarizes field personnel with the basic features of I/LEADS
Field Reporting capabilities
M.rfopics
c, BasIc System Components
~, Involvement Subsystem
c:: Searching
L, Data Entry
c:: Master Name Indexes (Name Vehicle. Property, and Location)
c: Reports and Queries
c~ Transferring Data
Pr....iSites
c: Responsibility for record creation In a field enVIronment
c: I/LEADS RMS User (IPST2201) or I/LEADS RMS Train-the-Trainer (IPST2203)
c::'" I/Mobile User (IPST2501)
M-, Conducted on-site by IPS personnel
:'ft-
v.....
T. .assifications I/LEADS Operator (field personnel), System Administrator, and Training
personnel
PrcIeot Phase After I/LEADS database has been created. Following any site-specific
configuration and/or GUI changes After successful completion of the
I/LEADS RMS User (IPST2201) or I/LEADS RMS Train-the-Trainer
(IPST2203) and I/Mobile User (IPST2501) Courses,
DuIl.n 2 days
St..- Capacity Twelve, with a maximum of two students per workstation
Corpus Christi, Texas SOW
Exhibit E: Attachment <\-2 Training Plan
Page 21 of 32
INTERGRAPH
19. I/LEADS Data Analysis Workshop (IPST2211)
I/L~ GataAna.lysis Workjhop (IPST2211)
This is a workshop designed to provide select individuals who may be responsible for extracting data from
the I/LEADS product In a format usable for cnme analysis and/or uniUpersonnel deployment based on
crime patterns. The workshop builds on the User or Train the Trainer class in using the capabilities of the
I/LEADS software, expanding the use of map to obtain certain data that IS collected in the I/LEADS
database and disseminate this data In the form of pin maps or reports
M.rfopics
" System Components
~.
~. Overview of Certain I'LEADS Modules
c: Configuration Tools
c; Queries In I/LEADS
c: Master Indexes (Name, Vehicle, Property, and Location)
r' Documentation
~,
c: I/LEADS Map tools - creating and uSing pin maps
P.....isites
c~ I/LEADS RMS User (IPST2201) or I/LEADS RMS Train-the-Tralner (IPST2203)
-, Responsibility as a System Administrator, Supervisor, Trainer or Data Analyst.
'-"V live operation for a period of at least 60 days
~. PrevIous attendance of either an I/LEADS User or I/LEADS Train the Trainer class
M.. Conducted on-site by Intergraph personnel
T4 'a8S~atlons System Administrator, Supervisor, Trainer or Data Analysis personnel
r,
~Pha.. After I/LEADS has been live for at least 60 days
"
O.'ltn 1 day
i;
.'
St"'elljt Capacity Twelve, with a maximum of two students per workstation
Corpus Christi, Texas SOW
Exhibit [: Attachment ..\-2 Training Plan
Page 22 of 32
I NTERGRAPH
20. I/LEADS RMS Core Team Orientation (IPST2212)
ilL'" Records Managemelat System (RMS) Core Team Orientation (IPST2212)
The I/LEADS RMS Core Team Orientation IS a hands-on class designed to familiarize the core team with
the practical operation of the system All applicable modules will be covered, with the exception of those
'n the JMS :Jail Management System) which are covered In a separate orientation session.
M.r topics
~. BasIc System Components
", Master Indexes (Name. Vehicle. Property, and Location)
.....0, Involvement Subsystem
",
.~ Data Entry
c::: Quenes and Reports
Pr..isites
- Responsibility for RMS operations
-, Member of the RMS Core Team
MeIIt()jl Conducted on-site by IPS personnel
Tat 1JassiflC;ations I/LEADS Operator, Core Team members
p..... Phase Following initial system Implementation
F ,:
Oufititn 4 days
5.e. Capa4:ity Twelve. with a maximum of two students per workstation
Corpus Christi, Texas SOW
Exhibit F: Attachment A-2 Training Plan
Page 23 of 32
INTERGRAPH
21. IILEADS JMS Core Team Orientation (IPST2213)
ilL:" Jail.an-.g4Pent Stftem (JMSlCore Team orientation. (IPST2213)
i/LEADS JMS Core Team Onentation IS a hands-on class designed to familiarize the core team with the
practical operation of the system All applicable modules will be covered
M""opicS
-, BasIc System components
-. Master Indexes (Name, Vehicle. Property, and Location)
~ Involvement Subsystem
-' Data Entry
~,
-' Quenes and Reports
,-",
P....isit8$
c: Responsibility for JMS Operations
c: Member of JMS Core Team
Mt4faoI Conducted on-site by Intergraph personnel
Taf eifass~tions I/LEADS JMS Operator, Core Team Members
T
Pr,*", Pha.e Following initial system implementation
Dufltrtn 2 days
.,';:;
S~... Capacity Twelve. with a maximum of two students per workstation
Corpus Christi, Texas SOW
Exhibit E: Attachment A-2 Training Plan
Page 24 of 32
INTERGRAPH
22. IILEADS Reports (IPST2214)
ilL" Reports (IPST2214)
I/LEADS Reports IS presented to personnel responsible for collecting cnme statistics. This intensive
course familiarizes customerMselected staff with features of the I/LEADS schema, and the skills required to
create custom reports for data collection
M.r 'opics
, Understanding the database schema
,
it
ij L. Creating reports using Microsoft Access and/or Crystal Reports
"
c~ Queries and Reports
P......isit..
I Responsibility for RMS supervision and/or training
I c~ Familiarization of RMS database model and data
c' Training in or equivalent knowledge of I/LEADS. Oracle / SQL, ODBC/SQLNet concepts,
Microsoft Access and Crystal Reports
M.. Conducted on-site by I PS personnel
Talt:llaSSifications System Administrator, and Cnme Analysts
& -\
p.... Phase Following completion of I/LEADS Train-the-Trainer training. Test system
should be in place prior to training to allow students access to the database
to create and test reports For customers using I/MARS, this training should
be conducted before, but In close proximity to the I/MARS user training.
DufI._n 2 days
St""t Capacity Three, one student per workstation
Corpus Christi, Texas SOW
r\hibit F: Attachment A-2 Training Plan
Page 25 of 32
INTERGRAPH
23. I/NetViewer-I/NetDispatcher (IPST2401)
"+twer-tIJIetDlspatCMr .ST2401)
I/NetViewer and I/NetDlspatcher training is presented directly to personnel responsible for operations,
either I/CAD or I/CAD at a remote facility. It familiarizes personnel with the commands used in the
i/NetViewer and/or I/NetDlspatcher application during event entry and inquiry operations. Laboratory
exercises are included with each module to provide additional experience in workstation operation. This
course is required for proper system operation with I/NetViewer and/or I/NetDispatcher and can also be
taught by graduates of the IICAD or I/CAD Traln-the- Trainer courses.
Malt' topics
ce Event Entry Operations
Inquiry Commands
~ Unit or Crew Operations
r:; Setting User Preferences
~ Other Utilities
P....isites
c; Knowledge of appropriate public safety terminology
~. Knowledge and familiarity with Windows user Interface
~
c; Knowledge and familiarity with latest version of Internet Explorer
M." Conducted by Intergraph personnel either on-site or in Madison
T....assifioations Operator, System Administrator, Mapping Support, Database Support,
Training and Management personnel
pr... Phase Should be complete with adequate time to prepare for cutover
Ouf'tttn 1 day
.
sb.jleet Capacity 12, With a maximum of one student per workstation
Corpus Christi, Texas SOW
Exhibit E: Attachment .\-2 Training Plan
Page 26 of 32
INTERGRAPH
24. IIMobile Workflow and Configuration Workshop (IPST2502)
I/rqlr. WOrlflow and eonr"'ration Workshop (IPST2502)
During lIMo bile Implementation, accomplishing certain parts of a City's workflow with I/Mobile may not be
Immediately evident to the City themselves This session dedicates IPS consultants to helping the City
define their workflows uSing IIMobile Before and during this process, specific configuration needs will
become apparent Including graphical user interface adjustments, report formats and other special
configuration tasks that may be required to accomplish the City's operational requirements. These
configuration tasks will be designed and possibly completed during this session. When finished, the intent
:s for the City to proceed with their I/Mobile user trainmg with the configuration and workflow definition as
close as possible to the final. to ensure their users are comfortable and competent with the system.
it will be necessary during this seSSion, to have at least one Dispatcher who is familiar with I/CAD and its
use present to perform dispatching and other IICAD tasks as necessary
M.r 'opics
c~ Overview of liMo bile Features and Functions
~ I/Mobile Workflow Definition
c:. Graphical User Interface DeSign and Configuration
c: Report Format Design and Configuration
~ Other Configuration Settings as Needed
Pit .isites
c: Responsibility for mobile computing operations
c: Completion of IICAD Essentials (for Trainers) training
c: Identification and documentation of aliI/Mobile workflows requiring special attention
M.. Conducted on-site by IPS personnel
T-i iassiflcations
;
System Administrator, Senior Field User and/or Supervisor, Field Training,
and Management personnel
p.... Phase
After I/CAD Essentials for Trainers is complete, but with adequate time to
accomplish all necessary configuration changes before I/Mobile user
training commences
.
Du.tifttn
3 days
S~ Capacity
Based on the City's requirements and available hardware
Corpus Christi, Texas SOW
Exhibit E: Attachment A-2 Training Plan
Page 27 of 32
INTERGRAPH
25. I/CAD System Administration (IPST3101)
.,,,
"*tystemAdministratiolt{IPST3101)
~he I/CAD System Administration course IS an intensive course designed for individuals responsible for the technical
administration. management. andlor support of the I/CAD System The System Administrator should be designated
early in the project, as their Involvement full time In the installation and implementation of the system is critical to
each agency s success and the Jverall success of the IICAD System. Students receive both classroom training and
hands-on experience enabling them to perform the basic functions associated with the day-to-day operation and
support of an I/CAD System Please note the stated prereqUisites and student capaCity, as strict adherence to these
's essential to the successful completion of this course.
MaJlr _pies
,. System Configuration and Layou1
c; Network (TCP/lP) Configuration
c; Database Introduction, including Oracle and SOL Serve! Setup
c:~ RADO Configuration and Use
c; Database Recovery
c; Software Component Overview and Installation
c; Changing Parameter Settings
c; Command Line and Macro Configuration
c; Introduction to Customizing the IICAD Graphic User Interface (GUI)
c; Maintaining I/CAD Configurations and the Registry
c; Administrator Utilities
c;; BaSIC Troubleshooting
P...,.,sites
Strong adherence to the following prerequiSites is absolutely mandatory
c; Responsibility for the Installation and Implementation of the IICAD System
c~ Working knowledge of Windows. Working knowledge of major networking components, including clients,
servers, local area networks, network adapter cards, drivers, protocols, and network operating systems
-' Proficiency using the Windows interface, including the ability to use Windows Explorer to locate, create,
'-----,
and manipulate folders and files. create shortcuts. map network drives. and configure the desktop
environment
c; Knowledge of basic computer hardware components, Including computer memory, hard disks, central
processing units (CPUS), communication and printer ports, display adapters, and pointing devices
c~ CADTools User (if appropriate), CADDBM User, and all appropriate database/operating system training as
necessary (unique per customer)
c~ Attendees of thiS course must attend the System Maintenance course taught after cutover to obtain full
system administration training
MetIod Conducted by Intergraph personnel on-site or In Madison
T~ Gtassifications System Administrator and Other Support personnel
Pr~lPhase After the I/CAD Data Workshop with adequate time before IICAD Essentials
training commences
;
Du". 4 days
stultnt Capacity Six, with a maximum of two students per workstation
Corpus Christi, Texas SOW
Exhibit F: Attachment A-2 Training PllIn
Page 28 of 32
INTERGRAPH
26. CADTools (IPST3103)
CAItr.,IS (IPST3103)
fhe CADTools User course IS presented to personnel responsible for the creation and maintenance of the
i/CAD street map. As part of CADTools training, students will use actual data from their agency to create
segments of a working database and will receive hands-on practice In entering, updating, deleting, and
inquiry
M.rfopics
Street Map Overview
c~ Map-related Database Structures
~
c:~ Address Verification
c: Polygon-based Deployment Plans
0::' Street Network Applications
c:: CADT ools/MicroStation Introduction
c:' Map Editing Tools
c- Intersection and Segment Manipulations
~.
0::' Special Address Manipulations
c:: Enhancements and Reference Files
c:. Remap Application/Showmap Application
P....isites
c;: Responsibility for data entry and/or map editing
[~ Knowledge of baSIC IiCAD terminology and data tables
c~' Familiarity with area geography and operational requirements
L~ Familiarity with MicroStation to aid in the understanding and retention of CADTools concepts. It is
best that all students will have taken the MicroStation for Mappers (TSYS5002) course to meet
this prerequisite, see Additional Training Options section for information on this course.
M.. Conducted on-site by IPS personnel
Tatk .assiflcations System Administrator, Mapping Support, Database Support, and Training
personnel
p..... Phase After the map IS ready for operations
Dut-tito 4 days
Sbleji Capacity Six, with a maximum of two students per workstation
Corpus Christi, Texas SOW
Exhibit F: Attachment "\-2 Training Plan
Page 29 of 32
INTERGRAPH
27. Map Maintenance for IICAD Systems (IPST3104)
M..inten.u;e for IICA[) erstems (IPS1'3104)
The Map Maintenance course familiarizes and emphasizes the map maintenance workflow to be carried
out at the particular City site It will be a highly customized class, with subject matter depending upon
several Important variables, such as whether the agency is maintaining its own map data, whether a local
GIS provider IS maintaining the map (and In what format), whether translation software is needed to make
the workflow easier, and the frequency with which updates will be completed. This informal class will leave
the responsible System Administrators with a workflow and document to complete the process
successfully themselves The class will be conducted using the designated map maintenance workstation,
and all reqUired mapping software (depends on City's system) must be installed and functional.
M.r Topics
c., Collection and Entry of Data
c: Map Validation and Network BUilding Routines
c; Table Building, Restructuring, and Updating
c~ Quality Control
c~ Re-mapping and Loading of New Map Data on User Workstations and Servers
P'itI'ljJisites
c~ System Administration and/or responsibility for map creation/maintenance
c~ Complete familiarity with the process of map creation as it relates to the City's data, including
knowledge of basic terminology and data tables
c:; MicroStation and MGE familiarity, or completion of courses MicroStation for Mappers (TSYS5002)
and MGE Foundations (TMAP21 00) see Additional Training Options for more information on
these courses
M~ Conducted on-site by IPS personnel
Ta8 Qlassiflcations System Administrator and Mapping Support. Possible involvement by
Database Support, and Project Management personnel
P~ Phase After the method and theory of the City's actual map maintenance has been
resolved and before cutover
Du*,*n 3 days, dependent upon City needs
S~ Capacity Six, with a maximum of one student per workstation
Corpus Christi, Texas SOW
Fxhibit F: Attachment A-2 Training Plan
Page 30 of 32
INTER GRAPH
28. I/CAD System Maintenance (IPST3107)
lI.yet_ Malnt..a.e (lpST3107)
The IICAD System Maintenance course covers the system administration and maintenance tasks required
following cutover to live operations, to ensure smooth transition and hand off of responsibilities from IPS to
City System Administrators. A review of essential System Administration topics will be conducted to
ensure comfort with those tasks. Other maintenance topics covered will include creation and management
of maintenance logs, IPS help desk procedures, and database maintenance and tuning. Please note the
stated prerequisites and student capaCity as strict adherence to these is essential to the successful
completion of this course
M.r Topics
System Administration Review
Logging/Support Process
T rou bleshooti ng
Other Maintenance Utilities
Clock Synchronization
Database Maintenance
Regular Maintenance Tasks
Help Desk Procedures
Upgrade Considerations and Preparation
Documentation/Change Log and Other Maintenance Log Generation
Windows Server Utilities
PI..isitea
~. It is mandatory that attendees of this course will have completed the IICAD System
Administration course
M... Conducted by IPS personnel on-site or in Madison
T. Cla$SifiCatlons System Administrator and Other Support personnel
PI'" Phase Immediately following cutover to live operations
Dup_n 4 days
S.. Capacity Six
Corpus Christi, Texas SOW
Exhibit f: Attachment ~-2 Training Plan
Page 31 of 32
INTERGRAPH
29. Support for Cutover to Live \lCAD Operations (IPST5003)
SuIIMIt for CUtover to Live tlCAD Operations (IPSTSOO3)
Support is provided by an IPS trainer to furnish IleAD users with continued support during cutover to live
IICAD Operations
M+ topics
~ Support for IICAD Users
PI,-,isites
-, None
c_,
M.ott Conducted by IPS personnel on-site
T. Classifications CAD Calltaker, CAD Dispatcher CAD Supervisor, System Administrator,
and Training personnel
P,.... Phase During cutover to live operations
DUltt.n 5 days
Sttllelt Capacity N/A
Corpus Christi, Texas SOW
Exhibit F: Attachment :\-2 Training Plan
Page 32 of 32
INTERGRAPH
Attachment A-3
Interface Control Documents
As stated In SOW task # 6, detailed Interface Control Documents (lCD's) will be developed as a result of
the information shared during Interface Requirements Workshops. Once developed and approved by
intergraph and the City. the lCD's will be Included in this SOW attachment. The interfaces for which lCD's
will be developed are
I/lnformer Interface to TCIC/NCICITLETSITDLD/PPDIDMV/Pawn
2 I!lnformer Interface to Municipal Court System
3 I/MDT - liMo bile Data Terminal (message switch)
4 I/FSA - I/Fire Station Alerting
5 I/Tracker
6 I/CADLink file transfer to CnmeView Web
7 I/FireRMS CADLink to Firehouse RMS
8 I/InterCAD to DECCAN Live MUM Interface
9. Interface to ANI-All E911
10. liTDD - Telephone Device for the Deaf - Zetron
11. I(LEADS RMS Import from Pawn Shop System Interface
12. Custom CAD and RMS reports
Preliminary Draft lCD's are enclosed below
Corpus Christi, Texas SOW
Exhibit E: Attachment A-3 Interface Control Document
Page 1 of 13
.-<. ..",.
INTERGRAPH
TLETS!TCIC/"IClC/NLFTS Interface
h.flee Name TCIC/lfClCITLETSlTDLD/PPD/DMVlPawn Interface
Interface Summary Provides transaction processing between Intergraph CAD/MDS users and the
systems connected via TLETSITCIC/NCIC/NLETS.
Intergraph System Install. configure, and test Intergraph' existing TLETSITCIC/NCIC/NLETS
Interface I Interface software (1/Informer) and configure the interface to conform to the Texas
I TCP/IP specifications
External System I Support for query and update to TLETSITCIC/NCIC/NLETS.
, Interface I TCP/IP
. Protocols
I I TCP/IP
, Intergraph
i Hardware Interface
I Intergraph Tasks Install configure and test interface software and message reformat utility.
, City Tasks Provide TCIC/NCICITLETSITDLD/PPDIDMV/Pawn system communications and
associated equipment
: Comments Intergraph is providing the software to support the definition of screen formats and
i the reformatting of these into the formats required by TLETS/TCIC/NCIC/NLETS.
For the list of standard queries provided to the Texas State TLETS interface,
please refer to the document titled "Error! No text of specified style in
document. Error! No text of specified style in document." and
RMS _ Texas_ State_Suite doc"
i
~ ~_.._._-_.._- _ _____-L- _ --.,.---- ------
Corpus Christi, Texas SOW
Exhibit E: Attachment A-3 Interface Control Document
Page 2 of 13
INTERGRAPH
2 IIlnformer interface to Municipal Court System
,
I'ntpffe Name IIlnfonl1er interface to Municipal Court System
Interface Summary Provides transaction processing between Intergraph CAD/MDS users and the
i City's Municipal Court System Courthouse 2000. which is the Court Specialists
I Inc. (CSI) system
Intergraph System Install configure, and test Intergraph' existing I/Informer interface software to
Interface communicate queries to / from the City's Municipal Court System.
External System Support for query and update to the City's Municipal Court System.
Interface I
i
, Protocols TCP/IP
. Intergraph IEEE 802 3 Ethernet LAN
Hardware Interface
Intergraph Tasks Install configure and test interface software and message reformat utility
City Tasks PrOVide system communications to I from the City's Municipal Court System, and
, shall provide all necessary documentation of the Courthouse 2000 system and an
authoritative technical contact for the duration of the effort.
Comments Intergraph is providing the software to support the definition of screen formats and
I the reformatting of these into the formats to I from the City's Municipal Court
I System
City shall assure the cooperation of all third parties to this development.
Intergraph assumes no costs for third party software that might be needed to
complete this development
This interface will allow the police department to obtain subpoenas, check status
of the court calendar, and obtain data pertaining to offender status and,
dispositions on cases
-..---.....- _. ,'-"--- .--.....-.-.. ....--.>-
Corpus Christi, Texas SOW
Exhibit E: Attachment A-3 Interface Control Document
Page 3 of 13
INTERGRAPH
3. I/MDT - I/Mobile Data Terminal (message switch)
I~e Name IIMOT -I/Mobile Data Terminal (message switch) Interface
Interface Summary The I/Mobile Data Terminal (I/MDT) interface sends and receives messages from
a message switch connected to the local area network (LAN) or an RS-232
communication port The message switch connects to the City's Wi-Fi 802.11 x /
Cingular/carrier network and the PadCom Total Roam solution to complete the
communication between the dispatch environment and the vehicle-based mobile
data terminals (MDTs) MDT's can review and update event, unit, personnel, and
I equipment information maintained In the dispatch environment.
i
Intergraph System Install. configure, and test a copy of the I/MDT message switch interface
Interface
! External System RadiO Infrastructures Supported
Interface . Motorola RD-LAP
. DataRadio DMP
. Any Winsock Compliant IP Stack provider
WNGS/MWCS (Motorola IP stack on top of RD-LAP)
MAlCOM EDACS (No native support for EDACS API - IP only)
DataRadio IP (IP stack on top of DMP - provided by DataRadio)
CDPD
GPRS
1 xRTT
! Protocols TCPIIP or RS-232
Intergraph
Hardware Interface
Intergraph Tasks Install, configure and test interface software,
, City Tasks The City to supply Intergraph a vendor contact that will supply complete and
accurate documentation on the City's Wi-Fi 80211 x I Cingular/carrier network to
be interfaced The City must also supply the third party message switch, and its
connectivity (RS-232 or TCP/IP)
Comments
. ---.""-,,,.,..,..- ----,----._- --- -- .---.-----. -_...__..._..._. ~~'-----"'-----'_._.,,_,-
Corpus Christi, Texas SOW
Exhibit E: Attachment A-3 Interface Control Document
Page 4 of 13
INTERGRAPH
4. I/Fire Station Alerting Interface
'.
II~f,e Name I/Fire ltation Alerting Interface
Interface Summary Provides support for alerting remote fire stations when units from a station are
dispatched
Intergraph System Install configure, and test Intergraph' existing l!Fire Station Alerting interface to
Interface City's turnout controller
I
l
External System l!Fire Station Alerting Interfaces with the following turnout controllers:
Interface . Zetron Model 6/26
. Westnet Firstln
I . Motorola Centracom Gold Elite
I . Motorola MOSCAD
!
I
, Protocols I TCP/IP
, Intergraph IEEE 802.3 Ethernet LAN or an RS-232 serial connection.
. Hardware Interface
Intergraph Tasks Install. configure and test interface software
City Tasks The City is responsible for providing complete and accurate documentation on the
devices to be Interfaced.
i Comments Each distinct turnout controller requires an additional license of I/Fire Station
Alerting.
Intergraph cannot be held accountable for incompatibilities in its interface which
are due to changes In inpuUoutput formats or data requirements of the vendor's
product
l;tergraPh does not recommend using the alert controller for printing run cards in
-------..--- a station. We suqqest a separate Imolementation
-"-----..-.-
Corpus Christi, Texas SOW
Exhibit E: Attachment A-3 Interface Control Document
Page 5 of 13
INTERGRAPH
5 IITracker (AVL) Interface
Iln*'*e Name IITrac"r (A VL) Interface
i
Interface Summary Provides the interface between GPS receivers in vehicles to CAD to provide
automatic vehicle location (AVL)
Intergraph System Install, configure, and test Intergraph' existing I/Tracker interface to one of the
Interface supported third-party AVL controller/message switch and/or the individual GPS
receivers mounted in the vehicle and the CAD system.
External System Interfaces with one of the following third-party AVL controller/message switch
Interface and/or the indiVidual GPS receivers mounted in the vehicle and the CAD system.
. Tnmble Placer 450 I 455
. Tnmble PSC 200
. Sierra Wireless MP 200
. Avel-Tech
The follOWing protocols are supported.
. NMEA
. TAIP
i
i Protocols TCP/IP
i
I Intergraph IEEE 802 3 Ethernet LAN or an (RS-232) serial connection
I Hardware Interface
i Intergraph Tasks Install configure and test interface software
City Tasks AcqUisition and installation of the GPS receivers in the vehicle (and a differential
correction base station, if required). City is also responsible for identifying which
mode the system should use for operation and for providing a complete and
accurate soeclfication of the protocol used to communicate with the AVL system..
Comments One copy of I/Tracker is required for each AVL controller and/or message switch.
llhe AVL controller or message switch must be available on the network or
. _______ connected by.RS-232 serial connection
Corpus Christi, Texas SOW
Exhibit E: Attachment A-3 Interface Control Document
Page 6 of 13
INTERGRAPH
6. I/CADLink file transfer to CrimeView Web
Ilntpf..e Na_ IICADLdnk file transfer to CrimeView Web
Interface Summary Provide CAD event and incident information to the City's CrimeView Web
application
Intergraph System Intergraph proposes its I/CADLink to push incident information to a specific
Interface location for the CnmeView Web Interface
External System Support updates to the City's existing CrimeView Web application.
. Interface
Protocols TCP/IP
Intergraph NIA
Hardware Interface
, Intergraph Tasks Install configure and test interface software utility.
I
City Tasks Import of the ASCII comma-delimited text or XML files containing I/CAD incident-
related data, into the City's CrimeView Web application database.
Comments I/CADLink exports specific incident-related event information from the I/CAD
database to ASCII comma-delimited text files and XML (formats suitable for
import into most database systems)
Note that IleAD events must be closed before they are candidates for export by
I/CAD-Link I/CAD-Llnk does not provide features or I/CAD interfaces for
obtaining "next available case numbers", "location verification", or any other
I/CAD-related functionality or interfaces; it only provides functionality for export of
~--,_._.__..'--""'--- speCified event data for closed I/CAD events.
Corpus Christi, Texas SOW
Exhibit E: Attachment A-3 Interface Control Document
Page 7 of 13
INTERGRAPH
7. IIFireRMS CADLink to Firehouse RMS
In"*e Name IIFireRMS CADlink to Firehouse RMS Interface
Interface Summary Provide CAD event information to the City's Firehouse RMS.
Intergraph System Intergraph proposes its I/FRMS-CADLink the interface to the customer's existing
Interface Firehouse RMS. I/FRMS-CADLink will transfer event and resource data to
Firehouse's CAD MONITOR which In turn will populate the Firehouse RMS
Database
External System Support updates to the City's existing Firehouse RMS
I nt.rface
Protocols TCP/IP
Int.rgraph NIA
Hardware Interface
Intergraph Tasks Install configure and test interface software utility
City Tasks Provide Firehouse RMS system communications and associated equipment City
is also responsible for acquiring and installing CAD MONITOR data import
caoabilitv into their current Fire RMS system
Comments I/Fire Link interfaces to various Fire RMS systems, facilitating the automatic
I transfer of IICAD event data I/Fire Link accomplishes these using INCO
I transactions
i
I An INC01 IS generated when the first unit belonging to a defined I/CAD agency
and dispatch group clears an event The INC01 contains a lot of event
i information
I An INC02 IS generated each time a unit belonging to a defined I/CAD agency and
: dispatch group clears an event The INC02 is unit-level information.
I An INC03 IS generated when the last unit clears the event and the event is
I closed. The INC03 contains additional event information since the INC01 was
[ sent
Ilntergraph cannot be held accountable for incompatibilities in its interface which
I are due to changes In input/output formats or data requirements of the vendor's
uroduct The customer is responsible for providing complete and accurate
--.--.-..----......- ____ documentation on the systems to be interfaced
Corpus Christi, Texas SOW
Exhibit E: Attachment A-3 Interface Control Document
Page 8 of 13
INTERGRAPH
8. I/InterCAD to DECCAN Live MUM Interface
II_flee Name DECCAN MUM Interface
;-,-'-"
Interface Summary The IllnterCAD application sends to the DECCAN-written MUMS client the
standard XML protocol that Intergraph has defined for unit status and event
information Each unit status change will result in a transmission from IlInterCAD
to the DECCAN-written server
The DECCAN MUM Interface is a two way interface (1) to push the information to
DECCAN LiveMUM (2) to send in real-time a request back to CAD to relocate
speCified units
Intergraph System I Install configure, and test Intergraph' interface to DECCAN's MUM software.
Interface I
External System I Support the sending of incident and unit information to the DECCAN MUM
Interface I application and the return to the IICAD system of request for the relocation of
Protocols I units
1 TCP/IP
I
I
i Intergraph IEEE 8023 Ethernet LAN
: Hardware Interface
! Intergraph Tasks Install. configure and test interface software
I City Tasks The City is responsible for providing complete and accurate documentation on the
systems to be interfaced.
, Comments Intergraph cannot be held accountable for incompatibilities in its interface which
are due to changes In input/output formats or data requirements of the vendor's
product
i
~,...__._._.....- ____.__L. _ ____________._
Corpus Christi, Texas SOW
Exhibit E: Attachment A-3 Interface Control Document
Page 9 of 13
INTERGRAPH
9 ANIIALllnterface
Ilo.,.e Name ANIIALllnterface
, Interface Summary Provide an interface directly to each of the Plant Equipment, Palladium, and
Positron 911 AN II All controllers Transfers data from the incoming ANI/All
packet to the appropriate fields in the event entry screen. When the interface
receives the telephone company information, an on-screen indicator button is
highlighted to notify the IICAD operator that a 911 call has been received. When
the button IS selected, IICAD automatically loads all available telephone company
Information into the main form
The ANIIALI interface also supports FCC Phase II requirements for Cellular 911
calls The IICAD system supports the creation of events based on a geographic
coordinate location Intergraph expects that ANIIALI packets for Phase II
Wireless 911 calls Will include the coordinates (in lat/long or other standard
coordinate system, as dictated by the NENA standard or FCC requirements), and
will use this information to create an event at the caller's geographic coordinate
location and show the location on the map. The exact format of this data in the
ANI/All packet must be supplied by the City (in conjunction with their phone
system supplier
Intergraph System Install. configure, and test Intergraph' existing interface (which supports each of
Interface the following 911 ANI/All controllers)
. Plant Equipment
. Palladium
. Positron
External System Interfaces to the following 911 ANI/All controllers
Interface . Plant Equipment
I · Palladium
I Positron
' .
I
Protocols ! Ethernet Network (TCP/IP, UDP) or an RS-232 connection.
I
Intergraph IEEE 802 3 Ethernet LAN
Hardware Interface
Intergraph Tasks Install configure and test interface software
I
City Tasks Install and test the Serial cable. The city must also supply a complete and
accurate documentation on each of the ANI/All controller interfaces.
Comments Intergraph cannot be held accountable for incompatibilities in its interface which
I are due to changes in input/output formats or data requirements of the vendor's
._____~ct
Corpus Christi, Texas SOW
Exhibit E: Attachment A-3 Interface Control Document
Page 10 of 13
INTERGRAPH
10. I/TOO - Telephone Device for the Deaf - Zetron Interface
In_.e Name Ifrelephone Device for the Deaf (I/TOO) Interface - Zetron
Interface Summary Provides connectivity to the Zetron Model 3030 through an RS-232 port. The
device detects the TOO call made by a hearing or speech impaired person. It also
allows the call taker to display the caller's message and converse with the caller
Via the TOO dialog
Intergraph System Install. configure, and test Intergraph' existing I/TOO interface to the Zetron Model
Interface 3030 controller through an RS-232 port
External System Interfaces with the Zetron Model 3030 through an RS-232 port.
Interface
Protocols Serial-232
Intergraph RS 232 serial connection.
Hardware Interface
Intergraph Tasks Install, configure and test interface software Intergraph will also supply a Zetron
3030 for each CAD workstation that is required to take TOO calls. An RS-232 port
on each CAD workstation is required for a Zetron 3030.
---
City Tasks
The City IS responsible for connecting the Zetron 3030s into the City's phone
system
Comments ~-
____________L__ .--"..----
Corpus Christi, Texas SOW
Exhibit E: Attachment A-3 Interface Control Document
Page 11 of 13
INTERGRAPH
11. I/LEADS RMS Import from Pawn Shop System Interface
In.,.e Name IILEAQS RMS Import from Pawn Shop System Interface
Interface Summary The I/LEADS Import utility allows a loosely-coupled exchange of data from
heterogeneous systems based on mutually agreeable formats such as XML or
comma-delimited ASCII and containing information in accordance with the
I/LEADS Schema current on delivery of the product to a designated location.
The Import Utility supports both manually activated and automatic or scheduled
imports.
Changes made to the Interface and I/LEADS tables via the I/LEADS GUI
Customization utility can be included in Imported data.
Intergraph System Install configure, and test Intergraph's I/LEADS Import utility to import the City's
Interface Pawn data
External System TBD
Interface
Protocols TCP/IP
Intergraph IEEE 802.3 Ethernet LAN
Hardware Interface
Intergraph Tasks Install configure and test interface software
City Tasks The City is responsible for providing all necessary documentation that pertains to
the site-specific customizations related to their Pawn system data. City is also
responsible for providing an authoritative point of contact from which Intergraph
development staff can request support during the development and
implementation process of this interface
Comments
------~-- .---.-. .-".--
Corpus Christi, Texas SOW
Exhibit E: Attachment A-3 Interface Control Document
Page 12 of 13
INTERGRAPH
12. Custom CAD and RMS Reports
The Citys RFP required a list of system reports for both CAD and RMS. A number of these reports are
stock reports with the CAD and RMS systems Intergraph will develop reports that are not currently
jelivered with the system
RFP Section 3.15.1 - CAD reports
. Dally log showing all calls received for the prior 24 hours from time of printing
. Number of calls by call type and/or time of day
. Number of calls by call type by unit responding
. Number of calls by call type and/or day of week
. Number of calls by day of week and/or time of day
. Number of calls by call type and/or shift
. Number of calls by call type. by reporting area
. Average response time to calls by district, call type and time of day
. Average response time to calls by district, call type and day of week
. Ratio reports (call taker to calls, dispatchers calls, field unit to dispatcher, etc)
. Total person hours consumed by time of day and day of week
. Average response time to calls by district, call type and shift (from ring time to arrival)
. Total person hours consumed by district, call type and day of week
. Total person hours consumed by district call, type and time of day
. Computer response time report
. Attempted security breeches
. Error messages by type for identifYing system problems
RFP Section 426 - RMS Reports
. Uniform Crime Report (submitted and forwarded to the State monthly basis)
. Arrest/Misdemeanor Citation Report (submitted and forwarded to the State monthly basis)
. Hate Cnmes Report (submitted and forwarded to the State on a monthly basis)
. Domestic Violence Report
. Officer/Clerk Productivity Report
. Property Inventory Report
. MiSSIng Case Numbers (from CAD to RMS)
. Pending Case Log by Case Number/Officer
. Type of Events by Reporting Districts/Time/Day
. Cnme Activity Reports
. Associates Reports
. Auto Theft Reports
. Traffic CollisIon Reports (Detail and Summary)
. Cnme/Arrest/Misdemeanor Citation/Traffic Collision Reports listing sorted by National
ClassificatIon Codes Reporting Districts, Reporting Officer, etc
. Cnminal Case Investigation Reporting (Cases Filed, Closed, Pending, Active, etc.)
Corpus Christi, Texas SOW
Exhibit E: Attachment A-3 Interface Control Document
Page 13 of 13
INTERGRAPH
Attachment A-4
System Performance Test Criteria
Measurement of response IS to be measured from operator action until visual response or operation
completion Queries are performed in the background while the operator continues to perform other
calltaking and dispatching commands being notified when the query is complete.
if hardware and software are purchased from Intergraph (or hardware approved by Intergraph), then
ntergraph commits to the following
. Sub-second response for 90 percent of calltaklng and dispatching commands
. Less than 5 seconds for 90 percent of queries with queries performed as background operations
. Seconds to minutes for reports also performed as background operations
For CAD If the City does not purchase hardware through Intergraph, the response times should still be
achieved uSing Licensor hardware specifications however. Intergraph shall not be penalized for
performance problems over which it has no control
Please note that I ntergraph cannot guarantee response times where that response time depends on the
performance of an external system for example queries to state databases
Intergraph agrees to work with the City to achieve performance goals, initially for a successful
acceptance and subsequently as the City administrates the system across time. Assistance will be
provided by the Intergraph Customer Care Center
Corpus Christi, Texas SOW
Exhibit E: Attachment A-4 System Performance Test Criteria
Page 1 of 1
EXHIBIT F - PROJECT SCHEDULE
!ntergraph Corporation
I'm F oml" /\ !.'.reement
c
.. ~
~ 8
~ Nt'I
U ~~
~ a
o
S
c:
"
E
"
Q.
E
"
"
0'
~ -;
n; ~
o
Fa
r'"
~
c
,
~
...
is
N..
N::Ii
a
<(
~
::Ii
...
Q
Q
N.Q
"
~...
a
c
~
u
"
o
..
L
o
..z
a
tl
o
~
-'"
z
>-
<(
"'~
Q
Q
:~
~ I~ ~ II.~! I!! i~ : !~ ~ ~ ~ !
i 0 :"'C 1 !~:::;I r. -0 'C:J :::;I :J
-;. ::1: ~ ii It it- ~ u. i;'== ~ f-
i~ I~ ~
!c:' I~ ~
:g ~ '~ I~ I!e I!e ~ I~ I!~ :g
w ... I~ ~ ~ ~ N m M .
~ ~ ~ ~ ~ ~ ~ N N
;; ~ I~ ILL ~ I 5 ~ ~ '2 -0
'V ~ IL>.- :E ~ -'- f-::J ~
~ "
! :
I
C: - ~ I:!: ~1!~Ii:gle i:g
~ N IN IN ~ ~ - ~ N IN
~ IS; I~ I~ ~ ~ ~ I~ ,:;
U a i ~ ;~ I~ [ ~ ~ ~ ;~
"'
:J
;rl)
i t
~...r~ jl'.~-r-I'.~ 1..e
0< NN N 'It en
~ ;; .~ :;; :~ I~
-::; D -0 -0 !~ 1"0
~ ,? .~ !~ :... :~
~ ?l ~ I?" ~e I, ~ i~T~ .~ i~
;;: ~ I~ '~ I~ .~ ~ i~ I~ ~ i5i
? ~ !~ ~u- ~ ' . :E ,:2 '~ !~ ,? I~
+
~!~I~I~ ~ ~'~'I',...~..'I~ ~ ~'.>.~~!~ ~
~ I: ~ I~ ~ ~ i~ .g .g~ :~ i~ :~ ~ ~
o .: L.. Ill) ~ .- ,'-', r, IN N :I'J ~~ ,..... '"
I- .,....-t +- -+- +---+--+--~----.----t-----+ -- -
(!)
z
>-
~ ~
>- >- >- ~ ~ ~
~-l g~~ ~ t-rr~uQ. ~
~~~ri ~ ~ 5 ~~~ .-
.~~~ ~._ ~~~.~~u
..- - rll!.~.---
~ :g !:g :!:
~ ~ :~ ~
c : 5 g
f:- :~::E
~ I~ ~ ~ ~ I~ ~ ~ I I ~ ~ ~ : ~ : ~ ~ ~ ~
i !~ ~ ~ ~ r ~ ~ ~ ~ ~ u- ~ ~ ~ ~ ~ ~ ~ i
,
i
'" '"
'" Q
: ~
~ ~
! ;
~ !I
~ I~
ni~ ~
, , ~
:g :g
;;; w
;;; ~
i~
! ~ ~
i ~ ~ ~ ~ ~ ~ ~
a~~~~~(I)~
~ I- I- ~ ~ ~ ~ I-
u.
:<
-- -; --- ;>.'"
:::i: Z '!: U)
~ ~ [ci;~~~~~.
~ LL.;>. ~ Z 0.. _---
~~~~~~ ~~~:::i:8~ ~-
~ u_ u ~ u u u. rn. 0.. 0.. 0.. _.
t U :::i::::i::::i::::i::::i::::i: ---
N :E _. a.. Q. a. a.. 0.. Q. .
N ~ Q.. ------
j:;; 0.._
... ...-. ~ - ~ ------ -
~ ........ .. ... ..
:g I!:g :!:
i:O 0 an
~ ::: ~
~ ~ 0
;;::: v 0
LL 12 :::i:
!~ ; ~
c
o
::;
,
.<: .<:
>- >-
~
~ i~iE!k
TI 1-0 10 ~
Lf) 10 IN ,n
- r _+-_i.
R---t-----+
I
~~bIHj~-dltl!~!!! !
I ,., I
I
w
>- ~ >- ;>.
1tI " 1tI tV
~ ~ ~ ~
II
1"-
Ii
I~
II
I~
i-'-
,~
"
!~
i~
:.i.! l~ Q) ~ ij
! ~ Icr I~ ) ~ ~ ~ i ~ 0 :
Ii II! lj ~ ;,j ~ i, Ii i! i~ ~ ~2:> i~:t II
10 C 0 ~ _ i. :0 I r !: ~ u 10
" 11- I) ~ ~ ~ '~ "0 .. ~ I~ ! ~ c ~ ~ i" > :~~ I~ t ~
I~ ; ~ IV':" ~ i~ ~ ~~ I~ I~ ~ ~ ~ u '. i I ~ Ice ~
)( ~ :: I 13 ~ ! ~ !~ ~ ~;; I ~ I~ ~ ~" ~ ~ .o~ <( ~i ~ ~ I
I-- 4: I (.l ~ ~ UJ ; : ~ ~ ~ ~ I~ !~ !II - ~ ~ ~;;>. ~ ~ ~ !
if :~ ~ (3 Q: 0 :5 in:: <( 4: LiJ 4. in:: "" E 0 en U ,Vl G.I ::: I
E, ~ '8 :8: ':! ~ ,i !~ jO
, '-T'rtlt8-ThHHhtffilFH.'
~
"'
,.
cr
"'
o
"
'"
i
IE
io\!
I~
-=-
~-
t+~ +
i~'
c I~ E
~ r~ I ~ ;
~2:; ~ ~ JI':i ~
~ ~::: co>-5~
oi>i2:~ ~~ii~
~ ~ ~ _ ~ .~ ~ I~ 5 a
I I ~ ~ I! ~ I~ ~ I
u 0 ~ 0 I- ~ ! 0 ~E ex: ~
* I~ E
uJ
,0
> >
m m
'0 '0
o _
w
~ ~ ~
'0 '0 '0
.. ~ -
i
I
I
I
I
I
I
I
I ~
~
C I~
g,!S
~ i~
c !~
~ I ~
.g' IB
~ II
i I!
U I"~)
~
13 I--
It Ie' ~ ~
~' ;-0 ~ ~ c ~ f ~
!~ I ~ ~ 0 6 ~ ~ ~ ~
~ * ~ ~ ;o~ ~o~ ~ ~ ~ ~
~ O~'U ~~~~ ~
~ ~ i ~ i l" j ~ j i ~ ~_i ~
~~w~:zz~~~[/)~'-~
~.iinlIllIV~~ltI~gsq.El'lI
~~i~t~~] ~t~8~0~ ~
u I ~ I> ~ ~ 0 0.. > S ~ ~
~ ! g u
!
i
~ Ig: g Jj~ ~ 1;:0; :ol ~ ::; ~ ~ ~ · ~ ~ ~ :;j ~ :r
::: ~ 5i: ;; ~
L
"
[ 5
~ ~
Vl ~
~ i i
a: LU 0
I
.
I
u
'0
C
~
{
o
a:
.<:
0.
m
rn
"
c
w
~
rn
o
a:
"-
~ ix
"0 0-
cr Vl W
~
>-
w
'0
u
.
'"
~
tl.
~
o
o
~
;' ::;
~ :3- g-
E a; -g
~ 0 "0
U) <r <r
II.
"
w 0
x ~ ~
~ a: ~
>
~
"'<0
~o
:g~
tl.M
.<: ~
0.,
t~
."0
.
<f)
'"
o ,
~~ ~
0_ ~.... Z'~ ~
'I g ~t '> ..~(j ~ i
D..-~ ~~ _ ~~--u.~~~ a. ~
Q) ] ---- ~.- .
:; '"
~ ~ ru
<) N::;
~ is
o
~
c
"
E
"
a.
E
u
.
o
'"
~>
o
"'Z
Ci
g;;
:~
u
"
0'
~ ~
"rU ~
o
X
I-
;:;
,.
~ ;
u U;
on
"
'"
o ~
U I
::: :
ii -~~ ! "~
E 0 ~
><
w
8
<(
~ ~ '~ 8 :g
'-0 liD ~ ~
iO ;:0
l::- IS 23
j:t i~
o <iJ
I: ICD Q :~ ~ ;g ::3
f! 0 I~ w ~~
:i ~ ~ t ~
c
~ !~
n' ,
~"'~ :!! :g 1$ T~ :5....1
'.~.'. I~ g'l- .1~1.~. I',
'D ... ,(1) ~ I ~ i'J.; !
L ,C ! 01J C::5;:-" I
_ '0 I:J o;~ '!-
::i !l-- I~' , ;,
~.."~~ i.~ 1:~i1.~
~ ~ it; ~ I~ !~
lC' l.O -CD <.C:'-O:-o
l-~ It t :~ :2 ~
o
"
'2
:::-,
ll" ~ "
~ >- >0 >- 1>- tlI ~
1] m III flJ I_ -0 In:;
~ +-D ~ :;' ~ ~~:'
'Ii! ~; 'l'U.;r;.,,- il'~po.
IB- :II:~ _ _
[, ~ ,~ Ij ~
c- '9,~ b
t i~ !€
C .... I:{:
i i~ !t~
tl i ~ ~ : ~
~ I~ :~ i.:~
.!! ig.
Q. : U <t it'll
. i~ '4= IE
6, Ql ':'I: :~
',~,
18 :-
~ ~ ~ ~
~ ~
~ 0) ~ <n
>~ ~ ,~~ ~- .~~
~ ~ ~ ~ ~ ~ u ~ ~ ~ ~ u
u .~~ ..0..... 0....0......[ ~~ .0.... 0.. 0.. ..
. ::;0.. __- ::;0.. ___
0. ~ _ ._.._ _ __ 0. ~_.
. .
w '" '"
I~ ~ ~
'0 '0 ~
!~ ~ ~
"' :g
~ ~
c
~ ~
'"
~
'"
. 0
, .
>-
! !~
en go
i~ "1::
ioo ~
i~ 0::
ia:: -0
!If.i "ii
I~ ~
I'" i. I
I~ I'~ 10'
l~ 2 I~
I~ J. I~
c. c m
~ ~ !~ 0:: ~:.
cv <1J III ::r. 'Ill Oll _
; & -; ~ ;:~ ~ :t::
~ ~ ~ 0 ~~ 0:: 0: ,~ ~ ~ 0
I ~ ~ ~. = E io.> ~ I!u J ~ ~
~ ,-_~~~ -' c _" =_'~~
~ - ~ ~ ~ ~,-~ ~ ; ~ ~ - ~
o ]et:: no.., rj !~ : 0 a::
'u .
i<{ U
, I";;
I~ t
I~ I.~
u::: ',E
i~ ij
I~..l !o
I ,~rlTI}tl-,
... ~ I'~ ~ I~ 0 ~ N ~ ... ~ I~
~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~
L L _. .L_l _1-..L '
u.
~
C. 0..
~ ;!
t~~i~
~ ~
"' "'
'0 '0
~ ~
~ ~ I ~ ~ ~ i ~:!~ ~ : i
..... c"":J t:: C . a GI .C
~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~
~ ~ ~ ~ ~ ~ ~ i i
~ ~ ,- ~ ~ ..,. ..,. c c
u ~ ~ ~ :J :J .C ~ 0
~ ~ ~ ~ ~ ~ ~ ~
! ~ : ~
;f ~ ";: c
U. ~
~
m
'0
- ~
~
" ~
~ ~ ;;- >. ~
~~~~~
~ ~
iai;'~~~~
~ ~ g a: :g a
m
c m
g 0
m .
.g ~
~ ~ l: --
~ ~ ~ ~
~ ~ c. c. ~ ~
C. E ~ Cll 'E Q."'Cl
~ E: ~ ~ ~ ~ ~ .~ t
~~ ~~~~sg-'t:_;c~K
~ ~ [ ~ ~ _ c. 1 .~ i-
~ ~Po. w ~ ~ rn ~ ~ ~ 0 ~ ~
~ _ ~ ~ u ~ ~ ~ ~ j U ~
c.~ O~t:s~~c~g-.~&;
~ ~ ; ~ i ~ ~ ~ ] ~ ~ ~
~ 0 ! ~ ~ u u a:: ~ ~ 0 ~ ~
~ g g ~ S
5
fD
~ ~ ~ : ~ ~ ~ ~ ~ g 0 ~ ~ ~
r.
.
f ~
~ ~
<f)
I I i
I
~
I
u
"
c
m
f
c:
~
0.
m
~
.
c
.
~
o
c:
.
~
m
0. >-
~ l
0: a. ~
'" <f) W
~
o
N
.
~
m
0..
n
.
c
o
.
::- ~
[ ~ ~
~ ~ ~
<f) '" '"
II.
~
m
>-
.
. c
~ j
D: ~
~
~
<f)
S!::€
~~
0..'"
~.
0.,
Ii
'1jFFC
"I
H
d
~ ~!
~I~
N~
a
I~
..~I
<>
:~
a
c
m
u
~
o
:g
<>
N~
~z
a
"- "-
~ ~
i'i
~
-
-
~
"'
..
<>
<>
:::~~
j : ~~.I
u ~~
~ 5"-
52
;
;:
Cl>
E
Cl>
c.
E
-
L---~-i-.!l
iii Si ~ ~
cc~.~ .C-~
..
~
l!:
:~
u
~ ~ !~ i~ I~ ~ ~ I~ ~ 'lie ~ If-I'~ 11~ ~ I~ ~ ~
Ii ". co I;: i~ ,~ ~ ~ I~ 3 ~ ~ ~ ~ t2 ~ !~ ~.
(\J .U) :~ I:: ;: I~ <l! I': ~ I~ ,-g I~ -g i~ 1)
:: C L;.. ,.t: .C::I ~ i::l r- 1....-:: [~ <l! ~
~ u:: I ju.. ~ !U-. !- :1-- ,>- II-' '5
lei~T~t-I.!S ~l',~ 1.~1..,.~ If ~ Wi~~ t'~ !~ ~:g
~ t: ~:~!~ ~ ~ ~ I~ ~ i~ ~ i~ I~ i~ i~~ r;;;
B 55 ~ ~ <-~ !~ f-~ ~ it t 2 .? ~ :~ i~ i~ { ~
VI
5. I I ' j
3 ~~-1 -+ 1- "-
~o I I
:0 ~U~ ~ ~ 1tli !~' >- ~J.;~. ~
:c 0 ~ ~ ~ ~ ~ ~ ~ :;: :;;: ~
~ - :".... ~ .--. ~ .,. .~ lr
I
I
I
I
)(
>-
~ !~ Ii! jg I~ ~ ~ 3 l~ ~ I~ ~lrj ~ ~ i ~ 1~ ~ : ~ i ~
~ ~ ~ ~ I~ ~ ~ ~ r~ ~ : ~ I~ I~ :~ ~ ; ~ 'I~ c ~ 1 ~ 0
~ u... :;: 0 Il.!- j 0 l.I..- ::l.. I" ~ 1:::1 ... -c .LL l..L. I- f- C1l
f- I~ ,I- ~ l-~ l- ;: r : f- ~
~ I~ I~ 1~1n~ ~'li~r~ Iff ~~n'~ ~. '~~ II ~ S ~ ~
~ I.~~ !c: i~ I~ ~ ~ 1.~. "2 ~ ~ '19 ~ ~ ~ QI I~ ~ ~ 1(0 ~
LL l~ 2- 'u.. :~ I~ ,? i~ ~ ~ f- I~ ~ ~ ~ ~ I~ ~ ~ I~ if-
. !<;
i . .
t---+- -+ t +- + 1- -+ - +- + +-+ + +-
-l!]'~ I' 11, 1:~~'~ t" I ~ ~'. R~Bi:'11'].4: - I' ~i_I'.
>- "' >- >. (1) . >- ", >- "C "'C >- >- >- >. >.
:ll "C ", ", 1:1 "C m Iv " III 00 (II IV m I'll nJ
~; ~ ~ ~ ~ ~ ~ -3_ ~ ~ ~ ~ ~ 1: ~ ~
I 1 1 1
I ! I I
_._._~ --
.+
.,.
~
-
~
o
~
>- -
8 81!~
: ~ ~
c ~ .
o " 0
::! >--- ,I-
"- -
........- ~._--_.
~
e>:
;;:
~ ..
~
e>:
;;:+
I
1-.
I~
.- ..
o
N
..
~ ,.
:I: ;;:
~
,.
e>:
;;:
;:
Cl
:I:
~
"-
e>:
~
~.
-
.
~
o
:I:
::;.
+
~
I~i~ ~]~,~I~iii~ ~I~
1~'1l I~ 1m i"' Ie i"'O tlJ m
~__,~__~~_~_J? .l~-;-i~
Ie
I~
I~:
I~
.~
I~
~ I:
;c
: ~ ~
iL.. C
i~ v' eJ
" 1-~o!S' u
~ .... It..; ~
! ,~ I~ I~
d I~ ~ ~ i~ ;;
I! I; ~ I! till
~ ~ l~ ~ 1__" .
I~ -; i_s ~ :3
!~ I !~ ~
~
Z
I-
"
~ (5
---.
i-
iJ
~~-
o
o
'" l-
e "
~ ~
.:: ,2
~ ill!
~ i-g
~ I~
~ 10
010
~ i<(
~- i~
~I
M
o
o
I-
~
c
o
~
t !~
8 10
~ I~
0> i~
c i~
~ I~ '2
~ If ~
~ ~ ~
0.. -;;:;
~ I~ ~
~ 10 ~
~
~
>-
,:;
-
~
Z
l-
i-
t;
---
~ ~ ~
~ ~ ~
?-ioi-
u U U
---
C) L? ~
~~~~~~~
~~~55~
i3 C3 0 _-
---
~
Z
l-
i-
--0
-
~ ~ ~
Z Z Z
I- I- I-
i-i-i-
u u u
---
~~~~~~~~~
o 0 0 ~ 25 , ' "'0
~ ~ ~ ~ ~ ~ ~ ~
~ i ~ ~ ~ ~ ~ ~ ~ ~
~ coo ~ ~ 0 000
o u c cue w ~ w
~ ~ ~ ~ ~ ~ ~ ~ ~
>- >-
~ m
" "
_ N
>- >-
m m
-0 "C
N N
>. >. >- >-
m III to 1'\1
""0 1:1 U "'C
..... N N N
8 888
~ ~ ;:; ~
~ ~ ~ -g
~ ~ ~ ~
-I';.
>- >-
~ m
" "
N N
>- >-
~ m
" "
N ..
i
i
1 I
",1m
~ !;
~ ~ ..... ; ; N ; N M ; ~
~ ~ ~ c c _ c ~ . c _
~ ~ 0 ~ ~. 5 ~ a ~ ~ g
8 8 ~ ~ ~ ~ ~ ~ ~ .~
~ ~ ~ 00 ~ ~
m
c
C
"
,::
E
~ I~
~ !~
(j) iu
<0'
~ ~
t ~
(f) ~
o ~ ~ ~ _ ~ ~ _ ~ ~ . ~
~ ~ ~ ~ I l ~ I l ~ I l I
~I~i~ ~i~ ~~.~~ ~~i}~~
~~~ ~~:: ~~::~~::~
S~~~li;r~~ ~~ (ij
~ u 0 ~ u 6 ~ 0 6 w u 6 u
~ 10 ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~
~I~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~
I 1 I I
II I
!
~~~~~~~~~~8
~ ~ ~ w ~ ~ ~ ~ ~ ~ ~
~~~~~~~~~~~
~l~ ~l_~} :; ~ ~ ~ ~ ~ ~ ~ ., ~ ~ ~ ~ ~
L
~
r 5
~ ~
"' ~
.~ i i
0: LJ.J 0
I
~
I
u
"
c
~
f
Ii.
~
a.
m
'"
~
c
~
'"
o
Ii.
a.
~ ~
"0 0. "
0: "' W
~
m
I-
~
o
M
~
'"
~
"-
n
.
c
o
. ~
I- ::;
i ~ ~
~ ~ ~
" 0: 0:
II.
.
~ e
~ ~
::- 0: ~
f
"'<D
~~
"-M
~~
a."
t~
."0
~
o
o
Nrn
N::;
a
:; ~I
:~
a
u
~
0",
z
~>~
o .t::
....zu
a
~
if>
'"
~:J
M'"
a ~I
'"
:;
-0
'"
.t:
'J
(/)
"
g
:!!
"
'"
E
'"
a.
E
;:;
'"
0'
0:
.::
..
o
X
I-
"
'"
"
.t:
U
'"
:J
Q.
,3 H-
u.!~ i
.0 I ~ I ~
~ l~J~
o
~
z
~
4-r-
!9}j0
~I
"'
Z
I-
-i----
u
'"
~
"
rn
to
z
" I-
:= ~
" u
,3 -
z:.
<3
15
z
I-
" to "
i..:I " Z Z Z
~ :: ~ ~ ~
>- ~ <3 l) ()
C5 u___
--
---~-
U
to
~
-
u
<5
IE
-.-
[ll
C5
" "
z Z
I- ~
-~->-
u 0
u
<5
----c;t -Z
Z l-
I-
i--
u
G
~
...~
--
v
Z
I-
"
0.
~
u
-
+
+
~ I~ ~ I~ I~ ~ ~ I~~ ~ ~ ~ !~
~ ~ ~ I; ~ IE IS: ~ :J !u::
~ ~ I~ ~ ~ l~ to-
'~.~! 1!~!I~.~ ': ~ I
i! I'" 'J I~ ,',c "~ :~ I-
.'-+
! !!l,H!\trt1i~~ I(
, I ~ ~ ~ .~ I~ Ii I~ I~ ~ I~ ~ I~ I~ > I
t-
t- -+-
i-
~
'"
.
z:.
o
15
z
I-
-
.--.--
z:.
>- ;>. U
(] u
.11
-~I-
.
~
~ ~
:; Ir ~ ~ ~
~ I! ~ ~ m
~ ,~ u- f- ~
~ I'~
~ .,.
ai ~
~ ~
~ I~
~ ~ ; ~ ~ ~ ~ ! ~ I
.... ~ f- f--- :::.;;
~2iO~:g~~:g
... ~ ~ ~ :: co
;:0 iD ;:0 "C f'--
~ ~ ~ ~ ~ ~ ~
~ I!~
~ ~
:= I~
:l !Li
~
i
,
~ !!
'i "
I~ ~
I
i
~ ~I'~'~ ~
lD ~ ; ~ ~
:5 ~ ~ ~ :J
~ ~ .~ s ~
"'I:'"
o 0
,. '"'
~ ~
~ IE
z:.
0.
I
! :
"
~ ~
I-
z:.
c3
I
~ N
S~.
.-
." ~
U. I-
~ ~ ~ ~ ~
~~~~~
,.,
c3
.
z:.
[il-~ j
~ ~ ~ ~ ~ ~ ~
II) l,{} ID 1.0 ;:;; iD
~ ~ LL ~ LL ~ ~
I I
~ I~ tll~~ ,., ~ ~ ~ ~ ~ ~ ~
~ ~ ~ ~ ~ ~ ~ ~ "C ~ ~ ~ "C U
o ~ g ~ ~ ~ ~ 0 ~ ~ ~ ~ ~ ~
+-+
i Ii ~
'N
"...J'......
rn "
n T'
'''~''
" rn
TI ~
. ~
il~'~l~ "
:~ '_~ ~ D
t-----.-- ,
lit . ~ '. '. I!I~ I~'~ .ii~li"~'~~ I~ .~~~ '~~ ~,~
i ;.- 1>-1 >- i~ >- "l >- n i~ ro '''l 11l I ro ~ "CI :0
I~ ."~jg~L~ 1 ,,", I~ ~ ,~,~~l:Jffi_~..g_l~ .:; !}
6-,
:~
I-
'If!
iQ"
:t:: ':.0 ~
~ .. c
o I:;:: 0
.~ ~ t~
C"
;,~
~ !~
I~
is ;~.
!t...') ,
;~ It;:
1'.1) 'll
!'"
:1 ~
f; :0 Q
~, E
!
'"
o
c
rn
~Li
~ I~"
4: i'-~
!~; [,
~ -
I- a
~~~~<~
S) t;; g: 50
~ ~ I~ ~,
~ I~ ~
~ ~X
~ i~
13 I~
i; ,I
g il
o !,
o I~
-. 1-
o
'm .c
o
:! I'~o~ ',~
tX .- :~
!~ '~
,0 I~
~
I...... I.....
k.. !U'J
i~ I~
1& ;2
Ig- i~
!{;; i~ 10 (l;
'II~ 10 it? i2
IS IE ij
j~)~ ~ I~
~ !~ II~ ~
'" lu ~
" : I~ 1 ,~
~ I~ ~ ~
I"
1 If;
I", Ie
IH'
I~ It
~ !~~,
g I~;
<:t: 1;:0
Iw '
'~ ~
,- Vi
'C) ~
~ ~
:~ ~:
I:? ~
;~ :? ~
I!~ it ~ ""
- :~_-' I ~;=
I'u) - 'g> fr
~ ~ :s (r
. "
UU
:~
iu...
o
~ a.
~ (/J Ql
~,- ~') @:- :~
':: Il t; ;~
::JI c:: ro
rn c
,D ~ ~,~
: ~ ~ ,~ ~ :~
,<;;: - : ~ ~ 12
:~ ~ :,ro ~ I~
,<.:' ;o:':~ 0 '10
1~ c i~
~ rJ)
~c-
~ I:
i~ litD
'= ,01
Iii
~ iSil
lu
!
Em'" '~ '", .,~~'= ''''10-1.,- t,N M
,~ ~ ~,~ ~ ~ ~ l~!~ ~
.L~_ --L __ ..L.-_.
i~
o
:~
"
E
o
"
~
<n
~
C a
,e c.>
i~ i~ g.
D !n; 10 ~
'~ i~ :t ^' II ~
8 !~ Ii ill~ I! i
~ _m~"2=~ i~ I~ ': " III S
i~ ~ ~ C 1_ ~ ~ ~
~ I E I~ .2 ~! ~
l.- i I! ! J ; I~
':' I ~ ,QJ (J) UJ !
1(') :0 U i> ~ 15 I
5
.
;::
~ :g
j III
~ IC::
:;; iz-
i~ :0
g i~
E 10
llII i<.l.1
!i~
o !o.::
<(
Ig
o
a.
~ ~
(/) '"
::; ~
~ ~ ~ ;
ra CD 0 ra
.9 U) ra III ra Q.
~llII~~~ 8
-~~~il~j~ i
g~~2G1f~~ '"
]~~ ~~~i 7n
:-go-g~!~~~ i
~ ~ g ~ ~ 0 ~ ~
I~-~!i~:~f~
i~lli~ill!~
en ~ (f.I >- U) >- U) fa
~ U ~ 0 ~ U ~ ~
W W w
555
<n
o
~
c
,E
I:;, ~
!s lU
Ii ~
3 :J
- ~
~ u,
~ ~
E rn
~ ~
~ ~
o 0
g>
"
~l
~ ~
lb .0::
~ iu-
20
~ if>
i ~
g. ~
~ ~ ~
u 0 0
~. c~ =_ ~l~J~ ~~_~_ EJ;_ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~
L
.
~ ~
~ ~
(/)
~ i
0: w
I
.
I
u
'"
c
rn
f
g-
O:
~
a.
rn
'"
~
c
~
'"
o
0:
a.
~ ~x
o c..
'" if> W
~
rn
I-
~
o
.,.
~
'"
rn
a.
n
I
'"
if>
o
'"
~
~
c
o
~
:;;
rn
I-
[ ~ ~
~ ~ ~
VI a: a:::
II.
~
'" "
~ ~ j
~ U: ~
~
fi
(/)'"
uo
~~
a.;;;
~~
0.0
W;
EO
I~ ~ 1ff~n~ .~ ~ ~ ~ I~ ! ! ~
:~ ~ I~ I~ I~ ~ ~ c c,~ I~ g ~ ~ g g g g : g 5!i
I~ ~ ~ I~ ~ ~ ~ - ~ ~ ~ ~ ~ ~ '~ ~ ~
I
IH IH '1!~^1 !tH ~H Ill+; ij~~! IJ I!-ml! I! ;! ~~~ i [ ;!~ ~;! ~
--.-.+----+-U - +---I--+-- + . --+----~ ---..-~-t --+- ~
~ 2 I
i~ E
I"
CJ '
:;>1
<(
:1
8
:~
a
~I
u
~
o
'"
o
~ >
o
...z
a
a.
'1!!
u. :i
~ ~
~ G
i:--
,]
--,-"
>-
> ~IG
~ l)
()
,if
~~
G.
I
I~ i~
II~, i~ ,-
:;:: s
o (/)
~ ~
"&- s
a C
a. 0
-g ~
t'Il :e
c 0
i ~
-g 0
:!: :
:5 :f
'" '0
~ ~
~ ::
.~..
-~----~---_&-U'~. ~
" [a.~;;
l) 2: :!::
,~ ~ ~ ~ u
'-' :::E N N
[is ~I..
:t I~
a. '"
- .
,g
~
(/)
'"
~ ..;
ow
M<(
a
~
..
:; '"
~ ~ t'Il
l,J ~~
~ a
o
'"
..
c:
..
E
"
Q.
E
<(
~
g
:~
'0
"
0'
n: j
.:t: "i:
.. .;:
Q
x
>-
--,-
OX,I<.O
C 10
(j i~
~ !~~
>- >-
- ---~u-o
o
-.5 -3-;
...
>-
G
cj
~ ~
-~
CJ
Z
~
-
~
~ '5
u in
'"
"
c-
o
u
~ i~ !~
..
>-
G
c
'"
~ ~
~'Il) .--
'" N
a. ~
- .
.~ I
~ ~
J:: 0
)(
w
ro
T
<::-'
.
c
o
. - ,J
:8- 1)00
Q- '~ i~ il
J. ;~ i~ ia.
iii, ii 111
:; 'e Ie I
!l... Iw
If~ :~ 15
~
z
~
~
.
...
>-
G
-
:.1
~
>- >-
.~~.
L
i !
~ ~
(/) ~
~ i i
0: l1J 0
~ '~ ; ; ~ ; ~ ~ ~
~ ~ ~ ~ ~ ~ ~ ~ ~
I
i
~
l)
~
c
m
{
o
0:
'"
0.
m
'"
~
c
~
'"
o
0:
0.
~ wi
"'6 a. '"
0' (/)
~ ~ I:;:
M M I~
~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~
: ~ ; ; ; ~ ~ ; ~ : ~
CC:>:C:C::C::lCO:::lO
o 0 0 0 0 0 ~ 0 ~ ~ ~
:::! ~ ::!: :::! ::!i!: :E l-- ~
~
.
...
"'
o
"'
~
'"
.
a.
~ I~ ~
~ I~ ~ ~
~+~ ;: ~
n
~~~iU'~~
~ ~ b ~ ~ ~
~
c
o
~
~ ~
~ ~ ~
~ ~ ~
(/) 0' 0'
i]
1-0
! ~
10
, "
14'
I
'"
~. ~
.. (n
'"
ti
<( ,~
~
~ .
!~ i~ :~
:.'~ I~ I~
1>0 i~ cr::
i~ I~ Ie 'I'~
I~ Ii:: ,U ..-
I ~ 10 1<( I'~
~ [tiE ~
~ ~ ii~
~ ~ i~ g
~ ~ !~ ~
~ IUJ U)
- i....J 0
I'" <(
I~ ~
i~
i~;
II.
(/)
~
ioo
'~
;~
.
o c
C .
-[ 0: I
(,0 ~ <II I
~ ':i ~ I
;; :1 ~ I
c ... .
~ j! t ~
! ~o~ i Ii
~ >- 0
f I'~ ~ I'~
-- l~ ~ ~
1~ ~ I
Q
~
-g IS
~ !@
~ Ii
~ ,~
_ 'c..
:g ! ~
<( I~'
~
~ c
t1) ~
-: ~ ~
r- C: ~
i':'
f;:
(/)<0
~~
a.Ci
"'m
0.0
i~
Eo
--r -rnml
o g; I~ ;:: ::! ~ ~ ~ ~ I:::
- NNN("oINNNNN
, , ,I
-1.. _L ~ _ 1-'"
~ ~ ~ ~
EXHIBIT G - INTERGRAPH PROPOSAL
IIncorporated by reference]
! ntergraph C)rporation
Pro Fomld ,\'-!reement
EXHIBIT H- RFP AMENDMENT NO 1 DATED SEPTEMBER 16,2005
Ilncorporated by referencel
I ntergraph Clrporation
Pro FOm1<l A '-'rel'l11ent
EXHIBIT I - CITY'S RFP
Ilncorporated by reference)
I ntergraph C <lrporation
I'm Forme! I\~reernellt
EXHIBIT J - CERTIFICATE OF INSURANCE
j ntergraph C \ lrporatioll
Pm Forma Ac'.reement
CERTIFICATE NUMBER
ATL-001132317-01
THIS CERTIFICATE IS ISSUED AS A MATTER OF INFORMATION ONLY AND CONFERS
NO RIGHTS UPON THE CERTIFICATE HOLDER OTHER THAN THOSE PROVIDED IN THE
POLICY, THIS CERTIFICATE DOES NOT AIIEND, EXTEND OR ALTER THE COVERAGE
AFFORDED BY THE POLICIES DESCRIBED HEREIN.
I
MARSH
CERTIFICA TE OF INSURANCE
! PRODUCER
'vlarsh USA inc
3475 Piedmont Road
:,U1te 1200
~tianta. GA 30305
iI.ttn Lisa IN orthan
404) 995-3344
E&0-05-06
N"
COMPANIES AFFORDING COVERAGE
DM'
A FEOERAL INSURANCE CO
F7542:l
IINSUREC
~:OM f.:-',j,Ny
ntergraph Corporation
Attn: Birgit Stensby
'vlAllSTOP 1,,\'2000
:" O. Box 240000
~untsvllle. Al 35824
B GREA T NORTHERN INSURANCE CO
OMc:.:"I\i'r
C ST PAUL FIRE AND MARINE INS. CO
~OM P':'N\
, D
I COVERAGE.. This certificate supersedes and replaces any previously issued certificate for the policy period noted below. 2
1 C"I", '0 CERTlFv T~e' POUCIES OF NS,JRANE DESCRIBED HERE'N f-'iIVE BEEN ISSUED TO THE INSURED NAMED HEREIN FOR THE POLICY PERIOC INDICATED
! '" ,- '''''''STANDING ~N' "EQUIREME~H TERM OR CNDITION OF ".~Y C::JNTRACT OR OTHER DOCUMENT WiTH RESPEC' TO WHICH THE OERTIFICATE MAY BE ISSUED OR MAY
~I Fe:, -HE INSURAN, ' ~FFORDED 8Y Tf-'=~OLl' '=S DESCRIBE C HE'"E;~ SUBJEC TS -'iE TERMS CONDITIONS AND EXCLUSIONS OF SUCH POLICIES AGGREGATE
\1''-::':';:-HOWN MAY "A\/' h~E~~ RELUa D BY f':",:O ':'.lMS
i
I
i CO
~.LTR
IA
i
POLICY EFFECTIVE POUCY EXPIRATION
DATE (MM/DDIYY) DATE (MM/DDIVY)
TYPE OF INSURANCE
POLICY NUMBER
LIMITS
GENERAL UABILm'
06/30/05
06/30/06
3533411
GENERAL AGGREGATE
PRODUCTS - COM PlOP AGG
PERSONAL & ADV INJURY
EACH OCCURRENCE
"'MMERC~lAl -,Er, c:,A.L .:..81
,:LriMS M',m
ANER &
x
TO'.)
~;:~:--,T
;
r B -AUTOMOBILE LIABILITY
:8
"322985 - (AOS'
'32/985" (V/1)
06/30/05
06/30/05
"\u
06/30/06
06/30/06
COMBINED SINGLE LIMIT
~NEO
BODILY INJURY
.:Per person)
_ '1EDL ED", T'
h-~O.A; ro~.
)f~~':)V\'JEC
BODILY INJURY
(per accldenll
~ROPERTY DAMAGE $
r .------..- _.-
GARAGE UABIUTY
$
$
$
$
$
$
$
2,000,000
2,000,000
1,000,000
1,000,000
INCLUDED
10,000
1,000,000
$
$
:"'U'-
AUTO ONLY - EA ACOIDENT $
OTHER THAN AUTO ONLYu c='=--
EACH ACCIDENT. $,
AGGREGATE $
t ;; --- EXCESS UABIUTY
I
;'974965"
06/30105
06/30/06
EACH OCCURRENCE
AGGREGA TE
'~~REL F' ~v
I;
,'HER THANJMB~ELLA ')R~:
WORKERS COMPENSATION AND
EMPLOYERS' LIABILITY
06/30/06
x T~~N~Ns
EL EACH ACOIDENT
OTH
ER!
-163901.-'
06/30/05
i'~ ~-<OPRIErOR
,'l,h;T~jERSlEXECl - Jf
,F~lf~;:::RS ARE
OTHER
$
S
EL DISEASE-EACH EMPLOYEE S
EL DiSEASE-POLICY LIMIT
~ >';,-':l
F'EctloPIC Errors & "'--iISSions
TE Dh80Y 19
06/30/06
Limit $5,000,000
Oed $250,000
06130/05
$
$
5,000,000
5,000,000
1,000,000
1,000,000
1,000,000
DESCRIPTION OF OPERA TIONS/LOCA TlONSIVEHICLESISPECIAL ITEMS
CITY 0>= CORPUS CHRISTI IS INCLUDED AS i'DDITIONAi INSURED AS REQUIRED BY WRITTEN CONTRACT AND/OR AGREEMENT, WAIVER OF
SUBROGATION APPLIES
I CERnFlCA_"
CANCELLATION
::;hOULD A.N' OF THE POLICIES OESCRIBED HEREIN BE CANCELLED BEFORE THE EXPIRATION DATE THEREOF
,jiTY OF CORPUS CHRISTI
A TTN: EVELYN PAGE HUMAN RESUURCES
'201 LEOPARD
ORPUS CHRISTI, TX 784()1
ThE INS~)RER AF"ORDING COVERAGE WILL ENDEAVOR TO MAIL -----3.0.. DAYS WRITTEN NonCE TO THE
:~ERT1FICAq HOlJER NAMED >iEREI~ BUT FAILURE TO MAIL SUCH NonCE SHALL IMPOSE NO OBLIGATION OR
SSUER OF rhlS CERTIFiCA"'C
.IABIL_iTY ANY r:IND ,j;.JON ;f-<E INSL.RER AFFORDNG COVERAGE ITS AGENTS OR REPRESENTATIVES, OR THE
j
,
i
L-
MARSH USA INC,
BY: Walter Gilstrap
MII1(3/02)
1t/~ ~~.,.
VALID AS OF: 03/20/06