My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
NEWPORT BEACH, CITY OF 2 -2004
Clerk
>
Contracts / Agreements
>
N
>
NEWPORT BEACH, CITY OF 2 -2004
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
1/3/2012 2:41:29 PM
Creation date
3/30/2005 9:58:27 AM
Metadata
Fields
Template:
Contracts
Company Name
City of Newport Beach
Contract #
A-2004-176-06
Agency
Police
Council Approval Date
8/16/2004
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
127
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
<br />Attachment B <br /> <br />will be included in the OCILJ Data Sharing Solution. Logistics for the workshops <br />shall be managed by the Orange County Integrated Law & Justice team <br />members. These requirements are applicable to both Phase 1 and Phase 2. <br /> <br />SQW2-4 System Design Documentation <br />Following the requirements validation workshops the Vendor shall develop <br />design documents detailing the configuration and any custom development. The <br />documentation must be detailed enough for reviewers to understand the function <br />and appearance of all screens. This documentation shall be submitted to the <br />OCILJ Steering Committee for a 1 week review period. During the review period <br />the Vendor shall update the project plan to reflect the configuration and <br />customization effort. Following the OCILJ Steering Committee's review, the <br />Vendor and the OCILJ Working Group shall finalize the design documents and <br />project schedule. These requirements are applicable to both Phase 1 and <br />Phase 2. <br /> <br />SQW2-5 Development and Customization <br />The Vendor shall perform the customizations outlined in the finalized System <br />Design Documentation described above. These requirements are applicable to <br />both Phase1 and Phase 2. <br /> <br />SOW2-6 Configuration <br />The Vendor shall undertake all configuration of the data sharing application, the <br />Search Tool, and Analysis Tools to meet the requirements as defined in the <br />workshops and design documentation. These requirements are applicable to <br />both Phase 1 and Phase 2. <br /> <br />SOW2-7 Interfaces <br />The Vendor shall be responsible for implementing all aspects of the interfaces <br />described in the requirements. The Vendor will be responsible for implementing <br />the legacy system end of the interfaces, working with OCILJ staff to understand <br />technical interface requirements and for liaising with RMS vendors to facilitate <br />interfaces with OCILJ RMS's. As appropriate, the Vendor will utilize existing <br />OCILJ relationships with RMS vendors. Each OCILJ agency intends to provide <br />support for establishing relationships with RMS vendors and bUilding the <br />interfaces for this project. but that support may not always be guaranteed. In <br />cases where select police agency Records Management System vendors do not <br />allow direct alterations for interfaces, the Vendor will liaise with RMS vendors for <br />the creation of required interfaces. These requirements are applicable to both <br />Phase 1 and Phase 2. <br /> <br />SOW2-8 Integration <br />Primary integration of the solution with outside systems will be the <br />responsibilities of the Vendor. The Vendor shall be fully responsible for full <br />integration' of the data sharing solution with the Search tool, Analysis Tools and <br />current police agency RMSs. The Vendor will also be responsible for integrating <br />the Data Sharing Solution with the ELETE system and the Orange County <br />Court's citation database. The Vendor shall actively work with Orange County <br />police agencies and courts, their staff, and any other contractors employed by <br /> <br />23 <br /> <br />~-:J <br />
The URL can be used to link to this page
Your browser does not support the video tag.