Emergency Ambulance Services. Attachment 5.5 Communications Interface and Equipment Information

Transcription

1 Emergency Ambulance Services August 4, 2017 Attachment 5.5 Cmmunicatins Interface and Equipment Infrmatin Intrductin This appendix prvides a general descriptin f the prcess flw and technlgy required t accmplish the Cntractr s Interface fr call taking and dispatch respnsibilities under the RFP. Each Prpser shuld fully evaluate the requirements and csts assciated with fulfilling these respnsibilities. Current System and Call Flw Described The prcess fr call handling is based n the distinct steps f an anatmy f a call. Calls typically enter the system at the primary BOEC-based PSAP center. The center handles all three emergency services disciplines (plice, Fire and EMS). EMS services are prvided under cntract by a cntracted ambulance service. In the current mdel, the cntracted ambulance service has a singule designated pd within the BOEC dispatch center. This pd des nt have the rle f initial assignment f vehicles but can readjust the assignment after BOEC persnnel have assigned the call. The pd s primary functin is t carry ut the ambulance Cntractr s redeplyment f resurces.

2 Figure 1 Timelines The system currently is fully integrated, and the BOEC dispatch center des bth the 911 call-taking activities and dispatch activities (911 timeline and CAD timeline). The current call priritizatin/triage tl is a manual prprietary paper-based tl that allws the same agent t handle bth the 911 call taking activities and the call priritizatin/triage activities (recrd pen). The call is sent ver t a primary dispatch desk t assign bth Fire and EMS resurces at the CAD pint f call transmitted (als referred t as call enters Queue). The call is then shifted t call fllw up channel; this channel fllws the call frm enrute t call clsed. The current Cntractr listens n the radi and fllws n the BOEC CAD but wrks ff f its wn CAD. This wrk flw is charted belw: Figure 2 Current Flw

3 Enhanced System Descriptin The RFP requires the use f an electrnically interfaced MPDS call priritizatin tl that is fully integrated with the CAD system, and that ffers agent perfrmance mnitring and quality imprvement functins. Requests fr service are t be priritized and pre-arrival instructins prvided in strict accrdance with Cunty clinical prtcls. Under this mdel, the Cntractr is respnsible fr staffing the call taking functin t include MPDS, thus the entire CAD timeline wuld be handled by the Cntractr. As illustrated in Figure 3 belw, the red segments will be handled by BOEC dispatch, and the blue segments will be handled by the Cntractr. As identified in the fllwing diagram, the call taking functin refers t identifying what service is required e.g., 911 what is yur emergency? and the lcatin e.g., what is the address f yur emergency?. Once thse tw aspects f the call are carried ut,and the call is identified as an EMS call, then the caller will be sent t the Cntractr fr call handling. If it is a Plice r Fire call the BOEC call taker cntinues with the call as it currently des. Figure 3 Revised Call Flw Technlgy Requirements and Optins There are tw distinct technlgy ptins t achieve the abve. The first ptin is that the Cntractr supplies its wn CAD. The secnd ptin the Cntractr uses the BOEC Versaterm CAD. In each f the fllwing senaris the Cntractr may be referred t as the Service Prvider. Cntractr/Service Prvider CAD The Service Prvider/Cntractr supplies its wn hardware which cnnects t BOEC s VMC (Message Cntrller) thrugh a TCP/IP cnnectin. This interface cnnects int

4 the Prvider s CAD system used by their dispatcher at the Cntractr s Cmmuncatin Center. A Versaterm CAD sftware install/cnnectin at BOEC will be prvided t the successful Prpser. The cst f additinal hardware/sftware installatins and high quality vice/data cnnectivity t the Cntractr s center are the the respnsibility f the Cntractr. The Versaterm/Prvider CAD interface is a ne-way transfer f data, with the exceptin f the Prvider CAD ACK transactin. Data that will be transmitted are: call-fr-service, unit status, and AVL data. A heartbeat transactin is used t keep the interface alive and verify that it is still wrking. The heartbeat transactin cntains an h wrapped arund start-f-text (SOT) and end-f-text (EOT) characters. The Prvider CAD needs t sends an ACK transactin in respnse t the heartbeat transactin. Versadex CAD 7.4 has the fllwing minimum requirements; these are t be achieved at Cntractr s expense: Cmputer: An IBM-cmpatible cmputer with a Pentium 4 class prcessr Vide: 1024 x 768 reslutin, 256 clrs (High clr 16-bit r higher recmmended), CAD with maps 24 bit clr depth with 96 dpi required. Higher reslutin CAD will adjust t higher reslutin but it may appear t small. Multiple mnitrs (2 r mre) per desktp are recmmended If running multiple mnitrs, a graphic card capable f driving multiple mnitrs. CAD with MapViewer requires a vide card with the fllwing specificatins: 64 MB RAM minimum, but 256 MB recmmended Accelerated graphics card driver Shader Mdel 2.0 minimum Latest vide card driver Operating System: Windws 7 SPI (32 r 64 bits) and Windws 8.1 (32 r 64 bits), Windws 10 is als supprted. Imprtant nte: Windws XP and Windws VISTA are nt supprted with CAD 7.4 Other sftware: Micrsft Internet Explrer Adbe reader.net 4.5 framewrk Java 1.5 r higher The Mbile Data Cmputer (MDC) fr field respnders (t supprt Versaterm data). The minimum requirements fr MDC 7.5 are:

