My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
R2012-137 ACCEPTING BID BODINE COMMUNICATIONS
COD
>
City Clerk
>
RESOLUTIONS
>
2012
>
R2012-137 ACCEPTING BID BODINE COMMUNICATIONS
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
8/20/2015 3:02:17 PM
Creation date
8/20/2015 3:02:15 PM
Metadata
Fields
Template:
Resolution/Ordinance
Res Ord Num
R2012-137
Res Ord Title
ACCEPTING BID BODINE COMMUNICATIONS - TRANSIT CENTER SECURITY CAMERA SYSTEM
Department
Mass Transit
Approved Date
6/18/2012
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
18
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
1. IPVSSP Base Software (herein `IPVSSP Base') <br /> Provides system-wide management, user access, shared event <br /> management, alarm and event correlation, video access, and <br /> distribution rights. The IPVSSP Base regulates and manages the flow <br /> of data between Video Client users, connected recording servers and <br /> integrated alerting applications. This includes: <br /> a. Creating composite events from multiple detection systems <br /> b. Sharing resources between Video Client users <br /> C. Shared bookmarking and event handling among multiple Video <br /> Client users at multiple sites <br /> d. Management of all user and authorization data. <br /> e. Coordination for on-event, push live video alertinb (`blank <br /> screen monitoring') <br /> f. Metadata management for all investigative tools <br /> g. Central hub/repository for all system configurations and shared <br /> resources: <br /> 1) Navigation map resources for Video Clients, for <br /> displaying cameras and camera groups on connected <br /> screens, including: <br /> i. map images <br /> ii. positioning and target of hyperlinks on maps <br /> iii. icons for linked cameras <br /> iv. icons for other assets, including entire <br /> V. groups of cameras, carousels, etc. <br /> 2) Views (arrays of camera, carousel, push-video alerting, <br /> hotspot and webpage panes) shared by all Video Client <br /> users <br /> 3) Bookmark information for designated segments of video, <br /> as generated by video client operators <br /> 4) Event coordination information, including: <br /> i. event details: event type, time/date, camera that <br /> triggered the event <br /> ii. classifications and tags, which are shared by <br /> authorized operators <br /> 5) Licensing management for all system components <br /> Decatur Public Transit System A-3 IP Video System <br />
The URL can be used to link to this page
Your browser does not support the video tag.