My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
TRITECH SOFTWARE SYSTEMS -2015
Clerk
>
Contracts / Agreements
>
T
>
TRITECH SOFTWARE SYSTEMS -2015
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
1/10/2024 10:18:10 AM
Creation date
12/22/2015 9:39:05 AM
Metadata
Fields
Template:
Contracts
Company Name
TRITECH SOFTWARE SYSTEMS
Contract #
A-2015-252
Agency
POLICE
Council Approval Date
11/17/2015
Destruction Year
2028
Notes
For Insurance Exp. Date see Notice of Compliance
Document Relationships
TRITECH SOFTWARE SYSTEMS
(Amended By)
Path:
\Contracts / Agreements\T
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.
/
365
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
Bidirectional interface configured for use with the ATIMS System. <br />• • Inform RMS • • • • XML <br />Inform FBR <br />• • • ' • TriTech's Cost Proposal includes licensing, deployment, initial configuration and <br />" warranty support of a bidirectional interface to share arrest and booking data. <br />In order to achieve this integration, TriTech will provide two mechanisms: <br />• Arrest Publisher <br />• Recent Information Importer <br />Arrest Publisher <br />In order to provide that integration, TriTech will develop an arrest publisher. The <br />Publisher will provide a defined set of data in an event -driven manner. On create and <br />modify of an Arrest Summary Record, arrest data will be published by TriTech as it <br />occurs in Inform RMS. <br />The published data will be placed on a network share for consumption by third party in <br />an XML file format that aligns with the Inform RMS database. <br />Each record published will contain both a record type and a unique source record <br />identifier that is based on the primary key of the parent record in Inform RMS. <br />TriTech will re -send the entire record following modification to the Summary Record. <br />The Publisher utility will maintain a log file that will identify any file I/O errors <br />encountered during its operation. <br />Recent Information Importer <br />TriTech will achieve this integration via an automated Importer that will monitor the <br />network share for Booking data for insertion into Recent Information for reuse in <br />Inform FBR Reports. <br />Booking data provided by ATIMS must include the Badge Number with the submission <br />file. <br />TriTech has a standard data format to accept Booking -related data from ATIMS; this <br />data format will be included in the Operational Scenario Document (OSD) and aligns <br />with the Inform database. Any variation on this data format will require customization <br />services at an additional cost. <br />General Information: <br />Deployment and operation of the interface, as described here, does not require <br />modifications to existing TriTech products and no product modifications are proposed. <br />The TriTech interface and associated data store reside on a conventional or virtualized <br />server platform compliant with TriTech's approved hardware and software <br />specifications. <br />TriTech's planned scope of work assumes the shared directory used by the ATIMS <br />System for depositing exported files will be on the same local area network as Inform <br />RMS or will be accessible from the Inform RMS network. <br />TriTech's Cost Proposal assumes the client will support any component and/or <br />integration testing required to facilitate the timely delivery of the TriTech interface. <br />Timely approval of interface documentation, support of remote deployment tasks (to <br />opyngMt 2015 TriTech Software Systems - Confidential & Proprietary, Unpublished: Rights reserved under the copyright laws of the United States, Pagel of <br />
The URL can be used to link to this page
Your browser does not support the video tag.