H.9.21.1 Ability to define groups of users to query their status (i.e., "WHO CAD" would show all users logged into CAD, while "WHO RMS" would show all users logged into RMS). A: Existing Inform CAD ‐ Inform CAD can display all logged in users of CAD and Mobile.
H.9.22 CJIS Security Compliance: The proposed system complies with all FBI CJIS security policies. A: ExistingH.10.0 Geovalidation: The system will perform address geocoding using the city's GIS data and store the x/y/z values in the database.
A: Existing
Inform CAD performs address verification utilizing the City's GIS data. Coordinate information associated with the location is stored in the database.
H.10.1 Address Modification: The system allows an authorized user to modify street address files, including the ability to temporarily edi block face, dummy intersections, aliases, and commonplace files. A: Existing H.10.2 Coordinates in Degrees: The system displays and prints latitude/longitude coordinates expressed in degrees. A: ExistingH.10.3 Geocoding Relies on Granularity: The system automatically selects the most appropriate Geofile record of decreasing or increasing granularity to obtain geocoding of the greatest accuracy given the address provided in the applicable field. Information returned will include call sign (or dispatch position), name, and the person’s designated number as contained in their personnel file.
A: Existing
H.10.4 Geofile Loading: The system permits the loading of Geofile map modifications. Modifications are available to the user withou restarting the system. A: Existing
H.10.5 GIS Modification Immediately Available: The system allows modifications made to the GIS database to be available immediately and shall not require the system to be halted. A: Existing
H.10.6 ArcGIS-Compliant: The proposed system is Environmental Systems Research institute, Inc. (ESRI) ArcGIS-compliant. A: ExistingH.11.0 Mapping integration: The solution shall include an integrated mapping subsystem that will be used to provide geographic context to CAD/RMS/MDS records and perform spatial analysis of CAD/RMS/MDS data. A: Existing H.11.1 Location Verification: The mapping display and location verification process shall utilize the same geographical data sets or be created from the same data file. Maintaining two separate geographical databases is not acceptable. A: Existing H.11.2 Mapping Attributes: The system shall allow the authorized user to set the following attributes for the map:H.11.2.1 The default display position on the monitor. A: ExistingH.11.2.2 The default size of the map when it is displayed. A: ExistingH.11.2.3 The default view and zoom level. A: ExistingH.11.2.4 The default layers which will be displayed on the map. A: ExistingH.11.2.5 The colors utilized on the map shall be consistent with those chosen for use within CAD. (e.g.: If a unit's status changes, the colo used in CAD to signify that status (enroute, on scene, available, etc.) will also be used as the color of the unit on the map.) A: Existing CentralSquare Technologies 8 of 9
#11..
- 651 -
(H) Global Requirements
File
Number All Sections in This Workbook Contain Required Functionality, unless specifically noted as "OPTIONAL" Vendor Response Comments H.11.3 Map Manipulation Features: The system includes the following map manipulation functions:H.11.3.1 Zoom in and zoom out. A: ExistingH.11.3.2 Pan in any direction. A: ExistingH.11.3.3 Add and remove (i.e., view and hide) layers of the map. A: ExistingH.11.4 Map Manipulation from Sources: The system allows the user to manipulate the map (pan, zoom) from the command line, a menu command or with a mouse. A: Existing
H.11.5 GIS Layer Display: The system allows users to display any GIS layer that is part of the proposed system, on the map. A: ExistingH.11.6 Map Symbol Connection to Records: All map symbols representing an underlying text record will be associated with the text record such that a user shall have the ability to double-click, right-click or position the mouse on the icon and the textual record will be retrieved.
A: Existing
H.11.7 Map Zoom: The system allows users to enter a street address, intersection, commonplace name, or other verifiable location and have the map zoom to the location and place an icon in the correct position. A: Existing H.11.8 External Query Based on Geofile: The system provides the ability to query outside systems for additional GIS information. Fo example, it shall be possible for a user to retrieve and display aerial photos of a given area of the map from an external orthophotography system.
F: Not Available
Inform CAD Maps natively display orthophotography layers. Central Square also offers optional interfaces with Pictometry.
H.11.9 GPD-Definable Icons: The system allows users to define and utilize a different icon for each category of premise information. F: Not AvailableH.11.10 Location Based on Clicking: The system allows users to select a location by clicking on the map screen with a mouse (or other pointing device) and the application will display the nearest known street address, intersection name or commonplace name for nonaddressed locations (i.e., McDonalds). A: Existing H.11.11 Cut and Paste into the Location Field: The system allows the location information to be inserted into a screen by executing a “cut-and paste” procedure or by a similar function. A: Existing
H.11.12 Water Locations: if the identified location is on water and within the map area the application shall display/print the latitude/longitud coordinates. A: Existing
H.11.13 Latitude/Longitude Cutting/Pasting: The system allows the latitude/longitude coordinates information to be inserted into a screen by executing a “cut-and-paste” procedure or by a similar function. A: Existing H.11.14 Icon Display of Premise Information: The system displays icons which represent the presence of premise information at a location. A: ExistingH.11.15 Location of Route Blocks: The system displays the location of route blocks and impediments on the map by using different icons to represent common categories of impediments. A: Existing H.11.16 Table Creation and Viewing: The system allows authorized users to create and view tables for underlying data depicted on map. A: ExistingH.11.17 Graphical GIS Tools: The system includes graphical tools to allow authorized users to maintain, view, or print from the GIS database These tools shall have the following minimum capabilities:
H.11.17.1 Add, modify, or delete any graphic element (e.g., a street or intersection). A: ExistingH.11.17.2 Move any graphic element. A: ExistingH.11.17.3 Add, modify, or delete the database record associated with any graphic element. A: ExistingH.11.17.4 Add, modify, or delete the text labels associated with graphic elements on the map. A: ExistingH.11.18 Modifications to GIS Do Not interrupt Applications: Modifications made to the GIS database with the CAD/RMS/MDC tools shall be available immediately and shall not require the system to be halted. A: Existing H.11.19 Physical Identification of Non-Geocoded Locations: The system allows users to physically identify a location on a map to generate x/y/z coordinates for location-specific-data that doesn’t geocode. A: Existing H.11.20
Disaster Recovery: The system supports fail-over or concurrent operation from a geographically distant location.
A: Existing
CentralSquare offers geographically diverse disaster recovery data centers as an available option. We would be pleased to discuss GPD's specific requirements and provide a quote after additional discussion and discovery.
H.11.21 Environments: The solution should include the following environments: PROD, TRAIN, BUILD/TEST (with commands to make porting over to a different environment simple - single execution) A: Existing CentralSquare Technologies 9 of 9
#11..
- 652 -
#11..
- 653 -
(I) AVL
File
Numbe
r
All Sections in This Workbook Contain Required Functionality, unless specifically noted as "OPTIONAL" Vendor Response Comments AVL
I.1.0 CAD Automatic Vehicle Location (AVL) is integrated with the mobile solution. A: ExistingI.1.1 The solution supports numerous GPS devices including both TAIP and NMEA standards. A: ExistingI.1.2 The software provides configurable icons for tracking police units on the map. A: ExistingI.1.3 The CAD AVL Map allows a "quick access" option, using standard windows ribbon functionality. A: ExistingI.1.4 The software provides a playback feature. A: ExistingI.1.5 The Playback feature allows the selection of specific unit(s). A: ExistingI.1.6 The Playback feature allows the selection of date/time ranges. A: ExistingI.1.7 The Playback feature shows the unit location, coordinates, and speed for each stored AVL transmission.
I.1.8 More than one type of GPS standard may be used concurrently (for example, one agency's devices use TAIP, and another uses NMEA).A: Existing I.1.9 The system administrator may define criteria that affects how often AVL data is refreshed on the call screen (for example, call typ distance traveled, speed, etc). A: Existing
I.1.10 The AVL data is logged in the database and easily retrieved for reporting later. A: ExistingI.1.11 The logged data includes the LAT/LON, or X/Y/Z coordinates for each point that is captured. A: ExistingI.1.12 The solution includes a mechanism that allows authorized operators to "play back" AVL data within a given timeframe, for specific unit an entire range of units. A: Existing
I.1.13 The Playback feature may be provided to authorized personnel inside each agency. A: ExistingI.1.14 The solution includes a mechanism to save the AVL playback in a standard video format, such as WMV, MP4, etc. F: Not Available While supporting AVL playback, Inform
CAD does not natively include a screen capture or playback mechanism that employs Windows media files (WMV or MP4). There are many optional third‐party applications (not included) that are capable of performing this function such as Bandicam, SnagIt and Camtasia among others.
I.1.15 The software has the ability to provide mobile units with routing information to a dispatched incident from their current GPS/AVL location.A: ExistingI.1.16 AVL provides CAD with routing to an event using street impedances to factor fastest route. A: ExistingI.1.17 The map provides both turn by turn and route indicators. A: ExistingI.1.18 The CAD software provides a driving directions toolbar which launches a directions window for easy navigation, allowing the directio "float" over the map. A: Existing
I.1.19 Auto-routing supports both units to calls and from call to call. A: ExistingI.1.20 Auto-routing uses a "find route" function that allows both text based driving directions and a visual route line on the map. A: ExistingI.1.21 Operators (with the correct permission) can overlay historical AVL data collected from field units and display that data on the map.I.1.22 The AVL data may be played back in chronological sequence, showing the movement of the field unit over a specified period of time. A: ExistingI.1.23 Historical data from both the CAD and RMS systems may be overlaid on the same map (for example, a map showing all CAD calls rela to fireworks complaints, and all RMS contacts related to fireworks violations). A: Existing I.1.24 The solution has the ability to provide mobile units with routing information to a dispatched incident from their current GPS/AVL location.A: ExistingI.1.25 Ability to use AVL for closest dispatch A: ExistingI.1.26 Ability to add closest dispatch feature by Unit ID A: Existing CentralSquare Technologies 1 of 2
#11..
- 654 -
(I) AVL
File
Numbe
r
All Sections in This Workbook Contain Required Functionality, unless specifically noted as "OPTIONAL" Vendor Response Comments I.1.27
Ability to use AVL even when the mobile device is not turned-on by the user. A: Existing Compliance assumes that the mobilehardware is configured to support sending the GPS position data to CAD from the cellular modems and that the modems are configured to operate when the mobile device (laptop) is not turned on by the user.
CentralSquare Technologies 2 of 2
#11..
- 655 -
(J) JMS
File
Number
All Sections in This Workbook Contain Required Functionality, unless specifically noted as "OPTIONAL" Vendor Response Comments JAIL MANAGEMENT FUNCTIONALITY
J.1 Information entered into JMS shall be validated on entry, and identified errors shall be resolved before additional information can be entered. The system edits necessary to perform this validation shall be controlled by a combination of user-defined and user-maintained parameters. A list of possible values for each field of entry will be provided to the operator by pressingthe appropriate key sequence. These values will be user-maintained A: Existing J.2 JMS shall accept and correctly process hyphenated names in any name component, first, middle, and/or last A: ExistingJ.3 JMS shall use Soundex coding in name searches to minimize the impact names with similar and variant spellings and of misspelled names (either on entry or in requesting a name search) A: Existing J.4 JMS shall allow for interruptions in data entry to accommodate other necessary tasks (i.e., a user may interrupt entering suspect data in order to conduct an inquiry) A: Existing J.5 The user shall be able to request that JMS remind detention facility personnel (with audible and visual notifications) when they are to perform required actions. These may be inmate-specific (e.g., check an inmate on suicide watch), or they may be more general (e.g., check the contents of emergency-response kits). Users may schedule actions based on the following A: Existing J.5.1 Inmate information (Name) A: ExistingJ.5.2 Housing Location (Unit) A: ExistingJ.5.3 Booking Number A: ExistingJ.5.4 Type of Action Scheduled A: ExistingJ.5.5 Date and Time of Scheduled Action A: ExistingJ.5.6 Type of Alert A: ExistingJ.5.7 Position(s) to Receive Alert A: ExistingJ.6 Alert messages (such as computer-generated notifications, schedule reminders, and operator-error messages) shall be accompanied by suitable attention-getting audible signals A: Existing J.7 Solution will share data amongst all points of entry within RMS and JMS (For example, once booking information has been entered on an inmate, it is available to all other JMS functions: classification, housing, transportation, food services, commissary, and medical services) A: Existing
DETENTION PROCESSING AND ACCOUNTING
J.8 If a user attempts to input information out of sequence, or the information entered is inconsistent with requirements for information entry, the entry shall be rejected, and an error message shall indicate the reason for the rejection, and the minimum requirements that must be met for the entry to be accepted A: Existing J.9 The user shall be able to return to a screen already processed to add optional information, or to modify information previously entered A: Existing
J.10 JMS shall not allow the modification of previously stored information that creates inconsistent conditions A: Existing J.11 JMS shall allow a user to cancel an action at any time prior to his or her completion of that action A: Existing J.12 Upon determining that the user has canceled an action, JMS shall restore any interim information entries the user has made to their status prior to the initiation of the action A: Existing J.13 JMS shall allow the user the ability to access any screen with the minimal use of sub-menuing A: ExistingJ.14 JMS shall display an inmate's current account balance on the general information screen for each inmate F: Not Available J.15 A display shall indicate the current status of a booking, and shall permit the user to determine what has to be done to complete that booking A: Existing
J.16 The information typically entered into JMS on a booking is listed below. The information below shall be obtained initially from the RMS reporting module (used by officers for entering their crime and arrest reports). Any information that is not entered through RMS shall be entered directly into JMS. Notwithstanding the list below, the selected vendor’s solution must include all of the NIBRS and CIBRS data elements associated with an arrest, as defined in the Appendix (see CA DOJ CIBRS A: Existing CentralSquare Technologies 1 of 15
#11..
- 656 -
(J) JMS
File
Number
All Sections in This Workbook Contain Required Functionality, unless specifically noted as "OPTIONAL" Vendor Response Comments J.16.1 Name (Last, First, Middle, Suffix) A: Existing
J.16.2 AKAs (no limit) A: ExistingJ.16.3 Permanent Address A: ExistingJ.16.4 Temporary Address A: ExistingJ.16.5 Telephone Numbers(s) A: ExistingJ.16.6 Date of Birth (multiple) A: ExistingJ.16.7 Place of Birth (City, State, Country) A: ExistingJ.16.8 Foreign National A: ExistingJ.16.9 Social Security Number (multiple) A: ExistingJ.16.10 Sex A: ExistingJ.16.11 Race of Arrestee A: ExistingJ.16.12 Hair Color A: ExistingJ.16.13 Eye Color A: ExistingJ.16.14 Height (Feet and inches) A: ExistingJ.16.15 Weight (Pounds) A: ExistingJ.16.16 Scars, Marks, Tattoos: Common SMT (or SMTs) and location (or locations) selected from user-maintained lists; unusual SMT (or SMTs) described in a free-form text field A: Existing J.16.17 SMT image processing required - flag(s), identification(s), and location(s) to alert for unusual SMT(s) which should be recorded, usually when mug shots are recorded (manually set) A: Existing J.16.18 Date and Time of Arrest A: Existing
J.16.19 Arresting Agency A: ExistingJ.16.20 Arrest Location (Address and Common Place Name) A: ExistingJ.16.21 Arrest Charge(s) A: ExistingJ.16.22 Arresting Officer’s Department and ID A: ExistingJ.16.23 Transporting Officer’s Department and ID A: ExistingJ.16.24 Driver’s License Number (multiple) A: ExistingJ.16.25 Vehicle License Plate and State A: ExistingJ.16.26 Vehicle Disposition A: ExistingJ.16.27 Special Identifiers (i.e., Career Criminal, Sex Offender, etc.) A: Existing J.16.28 Gang Affiliation A: ExistingJ.16.29 Agency DR Number A: ExistingJ.16.30 Date and Time Booked A: ExistingJ.16.31 Booking Officer’s ID A: Existing J.16.32 Searching Officer’s ID A: ExistingJ.16.33 Arrest Bail (Automatically calculated from user-definable table) A: ExistingJ.16.34 Property Description (Cash and Non-Cash) A: ExistingJ.16.35 Booking ID Number (Jail Number) A: ExistingJ.16.36 Emergency Contact information A: ExistingJ.16.36.1 Name A: ExistingJ.16.36.2 Relationship A: Existing CentralSquare Technologies 2 of 15
#11..
- 657 -
(J) JMS
File
Number
All Sections in This Workbook Contain Required Functionality, unless specifically noted as "OPTIONAL" Vendor Response Comments J.16.36.3 Address A: ExistingJ.16.36.4 Telephone Number A: ExistingJ.16.37 Occupation A: Existing J.16.38 Employer(s) A: ExistingJ.16.38.1 Occupation A: ExistingJ.16.38.2 Name A: ExistingJ.16.38.3 Address A: ExistingJ.16.38.4 Telephone Number (Multiple) A: ExistingJ.16.39 FBI Number (multiple) A: ExistingJ.16.40 AFIS Number A: ExistingJ.16.41 State of California Identifier Number (CII) (multiple) A: ExistingJ.16.42 Department of Corrections Number (multiple) A: ExistingJ.16.43 Calculated Release Date A: ExistingJ.16.44 Citation Number A: ExistingJ.16.45 Internal Identification Number (Booking Number) A: ExistingJ.16.46 Alien Registration Number A: ExistingJ.16.47 Sentencing Date A: ExistingJ.16.48 Warrant arrest information A: ExistingJ.16.48.1 Judge name and information A: ExistingJ.16.49 Local and/or foreign warrant number A: ExistingJ.16.50 Foreign or out of County A: ExistingJ.16.50.1 Field to identify County A: ExistingJ.16.51 Warrant number A: ExistingJ.16.52 Remanded booking/Commitment Court-Ordered Booking B: Configuration J.16.53 Court case number A: Existing
J.17 JMS shall provide a field for the entry of an inmate's primary language and dialect, selected from a user-maintained list. The automatic default for this field shall be English. B: Configuration J.18 Bail Calculation: JMS shall compute bail based on a stored list of charges and associated bail amounts. Charges and associated bail amounts shall be user-maintained values. JMS shall place no limit on the number of charges and bail amounts it can store. JMS shall also prompt the user for data that cannot be determined from charge codes, but on which the bail depends (for those charge codes for which this information is required). Since some charges do not have a known bail (e.g., warrants), and not all charges will be in the system, JMS shall accept the manual computation and entry of bail.
The system shall also accept the values of: A: Existing J.18.1 "No bail" (i.e., no bail is required, if other conditions are met for release) A: Existing J.18.1.1 Name of authorizing personnel A: ExistingJ.18.2 Felony vs. Misdemeanor identification A: ExistingJ.18.3 Bail conditions A: ExistingJ.19 JMS shall display identifying information about an inmate, and the amount of bail required for his or her release from custody. This display shall include each charge and/or warrant that comprises the total amount of bail. JMS shall accept a bail transaction at the time of booking, or at any time while an inmate is in custody, but has not been convicted (excludes A: Existing J.20 The system should enable a checkbox for any cash bails received A: Existing CentralSquare Technologies 3 of 15
#11..
- 658 -
(J) JMS
File
Number
All Sections in This Workbook Contain Required Functionality, unless specifically noted as "OPTIONAL" Vendor Response Comments J.21 The following is typical of the information that JMS shall require to process bail: A: Existing J.21.1 Name of person or bonding company posting the bail A: Existing J.21.2 Amount of bail posted (partial or complete) A: ExistingJ.21.3 Charge or charges against which the amount of bail is to be applied - in order of application to bail amounts (if requested by person or bonding company posting bail) A: Existing
J.21.4 Bond number - for a bond only A: Existing
J.21.4.1 Name of bonding company A: ExistingJ.21.4.2 Name of insurance company insuring the bond A: ExistingJ.21.5 Dept. ID of Officer accepting the bail - entered by the system A: Existing J.21.6 Date and time bail was posted - entered by the system A: Existing J.22 Bail receipts for all participants shall be printed in sequential order A: Existing J.22.1 includes foreign currency calculation F: Not Available J.23 When JMS has received an amount of bail equal to the total for all charges, the system shall print a notice to release at the holding area printer (if the inmate has not been transferred to a housing unit) A: Existing or a file share; however, automated printing capabilites are not available.
J.24 The proposed solution will enable collection of intake medical information. A: Existing J.25 The proposed solution conforms with HIPPA regulations regarding security and privacy of medical data collection F: Not Available J.26 If JMS contains medical history based on a prior record (or records), the system shall alert the user when a previous dangerous condition has not been recorded during the current booking A: Existing J.27 A user shall be able to enter information on an inmate that indicates that he or she should not associate with other specific prisoners A: Existing
J.28 The system shall prohibit any inmates that should be kept separate from being placed in the same housing unit A: Existing J.29 The system shall provide an alert when inmates that should be separated will be assigned to the same activities and programs (e.g., will be transported on the same bus) A: Existing J.30 Alerts shall be included in any printed lists of inmates (e.g., daily worksheets) A: ExistingJ.31 Alerts should include phone restrictions A: Existing J.32 JMS shall accept miscellaneous comments entered as free-form text. Comments shall be kept in the order in which they are entered; and each comment shall include the Dept. ID of its author and the date and time of entry A: Existing J.33 Ability to prepare the following standard reports, in addition to ad hoc reports: A: ExistingJ.33.1 Monthly Arrest and Citation Register (MACR), submitted electronically monthly A: Existing Inform Jail has an integrated custom report builder that can build any reports needed by GPD.
J.33.2
Adult Disposition of Arrest and Court Action Report (JUS-8715) A: Existing Inform Jail has an integrated custom report builder that can build any reports needed by GPD.
J.33.3
Monthly Juvenile Detention Report A: Existing
Inform Jail has an integrated custom report builder that can build any reports needed by GPD.
J.33.4
Monthly Booking and Confinement Report A: Existing
Inform Jail has an integrated custom report builder that can build any reports needed by GPD.
J.33.5
Monthly Release Report A: Existing
Inform Jail has an integrated custom report builder that can build any reports needed by GPD.
J.34 Processing of inmate Cash: JMS shall establish a cash account for every inmate booked into the system, even if the inmate has no cash to deposit in it A: Existing
CentralSquare Technologies 4 of 15
#11..
- 659 -
(J) JMS
File
Number
All Sections in This Workbook Contain Required Functionality, unless specifically noted as "OPTIONAL" Vendor Response Comments J.35 JMS relies on the RMS Property/Evidence module for processing inmate property with single-sign-on access to RMS from JMS booking workstations (including all necessary bar-code technology/peripherals). F: Not Available Inmate property is logged separately from Inform RMS Property and Evidence module.
J.36 Setting Court Appearances/Dates: JMS shall determine, from a user-maintained list, the specific court that has jurisdiction over an inmate’s case A: Existing
J.37 Inmate identification information may be printed as a label on the booking sheet. The number, size, and content of any other labels printed on the booking sheet shall be user-definable A: Existing J.38 The inmate identification information shall include the following information A: ExistingJ.38.1 Name A: Existing J.38.2 Booking Number (numeric and bar code) A: ExistingJ.38.3 Bar Code Number A: ExistingJ.38.4 Mugshot Image A: ExistingJ.39 Home Custody/Work Release inmates: JMS will treat the booking of a home custody/work release inmate in an identical manner to that of a booking for a standard, continuous incarceration, except that the booking employee shall be able to: A: Existing J.39.1 Indicate to JMS that the sentence is to be served on a discontinuous basis by selecting custody/work release status on the appropriate booking screen A: Existing
J.39.2 Designate the periods of time during which the sentence will be served by selecting them from a calendar-like display A: Existing J.40 JMS shall allow a booking employee to enter a transfer of housing location to the inmate's residence address and retain an inmate's booking record in inactive status, pending the next period of incarceration (When the defendant returns to serve a subsequent period of incarceration, JMS shall allow a booking employee to retrieve and activate the defendant’s booking record, indicating a transfer from the defendant’s residence to a suitable housing location in the detention facility) A: Existing J.41 Disposition Information: JMS shall allow for disposition information to be entered into the RMS Master Name Index (MNI) record for an inmate F: Not Available
J.42 If the inmate is sentenced to serve time in local custody, then JMS shall have the ability to calculate the release date, considering credit for time served, “good time” and “work time” credits and debits, percentage reductions and any other sentence modifications allowed by law, any court or other lawful process. The algorithm for this calculation shall be usermaintainable and definable A: Existing J.43 JMS shall release inmates for any of the following reasons: A: Existing J.43.1 Time limit without arraignment has run - an inmate has been detained for the maximum allowable period of time without having been arraigned. This type of release shall cause JMS to distribute information on the release to a usermaintained list (e.g., responsible investigator, investigator's supervisor) A: Existing J.43.2 Time served (automatically calculated) A: Existing J.43.3 Court authorized - the standard type of release A: ExistingJ.43.4 Transferred - custody of an inmate has been transferred to another agency or person [e.g., home bracelet detention] A: ExistingJ.43.5 Escape A: ExistingJ.43.6 Parole A: ExistingJ.43.7 Temporarily released to external agency A: ExistingJ.43.8 Death A: ExistingJ.43.9 Remanded to prison - an inmate has been convicted, and is transferred to state or federal prison A: ExistingJ.44 At the time of an inmate's release, JMS shall display for the Officer performing the release functions the inmate's classification code and any special handling-alerts applicable to him or her (i.e., domestic violence notifications) A: Existing J.44.1 Prior to release, JMS shall conduct the following processes: A: Existing J.44.2 Check the Want/Warrant System to determine that the inmate is not subject to any outstanding warrants A: ExistingJ.44.3 Require a positive identification before any inmate can be released A: Existing CentralSquare Technologies 5 of 15
#11..
- 660 -
(J) JMS
File
Number
All Sections in This Workbook Contain Required Functionality, unless specifically noted as "OPTIONAL" Vendor Response Comments J.44.4 Update all inmate records (e.g., criminal history) A: ExistingJ.45 JMS shall prepare a daily booking log, which shall list all inmates booked during the preceding 24-hour period. The daily booking log shall typically contain the following information on each inmate: A: Existing J.45.1 Name - last, first, middle, suffix A: ExistingJ.45.2 Identification number A: ExistingJ.45.3 Booking date A: ExistingJ.45.4 Booking time A: ExistingJ.45.5 Arresting/booking agency A: ExistingJ.45.6 Date of birth A: ExistingJ.45.7 Sex A: ExistingJ.45.8 Race A: ExistingJ.45.9 Document number (or numbers) A: ExistingJ.45.10 Charge(s) A: ExistingJ.45.11 Office ID A: ExistingJ.45.12 Officer Name A: ExistingJ.45.13 Custody Status A: ExistingJ.45.14 Warrant Number (if any) A: ExistingJ.45.15 Type of Warrant (local, other) A: ExistingJ.46 JMS shall maintain a set of accounts that will report the balance of: A: ExistingJ.46.1 Accounts receivable for inmate worker pay A: Existing
Invoices can be manually entered and subsequent accounts receivable tracking can be tracked within Inform Jail.
J.46.2 Accounts payable for bail and fines A: Existing
J.47 JMS should have the ability to post bail and fine receipts to the General Ledger and generate the appropriate accounting reports
A: Existing
J.48 JMS should have the ability to place holds on inmate’s account transactions F: Not Available J.49 For previously released inmates that are re-booked with a new Identification number, the system should be able to track any remaining moneys or negative balances associated with the previous Identification number of this inmate A: Existing J.50 JMS shall generate the following reports on a routine, user definable basis: A: ExistingJ.50.1 Detention cash summary A: ExistingJ.50.2 Balance sheet A: ExistingJ.50.3 Proof-of-Cash report A: ExistingJ.50.4 General Ledger Activity report A: ExistingJ.51 Generate receipts on any money transactions A: Existing
IDENTIFICIATION REQUIREMENTS
J.52
Utilizing the Live-Scan device, a fingerprint technician shall be capable of downloading identification information on any subject match to JMS. The system should capture and populate the JMS entry fields for the following criteria: F: Not Available J.52.1 Name - last, first, middle, suffix F: Not AvailableJ.52.2 AKAs F: Not AvailableJ.52.3 Sex F: Not AvailableJ.52.4 Race F: Not AvailableJ.52.5 Height F: Not Available CentralSquare Technologies 6 of 15
#11..
- 661 -
(J) JMS
File
Number
All Sections in This Workbook Contain Required Functionality, unless specifically noted as "OPTIONAL" Vendor Response Comments J.52.6 Weight F: Not AvailableJ.52.7 Hair color F: Not AvailableJ.52.8 Eye color F: Not AvailableJ.52.9 Date of birth (multiple) F: Not AvailableJ.52.10 Place of birth F: Not AvailableJ.52.11 Social Security number (multiple) F: Not AvailableJ.52.12 Booking date F: Not AvailableJ.52.13 Charge (or charges) F: Not AvailableJ.52.14 Document number F: Not AvailableJ.52.15 Arresting agency NCIC code F: Not AvailableJ.52.16 Registrant information F: Not AvailableJ.52.17 CDC Number F: Not AvailableJ.52.18 FBI Number F: Not AvailableJ.52.19 CII Number F: Not AvailableJ.52.20 GPD's NCIC code F: Not AvailableJ.53 If problems exist in determining the correct match for the inmate being processed, JMS shall force alert messages to the terminals used by the Identification Unit and the Detention booking Officers where the inmate is currently being housed. F: Not Available J.54 JMS will inform detention processing once a booking has been cleared by identification via messaging and printing the inmate’s name, Identification number and booking ID number at the detention supervisor’s position B: Configuration J.55 JMS shall display summary of completed and pending identification requests B: ConfigurationJ.56 JMS will rely upon RMS Master Name index (MNI) files for initial identification match criteria A: ExistingJ.57 MNI match criteria shall result in possible matches being presented in summary form to the user, with the most probable matches presented first, and other possible matches presented in descending order of probability A: Existing J.58 Local matches will automatically and non-destructively update inmate data A: ExistingJ.59 if a search identifies a prior detention history, JMS shall display the following information: A: Existing J.59.1 Identification Number A: Existing All previous inmate history is available via the MNI entry's H J.59.2 Charge (or charges) for which the most recent prior detention was imposed A: Existing All previous inmate history is available via the MNI entry's HJ.59.3 Housing classification (or classifications) A: Existing All previous inmate history is available via the MNI entry's HJ.59.4 Medical history - if specific user-defined medical conditions appear in the prior history A: Existing All previous inmate history is available via the MNI entry's HJ.59.5 Discipline record - for the most recent prior detention A: Existing All previous inmate history is available via the MNI entry's HJ.59.6 Special situations A: Existing All previous inmate history is available via the MNI entry's HJ.60 JMS shall permanently store at least three color images for each arrestee per booking, each with a description attached A: ExistingJ.61 JMS shall automatically associate all images with a specified inmate's file, and store the date and time at which it was recorded with the image A: Existing
J.62 Users shall be able to retrieve and/or print any mug shots associated with a present or past inmate's record (or with any other person whose photograph is in the system for identification purposes) A: Existing J.63
JMS shall also provide the user with the capability to generate a photo-lineup of up to six mug shots with the followingcapabilities:
A: Existing
J.63.1 Ability to prepare montage images of subjects with similar physical characteristics A: ExistingJ.63.2 Ability to utilize images from local and stock (vendor provided) database files F: Not Available
Only mugshots associated with MNI entries can be used in the digital lineup function with Inform Jail.
J.63.3 Ability to prepare montage in less than 2 seconds A: Existing CentralSquare Technologies 7 of 15
#11..
- 662 -
(J) JMS
File
Number
All Sections in This Workbook Contain Required Functionality, unless specifically noted as "OPTIONAL" Vendor Response Comments J.63.4 Random placement of images in photo line-up A: ExistingJ.64 JMS shall store color images of scars, marks, and tattoos for each arrestee A: Existing J.65 JMS shall automatically associate all images of an inmate's scars, marks, and tattoos with his or her MNI, and store the date and time at which the images were recorded A: Existing J.66
JMS shall differentiate images of scars, marks, and tattoos from mug shots, and shall require the user to attach a two-part description to each image of a scar, mark, or tattoo: A: Existing J.66.1
Class and location. Classes shall be scars, marks, or tattoos. Locations of scars, marks, and tattoos shall be selectable from a user-maintained list (e.g., right upper arm, back of right hand, left shoulder). The user shall be required to make brief free-form text entries to describe the locations of scars, marks, and tattoos not included in the A: Existing J.66.2
Type, subtype, and words. Common types and subtypes of scars, marks, and tattoos shall be selectable from a usermaintained list. The user shall be able to describe unusual types and subtypes in free-form text entries. A tattoo of words shall also be entered as free-form text. Standard entries to use validation tables. A: Existing J.67 JMS shall perform a check for outstanding wants and warrant for every booking and release A: Existing J.68
For each remote (external) database (i.e., CLETS, NCIC) to be checked for wants and warrants, JMS shall generate a query in the format required by the database being checked, and shall route it to the target database. The response from the database shall be accepted in the format provided by the database, and converted to the format used by JMS D: Third Party Inform Jail can provide NCIC query capabilities; however, CentralSquare has not included in pricing.
J.69 JMS shall include additional information about holds that may be placed on the inmate A: ExistingJ.70 The system shall provide for including additional charges for an arrested person (i.e., rebook), relying on the RMS Warrants module (JMS imports all data entered within the RMS warrants module). F: Not Available Additional charges (i.e., rebook) can be added at any time but do not currently pull from Inform RMS warrants module.
J.71
If a person being booked refuses to identify himself or herself, or an identity cannot be determined, the JMS shall accept "REFUSED (M)," "REFUSED (F)," "UNKNOWN (M)," or "UNKNOWN (F)" in the name field. "(M)" and "(F)" shall indicate the sex of the unidentified inmate. This entry shall cause JMS to generate a refused or unknown name with the next sequential number (e.g., REFUSED (M)-106) F: Not Available Inmates with unknown names can be processed through Intake but will not get a special sequence number reserved for unknown inmates.
CLASIFICATION REQUIREMENTS
J.72 To support classification of inmates, JMS shall make available the inmate's criminal history record. A: Existing J.73
JMS shall support classification interviews by displaying interview questions along with potential responses (where they can be determined) and text-entry fields for narrative information (to supplement predetermined answers, or for questions with open-ended answers). The system allows for the following information entry: A: Existing J.73.1 Current charge (or charges) for assault felony (or felonies), including attempts - code section selected from a usermaintained list A: ExistingJ.73.2 Convictions for prior assault felonies - code section (or sections) selected from a user-maintained list A: ExistingJ.73.3 Current charge (or charges) for sex offense (or offenses), including attempts - code section selected from a usermaintained list A: Existing J.73.4 Convictions for prior sex offenses - code section (or sections) selected from a user-maintained list A: ExistingJ.73.5 Escapes from medium- and maximum-security facilities, including attempts - facility (or facilities), date (or dates) A: Existing J.73.6 Institutional behavior problems - type (or types) selected from a user-maintained list, detention facility, date (or dates) or, for numerous problems, number of episodes and range of dates A: Existing J.73.7 Felony convictions in the past five years, including those for nonviolent crimes A: ExistingJ.73.8 Sentencing status - all cases resolved, additional cases pending A: ExistingJ.73.9 Most recent incarceration - location, release date A: ExistingJ.73.10 Previous state or federal prison commitments and level, including California Youth Authority - locations, time spans A: ExistingJ.73.11 Current probation status - type, probation officer's name A: ExistingJ.73.12 Parole status - parole office, parole officer's name A: Existing CentralSquare Technologies 8 of 15
#11..
- 663 -
(J) JMS
File
Number
All Sections in This Workbook Contain Required Functionality, unless specifically noted as "OPTIONAL" Vendor Response Comments J.73.13 Gang affiliation - name of gang, street/prison, membership status (active, associate, former), length of time in the gang, gang moniker A: Existing
J.73.14 Enemies - name (or names) of known enemies in custody, current housing location of enemies A: Existing J.73.15 Status as informant, witness, or recipient of protective custody - reason, location, agency, agency contact, confirmed/unconfirmed A: Existing
J.73.16 Gender identity (M, F, M-F, F-M) A: Existing
J.73.17 Other special housing requirements - youthful appearing, has been assaulted, elderly, other A: Existing J.73.18 Current medical problems - cardiac, respiratory, other; if under treatment, physician, physician's telephone number (with area code) A: Existing
J.73.19 Currently taking medication - type (or types), required while in detention, inmate supplied A: ExistingJ.73.20 Psychiatric/emotional problems - type; if under treatment, therapist/ counselor, therapist/ counselor's telephone number (with area code) A: Existing
J.73.21 Suicide attempts - when, method, current suicidal feelings A: ExistingJ.73.22 Allergies A: ExistingJ.73.23 Physical handicaps - type, restricted access, medication required, subject to victimization A: ExistingJ.73.24 Drug/alcohol abuse - type (or types) selected from user-maintained list, injected, length of use, most recent use A: ExistingJ.73.25 Special identifiers - selected from a user-defined list (e.g., career criminal, child abuse offender, child abuse victim) A: Existing J.73.26 Comments - any additional information entered as free-form text A: ExistingJ.74 Based on the information input by the classification interviewer, JMS shall use an algorithm to generate a recommended classification code A: Existing
J.75 The system shall set special handling alerts A: ExistingJ.76 The classification recommendation is subject to supervisor-approved change A: Existing J.77 JMS shall identify unoccupied housing locations which have been pre-designated to be acceptable for the particular inmate’s classification code and display a list of available beds A: Existing J.78
Before accepting a housing location, JMS shall check inmate records for the housing location against the inmate(s) to be housed for any restrictions for “keep separate”, co-defendant(s), gang restrictions, etc. and display an alert message indicating the restriction reason A: Existing J.79
If the classification officer chooses to place an inmate in a location deemed unsuitable by JMS, the system must allow for an explanation for over-ride field (free form text narrative), subject to supervisory approval F: Not Available
A special permission is required for a user to override a no contact violation but there is no narrative field available at the time of override.
J.80 JMS shall accept an unlimited number of inmate reclassifications A: Existing J.81 JMS shall also accept an unlimited number of actions to rehouse inmates as required by reclassifications A: Existing J.82 JMS shall maintain a housing history on each inmate and shall update RMS MNI with associate information based upon proximate inmate population A: Existing All housing history is maintained within Inform Jail, not Inform J.83 JMS shall maintain an audit trail of all classification and reclassification actions A: Existing J.84 The system should have the ability to track all inmate movement (virtually every movement of a prisoner, regardless of how slight) A: Existing
J.85 JMS shall generate reports designed to evaluate the effectiveness of the Department's classification activities. These shall include the following: A: Existing
J.85.1 Monthly list of inmates requiring reclassifications A: Existing J.85.2 Monthly summary of vacancies F: Not Available
J.85.3 Daily report of all major disciplinary actions A: Existing J.85.4 Discipline summary A: Existing
CentralSquare Technologies 9 of 15
#11..
- 664 -
(J) JMS
File
Number
All Sections in This Workbook Contain Required Functionality, unless specifically noted as "OPTIONAL" Vendor Response Comments J.85.5 initial classification delay summary report A: ExistingJ.85.6 Reclassification delay summary report A: Existing J.85.7 initial and reclassification delay summary report A: Existing J.85.8 Classification override summary A: ExistingJ.85.9 Classification Levels by housing A: Existing J.86 JMS shall provide full CLETS integration accessible from any RMS/JMS workstation D: Third Party Inform Jail does provide CLETS query capabilities; however, CentralSquare has not been included in pricing.
J.87 JMS shall be interfaced with LiveScan for all fingerprint exchanges to/from CAL ID F: Not Available Inform Jail provides a one‐way interface to Livescan.
HOUSING REQUIREMENTS
J.88 JMS shall provide the capability to record information on all special situations involving any inmate. Typical information to be collected shall include: A: Existing
J.88.1 All information available in the RMS AFR incident/arrest reporting modules. A: ExistingJ.88.2 Inmate (or inmates) involved - name and Identification number (if several inmates are involved, the incident will be recorded in all their booking records). A: Existing
J.88.3 Incident types that are unique to the jail (i.e., medical, psychiatric, violent behavior, criminal act, other disciplinary matter, refusal to accept a meal, refusal to accept medicine, telephone call, other) A: Existing J.89
The system shall determine which inmates are scheduled for court appearances; medical, dental, and psychiatric appointments; work furlough; and work release programs each day, and shall prepare lists, which are organized by unit (or house) and/or cell or bed assignment. These lists shall be printed out in each detention facility on a daily basis at 6:00 AM (or at another user-selectable time). The list for each unit, module and/or cell or bed assignment shall show: A: Existing Recurring reports can be created that can be sent to email or a file share; however, automated printing capabilites are not available.
J.89.1 Inmate's name A: ExistingJ.89.2 Identification number A: ExistingJ.89.3 Destination (court, clinic, work furlough location, work release crew) A: ExistingJ.89.4 Start time of inmate's activity - appearance, appointment, departure (date, time) A: Existing J.89.5 End time of inmate's activity - returns of work furlough participant only (date, time) A: ExistingJ.89.6 Holds and charges - court appearances only A: Existing J.89.7 Document number (or numbers) - court appearances only A: ExistingJ.90 JMS shall prepare lists of all inmates scheduled for court appearances, organized by court and showing the following A: ExistingJ.90.1 Inmate's name - last, first, middle, suffix A: ExistingJ.90.2 Special handling alert (or alerts), if any - escape risk, combative, suicide risk, other at risk from enemies, high-profile A: ExistingJ.90.3 Classification code A: ExistingJ.90.4 Date of birth A: ExistingJ.90.5 Sex A: ExistingJ.90.6 Identification number A: ExistingJ.90.7 Booking date A: ExistingJ.90.8 Arresting agency A: Existing J.90.9 Bail amount A: ExistingJ.90.10 Housing location - unit (or house), module and/or cell or bed assignment A: Existing J.90.11 Time of inmate's appearance A: ExistingJ.90.12 Charges A: ExistingJ.90.13 Holds A: Existing CentralSquare Technologies 10 of 15
#11..
- 665 -
(J) JMS
File
Number
All Sections in This Workbook Contain Required Functionality, unless specifically noted as "OPTIONAL" Vendor Response Comments J.90.14 Document number (or numbers) A: ExistingJ.91 JMS shall be capable of displaying various entry fields based upon the type of visitor (e.g., attorney vs. spouse) B: Configuration
for each visitor type if the standard set of fields does not cover all possible data.
J.92 JMS shall have the capability to manage both personal and professional (e.g., attorney) visits. Management shall include: A: Existing J.92.1 Maintaining lists of visitors authorized to see (or prohibited from seeing) each inmate A: Existing J.92.2 Running want and warrant checks on visitors A: ExistingJ.93 JMS shall accept entry of the names of and identifying information for persons authorized to visit each inmate A: ExistingJ.94 Identifying information for each visitor and each inmate he or she will visit shall be user-defined, and shall typically include: A: Existing J.94.1 Name - last, first, middle, suffix B: Configuration J.94.2 Name of firm (professional visits only) B: ConfigurationJ.94.2.1 CAL BAR Card Number (professional visits only) A: Existing J.94.3 Address - street number, direction, street name, street type, apartment number, city, state, zip code A: ExistingJ.94.4 Telephone number (with area code) A: ExistingJ.94.5 Name of inmate to be visited - last, first, middle, suffix A: Existing J.94.6 Identification number A: ExistingJ.94.7 Housing location - unit (or house), module and/or cell or bed assignment A: ExistingJ.94.8 Relationship - personal: specific relationship, professional (selected from a user-maintained list) A: Existing J.94.9 Date of birth A: ExistingJ.94.10 Social Security number A: ExistingJ.94.11 Passport or VISA A: ExistingJ.94.12 Driver's license number and state A: Existing J.94.13 Date authorized A: ExistingJ.94.14 Dept. ID of the person authorizing visits B: Configuration J.94.15
Access level - personal visits: specific facility at which person to be visited is housed; professional visits: one or more specified facilities; contact or non-contact visits A: Existing J.95 The system shall also alert the user to requests for visits by restricted persons A: ExistingJ.96 The system shall produce a visitor tracking report for those visitors identified by the user or to track all visitors to a particular inmate A: Existing
J.97 JMS shall allow for free-form narrative text entries in either the inmate’s record or the Visitor Tracking Records A: Existing J.98 JMS shall assist the staffs of the detention facilities in selecting inmates to serve as inmate workers, and in managing them A: ExistingJ.99 JMS shall identify inmates whose classifications indicate that they are potentially suitable for employment as inmate workers F: Not Available J.100 JMS shall prohibit overriding the exclusion of inmates with unsuitable classification codes from the inmate workers list A: Existing J.101 JMS shall also find suitable housing for inmate workers A: Existing J.102 The system's inmate worker management capabilities shall include: A: ExistingJ.102.1 Keeping track of inmate workers' assignments and schedules A: ExistingJ.102.2 Calculating each inmate’s accrual of total community service hours served A: ExistingJ.102.3 Tracking each inmate worker's job performance and discipline problems A: ExistingJ.102.4 Providing input to calculation of potential sentence reductions A: ExistingJ.103 JMS shall provide inmate worker officers (and other inmate worker supervisors) the capability to input lists of job assignments for inmate workers, and to schedule the inmate labor necessary to fulfill those assignments. Scheduling shall allow for staffing inmate worker positions 24 hours a day, seven days a week A: Existing CentralSquare Technologies 11 of 15
#11..
- 666 -
(J) JMS
File
Number
All Sections in This Workbook Contain Required Functionality, unless specifically noted as "OPTIONAL" Vendor Response Comments J.104 JMS shall print an inmate workers status list A: ExistingJ.105 Report summary for single or group of inmates A: ExistingJ.106 JMS shall have the capability to determine and accumulate the cost associated with housing and/or controlling inmates who are incarcerated for agencies other than GPD. A: Existing J.107
The system shall determine which inmates are being housed on a reimbursable basis and will store the rate per day for each inmate for each external agency A: Existing
J.108 JMS shall generate a monthly report identifying for each external agency: A: Existing J.108.1 Names of inmates housed and/or controlled during reporting period A: ExistingJ.108.2 Identification numbers A: ExistingJ.108.3 Start and end dates of each inmate's incarceration and/or control period A: ExistingJ.108.4 Daily charge for housing and/or controlling each inmate A: Existing J.108.5 Special charges, if any, itemized by date and type for each inmate (for example, transportation charges) A: Existing
some items, not all. Other items not available in the standard jail billing report can be reported on using a separate report.
J.108.6 Total charges and offsets for housing and/or controlling each inmate during the reporting period A: ExistingJ.108.7 Total charges and offsets for housing and/or controlling all inmates during the reporting period A: Existing
TRANSPORTATION REQUIREMENTS
J.109
The system shall determine which inmates are scheduled for court appearances; medical, dental, and psychiatric appointments; transportation to special destinations, and transfers from one detention facility to another, and shall prepare daily transportation lists. The list shall show all inmates that are to be transported to each specific destination. The inmates going to each destination shall be listed alphabetically by last name A: Existing J.110 The system shall accommodate special transportation requests and will capture the following information:J.110.1 Identity of vehicle(s) A: ExistingJ.110.2 Departure location - standard locations: selected from a user-maintained list; special locations: entered as free-form text (can include out-of-state locations) A: Existing
J.110.3 Departure odometer reading - edited against the immediately previous entry for this vehicle F: Not Available
Odometer reading can be entered manually but not pulled from the previous record.
J.110.4 Departure date A: ExistingJ.110.5 Planned departure time - hours, minutes A: Existing J.110.6
Arrival location - standard locations: selected from a user-maintained list; special locations: entered as free-form text (can include out-of-state locations) A: Existing
J.110.7 Arrival odometer reading - edited against the immediately previous entry F: Not Available
Odometer reading can be entered manually but not pulled from the previous record.
J.110.8 Arrival date A: ExistingJ.110.9 Estimated travel time - hours, minutes A: Existing J.110.10 Number of inmates to be transported A: ExistingJ.110.11 Number of other persons to be transported (if any, excluding the driver) A: ExistingJ.110.12 Special instructions and other comments - selected from a user-maintained list; or entered as free-form text A: ExistingJ.110.13 Dept. ID of driver A: ExistingJ.111 JMS will immediately route priority messages to transportation detail employees upon any schedule change A: Existing J.112 JMS shall maintain a log of each transportation run. Each record shall typically contain the following information: A: Existing CentralSquare Technologies 12 of 15
#11..
- 667 -
(J) JMS
File
Number
All Sections in This Workbook Contain Required Functionality, unless specifically noted as "OPTIONAL" Vendor Response Comments J.112.1 Identity of vehicle A: ExistingJ.112.2 Departure location A: ExistingJ.112.3 Odometer reading - edited against the immediately previous entry for this vehicle F: Not AvailableJ.112.4 Departure date A: ExistingJ.112.5 Departure time - hours, minutes A: Existing J.112.6 Arrival location A: ExistingJ.112.7 Arrival odometer reading - edited against the immediately previous entry F: Not Available J.112.8 Arrival date A: ExistingJ.112.9 Arrival time - hours, minutes A: ExistingJ.112.10 Number of inmates transported A: ExistingJ.112.11 Number of other persons transported A: ExistingJ.112.12 Special instructions and other comments A: ExistingJ.112.13 Driver's comments A: ExistingJ.112.14 Dept. ID of driver A: ExistingJ.112.15 Dept. ID(s) of other Department personnel, if any, assigned to the run for official reasons (e.g., to provide security) A: Existing J.113 Transportation entries should be input through the following: A: ExistingJ.113.1 Preparation of daily transportation lists A: Existing J.113.2 Input of a special transportation request A: ExistingJ.114 JMS shall maintain a list of all scheduled runs (from daily transportation lists and change messages), and shall print out a list of runs on the previous day for which run information has not been entered A: Existing or a file share; however, automated printing capabilites are not available.
J.115 Description of reimbursable runs A: ExistingJ.116 Vehicle log A: ExistingJ.117 Transportation summary to include the following: A: Existing J.117.1 Total number of trips A: ExistingJ.117.2 Number of inmates transported A: ExistingJ.117.3 Number of other persons transported A: ExistingJ.117.4 Number of miles traveled A: Existing
MEDICAL SERVICES REQUIREMENTS
J.118
JMS shall enable the creation of a medical record for all established inmates (regardless of whether there are any identifiable medical problems) F: Not Available
J.119 JMS will integrate with the State of California’s Health and Human Services application F: Not AvailableJ.120 JMS shall provide for the scheduling, rescheduling, and cancellation of appointments with both staff and outside practitioners.
A: Existing
While Inform Jail does not include a full medical module, scheduling and tracking of inmate movements to and from medical appointments can be accomplished.
J.121 After an inmate has been seen by a practitioner, JMS shall create and maintain a chart as part of the inmate's medical record. For the initial and each subsequent visit, the inmate's chart contains the following types of information:
J.121.1 Name F: Not Available
J.121.2 Identification number F: Not AvailableJ.121.3 Housing location - unit (or house) and cell F: Not AvailableJ.121.4 Practitioner seen - name of physician, dentist, nurse seen F: Not Available CentralSquare Technologies 13 of 15
#11..
- 668 -
(J) JMS
File
Number
All Sections in This Workbook Contain Required Functionality, unless specifically noted as "OPTIONAL" Vendor Response Comments J.121.5
Location, if outside the detention facility - street number, direction, street name, street type, suite number, city, zipcode F: Not Available
J.121.6 Telephone number (with area code), if outside the detention facility F: Not AvailableJ.121.7 Inmate's complaint (or complaints) F: Not AvailableJ.121.8 Vital signs and other physical examination findings F: Not AvailableJ.121.9 Diagnosis F: Not AvailableJ.121.9.1 Treatment plan F: Not AvailableJ.121.9.2 Medication (or medications) F: Not AvailableJ.121.9.3 Special diet - type, start date, stop date F: Not AvailableJ.121.10 Laboratory tests and X-rays F: Not AvailableJ.121.11 Follow-up chart review F: Not AvailableJ.121.12 Hospitalization, if required F: Not AvailableJ.121.13 Institution to which inmate is to be transferred, method of transportation (ambulance company, other) F: Not AvailableJ.121.14 Follow-up appointment (or appointments) - for each: date; practitioner, if known; location F: Not AvailableJ.121.15 Billing costs for internal expenses F: Not AvailableJ.121.16 Other information, as appropriate F: Not Available GPD JMS Reporting
J.122 JMS shall also prepare and automatically print the following reports at a user-defined interval: A: ExistingJ.122.1 Recap of jail statistics A: Existing or a file share; however, automated printing capabilites are not available.
J.122.2 Unit list - name sequence A: Existing
or a file share; however, automated printing capabilites are not available.
J.122.3 Unit list - name within cell sequence A: Existing or a file share; however, automated printing capabilites are not available.
J.122.4 Unit list - identification number sequence A: Existing or a file share; however, automated printing capabilites are not available.
J.122.5 Inmate housing location, by hour A: Existing
or a file share; however, automated printing capabilites are not available.
J.122.6 Inmate - by location with charges A: Existing
or a file share; however, automated printing capabilites are not available.
J.122.7 Inmate master list
A: Existing
or a file share; however, automated printing capabilites are not available.
J.122.8 Reproduction of inmate roster from specification A: Existing or a file share; however, automated printing capabilites are not available.
J.122.9 Daily Activity Log (Including prior period arrests, detentions, releases, incidents, dispositions, and user defined fields.
For each activity, the report identifies the officer/user-ID, date/time of activity, and notes.) A: Existing or a file share; however, automated printing capabilites are not available.
J.122.10 Inmate master list
A: Existing
or a file share; however, automated printing capabilites are not available.
J.122.11 Reproduction of inmate roster from specification A: Existing or a file share; however, automated printing capabilites are not available.
CentralSquare Technologies 14 of 15
#11..
- 669 -
(J) JMS
File
Number
All Sections in This Workbook Contain Required Functionality, unless specifically noted as "OPTIONAL" Vendor Response Comments GPD JMS Interfaces
J.123 JMS must be integrated with the following two systems: A: ExistingJ.123.1 Los Angeles Regional Crime Information System (LARCIS): The Data Systems Bureau houses the Los Angeles Regional Crime Information System ((LARCIS) that contains records of all incidents or events resulting in a report. Since the late 1990's LARCIS has served as the LASD RMS. LARCIS is an in-house designed RMS that is Oraclebased and housed on an HP-UX Superdome.
A: Existing
CentralSquare has extensive experience providing interface capability to LiveScan applications. While we are confident that our Inform Jail application can interface with LARCIS, we require additional information regarding GPD requirements including but not limited to the information transmitted, mode, and frequency to scope the interface. CentralSquare looks forward to this conversation with GPD in order to provide a firm, fixed quote J.123.2
Automated Justice Information System (AJIS): The LA Sheriff's Department uses an internally-developed solution called AJIS to managae the information system requirements of the jail. Other ancillary systems are used to facilitate the agency's ability to report on jail activity. The AJIS solution is in the process of being replaced by JIMS from Syscon Justice Systems.
A: Existing
Based on the RFP requirement, CentralSquare understands that AJIS will be replaced by JIMS. CentralSquare has extensive experience providing interface capability to various third party applications. While we are confident that our Inform Jail application can interface with JIMS, we require additional information regarding GPD requirements including but not limited to the information transmitted, mode, and frequency to scope the interface.CentralSquare looks forward to this conversation with GPD in order to provide a firm, fixed quote CentralSquare Technologies 15 of 15
#11..
- 670 -
#11..
- 671 -
(K) APCO Unified CAD
File
Number All Sections in This Workbook Contain Required Functionality, unless specifically noted as "OPTIONAL" Vendor Response Comments CALL HANDLING / CAD EVENT CREATION
K.1.0 The CAD will support an E-911 interface to import ANI/ALI and other specific call information into the system. A: ExistingK.1.1 The CAD will import a call for service generated on a remote workstation and mobile devices. A: ExistingK.1.2 The CAD will allow for multiple data entry and function access (i.e.. Command Line, Drag-N-Drop, Right Mouse Click, map dispatching and Function Keys). A: Existing
CAD Incident/Event Types
K.1.3 The CAD will allow for system administrator-defined CAD incident types or nature codes. A: Existing K.1.4 The CAD will allow system users to modify the incident type and provide new/updated response plan information/recommendations based on the new incident type. A: Existing
K.1.5 The CAD will provide the capability to create an event, assign a unit, and close the event with a disposition without going through the dispatch process steps. A: Existing
K.1.6 The CAD will allow entry of scheduled recurring events. A: Existing Update Call for Service Event Data
K.1.7 The CAD will enable a user to enter supplemental (new) information into the call for service event record. A: Existing K.1.8 The CAD will display a notification of the event update at each appropriate CAD position whenever an event record is updated, as determined by the system's configuration. A: Existing
K.1.9 The CAD will create an automatic time/date stamp for every transaction related to an event and store the responsible user ID, workstation ID and the nature of the change. A: Existing K.1.10 The CAD will add audit records to the event history or store audit records in the CAD system's audit log file. A: ExistingK.1.11 The CAD will create a permanent audit trail for all information recorded related to an event. A: ExistingK.1.12 The CAD will support ease of entry for supplemental event information and changes to existing event information. A: ExistingK.1.13 The CAD will allow the user to display a supplemental data entry screen by specifying either the event number or a unit assigned to the event. A: Existing
K.1.14 The CAD will allow the user to display a data entry screen to change information previously entered into a CAD event by specifying either the event number or a unit assigned to the event. A: Existing K.1.15 The CAD will allow the user to display a data entry screen to change information previously entered into a CAD event by specifying either the event number or a unit assigned to the event (noting that this functionality would not apply to closed CAD events/units). A: Existing K.1.16 The CAD will provide agency-definable visual and audible alerts to notify CAD system users (including users of systems interfaced to CAD such as Mobile Data Computers), of event changes and supplemental information. A: Existing K.1.17 The CAD will document all changes and supplemental information in the event history. A: ExistingK.1.18 The CAD will allow the user to update or change a unit’s most recent event by entering the unit’s identification or any unit that is currently assigned. A: Existing
K.1.19 The CAD system will allow the department to use agency-definable case numbers and allow numbers to be rolled monthly or yearly. A: ExistingK.1.20 The CAD system will allow various file types to be attached to CAD incidents and viewed. A: ExistingK.1.21 The CAD system will provide function key access for frequently used screens and functions (Traffic Stops, Unit Indicated Incidents, New Call Screens, etc.), which can be set by the agency. A: Existing K.1.22 The CAD system will include a remarks field for user-defined text and characters (including the ID of those who request report numbers, transportation data including purpose, arrival, and date/time, etc.). A: Existing Utilize Incident Disposition
K.1.23 The CAD will allow the user to enter one or more dispositions, as dictated by agency policy, when a CAD event is closed. A: ExistingK.1.24 The CAD will allow a CAD event to be closed OR placed back in pending if no remaining resources are assigned to the event. A: ExistingK.1.25 The CAD will allow the system administrator to define disposition codes. A: ExistingK.1.26 The CAD will allow a mobile unit to enter one or more dispositions when clearing from a CAD event. A: Existing Assign Incident Classification and Priority
CentralSquare Technologies 1 of 12
#11..
- 672 -
(K) APCO Unified CAD
File
Number All Sections in This Workbook Contain Required Functionality, unless specifically noted as "OPTIONAL" Vendor Response Comments K.1.27 The CAD will enable CAD users to select the appropriate incident/event type from a pre-defined list of codes based upon information received from reporting party. A: Existing
K.1.28 The CAD will provide the ability to generate a CFS event with only the location and incident type code entered. A: ExistingK.1.29 The CAD will allow the user to utilize incident screening menus, such as a drop-down menu, to assist in determining the appropriate incident/event type code. A: Existing
K.1.30 The CAD will allow the user to interrupt the CFS event creation process and save entered information, sometimes known as call stacking, to process a higher priority incoming incident. A: Existing K.1.31 The CAD will provide a warning notification of the held CFS event generated at an administrator-configured time. Any position can review current CFS events, retrieve a partial CFS record, and complete the CFS event entry. A: Existing K.1.31.1 Upon the entry of user-defined high-priority type codes (i.e., homicide, shooting), all on-duty dispatchers will receive an audible and visual alert. A: Existing
Check for Duplicate Incidents
K.1.32 The CAD will identify during the creation of a CFS event whether the event is a potential duplicate of an active CAD event or an event recently closed; and notify the call taker of the results (noting that closed CFS will not be presented as duplicates). A: Existing K.1.33 The CAD will present the user with the following information for each potential duplicate event if potential duplicates are located:
Incident ID, Incident Type, Incident Location, and Status. A: Existing K.1.34 The CAD will allow the user the ability to create a new CFS event and link the event to the primary event record; or, to merge any new information contained in a duplicate event into the main event record associated with the identified duplicate CAD event. A: Existing Location Verification
K.1.35 The CAD will validate all streets, intersections and address ranges and resolve ambiguities, while accounting for spelling variations and duplications. A: Existing
K.1.36 The CAD will validate entered incident addresses against the CAD geofile, using ESRI source data. A: ExistingK.1.37 The CAD will relate latitude, longitude, altitude (X/Y/Z) coordinates to an actual address and display on map. A: ExistingK.1.38 The CAD will provide the ability to enter a unique building and unit number to clearly identify the location. A: ExistingK.1.38.1 The location may be manually entered without validation, subject to validation prior to call closure. A: ExistingK.1.39 The CAD will provide various suggestions to assist users in selecting accurate incident locations. A: ExistingK.1.40 The CAD will allow each address or commonplace name to have an unlimited number of alias names that will appear on the calltaker's screen. A: Existing
K.1.41 The CAD will organize the display of possible address matches in an ergonomic, easily understood manner that aids users in identifying valid incident locations. A: Existing
K.1.42 The CAD will allow authorized users to configure their tactical map display to show jurisdictional boundaries (e.g. town boundaries) and to display potential valid incident locations by jurisdiction. A: Existing K.1.43 The CAD will provide the ability to enter a partial street name, with a minimum number of characters, and be presented with a list of possible matches to pick from for an exact match. A: Existing K.1.44 The CAD will provide the ability to enter a misspelled street name and be presented with a list of possible matches based on SOUNDEX and/or other methodology. A: Existing
K.1.45 The CAD will provide the ability to enter an incorrect street address for a correct street name and be presented with a list of valid ranges. A: Existing
K.1.46 The CAD will provide the ability to enter common street alias and abbreviations instead of the actual street name. A: ExistingK.1.47 The CAD will provide the ability to display the incident location in relation to other active incidents on the system’s tactical map display during the CAD event entry process.
K.1.48 The CAD will display premise warnings, hazards or alerts on the location of the incident. A: Existing Involved Person or Vehicle Information
K.1.49
The CAD will display prior incidents that occurred at an incident's location within a configurable period of time.
A: Existing
Inform CAD is compliant with showing prior incidents; however, this configuration is based on an GPD‐determined number of previous incidents, not by time frame.
CentralSquare Technologies 2 of 12
#11..
- 673 -
(K) APCO Unified CAD
File
Number All Sections in This Workbook Contain Required Functionality, unless specifically noted as "OPTIONAL" Vendor Response Comments K.1.50 The CAD will initiate an automatic query, upon entry of information about an individual associated with an event, using the following guidelines at a minimum: 1) If the name only is known, then a name query should be initiated to local files capable of performing a lookup based only on a name. 2) If the minimum required fields contain enough data for state and federal queries, then the system should initiate queries to local, state and federal databases. A: Existing K.1.51 The CAD will return all responses from local, state, and federal databases to the data entry originator. A: ExistingK.1.52 The CAD will bring positive responses (e.g. possible “hits”) that require a review by the originator to the attention of the originator through the use of audible and visual indicators. A: Existing K.1.53 Positive “hits” will appear on all CAD workstations in different color than non-hit returns. A: ExistingK.1.54 The CAD will initiate an automatic query to local, state and federal databases, upon entry of information about a vehicle associated with an event, using the following guidelines at a minimum: 1) License plate number and license plate state or 2) VIN. A: Existing K.1.55 The CAD will default the state to CA for all inquiries. A: Existing Premise Hazards and Previous History
K.1.56 The CAD Premise Hazard and Previous History file will be capable of storing information of interest to responders including, but not limited to:
K.1.56.1 Hazardous materials stored at the location A: ExistingK.1.56.2 Firearms kept at the location A: ExistingK.1.57 AND Information specific to individuals at the location, including, but not limited to:K.1.57.1 Warrants on file A: ExistingK.1.57.2 Serious medical information A: ExistingK.1.57.3 Impairments A: ExistingK.1.57.4 Potential dangers to first responders A: ExistingK.1.58 AND Information specific to the address, including, but not limited to:K.1.58.1 Entry codes A: ExistingK.1.58.2 Knox Box information A: ExistingK.1.59 The CAD will enable all required data for direct input, to be uploaded, or to be loaded via a live interface from RMS(s). A: Existing CAD Event Creation
K.1.60 The CAD will support the creation of new CFS events by either call takers or dispatchers depending on the source of the event information. A: Existing
Determine Response Agency and Service Area
K.1.61 The CAD will assess an event’s location and nature code, then use the system’s geofile to identify the appropriate service agency or agencies that need to handle the event. A: Existing
K.1.62 The CAD will use the service agency and response to notify the appropriate dispatcher(s) that they must process a CAD event. A: Existing CAD Event Routing
K.1.63 The CAD will allow configuration of any CAD workstation for Call Taking and/or Dispatching Functions. A: ExistingK.1.64 The CAD will examine the location, event type and response plans (when dedicated dispatch positions are in operation) to route the CFS event to one or more dispatch positions as the CFS event entry is being performed by a call taker. A: Existing K.2 DISPATCH SUPPORT
Response Plans
K.2.1 The CAD will allow for dynamic and fixed/static response plans. A: Existing K.2.2 The CAD will allow for assignment to be by officer, role, capability and equipment. A: ExistingK.2.3 The CAD will allow for the use of resource groups made up of individual units. A: ExistingK.2.4 The CAD will allow for the use of AVL systems for selecting units. A: ExistingK.2.5 The CAD will support multiple agency response plans. A: ExistingK.2.6 The CAD will allow for unit assignment based on time or distance to the incident. A: ExistingK.2.7 The CAD will allow for adjustable plans that are based on time of day or day of week. A: Existing Unit Rotation
CentralSquare Technologies 3 of 12
#11..
- 674 -
(K) APCO Unified CAD
File
Number All Sections in This Workbook Contain Required Functionality, unless specifically noted as "OPTIONAL" Vendor Response Comments K.2.8 The CAD will allow for customization based on the needs of the agency (e.g. incident address, response type, assignment, resources required, unit-on-task-time, unit utilization, time of day and proximity if you have multiple available units with the capability required). A: Existing K.2.9 The CAD will make unit response recommendations based on the configuration of rules defined by an agency, and unit class. A: Existing Be On the Look-Out / Attempt to Locate
K.2.10 The CAD will support creation and distribution of any BOLO entered into the system. A: ExistingK.2.11 The CAD will provide a BOLO structure to include all necessary information such as the nature of the BOLO, priority, date, range of effectiveness, subject and/or vehicle information, hazard information, and contact information. A: Existing K.2.12 The CAD will allow narrative fields for additional information. A: ExistingK.2.13 The CAD will provide the means for BOLO information to be easily searchable, printable, and have the ability to automatically populate on an incident sheet referencing any particular name, address, or vehicle information. A: Existing K.2.14 The CAD will flag the field (automatically) with configurable visual and audible alerts. A: ExistingK.2.15 The CAD will support a workflow record for initial BOLO creation and any additional edits. A: Existing Dispatch Units
K.2.16 The CAD will have the ability to assign one incident number to each unit responding to the incident. A: ExistingK.2.17 The CAD will capture every time stamp associated with each unit’s response and status change related to the incident. A: ExistingK.2.18 The CAD will capture all status changes and their times for statistical and research purposes (e.g. out of service versus in service to calculate “lost unit hours”). A: Existing
Resource Alerting for Units
K.2.19 The CAD will alert units via MDC and handheld devices and tablets. A: ExistingK.2.20 The CAD will support alphanumeric paging via TAP, WCTP, SMTP, and SNPP. A: ExistingK.2.21 The CAD will support sending SMS messages either directly via cellular modem or using a common carrier’s SMTP interface. A: ExistingK.2.22 The CAD includes the ability to send a copy of an event to all units without assigning them to the event with a single command.
A: Existing
Inform CAD does not supply this functionality with a command, rather all authorized users can view any incident through Inform Mobile.
K.3 RESOURCE / UNIT MANAGEMENT
Rostering
K.3.1 The CAD will provide the capability to create rosters (i.e. assign personnel to a vehicle or position to facilitate on/off duty transactions). A: Existing
K.3.2 The CAD will allow the dispatcher to adjust the rosters and/or assignments (i.e. on-the-fly, during shifts, and above normal complements). A: Existing
K.3.3
The CAD will contain a 2-way, real-time interface to auto populate roster information in CAD.
A: Existing
Inform CAD contains an in‐application rostering system. If the GPD is interested in an interface to a third party rostering system, Central Square can provide a quote once information about that system is available Scheduling
K.3.4 The CAD will provide scheduling capabilities to include pre-assignment of personnel to shifts, districts, and beats. A: ExistingK.3.5 The CAD will allow the dispatcher, with proper permissions, to make adjustments to scheduling on-the-fly and/or during shifts. A: ExistingK.3.6 The CAD allows dispatchers to retrieve historic rosters within a user-defined date/time range. A: Existing Mileage Tracking
K.3.7 The CAD will capture beginning and ending mileage for individual transports. A: ExistingK.3.8 The CAD will provide a method of integration with an AVL system for increased accuracy and efficiency. A: Existing CentralSquare Technologies 4 of 12
#11..
- 675 -
(K) APCO Unified CAD
File
Number All Sections in This Workbook Contain Required Functionality, unless specifically noted as "OPTIONAL" Vendor Response Comments K.3.9
The CAD will use GIS/mapping to supplement driving directions based on shortest route beginning and ending address locations, with regard to environmental factors such as time of day, weather conditions, train schedules, and road/bridge blockages.
A: Existing
Inform CAD provides driving directions based on time of day and GPD geofile and configuration information (e.g. schedules and road blockages). Weather does not impact driving directions. CentralSquare can offer custom interfaces for this ability; however, additional information about sourcing is required.
K.3.10 The CAD will provide the ability for an authorized user to manually override an entry by a dispatcher or supervisor. A: ExistingK.3.11 The CAD will record the overridden information in an audit log. A: ExistingK.4 CALL / INCIDENT / EVENT MANAGEMENT Display of Incident/Event Data
K.4.1 The CAD will display CFS event data on the CAD monitor after being selected by the dispatcher. All CFS event data will be accessible to the dispatcher. A: Existing
K.4.2 The CAD will enable Windows tabs to be used to allow the dispatcher to select supplemental history about the incident (e.g. premises history, past event history, hazards, persons of interest). A: Existing K.4.3 The CAD will display (automatically) updates to the CFS event for the dispatcher. A: ExistingK.4.4 The CAD will provide updated information that is easily discernible from the previously read data (e.g. newest information on the top, different font/color text). A: Existing
K.4.5 The CAD will present an audible and/or visual indication to the dispatcher when a CFS event is updated by another source such as a call taker, another dispatcher, or a field unit. A: Existing K.4.6 The CAD will provide, upon receipt of an update, a method of ease, such as an ‘Update’ button, for the dispatcher to retrieve the CFS event that has been updated. A: Existing
K.4.7 The CAD will remove CFS events as they are closed by the dispatcher from the CFS event display, without additional interaction from the dispatcher. A: Existing
Assign Units
K.4.8 The CAD will allow the assignment of units by using drag-and-drop and point-and-click pull-down menus or command line. A: ExistingK.4.9 The CAD will re-queue the CFS that has had all units removed, but has not been handled. A: ExistingK.4.10 The CAD will recommend a unit that is unavailable only if SOP permits units to be pre-empted for a higher priority event.K.4.11 The CAD will provide the ability to assign one or more units to an incident with a single command. A: ExistingK.4.12 The CAD will provide the ability to dynamically, and without user intervention, change the unit recommendation if relevant incident information changes (i.e. type, location). A: Existing
K.4.13 The CAD will provide the ability to notify users that the unit recommendation has changed. A: ExistingK.4.14 The CAD will provide the ability to cancel a unit from an assignment: If the cancelled unit is the only unit assigned, then the CFS will be returned to the pending event queue. A: Existing
K.4.15 The CAD will provide the ability to hold a CFS event for a specific unit. A: ExistingK.4.16 The CAD will allow the dispatcher to override the system recommended units and assign other units. A: ExistingK.4.17 The CAD will allow the dispatcher to assign any valid field unit to an incident even if that unit is not currently logged on to the system. A: ExistingK.4.18 The CAD will notify the dispatcher and confirm that the correct unit has been assigned if a unit assigned to an incident is not logged on the system. A: Existing
Update Incident Data
K.4.19 The CAD will log the following information for all entries into the CFS event: date, time, user ID (or note if action was system generated), position (terminal) ID, action performed, and any notes associated with action. A: Existing K.4.20 The CAD will allow, at any time, additional incident information to be added to the CFS event prior to incident closure. A: ExistingK.4.21 The CAD will allow the user to display the added comments in reverse chronological order. A: ExistingK.4.22 The CAD will provide the user the option of specifying the CFS event to update by entering the call sign of any assigned unit or by entering the incident number. A: Existing
K.4.23 The CAD will permit multiple users, including MDC-equipped field resources, the ability to simultaneously update information to the CFS event. A: Existing
CentralSquare Technologies 5 of 12
#11..
- 676 -
(K) APCO Unified CAD
File
Number All Sections in This Workbook Contain Required Functionality, unless specifically noted as "OPTIONAL" Vendor Response Comments K.4.24 The CAD will provide the ability for one or more CAD users to simultaneously add incident information to an active CFS event. A: Existing Assign RMS Incident / Case Number
K.4.25 The CAD includes an interface to an RMS to allow the transfer and tracking of incident data. A: ExistingK.4.26 The CAD will provide the ability to transfer the incident data to the RMS at a set time (incident closure) or at dispatcher discretion based upon the field unit’s needs. A: Existing
K.4.27 The CAD will coordinate the assignment of RMS incident/case numbers through a list maintained in the CAD system. A: ExistingK.4.28 The CAD will provide the ability for the dispatcher to retrieve the RMS incident number at any point during the event or after the incident has been closed. A: Existing
Transfer Incident Data To/From the RMS
K.4.29 The CAD will auto-populate necessary CAD data into RMS via appropriate interface. A: ExistingK.4.30 The CAD will automatically query a different RMS system via appropriate interface (in a best-of-breed environment). A: Existing Scheduled Events
K.4.31 The CAD will provide the ability to automatically schedule the CFS event for future dispatch. A: ExistingK.4.32 The CAD will be capable of displaying a list of all scheduled events. A: ExistingK.4.33 The CAD will provide the ability for authorized users to activate a scheduled event at any time. A: ExistingK.4.34 The CAD will send a message to the appropriate users when the scheduled activity occurs. A: ExistingK.4.35 The CAD will support location override for scheduled incidents. A: Existing Secondary Incident Location
K.4.36 The CAD will provide the ability to note responding units have arrived “in staging,” which may be a remote secondary address associated with the primary incident location. A: Existing K.4.37 The CAD will provide the ability to change a unit’s location from the primary address to a secondary address without clearing the unit from the incident or CAD record. A: Existing
K.4.38 The CAD will log a date/time stamped record of the change in the CFS event. A: Existing Single Discipline Incident to a Combined Discipline Incident K.4.39 The CAD will provide the ability to add another agency’s resources to a CFS event. A: ExistingK.4.40 The CAD will provide the ability to assign an agency specific incident/event number to the CFS event. A: ExistingK.4.41 The CAD will provide the ability to link added agency records with the initial CFS event. A: ExistingK.4.42 The CAD will provide the ability to share incident information across multiple linked records. A: ExistingK.4.43 The CAD will provide the ability to track the added resources for the duration of the incident. A: Existing Timers
K.4.44 The CAD will have, and allow configuration of, multiple timers based on unit status and CAD incident type, such as time on a particular call, time since last check-in, and time at the hospital or jail. A: Existing K.4.45 Ability to run status command (to view/monitor different dispatch groups). A: ExistingK.4.46 The CAD will have, and allow configuration of, timers for CAD system events, such as a priority 1 call overdue to be dispatched. A: ExistingK.4.47 The CAD will allow for operators to manually place a timer alert on a CFS or a unit. A: ExistingK.4.48 The CAD will minimally include “down to the second” timestamps (e.g. hhhh/mm/ss). A: ExistingK.4.49 The CAD will allow configurable timers (i.e. ‘hh:mm:ss’, ‘mm:ss’, or ‘ss’). A: ExistingK.4.50 The CAD will be equipped with predefined timers that can be configured by the system administrator. A: ExistingK.4.51 The CAD will provide the ability for the system administrator to create customized definable timers. A: ExistingK.4.51.1 The CAD will record timer activity to the CFS event log. A: ExistingK.4.51.2 The CAD will produce both visual and audible alerts to the dispatcher when a timer is triggered. A: ExistingK.5 SUPPLEMENTAL RESOURCE REQUEST AND TRACKING Supplemental Resources
K.5.1 The CAD will be able to store, and easily retrieve, a file for standardized and ad hoc supplemental resources that may be recalled and requested as needed for services not available from the public safety agencies. A: Existing CentralSquare Technologies 6 of 12
#11..
- 677 -
(K) APCO Unified CAD
File
Number All Sections in This Workbook Contain Required Functionality, unless specifically noted as "OPTIONAL" Vendor Response Comments K.5.2 The CAD will make request and “dispatch” of said resources on the basis of the unique type of service needed, the geographic proximity to the site of the needed service, or a rotation of the unique service providers of a given type—or, a combination of methods. A: Existing K.5.3 The CAD will be able to create a unique or supplemental unit designation in real time. A: ExistingK.5.4 The CAD will be able to record the activities of unique or supplemental units in the same manner in which agency response units are tracked and their activities recorded. A: Existing
K.5.5 The CAD will allow for agency-configurable non-agency units to be recommended, such as the closest towing company recommendation when a unit is dispatched to an accident event type. The recommendation will take into account the rotation of towing companies. A: Existing K.5.6 The CAD will store, and provide for easy retrieval, a list of authorized providers of unique or supplemental supplies or services A: ExistingK.5.7 The CAD will provide multiple sources of contact for each authorized vendor. A: ExistingK.5.8 The CAD will be able to display the list of authorized service providers based upon geographical proximity to the site of need, by rotation, or by agency preference based upon contractual agreement. A: Existing K.5.9 The CAD will record the transactions that occur with supplemental or unique resources. A: ExistingK.5.10 The CAD will provide the ability to create a record of the supplemental service request. A: ExistingK.5.11 The CAD will accommodate selection from the provided list either at random, by geographic proximity to the site of need, or by rotation.
A: Existing
Inform CAD does not provide the ability for random selections. Providers can be set through a rotation, or through configuration, can be created as an agency for closest proximity. Central Square Business Analysts will work closely with the GPD to determine the appropriate and most efficient configurations to meet the desired workflows.
K.5.12 The CAD will trigger the next provider in the rotation, when selected by rotation and upon creation of the record A: ExistingK.5.13 The CAD will process the rotation regardless of the requested resource’s ability to respond. A: ExistingK.6 GEOFILE MAINTENANCEK.6.1 The CAD will validate all locations entered into or processed by the CAD system against the CAD system’s geofile. A: ExistingK.6.2 The CAD will provide an interactive, GUI-based address matching tool for assisting users to determine the location of incidents that do not have an exact geofile match for their initially-entered location. A: Existing K.6.3
The CAD will be capable of determining X/Y/Z coordinate values that represent the location of incidents whose locations have been validated.
A: Existing
Inform CAD captures X/Y coordinates. At this time, since no data standard for Z coordinates have been supplied by Next Generation 911, the z coordinate is not part of the location representation. Inform CAD is ready to accept this information as it becomes available.
K.6.4 The CAD will be capable of displaying coordinates anywhere on the map with mouse over. A: ExistingK.6.5 The CAD will support coordinate-based operations including X/Y/Z, Lat/Lon, and USNG. A: ExistingK.6.6 The CAD will make possible integration of the CAD system’s geofile with Global Positioning Satellite (GPS), AVL, and Automatic Person Location (APL) systems. A: Existing
K.6.7
The CAD will support X/Y/Z coordinate-based geographic searches for such things as nearby hazardous materials, duplicate incidents, and premises information at or near an incident’s location.
A: Existing
Inform CAD captures X/Y coordinates. At this time, since no data standard for z coordinates have been supplied by Next Generation 911, the z coordinate is not part of the location representation. Inform CAD is ready to accept this information as it becomes available.
K.6.8 The CAD will be capable of importing geographic boundary information (e.g. station boundaries, jurisdictional boundaries, reporting districts, response zones, neighborhoods, precincts) from GIS and other geographic data sources. A: Existing K.6.9 The CAD will be capable of importing topologically-structured street networks and other linear features (e.g. rivers, streams, utility right of ways, bus routes) from GIS and other geographic data sources. A: Existing CentralSquare Technologies 7 of 12
#11..
- 678 -
(K) APCO Unified CAD
File
Number All Sections in This Workbook Contain Required Functionality, unless specifically noted as "OPTIONAL" Vendor Response Comments K.6.10 The CAD will be capable of importing point data (e.g. landmarks, parcel address points, business locations, retail store address points, etc.) from GIS and other geographic data sources. A: Existing K.6.11 The CAD will be capable of importing other types of geographic data (e.g. park boundaries, rectified aerial photography, trailer parks, apartment complexes) from GIS and other geographic data sources. A: Existing K.6.12
The CAD will support parcel-level GIS information and use this information for address/location validation. A: Existing Point in parcel utilizing address points can be used for address verification.
K.6.13 The CAD will support multiple layers of information; for example, the storage of building footprints, aerial photographs and other images (i.e. pictures of specific buildings) that are associated with specific areas and addresses. A: Existing K.6.14 The CAD will maintain the CAD system’s geofile while the system is live and operational. A: ExistingK.6.15 The CAD meets i3 standards and functions in order to comply with NG9-1-1 requirements. A: ExistingK.7 SECURITYK.7.1 The CAD will employ data security measures that are compliant with applicable state and federal security standards. A: ExistingK.7.2 The CAD will employ data encryption that meets CJIS security policy standards for any exchange or transmittal of data. A: ExistingK.7.3 The CAD will provide appropriate safeguards to ensure that only authorized devices and users are allowed access to the CAD system and stored information. A: Existing
K.7.4 The CAD will provide a security profile to control individual user access to the various modules, applications, functions, features, and data available within the CAD system. A: Existing
K.7.5 The vendor's company and solution meets all FBI CJIS Security Policy requirements. A: ExistingK.7.6 The CAD will validate each user’s credentials through a mandatory logon process before being granted access to any functions or data available within the CAD system. A: Existing
K.7.7 The CAD will enable a user replacing an existing user to quickly log off the existing user and logon without the need to exit from CAD or re-start the CAD application (i.e. when two-factor authentication does not apply.) A: Existing K.7.8 The CAD will enable system administrators to create and maintain a centralized and indexed database containing information about each system user, including their unique user ID, password, contact information, and security profile. A: Existing K.7.9 The CAD will enable system administrators to define individual user access privileges and assign them to security groups. A: ExistingK.7.10 The CAD will provide a method for authorized users to reset a user’s password. A: ExistingK.7.11 The CAD will associate the user ID and workstation ID with all CAD system transactions, including data entry and report generation. A: ExistingK.7.12 The CAD will limit access to the centralized user security database to only specifically authorized users. A: ExistingK.7.13 The CAD will establish security profiles that are assigned to individual users or user groups based on personnel classifications (e.g. call taker, dispatcher, system administrator, supervisor). A: Existing K.7.14 The CAD will prohibit deletion of any data entered into a CFS event. A: ExistingK.7.15 The CAD will provide application and module level security that enables certain users to access specific CAD system functions and application modules, while keeping other users from accessing these same functions and modules. A: Existing K.7.16 The CAD will provide data entry form security that enables certain users to access specific data entry forms, while keeping other users from accessing these same data entry forms. A: Existing K.7.17 The CAD will provide record type security that enables certain users to access specific CAD system record types, while keeping other users from accessing these same record types. A: Existing K.7.18 The CAD will provide transaction level security that enables certain users to access specific transaction types. A: ExistingK.7.19 The CAD will provide data field level security that enables certain users to access specific CAD data fields, while keeping other users from accessing these same data fields. A: Existing
K.7.20 The CAD will facilitate the use of unique user IDs and passwords to control CAD system access and privileges. A: ExistingK.7.21 The CAD will provide a “single entry” to enable logons to multiple authorized systems that are available through the system (e.g.
CAD, RMS, External and Internal Interfaces). A: Existing K.7.22 The ability to use Active Directory for using multiple domains. A: ExistingK.7.23 The CAD will limit access to system functions and data by physical device (e.g. PCs, terminals), as well as by user ID.
A: Existing
System functions are limited by user authorization not device, with the exception of specific device information needed for CJIS security and mnemonics.
CentralSquare Technologies 8 of 12
#11..
- 679 -
(K) APCO Unified CAD
File
Number All Sections in This Workbook Contain Required Functionality, unless specifically noted as "OPTIONAL" Vendor Response Comments K.7.24 The CAD will provide the ability to “lock out” a user after a system administrator defined number of failed attempted logons. A: ExistingK.7.25 The CAD will provide the capability for individual user name change (e.g. getting married) and keep a link to historical data. A: Existing Logging
K.7.26 The CAD will include a transaction audit database that contains all system transactions and that includes the logon identification (i.e. user ID and workstation ID), date and time stamp, transaction type, contents before ID, and contents after the transaction completes. A: Existing K.7.27 The CAD will enable authorized system users to search the transaction audit database by date and time ranges, by application module, transaction type, specific tables and data fields within tables, specific data entry forms, individual users, user groups, workstation ID, and by various combinations of these factors. A: Existing K.7.28 The CAD will enable authorized system users to create formatted reports and/or export the results of transaction audit database queries and searches. A: Existing
K.7.29 The CAD will prohibit any changes to the contents of the CAD transaction audit database. A: ExistingK.7.30 The CAD transaction audit database will capture and store ALL system transactions. A: Existing Configuration
K.7.31 The CAD will enable authorized system administrators to configure the CAD system to meet the requirements of the department by creating and modifying CAD configuration parameters. A: Existing K.7.32 The CAD will enable authorized system administrators to modify CAD configuration parameters without the requirement for programmer or other support from the manufacturer of the CAD system. A: Existing K.7.33 The CAD Configuration will include functionality for table driven and directly modifiable functionality by authorized system administrators. A: Existing
K.7.34 The CAD Configuration will include functionality for interactive, menu-driven, GUI-based tool that allows authorized administrators to easily update and modify parameters. A: Existing
K.7.35 The CAD Configuration will allow system administrators to specify or modify the following: A: ExistingK.7.35.1 Incident Types A: ExistingK.7.35.2 Incident Priorities A: ExistingK.7.35.3 Reporting District(s) A: ExistingK.7.35.4 Beat(s) A: ExistingK.7.35.5 Agencies A: ExistingK.7.35.6 Type of Resources (color-coded text) A: ExistingK.7.35.7 Dispatch Policies A: ExistingK.7.35.8 Alerts/ Timers A: ExistingK.7.35.9 Type of Dispositions A: ExistingK.7.35.10 Case Number Formatting A: ExistingK.7.35.11 Windows / Menus layout, color, font, attributes A: ExistingK.7.35.12 Map Display Zoom Levels A: ExistingK.7.35.13 Display and functional characteristics of CAD system queues (i.e. pending, active, etc.) A: ExistingK.7.35.14 Display and functional characteristics of CAD system interfaces systems and gateways. A: Existing Table Maintenance
K.7.36 The CAD Table Maintenance will include CAD tables that are maintained using entry windows. A: ExistingK.7.37 The CAD Table Maintenance will include CAD table maintenance entry windows that have context-sensitive, field-level help. F: Not AvailableK.7.38 The CAD Table Maintenance will enable changes made to CAD tables to become immediately effective and shall not affect overall CAD system availability nor require any CAD system down time. A: Existing K.7.39 The CAD Table Maintenance will allow agencies to define additional data elements based on their operational requirements. A: ExistingK.7.40 The CAD Table Maintenance will provide the ability for tables to be defined to support the maintenance of the following CAD objects: A: ExistingK.7.40.1 Incident Types A: Existing CentralSquare Technologies 9 of 12
#11..
- 680 -
(K) APCO Unified CAD
File
Number All Sections in This Workbook Contain Required Functionality, unless specifically noted as "OPTIONAL" Vendor Response Comments K.7.40.2 Agencies A: ExistingK.7.40.3 Disposition Codes A: ExistingK.7.40.4 Commands A: ExistingK.7.40.5 Hazards A: ExistingK.7.40.6 Units A: ExistingK.7.40.7 Unit statuses A: ExistingK.7.40.8 Unit types A: ExistingK.7.40.9 Vehicles A: ExistingK.7.40.10 Service Types (i.e. police, animal control, etc) A: ExistingK.7.40.11 Response Plans A: ExistingK.7.40.12 Personnel A: ExistingK.7.40.13 Rosters A: ExistingK.7.40.14 Messages (e.g. canned, scheduled) A: ExistingK.7.40.15 Alerts/ Timers A: ExistingK.7.40.16 Notifications A: ExistingK.7.40.17 Equipment A: Existing CAD Catch-Up
K.7.41 The CAD will allow a CAD Catch-Up function due to interruption of CAD services. A: ExistingK.7.42 The CAD will have the ability to manually open and create a CFS event sheet. A: ExistingK.7.43 The CAD will have the ability to log the entering individual's information and time of entry. A: ExistingK.7.44 The CAD will provide the ability for all information to be entered without any restrictions, and times/dates changed to reflect the actual time that notice of the CFS event was received. A: Existing K.7.45 The CAD will denote the manually-entered CFS event so there is a record that the CFS event was not entered when it was actually received. A: Existing
K.7.46 The CAD will provide ability to manually designate the “starting” incident number (i.e. the last incident +1 for the starting number once the system is restarted). A: Existing
K.7.47 The CAD will allow for simultaneous automatic and manual entry without degradation. A: ExistingK.7.48 The CAD will include all the information in back entered records that a live incident/event sheet should require. A: ExistingK.8 SYSTEM FUNCTIONS Notifications
K.8.1 The CAD will enable the system administrator to define the rules for automatic CFS event notifications. A: ExistingK.8.2 The CAD will provide the ability to create messages that are retained in the system and sent at pre-specified times. A: ExistingK.8.3 The CAD will allow the user to send and store messages to other users, groups, positions, or mobile devices. A: ExistingK.8.4 The CAD will allow a message to be sent to multiple recipients and/or groups. A: ExistingK.8.5 The CAD will log all sent messages. A: ExistingK.8.6 The CAD will provide the ability to create and maintain automatic reminders of scheduled activities (e.g. radio tests). A: Existing Premises Information / Hazards
K.8.7 The CAD will provide the ability to enter a premises location by full address detail, cross street or latitude/longitude, and commonplace name. A: Existing
K.8.8 The CAD will notify the dispatchers if non-safety-related information exists (wherein users may click to read the information), whereas safety/hazard information is automatically displayed and added to the call. A: Existing K.8.9 The CAD will provide the ability to capture, maintain or interface to specific premises information types for operators. (i.e. Hazard Materials, Handicap, Warrants, Unit Safety, Dangerous Animals, Sex Offenders, etc.) A: Existing K.8.10 The CAD will provide the ability to automatically create (i.e. upon closing of an incident) premises history based on pre-determined criteria. A: Existing
CentralSquare Technologies 10 of 12
#11..
- 681 -
(K) APCO Unified CAD
File
Number All Sections in This Workbook Contain Required Functionality, unless specifically noted as "OPTIONAL" Vendor Response Comments K.8.11 The CAD will provide the ability for supervisors to delete premise information for a given address or location based on expiration date and/or time of record, with prompted review prior to deletion. A: Existing K.8.12 The CAD allows dispatch premise information to expire automatically at a pre-defined interval of time, but remain available for supervisory review (without being deleted). A: Existing K.8.13 The CAD will provide the ability to automatically embed premises information into the event history at the time the event is created. A: ExistingK.8.14 The CAD will provide (or interface to) a “cautions” file to contain information pertaining to dangerous individuals possibly residing at that location or near proximity, and exceptional persons at the location, such as an emotionally disturbed person. A: Existing Dispatch Standard Operating Procedures
K.8.15 The CAD will provide the ability to store and easily retrieve SOPs for the PSAP. A: ExistingK.8.16 The CAD will provide a SOP tool to prompt the user to ask for additional information, perform certain tasks, or relay critical information to responding units or other responders. A: Existing K.8.17 The CAD will provide a method where the retrieval of relevant SOPs are accessible from the CFS event information window and associated with the location, incident type, unit, or special skilled personnel responding. A: Existing CAD Workstation to CAD Workstation Messaging
K.8.18 The CAD will provide short messaging from one CAD workstation to another. A: ExistingK.8.19 The CAD will include the ability to create message groups, whether they are dispatch workstations, mobile computers, groups within the PSAP, or other communications devices. A: Existing
K.8.20 The CAD will enable the system administrator to disable this function if desired on an agency basis. A: ExistingK.8.21 The CAD will log all messages. A: ExistingK.8.22 The CAD will provide the ability to create user definable “canned” messages for selection and distribution to other system users. F: Not Available Narrative Field “Shorthand” / Auto Text
K.8.23 The CAD will provide the ability to recognize character patterns and automatically fill in expanded text. A: ExistingK.8.24 The CAD will expand (automatically) the shorthand into a full description and save it into the narrative. A: ExistingK.8.25 The CAD will allow the agency to add agency-specific shorthand terms and their expansions. A: Existing Multi-Agency / Multi-Jurisdictional Capability
K.8.26 The CAD will have the ability to create a CFS event for user-defined multi-agency events and route the CFS event to the appropriate agency dispatch position(s). A: Existing
K.8.27 The CAD will have the ability to create a linked CFS event for each required agency and route the CFS event(s) to the appropriate dispatch positions when an event involves more than one agency. A: Existing K.8.28 The CAD will have the capacity to create a multi-jurisdictional response. A: ExistingK.8.29 The CAD will provide the ability to create and route a CFS event for dispatch even though the event is in another jurisdiction. A: Existing Communications Supervisor Support
K.8.30 The CAD will provide the ability for a CAD supervisor, or another dispatcher with appropriate system permissions, to observe the activity of a given dispatcher including the pending events queue, active events, available units list, and map. A: Existing K.8.31 The CAD will enable a supervisor, or another dispatcher with appropriate system permissions, to co-dispatch the units under the control of another dispatcher. A: Existing
CAD Testing / Training Environment
K.8.32 The CAD will support a CAD testing/training environment that mirrors the functionality of the CAD live environment. A: ExistingK.8.33 The CAD testing/training will be able to be used, operated, started up, shut down, and updated to match the live application without affecting the live environment. A: Existing
K.8.34 The CAD testing/training will include all tables and administrative configurations, and allows for call takers and dispatchers to train on specific services and on pre-configured geographic areas identical to that of the live environment. A: Existing K.8.35 The CAD testing/training will have a separate E9-1-1 test connection or canned script E9-1-1 information and provide realistic training regarding incoming E9-1-1 data. A: Existing
CentralSquare has included optional pricing for this feature.
K.8.36 The CAD testing/training will be able to be used to test modifications and updates to the live CAD application prior to implementing the modifications and updates in the live environment. A: Existing K.9 REPORTING AND MONITORING
CentralSquare Technologies 11 of 12
#11..
- 682 -
(K) APCO Unified CAD
File
Number All Sections in This Workbook Contain Required Functionality, unless specifically noted as "OPTIONAL" Vendor Response Comments Dispatch Supervisor Support
K.9.1 The ability to add additional dispatchers “on-the-fly” for one or more services either globally or for predetermined geographical areas. A: ExistingK.9.2 The ability to create police districts/beats on the fly, which allows dispatchers to move units to defined city zones. Can be moved by command to other workstations/people/dispatchers. A: Existing CAD Management Reporting
K.9.3 The system will include standard reports that simultaneously use date, time, location, and/or incident type search parameters for report definitions. A: Existing
K.9.4 Ability to concatenate file size (i.e., lengthy DUI checkpoint events). F: Not AvailableK.9.5 The system will include the capability of customizing standard reports and for creating user-defined reports. A: ExistingK.9.6 The system will provide access to all reports to the user, subject to permissions, from within the CAD system. A: ExistingK.9.7 The system will include reports in the CAD security/permissions function (i.e. individual reports can be made available/unavailable based on a user’s security profile). A: Existing
K.9.8 The system will provide all reports to users, subject to permissions, regardless of the application used to create user-defined or custom reports (i.e. internal to the CAD system or via a third-party reporting or analysis tool). A: Existing K.9.9 The system will provide an ad hoc reporting capability. A: ExistingK.9.10 End users may retrieve report detail from either the incident number or the DR. A: ExistingK.9.11 The system will provide a data exporting capability. A: Existing Training and Testing
K.9.12 The CAD system’s training environment is clearly identifiable as the training environment (e.g. “TRAINING” prominently displayed on the screen). A: Existing
Snapshot/Incident Relay
K.9.13 The proposed CAD includes functionality to provide a detailed, system-wide snapshot report and/or graphic display of the system status to include all units and events, based on a user-specified date, and time and an incident replay, based on a user-specified dateand time, specific incidents, or other CAD events. A: Existing K.10 ADDITIONAL APCO REQUIREMENTS
National Suspicious Activity Reporting (SAR) Features
K.10.1 The CAD allows users to flag a CFS as “suspicious” with regard to the National SAR Initiative. A: Existing As described in response to C.1.11 K.10.2 Flagged CFS are exported to the appropriate fusion center for SAR reporting. A: Existing As described in response to C.1.11K.10.3 The CAD provides the capability to notify an intelligence unit/counterterrorism unit when a SAR is submitted. A: Existing As described in response to C.1.11 CentralSquare Technologies 12 of 12
#11..
- 683 -
Resumes of Key Personnel
CentralSquare Technologies Copyright © 2018 Confidential and Proprietary Bruce Plannette Senior Project Manager
Summary Skilled project manager with 15 years of experience managing implementation of public safety software systems.
Experience
Senior Project Manager CentralSquare Technologies, Lake Mary, FL 2003 – Present
Primary point of contact during project implementation. Develop project documents including: Statement of Work (SOW),
Implementation Schedule, technical requirements, and project budget. Oversee entire project, generating detailed documentation on project status to management and clients.
Key Projects with
CentralSquare
Orange County Sheriff-Coroner Department, CA – FBR
July 2015 – December 2017 (Pilot)
Positions: 600 concurrent Field Based Reporting positions.
Solution: Deployment of Field Based Reporting for an existing Inform RMS client within phased approach. Current phase agency roll-out.
This project also included three integrations between Jail, Property/Evidence and the OCSD Imaging system.
The San Francisco Bay Area Rapid Transit (BART) Police – Regional Anti-Terror Integrated Law Enforcement System, CA – CAD/Mobile/RMS/PSIM
June 2009 – April 2016
Positions: Ten CAD production seats; Mobile; RMS; PSIM.
Solution: Deployment of CAD, Mobile, integrations to external systems and two subcontractors. This project also included a subcontract for, and integration with, a Physical Security Information Management System (PSIM). Thorough this integration the PSIM will create a CAD incident based upon BART Industrial Control Solution(s) input to the PSIM rules engine.
Singapore Civil Defense Force Advanced C3 Emergency
System, Singapore – CAD/Mobile
September 2009 – November 2014
Positions: 22 CAD production seats; 600 Mobile.
Solution: Deployment of CAD, Mobile, and 13 interfaces to external systems. This project also included more than 20 CAD
customizations.
#11..
- 684 -
Resumes of Key Personnel
Confidential and Proprietary CentralSquare Technologies Copyright © 2018 Orange County Fire Authority, CA – CAD/Mobile
November 2012 – December 2014
Positions: 29 CAD production seats; 350 Mobile.
Solution: Deployment of CAD, Mobile, and seven interfaces to external systems. This project also included: Integration to an Interoperability Information Sharing HUB between four
communications centers and four Ambulance Service Area
Providers; Hardware and third parties under a subcontract relationship.
Director of Performance
Improvement and Business
Systems
Emergency Ambulance Services Inc., Brea, CA
2002 – 2003
• Systems Support and development for CAD, Mobile, and
Accounting Systems
• Responsible for CAAS accreditation process
Systems Analyst American Medical Response
1993 – 2002
• Systems Support for CAD and Mobile Systems
• Reporting Platform and Report development for all
compliance reporting
• Communications Center Quality Improvement
Education California State University Long Beach, Master Degree in Health Care Administration
California State University Long Beach, Bachelor Degree in Political Science
#11..
- 685 -
Resumes of Key Personnel
CentralSquare Technologies Copyright © 2018 Confidential and Proprietary Cindy Belcher Senior Project Manager
Summary Skilled project manager with 22 years of experience managing implementation of public safety software systems.
Experience
Senior Project Manager CentralSquare Technologies, Lake Mary, FL 2013 – Present
Primary point of contact during project implementation from initial contract review to project kick-off and final sign-off. Oversee entire project, generating detailed documentation on project status to management and clients.
Key Projects with
CentralSquare
Hamilton County, OH Emergency Communications Center
2014 – 2016
Inform CAD (multi-jurisdictional), Mobiles, IQ/Analytics, and interfaces.
Milwaukee Police Department, WI
2016 – 2018
Sworn officers: 1,800+ (largest Inform RMS Web client with Inform RMS, Inform Jail 5, interfaces, and data conversion).
Public Safety Consulting
Practice Manager
ClientFirst Consulting Group, LLC
2011 – 2013
Responsible for business development and delivery of consulting services nationwide to law enforcement, fire service, and local City government agencies. Projects included needs assessments, RFP development, vendor selection and comparative analysis, contract negotiations, and IT strategic planning. Managed implementation for both new projects as well as existing, troubled vendor deployments.
Project Manager Intergraph Corporation
2009 – 2011
• Responsible for the oversight, administration, and
implementation of complex public safety technology projects • Scheduled and supervised technical resources, coordinated contractual issues and technical scope with third-party vendors
#11..
- 686 -
Resumes of Key Personnel
Confidential and Proprietary CentralSquare Technologies Copyright © 2018 Senior Technical Instructor Intergraph Corporation
2006 – 2009
Provided business analysis and technical configuration expertise on large, complex public safety software implementations for Tier 1 and 2 accounts
Public Safety and Justice
Senior Account Executive
HTE, Inc./SunGard
1999 – 2003
Consultative sales for new and existing accounts. Territory and client account management to promote regional growth and ensure client satisfaction.
Project Manager/Application
Specialist
HTE, Inc.
1996 – 1999
Provided best practice and change management expertise and instruction to public safety clients across the U.S.
Education Ohio State University, Bachelor Degree in Business Administration University of the Pacific, McGeorge School of Law, First year studies in Contracts, Criminal Law, Torts, Legal Research and Writing
Certifications Project Management Institute (PMI), Project Management Professional (PMP)
#11..
- 687 -
Resumes of Key Personnel
CentralSquare Technologies Copyright © 2018 Confidential and Proprietary Linda Ali Senior Project Manager
Summary Skilled project manager with 22 years of experience managing implementation of public safety software systems.
Experience
Senior Project Manager CentralSquare Technologies, Lake Mary, FL 2009 – Present
Primary point of contact during project implementation. Develop project documents including: Statement of Work (SOW),
Implementation Schedule, technical requirements, and project budget. Oversee entire project, generating detailed documentation on project status to management and clients.
Key Projects with
CentralSquare
City of College Station, TX – CAD/Mobile/RMS/Jail
January 2016 – Present
Positions: 13 CAD production seats with Mobile, RMS, and JMS.
Solution: CAD, Mobile, RMS, and JMS full suite deployment including a CAD-to-CAD with the City of Bryan. This project has several custom interfaces and data conversion.
Dallas/Fort Worth International Airport, TX –
CAD/Mobile/RMS/Jail
May 2014 – December 2015
Positions: Nine CAD production seats with Mobile, RMS, and JMS.
Solution: CAD, Mobile, RMS, and JMS full suite deployment including installation of third-party hardware and deployment of multiple third-party systems. This project has several custom interfaces and full data conversions from multiple sources.
Union County Public Safety, NJ – CAD/Mobile
April 2013 – December 2013
Positions: Eight CAD production seats with Mobile.
Solution: CAD and Mobile deployment with several standard interfaces. This project was a rapid deployment from a previously joint CAD system.
Cy-Fair Volunteer Fire Department, TX – CAD/Mobile
January 2012 – October 2012
Positions: 17 CAD production seats with Mobile.
Solution: CAD and Mobile deployment for the nation’s largest volunteer fire department. This project has several interfaces and data conversions.
#11..
- 688 -
Resumes of Key Personnel
Confidential and Proprietary CentralSquare Technologies Copyright © 2018 City of San Antonio, TX – CAD/Mobile
April 2009 – September 2010
Positions: 50 CAD production seats with Mobile.
Solution: CAD and Mobile deployment with three different law enforcement agencies and two fire departments. This project was managed by a Regional Board with multiple sponsors and
stakeholders. This project deployed many third-party systems, several custom and standard interfaces, and data conversions from multiple sources.
Consultant Vignon Corporation, Dallas, TX
2006 – 2009
• Oversaw the implementation of a $6.5 million public safety computer aided dispatch system for the Fire, Police, and 9-1-1 agencies replacing a 30-year old in-house developed mainframe system for the City of Dallas.
• Successfully directed project team through the
implementation process meeting stakeholders expectations after joining a two-year development in progress.
• Engaged all technology and user teams during the testing and implementation of the system infrastructure and
application components while setting priorities and managing risk.
• Transitioned the team from development to system support with the implementation of a problem management tracking process, creating hardware/software documentation, setting on-call rotation, and setting tasks priorities.
• Participated in a lead role for the development and
implementation of a new mobile application and mobile
hardware to be used in all public safety vehicles, an
$11 million City of Dallas initiative.
• Direct numerous third-party resources and vendors to
maintain 24x7 system availability at each government
satellite office and the official Dallas County Clerk public website.
Education Texas A&M University, Bachelor of Business Administration in Business Analysis
#11..
- 689 -
Resumes of Key Personnel
CentralSquare Technologies Copyright © 2018 Confidential and Proprietary Susan Irwin Senior Project Manager
Summary Skilled project manager with 12 years of experience managing implementation of public safety software systems.
Experience
Senior Project Manager CentralSquare Technologies, Lake Mary, FL 2007 – Present
Primary point of contact during project implementation from initial contract review to project kick-off and final sign-off. Oversee entire project, generating detailed documentation on project status to management and clients.
Key Projects with
CentralSquare
BRETSA (Boulder Regional Emergency Telephone Service
Authority), CO – CAD/Mobile
August 2009 – November 2012
Positions: 47 CAD production/disaster recovery, 312 Mobile.
Solutions: Deployment of Inform CAD/Mobile and installation of system and third-party hardware. Project spanned 34 County municipalities and Fire Protection Districts, the University of Colorado, and County of Boulder.
Lucas County, OH – CAD/Mobile
October 2010 – June 2014
Positions: 117 CAD production seats, 39 disaster recovery, 80 Mobile.
Solutions: Deployment of Inform CAD/Mobile and 17 interfaces for Lucas County, which comprises seven PSAPs/dispatch centers, serving 16 law enforcement agencies and 15 fire agencies. Included installation of system and third-party hardware.
City of Alexandria, VA – CAD/Mobile
January 2013 – January 2015
Positions: 37 CAD production seats with disaster recovery and 365 Mobile
Solution: Deployment of Inform CAD/Mobile with 18 interfaces and installation of system and third-party hardware. Included National Capital Region CAD-CAD Data Exchange Hub interface, in
conjunction with Arlington and Fairfax counties.
#11..
- 690 -
Resumes of Key Personnel
Confidential and Proprietary CentralSquare Technologies Copyright © 2018 Montgomery County, TN – CAD/Mobile/RMS/FBR/Jail
December 2016 – August 2017
Positions: 16 CAD, 255 Mobile, 25 RMS, 15 Jail.
Solutions: Deployment and installation of Inform full-suite product line for Montgomery County E9-1-1 and Montgomery County Sheriff, which was accomplished in eight months from project kickoff to Go Live, with no adjustments to project timeline.
Director of Project
Management
InterAct Public Safety Systems
2006 – 2007
Responsible for process re-engineering of department; performance management, coaching/mentoring, resource management, portfolio management, risk analysis, and ISO auditing. Acted as Corporate Liaison to Finance, Purchasing, Development, Staging, Training, Technical, Tech Support, and Customer Care.
Project Manager InterAct Public Safety Systems
2006 – 2007
Responsible for overall project management.
#11..
- 691 -
Resumes of Key Personnel
CentralSquare Technologies Copyright © 2018 Confidential and Proprietary Vidas K. Germanas Project Manager
Summary Skilled project manager with 22 years of experience managing implementation of public safety software systems on both the agency and vendor side.
Experience
Project Manager CentralSquare Technologies, Lake Mary, FL 2010 – Present
Oversee entire project including SOW, schedule, budget, technical requirements, and associated documentation. Chair regular status meetings between CentralSquare team members and the clients’ governing officials to ensure success.
Key Projects with
CentralSquare
Washington County Consolidated Communications Agency
(WCCCA) – CAD/Mobile/CAD-to-CAD
December 2015 – March 2018
Solution: Deployment of CAD, Mobile, and 16 interfaces to external systems, as well as a regional CAD-to-CAD.
City of Long Beach, CA – CAD/Mobile/RMS/Jail/Fire RMS
September 2012 – March 2014
Solution: Deployment of CAD, Mobile, and 13 interfaces to external systems, as well as RMS, Jail, and an upgrade of their existing Fire RMS. This project also included two CAD customizations.
Prince George’s County Police Department, MD – CAD/Mobile December 2009 – January 2012
Positions: 82 CAD
Solution: Deployment of CAD and Mobile.
Arlington County Police and Fire, VA – CAD/Mobile
December 2009 – January 2012
Solution: Deployment of CAD, Mobile and Regional CAD-to-CAD. 9-1-1/CAD/MSAG
Administrator
DuPage County Emergency Telephone System Board (ETSB),
Wheaton, IL
1995 – 2010
• Systems Implementation, Administration, and final level Management Support of Public Safety Software Data
Systems for 9-1-1 Call Taking and 9-1-1 Call Management Systems, Computer Aided Dispatch, Mobile Data Systems,
GPS Automated Vehicle Locating Systems (AVL), and
coordinate-based Geographic Information System
databases.
#11..
- 692 -
Resumes of Key Personnel
Confidential and Proprietary CentralSquare Technologies Copyright © 2018 • Manager of technical issue resolution efforts involving users and Fortune 100 corporate vendor partners.
• Administration and Management of the DuPage County
9-1-1 Master Street Address Guide (MSAG).
• Wireless Phase 2 and Wireline 9-1-1 Call Handling, Routing and Overflow Administration for the 15 9-1-1 centers within the DuPage County ETSB’s jurisdiction.
• Administration of the DuPage County Emergency
Telephone System Board’s 33 node IP over SONET highspeed, high-availability, wide-area data network including protocol management, preliminary network routing design, and edge network interfaces to Federal, State, and Local Law Enforcement networks.
Education Litauisches Gymnasium, Huttenfeld, Germany, Coursework (1981 – 1982)
University of Illinois Chicago, Coursework (1982 – 1984) North East Illinois Multi-Regional Training Institute (1984 – 1986)
Certifications Illinois State Police LEADS Certification (1985 – 2011) Esri ArcGIS Desktop (2005)
#11..
- 693 -
Resumes of Key Personnel
CentralSquare Technologies Copyright © 2018 Confidential and Proprietary April Johnson Project Manager
Summary Skilled project manager with 13 years of experience managing implementation of public safety software systems on both the agency and vendor side.
Experience
Project Manager CentralSquare Technologies, Lake Mary, FL 2011 – Present
Primary point of contact during project implementation. Develop project documents including: Statement of Work (SOW),
Implementation Schedule, technical requirements, and project budget. Oversee entire project, generating detailed documentation on project status to management and clients.
Key Projects with
CentralSquare
CRISP (Fort Collins, CO) – CAD, Mobile, RMS, and Jail
San Bernardino Sheriff’s Department, CA – CAD, Mobile, and RMS
Burbank Police Department, CA – CAD, Mobile, RMS, and Jail Project Manager Motorola Solutions, Inc.
2007 – 2012
• Responsible for the oversight, administration, and
implementation of complex public safety technology projects • Schedules and supervises technical resources; oversees and coordinates contractual issues and technical scope with third-party vendors.
Application
Engineer/Business Analyst
Motorola Solutions, Inc.
2005 – 2007
• Develop training plans to meet customer needs and
expectations
• Conduct technical training sessions with the customer end user
• Troubleshoot software issues
• Document and report software defects and work with the engineering department to resolve
• Review technical documentation and provide updates as needed
Education Regis University, Bachelor Degree in Business Technology Management
Regis University, Masters of Science degree in Organizational Leadership
#11..
- 694 -
Resumes of Key Personnel
Confidential and Proprietary CentralSquare Technologies Copyright © 2018 Certifications Project Management Institute (PMI), Project Management Professional (PMP)
Masters Certificate in Information Technology Project Management #11..
- 695 -
Resumes of Key Personnel
CentralSquare Technologies Copyright © 2018 Confidential and Proprietary Ann Marie Newton Project Manager
Summary Skilled project manager with 21 years of experience managing implementation of public safety software systems.
Experience
Project Manager CentralSquare Technologies, Lake Mary, FL 2015 – Present
Primary point of contact during project implementation. Develop project documents including: Statement of Work (SOW),
Implementation Schedule, technical requirements, and project budget. Oversee entire project, generating detailed documentation on project status to management and clients.
Key Projects with
CentralSquare
LOGIS, MN – Classic RMS and RMS Web
June 2015 – Present
Positions: 300 RMS production seats
Solution: RMS/RMS Web for 23 law agencies, approximately 1,250 officers using RMS Web. The first agency was brought live in January 2016. There were several interfaces associated with this project.
Anoka County, MN – Classic RMS and RMS Web
June 2015 – Present
Positions: 200 RMS Production seats
Solution: RMS/RMS Web for 11 law agencies, approximately 1,200 officers using RMS Web. The system went live in November 2015.
There were several interfaces associated with this project.
Berkeley County, SC – CAD/Mobile/RMS/JMS
September 2017 – Present
Positions: Nine CAD Production seats, 180 Mobile users, RMS, and JMS with disaster recovery.
Solution: Full suite deployment with a one-phased approach for all products. There are several interfaces associated with this project.
Project Manager, Short
Cycle Enhancements
Tiburon
2013 – 2015
Managed multiple short cycle enhancements, including Version Management Program; provided weekly financial reporting plan for Operations Director, including projection of hours to complete, identification of required internal resources, and projection of final billings.
#11..
- 696 -
Resumes of Key Personnel
Confidential and Proprietary CentralSquare Technologies Copyright © 2018 Project Manager Intrado
2008 – 2013
Managed and participated in highly complex projects to accomplish identified, strategic initiatives which may include short- and long-term strategies and relationship management; documented and reviewed project plan for Executive Management review, including timeline, cost analysis, identification of required internal resources, risk analysis, identification of individual projects, and process/procedure recommendations.
Education The University of North Carolina at Wilmington, Bachelor Degree in Business Systems
#11..
- 697 -
Resumes of Key Personnel
CentralSquare Technologies Copyright © 2018 Confidential and Proprietary Julie Walde Project Manager
Summary Skilled project manager with 25 years of experience managing implementation of public safety software systems on both the agency and vendor side.
Experience
Project Manager CentralSquare Technologies, Lake Mary, FL 2011 – Present
Primary point of contact during project implementation. Develop project documents including: Statement of Work (SOW),
Implementation Schedule, technical requirements, and project budget. Oversee entire project, generating detailed documentation on project status to management and clients.
Key Projects with
CentralSquare
Westcom 911, IA – CAD/Mobile/RMS/IQ
January 2016 – Present
Positions: Nine CAD production seats with disaster recovery and Mobile.
Positions: 80 RMS production seats; multi agency environment.
Solution: CAD, Mobile, RMS suite deployment with staggered Go Live dates. CAD and Mobile went live January 4, 2017 with RMS following on January 24, 2017. There are several interfaces with this project including additions, scope changes and removal. Pending IA DPS Certification for closure.
Prescott, AZ – CAD/Mobile/RMS/IQ
February 2017 – Present
Positions: Ten CAD production seats with disaster recovery and Mobile.
Position: 70 RMS production seats; multi-agency environment.
Solution: CAD, Mobile, RMS suite deployment with staggered Go Live dates. CAD and Mobile went live February 13, 2018 with RMS following on August 1, 2018. There are several interfaces with this project including additions, scope changes, and removal.
Parker, CO – RMS/IQ
October 2017 – Present
Current CAD User – Add on RMS/IQ
Position: 65 RMS production seats.
Solution: RMS, IQ deployment with staggered Go Live dates. RMS Go Live on September 18, 2018. There are several interfaces with this project including additions, scope changes, and removal. #11..
- 698 -
Resumes of Key Personnel
Confidential and Proprietary CentralSquare Technologies Copyright © 2018 IT Manager City of Greeley, CO
2001 – 2010
• Supported Weld County Public Safety System including
CAD, Mobile, Message Switch, CAD Reporting, Police
Records, Jail Reports, Mobile Reporting, Civil, and
interfaces
• System supported 17 law agencies, 23 fire agencies, and one ambulance service
• Project management of long and short-term projects,
including replacement of the public safety system
Systems Manager City of Fort Collins, CO
1997 – 2001
• Supported public safety system for City of Fort Collins, Colorado State University, Poudre Fire Authority, and Platte Valley Ambulance Service
• Project management of long and short-term projects,
including the replacement of the public safety system
Systems Administrator II City of Greely, CO
1993 – 1997
• Supported Weld County Public Safety System including:
CAD, Mobile, Message Switch, CAD Reporting, Police
Records, Mobile Reporting, Jail Records, Civil, District Attorney records, and interfaces
• System supported 17 law agencies, 23 fire agencies, and one ambulance service
Education University of Northern Colorado, Bachelor Degree in Business #11..
- 699 -
Resumes of Key Personnel
CentralSquare Technologies Copyright © 2018 Confidential and Proprietary Timothy Collins Project Manager
Summary Skilled project manager experienced with integrated CAD, Mobile, RMS, and JMS implementations. Mr. Collins has 32 years of progressive public safety experience as a State Trooper, Software Product Manager, and IT Project Manager.
Experience
Project Manager CentralSquare Technologies, Lake Mary, FL 2016 – Present
Primary point of contact during project implementation. Develop project documents including: Statement of Work (SOW),
Implementation Schedule, technical requirements, and project budget.
Oversee entire project, generating detailed documentation on project status to management and clients. These responsibilities include:
• Contract review and preparation of project kick-off materials (scheduling, budget, P&L analysis, critical path analysis, team member task assignment, etc.).
• Tracking and reporting on task progress of internal and subcontractor resources per the project Statement of Work and Implementation Schedule.
• Chairing regular status meetings between CentralSquare team members and the clients’ governing officials.
Key Projects with
CentralSquare
Sumner County 911, TN – CAD/Mobile
January 2016 – July 2017
Position: Consolidation of seven PSAPs; 21 CAD positions.
Solution: This project was a fast implementation. Client was required to Go Live in July 2017. Project included management of third-party vendors.
Raleigh – Wake County, NC – CAD/Mobile
August 2017 – Present
Position: 53 CAD production seats with 1,400 Mobile.
Solution: Project deployment for three separate PSAPs onto centralized servers. Project includes Disaster Recovery and numerous interfaces. Go Live scheduled for March 2019.
Sonoma County Public Safety Consortium, CA – RMS
April 2018 – Present
Ongoing project deploying Law RMS to a consortium of nine agencies. Project includes eight custom interfaces and disaster recovery. Expected Go Live of February 2019.
#11..
- 700 -
Resumes of Key Personnel
Confidential and Proprietary CentralSquare Technologies Copyright © 2018 Project Manager/Business
Analyst
Harris Computer Systems (Caliber Public Safety R&D Division) 2008 – 2012
• Responsible for owning and managing Caliber’s flagship enterprise Records Management System, Online RMS
(Oracle cloud and premise-based). Set roadmap priorities. • Managed efforts between engineering, quality assurance, sales, operations support, and implementation; deployment for multiple software releases each year.
Managing Director Purdue University (Visual Analytics for Command, Control and Interoperability Environments)
2008 – 2012
• Oversaw all operating aspects of this Homeland Security Command, Control, and Interoperability Big Data Center of Excellence involving more than 70 scientists and researchers in the United States, Canada, Germany, and the United
Kingdom.
• Conceptualized and co-led development of innovative
software technologies to aid public safety and intelligence agencies meet their tactical, operational, and strategic missions. Technologies included U.S. Coast Guard Search and Rescue software decreased lives lost on the Great
Lakes by 36% in 2011. Received U.S. Coast Guard
Commanders Award for Excellence.
• Facilitated all industry and government business relations to include negotiating numerous Statements of Work,
Memorandums of Understanding, and Non-Disclosure
Agreements with public safety agencies.
Education Purdue University, Master of Business Administration Degree FBI National Academy, Professional Education
#11..
- 701 -
Resumes of Key Personnel
CentralSquare Technologies Copyright © 2018 Confidential and Proprietary Jameson Gartner Project Manager
Summary Accomplished project manager experienced with integrated 911/CAD/Mobile/RMS implementations. Jameson has more than 17 years of progressive public safety supervisory and project management experience. He has worked as a project manager, traffic operations supervisor and SWAT element leader.
Experience
Project Manager CentralSquare Technologies, Lake Mary, FL 2016 – Present
Primary point of contact during project implementation. Develop project documents including: Statement of Work (SOW),
Implementation Schedule, technical requirements, and project budget.
Oversee entire project, generating detailed documentation on project status to management and clients. These responsibilities include:
• Contract review and preparation of project kick-off materials (scheduling, budget, P&L analysis, critical path analysis, team member task assignment, etc.).
• Tracking and reporting on task progress of internal and subcontractor resources per the project Statement of Work and Implementation Schedule.
• Chairing regular status meetings between CentralSquare team members and the clients’ governing officials.
Key Projects with
CentralSquare
City of Cincinnati, OH – CAD/Mobile
May 2016 – February 2017
Positions: 36 CAD production seats with disaster recovery and Mobile.
Solution: Deployment of Inform CAD/Mobile which also included the installation of all third-party hardware, re-configuration of the previously built joint CAD system, and the configuration of Mobile.
System went live January 24, 2017 without any adjustments to the schedule.
Arapahoe County, CO – CAD/Mobile/RMS/JMS
October 2016 – Present
Positions: 24 CAD production seats with disaster recovery and Mobile.
#11..
- 702 -
Resumes of Key Personnel
Confidential and Proprietary CentralSquare Technologies Copyright © 2018 Solution: CAD, Mobile, RMS, and JMS full suite deployment with a two-phased approach for CAD/Mobile. CAD/Mobile was brought live in November 2017, on schedule. This project also includes the consolidation of four municipalities CAD/Mobile which went live in May 2018. There are several interfaces associated with this project including several additions, scope changes, and removals.
Arapahoe County Consolidation—CAD/Mobile
September 2017 – Present
Positions: 23 CAD production seats with Mobile.
Solution: CAD/Mobile deployment will bring four separate law PSAPs on to the Arapahoe County centralized CAD/Mobile solution. This project includes the deployment of a VDI solution to mitigate the need to have CAD/Mobile servers at each client site. This project went Live in May 2018.
Warren County Sheriff, OH – CAD/Mobile/RMS/JMS
May 2016 – Present
Positions: 24 CAD production seats with Mobile, RMS, and JMS.
Solution: CAD, Mobile, RMS, and JMS full suite deployment with ten different law enforcement agencies and 15 fire departments. This project is managed by an IT staff centralized data warehouse with multiple sponsors and stakeholders. This project has several custom interfaces and data conversions from multiple sources.
Loveland Police Department, Loveland, CO
2001 – 2016
• Responsible for oversight and management of daily team activities
• Annual budget planning and management
• Critical incident management
Project manager for multiple department technology projects including: TeleStaff, ARAS 360, Regional Unmanned Air Systems, County Consortium, and Brazos Citations Technology.
Education Columbia Southern University, Bachelor of Science, Administration of Justice
Colorado POST Certification-Academy, Weld County, CO
#11..
- 703 -
Resumes of Key Personnel
CentralSquare Technologies Copyright © 2018 Confidential and Proprietary Eric Johnson Project Manager
Summary Skilled project manager with ten years of experience managing implementation of public safety software systems on both the agency and vendor side.
Experience
Project Manager CentralSquare Technologies , Lake Mary, FL 2011 – Present
Primary point of contact during project implementation. Develop project documents including: Statement of Work (SOW),
Implementation Schedule, technical requirements, and project budget. Oversee entire project, generating detailed documentation on project status to management and clients.
Key Projects with
CentralSquare
Dekalb County Police Department (GA) – CAD/Mobile
Sept 2016 – April 2018
Positions: 100 CAD seats; 750 Mobile.
Solution: Deployment of CAD, Mobile, integrations to external systems and integration with Inform RMS; 12 interfaces.
Washington County Sheriff Department (MN) – CAD/Mobile/ RMS/Jail
July 2015 – December 2017 (Pilot)
Positions: 11 CAD, 300 Mobile, 100 RMS, 30 Jail.
Solution: Deployment of CAD/Mobile/RMS/Jail systems. Due to client needs, systems went live at the same time. This project also included integrations between CAD/RMS/ Property/Evidence/Jail and additional interfaces.
Williamson County, TN
Williamson County Sheriff Department (TN) – CAD/Mobile/E911 July 2016 – December 2016
Positions: 23 CAD, 100 Mobile.
Solution: CAD/Mobile/E911 systems in a new building under a tight deadline.
RMS Project Manager Motorola Solutions
2010 – 2016
• Held bottom-line accountability for multiple departments and provided leadership of complex and diverse software
engineering projects. Managed engineering project
lifecycles and multi-million-dollar projects in addition to national product support.
#11..
- 704 -
Resumes of Key Personnel
Confidential and Proprietary CentralSquare Technologies Copyright © 2018 • Effectively grew client relationships through strategic engineering interactions and deliveries.
• Received multiple Motorola Quality Awards in recognition of outstanding leadership.
• Provided leadership for three diverse departments.
Senior Software Engineer
Team Lead
Motorola Solutions
2008 – 2010
Reviewed operations to ensure compliance with service level agreements (SLAs) and organizational benchmarks. Conducted technical and operational training for managers. Assessed current policies/procedures and implemented new standards to enhance efficiency.
Additional Positions Senior Software Engineer (two years) Senior Project Software Consultant/QA (two years)
Project Manager/IT Manager (one year)
Software Developer (three years)
Technical Support (two years)
Data Analyst (two years)
Network Communications Administrator (nine years)
Education University of Phoenix, Master of Science, Information Systems/IT Management
University of Phoenix, Bachelor of Science, IT/Software Engineering
#11..
- 705 -
Resumes of Key Personnel
CentralSquare Technologies Copyright © 2018 Confidential and Proprietary Cheryl McIntyre Project Manager
Summary Skilled project manager experienced with integrated CAD/ Mobile/RMS implementations. Ms. McIntyre has more than seven years project management experience as well as experience managing implementation of public safety software systems on both the agency and vendor side.
Experience
Project Manager CentralSquare Technologies , Lake Mary, FL 2011 – Present
Primary point of contact during project implementation. Develop project documents including: Statement of Work (SOW),
Implementation Schedule, technical requirements, and project budget. Oversee entire project, generating detailed documentation on project status to management and clients.
Key Projects with
CentralSquare
City of Campbell, CA – CAD/Mobile/RMS
October 2017 – June 2018
Positions: Six CAD production seats with Mobile, 10 RMS seats.
Solution: CAD, Mobile, RMS deployment. This project has several interfaces, data conversions, and was a Rapid Implementation Deployment. They went live on April 24, 2018 with no adjustments to the schedule.
CA State University of Long Beach, CA – CAD/Mobile/911
upgrade
January 2018 – Present
Positions: Four CAD production seats with Mobile.
Solution: CAD and Mobile deployment with several standard interfaces. This project is a Rapid Implementation Deployment and is a Los Angeles site for Direct Integration between TTMS and CAD.
Cleveland Bradley, TN – CAD/Mobile
January 2018 – Present
Positions: Eight CAD production seats with disaster recovery and Mobile.
Solution: Deployment of Inform CAD/Mobile which also included multiple interfaces and a five years data conversion. This project Is a Rapid Implementation Deployment.
Project Manager Component Control
2012 – 2016
• Initiates, plans, executes, controls, and closes projects for aviation software implementations
#11..
- 706 -
Resumes of Key Personnel
Confidential and Proprietary CentralSquare Technologies Copyright © 2018 • Serve as the key point for managing 30-40 accounts at one time
• Proactively manage communication throughout the
implementation by setting regular conference calls,
meetings; and using our software to monitor communication across the board
• Create risk register, monitor risks, and change requests throughout the project. Implement the approved actions and workarounds required to mitigate project risks
• Prepare, monitor, and maintain the project budget
• Ensure a common understanding by setting expectations in accordance with the Project Plan to align the stakeholders and team members
Education Project Management Institute – Certified Project Management Professional
University of Rhode Island, RI – Bachelor of Science Degree:
Cum Laude
Certifications Project Management Institute (PMI), Project Management Professional (PMP)
#11..
- 707 -
Resumes of Key Personnel
CentralSquare Technologies Copyright © 2018 Confidential and Proprietary Susanne Valdez Project Manager
Summary Project Manager with over 25 years of experience in the Public Safety arena and more than a decade of that time implementing systems for public safety agencies.
Experience
Project Manager CentralSquare Technologies , Lake Mary, FL 2011 – Present
Primary point of contact during project implementation. Develop project documents including: Statement of Work (SOW),
Implementation Schedule, technical requirements, and project budget. Oversee entire project, generating detailed documentation on project status to management and clients.
Key Projects with
CentralSquare
Jefferson County E911 Authority-Consolidation – Inform
CAD/Mobile/Field Ops/Advanced Reporting
February 2017 – Present
• Took over project after Jeffcom had a complete change in upper management. Worked with Jeffcom Team to get back
on track and create new project Plan for project
implementation
• This project consolidated eight agencies into Jeffcom with a total of eight separate Go Lives
• Project is on time, in scope, and in budget
• Developed positive working relationships and trust with Jeffcom and the E911 Authority Board
Charlotte County, FL Sheriff’s Office – Inform Web RMS
August 2017 – Present
• Developed Project Plan for project implementation
• Developed budget and SOW
• Project is on time, in scope, and in budget
Yahmill, OR Communications – Inform CAD/Mobile
December 2017 – Present
• Developed Project Plan for project implementation
• Developed budget and SOW
• Project is on time, in scope, and in budget
#11..
- 708 -
Resumes of Key Personnel
Confidential and Proprietary CentralSquare Technologies Copyright © 2018 Business Analyst Motorola Solutions, Chicago, IL
New World Systems, Troy MI
February 2006 – December 2016
• Point of contact for large clients. Projects included Colorado State Patrol, Honolulu Police Department, Prince George’s County, MD, and the National Park Service Yosemite
National Park, and Lake Mead National Recreation Area.
Assigned to Tier 1 projects
• Developed professional relationships and trust with clients during project life, from Kickoff to Go Live. Worked with clients to configure, test, train, and implement CAD/Mobile software
Education State of Colorado, Colorado
April 1993 – June 2006
• Public Affairs Specialist, Colorado State Patrol
• Cadet Trooper, Colorado State Patrol
• Communications Specialist, Colorado State Patrol
• Sergeant, Colorado Department of Corrections
#11..
- 709 -
Resumes of Key Personnel
CentralSquare Technologies Copyright © 2018 Confidential and Proprietary Brian K. Powell Project Manager
Summary Skilled project manager with 20 years of experience managing implementation of public safety software systems on both the agency and vendor side. Mr. Powell has over 35 years of public safety experience and began dispatching in 1983.
Experience
Project Manager CentralSquare Technologies , Lake Mary, FL 2016 – Present
Primary point of contact during project implementation. Develop project documents including: Statement of Work (SOW),
Implementation Schedule, technical requirements, and project budget. Oversee entire project, generating detailed documentation on project status to management and clients.
Key Projects with
CentralSquare
Monroe County, NY – Inform Jail 5
February 2018 – Present
Positions: 175 Jail production positions with disaster recovery.
Solution: Deployment of Inform Jail, including NCIC/Records check integration. Target Go Live is March 2019.
San Bernardino County, CA – Inform RMS
February 2018 – Present
Positions: 185 RMS production positions, 250 FBR production positions.
Solution: Deployment of Inform RMS along with interfaces to CopLink, Crossroads, LinX, Data Ticket, and APS citation import, County DA system, County Imaging system, and Tiburon TC CAD and Message Switch integration. Target Go Live is December 2018.
City of Alameda, CA – CAD/RMS/Mobile
March 2017 – March 2018
Positions: Five CAD production seats with Mobile, 23 RMS.
Solution: Deployment of Inform CAD, Mobile, and RMS, including ANI/ALI interface, NCIC/Records Check, and interfaces to ePolice Reporting and Turbo Data Citation import.
CAD System Administrator
and Project Manager
Valley Communications Center
2010 – 2016
Responsible for the successful CAD implementation for a 23-agency dispatch center. As a hands-on manager, created mobile and web templates for the system, statistical and billing reports, and technical documentation. Oversaw the maintenance of both the new system and the one being phased out.
#11..
- 710 -
Resumes of Key Personnel
Confidential and Proprietary CentralSquare Technologies Copyright © 2018 CAD Team Lead / Project
Manager / Solutions
Engineer
Tiburon Inc.
1998 – 2010
Managed CAD and RMS implementations for agencies throughout the United States. Trained clients and internal staff; answered RFPs, provided system and hardware information and pricing.
Additional Positions Police/Fire/EMS dispatcher (15 years) Police Officer (three years)
Education Eastern Washington University – Computer Science #11..
- 711 -
Resumes of Key Personnel
CentralSquare Technologies Copyright © 2018 Confidential and Proprietary Naomi Bissonette Project Manager
Summary Skilled project manager with 18 years of experience managing implementation of public safety software systems on both the agency and vendor side.
Experience
Project Manager CentralSquare Technologies, Lake Mary, FL 2007 – Present
Primary point of contact during project implementation. Develop project documents including: Statement of Work (SOW),
Implementation Schedule, technical requirements, and project budget. Oversee entire project, generating detailed documentation on project status to management and clients.
Key Projects with
CentralSquare
• City of Milpitas, CA – RMS web implementation
• St. Louis County, MN – CAD/Mobile implementation
• Fort Mill, SC – RMS web implementation
• Brentwood, TN – RMS web implementation
CAD Project Manager Consolidated Dispatch Agency, City of Tallahassee, Leon County
2016
Managed simultaneous projects in the Consolidated Dispatch Center directly related to the Computer Aided Dispatch workstations and CAD software:
• CAD software upgrade for multiple agencies (law, fire, EMS)
• Managing personnel
• Process Improvement, Performance Management,
Coaching and Mentoring, Resource Management, Risk
Analysis
• Agency Liaison: Finance, Purchasing, Development,
Staging, Training, Desktop Support, Tech Support,
Customer Care
Project Manager for Public
Safety Solutions
SunGard
2000 – 2015
• Led simultaneous public safety and justice software
implementations on-time and within budget
• Increased use of technology, reduced redundancy, and
improved data accuracy/sharing through data integration • Managed client relationships, provided strategic direction, and coordinated with intra-agency departments.
#11..
- 712 -
Resumes of Key Personnel
Confidential and Proprietary CentralSquare Technologies Copyright © 2018 • Implemented records management, computer aided
dispatch, emergency medical service (EMS), courts, and
jails
• Managed client transition from implementation to customer support upon completion of successful projects
• Established client trust, ensured communications with all levels of agency stakeholders and third-party vendors.
Education Everglades University – Bachelor Degree in Alternative Medicine Edison College – Associates Degree in Criminal Justice
University of Louisville – Southern Police Institute –
Administrative Officer’s Course
Certifications Project Management Institute (PMI), Project Management Professional (PMP) since 2010
#11..
- 713 -
Resumes of Key Personnel
CentralSquare Technologies Copyright © 2018 Confidential and Proprietary Stephen Watt Project Manager
Summary Skilled project manager with 32 years of experience managing implementation of public safety software systems on both the agency and vendor side.
Experience
Project Manager CentralSquare Technologies , Lake Mary, FL 2007 – Present
Primary point of contact during project implementation. Develop project documents including: Statement of Work (SOW),
Implementation Schedule, technical requirements, and project budget. Oversee entire project, generating detailed documentation on project status to management and clients.
Key Projects with
CentralSquare
Hall County, GA – CAD/Mobile
September 2016 – June 2017
Positions: 20 CAD production seats with disaster recovery and Mobile.
Solution: Deployment of Inform CAD/Mobile which also included the installation of multiple Interfaces including the Inform Message Switch. System went live June 20, 2017 without any adjustments to the schedule.
Central EMS, AR – CAD/Mobile
June 2017 – December 2017
Positions: Five CAD production seats with Mobile.
Solution: The Inform CAD/Mobile deployment for Central EMS was a Rapid Implementation Deployment. The Inform CAD/Mobile System went live December 5, 2017, which was less than six months from the time of the project kickoff.
Rutherford County, TN – CAD/Mobile/RMS/JMS
January 2017 – Present
Position: Seven CAD production seats with disaster recovery and Mobile.
Solution: Inform CAD/Mobile/RMS/JMS full suite deployment with a two-phased approach. CAD/Mobile is scheduled to Go Live June 11 as part of the first-phase. In the second-phase, RMS and Jail is scheduled to Go Live in November 2018. This project also includes the integration of the Rutherford EMS Communications Center into the Rutherford County Sheriff’s Inform CAD/Mobile system for dispatch of County Fire and EMS agencies. There are multiple standard and custom interfaces associated with this project including a CAD-to-CAD interface with the Murfreesboro Police Department. #11..
- 714 -
Resumes of Key Personnel
Confidential and Proprietary CentralSquare Technologies Copyright © 2018 Project Manager L. Robert Kimball
2006 – 2016
Managed and consulted on projects to include radio systems acquisition/implementation, assessment, and management of 9-1-1 operations, Next Generation (NG) 9-1-1 network implementation, and new facilities technology acquisition/implementation. • Consistently completed projects on time and within budget • Assisted in development of large bids and proposals
• Managed project budgets over $1M
• Consulted on variety of public safety projects to include 9-1-1 operations assessment, NG 9-1-1 networks, ESInet, CAD/RMS and Radio
Emergency Services
Director
Crawford County
1986 – 2006
Responsible for the management of the Emergency Management Program, 9-1-1 Communication Center, and the Hazardous
Materials Safety Program.
• Coordinated the implementation of 9-1-1 and new
communication center
• Directed the implementation of a new county-wide public safety radio network
• Maintained emergency plans and response procedures to state and federal standards
Education Edinboro University, Field Fire Science
#11..
- 715 -
Resumes of Key Personnel
CentralSquare Technologies Copyright © 2018 Confidential and Proprietary Jennifer Hart Project Manager
Summary Skilled project manager with nine years of experience managing implementation of public safety software systems on both the agency and vendor side.
Experience
Project Manager CentralSquare Technologies , Lake Mary, FL 2016 – Present
Primary point of contact during project implementation. Develops project documents including: Statement of Work (SOW),
Implementation Schedule, technical requirements, and project budget. Oversees entire project, generating detailed documentation on project status to management and clients.
Key Projects with
CentralSquare
Upland Police Department, CA – CAD/Mobile/RMS
May 2017 – March 2018
Positions: Five CAD production seats with Mobile and RMS Solution: CAD, Mobile, and RMS deployment including several custom interfaces and full data conversions for CAD and RMS.
Murrieta Police Department, CA – CAD/Mobile/RMS
July 2017 – Present
Positions: Five CAD production seats with Mobile and RMS.
Solution: CAD, Mobile, and RMS deployment including several custom interfaces and full data conversions from multiple sources for CAD and RMS.
Senior Project Manager ScrollMotion, San Diego CA
April 2013 – June 2016
• Managed end-to-end custom-built mobile applications and software solutions using ScrollMotion's enterprise platform to create interactive content
• Responsible for all aspects of the product life cycle from requirements collection through maintenance/post
deployment using tools such as Jira, SmartSheet, Microsoft Office, and Google Docs
• Successfully managed the client relationship from execution of SOW to delivery for multi large-scale mobile enterprise technology initiatives for clients such as Apple, VMware, AirWatch, Dow Chemical, Mattel, BP, and more
• Documented functional requirements using requirements matrix for custom projects to ensure a final solution mapped to business needs
• Proactively tracked, monitored, and reported all aspects of a detailed project plan, including but not limited to project #11..
- 716 -
Resumes of Key Personnel
Confidential and Proprietary CentralSquare Technologies Copyright © 2018 scope, timeline, resource utilization, budget, and quality assurance, ensuring visibility to leadership and escalating roadblocks as needed
Client Success Manager Mitek Systems, San Diego, CA
February 2011 – May 2012
• A successful Client Services Manager for an innovative, beta technology for multiple high-profile fortune 500
accounts that enable mobile applications with advanced
Optical Character Recognition (OCR) software using
Smartphone cameras.
• Maintained continuous alignment of project scope with strategic business objectives and made functional
requirement recommendations to achieve the business
result.
• Provided solution consulting to enterprise customers, including integration of Mitek’s Mobile Imaging Platform with existing architecture, troubleshooting, performance tuning, and best practices for UI design.
• Worked directly with the Engineering, Mobile Development, Sales, and Product Management teams and helped
standardize product offerings across verticals.
• Developed detailed project plans for simultaneous projects that resulted in enhanced visibility of inter-project
dependencies and greatly improved development efficiency.
Project Manager Concerro, San Diego, CA
July 2007 – January 2011
• Successfully configured, deployed, and trained 25 clients on the Concerro’s open shift software, from initiation to close. • Conducted initial reviews, planning, in-depth analysis, development of integration plans, and customer specific training of internet-based total shift management
functionality.
• Provided proactive and event-driven troubleshooting and triage, and balanced multiple customer implementations
simultaneously.
• Reviewed functional design specifications and competently identified and reported product defects.
• Worked closely with developers and effectively resolved diverse issues.
Education University of Redlands, Redlands, CA
Bachelor of Science, Business Administration
Certifications Project Management Professional, PMP (April 2013 – Present) #11..
- 717 -
Resumes of Key Personnel
CentralSquare Technologies Copyright © 2018 Confidential and Proprietary Wendy Cotton Senior Business Analyst
Summary Skilled business analyst with 22 years of experience in public safety software systems on both the agency and vendor side.
Experience
Senior Business Analyst TriTech Software Systems, San Diego, CA 2006-Present
Maintain project documentation and client-supplied information.
Identify, document, and communicate project risks to the project manager. Perform analysis and mapping of existing client operational processes to the TriTech system capabilities. Define system requirements and perform system demonstration and configuration. Create and maintain Operational and Test documentation.
Key Projects with
CentralSquare
Singapore Civil Defense Force Advanced C3 Emergency
System (Singapore) – CAD/Mobile
September 2009 – November 2014
Positions—22 CAD Production seats; 600 Mobile.
Solution— Deployment of CAD, Mobile and 13 interfaces to external systems. This project also included more than 20 CAD customizations.
Orange County Fire Authority (CA) – CAD/Mobile
November 2012 – December 2014
Positions—29 CAD Production seats; 350 Mobile.
Solution— Deployment of CAD, Mobile and 7 interfaces to external systems. This project also included: Integration to an
Interoperability Information Sharing HUB between four
communications centers and four Ambulance Service Area
Providers; Hardware and third parties under a subcontract relationship.
The San Francisco Bay Area Rapid Transit Police – Regional Anti-Terror Integrated Law Enforcement System (CA) –
CAD/Mobile/RMS/PSIM
August 2015 – February 2016
Positions—10 CAD Production seats; Mobile; RMS; PSIM.
Solution— Deployment of CAD, Mobile, integrations to external systems and two subcontractors. This project also included a subcontract for, and integration with a Physical Security Information Management System (PSIM). Thorough this integration the PSIM will create a CAD incident based upon BART Industrial Control Solution(s) input to the PSIM rules engine.
Senior Product Manager W.E. Consultants
2002-2005
Established a sole proprietorship company providing consulting services based on the needs of the contract agreement as defined by TriTech Software Systems.
#11..
- 718 -
Resumes of Key Personnel
Confidential and Proprietary CentralSquare Technologies Copyright © 2018 Paramedic I Keefco Ambulance
2004-2005
Responsible for the treatment and transport of patients in nonemergency situations; maintaining certification of Paramedic levels and advancing personal education; maintaining CPR certification.
Paramedic I Emergency Medical Care, Inc.
1997-2005
Dispatcher Emergency Medical Care, Inc.
1996-2001
Certifications • Paramedic level I
• CPR
• Emergency Medical Priority Dispatch Certification
• Level I–Basic Fire Fighters
• Class 4 (Ambulance, taxi and mini bus) license
#11..
- 719 -
Resumes of Key Personnel
CentralSquare Technologies Copyright © 2018 Confidential and Proprietary Don Shumate Lead Training Specialist
Summary Skilled training specialist with 25 years of experience in public safety.
Experience
Training Specialist TriTech Software Systems, San Diego, CA 2013-Present
Develop training materials and documentation for Inform CAD.
Implement and maintain the internal Training Web platform to unify product technical knowledge as well as serving as the head point for remote demonstration and training. Conduct business analysis of communication center workflow and procedures for custom adaptation of Inform CAD with code file data collection and integration. Deliver technical and software training to TriTech Clients.
Key Projects with
CentralSquare
Albany County, New York- CAD, 911
Aug-Oct 2017
• Positions- 50 (throughout region)
• Solution- Deployed CAD and 911 end user training to
numerous agencies within the Albany County 911 system.
LOGIS, Minnesota- CAD, Mobile, FBR/RMS
Jan-May 2017
• Positions- 50+ (throughout region)
• Solution- Deployed CAD, Mobile and FBR/RMS end user
training.
Hamilton County 911, Tennessee- CAD / Mobile / 911
Aug-Oct 2016
• Positions- 42
• Solution- Deployed CAD, Mobile and 911 end user training.
Orange County 911, New York- CAD, Mobile
June-Aug 2016
• Positions- 46
• Solution- Deployed CAD and Mobile end user training.
California State Parks / Lifeguards, California- CAD
March-April 2014
• Positions- 16
• Solution- Deployed CAD and 911 end user training to
numerous agencies within the Albany County 911 system.
Field Radio / Radio Console
Trainer
Motorola Solutions
2008-2013
Developed and delivered technical radio communications training to various governmental Motorola clients.
Police Officer / Sergeant Escondido Police Department
1989-2012
#11..
- 720 -
Resumes of Key Personnel
Confidential and Proprietary CentralSquare Technologies Copyright © 2018 Supervised, trained and managed police officers on varying shifts and divisions.
Incident Commander for numerous, large-scale critical incidents (wildfires, dignitary protection, shootings, civil disturbances, etc.).
Communications / CAD coordinator.
Chairman, Law Enforcement
Assistance Network
County of San Diego (L.E.A.N.)
1996-2012
Chairman of county-wide critical incident debriefing network attended by all governmental law enforcement agencies within the County of San Diego (including Federal and military) with the goal of improving interoperability during multi-agency, critical incidents.
Education San Diego State University, Bachelor Degree in Psychology Certifications • Incident Command (ICS) and National Incident Command (NIMS) Certifications- IS 100, 200, 300a, 300b, 400, 700, 800, COML
• California Police Officer Standards and Training (POST)- Supervisory Cert, POST Basic, Intermediate and Advanced Certs
• Presenter- APCO 2012, 2013
#11..
- 721 -
Resumes of Key Personnel
CentralSquare Technologies Copyright © 2018 Confidential and Proprietary Robert Vega Business Analyst
Summary Seasoned business analyst with over 16 years of experience managing the TriTech Inform CAD as a system administrator in a public safety dispatch environment.
Experience
Business Analyst TriTech Software Systems, San Diego, CA October 2016 – Present
Perform analysis and mapping of existing client operational processes to the TriTech system capabilities for dispatching, field operations, and reporting.
• Define system requirements, and perform system
demonstration and configuration.
• Create and maintain Operational Requirements Documents based on client operational needs and scenarios.
• Prepare Functional Acceptance Test documentation and
conduct tests.
• Support production roll out of new CAD and Mobile systems and client post-Go Live operations.
• Client training on TriTech applications.
.
Key Projects with
CentralSquare
Montgomery County/Clarksville Police, Clarksville, TN
December 2016 – August 2017
• Business Analyst – Inform CAD, Mobile and Inform ME
• Consolidated 9-1-1 PSAP between the County and City
• Police, Sheriff, City and County Fire Departments.
Population 193,479
• Interfaces to Classic RMS, Inform Web RMS, Jail, Watson Report Writing
• Complex, dynamic response planning for law and fire
agencies
• Paging, TTMS/Records Check, Station Alerting
• Administrative and End-user training for CAD and Mobile • System went live on schedule without delay
Jefferson County E9-1-1, Lakewood, CO
January 2017 – March 2018
• Business Analyst – Inform CAD and Mobile
• New consolidated 9-1-1 PSAP responsible for the dispatch of the Jefferson County Sheriff’s Office, four city police departments (Arvada, Golden, Lakewood, and Wheat Ridge) and three fire communications centers (West Metro, Arvada, and Evergreen). Population: 565, 524
• Paging, Station Alerting, Smart 911, TTMS/Records Check, Auto-Dispatch, RMS interfaces to multiple systems.
• Administrative and End-user training for CAD and Mobile • System prepared to Go Live without delay.
#11..
- 722 -
Resumes of Key Personnel
Confidential and Proprietary CentralSquare Technologies Copyright © 2018 Communications Supervisor
CAD System Manager
City of Milpitas Police Department, Milpitas, CA
May 1997 to October 2016
• Implementing and managing the TriTech Inform CAD
• Agency CLETS/NCIC Coordinator
• Supervisor of busy public safety answering point
Dispatcher /
CAD Administrator
San Ramon Valley Fire Protection District, San Ramon, CA January 2011 - Present
• Inform CAD build and management
• Police, Fire and EMS Dispatcher
• Inform CAD Trainer
#11..
- 723 -
Resumes of Key Personnel
CentralSquare Technologies Copyright © 2018 Confidential and Proprietary Allen Anderson Business Analyst
Summary Skilled business analyst with more than 20 years of experience in public safety software systems on both the agency and vendor side.
Experience
Business Analyst CentralSquare Technologies, Lake Mary, FL 2012-Present
Maintain project documentation and client-supplied information.
Identify, document, and communicate project risks to the project manager. Perform analysis and mapping of existing client operational processes to the Inform system capabilities. Define system requirements and perform system demonstration,
configuration, and facilitated application workshops. Create and maintain Operational and Test documentation. Conduct Inform RMS and Inform Jail Functional Acceptance Tests, based on the approved test documents.
Key Projects with
CentralSquare
Hamilton County Sherriff Office, Chattanooga, TN -- Primary Inform RMS Business Analyst, 2016 – 2017
Implementation of Inform RMS Web
Greene County Sheriff Office, Greeneville, TN -- Primary Inform Jail and Inform RMS Business Analyst, 2015 – 2017
Implementation of Inform RMS, Inform Jail, Inform CAD
San Ramon Police Department, San Ramon, CA -- Primary
Inform RMS Business Analyst, 2016 – 2017
Implementation of Inform RMS, Inform CAD, Inform Mobile with Multiple Interfaces
Concord Police Department, Concord, CA -- Primary Inform RMS Business Analyst, 2016 – 2018
Implementation of Inform RMS, Inform CAD, Inform Mobile Gila River Police Department, Gila River Indian Community, AZ --Primary Inform RMS Web Business Analyst, 2017 – 2018
Implementation of Inform RMS Web, Inform CAD, Inform Mobile Various Positions Various Companies
• Fifteen years of experience as a Support Technician, Public Safety Software Specialist including all areas of
Implementation of a multitude of public safety applications • Eight years as Safety Director for non-profit organization including site security, OSHA standards training, employee management, and the primary liaison with local, county, state and federal (FBI) public safety officials
• Responsible as Safety Director for annual budgets in excess of $250,000 and multimillion-dollar properties.
• As Safety Director, managed, designed, and implemented the safety and security systems for executives and traveled with VIPs in the U.S., Canada, Europe, Australia, and West Africa.
#11..
- 724 -
Resumes of Key Personnel
Confidential and Proprietary CentralSquare Technologies Copyright © 2018 • Received Law Enforcement Degree from the City of Atlanta Police Academy
• Atlanta Police Officer patrolling/working high crime areas of the metro for eight years.
• Police Training Officer, trained police recruits and was also formally trained in and performed domestic crisis
intervention duties
Education University Georgia, Bachelor Degree in Journalism/Political Science
Georgia State University, Undergraduate Course Study, Business Administration
Certifications • United States Air Force, Weather Forecaster Certificate, Veteran
• Awarded Certificate of Commendation from State of
Minnesota, Governor Tim Pawlenty
#11..
- 725 -
Resumes of Key Personnel
CentralSquare Technologies Copyright © 2018 Confidential and Proprietary Angela Velasquez Business Analyst
Summary Skilled business analyst with 12 years of experience in public safety software systems.
Experience
Business Analyst CentralSquare Technologies, Lake Mary, FL 2012-Present
Maintain project documentation and client-supplied information.
Identify, document, and communicate project risks to the project manager. Perform analysis and mapping of existing client operational processes to the Inform system capabilities. Define system requirements and perform system demonstration and configuration. Create and maintain Operational and Test documentation.
Key Projects with
CentralSquare
The City of Bryan Local Police Department, Brazos County Sheriff, Brazos County Constables (TX) – RMS/FBR
April 2016 – Present
Positions – 10 CAD Call taker/Dispatcher positions, 70 concurrent mobile units, and 182 concurrent Field Based Reporting/RMS positions.
Solution – Deployment of previous TC CAD customer to Inform RMS. This project also included integrations with Property & Evidence hardware, and interface with Odyssey, their existing jail and court software.
The City of Campbell Police Department (CA) –
RMS/FBR/CAD/Mobile
October 2017 – April 2018 – pilot
Positions – 45 concurrent Field Based Reporting/RMS positions.
Solution – Deployment of RMS Web and RMS Client UI systems, along with integration with Inform CAD. This project also included an interface with the BEAST Property and Evidence software.
Murrieta Police Department (CA) – RMS/FBR/CAD/Mobile
June 2017 – Present
Positions – 25 concurrent Field Based Reporting/RMS positions.
Solution – Deployment of RMS Web and RMS Client UI systems.
This project also included integration with Inform CAD, Mobile, and IQ.
Training Specialist CentralSquare Technologies, Lake Mary, FL 2011-2012
Develop training materials and deliver technical and software training to clients.
Dispatcher San Antonio Police Department
2009-2011
Managing Partner Texas Diversified Services
2009
Construction and landscaping services.
#11..
- 726 -
Resumes of Key Personnel
Confidential and Proprietary CentralSquare Technologies Copyright © 2018 Underwriting Supervisor Marsh USA
2006-2008
Licensed Flood Insurance Underwriter
Education University of The Incarnate Word, Master’s Degree in Organizational Development
University of The Incarnate Word, Bachelor Degree in Banking and Finance
Certifications • Texas Crime Information Center / National Crime Information Center (TCIC/NCIC) Certification
• National Flood Insurance Program, Training
• FEMA Training on Flood Maps/Mapping
#11..
- 727 -
Resumes of Key Personnel
CentralSquare Technologies Copyright © 2018 Confidential and Proprietary Crystal Roth Senior Business Analyst
Summary Crystal Roth is a Business Analyst with 25 years of experience in Law Enforcement and Public Safety. Ms. Roth’s experience and skills permits her to be successful through all phases of project implementation. Ms. Roth’s project experience is instrumental in providing clients with a thorough business process analysis, guidance in system configuration to achieve client goals and expectations, and training for application software and interfaces, system integration, and full client support during and after the implementation process. Ms. Roth was a previous
Telecommunicator for 20 years prior to joining CentralSquare.
Experience
Business Analyst CentralSquare Technologies
2013-Present
• Complete project assignments and work in partnerships with clients.
• Maintain project documentation, files, journals, and clientsupplied information. • Identify, document, and communicate project risks to the project manager.
• Perform analysis and planning of existing client operational processes to the Inform system capabilities taking into consideration the client’s needs but not limited to
dispatching, field operations, administrative, and State reporting for UCR and NIBRS.
• Conduct Functional Acceptance Tests, based on the
approved test documents.
• Support production implementation of new systems and
client post-Go Live operations.
• Provide training on Inform applications.
• Support implementation of interfaces; State interfaces and various third-party interfaces.
• Assist with development and deployment of new product features.
• Support data conversion efforts.
Key Projects with
CentralSquare
Milwaukee Police Department, Milwaukee, WI - Inform RMS - Primary RMS Business Analyst 2016 -
2018
• Implementation of Inform RMS, Inform Jail, Tiburon CAD integration with Inform RMS
• Multiple Interfaces implemented; TraCS Interface for
Crash and Citation, COMPASS (local interface), BAIR
Analytics, Lexis Nexis Accurint Crime Analysis and iBase to support Agency Fusion Center, Morpho ID, Wisconsin
Justice Information Sharing
Anchorage Police Department, Anchorage, AK - Inform RMS - Primary RMS Business Analyst 2016 - 2018
• Implementation of Inform RMS, Inform CAD, Inform Mobile • Alaska State Crash and Citation
• Alaska State and Municipal Court Interfaces
• Alaska State APSIN/NCIC interface
#11..
- 728 -
Resumes of Key Personnel
Confidential and Proprietary CentralSquare Technologies Copyright © 2018 Dallas Fort Worth Airport Police - Inform CAD, Inform Mobile, Inform RMS - Primary RMS Business Analyst 2017
• Implementation of Inform RMS, Inform CAD, Inform Mobile Training/Resource Specialist Tiburon, Inc.
2013-2016
• Provide Remote and Onsite Administration, User Training, and Train-the-Trainer for both DispatchNow CAD and
Total Enforcement RMS.
• Coordinate and provide direction to multi-agency clients through the implementation process of Tiburon systems,
working with a variety of Department Heads or their
respective representatives.
• Prepare clients for software implementation in which may consist of QA of the sites system as well as assistance with configurations.
• Provide Onsite Go-Live support to clients.
• Work directly with Project Managers to ensure successful training and implementations of Tiburon products.
• Prepare Agenda and Training Documents.
Facilitator/Instructor Southwestern Illinois Law Enforcement Commission 2009-2013
• Facilitate the 80-hour Telecommunicator Course for new Telecommunicators within a five-county region in
accordance to APCO and State Standards.
• Instruct various Telecommunicator classes within the
course curriculum
Training Coordinator /
CAD Project Manager /
EMD Coordinator
St. Clair County ETSB
2006-2013
• Develop and Implement various training programs for
Telecommunicator’s in St. Clair County
• CAD Administrator of the Positron PowerCAD System
• Project Manager for the implementation of the Tiburon DispatchNow CAD System
Education Southwestern Illinois College, Degree in Administration of Justice
Southwestern Illinois College, Degree in Computer Science Certifications CJIS-certified
#11..
- 729 -
Inform Jail Implementation Team
Tom Crockett – Business Analyst
Mr. Crockett has over five years of software conversion and implementation experience. He thrives while problem solving and will collaborate with PPD to determine the best way to utilize the system software. With prior customer service and educational experience, Mr. Crockett has experience in and enjoys working with many different people at once. Mr. Crockett will collaborate with the project manager as necessary to configure and then train users on the Inform Jail software during implementation for PPD. He holds a bachelor’s degree in business administration with an emphasis in economics from the University of South Dakota.
Carl Ware – Data Conversion Analyst II
Mr. Ware has more than seven years of experience in data conversion and analysis. He will identify how PPD legacy data is formatted, linked, and organized, and will develop scripts to load the legacy data into conversion tools and ultimately into Inform Jail. He will work with PPD to determine where the agency needs and wants the legacy data to appear in Inform Jail. Mr. Ware has a deep knowledge of a variety of database systems and the tools used to perform data conversions. He holds a bachelor’s degree in computer information systems from Dakota State University. Mr. Ware is also CJIS certified and a member of the (605) SQL User Group.
Shelby Schmidt – Training Specialist
Ms. Schmidt has over 20 years of public safety experience as a 911 dispatcher and supervisor. With experience on both sides of the training process, Ms.
Schmidt understands how training impacts end users. She will work with the project manager and PPD as necessary to configure and train users on Inform Jail during implementation. Ms. Schmidt values continuing education and has taken courses in facilitative learning. She is a certified public manager and holds a bachelor’s degree in criminal justice from Carroll College in Waukesha, WI.
Resumes of Key Personnel
CentralSquare Technologies Copyright © 2018 Confidential and Proprietary #11..
- 730 -
Jason Banik –Associate Systems Engineer
Mr. Banik brings more than 15 years of information technology experience to the table. With prior experience in customer service and database security, Mr. Banik has the strong customer focus and IT knowledge necessary to successfully implement interfaces for PPD. He will work closely with the thirdparty vendors and PPD to ensure that interfaces perform at maximum efficiency. Mr. Banik specializes in NCIC interfaces and will work with Inform Jail’s development team to test the interface functionality prior to Go Live.
Mr. Banik studied computer network administration at Southeast Technical Institute.
Resumes of Key Personnel Confidential and Proprietary CentralSquare Technologies Copyright © 2018 #11..
- 731 -
ID WBS Task Name Duration Start Finish Predecessors Successors Resource Names 0 0 Glendale 398.5 days Tue Jan 1,
'19
Tue Jul 28, '20
1 1 Phase I- Initiation 25 daysWed Jan 2, '19 Tue Feb 5, '19 377SS,378SS,379SS 2 1.1 Contract complete 20 daysWed Jan 2, '19 Tue Jan 29, '19 3,4,270 3 1.2 Review Project Schedule 5 daysWed Jan 30, '19Tue Feb 5, '19 2 TSS-PM 4 1.3 Perform TriTech Internal Initiation activities 5 daysWed Jan 30, '19Tue Feb 5, '19 2 5 TSS-PM 5 1.4 Phase I (Initiation) Complete 0 days Tue Feb 5, '19Tue Feb 5, '19 4 7 6 2 Phase II- Planning 19 daysWed Feb 6, '19 Tue Mar 5, '19 7 2.1 Develop Project Management Plans (Communications
Mgmt, Risk Mgmt)
5 days Wed Feb 6,
'19
Tue Feb
12, '19
5 9,8FS+4 days,37 TSS-PM
8 2.2 Baseline Project Schedule 10 daysWed Feb 20, '19 Tue Mar 5, '19 7FS+4 days 9 TSS-PM 9 2.3 Phase II (Planning) Complete 0 daysTue Mar 5, '19 Tue Mar 5, '19 7,8 10 3 Phase III - Execution 398.5 days Tue Jan 1, '19 Tue Jul 28, '20 11 3.1 Hardware/OS Configuration 124 daysWed Feb 27, '19 Wed Aug 21, '19 12 3.1.1 HDW - Review: Site Prep/Network Diagram Review 5 daysWed Feb 27, '19 Tue Mar 5, '19 37FS+5 days 21,13 TSS-PM,Client,TSS-CIS 13 3.1.2 HDW - Procure and deliver Hardware and third party Software 30 days Wed Mar 6, '19
Tue Apr
16, '19
12 14FS+5 days TSS-PM,Client 14 3.1.3 HDW - Complete ISR Configuration Sheet 5 daysWed Apr 24, '19 Tue Apr 30, '19 13FS+5 days 15 Client 15 3.1.4 HDW - Base HDW/OS installation 20 daysWed May 1, '19 Wed May 29, '19 14 21,17,16,86 Client 16 3.1.5 HDW - VM Configuration 2 daysThu May 30, '19 Fri May 31, '19 15 17 Client 17 3.1.6 HDW - System Installation and Server Configuration 20 daysMon Jun 3, '19Fri Jun 28, '19 15,16 43FS+10 days,47,21,20,18,32,95,242,19,31,30 TSS-CIS,Client 18 3.1.7 HDW - Conduct Technical Handoff Meeting with Client 1 day Mon Jul 1, '19Mon Jul 1, '19 17 21 Client,TSS-CIS,TSS-TSE 19 3.1.8 HDW - Archiving_Reporting/Replication and Purging 2 days Mon Jul 1, '19Tue Jul 2, '19 17 21,20FS+30 days TSS-CIS 20 3.1.9 HDW - Disaster Recovery System Installation and Configuration
5 days Thu Aug 15,
'19 Wed Aug21, '19
17,19FS+30 days 21 TSS-CIS 21 3.1.10 HDW - Complete 0 daysWed Aug 21, '19 Wed Aug 21, '19 12,15,17,19,20,18 22 3.2 GIS 91 daysWed Feb 27, '19Fri Jul 5, '19
23 3.2.1 GIS - Inform GIS Orientation (Remote) 0.5 daysWed Feb 27, '19 Wed Feb 27, '19 37FS+5 days 24 3.2.2 GIS - Client Supplies GIS Data 10 daysWed Mar 6, '19 Tue Mar 19, '19 37FS+10 days 25 Client 25 3.2.3 GIS - Complete GIS Analysis and Report 5 daysWed Mar 20, '19 Tue Mar 26, '19 24 26,34 26 3.2.4 GIS - Analysis and Report Review (Remote) 0.5 daysWed Mar 27, '19 Wed Mar 27, '19 25 27 27 3.2.5 GIS - GIS Data Corrections based on GIS Analysis and Report
10 days Wed Mar 27,
'19 Wed Apr10, '19
26 28
TSS-PM
TSS-PM
2/5
TSS-PM
TSS-PM
3/5
TSS-PM,Client,TSS-CIS TSS-PM,Client ClientClient ClientTSS-CIS,Client Client,TSS-CIS,TSS-TSE TSS-CIS TSS-CIS 8/21 Client Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May 4th Quarter 1st Quarter 2nd Quarter 3rd Quarter 4th Quarter 1st Quarter 2nd Quarter 3rd Quarter 4th Quarter 1st Quarter 2nd Quarter Task Split Milestone
Summary Project Summary External Tasks External MilestoneInactive Task Inactive Milestone
Inactive Summary Manual Task Duration-only Manual Summary Rollup Manual Summary Start-only Finish-only Deadline Progress Manual Progress Page 1 Project: Glendale Date: Thu Jan 24, '19 Exhibit B - Sample Project Plan CentralSquare Technologies 1 of 14 #11..
- 732 -
ID WBS Task Name Duration Start Finish Predecessors Successors Resource Names 28 3.2.6 GIS - Standard Mapping Conversion and Data Import for CAD 10 days Wed Apr 10, '19 Wed Apr24, '19
27 43FS+10 days,34,29TSS-GIS 29 3.2.7 GIS - Mobile Map Template and Configuration Build 1 dayWed Apr 24, '19 Thu Apr 25, '19 28 TSS-GIS 30 3.2.8 GIS - GIS Link Installation on Client's Site 1 day Mon Jul 1, '19Mon Jul 1, '19 17 34,33 TSS-GIS 31 3.2.9 GIS - Routing Server Configuration 0.5 days Mon Jul 1, '19Mon Jul 1, '19 17 32 3.2.10 GIS - RMS GIS Services 0.5 days Mon Jul 1, '19Mon Jul 1, '19 17 95 TSS-GIS 33 3.2.11 GIS - GISLink Training (onsite) 3 days Tue Jul 2, '19Fri Jul 5, '19 30 34 3.2.12 GIS - Complete 0 days Mon Jul 1, '19Mon Jul 1, '19 28,30,25 35 3.3 Inform CAD and Mobile Implementation 398.5 days Tue Jan 1, '19 Tue Jul 28, '20 36 3.3.1 Inform CAD 368.5 daysWed Feb 13, '19 Tue Jul 28, '20 37 3.3.1.1 CAD - Project Kickoff & System Orientation 4 daysWed Feb 13, '19 Tue Feb 19, '19 7 12FS+5 days,39FS+5 days,94FS+10 days,24FS+10 days,38FS+10 days,81FS+10 days,23FS+5 days,58 TSS-BA CAD,TSS-GIS,Client 38 3.3.1.2 CAD - Remote SMS Work Session 2 hrsWed Mar 6, '19 Wed Mar 6, '19 37FS+10 days TSS-BA CAD,TSS-GIS,Client 39 3.3.1.3 CAD - Client to complete SMS Worksheet 10 daysWed Feb 27, '19 Tue Mar 12, '19 37FS+5 days 40 Client 40 3.3.1.4 CAD - Conduct Codefile validation 5 daysWed Mar 13, '19 Tue Mar 19, '19 39 42 TSS-BA CAD,Client 41 3.3.1.5 CAD - Administration Training Course (Code File management)
3 days Wed Jul 8, '20 Mon Jul 13, '20261FS+20 days 42 3.3.1.6 CAD - Base Codefile Entry 45 daysWed Mar 20, '19 Tue May 21, '19 40 43FS+10 days TSS-BA CAD 43 3.3.1.7 CAD - DOLF Preparation 5 days Tue Jul 16, '19 Mon Jul 22, '19 42FS+10 days,17FS+10 days,28FS+10 days 44 TSS-BA CAD 44 3.3.1.8 CAD - DOLF 5 days Tue Jul 23, '19 Mon Jul 29, '19 43 45,46FS+20 days,240,66,76,71 TSS-BA CAD,Client 45 3.3.1.9 CAD - Post DOLF Codefile entry 80 days Tue Jul 30, '19 Tue Nov 19, '19 44 47 Client 46 3.3.1.10 CAD - Response Plan Workshop 3 daysTue Aug 27, '19 Thu Aug 29, '19 44FS+20 days 47 3.3.1.11 CAD - Testing (FAT- Prep) 5 daysWed Nov 20, '19 Tue Nov 26, '19 45,17 48 TSS-BA CAD 48 3.3.1.12 CAD - Testing (FAT - Client Site) 4 daysWed Nov 27, '19 Wed Dec 4, '19 47 49FS+20 days,50 TSS-BA CAD,Client 49 3.3.1.13 CAD - Workshop #1 3 daysMon Jan 6, '20 Wed Jan 8, '20 48FS+20 days 50 TSS-BA CAD,Client 50 3.3.1.14 CAD - System Integration Ready 0 daysWed Jan 8, '20 Wed Jan 8, '20 48,49 53FS+4 days,254,255 51 3.3.1.15 CAD - User Training 136.5 daysWed Jan 15, '20 Tue Jul 28, '20 52 3.3.1.15.1 CAD - System Administration Training (at TriTech) 4 daysWed Jul 22, '20 Tue Jul 28, '20 261FS+30 days 53 3.3.1.15.2 CAD - User Training #1 4 daysWed Jan 15, '20 Mon Jan 20, '20 50FS+4 days 55,54FS+10 days TSS-BA CAD,Client 54 3.3.1.15.3 CAD - Supervisor Training 5 days Tue Feb 4, '20 Mon Feb 10, '20 53FS+10 days 55 TSS-BA CAD,Client 55 3.3.1.15.4 CAD User Training Complete 0 daysMon Feb 10, '20 Mon Feb 10, '20 53,54 56 56 3.3.1.15.5 Client End User Training 20 daysTue Feb 11, '20 Tue Mar 10, '20 55 261,63 Client 57 3.3.2 Inform Mobile 321 days Tue Jan 1, '19Tue Apr 7, '20 58 3.3.2.1 Mobile - System Orientation 1 dayWed Feb 20, '19 Wed Feb 20, '19 37 59 Client,TSS-BA MBL TSS-GIS TSS-GIS TSS-GIS TSS-GIS 7/1
TSS-BA CAD,TSS-GIS,Client TSS-BA CAD,TSS-GIS,Client Client TSS-BA CAD,Client TSS-BA CAD
TSS-BA CAD
TSS-BA CAD,ClientClient TSS-BA CAD
TSS-BA CAD,Client TSS-BA CAD,Client 1/8
TSS-BA CAD,Client TSS-BA CAD,Client 2/10Client Client,TSS-BA MBL Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May 4th Quarter 1st Quarter 2nd Quarter 3rd Quarter 4th Quarter 1st Quarter 2nd Quarter 3rd Quarter 4th Quarter 1st Quarter 2nd Quarter Task Split Milestone
Summary Project Summary External Tasks External MilestoneInactive Task Inactive Milestone
Inactive Summary Manual Task Duration-only Manual Summary Rollup Manual Summary Start-only Finish-only Deadline Progress Manual Progress Page 2 Project: Glendale Date: Thu Jan 24, '19 Exhibit B - Sample Project Plan CentralSquare Technologies 2 of 14 #11..
- 733 -
ID WBS Task Name Duration Start Finish Predecessors Successors Resource Names 59 3.3.2.2 Mobile - Software Installation and Configuration 25 daysThu Feb 21, '19 Wed Mar 27, '19 58 60 Client,TSS-BA MBL 60 3.3.2.3 Mobile - Administrator Training 1 dayThu Mar 28, '19 Thu Mar 28, '19 59 Client,TSS-BA MBL 61 3.3.2.4 Mobile - Train the trainer 1 dayWed Jan 2, '19 Wed Jan 2, '19 62 0 Mobile - System Integration Ready 0 days Tue Jan 1, '19Tue Jan 1, '19 254,255,63 Client,TSS-BA MBL 63 3.3.2.6 Client End User Training 20 daysWed Mar 11, '20Tue Apr 7, '20 62,56 261 Client 64 3.3.3 Standard CAD Interfaces 146 daysWed Mar 6, '19 Mon Sep 30, '19 65 3.3.3.1 IF ANI-ALI (E911) 15 daysTue Jul 30, '19 Mon Aug 19, '19 66 3.3.3.1.1 ANI-ALI (E911) - Standard IRD Review 3 days Tue Jul 30, '19 Thu Aug 1, '19 44 67 TSS-SE,Client 67 3.3.3.1.2 ANI-ALI (E911) - Installation - Configuration 5 days Fri Aug 2, '19 Thu Aug 8, '19 66 68 TSS-SE 68 3.3.3.1.3 ANI-ALI (E911) - Client/Vendor Testing 5 days Fri Aug 9, '19 Thu Aug 15, '19 67 69 TSS-SE,Client 69 3.3.3.1.4 ANI-ALI (E911) - FAT 2 days Fri Aug 16, '19 Mon Aug 19, '19 68 91 TSS-SE,Client 70 3.3.3.2 IF Alpha-Numeric Paging 15 daysTue Jul 30, '19 Mon Aug 19, '19 71 3.3.3.2.1 Standard IRD Review 3 days Tue Jul 30, '19 Thu Aug 1, '19 44 72 TSS-SE,Client 72 3.3.3.2.2 Installation - Configuration 5 days Fri Aug 2, '19 Thu Aug 8, '19 71 73 TSS-SE 73 3.3.3.2.3 Client/Vendor Testing 5 days Fri Aug 9, '19 Thu Aug 15, '19 72 74 TSS-SE,Client 74 3.3.3.2.4 FAT 2 days Fri Aug 16, '19 Mon Aug 19, '19 73 91 TSS-SE,Client 75 3.3.3.3 IF CAD to External System Incident Transfer 15 daysTue Jul 30, '19 Mon Aug 19, '19 76 3.3.3.3.1 External System Incident Transfer - Standard IRD Review3 days Tue Jul 30, '19 Thu Aug 1, '19 44 77 TSS-SE,Client 77 3.3.3.3.2 External System Incident Transfer - Installation - Configuration
5 days Fri Aug 2, '19 Thu Aug 8,
'19
76 78 TSS-SE 78 3.3.3.3.3 External System Incident Transfer - Client/Vendor Testing5 days Fri Aug 9, '19 Thu Aug 15, '19 77 79 TSS-SE,Client 79 3.3.3.3.4 External System Incident Transfer - FAT 2 days Fri Aug 16, '19 Mon Aug 19, '19 78 91 TSS-SE,Client 80 3.3.3.4 IF Records Check 146 daysWed Mar 6, '19 Mon Sep 30, '19 81 3.3.3.4.1 IF R-Check - Standard IRD Review 5 daysWed Mar 6, '19 Tue Mar 12, '19 37FS+10 days 82SS,83SS TSS-SE,Client 82 3.3.3.4.2 IF R-Check - Provide all connectivity information to TriTech
10 days Wed Mar 6,
'19
Tue Mar 19, '1981SS Client 83 3.3.3.4.3 IF R-Check - Provide State Communication Protocol and Msg Key Documentation to TriTech 10 days Wed Mar 6,
'19
Tue Mar 19, '1981SS 84 Client 84 3.3.3.4.4 IF R-Check - Draft Query Configuration Sheet 10 daysWed Mar 20, '19Tue Apr 2, '19 83 85 TSS-SE 85 3.3.3.4.5 IF R-Check - Final Query Configuration Sheet 10 daysWed Apr 3, '19 Tue Apr 16, '19 84 86 TSS-SE 86 3.3.3.4.6 IF R-Check - Installation and Configuration (Including RMS Plugin)
60 days Thu May 30,
'19
Thu Aug
22, '19
85,15 87 TSS-Eng
Client,TSS-BA MBL Client,TSS-BA MBL 1/1 Client TSS-SE,Client TSS-SE TSS-SE,Client TSS-SE,Client TSS-SE,Client TSS-SE TSS-SE,Client TSS-SE,Client TSS-SE,Client TSS-SE TSS-SE,Client TSS-SE,Client TSS-SE,Client Client Client TSS-SE TSS-SE TSS-Eng Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May 4th Quarter 1st Quarter 2nd Quarter 3rd Quarter 4th Quarter 1st Quarter 2nd Quarter 3rd Quarter 4th Quarter 1st Quarter 2nd Quarter Task Split Milestone
Summary Project Summary External Tasks External MilestoneInactive Task Inactive Milestone
Inactive Summary Manual Task Duration-only Manual Summary Rollup Manual Summary Start-only Finish-only Deadline Progress Manual Progress Page 3 Project: Glendale Date: Thu Jan 24, '19 Exhibit B - Sample Project Plan CentralSquare Technologies 3 of 14 #11..
- 734 -
ID WBS Task Name Duration Start Finish Predecessors Successors Resource Names 87 3.3.3.4.7 IF R-Check - External System Ready for Connectivity Test
1 day Fri Aug 23, '19 Fri Aug 23,
'19
86 88 Client 88 3.3.3.4.8 IF R-Check - Connectivity Test 5 daysMon Aug 26, '19 Fri Aug 30, '19 87 89 Client,TSS-Eng 89 3.3.3.4.9 IF R-Check - Client/State testing 10 days Tue Sep 3, '19 Mon Sep 16, '19 88 90 TSS-Eng,Client 90 3.3.3.4.10 IF R-Check - FAT 10 daysTue Sep 17, '19 Mon Sep 30, '19 89 91 TSS-SE,Client 91 3.3.3.5 Interfaces - System Integration Ready 0 daysMon Sep 30, '19 Mon Sep 30, '19 90,79,69,74 254,255 92 3.4 Inform RMS 317.5 daysWed Mar 6, '19Thu Jun 4, '20 93 3.4.1 Inform RMS Implementation 317.5 days Wed Mar 6, '19
Thu Jun 4,
'20
94 3.4.1.1 RMS - Project Kickoff & System Orientation 4 daysWed Mar 6, '19 Mon Mar 11, '19 37FS+10 days 229,95,118FS+15 days,128FS+20 days,168FS+20 days,158FS+20 days,148FS+20 days,138FS+20 days TSS-BA RMS,Client 95 3.4.1.2 RMS - Administration Review and Training 3 days Mon Jul 1, '19Fri Jul 5, '19 94,17,32 97FS+15 days,96,104,106,107 TSS-BA RMS,Client 96 3.4.1.3 RMS - Base System Build by Client 90 days Fri Jul 5, '19 Mon Nov 11, '19 95 106,107 TSS-BA RMS 97 3.4.1.4 RMS - Workshop #1 (Incident, Arrest, Case Management)
3 days Fri Jul 26, '19 Wed Jul 31, '1995FS+15 days 98FS+15 days,107,104,106TSS-BA RMS,Client 98 3.4.1.5 RMS - Workshop #2 (Citation, Crash, and Other Event) 3 daysWed Aug 21, '19 Mon Aug 26, '19 97FS+15 days 106,107,104,99FS+15 days Client,TSS-BA RMS 99 3.4.1.6 RMS - Report Writing Training 3 daysTue Sep 17, '19Fri Sep 20, '19 98FS+15 days 100FS+10 days Client,TSS-BA RMS 100 3.4.1.7 RMS - Output Designer Training 3 days Fri Oct 4, '19 Wed Oct 9, '19 99FS+10 days 101FS+15 days Client,TSS-BA RMS 101 3.4.1.8 RMS User Training - Property/Evidence 3 daysWed Oct 30, '19 Mon Nov 4, '19 100FS+15 days 102FS+15 days,104,106,107 Client,TSS-BA RMS 102 3.4.1.9 RMS - Workshop #3 (Records Administration) 3 daysMon Nov 25, '19 Mon Dec 2, '19 101FS+15 days 104,106,107,103 Client,TSS-BA RMS 103 3.4.1.10 RMS - System Build Out 60 daysMon Dec 2, '19 Thu Feb 27, '20 102 104 Client 104 3.4.1.11 RMS - DOLF - Prep 5 daysThu Feb 27, '20 Thu Mar 5, '20 97,98,95,101,102,103 105 TSS-BA RMS 105 3.4.1.12 RMS - DOLF 3 daysThu Mar 5, '20 Tue Mar 10, '20 104 107FS+7 days,106,240,133,233,223,213,203,193,183,173,163,153,143 Client,TSS-BA RMS 106 3.4.1.13 RMS - Testing (FAT- Prep) 5 daysTue Mar 10, '20 Tue Mar 17, '20 105,98,95,96,97,101,102 107 TSS-BA RMS 107 3.4.1.14 RMS - Testing (FAT- Execute at Client Site) 2 daysThu Mar 19, '20 Mon Mar 23, '20 106,105FS+7 days,98,97,95,96,101,102 108 Client,TSS-BA RMS 108 3.4.1.15 RMS - System Integration Ready 0 daysMon Mar 23, '20 Mon Mar 23, '20 107 110FS+20 days,255 109 3.4.1.16 RMS - User Training 32 daysMon Apr 20, '20Thu Jun 4, '20 110 3.4.1.16.1 RMS User Training - Field Officers 3 daysMon Apr 20, '20 Thu Apr 23, '20 108FS+20 days 113,111FS+1 day TSS-Trainer,Client 111 3.4.1.16.2 RMS User Training - Investigations 3 days Fri Apr 24, '20 Wed Apr 29, '20 110FS+1 day 113,112FS+2 daysTSS-Trainer,Client 112 3.4.1.16.3 RMS User Training - Records 3 days Fri May 1, '20 Wed May 6, '20 111FS+2 days 113 TSS-Trainer,Client 113 3.4.1.16.4 RMS - Client Conducted End User Training 4 wksWed May 6, '20Thu Jun 4, '20 110,112,111 114 Client 114 3.4.1.16.5 RMS User Training Complete 0 days Thu Jun 4, '20Thu Jun 4, '20 113 266 115 3.4.2 Inform RMS Interfaces 267.5 days Tue Apr 2, '19 Tue Apr 21, '20 116 3.4.2.1 Custom RMS Interfaces 267.5 days Tue Apr 2, '19 Tue Apr 21, '20 Client Client,TSS-Eng TSS-Eng,Client TSS-SE,Client 9/30 TSS-BA RMS,ClientTSS-BA RMS,Client TSS-BA RMS TSS-BA RMS,Client Client,TSS-BA RMS Client,TSS-BA RMS Client,TSS-BA RMS Client,TSS-BA RMS Client,TSS-BA RMS Client TSS-BA RMS Client,TSS-BA RMS TSS-BA RMS Client,TSS-BA RMS 3/23 TSS-Trainer,Client TSS-Trainer,Client TSS-Trainer,Client Client 6/4 Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May 4th Quarter 1st Quarter 2nd Quarter 3rd Quarter 4th Quarter 1st Quarter 2nd Quarter 3rd Quarter 4th Quarter 1st Quarter 2nd Quarter Task Split Milestone
Summary Project Summary External Tasks External MilestoneInactive Task Inactive Milestone
Inactive Summary Manual Task Duration-only Manual Summary Rollup Manual Summary Start-only Finish-only Deadline Progress Manual Progress Page 4 Project: Glendale Date: Thu Jan 24, '19 Exhibit B - Sample Project Plan CentralSquare Technologies 4 of 14 #11..
- 735 -
ID WBS Task Name Duration Start Finish Predecessors Successors Resource Names 117 3.4.2.1.1 Custom RMS Interface #1 LINX 76 days Tue Apr 2, '19 Thu Jul 18, '19 118 3.4.2.1.1.1 Requirement Analysis 5 days Tue Apr 2, '19 Mon Apr 8, '19 94FS+15 days 119 TSS-SE,Client 119 3.4.2.1.1.2 OSD Development 15 days Tue Apr 9, '19 Mon Apr 29, '19 118 120 TSS-SE 120 3.4.2.1.1.3 OSD Review and Revision 5 daysTue Apr 30, '19 Mon May 6, '19 119 121 TSS-SE,Client 121 3.4.2.1.1.4 OSD Approval 1 dayTue May 7, '19 Tue May 7, '19 120 122,178,188,198,208,218 Client 122 3.4.2.1.1.5 Interface Coding 4 wksWed May 8, '19 Wed Jun 5, '19 121 123 TSS-Eng 123 3.4.2.1.1.6 Interface Installation and Initial Testing 5 days Thu Jun 6, '19 Wed Jun 12, '19 122 124 TSS-Eng,Client 124 3.4.2.1.1.7 Interface testing with Vendor and Client 10 daysThu Jun 13, '19 Wed Jun 26, '19 123 125 TSS-Eng,Client 125 3.4.2.1.1.8 Interface Troubleshooting and Rework 10 daysThu Jun 27, '19 Thu Jul 11, '19 124 126 TSS-Eng 126 3.4.2.1.1.9 Interface FAT 5 days Fri Jul 12, '19 Thu Jul 18, '19 125 227 TSS-Eng,Client 127 3.4.2.1.2 Custom RMS Interface # 2 Citation Import 262.5 days Tue Apr 9, '19 Tue Apr 21, '20
128 3.4.2.1.2.1 Requirement Analysis 5 days Tue Apr 9, '19 Mon Apr 15, '19 94FS+20 days 129 TSS-SE 129 3.4.2.1.2.2 OSD Development 15 daysTue Apr 16, '19 Mon May 6, '19 128 130 TSS-SE 130 3.4.2.1.2.3 OSD Review and Revision 5 daysTue May 7, '19 Mon May 13, '19 129 131 TSS-SE,Client 131 3.4.2.1.2.4 OSD Approval 1 dayTue May 14, '19 Tue May 14, '19 130 132 Client 132 3.4.2.1.2.5 Interface Coding 4 wks Wed May 15, '19 Wed Jun 12, '19 131 133 TSS-Eng 133 3.4.2.1.2.6 Interface Installation and Initial Testing 5 daysTue Mar 10, '20 Tue Mar 17, '20 132,105 134 TSS-Eng 134 3.4.2.1.2.7 Interface testing with Vendor and Client 10 daysTue Mar 17, '20 Tue Mar 31, '20 133 135 TSS-Eng,Client 135 3.4.2.1.2.8 Interface Troubleshooting and Rework 10 daysTue Mar 31, '20 Tue Apr 14, '20 134 136 TSS-Eng 136 3.4.2.1.2.9 Interface FAT 5 daysTue Apr 14, '20 Tue Apr 21, '20 135 227 TSS-Eng,Client 137 3.4.2.1.3 Custom RMS Interface # 3 Suspicious Activity 262.5 days Tue Apr 9, '19 Tue Apr 21, '20 138 3.4.2.1.3.1 Requirement Analysis 5 days Tue Apr 9, '19 Mon Apr 15, '19 94FS+20 days 139 TSS-SE 139 3.4.2.1.3.2 OSD Development 15 daysTue Apr 16, '19 Mon May 6, '19 138 140 TSS-SE 140 3.4.2.1.3.3 OSD Review and Revision 5 daysTue May 7, '19 Mon May 13, '19 139 141 TSS-SE,Client 141 3.4.2.1.3.4 OSD Approval 1 dayTue May 14, '19 Tue May 14, '19 140 142 Client 142 3.4.2.1.3.5 Interface Coding 4 wks Wed May 15, '19 Wed Jun 12, '19 141 143 TSS-Eng 143 3.4.2.1.3.6 Interface Installation and Initial Testing 5 daysTue Mar 10, '20 Tue Mar 17, '20 142,105 144 TSS-Eng 144 3.4.2.1.3.7 Interface testing with Vendor and Client 10 daysTue Mar 17, '20 Tue Mar 31, '20 143 145 TSS-Eng,Client 145 3.4.2.1.3.8 Interface Troubleshooting and Rework 10 daysTue Mar 31, '20 Tue Apr 14, '20 144 146 TSS-Eng 146 3.4.2.1.3.9 Interface FAT 5 daysTue Apr 14, '20 Tue Apr 21, '20 145 227 TSS-Eng,Client 147 3.4.2.1.4 Custom RMS Interface # 4 CalGang 262.5 days Tue Apr 9, '19 Tue Apr 21, '20 148 3.4.2.1.4.1 Requirement Analysis 5 days Tue Apr 9, '19 Mon Apr 15, '19 94FS+20 days 149 TSS-SE TSS-SE,Client TSS-SE TSS-SE,Client ClientTSS-Eng TSS-Eng,Client TSS-Eng,Client TSS-Eng TSS-Eng,Client TSS-SE TSS-SE TSS-SE,Client ClientTSS-Eng TSS-Eng TSS-Eng,Client TSS-Eng TSS-Eng,Client TSS-SE TSS-SE TSS-SE,Client ClientTSS-Eng TSS-Eng TSS-Eng,Client TSS-Eng TSS-Eng,Client TSS-SE Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May 4th Quarter 1st Quarter 2nd Quarter 3rd Quarter 4th Quarter 1st Quarter 2nd Quarter 3rd Quarter 4th Quarter 1st Quarter 2nd Quarter Task Split Milestone
Summary Project Summary External Tasks External MilestoneInactive Task Inactive Milestone
Inactive Summary Manual Task Duration-only Manual Summary Rollup Manual Summary Start-only Finish-only Deadline Progress Manual Progress Page 5 Project: Glendale Date: Thu Jan 24, '19 Exhibit B - Sample Project Plan CentralSquare Technologies 5 of 14 #11..
- 736 -
ID WBS Task Name Duration Start Finish Predecessors Successors Resource Names 149 3.4.2.1.4.2 OSD Development 15 daysTue Apr 16, '19 Mon May 6, '19 148 150 TSS-SE 150 3.4.2.1.4.3 OSD Review and Revision 5 daysTue May 7, '19 Mon May 13, '19 149 151 TSS-SE,Client 151 3.4.2.1.4.4 OSD Approval 1 dayTue May 14, '19 Tue May 14, '19 150 152 Client 152 3.4.2.1.4.5 Interface Coding 4 wks Wed May 15, '19 Wed Jun 12, '19 151 153 TSS-Eng 153 3.4.2.1.4.6 Interface Installation and Initial Testing 5 daysTue Mar 10, '20 Tue Mar 17, '20 152,105 154 TSS-Eng 154 3.4.2.1.4.7 Interface testing with Vendor and Client 10 daysTue Mar 17, '20 Tue Mar 31, '20 153 155 TSS-Eng,Client 155 3.4.2.1.4.8 Interface Troubleshooting and Rework 10 daysTue Mar 31, '20 Tue Apr 14, '20 154 156 TSS-Eng 156 3.4.2.1.4.9 Interface FAT 5 daysTue Apr 14, '20 Tue Apr 21, '20 155 227 TSS-Eng,Client 157 3.4.2.1.5 Custom RMS Interface # 5 Fingerprint 262.5 days Tue Apr 9, '19 Tue Apr 21, '20 158 3.4.2.1.5.1 Requirement Analysis 5 days Tue Apr 9, '19 Mon Apr 15, '19 94FS+20 days 159 TSS-SE 159 3.4.2.1.5.2 OSD Development 15 daysTue Apr 16, '19 Mon May 6, '19 158 160 TSS-SE 160 3.4.2.1.5.3 OSD Review and Revision 5 daysTue May 7, '19 Mon May 13, '19 159 161 TSS-SE,Client 161 3.4.2.1.5.4 OSD Approval 1 dayTue May 14, '19 Tue May 14, '19 160 162 Client 162 3.4.2.1.5.5 Interface Coding 4 wks Wed May 15, '19 Wed Jun 12, '19 161 163 TSS-Eng 163 3.4.2.1.5.6 Interface Installation and Initial Testing 5 daysTue Mar 10, '20 Tue Mar 17, '20 162,105 164 TSS-Eng 164 3.4.2.1.5.7 Interface testing with Vendor and Client 10 daysTue Mar 17, '20 Tue Mar 31, '20 163 165 TSS-Eng,Client 165 3.4.2.1.5.8 Interface Troubleshooting and Rework 10 daysTue Mar 31, '20 Tue Apr 14, '20 164 166 TSS-Eng 166 3.4.2.1.5.9 Interface FAT 5 daysTue Apr 14, '20 Tue Apr 21, '20 165 227 TSS-Eng,Client 167 3.4.2.1.6 Custom RMS Interface # 6 In Car Video 262.5 days Tue Apr 9, '19 Tue Apr 21, '20 168 3.4.2.1.6.1 Requirement Analysis 5 days Tue Apr 9, '19 Mon Apr 15, '19 94FS+20 days 169 TSS-SE 169 3.4.2.1.6.2 OSD Development 15 daysTue Apr 16, '19 Mon May 6, '19 168 170 TSS-SE 170 3.4.2.1.6.3 OSD Review and Revision 5 daysTue May 7, '19 Mon May 13, '19 169 171 TSS-SE,Client 171 3.4.2.1.6.4 OSD Approval 1 dayTue May 14, '19 Tue May 14, '19 170 172 Client 172 3.4.2.1.6.5 Interface Coding 4 wks Wed May 15, '19 Wed Jun 12, '19 171 173 TSS-Eng 173 3.4.2.1.6.6 Interface Installation and Initial Testing 5 daysTue Mar 10, '20 Tue Mar 17, '20 172,105 174 TSS-Eng 174 3.4.2.1.6.7 Interface testing with Vendor and Client 10 daysTue Mar 17, '20 Tue Mar 31, '20 173 175 TSS-Eng,Client 175 3.4.2.1.6.8 Interface Troubleshooting and Rework 10 daysTue Mar 31, '20 Tue Apr 14, '20 174 176 TSS-Eng 176 3.4.2.1.6.9 Interface FAT 5 daysTue Apr 14, '20 Tue Apr 21, '20 175 227 TSS-Eng,Client 177 3.4.2.1.7 Custom RMS Interface # 7 CrossRoads 241.5 daysWed May 8, '19 Tue Apr 21, '20 178 3.4.2.1.7.1 Requirement Analysis 5 daysWed May 8, '19 Tue May 14, '19 121 179 TSS-SE 179 3.4.2.1.7.2 OSD Development 15 days Wed May 15, '19 Wed Jun 5, '19 178 180 TSS-SE 180 3.4.2.1.7.3 OSD Review and Revision 5 days Thu Jun 6, '19 Wed Jun 12, '19 179 181 TSS-SE,Client TSS-SE TSS-SE,Client ClientTSS-Eng TSS-Eng TSS-Eng,Client TSS-Eng TSS-Eng,Client TSS-SE TSS-SE TSS-SE,Client ClientTSS-Eng TSS-Eng TSS-Eng,Client TSS-Eng TSS-Eng,Client TSS-SE TSS-SE TSS-SE,Client ClientTSS-Eng TSS-Eng TSS-Eng,Client TSS-Eng TSS-Eng,Client TSS-SE TSS-SE TSS-SE,Client Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May 4th Quarter 1st Quarter 2nd Quarter 3rd Quarter 4th Quarter 1st Quarter 2nd Quarter 3rd Quarter 4th Quarter 1st Quarter 2nd Quarter Task Split Milestone
Summary Project Summary External Tasks External MilestoneInactive Task Inactive Milestone
Inactive Summary Manual Task Duration-only Manual Summary Rollup Manual Summary Start-only Finish-only Deadline Progress Manual Progress Page 6 Project: Glendale Date: Thu Jan 24, '19 Exhibit B - Sample Project Plan CentralSquare Technologies 6 of 14 #11..
- 737 -
ID WBS Task Name Duration Start Finish Predecessors Successors Resource Names 181 3.4.2.1.7.4 OSD Approval 1 dayThu Jun 13, '19 Thu Jun 13, '19 180 182 Client 182 3.4.2.1.7.5 Interface Coding 4 wks Fri Jun 14, '19Fri Jul 12, '19 181 183 TSS-Eng 183 3.4.2.1.7.6 Interface Installation and Initial Testing 5 daysTue Mar 10, '20 Tue Mar 17, '20 182,105 184 TSS-Eng 184 3.4.2.1.7.7 Interface testing with Vendor and Client 10 daysTue Mar 17, '20 Tue Mar 31, '20 183 185 TSS-Eng,Client 185 3.4.2.1.7.8 Interface Troubleshooting and Rework 10 daysTue Mar 31, '20 Tue Apr 14, '20 184 186 TSS-Eng 186 3.4.2.1.7.9 Interface FAT 5 daysTue Apr 14, '20 Tue Apr 21, '20 185 227 TSS-Eng,Client 187 3.4.2.1.8 Custom RMS Interface # 8 Vigilant 241.5 daysWed May 8, '19 Tue Apr 21, '20 188 3.4.2.1.8.1 Requirement Analysis 5 daysWed May 8, '19 Tue May 14, '19 121 189 TSS-SE 189 3.4.2.1.8.2 OSD Development 15 days Wed May 15, '19 Wed Jun 5, '19 188 190 TSS-SE 190 3.4.2.1.8.3 OSD Review and Revision 5 days Thu Jun 6, '19 Wed Jun 12, '19 189 191 TSS-SE,Client 191 3.4.2.1.8.4 OSD Approval 1 dayThu Jun 13, '19 Thu Jun 13, '19 190 192 Client 192 3.4.2.1.8.5 Interface Coding 4 wks Fri Jun 14, '19Fri Jul 12, '19 191 193 TSS-Eng 193 3.4.2.1.8.6 Interface Installation and Initial Testing 5 daysTue Mar 10, '20 Tue Mar 17, '20 192,105 194 TSS-Eng 194 3.4.2.1.8.7 Interface testing with Vendor and Client 10 daysTue Mar 17, '20 Tue Mar 31, '20 193 195 TSS-Eng,Client 195 3.4.2.1.8.8 Interface Troubleshooting and Rework 10 daysTue Mar 31, '20 Tue Apr 14, '20 194 196 TSS-Eng 196 3.4.2.1.8.9 Interface FAT 5 daysTue Apr 14, '20 Tue Apr 21, '20 195 227 TSS-Eng,Client 197 3.4.2.1.9 Custom RMS Interface # 9 Turbodata 241.5 daysWed May 8, '19 Tue Apr 21, '20 198 3.4.2.1.9.1 Requirement Analysis 5 daysWed May 8, '19 Tue May 14, '19 121 199 TSS-SE 199 3.4.2.1.9.2 OSD Development 15 days Wed May 15, '19 Wed Jun 5, '19 198 200 TSS-SE 200 3.4.2.1.9.3 OSD Review and Revision 5 days Thu Jun 6, '19 Wed Jun 12, '19 199 201 TSS-SE,Client 201 3.4.2.1.9.4 OSD Approval 1 dayThu Jun 13, '19 Thu Jun 13, '19 200 202 Client 202 3.4.2.1.9.5 Interface Coding 4 wks Fri Jun 14, '19Fri Jul 12, '19 201 203 TSS-Eng 203 3.4.2.1.9.6 Interface Installation and Initial Testing 5 daysTue Mar 10, '20 Tue Mar 17, '20 202,105 204 TSS-Eng 204 3.4.2.1.9.7 Interface testing with Vendor and Client 10 daysTue Mar 17, '20 Tue Mar 31, '20 203 205 TSS-Eng,Client 205 3.4.2.1.9.8 Interface Troubleshooting and Rework 10 daysTue Mar 31, '20 Tue Apr 14, '20 204 206 TSS-Eng 206 3.4.2.1.9.9 Interface FAT 5 daysTue Apr 14, '20 Tue Apr 21, '20 205 227 TSS-Eng,Client 207 3.4.2.1.10 Custom RMS Interface # 10 CSAR 241.5 days Wed May 8, '19
Tue Apr
21, '20
208 3.4.2.1.10.1 Requirement Analysis 5 daysWed May 8, '19 Tue May 14, '19 121 209 TSS-SE 209 3.4.2.1.10.2 OSD Development 15 days Wed May 15, '19 Wed Jun 5, '19 208 210 TSS-SE 210 3.4.2.1.10.3 OSD Review and Revision 5 days Thu Jun 6, '19 Wed Jun 12, '19 209 211 TSS-SE,Client 211 3.4.2.1.10.4 OSD Approval 1 dayThu Jun 13, '19 Thu Jun 13, '19 210 212 Client 212 3.4.2.1.10.5 Interface Coding 4 wks Fri Jun 14, '19Fri Jul 12, '19 211 213 TSS-Eng ClientTSS-Eng TSS-Eng TSS-Eng,Client TSS-Eng TSS-Eng,Client TSS-SE TSS-SE TSS-SE,Client ClientTSS-Eng TSS-Eng TSS-Eng,Client TSS-Eng TSS-Eng,Client TSS-SE TSS-SE TSS-SE,Client ClientTSS-Eng TSS-Eng TSS-Eng,Client TSS-Eng TSS-Eng,Client TSS-SE TSS-SE TSS-SE,Client ClientTSS-Eng Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May 4th Quarter 1st Quarter 2nd Quarter 3rd Quarter 4th Quarter 1st Quarter 2nd Quarter 3rd Quarter 4th Quarter 1st Quarter 2nd Quarter Task Split Milestone
Summary Project Summary External Tasks External MilestoneInactive Task Inactive Milestone
Inactive Summary Manual Task Duration-only Manual Summary Rollup Manual Summary Start-only Finish-only Deadline Progress Manual Progress Page 7 Project: Glendale Date: Thu Jan 24, '19 Exhibit B - Sample Project Plan CentralSquare Technologies 7 of 14 #11..
- 738 -
ID WBS Task Name Duration Start Finish Predecessors Successors Resource Names 213 3.4.2.1.10.6 Interface Installation and Initial Testing 5 daysTue Mar 10, '20 Tue Mar 17, '20 212,105 214 TSS-Eng 214 3.4.2.1.10.7 Interface testing with Vendor and Client 10 daysTue Mar 17, '20 Tue Mar 31, '20 213 215 TSS-Eng,Client 215 3.4.2.1.10.8 Interface Troubleshooting and Rework 10 daysTue Mar 31, '20 Tue Apr 14, '20 214 216 TSS-Eng 216 3.4.2.1.10.9 Interface FAT 5 daysTue Apr 14, '20 Tue Apr 21, '20 215 227 TSS-Eng,Client 217 3.4.2.1.11 Custom RMS Interface # 11 Coplink 241.5 daysWed May 8, '19 Tue Apr 21, '20 218 3.4.2.1.11.1 Requirement Analysis 5 daysWed May 8, '19 Tue May 14, '19 121 219 TSS-SE 219 3.4.2.1.11.2 OSD Development 15 days Wed May 15, '19 Wed Jun 5, '19 218 220 TSS-SE 220 3.4.2.1.11.3 OSD Review and Revision 5 days Thu Jun 6, '19 Wed Jun 12, '19 219 221 TSS-SE,Client 221 3.4.2.1.11.4 OSD Approval 1 dayThu Jun 13, '19 Thu Jun 13, '19 220 222 Client 222 3.4.2.1.11.5 Interface Coding 4 wks Fri Jun 14, '19Fri Jul 12, '19 221 223 TSS-Eng 223 3.4.2.1.11.6 Interface Installation and Initial Testing 5 daysTue Mar 10, '20 Tue Mar 17, '20 222,105 224 TSS-Eng 224 3.4.2.1.11.7 Interface testing with Vendor and Client 10 daysTue Mar 17, '20 Tue Mar 31, '20 223 225 TSS-Eng,Client 225 3.4.2.1.11.8 Interface Troubleshooting and Rework 10 daysTue Mar 31, '20 Tue Apr 14, '20 224 226 TSS-Eng 226 3.4.2.1.11.9 Interface FAT 5 daysTue Apr 14, '20 Tue Apr 21, '20 225 227 TSS-Eng,Client 227 3.4.3 RMS Interfaces - System Integration Ready 0 daysTue Apr 21, '20 Tue Apr 21, '20 136,126,226,216,206,196,186,176,166,156,146 255 228 3.4.4 Law RMS Legacy Data Conversion (LDC) 313.5 daysTue Mar 12, '19Thu Jun 4, '20 229 3.4.4.1 LDC RMS - Provide Legacy Data to TriTech 10 daysTue Mar 12, '19 Mon Mar 25, '19 94 230 Client 230 3.4.4.2 LDC RMS - Data Analysis and Review 20 daysTue Mar 26, '19 Mon Apr 22, '19 229 231 TSS-Eng 231 3.4.4.3 LDC RMS - Define Data Mapping 20 daysTue Apr 23, '19 Mon May 20, '19 230 232 TSS-Eng,Client 232 3.4.4.4 LDC RMS - Develop Data Conversion Plan 40 daysTue May 21, '19 Wed Jul 17, '19 231 233 TSS-Eng 233 3.4.4.5 LDC RMS - Perform Conversion on a sample set 5 daysTue Mar 10, '20 Tue Mar 17, '20 232,105 234 TSS-Eng 234 3.4.4.6 LDC RMS - Perform Data Validation 10 daysTue Mar 17, '20 Tue Mar 31, '20 233 235 Client 235 3.4.4.7 LDC RMS - Update Data Conversion Plan and test 20 daysTue Mar 31, '20 Tue Apr 28, '20 234 236 TSS-Eng 236 3.4.4.8 LDC RMS - Perform Final Legacy RMS Data Conversion 2 days Tue Jun 2, '20Thu Jun 4, '20 235,266SF 237 TSS-Eng 237 3.4.4.9 LDC RMS - Data Conversion Complete 0 days Thu Jun 4, '20Thu Jun 4, '20 236 238 3.5 IQ 392.5 daysWed Jan 2, '19 Mon Jul 20, '20
239 3.5.1 CrimeView 392.5 daysWed Jan 2, '19 Mon Jul 20, '20 240 3.5.1.1 IQ-CV - Requirement Analysis 4 daysTue Mar 10, '20 Mon Mar 16, '20 44,105 241 TSS-CV 241 3.5.1.2 IQ-CV - Collection of Prerequisites 15 daysMon Mar 16, '20 Mon Apr 6, '20 240 242 TSS-CV[25%],Client[75%] 242 3.5.1.3 IQ-CV - ETL Software Install and Configuration 25 daysMon Apr 6, '20 Mon May 11, '20 241,17 244,243 TSS-CV 243 3.5.1.4 IQ-CV - Crimemapping Configuration and Deployment 10 days Mon May 11, '20 Tue May 26, '20 242 TSS-CV,Client[10%] 244 3.5.1.5 IQ-CV - CrimeView Dashboard Configuration 10 days Mon May 11, '20 Tue May 26, '20 242 245 TSS-CV TSS-Eng TSS-Eng,Client TSS-Eng TSS-Eng,Client TSS-SE TSS-SE TSS-SE,Client ClientTSS-Eng TSS-Eng TSS-Eng,Client TSS-Eng TSS-Eng,Client 4/21 ClientTSS-Eng TSS-Eng,Client TSS-Eng TSS-Eng ClientTSS-EngTSS-Eng 6/4 TSS-CV
TSS-CV[25%],Client[75%] TSS-CV
TSS-CV,Client[10%] TSS-CV
Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May 4th Quarter 1st Quarter 2nd Quarter 3rd Quarter 4th Quarter 1st Quarter 2nd Quarter 3rd Quarter 4th Quarter 1st Quarter 2nd Quarter Task Split Milestone
Summary Project Summary External Tasks External MilestoneInactive Task Inactive Milestone
Inactive Summary Manual Task Duration-only Manual Summary Rollup Manual Summary Start-only Finish-only Deadline Progress Manual Progress Page 8 Project: Glendale Date: Thu Jan 24, '19 Exhibit B - Sample Project Plan CentralSquare Technologies 8 of 14 #11..
- 739 -
ID WBS Task Name Duration Start Finish Predecessors Successors Resource Names 245 3.5.1.6 IQ-CV - Dashboard Testing Install & Initial Demo 7 daysTue May 26, '20Thu Jun 4, '20 244 246 TSS-CV,Client[5%] 246 3.5.1.7 IQ-CV - Dashboard Production Install 5 days Thu Jun 4, '20 Thu Jun 11, '20 245 247 TSS-CV 247 3.5.1.8 IQ-CV - Dashboard Content Development 5 daysThu Jun 11, '20 Thu Jun 18, '20 246 248 TSS-CV 248 3.5.1.9 IQ-CV - Admin training (remote) 1 dayThu Jun 18, '20Fri Jun 19, '20 247 249 249 3.5.1.10 IQ-CV - Dashboard Administrator & Designer Training 2 days Fri Jun 19, '20 Tue Jun 23, '20 248 250 TSS-CV[25%],Client[25%] 250 3.5.1.11 IQ-CV - Dashboard Revisions and Content Building 15 daysTue Jun 23, '20 Wed Jul 15, '20 249 251 Client,TSS-CV[50%] 251 3.5.1.12 IQ-CV - Dashboard End User Training (remote) 3 daysWed Jul 15, '20 Mon Jul 20, '20 250 Client[33%],TSS-CV 252 3.5.1.13 IQ-CV - Final Application Testing/Review 15 daysWed Jan 2, '19 Tue Jan 22, '19 384 TSS-CV[10%],Client[90%] 253 3.6 System Integration Testing 74.5 days Thu Jan 9, '20 Thu Apr 23, '20 254 3.6.1 CAD/MBL - System Integration Testing 1 day Thu Jan 9, '20Thu Jan 9, '20 50,62,91 261 255 3.6.2 CAD/MBL/RMS - System Integration Testing 2 daysTue Apr 21, '20 Thu Apr 23, '20 50,62,108,91,227 266 256 3.7 Go - Live 46 days Fri Apr 3, '20Tue Jun 9, '20
257 3.7.1 CAD/MBL - Go Live Assessment/Authorization to Proceed 3 days Fri Apr 3, '20 Wed Apr 8, '20 261SF-40 days 258 3.7.2 CAD/MBL - Pre Go Live System Checks 5 days Wed May 13, '20 Wed May 20, '20 259SF 259 3.7.3 CAD/MBL - System Lock Down 10 days Wed May 20, '20Thu Jun 4, '20 261SF 258SF 260 3.7.4 CAD/MBL - Pre Go Live Activities 1 dayWed Jun 3, '20Thu Jun 4, '20 261SF 261 3.7.5 CAD/Mbl - Go Live 3 days Thu Jun 4, '20Tue Jun 9, '20 56,63,254,266SS 382FS+20 days,260SF,259SF,257SF-40 days,41FS+20 days,52FS+30 days 262 3.7.6 RMS - Go Live Assessment/Authorization to Proceed 3 days Fri Apr 3, '20 Wed Apr 8, '20 266SF-40 days 263 3.7.7 RMS - Pre Go Live System Checks 5 daysFri May 22, '20 Mon Jun 1, '20 264SF 264 3.7.8 RMS - System Lock Down 3 daysMon Jun 1, '20Thu Jun 4, '20 266SF 263SF 265 3.7.9 RMS - Pre Go Live Activities 1 dayWed Jun 3, '20Thu Jun 4, '20 266SF 266 3.7.10 RMS - Go Live 2 days Thu Jun 4, '20 Mon Jun 8, '20 114,255 383FS+20 days,265SF,264SF,262SF-40 days,236SF,261SS 267 3.8 Inform Jail 6 349 daysWed Jan 30, '19 Mon Jun 15, '20 268 3.8.1 Inform Jail Implementation 349 daysWed Jan 30, '19 Mon Jun 15, '20 269 3.8.1.1 Agency Kickoff Meeting 7 daysWed Jan 30, '19 Thu Feb 7, '19 270 3.8.1.1.1 Schedule Kickoff Meeting 1 dayWed Jan 30, '19 Wed Jan 30, '19 2 272,271 TSS-PM 271 3.8.1.1.2 Coordinate Appropriate Personnel at Kickoff Meeting 1 dayThu Jan 31, '19 Thu Jan 31, '19 270 272 Client,TSS-PM 272 3.8.1.1.3 Create Kickoff Presentation 4 days Fri Feb 1, '19 Wed Feb 6, '19 270,271 273,274FS+30 daysTSS-PM 273 3.8.1.1.4 Attend Kickoff Meeting (online meeting) 1 day Thu Feb 7, '19Thu Feb 7, '19 272 275 Client,TSS-BA Jail,TSS-PM 274 3.8.1.2 Post-Kick off Meeting Tasks 2 daysFri Mar 22, '19 Mon Mar 25, '19 272FS+30 days 275 3.8.1.2.1 Client provides image files and info for login screen 1 dayFri Mar 22, '19 Fri Mar 22, '19 273 276 Client 276 3.8.1.2.2 Client schedules meeting with third party vendors for interface discussions 1 day Mon Mar 25, '19 Mon Mar 25, '19
275 279 Client,TSS-PM
TSS-CV,Client[5%] TSS-CV
TSS-CV
TSS-CV[25%],Client[25%] Client,TSS-CV[50%] Client[33%],TSS-CV TSS-CV[10%],Client[90%]
TSS-PM
Client,TSS-PM
TSS-PM
Client,TSS-BA Jail,TSS-PM
Client Client,TSS-PM
Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May 4th Quarter 1st Quarter 2nd Quarter 3rd Quarter 4th Quarter 1st Quarter 2nd Quarter 3rd Quarter 4th Quarter 1st Quarter 2nd Quarter Task Split Milestone
Summary Project Summary External Tasks External MilestoneInactive Task Inactive Milestone
Inactive Summary Manual Task Duration-only Manual Summary Rollup Manual Summary Start-only Finish-only Deadline Progress Manual Progress Page 9 Project: Glendale Date: Thu Jan 24, '19 Exhibit B - Sample Project Plan CentralSquare Technologies 9 of 14 #11..
- 740 -
ID WBS Task Name Duration Start Finish Predecessors Successors Resource Names 277 3.8.1.3 Infrastructure 311 daysTue Mar 26, '19 Mon Jun 15, '20 278 3.8.1.3.1 Complete Infrastructure Documents 8 daysTue Mar 26, '19 Thu Apr 4, '19 279 3.8.1.3.1.1 Size and Spec Servers 1 dayTue Mar 26, '19 Tue Mar 26, '19 276 280 Client,TSS-PM 280 3.8.1.3.1.2 Send Network Requirement Specification Document to Client 1 day Wed Mar 27, '19 Wed Mar 27, '19
279 281,282 TSS-PM
281 3.8.1.3.1.3 Send Server Requirement Specifications Document to Client 1 day Thu Mar 28, '19
Thu Mar 28, '19280 283,285 TSS-PM
282 3.8.1.3.1.4 Complete, Sign, and Return the Network
Requirements Specifications Document
5 days Thu Mar 28,
'19 Wed Apr3, '19
280 296 Client,TSS-PM
283 3.8.1.3.1.5 Complete, Sign, and Return the Server
Requirements Specifications Document
5 days Fri Mar 29,
'19
Thu Apr 4,
'19
281 319 Client,TSS-PM
284 3.8.1.3.2 Procurement 22 daysFri Mar 29, '19 Mon Apr 29, '19 285 3.8.1.3.2.1 Order Servers 1 dayFri Mar 29, '19 Fri Mar 29, '19 281 286,303 TSS-PM 286 3.8.1.3.2.2 Build and Ship Servers 20 daysMon Apr 1, '19Fri Apr 26, '19 285 287 HDW-Sub-contractor 287 3.8.1.3.2.3 Receive Servers 1 dayMon Apr 29, '19 Mon Apr 29, '19 286 289,290,340 TSS-CIS 288 3.8.1.3.3 Server Configuration 8 daysTue Apr 30, '19 Thu May 9, '19 289 3.8.1.3.3.1 Review the Completed and Signed Server
Requirement Specificaitons
1 day Tue Apr 30,
'19
Tue Apr
30, '19
287 TSS-CIS 290 3.8.1.3.3.2 Review the Completed and Signed Network Requirement Specifications
1 day Tue Apr 30,
'19
Tue Apr
30, '19
287 291 TSS-CIS 291 3.8.1.3.3.3 Compelte Server Configuration 2 daysWed May 1, '19 Thu May 2, '19 290 292 TSS-CIS 292 3.8.1.3.3.4 Install Network Configuration 2 days Fri May 3, '19 Mon May 6, '19 291 293 TSS-CIS 293 3.8.1.3.3.5 Install Software Configuration 2 daysTue May 7, '19 Wed May 8, '19 292 294 TSS-CIS 294 3.8.1.3.3.6 Ship Servers to Client 1 dayThu May 9, '19 Thu May 9, '19 293 297FS+5 days 295 3.8.1.3.4 Installation 39 days Thu Apr 4, '19 Wed May 29, '19 296 3.8.1.3.4.1 Configure Network per Netwrok Requirement Specificaiton Document
2 days Thu Apr 4, '19 Fri Apr 5,
'19
282 Client 297 3.8.1.3.4.2 Install Servers 2 daysFri May 17, '19 Mon May 20, '19 294FS+5 days 298SS,299 Client 298 3.8.1.3.4.3 Install Gizmo Device 2 daysFri May 17, '19 Mon May 20, '19 297SS 299 Client 299 3.8.1.3.4.4 Post Server Installation Configuration and Security Audit
2 days Tue May 21,
'19 Wed May22, '19
297,298 300 Client,TSS-CIS 300 3.8.1.3.4.5 Ensure Connectivity to Inform Jail 6 Server 2 daysThu May 23, '19 Fri May 24, '19 299 301 TSS-CIS Client,TSS-PM
TSS-PM
TSS-PM
Client,TSS-PM
Client,TSS-PM
TSS-PM
HDW-Sub-contractor TSS-CIS TSS-CIS TSS-CIS TSS-CIS TSS-CIS TSS-CIS Client Client Client Client,TSS-CIS TSS-CIS Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May 4th Quarter 1st Quarter 2nd Quarter 3rd Quarter 4th Quarter 1st Quarter 2nd Quarter 3rd Quarter 4th Quarter 1st Quarter 2nd Quarter Task Split Milestone
Summary Project Summary External Tasks External MilestoneInactive Task Inactive Milestone
Inactive Summary Manual Task Duration-only Manual Summary Rollup Manual Summary Start-only Finish-only Deadline Progress Manual Progress Page 10 Project: Glendale Date: Thu Jan 24, '19 Exhibit B - Sample Project Plan CentralSquare Technologies 10 of 14 #11..
- 741 -
ID WBS Task Name Duration Start Finish Predecessors Successors Resource Names 301 3.8.1.3.4.6 Install Inform Jail 6 Client on Client's Project Team Computers
2 days Tue May 28,
'19 Wed May29, '19
300 Client 302 3.8.1.3.5 Configuration 307 daysMon Apr 1, '19 Mon Jun 15, '20 303 3.8.1.3.5.1 Create the Client Configuration Guide 2 daysMon Apr 1, '19Tue Apr 2, '19 285 306,307 TSS-BA Jail,TSS-PM 304 3.8.1.3.5.2 Complete Module Configuration 207 daysWed Apr 3, '19 Mon Jan 27, '20 305 3.8.1.3.5.2.1 Jail 116 daysWed Apr 3, '19 Mon Sep 16, '19 306 3.8.1.3.5.2.1.1 Send Configuration Manual to Client 1 dayWed Apr 3, '19 Wed Apr 3, '19 303 TSS-PM 307 3.8.1.3.5.2.1.2 Schedule Meeting to Complete
Configuration Changes with Client
1 day Wed Apr 3,
'19 Wed Apr3, '19
303 308FS+20 days TSS-PM,TSS-BA Jail 308 3.8.1.3.5.2.1.3 Lead and Assist with Completion of Configuraiton Changes to Client
15 days Thu May 2,
'19 Wed May22, '19
307FS+20 days 309FS+5 days Client,TSS-BA Jail 309 3.8.1.3.5.2.1.4 Complete Configuration Tasks 15 daysFri May 31, '19 Thu Jun 20, '19 308FS+5 days 310 Client 310 3.8.1.3.5.2.1.5 Conduct Testing of Module 20 days Fri Jun 21, '19Fri Jul 19, '19 309 311FS+30 days,352Client 311 3.8.1.3.5.2.1.6 Installation and testing of peripheral 10 days Tue Sep 3, '19 Mon Sep 16, '19 310FS+30 days 313FS+15 days,320Client 312 3.8.1.3.5.2.2 Reporting Module 76 days Tue Oct 8, '19 Mon Jan 27, '20 313 3.8.1.3.5.2.2.1 Send Configuraiton Manual to Client 1 day Tue Oct 8, '19Tue Oct 8, '19 311FS+15 days 314SS TSS-BA Jail 314 3.8.1.3.5.2.2.2 Schedule Meeting to Complete Configuration Changes with Client
1 day Tue Oct 8, '19 Tue Oct 8,
'19
313SS 315FS+15 days TSS-BA Jail,TSS-PM
315 3.8.1.3.5.2.2.3 Lead and Assist with Completion of
Configuraiton Changes to Client
20 days Wed Oct 30,
'19
Tue Nov 26, '19314FS+15 days 316FS+5 days Client,TSS-BA Jail 316 3.8.1.3.5.2.2.4 Complete Configuration Tasks 15 days Fri Dec 6, '19 Fri Dec 27, '19 315FS+5 days 317 Client 317 3.8.1.3.5.2.2.5 Conduct Testing of Module 20 daysMon Dec 30, '19 Mon Jan 27, '20 316 Client 318 3.8.1.3.5.3 Business Practice Review 303 days Fri Apr 5, '19 Mon Jun 15, '20 319 3.8.1.3.5.3.1 Schedule Business Practice Reviews (BPR) 1 day Fri Apr 5, '19 Fri Apr 5, '19
283 Client,TSS-PM
320 3.8.1.3.5.3.2 Create Business Practice Review (BPR) Agency Document 1 day Tue Sep 17, '19
Tue Sep
17, '19
311 322 TSS-PM
321 3.8.1.3.5.3.3 BPR 12 daysWed Sep 18, '19Thu Oct 3, '19 322 3.8.1.3.5.3.3.1 Provide Initial Inform Jail 6 Overview 1 dayWed Sep 18, '19 Wed Sep 18, '19 320 323,324 Client,TSS-BA Jail 323 3.8.1.3.5.3.3.2 Discuss and Set Appropriate Inform Jail 6 Global Settings
1 day Thu Sep 19,
'19
Thu Sep
19, '19
322 Client,TSS-BA Jail 324 3.8.1.3.5.3.3.3 Jail module review 1 dayThu Sep 19, '19 Thu Sep 19, '19 322 325,326,328,330,331,333,335 Client,TSS-BA Jail 325 3.8.1.3.5.3.3.4 Reporting module review 1 day Fri Sep 20, '19Fri Sep 20, '19 324 Client,TSS-BA Jail Client TSS-BA Jail,TSS-PM
TSS-PM
TSS-PM,TSS-BA Jail Client,TSS-BA Jail ClientClient Client TSS-BA Jail TSS-BA Jail,TSS-PM Client,TSS-BA Jail ClientClient Client,TSS-PM
TSS-PM
Client,TSS-BA Jail Client,TSS-BA Jail Client,TSS-BA Jail Client,TSS-BA Jail Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May 4th Quarter 1st Quarter 2nd Quarter 3rd Quarter 4th Quarter 1st Quarter 2nd Quarter 3rd Quarter 4th Quarter 1st Quarter 2nd Quarter Task Split Milestone
Summary Project Summary External Tasks External MilestoneInactive Task Inactive Milestone
Inactive Summary Manual Task Duration-only Manual Summary Rollup Manual Summary Start-only Finish-only Deadline Progress Manual Progress Page 11 Project: Glendale Date: Thu Jan 24, '19 Exhibit B - Sample Project Plan CentralSquare Technologies 11 of 14 #11..
- 742 -
ID WBS Task Name Duration Start Finish Predecessors Successors Resource Names 326 3.8.1.3.5.3.3.5 Crime Reporting Review 1 day Fri Sep 20, '19Fri Sep 20, '19 324 Client,TSS-BA Jail 327 3.8.1.3.5.3.3.6 Review Interface Specifications 1 day Fri Sep 20, '19 Fri Sep 20, '19 328 3.8.1.3.5.3.3.6.1 Review Client Interfaces Specifications 1 day Fri Sep 20, '19Fri Sep 20, '19 324 Client,TSS-BA Jail 329 3.8.1.3.5.3.3.7 Discuss Inform Jail 6 Module Configuration 1 day Fri Sep 20, '19 Fri Sep 20, '19 330 3.8.1.3.5.3.3.7.1 Review Inform Jail 6 modules that are configured 1 day Fri Sep 20, '19 Fri Sep 20,
'19
324 Client,TSS-BA Jail 331 3.8.1.3.5.3.3.7.2 Review Inform Jail 6 modules that need to be configured 1 day Fri Sep 20, '19 Fri Sep 20,
'19
324 Client,TSS-BA Jail 332 3.8.1.3.5.3.3.8 Discuss Training Formats and Needs 1 day Fri Sep 20, '19 Fri Sep 20, '19 333 3.8.1.3.5.3.3.8.1 Review the Training Requirement and Specificaiton Documents
1 day Fri Sep 20, '19 Fri Sep 20,
'19
324 Client,TSS-PM
334 3.8.1.3.5.3.3.9 Post BPR 10 days Fri Sep 20, '19Thu Oct 3, '19 335 3.8.1.3.5.3.3.9.1 Confirm Project Timeline 2 days Fri Sep 20, '19 Mon Sep 23, '19 324 336,337 Client,TSS-PM 336 3.8.1.3.5.3.3.9.2 Create Configuration Management
Document (CMD)
1 day Tue Sep 24,
'19
Tue Sep
24, '19
335 TSS-PM
337 3.8.1.3.5.3.3.9.3 Send CMD 1 dayTue Sep 24, '19 Tue Sep 24, '19 335 338FS+5 days TSS-PM 338 3.8.1.3.5.3.3.9.4 Review and Sign CMD 2 daysWed Oct 2, '19Thu Oct 3, '19 337FS+5 days 351,367 Client 339 3.8.1.3.5.3.4 Interfaces 245 daysTue Apr 30, '19 Thu Apr 16, '20 340 3.8.1.3.5.3.4.1 Write Interface Specification Documents 40 daysTue Apr 30, '19 Tue Jun 25, '19 287 341FS+20 days TSS-SE 341 3.8.1.3.5.3.4.2 Develop Interfaces 80 days Thu Jul 25, '19 Thu Nov 14, '19 340FS+20 days 342FS+20 days TSS-SE 342 3.8.1.3.5.3.4.3 Test Interfaces - TriTech 20 daysTue Dec 17, '19 Wed Jan 15, '20 341FS+20 days 343FS+10 days TSS-SE 343 3.8.1.3.5.3.4.4 Test Interfaces - Client 20 daysThu Jan 30, '20 Thu Feb 27, '20 342FS+10 days 344FS+10 days Client 344 3.8.1.3.5.3.4.5 Provide Testing Feedback to TriTech 10 daysFri Mar 13, '20 Thu Mar 26, '20 343FS+10 days 345FS+10 days Client 345 3.8.1.3.5.3.4.6 Final Interface Testing 5 days Fri Apr 10, '20 Thu Apr 16, '20 344FS+10 days 347 TSS-SE 346 3.8.1.3.5.3.5 System Review 41 days Fri Apr 17, '20 Mon Jun 15, '20 347 3.8.1.3.5.3.5.1 Designate System Review Team 1 day Fri Apr 17, '20Fri Apr 17, '20 345 348FS+15 days Client,TSS-PM 348 3.8.1.3.5.3.5.2 Baseline Project Schedule 10 days Mon May 11, '20 Fri May 22, '20 347FS+15 days 349 Client,TSS-BA Jail 349 3.8.1.3.5.3.5.3 Jail 15 daysTue May 26, '20 Mon Jun 15, '20 348 Client,TSS-BA Jail 350 3.8.1.3.5.3.6 Training 55 daysMon Jul 22, '19 Mon Oct 7, '19 351 3.8.1.3.5.3.6.1 Schedule Training 2 days Fri Oct 4, '19 Mon Oct 7, '19 338 Client,TSS-PM 352 3.8.1.3.5.3.6.2 Create Training Agenda 1 dayMon Jul 22, '19 Mon Jul 22, '19 310 353 TSS-PM 353 3.8.1.3.5.3.6.3 Review Training Agenda 1 day Tue Jul 23, '19 Tue Jul 23, '19 352 354 Client 354 3.8.1.3.5.3.6.4 Create Training Dcoumentation 1 dayWed Jul 24, '19 Wed Jul 24, '19 353 355,364SS TSS-PM Client,TSS-BA Jail Client,TSS-BA Jail Client,TSS-BA Jail Client,TSS-BA Jail Client,TSS-PM Client,TSS-PM
TSS-PM
TSS-PM
Client TSS-SE TSS-SE TSS-SE ClientClient TSS-SE Client,TSS-PM Client,TSS-BA Jail Client,TSS-BA Jail Client,TSS-PM
TSS-PM
Client TSS-PM
Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May 4th Quarter 1st Quarter 2nd Quarter 3rd Quarter 4th Quarter 1st Quarter 2nd Quarter 3rd Quarter 4th Quarter 1st Quarter 2nd Quarter Task Split Milestone
Summary Project Summary External Tasks External MilestoneInactive Task Inactive Milestone
Inactive Summary Manual Task Duration-only Manual Summary Rollup Manual Summary Start-only Finish-only Deadline Progress Manual Progress Page 12 Project: Glendale Date: Thu Jan 24, '19 Exhibit B - Sample Project Plan CentralSquare Technologies 12 of 14 #11..
- 743 -
ID WBS Task Name Duration Start Finish Predecessors Successors Resource Names 355 3.8.1.3.5.3.6.5 Provide Client specific scenarios for training 1 day Thu Jul 25, '19 Thu Jul 25, '19
354 357 Client 356 3.8.1.3.5.3.6.6 Prepare Client Training Location 3 days Fri Jul 26, '19 Tue Jul 30, '19 357 3.8.1.3.5.3.6.6.1 Setup 10 workstations 1 day Fri Jul 26, '19Fri Jul 26, '19 355 358 Client 358 3.8.1.3.5.3.6.6.2 Install Inform Jail 6 Training Environment 1 dayMon Jul 29, '19 Mon Jul 29, '19 357 359 Client 359 3.8.1.3.5.3.6.6.3 Setup Projector and Screen 1 day Tue Jul 30, '19 Tue Jul 30, '19 358 363 Client 360 3.8.1.3.5.3.6.7 Conduct Training 15 daysWed Jul 31, '19 Tue Aug 20, '19 361 3.8.1.3.5.3.6.7.1 Training 15 daysWed Jul 31, '19 Tue Aug 20, '19 362 3.8.1.3.5.3.6.7.1.1 Jail Training 15 daysWed Jul 31, '19 Tue Aug 20, '19 363 3.8.1.3.5.3.6.7.1.1.1 Conduct Scenario Based Training 15 daysWed Jul 31, '19 Tue Aug 20, '19 359 365,368 TSS-BA Jail 364 3.8.1.3.5.3.6.8 Create Training Verification Dcoument 1 dayWed Jul 24, '19 Wed Jul 24, '19 354SS TSS-PM 365 3.8.1.3.5.3.6.9 Sign and Return Training Verification Dcoument 1 day Wed Aug 21, '19 Wed Aug21, '19
363 Client 366 3.8.1.3.5.4 Go Live with Inform Jail 6 34 daysWed Aug 21, '19Tue Oct 8, '19 367 3.8.1.3.5.4.1 Schedule Go Live 1 day Fri Oct 4, '19Fri Oct 4, '19 338 Client,TSS-PM 368 3.8.1.3.5.4.2 Identify Go Live Timeline & Team 1 dayWed Aug 21, '19 Wed Aug 21, '19 363 369FS+5 days Client,TSS-PM 369 3.8.1.3.5.4.3 Create Go Live Verification Signoff Documentation 1 day Thu Aug 29,
'19
Thu Aug
29, '19
368FS+5 days 370FS+5 days TSS-PM
370 3.8.1.3.5.4.4 Review and Sign Go Live Verification Document 1 day Mon Sep 9, '19 Mon Sep9, '19
369FS+5 days 371FS+15 days Client 371 3.8.1.3.5.4.5 TriTech Go Live Team Onsite 1 day Tue Oct 1, '19Tue Oct 1, '19 370FS+15 days 372,373,374,375FS+4 days Client,TSS-BA Jail,TSS-PM 372 3.8.1.3.5.4.6 Complete Interface Implementation 1 dayWed Oct 2, '19 Wed Oct 2, '19 371 Client,TSS-BA Jail,TSS-PM 373 3.8.1.3.5.4.7 Begin using Inform Jail 6 Produciton 1 dayWed Oct 2, '19 Wed Oct 2, '19 371 Client 374 3.8.1.3.5.4.8 Schedule Support Transition 1 dayWed Oct 2, '19 Wed Oct 2, '19 371 Client,TSS-BA Jail,TSS-PM 375 3.8.1.3.5.4.9 Attend Support Transition 1 day Tue Oct 8, '19Tue Oct 8, '19 371FS+4 days 385SS Client,TSS-BA Jail,TSS-PM 376 4 Phase IV - Controlling and Monitoring 1 day Wed Jul 8, '20Thu Jul 9, '20 377 4.1 Control and Monitor Project Activities 1 day Wed Jul 8, '20Thu Jul 9, '20 1SS,386FF TSS-PM 378 4.2 Process TCRs 1 day Wed Jul 8, '20Thu Jul 9, '20 1SS,386FF TSS-PM[0%] 379 4.3 Produce Project Reports 1 day Wed Jul 8, '20Thu Jul 9, '20 1SS,386FF TSS-PM[0%] 380 5 Phase V - Closure 370.5 daysWed Jan 23, '19Thu Jul 9, '20 381 5.1 Hand Off to Support 370.5 daysWed Jan 23, '19Thu Jul 9, '20 386 382 5.1.1 CAD/MBL - Hand Off to Support 1 day Wed Jul 8, '20Thu Jul 9, '20 261FS+20 days Client,TSS-PM,TSS-CAM,TSS-TSG,TSS-BA CAD,TSS-BA MBL,TSS-SE 383 5.1.2 RMS - Hand Off to Support 1 day Tue Jul 7, '20Wed Jul 8, '20 266FS+20 days Client,TSS-PM,TSS-CAM,TSS-TSG,TSS-BA RMS,TSS-SE Client Client Client Client TSS-BA Jail TSS-PM
Client Client,TSS-PM
Client,TSS-PM
TSS-PM
Client Client,TSS-BA Jail,TSS-PM
Client,TSS-BA Jail,TSS-PM
Client Client,TSS-BA Jail,TSS-PM
Client,TSS-BA Jail,TSS-PM
TSS-PM
TSS-PM[0%] TSS-PM[0%] Client,TSS-PM,TSS-CAM,TSS-TSG,TSS-BA CAD,TSS-BA MBL,TSS-SE Client,TSS-PM,TSS-CAM,TSS-TSG,TSS-BA RMS,TSS-SE Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May 4th Quarter 1st Quarter 2nd Quarter 3rd Quarter 4th Quarter 1st Quarter 2nd Quarter 3rd Quarter 4th Quarter 1st Quarter 2nd Quarter Task Split Milestone
Summary Project Summary External Tasks External MilestoneInactive Task Inactive Milestone
Inactive Summary Manual Task Duration-only Manual Summary Rollup Manual Summary Start-only Finish-only Deadline Progress Manual Progress Page 13 Project: Glendale Date: Thu Jan 24, '19 Exhibit B - Sample Project Plan CentralSquare Technologies 13 of 14 #11..
- 744 -
ID WBS Task Name Duration Start Finish Predecessors Successors Resource Names 384 5.1.3 IQ-SRCH - Hand Off to Support 1 dayWed Jan 23, '19 Wed Jan 23, '19 252 Client,TSS-PM,TSS-CAM,TSS-TSG,TSS-BA FBR 385 5.1.4 Jail - Hand Off to Support 1 day Tue Oct 8, '19Tue Oct 8, '19 375SS Client,TSS-PM,TSS-CAM,TSS-TSG,TSS-BA Jail 386 5.2 Phase IV Closure Complete 0 days Thu Jul 9, '20Thu Jul 9, '20 381 377FF,378FF,379FFTSS-BA CAD,TSS-BA MBL,TSS-SE Client,TSS-PM,TSS-CAM,TSS-TSG,TSS-BA FBR Client,TSS-PM,TSS-CAM,TSS-TSG,TSS-BA Jail 7/9 Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May 4th Quarter 1st Quarter 2nd Quarter 3rd Quarter 4th Quarter 1st Quarter 2nd Quarter 3rd Quarter 4th Quarter 1st Quarter 2nd Quarter Task Split Milestone
Summary Project Summary External Tasks External MilestoneInactive Task Inactive Milestone
Inactive Summary Manual Task Duration-only Manual Summary Rollup Manual Summary Start-only Finish-only Deadline Progress Manual Progress Page 14 Project: Glendale Date: Thu Jan 24, '19 Exhibit B - Sample Project Plan CentralSquare Technologies 14 of 14 #11..
- 745 -
TriTech Software Systems
9477 Waples Street, Suite 100
San Diego, CA 92121
Fax: 858.799.1010
Customer Services: 1.800.987.0911
STATEMENT OF WORK
Glendale Police Department
Inform CAD, Inform Mobile, Inform
RMS, and Inform Jail
Version 1
#11..
- 746 -
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2017 TriTech Software Systems
ii
© 2003-2018 TriTech Software Systems
Unpublished: Rights reserved under the copyright laws of the United States.
All information in this document is proprietary and confidential and owned by TriTech Software Systems™.
No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of TriTech Software Systems.
Trademarks
Microsoft, Windows, Microsoft Access, Microsoft Excel, Microsoft Exchange, and Microsoft Word are either registered trademarks or trademarks of Microsoft Corporation in the United States and other countries.
Inform CAD, Inform Mobile, Inform CAD Browser, Inform RMS, Inform Jail, IQ Search, and Inform CAD GISLink are trademarks of TriTech Software Systems.
ArcGIS, ArcMap and ArcCatalog are registered trademarks of Environmental Systems Research Institute (ESRI) in the United States and other countries.
Document Control
Template creation date: 5.31.17 – last update:2/14/2018 Date Version Details/Changes Author
01/24/19 1 Initial draft TriTech
Note: Prior to finalizing the document, select all of the document text (ctl-A) and activate F9 to update reference fields and the table of contents.
#11..
- 747 -
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
iii
Table of Contents
Document Control ....................................................................................................................... ii Table of Contents ....................................................................................................................... iii 1 Overview ................................................................................................................................ 1
1.1 Statement of Work ......................................................................................................................................... 1
1.2 Project Implementation Definitions ............................................................................................................... 1
1.3 System Acceptance Process ........................................................................................................................... 2
1.3.1 Functional Acceptance Testing .............................................................................................................. 2
1.3.2 TriTech System Integration Testing (SIT) ............................................................................................. 3
1.3.3 Client System Integration Testing ......................................................................................................... 3
1.3.4 Reliability Acceptance Period................................................................................................................ 4
1.4 General Client Responsibilities ..................................................................................................................... 4
1.5 Project Exclusions ......................................................................................................................................... 6 2 Project Deliverables .............................................................................................................. 7
2.1 Overview of Project Deliverables .................................................................................................................. 7 3 TriTech Project Roles and Responsibility ........................................................................ 10
3.1 Overview ..................................................................................................................................................... 10
3.2 TriTech Project Manager ............................................................................................................................. 10
3.3 Systems Engineer ......................................................................................................................................... 10
3.4 Inform CAD Business Analyst .................................................................................................................... 11
3.5 Inform Mobile Business Analyst ................................................................................................................. 11
3.6 GIS Analyst ................................................................................................................................................. 11
3.7 IQ CrimeView Implementation Specialist ................................................................................................... 11
3.8 Inform RMS Business Analyst .................................................................................................................... 12
3.9 Training Specialist ....................................................................................................................................... 12
3.10 Client Installation Services Team ................................................................................................................ 12
3.11 Customer Services Group ............................................................................................................................ 12
3.12 Account Manager......................................................................................................................................... 12 4 Recommended Client Roles and Responsibilities ........................................................... 14
4.1 Overview ..................................................................................................................................................... 14
4.2 Project Manager ........................................................................................................................................... 14
4.3 System Administrator .................................................................................................................................. 15
4.4 Inform CAD Administrator ......................................................................................................................... 15
4.5 Inform Mobile Administrator ...................................................................................................................... 15
4.6 Inform RMS Administrator ......................................................................................................................... 16
4.7 Inform RMS Output Designer Administrator .............................................................................................. 16
4.8 Inform Jail Administrator ............................................................................................................................ 17
4.9 GIS Analyst ................................................................................................................................................. 17
4.10 Inform CAD/Inform RMS /Inform Jail/Supervisors .................................................................................... 17
4.11 Subject Matter Experts ................................................................................................................................ 17
4.12 Application Trainers .................................................................................................................................... 18
4.13 IQ CrimeView & FireView Dashboard Administrator ................................................................................ 18
4.14 IQ CrimeView Dashboard Designer ............................................................................................................ 18 5 Project Controlling Processes ........................................................................................... 19
5.1 Overview ..................................................................................................................................................... 19
5.1.1 TriTech Responsibilities ...................................................................................................................... 20 #11..
- 748 -
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
iv
5.1.2 Client Responsibilities ......................................................................................................................... 20
5.2 Change Management Process ...................................................................................................................... 20
5.2.1 TriTech Responsibilities ...................................................................................................................... 21
5.2.2 Client Responsibilities ......................................................................................................................... 21
5.3 Project Reporting ......................................................................................................................................... 21
5.3.1 TriTech Responsibilities ...................................................................................................................... 22
5.3.2 Client Responsibilities ......................................................................................................................... 22
5.4 Document Review ....................................................................................................................................... 23
5.4.2 TriTech Responsibilities ...................................................................................................................... 23
5.4.3 Client Responsibilities ......................................................................................................................... 23
5.5 Third Party Management ............................................................................................................................. 24
5.5.1 TriTech Responsibilities ...................................................................................................................... 24
5.5.2 Client Responsibilities ......................................................................................................................... 24 6 Project Initiation and Planning .......................................................................................... 25
6.1 Overview ..................................................................................................................................................... 25
6.1.1 TriTech Responsibilities ...................................................................................................................... 25
6.1.2 Project Kick Off ................................................................................................................................... 26 7 Project Execution ................................................................................................................ 27
7.1 Overview ..................................................................................................................................................... 27
7.2 System Installation (Inform CAD, Inform Mobile, Inform RMS,and Interfaces) ....................................... 27
7.2.1 Review Hardware Specifications ......................................................................................................... 27
7.2.2 Hardware and Equipment Procurement Process .................................................................................. 27
7.2.3 Hardware Staging and Preparation for Installation .............................................................................. 28
7.2.4 TriTech Responsibilities ...................................................................................................................... 29
7.2.5 Basic Server preparation and Network Services .................................................................................. 30
7.2.6 System Installation ............................................................................................................................... 31
7.3 Implementation of Inform CAD .................................................................................................................. 33
7.3.1 Inform CAD System Orientation ......................................................................................................... 34
7.3.2 Inform CAD Base System Code File Entry ......................................................................................... 35
7.3.3 Geographical Information Services ..................................................................................................... 37
7.3.4 Inform CAD Demonstration of Licensed Functionality (DOLF) ........................................................ 38
7.3.5 Inform CAD Workshop(s) ................................................................................................................... 40
7.3.6 Inform CAD Functional Acceptance Testing (FAT) ........................................................................... 41
7.3.7 Inform CAD Legacy Data Conversion ................................................................................................ 43
7.3.8 Inform CAD Training .......................................................................................................................... 45
7.4 Implementation of Inform Mobile ............................................................................................................... 48
7.4.1 Inform Mobile System Orientation ...................................................................................................... 48
7.4.2 Inform Mobile Map Data Import ......................................................................................................... 49
7.4.3 Inform Mobile Configuration .............................................................................................................. 49
7.4.4 Inform Mobile Training ....................................................................................................................... 49
7.5 System Integration Testing (SIT)of Inform CAD, Inform Mobile, and Interfaces ...................................... 50
7.6 Implementation of Inform RMS .................................................................................................................. 51
7.6.1 Inform RMS System Orientation ......................................................................................................... 51
7.6.2 Inform RMS Administration and Review Training ............................................................................. 52
7.6.3 Inform RMS Base System Build .......................................................................................................... 53
7.6.4 Geographical Information Services ..................................................................................................... 54
7.6.5 Inform RMS Workshops ...................................................................................................................... 54
7.6.6 Inform RMS Output Designer Workshop ............................................................................................ 55
7.6.7 Inform RMS Demonstration of Licensed Functionality (DOLF) ........................................................ 55
7.6.8 Inform RMS Functional Acceptance Testing (FAT) ........................................................................... 57 #11..
- 749 -
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
v
7.6.9 Inform RMS Data Conversion ............................................................................................................. 58
7.6.10 Inform RMS Training .......................................................................................................................... 58
7.7 Inform RMS System Integration Testing (SIT) ........................................................................................... 61
7.7.1 TriTech Responsibilities ...................................................................................................................... 61
7.7.2 Client Responsibilities ......................................................................................................................... 61
7.8 Implementation of CDP Search ................................................................................................................... 61
7.8.1 CDP Search Setup and Conversion Services ....................................................................................... 61
7.8.2 CDP Search Administration Training (Remote) .................................................................................. 62
7.8.3 CDP Search Core End User Training (Remote) .................................................................................. 63
7.9 Implementation of IQ CrimeView Dashboard ............................................................................................. 64
7.9.1 Prerequisite Collection and Preparation ............................................................................................... 64
7.9.2 Application Configuration, Staging Deployment, and Initial Review ................................................. 65
7.9.3 Installation ........................................................................................................................................... 65
7.9.4 Dashboard Administrator/Designer Training (Remote) ....................................................................... 66
7.9.5 Dashboard Train the Trainer Training (On Site) .................................................................................. 66
7.10 Dashboard Go Live & System Review ........................................................................................................ 67
7.10.1 System Review .................................................................................................................................... 67
7.11 Implementation of Crimemapping.com ....................................................................................................... 69
7.12 Crimemapping.com System Review & Go Live ......................................................................................... 69
7.12.1 System Review .................................................................................................................................... 70
7.13 Implementation of System Interfaces .......................................................................................................... 71
7.13.1 Inform Standard Interfaces’ Requirement Gathering and Configuration ............................................. 71
7.13.2 Custom Interfaces’ Requirement Gathering and Configuration ........................................................... 72
7.13.3 Interface Functional Acceptance Testing (FAT) .................................................................................. 73
7.14 System and Subsystem Go Live .................................................................................................................. 75
7.14.1 Inform CAD, Mobile, and Inform CAD Subsystem Go Live .............................................................. 75
7.14.2 Inform RMS Go Live ........................................................................................................................... 76
7.14.3 CrimeView Go Live, System Review, & Acceptance ......................................................................... 77
7.15 Reliability Acceptance Period ..................................................................................................................... 79 8 Implementation of Inform Jail 6 ......................................................................................... 81
8.1.1 Software ............................................................................................................................................... 81
8.1.2 Interfaces ............................................................................................................................................. 82
8.1.3 Customer Hardware, Network and Power Requirements .................................................................... 82
8.1.4 Implementation Process Overview ...................................................................................................... 83
8.1.5 Training and Go Live Support ............................................................................................................. 84 9 Project Closure .................................................................................................................... 86
9.1.1 System Transition ................................................................................................................................ 86 10 Appendix A - Required Inform CAD DOLF Code File build ............................................. 87 11 Appendix B - Contracted Modifications to Standard TriTech Software Products ........ 88 12 Appendix C - Standard TriTech Interfaces ....................................................................... 89
12.1 Standard Interfaces for Each Environment .................................................................................................. 89
12.1.1 Production Environment: ..................................................................................................................... 89
12.1.2 Disaster Recovery Environment: ......................................................................................................... 89
12.1.3 Test Environment: ............................................................................................................................... 89
12.2 NCIC State Message Switch ........................................................................................................................ 89
12.2.1 Connections ......................................................................................................................................... 90
12.2.2 Transactions ......................................................................................................................................... 90
12.2.3 Query Builder Feature ......................................................................................................................... 94
12.2.4 Client Responsibility............................................................................................................................ 95 #11..
- 750 -
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
vi
12.2.5 TriTech Responsibility ........................................................................................................................ 95 13 Appendix D - Custom TriTech Interfaces .......................................................................... 96
13.1 Custom Interfaces for Each Environment .................................................................................................... 96
13.1.1 Production Environment: ..................................................................................................................... 96
13.1.2 Disaster Recovery Environment: ......................................................................................................... 97
13.1.3 Test Environment: ............................................................................................................................... 97 14 Appendix E - Subcontractor(s) Statement(s) of Work ..................................................... 98 15 CrimeView & FireView Appendix A – Dashboard Hardware, Software, and Related Requirements ............................................................................................................................ 99 16 CrimeView Appendix B – Dashboard GIS Data and Application Specifications ......... 101
16.1.1 GIS Data Specifications ..................................................................................................................... 101
16.1.2 Application Specifications ................................................................................................................. 101 17 CrimeView Appendix C – Dashboard Standard Field Lists ........................................... 103 #11..
- 751 -
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
vii
#11..
- 752 -
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2017 TriTech Software Systems
1 1 OVERVIEW
1.1 Statement of Work
This Statement of Work (SOW) defines the services and deliverables that TriTech will be providing in accordance with the terms and conditions of the System Purchase Agreement (the “Purchase Agreement”) between TriTech Software Systems (TriTech) and Glendale Police Department (“Client”).
The pricing and services for this assume the project duration will not exceed a period of twenty-four (24) months. If the project exceeds the expected duration due to client delays, additional services must be purchased.
This project description includes the services and deliverables specified by the Purchase Agreement, including if applicable, TriTech Software and services, Subcontractor activities, Third Party products and services for the implementation of the System and Subsystems specified in the Purchase Agreement (collectively the “Project”).
Statement(s) of Work for applicable TriTech Subcontractor(s) are presented in Appendix E - Subcontractor(s) Statement(s) of Work.
In some cases, the framework of Deliverables documented by this SOW for this Project is further defined through additional documents such as: Operational Scenario Documents (OSD); Interface Requirements Documents (IRD); Functional Design Documents (FDD); User and Administrator Documentation and Training Materials.
The number and type of software licenses, products, or services provided by TriTech or its Subcontractors are specifically listed in the Purchase Agreement and any reference within this document as well as Subcontractors’ SOWs (if applicable) does not imply or convey a software, license, or services that are not explicitly listed in the Purchase Agreement.
1.2 Project Implementation Definitions
Unless otherwise defined herein, capitalized terms within this document have the meanings described in the Definitions section of the Purchase Agreement and where applicable Software Support Agreement.
The following terms are used in this document. Since these terms may be used differently in other settings, these definitions are provided for clarity.
Project Schedule means the schedule providing dates and timeframes for completion of tasks and Deliverables during the course of this Project. The Project Schedule is subject to change at the mutual agreement of TriTech and the Client as further described in this SOW. Project Management Plan means collectively the Communications Management Plan; Risk Management Plan; and Change Management Plan that provide the criteria for managing those tasks within the Project.
The OSD provides an operational description of a capability or feature within the applicable TriTech solution in sufficient detail that both Client and TriTech team mutually agree to the expected deliverable. The OSD provides the “what”, “how,” and the information flow (including data flow and data elements, when appropriate) of the capability or feature. The OSD does not provide the technical #11..
- 753 -
Overview
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
2 or internal design of how TriTech’s Development team will accomplish the requested feature. An OSD will be provided for each contracted product customization to be developed. Once approved by the Client, the OSD becomes the basis for TriTech’s development. Once approved, any further changes requested by the Client to the OSD and/or design may incur additional costs to the Client. Standard Interface Requirement Document (IRD) defines the functionality of the Standard Interfaces.
These documents are standard, published TriTech documents, and are not specific to a Client. Functional Design Document (FDD) contains details for data conversions such as the proposed approach, fields that will be converted, and assumptions.
1.3 System Acceptance Process
This project shall follow a standard Acceptance Test methodology which is designed to allow the parties to thoroughly evaluate and verify the functionality and reliability of TriTech System and Subsystems. These procedures include several steps that are described in later sections of this SOW. Upon successful completion of these procedures the system is deemed Accepted.
1.3.1 Functional Acceptance Testing
Functional Acceptance Testing (FAT) is conducted on each Subsystem prior to conducting End User Training on these applications and staging them for Go Live. The focus of these tests is to verify that each Subsystem meets the functions as described in TriTech’s standard FAT documents, which have been created based on TriTech’s standard product specifications.
Note: Functional Acceptance Testing for each Subsytem will occur one time, at one location. For projects that will place Subsytems for agencies and/or PSAPs in multiple phases, FAT will only be conducted for the first phase going into Production, and will not be repeated for subsequent phases. The Client must ensure that appropriate representation from various agencies and/or PSAPs attend the FAT for each Subsytem.
The Functional Acceptance Tests are performed based upon standard TriTech FAT documents and have a standard content and format. These standard FAT documents will be submitted to the Client for review prior to testing.
During the scheduled FAT and according to the FAT documents, TriTech and Client project personnel will work to identify any errors where the Subsystem does not conform materially to the FAT documents. Any such errors will be documented by TriTech on the FAT exceptions list. Errors listed on the FAT exception list will be classified as follows:
1) Pre-Go Live Issues: Issues in the Subsystem that prevent the Client from performing normal daily and monthly operations and therefore must be corrected prior to Go Live. 2) Post Go Live Issues: Issues identified in the FAT testing that do not prevent the Client from performing normal daily and monthly processes and therefore can be corrected after the Subsystem Go Live. These issues will not be used as part of the criteria for Acceptance. #11..
- 754 -
Overview
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
3 In the event that the Client chooses not to follow the Acceptance Test processes defined in the Statement of Work, the Client’s cutover to live production status (i.e., productive use) of any TriTech supplied Subsystem constitutes the Client’s acceptance of the Subsystem.
1.3.2 TriTech System Integration Testing (SIT)
Once the FAT is successfully concluded for all subsystems that are scheduled to go live together and in preparation for Go Live, TriTech and the Client will conduct a remote SIT (up to 4 hours). Typically Inform CAD, Inform Mobile, and CAD interfaces Go Live together. Inform RMS and Inform Jail, along with their associated Interfaces may go live together or separately.
The SIT for CAD and its Subsystems will be conducted based on a scenario that test the call flow from the call creation to disposition in CAD. The scenario will include Mobile, selected interfaces (Paging, CAD to External RMS, Station Alerting, and Records Check/NCIC) and the suite integration. The core client project team will participate in this test with TriTech. TriTech will provide a standard set of test scenarios that test the CAD system and suite integration.
The SIT for Inform RMS will be conducted based a scenario that test the records management process. The scenario will include RMS and Records Check/NCIC. The core client project team will participate in this test with TriTech. TriTech will provide a standard scenario that test the Records Management System.
The SIT scenario will be provided to the Client for review prior to the commencement of the SIT. A TCR will be submitted to the Client documenting the delivery of the SIT Test plans and must be approved prior to testing. At the successful completion of SIT, without any issues that prevent the System to be taken Live, the Client shall provide written approval that the System is ready for Go Live. If the project includes separate Go Lives for each System (CAD/Mobile, RMS, Jail), then separate SIT Scenarios and Go Live Authorizations will be prepared for each set of Subsystems and interfaces going live together.
1.3.3 Client System Integration Testing
TriTech's Standard System Integration Testing is designed to test the system under a standard set of parameters and typical scenarios.
It is recommended that the Client build out their own set of system integration tests based on their operational business processes. Industry best practices have found that testing the individual applications that will go-live together reduces the amount of risk and unexpected ad-hoc configuration changes post golive.
The core client project team should assemble a small group of end users from each respective discipline (dispatchers, field users, and records clerks) to conduct the Client System Integration Testing. The Client should build their test scenarios around typical day to day call and incident processing workflows, as well as scenarios that may be more atypical, such as large scale, mass casualty, or active shooter type #11..
- 755 -
Overview
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
4 incidents. Using data from the legacy system provides an excellent opportunity to test the new system under similar circumstances.
The Client will be responsible for coordination and execution of the Client System Integration Testing.
TriTech project staff will be available to support the testing remotely on an as-needed basis. Any issues identified during the Client System Integration Testing should be immediately reported and escalated as outlined elsewhere in this SOW.
1.3.4 Reliability Acceptance Period
As further defined in the Agreement, immediately upon production cutover (Go Live) of the TriTech Subsystems, a thirty (30) day Acceptance Test Period will begin to verify operational functionality in a live environment. If no Critical Priority or Urgent Priority Software Errors (as those terms are defined in Addendum E to the Agreement) are reported during such thirty (30) day period, the Subsystems shall be deemed to have achieved Final Acceptance. In the event that a Critical Priority or Urgent Priority Software Error occurs during the Acceptance Test Period, TriTech shall commence actions in accordance with the Software Support Agreement to correct the reported error. This process is further defined in section 7.15, Reliability Acceptance Period.
1.4 General Client Responsibilities
In addition to those Client responsibilities stated elsewhere in this SOW, the Client is responsible for:
1) Electrical facilities (e.g., outlets, generator and other electrical infrastructure facilities) required for this project, including necessary maintenance.
2) Cabling (e.g., power, network, interface and other electrical and data transmission lines) required for this project, including necessary maintenance.
3) Network/communications connections (e.g., LAN/WAN, commercial wireless, telephone, VPN, and other voice/data connections), or ongoing network/communications charges associated with installation, operation or support of the proposed system including the establishment and maintenance of security accounts.
4) Configuration and/or programming of network routers, switches and bridges – this includes providing information to TriTech staff on any firewalls within the overall network that the system will operate and necessary port access for the system to operate in accordance with TriTech documentation.
5) The installation, configuration, maintenance (including patch management and upgrades of Microsoft software required by the System.
6) The installation of servers into racks and the connection of such servers to network switches. 7) The assignment of machine names and IP addresses for servers to be utilized by the System. This includes joining the servers to the network and the assignment of security accounts as specified by TriTech documentation.
#11..
- 756 -
Overview
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
5 8) Any hardware and third party software or services necessary for implementing the System that is not listed in the Purchase Agreement as a TriTech Deliverable (not listed as a line item in the Price and Payment section of the Purchase Agreement). This includes workstations, server hardware, network equipment, telephone or TDD equipment, performance test software, Microsoft licenses, Disaster Recovery Software, and services required to extract legacy data and convert into acceptable data formats.
9) Configuration, maintenance, testing, and supporting the Third-Party Systems that the Client operates and which will be interfaced with as a part of this project. This project includes the contracted Interfaces listed in Appendix C - Standard TriTech Interfaces and Appendix D - Custom TriTech Interfaces. The Client is responsible for maintaining and supporting these systems in good working order. The Client is responsible for providing Application Programming Interface (API) documentation to these systems that document the integration process for the level of interface integration defined by TriTech’s response to the RFP, as described by TriTech responses to the RFP as well as Interface IRD and approved OSDs. The Client is also responsible for any cost associated with the development, or configuration of the Third-Party System Vendor side of the Interfaces. 10) Consoles, furniture or fixtures as well as any modifications to install equipment used for Systems or Subsystems specified by the Purchase Agreement into existing consoles, furniture, vehicles or existing facilities. Installation of Workstations into consoles, furniture, vehicles or like items, is the responsibility of the Client.
11) Active participation of the appropriate personnel with the necessary background knowledge and availability in the Project implementation meetings and working sessions during the course of the Project. Examples of such implementation sessions are System Orientation, DOLF, Acceptance Testing, Training, regular Project meetings, discussion regarding Interfaces, system installation planning, and the like.
12) The provision of Code Files and GIS data as requested by TriTech staff. This information must be provided on a timely basis in order to meet the project timelines. This information will be provided in a format requested by TriTech staff in accordance with TriTech Documentation. 13) Assistance with any non-TriTech systems and/or databases the IQ CrimeView application or import process will interface with in order to obtain data or provide functionality. Common examples include provision of data dictionaries, ODBC connectivity, and information pertaining to the type, location, and structure of data in the source CAD, RMS, or other source database(s) or data file(s). 14) The timely review and approval of Functional Acceptance Testing (FAT) documents, OSDs, IRDs, Task Completion Reports (TCR) and/or other project documentation as further defined in this SOW. 15) Provide a facility with the required computer and audio-visual equipment for training. 16) Timely completion of acceptance testing for each of the TriTech Subsystems. 17) Timely completion of Data Categorization Worksheets, Application Reviews and, where appropriate, Content Building for the IQ CrimeView application. 18) TriTech pricing for this Project assumes that all Client supplied products and services required to support the project will be delivered according to this agreed to Statement of Work, based upon a mutually agreed upon project schedule. This timeline will require a commitment by Client staff to attend project meetings, attend training, and execute action items in a timely fashion. Should the Client find that it is unable to support the agreed to schedule, TriTech reserves the right to execute a #11..
- 757 -
Overview
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
6 mutually agreed to Project Change Order. The Change Order will make the necessary modifications to schedule and/or scope of the project and, if applicable, allow TriTech to recoup any additional costs which may be incurred by TriTech as a result of Client delays. 19) The Client is responsible for providing remote connectivity to TriTech for the purpose of installation, configuration, testing, and troubleshooting of TriTech’s applications at the Client site.
TriTech’s approved remote connectivity methods are described in the System Planning Document. 20) Connect and configure any Third-Party hardware (such as Bar Code Scanners, Bar Code Printers, Biometric Fingerprint Scanners, and Signature Pads) to Client workstations, if these services are not explicitly sold in the System Purchase Agreement.
21) The Client is responsible for the creation and ongoing maintenance of SSL certificates required for the operation of the software of on-Premise hardware. This includes the tracking of expiry dates and the timely renewal of certificates.
1.5 Project Exclusions
1) TriTech Software Systems provides software applications that it develops. These applications are sold as is and are considered to be “Commercial Off the Shelf” (COTS) software packages. The functionality of these products will be based on TriTech’s current design and functionality of these COTS products, unless otherwise indicated in the Purchase Agreement, or if applicable, TriTech’s responses to the RFP.
2) Work, software, services, hardware, Systems, Subsystems, product/software modifications, or any other deliverables not explicitly stated in the Purchase Agreement will not be included in the Project. 3) Any modification to TriTech standard products or customizations to such products that are not explicitly stated in the Purchase Agreement are excluded from the scope of this Project. 4) Changes in scope will only be executed through a mutually agreed upon Change Management Process, as described in the Project Management Plan.
5) TriTech is not responsible for the deficiencies in the Client’s internal or contracted network to support remote Inform CAD, Inform RMS, Inform Jail or other subsystem workstations. 6) TriTech is not responsible for the deficiencies in a Client’s internal or contracted network to support some of the extended features of Inform Mobile and Inform RMS products due to bandwidth or limitations in wireless coverage.
7) TriTech is not responsible for the removal of the old (legacy) equipment, hardware, furniture, consoles, cabling, as part of the Project implementation unless specifically stated in the Purchase Agreement and this SOW.
8) Unless otherwise stated, this project does not include reconfiguring the data import process for IQ CrimeView for a separate or replacement CAD, RMS, or other source database/system after the initial configuration is initiated.
9) This project does not include creation or modification of GIS data by TriTech staff. #11..
- 758 -
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2017 TriTech Software Systems
7 2 PROJECT DELIVERABLES
2.1 Overview of Project Deliverables
This project will provide a combination of software and services that comprise the System for use by the Client’s Public Safety Organization(s). The individual Subsystems to be provided comprise the overall System. The Purchase Agreement specifies the software licenses included in this Project by the quantity and environment in which licensed. This includes all Server and User Licenses, Standard and Custom Interfaces, as well as other TriTech tools and utilities.
The Purchase Agreement for this project incorporates the following major Subsystems:
1) Inform CAD (Production, Test, Training)
a. Inform CAD Browser
b. Inform CAD GISLink
c. Inform CAD Archive and Reporting Server
d. Inform CAD Routing Server
e. Inform CAD Rotation Provider
f. Inform CAD Standard Operating Procedure (SOP)
2) Inform Mobile (Production, Test, Training)
a. Inform Mobile Magnetic Stripe Reader
3) Inform RMS (Production, Test, Training)
a. Inform RMS Evidence and Barcoding
b. Inform RMS Reporting Server License
c. Inform RMS Accident
d. Inform RMS GIS (With CAD)
4) Inform Jail 6 (Production)
a. Inform Jail 6 Administration Core
b. Inform Jail 6 Financial Core
c. Inform Jail 6 Advanced
d. Inform Jail 6 Personnel Core
e. Inform Jail 6 Personnel Advanced
f. Inform Jail 6 Reporting Core
5) TriTech Message Switch
6) TriTech Message Switch Query Builder
7) CDP Search subscription
#11..
- 759 -
Project Deliverables
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
8 8) CDP Crimemapping.com
9) IQ CrimeView (to include Middleware, Hosted Dashboard & Subscription) 10) System Interfaces as listed in the Appendices to this SOW Implementation of different components of the System is performed in a series of interrelated processes.
Some processes can be performed concurrently while others are sequential in nature. TriTech has implemented process gates to ensure successful completion of tasks in the optimal order before a subsequent activity begins.
The only reference for the number and type of software licenses is the Purchase Agreement. Any reference within this document to services associated with a specific software product does not imply or convey a software license for products that are not listed in the Purchase Agreement.
2.1.1.1 Standard TriTech Software Deliverables
The functionality provided by Standard TriTech Software Products, including Interfaces (the core TriTech Software and Interfaces without any Modifications) is defined by TriTech Standard documentation such as User and Administration Guides for TriTech’s major Subsystems such as Inform CAD, Inform Mobile, Inform CAD Browser, Inform RMS, Inform Jail, IQ Search, Inform CAD GISLink and other Standard Software products. Standard Interface Requirement Documents (IRD) define the functionality of the Standard Interfaces. These documents are standard, published TriTech documents, and are not specific to a Client.
Standard TriTech Interface Software to be delivered through this Project is identified as software licenses in the Purchase Agreement. The functionality provided by Standard TriTech Interface Software is defined by TriTech IRDs.
Any Modification to the functionality of Standard TriTech Software within the System, or Subsystems, shall follow the Change Management Process as described in Section 5.2, Change Management Process. The scope of the Modification will be described in an OSD. Release of all Modifications to TriTech’s Standard Interfaces will follow Subsystem release cycles (i.e., Inform CAD, Inform RMS, and the like).
2.1.1.2 Contracted Modifications to Standard TriTech Software Products Any Modifications to Standard TriTech Software Products including Inform CAD, Inform Mobile, Inform RMS, Inform Jail, IQ Search, Inform CAD GISLink, and Standard System Interfaces that are to be delivered through this Project are listed in the Purchase Agreement. The functional scope of any Modification procured through the Purchase Agreement will be summarized in this Statement of Work and defined by an OSD for all items listed under Appendix B - Contracted Modifications to Standard TriTech Software Products for Inform CAD, Inform Mobile, Inform RMS, Inform Jail, and other major TriTech Subsystems; and under Appendix C - Standard TriTech Interfaces, for modifications to Standard Interfaces. Any and all modifications or enhancements that are not explicitly listed in the Purchase Agreement or TriTech’s responses to the RFP are not within the scope of this Project.
Any changes in the requirements documented in the System OSDs, post approval of the OSDs are subject to formal Change Order.
Note: All enhancements and modifications to any of TriTech’s Standard products (including the Interfaces) will only be released with a major version of the applicable subsystem (i.e., Inform #11..
- 760 -
Project Deliverables
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
9 CAD, Inform Mobile, Inform RMS, Inform Jail and the like) based upon the relevance and dependency to these products.
Note: Software versioning is the process of assigning either unique version names or unique version numbers to unique states of computer software while a service pack or patch is a piece of software designed to fix problems with, or update a computer program or its supporting data.
This includes fixing security vulnerabilities and other bugs.
2.1.1.3 Contracted Custom Interface Software
Custom Interfaces to be created by TriTech are identified as individual software licenses in the Purchase Agreement. A high-level description of the intended functionality and scope is attached as part of Appendix D - Custom TriTech Interfaces to this SOW. The detailed functional scope of any custom Interface procured through the Purchase Agreement will be defined by an OSD, which will be developed and delivered to the Client during the project.
Any changes in the requirements documented in the System OSDs, post approval of the OSDs are subject to formal Change Order.
#11..
- 761 -
TriTech Project Roles and Responsibility
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
10 3 TRITECH PROJECT ROLES AND RESPONSIBILITY
3.1 Overview
TriTech will appoint a team of specialized personnel that will implement the Project under the direction of TriTech’s Project Manager. The team will be multi-disciplinary and the team members may specialize in different products or Subsystems. Team members may be engaged in different phases of the Project as necessary and in some cases are involved in the Project for a limited timeframe. Any personnel changes by TriTech will be discussed with and agreed upon by the Client in advance. Such agreement will not be unreasonably withheld.
The descriptions of personnel roles noted below provide an overview of typical Project team members. Other personnel may be involved under the direction of the TriTech Project Manager in order to complete the requirements of the Project.
3.2 TriTech Project Manager
TriTech has appointed a TriTech Project Manager as the principal TriTech contact who will be responsible for managing TriTech’s responsibilities related to the implementation of the Project, as described in this SOW and within the scope of the Purchase Agreement. The Project Manager is also responsible for managing the Deliverables for TriTech’s subcontractors.
Each of TriTech’s Subcontractors may appoint a Project Manager to manage their portion of the Project Deliverables and activities. However, the TriTech Project Manager will have the overall responsibility for coordinating all activities and supervising the progress of each sub-Project. The TriTech Project Manager will manage all communications between the Client and each of TriTech’s Subcontractors. TriTech’s Project Manager is responsible for Project scheduling and management of TriTech Project personnel and subcontractor/supplier resources.
The Project Manager utilizes a standardized methodology for project implementation, project management, and risk identification and management. TriTech’s Project Manager is responsible for Project scheduling and management of TriTech Project personnel and applicable Subcontractor/supplier resources, budget management, identification and management of Project risks, and communication with the Client’s Project team. The TriTech Project Manager will be responsible for the collaborative coordination of Client resources in an effort to ensure that avoidable Project delays will be minimized.
The Project Manager is involved in the Project beginning with the SOW development and continuing through post Go Live Project closure activities. The Project Manager will be an active participant in many of the milestone events through the course of the Project including System Orientation, DOLF, and Go Live.
The Project Manager will organize a bi-weekly Project status call with the Client and necessary Project team members. Additionally, the Project Manager will provide the Client with a written Project status report on a monthly basis, as further defined in this SOW.
3.3 Systems Engineer
The Systems Engineer is responsible for two primary functions, within the scope of the Project: 1) configuration of Standard TriTech Interfaces (including configuration documentation); and 2) development of software requirements documentation for Custom Interfaces. The Systems Engineer will additionally #11..
- 762 -
TriTech Project Roles and Responsibility
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
11 participate in testing of each of these Subsystems. In some cases, Development Engineers may perform the role of the Systems Engineer for specialized interfaces, particularly for Inform RMS and Inform Jail interfaces.
3.4 Inform CAD Business Analyst
The Inform CAD Business Analyst is responsible for the configuration of the CAD based on the Client’s system requirements, business rules, configuration data, and reporting needs. The Business Analyst will provide consultation services to the Client with regard to the configuration and operation of CAD. The Inform CAD Business Analyst is also responsible for conducting the CAD System Orientation, Demonstration of Licensed Functionality (DOLF), performing the Acceptance Testing and providing consulting support throughout the Project implementation life cycle.
After the completion of the DOLF session, ownership for continued Code File configuration and maintenance transfers to the Client. At this stage, the Business Analyst will serve as a consultant for the Client’s further configuration of the Client’s CAD system until the Client’s System is in live operation.
These activities are described in later sections of this SOW.
The Business Analyst will be an active participant in many of the milestone events through the course of the Project and will participate in bi-weekly Project status calls, as needed.
3.5 Inform Mobile Business Analyst
The Inform Mobile Business Analyst is responsible for the configuration of the Inform Mobile based on the Client’s system requirements and the dispatch and field users’ operations. The Business Analyst will provide consultation services to the Client with regard to the configuration and operation of Inform Mobile. The Inform Mobile Business Analyst is also responsible for conducting the Inform Mobile System Orientation, performing the Acceptance Testing, delivery of Train the Trainer and Inform Mobile Administration Class, as well as providing consulting support throughout the Project implementation life cycle.
3.6 GIS Analyst
As part of the implementation team, TriTech utilizes a GIS Analyst that specializes in geographical Information technology. The GIS Analyst is responsible for 1) performing an analysis regarding the Client’s GIS source data; 2) consultation services regarding converting the GIS source data for use in Inform CAD, Inform Mobile, and Inform RMS; 3) providing training for applicable TriTech GIS tools as included in the Purchase Agreement; 4) preparing the one-time GIS data configuration for the Inform Product Suite.
3.7 IQ CrimeView Implementation Specialist
The IQ CrimeView Implementation Specialist specializes in GIS (Geographic Information Systems), ETL (Extract, Transform, Load) data processes, and public safety analysis. This individual is responsible for assisting with software installation and configuration, assessing GIS and other data, configuring the SQL, geocoding, and ETL middleware interfaces, configuring the end user application, and training administrators and users. The IQ CrimeView Implementation Specialist will also coordinate deployment/installation of web applications and advising on server and web configurations related to those applications. #11..
- 763 -
TriTech Project Roles and Responsibility
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
12 3.8 Inform RMS Business Analyst
Inform RMS and Inform Jail Business Analyst(s) participate in various activities throughout the implementation of each of these Subsystems. They are primarily responsible for conducting the System Orientation with the Client to observe and evaluate the Client’s current business practices and make recommendations for improving efficiency and areas that need to be reviewed. They also conduct the Demonstration of Licensed Functionality (DOLF), Administration Training, guide the Client through Functional Acceptance Testing, and provide consulting support throughout the Project implementation life cycle.
After the completion of the RMS Admininstration & Review training session, ownership for continued system build and maintenance transfers to the Client. At this stage, the Business Analyst will serve as a consultant for the Client’s further configuration of the Client’s system until the Client’s System is in live operation. These activities are described in later sections of this SOW.
The Business Analyst will be an active participant in many of the milestone events through the course of the Project and will participate in bi-weekly Project status calls, as needed.
3.9 Training Specialist
Training for TriTech applications is provided by TriTech Training Specialists. Training staff for other products and functions will vary by the type of product and training proposed.
This process is described in greater detail in the training sections of this document, related to each of these products.
3.10 Client Installation Services Team
TriTech’s Client Installation Services (CIS) team is responsible for installation and integration of TriTech Software onto the system hardware that is identified for this Project. This team works closely with the Client’s staff to coordinate IP and network addressing, security accounts, network connections, and remote access to the System.
This process is described in greater detail in Section 7.2, System Installation of the SOW.
3.11 Customer Services Group
Customer service functions and technical support for the Client’s System during the Project is coordinated by the TriTech Project Manager. After Go Live, TriTech’s Customer Services Group is responsible for providing on-going support for the Client’s System as defined in the Purchase Agreement and the Software Support Agreement.
3.12 Account Manager
The Account Manager is an important resource to the Client throughout the life of their System. The Account Manager will be the primary contact and liaison for non-technical support issues, system changes and billing questions. They provide support for general customer service requests, manage requests for new software and services, and provide assistance with planning technology upgrades post System Go Live. #11..
- 764 -
TriTech Project Roles and Responsibility
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
13 Having the Account Manager participate as a key Project member provides an enhanced level of continuity for the Client as they continue their relationship with TriTech. #11..
- 765 -
Recommended Client Roles and Responsibilities
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
14 4 RECOMMENDED CLIENT ROLES AND
RESPONSIBILITIES
4.1 Overview
Implementation of the Subsystems in a manner that meets the Client’s operational needs requires collaboration with the Client’s team. In general, the Client’s Project team should include staff experienced in the operation and administration of the Client’s current public safety technology systems as applicable to the scope of this project. Such teams may include representatives from the Inform CAD, Inform Mobile, Inform RMS, and Inform Jail users and stakeholders. These “subject matter experts” need to be engaged through the course of the Project from initiation until live operations, and may be involved in the support and maintenance of the System and Subsystems after Go Live.
These recommendations do not speak to specific positions. Rather, this information defines specific responsibilities and estimated time commitment. The Client may elect to create individual positions, combine responsibilities, and/or assign responsibilities within their current organizational structure. The Client needs to periodically assess its staffing needs based on changes in the Client’s operational use of this technology.
Often, there is overlap with these core responsibilities - therefore, the team can generally be kept to a small group, dependent upon the complexity of the system being implemented and the number of Subsystems.
In addition, it is recommended that the Client, early within the implementation process, identify those persons that will be responsible for the ongoing maintenance of the Client’s System to include the technical and business processes. The application Administrators (Inform CAD, Inform Mobile, Inform RMS, and Inform Jail), as well as the System Administrator, are very key to the success of the Project. It is paramount that the Client develops this team during the implementation process so that the Client successfully achieves a degree of self-reliance with the understanding of each of the Systems in addition to the generalized technical responsibilities.
4.2 Project Manager
The Client’s Project Manager is the principal Client contact who will manage a team of Client Project personnel. The Client’s Project Manager manages and coordinates Client’s resources responsible for completing assigned Project tasks and activities.
Activities include facilitating Project Schedules and meetings, timely approval and processing of invoices, review and approval of Task Completion Reports (“TCRs”), Project management plans, applicable configuration sheets, OSDs and IRDs, approval of the Project documentation and FAT, and management of the Client’s staff. Additionally the Client’s Project Manager is responsible for coordinating the efforts, activities, and communications between TriTech and third party vendors that are not TriTech Subcontractors, as well as any deliverables from these vendors to the Project. #11..
- 766 -
Recommended Client Roles and Responsibilities
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
15 4.3 System Administrator
The Client’s System Administrator is the individual primarily responsible for managing the technical backend of the System including Windows, SQL Server, network, hardware, data back-ups and log management.
This individual is the primary technical point of contact representing the Client.
As identified in the Purchase Agreement and the Software Support Agreement, following the initial system installation, administration, and support for hardware (including the software operating system) and network components are the responsibility of the Client. The Client needs to plan for support and maintenance through the development of Client resources, other departments within the Client’s organization, or by contracting for such services. The Client should establish procedures for managing warranty service of hardware.
Activities for this position include 1) management of Microsoft Windows Operating System including patches and service packs; 2) management of Microsoft SQL Server including patches and service packs; 3) implementation of software prerequisites (in accordance with TriTech Documentation) on computers as needed for current operations and System upgrades; 4) monitoring, management and maintenance of the Client’s network including LANs, WANs, wireless networks, security accounts and support connectivity (in accordance with TriTech Documentation); 5) hardware maintenance and troubleshooting; file and data backups and software and error log management; and 6) creation, maintenance and renewal of certificates of onPremise systems.
Time commitment will vary with the number of computers on the system, the complexity of the network (including the use of a WAN) and the number of personnel to be managed in network access. If the System LAN is connected to the Client’s administrative LAN/WAN1 , coordination will be important to avoid
problems with the Client’s network traffic. Personnel involved in System Administration should attend the applicable TriTech System Administrator Course(s). Where a large team is involved, a core team should attend a System Administrator Course and then the Client’s System Administration team should conduct a smaller version of the training for local staff.
4.4 Inform CAD Administrator
The Client’s Inform CAD Administrator is the individual primarily responsible for managing the Inform CAD application software settings to ensure efficient operation. This individual is the primary CAD configuration point of contact representing the Client.
Activities include TriTech software setup, assignment, and management of TriTech Software modular security, maintenance of the Code Files, evaluation and implementation of version updates, reporting, prioritization, and management of support issues.
Within the Multi-Agency environment, separate CAD administration staff may be required to manage the components used by each operation - under the direction of an overall System-Wide CAD Administrator.
Any personnel involved in CAD administration should participate in the DOLF session so they are prepared to maintain the CAD Code Files post DOLF. The CAD Administrator should additionally attend Inform CAD User Training.
4.5 Inform Mobile Administrator
The Client Inform Mobile Administrator must possess a set of skills necessary to support the Client’s implementation of the Mobile System. The Inform Mobile Administrator will be responsible setting up and maintaining the users, and vehicles as well as minor configuration changes to the Inform Mobile product.
The desired administrator should possess a working knowledge of:
1 TriTech recommends a dedicated LAN for CAD as documented in the System Planning Document. #11..
- 767 -
Recommended Client Roles and Responsibilities
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
16 HTML/XML, CSS, and JavaScript.
SQL, especially views, stored procedures, and database schema.
Standard GPS protocol (TAIP and NMEA).
The Inform Mobile Administrator should attend the Inform Mobile Train-the-Trainer course and the Inform Mobile Administration course.
This individual should work closely with the System Administrator in order to manage file and data back-ups and System administration of the hardware and network.
4.6 Inform RMS Administrator
The Inform RMS Administrator will have the responsibilities for the implementation, configuration, and maintenance of TriTech’s Inform RMS. This person or persons will be engaged in the implementation of the TriTech’s Inform RMS, and will participate in making decisions as it relates to implementing the TriTech’s Inform RMS.
Inform RMS Administrator will attend the Inform RMS Workshops throughout the course of the Project.
This person should have a comprehensive understanding of the internal structure and workflow of Inform RMS, departmental policies and procedures as well as how the records department interacts with dispatch and field operations personnel.
The Inform RMS Administrator will be responsible for building and maintaining the RMS templates, workflows and code tables. Additional activities include TriTech software setup, assignment, and management of the agency specific Code Files, evaluation and implementation of version updates, reporting, prioritization, and management of support issues.
Within the Multi-Agency environment, separate local RMS administration staff may be required to manage the components used by each Agency - under the direction of an overall Central RMS Administrator. Any personnel involved in RMS administration should participate in the RMS workshops so they are prepared to maintain Inform RMS.
4.7 Inform RMS Output Designer Administrator
The Inform RMS Output Designer Administrator will have the responsibilities for creating custom form outputs within RMS using Microsoft SQL Server Reporting Services (SSRS), which can be accessed from the Inform RMS Web UI Data Entry Templates. Using the Inform RMS Output Designer application utility, the administrator will learn to generate a dataset based on the Inform RMS Module template, utilizing SSRS to customize the output based off a pre-defined default output report. This administrator will be responsible for configuring the templates to use the custom form output within the Inform RMS Web Data Entry Designer tool in conjunction with the Inform RMS Administrator.
This is an advanced role and the resource should have prior working experience using SSRS. TriTech will not provide training on SSRS. This resource will also need to be familiar with the Inform RMS Templates as designed by the Inform RMS Administrator.
#11..
- 768 -
Recommended Client Roles and Responsibilities
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
17 4.8 Inform Jail Administrator
The Inform Jail Administrator will have the responsibilities for the implementation, configuration, and maintenance of TriTech’s Inform Jail. This person or persons will be engaged in the implementation of the Inform Jail and will participate in making decisions as it relates to implementing this application.
The Inform Jail Administrator must have a comprehensive understanding of the Jail’s internal structure, as well as, policies and procedures, list of bonding companies, floor/bed layout of all facilities, i.e., main jail and annexes, and other information that are applicable to implementation and maintenance of the Inform Jail.
The Inform Jail Administrator will be responsible for building and maintaining the Jail Code Files.
Additional activities include TriTech software setup, assignment, and management of the agency specific Code Files, evaluation and implementation of version updates, reporting, prioritization, and management of support issues.
4.9 GIS Analyst
The GIS Analyst is responsible for the mapping components required for Inform CAD, Inform Mobile, Inform RMS, and IQ CrimeView. Activities include providing the initial GIS files to TriTech for analysis.
The GIS Analyst will be responsible for updating the Inform CAD and Inform Mobile Streets data using GIS Link, and working with TriTech’s GIS Analyst to implement mapping components for Inform RMS and IQ CrimeView.
During scheduled activities, the Client should have a fully dedicated person or persons. Post implementation workload is based upon the number and type of GIS data edits that will be necessary for the local operations.
This person (or group of people) should attend GISLink training and IQ CrimeView Dashboard Training.
4.10 Inform CAD/Inform RMS /Inform Jail/Supervisors
Input from the Users/Supervisors is important to ensure that the configuration settings approved by the Client’s team will be perceived as usable by users of the each of the Subsystems. These Users/Supervisors should participate in meetings defining and evaluating the requirements and configuration of their respective products, such as System Orientation and Administration Training.
During scheduled activities, the Client should have a fully dedicated person or persons. Post implementation should be maintenance only. These personnel should attend the applicable User trainings.
4.11 Subject Matter Experts
Input from subject matter experts in all applicable areas (Inform CAD, Inform Mobile, Inform RMS, Inform Jail, and each of the Interfaces and external Systems that integrate with TriTech Systems) is essential to successful implementation of the system. The subject matter expert(s) in each area are the individuals who are knowledgeable about the current operational and technical specifications of the system, the data flow between and among different applications, and any limitations associated with each application.
For Standard and Custom Interfaces, subject matter experts may be from the Client Agency, and third party vendors. If the vendors are not TriTech Subcontractors, the Client will be responsible for engaging them in necessary discussions and documentation of the requirements. #11..
- 769 -
Recommended Client Roles and Responsibilities
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
18 The Client should involve a fully dedicated person or persons during the scheduled activities, such as requirements analysis, demonstration of the applications (if applicable), review of requirements documentation, the testing process, and other events that are described in later sections of this SOW. Post implementation, the involvement of the subject matter experts should be limited to maintenance only.
4.12 Application Trainers
A team of trainers is needed for training the Client staff on TriTech Software on an on-going basis. Trainers will be responsible for reading TriTech Software release notes and maintaining an understanding of new and existing features.
The Client should involve a fully dedicated person or persons during scheduled activities such as training sessions. Post implementation, the involvement of the subject matter experts should be limited to maintenance only. These personnel should attend the applicable product specific training courses.
4.13 IQ CrimeView & FireView Dashboard Administrator
The IQ CrimeView & FireView Dashboard Administrator(s) will be responsible for the management of the application, including users, permissions, and organization, as well as coordinating or providing any ongoing internal user training. This person or persons will be engaged in the implementation of the system and will participate in making decisions relating to its configuration.
The Dashboard Administrator will attend all of the Workshops/Trainings as purchased throughout the Purchase Agreement. This person should have a general understanding of the internal structure and workflow of the Client’s departmental policies and procedures.
4.14 IQ CrimeView Dashboard Designer
The IQ CrimeView Dashboard Designer(s) will have the responsibilities for creating and managing the application content (Widgets, Pages, Alerts, Queries on Demand, etc.) and may also be the Dashboard Administrator.
The Dashboard Designer will attend all of the Workshops as purchased throughout the Purchase Agreement.
This person should have a comprehensive understanding of the analytical needs of the department or the user group they represent.
#11..
- 770 -
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2017 TriTech Software Systems
19 5 PROJECT CONTROLLING PROCESSES
5.1 Overview
Project Controlling Processes are established early in the Project life cycle during the Planning Phase and described within the Project Management plans. Project Control is the process that includes completing regularly scheduled Project progress meetings and the use of regularly delivered Project progress reports, as well as implementing the processes needed for Communication Management, Risk Management, and Change Management. The process begins during the initiation process and concludes at the end of the Project.
The establishment of defined processes for Client communication (contact persons and reporting methods) provides a basis for effective and regular communication. This supports the previously noted processes necessary for successful Project outcome.
As part of the Controlling Processes, TriTech utilizes a series of measurements and management reviews to mitigate the effect of these variances. Checkpoints or milestones are planned into each phase of the Project to measure performance and determine if the Project is ready for the next phase.
Checkpoints are key tasks that act as gates to the next phase of a project. A delay in a milestone may cause a delay in starting or completing subsequent tasks; in effect creating a risk to the overall Project. Therefore, TriTech’s Project staff closely monitors checkpoint tasks and milestones and promptly notifies the Project Manager of any delay or failure with a milestone task. Milestone delays on the part of either party will trigger an overall review of Project activities so that risks can be assessed and properly managed. In the event that either party becomes aware of a delay, notification shall be provided to the other party as soon as reasonably possible.
Evaluation of overall Project status at each checkpoint is essential to ensure that the Project is effectively progressing toward completion and that new risks are not being introduced. In many cases, Project activities leading to a checkpoint are interrelated to later scheduled tasks. Success at checkpoints diminishes the risk to the Project going forward.
Incomplete actions at a checkpoint may prompt delays and a rescheduling of the Project. For example, delays in completing or approving Custom Interface OSDs will delay the start and completion of the Interface development work, which may ultimately have an impact on the projected Go Live date.
Depending upon the importance of the Deliverable, these kinds of delays can have a cascading effect upon the Project Schedule including training and Go Lives.
As part of the Project controlling process, upon completion of significant milestones and or tasks, TriTech will submit a Task Completion Report (“TCR”) to the Client. The TCR serves as a formal tool for the purpose of verifying with the Client that the work has been performed, services rendered, and products delivered according to the requirements specified within the SOW and/or related documents.
TCRs are presented to the Client by TriTech’s Project Manager for signature. Some TCRs may trigger a Project payment, in accordance with the payment terms within the Purchase Agreement. Upon execution of a TCR that is tied to a Project payment milestone, the Client will receive an invoice from TriTech’s Accounting Department which must be paid based on the terms and conditions of the Purchase Agreement. #11..
- 771 -
Project Controlling Processes
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
20 As the Prime Contractor, TriTech is responsible for processing TCRs for all Subcontractor activities, under the Contract.
The TCR will include the following information:
1. Description of Work performed and products delivered.
2. Comments noting any special circumstances.
3. Product/Service deliverables listing the contract line items that are being recognized as delivered and will be invoiced.
4. Related Payment Terms in accordance with the Purchase Agreement, for contract line items that will be invoiced relative to the TCR.
5.1.1 TriTech Responsibilities
a) TriTech will prepare and submit TCRs for Client’s signature upon completion of the applicable task. b) The TCR will cite the appropriate SOW reference.
c) TCRs that trigger a payment will include the payment amount in accordance with the Purchase Agreement payment schedule.
5.1.2 Client Responsibilities
a) Client will review and approve TCRs within a five (5) business day period from the time of receipt less any challenges to the validity of the report.
b) In the event that Client disagrees with a TCR, Client shall submit to TriTech a written explanation detailing why the Client believes that the subject of the TCR and/or tasks have not been completed in accordance with the Purchase Agreement or this SOW. Such notification from the Client shall be provided to the TriTech Project Manager within five (5) business days of receipt of the TCR.
5.2 Change Management Process
Either party can request changes to the scope of the project at any time. Since a change may affect the price, project deliverables, this SOW, the supporting project schedule, and/or the terms of the Purchase Agreement for this SOW, both parties must approve each change in writing and agree on the impact each change may have on the Purchase Agreement and related attachments.
The purpose of the Change Management Process is to manage any significant changes to the Project as described in this SOW or related documents as referenced within the SOW. These changes may include, but are not limited to a modification to Project scope, Standard or Custom products’ functionality, TriTech and Client’s identified roles and responsibilities, Project payment terms, and modifications to the scope or delivery location of services within the Project. All significant changes must be documented through the Change Management Process. The type of documentation needed will depend on the nature and significance of the change.
A Project Change Order will be the vehicle for communicating and approval of the changes. Whether initiated by the Client or TriTech, all Change Orders will be documented by the TriTech Project Manager. The Change Order shall describe the requested change, the party requesting the change, and the effect the change will have on the project, including the price, project deliverables, this SOW, the supporting project schedule, and/or the terms of the Purchase Agreement for this SOW.
#11..
- 772 -
Project Controlling Processes
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
21 All Change Orders must go through the TriTech’s internal approval process before they can be presented to the Client for review and approval. Once the Change Order is generated, the Client Project Manager and TriTech Project Manager will review the proposed change and communicate as necessary to answer any questions, and/or work to resolve any issues preventing acceptance of the Change Order by both parties. Upon the approval by both parties the Change Order will be authorized for implementation.
The creation of some Change Orders may, depending upon the scope of the requested change, require fees in order for TriTech to properly investigate and scope of the requested change. If additional fees are required by TriTech to create a Change Order, those fees will be identified and communicated to the Client Project Manager prior to TriTech’s investigation of the requested change. In such situations, TriTech will only proceed with the investigation required to create the Change Order if the Client has agreed to pay the additional fees associated with creation of the Change Order.
Additional deliverables or Project deletions in terms of Software and services will require a mutually agreed upon Change Order. It must be noted that the later in the Project that a change is requested, the greater the likely impact in terms of costs, risks, and timescale. It is recommended that the Client not delay any review activity as it is a best practice to discover potential changes as early as possible. In some cases, it may be more appropriate to plan modifications for post Go Live delivery.
5.2.1 TriTech Responsibilities
a) Change Orders will be prepared for submission to the Client when required. b) Where Project changes require Engineering-level modifications, TriTech will perform requirements capture necessary to prepare required documentation including a high level description of the change for Client review and approval.
c) Where Project changes require Engineering-level modifications, Client will be informed of the delivery mechanism (version and schedule).
5.2.2 Client Responsibilities
a) When applicable, the Client will identify the services or deliverables that will be subject to a Change Order, per the Purchase Agreement between both parties. b) When applicable, the Client will identify changes to features or functionality related to CAD, Mobile, RMS, Jail, Interfaces, or any other Subsystems that will require a change order. This process may also include participation with the requirements process.
c) Client will approve and process Change Orders in a timely manner.
5.3 Project Reporting
TriTech will provide Monthly Status Reports advising the Client Project Manager and key Client Project Stakeholders of the progress and status of project activities. This report will include the significant accomplishments, planned activities, issues, and potential risks associated with TriTech and TriTech’s Subcontractors’ Deliverables. The Project Status Reports will include the following:
a) Accomplishments during the Reporting Period.
b) Planned upcoming activities.
c) Issues.
#11..
- 773 -
Project Controlling Processes
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
22 d) Risks.
e) Key Action Items.
In addition, the TriTech Project Manager will hold bi-weekly status meetings/conference calls to update the Client on the status of the Project and key action items and deliverables.
During the course of the Project, one or more Project journals will be created to document Project issues and action items. These journals are generally product specific and are used by the Project Manager and other team members to facilitate successful Project completion. Project journals are reviewed with the Client during bi-weekly Project status calls and on an as needed basis through the course of the Project. The Project Manager is responsible for periodically providing copies of updated journals.
TriTech will provide an updated Project Schedule advising the Client Project Manager of the progress of project activities. The Project Schedule may be lacking the detailed tasks for the Client team, and the Client may add such tasks, owners, and durations to the Project in collaboration with TriTech Project Manager. The Project Schedule will consist of the following:
a) Major Tasks.
b) Task Responsibility.
c) Task Duration.
d) Major Milestones.
e) Tasks Completed.
f) Tasks in Progress.
5.3.1 TriTech Responsibilities
a) Provide a written report of Project status once a month. b) Track issues and action items to closure through product specific journals. The Client will be periodically provided with updated copies of the journal. c) Conduct status meetings/conference calls every two weeks. d) Maintain an up-to-date Project Schedule.
5.3.2 Client Responsibilities
a) Review the written report of Project status and provide feedback within five (5) business days in order to ensure that the documentation is correct.
b) Participate in Project status meetings.
c) Ensure participation of personnel in tasks and meetings. #11..
- 774 -
Project Controlling Processes
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
23 5.4 Document Review
In the course of the Project, TriTech will deliver several documents to the Client for review. These documents will include but are not limited to the Acceptance Test Procedure, Project Schedule, DOLF report, OSD, Training Material and Interface Requirement Documents for the Project. Approved documents are returned to the TriTech Project Manager. All documents will be provided in electronic (soft copy). If Client desires printed (hard copy) documentation, it is their responsibility to print and bind the desire copies. The TriTech Project Manager will retain a copy and provide Client with a copy.
Should the Client find any document unacceptable, the Client must provide specific reasons in writing to the TriTech Project Manager. TriTech can then assess any required corrective measures and make revisions or modifications to provide acceptable documents within a mutually satisfactory timeframe.
Status Reports are not subject to approval.
In order to ensure compliance with the Project Implementation Schedule, the Client is responsible for the review of such documents and providing any comments to TriTech within five (5) business days.
5.4.1.1 Documents Subject to Client Approval
a) Change Orders
b) Operational Scenario Documents (OSD)
c) Application Configuration Sheet
d) Functional Acceptance Test Procedure documents
e) Task Completion Reports
5.4.1.2 Documents Subject to Client Review not Requiring Approval a) Project Schedule
Note: The Project Schedule and any changes hereto are to be mutually agreed upon between the Client and TriTech.
b) Project Status Reports
c) DOLF Reports for Inform CAD, and Inform RMS
d) Interface Requirements Documents (IRD)
5.4.2 TriTech Responsibilities
a) Distribute the documents to the Client.
b) Coordinate the process to consolidate comments and edit documents. c) Manage the signoff process for applicable documents and the distribution of originals to the Client and TriTech for filing.
5.4.3 Client Responsibilities
a) Review the documents presented and provide the appropriate information back to TriTech within five (5) business days for configuration sheets, Change Orders and/or Sales Orders. #11..
- 775 -
Project Controlling Processes
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
24 b) Review the documents presented and provide the appropriate information back to TriTech within ten (10) business days for requirements documents defined above. Unless unanticipated changes to the Project Schedule would warrant a shortened turn around.
5.5 Third Party Management
TriTech will be responsible for the management of third parties that have been identified as Subcontractors or executed Change Orders to the Purchase Agreement. The identified TriTech Subcontractors under the Contract are the following:
1. Hardware Provider
As part of the Subcontractor agreement, all communications between those third parties and the Client will be managed by TriTech. Any communication directly between the Client and third parties that may require or imply the promise of a material change in scope or responsibilities will not be acknowledged by TriTech unless an appropriate Change Order has been prepared.
Conversely, the Client will be responsible for the management of third parties that TriTech is not responsible for. The Client will be responsible for the facilitation of discussions and the acquisition of materials from those third parties that are necessary for the configuration and development of the Client’s System.
5.5.1 TriTech Responsibilities
a) Assume responsibility for third parties that are the responsibility of TriTech within the terms of the Purchase Agreement between TriTech and the Client.
b) Process any Change Orders that may arise from a material change in scope where third parties are concerned.
c) Inform the Client when configuration and or programming will require interaction and/or documentation from a third party which is not the responsibility of TriTech under the Purchase Agreement between TriTech and the Client.
5.5.2 Client Responsibilities
a) Work directly through TriTech with regard to third parties that are the responsibility of TriTech. b) Review, sign and process any Change Orders that may arise from a material change in scope where third parties are concerned.
c) Facilitate interaction between TriTech and third parties not the responsibility of TriTech to include conference calls, answers to questions and documentation as requested. #11..
- 776 -
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2017 TriTech Software Systems
25 6 PROJECT INITIATION AND PLANNING
6.1 Overview
Project Initiation and Planning involves gathering the necessary Project specific information in order to produce a Project Management Plan and a Project Schedule. In short, Project Planning consists of those processes designated to establish when and how the Project will be implemented while further elaborating on Project Deliverables. Most of the information exchange between the Client and TriTech during this process is at a high level and consists of interaction between both Project Managers and a small group of Project stakeholders.
Major Deliverables for the Project Planning phase are the specific Project Management Plans, and a baseline Project Schedule.
The project must be managed in a manner that will allow for the adjusting the Project Management Plan and Project Schedule to address the circumstances that affect a project during Project Execution. As a result of these changes during the Project life cycle, Project Planning will overlap each subsequent process during the Project. Typically, Project Planning tasks will decrease in frequency as checkpoints are successfully completed and as the Project nears Go Live and Project completion.
Note: The Project Schedule is a living document, subject to change during the course of the Project due to several factors such as change in Project scope, scheduling conflicts, delay in approving project documents, resource availability, etc. All changes to the Project Schedule will be discussed between both parties and will be incorporated within a published schedule upon approval from the Client and TriTech.
6.1.1 TriTech Responsibilities
a) Assign a Project Manager to the Project to participate in Initiation phase activities. b) Produce required documentation to support Initiation activities (such as Standard IRDs, System Planning Document, etc.)
c) Review and finalize the SOW with the Client.
d) Identify and engage the TriTech Project team responsible for carrying out Project Execution. e) In collaboration with the Client, develop the Project Management Plan (includes the Communication Management Plan, Risk Management Plan, and Change Management Plan). f) Baseline the Project Schedule.
g) Prepare and submit the TCRs for Client acceptance of the Project Management Plan as defined above. h) Develop and submit invoice for payment due at execution of the Purchase Agreement.
6.1.1.1 Client Responsibilities
a) Assign a Project Manager for the Project to participate in Initiation phase activities. b) Identify and engage the Client’s Project team.
c) Review and comment on the TriTech Project Management Plan and the Project Schedule. #11..
- 777 -
Project Initiation and Planning
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
26 d) Review and comment on TriTech provided documentation to support Initiation activities. e) Finalize and approve the SOW with TriTech.
f) Approve the TCRs for the Project Management Plan within 5 business days.
6.1.2 Project Kick Off
During the planning phase, the TriTech Project Manager will hold a Kick-Off meeting with the Client’s Project team. During the Kick-Off meeting, the TriTech Project Manager will provide an overview of the following:
1. The TriTech Execution Process.
2. A high level description of Project Deliverables.
3. Roles and responsibilities for the Project team members.
4. A high level review of the preliminary Project Schedule including projected Project milestones and checkpoints.
5. Describe the work that has been either completed, is in progress or is due to begin within the immediate future.
6. Review any project related questions from the Client’s team.
6.1.2.1 TriTech Responsibilities
a) Prepare the agenda and set a date for the Kick-Off that is convenient to the Client and TriTech Team. b) Distribute any documents that the Client should review in advance of the Kick-Off meeting. c) Conduct the Kick-Off meeting.
6.1.2.2 Client Responsibilities
a) Work with the TriTech Project Manager to facilitate scheduling a date for the Kick-Off meeting. b) Schedule the appropriate personnel from the Client’s team to attend. This should also include key stakeholders that may not participate routinely in Project operations, but who have authority or responsibility over the Project.
c) Provide adequate accommodations to include adequate seating and audio-visual equipment including a projector(s), screen, and whiteboard.
#11..
- 778 -
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2017 TriTech Software Systems
27 7 PROJECT EXECUTION
7.1 Overview
Project Execution focuses on the development and delivery of Project Deliverables. Processes will be iterative and consist of: 1) a review of Deliverable documents; 2) Development, configuration, Installation and testing of software and hardware deliverables, and 3) Delivery of Project related services such as Project related training. These processes are iterative in nature with a number of checkpoints to evaluate Project progress and where applicable, to initiate Change Management processes. Each Deliverable has a closing process which consists of specific completion criteria. These Deliverable closing processes are independent from the closing process of the Project.
7.2 System Installation (Inform CAD, Inform Mobile,
Inform RMS,and Interfaces)
System installation is one of the early processes in the Project implementation phase, and has a significant impact on and critical dependency on a number of key activities. All tasks and activities related to System Installation are included in this section and will occur in the order presented. Note that other project activities can occur concurrently or between these steps.
7.2.1 Review Hardware Specifications
TriTech and Client will review the specifications to ensure that the correct hardware and third party software components are procured and installed. TriTech will only be responsible for procurement of the hardware and third party software that is explicitly listed under the Agreement as TriTech Deliverables or Deliverables of TriTech’s Subcontractors.
7.2.1.1 TriTech Responsibilities
1) Provide hardware and Third Party specifications to Client.
7.2.1.2 Client Responsibilities
1) Review and validate hardware and Third Party specifications.
7.2.2 Hardware and Equipment Procurement Process
TriTech and Client will procure hardware, third party software, and equipment per TriTech’s recommended Specifications. TriTech is only responsible for procurement of the hardware and third party software that is identified as TriTech Deliverables in the Purchase Agreement.
If the hardware and third party software is procured by the Client, it is the Client’s responsibility to procure the required equipment based on TriTech approved specifications, and to ensure the timely delivery of the hardware and third party software to the site to allow timely implementation of the System and Subsystems.
Where the Client is responsible for procuring the server hardware, the Client will be responsible for completing the following steps:
1) Fully configuring the servers with cores, memory, and disks. 2) Loading VMware and Microsoft Windows.
#11..
- 779 -
Project Execution
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
28 3) Partitioning disk drives partitioned and the implementing applicable Raid level based upon TriTech documentation.
4) Assigning the computer name and IP address based upon TriTech documentation. 5) Creating the SSL Certificates needed for each server which requires one based upon TriTech documentation
6) Providing the media and licenses for SQL Server in a location accessible by the servers.
7.2.2.1 Servers provided by TriTech
If System servers are procured through TriTech, TriTech will ensure that the hardware and third party software matches or exceeds the specifications listed in the Purchase Agreement. The following work will be completed before the server is delivered to the Client site:
1) The servers fully configured with cores, memory, and disks. 2) VMware and Microsoft Windows Operating System are loaded. 3) Disk drives partitioned and the applicable Raid level implemented. 4) The machine name and IP address assigned. (Note: The machine names will be assigned only if the servers are ordered from HP. If the hardware vendor is Dell, TriTech will not be able to assign the machine names, and this task must be completed by the Client once the servers arrive at the Client site).
7.2.3 Hardware Staging and Preparation for Installation The Client will be performing basic server integration for all servers. Basic server integration includes placing the servers in the racks, joining them to the existing domain, with the Domain Controller in place, running the TriTech pre-requisite DVD on Inform CAD and Inform Mobile servers, and establishing remote connectivity capability (VPN and Remote Desktop, or Bomgar) for authorized TriTech personnel to perform configuration. These activities will be coordinated between TriTech and the Client IT staff. Guidance will be provided by TriTech’s Client Installation Services (CIS) team as required. If the Client is not willing to complete the basic server integration, this task may be performed by TriTech or TriTech’s Subcontractors at additional cost.
In order to start configuration, the Client must provide remote connectivity to TriTech. The Client must also provide the server names, IP addresses, Administrator Account Information (User Name, Password), Services Account Information, and the location of 3rd Party Software media (such as SQL). An Installation Service Request (ISR) will be provided to the Client that organizes this information in to the TriTech preferred format. The Client is responsible for providing the completed ISR to TriTech no later than two (2) weeks prior to the installation activities.
The Client is responsible for ensuring that the site is prepared and ready for the installation of hardware, third party software, and TriTech software as detailed in TriTech’s documentation including the System Planning Document no later than two (2) weeks prior to the scheduled Installation date. Delay in providing this information in its complete form will result in a delay in the Installation and the activities that follow installation of the System.
#11..
- 780 -
Project Execution
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
29 At least one (1) week prior to installation, a member of the TriTech CIS team will verify: (1) connectivity to the Client site via VPN, (2) connectivity to each of the servers, and (3) access to all required security accounts.
If the servers, accounts and connectivity are not ready the Project may be rescheduled, which may have an impact on the overall Project timelines.
7.2.4 TriTech Responsibilities
a) Provide the System Planning Document.
b) Facilitate a hardware review prior to hardware/OS procurement. c) Procure equipment and third party software if included in the Purchase Agreement as a TriTech deliverable.
d) Provide guidance and assistance as necessary if the system equipment is procured by the Client. e) Distribute the Installation Service Request (ISR) document to the Client. f) Assist the Client in completing the ISR.
g) Review the completed ISR prior to the installation.
h) Test the remote connectivity to the site prior to installation of the hardware and software. i) Install the Microsoft SQL software.
j) Prepare and submit a TCR for Client review and approval upon completion of these activities.
7.2.4.1 Client Responsibilities
a) Complete the Installation Service Request (ISR) document and provide to TriTech. b) Prepare a network diagram and provide to TriTech.
c) Perform site preparation, as specified in the System Planning Document and ISR. d) Assign the computer name(s) and IP address(es) based upon TriTech documentation. e) Establish remote connectivity capability (VPN and Remote Desktop, or Bomgar) for authorized TriTech personnel to perform software installation and configuration. f) Run TriTech Pre-Requisite DVD on all applicable Inform servers prior to any installation work being performed.
g) Provide all horizontal and vertical cable runs, pathways, coring, access points, floor cutting or drilling, and related tasks related to cable and equipment installation. h) Provide all Client-supplied telephone, external interface connection points, electrical power and other receptacles within manufacturer recommended distance of the equipment and all peripheral components. i) Provide and install all data communication lines, modems, hubs and routers, cabling, equipment and other components necessary for system operation and maintenance and for remote sites and connection to other systems. All lines will be clearly identified and tested. j) Provide TCP/IP communications and connection to the hub equipment provided in support for any existing networks, workstations and printers that are to have access to the TriTech applications. k) Obtain all necessary IP addresses and schemes.
#11..
- 781 -
Project Execution
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
30 l) Allow remote access to TriTech to all development and system “root” accounts on all servers running TriTech licensed Software.
m) Procure equipment and third party software if it is the responsibility of the Client according to the Purchase Agreement.
n) Install operating system software, perform Windows Genuine Advantage validation, and install all Windows Updates for Client procured hardware unless the service is specified as a TriTech responsibility in the Purchase Agreement.
o) Perform basic server integration including, but not limited to:
i. Installation of servers in applicable racks.
ii. Joining servers to the existing domain with the domain controller in place. iii. If applicable, install and setup of the VM environment. p) Provide TriTech with all necessary configuration documentation which includes machine naming, IP addresses, Administrator Account information, Service(s) Account information, naming convention, and connectivity as prescribed.
q) Provide TriTech with a high-level network diagram. The diagram should be provided prior to TriTech Software installation.
r) Install all peripheral equipment, including scanners, printers, barcode readers, etc. s) Create and maintain SSL certificates for the servers which require them, per TriTech documentation. t) Approve the applicable TCR.
7.2.5 Basic Server preparation and Network Services
Performing the services listed in this section is a responsibility of the Client. If these services are explicitly included in the Purchase Agreement, TriTech or a TriTech Subcontractor will implement 3rd party software and/or hardware solutions based upon the following task list. These solutions can include but is not limited to, SAN, Citrix, VMware, and Domain Controller configurations. These services can be performed on site or remotely via a VPN connection. These services will be performed at additional cost to the Client and are not included in TriTech’s standard installation services.
7.2.5.1 Client Responsibilities
a) Provide the facility suitable to house Server hardware and network infrastructure. b) Have a member of the Client’s IT staff available while software/network configuration is being performed.
a) When deploying a SAN, configure the applicable RAID configuration, create the LUN(s) and present them to the physical or virtual servers.
b) If the VM servers are not procured through TriTech, the Client is responsible for building individual servers.
c) When deploying a VMware solution, install the VMware operating system, connect physical host servers to a SAN if applicable, configure vCenter, create a VM Template for Interfaces and business servers, and configure vMotion and High Availability (HA) if applicable. The Client is also responsible for building individual VM servers.
#11..
- 782 -
Project Execution
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
31 d) If required, deploy the Domain Controller by adding the member server to an existing Domain or create a new Domain, promote the member server to Domain Controller, enable and configure DNS, enable and configure DHCP if required.
e) Create domain account(s) for TriTech’s remote support connectivity and access so that TriTech can assist Client with installation and ongoing maintenance f) Perform all necessary network configurations, to include but not limited to determining the network design routing protocols, subnet mask, redundancy, router and switch configuration. g) Create Networking/Server documentation to illustrate intended configuration.
Note: VMware, vMotion and HA require a SAN or a way to present shared storage to the physical host servers in a VMware virtual farm.
Note: Network and Server security are always a responsibility of the client.
7.2.6 System Installation
Once TriTech and the Client have prepared the site based on TriTech documentation, to include the System Planning Document and the applicable ISR form is completed, a TriTech Client Installation Services specialist will perform the TriTech installation services.
These services will be performed remotely, unless otherwise specified in the Purchase Agreement, and include installation of the contracted TriTech Software products on the quantity of servers and workstations as specified in the Purchase Agreement.
These installation activities will be coordinated between TriTech and the Client.
Note 1: All SQL server licenses will be installed by TriTech. The Client is responsible for making the media and license keys available to TriTech for the installation.
Note 2: The Installation services for different components of the System may be performed at different times, based on the implementation and deployment timelines for each Subsystem.
Note 3: The scope of installation services and the number of servers and workstations to be installed and configured by TriTech is limited to the servers and workstations that have been explicitly listed in the Purchase Agreement. If the Client has been granted Site Licensing for selected TriTech Software, TriTech is only responsible for the initial installation services, and installation of additional servers will be subject to additional charges. #11..
- 783 -
Project Execution
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
32 Note 4: If Client does not follow the processes and procedures detailed in the TriTech System Planning Document and this results in a need for reinstallation of the hardware or software, the reinstallation effort will be performed at additional cost to the Client.
Note 5: At TriTech’s discretion, TriTech may perform installation activities for certain components of the system on-site.
The following pre-requisites must be in place prior to the start of TriTech Software installation:
a) Site preparation is complete as outlined in the sections above. b) Hardware has been installed at Client site.
c) Client has provided TriTech with remote connectivity to all applicable servers. d) All SSL Certificates required for operation must be created per TriTech documentation. e) Client had provided TriTech all relevant documentation as outlined in the sections above to include licensing keys, IP addresses, username/passwords, and the completed ISR.
7.2.6.1 TriTech Responsibilities
a) Install and configure Microsoft SQL to operate with each of the applicable TriTech product(s). b) Configure the System servers in the applicable environments (Production, Test, Training, and Disaster Backup environments, if provisioned by the Purchase Agreement). c) Install and configure the applicable TriTech system(s), such as Inform CAD, Inform RMS, and Inform Mobile on the designated servers and applicable environments as specified in the Purchase Agreement. d) Provide verbal support to the Client with self-installation procedures for the workstations using the TriTech provided Prerequisite Installation DVD and applicable Launch configurations. e) If applicable, create data dumps for Microsoft SQL database backups (as a backup for Inform RMS databases).
f) After completion of the initial installation and configuration of each major System (such as Inform CAD, Inform RMS servers), a member of Technical Services team provides a technical hand-off to designated staff from the Client’s information Technology team via a conference call. The following major topics will be discussed during this technical hand-off:
i. Proper procedures for performing System Backups:
o File Structure – Inclusions and exclusions
o Databases
o Moving Backups to media
ii. Proper procedures for refreshing Test/Training system (and related documentation) iii. Approved configuration and use of Virus Scan software iv. Approved procedure for application of Windows updates #11..
- 784 -
Project Execution
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
33 v. System Upgrade process and procedures
vi. Support Website and TriTech list server access
vii. Managing/Reviewing system logs (CAD, SQL and Event Logs) g) Prepare and submit a TCR upon completion of the installation tasks and activities.
7.2.6.2 Client Responsibilities
a) Allocate appropriate onsite Project personnel to support TriTech personnel during configuration tasks as necessary and designate a primary point of contact to be available to address and answer questions that arise during the installation of the baseline application software. Appropriate Client personnel include the necessary IT personnel and database administrator(s) as needed during installation. b) Complete the configuration of workstations (after the installation of the limited number of workstations by TriTech) using the Prerequisite Installation DVD and applicable Launch configurations. c) Put in place TriTech’s recommended backup procedures as outlined in the System Planning Document and ensure backup procedures are consistently followed beginning at the completion of this task. d) Install and configure virus scanning software as outlined in the System Planning Document. e) Provide SSL Security Certificates for all TriTech web-enabled applications that require a certificate, configured per TriTech documentation.
f) After completion of the initial installation and configuration of System servers, the Client will be responsible for maintaining the System based on TriTech System Document, and the technical hand-off from TriTech Technical Services department. Specifically, the Client’s IT staff is responsible completing the following activates related to Inform Subsystem servers:
o Updating Training/Test Systems with fresh data (from Production) as needed o Continued updating and monitoring of virus scan software o Application of Windows updates
o Following the procedures for System Upgrade
o Managing/Reviewing system logs (SQL and Event Logs)
o Management of Microsoft and other Third Party Software include patch applications and upgrades as needed for new Subsystem versions.
o Deployment and use of the Prerequisite Installation DVD for Subsystem upgrades as required.
g) Review and approve the applicable TCRs.
7.3 Implementation of Inform CAD
Inform CAD is implemented through a series of standard steps and process gates. These steps are designed to ensure that the operational needs of the Client are identified, the configurations are verified, and the system is tested to validate the proper functionality of the system prior to deployment. The following sections describe the implementation process for Inform CAD.
#11..
- 785 -
Project Execution
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
34 7.3.1 Inform CAD System Orientation
The Inform CAD System Orientation is conducted at the Client’s site and led by a TriTech Business Analyst.
The duration of the Inform CAD System Orientation is generally up to four (4) days and includes a Business Process Review of the Client’s operations. This System Orientation can be conducted in conjunction with Inform RMS if purchased together.
Some key discovery points for the Inform CAD System Orientation are as follows:
a) Work Flow – Understanding the setup for work flow from first receipt of an incident through incident completion. This may include time observing Dispatch Staff and Ride-Alongs with field units. b) Agency Type Setup – The segmentation of operational processes including incidents, units, and calltaker/dispatcher roles and responsibilities. c) Review reporting requirements (geographic reporting segmentation and the like). d) Event numbering (Incidents) including master incident numbers, response numbers and case numbers.
It is recommended that the number of attendees in the System Orientation is limited to 10-15 to allow for more effective communication during the session. Based on the key discovery points during this session, it is necessary that the attendees include individuals who can properly address these key points and make configuration decisions.
During the System Orientation session, the Business Analyst will facilitate an operational review of Inform CAD by demonstrating various System functionality and start gathering the configuration information.
A System Module Setup worksheet (SMS) and other reference material will be provided to the Client to assist in gathering the required Code Files. Information that cannot be produced during the meeting must be sent to TriTech as specified by the mutually agreed upon schedule.
Note: The Client’s provision of Code File information is an early Project checkpoint. Remote Web sessions will be scheduled as a follow up to System Orientation to guide the Client through the Code File data collection process. This information is needed to prepare the DOLF and incomplete, inaccurate or delayed Code File information can have a cascading effect on the Project Schedule.
7.3.1.1 TriTech Responsibilities
a) Schedule the System Orientation meeting in accordance with the Client’s availability and the Project Schedule.
b) Prepare and distribute the meeting agendas and documents for Client review or completion two weeks prior to each meeting.
c) Conduct the meetings based on the distributed agenda. d) Document the Client’s requirements and configuration specifications resulting from the System Orientation discussions.
e) Send the System Module Setup worksheet (SMS) and other reference material to the Client. #11..
- 786 -
Project Execution
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
35 f) Document and assign owners and due dates to any action items and track all action items to closure. g) Document any gaps between the standard functionality of the System and functionality required by the Purchase Agreement for further analysis and discussion and/or facilitate the change control process.
Client requested changes for changes beyond the scope of the Purchase Agreement will be evaluated at this phase, but will have to be evaluated for the potential impact on the Project Schedule and for additional project charges to be paid by the Client.
h) Schedule one or more Remote Web sessions as a follow up to System Orientation to guide the Client through the Code File data collection process.
i) Produce a System Orientation Report with the key decisions and configuration points as a result of the System Orientation.
j) Prepare and submit a TCR upon completion of relevant activities.
7.3.1.2 Client Responsibilities
a) Provide adequate facilities to comfortably hold the System Orientation to include a computer projector, whiteboards, and adequate seating. Two projectors are preferred. b) Ensure participation of key stakeholders and decision-makers in the System Orientation process. a) Provide subject matter experts that can explain the communication center’s current call flow and agency structure. These persons should have the ability to make decisions regarding any changes in work flow that may arise through the use of the new Inform CAD System. c) Provide subject matter experts with the ability to gather and provide the data elements used to build Code Files to TriTech.
d) Provide subject matter experts that will be able to explain the agency’s geopolitical/operational boundaries. This person (or persons) should be able to articulate the specific response requirements that will be built within CAD response plans.
e) Provide subject matter experts that will be the CAD super users, as well as a person or persons that will be responsible for the ongoing maintenance of the CAD Code Files and configuration (CAD Administrator).
f) Provide subject matter experts that will be responsible for translating the geopolitical/operational boundaries into data (ESRI shape files) suitable for use within the CAD. g) Provide subject matter experts that will be responsible for the maintenance of the agency’s street centerline data.
h) Provide subject matter experts that can provide information on technical Systems (Interfaces and Hardware/Network) or field-related functions (Inform Mobile or other mobile systems, station alerting and the like).
i) Review and approve applicable TCRs.
7.3.2 Inform CAD Base System Code File Entry
After completion of the Inform CAD System Orientation and receiving requested data from the Client, the assigned TriTech Business Analyst will start and supervise the initial Code File building process. The Business Analyst also configures the system hierarchy based on Client’s call flow and operational processes as defined in the System Orientation. The Client will be actively involved at each step of the Code File configuration process through periodic reviews including conference calls and remote web sessions. #11..
- 787 -
Project Execution
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
36 A Code File review is completed prior to TriTech initiating the Code File entry process. The review is initiated via one or more web meetings as the Client submits the requested Code File information. The Code File review validates the accuracy and completeness of the information and ensures that there is a mutual understanding of how the information is to be used within Inform CAD.
TriTech will complete the Code File entry for Inform CAD System to a level that will allow for an evaluation of call flow and incident management. Code file build to the level described in Appendix A - Required Inform CAD DOLF Code File build of this SOW establishes a foundation that will validate basic functions such as call-taking layout, System hierarchy, incident numbering, and Incident/Unit displays.
Validation through the DOLF process allows for the completion of Code File setup while limiting the risk of rework. This task is considered to have been completed when the Business Analyst has demonstrated that Code Files are complete to the level documented in Appendix A - Required Inform CAD DOLF Code File build.
TriTech personnel will participate in the Code File building process. Some Code Files that require local knowledge of the geography and the physical location of business and high-risk areas of the community (such as response plans, premise, and caution note/hazard information) cannot be built by TriTech. The Client will be responsible for entering or geo-verifying some Code File elements such as premises. The Code Files prepared by TriTech and the Code Files prepared by the Client are described in Appendix A - Required Inform CAD DOLF Code File build. The responsibility for building and maintenance of the System Code Files will transfer to the Client after DOLF with assistance from TriTech’s Business Analyst.
7.3.2.1 TriTech Responsibilities
a) Monitor and evaluate Code File submitted by the Client and provide guidance as needed. b) Conduct one or more web meetings to validate the completeness and applicability of Client submitted Code File information, prior to initiating the Code file entry. c) Perform a preliminary Code File build of the Client’s Inform CAD System at TriTech. This Code File build will be completed based upon the applicable requirements described in Appendix A - Required Inform CAD DOLF Code File build.
d) Facilitate updates to the System Module Setup (SMS) building sheet. e) Prepare and submit a TCR to confirm the delivery of the SMS worksheet by the Client.
7.3.2.2 Client Responsibilities
a) Provide timely input and updates to the SMS sheet to support the Code File building timelines. b) Participate in the Code File validation conference call. c) Continue building the System Code Files (those not built by TriTech) after DOLF (refer to Appendix A - Required Inform CAD DOLF Code File build).
d) Review and approve applicable TCRs.
#11..
- 788 -
Project Execution
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
37 7.3.3 Geographical Information Services
7.3.3.1 Data Evaluation
The TriTech GIS Analyst will work with the Client to perform a one-time evaluation and initial conversion of the Client provided street center-line GIS data. GIS data must be from a single integrated source when delivered to TriTech for conversion. This analysis will include the following:
a) Routing and Navigability - The data will be analyzed to ensure that there are no breaks in the road network and that an acceptable percentage of addresses2 within the service area are routable with
impedances or speed limits, applicable turn restrictions (one way data), elevations for overpasses and street types.
b) Addressing – Evaluate data for the presence of block ranges, street types, and city designators. c) Supplemental Coverage - An evaluation of GIS data that may be available for response areas, ESRI compatible overlays including satellite image, and applicable point data to ensure compatibility.
A report will be presented to the Client upon completion of the GIS analysis prior to the import of GIS data into one or more Systems or Subsystems. If there are significant problems with the data, additional GIS work and analysis may have to be added to the project via Change Order. Additional project costs may apply.
NOTE: Data evaluation only applies to Custom Map conversions of Client supplied data. Standard mapping conversion (TeleAtlas data) is limited to converting source mapping data from one of the standard mapping data providers and must also be provided by the Client.
7.3.3.2 TriTech Responsibilities
a) Evaluate Client-supplied GIS data to ensure it is formatted correctly for street-centerline display, address point usage and address functions. A report will be generated based on this analysis. b) Evaluate Client-supplied GIS data to ensure it is formatted correctly for routable functions. A report will be generated based on this analysis.
c) Evaluate Client-supplied GIS data to ensure it is formatted correctly for Inform CAD Quickest Path Unit Recommendations functionality.
d) Review the Client-supplied GIS layers for Inform CAD and Inform Mobile for viewing and execute the initial basic map configuration.
e) Provide a report which summarizes the findings from applicable GIS analysis services for CAD only. f) Prepare and submit a TCR upon delivery of the GIS analysis report.
7.3.3.3 Client Responsibilities
a) Provide data in the required format, and per Project Schedule. b) Provide data to include 1) Centerline data; 2) response areas; 3) viewable/cosmetic layers. c) Based on the analysis report provided by TriTech, make needed changes to mapping data to allow the resulting GIS data to meet TriTech’s mapping data requirements. d) Review and approve the appropriate TCR.
2 The phrase “acceptable percentage” refers to a decision that the Client must make regarding the acceptable level of navigability needed within the street centerline network. Since editing and maintaining the street data is a Client responsibility, the Client will have to evaluate and make a judgment regarding the impact of the level of accuracy and the cost associated with increasing the navigability of the data.
#11..
- 789 -
Project Execution
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
38 7.3.3.4 Mapping Data Conversion and Import
TriTech will perform a Mapping Data Import that provides maps for the Inform CAD system. This process does not include making any corrections to the Client GIS data. If the GIS data consists of data from more than one source, TriTech will not be responsible for joining these areas, or “stitching” the areas to create a uniform geographic area.
7.3.3.5 Configuration of Mapping Layers
A TriTech GIS Analyst will configure up to 7 standard GIS layers each for viewing on Inform CAD and Inform Mobile. Such conversion activities will be part of the training process to allow the Client to add their own layers to the map displays in Inform CAD and Inform Mobile. Additional conversion work by TriTech staff is an additional charge and must be authorized by the Purchase Agreement or a Change Order. The standard layers are limited to the following:
1- Water line features (rivers, streams, creeks)
2- Water polygon features (ocean, lakes, ponds)
3- Airports
4- Railroads
5- Parks
6- City Boundaries
7- County Boundaries
7.3.3.6 Response Area Import Service
If the Client provides Response Area data to TriTech at the time of CAD map conversion, TriTech GIS Analyst will import the Response Areas into Inform CAD. GISLink training will provide the Client with the capability to add, delete, or modify Response Areas for ongoing GIS maintenance.
7.3.3.7 TriTech Responsibilities
a) Provide the initial configuration services to enable use of Inform CAD Quickest Path Unit Recommendations functionality.
b) Perform a mapping data conversion and import of the Client-supplied data into applicable licensed Systems and Subsystems.
c) Provide the initial configuration services to enable use of Inform CAD Quickest Path Unit Recommendations functionality.
d) Prepare and submit a TCR upon completion of the mapping conversion activities.
7.3.3.8 Client Responsibilities
a) After initial GIS conversion, assume responsibility for updating the data using TriTech provided GIS tools to ensure that data is up to date for Go Live.
b) Review and approve the applicable TCR.
7.3.4 Inform CAD Demonstration of Licensed Functionality (DOLF) Once the initial Code File and configuration phase is complete, CAD is installed at the Client site, and the initial GIS map conversion is complete, a Demonstration of Licensed Functionality (DOLF) is conducted.
This working meeting includes a review of the preliminary Code Files and configuration, a review of imported GIS data, and hands-on training on software utilities for completing the Code File build and on- #11..
- 790 -
Project Execution
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
39 going Code File management. The DOLF for Inform CAD will be 4 days and will be held at the Client’s facilities on the Client’s system hardware after it has been configured by TriTech.
Client will be responsible for supplying the requested data to TriTech no later than four (4) weeks prior to DOLF to allow sufficient configuration time. The data will be requested as a follow up to the System Orientation for the Inform CAD. The configuration of some CAD modules may be delayed based on the Client’s decision, and consultation with TriTech Business Analyst.
It is also required that the Client’s centerline conversion be completed at no later than four (4) weeks prior to DOLF. In order to meet this deadline, all GIS data must be delivered to TriTech in required format per the agreed upon schedule. Any delays will result in a cascading effect on the project timelines.
Participants include key members of TriTech’s implementation team and should not generally exceed ten (10) core members of the Client’s implementation team. The Client’s team should include representatives of dispatch, field operations and administration (reporting). At the conclusion of the session, a DOLF report is produced which documents the core software configuration, Code Files, and activities to be completed by the Client. Any issues that require follow-up action, including any outstanding Go Live issues will be documented in the applicable Project journal. Any issue that is determined to be outside the scope of this Project, as defined herein, requiring a modification or enhancement to the TriTech Software will be addressed through the Change Control process.
In preparation for the execution of the DOLF, the Client system should be built to a level that will allow for the demonstration of modules and features that the Client has licensed. The Code Files completed preDOLF are defined in Appendix A - Required Inform CAD DOLF Code File build. Based upon this level of Code File build, system functionality and workflow will be examined during the DOLF.
Additional Code Files (as specified in Appendix A - Required Inform CAD DOLF Code File build) will be configured during the DOLF.
Following the DOLF process, ownership of Code Files transfers to the Client. Post DOLF, the Client will enter the balance of the Code Files (not built by TriTech). These are typically geo-centric items that require local knowledge of the community. The Client also becomes responsible for maintaining Code Files (personnel, unit, premise, caution notes and the like) that must be continuously updated to keep the Code Files in GO-Live ready status. During this phase, the assigned TriTech Business Analyst will provide consultation services.
Note: Inform CAD DOLF is an event applicable to Inform CAD only. No other Systems or Subsystems will be demonstrated during this session.
7.3.4.1 TriTech Responsibilities
a) Schedule the DOLF meeting in accordance with the Client’s availability and the Project Schedule. b) Prepare and distribute the meeting agendas to all required attendees a week prior to each meeting. c) Conduct the meetings based on the distributed agenda. d) Provide initial hands on training on the applicable system and introduction to different modules and their configurations.
#11..
- 791 -
Project Execution
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
40 Note: This training is not meant to be comprehensive for end user understanding of the Subsystem.
The purpose is to give the participant an understanding of basic features, call flow and how the configuration files influence them.
e) Review the maps for Inform CAD.
f) Introduce the Client to and begin documentation within the Subsystem Journal. g) Document and assign owners and due dates for any action items and track all action items to closure. h) Develop and deliver the DOLF report which serves as an “as built” document describing the build of the system following the DOLF.
i) Handoff the management the Code Files to the Client. j) Provide the Client team with a copy of the Inform CAD User and Administration Guides. k) Prepare and submit a TCR upon completion of the DOLF, and upon delivery of the DOLF report to the Client.
7.3.4.2 Client Responsibilities
a) Provide adequate facilities to comfortably hold the DOLF to include an overhead projector. Two projectors are preferred. DOLF also requires workstations for each participant. b) Provide subject matter experts that can examine the hierarchy build as articulated to the Business Analyst in terms of the agency structure.
c) Provide subject matter experts that can examine the proposed call flow. These persons should have the ability to make decisions regarding any changes in call flow that may arise through the use of the new Subsystem.
d) Provide participants that are versed with the ability to continue the configurations, or Code File build once ownership transfers.
e) Provide participants that will be able to verify the agency’s geopolitical/operational boundaries. f) Provide participants that were responsible for translating the geopolitical/operational boundaries into data (ESRI shape files) suitable for use within the Subsystem, and are able to validate those boundaries. g) Provide participants that will be responsible for the maintenance of the agency’s street centerline data. h) Assume ownership for the continued build and maintenance of the system under the guidance of the TriTech project team.
i) Ensure participation of key stakeholders and decision-makers in the DOLF process. j) Observe the change control process for any requested software changes. k) Review and approve the applicable TCRs.
7.3.5 Inform CAD Workshop(s)
After the Inform CAD DOLF has been completed, the TriTech project team will conduct one or more Inform CAD workshops either remotely or at the Client site. This session is intended to be an extension to the Inform CAD DOLF for more complex implementations and multi-jurisdictional agencies as specified in the contract. Each Inform CAD workshop will be up to four (4) days onsite. If the Project includes multiple Workshops, they may or may not be scheduled to occur over consecutive weeks. #11..
- 792 -
Project Execution
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
41 The Project includes:
Two (2) Inform CAD Workshops
7.3.5.1 TriTech Responsibilities
a) Schedule the Inform CAD Workshop in accordance with the Client’s availability and the Project Schedule.
b) Prepare and distribute the meeting agendas and documents for Client review or completion to all required attendees two weeks prior to each meeting.
c) Conduct the meetings based on the distributed agenda. d) Prepare and submit a TCR upon completion of the workshop.
7.3.5.2 Client Responsibilities
a) Provide adequate facilities to comfortably hold the training activities. b) Ensure participation of the appropriate personnel.
c) Continue the code file building activities after completion of this training. d) Review and approve the applicable TCR.
7.3.6 Inform CAD Functional Acceptance Testing (FAT)
TriTech will execute the Functional Acceptance Testing (FAT) of the Inform CAD, after DOLF and prior to User Training. This process is completed prior to Final Acceptance of the System. The purpose of the FAT is to test specific functionality of the CAD System and to formally document that the Inform CAD meets the required functionality according to the Purchase Agreement between the Client and TriTech.
Note: Functional Acceptance Testing for Inform CAD will occur one time, at one location. For projects that will place Subsytems for agencies and/or PSAPs in multiple phases, FAT will only be conducted for the first phase going into Production, and will not be repeated for subsequent phases. The Client must ensure that appropriate representation from various agencies and/or PSAPs attend the FAT for each Subsytem.
Since the focus of the Functional Acceptance Testing is the functionality of the System and not a validation of the Code Files, it is not necessary that all Code Files are built prior to conducting this test process. This Functional Test process consists of running a number of tests designed to verify the functionality of the Inform CAD.
The Functional Acceptance Tests are performed based upon standard TriTech FAT documents that have a standard content and format. The standard TriTech FAT documents will be submitted to the Client prior to testing.
Before the FAT is administered the Client must sign-off on the receipt of the standard FAT documents and verify that these tests will be used of validation of the System functionality for Pre-Production and Post Go Live assessment of features for Software Acceptance.
#11..
- 793 -
Project Execution
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
42 After delivery of the Inform CAD system to the Client’s site and completion of DOLF, a TriTech Business Analyst will conduct the FAT on the Client’s Inform CAD system, at the Client site on the Client System hardware. The purpose of this process is to validate that Inform CAD features are working correctly per Standard System functionality as described in the FAT documents. The testing will be fully completed and problems with individual tests will be documented, if applicable.
This process tests Inform CAD features as installed and configured at the Client site, therefore it is important that this process is executed early within the implementation cycle so that any issues discovered may be resolved. Since installation of the hardware is a predecessor to conducting the FAT, any delays to the installation of the Client’s system could impair TriTech’s ability to resolve issues without affecting project timelines. Other significant tasks and processes are dependent upon the Inform CAD passing the FAT process. TriTech will not train the Client’s end users until the Inform CAD has passed the FAT.
Once the FAT has been successfully completed the Client’s Inform CAD system will have been considered to have completed Pre-Production Acceptance (see note below). A TCR will be submitted that affirms that the Inform CAD has passed this test. Upon completion of FAT, the Client and TriTech will review the list of FAT failures (if any), perform an assessment of the errors, and determine the timeline for remedying the issues (pre versus post Go Live).
TriTech will repeat any failed FAT test following the correction of any issues which has caused the test to fail. A full retest of the System will not be conducted to verify the FAT exceptions.
Note: TriTech may organize at its discretion, separate breakout FAT sessions for subsections of the FAT documents that are applicable only to one agency (for example, applicable only to Law or Fire agencies). Each test will be executed once, and all applicable users and agencies must attend the FAT session and observe the tests.
Note: Successful completion of the FAT as part of the Pre-Go Live testing process does not constitute Final System Acceptance if such a Post-Go Live Reliability Testing is defined in the Purchase Agreement.
7.3.6.1 TriTech Responsibilities
a) Deliver TriTech’s standard FAT documents to Client for review no later than two weeks prior to conducting the FAT.
b) Provide a TCR to the Client to approve the receipt of the FAT documents. c) Assist the Client in conducting FAT based upon the FAT documents. d) Identify and document any issues and exceptions discovered during the Acceptance Test Procedures e) Upon successful completion of the FAT, provide a TCR to the Client, to be signed and returned to TriTech. All FAT exceptions will be noted in the TCR.
f) Schedule follow up testing for validation of any exceptions to the FAT after such exceptions have been resolved, and document the results.
7.3.6.2 Client Responsibilities
a) Work toward the timely completion of all predecessor tasks to include the base system installation. #11..
- 794 -
Project Execution
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
43 b) Provide adequate facilities to execute the FAT.
c) Review and signoff on the FAT documents that have been delivered by TriTech no later than one week prior to commencement of the FAT. (through approval of a TCR) d) Participate in the FAT by providing operational subject matter experts that have the authority to provide validation that the tests have passed.
e) Assist TriTech in documenting FAT findings and results. f) Review and approve the applicable TCRs.
Note: Inform CAD User Training may only be conducted after successful completion of the FAT, and if the identified exceptions are not critical in nature. The details of Inform CAD related training is included in later sections of this SOW.
Note: If included in the Purchase Agreement, the Post-Go Live Reliability Acceptance Period is described later in this Section.
7.3.7 Inform CAD Legacy Data Conversion
TriTech will implement a structured methodology for Inform CAD data conversion. The Client is responsible for providing TriTech with extracted data in a format that can be used by TriTech for import.
Formats suitable for import into can include Excel, MDB, CSV, and ODBC access from MS SQL; however, the specific format to be used for this Project should be reviewed between the respective TriTech and Client teams.
This Project provides the following Legacy data conversion services for Inform CAD:
1) CAD Premise Conversion
2) CAD Caution Notes Conversion
3) Two (2) years of CAD Historical Incident Conversion.
The conversion of prior CAD data is a process that involves several steps. TriTech develops a data conversion plan to the Client detailing the data mapping between the legacy System and TriTech Inform CAD. During this phase of work, TriTech will work closely with the appropriate individuals from the Client to map each data element in each legacy application to the appropriate target data element in the Inform CAD databases and reflect this information in the data conversion plan.
Generally, there is an initial conversion to bring the data set close to Go Live, a second conversion just before Go Live and a last conversion after Go Live. Each step does not involve a re-conversion of previously converted data. These steps do not include ongoing maintenance of imported data. The scope of data conversion is limited to converting the Premises, Caution notes, Incidents and units. As long as the legacy data elements have a relevant counterpart in the target Inform CAD databases, TriTech can map the data and import it into the Inform CAD database structure.
Conversion of Premises and Caution notes can be performed independent from the Prior Incident data. A small sub-set of the data will be initially converted and loaded to validate the process. Upon successful completion of this test, the Premise and Caution notes data will be converted and imported to the system #11..
- 795 -
Project Execution
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
44 close to Go Live, as a onetime process. Additions to Premises and Caution notes in the old system, between the time of data conversion and Go Live will be manually entered to the new system.
It is imperative that a member of the Client’s staff be available to support the data conversion effort. Many operational questions will arise that depend on the data and operational expertise of the Client’s staff.
This process is considered complete once the last set of data has been converted for the new Inform CAD system. The Client is responsible for the validation of the data.
Note: Legacy data conversion will not include conversion of attachments to Premises or Historical Incidents into TriTech databases.
7.3.7.1 TriTech Responsibilities
a) With assistance from the Client, define a data mapping for each legacy application. b) Work with the Client to plan the data migration and develop a data conversion plan. c) Complete the data conversion, based on the defined scope of the Project and based on the phases that are defined for this process.
d) Prepare and submit a TCR upon completion of the initial data conversion (pre-Go Live). e) Prepare and submit a TCR upon completion of the final data conversion (Post-Go Live).
Note: TriTech does not perform data scrubbing or cleaning on the Client’s legacy data.
7.3.7.2 Client Responsibilities
a) Identify all legacy applications containing data that must be migrated to the new System. b) Extract the entire data and provide it to TriTech based on the requirements set forth by TriTech. c) Perform any data cleaning and modification activities that may be necessary prior to conversion of the legacy data into Inform CAD.
d) Assist TriTech in defining a data mapping for each legacy application by providing the following:
e) Legacy application software architecture (operating system; application software; database management system)
f) Database schema (if data resides in a DBMS) or file layouts (if data resides in flat file formats) g) Data definition for each data element (data format, description of data field use, etc.) h) Data relationships between data files and data elements i) Obtain cooperation from any third party vendors for the legacy application that may have an impact on the data conversion process.
j) Perform validation for the data conversion.
k) Review and approve the applicable TCRs.
Note: Due to the need for specific knowledge of the Client’s area, the geo validation process for the converted data is the responsibility of the Client.
#11..
- 796 -
Project Execution
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
45 7.3.8 Inform CAD Training
Note: Training classes are conducted based on the quantities that are specified in the Purchase Agreement. The appearance of a course description in this Statement of Work does not mean a course will be conducted – it must be listed in the Purchase Agreement.
Inform CAD Training classes are conducted on consecutive weekdays during business hours (TuesdayFriday, during business hours). Alternate training schedules (e.g., Monday class starts, multiple classes per day, evening and weekend classes) will be subject to an additional charge.
The training classes related to Inform CAD and its subsystems are classified into three general groups:
a) Classes that are dependent upon specific Client configurations and requirements; therefore, they are only conducted on the Client System after completion of the Functional Acceptance Test (FAT) and in preparation of Go Live. Inform CAD Call Taker/Dispatcher User Training Course is an example of these classes.
b) Classes such as GISLink that are delivered to a specialized group within the Client’s team during the course of the Project to assist them with implementation and maintenance of the System on a routine basis.
c) Classes such as System Administration Training and CAD API Training that are not dependent upon individual Client configurations and are generic in nature. These classes are held at TriTech facilities based on a regular schedule, and are offered to attendees from different agencies.
The Inform CAD Demonstration of Licensed Functionality (DOLF) session is not listed as a training class, but includes certain training elements on the CAD setup utilities.
A detailed description of these classes is provided below.
7.3.8.1 TriTech Responsibilities (for all Inform CAD training activities) a) Conduct a training orientation via conference call between the assigned TriTech Training personnel and the designated Client representative. The objective of this session is to define the curriculum for the Training, based on the configurations of the Subsystem. b) Conduct the training in increments of one (1), eight (8) hour days. c) Provide feedback to Client Supervision as to the progress of the students. d) For the Training classes that are held at TriTech, provide adequate training facilities and equipment. e) Prepare and submit a TCR upon completion of each class or group of consecutive classes.
7.3.8.2 Client Responsibilities (for all Inform CAD training activities) a) Participate with the training orientation by providing a decision maker that can articulate the specific business practices that have been used in guiding the build of the Client’s System. b) Provide adequate facilities for the execution of the training to include adequate seating for each workstation and an overhead projector.
c) Provide a supervisor for each class that can answer agency specific questions as related to the build of the Client’s system.
#11..
- 797 -
Project Execution
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
46 d) Review and approve the applicable TCRs.
7.3.8.3 Inform CAD Call Taker/Dispatcher User Training Course (Client site) The Inform CAD User Training course is a four (4) day class, and training days are a maximum of eight (8) hours in length. Prior to training, TriTech will hold a training orientation to develop an Inform CAD training plan for the Client. This plan will take into consideration the multi-agency and multi-site setup of the System. The training orientation should be held between TriTech Training personnel and designated Client personnel. Client personnel should include person(s) who can articulate the specific Client business processes related to configuration of the Client’s System. TriTech Training personnel will tailor the training curriculum to include those business practices where applicable. Given that questions may arise for specific agency procedures during the course of the training, TriTech recommends that the Client have a supervisor present at each training class. Ideally, this supervisor would have participated in part with the implementation process.
Training classes will start on a Tuesday, and end on Friday. The number of students attending the User Training course will be limited to ten (10) students per class.
This class will be held at the Client’s site. The Client is responsible for providing adequate training facilities, including a conference room with adequate space and seating/conference table space, white board, projector, and computer projector (capable of 1024x768 resolution).
7.3.8.4 Inform CAD Dispatch Supervisor Training (Client site) The Inform CAD Dispatch Supervisor Training class has been designed as a five (5) day class that includes a four (4) day Inform CAD Call Taker/Dispatcher User Training followed by a one (1) day Inform CAD Supervisor training. This class is designed for the Dispatch Supervisors with the goal of preparing them to support the users after Go Live by answering their questions and addressing post-Go Live common problems. This class will include topics such as PowerLine configuration, Premise building and maintenance, Personnel maintenance, Vehicle Manager, and other areas that may require assistance from the supervisors. This class is recommended only for the supervisors.
This class will start on a Monday, and end on a Friday, and the class size will be limited to ten (10) students.
7.3.8.5 Inform Administration (CAD Code File Management) Training (Client Site) The focus of this three (3) day course is to prepare selected Client personnel to manage Inform CAD Code Files using Inform CAD utilities.
Students will learn how the Code Files interact within the System and how to make necessary changes. This includes evaluating their current set up and options to optimize their System. TriTech strongly recommends that a test or training system be used for this course.
Training classes will start on a Tuesday, and end on Thursday. The number of students attending the User Training course will be limited to ten (10) students per class.
This class will be held at the Client’s site. The Client is responsible for providing adequate training facilities, including a conference room with adequate space and seating/conference table space, white board, projector, and computer projector (capable of 1024x768 resolution).
Prerequisites: Completion of Inform CAD Dispatcher/Call Taker User Training. #11..
- 798 -
Project Execution
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
47 7.3.8.6 GISLink Utility Training Course (Client site) The focus of this course, conducted at Client’s site, is to prepare selected Client personnel to import and use existing GIS data in Inform CAD and manage the GIS data used by Inform CAD and Inform Mobile.
GISLink is an Inform CAD Utility that provides a way for Clients to intelligently import Client GIS data into the Inform CAD databases. It consolidates GIS data related tools for maintaining and using GIS data in TriTech products. It consists of a Windows Forms application, a command line console application, and a programming API that consists of a set of reusable publicly exported classes and methods.
Training classes will be conducted between Tuesday and Thursday, based on mutual availability of the TriTech and Client staff. Training course will be limited to three (3) students per class.
This class will be held at the Client’s site. The Client is responsible for providing adequate training facilities, including at least one Inform CAD console with GISLink utility installed on it.
Prerequisites: GIS knowledge and background; familiarity with ESRI tools.
No other activities (including but not limited to TriTech performing follow up changes to the Client’s maps, development of special material for the Client, or a follow-up one-on-one session with the Client’s GIS staff) are within the scope of this class.
7.3.8.7 Inform CAD System Administration Training (TriTech Site) The System Administration Training course provides an overall administrative perspective of the system including operating system and database management software and equipment components. This comprehensive 4 to 5-day course is held at TriTech headquarters, and trains System Administrators and staff members on how to set up and administer infrastructure configurations for the Client-configured Inform CAD System. The class will also provide attendees with sufficient skills to perform system maintenance manage and monitor interfaces, manage system operation and database settings for application support, maintenance and backup, and general troubleshooting skills.
Attendance of the Client-designated individuals should be coordinated and scheduled through TriTech’s Project Manager and should be coordinated in such a way that does not interfere with progress of the Project.
System Administration classes are held regularly in TriTech’s training facility in San Diego and may have attendees registered from agencies other than the Client.
Training classes start on a Monday and end on Friday. The number of attendees will be based on the number of seats that have been purchased by the Client. If more than one seat is purchased by the Client, the Client has the option to send their attendees to one class or different classes.
The Client is responsible for the travel fees and out of pocket expenses for their staff attending this class in TriTech’s facility.
Prerequisites: Basic Windows and SQL Server knowledge
No other deliverables or follow up activities, including creating special material or applications for the Client, are included within the scope of this class.
#11..
- 799 -
Project Execution
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
48 7.4 Implementation of Inform Mobile
7.4.1 Inform Mobile System Orientation
The Inform Mobile System Orientation is conducted by a TriTech Inform Mobile Business Analyst. Inform Mobile is an Inform CAD-Integrated System, meaning that a significant amount of mobile functionality is dependent upon CAD functions as well as the configuration of the Client’s Inform CAD system. Given this interdependency, the Inform Mobile System Orientation generally will follow Inform CAD System Orientation, and occasionally is deferred until after verification of the hierarchy at DOLF.
During the Inform Mobile System Orientation, the Business Analyst will give a demonstration of the Mobile product. It is suggested that Client personnel who will be responsible for facilitating Mobile end user training should also take part in the configuration of Mobile.
The TriTech Business Analyst will document the Client’s configuration options in a Configuration worksheet which will be presented to the Client team for review and approval prior to configuring the application. Timely review and approval of this document by each agency is key to timely completion of the configuration work. Functional Acceptance Testing of the Mobile system is based on a standard set of FAT test documents, as they are applicable to specific configurations of the system.
7.4.1.1 TriTech Responsibilities
a) Schedule the Inform Mobile System Orientation meeting in accordance with the Client’s availability and the Project Schedule.
b) Prepare and distribute the meeting agendas and documents for Client review or completion to all required attendees two weeks prior to each meeting.
c) Conduct the meetings based on the distributed agenda. d) Document the Client’s requirements and configuration specifications resulting from the System Orientation discussions for Mobile.
e) Document and assign owners and due dates to any action items and track all action items to closure. f) Document any gaps between the standard functionality of the System and functionality required by the Purchase Agreement for further analysis and discussion and/or facilitate the change control process.
Client requests for functionality beyond the scope of the Purchase Agreement will be reviewed at this phase, but will have to be evaluated for the potential impact on the Project Schedule and for additional project charges to be paid by the Client.
g) Complete the configuration worksheets and deliver to the Client for review and approval. h) Prepare and submit a TCR upon completion of the System Orientation activities, and upon delivery of the configuration worksheets to the Client.
7.4.1.2 Client Responsibilities
a) Provide adequate facilities to comfortably hold the System Orientation to include a computer projector, whiteboards, and adequate seating. Two projectors are preferred. b) Provide communications center representatives authorized to make decisions with regard to the interrelationship between Mobile use and dispatcher control functions such as status updates; traffic stops and the like.
#11..
- 800 -
Project Execution
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
49 c) Provide subject matter experts that can describe operational requirements of field users. d) Provide a subject matter expert for Mobile WAN connectivity, firewall and network configuration and in-vehicle computer hardware.
e) Ensure that requested information such as data elements necessary to begin the Subsystem build are provided within a timely manner.
f) Upon receiving the Mobile configuration worksheet, review and provide approval, or any necessary changes to TriTech in a timely manner.
g) Participate in the Change Management Process for any requested software changes. h) Review and approve the applicable TCRs.
7.4.2 Inform Mobile Map Data Import
The process of Inform Mobile Map Data Map Import converts the Inform CAD streets data into a format that can be used by Mobile. This process also includes adding necessary map layers for the Client.
7.4.3 Inform Mobile Configuration
Inform Mobile Business Analyst will configure the Mobile based upon the options that have been documented in the Mobile configuration sheet, once the servers have been installed at the Client site. The Business Analyst will also use these configurations for preparing the FAT document. These activities will be performed remotely.
7.4.4 Inform Mobile Training
Inform Mobile Training classes are conducted based on the quantities that are specified in the Purchase Agreement. These classes are conducted on consecutive days, on the weekdays during business hours (Tuesday-Friday, during business hours). Alternate training schedules (multiple classes per day, evening, and weekend classes) will be subject to additional charge. Training classes will only be delivered after the FAT have been completed and the results are documented in a TCR.
Typically TriTech trains a small group of the trainers from the Client field users, and that group completes training the balance of the field users.
A detailed description of these classes is provided below.
7.4.4.1 TriTech Responsibilities
a) Schedule training classes with the Client.
b) Conduct training classes as scheduled.
c) Prepare and submit a TCR to the Client upon completion of each class or group of consecutive classes.
7.4.4.2 Client Responsibilities
a) Schedule appropriate Client staff to attend scheduled training. b) Provide adequate facilities for the execution of the training to include adequate seating for each workstation and an overhead projector.
c) Review and approve the applicable TCRs.
#11..
- 801 -
Project Execution
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
50 7.4.4.3 Inform Mobile Administration Course
Mobile Administration training is a hands-on course provided by experienced trainers who have both training and public safety experience. This half (½) day course prepares the Mobile Administrator to configure and maintain the Mobile Server and Mobile Interface(s). The course is set for one (1) or two (2) students. Access to the Mobile Server and Interface(s) is required. During this process TriTech Business Analyst/System Engineer will instruct the client on installation of Mobile Clients and provides assistance for installation of up to five (5) Mobile devices. The Client will be responsible for installation of the balance of Mobile devices.
The course includes the operation of the Mobile system including customization of specific screen layouts, Active & Waiting Incident Queue, Unit Queue, and agency-specific screens.
Training classes will be conducted between Tuesday and Friday. The number of students attending the User Training course will be limited to three (3) students per class.
Prerequisites: Knowledge of: 1) HTML/XML, CSS, and JavaScript 2) SQL, especially views, stored procedures, and database schema; and 3) Standard GPS protocol (TAIP and NMEA)
7.4.4.4 Inform Mobile Train-the-Trainer Course
Mobile Train-the-Trainer training is a hands-on course provided by experienced trainers who have both training and public safety experience. The course prepares personnel to use Inform Mobile and teach others how to use Inform Mobile. The course can accommodate up to eight (8) students with working and configured Mobile devices. It is desirable that each participant have their own configured Mobile device.
The course includes user operation including starting and stopping the application, updates, screen layouts, messaging, status changes, mobile maps, incident assignments and incident updates. Hands-on training and agency scenarios may vary by Agency. The duration of this class may be between four and six (4-6) hours.
Training classes will be held between Tuesday, and Friday. The number of students attending the User Training course will be limited to eight (8) students per class.
This class will be held at the Client’s site. The Client is responsible for providing adequate training facilities, including a conference room with adequate space and seating/conference table space, white board, projector, and computer projector (capable of 1024x768 resolution).
Prerequisites: Completion of a Microsoft Windows Tutorial (this may be waived upon demonstrated ability to work with Windows), typing skills of a minimum of 25 words/minute and Mobile field user experience.
7.5 System Integration Testing (SIT)of Inform CAD,
Inform Mobile, and Interfaces
Once the FAT is concluded for all subsystems (Inform CAD, Inform Mobile, and each of the interfaces) and in preparation for Go Live, TriTech and the Client will conduct a one day SIT. The SIT will be conducted based on a number of scenarios that test the call flow from the call creation to disposition in CAD. These scenarios include the Inform CAD, Inform Mobile and Interfaces that can be tested in the pre-production environment and are scheduled to Go Live at the same time. A small group of the Client staff (1-2 dispatchers and 1-2 Mobile field users) should participate in this test with TriTech. TriTech will work with the Client on defining a set of test scenarios that test the system based on the Client’s practices. It is recommended that the Client utilize sample calls from their legacy System. These scenarios must be signed #11..
- 802 -
Project Execution
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
51 off prior to commencement of the SIT. At the successful completion of SIT without any issues that prevent the System to be taken Live the Client shall provide written approval that the System is ready for Go Live.
7.6 Implementation of Inform RMS
Inform RMS is implemented through a series of standard steps and process gates. These steps are designed to ensure that the operational needs of the Client are identified, the configurations are verified, and the system is tested to validate the proper functionality of the system prior to deployment. The following sections describe the implementation process for Inform RMS.
7.6.1 Inform RMS System Orientation
The Inform RMS System Orientation is conducted at the Client’s site and led by a TriTech Business Analyst.
The duration of the Inform RMS System Orientation is generally up to three (3) days and includes a Business Process Review of the Client’s operations. This System Orientation can be conducted in conjunction with Inform CAD or Jail if purchased together.
Some key discovery points for the Inform RMS System Orientation are as follows:
a) Work Flow – Understanding the setup for work flow processes from the field report to the State Submission. This may include time observing Departmental Divisions (such as Patrol, Records, Investigations, Property and Evidence, and the like).
b) Review reporting requirements.
c) Event numbering (Incidents) including master incident numbers and case numbers.
It is recommended that the number of attendees in the System Orientation is limited to 10 to allow for more effective communication during the session. Based on the key discovery points during this session, it is necessary that the attendees include individuals who can properly address these key points and make configuration decisions.
During the System Orientation session the Business Analyst will facilitate an operational overview of Inform RMS by demonstrating the report flow from creation to approval and case assignment.
7.6.1.1 TriTech Responsibilities
a) Schedule the System Orientation meeting in accordance with the Client’s availability and the Project Schedule.
b) Prepare and distribute the meeting agendas and documents for Client review or completion two weeks prior to each meeting.
c) Conduct the meetings based on the distributed agenda. d) Document the Client’s requirements and configuration specifications resulting from the System Orientation discussions.
e) Document and assign owners and due dates to any action items and track all action items to closure. f) Document any gaps between the standard functionality of the System and functionality required by the Purchase Agreement for further analysis and discussion and/or facilitate the change control process.
Client requested changes for changes beyond the scope of the Purchase Agreement will be evaluated at this phase, but will have to be evaluated for the potential impact on the Project Schedule and for additional project charges to be paid by the Client.
#11..
- 803 -
Project Execution
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
52 g) Produce a System Orientation Report with the key decisions and configuration points as a result of the System Orientation.
h) Prepare and submit a TCR upon completion of relevant activities.
7.6.1.2 Client Responsibilities
a) Provide adequate facilities to comfortably hold the System Orientation to include a computer projector, whiteboards, and adequate seating. Two projectors are preferred. b) Ensure participation of key stakeholders and decision-makers in the System Orientation process. c) Provide subject matter experts that can explain the agency’s current work flow and application processes. These persons should have the ability to make decisions regarding any changes in work flow that may arise through the use of the new Inform RMS System. d) Provide subject matter experts that will be the RMS super users, as well as a person or persons that will be responsible for the ongoing maintenance of the RMS Code Files and configuration (RMS Administrator).
e) Provide subject matter experts that will be responsible for translating the geopolitical/operational boundaries into data (ESRI shape files) suitable for use within the RMS. f) Provide subject matter experts that will be responsible for the maintenance of the agency’s street centerline data.
g) Review and approve applicable TCRs.
7.6.2 Inform RMS Administration and Review Training
The Inform RMS Administration and Review Training is a hands-on course for Inform RMS System Administrators conducted once RMS is installed at the Client site. During the course, students will learn how to create users, assign roles, create RMS templates and assign workflows. Students also learn overall administration responsibilities for implementation, configuration, and maintenance of Inform RMS.
Participants include key members of TriTech’s implementation team and should not exceed ten (10) core members of the Client’s implementation team. The Client’s team should include RMS Central and Local Administrators.
Following the training, ownership of the RMS System Build transfers to the Client. The Client will enter the balance of the Code Files, build templates, create workflows, and complete the build of personnel . The Client also becomes responsible for maintaining Code Files (personnel, Violation Codes, Property Locations, and the like) that must be continuously updated to keep the Code Files in Go-Live ready status. During this phase, the assigned TriTech Business Analyst will provide consultation services.
The Inform RMS Administration and Review Training will be up to three (3) days onsite.
7.6.2.1 TriTech Responsibilities
a) Schedule the Inform RMS Administration and Review Training in accordance with the Client’s availability and the Project Schedule.
b) Prepare and distribute the meeting agenda and documents for Client review or completion to all required attendees two weeks prior to the training.
c) Conduct the meetings based on the distributed agenda. #11..
- 804 -
Project Execution
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
53 d) Create the project checklist itemizing the tasks for completion throughout the RMS implementation. e) Provide the Client team with a copy of the Inform RMS User and Administration Guides. f) Prepare and submit a TCR upon completion of the training.
7.6.2.2 Client Responsibilities
a) Provide adequate facilities to comfortably hold the training activities. b) Ensure participation of the appropriate personnel.
c) Continue the code file building activities after completion of this training. d) Review and approve the applicable TCR.
7.6.3 Inform RMS Base System Build
After completion of the Inform RMS Administration and Review Training, it is the responsibility of the Client to assume ownership of building and maintaining the RMS templates, personnel, and roles.
This will be an iterative process throughout the implementation of RMS building upon knowledge learned through each training class and workshop. The assigned TriTech Business Analyst will work with the Client to start and supervise the initial Code File building process during the workshops. The Client will be actively involved and responsible for the Code File configuration process throughout the project.
TriTech will deliver the Inform RMS System with the base NCIC Codes. The Client is responsible for building and maintaining the System Codes, Personnel, Property Locations, and Violation Codes (including local ordinances). The TriTech Business Analyst will begin the System Build with a base of 50 personnel entered in to the system. The Client is responsible for the remaining Personnel data being entered and maintained.
Note: It is the responsibility of the client to complete the UCR/NIBRS code mapping to the violation codes.
Validation through the implementation until DOLF allows for the continual review and updating of the Code File setup while limiting the risk of rework. This task is considered to have been completed when the Business Analyst has demonstrated the RMS functionality at DOLF.
7.6.3.1 TriTech Responsibilities
a) Monitor and evaluate the System build throughout the implementation and provide guidance as needed.
7.6.3.2 Client Responsibilities
a) Provide timely input and updates to the Templates, Workflows, Users, Roles, and System codes. b) Continue building the Templates, Workflows, Users, Roles, and System Code Files (those not built by TriTech) through completion.
#11..
- 805 -
Project Execution
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
54 7.6.4 Geographical Information Services
7.6.4.1 Data Evaluation
The TriTech GIS Analyst will work with the Client to create the address locator packages and configure the RMS GIS services. GIS data must be from a single integrated source when delivered to TriTech for conversion.
7.6.4.2 TriTech Responsibilities
g) Evaluate Client-supplied GIS data to ensure it is formatted correctly for creation of the address locator packages.
h) Create the address locator packages, and configure the RMS GIS services i) Prepare and submit a TCR upon completion of this work.
7.6.4.3 Client Responsibilities
e) Provide data in the required format, and per Project Schedule. f) Based on the analysis provided by TriTech, make needed changes to mapping data to allow the resulting GIS data to meet TriTech’s mapping data requirements.
g) Review and approve the appropriate TCR.
7.6.5 Inform RMS Workshops
After the Inform RMS Administration and Review Training has been completed, the TriTech project team will conduct one or more Inform RMS workshops either remotely or at the Client site. This session is intended to be an extension to the Inform RMS Administration Training for more complex implementations and multi-jurisdictional agencies as specified in the contract. Each Inform RMS workshop will be up to three (3) days onsite. An example of workshops would be (Incident/Arrest/Case Management), (Crash, Citation, Other Event), or (Records Administration). If the Project includes multiple Workshops, they may or may not be scheduled to occur over consecutive weeks.
Participants include key members of TriTech’s implementation team and should not exceed ten (10) core members of the Client’s implementation team. The Client’s team should include RMS Central and Local Administrators.
The Project includes:
Three (3) Inform RMS Workshops
7.6.5.1 TriTech Responsibilities
a) Schedule the Inform RMS Workshop in accordance with the Client’s availability and the Project Schedule.
b) Prepare and distribute the meeting agendas and documents for Client review or completion to all required attendees two weeks prior to each meeting.
c) Conduct the meetings based on the distributed agenda. d) Prepare and submit a TCR upon completion of the workshop. #11..
- 806 -
Project Execution
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
55 7.6.5.2 Client Responsibilities
a) Provide adequate facilities to comfortably hold the training activities. b) Ensure participation of the appropriate personnel.
c) Continue the code file building activities after completion of this training. d) Review and approve the applicable TCR.
7.6.6 Inform RMS Output Designer Workshop
The TriTech project team will conduct the three (3) day Inform RMS Output Designer Workshop at least 6-8 weeks upon completion of the (Incident, Arrest, Case Management Workshop). TriTech recommends the RMS templates should be 90-95% complete prior to this workshop to prevent rework on the form outputs.
This session is intended for creating custom form outputs using Microsoft SQL Server Reporting Services (SSRS), which can be accessed from the Inform RMS Web UI Data Entry Templates. Using the Inform RMS Output Designer application utility, attendees will learn to generate a dataset based on the Inform RMS Module template, utilizing SSRS to customize the output based off a pre-defined default output report.
Attendees will also learn how to configure the templates to use the custom form output within the Inform RMS Web Data Entry Designer tool.
This is an advanced Workshop and attendees must have prior experience using SSRS. TriTech will not provide training on SSRS. This Workshop will be up to three (3) consecutive days with a class size limitation of five (5)students.
7.6.6.1 TriTech Responsibilities
e) Schedule the Workshop in accordance with the Client’s availability and the Project Schedule. f) Prepare and distribute the Workshop agenda and documents for Client review or completion to all required attendees two weeks prior to the training.
g) Conduct the meetings based on the distributed agenda. h) Prepare and submit a TCR upon completion of the Workshop.
7.6.6.2 Client Responsibilities
a) Provide workstations with Inform RMS and SQL Server Reporting Service access. b) Provide adequate facilities to comfortably conduct the Workshop to include an overhead projector and whiteboard.
c) Ensure participation of the appropriate personnel.
d) Continue the Output Designer activities after completion of this training. e) Review and approve the applicable TCR.
7.6.7 Inform RMS Demonstration of Licensed Functionality (DOLF) Once the System build is complete, a Demonstration of Licensed Functionality (DOLF) is conducted. This working workshop includes a review of the Templates, Workflow, Users, Roles, Code Files and #11..
- 807 -
Project Execution
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
56 configuration. The Inform RMS DOLF workshop will review the completeness of the codefiles in the Client’s system, review system functionality, review templates, personnel, workflow, system codes, and configurations to conduct an overall system readiness assessment. This session will also provide a forum for the Client to discuss any final workflow questions or issues prior to Functional Acceptance Testing and End User Training.
The DOLF for Inform RMS is up to three (3) days and will be held at the Client’s facilities on the Client’s system hardware, after it has been configured by TriTech.
Participants include key members of TriTech’s implementation team and should not generally exceed ten (10) core members of the Client’s implementation team. The Client’s team should include RMS Administrators and Subject Matter Experts. At the conclusion of the session, a DOLF report is produced which documents the core software configuration and activities to be completed by the Client. Any issues that require follow-up action, including any outstanding Go Live issues will be documented in the applicable Project journal. Any issue that is determined to be outside the scope of this Project, as defined herein, requiring a modification or enhancement to the TriTech Software will be addressed through the Change Control process.
7.6.7.1 TriTech Responsibilities
a) Schedule the DOLF workshop in accordance with the Client’s availability and the Project Schedule. b) Prepare and distribute the meeting agendas to all required attendees a week prior to each meeting. c) Conduct the meetings based on the distributed agenda. d) Provide initial hands on training on the applicable system and introduction to different modules and their configurations.
Note: This training is not meant to be comprehensive for end user understanding of the Subsystem.
The purpose is to give the participant an opportunity to perform validation and readiness of the Inform RMS (and Field Based Reporting if purchased).
e) Document and assign owners and due dates for any action items and track all action items to closure. f) Develop and deliver the DOLF Trip report.
g) Handoff the management the Code Files to the Client. h) Prepare and submit a TCR upon completion of the DOLF, and upon delivery of the DOLF Trip report to the Client.
7.6.7.2 Client Responsibilities
a) Provide adequate facilities to comfortably hold the DOLF to include an overhead projector. Two projectors are preferred. DOLF also requires workstations for each participant. b) Ensure complete participation of Central and Local Inform RMS Administrators for the purposes of reviewing the RMS configuration as-built.
c) Provide participants that are versed with the ability to continue the configurations. d) Assume ownership for the continued build and maintenance of the system under the guidance of the TriTech project team.
e) Ensure participation of key stakeholders and decision-makers in the DOLF process. #11..
- 808 -
Project Execution
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
57 f) Observe the change control process for any requested software changes. g) Review and approve the applicable TCRs.
7.6.8 Inform RMS Functional Acceptance Testing (FAT)
Inform RMS Functional Acceptance Testing follows a standard content, approach and format. An Inform RMS Business Analyst performs the acceptance testing with the Client, prior to the start of End User Training. This process will be based on the standard TriTech FAT documents. The FAT documents have a standard content and format. The standard TriTech FAT documents will be sent to the Client for review prior to conducting the tests. The FAT results are documented in a TCR for verification and approval by the Client. Upon completion of FAT, the Client and TriTech will review the list of FAT failures (if any), and perform an assessment of the errors and determine the timeline for remedying the issues (pre versus post Go Live).
Participants include key members of TriTech’s implementation team and should not generally exceed five (5) core members of the Client’s implementation team.
TriTech will repeat any specific failed FAT tests following the correction of any issues which has caused the test to fail. This process will not include a repeat of the entire tests.
Note: TriTech may organize at its discretion, separate breakout FAT sessions for subsections of the FAT documents that are applicable only to one agency (for example, applicable only to a Sheriff’s Department or single agency). Each test will be executed once, and all applicable users and agencies must attend the FAT session and observe the tests.
Note: Successful completion of the FAT as part of the Pre-Go Live testing process does not constitute Final System Acceptance if such a Post-Go Live Reliability Testing is defined in the Purchase Agreement.
7.6.8.1 TriTech Responsibilities
a) Deliver TriTech’s standard FAT documents to the Client no later than two weeks prior to conducting the FAT.
b) Provide a TCR to the Client to approve the receipt of the FAT documents. c) Assist the Client in conducting the FAT in accordance with FAT documents. d) Identify and document any issues discovered during the FAT. e) Upon completion of FAT prepare and submit a TCR to the Client, including a list of any exceptions to FAT.
7.6.8.2 Client Responsibilities
a) Work toward the timely completion of all predecessor tasks to include the base code table entry and configuration.
b) Provide adequate facilities to execute the FAT.
c) Participate in the FAT by providing operational subject matter experts. #11..
- 809 -
Project Execution
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
58 d) Assist TriTech in documenting FAT findings and results. e) Review and approve the appropriate TCRs.
7.6.9 Inform RMS Data Conversion
This Project includes a one-time conversion of the data from one (1) legacy database into Inform RMS.
These sources are:
Refer to the Functional Design Document (FDD) for the above noted conversion. It contains details on the planned approach, data fields that will be converted into Inform RMS and assumptions.
7.6.9.1.1 TriTech Responsibilities
a) Perform an analysis of the legacy data, provided by the Client. b) Collaborate with the Client in defining the data mapping, as well the resolution of the duplicate names. c) Provide an Operational Scenario Document (OSD) prior to developing the scripts for the data conversions.
d) Create the necessary scripts for the data transfer.
e) Perform the initial data conversion and import for review by the Client. f) Perform the final data conversion and import into the Inform RMS. g) Prepare and submit the applicable TCRs.
7.6.9.1.2 Client Responsibilities
a) Extract and scrub the legacy data, and deliver it to TriTech in SQL format within thirty (30) days from the date of Inform RMS System Orientation.
b) Provide a data dictionary to define all elements of the legacy data. c) Assist TriTech with data mapping exercise.
d) Review, provide feedback and approve the OSD document prior to performing the data conversion. e) Review and approve (or provide feedback, detailing the required corrections) for the interim data conversion delivery within ten (10) days of receiving.
f) Review and approve (or provide feedback, detailing the required corrections) the final data conversion delivery within ten (10) days of the final conversion.
g) Provide a secure and reliable network connection.
h) Review and approve the applicable TCRs.
7.6.10 Inform RMS Training
Note: Training classes are conducted based on the quantities that are specified in the Purchase Agreement. The appearance of a course description in this Statement of Work does not mean a course will be conducted – it must be listed in the Purchase Agreement.
Inform RMS Training classes are conducted on consecutive weekdays (Tuesday-Friday) during business hours. Alternate training schedules (multiple classes per day, evening, and weekend classes) will be subject #11..
- 810 -
Project Execution
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
59 to additional charge. Training classes will only be delivered after the Inform RMS FAT has been completed and the results are documented.
Descriptions of classes are provided below.
7.6.10.1 TriTech Responsibilities (for all Inform RMS Classes) a) Conduct a training orientation via conference call between the assigned TriTech Training personnel and the designated Client representative. The objective of this session is to define the Training Schedule, based on the configurations of the Subsystem.
b) Schedule the Inform RMS Training class(es) in accordance with the Client’s availability and the Project Schedule.
c) Prepare and distribute the meeting agendas and documents for Client review or completion to all required attendees two weeks prior to each meeting.
d) Develop and provide the Inform RMS Training Plan for all licensed product options to the Client. e) Conduct the training session(s) for the licensed product options on a mutually agreed to schedule. f) Prepare and submit a TCR upon completion of each class, or a group of consecutive classes.
7.6.10.2 Client Responsibilities (for all Inform RMS Classes) a) Participate in the training orientation by providing a decision maker that can articulate the specific business practices that have been used in guiding the build of the Client’s System. b) Provide adequate facilities for the execution of the training to include adequate seating for each workstation and an overhead projector.
c) Provide a Local RMS Administrator for each class that can answer agency specific questions as related to the build of the Client’s system.
d) Review and approve the applicable TCRs.
7.6.10.3 Inform RMS End User Training – Records
The Inform RMS End User Training for Records is a hands-on course that prepares the students to add, edit, and modify Incident, Arrest, Custody, Crash, Citation, Field Interviews, State Reporting, Redaction and Expungements. This class also instructs users on how to search crime report records easily and efficiently.
Students learn how to maintain State-reportable UCR/NIBRS reports. This class is recommended for all personnel responsible for the day-to-day records data entry and maintenance of all departmental reports. This three-day course prepares a core set of end users to use Inform RMS.
Training classes are conducted between Tuesday and Friday, with a maximum of ten (10) students per class.
Prerequisites: 1) Basic understanding of computers and the Microsoft Windows Environment. 2) A comprehensive understanding of the internal structure of the Records Department and departmental policies and procedures. 3) An understanding of how the Records Department interacts with Dispatch and Patrol.
7.6.10.4 Inform RMS End User Training – Field Officers
The Inform RMS End User Training for Field Officers session is a hands-on three-day course. This course trains students to use Inform RMS and includes instructions on how to create and submit Incident, Arrest, Field Interview, Citation, and Crash (or applicable modules) through the workflow process. For the train-thetrainer portion of the class, TriTech prepares selected Client personnel to train other end users on Inform #11..
- 811 -
Project Execution
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
60 RMS. The goal is to prepare these personnel to apply TriTech’s training concepts to train field users on Inform RMS.
Training classes are conducted between Tuesday and Friday, with a maximum of ten (10) students per class.
Prerequisites: 1) Basic understanding of computers and the Microsoft Windows Environment. 2) A comprehensive understanding of the departmental policies and reporting procedures. 3) An understanding of how Patrol interacts with the Records Department and Dispatch.
7.6.10.5 Inform RMS Property and Evidence Training
The Inform RMS Property and Evidence training is a hands-on three-day workshop for personnel responsible for entering, updating, and maintaining evidence records, and providing written notification for property or impounds. Students learn how to configure the module, search evidence records, manage evidence items, create item barcodes, and use barcoding for inventory evidence. Training should be conducted directly with the Evidence Technicians at the agency’s Evidence room.
Training classes are conducted between Tuesday and Friday, with a maximum of ten (10) students per class.
Prerequisites: 1) Basic understanding of computers and the Microsoft Windows Environment. 2) A comprehensive understanding of the departmental policies and procedures associated to maintaining Evidence. 3) A thorough understanding of how each of the Agency’s Evidence locations are laid out and used.
7.6.10.6 Inform RMS End User Training – Investigations Training The Inform RMS Investigations training is a hands-on three-day course for Case Managers, Investigative Supervisors, and Investigators (Detectives). Students learn how to assign cases for investigation and track their progress, add case supplements/case materials, create incident supplements, arrests, and update cases as needed. Training should be conducted directly with detectives that can train other detectives at their agency; this helps ensure proper workflows are discussed and configured.
Training classes are conducted between Tuesday and Friday, with a maximum of ten (10) students per class.
Prerequisites: 1) Basic understanding of computers and the Microsoft Windows Environment. 2) A comprehensive understanding of the departmental policies and procedures associated to Case Management, Investigations, and the management of Intelligence data (if applicable).
7.6.10.7 Inform RMS Report Writing Class
The Inform RMS Report Writing Training is a hands-on course that will prepare students to create, modify, and run reports on data within the Inform RMS application. Students will learn how to use the Ad-Hoc Reporting module within Inform RMS, as well as how to create new Microsoft SQL Reporting Services (SSRS) Custom Reports using SQL Database Model Views. This three (3) day class is recommended for all personnel that will utilize the provided reporting tools to extract data from the Inform RMS.
Training classes will be conducted between Tuesday and Friday. The number of students attending the User Training course will be limited to no more than ten (10) students per class.
Prerequisites: 1) Completion of Inform RMS Training. 2) General understanding of Microsoft SQL Reporting Services. 3) Understanding of Department Reporting requirements. #11..
- 812 -
Project Execution
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
61 7.7 Inform RMS System Integration Testing (SIT)
Once the FAT is concluded for Inform RMS and in preparation for Go Live, TriTech and the Client will conduct a one day remote SIT. The SIT will be conducted based on a provided scenario that test the records management process. A small group of the Client staff (1-2 Records staff and field users) should participate in this test with TriTech. TriTech will work with the Client on refining the test scenario that test the system based on the Client’s practices. This scenario must be signed off prior to commencement of the SIT. At the successful completion of SIT without any issues that prevent the System to be taken Live the Client shall provide written approval that the System is ready for Go Live.
7.7.1 TriTech Responsibilities
a) Schedule A SIT with the Client.
b) Assist the Client in preparing test scenarios that can be used during this test and closely simulates the normal Client’s call flow.
c) Prepare and submit a TCR to the Client documenting the tests that will be used for the SIT. d) Participate in the SIT with the Client.
e) Prepare and submit TCRs upon successful completion of the SIT.
7.7.2 Client Responsibilities
a) Provide test scenarios that closely simulate the Client’s normal call flow. b) Participate in conducting the SIT.
c) Review and approve the applicable TCRs.
d) Provide test systems (or pre-Production systems) for all integrations and interfaces. If the client can not provide a test system TriTech must test using the production system. This testing includes, but it not limited to, test data entry in a production system.
7.8 Implementation of CDP Search
CDP Search is implemented through a series of standard steps and process gates. These steps are designed to ensure that the operational needs of the Client are identified, the configurations are verified, and the system is tested to validate the proper functionality of the system prior to deployment. The following sections describe the implementation process for CDP Search.
7.8.1 CDP Search Setup and Conversion Services
The historical data import is a process by which TriTech extracts applicable data from TriTech applications and imports that data into IQ Search. The data is then available for search and reporting functionality subject to subscriptions purchased.
.
#11..
- 813 -
Project Execution
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
62 The data available in CDP Search from the Inform Product Suite is listed in each applications’ IQ Search Field Mapping Guide.
7.8.1.1 TriTech Responsibilities
a) Deliver the CDP Search Client Readiness Checklist to Client and review with Client once completed and returned.
b) Install and Configure Synchronization.
c) Perform historical Bulk Import.
d) Configure CDP Search:
o Provision Agencies within CDP Search
o Provision Administrator Users within CDP Search
e) Prepare and submit Task Completion Reports (TCR) to the Client for approval to document delivery of products and services.
7.8.1.2 Client Responsibilities
a) Complete the CDP Search Client Readiness Checklist, return and review with TriTech once completed, address any necessary requirements.
b) Provide remote access to TriTech’s implementation team to Client servers. c) Make appropriate Client staff available during the installation to assist TriTech’s implementation team in resolving any issues during the process.
d) Review and approve the applicable TCRs.
7.8.2 CDP Search Administration Training (Remote)
This TriTech instructor led class is designed for those individuals who will be responsible for the administration of CDP Search. Participants will be instructed on how to configure, administer, and operate CDP Search in an administration role. The recommended class size for this training is up to 9 participants.
This training is up to 4 hours and is delivered in one remote session.
At the completion of the training, participants will be able to perform the following:
Access and successfully login to CDP Search
Understand the CDP Search site
Understand the management console for CDP Search
Create and manage roles
Create and manage users
7.8.2.1 TriTech Responsibilities
a) Schedule the Administration training in accordance with the Client’s availability and the Project Schedule.
b) Provide standard Administration training sessions for Client personnel #11..
- 814 -
Project Execution
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
63 c) Prepare and submit TCRs upon completion of the training.
7.8.2.2 Client Responsibilities
a) Schedule appropriate personnel to attend Administration training. b) Ensure participation of the appropriate personnel.
c) Review and approve the applicable TCRs.
7.8.3 CDP Search Core End User Training (Remote)
This TriTech instructor led class is designed for the end users of CDP Search. End users include roles such as officers, records clerks, dispatchers, dispatch supervisors, managers, and agency administrators. This class may be attended by the end users, or trainers who will be training the end users within the agency(ies). The recommended class size for this training is up to 12 participants.
This training is up to 4 hours and is delivered in one remote session.
At completion of this training, participants will be able to perform the following:
Access and successfully login to CDP Search
Understand the CDP Search site
Use links within the site
Use Online Help
Use Search Filters
Save searches and manage saved searches
View Search History
View Search Details
Set up Search Alerts and manage alerts
Create and access reports
These half day courses are conducted remotely and trains a core set of end users on the CDP System.
Typically, the remaining end users will be trained via Client delivered training sessions.
The number of students attending the User Training course will be limited to no more than ten (10) students per class.
Note: All remaining IQ Search end users must complete Client provided end user training.
7.8.3.1 TriTech Responsibilities
a) Schedule the CDP Search Core End User Training class(es) in accordance with the Client’s availability and the Project Schedule.
b) Conduct the training session(s) on a mutually agreed to schedule. c) Prepare and submit a TCR to the Client upon completion of the training. #11..
- 815 -
Project Execution
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
64 7.8.3.2 Client Responsibilities
a) Provide adequate facilities to comfortably hold the training activities. b) Ensure participation of the appropriate personnel.
c) Ensure that all CDP Search core end-users attend the end-user training provided by TriTech. d) Provide CDP Search training to all other end users.
e) Ensure that each CDP Search end-user completes relevant training before assigning the end-user a username and password to access the CDP Search.
f) Review and approve the appropriate TCR.
7.8.3.3 CDP Search Acceptance
The CDP Search application will be considered Accepted upon completion of the first CDP Search Core End User Training provided by TriTech and the first Subsystem (such as Inform CAD or Inform RMS) is contributing Production data to the CDP Search application.
7.9 Implementation of IQ CrimeView Dashboard
The CrimeView Dashboard will be implemented through a series of standard steps and process gates.
7.9.1 Prerequisite Collection and Preparation
The Client’s preparation and delivery of prerequisites to the TriTech project team is a critical gate for starting the implementation work.
7.9.1.1 TriTech Responsibilities
i) Provide a prerequisites list following the project kick-off meeting. j) Prepare and submit a TCR upon completion of critical prerequisite collection.
7.9.1.2 Client Responsibilities
a) Configure hardware, including creation of a TriTech local administrator account on the application servers (details in CrimeView & FireView CrimeView & FireView Appendix A – Dashboard Hardware, Software, and Related Requirements)
b) Provide source data access information, typically including ODBC connection details, a read-only database user in each source system, installation of any necessary ODBC or other drivers on the Import Server, and delivery of data dictionaries or target table/field information where requested by TriTech. c) Install required software on the Import Server: ArcGIS Desktop, ArcGIS VBA, TriTech Desktop application(s)
d) Provide required GIS data (details in CrimeView & FireView Appendix B) e) Configure remote access according to TriTech’s approved remote connectivity methods f) Review and approve the applicable TCRs.
#11..
- 816 -
Project Execution
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
65 7.9.2 Application Configuration, Staging Deployment, and Initial Review The TriTech Implementation Specialist will configure and automate the ETL (Extract, Transform, and Load) processes, including configuring connection(s) to the CAD, RMS, and/or other data sources, SQL or text file imports, data processing, geocoding, and output and transfer of data. Upon completion of this process, the Implementation Specialist will configure the Dashboard application according to the Application Specifications listed in CrimeView & FireView CrimeView Appendix B – Dashboard GIS Data and Application Specifications and Standard Field Lists listed in CrimeView & FireView CrimeView Appendix C – Dashboard Standard Field Lists. The application will then be installed in the TriTech staging environment and demonstrated to the customer for an initial review, and training dates will be scheduled during or following the demonstration.
7.9.2.1 TriTech Responsibilities
a) Configure the ETL process and Dashboard application. b) Provide the Client with data categorization worksheets as necessary. c) Install the application in the TriTech staging environment. d) Schedule and conduct the Application Review Meeting. e) Initiate Scheduling of all Dashboard Training sessions. f) Prepare and submit a TCR upon completion of the Application Review Meeting.
7.9.2.2 Client Responsibilities
a) Respond promptly to information, data, and assistance requests from the TriTech team. b) Complete data categorization worksheets, if required, within 5 business days of the request. c) Work with the TriTech Project Manager to facilitate scheduling a date for the Application Review meeting.
d) Schedule the appropriate personnel from the Client’s team to attend the Application Review Meeting.
This review should include key stakeholders, including analysts, appropriate command staff representatives, and other potential users and subject matter experts. e) Review and approve the applicable TCRs.
7.9.3 Installation
The TriTech Implementation Team will install the application.
7.9.3.1 TriTech Responsibilities
a) Coordinate an Installation Planning Meeting with the customer if necessary b) Install the application in the live environment.
7.9.3.2 Client Responsibilities
a) Provide all hardware, software, and other requirements outlined in Error! Reference source not found.. b) Coordinate attendance of required staff for the Installation Planning Meeting #11..
- 817 -
Project Execution
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
66 7.9.4 Dashboard Administrator/Designer Training (Remote) This TriTech instructor led class is designed for those individuals who will be responsible for the administration of the CrimeView Dashboard users, permissions, and content. These individuals typically hold analyst, command staff, GIS, or Information Technology positions. Participants will be instructed on how to use the full application, add/remove users, configure roles and permissions, create content (widgets, alerts, queries on demand, and notes), and organize the content into briefing books and groups. The recommended class size for this training is 2-8 participants.
This training is 4- 6 hours and is delivered in one or two remote sessions.
7.9.4.1 TriTech Responsibilities
d) Schedule the Administrator/Designer training in accordance with the Client’s availability and the Project Schedule.
e) Provide standard Administrator/Designer training sessions for Client personnel f) Prepare and submit TCRs upon completion of the training.
7.9.4.2 Client Responsibilities
d) Schedule appropriate personnel to attend Administrator/Designer training. e) Ensure participation of the appropriate personnel.
f) Provide adequate hardware, telecom, and/or other facilities for the training. g) Review and approve the applicable TCRs.
7.9.5 Dashboard Train the Trainer Training (On Site)
Note: Train the Trainer occurs after Dashboard Go Live & System Review and is not a dependency for System Acceptance.
Note: This training must occur within 6 weeks of Dashboard Go Live & System Review. If the Client cannot schedule the training within this window, an alternative, equivalent delivery method such as a video or remote training will be provided. No refund or credit will be provided as a result of this change.
This TriTech instructor led class is designed for a focused group of Dashboard end users who will be responsible for formally or informally training the balance of users at the agency. End users include roles such as officers, command staff, analysts, and administrators. This class may be attended by the end users or trainers who will be training the end users within the agency(ies). The recommended class size for this training is up to 15 participants, and TriTech recommends that each participant follows along on a computer.
At completion of this training, participants will be able to perform the following:
Access and successfully login to Dashboard
Navigate and view the content within the site
Run queries and analysis routines within the site.
View and post notes/missions within the site.
#11..
- 818 -
Project Execution
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
67 Save their own individual queries within the site.
This training includes two duplicate 4 hour sessions that are delivered on-site both on the same day or in the afternoon of the first day and the morning of the following day. These half day courses train a core set of end users on the CrimeView Dashboard System. Typically, the remaining end users will be trained via Client delivered training sessions.
The number of students attending the User Training course will be limited to no more than fifteen (15) students per class.
7.9.5.1 TriTech Responsibilities
d) Schedule the Dashboard Train the Trainer classes in accordance with the Client’s availability and the Project Schedule.
e) Conduct the training session(s) on a mutually agreed to schedule. f) Prepare and submit a TCR to the Client upon completion of the training.
7.9.5.2 Client Responsibilities
e) Provide adequate training facilities, including a conference room with adequate space, computers for each attendee, and a computer projector.
f) Prepare the training computers by installing any required software and ensuring access to the Dashboard website(s).
a) Ensure participation of the appropriate personnel.
b) Provide Dashboard training to all other end users.
c) Review and approve the appropriate TCR.
7.10 Dashboard Go Live & System Review
Dashboard “Go Live” occurs at the point when the Dashboard application is available to trained Administrator users. This initiates the System Review, during which the client takes responsibility for testing and data validation, and TriTech provides support and consultation.
7.10.1 System Review
Once the system is in production, one or more Administrator logins have been provided to the client, and the Administrator/Designer training has been completed, the application will be considered “live”, and the System Review will begin. During the System Review, the client is responsible for reviewing the application and informing the TriTech Project Manager of any noticed or potential issues or deficiencies with the configuration or data. The System Review period will expire in 10 business days, at which point, TriTech will address all submitted items prior to Train the Trainer training.
TriTech responses to each submitted item will fall into one of the following categories:
This item refers to something in the application or data import configuration that has been confirmed and fixed/changed.
Further information or action from the Client is required in order to assess the item (a time window for Client action will be provided).
#11..
- 819 -
Project Execution
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
68 This item is a result of the source query or GIS data provided by the Client and requires Client action to fix (a time window for Client action will be provided). This item identifies a software bug that has been submitted for review and rectification. This item refers to a function or known limitation of the application that lies in the application code rather than the configuration, and changes to the application code are excluded from this project.
Suggested Client Review Items:
Presence of contracted Query Layers (example: Calls for Service, Incidents, Arrests, etc.) o Query Layers are listed/visible in the “What” query panel. Query layer data integrity and completeness:
o Compare/confirm the number of records vs. the source database (CAD/RMS) by running identical queries in both systems.
o Confirm the fields identified in the Statement of Work are included by viewing the data in the Table.
o Confirm that the fields displayed in the Table contain the expected values (including codes/descriptions)
o Review Crime/Incident/Data type categorization/symbology. Saved Query Completeness and Accuracy
o Confirm the accuracy and completeness of the Saved Query picklists on the “What” query panel.
o Perform queries and confirm that they return the expected results. Geocoding
o Use Pin Map queries and/or Filter widgets to plot records on the map and spot check general accuracy to confirm the mapped location matches the address/location listed on the record.
o Spot check the address values displayed in the Dashboard (every query layer) against the address listed in the source system/data.
Geography and Operational Layers
o Confirm the Geographic Query Layers identified in project planning (up to 10) are present and the proper selection values are listed on the “Where” query panel (example: “Zone 1, Zone 2, Zone 3…”)
o Confirm the Operational Layers identified in project planning (up to 5) are present and accurately reflect the GIS data provided for the project.
7.10.1.1 TriTech Responsibilities
a) Prepare and submit a “Go Live” TCR at the completion of Administrative/Designer Training b) Notify the Client that the System Review period has begun, provide the review items listed above c) Receive and address all items/issues submitted by the Client during the System Review d) Prepare and submit a TCR.
7.10.1.2 Client Responsibilities
a) Complete the Suggested Client Review Items listed above. #11..
- 820 -
Project Execution
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
69 b) Inform the TriTech Project Manager of any questions, issues, or requested configuration changes. c) Review and approve the appropriate TCRs
7.11 Implementation of Crimemapping.com
Note: Crimemapping.com utilizes the hardware, software, and other requirements for CrimeView Dashboard and may be implemented prior to Dashboard if desired by the Client. Completion of task Error! Reference source not found. is a prerequisite for this task.
The TriTech Project Manager will provide the Client with a Crime Categorization Worksheet enabling them to match the Agency’s offense codes to the 15 Crimemapping Crime Categories. All offense codes not mapped to one of the 15 categories will be excluded from the site. The Client will complete the worksheet and return it to the Project Manager within 5 days.
Upon receipt of the required items and information, the TriTech Implementation Specialist will configure the data extraction application and deploy the agency’s data to the Crimemapping environment. Site and data specifications are listed in CrimeView & FireView Error! Reference source not found..
The TriTech Project Manager will provide the Client with the Crimemapping Staging Site URL and login information. At this point, the Client will have 10 days to review the site prior to the data being made available to the public on Crimemapping.com.
7.11.1.1 TriTech Responsibilities
a) Connect to the source server and configure the ETL process b) Prepare the Crime Categorization Worksheet and provide it to the Client c) Configure the agency on the Crimemapping.com staging site d) Provide the Client with the Crimemapping.com staging site URL and login account
7.11.1.2 Client Responsibilities
a) Complete the Crime Categorization Worksheet within 5 days and return it to the TriTech Project Manager
b) Provide the following to the TriTech project manager:
o Jurisdiction boundary GIS file (if available)
o Address of the agency’s headquarters
o The agency website and up to three additional URLs may be provided for reference on Crimemapping.com
7.12 Crimemapping.com System Review & Go Live
The Crimemapping.com System Review initiates upon TriTech’s provision of the Crimemapping staging site URL and login account. The System Review duration is 10 days, and upon completion of the review period, the client agency’s data will be released to the publicly available Crimemapping.com site signifying “Go Live.”
#11..
- 821 -
Project Execution
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
70 7.12.1 System Review
During the System Review, the client is responsible for reviewing the application and informing the TriTech Project Manager of any noticed or potential issues or deficiencies. The System Review period will expire in 10 business days, at which point, TriTech will address all submitted items prior to Go Live.
TriTech responses to each submitted item will fall into one of the following categories:
This item refers to something in the application or data import configuration that has been confirmed and fixed/changed.
Further information or action from the Client is required in order to assess the item (a time window for Client action will be provided).
This item is a result of the source query or GIS data provided by the Client and requires Client action to fix (a time window for Client action will be provided). This item identifies a software bug that has been submitted for review and rectification. This item refers to a function or known limitation of the application that lies in the application code rather than the configuration, and changes to the application code are excluded from this project.
Suggested Client Review Items:
Ability to log into the Crimemapping staging site
Presence of client agency data in the staging site, searchable by agency, address, and city/state
Data integrity and completeness: the crime records shown on the site generally reflect the count queried from RMS. Note: data filtering and categorizing may produce slight variations between RMS and Crimemapping.com, and the site generally shows one record per included offense rather than one record per incident.
Geocoding: the records are placed appropriately on the map. Note: map placement is generalized to the center of the street in an effort to protect victim privacy.
7.12.1.1 TriTech Responsibilities
a) Receive and address all items/issues submitted by the Client during the System Review b) Release the Client Agency’s data to the public Crimemapping.com site after the 10 day review period c) Prepare and submit a TCR.
7.12.1.2 Client Responsibilities
a) Review the Agency’s data on the Crimemapping Staging Site b) Provide approval to release the Agency’s data to the public Crimemapping.com site prior to expiration of the 10 day review period if desired
c) Review and approve the appropriate TCRs
#11..
- 822 -
Project Execution
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
71 7.13 Implementation of System Interfaces
7.13.1 Inform Standard Interfaces’ Requirement Gathering and Configuration The functionality and applicable configuration options for each of the TriTech Standard Interfaces are described in the Interface Requirements Documents (IRD).
A TriTech Systems Engineer will review the IRDs for each of the applicable Standard Interfaces with the Client’s subject matter experts and prepare a configuration worksheet (Interface Configuration Document – ICD) detailing the parameters that will be set to meet the desired functionality for the Interface. This process may be performed for different interfaces at different times. This process will be performed remotely via phone conference. The Client is responsible for engaging the third-party vendors whose systems are being interfaced with, so that an end to end flow of the data is discussed.
TriTech Systems Engineer will configure and install the Standard interfaces on Client’s system hardware.
IRDs are not Client specific documents, and not subject to edits, changes, or approval. Client specific configurations for Standard Interfaces are documented in configuration worksheets (ICD) and must be approved prior to configuration of the interface.
Installation and configuration of Standard Interfaces can only be performed by qualified members of TriTech System Engineering or Engineering teams, using proprietary tools. Any changes to the requirements of the Records Check Interface from the approved Configuration worksheet will be subject to additional cost and configuration time. Once each of the Standard Interfaces are installed and configured, they can be staged for FAT.
TriTech is not responsible for coordination, management, or covering the cost of any software, work, customization, coding or testing that is required to be performed by the third-party vendors engaged in the implementation of the standard or custom interfaces, unless the work is defined under a subcontract with TriTech within the scope of this Purchase Agreement.
Note 1: Standard Interfaces are developed and enhanced within the TriTech product version process for TriTech software products (such as Inform CAD). Changes to standard Interfaces will require adherence to the development life cycle therein. Changes to standard Interfaces that are delivered within this life cycle will require the Client’s system to be on a compatible version.
Note 2: The Client’s provision of Interface Requirements for Standard Interfaces is an early Project checkpoint. This information is needed to prepare the configuration sheets for Standard Interfaces. Incomplete, inaccurate or delayed information can have a cascading effect on the Project Schedule, and may result in a significant delay in completion of the project, since modification to Standard Interfaces are only released with a major version of Inform CAD. #11..
- 823 -
Project Execution
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
72 Note 3: Any changes to the configuration of Standard Interfaces made by the Client makes the Interface non-supportable, and all troubleshooting efforts resulted by such changes will be subject to additional cost.
Note 4: The Client is responsible for any services or software needed from such Third-Party Systems to allow for interaction with the Third-Party System or for connecting to TriTech Interfaces Software in the absence of a Third Party API. TriTech is not responsible for any cost associated for the API, any required third party lab or certification testing, cost associated with required programming or custom work by the third-party vendors, or any license fees that may be required by the third party vendors.
7.13.2 Custom Interfaces’ Requirement Gathering and Configuration A TriTech Systems Engineer will review requirements specified by the Purchase Agreement applicable to Custom Interfaces, and lead gathering detailed operational requirements within the scope of the Purchase Agreement. This process may be performed for different interfaces at different times. This process will be performed remotely via phone conference.
Once sufficient information has been gathered to describe the operational functionality of the Interface, the Systems Engineer will create Operational Scenario Documents (OSD) detailing the operation of the Interface. Client’s input in detailing all relevant information regarding the operations of these interfaces and interactions with the external systems are essential to timely and accurate development of the OSDs. The completed OSDs will be provided for Client’s review. This document must be approved by both the Client and TriTech prior to development. The Client will be given a TCR that the document was provided, meets the requirements and has been reviewed with the Client. The Client must review the OSD within 10 days from delivery by TriTech, and provide comments and questions back to TriTech or provide approval if no changes or edits is necessary.
The Client is responsible for obtaining the API for each of the third-party vendors that TriTech applications are interfacing with. The API must be for the version of the third-party software that TriTech will be interfacing with. The timelines for providing these documents to TriTech is concurrent with development of the OSD, so that any limitations associated with the level of integration with the third-party application can be taken into consideration.
Delays in review and approval of the OSDs can impact timely development of the interfaces, and ultimately delay the Go Live of the system. All requirement changes for Custom Interfaces after approval of the OSD shall follow the Change Management process, and may be subject to additional cost and development time.
Upon approval of the OSD the custom interfaces are developed by TriTech engineering team. Once developed, these interfaces will be installed on Client equipment and go through testing with the Client and applicable third party vendors who own and administer the vendor side of the interface.
The Client is also responsible for coordinating execution of a mutual Non-Disclosure Agreement (NDA) between the third-party vendors and TriTech before any technical information or documentation can be exchanged or testing can commence.
#11..
- 824 -
Project Execution
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
73 TriTech is not responsible for coordination, management, or covering the cost of any software, work, customization, coding or testing that is required to be performed by the third-party vendors engaged in the implementation of the standard or custom interfaces, unless the work is defined under a subcontract with TriTech within the scope of this Purchase Agreement.
Note 1: The Client’s provision of Interface requirements for each of the Custom Interfaces is an early Project checkpoint. This information is needed to develop the OSDs for Custom Interfaces.
Incomplete, inaccurate, or delayed information can have a cascading effect on the Project Schedule, and may result in a significant delay in completion of the project.
Note 2: The Client is responsible for providing Application Programming Interface (API) documentation for the Third-Party Systems. The API must document the integration process for the level of interface integration defined by TriTech’s response to the RFP. The Client is responsible for any services or software needed from such Third-Party Systems to allow for integration with the third party system.
Note 3: The scope of functionality for the custom interfaces is limited to 1) the capability of the TriTech System being interfaced and 2) the Application Programming Interface (API) capabilities of the external system being interfaced.
Note 4: High level descriptions of each of the custom interfaces in Appendix D - Custom TriTech Interfaces, will become the basis for the scope of detailed requirements, described in the OSD. Any changes in the requirements documented in the System OSDs, post approval of the OSDs are subject to formal Change Order.
Note 5: The Client is responsible for coordinating the development of the vendor side of all interfaces to the third party applications for the interfaces that the vendor is not a TriTech Subcontractor, based on the Purchase Agreement.
Note 6: TriTech is not responsible for any cost associated for the API, any required third party lab or certification testing, cost associated with required programming or custom work by the third party vendors, or any license fees that may be required by the third party vendors.
7.13.3 Interface Functional Acceptance Testing (FAT)
All Standard and Custom Interfaces are subject to Functional Acceptance Testing (FAT). FAT for Standard Interfaces is based on a standard set of TriTech FAT documents for each interface, as they are applicable to Client’s configurations.
#11..
- 825 -
Project Execution
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
74 FAT for Custom Interfaces are based on the functionality described in the approved OSD for the interface.
This process will be based on an FAT document developed by the Systems Engineer. The test source will be the provided IRDs; therefore, all Standard Interfaces will be tested against standard, predefined TriTech FAT documents. These tests have a standard format and will be sent to the Client for review prior to conducting the FAT.
TriTech will repeat any failed FAT test following the correction of any issues which has caused the test to fail.
7.13.3.1 TriTech Responsibilities
a) Provide the IRD to the Client for review for each of the Standard Interfaces. b) Prepare and submit a TCR to the Client, documenting the delivery of the IRDs to the Client for Standard Interfaces.
c) Review the IRD with the Client for each of the Standard Interfaces and gather and document the configuration options for the Interface.
d) Install and Configure the Standard Interfaces based on the agreed upon configurations. e) Gather the operational requirements for each of the Custom Interfaces and develop and OSD. f) Provide the OSD to the Client for review and approval. (for custom interfaces only) g) Prepare and submit a TCR to the Client, documenting Client’s approval of the OSD for each of the Custom Interfaces.
h) Develop the Custom Interfaces based on the approved OSD. i) Install and configure the Custom Interfaces.
j) Prepare and submit TCRs upon installation of the Interfaces. k) Develop FAT documents reflecting feature descriptions found within the provided and applicable OSDs. l) Provide the FAT documents to the Client for review prior to conducting the FAT for each interface. m) Provide a TCR to the Client to approve the receipt of the FAT documents. n) Assist the Client in conducting Acceptance Testing in accordance with FAT documents. o) Prepare and Submit a TCR, documenting completion of FAT including any exceptions to FAT. p) Resolve FAT issues and re-run tests as required.
7.13.3.2 Client Responsibilities
a) Participate in the review of the IRDs and provide the configuration information to TriTech in a timely manner.
b) Provide the information that are necessary for development of the OSD for each Custom Interface. c) Obtain the API for each of the third-party applications that TriTech interfaces with and provide the document to TriTech.
d) Review and approve the OSDs based on the required timelines. e) Engage the third-party vendors in the requirement gathering, development, testing and other interface development activities.
#11..
- 826 -
Project Execution
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
75 f) Review and approve the FAT documents.
g) Participate in the FAT.
h) Assist TriTech in documenting FAT findings and results. i) Review and approve the applicable TCRs.
7.14 System and Subsystem Go Live
The “cut over” of each of the Inform CAD, Inform Mobile, Inform RMS,Inform CAD Browser Subsystems, and Interfaces into the production environment is a highly orchestrated activity that will require a number of resources from both the Client and TriTech teams. It is recommended that Inform CAD, Mobile, and the Inform CAD Subsystems (such as the Go Live interfaces) are taken into production at one time, then other systems, such as Inform RMS and Inform Jail are taken into production in phases following the Inform CAD cutover.
7.14.1 Inform CAD, Mobile, and Inform CAD Subsystem Go Live The “cut over” of the Inform CAD, Inform Mobile, Inform CAD Browser and Interfaces into the production environment is a team approach. It is the intent of the Project to take all these Subsystems Live at the same time.
TriTech utilizes a pre-Go Live checklist for Inform CAD with various activities to ensure readiness of the System prior to Go Live. There are some tasks that must be performed by the Client, which are detailed in the pre-Go Live checklist. This activity begins several weeks in advance of Go Live.
TriTech will provide the Client with a standard Go Live authorization letter that must be approved by the Client no later than 3 weeks prior to Go Live. This letter will list all the Subsystems that are scheduled for the Go Live, and any exceptions to Go Live applications. It also memorializes the date and time of Go Live, as well as the Client’s confirmation that the System and staff are ready for Go Live.
TriTech will provide the Client with a Go Live authorization letter, detailing the date and time of Go Live and those components that will be taken into Live operations. It is necessary that the Client approves this letter no later than 2 weeks prior to the scheduled Go Live to secure the Go Live support resources.
Prior to Go Live the pre-production test data will be purged from the Client’s system. The equipment is staged to move into the communications center and/or units. Units and personnel are logged into the System and Interfaces are activated.
At Go Live, the TriTech and Client implementation teams will support the users in the transition to the new System. Any issues are logged and resolved through TriTech Customer Services. A more detailed Go Live plan will be provided with adequate lead time.
The duration of the Go Live support for Inform CAD and its subsystems for this project will be 3 days (to include pre and post cutover) by 2 people. The Project Manager will be an active participant in the Go Live process. Go Lives are conducted on consecutive weekdays (Monday-Friday). Go Lives that require TriTech support that begins before or extends beyond weekdays will be subject to additional charge. The breakdown of onsite Go Live Services is as follows:
Inform CAD, Mobile, and Inform CAD Interfaces:
#11..
- 827 -
Project Execution
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
76 2 people for 3 days covering 24 hour shifts
7.14.1.1 TriTech Responsibilities
a) Provide to the Client a Go Live check list with adequate time for review. b) Prepare and submit a Go Live authorization letter to the Client. c) Identify the participants for the Go Live in accordance with the terms of the Purchase Agreement. d) Have specified personnel onsite in advance of the Go Live date to begin the final inspection of the Client’s system as part of the Go Live check list.
e) Prepare and submit a TCR upon first Go Live operation of the Inform CAD.
7.14.1.2 Client Responsibilities
a) Timely review of the Go Live checklist.
b) Complete Mobile roll out process in sufficient time to allow for testing prior to Go Live. c) Review and approve the Go Live authorization letter no later than 3 weeks prior to the scheduled Go Live.
d) Provide adequate persons for the supervision and monitoring of the Client’s Inform CAD end users 24/7 beyond the participation of the TriTech staff.
e) Provide dedicated workstations (preferably 2 workstations) for TriTech support staff during Go Live support period.
f) Provide 24/7 support by the Client’s IT department.
g) Develop a process for the reporting and resolution of field mobile issues. h) Review and approve the applicable TCR.
7.14.2 Inform RMS Go Live
Once end-user training has been completed and Inform RMS is ready to be placed into production, TriTech will assist the Client in placing the system into operation. In preparation for Go Live, TriTech will assist the Client in cleaning the training data from the Inform RMS System.
TriTech will provide the Client with a standard Go Live authorization letter that must be approved by the Client no later than 3 weeks prior to Go Live. This letter will list all the Subsystems that are scheduled for the Go Live, and any exceptions to Go Live applications. It also memorializes the date and time of Go Live, as well as the Client’s confirmation that the System and staff are ready for Go Live.
At Go Live, the TriTech and Client implementation teams will support the users in the transition to the new System. Any issues are logged and resolved through TriTech Customer Services. A more detailed Go Live plan will be provided with adequate lead time.
The duration of the Go Live support for Inform RMS and its subsystems for this project will be 2 days (to include pre and post cutover) by 2 people. Go Lives are conducted on consecutive weekdays (MondayFriday). Go Lives that require TriTech support that begins before or extends beyond weekdays will be subject to additional charge. The breakdown of onsite Go Live Services is as follows:
Inform RMS Go Live Coverage:
2 people for 2 days covering single a shift during normal business hours #11..
- 828 -
Project Execution
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
77 7.14.2.1 TriTech Responsibilities
e) Prepare and submit a Go Live authorization letter to the Client. a) Identify the participants for the Go Live in accordance with the terms of the Purchase Agreement. b) Have specified personnel onsite in advance of the Go Live date to begin the final inspection of the Client’s system as part of the Go Live preparations.
c) Be on-site to assist the Client in placing the system into production status. d) Assist Client staff in using the system and assist the computer operations staff in supporting the system. e) Provide System monitoring following the actual System cut over as specified within the Purchase Agreement.
f) Prepare and submit a TCR upon first Live operation of Inform RMS.
7.14.2.2 Client Responsibilities
d) Complete Inform RMS roll out to support the Go Live date. e) Review and approve the Go Live authorization letter no later than 3 weeks prior to each scheduled Go Live.
f) Complete all relevant end user training to support the Go Live of the Subsystems. g) Place the software into production and begin operational use in consultation with TriTech and in accordance with the project schedule.
h) Provide adequate persons for the supervision and assisting the end users beyond the participation of the TriTech staff.
i) Provide dedicated workstations for TriTech support staff during Go Live support period. j) Provide Client IT support to cover all Client end user and TriTech staff hours of operation. k) Develop a process for the reporting and resolution of issues. l) Review and approve the applicable TCR.
7.14.3 CrimeView Go Live, System Review, & Acceptance
“Go Live” for CrimeView occurs at the point when the Dashboard application is available to trained Administrator users. This initiates the System Review, during which the client takes responsibility for testing and data validation, and TriTech provides support and consultation.
7.14.3.1 CrimeView & FireView System Review
Once one or more CrimeView Administrator logins have been provided to the client, and the CrimeView Administrator/Designer training has been completed, the application will be considered “live”, and the System Review will begin. During the System Review, the client is responsible for reviewing the application and informing the TriTech Project Manager of any noticed or potential issues or deficiencies with the configuration or data. The System Review period will expire in 10 business days, at which point, TriTech will address all submitted items prior to Train the Trainer training.
TriTech responses to each submitted item will fall into one of the following categories:
#11..
- 829 -
Project Execution
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
78 This item refers to something in the application or data import configuration that has been confirmed and fixed/changed.
Further information or action from the Client is required in order to assess the item (a time window for Client action will be provided).
This item is a result of the source query or GIS data provided by the Client and requires Client action to fix (a time window for Client action will be provided). This item identifies a software bug that has been submitted for review and rectification. This item refers to a function or known limitation of the application that lies in the application code rather than the configuration, and changes to the application code are excluded from this project.
Suggested Client Review Items:
Presence of contracted Query Layers (example: Calls for Service, Incidents, Arrests, etc.) o Query Layers are listed/visible in the “What” query panel. Query layer data integrity and completeness:
o Compare/confirm the number of records vs. the source database (CAD/RMS) by running identical queries in both systems.
o Confirm the fields identified in the Statement of Work are included by viewing the data in the Table.
o Confirm that the fields displayed in the Table contain the expected values (including codes/descriptions)
o Review Crime/Incident/Data type categorization/symbology. Saved Query Completeness and Accuracy
o Confirm the accuracy and completeness of the Saved Query picklists on the “What” query panel.
o Perform queries and confirm that they return the expected results. Geocoding
o Use Pin Map queries and/or Filter widgets to plot records on the map and spot check general accuracy to confirm the mapped location matches the address/location listed on the record.
o Spot check the address values displayed in the Dashboard (every query layer) against the address listed in the source system/data.
Geography and Operational Layers
o Confirm the Geographic Query Layers identified in project planning (up to 10) are present and the proper selection values are listed on the “Where” query panel (example: “Zone 1, Zone 2, Zone 3…”)
o Confirm the Operational Layers identified in project planning (up to 5) are present and accurately reflect the GIS data provided for the project. #11..
- 830 -
Project Execution
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
79 7.14.3.1.1 TriTech Responsibilities
a) Prepare and submit a “Go Live” TCR at the completion of Administrative/Designer Training b) Notify the Client that the System Review period has begun, provide the review items listed above c) Receive and address all items/issues submitted by the Client during the System Review d) Prepare and submit a TCR.
7.14.3.1.2 Client Responsibilities
a) Complete the Suggested Client Review Items listed above. b) Inform the TriTech Project Manager of any questions, issues, or requested configuration changes. c) Review and approve the appropriate TCRs
7.14.3.2 CrimeView & FireView Acceptance
The CrimeView & FireView Dashboard application will be considered Accepted upon completion of the System Review.
7.15 Reliability Acceptance Period
Upon Go Live for the Subsystem(s), the Client shall use the Subsystem for a thirty (30) consecutive day period to verify operational functionality in a live environment. If no Critical Priority or Urgent Priority Software Errors (as those terms are defined in Addendum E to the Agreement) are reported during such thirty (30) day period, the Subsystems shall be deemed to have achieved Final Acceptance. In the event that a Critical Priority or Urgent Priority Software Error occurs during the Acceptance Test Period, TriTech shall commence actions in accordance with the Software Support Agreement to correct the reported error.
Note: If Subsystems do not Go Live on the same day, or if agencies and/or PSAPs Go Live in multiple phases, the Reliability Acceptance Period for each Subsystem will start the first day that Subsystem Goes Live and is used in a Production environment by any agency and/or PSAP. There will not be separate Reliability Acceptance Periods as subsequent agencies and/or PSAPs Go Live.
In the event that a Critical Priority Software Error occurs between day one (1) and day thirty (30) of the Acceptance Test Period, the Acceptance Test Period will be stopped and restarted at day one (1) once the Software Error has been resolved in accordance with the Software Support Agreement.
In the event that an Urgent Priority Software Error occurs between day one (1) and day fifteen (15), the Acceptance Test Period will be stopped and restarted from day one (1) once the Software Error has been resolved in accordance with the Software Support Agreement. If the Software Error occurs between day fifteen (15) and day thirty (30), the Acceptance Test Period will be stopped and restarted from the day the resolution has been provided in accordance with the Software Support Agreement. #11..
- 831 -
Project Execution
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
80 Critical or Urgent Priority software errors caused by factors that are outside of TriTech’s control, and/or from variables which are outside the scope of TriTech’s responsibilities, will not be counted Critical or Urgent Priority software errors. Examples of such issues could be, but are not limited to:
Power failures
Operator error
External network failure
Availability of components that are not provided by TriTech but interface to/from the TriTech solution Hardware or Operating System software
Non TriTech supplied software components introduced to the working environment During the Acceptance Test Period, the Subsystem will be frozen, (i.e., no changes, fixes, and/or updates will be applied, except those that are required to address Downtime Failures associated with the Acceptance Test Period.)
At the conclusion of the Acceptance Test Period, as further defined in the Agreement, the Subsystem will be deemed accepted by the Client.
7.15.1.1 TriTech Responsibilities
a) Document the start of the Reliability Acceptance Period upon Go Live of the Subsystem in a TCR. b) Address any Reliability Acceptance Period issues that are reported during this test period. c) Document other issues that are not considered “Reliability Acceptance” issues to be addressed as part of the support and maintenance of the Subsystem.
d) Provide the appropriate TCR to document the Final Acceptance of the System.
7.15.1.2 Client Responsibilities
a) Report issues when they develop.
b) Review and approve the applicable TCRs.
#11..
- 832 -
Implementation of Inform Jail 6
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
81 8 IMPLEMENTATION OF INFORM JAIL 6
Inform Jail 6 is implemented through a series of standard steps and process gates. These steps are designed to ensure that the operational needs of the Client are identified, the configurations are verified, and the system is tested to validate the proper functionality of the system prior to deployment. The following sections describe the implementation process for Inform Jail.
8.1.1 Software
The software detailed in the following sections includes, but is not limited to, the listed functionality.
Inform Jail 6 Suite Base Operating system software
Database software
Master name index
Master address index
Master vehicle index
Secure intra-Customer messaging
Configurable dashboard
Web address links
No duplicate data entry
Authentication
Inform Jail 6 Suite
Administration
Equipment
Fleet Management
Iventory Management
Purchase Requisitions
Service Dogs
Policy Manual
Full audit trail
Custom Forms
Financial (Core) Double-entry accounting
Automatic invoice creation
Configurable addition of fees
based on Records workflow
Account reconciliation
Receipt generation
Statement printing
Bulk Invoice Payments
Full audit trail
Jail (Core) Booking, Intake, and Release
Wizard
Cell Occupancy Log
Activities
Basic Bank
Issued Property
Medicine
Jail Billing
Bond Payments
Sentence calculation and Good
Time
Inmate Property
Victim Notification
Visitor logging
Jail Log
Shift Log
Court Events
Classification
Cell Recommendation
Inmate Classes and Transportation
Full audit trail
#11..
- 833 -
Implementation of Inform Jail 6
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
82 Jail (Advanced) Advanced Inmate Bank
Expenses
Expungement Log
Sentence Reductions
Inmate Checks
Inmate Work Shifts
Stay Scheduling (Weekenders)
Multiple Facilities
Jail workflow
Custom Forms
Personnel (Core) Personnel Log Full audit trail
Reporting (Core) Pre-defined reports
Custom reports
Ad-hoc reports
Drag and drop report
building
Export to PDF, XLS, XML, TXT
Custom data filters
Statistical analysis
Scheduled reports
COMSTAT compatible
Emailed reports
8.1.2 Interfaces
Any interfaces that cannot be deployed as part of System go-live due to Customer or a third-party vendor not being ready for deployment shall not delay System Acceptance.
Customer shall not allow any party, other than TriTech, to add, update, or delete database records or file system objects directly to or on the server or database except as provided for in the Inform Jail 6 Documentation.
Customer shall not access any Server Hardware except as provided in the Inform Jail 6 Documentation or cause any software except the Software provided under this Agreement to be installed on or executed on the Server Hardware.
8.1.2.1 Jail – N-DEx Adapter (IB IEPD)
This is an adapter that produces XML that is conformant to the N-DEx Incarceration/Booking (IB) IEPD.
Inform Jail 6 transmits data to the N-DEx web service via the existing N-DEx WSDL. Data transmission does not include all fields defined in the IEPD.
8.1.2.2 Inform Jail 6 – Time Synchronization Interface
This is a one-way interface that uses NTP to keep all Inform Jail 6 Servers' clocks in sync.
8.1.3 Customer Hardware, Network and Power Requirements TriTech is not responsible for installation or networking of the computer hardware required for operating Inform Jail 6 Software.
Unless otherwise specified, Customer will be responsible for providing the following to meet the hardware, network and power requirements for the System.
#11..
- 834 -
Implementation of Inform Jail 6
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
83 8.1.3.1 Server Hardware
1. Two (2) rack-mount servers will be purchased by Customer as part of this agreement.
2. They will be configured as Inform Jail 6 Servers as follows:
(a) One (1) Production Server with Lantronix remote access device (b) One (1) Testing/Training server
3. The servers will be installed at the Glendale Police Department.
4. Ten (10) inches of rack space is required at the primary server location for one (1) Inform Jail 6 Production rack-mounted server (3.5”), one (1) Inform Jail 6 Testing/Training rack-mounted server (3.5”), and one (1) Lantronix remote access device (3.0”).
8.1.3.2 Production and Testing/Training Server Network Requirements
1. Six (6) open Ethernet cables and ports to be used by one (1) Inform Jail 6 Production rack-mounted server, one (1) Inform Jail 6 Testing/Training rack-mounted server, and one (1) Lantronix remote access device.
2. Static IP addresses that include four (4) for the Inform Jail 6 Production rack-mounted server, three (3) for the Inform Jail 6 Testing/Training rack-mounted server, and one (1) for the Lantronix remote access device.
3. Network access that maintains low-latency and high bandwidth that includes a Virtual Private Network (VPN) to support remote users per the requirements that are set forth in the Network Requirement Specifications and Server Requirement Specification documents provided by TriTech.
8.1.3.3 Production and Testing/Training Server Power Requirements
1. One (1) uninterrupted power supply (UPS) that support 1000 watts.
2. Power supply that will handle dual 720 watts for one (1) Inform Jail 6 Production rack-mounted server, one (1) Inform Jail 6 Testing/Training rack-mounted server, and one (1) Lantronix remote access device.
3. Server cooling that will ensure the appropriate temperatures for one (1) Inform Jail 6 Production rackmounted server, one (1) Inform Jail 6 Testing/Training rack-mounted server, and one (1) Lantronix remote access device.
8.1.4 Implementation Process Overview
TriTech uses a multi-phase approach to ensure a successful implementation for each Inform Jail 6 Customer.
Trained and experienced members of the TriTech implementation team move through the process with Customers to ensure successful outcomes. Timelines will be discussed with Customer’s project manager and will be mutually agreed upon to ensure a successful Go Live.
8.1.4.1 Kickoff Meeting
Upon contract signature, a kickoff meeting is scheduled to initiate the implementation process, setting up a #11..
- 835 -
Implementation of Inform Jail 6
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
84 statement of work, server installations and scheduling the Business Practice Review (BPR).
8.1.4.2 Business Practice Review
During this meeting, the TriTech project team works with Customer’s build team and will demonstrate the functionality of Inform Jail 6 modules and guide the agency on their configuration tasks.
8.1.4.3 Configuration
Customer plays a large part in the configuration and setup of the final system. Configuration of Inform Jail 6 software is guided by Business Analysts, via in-person or remote online sessions, but is considered a Customer responsibility to complete.
8.1.4.4 Interfaces
Customer tasks related to interfaces will start immediately after the initial TriTech kickoff meeting. Customer will set up conference calls with TriTech and each interface vendor within two weeks of contract signing or one week of kickoff call. Interfaces to and from TriTech software are created and tested internally before being available for Customer testing.
Customer is responsible for initiating and facilitating the relationship(s) between TriTech and the third-party interface vendor(s).
Inform Jail 6 software interface specifications must be clearly defined in the Interface One Sheet or Interface Specifications Document. If applicable, each interface will be thoroughly tested by Customer before Go Live.
8.1.4.5 Final System Review
Throughout the project, implementation analysts from TriTech will schedule sessions with Customer’s Build Team and end users to review any questions or concerns.
8.1.4.6 Train-the-Trainer and/or End User Training
TriTech offers several options for end user training. All of the training options provide hands-on use of the software with real-world examples. Class sizes are limited to ensure that each individual has sufficient time to practice using the system. When the go live date arrives, users are well-prepared to begin using the new software.
8.1.4.7 Go Live
TriTech provides on-site and/or remote support the day that the new system goes live. Any questions that arise are addressed immediately by the team, ensuring that the first day(s) using the new system goes smoothly.
8.1.5 Training and Go Live Support
8.1.5.1 Training
TriTech staff will provide on-site or remote training.
The number of days specified for ‘on-site’ services herein may include travel days in addition to actual days on site at Customer’s location(s). TriTech will make a good faith effort to minimize the travel time which is necessary for a project by working with Customer to most efficiently plan and schedule the delivery of on-site #11..
- 836 -
Implementation of Inform Jail 6
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
85 services.
8.1.5.2 System Configuration and Training
The first portion of training will be performed by the TriTech project team. Team members will train and guide Customer’s Build Team in configuring the TriTech Suite system, setting up and maintaining code tables, managing users and user rights, among other options. Through TriTech-guided configuration of the system, the Build Team becomes well versed in the TriTech software system administration.
8.1.5.3 Train-the-Trainer and/or End User Training
Trainers will conduct detailed courses for each of Customer’s user groups (such as dispatchers or officers).
The content of each course will be tailored to the features and functionality in Inform Jail 6 software that each group needs to know and use.
8.1.5.4 Refresher Training
TriTech will provide follow-up training (after successful implementation) to refresh existing personnel on best practices with regard to using Inform Jail 6.
8.1.5.5 Training Resources
Training will be scheduled within standard business hours (7:00 AM CST to 6:00 PM CST, Monday through Friday).
The training facilities and equipment will be provided by Customer based on the following:
8.1.5.5.1 Trainer Resources
1. One (1) computer with a network connection
2. Most recent Inform Jail 6 version installed and tested (includes login)
3. Two (2) projectors and two (2) screens set up and tested
4. One (1) podium or desk for trainer
8.1.5.5.2 Trainee Resources
1. Five (5) to ten (10) computers with network connections two (2) monitors required
2. One (1) supervisor will attend every class to address policy questions
3. No more than ten (10) trainees in each class
4. Most recent Inform Jail 6 version installed and tested (includes login)
5. All third-party devices (e.g., printers, scanners, barcode reader, mugshot camera) connected and tested
8.1.5.6 Go Live Support
TriTech staff will assist users with questions that arise during Go Live and will reinforce skills learned during the training sessions. Tritech staff will be on site or remote for Go Live. #11..
- 837 -
Project Closure
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
86 9 PROJECT CLOSURE
When all pre and post go live project deliverables have been completed, Project Closure activities will take place. Support of the System and Subsystems are transitioned to TriTech’s Customer Services Group. Any remaining Project related administrative tasks are completed by TriTech and Client. Project documentation is archived and primary Client interaction is officially handed over from the TriTech Project Manager to the TriTech Account Manager.
9.1.1 System Transition
Following Go Live, there is a transition period where the Client moves from the implementation team to the support team. This transition will change the Client’s primary point of contact from the Project Manager back to the Account Manager. Software support will be handled through the Customer Services Group. The Client’s issues will be entered, tracked, and managed via a computerized and web-enabled issues tracking system. This tracking system will become available to the Client at system installation.
9.1.1.1 TriTech Responsibilities
a) Provide payment reconciliation, final TCRs and final invoices. b) Transition the TriTech point of contact from the Project Manager to the Account Manager and Customer Support Services Department.
c) Provide continued support based on terms of Purchase Agreement.
9.1.1.2 Client Responsibilities
a) Provide approval of Project TCRs within five (5) business days. b) Provide payment reconciliation and payment of final invoices. #11..
- 838 -
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2017 TriTech Software Systems
87 10 APPENDIX A - REQUIRED INFORM CAD DOLF CODE
FILE BUILD
The purpose of this table is to identify specific portions of the System Code files and modules that must be built and configured prior to Inform CAD System DOLF.
Note: Items identified with asterisk (*) are optional, and will be built as specified, only if the Client chooses to use them.
Provided during Implementation.
#11..
- 839 -
Appendix B - Contracted Modifications to Standard TriTech Software Products The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
88 11 APPENDIX B - CONTRACTED MODIFICATIONS TO
STANDARD TRITECH SOFTWARE PRODUCTS
Note: Any changes in the requirements documented in the System OSDs, post approval of the OSDs are subject to formal Change Order.
List of Product Modification OSDs:
There are no product modifications proposed for this project.
#11..
- 840 -
Appendix C - Standard TriTech Interfaces
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
89 12 APPENDIX C - STANDARD TRITECH INTERFACES
Note: The scope of functionality for these Standard interfaces is limited to 1) the capability of the TriTech System being interfaced and 2) the capabilities of the external system being interfaced.
Note: High level descriptions of each of the custom interfaces below will become the basis for the scope of detailed requirements, described in the OSD. Any changes in the requirements documented in the System OSDs, post approval of the OSDs are subject to formal Change Order.
Note: The Client is responsible for coordinating the development of the vendor side of all interfaces to the third party applications for the interfaces that the vendor is not a TriTech Subcontractor, based on the Purchase Agreement.
12.1 Standard Interfaces for Each Environment
The following sections list the Standard Interfaces that are included in this Purchase Agreement. If not explicitly listed, the interface will not be installed and supported in the specific environment.
12.1.1 Production Environment:
a) One (1) Standard Alphanumeric Paging Interface
b) One (1) Standard ANI/ALI Interface
c) One (1) Inform CAD ASAP Interface
d) One (1) Standard Inform CAD to External System Incident Data Transfer Interface
12.1.2 Disaster Recovery Environment:
a) None
12.1.3 Test Environment:
a) None
12.2 NCIC State Message Switch
#11..
- 841 -
Appendix C - Standard TriTech Interfaces
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
90 The Standard NCIC/State Message Switch Solution includes the following Connections, Transactions, and Query Builder Feature (Optional Purchased Feature):
12.2.1 Connections
12.2.1.1 Inform CAD
12.2.1.1.1 Standard Connections for Inform CAD
The following standard connections will be included in the project, subject to applicable access a) State Justice Switch (County Justice Switch in California) for State/NLETS/NCIC transactions b) Inform CAD Be on the Look Out (BOLO) and Supplemental Information. Access is available through Inform CAD and Mobile for BOLO and Supplemental Information (previous incident-related Person, Vehicle, Firearm and Property queries run from Inform CAD or Inform Mobile) queries. c) Inform RMS System from Inform CAD (Only if Client has Inform RMS)
12.2.1.1.2 Custom Connections for Inform CAD
Custom connections allow the ability to access additional records management systems, warrant/court systems, or other accessible external databases. Access to custom connections from Inform CAD and/or Inform Mobile will be identified.
Custom connections included in this Purchase Agreement:
a) No Custom Connections are included as part of this Purchase Agreement
12.2.1.2 Inform RMS
12.2.1.2.1 Standard Connections for Inform RMS
The following standard connections will be included in the project, subject to applicable access a) State Justice Switch (County Justice Switch in California) for State/NLETS/NCIC transactions
12.2.1.2.2 Custom Connections for Inform RMS
Custom connections allow the ability to access additional records management systems, warrant/court systems, or other accessible external databases.
Custom connections included in this Purchase Agreement:
a) No Custom Connections are included as part of this Purchase Agreement
12.2.2 Transactions
12.2.2.1 Standard State/NLETS/NCIC Connection Transactions The following standard transactions will be included in the project, subject to applicable access. These standard queries can be performed via Inform CAD PowerLine, Inform CAD Query entry page, Inform Mobile Query entry page, Inform RMS query entry page.
#11..
- 842 -
Appendix C - Standard TriTech Interfaces
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
91 a) The following Standard State transactions are supported:
Category Message Key Transaction Name
Vehicle BQ Query Boat Registration
Person QWA Wanted Person Inquiry - All
Article TQAB Test QAB - CLETS Property Query
Article TQAN Test QAN - CLETS Property Query
Article TQA Test QA - Single Article Inquiry
Vehicle TQB Test QB - Boat Inquiry
Person TQHA Test CLETS Query Criminal History By
Alpha
Person TQHC Test CLETS Query Criminal History By
CII
Person TQHN Test CLETS Query Criminal History By
Number
Person TQHP Test CLETS Query Personal Data
Person TQM Test CLETS Query Missing Person
Article TQS Test QS - CLETS Property Query
Vehicle TQV Test CLETS Stolen or Felony Vehicle
Inquiry
Vehicle LTS.GQ Query Aircraft Registration
AdminOther Free Form Clets Transaction
Person LTS.KQ NLETS Driver History Query
Person QW Wanted Person Inquiry
Vehicle LTS.RQG NLETS Regional Vehicle Registration
Query
AdminOther LTS.TQ ORION File Query
Person IN DMV Query Drivers License By Name
Person ID DMV Query Drivers License By Number
Vehicle IV DMV Query Vehicle Registration by
Plate or VIN
Article QAN CLETS Property Query By Name
Person QAR SRF Individual Record Inquiry - Arson
Registrant
#11..
- 843 -
Appendix C - Standard TriTech Interfaces
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
92 Article QA Single Article Inquiry
Person QCA SRF Individual Record Inquiry - CDC
Parole
Person QCR SRF Individual Record Inquiry - Career
Criminal
Person QFR SRF Individual Record Inquiry - Federal
Probation
Gun QGHX Gun Inquiry with History Exact Spelling
Gun QG Gun Inquiry
Person QHA CLETS Query Criminal History By
Alpha
Person QHC CLETS Query Criminal History By CII
Person QHN CLETS Query Criminal History By
Number
Person QHP CLETS Query Personal Data
Person QPR SRF Individual Record Inquiry - County
Probation
Person QSR SRF Individual Record Inquiry - Sex
Registrant
Article QS CLETS Property Query By Serial
Number
Person QVCK SRF Inquiry - Abbreviated Response
Person QYA SRF Individual Record Inquiry - CYA
Parole
Article QAB CLETS Property Query By ORI
Vehicle QB Boat Inquiry
Gun QGB Gun Inquiry with LE and History
Person QM CLETS Query Missing Person
Person QVC SRF Inquiry - Full Response
Vehicle QV Stolen or Felony Vehicle Inquiry
Person R.QR Full III Criminal History Record Inquiry
Person UQ NLETS Canadian Driver Record Query
Vehicle RQ NLETS Vehicle Registration Query
Vehicle XQ NLETS Canadian Vehicle Registration
Query
#11..
- 844 -
Appendix C - Standard TriTech Interfaces
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
93 Vehicle VQ NLETS Canadian Vehicle File Query
Person WQ NLETS Canadian Person File Query
Person IQ NLETS Criminal History Identity Query
Person FQ NLETS Full Criminal History Query
Person DQ NLETS Driver Record Query
Person DNQ NLETS Driver History Query By Name
Only
Vehicle RNQ NLETS Vehicle Registration Query By
Name Only
Vehicle MQ Hazardous Materials Query
Person QH III Criminal History Record Inquiry
b) The following responses are supported for parsing local Person and Vehicle state transactions. Parsing of returns is applicable if Client is using Inform RMS and transactions are already defined.
MessageKey
ID
IN
IV
Note: None of above queries include record entry, modification or update (Cancel, Clear, Locate) transactions. This functionality is available only if Query Builder is purchased and the customer builds the queries or TriTech develops the query. Reference Custom Transactions section.
Note: Above queries are included as long as they can run against Standard Connections, or Custom connections specified by the Purchase Agreement.
c) The following queries can be run from any system that is integrated with the TriTech Message Switch (TTMS).
o Standard Inform CAD Connection Transactions
o Inform CAD Be On the Lookout (BOLO) records:
Person by Name or Driver’s License Number
Vehicle by License Plate or VIN
o Inform CAD Supplemental Information records:
Person by Name or Driver’s License Number
#11..
- 845 -
Appendix C - Standard TriTech Interfaces
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
94 Vehicle by License Plate or VIN
Firearm by Serial Number
Property by Serial Number
o Standard Inform RMS Connection Queries
Person by Name or Driver’s License Number
Vehicle by License Plate or VIN
Article
Location
12.2.2.2 Custom Transactions
Custom transactions can be developed or performed via Inform CAD Records Check Client, Inform RMS Inline transactions, and Inform Mobile Query screens only. For an additional cost, custom PowerLine commands can be developed for these transactions in Inform CAD.
Examples of custom transactions include, but are not limited to the following:
a) Boat, aircraft, or ATV/snowmobile queries
b) Restraining Order or Criminal History queries
c) Administrative messages
d) Entry Transactions
e) Modify Transactions (modify existing records)
f) Update Transactions (Clear, Cancel, Locate)
g) Queries against records accessed through custom connections.
Custom connections included in this Purchase Agreement:
a) No Custom Connections are included as part of this Purchase Agreement
12.2.3 Query Builder Feature
The TriTech Query Builder, comprised of the TriTech Message Switch application, provides a user with the ability to define and submit State, NLETS and NCIC transactions to the State’s Records Check system (State system).
The Message Switch’s Query Builder feature allows a Message Switch user to define State, NLETS or NCIC transaction messages by specifying a transaction identifier (such as a Message Key) and a list of input fields that accompanies each message. The user will be able to save the message definition for later editing and test the message by sending it, along with values for the defined fields, to the State system. Finally, the user will #11..
- 846 -
Appendix C - Standard TriTech Interfaces
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
95 be able to designate a message as “active”, which makes it available for use outside of the Message Switch application.
For any system integrated with TTMS, it allows a user to select the pre-defined Message Switch message, enter values for its defined fields, and submit it to the State system. The user will then be able to view the unparsed data from the responses returned by the State system.
Note: State Certification requirements may dictate which transactions must be defined as certification-tested. The certification requirements may require “custom transactions” be certified as part of the approved library of transactions.
12.2.4 Client Responsibility
a) Client to communicate with the State to ensure compliance with any required documentation, certification, and applications they must submit, the timelines involved, and define any deliverables from TriTech that may be required to complete implementation. b) Client to have a subject matter expert (SME) in connectivity to the state or any external connection. c) Client to have a subject matter expert (SME) in operational workflow and expected results from the state or any external connection.
d) Client to establish connectivity to the state or any external connection for testing and production operations.
e) Client to obtain valid ORI’s and/or Mnemonics for testing and production operations.
12.2.5 TriTech Responsibility
a) TriTech will install and configure the TTMS solution and the components to support the TriTech systems (Inform CAD, Inform Mobile, Inform RMS, and Inform Jail). b) TriTech will provide Query Builder (if purchased) training with the client’s State and/or external connection SME.
c) TriTech will configure any final changes to support Go Live.
#11..
- 847 -
Appendix D - Custom TriTech Interfaces
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
96 13 APPENDIX D - CUSTOM TRITECH INTERFACES
Note: The Client is responsible for providing Application Programming Interface (API) documentation to these Third-Party Systems that document the integration process for the level of interface integration defined by TriTech’s response to the RFP. The Client is responsible for any services or software needed from such Third-Party Systems to allow for interaction with the Third Party System API or for connecting to TriTech Interfaces Software in the absence of a Third Party API.
Note: The scope of functionality for these custom interfaces is limited to 1) the capability of the TriTech System being interfaced and 2) the Application Programming Interface (API) capabilities of the external system being interfaced.
Note: High level descriptions of each of the custom interfaces below will become the basis for the scope of detailed requirements, described in the OSD. Any changes in the requirements documented in the System OSDs, post approval of the OSDs are subject to formal Change Order.
Note: The Client is responsible for coordinating the development of the vendor side of all interfaces to the third party applications for the interfaces that the vendor is not a TriTech Subcontractor, based on the Purchase Agreement.
13.1 Custom Interfaces for Each Environment
The following sections list the Custom Interfaces that are included in this Purchase Agreement. If not explicitly listed, the interface will not be installed and supported in the specific environment.
List of Project’s Custom Interfaces (OSDs to be provided):
13.1.1 Production Environment:
a) One (1) Linx Interface
b) One (1) Citation Import Brazos Interface
c) One (1) Suspicious Activity Reporting Interface
d) One (1) CalGang Interface
e) One (1) Complink Expot from Inform RMS – Coplink format #11..
- 848 -
Appendix D - Custom TriTech Interfaces
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
97 f) One (1) Crash Importer – Crossroads Interface
g) One (1) In Car Video Interface
h) One (1) Fingerprint Bidirectional to Inform RMS – 3rd party format i) One (1) Vigilant ALPR Interface
j) One (1) Citation Import TurboData Interface
k) One (1) California Sex Offender and Arson Register (CSAR) Interface l) One (1) eProsecutor Publisher Interface
m) One (1) Jail 6 Reporting Universal Interface Engine
n) One (1) Jail 6 Time Synchronization Interface
13.1.2 Disaster Recovery Environment:
a) None
13.1.3 Test Environment:
a) None
#11..
- 849 -
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2017 TriTech Software Systems
98 14 APPENDIX E - SUBCONTRACTOR(S) STATEMENT(S) OF
WORK
None
#11..
- 850 -
CrimeView & FireView Appendix A – Dashboard Hardware, Software, and Related Requirements
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
99 15 CRIMEVIEW & FIREVIEW APPENDIX A – DASHBOARD
HARDWARE, SOFTWARE, AND RELATED
REQUIREMENTS
NOTE: All hardware and software provided by the Client must be solely dedicated for the CrimeView Dashboard application unless approved in writing by the TriTech Project Manager.
15.1.1.1 Client Hardware
a) Import Server
1. CPU: Quad-core processor, 1.8 GHz or faster
2. 8 GB RAM
3. RAID 1 disk configuration using two (2) 146GB 15K RPM SAS disk drives
4. 1000Mb Network Card
5. Windows Server 2008, 2008 R2, 2012, or 2012 R2 (upon compatibility with ESRI’s ArcGIS software)
6. Local administrator account provided to TriTech
b) Database Server
1. Two (2) Quad-core processors (2.67 GHz minimum) or comparable
2. 16 GB RAM
3. RAID 1 disk configuration using two (2) 300GB 15K RPM SAS disk drives
4. RAID 10 disk configuration using four (4) 146GB 15K RPM SAS disk drives
5. 1000Mb Network Card
6. Windows Server 2012 R2 Standard
c) Application/Web Server
1. Two (2) Quad-core processors (2.67 GHz minimum) or comparable
2. 16 GB RAM
3. RAID 1 disk configuration using two (2) 300GB 15K RPM SAS disk drives
4. 1000Mb Network Card
5. Windows Server 2012 R2 Standard
d) End User Workstations
1. Windows
i. 2 GB RAM
ii. Processor: 1.8 GHz or faster
iii. Minimum monitor resolution: 1280 x 1024 px
#11..
- 851 -
CrimeView & FireView Appendix A – Dashboard Hardware, Software, and Related Requirements
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
100
iv. 100/1000Mb network card
v. Windows: Vista, 7, 8, 9, or 10
vi. Internet Explorer 7 or later
vii. Microsoft Silverlight 5 or later
2. Macintosh (Intel-based)
i. 2 GB RAM
ii. Processor: 1.83 GHz or faster
iii. Minimum monitor resolution: 1280 x 1024 px
iv. 100/1000Mb network card
v. Safari
vi. Microsoft Silverlight 5 or later
15.1.1.2 TriTech Provided Software
a) TriTech ETL Tools: Import Wizard, etc.
b) IQ CrimeView & FireView Dashboard
15.1.1.3 Client Provided Software
a) ArcGIS Desktop 10.0 – Standard License (formerly ArcEditor) b) ArcGIS Desktop VBA Resources for Developers (no cost license only) c) ArcGIS Server 10.0 Standard Enterprise – licensed appropriately for Database Server CPUs/cores
d) Microsoft SQL Server 2008, 2008 R2, 2012, or 2012 R2 – licensed appropriately for Database Server CPUs
15.1.1.4 Other Client Provided Items
a) 2-3 DNS Host (A) records for use as a host-header for the application’s URL (example:
http://dashboard.anytownpolice.com)
b) SSL certificate(s) if required
c) If the site is to be configured to use Active Directory logins: one Active Directory user for the application/TriTech and information about the A/D system and groups. #11..
- 852 -
CrimeView Appendix B – Dashboard GIS Data and Application Specifications The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
101
16 CRIMEVIEW APPENDIX B – DASHBOARD GIS DATA
AND APPLICATION SPECIFICATIONS
16.1.1 GIS Data Specifications
a) Boundary and Landmark Features
The client shall provide files of relevant boundaries and landmarks within the area of interest.
Typical features include:
i. Boundaries and jurisdictions such as beats and reporting districts ii. Landmark information such as schools, parks, and other locations of interest b) Geocoding Reference Data
The client is responsible for providing accurate Geocoding Reference Data in a GIS format that will be used to generate a geocoding service. Reference data may consist of street centerlines, address points, parcels, points of interest, or other GIS features referenceable in the data to be geocoded. The quality of geocoding (placement of records on the map) will be dependent upon the quality, completeness, and consistency of the Geocoding Reference Data and the consistency of location/feature names and references between the Geocoding Reference Data and the CAD, RMS, or other data being geocoded.
c) Map Caches
The CrimeView Dashboard supports the use of one or more map caches, which serve as the background map(s) for the application. ESRI’s ArcGIS Online maps are the current default map caches for the application’s background layers, and at its sole discretion, TriTech may replace one third party map cache source for another third party map cache. The client may provide map caches for the application if the following requirements are met:
i. Caches must be built using the Web Mercator Auxiliary Sphere (102100 or 3857) projection.
ii. If multiple caches will be used in the Dashboard, the zoom levels must match between caches.
iii. The caches must be accessible by URL to all intended end-users and to the location of the Dashboard web server.
iv. The client is responsible for maintaining the map cache(s) and assuring availability and accessibility.
v. The cache site may be required to reside in an SSL website.
16.1.2 Application Specifications
a) Data History
The Dashboard will include a rolling thirty-six (36) months of historical data for each dataset. b) Widgets
#11..
- 853 -
CrimeView Appendix B – Dashboard GIS Data and Application Specifications The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
102
Each widget presents data in based on the query/selection configured for it by the agency.
Widgets can be added, deleted, and modified by administrator or designer users and are updated automatically up to four times per day. A total of 400 widgets are licensed with the Dashboard, and more may be added at an additional cost.
c) Briefing Books
Briefing books are role-oriented containers that store up to 10 pages of widgets at a maximum of 6 widgets per page. Briefing books can be configured by the Client agency’s users as standard functionality. A total of 25 briefing books are licensed with the Dashboard, and TriTech will configure up to 2 standard briefing books to serve as initial content or templates for the Client. d) Symbology
All applications include standard TriTech symbology for each data source. e) Operational Layers
An operational layer represents a set of geographic features, typically boundaries or landmarks, that can be displayed on top of the base geography. TriTech will configure up to five (5) operational layers.
f) Saved Queries
Saved Queries are a set of pre-defined data queries organized in folders. Data queries are based on data available from the RMS or CAD system and vary in design from one application to another. TriTech will configure Saved Queries for the fields designated in Appendix C where code/description lookup tables are available either by provision from the customer or in the source database. Each Saved Query group will query one field within the data, and a maximum of five hundred (500) total saved query pick list items will be provided per designated field. g) Geographic Queries
Geographic queries filter data query by location, a known boundary, point of interest, address or intersection. This will limit search results to those records occurring within the selected boundary or within the specified radius of the point of interest, address or intersection. TriTech will configure up to ten (10) geographic query layers.
h) Users
Three user types will be provided in order to utilize and administer the application:
vi. Three (3) Administrator logins for purposes of creating new content and managing user logins
vii. Unlimited Designer logins for purposes of creating and modifying content viii. Unlimited Standard User logins for purposes of viewing content and creating Queries on Demand
#11..
- 854 -
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2017 TriTech Software Systems
103
17 CRIMEVIEW APPENDIX C – DASHBOARD STANDARD
FIELD LISTS
NOTE: The system will include only the data sources listed in the Error! Reference source not found. section above. The lists below may reference data sources not included in this project.
Calls for Service
ORDER DISPLAY NAME FIELD NAME
REPORT
GRID
SAVED
QUERY CATEGORIES
AD
HOC
1 AGENCY AGENCY YES YES YES YES
2 CALL NUMBER CALL_NUM YES
3 CALL TYPE CALL_TYPE YES YES YES YES
4 CALL DESC CALL_DESC YES YES YES
5 CALL DATE CALL_DATE YES
6 ADDRESS CV_ADDRESS YES
7 APT APT YES
8 COMMON NAME COMMON_NAME YES
9 AREA 1* YES YES YES
10 AREA 2* YES YES YES
11 AREA 3* YES YES YES
12 AREA 4* YES YES YES
13 PRIORITY PRIORITY YES YES YES YES
14 DISPOSITION DISPO_DESC YES YES YES YES
15 CALL SOURCE CALL_SOURCE_DESC YES YES YES YES
16 SHIFT SHIFT YES YES YES YES
17 PRIMARY UNIT PRIM_UNIT YES
18 PRIMARY OFFICER OFFICER YES
19 REMARKS REMARKS YES
20 PRIMARY KEY PRIMARY_KEY YES
*Each Area field may include one of the following: Beat, District, Precinct, Sector, City, Zip Code, etc. #11..
- 855 -
CrimeView Appendix C – Dashboard Standard Field Lists
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
104
Crime Incidents/Offenses
ORDER DISPLAY NAME FIELD NAME
REPORT
GRID
SAVED
QUERY CATEGORIES
AD
HOC
1 AGENCY AGENCY YES YES YES YES
2 CASE NUMBER CASE_NUM YES
3 CRIME CATEGORY CV_LEGEND YES YES YES YES
4 NIBRS OR UCR CRIME_DESC YES YES YES YES
5 STATUTE OR CHARGE CHARGE_DESC YES YES YES YES
6 HIGHEST CHARGE FLAG HIGH_CHARGE_FLAG YES YES YES YES 7 ADDRESS CV_ADDRESS YES
8 APT APT YES
9 AREA 1* YES YES YES
10 AREA 2* YES YES YES
11 AREA 3* YES YES YES
12 AREA 4* YES YES YES
13 COMMON NAME COMMON_NAME YES
14 SPLIT DATE SPLIT_DATE YES
15 FROM DATE FROM_DATE YES
16 TO DATE TO_DATE YES
17 REPORT DATE REPORT_DATE YES
18 SHIFT SHIFT YES YES YES YES
19 CASE STATUS CASE_STATUS_DESC YES YES YES YES
20 CLEARANCE OR DISPO DISPO_DESC YES YES YES YES
21 PREMISE PREMISE_DESC YES YES YES YES
22 WEAPON WEAPON_DESC YES YES YES YES
23 DOMESTIC VIOL DV YES YES YES YES
24 GANG RELATED GANG YES YES YES YES
25 ALCOHOL RELATED ALCOHOL YES YES YES YES
26 PRIMARY OFFICER OFFICER YES
27 PRIMARY KEY PRIMARY_KEY YES
*Each Area field may include one of the following: Beat, District, Precinct, Sector, City, Zip Code, etc. #11..
- 856 -
CrimeView Appendix C – Dashboard Standard Field Lists
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
105
Arrests
ORDER DISPLAY NAME FIELD NAME
REPORT
GRID
SAVED
QUERY CATEGORIES AD HOC
1 AGENCY AGENCY YES YES YES YES
2 ARR NUMBER ARREST_NUM YES
3 CASE NUMBER CASE_NUM YES
4 PERSON NAME FULL_NAME YES
5 ALIAS NAME ALIAS YES
6 STATUTE OR CHARGE CHARGE_DESC YES YES YES YES
7 NIBRS OR UCR CRIME_DESC YES YES YES YES
8 CV_LEGEND OMEGA CRIME TYPE YES YES YES YES
9 ARR DATE ARR_DATE YES
10 ARR LOCATION ARR_ADDRESS YES
11 APT APT YES
12 AREA 1* YES YES YES
13 AREA 2* YES YES YES
14 AREA 3* YES YES YES
15 AREA 4* YES YES YES
16 ARR TYPE ARR_TYPE_DESC YES
17 SEX SEX YES YES YES YES
18 RACE RACE YES YES YES YES
19 ETHNICITY ETHNICITY YES YES YES YES
20 AGE AGE YES YES YES YES
21 DOB DOB YES
22 HEIGHT HEIGHT YES
23 WEIGHT WEIGHT YES
24 HAIR HAIR YES
25 EYES EYES YES
26 SCARS MARKS TATS SMT YES
27 DRIVERS LICENSE LICENSE YES
28 HOME LOCATION HOME_ADDRESS YES
29 PRIM ARR OFFICER OFFICER YES YES YES
30 MUG SHOT MUG_SHOT YES
33 PRIMARY KEY PRIMARY_KEY YES
34 HIGH_CHARGE_FLAG HIGH_CHARGE_FLAG YES YES YES YES *Each Area field may include one of the following: Beat, District, Precinct, Sector, City, Zip Code, etc. #11..
- 857 -
CrimeView Appendix C – Dashboard Standard Field Lists
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
106
Field Interviews
ORDER DISPLAY NAME FIELD NAME
REPORT
GRID
SAVED
QUERY CATEGORIES
AD
HOC
1 AGENCY AGENCY YES YES YES YES
2 FI NUMBER FI_NUM YES
3 REASON REASON_DESC YES YES YES YES
4 PERSON NAME FULL_NAME YES
5 ALIAS NAME ALIAS YES
6 FI DATE FI_DATE YES
7 FI ADDRESS CV_ADDRESS YES
8 APT APT YES
9 AREA 1* YES YES YES
10 AREA 2* YES YES YES
11 AREA 3* YES YES YES
12 AREA 4* YES YES YES
13 SEX SEX YES YES YES YES
14 RACE RACE_DESC YES YES YES YES
15 ETHNICITY ETHNICITY YES YES YES YES
16 AGE AGE YES YES YES YES
17 DOB DOB YES
18 HEIGHT HEIGHT YES
19 WEIGHT WEIGHT YES
20 EYES EYES YES
21 HAIR HAIR YES
22 SCARS MARKS TATS SMT YES
23 DRIVERS LICENSE LICENSE YES
24 GANG NAME GANG_NAME YES YES YES
25 CASE NUMBER YES
26 PRIMARY OFFICER OFFICER YES
27 COMMENTS COMMENTS YES
28 PRIMARY KEY PRIMARY_KEY YES
*Each Area field may include one of the following: Beat, District, Precinct, Sector, City, Zip Code, etc. #11..
- 858 -
CrimeView Appendix C – Dashboard Standard Field Lists
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
107
Citations
ORDER DISPLAY NAME FIELD NAME
REPORT
GRID
SAVED
QUERY CATEGORIES
AD
HOC
1 AGENCY AGENCY YES YES YES YES
2 CIT NUMBER CIT_NUM YES
3 CASE NUMBER CASE_NUM YES
4 PERSON NAME FULL_NAME YES
5 ALIAS NAME ALIAS YES
6 CIT TYPE CIT_TYPE_DESC YES YES YES YES
7 STATUTE STATUTE_DESC YES YES YES YES
8 CIT DATE CIT_DATE YES
9 ADDRESS CV_ADDRESS YES
10 APT APT YES
11 AREA 1* YES YES YES
12 AREA 2* YES YES YES
13 AREA 3* YES YES YES
14 AREA 4* YES YES YES
15 SEX SEX YES YES YES YES
16 RACE RACE_DESC YES YES YES YES
17 ETHNICITY ETHNICITY YES YES YES YES
18 AGE AGE YES YES YES YES
19 DOB DOB YES
20 HEIGHT HEIGHT YES
21 WEIGHT WEIGHT YES
22 HAIR HAIR YES
23 EYES EYES YES
24 SCARS MARKS TATS SMT YES
25 DRIVERS LICENSE LICENSE YES
26 PRIMARY OFFICER OFFICER YES
27 PRIMARY KEY PRIMARY_KEY YES
*Each Area field may include one of the following: Beat, District, Precinct, Sector, City, Zip Code, etc. #11..
- 859 -
CrimeView Appendix C – Dashboard Standard Field Lists
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
108
Traffic Collisions
ORDER DISPLAY NAME FIELD NAME
REPORT
GRID
SAVED
QUERY CATEGORIES
AD
HOC
1 AGENCY AGENCY YES YES YES YES
2 ACC NUM ACCIDENT_NUM YES
3 COLLISION DESC COLLISION_DESC YES YES YES YES
4 ACC DATE ACCIDENT_DATE YES
5 ADDRESS CV_ADDRESS YES
6 APT APT YES
7 INTERSECTION CV_INTERSECTION YES
8 AREA 1* YES YES YES
9 AREA 2* YES YES YES
10 AREA 3* YES YES YES
11 AREA 4* YES YES YES
12 CAUSE DESC CAUSE_DESC YES YES YES YES
13 INJURY INJURY YES YES YES YES
14 FATALITY FATALITY YES YES YES YES
15 SPEED RELATED SPEED_RELATED YES YES YES YES
16 ALCOHOL RELATED ALCOHOL_RELATED YES YES YES YES 17 PED RELATED PED_RELATED YES YES YES YES
18 HIT & RUN HIT_RUN YES YES YES YES
19 WEATHER WEATHER YES YES YES
20 TRAFFIC CONTROL TRAFFIC_CONTROL YES YES YES
21 PRIMARY OFFICER OFFICER YES
22 PRIMARY KEY PRIMARY_KEY YES
*Each Area field may include one of the following: Beat, District, Precinct, Sector, City, Zip Code, etc. #11..
- 860 -
CrimeView Appendix C – Dashboard Standard Field Lists
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
109
Warrants
ORDER DISPLAY NAME FIELD NAME
REPORT
GRID
SAVED
QUERY CATEGORIES
AD
HOC
1 AGENCY AGENCY YES YES YES YES
2 WARRANT NUMBER WARRANT_NUM YES
3 PERSON ID PERSON_ID YES
4 PERSON NAME FULL_NAME YES
5 ALIAS NAME ALIAS YES
6 STATUTE OR CHARGE CHARGE_DESC YES
7 WARRANT TYPE WARRANT_TYPE_DESC YES YES YES YES
8 WARRANT STATUS WARRANT_STATUS_DESC YES YES YES YES 9 ISSUE DATE ISSUE_DATE YES
10 WARRANT LOCATION CV_ADDRESS YES
11 APT APT YES
12 AREA 1* YES YES YES
13 AREA 2* YES YES YES
14 AREA 3* YES YES YES
15 AREA 4* YES YES YES
16 SEX SEX YES YES YES YES
17 RACE RACE_DESC YES YES YES YES
18 ETHNICITY ETHNICITY YES YES YES YES
19 AGE AGE YES YES YES YES
20 DOB DOB YES
21 HEIGHT HEIGHT YES
22 WEIGHT WEIGHT YES
23 EYES EYES YES
24 HAIR HAIR YES
25 SCARS MARKS TATS SMT YES
26 DRIVERS LICENSE LICENSE YES
27 PRIMARY KEY PRIMARY_KEY YES
*Each Area field may include one of the following: Beat, District, Precinct, Sector, City, Zip Code, etc. #11..
- 861 -
CrimeView Appendix C – Dashboard Standard Field Lists
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
110
Arrestees
ORDER DISPLAY NAME FIELD NAME
REPORT
GRID
SAVED
QUERY CATEGORIES
AD
HOC
1 AGENCY AGENCY YES YES YES YES
2 ARREST NUMBER ARREST_NUM YES
3 CASE NUMBER CASE_NUM YES
4 PERSON NAME FULL_NAME YES
5 ALIAS NAME ALIAS YES
6 STATUTE OR CHARGE CHARGE_DESC YES YES YES YES
7 NIBRS OR UCR CRIME_DESC YES YES YES YES
8 CV_LEGEND OMEGA CRIME TYPE YES YES YES YES
9 ARR DATE ARR_DATE YES
10 HOME LOCATION HOME_ADDRESS YES
11 APT APT YES
12 AREA 1* YES YES YES
13 AREA 2* YES YES YES
14 AREA 3* YES YES YES
15 AREA 4* YES YES YES
16 ARR TYPE ARR_TYPE_DESC YES YES YES YES
17 SEX SEX YES YES YES YES
18 RACE RACE_DESC YES YES YES YES
19 ETHNICITY ETHNICITY YES YES YES YES
20 AGE AGE YES YES YES YES
21 DOB DOB YES
22 HEIGHT HEIGHT YES
23 WEIGHT WEIGHT YES
24 HAIR HAIR YES
25 EYES EYES YES
26 SCARS MARKS TATS SMT YES
27 DRIVERS LICENSE LICENSE YES
28 ARR LOCATION ARR_ADDRESS YES
29 PRIM ARR OFFICER OFFICER YES
30 MUG SHOT MUG_SHOT YES
33 PRIMARY KEY PRIMARY_KEY YES
34 HIGH_CHARGE_FLAG HIGH_CHARGE_FLAG YES YES YES YES *Each Area field may include one of the following: Beat, District, Precinct, Sector, City, Zip Code, etc. #11..
- 862 -
CrimeView Appendix C – Dashboard Standard Field Lists
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
111
Gang Members
ORDER DISPLAY NAME FIELD NAME
REPORT
GRID
SAVED
QUERY CATEGORIES
AD
HOC
1 AGENCY AGENCY YES YES YES YES
2 PERSON ID PERSON_ID YES
3 PERSON NAME FULL_NAME YES
4 ALIAS NAME ALIAS YES
5 GANG NAME GANG_NAME YES YES YES YES
6 GANG SUBSET GANG_SUBSET YES YES YES
7 GANG MEMBER RANK GANG_RANK YES YES YES
8 HOME ADDRESS CV_ADDRESS YES
9 APT APT YES
10 REPORT DATE REPORT_DATE YES
11 WARRANT NUMBER WARRANT YES YES YES YES
12 SEX SEX YES YES YES YES
13 RACE RACE_DESC YES YES YES YES
14 ETHNICITY ETHNICITY YES YES YES YES
15 AGE AGE YES YES YES YES
16 DOB DOB YES
17 HEIGHT HEIGHT YES
18 WEIGHT WEIGHT YES
19 EYES EYES YES
20 HAIR HAIR YES
21 SCARS MARKS TATS SMT YES
22 DRIVERS LICENSE LICENSE YES
23 COMMENTS COMMENTS YES
24 PRIMARY KEY PRIMARY_KEY YES
*Each Area field may include one of the following: Beat, District, Precinct, Sector, City, Zip Code, etc. #11..
- 863 -
CrimeView Appendix C – Dashboard Standard Field Lists
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
112
Incident Person Involvements
ORDER DISPLAY NAME FIELD NAME
REPORT
GRID
SAVED
QUERY CATEGORIES
AD
HOC
1 AGENCY AGENCY YES YES YES YES
2 PERSON ID PERSON_ID YES
3 CASE NUMBER CASE_NUM YES
4 PERSON NAME FULL_NAME YES
5 ALIAS NAME ALIAS YES
6 INVOLVEMENT TYPE INVOLVEMENT_DESC
7 STATUTE OR CHARGE
(highest) CHARGE_DESC YES YES YES YES
8 NIBRS OR UCR (highest) CRIME_DESC YES YES YES YES 9 FROM DATE FROM_DATETIME
10 TO DATE TO_DATETIME
11 REPORT DATE RPT_DATETIME
12 ARR DATE ARR_DATE YES
13 HOME LOCATION HOME_ADDRESS YES
14 APT APT YES
15 AREA 1* YES YES YES
16 AREA 2* YES YES YES
17 AREA 3* YES YES YES
18 AREA 4* YES YES YES
19 SEX SEX YES YES YES YES
20 RACE RACE_DESC YES YES YES YES
21 ETHNICITY ETHNICITY YES YES YES YES
22 AGE AGE YES YES YES YES
23 DOB DOB YES
24 HEIGHT HEIGHT YES
25 WEIGHT WEIGHT YES
26 HAIR HAIR YES
27 EYES EYES YES
28 SCARS MARKS TATS SMT YES
29 DRIVERS LICENSE LICENSE YES
30 CASE
STATUS/DISPO/CLEARANCE CASE_STATUS YES
31 INCIDENT LOCATION INC_ADDRESS YES
32 ARREST LOCATION ARR_ADDRESS YES
33 MUG SHOT MUG_SHOT YES
34 PRIMARY KEY PRIMARY_KEY YES
*Each Area field may include one of the following: Beat, District, Precinct, Sector, City, Zip Code, etc. #11..
- 864 -
CrimeView Appendix C – Dashboard Standard Field Lists
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
113
License Plate Reader
ORDER DISPLAY NAME FIELD NAME
REPORT
GRID
SAVED
QUERY CATEGORIES
AD
HOC
1 ACTIVITY ID ACTIVITYID YES
2 AGENCY AGENCY YES YES
3 LICENSE PLATE LICENSE_PLATE YES
4 LICENSE PLATE HYPERLINK LICENSE_PLATE_HYPERLINK YES 5 VEHICLE HYPERLINK VEHICLE_HYPERLINK YES
6 CAMERA ID CAMERA_ID YES
7 CAMERA TYPE CAMERA_TYPE YES
8 PRIMARY KEY*** PRIMARY_KEY YES
9 GEO STATUS*** Status YES
10 HOW GEOCODED*** iwGeoName YES
11 LOCAL_X LOCATION_X
12 LOCAL_Y LOCATION_Y
13 LATITUDE LATITUDE
14 LONGITUDE LONGITUDE
15 ACTIVITY_DATE CV_ACTIVITY_DATE YES
16 ACTIVITY_DOW CV_ACTIVITY_DOW YES
17 ACTIVITY_TIME CV_ACTIVITY_TIME YES
#11..
- 865 -
CrimeView Appendix C – Dashboard Standard Field Lists
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
114
Parolees
ORDER DISPLAY NAME FIELD NAME
REPORT
GRID
SAVED
QUERY CATEGORIES
AD
HOC
1 AGENCY AGENCY YES YES YES YES
2 PERSON ID PERSON_ID YES
3 PERSON NAME FULL_NAME YES
4 ALIAS NAME ALIAS YES
5 STATUTE OR CHARGE CHARGE_DESC YES YES YES YES
6 HOME ADDRESS CV_ADDRESS YES
7 APT APT YES
8 AREA 1* YES YES YES
9 AREA 2* YES YES YES
10 AREA 3* YES YES YES
11 AREA 4* YES YES YES
12 PAR BEGIN DATE PAROLE_DATE YES
13 PAR END DATE DISCHARGE_DATE YES
14 PAR STATUS PAR_STATUS_DESC YES YES YES YES
15 NARC REG HS_REQ / NARC_REG YES YES YES YES
16 SEX_REG PC_290 / SEX_REG YES YES YES YES
17 ARSON_REG PC_457 / ARSON_REG YES YES YES YES
18 VIOLENT PC_3058_RE / VIOLENT YES YES YES YES
19 PROB NARCO PROB_NARCO YES
20 PROB ASSUALT PROB_ASSUALT YES
21 PROB SEX PROB_SEX YES
22 PROB OTHER PROB_OTHER YES
23 SEX SEX YES YES YES YES
24 RACE RACE_DESC YES YES YES YES
25 ETHNICITY ETHNICITY YES YES YES YES
26 AGE AGE YES YES YES YES
27 DOB DOB YES
28 HEIGHT HEIGHT YES
29 WEIGHT WEIGHT YES
30 EYES EYES YES
31 HAIR HAIR YES
32 SCARS MARKS TATS SMT YES
33 DRIVERS LICENSE LICENSE YES
34 PRIMARY OFFICER OFFICER YES
35 MUG SHOT MUG_SHOT YES
*Each Area field may include one of the following: Beat, District, Precinct, Sector, City, Zip Code, etc. #11..
- 866 -
CrimeView Appendix C – Dashboard Standard Field Lists
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
115
Probationers
ORDER DISPLAY NAME FIELD NAME
REPORT
GRID
SAVED
QUERY CATEGORIES
AD
HOC
1 AGENCY AGENCY YES YES YES YES
2 PERSON ID PERSON_ID YES
3 PERSON NAME FULL_NAME YES
4 ALIAS ALIAS YES
5 STATUTE OR CHARGE CHARGE_DESC YES
6 PROB STATUS PROB_STATUS YES YES YES YES
7 PROB BEGIN DATE PROB_BEGIN_DATE YES
8 PROB END DATE PROB_END_DATE YES
9 HOME ADDRESS CV_ADDRESS YES
10 APT APT YES
11 AREA 1* YES YES YES
12 AREA 2* YES YES YES
13 AREA 3* YES YES YES
14 AREA 4* YES YES YES
15 SEX SEX YES YES YES YES
16 RACE RACE_DESC YES YES YES YES
17 ETHNICITY ETHNICITY YES YES YES YES
18 AGE AGE YES YES YES YES
19 DOB DOB YES
20 HEIGHT HEIGHT YES
21 WEIGHT WEIGHT YES
22 EYES EYES YES
23 HAIR HAIR YES
24 SCARS MARKS TATS SMT YES
25 DRIVERS LICENSE LICENSE YES
26 PRIMARY OFFICER OFFICER YES
27 MUG SHOT MUG_SHOT YES
28 PRIMARY KEY PRIMARY_KEY YES
*Each Area field may include one of the following: Beat, District, Precinct, Sector, City, Zip Code, etc. #11..
- 867 -
CrimeView Appendix C – Dashboard Standard Field Lists
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
116
Recovered Vehicles
ORDER DISPLAY NAME FIELD NAME
REPORT
GRID
SAVED
QUERY CATEGORIES
AD
HOC
1 AGENCY AGENCY YES YES YES YES
2 CASE NUMBER CASE_NUM YES
3 STATUTE OR CHARGE CHARGE_DESC YES YES YES YES
4 RECOV DATE REC_DATE YES
5 FROM DATE FROM_DATE YES
6 TO DATE TO_DATE YES
7 ADDRESS CV_ADDRESS YES
8 APT APT YES
9 COMMON NAME COMON_NAME YES
10 PREMISE PREMISE_DESC YES YES YES YES
11 AREA 1* YES YES YES
12 AREA 2* YES YES YES
13 AREA 3* YES YES YES
14 AREA 4* YES YES YES
15 CASE STATUS CASE_STATUS_DESC YES YES YES YES
16 VEH STATUS VEH_STATUS_DESC YES YES YES YES
17 RECOV STATUS RECOV_STATUS_DESC YES YES YES YES 18 VEHICLE TYPE VEH_TYPE_DESC YES YES YES YES
19 VEHICLE YEAR VEH_YEAR YES YES YES
20 VEHICLE MAKE VEH_MAKE_DESC YES YES YES YES
21 VEH MODEL VEH_MODEL YES YES YES
22 VEH COLOR VEH_COLOR YES YES YES
23 VEH DOORS VEH_DOORS YES YES YES
24 VEH LIC PLATE NO VEH_LICENSE YES
25 VEH LIC PLATE ST VEH_STATE YES
26 VEHICLE VIN VEH_VIN YES
27 RECOV CONDITION RECOV_CONDITION_DESC YES YES YES YES 28 PRIMARY OFFICER OFFICER YES
29 PRIMARY KEY PRIMARY_KEY YES
*Each Area field may include one of the following: Beat, District, Precinct, Sector, City, Zip Code, etc. #11..
- 868 -
CrimeView Appendix C – Dashboard Standard Field Lists
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
117
Stolen Vehicles
ORDER DISPLAY NAME FIELD NAME
REPORT
GRID
SAVED
QUERY CATEGORIES
AD
HOC
1 AGENCY AGENCY YES YES YES YES
2 CASE NUMBER CASE_NUM YES
3 STATUTE OR CHARGE CHARGE_DESC YES YES YES YES
4 FROM DATE FROM_DATE YES
5 TO DATE TO_DATE YES
6 RECOV DATE REC_DATE YES
7 ADDRESS CV_ADDRESS YES
8 APT APT YES
9 COMMON NAME COMON_NAME YES
10 PREMISE PREMISE_DESC YES YES YES YES
11 AREA 1* YES YES YES
12 AREA 2* YES YES YES
13 AREA 3* YES YES YES
14 AREA 4* YES YES YES
15 CASE STATUS CASE_STATUS_DESC YES YES YES YES
16 VEH STATUS VEH_STATUS_DESC YES YES YES YES
17 RECOV STATUS REC_STATUS_DESC YES YES YES YES
18 VEH TYPE VEH_TYPE_DESC YES YES YES YES
19 VEH YEAR VEH_YEAR YES YES YES
20 VEH MAKE VEH_MAKE_DESC YES YES YES YES
21 VEH MODEL VEH_MODEL YES YES YES
22 VEH COLOR VEH_COLOR YES YES YES
23 VEH DOORS VEH_DOORS YES YES YES
24 VEH LIC PLATE NO VEH_LICENSE YES
25 VEH LIC PLATE ST VEH_STATE YES
26 VEHICLE VIN VEH_VIN YES
27 RECOV CONDITION RECOV_CONDITION_DESC YES YES YES YES 28 PRIMARY OFFICER OFFICER YES
29 PRIMARY KEY PRIMARY_KEY YES
*Each Area field may include one of the following: Beat, District, Precinct, Sector, City, Zip Code, etc. #11..
- 869 -
CrimeView Appendix C – Dashboard Standard Field Lists
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
118
Sex Registrants
ORDER DISPLAY NAME FIELD NAME
REPORT
GRID
SAVED
QUERY CATEGORIES
AD
HOC
1 AGENCY AGENCY YES YES YES YES
2 PERSON ID PERSON_ID YES
3 PERSON NAME FULL_NAME YES
4 ALIAS NAME ALIAS YES
5 STATUTE OR CHARGE CHARGE_DESC YES YES YES YES
6 RISK LEVEL RISK_LEVEL YES YES YES YES
7 REGISTRATION DATE REG_DATE YES
8 HOME LOCATION CV_ADDRESS YES
9 APT APT YES
10 AREA 1* YES YES YES
11 AREA 2* YES YES YES
12 AREA 3* YES YES YES
13 AREA 4* YES YES YES
14 SEX SEX YES YES YES YES
15 RACE RACE_DESC YES YES YES YES
16 ETHNICITY ETHNICITY YES YES YES YES
17 AGE AGE YES YES YES YES
18 DOB DOB YES
19 HEIGHT HEIGHT YES
20 WEIGHT WEIGHT YES
21 HAIR HAIR YES
22 EYES EYES YES
23 SCARS MARKS TATS SMT YES
24 DRIVERS LICENSE LICENSE YES
25 CASE NUMBER CASE_NUM YES
26 CONVIC DATE CONV_DATE YES
27 COMMENTS COMMENTS YES
28 MUG SHOT MUG_SHOT YES
29 PRIMARY KEY PRIMARY_KEY YES
*Each Area field may include one of the following: Beat, District, Precinct, Sector, City, Zip Code, etc. #11..
- 870 -
CrimeView Appendix C – Dashboard Standard Field Lists
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
119
ShotSpotter
ORDER DISPLAY NAME FIELD NAME
REPORT
GRID
SAVED
QUERY CATEGORIES
AD
HOC
1 INCIDENT ID INCIDENT_ID YES
2 CAD ID CaseNumber YES
3 INCIDENT TYPE IncidentType YES YES YES YES
4 INCIDENT DATE TriggerTime YES
5 NEAREST ADDRESS CV_ADDRESS YES
6 BEAT BeatName YES YES YES
7 COVERAGE AREA CoverageAreaName YES
8 NUMBER OF SHOTS NumShots YES YES YES YES
9 COMMENTS COMMENTS YES
#11..
- 871 -
CrimeView Appendix C – Dashboard Standard Field Lists
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
120
Special Flags / Known Offenders
ORDER DISPLAY NAME FIELD NAME
REPORT
GRID
SAVED
QUERY CATEGORIES AD HOC
1 AGENCY AGENCY YES YES YES YES
2 PERSON ID PERSON_ID YES
3 PERSON NAME FULL_NAME YES
4 ALIAS NAME ALIAS YES
5 CASE NUM CASE NUM YES
6 STATUTE OR
CHARGE CHARGE_DESC YES YES YES YES
7 ADDRESS CV_ADDRESS YES
8 ADDRESS TYPE ADDR_TYPE YES
9 APT APT YES
10 AREA 1* YES YES YES
11 AREA 2* YES YES YES
12 AREA 3* YES YES YES
13 AREA 4* YES YES YES
14 CONVICTION_DATE CONVICTION_DATE YES
15 RELEASED_DATE RELEASED_DATE YES
16 REGISTERED DATE REGISTERED_DATE YES
17 REGISTRANT
STATUS REG_STATUS_DESC YES YES YES YES
18 RISK LEVEL RISK_LEVEL YES YES YES YES
19 FLAG TYPE FLAG_TYPE YES YES YES YES
20 SEX SEX YES YES YES YES
21 RACE RACE_DESC YES YES YES YES
22 ETHNICITY ETHNICITY YES YES YES YES
23 AGE AGE YES YES YES YES
24 OFFICER OFFICER YES
25 COMMENTS
*Each Area field may include one of the following: Beat, District, Precinct, Sector, City, Zip Code, etc.
Queries
Standard NLETS/NCIC/DMV Queries (dependent on State availability) Person by Name & DOB or DL/OLN (photo return “in state”) Gun
Vehicle by Plate or VIN
#11..
- 872 -
CrimeView Appendix C – Dashboard Standard Field Lists
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
121
Fire/EMS Incidents
DISPLAY NAME ORDER FIELD NAME
REPORT
GRID
SAVED
QUERY CATEGORIES
AD HOC
CHART
AGENCY 1 AGENCY YES YES YES YES
INCIDENT NUMBER 2 INCIDENT_NUM YES
INCIDENT CATEGORY 3
FV_LEGEND (Omega
Derived) YES YES YES YES
INCIDENT TYPE 4 INC_TYPE YES YES YES(TOP 20) YES
SHIFT 5 SHIFT YES YES YES YES
ADDRESS 6 FV_ADDRESS YES
APARTMENT 7 APT YES
AREA 1* 8 YES YES YES
AREA 2* 9 YES YES YES
AREA 3* 10 YES YES YES
STATION 11 STATION YES YES YES YES
RESPONSE
TYPE/PRIORITY
RESPONSE 12 RESP_TYPE_DESC YES YES YES YES
911 DATE 13 911_DATE YES
NOTIFY DATE 14 NOTIFY_DATE YES
ARRIVAL DATE 15 ARRIVAL_DATE YES
LAST UNIT CLEAR DATE 16 CLEAR_DATE YES
PROCESS TIME 17 PROCESS_TIME YES YES**
DEPT RESPONSE TIME 18 DEPT_RESP_TIME YES YES**
TOTAL REFLEX TIME 19 TOTAL_REFLEX_TIME YES YES**
ACTION TAKEN 20 ACTION1_DESC YES YES YES YES
PROPERTY USE 21 PROP_USE_DESC YES YES YES YES
PROPERTY LOSS 22 PROP_LOSS YES
PROPERTY VALUE 23 PROP_VALUE YES
PROPERTY SAVED
(percent value) 24 PROP_LOSS,PROP_VALUE YES
MUTUAL AID 25 MUTUAL_AID_DESC YES YES YES YES
CAUSE OF IGNITION 26 CAUSE_IGN_DESC YES YES YES YES FIRE SPREAD 27 FIRE_SPREAD YES YES YES YES
INJURY_FATALITY 28
FS_FATAL, FS_NONFATAL,
OTHER_FATAL,
OTHER_NONFATAL YES YES
REPORT COMPLETED 29 COMPLETED YES YES YES YES
*Each Area field may include one of the following: District, Zone, Atom, First Due, City, Zip Code, etc. ** Part of "Response Times" query group
#11..
- 873 -
CrimeView Appendix C – Dashboard Standard Field Lists
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
122
FIRE/EMS Unit Responses (Apparatus)
DISPLAY NAME ORDER FIELD NAME
REPORT
GRID
SAVED
QUERY CATEGORIES
AD HOC
CHART
AGENCY 1 AGENCY YES YES YES YES
INCIDENT NUMBER 2 INCIDENT_NUM YES
UNIT 3 UNIT YES YES YES
APPARATUS TYPE 4 UNIT_TYPE_DESC YES YES YES YES
ARRIVAL ORDER 5
ARRIVAL_ORDER_OVERALL
(Omega Derived) YES YES YES YES
INCIDENT CATEGORY 6
FV_LEGEND (Omega
Derived) YES YES YES YES
INCIDENT TYPE 7 INC_TYPE_DESC YES YES YES (TOP 20) YES ADDRESS 8 FV_ADDRESS YES
APARTMENT 9 APT YES
AREA 1* 10 YES YES YES
AREA 2* 11 YES YES YES
AREA 3* 12 YES YES YES
STATION 13 STATION YES YES YES YES
SHIFT 14 SHIFT YES YES YES YES
RESPONSE TYPE/PRIORITY 15 RESP_TYPE_DESC YES YES YES YES 911 DATE 16 911_DATE YES
NOTIFY/DISPATCH DATE 17 DISPATCH_DATE YES
ENROUTE/ROLL DATE 18 ENROUTE_DATE YES
ARRIVAL DATE 19 ARRIVAL_DATE YES
HOSPITAL ARRIVAL DATE 20 ARRIVAL_HOSP_DATE YES
CLEAR DATE 21 CLEAR_DATE YES
TURNOUT TIME 22 TURNOUT_TIME YES YES***
TRAVEL TIME 23 TRAVEL_TIME YES YES***
DEPT RESPONSE TIME 24 DEPT_RESP_TIME YES YES***
TOTAL REFLEX TIME 25 TOTAL_REFLEX_TIME YES YES***
HOSPITAL WAIT TIME 26 HOSP_WAIT_TIME YES YES***
PROPERTY USE 27 PROP_USE YES YES*** YES YES
ACTION TAKEN 28 ACTION1_DESC YES YES YES YES
MUTUAL AID 29 MUTUAL_AID_DESC YES YES YES YES
PRIMARY KEY 30 PRIMARY_KEY YES
*Each Area field may include one of the following: District, Zone, Atom, First Due, City, Zip Code, etc. ** Part of "Response Times" query group
#11..
- 874 -
CrimeView Appendix C – Dashboard Standard Field Lists
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
123
Fire Inspections
DISPLAY NAME ORDER FIELD NAME
REPORT
GRID
SAVED
QUERY CATEGORIES
AD HOC
CHART
AGENCY 1 AGENCY YES YES YES YES
INSPECTION NUMBER 2 INCIDENT_NUM YES
OCCUPANCY ID 3 OCC_ID YES
OCCUPANT_NAME 4 OCCUPANT_NAME YES
ADDRESS 5 FV_ADDRESS YES
APARTMENT 6 APT YES
AREA 1* 7 YES YES YES
AREA 2* 8 YES YES YES
AREA 3* 9 YES YES YES
STATION 10 STATION YES YES YES YES
BUILDING CLASS 11 BLDG_CLASS_DESC YES YES YES YES BUILDING STATUS 12 BLDG_STATUS_DESC YES YES YES YES CONSTRUCTION TYPE 13 CONST_TYPE_DESC YES YES YES YES ROOF COVER 14 ROOF_COVER_DESC YES YES YES YES
FLOORS 15 FLOORS_ABOVE YES YES** YES YES
OCCUPANT LOAD 16 OCC_LOAD YES
PROPERTY USE 17 PROP_USE_DESC YES YES YES YES
MIXED USE 18 MIXED_USE_DESC YES YES YES
DETECTOR TYPE 19 DET_TYPE_DESC YES YES YES YES
AES TYPE 20 AES_TYPE_DESC YES YES YES YES
HAZARDOUS
MATERIALS 21 HAZMAT_DESC YES YES YES
INSPECTION TYPE 22 INSP_TYPE_DESC YES YES YES YES INSPECTION STATUS 23 INSP_STATUS_DESC YES YES YES YES DATE REQUESTED 24 DATE_REQUESTED YES
DATE SCHEDULED 25 DATE_SCHEDULED YES YES YES
DATE COMPLETED 26 DATE_COMPLETED YES YES YES
INSPECTED BY 27 UNIT/STAFF YES YES YES
PROPERTY ID 28 PROP_ID Y/N
PARCEL 29 PARCEL Y/N
VIOLATION(S) 30 VIOLATION_DESC YES YES YES
PRIMARY KEY 31 PRIMARY_KEY
*Each Area field may include one of the following: District, Zone, Atom, First Due, City, Zip Code, etc. #11..
- 875 -
CrimeView Appendix C – Dashboard Standard Field Lists
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
124
Fire Occupancies
DISPLAY NAME ORDER FIELD NAME
REPORT
GRID
SAVED
QUERY
CATE‐
GORIES
AD
HOC
CHART
AGENCY 1 AGENCY YES YES YES YES
OCCUPANCY ID 2 OCC_ID YES
OCCUPANT_NAME 3 OCCUPANT_NAME YES
ADDRESS 4 FV_ADDRESS YES
APARTMENT 5 APT YES
AREA 1* 6 YES YES YES
AREA 2* 7 YES YES YES
AREA 3* 8 YES YES YES
STATION 9 STATION YES YES YES YES
BUILDING CLASS 10 BLDG_CLASS_DESC YES YES YES YES BUILDING STATUS 11 BLDG_STATUS_DESC YES YES YES YES CONSTRUCTION TYPE 12 CONST_TYPE_DESC YES YES YES YES ROOF COVER 13 ROOF_COVER_DESC YES YES YES YES
FLOORS 14 FLOORS_ABOVE YES YES** YES YES
OCCUPANT LOAD 15 OCC_LOAD YES
PROPERTY USE 16 PROP_USE_DESC YES YES YES YES
MIXED USE 17 MIXED_USE_DESC YES YES YES YES
DETECTOR TYPE 18 DET_TYPE_DESC YES YES YES YES
AES TYPE 19 AES_TYPE_DESC YES YES YES YES
HAZARDOUS MATERIALS 20 HAZMAT_DESC YES YES YES
PROPERTY ID 21 PROP_ID Y/N
PARCEL 22 PARCEL Y/N
LAST INSPECTION START
DATE 23 DATE_STARTED YES
LAST INSPECTION
COMPLETED DATE 24 DATE_COMPLETED YES
LAST INSPECTION
NUMBER 25 INSP_NO YES
LAST INSPECTION TYPE 26 INSPECTION_TYPE YES
LAST INSPECTION STATUS 27 INSP_STATUS_DESC YES
LAST INSPECTED BY 28 UNIT/STAFF YES
LAST INCIDENT DATE 29 INC_DATE Y/N
LAST INCIDENT TYPE 30 INC_DESC Y/N
RISK LEVEL 31 RISK_LEVEL
PRIMARY KEY 32 PRIMARY_KEY
*Each Area field may include one of the following: District, Zone, Atom, First Due, City, Zip Code, etc. #11..
- 876 -
CrimeView Appendix C – Dashboard Standard Field Lists
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
125
EMS Patients
DISPLAY NAME ORDER FIELD NAME
REPORT
GRID
SAVED
QUERY CATEGORIES
AD HOC
CHART
AGENCY 1 AGENCY YES YES YES YES
INCIDENT NUMBER 2 INCIDENT_NUM YES
INCIDENT CATEGORY 3
FV_LEGEND (Omega
Derived) YES YES YES YES
INCIDENT TYPE 4 INC_TYPE YES YES YES(TOP 20) YES
UNIT 5 UNIT YES YES YES
SHIFT 6 SHIFT YES YES YES YES
ADDRESS 7 FV_ADDRESS YES
APARTMENT 8 APT YES
LOCATION TYPE 9 LOCATIONTYPE_DESC
AREA 1* 10 YES YES YES
AREA 2* 11 YES YES YES
AREA 3* 12 YES YES YES
AREA 4* 13 YES YES YES
RESPONSE
TYPE/URGENCY 14 RESP_TYPE_DESC YES YES YES YES
911 DATE/TIME 15 911_DATE YES
DISPATCH DATE/TIME 16 NOTIFY_DATE YES
ENROUTE DATE/TIME 17
ARRIVAL AT SCENE
DATE/TIME 18 ARRIVAL_DATE YES
ARRIVAL AT PATIENT
DATE/TIME 19 ATPATIENT_DATE YES
TRANSPORT DATE/TIME 20 TRANSPORT_DATE
AT HOSPITAL DATE/TIME 21
CLOSE/CLEAR DATE/TIME 22 CLEAR_DATE YES
PROCESS TIME 23 CALCULATED BY OMEGA YES
DISPATCH TO ENROUTE
TIME 24 CALCULATED BY OMEGA YES
DISPATCH TO SCENE
TIME 25 CALCULATED BY OMEGA YES
DISPATCH TO PATIENT
TIME 26 CALCULATED BY OMEGA YES
TOTAL RESPONSE TIME
TO SCENE 27 CALCULATED BY OMEGA YES
TOTAL RESPONSE TIME
TO PATIENT 28 CALCULATED BY OMEGA YES
#11..
- 877 -
CrimeView Appendix C – Dashboard Standard Field Lists
The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced, published or disclosed to others without the prior written consent of TriTech Software Systems.
©2018 TriTech Software Systems
126
TRANSPORT TIME 29 CALCULATED BY OMEGA YES
HOSPITAL WAIT TIME 30 CALCULATED BY OMEGA YES
CAUSE 31 CAUSE YES YES YES YES
IMPRESSION 32 IMPRESSION YES YES YES YES
FINDINGS 33 FINDINGS YES YES YES YES
TREATMENT 34 TREATMENT YES YES YES YES
DISPOSITION 35 DISPOSITION YES YES YES YES
DESTINATION 36 TRANSPORT_DESTINATION YES YES YES
REPORT COMPLETED 37 COMPLETED YES YES YES YES
#11..
- 878 -
Sample Training Plans – CentralSquare CAD Enterprise (powered by Inform)