Orange County NC Website
Browse       Search
DocuSign Envelope ID:77803446-26E8-4424-B3DD-15F947931AE8 <br /> 5. The following are best practice recommendations but may be excessive for some smaller installations. Contact BCS for <br /> specific recommendations. <br /> a. MARVLIS Server—Requires a dedicated server <br /> b. MARVLIS Deployment Monitor—Requires a dedicated workstation <br /> c. MARVLIS Demand Monitor—Requires a dedicated workstation or small server <br /> d. MARVLIS Deployment Planner—Requires a staff workstation <br /> e. MARVLIS Impedance Monitor-Requires a staff workstation <br /> NOTE:None of these applications should reside on the same physical machines as the end users CAD software. <br /> NOTE:Please see MARVLIS System requirements for more detail. <br /> 6. MARVLIS Server must have access to a SQL Server data repository in order to store the AVL data as it arrives from the <br /> vehicles. This SQL Server table will be used for any AVL playback as well as street data processing with Impedance <br /> Monitor. This SQL Server should be separate from the CAD Server so as to minimize interference with normal CAD <br /> operations. <br /> 7. CAD incident data replication—The CAD incident table should be replicated into the same SQL Server data repository as <br /> the AVL data. <br /> a. The purpose of this replication is to minimize queries on the live CAD system by MARVLIS Demand Monitor <br /> and MARVLIS Deployment Planner. Replication on a nightly or even weekly basis is sufficient to support the <br /> MARVLIS applications. <br /> b. BCS will coordinate with OSSI to establish the replication. <br /> 8. All installation locations must be determined in advance in order for the correct number of supporting ESRI runtimes to be <br /> quoted and acquired. <br /> a. If the end user changes the number of installation locations,this may result in additional costs for ESRI <br /> runtimes. <br /> b. NOTE: Please see Attachment—MARVLIS System Requirements for more details <br /> d <br /> 9. BCS must be provided VPN access(Cisco AnyConnect or similar)to all hardware,except Client,for support,monitoring <br /> and troubleshooting. <br /> MARVLIS IMPLEMENTATION TASKS: <br /> The timeline(attached to Exhibit B as Schedule 2)for these tasks is based on the availability of and access to Orange County <br /> equipment and personnel. BCS's total hours for the actual install and configuration should be less than a week but time has <br /> been allotted for waiting for customer availability and responses to questions. <br /> 1. MARVLIS Server and MARVLIS Client Installation/Configuration <br /> a. Installation of MARVLIS Server on dedicated server hardware <br /> b. Installation of MARVLIS Client—Test Vehicle <br /> c. Configuration and testing of MARVLIS Server and MARVLIS Client <br /> i. MARVLIS Server—Configure read/write access to SQL Server database for AVL data logging <br /> ii. Configure and test CAD communications <br /> iii. MARVLIS Server/Client—Confirm successful data transmission over the wireless communications <br /> network <br /> d. Customer staff with BCS support will generally perform Installation/Configuration of remaining MARVLIS <br /> Clients. <br /> 2. MARVLIS Deployment Monitor Installation/Configuration <br /> a. Installation on Dedicated Deployment Monitor workstation <br /> b. Load and configure street network data. <br /> c. Configure/Test to receive and display data from MARVLIS Server once the MARVLIS Client test vehicle is <br /> available <br /> 3. MARVLIS Demand Monitor Installation/Configuration <br /> a. Installation on Dedicated Demand Monitor workstation <br /> B-6 <br /> CORE/0804998.0008/128897050.2 <br />