My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
25B - AGMT - PD SOFTWARE SYS
Clerk
>
Agenda Packets / Staff Reports
>
City Council (2004 - Present)
>
2015
>
11/17/2015
>
25B - AGMT - PD SOFTWARE SYS
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
11/12/2015 2:33:31 PM
Creation date
11/12/2015 1:58:24 PM
Metadata
Fields
Template:
City Clerk
Doc Type
Agenda Packet
Agency
Clerk of the Council
Item #
25B
Date
11/17/2015
Destruction Year
2020
Jump to thumbnail
< previous set
next set >
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
204
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
Prerequisites: 1) Attended the Inform RMS Core End User Training; 2) Daily user of the designated <br />application module; 3) Classroom instruction experience and demonstrated presentation skills. <br />Inform FBR is implemented through a series of standard steps and process gates. These steps are designed to <br />ensure that the operational needs of the Client are identified, the configurations are verified, and the system <br />is tested to validate the proper functionality of the system prior to deployment. The following sections <br />describe the implementation process for Inform FBR. <br />7.7.1 Inform FSR System Orientation <br />The Inform FBR System Orientation is conducted at the Client's site and led by a TriTech Business Analyst. <br />The duration of the Inform RMS System Orientation is generally between 1 -2 days and includes a Business <br />Process Review of the Client's operations. This System Orientation can be conducted in conjunction with <br />Inform RMS if purchased together. <br />Some key discovery points for the Inforn FBR System Orientation are as follows: <br />a) Work Flow — Understanding the workflow processes for the field reports. This may include time <br />observing Departmental Divisions such as Records Staff and Ride- Alongs with field units. <br />b) Review reporting requirements (reporting segmentation and the like). <br />c) Event numbering (Incidents) including master incident numbers and case numbers. <br />It is recommended that the number of attendees in the System Orientation is limited to 10 -15 to allow for <br />more effective communication during the session. Based on the key discovery points during this session, it is <br />necessary that the attendees include ind'iv'iduals who can properly address these key points and make <br />configuration decisions. <br />During the System Orientation session, the Business Analyst will facilitate an operational review of htfonn <br />FBR by demonstrating various System functionality and start gathering the configuration information. <br />Due to the integration and sharing of Code Files with Inform RMS, a System Modulo Setup worksheet <br />(SMS) will not be used with Inform FBR. This information will be collected through the Inform RMS <br />System Module Setup (SMS) as needed <br />Note:. As part of the System Administrator training the FBR Administrators will learn to complete the <br />personnel registrations within Inform FBR, It is the responsibility of the client to complete the <br />Inform FBR personnel user registrations, <br />7.7.11 TrlTech Responsibilities <br />a) Schedule the System Orientation meeting in accordance with the Client's availability and the Project <br />Schedule. <br />b) Prepare and distribute the meeting agendas and documents for Client review or completion two weeks <br />prior to each meeting. <br />o) Conduct the meetings based on the distributed agenda. <br />d) Document the Client's requirements and configuration specifications resulting from the System <br />Orientation discussions. <br />50 <br />25B -96 <br />
The URL can be used to link to this page
Your browser does not support the video tag.