The URL can be used to link to this page

Home My WebLink AboutRFP - P882 DATABASE CONVERSION PROJECT (2)Administra.tve Services Purchasing Division CITY OF FORT COLLINS City of Fort Collins ADDENDUM No. 4 SPECIFICATIONS AND CONTRACT DOCUMENTS Description of Bid: P882 Database Conversion Project OPENING DATE: October 24, 2003 3:00 p.m. (Our Clock) To all prospective bidders under the specifications and contract documents described above, the following changes are hereby made. Fort Collins Questions: 1. In section 3.4 (Technical Expertise), bullet point six asks to describe the strategy for migrating non -relational data to a newly modeled relational database. Throughout the RFP, however, the old PRC Tri-fox version 5.5 is referred to as a relational database. Why would we need to migrate non -relational data? The new Records Management System that is being implemented in a combined system with Fort Collins Police Services and Larimer County Sheriff's Office. This requirement was listed because the Larimer County Sheriff's Office would like the option open to them to convert some of their legacy data which is housed in a database that is non -relational. 2. Under Section VII (Scope of Work, Process Identification), the RFP states that data dictionaries will be provided to the successful vendor for both systems. Are these available in an easy to read visual format (i.e. data model)? We will make these available in an easy to read format. 3. Section 3.4 (Technical Expertise) bullet point three asks for 'Qualifications of personnel and experience developing web sites'. What activities in this project will involve the development of web sites? This is actually an oversight on our part. This requirement is not necessary in the conversion of our database. 4. Section VII (Current System) mentions the possibility of converting data for the Latimer County Sheriffs Department. Should this be in the scope of the proposal? Or should we initially focus on the data migration for Fort Collins Police Services only? The proposal should focus on the data migration for Fort Collins Police Services. 215 North Mason Street • 2nd Floor • P.O. Box 580 • Fort Collins, CO 80522-0580 • (970) 221-6775 • FAX (970) 221-6707 27. Does the Tiburon system have an application programming interface (API) to insert/update information, or is the database integration the only technical alternative to importing data? Yes, Tiburon has an API data conversion tool. 28. Does FC Police Services have ODBC, JDBC, or other adapter interfaces into the source systems (Oracle 6.4, Unisys DMS 1100 hierarchical DBMS), or will the vendor be required to supply these? Both the legacy system and the new system are ODBC compliant. 29.As the prime contractor, can CIBER team with another company (providing a specific data transformation/conversion tool set and methodology) in a joint bid? As stated in the RFP, there can be no subcontractors. I'm not sure how it would work if you `teamed' with another company, as long as there are no subcontractors. 30. Is there a specific reason why Tiburon, as the provider of the new RMS, is not providing the legacy data conversion services requested in Proposal P882 as part of the RMS replacement engagement? As part of their response to an RFP for a new Records Management System, Tiburon provided information regarding database conversion. However we have chosen to separate the data conversion process from the implementation of a new Records Management System. 31. Can Tiburon submit a bid on Proposal P882? Yes, Tiburon can submit a bid on this proposal if they so choose. RECEIPT OF THIS ADDENDUM MUST BE ACKNOWLEDGED BY A WRITTEN STATEMENT ENCLOSED WITH THE BID/QUOTE STATING THAT THIS ADDENDUM HAS BEEN RECEIVED. -- FIELD CONTACT -- + ACTIVITY ------------------------------------------------------------------ Agcy FCPS Contact # 7380 Contact Date 01/09/1999 Time Reason SUSPICIOUS Status CLOSED + No ----------- ----- ------------------------------------------ ;Caution Weapons Ident # 353529622 ;Name Type P Name FINLEY, ROBERT GEORGE Race W Eth Sex M Date of Birth 09/08/1958 Age 40/ 40 Height 509/509 Weight 165/165 Hair BRO Eyes BLU Build Skin Tone Occupation Place of Birth Residence Status Citizenship Role FICARD # Alcohol/Drug Use Blood Alcohol Level ;Note + (Type/Address/Since Date) (S) ------------------------------------- *COTH /TRANSIENT, FT COLLINS, CO 80521 /12/22/1992', *HOME /2025 N COLLEGE AV #46, FT COLLINS, CO 80524 /06/04/2002 *HOME /2225 S COLLEGE AV, FT COLLINS, CO 80521 /04/22/2002 + IMN#NW (Type /Nmbr/Iss/ExpYr) (S) ++ 11IN1111#0M (Type/Number/Note) (S) - I*SID /246822 /CO / „ *HOME/(970) 493-7729 / *FBI /10234R7 / / *HOME/(970) 226-4812 / *DL /920711791 /CO / ;;*OTHR/(970) 493-0141 / +---- ----- ----- --++ -------------------------------- -[Fort Collins LIVE System] ---------------------[PRC Public Sector, Inc.]- ---> 1=ALIAS 2=ASSOC 3=FEATURES 4=PROP/VEH 5-NAM SUPP 6=VERIFY NM TABLES FIELDS # CHARACTERS NAMETYP = Name Type 1 SURNAME and GIVNAME = Name 40 RACE = Race 1 SEX = Sex 1 DOB = DOB 10 XNCAUT CAUTIONS = Caution 27 XNWPN WEAPONS = Weapons 13 WOSA 10/97 LO_HGT = Height 3 HI HGT = Height 3 LO WGT Weight 3 HI WGT = Weight 3 LO AGE = Age 3 HI AGE = Age 3 XNHAIR HAIR = Hair 3 XNEYES EYES = Eyes 3 XNSKIN SKIN = Skin Tone 3 XNBUILD BUILD = Build 3 XNOCCUP OCCUPATION = Occupation 10 XNETH ETH = Eth 1 POB = Place of Birth ? XNRESID RESID STAT = Residence Status 6 CIT = Citizenship ? BLD ALC LVL = Blood Alcohol Level 4 XNALDRG ALC DRG USE = Alcohol/Drug Use 10 NOTE = Note 70 XNLOCTYP LOC TYP = Address Type 5 XNIDTYP ID TYP = ID Number Type 6 ID NO = Nmbr 20 ID ISS = Iss 4 = ExpYr 4 XNPHTYP WOSA 10/97 PH TYP = Phone Number Type PH NO = Number PH NOTE = Note 4 14 16 -- TRAFFIC COLLISION -- + ACTIVITY ------- ---------- -------------------------------- Agcy FCPS Report # 03-1234 Reported Date 01/20/2003 Time 13:50:19 Call Type MVAH&R Call Disposition RTF + NAME -- ---------- -------------------------------------------- ;Caution Weapons Ident # 077483328 ;Name Type P Name FERRARESE, ANNEMARIE Race W Eth Sex F +----------- ------------------------------------------ Alias Name/Moniker Race Sex Birth Date +------------------------------ ----- -[Fort Collins LIVE System]---------------------[PRC Public Sector, Inc.]- ---> 1=ALIAS 2=ASSOC 3=FEATURES 4=PROP/VEH 5=NAM SUPP TABLES FIELDS # CHARACTERS SURNAME and GIVNAME = Alias Name/ Moniker 40 RACE = Race 1 SEX = Sex 1 DOB = DOB 10 WOSA 10/97 -- TRAFFIC COLLISION -- + ACTIVITY ------------------------------------------------------------------ Agcy FCPS Report # 03-1234 Reported Date 01/20/2003 Time 13:50:19 I Call Type MVAH&R Call Disposition RTF + NAME ---------------------------------------------------------------------- ;Caution Weapons Ident # 077483328 ;Name Type P Name FERRARESE, ANNEMARIE Race W Eth Sex F + --------------------------------------------- Person/Institution Named Below is of Person/Institution Named Above; ;Caution Weapons Ident # ,Name Type Name Race Eth Sex Date of Birth Age / Height / Weight / Hair Eyes Build Skin Tone Place of Birth ,Occupation Alcohol/Drug Use Blood Alcohol Level ;Note + ADDRESS (Type/Address/Since Date) (S)------------------------------------- + ID NUMBER(Type/Nmbr/Iss/ExpYr) (S) ++ PHONE NUMBER (Type/Number/Hours) (S) +-----------------++---------------------- -[Fort Collins LIVE System] -------- [PRC Public Sector, Inc.]- ---> 1=ALIAS 2-ASSOC 3=FEATURES 4=PROP/VEH 5-NAM SUPP 6=VERIFY NM TABLES FIELDS # CHARACTERS XNASSOC Person/Institution Named Below is 8 NAMETYP = Name Type 1 SURNAME and GIVNAME = Name 40 RACE = Race 1 SEX = Sex 1 DOB = DOB 10 WOSA 10/97 XNCAUT CAUTIONS = Caution 27 XNWPN WEAPONS = Weapons 13 LO HGT = Height 3 HI HGT = Height 3 LO WGT = Weight 3 HI WGT = Weight 3 LO AGE = Age 3 HI AGE = Age 3 XNHAIR HAIR = Hair 3 XNEYES EYES = Eyes 3 XNSKIN SKIN = Skin Tone 3 XNBUILD BUILD = Build 3 XNOCCUP OCCUPATION = Occupation 10 XNETH ETH = Eth 1 POB = Place of Birth ? XNRESID RESID STAT = Residence Status 6 CIT = Citizenship ? BLD ALC LVL = Blood Alcohol Level 4 XNALDRG ALC DRG USE = Alcohol/Drug Use 10 NOTE = Note 70 XNLOCTYP LOC TYP = Address Type 5 XNIDTYP ID TYP = ID Number Type 6 ID NO = Nmbr 20 ID ISS = Iss 4 ExpYr 4 XNPHTYP PH TYP = Phone Number Type 4 PH NO = Number 14 PH NOTE = Note 16 WOSA 10/97 -- TRAFFIC COLLISION -- + ACTIVITY ------------------------------------------------------------------ Agcy FCPS Report # 03-1234 Reported Date 01/20/2003 Time 13:50:19 Call Type MVAH&R Call Disposition RTF + NAME ---------------------------------------------------------------------- ;Caution Weapons Ident # 077483328 ;Name Type P Name FERRARESE, ANNEMARIE Race W Eth Sex F + ) ------------------------------------------------------ ;Category Type Location Description + ------------------------------------------------------ ;Category COAT Type WINTER Color BLU/ Note DOWN -FILLED + -------------------------------------------------------- :Type Modus Operandi +-------------------- ------------------------------------- -[Fort Collins LIVE System] ----------[PRC Public Sector, Inc.]- ---> 1=ALIAS 2=ASSOC 3=FEATURES 4=PROP/VEH 5=NAM SUPP TABLES FIELDS # CHARACTERS XNFTCAT FEAT CAT = Category 6 XNFTCAT FEAT TYP = Type 10 XNFTLOC FEAT LOC = Location 6 wMWOKINNNO FEAT NOTE = Description 50 CAT = Category 10 TYP = Type 10 WOSA 10/97 COLORI = Color COLOR2 = Color NOTE = Note 23 PXMOTYP TYP = Type 10 VALUE = Modus Operandi 25 WOSA 10/97 -- TRAFFIC COLLISION -- + ACTIVITY ------------------- ----------- ------ Agcy FCPS Report # 03-1234 Reported Date 01/20/2003 Time 13:50:19 Call Type MVAH&R Call Disposition RTF + NAME ----------------------------------------- ;Caution Weapons Ident # 077483328 ;Name Type P Name FERRARESE, ANNEMARIE Race W Eth Sex F + ---------------- ------------------------------ Invl Status Type Year Make Model License Color OWNER ACCID AU/SW 1991 SOBA 886DLG GLD/ I / / I / / I I / / I / / +---------- ------ -[Fort Collins LIVE System]---------------------------[PRC Public Sector, Inc.]- ---> 1=ALIAS 2-ASSOC 3-FEATURES 4=PROP/VEH 5=NAM SUPP TABLES FIELDS # CHARACTERS PINAMPRP = Invl o WOSA 10/97 -- TRAFFIC COLLISION -- + INCIDENT --------------------------- ----------------- ,Agcy FCPS Report # 03-1234 Reported Date O1/20/2003 Time 13:50:19 Call Type MVAH&R Call Disposition RTF ;Location 1501 S LEMAY AV, FT COLLINS, CO + ---------------- ----------------------------- NarrID Date Description of Narrative FORM O1/02/2003 K SPAULDING/LM/IN MAIN FILE/FINAL PSUPOI O1/02/2003 J VANDERVLIET/WLH/FINAL/020303/JPK PSUP02 01/04/2003 D BUHRMAN/MAZ/FINAL/011203/HR PSUP03 01/04/2003 K SPAULDING/MAZ/FINAL/010803/JBF PSUP04 01/08/2003 J KOVATS-FULTON/WLH/FINAL/011403/EP PSUP05 01/10/2003 L DINGMAN/LM/FINAL/031503/LM PSUP06 01/16/2003 L DINGMAN/HR/FINAL/021903/RLM PSUP07 03/13/2003 J KOVATS-FULTON/EP +----------------------------------- ----------------------------------- -[Fort Collins LIVE System]-------------------[PRC/Public Mgmt. Services]- ---> 1=EDIT 2=READ 4=PRINT TABLES FIELDS # CHARACTERS NARR ID = NarrID 6 NARR DT = Date 12 NOTE = Description of Narrative 59 WOSA 10/97 -- TRAFFIC COLLISION -- + INCIDENT --------------------------------- --------------------------- ;Agcy FCPS Report # 03-1234 Reported Date 01/20/2003 Time 13:50:19 Call Type MVAH&R Call Disposition RTF ;Location 1501 S LEMAY AV, FT COLLINS, CO + ------------------------------------------------------ Role REPOFF Dept ID FCC20 Name ROBINSON, RANDY ASSIST FCC14 AUSTERBERRY, JOHN I I + ------------------------------------------------- Event Class Agcy Reference Number +---------------------------------------------------------------------------- -[Fort Collins LIVE System]---------------------------[PRC Public Sector, Inc.]- ---> 1-NAME 2=VEHICLE 3=OFF/XREF 4=NARR IDX TABLES FIELDS # CHARACTERS PIINACT ACT TYP = Role 6 DEPT ID = DeptID NAME = Name F EVENT CLASS = Event Class 8 AGCY = Agcy 4 REF NO = Reference Number 12 WOSA 10/97 REQUEST FOR PROPOSAL FOR THE FORT COLLINS POLICE SERVICES DATABASE CONVERSION PROJECT THE CITY OF FORT COLLINS POLICE DEPARTMENT Opening Date: October 24, 2003 3:00 P.M. (Our Clock) RFPfor FCPS Database Conversion Project; Page / WOSA 10/97 -- PAWNED PROPERTY -- + ------------------------------------------------------- Agcy FCPS Pawn # 1 Pawn Shop Date Time Location 802 S COLLEGE AV, FT COLLINS, CO 80524 Geo -> Patrol P2 Rep Dist I006 Map 30Ll Coord / ;Status PAWNED Type R /CDISC Make Model Color / Desc VARIOUS ARTISTS Serial # / OAN + --------------- -------------- CCIC ENTRY (Y) + NAME (DISPLAY ONLY) ---------------------------------------------------- Caution Weapons Ident No 524590856 Name LANTZ, TROY MICHAEL Race W Eth Sex M DOB 10/10/1972 +---------------- --------- -[Fort Collins LIVE System]----------- ---------[PRC Public Sector, Inc.]- ---> 1=NAMES 2=VEHICLE 3-NOTES TABLES PMPPTYP PXPATROL PXREPDIS WOSA 10/97 FIELDS # CHARACTERS REF NO = Pawn # 12 EVENT TYP = Call Type 20 REF DT = Reported Date 10 REF TM = Reported Time 8 LOCATION = Location (GEO File) ? PAT AREA = Patrol 6 REP AREA = Rep Dist 6 MAP = Map 6 PPSTAT WOSA 10/97 PV STATUS = Status PV TYP = Type (NCIC Codes) PV_CATEGORY (NCIC Codes) MAKE = Make MODEL = Model COLOR1 = Color COLOR2 = Color Note = Desc SER1 = Serial # SER2 = Serial # CAN = CAN CCIC ENTRY (Y) _ 6 2 8 3 3 20 20 20 20 1 -- PAWNED PROPERTY -- + ACTIVITY ------------------------------------------------------------------ Agcy FCPS Pawn # 1 Date Time Pawn Shop + M ---------------------------------p------------------------------------ ;Caution Weapons Ident # 524590856 ;Name Type P Name LANTZ, TROY MICHAEL Race W Eth Sex M Date of Birth 10/10/1972 Age 19/ 19 Height 603/603 Weight 155/155 Hair BRO Eyes BRO Build Skin Tone Occupation Place of Birth Residence Status Citizenship Role PAWNER # Alcohol/Drug Use Blood Alcohol Level I ;Note + (Type/Address/Since Date) (S) ------------------------------------- *HOME /UNK WEST ST, ET COLLINS, CO /01/14/1994 *WORK /CABLES END, FT COLLINS, CO 80525 /01/14/1994 + (Type/Nmbr/Iss/Ex Yr) (S) ++ p 11NA)(Type/Number/Note) (S) - *DL /P948285 /CO / *HOME/(303) 490-1580 / +------------------------------------++-------------------------------------- -[Fort Collins LIVE System]---------------------------[pRC Public Sector, Inc.]- ---> 1=ALIAS 2=ASSOC 3-FEATURES 4=PROP/VEH 5=NAM SUPP 6=VERIFY NM TABLES FIELDS # CHARACTERS NAMETYP = Name Type 1 SURNAME and GIVNAME = Name 40 RACE = Race 1 SEX = Sex I DOB = DOB 10 WOSA 10/97 XNCAUT CAUTIONS = Caution 27 XNWPN WEAPONS = Weapons 13 LO_HGT = Height 3 HI_HGT = Height 3 LO WGT = Weight 3 HI WGT = Weight 3 LO AGE = Age 3 HI AGE = Age 3 XNHAIR HAIR = Hair 3 XNEYES EYES = Eyes 3 XNSKIN SKIN = Skin Tone 3 XNBUILD BUILD = Build 3 XNOCCUP OCCUPATION = Occupation 10 XNETH ETH = Eth 1 POB = Place of Birth ? XNRESID RESID STAT = Residence Status 6 CIT = Citizenship ? BLD ALC LVL = Blood Alcohol Level 4 XNALDRG ALC DRG USE = Alcohol/Drug Use 10 NOTE = Note 70 WRIMM XNLOCTYP LOC_TYP = Address Type 5 XNIDTYP ID TYP = ID Number Type 6 ID NO = Nmbr 20 ID ISS = Iss 4 = ExpYr 4 MMIMNIMOM XNPHTYP PH TYP = Phone Number Type 4 PH NO = Number 14 PH NOTE = Note 16 WOSA 10/97 -- PAWNED PROPERTY -- + ACTIVITY ------------------------------------------------------------------ Agcy FCPS Pawn # 1 Date Time Pawn Shop + NAME ---------------------------------------------------------------------- ;Caution Weapons Ident # 524590856 ;Name Type P Name LANTZ, TROY MICHAEL Race W Eth Sex M Alias Name/Moniker Race Sex Birth Date - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -[Fort Collins LIVE System]---------------------------[PRC Public Sector, Inc.]- ---> 1=ALIAS 2=ASSOC 3=FEATURES 4=PROP/VEH 5=NAM SUPP TABLES FIELDS # CHARACTERS SURNAME and GIVNAME = Alias Name/ Moniker 40 RACE = Race 1 SEX = Sex I DOB = DOB 10 WOSA 10/97 -- PAWNED PROPERTY -- + ACTIVITY ------------------------------------------------ Agcy FCPS Pawn # 1 Date Pawn Shop + NAME ---------------------------------------------------- ,Caution Weapons ;Name Type P Name LANTZ, TROY MICHAEL Time Ident # 524590856 Race W Eth Sex M + -------------------------------------------------------- Person/Institution Named Below is of Person/Institution Named Above; ;Caution Weapons Ident # ;Name Type Name Race Eth Sex Date of Birth Age / Height / Weight / Hair Eyes Build Skin Tone Place of Birth :Occupation Alcohol/Drug Use Blood Alcohol Level ;Note + (Type/Address/Since Date) (S) ------------------------------------- I / / + (Type /Nmbr/Iss/ExpYr) (S) ++ (Type/Number/Hours) (S) +------------------------------------++-------------------------------------- -[Fort Collins LIVE System]---------------------------[PRC Public Sector, Inc.]- ---> 1=ALIAS 2=ASSOC 3-FEATURES 4=PROP/VEH 5=NAM SUPP 6=VERIFY NM TABLES FIELDS /% CHARACTERS XNASSOC Person/Institution Named Below is 8 NAMETYP = Name Type 1 SURNAME and GIVNAME = Name 40 RACE = Race 1 SEX = Sex I WOSA 10/97 DOB = DOB XNCAUT CAUTIONS = Caution XNWPN WEAPONS = Weapons LO HGT = Height HI HGT = Height LO WGT = Weight HI WGT = Weight LO AGE = Age HI AGE = Age XNHAIR HAIR = Hair XNEYES EYES = Eyes XNSKIN SKIN = Skin Tone XNBUILD BUILD = Build XNOCCUP OCCUPATION = Occupation XNETH ETH = Eth POB = Place of Birth XNRESID RESID STAT = Residence Status CIT = Citizenship BLD ALC LVL = Blood Alcohol Level XNALDRG ALC DRG USE = Alcohol/Drug Use NOTE = Note SIMON XNLOCTYP LOC TYP = Address Type XNIDTYP ID TYP = ID Number Type ID NO = Nmbr ID ISS = Iss = ExpYr PH TYP = Phone Number Type PH NO = Number PH NOTE = Note WOSA 10/97 10 27 13 3 3 3 3 3 3 3 3 3 3 10 1 6 ? 4 10 70 5 6 20 4 4 4 14 16 -- PAWNED PROPERTY -- + ACTIVITY ------------------------------------------------------------------ Agcy FCPS Pawn # 1 Date Time Pawn Shop + NAME ---------------------------------------------------------------------- ;Caution Weapons Ident # 524590856 ;Name Type P Name LANTZ, TROY MICHAEL Race W Eth Sex M + ) ------------------------------------------------------ ;Category Type Location Description + ------------------------------------------------------ ;Category COAT Type WINTER Color BLU/ Note DOWN -FILLED + -------------------------------------------------------- ;Type Modus Operandi +---------------------------------------------------------------------------- -[Fort Collins LIVE System]---------------------------[PRC Public Sector, Inc.]- ---> 1=ALIAS 2-ASSOC 3-FEATURES 4=PROP/VEH 5=NAM SUPP TABLES FIELDS # CHARACTERS XNFTCAT FEAT CAT = Category 6 XNFTCAT FEAT TYP = Type 10 XNFTLOC FEAT LOC = Location 6 INNIUMMISM FEAT NOTE = Description 50 CAT = Category 10 TYP = Type 10 WOSA 10/97 COLORI = Color COLOR2 = Color NOTE = Note 23 PXMOTYP TYP = Type 10 VALUE = Modus Operandi 25 WOSA 10/97 City of Fort Collins Administr...ive Services Purchasing Division REQUEST FOR PROPOSAL Proposal Number P882 Database Conversion Project The City of Fort Collins is seeking proposals from qualified firms. Written proposals, six (6) will be received at the City of Fort Collins' Purchasing Division, 215 North Mason St., 2nd floor, Fort Collins, Colorado 80524. Proposals will be received before 3:00 p.m. (our clock), October 24, 2003. Proposal No. P-882. If delivered, they are to be sent to 215 North Mason Street, 2"d Floor, Fort Collins, Colorado 80524. If mailed, the address is P.O. Box 580, Fort Collins, 80522-0580. Questions concerning the scope of the project should be directed to Project Manager Susan Neiman (970)221-6825. Questions regarding proposals submittal or process should be directed to James B. O'Neill II, CPPO FNIGP (970) 221-6775. A copy of the Proposal may be obtained as follows: Call the Purchasing Fax -line, 970-416-2033 and follow the verbal instruction to request document #30882. 2. Download the Proposal/Bid from the Purchasing Webpage, www.fcgov.com/purchasing. 3. Come by Purchasing at 215 North Mason St., 2"d floor, Fort Collins, and request a copy of the Bid. Sales Prohibited/Conflict of Interest: No officer, employee, or member of City Council, shall have a financial interest in the sale to the City of any real or personal property, equipment, material, supplies or services where such officer or employee exercises directly or indirectly any decision - making authority concerning such sale or any supervisory authority over the services to be rendered. This rule also applies to subcontracts with the City. Soliciting or accepting any gift, gratuity favor, entertainment, kickback or any items of monetary value from any person who has or is seeking to do business with the City of Fort Collins is prohibited. Collusive or sham proposals: Any proposal deemed to be collusive or a sham proposal will be rejected and reported to authorities as such. Your authorized signature of this proposal assures that such proposal is genuine and is not a collusive or sham proposal. The City of Fort Collins reserves the right to reject any and all proposals and to waive any irregularities or informalities. Sincerely, J B. O'Neill II, PCPPO, FNIGP Director of Purchasing & Risk Management 215 North Mason Street • 2nd Floor • P.O. Box 580 • Fort Collins, C e 1W�V Wf(g. OgS2_6707 -- PAWNED PROPERTY -- + PAWN INFORMATION ---------------------------------------------------------- Agcy FCPS Pawn # 1 Pawn Shop Date Time Location 802 S COLLEGE AV, FT COLLINS, CO 80524 Geo -> Patrol P2 Rep Dist I006 Map 30L1 Coord / --------------------------------------------------------------- Status Lic Number Lic Issuer Lic Year Lic Type I Veh Type / Year Make Model Color / I I Desc II Vin + -------------------------------------------------- I I I I II I I I I I I 1 + Invl Name LANTZ, TROY MICHAEL DOB 10/10/1972 +---------------------------------------------------------------------------- -[Fort Collins LIVE System]---------------------------[pRC Public Sector, Inc.]- ---> 1=NAMES 2=VEHICLE 3=NOTES TABLES FIELDS # CHARACTERS MINNINNISM PPSTAT PV STATUS = Status 6 LIC NO = Lic Number 10 LIC ISS = Lic Issuer LIC YR = Lic Year PPLICTYP LIC TYP = Lic Type 2 PV_TYP = Veh Type 2 PV CATEGORY 8 YEAR = Year MAKE = Make o WOSA 10/97 PXPATROL PXREPDIS WOSA 10/97 MODEL = Model COLORI = Color COLOR2 = Color Note = Desc PV VALUE = Property SER1 = VIN/Ser # OAN = OAN REC DT = Recovered REC VALUE = Value $ = Type = Condition LOCATION = Location PAT AREA = Patrol REP —AREA = Rep Dist MAP = Map Value $ Date 3 3 70 9 20 20 12 9 2 12 6 6 6 PAWNED PROPERTY + ACTIVITY ------------------------------------------------------------------ Agcy FCPS Pawn # 1 Date Time Pawn Shop + NAME ---------------------------------------------------------------------- ;Caution Weapons Ident # 524590856 ;Name Type P Name LANTZ, TROY MICHAEL Race W Eth Sex M I + ------------------------------------------------------ Invl Status Type Year Make Model License Color PAWNED M /SOUSAP BUNDY / I ----------------------------------------------------------------------------- I I / / I I I / / I I I / / I I I I / / I I I / / I I I / / I I I / / I I / / I I / / I I I / / -[Fort Collins LIVE System]---------------------------[PRC Public Sector, Inc.]- ---> 1=ALIAS 2-ASSOC 3=FEATURES 4=PROP/VEH 5=NAM SUPP TABLES FIELDS # CHARACTERS PINAMPRP = Invl v WOSA 10/97 -- EVIDENCE -- + EVENT --------------------------------------------------------------------- Agcy FCPS Ref # 03-2 Date 12/31/2002 Time 23:13:26 Type TRESP3 + 111111141111111111M --------------------------------------------------- ;Tag # FC119-01 Rcvd Dt 01/10/2003 Rcvd Tm 12:25 Review Dt 07/12/2003 I ;Letter Prn Storage Locn E2B07 Rel OKd / ;Status EVID Type Y /MISCEL Make Model Color / Desc PLASTIC BAG WITH STYROFOAM CUPS/LR Ser# OAN VehLic Issu + ----------------------------------------------------- Property In - Rcvd From ;Action Date Time Clerk ID Out - Given To Note +---------------------------------------------------------------------------- -[Fort Collins LIVE System] ------------------------- [pRC/Public Mgmt. Services]- ---> 1=EVID LIST 2=CHAIN 3=NAME 4=ACTIVITY 5=PROP SUPL 6=TRANSFER TABLES FIELDS # CHARACTERS TAG_NO = Tag # 15 REC-DT = Rcvd Dt 12 Rcvd Tm 5 REL_AUTH DT = Review Dt 12 PPSTORLC STORAGE_LOC = Storage Locn 17 PPSTAT PV STATUS = Status 6 WOSA 10/97 PV TYP = Type (NCIC Codes) 2 PV_CATEGORY (NCIC Codes) g MAKE = Make MODEL = Model COLORI = Color 3 COLOR2 = Color 3 Note = Desc 20 SER1 = Serial # 20 SER2 = Serial # 20 OAN = OAN 20 LIC NO = VehLic 10 LIC_ISS = Issu 2 PPTRACK ACTION = Action 6 ACT DT = Date 12 ACT TM = Time 5 TO —FROM = In - Received From Out - Given To 20 NOTE = Note 21 DEPT ID = DeptID 6 WOSA 10/97 -- EVIDENCE -- + ACTIVITY ------------------------------------------------------------------ Agcy FCPS Report # 03-2 Reported Date 12/31/2002 Time 23:13:26 Call Type TRESP3 Call Disposition RTF + M ---------------------------------------------------------------------- !Caution Weapons Ident # ;Name Type P Name CRAIG, CARRIE Race Eth Sex F Date of Birth Age / Height / Weight / Hair Eyes Build Skin Tone Occupation Place of Birth Residence Status Citizenship Role GUARDIAN# Alcohol/Drug Use Blood Alcohol Level ;Note AUNT WITH FULL CUSTODY + jjMM (Type/Address/Since Date) (S) ------------------------------------- CWOR /PET EXPRESS, FT COLLINS, CO /12/31/2002', I / / + (Type/Nmbr/Iss/ExpYr) (S) ++ ##M#MMMM (Type /Number /Note) (S) - CWOR/(970) 545-0637 / +------------------------------------++-------------------------------------- -[Fort Collins LIVE System]--------------------------- [PRC Public Sector, Inc.]- ---> 1=ALIAS 2-ASSOC 3=FEATURES 4=PROP/VEH 5=NAM SUPP 6=VERIFY NM TABLES FIELDS # CHARACTERS WOSA 10/97 XNWPN WEAPONS = Weapons 13 LO_HGT = Height 3 HI_HGT = Height 3 LO_WGT = Weight 3 HI WGT = Weight 3 LO AGE = Age 3 HI AGE = Age 3 XNHAIR HAIR = Hair 3 XNEYES EYES = Eyes 3 XNSKIN SKIN = Skin Tone 3 XNBUILD BUILD = Build 3 XNOCCUP OCCUPATION = Occupation 10 XNETH ETH = Eth 1 POB = Place of Birth XNRESID RESID STAT = Residence Status 6 CIT = Citizenship ? BLD ALC LVL = Blood Alcohol Level 4 XNALDRG ALC DRG USE = Alcohol/Drug Use 10 NOTE = Note 70 XNLOCTYP LOC_TYP = Address Type 5 XNIDTYP ID TYP = ID Number Type 6 ID NO = Nmbr 20 ID ISS = Iss 4 MMMMMMMM = ExpYr q XNPHTYP PH TYP = Phone Number Type 4 PH NO = Number 14 PH —NOTE = Note 16 WOSA 10/97 -- EVIDENCE -- + ACTIVITY ------------------------------------------------------------------ Agcy FCPS Report # 03-2 Reported Date 12/31/2002 Time 23:13:26 Call Type TRESP3 Call Disposition RTF + NAME ---------------------------------------------------------------- ;Caution Weapons Ident # ;Name Type P Name CRAIG, CARRIE Race Eth Sex F Alias Name/Moniker Race Sex Birth Date I I +---------------------------------------------------------------------------- -[Fort Collins LIVE System]---------------------------[PRC Public Sector, Inc.]- ---> 1=ALIAS 2=ASSOC 3=FEATURES 4=PROP/VEH 5=NAM SUPP TABLES FIELDS # CHARACTERS VIRMOVANK SURNAME and GIVNAME = Alias Name/ Moniker 40 RACE = Race 1 SEX = Sex I DOB = DOB 10 WOSA 10/97 EVIDENCE + ACTIVITY Agcy FCPS Report # 03-2 Reported Date 12/31/2002 Time 23:13:26 Call Type TRESP3 Call Disposition RTF + NAME ---------------------------------------------------------------------- :Caution Weapons Ident # 'Name Type P Name CRAIG, CARRIE Race Eth Sex F + -------------------------------------------------------- Person/Institution Named Below is of Person/Institution Named Above: :Caution Weapons Ident # :Name Type Name Race Eth Sex Date of Birth Age / Height / Weight / Hair Eyes Build Skin Tone Place of Birth ;Occupation Alcohol/Drug Use Blood Alcohol Level ;Note + (Type/Address/Since Date) (S) ------------------------------------- + (Type/Nmbr/Iss/ExpYr) (S) ++ (Type/Number./Hours) (S) +------------------------------------++-------------------------------------- -[Fort Collins LIVE System]---------------------------[PRC Public Sector, Inc.]- ---> 1=ALIAS 2=ASSOC 3=FEATURES 4=PROP/VEH 5=NAM SUPP 6=VERIFY NM TABLES FIELDS # CHARACTERS XNASSOC Person/Institution Named Below is 8 NAMETYP = Name Type 1 SURNAME and GIVNAME = Name 40 RACE = Race 1 SEX = Sex I DOB = DOB 10 WOSA 10/97 XNCAUT CAUTIONS = Caution 27 XNWPN WEAPONS = Weapons 13 LO_HGT = Height 3 HI_HGT = Height 3 LO_WGT = Weight 3 HI WGT = Weight 3 LO AGE = Age 3 HI_AGE = Age 3 XNHAIR HAIR = Hair 3 XNEYES EYES = Eyes 3 XNSKIN SKIN = Skin Tone 3 XNBUILD BUILD = Build 3 XNOCCUP OCCUPATION = Occupation 10 XNETH ETH = Eth 1 POB = Place of Birth XNRESID RESID STAT = Residence Status 6 CIT = Citizenship ? BLD ALC LVL = Blood Alcohol Level 4 XNALDRG ALC DRG USE = Alcohol/Drug Use 10 NOTE = Note 70 XNLOCTYP LOC TYP = Address Type 5 IMMMMMM XNIDTYP ID TYP = ID Number Type 6 ID NO = Nmbr 20 ID ISS = Iss 4 = ExpYr 4 XNPHTYP WOSA 10/97 PH TYP = Phone Number Type PH NO = Number PH NOTE = Note 4 14 16 Vendors: The City of Fort Collins Purchasing Division has implemented an on-line vendor registration system. This system allows vendors to register, view and update their business information and commodities. In the future, vendors will also be able to receive Requests for Proposals (RFP's) and Invitations to Bids through the on-line system. All vendors doing business with the City of Fort Collins are requested to register. The vendor system is accessible through our internet website at www.fcgov.com/purchasino. Rfk lNil¢A w+, ur9 Gcnewm MM;IM 777777£' `FNk Wn1rh AM YTtia!{W.1 AnrY'7t:8 qnw Mtldfl�1+�L:Mf rvl Fbft Y.' - Y inimmeylion,er,ist o�thus`.,.n1�'.w rn'et peega eca ary psn ria tm,wr ,w,emnn.�mr,no wlw wYarrly xa lmcwna4nv na ens�uan.w-� ersxsmr. �G�w srA�,rd¢,r opsr,reg IIryWb. r,[rav yur� ss� S+uy a wn Arv+ia+ ++^n �sem M.. +sxsrn �n The vendor registration form is located v m by cli cki ng https://secure2.fcoov.comlbWloai n.i sp to redirect you to the registration site. ivUfai+ w .»bYtk..tit:':e Also please note the printable instruction pages link. If you have any difficulty completing the registration process, please call the Purchasing Division at (970) 221-6775 for assistance. RFPfor FCPS Database Conversion Project, Page 3 -- EVIDENCE -- + ACTIVITY ------ ------------------------------------------------------ Agcy FCPS Report # 03-2 Reported Date 12/31/2002 Time 23:13:26 Call Type TRESP3 Call Disposition RTF + NAME ---------------------------------------------------------------------- ;Caution Weapons Ident # :Name Type P Name CRAIG, CARRIE Race Eth Sex F + ) ------------------------------------------------------ :Category Type Location Description + ------------------------------------------------------ :Category COAT Type WINTER Color BLU/ Note DOWN -FILLED I + 11111111111MIJIM -------------------------------------------------------- :Type Modus Operandi +---------------------------------------------------------------------------- -[Fort Collins LIVE System]---------------------------[PRC Public Sector, Inc.]- ---> 1=ALIAS 2-ASSOC 3=FEATURES 4=PROP/VEH 5=NAM SUPP TABLES FIELDS # CHARACTERS XNFTCAT FEAT_CAT = Category 6 XNFTCAT FEAT TYP = Type 10 XNFTLOC FEAT LOC = Location 6 FEAT NOTE = Description 50 CAT = Category TYP = Type WOSA 10/97 10 10 COLORI = Color COLOR2 = Color NOTE = Note nmwmmmm PXMOTYP TYP = Type VALUE = Modus Operandi WOSA 10/97 23 10 25 -- EVIDENCE -- + ACTIVITY ------------------------------------ ,Agcy FCPS Report # 03-2 Reported Date 12/31/2002 Time 23:13:26 I Call Type TRESP3 Call Disposition RTF + NAME ---------------------------------------------------------------------- ;Caution Weapons Ident # ;Name Type P Name CRAIG, CARRIE Race Eth Sex F Invl Status Type Year Make EVID Y /MISCEL EVID Y /MISCEL EVID Y /MISCEL EVID Y /MISCEL EVID Y /PHOTO EVID Y /PHOTO EVID Y /MISCEL I / I / +----------------------------------------------- Model License Color -[Fort Collins LIVE System]---------------------------[PRC Public Sector, Inc.]- ---> 1=ALIAS 2=ASSOC 3=FEATURES 4=PROP/VEH 5=NAM SUPP TABLES PINAMPRP WOSA 10/97 FIELDS = Invl # CHARACTERS -- EVIDENCE -- + EVENT --------------------------------------------------------------------- Agcy FCPS Ref # 03-2 Date 12/31/2002 Time 23:13:26 Type TRESP3 + PROPERTY IN CUSTODY (S) --------------------------------------------------- ;Tag # FC119-01 Rcvd Dt 01/10/2003 Rcvd Tm 12:25 Review Dt 07/12/2003 ;Letter Prn Storage Locn E2B07 Rel OKd / ;Status EVID Type Y /MISCEL Make Model Color / Desc PLAST+ Wom --------------------------------------------+ , , Ser# Issu + CHAIN OF E; Action Date Time --------- Clerk ID In From/Out To , , ;Action D; Note ;ote , , , , +------------------------------------------------------+ , , , , , , , , -[Fort Collins LIVE System] ------------------------- [PRC/Public Mgmt. Services]- ---> 1=TAG ITEMS SEE EVIDENCE MAIN SCREEN FOR DETAILS WOSA 10/97 SERVICES AGREEMENT WORK ORDER TYPE THIS AGREEMENT made and entered into the day and year set forth below, by and between THE CITY OF FORT COLLINS, COLORADO, a Municipal Corporation, hereinafter referred to as the "City" and Provider'. WITNESSETH: hereinafter referred to as "Service In consideration of the mutual covenants and obligations herein expressed, it is agreed by and between the parties hereto as follows: 1. Services to be Performed. a. This Agreement shall constitute the basic agreement between the parties for services for The conditions set forth herein shall apply to all services performed by the Service Provider on behalf of the City and particularly described in Work Orders agreed upon in writing by the parties from time to time. Such Work Orders, a sample of which is attached hereto as Exhibit "A", consisting of (_ ) page[s], and incorporated herein by this reference, shall include a description of the services to be performed, the location and time for performance, the amount of payment, any materials to be supplied by the City and any other special circumstances relating to the performance of services. No workorder shall exceed $ . The only services authorized under this agreement are those which are performed after receipt of such Work Order, except in emergency circumstances where oral work requests may be issued. Oral requests for emergency actions will be confirmed by issuance of a written Work Order within two (2) working days. WOSA 10197 b. The City may, at any time during the term of a particular Work Order and without invalidating the Agreement, make changes within the general scope of the particular services assigned and the Service Provider agrees to perform such changed services. 2. Changes in the Work. The City reserves the right to independently bid any services rather than issuing work to the Service Provider pursuant to this Agreement. Nothing within this Agreement shall obligate the City to have any particular service performed by the Service Provider. 3. Time of Commencement and Completion of Services The services to be performed pursuant to this Agreement shall be initiated as specified by each written Work Order or oral emergency service request. Oral emergency service requests will be acted upon without waiting for a written Work Order. Time is of the essence. 4. Contract Period. [Option 1] This Agreement shall commence upon the date of execution shown on the signature page of this Agreement and shall continue in full force and effect for one (1) year, unless sooner terminated as herein provided. In addition, at the option of the City, the Agreement may be extended for an additional period of one (1) year at the rates provided with written notice to the professional mailed no later than 90 days prior to contract end. 4. Contract Period. [Option 2] This Agreement shall commence 2000, and shall continue in full force and effect until , 2000, unless sooner terminated as herein provided. In addition, at the option of the City, the Agreement may be extended for additional one year periods not to exceed _ (_) additional one year periods. Pricing changes shall be negotiated by and agreed to by both parties and may not exceed the Denver - Boulder CPI-U as published by the Colorado State Planning and Budget Office. Written notice of renewal shall be provided to the Service Provider and mailed no later than 90 days prior to contract end. WOSA 10/97 5. Delay. If either party is prevented in whole or in part from performing its obligations by unforeseeable causes beyond its reasonable control and without is fault or negligence, then the party so prevented shall be excused from whatever performance is prevented by such cause. To the extent that the performance is actually prevented, the Service Provider must provide written notice to the City of such condition within fifteen (15) days from the onset of such condition. 6. Early Termination by City/Notices. Notwithstanding the time periods contained herein, the City may terminate this Agreement at any time without cause by providing written notice of termination to the Service Provider. Such notice shall be mailed at least fifteen (15) days prior to the termination date contained in said notice unless otherwise agreed in writing by the parties. All notices provided under this Agreement shall be effective when mailed, postage prepaid and sent to the following address: City Service Provider In the event of early termination by the City, the Service Provider shall be paid for services rendered to the termination date, subject only to the satisfactory performance of the Service Provider's obligations under this Agreement. Such payment shall be the Service Provider's sole right and remedy for such termination. 7. Contract Sum. This is an open-end indefinite quantity Agreement with no fixed price. The actual amount of work to be performed will be stated on the individual Work Orders. The City makes no guarantee as to the number of Work Orders that may be issued or the actual amount of services which will in fact be requested. No Work Order of or more shall be issued. WOSA 10/97 8. Payments. a. The City agrees to pay and the Service Provider agrees to accept as full payment for all work done and all materials furnished and for all costs and expenses incurred in performance of the work the sums set forth for the hourly labor rate and material costs, with markups, stated within the Bid Schedule Proposal Form, attached hereto as Exhibit "B", consisting of (_) page[s], and incorporated herein by this reference. b. Payment shall be made by the City only upon acceptance of the work by the City and upon the Service Provider furnishing satisfactory evidence of payment of all wages, taxes, supplies and materials, and other costs incurred in connection with the performance of such work. 9. City Representative. The City's representative will be shown on the specific Work Order and shall make, within the scope of his or her authority, all necessary and proper decisions with reference to the work requested. All requests concerning this Agreement shall be directed to the City Representative. 10. Independent Contractor. It is agreed that in the performance of any services hereunder, the Service Provider is an independent contractor responsible to the City only as to the results to be obtained in the particular work assignment and to the extend that the work shall be done in accordance with the terms, plans and specifications furnished by the City. 11. Personal Services. It is understood that the City enters into the Agreement based on the special abilities of the Service Provider and that this Agreement shall be considered as an agreement for personal services. Accordingly, the Service Provider shall neither assign any responsibilities nor delegate any duties arising under the Agreement without the prior written consent of the city. 12. Acceptance Not Waiver. The City's approval or acceptance of, or payment for any of the services shall not be construed to operate as a waiver of any rights under the Agreement or of any cause of action arising out of the performance of this Agreement. WOSA 10/97 13. Warranty. (a) Service Provider warrants that all work performed hereunder shall be performed with the highest degree of competence and care in accordance with accepted standards for work of a similar nature. (b) Unless otherwise provided in the Agreement, all materials and equipment incorporated into any work shall be new and, where not specified, of the most suitable grade of their respective kinds for their intended use, and all workmanship shall be acceptable to City. (c) Service Provider warrants all equipment, materials, labor and other work, provided under this Agreement, except City -furnished materials, equipment and labor, against defects and nonconformances in design, materials and workmanship/workwomanship for a period beginning with the start of the work and ending twelve (12) months from and after final acceptance under the Agreement, regardless whether the same were furnished or performed by Service Provider or by any of its subcontractors of any tier. Upon receipt of written notice from City of any such defect or nonconformances, the affected item or part thereof shall be redesigned, repaired or replaced by Service Provider in a manner and at a time acceptable to City. 14. Default. Each and every term and condition hereof shall be deemed to be a material element of this Agreement. In the event either party should fail or refuse to perform according to the terms of this agreement, such party may be declared in default thereof. 15. Remedies. In the event a party has been declared in default, such defaulting party shall be allowed a period of ten (10) days within which to cure said default. In the event the default remains uncorrected, the party declaring default may elect to (a) terminate the Agreement and seek damages; (b) treat the Agreement as continuing and require specific performance; or (c) avail himself of any other remedy at law or equity. If the non -defaulting party commences legal or equitable actions against the defaulting party, the defaulting party shall be liable to the non -defaulting party for the non -defaulting party's reasonable attorney fees and costs incurred because of the default. 16. Binding Effect. This writing, together with the exhibits hereto, constitutes the entire agreement between the parties and shall be binding upon said parties, their officers, WOSA 10/97 employees, agents and assigns and shall inure to the benefit of the respective survivors, heirs, personal representative, successors and assigns of said parties. 17. Indemnity/Insurance. a. The Service Provider agrees to indemnify and save harmless the City, its officers, agents and employees against and from any and all actions, suits, claims, demands or liability of any character whatsoever, brought or asserted for injuries to or death of any person or persons, or damages to property arising out of, result from or occurring in connection with the performance of any service hereunder. b. The Service Provider shall take all necessary precautions in performing the work hereunder to prevent injury to persons and property. c. Without limiting any of the Service Provider's obligations hereunder, the Service Provider shall provide and maintain insurance coverage naming the City as an additional insured under this Agreement of the type and with the limits specified within Exhibit "D", consisting of ( ) page[s], attached hereto and incorporated herein by this reference. The Service Provider before commencing services hereunder, shall deliver to the City's Director of Purchasing and Risk Management, 215 N. Mason, PO Box 580, Fort Collins, Colorado 80522 one copy of a certificate evidencing the insurance coverage required from an insurance company acceptable to the city. 18. Entire Agreement. This Agreement, along with all Exhibits and other documents incorporated herein, shall constitute the entire Agreement of the parties. Covenants or representations not contained in this Agreement shall not be binding on the parties. 19. Law/Severability. This Agreement shall be governed in all respect by the laws of the State of Colorado. In the event any provision of this Agreement shall be held invalid or unenforceable by any court of competent jurisdiction such holding shall not invalidate or render unenforceable any other provision of this Agreement. WOSA 10/97 SECTION I PROPOSAL INFORMATION Section I provides general information to potential vendors on subjects such as where to submit proposals, number of copies, amendments, proprietary information designation, and other similar administrative elements. 1.1 PRE -PROPOSAL CONFERENCE A pre -proposal conference will not be held on this project. All questions prior to submission of your proposal should be sent in writing via email to Susan Neiman, sneiman(a)_fcgov.com, Fort Collins Police Services (FCPS) Records Manager. 1.2 SUBMISSION OF PROPOSAL a. Sealed offers are to be submitted to: Mr. James B. O'Neill, II CPPO, FNIGP The City of Fort Collins Purchasing Department 215 N. Mason Street, 2Id Floor PO Box 580 Fort Collins, CO 80522-0580 *********************NO LATE OFFERS WILL BE ACCEPTED****************** b. Date/Time: Proposals shall be received on or before 3:00 p.m., October 24, 2003. 1.3 NUMBER OF COPIES Vendor shall submit one original set and six (6) copies of proposal documents. This will greatly facilitate the evaluation process. The proposal shall remain the property of the City of Fort Collins (The City). 1.4 PROPOSAL INFORMATION • All questions regarding proposal preparation, the selection process, specifications and interpretations of the terms and conditions of the RFP shall be submitted in writing no later than seven (7) calendar days prior to the deadline for submission of offers. • Following the award of a contract, responses to this solicitation may be subject to release as public information unless the response or specific parts of the response can be shown to be exempt from public information. Vendors are advised to consult with their legal counsel regarding disclosure issues and take the appropriate precautions to safeguard trade secrets or any other proprietary information. The City of Fort Collins assumes no obligation or responsibility for asserting legal arguments on behalf of potential vendors. • This is not a public bid opening, therefore, the City of Fort Collins will not release any information pertaining to the number of offers received, names of vendors, or pricing until an award is made. The City of Fort Collins will confirm receipt of your proposal if requested. RFP for FCPS Database Conversion Project; Page 5 20. Special Provisions. [Optional] Special provisions or conditions relating to the services to be performed pursuant to this Agreement are set forth in Exhibit _, consisting of ( ) page[s], attached hereto and incorporated herein by this reference. CITY OF FORT COLLINS, COLORADO a municipal corporation By: John F. Fischbach City Manager By: James B. O'Neill II, CPPO Director of Purchasing and Risk Management Date: ATTEST: City Clerk APPROVED AS TO FORM: Assistant City Attorney [INSERT CORPORATIONS NAME] or [Insert Partnership name] or [Insert individual's name] Doing business as [Insert name of business] By: PRINT NAME CORPORATE PRESIDENT OR VICE PRESIDENT Date: ATTEST: CORPORATE SECRETARY WOSA 10/97 (Corporate Seal) WORK ORDER FORM PURSUANT TO AN AGREEMENT BETWEEN THE CITY OF FORT COLLINS AND DATED: Work Order Number: Purchase Order Number: Project Title: Commencement Date: Completion Date: Maximum Fee: (time and reimbursable direct costs): Project Description: Scope of Services: Acceptance _ User Service Provider agrees to perform the services identified above and on the attached forms in accordance with the terms and conditions contained herein and in the Services Agreement between the parties. In the event of a conflict between or ambiguity in the terms of the Services Agreement and this work order (including the attached forms) the Services Agreement shall control. The attached forms consisting of (_) pages are hereby accepted and incorporated herein by this reference, and Notice to Proceed is hereby given. Service Provider By: City of Fort Collins By: Date: RFP for Police Database Conversion Project, Page 133 Jim O'Neill -,Re: Database Proposals Page 1 ` From: Jim O'Neill To: Susan Neiman Subject: Re: Database Proposals Thanks. >>> Susan Neiman 11/05/03 09:58AM >>> Jim, We are evaluating at this point whether we want to proceed with this project due to the proposed costs coming back so high -- viable candidates range from $150,000 to $454,000. 1 should know by the end of the week which direction we'll be heading. Susan:-) >>> Jim O'Neill 11/5/2003 9:48:57 AM >>> Susie, How are the ratings coming? I don't have any finished rating sheets back from anybody yet. Jim 1.5 CONFIDENTIAL OR PROPRIETARY INFORMATION If a vendor believes that parts of an offer are confidential, then the vendor must so specify. The vendor must stamp in bold letters the term CONFIDENTIAL on that part of the offer, which the vendor believes to be confidential. The vendor must submit in writing specific detailed reasons, including any relevant legal authority, stating why the vendor believes the material to be confidential. Vague and general claims as to confidentiality will not be accepted. The City of Fort Collins will be the sole judge as to whether a claim is general and/or vague in nature. All offers and parts of offers, which are not marked as confidential, will be automatically considered public information after the contract is awarded. The successful offer may be considered public information even though parts are marked confidential. 1.6 AMENDMENTS In the event that it becomes necessary to revise any part of this RFP, or if additional information is necessary to enable the vendor to make an adequate interpretation of this RFP, a supplement to the RFP will be provided to each vendor. Amendments to this RFP may be issued at any time prior to the time set for receipt of proposals. The vendors are required to acknowledge receipt of any amendments by submitting a signed copy of each. amendment issued. Signed copies must be submitted as part of the signed proposal submittal. 1.7 WITHDRAWAL OR MODIFICATION OF OFFERS Any vendor may modify or withdraw an offer in writing at any time prior to the deadline for submission of an offer (see 1.2 above). Any request for withdrawal of an offer must be signed by the individual who signed the initial proposal submittal. 1.8 ACCEPTANCE • Any offer received shall be considered an offer, which may be accepted by the City of Fort Collins based on initial submission without discussions or negotiations. • Acceptance time. By submitting an offer in response to this solicitation the vendor agrees that any offer it submits may be accepted by the City of Fort Collins at anytime within 90 days from the date of submission deadline (see 1.2 above.) • The City of Fort Collins reserves the right to reject any or all offers and to waive informalities and minor irregularities in offers received, and/or to accept any portion of the offer if deemed in the best interest of the City of Fort Collins. Failure of the vendor to provide in its offer any information requested in the RFP may result in rejection for non -responsiveness. 1.9 PROPOSAL PREPARATION COST The cost of proposal preparation is not a reimbursable cost. Proposal preparation costs shall be at the vendor's expense and are the vendor's total responsibility. 1.10 AWARD The City of Fort Collins intends to make an award using the evaluation criteria listed in the RFP to determine the Best Value, including financial proposal and other factors in the proposal submitted. See Section IV for Evaluation Elements. 1.11 CONTRACT ADMINISTRATION The City of Fort Collins Police Records Division shall be responsible for administration of the contract for compliance with the interpretation of scope, schedule, budget, construction and quality of services and product. RFP for FCPS Database Conversion Project; Page 6 1.12 SUBSTANTIVE PROPOSALS The respondent shall certify (a) that his/her proposal is genuine and is not made in the interest of, or on behalf of, any undisclosed person, firm, or corporation; (b) that s/he has not directly or indirectly induced or solicited any other respondent to put in a false or sham bid; (c) that s/he has not solicited or induced any other person, firm, or corporation from proposing; and (d) that s/he has not sought by collusion to obtain for himself any advantage over any other respondents or over the City of Fort Collins. 1.13 GOVERNING LAW The laws of the State of Colorado shall govern any contract executed between the successful consultant and the City of Fort Collins. Further, the place of performance and transaction of business shall be deemed to be in the County of Larimer, State of Colorado, and in the event of litigation, the exclusive venue and place of jurisdiction shall be the District Court of the Eighth Judicial District, Larimer County, Colorado. 1.14 INQUIRIES Questions about the RFP shall be in writing and directed to Susan Neiman, at the following address or email sneiman6a' fcgov.com. A written response to any inquiry will be provided in the form of an Amendment to the solicitation to each vendor. Questions concerning the proposal process or contractual questions shall be addressed to Mr. Jim O'Neill. Susan Neiman Records Manager Fort Collins Police Services 300 Laporte Avenue Fort Collins, CO 80521 (970)221-6825 Mr. James B. O'Neill, II CPPO, FNIGP The City of Fort Collins Purchasing Department 215 N. Mason Street, 2"d Floor PO Box 580 Fort Collins, CO 80522-0580 RFP for FCPS Database Conversion Project; Page 7 SECTION II MINIMUM SPECIFICATIONS 2.0 BACKGROUND The Fort Collins Police Services Records Division is responsible for entry of all data into a Records Management System. The Records Division currently uses a PRC Records Management System that no longer meets their functional, business rules, and performance needs. The current system has been in use for more than 10 years. A new system is being purchased with installation and implementation scheduled approximately the second quarter of 2004. The vendor of the new Records Management System is Tiburon, Inc. 2.1 OBJECTIVES 2.1.1 Data Migration The vendor shall successfully move all legacy data into the new relational database. The specific methods will be discussed during the design review meeting with stakeholders, users, and managers. 2.1.2 Maintenance The vendor shall provide technical support for a two -month period after the client accepts the final product. A "burn -in" period warranty shall be included in the vendors' proposal for 21 days after installation of the final product. During this time all "bugs" not previously found will be corrected by the vendor prior to initiation of the maintenance period. 2.2 ADDITIONAL INFORMATION/EXPECTATIONS It is expected that the vendor will complete all work within 180 work days (— 6 months; M-F). After the project kick-off meeting, on -time weekly status reports (WSR) shall be emailed to the FCPS project manager (FPM) no later than 10AM each Friday until the contract closure. Communication is essential to the success of this project and we expect the vendor Project Manager (PM) to report issues that affect, scope, schedule, or contract performance to the FPM as soon as possible. The vendor PM shall maintain a project schedule and risk management plan. The vendor shall provide to the FPM every three weeks an account of all internal hours expended by name, rate, hours, and grand total. Finally we expect that the vendor assembled project team will remain on the project until the FPM accepts the final product. A request must be submitted prior to and approved by the FPM for any staff changes. All project documentation and products will become the sole property of the Fort Collins Police Department. The vendor will provide a CD-ROM with all project documentation, source code, product installation program, and executables to the FPM at contract closure. All scope changes shall be provided to the FPM in written form — Request for Change (RFC). The vendor cannot begin work on an un-approved RFC. Approval of all RFCs will carry the signature of the FCPS Project Manager. The Fort Collins Police Department will provide facilities, work surface and network access at the Police Operations Center (POC) located at 300 Laporte Avenue, Fort Collins, Colorado. At least 50% of all vendor project work must occur at the POC. 2.3 DELIVERABLES 1) Updated Requirements Specification 2) Test Plan & Procedures Document 3) Design Documentation for all developed databases, stored procedures, views, web - application, reports, database table layout and data dictionary. RFPfor FCPS Database Conversion Project; Page 4) Legacy data conversion and migration 5) Maintenance & Technical Support/SLA for 2 months. 6) CD-ROM with all as -built project documents, source code, and executables. 2.4 BUDGET The City of Fort Collins has funding allocated for this project. 2.5 SCHEDULE We expect the vendor will begin work on this project within 14 work days after contract award. The kick-off meeting will be scheduled by the vendor PM and will occur at the POC. An agenda shall be provided prior to the meeting and provided to the FPM in advance of the meeting. 2.6 BILLING/DELIVERY INFORMATION An invoice shall be submitted at major project milestones as defined by the Police FPM. All invoices shall contain the following information: Name of the vendor, contract number, itemized list of services/supplies furnished, and date of services/supplies furnished. All invoices shall be billed on a net 30 basis. No late charges shall be assessed to, or paid by the City of Fort Collins Police Department. Unless otherwise notified in writing, all work produced shall be delivered to the City of Fort Collins Police Department, 300 Laporte Avenue, Fort Collins, CO 80521. RFP for FCPS Database Conversion Project: Page 9 SECTION III PROPOSAL CONTENT 3.0 PROPOSAL FORMAT Your written proposal should include the information in the format outlined below and is limited to no more than 50 pages. We recommend that you include concise, but complete information about your firm, emphasizing why you believe your firm to be uniquely qualified for this operation. Short listed firms may be required to make a formal; in person presentation to the selection committee. The City of Fort Collins reserves the right to make a selection of the successful bidder from the original proposal submittals. 3.1 ORGANIZATIONAL BACKGROUND AND OVERVIEW Provide a brief history and overview of your company and its organizational structure, with special emphasis on your understanding of the project and how your company proposes to fulfill the needs of the Fort Collins Police Department, including the following information; • Name, address, and telephone number of the firm. • Type of organization (individual, partnership, corporation, or other) • Principals of your firm. 3.2 STATEMENT OF QUALIFICATIONS Submit a general description of your background and experience, on a company -wide basis, with accounts similar to this. Provide the name, address and telephone number of three (3) locations at which your organization is currently operating along with specific individuals whom we may contact for references. • List the three current projects with contact information under contract by your firm that are also being handled by the personnel that will be assigned to this project, including name, type, location, estimated construction cost, and percent of completion. • Discuss your firm's knowledge and experience in use of relational database technology. • Include any other information that you feel is appropriate to assist the Fort Collins Police Department in selecting your firm for the project. 3.3 AVAILABILITY OF STAFF & RESOURCES The City of Fort Collins is interested in ascertaining that the successful vendor has the necessary staff and resources to take on this project immediately to insure timely completion. The following questions must be addressed; • A proposed time schedule indicating your firm's capability of performing the required tasks in a timely manner. • Would your firm, associates, and consultants be readily available to begin this project immediately should this project be awarded to your firm? • Could your firm give uninterrupted and continuous service by one team or group until the work is complete? • Does your firm have adequate technical and financial resources to perform the tasks in a timely manner? 2/9/00 5. For the current PRC Tri-fox database, do you have tools for querying data (i.e. SQL Plus, other SQL tools)? We currently use SQL and SQL plus as querying tools for the PRC database. 6. Is the Oracle 9i instance the Enterprise edition or is it the Standard edition? At this point, we anticipate it to be the Enterprise edition. However, we have not proceeded far enough in the implementation of the new RMS system with Tiburon to know this information. 7. How many licensed users do you have for Oracle 90 This has not been determined yet. 8. The RFP refers primarily to conversion of the PRC system into the Tiburon system Section VII also identifies the JMS and RMS (Unisys) systems. Are all three systems part of the conversion scope? The scope of this project is for conversion from the PRC system into the Tiburon system. However, the JMC and RMS (Unisys) systems were included if Larimer County Sheriff's Office determines that they need to convert data from these systems. But these systems should not be included as part of the RFP response. 9. Is a backup strategy for the new system part of the scope of this effort, or is that handled by the Tiburon vendor? Backup of the new Tiburon system will be handled by Tiburon, Inc. 10. Are the old and new systems 24x7 production systems? Yes, the old system is currently a 24X7 production system and the new system will be 24X7 as well. RECEIPT OF THIS ADDENDUM MUST BE ACKNOWLEDGED BY A WRITTEN STATEMENT ENCLOSED WITH THE BID/QUOTE STATING THAT THIS ADDENDUM HAS BEEN RECEIVED. 3.4 TECHNICAL EXPERTISE In order to evaluate the depth of your technical expertise, please provide information on the following: • Provide a work plan, which addresses the scope of service; describe your proposed approach to the task, the methodology to be followed, and a proposed schedule. • A description of the technology to be used to develop and deliver the respective programs. • Qualifications of personnel and experience developing web sites. • An overview of the type and content of each deliverable. • A detailed schedule and time estimate or a proposed timeline using a Gantt chart format and a budget breakdown by task. No subcontractors will be allowed on this project. Describe your strategy for migrating non -relational data to a newly modeled relational database. • What conversion tools do you intend to use, if any? What is your level of experience using these tools? What methods or techniques will be used to assure the integrity of the data that is converted? • What database environments do you support? What data modeling tools do you use? 3.5 FINANCIAL PROPOSAL Provide a financial estimate in work breakdown structure (WBS) format. 3.6 PERSONNEL Quality of personnel is of critical importance in the City of Fort Collins' decision -making process for awarding this contract. In this section, please submit the following information: a. Person to be in charge of the project. b. Resumes and functions of personnel who will be assigned to the project. 3.7 SUBMITTALS Submit six (6) copies, including all Attachments. 2/9/00 SECTION IV EVALUATION CRITERIA 4.1 EVALUATION CRITERIA Professional firms will be evaluated on the following criteria. These criteria will be the basis for review of the written proposals and interview session. The City of Fort Collins may elect to select a firm from the written proposals only. The rating scale shall be from 1 to 5, with 1 being a poor rating, 3 being an average rating, and 5 being an outstanding rating. WEIGHTING QUALIFICATION STANDARD FACTOR 2.0 Scope of Proposal Does the proposal show an understanding of the project objective, methodology to be used and results that are desired from the project? 2.0 Assigned Personnel Do the persons who will be working on the project have the necessary skills? Are sufficient people of the requisite skills assigned to the project? 1.0 Availability Can the work be completed in the necessary time? Can the target start and completion dates be met? Are other qualified personnel available to assist in meeting the project schedule if required? Is the project team available to attend meetings as required by the Scope of Work? 1.0 Motivation Is the firm interested and are they capable of doing the work in the required time frame? 2.0 Cost and Do the proposed cost and work hours compare Work Hours favorably with the project Manager's estimate? Are the work hours presented reasonable for the effort required in each project task or phase? 2.0 Firm Capability Does the firm have the support capabilities the assigned personnel require? Has the firm done previous projects of this type and scope? 2i9i00 Reference evaluation (Top Ranked Firm) The project Manager will check references using the following criteria. The evaluation rankings will be labeled Satisfactory/Unsatisfactory. QUALIFICATION STANDARD Overall Performance Would you hire this Professional again? Did they show the skills required by this project? Timetable Was the original Scope of Work completed within the specified time? Were interim deadlines met in a timely manner? Completeness Was the Professional responsive to client needs; did the Professional anticipate problems? Were problems solved quickly and effectively? Budget Was the original Scope of Work completed within the project budget? Job Knowledge a) If a study, did it meet the Scope of Work? b) If Professional administered a construction contract, was the project functional upon completion and did it operate properly? Were problems corrected quickly and effectively? The City of Fort Collins reserves the right to reject any and all proposals and to waive any formality in proposals received, to accept or reject any or all of the items in the proposal, and award the job in whole or in part, if it is in the best interest of the City of Fort Collins. 4.2 SELECTION -COMMITTEE A Selection Committee will screen all submissions. Proposals will be ranked according to evaluation criteria, as outlined in the Request for Proposal. Through this process, the City of Fort Collins will determine which proposals are acceptable or unacceptable. The City of Fort Collins, in writing, will notify participating firms whose proposals are deemed to be unacceptable. Those firms submitting proposals deemed to be acceptable by the City of Fort Collins will be evaluated by the Selection Committee. The Selection Committee may determine it necessary to require "oral presentations/interviews" with the "short listed" firms WOSA 10/97 considered to be in the competitive range. If oral presentations/interviews are conducted they will also be scored. The committee may request revisions to the proposal from each of the vendors at the conclusion of the interviews. However, if it is determined necessary to seek revisions to the proposals at the conclusion of interviews, then all vendors interviewed will be requested to submit revisions, and the revisions will be scored accordingly. 4.3 AWARD OF CONTRACT The City of Fort Collins reserves the right to award this Contract not necessarily to the firm with the most advantageous financial proposal, but to the firm that demonstrates the best ability to fulfill the requirements of this Request for Proposal that are determined to be the most advantageous to the City of Fort Collins. The City of Fort Collins will select the most qualified firm, and a contract prepared by the City of Fort Collins will be negotiated with the top ranked firm as selected by the committee. In the event a contract cannot be negotiated with the top ranked firm, the City of Fort Collins may enter into negotiations with the second highest ranked firm or the City of Fort Collins may decide to call for new proposals. Immediately after the notice of Award, the Vendor will begin planning in conjunction with the Fort Collins Police Department staff to insure fulfillment of all its obligations. WOSA 10/97 SECTION V CONTRACT TERMS AND CONDITIONS/APPENDICES 5.1 INDEPENDENT CONTRACTOR In the performance of the Vendor's obligations under this Contract, it is understood, acknowledged and agreed between the parties that the Vendor is at all times acting and performing as an Independent Contractor, and the City of Fort Collins shall neither have nor exercise any control or direction over the manner and means by which the Vendor performs the Vendor's obligations under this Contract, except as otherwise stated within the Contract terms. The Vendor understands and agrees that the Vendor and the Vendor's employees, agents, servants, or other personnel are not City of Fort Collins employees. The Vendor shall be solely responsible for payment of salaries, wages, payroll taxes, unemployment benefits or any other form of compensation or benefit to the Vendor or any of the Vendor's employees, agents, servants or other personnel performing services or work under this Contract, whether it is of a direct or indirect nature. Further in that regard, it is expressly understood and agreed that for such purposes neither the Vendor nor the Vendor's employees, agents, servants nor other personnel shall be entitled to any City of Fort Collins payroll, insurance, unemployment, worker's compensation, retirement or any other benefits whatsoever. 5.2 NON -WAIVER OF RIGHTS No waiver of default by the City of Fort Collins of any of the terms, covenants, and conditions hereof to be performed, kept, and observed by the Vendor shall be construed, or shall operate, as a waiver of any subsequent default of any of the terms, covenants, or conditions herein contained to be performed, kept, and observed by the Vendor. 5.3 INTEGRATION This is a completely integrated Agreement and contains the entire agreement between the parties. Any prior written or oral agreements or representations regarding this Agreement shall be of no effect and shall not be binding on Vendor or the City of Fort Collins. Further, Vendor and the City of Fort Collins acknowledge and agree that this is a negotiated text agreement, and that as such no term shall be construed against the City of Fort Collins as the author thereof. 5.4 LAW This Contract is subject to and shall be interpreted under the law of the State of Colorado, and the Charter, City of Fort Collins Code, Ordinances, Rules and Regulations of the City of Fort Collins, Colorado, a Colorado Home Rule City. Court venue and jurisdiction shall exclusively be in the Colorado District Court for Larimer County, Colorado. The Vendor shall insure that the Vendor and the Vendor's employees, agents, and officers are familiar with, and comply with, applicable Federal, State, and Local laws and regulations as now written or hereafter amended. 5.5 APPROPRIATION OF FUNDS In accord with the Colorado Constitution and the City of Fort Collins Charter, performance of the City of Fort Collins's obligations under this Agreement is expressly subject to appropriation of funds by the City Council and the availability of those appropriated funds for expenditure. Further, in the event that funds are not appropriated in whole or in part sufficient for performance of the City of Fort Collins's obligations under this Agreement, or appropriated funds WOSA 10197 may not be expended due to Constitutional or City of Fort Collins Charter spending limitations, then the City of Fort Collins may terminate this Agreement without compensation to the Vendor. 5.6 TERMINATION The City of Fort Collins may, at its sole discretion, terminate this Agreement upon ten (10) days prior written notice to Vendor if the City of Fort Collins determines that the Vendor's performance is unsatisfactory, or that the Vendor has violated any of the terms or provisions of this Agreement; or in the event the Vendor becomes insolvent or is named as a Debtor in Bankruptcy. In the event of termination by the City of Fort Collins under this subparagraph, the Vendor, at the option of the City of Fort Collins, shall forfeit as liquidated damages all performance or other sureties given to the City of Fort Collins under this Agreement. This liquidated damage option shall be in addition to any and all remedies at law, which may be available to the City of Fort Collins. The City of Fort Collins expressly reserves the right to request correction of any breach of term or condition by the Vendor prior to exercising the City of Fort Collins's rights to terminate this Agreement. However, any request for correction shall not act to waive the City of Fort Collins's right to terminate this Agreement if the City of Fort Collins's terms of correction are not performed to the City of Fort Collins's satisfaction. If Vendor is prevented by Court Order, the City of Fort Collins, or by order of a state of Larimer County governmental authority, from doing business for a period of three (3) months through no act, fault or neglect of the Vendor or Vendor's employees or agents, then Vendor may, upon ten (10) days prior written notice to the City of Fort Collins, terminate this Agreement, in which event the provision for liquidated damages in this Agreement shall not apply. Vendor, at Vendor's sole expense, shall procure, post, and keep valid, all permits or licenses necessary for performance of this Agreement. 5.7 INDEMNIFICATION Vendor agrees that Vendor shall indemnify, defend and hold harmless the City of Fort Collins, its officers, employees and agents, from and against any and all loss, damage, injuries, claims, cause or causes of action, or any liability whatsoever resulting from, or arising out of, or in connection with the Vendor's performance under this Agreement. 5.8 ASSIGNMENT Vendor shall not assign or otherwise transfer this Agreement or any right or obligation hereunder without the prior written consent of the City of Fort Collins. WOSA 10/97 SECTION VI INSURANCE SPECIFICATION For this contract, the following provisions for insurance shall apply: Vendor shall carry, at his own expense in reliable insurance companies approved by the City of Fort Collins, the following insurance coverages with limits not less than stated below. Worker's Compensation and Employers Liability Worker's Compensation insurance, as required by statute. Employers Liability coverage is to be carried for a minimum limit of $100,000. Automobile Liability Comprehensive Automobile Liability coverage is required for limits of not less than $500,000 combined single limits for bodily injury and property damage. Automobile contractual coverage protecting the interests of the City of Fort Collins must be included. Excess or Umbrella Liability This type of coverage will be discussed with the appropriate department by the Claims and Insurance office to determine if coverage is needed and at what limits. If coverage is needed, the coverage will name the City of Fort Collins as additional insured. A Certificate of Insurance evidencing all the above coverages shall be filed with the appropriate department prior to the commencement of work. Renewal certificates and polices, as required, will be forwarded to the appropriate department for as long as vendor performs the work as specified in this contract. All certificates and policies shall contain a provision that coverages afforded will not be canceled or materially altered until at least forty five (45) days prior written notice has been given the City of Fort Collins. WOSA 10/97 SECTION VII SCOPE OF WORK PROJECT OVERVIEW Fort Collins Police Services Records Division is responsible for entry of all data into a Records Management System. The Records Division currently uses a PRC Records Management System that no longer meets their functional, business rules, and performance needs. The current system has been in use for more than 10 years. A new system is being purchased with installation and implementation scheduled during the second quarter of 2004. The vendor of the new Records Management System will be Tiburon, Inc. Fort Collins Police Services desires to convert legacy data from its current PRC Records Management System to a new Records Management System — Tiburon, Inc. This document will outline the general approach to conversion as well as provide additional information on each of the baseline conversion deliverables. CURRENT SYSTEM There is approximately eight (8) gigabytes of data stored across multiple files. These are relational files with the indices linking the various files. The data currently resides in a PRC Tri-Fox version 5.5 relational database running on Oracle version 6.4. The Tiburon, Inc. RMS system runs on an RS/6000, AIX version 4.x, stored in Oracle version 9i. All together there are approximately 130 tables, many of these with over 35 fields. This project may also require the conversion of data from the Larimer County Sheriff's Department's current RMS system and Jail Management System (JMS). There is approximately 12 gigabytes of data stored across numerous files. These are database files with the indices linking the various files. The RMS data currently resides in a Unisys DMS 1100 Hierarchical database running on a Unisys 2200/500 mainframe. The JMS data currently resides on an RS/6000 AIX version 4.X stored in Oracle 9i HACMP leveraged for failover and RMAN for Oracle system maintenance. For data conversion, Fort Collins Police Department staff will be available to work with the vendor's technical staff to assist with data mapping and decisions to resolve mapping issues. FCPS staff will also provide technical assistance, data reconciliation assistance, and conversion facilities as needed. The vendor should indicate the roles that are appropriate for FCPS participation. As part of contract negotiation with the successful vendor, FCPS may choose to convert all, some, or none of the data from the existing systems. FCPS has provided information on the volume of data below to assist the vendor in estimating the data conversion effort. (Numbers provided are approximates). • Permanent Records (i.e. homicides, sex assaults, etc. including sentencing information): 13,234 • Felony Arrests: 29,463 WOSA 10/97 • Misdemeanor Arrests: 115,160 • Known Offender/Repeat Offender: 947 • Sex Offender: 161 • Gang Records: 2,069 • Field Contact: 2,000 • Motor Vehicle Accidents: 35,000 • Traffic Citations: 44,000 • Warrants — Misdemeanor: 2,000 • Warrants — Felony 7,800 • Warnings: 3,200 • Pawns: 129,000 • Case Management: 7,700 • Police Criminal Cases (not included above: 8,828 • Police Non -Criminal Cases: 9,637 • Evidence Records: 30,000 Identification information for which an individual may have multiple instances is kept in separate name attribute files. Files currently exist for aliases, scars/marks/tattoos, vehicle operator license numbers, phone numbers, state identification numbers, federal identification numbers, etc. However, these Master Name Index (MNI) records are not part of this conversion project. NEW SYSTEM The Tiburon, Inc. RMS system is a complex database system. All together there are over 500 tables, many of these with more than 50 fields. To map to the Tiburon data dictionary it has been determined that some of the legacy data will map/filter, while some will require more intense customization. FUNCTIONAL REQUIREMENTS To the extent that Fort Collins Police Services wishes to migrate historical information from the legacy database to the new database, it will be necessary to develop and execute routines to move the data. This will require: 1. Analyzing the current file structure(s) and mapping existing data to the new structure. 2. For each new structure being populated with existing data, a detailed mapping will be documented including any transformations required between the old and new data structures. 3. Statistics regarding the data being converted will be collected. This might include the number of records, total of amount fields, number of entities, etc. This same information will be generated from the new data and compared to ensure that all data was successfully converted. 4. Developing import routines, masks, and filters to extract the data from existing files and import it into the new relational database. WOSA 10/97 5. Testing and executing the migration routines, thus loading the data into the production database. 6. For each data conversion process, an error detection strategy will be implemented with documented procedures for correcting the errors. 7. Manually correcting data anomalies that may arise because the new system's referential integrity rules were not enforced by the previous system. 8. Reports of the new data will be generated so that the information can be verified as needed. All Fort Collins Police Services requirements are met by accounting for all tables that are required by Tiburon, Inc., and by converting or continuing all data and data elements to Tiburon, Inc. Records Management System specifications. PROCESS IDENTIFICATION Data dictionaries will be provided to the successful vendor for both the PRC RMS system and the Tiburon RMS system. The data mapping effort will include but not be limited to: • The identification of PRC Records Management System tables (records) • The identification of columns (fields) • The length of each field • The identification of attributes (char, num, etc.) • Whether the data element is required, and by which system • The identification of prompt table or translate table • The default value • The field name from the PRC Records Management System legacy system • The valid values for translation tables or prompt tables • Cross reference tables - laying out how each legacy data element maps to a Tiburon, • Inc. Records Management System element • Grouping of data by functional areas for project planning and scheduling, and • Comments - identification of any special conversion rules POSSIBLE DATA MAPPING ISSUES A PRC Records Management System legacy -required data element has no corresponding Tiburon, Inc. Records Management System data element. • We can use an existing Tiburon, Inc. Records Management System data element that can be user defined and clearly documented. But this carries the risk that Tiburon, Inc. might delete this element in a later release or change its intended use. • We can choose to no longer track this element unless it is legally or otherwise externally required. • We can build our own data element and document that fact, but we must ensure that the upgrade path is not in jeopardy, use all standard naming conventions as outlined in the naming convention document, build it on our own table with a key structure that supports the table that does not have this required data element, establish if the WOSA 10/97 Administrkave Services i Purchasing Division CITY OF FORT COLLINS City of Fort Collins ADDENDUM No. 3 SPECIFICATIONS AND CONTRACT DOCUMENTS Description of Bid: P882 Database Conversion Project OPENING DATE: October 24, 2003 3:00 p.m. (Our Clock) To all prospective bidders under the specifications and contract documents described above, the following changes are hereby made. Fort Collins Questions: 1. Section II Minimum Specifications, 2.3 Deliverables. How do Deliverables 1,2,3 relate back to the SOW whose main tasks are data conversion and migration? The vendor will more than likely have specific requirements that need to be provided by the City as well as an implementation plan, test plan and procedures on how to accomplish this data conversion. The design documents are documentation for the areas described in this section. These documents will be kept as part of this project for future reference. 2. Is the requirement for Section II Deliverables 1,2,3 to develop or manage the updated requirements specification/test plan/design documentation? Yes. 3. Section 3.4 Technical Expertise, bullet 2 states " a description of the technology used to develop and deliver the respective programs". Please provide information on which respective programs relative to the database conversion and maintenance work as specified in Section VII. Instead of respective programs, it should say `....develop and complete the data conversion process. 4. Section 3.4 Technical Expertise, bullet 3 states " qualifications of personnel and experience developing web sites". Please provide information on this requirement relative to the work as specified in Section VII. This is actually an oversight on our part. This requirement is not necessary in the conversion of our database. RECEIPT OF THIS ADDENDUM MUST BE ACKNOWLEDGED BY A WRITTEN STATEMENT ENCLOSED WITH THE BID/QUOTE STATING THAT THIS ADDENDUM HAS BEEN RECEIVED. 215 North Mason Street • 2nd Floor • P.O. Box 580 • Fort Collins, CO 80522-0580 9 (970) 221-6775 • FAX (970) 221-6707 field can be updated or is view only, develop panels for updating or viewing, determine what menu bar item allows you to update or view, and establish security. The danger is that Tiburon, Inc. can choose to delete this in a later release. A PRC Records Management System legacy data element is split into two or more Tiburon, Inc. data elements. • We can develop a value -specific mapping/matrix table using appropriate mapping criteria. A Tiburon, Inc. Records Management System required data element has no corresponding PRC Records Management System legacy data element. • Depending on the default value it may be possible to leave the field blank or null. If this is impossible, document the rules for filling or converting this field. SCHEDULE We expect the vendor will begin work on this project within 14 work days after contract award. The kick-off meeting will be scheduled by the vendor PM and will occur at an FCPS facility. An agenda shall be provided prior to the meeting and provided to the TPM in advance of the meeting. CONVERSION DELIVERABLES The following deliverables will be completed as a part of this data conversion project: • Data mapping documents • Conversion extract programs • Data validation reports that can be used to assist any data cleanup efforts. CONCLUSION While some details remain to be worked out, this document should effectively represent the substantive requirements for the system. WOSA 10197 FORT COLLINS POLICE SERVICES DATA CONVERSION STRATEGY WOSA 10/97 Overview Tiburon, Inc. Records Management System (RMS) has proposed to replace the existing PRC Records Management (PRC) legacy system. This document describes the strategy for migrating data from the legacy system into the proposed Tiburon, Inc. RMS database. Details of the system that need to be converted are provided in this document. This document will be the baseline for planning and implementation of data conversion for this project. 1.DEFINITIONS Business Rules Guidelines for transactions in database, covering data type, data length and valid range of values. Business rules are in sync with business processes and help maintain database integrity. Data Conversion Process involving rollout replacing the legacy systems Transition Strategy Data Dictionary A data dictionary defines each term encountered during the analysis and design of a system and primarily records the information content of data. Data Purification Process of correcting any legacy data, not conforming to business rules identified during data conversion. Edits Report, generated in the process of data conversion, that lists data suspected to be incorrect. Flat File Intermediate file between legacy system data and Tiburon, Inc. RMS database facilitating data migration from legacy system to Tiburon, Inc. RMS system in ASCII format Rollout Application implementation on production environment encompassing data, code, locations and setup parameters. Data Mapping The identification of PRC Records Management System legacy data elements to be converted. The mapping of the PRC Records Management System legacy data elements and data to Tiburon, Inc. Records Management System data elements. The establishment of data conversion rules. Legacy Data Data used by an existing, legacy system, which must be cleansed and converted for use by a new application. 2. DATA CONVERSION OBJECTIVE The objective of the conversion is to centralize the information for the new system. The existing data shall be converted to Tiburon, Inc. RMS database as per scope defined in the RFP. The process therefore involves the transformation of data from its current legacy WOSA 10/97 format and storage media into a new application's format and storage media. Data conversion activity is usually concurrent with the new system design and development activity and is performed by a small team of people. Depending on the data volume the size of the team may be increased. 3. RESOURCES The resources required for data conversion cycle are as follows: 3.1 Environment (Hardware & Software) • Access to legacy and Tiburon, Inc. system databases for conversion runs. • PRC Records Management System operates using an Oracle Rdb on a VAX platform. • LCSO Records Management System operates using a Unisys DMS 1100 hierarchical database running on a Unisys 2200/500 mainframe. • Tiburon, Inc. Records Management System operates using a Tiburon/Oracle 9i on an IBM RS 600. 3.2 Data Conversion Team The team will be lead by Fort Collins Police Department Records Manager, Susan Neiman and assisted by a. Personnel — yet to be identified. 4. DATA CONVERSION CURRENT ENVIRONMENT Legacy system data, which need to be converted for this project, are in an Oracle Rdb platform or a Unisys DMS 1100 hierarchical database. This legacy data shall be migrated to the new Tiburon/Oracle 9i database. 5. DATA PREPARATION Once the source data to be converted has been identified, it must be prepared for conversion. For conversion efforts, conversion -ready data does not have to reside in a single file. The program may be designed to create multiple files during the formatting process, each file containing only data pertinent to a single or related set of destination tables. Smaller file sizes are more manageable and will result in faster conversion processing. Also, the data preparation itself may be broken into multiple programs based on the destination table or tables. Data clean up can be a very time-consuming task of the conversion project. One method of mitigating this task is to cleanse the data via a data preparation/extract program. This program would contain more logic to ensure data validity and thus take a longer time to program and test but would reduce back -end time during the data cleaning effort. Another option to lessen the data cleansing effort for the conversion team is to create a report for review by appropriate functional experts, technical experts, employees, and/or WOSA 10/97 managers. These reports can be used for data verification and correction before the data is actually written to the database. For source data known or discovered to be invalid, steps may be taken to correct them on the originating system first, before being prepared for conversion. 6. DATA PURIFICATION During the conversion process, after the business rules to be applied on the data to be converted are established, any data, which is migrated from legacy systems to Tiburon, Inc. RMS system and does not conform to the business rules, is considered potentially impure/invalid. Such "suspect' data would be identified and corrected in the legacy systems by the FCPS team. The Vendor would provide information and/or print outs of such suspect data to the team. The team would review the information, research, and correct erroneous data in the source systems. The data conversion process would be iterated to make the data as pure as possible. If any impure/invalid data is identified after the final conversion into Tiburon, Inc. RMS production database, the Vendor would facilitate/guide the FCPS team to correct the data in Tiburon, Inc. RMS database itself. 7. DATA CONVERSION ISSUE RESOLUTION Conversion issues can be classified as the following types: • Problems due to faulty/incomplete logic in the conversion programs. In such a case, the Vendor shall resolve these problems by correcting the programs and re -executing the conversion programs. • Data inconsistency in the legacy system database. These types of problems will be handled by FCPS personnel prior to the actual conversion. All such data issues need to be corrected on the legacy database so as to avoid recurrence at the time of production data conversion. However, if such problems are found even after the actual conversion is completed in the live database, FCPS personnel shall have to resolve these problems via manual data entry / correction at the backend. The Vendor shall facilitate/guide FCPS personnel in doing so. All the data that is inherently erroneous may conform to the business rules and therefore remain uncorrected during the transition to the Tiburon, Inc. RMS system. For instance, the social security number of a participant should be in the format of 123456789. The business rules enforced would validate whether the social security number is in the format specified, but it cannot ensure that the contents of social security number of the participant is in fact correct and belongs to the said participant. Such type of errors can be corrected whenever identified during and after Tiburon, Inc. RMS system implementation by the FCPS team. The Vendor would facilitate the correction of such errors. • A PRC Records Management System legacy -required data element has no corresponding Tiburon, Inc. Records Management System data element. WOSA 10/97 We can use an existing Tiburon, Inc. RMS system data element that can be user defined and clearly documented. But this carries the risk that Tiburon, Inc. might delete this element in a later release or change its intended use. We can choose to no longer track this element unless it is legally or otherwise externally required. We can build our own data element and document that fact, but we must - ensure that the upgrade path is not in jeopardy, use all standard naming conventions as outlined in the naming convention document, build it on our own table with a key structure that supports the table that does not have this required data element, establish if the field can be updated or is view only, develop panels for updating or viewing, determine what menu bar item allows you to update or view, and establish security. The danger is that Tiburon, Inc. can choose to delete this in a later release. • A PRC RMS System legacy data element is split into two or more Tiburon, Inc. data elements. We can develop a value -specific mapping/matrix table using appropriate mapping criteria. • A Tiburon, Inc. RMS System required data element has no corresponding PRC RMS System legacy data element. Depending on the default value it may be possible to leave the field blank or null. If this is impossible, document the rules for filling or converting this field. • Problems as a result of field length differences (i.e. 12 characters in PRC vs. 10 characters in Tiburon). In such a case, the Vendor shall provide solution recommendations. 8. DATA CONVERSION TRANSITION STRATEGY Transition Strategy can be classified as the following two types: • Identify and prepare a fallback / contingency plan for data conversion. The actual process of data conversion will be carried out based on the rollout strategy, which would be finalized prior to implementation of Tiburon, Inc. RMS system by the Vendor and FCPS teams. Depending on the rollout strategy, conversion can be carried out by regions. The conversion strategy would be synchronized with the rollout strategy. In the event of any unforeseen problems in the conversion process, the rollout plan would have to be re -scheduled. • Identify the elements of systems / applications which need to run during the transition from legacy to the Tiburon, Inc. RMS system. WOSA 10/97 Typically, conversion would be carried either on a weekend or a holiday. During this period business users would be denied access to legacy system. There are various data staging tools available in the market which can cater to this requirement. These staging tools can automate some of the critical tasks like updating incremental data from legacy systems to the Tiburon, Inc. RMS database, facilitating synchronized update, and unhindered reporting during the rollout of Tiburon, Inc. RMS. 9. DATA CONVERSION STRATEGY The Vendor in coordination with the FCPS team would adapt the following approach for converting the legacy systems identified in the RFP. The conversion activities have been classified into three broad categories. • Initial Preparation & Planning • Transformation of Data • Final Conversion # ACTIVITIES TO BE PERFORMED RESPONSIBILITY Initial Preparation & Planning 1. Identify conversion & data validation team consisting of Vendor/FCPS personnel as stated in the strategy. 2. Identify all data / computerized files to be converted. Vendor/FCPS 3. Provide list of all databases duly identifying the data FCPS elements stored. 4. Provide legacy database structures & data dictionary to FCPS the Vendor. 5. Provide sample listing of all mainframe databases and Vendor/FCPS files in ASCII format with file layout. 6. Identify validation rules/controls that are to be Vendor/FCPS established at table/column level. 7. Design intermediary tables based on the data dictionary Vendor structures with all the business rules. 8. Provide the intermediary table structures (replica of Vendor Legacy system) for review and verification with business rules to FCPS. 9. Map old database structures with the intermediary table Vendor/FCPS structures. 10. Identify all System Generated Ids / #s that need to be Vendor/FCPS generated. 11. Identify a scheme for mapping existing legacy system Vendor/FCPS master codes to Tiburon, Inc. RMS Master codes. 12. Review & Approve Mapping Scheme. FCPS WOSA 10/97 Transformation Of Data 13. Allocate necessary resources to the Vendor, as shall be FCPS identified in the Conversion Plan, to enable the Vendor to carry on the conversion activity. 14. Provide assistance to the Vendor on usage of Mainframe FCPS & Client Server Utilities and compilers if necessary. 15. Provide the pathname of databases if necessary. FCPS 16. Develop programs to convert legacy databases into flat Vendor/FCPS file. 17. Run conversion programs and create test dumps of flat Vendor/FCPS files (sample records). 18. Develop scripts / programs to upload flat files provided by Vendor/FCPS FCPS into Oracle Intermediary tables. 19. Run scripts to upload the flat files to Intermediary Oracle Vendor/FCPS Database. 20. Print sample reports of the uploaded data. Vendor/FCPS 21. Check reports & verify that tables are properly Vendor/FCPS populated. • Review for possible duplicates and redundancies. • Identify impure/invalid data as defined in Section 6 — Data Purification. Research and correct "suspect' data. • Restart the process of data load after the impure/invalid data is corrected in legacy system. • Reiterate the identification/correction of invalid/impure data. 22. Resolve issues as per the data conversion issue Vendor/FCPS resolution strategy defined in Section 7 of this document, if any and repeat steps 19 to 21, if necessary. 23. Advise FCPS personnel of conversion results. Vendor Final Conversion 24. Arrange for necessary resources. Vendor/FCPS 25. Run conversion programs to convert the existing FCPS Databases into flat files for updated records. 26. Repeat steps 20 to 23 for final conversion. 27. Design staging database tables with normalization and Vendor data validation rules. 28. Upload data from the intermediary tables to staging Vendor tables. 29. Review the tables for possible duplicates and Vendor/FCPS redundancies. 30. Provide assistance to correct the data, if required as per Vendor/FCPS the data conversion strategy defined in section 8 and 9 of this document and steps 21. 31. Advise action to be taken on removal of duplicate and Vendor/FCPS WOSA 10/97 redundant records. 32. Remove Duplicate data. Vendor 33. View the new databases and verify for accuracy and Vendor/FCPS integrity of data, to reaffirm that step 21 was effective in purification of data. 34. Develop scripts to upload data from staging area to target Vendor Tiburon, Inc. RMS live data. 35. Upload the finalized data from staging tables to the Vendor Tiburon, Inc. RMS live database. The above -mentioned activities shall be performed in conjunction with the Implementation Plan. 10. DATA CONVERSION SCOPE The following table describes a portion of the table structure for the PRC Records Management System. (See additional information in Appendix A) Field Name able/Column Name DOM Name Null ? Type PITCASE SA XETEVENT EVT-MASTFK NOT NULL CHAR 12 SA PITCASE EVT-SUBSA NOT NULL CHAR 12 SA XPTEMP SASPEC CHAR 12 SF TOTAL NUMBER NUMBER 4 Assigned Date ASGN DT DATE NUMBER 8 Unit UNIT CODE CHAR 10 Status Date STATUS DT DATE NUMBER 8 Status STATUS CODE CHAR 6 INV CLASS CODE CHAR 10 FILED FLG CHAR1 CHAR 1 Follow up Date FOLLOWUP DT DATE NUMBER a The following table describes a portion of the table structure for the Tiburon, Inc. Records Management System. Additional information will be supplied to the vendor selected to perform this project. Report No Report number. Report numbers are Departmental 10 assigned by CAD and displayed in the Reference Number format of YYNNNNNNN. Quick entry can be used to retrieve a report within the current year, by entering the report number s only, leavino off the vear. Reported Date of event. Click on appropriate Date 10 Date calendar date above or enter date in one of the following formats; T = today, Y = yesterday, T-10 = 10 days ago, T+10 = 10 days from today, MON = Monday of this week, LMO = Monday of last week. WOSA 10/97 Reported Time of event. Time (without 5 Time I seconds) CAD Call Call number (populated during the CAD Value 9 No to RMS transfer when the CAD call is closed; used to cross-reference the dispatch information from CAD). Status Status field populated during the CAD Code Type: IS 4 transfer to RMS. The field should be modified to describe the appropriate status of the report. Nature of Nature of call. Originally populated from Code Type: N` 10 Call the CAD transfer, the field should be modified to describe the type of report written. Statistic Crime code or nature of call associated Code Type: BZ 10 Class with the UCR Report. WOSA 10/97 Citv of Fort Collins Administr.ave Services Purchasing Division CITY OF FORT COLLINS ADDENDUM No. 2 SPECIFICATIONS AND CONTRACT DOCUMENTS Description of Bid: P882 Database Conversion Project OPENING DATE: October 24, 2003 3:00 p.m. (Our Clock) To all prospective bidders under the specifications and contract documents described above, the following changes are hereby made. Fort Collins Questions: 1) Why do vendor personnel need to develop web sites? (3.4 Technical Experience, 3`d bullet) This is actually an oversight on our part. This requirement is not necessary in the conversion of our database. 2) Does the city use MSOffice Professional? MS Access is a good tool for quick ODBC manipulation, which might be needed for the UNISYS data? The City standard is MS Office Professional. 3) Does the City have licenses for Oracle Development tools: a. Forms Builder b. Report Builder c. Procedure Builder d. Designer The City has the licenses necessary. 4) Has the city defined major project milestones? (2.6 Billing) Or is this part of the expected work plan from the vendor. Milestones have not been developed. These are typically identified by the vendor in a schedule for the project. 5) Is the data to be converted going to a system currently in production? Or a system being put into production. The data to be converted is going to a system that is currently in production, but it is not in production at our agency. We are in the process of implementing the system and anticipate the cutover to a live system in early to mid 2004. 6) Does the final conversion need to happen at night or on weekends? Since the conversion will take place before we go live with our new system, it won't impact end users and the dates for the final conversion can be determined by the vendor selected to perform the data conversion and the vendor who is implementing our new system. 215 North Mason Street • 2nd Floor • P.O. Box 580 • Fort Collins, CO 80522-0580 • (970) 221-6775 9 FAX (970) 221-6707 APPENDIX A -- IDENTIFICATION -- + IDENT ------------------------------------------- Agcy FCPS Ident No. 521065681 + --------------------- Photograph Date Photograph # or Location Fingerprint File Location NCIC Fingerprint Classification Henry Fingerprint Classification Ident Date 11/30/1990 Henry Format -> 99 A 99 A AAA 99 9 = Numeric or -> 99 A 99 aAaaa 99 A = Uppercase a = Lowercase Ten Print Available? Major Case Prints Avail? Concealed Weapons Permit? + NAME (DISPLAY ONLY) ------------------------------------------------------- Caution Weapons Ident No 521065681 Name NEIMAN, SUSAN FAYE Race W Eth Sex F DOB 03/29/19551 +---------------------------------------------------------------------------- -[Fort Collins LIVE System] ------------------------- [PRC/Public Mgmt. Services]- ---> 1=NAMES 2-NOTES TABLES WOSA 10/97 FIELDS # CHARACTERS FILE _LOC = Fingerprint File Location 15 NCIC_CLASS = NCIC Fingerprint Classification 20 HENRY -CLASS = Henry Fingerprint Classification 1-5 LCCCW Ten Print Available? Major Case Prints Available? = Concealed Weapons Permit? WOSA 10/97 -- IDENTIFICATION -- + ACTIVITY ------------------------------------------------------------------ Agcy FCPS Ident # 521065681 Ident Date 11/30/1990 Time + M - --------------- ------------------------------------- ;Caution Weapons Ident # 521065681 ;Name Type P Name NEIMAN, SUSAN FAYE Race W Eth Sex F Date of Birth 03/29/1955 Age 35/ 35 Height 503/503 Weight 114/114 Hair RED Eyes HAZ Build Skin Tone Occupation Place of Birth Residence Status Citizenship Role IDENT # Alcohol/Drug Use Blood Alcohol Level ;Note + 111M (Type/Address/Since Date) (S) ------------------------------------- CHOM /1600 W MOUNTAIN AV, FT COLLINS, CO 80521 /11/18/1995I CWOR /300 LAPORTE AV, FT COLLINS, CO 80521 /07/17/2003 + (Type/Nmbr/Iss/Ex Yr) (S) ++ p (Type/Number/Note) (S) - DL /941581047 /CO / CHOM/(970) 484-5739 / CWOR/(970) 221-6825 / WORK/(970) 221-6838 / +------------------------------------++-------------------------------------- -[Fort Collins LIVE System]---------------------------[PRC Public Sector, Inc.]- ---> 1=ALIAS 2=ASSOC 3-FEATURES 4=PROP/VEH 5=NAM SUPP 6=VERIFY NM TABLES FIELDS # CHARACTERS NAMETYP = Name Type 1 SURNAME and GIVNAME = Name 40 RACE = Race I SEX = Sex 1 DOB = DOB 10 XNCAUT CAUTIONS = Caution 27 WOSA 10/97 -- IDENTIFICATION -- + ACTIVITY ------------- ------ Agcy FCPS Ident # 521065681 + NAME ------------------ :Caution ;Name Type P Name NEIMAN, +SHINNIONNINNEW ------- Ident Date 11/30/1990 Time Weapons Ident # 521065681 SUSAN FAYE Race W Eth Sex F --------------------------------------------------- Alias Name/Moniker Race Sex Birth Date MURR, SUZI W F 03/29/1955 MURR, I SUSAN FAYE W F 03/29/1955 +------------------------------------------------------------------------ -[Fort Collins LIVE System]--------------------------- [PRC Public Sector, Inc.]- ---> 1=ALIAS 2-ASSOC 3=FEATURES 4=PROP/VEH 5=NAM SUPP TABLES FIELDS // CHARACTERS SURNAME and GIVNAME = Alias Name/ Moniker 40 RACE = Race 1 SEX = Sex 1 DOB = DOB 10 WOSA 10/97 -- INCIDENT -- + 1110M ------------------------------------------------------------------ ;Agcy FCPS Report # 03-2094 Reported Date 02/01/2003 Time 01:40:52 Call Type DUI Call Disposition ;Location 1000 S COLLEGE AV, FT COLLINS, CO Geo -> Patrol P2 Rep Dist I006 Map 30L3N Coord / Enter R to Mark RMS Ownership R Prompt Set From -> Date 02/01/2003/SAT Time 01:40 To -> Date 02/01/2003/SAT Time 01:40 + -------------------------------------------------------- ISeq 1 Offense DUI Att/Corn C Count for SBR? Y Off Count I Location Type HIWAY Involves -> Force? Alcohol? Y Drugs? Computer? I Clear-> Date 02/01/2003 Type AD-ARR Domestic/Bias/Hate I Criminal Activities U Weapons/Tools UCR Codes (Generated) -> Summary Based 21 Incident Based +1111011111MR1111M--------------------------++1144§1114MM --------- Invl Date Agcy DeptID Name Class Agcy Number SUPOFF 02/01/2003 FCPS FC152 SPARACIO, STEPHAN ;;*PIAR FCPS 03-2094-01 REPOFF 02/01/2003 FCPS FC111 GRANT, DAVID I I I I I I I I I I I I I I + - + + -[Fort Collins LIVE System] ------------------------- [PRC/Public Mgmt. Services]- ---> 1-NAME 2=PROPERTY 3=VEHICLE 4=NOTES 5=SUPL DATA 6=VIC/REL TABLES FIELDS /% CHARACTERS REF_NO = Report # 12 REF DT = Reported Date 10 REF_TM = Reported Time g PIINTYP EVENT_TYP = Call Type 20 PIINSTAT EVENT STATUS = Call Disposition 6 LOCATION = Location (GEO File) ? PXPATROL PAT AREA = Patrol 6 PXREPDIS REP AREA = Rep Dist 6 WOSA 10/97 PICLASS PIPREM PXWEAPON PICRMACT PICLRTYP PICRMTYP PIINACT WOSA 10/97 MAP = Map 6 BEG DT = From Date 14 BEG TM = From Time 8 END DT = To Date 14 END TM = To Time 8 SEQ NO = Seq 2 OFFENSE - Offense 22 ATTEMPT COMP = Att/Com 1 PREMISE = Location Type 10 FORCE FLG = Force? 1 WEAPON = Weapons/Tools 20 DRUG FLG = Drugs? 1 ALCOHOL FLG - Alcohol? 1 OFF CNT - Off Count 3 COMPUTER FLG = Computer? 1 CRIM ACT = Criminal Activities 20 SBR FLAG = Count for SBR 1 CLEAR DT = Clear Date 12 CLEAR TYP = Type 6 CRIME TYP = Domestic/Bias/Hate 20 ACT DT = Date 12 ACT TYP = Invl 6 AGCY = Agcy 4 DEPT_ID = DeptID 6 NAME = Name 18 EVENT CLASS = Class 8 AGCY Agcy 4 REF NO = Number 12 -- INCIDENT -- + INCIDENT ------------------------------------------------------------------ Agcy FCPS Report # 03-1 Reported Date 12/31/2002 Time 23:35:40 Call Type THFT33 Call Disposition RTF ,Location 2160 W DRAKE RD #A5, FT COLLINS, CO + VICTIM (S) ---------------------------------------------------------------- ;Name WALGREEN DRUG STORES Race Eth Sex DOB + OFFENSE (S) --------------------------------------------------------------- ;Enter X to Link Seq # UCR/SBR UCR/IBR Offense Location Type 1 06CC THFT33 DEPT + NIFERWRIM ------------------------------------------------------------- ;Relation Role Name Race Eth Sex DOB SUSPECT FCPS, MALE w SUSPECT FCPS, MALE w I +---------------------------------------------------------------- M M -[Fort Collins LIVE System] ------------------------- [PRC/Public Mgmt. Services]- ---> 1=NAME 2=PROPERTY 3=VEHICLE 4=NOTES 5=SUPL DATA 6=VIC/REL TABLES FIELDS # CHARACTERS PIVICSUS RELATION = Relation 6 WOSA 10/97 INCIDENT + INCIDENT Agcy FCPS Report # 03-1 Reported Date 12/31/2002 Time 23:35:40 Call Type THFT33 Call Disposition RTF ,Location 2160 W DRAKE RD #A5, FT COLLINS, CO + ------------------------------- OFFICER> Dept. ID Type of Aslt Assignment Activity Wearing Armor Armor Preventative Discharged Firearm Years Experience Aware of Offender Weapon I OFFENDER> Used Officer Weapon Weapon Type Discharged Firearm Distance From Officer +-------------- ------ -[Fort Collins LIVE System] -------------------[PRC/Public Mgmt. Services]- ---> 1=NAME 2=PROPERTY 3=VEHICLE 4=NOTES 5=SUPL DATA 6=VIC/REL TABLES FIELDS # CHARACTERS DEPT_ID = Dept. ID ? PIEMPSTT STATUS = Type of Aslt 10 PIEMPASN ASGN = Assignment 10 PIEMPACT ACTIVITY = Activity 10 PIEMPARM ARMOR = Wearing Armor 10 PIEMPPRV PREVENT = Armor Preventative 10 PIEMPDSC EMP_DISCH = Discharged Firearm 10 EXPER = Years Experience 2 PIEMPAWR AWARE = Aware of Offender Weapon 10 PIOFFUSE OFFICER_WPN = Offender Used Officer Weapon 10 PIOFFWPN WPN TYP = Weapon Type 10 PIOFFDSC OFF DISCH = Discharged Firearm 10 DISTANCE = Distance from Officer 3 WOSA 10/97 -- INCIDENT -- + ACTIVITY -------------------------- --------------------------- Agcy FCPS Report # 03-1 Reported Date 12/31/2002 Time 23:35:40 Call Type THFT33 Call Disposition RTF +-------------- ---------------------------------------- ;Caution Weapons Ident # :Name Type P Name FOPS, MALE Race W Eth Sex M Date of Birth Age / Height / Weight / Hair Eyes Build Skin Tone Occupation Place of Birth Residence Status Citizenship Role SUSPECT # 1 Alcohol/Drug Use Blood Alcohol Level ;Note SEE FEATURES + JOIN= (Type/Address/Since Date) (S) ------------------------------------- I / / + (Type/Nmbr/Iss/ExpYr) (S ++ (Type/Number/Note) (S) - +------------------------------------++-------------------------------------- -[Fort Collins LIVE System]---------------------------[PRC Public Sector, Inc.]- ---> 1=ALIAS 2=ASSOC 3=FEATURES 4=PROP/VEH 5-NAM SUPP 6=VERIFY NM WOSA 10/97 XNWPN WEAPONS = Weapons 13 LO_HGT = Height 3 HI_HGT = Height 3 LO WGT = Weight 3 HI WGT = Weight 3 LO AGE = Age 3 HI AGE = Age 3 XNHAIR HAIR = Hair 3 XNEYES EYES = Eyes 3 XNSKIN SKIN = Skin Tone 3 XNBUILD BUILD = Build 3 XNOCCUP OCCUPATION = Occupation 10 XNETH ETH = Eth 1 POB = Place of Birth ? XNRESID RESID STAT = Residence Status 6 CIT = Citizenship ? BLD ALC LVL = Blood Alcohol Level 4 XNALDRG ALC DRG USE = Alcohol/Drug Use 10 NOTE = Note 70 MMMMM XNLOCTYP LOC TYP = Address Type 5 XNIDTYP ID TYP = ID Number Type 6 ID NO = Nmbr 20 ID ISS = Iss 4 = ExpYr 4 XNPHTYP PH TYP = Phone Number Type 4 PH NO = Number 14 PH NOTE - Note 16 WOSA 10/97 7) Are the source databases in production? The source database is currently in production. 8) Is there a chance of source data becoming "stale"? Yes, there is a good possibility that the data will become stale. Any suggestions by vendors will be considered. Our goal is to have a plan in place to deal with this issue. RECEIPT OF THIS ADDENDUM MUST BE ACKNOWLEDGED BY A WRITTEN STATEMENT ENCLOSED WITH THE BID/QUOTE STATING THAT THIS ADDENDUM HAS BEEN RECEIVED. + ACTIVITY ---------- Agcy FCPS Report # 03-1 23:35:40 I Call Type THFT33 + NAME ------------------------ ;Caution ;Name Type P Name FCPS, MALE Alias Name/Moniker -- INCIDENT --------------- - Reported Date 12/31/2002 Time Call Disposition RTF ----------------------------------- Weapons Race Sex Ident # Race W Eth Sex M ------------------- Birth Date -[Fort Collins LIVE System]---------------------------[PRC Public Sector, Inc.]- ---> 1=ALIAS 2=ASSOC 3=FEATURES 4=PROP/VEH 5=NAM SUPP TABLES FIELDS # CHARACTERS MMONNNIM SURNAME and GIVNAME = Alias Name/ Moniker 40 RACE = Race 1 SEX = Sex I DOB = DOB 10 WOSA 10/97 -- INCIDENT -- + ACTIVITY ------------- ------------- ------------------------- IAgcy FCPS Report # 03-1 Reported Date 12/31/2002 Time 23:35:40 Call Type THFT33 Call Disposition RTF + NAME ------------ ---------- ;Caution Weapons Ident # ;Name Type P Name FCPS, MALE Race W Eth Sex V. + -------------------------------------------------------- Person/Institution Named Below is of Person/Institution Named Above; ;Caution Weapons Ident # ;Name Type Name Race Eth Sex Date of Birth Age / Height / Weight / Hair Eyes Build Skin Tone Place of Birth ,Occupation Alcohol/Drug Use Blood Alcohol Level ,Note + ADDRESS (Type/Address/Since Date) (S) ------------------------------------- + ID NUMBER(Type/Nmbr/Iss/ExpYr) (S) ++ PHONE NUMBER (Type/Number/Hours) (S) +------------------------------------++-------------------------------------- -[Fort Collins LIVE System]---------------------------[PRC Public Sector, Inc.]- ---> 1=ALIAS 2=ASSOC 3=FEATURES 4=PROP/VEH 5=NAM SUPP 6=VERIFY NM TABLES FIELDS # CHARACTERS XNASSOC Person/Institution Named Below is 8 WOSA 10/97 -- INCIDENT -- + ACTIVITY --------------- -------------------------------- Agcy FCPS Report # 03-1 Reported Date 12/31/2002 Time 23:35:40 Call Type THFT33 Call Disposition RTF + NAME ------------------------- -------------------- ;Caution Weapons Ident # ;Name Type P Name FCPS, MALE Race W Eth Sex M + ) ------------------------------------------------------ ;Category Type Location Description + ------------------------------------------------------ :Category COAT Type WINTER Color BLU/ Note DOWN -FILLED I / +11111MIJIMINIMM -------------------------------------------------------- :Type Modus Operand +---------------------------------------------------------------------------- -[Fort Collins LIVE System]---------------------------[PRC Public Sector, Inc.]- ---> 1=ALIAS 2=ASSOC 3=FEATURES 4=PROP/VEH 5=NAM SUPP TABLES FIELDS # CHARACTERS XNFTCAT FEAT CAT = Category 6 XNFTCAT FEAT TYP = Type 10 XNFTLOC FEAT LOC = Location 6 w"MoMMIUMM FEAT NOTE = Description - 50 CAT = Category 10 TYP = Type 10 WOSA 10/97 COLORl = Color COLOR2 = Color NOTE = Note 23 PXMOTYP TYP = Type 10 VALUE = Modus Operandi 25 WOSA 10/97 -- INCIDENT -- MSG + ACTIVITY ----------------------------------- Agcy FCPS Report # 03-1 Reported Date 12/31/2002 Time 23:35:40 I Call Type THFT33 Call Disposition RTF + NAME ------------------------------------- ;Caution Weapons Ident # ;Name Type P Name FCPS, MALE Race W Eth Sex M + 111111111A11111111M ---------------------- ---------------------- Invl Status Type Year Make Model License Color I / / I / / I / / I / / I / / I / / I / / +------------- -------------------- -[Fort Collins LIVE System]--------------------[PRC Public Sector, Inc.]- ---> 1=ALIAS 2=ASSOC 3=FEATURES 4=PROP/VEH 5-NAM SUPP TABLES FIELDS # CHARACTERS PINAMPRP = Invl o WOSA 10/97 -- INCIDENT -- + ACTIVITY ------- Agcy FCPS Report # 03-1 Reported Date 12/31/2002 Time 2 3 : 3 5 : 4 0 I Call Type THFT33 Call Disposition RTF + NAME ------------------- ;Caution Weapons Ident # ;Name Type P Name FCPS, MALE Race W Eth Sex M Diversion Date Restitution Amount/Date Warrant#/Expiration Date Refiled Warrant#/Exp Date Injury Type(s) to Victim +----------------------- ----------------------------- -[Fort Collins LIVE System]-------------------[PRC Public Sector, Inc.]- ---> 1=ALIAS 2=ASSOC 3=FEATURES 4=PROP/VEH 5=NAM SUPP TABLES FIELDS # CHARACTERS Diversion Date ? Restitution Amount/Date ? Warrant#/Expiration Date ? Refiled Warrant#/Exp Date ? XNININJT Injury Type(s) to Victim ? WOSA 10/97 -- INCIDENT -- + INCIDENT ---------------------- Agcy FCPS Report # 03-21 Reported Date 01/01/2003 Time 04:00:41 Cali Type MVT10A Call Disposition RTF ;Location 908 PEAR ST, FT COLLINS, CO + ------------------ ------------------------------- ;Status STOLEN Type R /CDISC Make Model Color / Desc VARIOUS ARTISTS Serial # / CAN Property Value $ Number of Like Items 23 When Recovered Enter -> Recovery Date Recovery Value $ + PROPERTY SUPPLEMENTAL (S) ---------------------- --------------------- CCIC ENTRY (Y) More Description More Description Force as Duplicate (Y/N) +---------------------------------------------------------------------------- -[Fort Collins LIVE System] ------------------------- [PRC/Public Mgmt. Services]- ---> 1=NAME 2=PROP/NAME 3=VEHICLE 4=NOTES 5=SUPL DATA 6=VIC/REL TABLES FIELDS # CHARACTERS PPSTAT PV STATUS = Status 6 PV TYP = Type (NCIC Codes) 2 PV_CATEGORY (NCIC Codes) 8 MAKE = Make MODEL = Model COLORI = Color 3 COLOR2 = Color 3 WOSA 10/97 Note SER1 Desc SER2 se , # OAN - OAN set, # 2 o " VALUEpro?d RACDINT NunhezrY Value $ 20 REC VALUERecoverY pate ike Items 9 0 Recovery value 3 12 9 wOSA 10197 -- INCIDENT -- + INCIDENT ------------------------------------------------------------------ Agcy FCPS Report # 03-21 Reported Date 01/01/2003 Time 04:00:41 Call Type MVT10A Call Disposition RTF ;Location 908 PEAR ST, FT COLLINS, CO + )-------------- ;Status RECOV Lic Number 468BCC Lic Issuer CO Lic Year Lic Type PC Veh Type AU/CP Year 1996 Make PONT Model FBD Color RED/ Desc Value $ VIN/Ser # 2G2FS22K2T2228233 CAN Recovered -> Date 01/01/2003 Value $ Type A Condition HVY DAMAGE Location 201 S IMPALA DR, FT COLLINS, CO 80521 Geo -> Patrol P7 Rep Dist H002 Map 29I4N Coord + VEHICLE SUPPLEMENTAL (S) ----------------------------------- ICU CCIC ENTRY (Y) *DO NOT USE 3/96 (damage) *DO NOT USE 3/96 (desc) *DO NOT USE 3/96 (more) *DO NOT USE 3/96 (addtl) Force as Duplicate (Y/N) +----------- 11 ------------------------- -[Fort Collins LIVE System] ------------------------- [PRC/Public Mgmt. Services]- ---> 1=NAME 2=PROPERTY 3=VEH/NAME 4=NOTES 5=SUPL DATA 6=VIC/REL TABLES FIELDS # CHARACTERS PPSTAT PV STATUS = Status 6 LIC NO = Lic Number 10 LIC ISS = Lic Issuer LIC YR = Lic Year o PPLICTYP LIC TYP = Lic Type 2 PV_TYP = Veh Type 2 PV_CATEGORY 8 WOSA 10/97 PXPATROL PXREPDIS WOSA 10/97 YEAR = Year MAKE = Make MODEL = Model COLORI = Color COLOR2 = Color Note = Desc PV VALUE = Property SER1 = VIN/Ser # CAN = CAN REC DT = Recovered REC VALUE = Value $ Type Condition LOCATION = Location PAT AREA = Patrol REP AREA = Rep Dist = Map Value $ Date 3 3 70 9 20 20 12 9 2 12 6 6 Administruave Services Purchasing Division CITY OF FORT COLLINS City of Fort Collins ADDENDUM No. 1 SPECIFICATIONS AND CONTRACT DOCUMENTS Description of Bid: P882 Database Conversion Project OPENING DATE: October 24, 2003 3:00 p.m. (Our Clock) To all prospective bidders under the specifications and contract documents described above, the following changes are hereby made. QUESTIONS: 1. The RFP contained an appendix that appears to be a combination of screen layouts and related source tables from the source system. Is this an accurate description of the appendix? Please provide a description of the appendix and its purpose. That is an accurate description of the appendix. It was intended to provide an idea of the screen layout in the PRC system as well as the related source tables so vendors could get a better understanding of what was involved regarding the source system. 2. What is the budget for this data conversion effort? 3. How much budget has been allocated to this conversion project? The budget is sufficient for this project. 4. What company is implementing the Tiburon Records Management System? Tiburon, Inc. is providing the Records Management System. However, all questions regarding this RFP are to be referred to Susan Neiman, Project Manager and not to Tiburon. 5. How "clean" do you believe the legacy PRC source data to be? (1 — 10, 10 being perfectly clean) The legacy PRC data is probably a 7 - 8. 6. Is Fort Collins Police Services (FCPS) taking advantage of the implementation and data conversion to cleanse the legacy data as it is converted? (i.e. fix data entry errors from the past 10 years) 215 North Mason Street • 2nd Floor • P.O. Box 580 • Fort Collins, CO 80522-0580 • (970) 221-6775 • FAX (970) 221-6707 -- INCIDENT -- + INCIDENT ---------------- Agcy FCPS Report # 03-21 Reported Date 01/01/2003 Time 04:00:41 Call Type MVT10A Call Disposition RTF ;Location 908 PEAR ST, FT COLLINS, CO ------------------------- --------------------- +------ ----------------------- -[Fort Collins LIVE System] --------- --[PRC/Public Mgmt. Services]- ---> 1=NAME 2=PROPERTY 3=VEHICLE 4=NOTES 5=SUPL DATA 6=VIC/REL TABLES FIELDS # CHARACTERS NOTE = Notes WOSA 10197 -- INCIDENT -- + INCIDENT---------------------------- Agcy FCPS Report # 03-21 Call Type MVT10A ;Location 908 PEAR ST, FT COLLINS, CO +W --------------- Reported Date 01/01/2003 Time 04:00:41 Call Disposition RTF NarrID Date Description of Narrative FORM 01/02/2003 K SPAULDING/LM/IN MAIN FILE/FINAL PSUP01 01/02/2003 J VANDERVLIET/WLH/FINAL/020303/JPK PSUP02 01/04/2003 D BUHRMAN/MAZ/FINAL/011203/HR PSUP03 01/04/2003 K SPAULDING/MAZ/FINAL/010803/JBF PSUP04 01/08/2003 J KOVATS-FULTON/WLH/FINAL/011403/EP PSUP05 01/10/2003 L DINGMAN/LM/FINAL/031503/LM PSUP06 01/16/2003 L DINGMAN/HR/FINAL/021903/RLM PSUP07 03/13/2003 J KOVATS-FULTON/EP +------------------ ------ ---------------------------------------- -[Fort Collins LIVE System] -------------------[PRC/Public Mgmt. Services]- ---> 1=EDIT 2=READ 4=PRINT TABLES FIELDS # CHARACTERS NANINNINNOW NARR ID = NarrID 6 NARR DT = Date 12 NOTE = Description of Narrative 59 WOSA 10/97 -- CASE MANAGEMENT -- + INCIDENT ----------- ----------------------------------------------- Agcy FCPS Report # 03-1 Reported Date 12/31/2002 Time 23:35:40 Call Type THFT33 Call Disposition RTF ;Location 2160 W DRAKE RD 05, FT COLLINS, CO + ------------------------------------------------------- Investigator> ID FC78 Name ROGERS, ERIC Unit Asgn'Date 12/31/2002 Class THFT33 Status Date 12/31/2002 Status SU Next Followup Due Case Filed? Solvability Score Total + RMONOW ------------------------------------------ Suspect Arrested Suspect is Known Suspect is Repeat Offende Suspect can be Identified Suspect Location is Known Vehicle License is Known Vehicle can be identified Traceable Property Lost Sex Offense Serious Injury to Victim -[Fort Collins LIVE System]------------------ [PRC/Public Mgmt. Services]- ---> 1=INCIDENT 2=ACTIVITY 3=FRAUD 4=NOTE 6=REL EVID TABLES FIELDS # CHARACTERS MMINNow DEPT ID = Investigator ID 6 NAME = Name 32 PIDUNIT UNIT = Unit 10 ASGN_DT = Asgn Date 12 PIINVCLS INV CLASS = Class 10 STATUS DT = Status Date 12 PISTATUS STATUS = Status 6 WOSA 10/97 FOLLOWUP DT = Next Followup Due 12 FILED FLG = Case Filed? 1 SUPL KEY SUPL DATA WOSA 10/97 -- CASE MANAGEMENT -- + INCIDENT ------------------------------------------------------------------ ;Agcy FCPS Report # 03-1 Reported Date 12/31/2002 Time 23:35:40 Call Type THFT33 Call Disposition RTF ;Location 2160 W DRAKE RD #A5, FT COLLINS, CO L I n v e s t i g a t o r Spent; Date DeptID Name ; ; --------------------------------------------------- -[Fort Collins LIVE System] ------------------------ Services]- ---> 1=INCIDENT 2=ACTIVITY 3=FRAUD 4=NOTE TABLES FIELDS i ACT DT = Date ACT TYP = Type ACT CNT = Count 4000af. ACT —DUR = Time Spent DEPT_ID = Investigator ID NAME = Name WOSA 10/97 A c t i v i t y Time Type Count hhh.hh -[PRC/Public Mgmt. 6=REL EVID # CHARACTERS 12 6 5 5 6 32 WOSA 10/97 -- CASE MANAGEMENT -- + INCIDENT ------------------------------------------------------------------ Agcy FCPS Report # 03-1 Reported Date 12/31/2002 Time 23:35:40 Call Type THET33 Call Disposition RTF 'Location 2160 W DRAKE RD #A5, FT COLLINS, CO + CASE MANAGEMENT (S) ------------------------------------------------------- Investigator> ID FC78 Name ROGERS, ERIC Unit + ----------------------------------------------------------------- +---------------------------------------------------------------------------- -[Fort Collins LIVE System] ------------------------- [PRC/Public Mgmt. Services]- ---> 1=INCIDENT 2=ACTIVITY 3-FRAUD 4-NOTE 6=REL EVID TABLES FIELDS # CHARACTERS NOTES = Notes WOSA 10/97 -- FRAUDULENT DOCUMENTS -- + INCIDENT ------- ----------------------------------------------------- ;Agcy FCPS Report # 03-1 Reported Date 12/31/2002 Time 23:35:40 Call Type THFT33 Call Disposition RTF ;Location 2160 W DRAKE RD #A5, FT COLLINS, CO + --------------------------------------------------- ;Fraud Type Total Amount $ Document> # Type Date # of Documents I ;Note + JIMM ------------------------------------------------------------------ ;Role Name Type Phone # Name Race Sex DOB Address ;Role Name Type Phone # Name Race Sex DOB Address + ----------------------------------------------- :ID Type ID Number +---------------------------------------------------------------------------- -[Fort Collins LIVE System] ------------------------- [PRC/Public Mgmt. Services]- ---> TABLES FIELDS CHARACTERS t e PIFRDTYP FRAUD _TYP = Fraud Type 10 TOT ANT = Total Amount $ 11 DOC NO = Document # 19 PIDOCTYP DOC_TYP = Type 6 DOC DT = Date 12 NUM DOC = # of Documents 3 NOTE = Note 70 WOSA 10/97 PIFRDROL ROLE = Role 8 XNNAMTYP NAMETYP = Name Type 1 PHONE - Phone # ? NAME = Name ? XNRACE RACE = Race 1 XNSEX SEX = Sex 1 ADDR = Address ? OWN PIFRDID ID TYP = ID Type 6 ID NO = ID Number 22 WOSA 10/97 -- ARREST -- + NIONNOON ---------------------------------------------------------------- IAgcy FCPS Arrest -> Type CIT Number 03-4018-01 Date 03/01/2003 Time 00:30 Disposition COUNTY Date 03/05/2003 Time 10:17 :Arrest Location 817 SKYLINE DR, FT COLLINS, CO 80521 Geo -> Patrol P6 Rep Dist H009 Map 30JlS Coord / + --------------------------------------------------- Court date 04/09/2003 Court date Restitution Amount/Date Entry From Summons? Y Test Type + INIIIINNINNIM (Date /Role/Agcy/Dept ID/Note) (S) ----------------------- 03/01/2003 ARREST FCPS FC133 I + NAME (DISPLAY ONLY) ------------------------------------------------------- ;Caution Weapons Ident # 523595807 ;Name MAY, JOHN RUFF Rac W Eth Sex M DOB 08/12/1982: +---------------------------------------------------------------------------- -[Fort Collins LIVE System] ------------------------- [PRC/Public Mgmt. Services]- ---> 1=NAME 2=CHARGES 3=NOTE/XREF 4=VEHICLE TABLES PIARTYP PIARSTAT WOSA 10/97 FIELDS # CHARACTERS EVENT_TYP = Type 20 REF NO = Number 12 REF DT = Date 12 REF_TM = Time 4 EVENT _STATUS = Disposition 6 Date/Time - System defaults to date of Entry These types of problems will be handled by FCPS personnel prior to the actual conversion. All such data issues need to be corrected on the legacy database so as to avoid recurrence at the time of production data conversion. However, if such problems are found even after the actual conversion is completed in the live database, FCPS personnel shall have to resolve these problems via manual data entry 1 correction at the backend. The Vendor shall facilitate/guide FCPS personnel in doing so. All the data that is inherently erroneous may conform to the business rules and therefore remain uncorrected during the transition to the Tiburon, Inc. RMS system. For instance, the social security number of a participant should be in the format of 123456789. The business rules enforced would validate whether the social security number is in the format specified, but it cannot ensure that the contents of social security number of the participant is in fact correct and belongs to the said participant. Such type of errors can be corrected whenever identified during and after Tiburon, Inc. RMS system implementation by the FCPS team. The Vendor would facilitate the correction of such errors. 7. Can the bidders obtain a copy of the data dictionary for the legacy PRC system as well as the new Tiburon system prior to submitting the proposal? As stated in the RFP, the data dictionaries for both systems will be provided to the successful vendor. 8. Will all historical data be converted to the new system, or will some data remain archived in the legacy system? Some data will remain archived and not converted to the new system. 9. Has the data architecture for the new Tiburon system been finalized? If not, will a final data dictionary for the new Tiburon system be available for data mapping at the start of the data conversion effort? The data architecture for the new system has not been finalized and a final data dictionary for the new Tiburon system will be available at the start of the data conversion effort. 10. Have all the code tables and code values in the new Tiburon system been defined? If not, will they be defined by the start of the data conversion effort? No. the code tables and code values in the new Tiburon system have not been defined. However, they will be defined by the start of the data conversion effort. LOCATION = Arrest Location (GEO file) PXPATROL PAT AREA = Patrol PXREPDIS REP AREA = Rep Dist MAP = Map SUPL Key SUPL DATA WOSA 10/97 -- ARREST -- + ARREST (S) --- ------------------------------------------------------- ;Agcy FCPS Arrest -> Type CIT Number 03-4018-01 Date 03/01/2003 Time 00:30 Disposition COUNTY Date 03/05/2003 Time 10:17 + ---------------- ------------------------- No 1 Date 03/01/2003 Agcy FCPS Rpt # 03-4018 Chg LIQU30 Lvl M Want/Warrant # ORI Citation # 03C101994 Disp Date Disposition Amended Chg Lvl Sentence ;No Date Agcy Rpt # Chg Lvl Want/Warrant # ORI Citation # Disp Date Disposition Amended Chg Lvl Sentence No Date Agcy Rpt # Chg Lvl Want/Warrant ORI Citation # Disp Date Disposition Amended Chg Lvl Sentence + NAME (DISPLAY ONLY) ------------------------------------------------------- ;Caution Weapons Ident # 523595807 ;Name MAY, JOHN RUFF Rac W Eth Sex M DOB 08/12/1982 +---------------------------------------------------------------------------- -[Fort Collins LIVE System] ------------------------- [PRC/Public Mgmt. Services]- ---> 1=NAME 2-CHARGES 3=NOTE/XREF 4=VEHICLE TABLES FIELDS # CHARACTERS CHG NO = No 2 CHG DT = Date 12 AGCY = Agcy (system defaults) 4 RPT_NO = Rpt # 12 PICHARGE CHG = Chg 17 PICHGLVL CHG LVL = Lvl I WAR NO = Want/Warrant # 12 WOSA 10/97 ORI = ORI 9 CIT NO = Citation # 12 DISP_DT = Disp Date 12 PICHGDSP DISP = Disposition 6 PICHARGE AMEND CHG = Amended Chg 17 PICHGLVL AMEND CHG LVL = Lvl 1 SENTENCE = Sentence 60 WOSA 10/97 -- ARREST -- + ARREST (S) ----------------------------------------------------------- ;Agcy FCPS Arrest -> Type CIT Number 03-4018-01 Date 03/01/2003 Time 00:30I Disposition COUNTY Date 03/05/2003 Time 10:17 ;Arrest Location 817 SKYLINE DR, FT COLLINS, CO 80521 + MINIM ------------------------------------------------------------ Event Class Agcy Reference Number +---------------------------------------------------------------------------- -[Fort Collins LIVE System] ------------------------- [PRC/Public Mgmt. Services]- ---> 1=NAME 2=CHARGES 3=NOTE/XREF 4=VEHICLE TABLES FIELDS // CHARACTERS NOTES = Notes EVENT CLASS = Event Class 8 AGCY = Agcy 4 REF NO = Reference Number 12 WOSA 10/97 -- ARREST -- + ACTIVITY ------------------------------------------------------------------ IAgcy FCPS Arrest # 03-4018-01 Arrest Date 03/01/2003 Time 00:30:00 I ;Arrest Type CIT Disposition COUNTY + Nw ---------------------------------p------------------------------------ ;Caution Weapons Ident # ;Name Type Name Race Eth Sex Date of Birth Age / Height / Weight / Hair Eyes Build Skin Tone Place of Birth ;Occupation Alcohol/Drug Use Blood Alcohol Level ;Note + ADDRESS (Type/Address/Since Date) (S) ------------------------------------- I / / + ID NUMBER(Type/Nmbr/Iss/ExpYr) (S) ++ PHONE NUMBER (Type/Number/Hours) (S) +------------------------------------++-------------------------------------- -[Fort Collins LIVE System]---------------------------[PRC Public Sector, Inc.]- ---> 1=ALIAS 2=ASSOC 3=FEATURES 4=PROP/VEH 5=NAM SUPP 6=VERIFY NM TABLES FIELDS # CHARACTERS NAMETYP = Name Type 1 SURNAME and GIVNAME = Name 40 RACE = Race 1 SEX = Sex I DOB = DOB 10 i XNCAUT CAUTIONS = Caution 27 XNWPN WEAPONS = Weapons 13 LO_HGT = Height 3 HI_HGT = Height 3 LO WGT = Weight 3 HI_WGT = Weight 3 LO AGE = Age 3 HI AGE = Age 3 XNHAIR HAIR = Hair 3 XNEYES EYES = Eyes 3 WOSA 10/97 XNSKIN SKIN = Skin Tone 3 XNBUILD BUILD = Build 3 XNOCCUP OCCUPATION = Occupation 10 XNETH ETH = Eth 1 POB = Place of Birth ? XNRESID RESID STAT = Residence Status 6 CIT = Citizenship ? BLD ALC LVL = Blood Alcohol Level 4 XNALDRG ALC DRG USE = Alcohol/Drug Use 10 NOTE = Note 70 XNLOCTYP LOC TYP = Address Type 5 -- ARREST -- + ACTIVITY ------------ ----- ------ ------ Agcy FCPS Arrest # 03-4018-01 Arrest Date 03/01/2003 Time 00:30:00 I ;Arrest Type CIT Disposition COUNTY + NAME -------------- ------ ---- -------------------- ,Caution Weapons Ident # 523595807 ;Name Type P Name MAY, JOHN RUFF Race W Eth Sex M + - ---------------------------------------------------- Alias Name/Moniker WOSA 10/97 Race Sex Birth Date -[Fort Collins LIVE System] -------------------[PRC Public Sector, Inc.]- ---> 1=ALIAS 2=ASSOC 3=FEATURES 4=PROP/VEH 5=NAM SUPP TABLES FIELDS # CHARACTERS SURNAME and GIVNAME = Alias Name/ Moniker 40 RACE = Race 1 SEX = Sex 1 DOB = DOB 10 WOSA 10/97 -- ARREST -- + ACTIVITY ------------------------------ ------------------- Agcy FCPS Report # 03-1 Reported Date 12/31/2002 Time 23:35:40 : Call Type THFT33 Call Disposition RTF + NAME --------------------------- ;Caution Weapons Ident # ;Name Type P Name FCPS, MALE Race W Eth Sex M +N118111111110M------------- --------------------------- Person/Institution Named Below is of Person/Institution Named Above: :Caution Weapons Ident # :Name Type Name Race Eth Sex Date of Birth Age / Height / Weight / Hair Eyes Build Skin Tone Place of Birth :Occupation Alcohol/Drug Use Blood Alcohol Level :Note + #KIM (Type/Address/Since Date) (S) ------------------------------------- (Type/Nmbr/Iss/ExpYr) (S) ++ (Type/Number/Hours) (S) +------------------------------------++-------------------------------------- -[Fort Collins LIVE System]---------------------------[PRC Public Sector, Inc.]- ---> 1=ALIAS 2=ASSOC 3=FEATURES 4=PROP/VEH 5-NAM SUPP 6=VERIFY NM TABLES FIELDS /% CHARACTERS XNASSOC Person/Institution Named Below is 8 NAMETYP = Name Type 1 SURNAME and GIVNAME - Name 40 RACE = Race 1 SEX = Sex I DOB = DOB 10 WOSA 10/97 XNCAUT CAUTIONS = Caution 27 XNWPN WEAPONS = Weapons 13 LO HGT = Height 3 HI HGT = Height 3 LO WGT = Weight 3 HI_WGT = Weight 3 LO AGE = Age 3 HI AGE = Age 3 XNHAIR HAIR = Hair 3 XNEYES EYES = Eyes 3 XNSKIN SKIN = Skin Tone 3 XNBUILD BUILD = Build 3 XNOCCUP OCCUPATION = Occupation 10 XNETH ETH = Eth 1 POB = Place of Birth ? XNRESID RESID STAT = Residence Status 6 CIT = Citizenship ? BLD ALC LVL = Blood Alcohol Level 4 XNALDRG ALC DRG USE = Alcohol/Drug Use 10 Isom NOTE = Note 70 XNLOCTYP LOC_TYP = Address. Type 5 WOSA 10/97 -- ARREST -- + ACTIVITY ----------- ------------------------------------------------- Agcy FCPS Report # 03-1 Reported Date 12/31/2002 Time 23:35:40 Call Type THFT33 Call Disposition RTF + NAME -------------------------- -------------------------------------- ;Caution Weapons Ident # ;Name Type P Name FCPS, MALE Race W Eth Sex M + ) ------------------------------------------------------ ;Category Type Location Description + ------------------------------------------------------ ;Category COAT Type WINTER Color BLU/ Note DOWN -FILLED I / +-------------------------------------------------------- !Type Modus Operandi +---------------------------------------------------------------------------- -[Fort Collins LIVE System]---------------------------[PRC Public Sector, Inc.]- ---> 1=ALIAS 2=ASSOC 3=FEATURES 4=PROP/VEH 5=NAM SUPP TABLES FIELDS # CHARACTERS MINIMMOMM XNFTCAT FEAT _CAT = Category 6 XNFTCAT FEAT TYP = Type 10 XNFTLOC FEAT LOC = Location 6 IMMUMPM FEAT NOTE = Description 50 CAT = Category 10 TYP = Type 10 WOSA 10/97 11. Does the legacy PRC system rigorously enforce referential integrity, or should the conversion team be prepared to fix "orphaned" records and/or codes? The PRC system does enforce referential integrity, however that does not mean that there won't be any `orphaned' records or codes. If any are discovered, the conversion team should be prepared to fix them. 12.Is the legacy PRC system highly codified? What degree of flexibility do the end users have when they are entering data? (i.e. can "bad" data be entered easily into the system?) Yes, the PRC system is highly codified. The end users cannot enter "bad" data into fields that are tied to code tables 13. How many FCPS resources will be working on this project and how much time per week will each person dedicate? 14. What is the project managers' current estimated level of effort in hours? At this point, the resources for this project have not been identified nor has the amount of time per week been identified. That will occur when we are closer to starting this project. 15. Will the FCPS provide the hardware/software to support the conversion effort? (i.e. separate conversion server(s), Oracle licenses, Tiburon licenses, etc.) FOPS will provide Oracle licenses, Tiburon licenses, etc. as well as the hardware (server) that the data will be converted to. FCPS will not provide additional or separate servers to be used solely for data conversion. 16. Will the data conversion team have access to the legacy PRC system to review data in the source system during the project? Yes, the conversion team will have access to the legacy PRC system during the project. 17. Will the data conversion team have access to an instance of the new Tiburon system for test conversions and data review? Yes, the conversion team will have access to the new Tiburon system for test conversions and data review. 18. Will FCPS be extending the deadline for the data conversion RFP? FCPS has no plans to extend the deadline for the data conversion RFP. COLORI = Color COLOR2 = Color NOTE = Note 23 PXMOTYP TYP = Type 10 VALUE = Modus Operandi 25 WOSA 10/97 -- ARREST -- + ARREST (S)------------------ ------ ------------------ Agcy FCPS Arrest -> Type CIT Number 03-4018-01 Date 03/01/2003 Time 00:30 Disposition COUNTY Date 03/05/2003 Time 10:17 ;Arrest Location 817 SKYLINE DR, FT COLLINS, CO 80521 + -------------------------------------------------------------- Status Lic Number Lic Issuer Lic Year Lic Type Veh Type / Year Make Model Color / Desc Vin + ------------------------------------------------- Invl Role CITE Name MAY, JOHN RUFF +---------------------------------------------------------------------------- -[Fort Collins LIVE System] ------------------------- [PRC/Public Mgmt. Services]- ---> 1=NAME 2=CHARGES 3=NOTE/XREF 4=VEHICLE TABLES FIELDS # CHARACTERS PPSTAT PV STATUS = Status g LIC NO = Lic Number 10 LIC ISS = Lic Issuer LIC YR = Lic Year PPLICTYP LIC TYP = Lic Type 2 PV TYP = Veh Type 2 PV CATEGORY 8 YEAR = Year MAKE = Make WOSA 10/97 PXPATROL PXREPDIS WOSA 10/97 MODEL = Model COLORI = Color COLOR2 = Color Note = Desc PV VALUE = Property SER1 = VIN/Ser # CAN = CAN REC DT = Recovered REC_VALUE = Value $ Type Condition LOCATION = Location PAT AREA = Patrol REP AREA = Rep Dist MAP = Map Value $ Date 3 3 70 9 20 20 12 9 2 12 6 6 6 -- ARREST -- + ACTIVITY ----------------------------- Agcy FCPS Arrest # 03-4018-01 Arrest Date 03/01/2003 Time 00:30:00 I ;Arrest Type CIT Disposition COUNTY + NAME ------- --------- -------- ------------------ ;Caution Weapons Ident # 523595807 ;Name Type P Name MAY, JOHN RUFF Race W Eth Sex M 1 +MINNIE= ------------------------------------------------------ Invl Status Type Year Make Model License Color ----------------------------------------------------------------------------- 1 1 1 I I / / 1 1 1 1 I / / 1 1 I / / 1 1 I / / I / / I 1 I / / I I I / / -[Fort Collins LIVE System]---------------------------[PRC Public Sector, Inc.]- ---> 1=ALIAS 2-ASSOC 3=FEATURES 4=PROP/VEH 5=NAM SUPP TABLES FIELDS # CHARACTERS PINAMPRP = Invl WOSA 10/97 -- FIELD CONTACT -- + 11MM ---------------- ------------------------------------- Agcy FCPS Contact -> No. 7380 Date 01/09/1999 Time Reason SUSPICIOUS Status CLOSED Location 300 N COLLEGE AV, FT COLLINS, CO 80521 Geo -> Patrol P5 Rep Dist E015 Map 29L1 Coord + ----------------------- Is subject a juvenile? Parole or Probation Subject in vehicle? Related case number Purge Code Gang Related or Gang Name Fingerprinted? Role FIOFF Dept ID FC109 Name SMITH, DOUG ; + NAME (DISPLAY ONLY) ------------------------------------------------------- Caution Weapons Ident No 353529622 Name FINLEY, ROBERT GEORGE Race W Eth Sex M DOB 09/08/1958: +---------------------------------------------------------------------------- -[Fort Collins LIVE System] ------------------------- [PRC/Public Mgmt. Services]- ---> 1=NAMES 2=VEHICLE 3=NOTES TABLES FIELDS # CHARACTERS AGCY = Agcy (system default) 4 REF NO = Contact No. REF DT = Date 12 REF TM = Time 8 PMFCTYP EVENT TYP = Reason 20 PMFCSTAT EVENT STATUS = Status 6 LOCATION = Location (GEO File) ? WOSA 10/97 PXPATROL PAT AREA = Patrol PXREPDIS REP AREA = Rep Dist MAP = Map SUPL KEY SUPL DATA WOSA 10/97 -- FIELD CONTACT -- + ACTIVITY -------- ------------ ---------------------------------- Agcy FCPS Contact # 7380 Contact Date 01/09/1999 Time Reason SUSPICIOUS Status CLOSED + so ----------------------------- -------------------------- ;Caution Weapons Ident # 353529622 ;Name Type P Name FINLEY, ROBERT GEORGE Race W Eth Sex N Date of Birth 09/08/1958 Age 40/ 40 Height 509/509 Weight 165/165 Hair BRO Eyes BLU Build Skin Tone Occupation Place of Birth Residence Status Citizenship Role FICARD # Alcohol/Drug Use Blood Alcohol Level ;Note (Type/Address/Since Date) (S) ------------------------------------- *COTH /TRANSIENT, FT COLLINS, CO 80521 /12/22/1992 *HOME /2025 N COLLEGE AV #46, FT COLLINS, CO 80524 /06/04/2002 *HOME /2225 S COLLEGE AV, FT COLLINS, CO 80521 /04/22/2002 + (Type/Nmbr/Iss/ExpYr) (S) ++ Ifl§0110M (Type/Number/Note) (S) - *SID /246822 /CO / ;;*HOME/(970) 493-7729 / *FBI /10234R7 / / ;;*HOME/(970) 226-4812 / *DL /920711791 /CO / ;:*OTHR/(970) 493-0141 / +------------------------------------++-------------------------------------- -[Fort Collins LIVE System]---------------------------[PRC Public Sector, Inc.]- ---> 1=ALIAS 2=ASSOC 3=FEATURES 4=PROP/VEH 5=NAM SUPP 6=VERIFY NM TABLES FIELDS # CHARACTERS NAMETYP = Name Type 1 SURNAME and GIVNAME = Name 40 RACE = Race I SEX = Sex 1 DOB = DOB 10 XNCAUT CAUTIONS = Caution 27 WOSA 10/97 XNWPN WEAPONS = Weapons 13 LO HGT = Height 3 HI HGT = Height 3 LO WGT = Weight 3 HI WGT = Weight 3 LO—AGE = Age 3 HI_AGE = Age 3 XNHAIR HAIR = Hair 3 XNEYES EYES = Eyes 3 XNSKIN SKIN = Skin Tone 3 XNBUILD BUILD = Build 3 XNOCCUP OCCUPATION = Occupation 10 XNETH ETH = Eth 1 POB = Place of Birth ? XNRESID RESID STAT = Residence Status 6 CIT = Citizenship ? BLD ALC LVL = Blood Alcohol Level 4 XNALDRG ALC DRG USE = Alcohol/Drug Use 10 MUMM NOTE = Note 70 XNLOCTYP LOC TYP = Address Type 5 now XNIDTYP ID TYP = ID Number Type 6 ID NO = Nmbr 20 ID ISS = Iss 4 = ExpYr 4 XNPHTYP WOSA 10/97 PH TYP = Phone Number Type PH NO = Number PH NOTE = Note 4 14 16 -- FIELD CONTACT -- + ACTIVITY -------------- ------------------------------- Agcy FCPS Contact # 7380 Contact Date 01/09/1999 Time Reason SUSPICIOUS Status CLOSED + NAME ---------------------------- ----------------------------- ;Caution Weapons Ident # 353529622 ;Name Type P Name FINLEY, ROBERT GEORGE Race W Eth Sex M +NINNINNOMM -------- ------------------------------------------- Alias Name/Moniker Race Sex Birth Date +----------------------- ----------------------------------------------- -[Fort Collins LIVE System]---------------------------[PRC Public Sector, Inc.]- ---> 1=ALIAS 2=ASSOC 3-FEATURES 4=PROP/VEH 5=NAM SUPP TABLES FIELDS # CHARACTERS SURNAME and GIVNAME = Alias Name/ Moniker 40 RACE = Race 1 SEX = Sex 1 DOB = DOB 10 WOSA 10/97 -- FIELD CONTACT -- + ACTIVITY ------------------------------------------------------------------ Agcy FCPS Contact # 7380 Contact Date 01/09/1999 Time Reason SUSPICIOUS Status CLOSED + NAME ---------------------------------------------------------------------- ;Caution Weapons Ident # 353529622 ;Name Type P Name FINLEY, ROBERT GEORGE Race W Eth Sex M + 111111111111jum -------------------------------------------------------- Person/Institution Named Below is of Person/Institution Named Above; ;Caution Weapons Ident # ;Name Type Name Race Eth Sex Date of Birth Age / Height / Weight / I Hair Eyes Build Skin Tone Place of Birth I ;Occupation Alcohol/Drug Use Blood Alcohol Level I I ;Note + ADDRESS (Type/Address/Since Date) (S) ------------------------------------- + ID NUMBER(Type/Nmbr/Iss/ExpYr) (S) ++ PHONE NUMBER (Type/Number/Hours) (S) +------------------------------------++-------------------------------------- -[Fort Collins LIVE System]---------------------------[PRC Public Sector, Inc.]- ---> 1=ALIAS 2=ASSOC 3-FEATURES 4=PROP/VEH 5=NAM SUPP 6=VERIFY NM TABLES FIELDS /% CHARACTERS XNASSOC Person/Institution Named Below is 8 NAMETYP = Name Type I SURNAME and GIVNAME = Name 40 RACE = Race 1 SEX = Sex I DOB = DOB 10 WOSA 10/97 19. Will data from the Larimer County Sheriff's Office be converted? At this point, there are no plans to convert legacy data for the Larimer County Sheriff's Office. Their information was included solely as a reference in the event they determine a need for their data to be converted. 20. Which source systems should be included in the scope? Currently, there is only one source system to be included in this scope. That is the PRC system. 21. What are your expectations for screen changes for, say, data that's in the source but not in the target system? We don't expect to make any screen changes in the target system. However, there are additional fields in the target system that can be user - defined. 22.Are there sub -systems that are reliant on the source system such as reports or data files? All the data files are reliant on the source system. The source system was used for data entry to create the data files. 23. Would you consider an alternative strategy to the one outlined in the Data Conversion Strategy? Yes, we would consider alternative strategies. 24. Would you consider an approach utilizing conversion and reporting tools as opposed to custom coding approach? Yes, we would consider an approach utilizing conversion and reporting tools as opposed to custom coding approach. 25. Is the 21 day post production support period part of the 2 month maintenance agreement? No it is not part of the 2 month maintenance agreement. 26. Will you provide dev, qa, and user acceptance environments? This possibility has been discussed but a final decision has not been made yet. XNCAUT CAUTIONS = Caution 27 XNWPN WEAPONS = Weapons 13 LO HGT = Height 3 HI HGT = Height 3 LO WGT = Weight 3 HI_WGT = Weight 3 LO AGE = Age 3 HI AGE = Age 3 XNHAIR HAIR = Hair 3 XNEYES EYES = Eyes 3 XNSKIN SKIN = Skin Tone 3 XNBUILD BUILD = Build 3 XNOCCUP OCCUPATION = Occupation 10 XNETH ETH = Eth 1 POB = Place of Birth ? XNRESID RESID STAT = Residence Status 6 CIT = Citizenship ? BLD ALC LVL = Blood Alcohol Level 4 XNALDRG ALC DRG USE = Alcohol/Drug Use 10 MUMI,,,, NOTE = Note 70 XNLOCTYP LOC_TYP = Address Type 5 XNIDTYP ID TYP = ID Number Type 6 ID NO = Nmbr 20 ID ISS = Iss 4 = ExpYr 4 XNPHTYP WOSA 10/97 PH TYP = Phone Number Type PH NO = Number PH NOTE = Note 4 14 16 -- FIELD CONTACT -- + ACTIVITY ---------------------- ---------------------------------- IAgcy FCPS Contact # 7380 Contact Date 01/09/1999 Time Reason SUSPICIOUS Status CLOSED + NAME ----------- -------- -------- ;Caution Weapons Ident # 353529622 ;Name Type P Name FINLEY, ROBERT GEORGE Race W Eth Sex M + )------------------------------------------------------ :Category Type Location Description ;Category COAT Type WINTER Color BLU/ Note DOWN -FILLED I / + 411111111MINIM -------------------------------------------------------- ;Type Modus Operandi I +---------------------------------------------------------------------------- -[Fort Collins LIVE System]---------------------------[PRC Public Sector, Inc.]- ---> 1=ALIAS 2=ASSOC 3=FEATURES 4=PROP/VEH 5=NAM SUPP TABLES FIELDS # CHARACTERS XNFTCAT FEAT CAT = Category 6 XNFTCAT FEAT TYP = Type 10 XNFTLOC FEAT LOC = Location 6 FEAT 9411MIM11MM NOTE Description 50 CAT = Category 10 TYP = Type 10 WOSA 10/97 COLORI = Color COLOR2 = Color NOTE = Note 23 PXMOTYP TYP = Type 10 VALUE = Modus Operandi 25 WOSA 10/97 -- FIELD CONTACT -- + ACTIVITY ------------------------------------------------------------------ ;Agcy FCPS Contact # 7380 Contact Date 01/09/1999 Time Reason SUSPICIOUS Status CLOSED + NAME ---------------------------------------------------------------------- ;Caution Weapons Ident # 353529622 ;Name Type P Name FINLEY, ROBERT GEORGE Race W Eth Sex M + ---------------------------------------------- Solvefact (23)> ; ; +---------------------------------------------------------------------------- -ZFopt Collins LIVE Systemi---------------------------ZPRC Pu`lic Sectop Inc- \ - --- > 1<ALIAS 2<ASSOC 3<FEATURES 3<PROP/VEG 5<NAM SUPP TABLES FIELDS # CHARACTERS Newsom Solvefact (23) ? WOSA 10/97 -- FIELD CONTACT -- + CONTACT ------------------------------------------------------ Agcy FCPS Contact -> No. 7380 Date 01/09/1999 Time Reason SUSPICIOUS Status CLOSED Location 300 N COLLEGE AV, FT COLLINS, CO 80521 Geo -> Patrol P5 Rep Dist E015 Map 29L1 Coord / + INIMM ----------------------------------------------------------------- Contacted subject hitch hiking north on College. He said he was just released out of prison for menacing and is on parole (Barnhill). 1 + ----------------------------------------- Event Class Agcy Reference Number +----------------------------------- -------------------- -[Fort Collins LIVE System] ----------- --[PRC/Public Mgmt. Services]- ---> 1=NAMES 2=VEHICLE 3=NOTES TABLES FIELDS # CHARACTERS NOTES = Notes EVENT CLASS - Event Class 8 AGCY Agcy 4 REF NO = Reference Number 12 WOSA 10/97 -- FIELD CONTACT -- + CONTACT ------------------------------------------------------------------- Agcy FCPS Contact -> No. 7380 Date 01/09/1999 Time Reason SUSPICIOUS Status CLOSED Location 300 N COLLEGE AV, FT COLLINS, CO 80521 Geo -> Patrol P5 Rep Dist E015 Map 29L1 Coord / + ------------------------------------------------------ -Status Lic Number Lic Issuer Lic Year Veh Type / Year Make Model Color Desc Vin +11INkNIFAININININflum----------------------------------------- Lic Type Invl Name FINLEY, ROBERT GEORGE DOB 09/08/1958 I +-------------------------------------------------------------------- -[Fort Collins LIVE System] ------------------------- [PRC/Public Mgmt. Services]- ---> 1-NAMES 2=VEHICLE 3=NOTES TABLES FIELDS # CHARACTERS INNINNIOW PPSTAT PV STATUS - Status 6 LIC NO = Lic Number 10 LIC ISS = Lic Issuer LIC YR = Lic Year PPLICTYP LIC TYP = Lic Type 2 PV_TYP = Veh Type 2 PV CATEGORY 8 WOSA 10/97 PXPATROL PXREPDIS WOSA 10/97 YEAR = Year MAKE = Make MODEL = Model COLORI = Color COLOR2 = Color Note = Desc PV_VALUE = Property SER1 = VIN/Ser # OAN = CAN REC DT = Recovered REC_VALUE = Value $ Type = Condition LOCATION = Location PAT AREA = Patrol REP AREA = Rep Dist MAP = Map Value $ Date 3 3 70 9 20 20 12 9 2 12 6 6 6 -- FIELD CONTACT -- + ACTIVITY -------------- --------------------------------------------- Agcy FCPS Contact # 7380 Contact Date 01/09/1999 Time Reason SUSPICIOUS Status CLOSED + NAME ------------ ------------ ------- ------------------- ;Caution Weapons Ident # 353529622 ;Name Type P Name FINLEY, ROBERT GEORGE Race W Eth Sex M + ------------------------------------------------------ Invl Status Type Year Make Model License Color I I I I I I I I I I I / / I I I / / I I I / / I I I / / I + _ _ _ _ -[Fort Collins LIVE System]---------------------------[PRC Public Sector, Inc.]- ---> 1=ALIAS 2-ASSOC 3=FEATURES 4=PROP/VEH 5=NAM SUPP TABLES FIELDS # CHARACTERS PINAMPRP = Invl WOSA 10/97 -- TRAFFIC COLLISION -- +1111M ---------- -------------------------------------------------- Agcy FOPS Report # 03-1234 Reported Date 01/20/2003 Time 13:50:10, Call Type MVAH&R Call Disposition RTF ;Location 1501 S LEMAY AV, FT COLLINS, CO Geo -> Patrol P2 Rep Dist I012 Map 301,4S Coord / Enter R to Mark RMS Ownership R From -> Date 01/20/2003/MON Time 13:50 To -> Date 01/20/2003/MON Time 13:50 +ONFAM----------------------------------------------------------------- IStreetl S LEMAY Impact NEAR Street2 E PROSPECT ;Traffic Area Acc Type HR Cause ;Number of Persons Killed Number of Persons Injured Damage $ + ------------------------------------------------ Summons Issued? (Y/N) N Original Processed? (Y) Y I +---------------------------------------------------------------------------- -[Fort Collins LIVE System]---------------------------[PRC Public Sector, Inc.]- ---> 1=NAME 2-VEHICLE 3=OFF/XREF 4=NARR IDX TABLES FIELDS # CHARACTERS ONNNNEMM REF NO = Report # 12 REF DT = Reported Date 10 REF_TM = Reported Time g PIINTYP EVENT TYP = Call Type 20 PIINSTAT EVENT STATUS = Call Disposition 6 LOCATION = Location (GEO File) ? PXPATROL PAT AREA = Patrol 6 PXREPDIS REP AREA = Rep Dist 6 WOSA 10/97 PIACCTYP PIPRIMCS WOSA 10/97 MAP = Map 6 BEG DT = From Date 14 BEG TM = From Time 8 END DT = To Date 14 END TM = To Time 8 STREETI = Streetl 19 IMPACT PT = Impact 15 STREET 2 = Street2 19 TRAF AREA = Traffic Area 10 ACC TYP = Acc Type 17 PRIM CAUSE = Cause 17 FATAL CNT = Number of Persons Killed 4 INJ_CNT = Number of Persons Injured 4 PROP DAMAGE = Damage $ 6 Summons Issued? 1 Original Processed? 1