5 Cmputer: An IBM-cmpatible cmputer with full Windws Desktp Operating System. Peripherals: Muse r pinting device, COMM prt, USB prts. Tuchscreen recmmended. Vide: 1024 x 768 reslutin, 24-bit clr depth. Higher MDT will adjust, but FxPr MRE may appear t small. MDT can be cnfigured fr displaying n nn-standard screen aspect ratis. Accelerated graphics card 256 MB recmmended. 64 MB minimum. Shader Mdel 2.0 minimum. Latest drivers. Operating System: Windws 7 SP1-32 and 64 bit, Windws 8.1, Windws 10 Memry: 4 Gig recmmended. 3 Gig minimum. CPU: I5 r 2.5 GHz recmmended. I3 r 2.2 GHz minimum. Hard Drive: 80 Gig recmmended. 40 Gig minimum. Other Sftware: Micrsft Internet Explrer 9.0.Net 4.5 Framewrk Cntractr/Service Prvider uses the BOEC CAD (Versaterm) nly The Versaterm technlgy requirements remain the same as listed abve. Since this ptin wuld require a wrking agreement between BOEC and the Cntractr/Service Prvider, the fllwing utlines the standard anticipated cntractual requirements between the tw agencies: SERVICE PROVIDER acknwledges and agrees that SERVICE PROVIDER emplyees and subcntractrs will nly Access VCAD and the infrmatin available in r thrugh VCAD fr Authrized Use as utlined in this Agreement. Permissin t Access VCAD r t use the infrmatin available in r thrugh VCAD ther than fr Authrized Use shall be btained in writing frm the Prtland Plice Bureau prir t any such Access r use. SERVICE PROVIDER is respnsible fr prviding cmputers, ruters, switches, printers, and ther SERVICE PROVIDER lcated devices required by PROVIDER s Users f VCAD. SERVICE PROVIDER is respnsible fr wrking with BTS t install, cnfigure, and prvide netwrk access t devices lcated in SERVICE PROVIDER s lcatin including, but nt limited t, cmputers, ruters, switches, and printers.

6 SERVICE PROVIDER is respnsible fr prviding secure netwrk access that meets BTS security requirements, and enables SERVICE PROVIDER s technlgy t reach the VCAD netwrk demarcatin pints. SERVICE PROVIDER is respnsible fr wrking with BTS t prvide all netwrk cmmunicatin devices and services between SERVICE PROVIDER cmputers and City netwrk demarcatin pints. SERVICE PROVIDER is respnsible fr ensuring that all SERVICE PROVIDER netwrk infrastructure and wrkstatins with Access t VCAD are prperly prtected by adequate technical, administrative, and physical safeguards as cvered in the sectin titled SECURITY. SERVICE PROVIDER is respnsible fr prviding the BOEC CAD Crdinatr with the mst current cntact infrmatin fr the SERVICE PROVIDER IT security persnnel and any changes theref within 7 days f any change. SERVICE PROVIDER is respnsible fr ensuring that all SERVICE PROVIDER Users that are granted Authrized Use f VCAD cmply with the IT security requirements specified in this Agreement. SECURITY Physical Security SERVICE PROVIDER shall be respnsible fr maintaining the physical security f all devices that are able t access VCAD, as well as any printed utput r system dcumentatin which might permit unauthrized access t, r use f VCAD frm within the SERVICE PROVIDER s lcatin. Online Security VCAD cntains prcedures and tls t ensure that nly authrized SERVICE PROVIDER users and devices can access the infrmatin available in r thrugh VCAD. SERVICE PROVIDER users will be required t enter special identificatin cdes and passwrds befre gaining access t VCAD and its functins and data. SERVICE PROVIDER acknwledges and agrees that SERVICE PROVIDER emplyees will nt share VCAD user accunts r passwrds.