1. Slide 1 San Diego InterCAD Project A Retrospective View ITS America Annual Meeting Long Beach, CA April 29-May 2, 2002 Bruce Churchill, National Engineering Technology Corporation Pam Scanlon, Executive Director San Diego Automated Regional Justice Information System

2. Slide 2 Topics Covered Incident Response Incident Response Coordination Deficiencies Coordination Deficiencies InterCAD Results InterCAD Results Interface Recommendations Interface Recommendations Standards Recommendations Standards Recommendations Institutional Recommendations Institutional Recommendations Next Steps Next Steps

3. Slide 3 X Incident Location Public Safety Answering Point (EMC) (Cellular 9-1-1 PSAP) Traffic Management Center (TMC - DOT) Response Centers (EMC) (PD/FD/EMS) Wireless Switching Office Nearest Cell Site Public Telephone Network A B C D F F E G Future Regional Network Motorist Aid Patrol Incident Response Truck G G Why InterCAD?

4. Slide 4 Incident Response Analysis From Previous Slide From Previous Slide –Telephonic notifications slow down coordination process behind the scenes – on scene radio coordination is a separate set of issues –With regional network and evolving IEEE standards for TMC-EMC links, once call gets to PSAP, notification of other responders and regional TMC is nearly instantaneous and automatic, bypassing Telco delays and human error

5. Slide 5 Why InterCAD? Originating Agency Radio Dispatcher Call Taker Mutual Aid Agency Screen-toScreen Communications

6. Slide 6 Fundamental Barriers to Information Sharing Institutional inertia – resistance to change Institutional inertia – resistance to change Lack of appreciation for other agencies needs Lack of appreciation for other agencies needs NIH syndrome NIH syndrome Lack of a regional vision Lack of a regional vision Lack of known and respected champions Lack of known and respected champions Legacy (closed) systems Legacy (closed) systems Lack of a regional architecture Lack of a regional architecture Security concerns Security concerns CAD vendor involvement in ITS Public Safety Program CAD vendor involvement in ITS Public Safety Program

7. Slide 7 Operational Differences TMCs vs. Communications Centers TMCs vs. Communications Centers On-Scene Interoperability vs. Center-to- Center Interoperability On-Scene Interoperability vs. Center-to- Center Interoperability Law enforcement (patrol) vs. Fire/EMS (in- quarters) Law enforcement (patrol) vs. Fire/EMS (in- quarters)

8. Slide 8 Integrating Incident Information PUBLIC SAFETY DISPATCH TRANSPORTATION MANAGEMENT Data Fusion/Dissemination Awareness set by sensors Multi-agency incident mgmt Real-time facility mgmt Traveler Information New development systems Real-time mobile resource mgmt Awareness set by radio comms Multi-agency incident mgmt Interface to motorists/public (call box + Mobile 9-1-1 + 9-1-1) Legacy systems Fundamental System Differences

9. Slide 9 CAD Interfaces AVL Mobile Data Computers CAD Pen-Based Computers Same considerations apply to Fire/EMS equipment

10. Slide 10 Traffic Management Center (TMC) ATMS SoftwareATMS Software TMC OperatorsTMC Operators Highway Patrol MIOHighway Patrol MIO DispatchDispatch Traffic Management Center (TMC) ATMS SoftwareATMS Software TMC OperatorsTMC Operators Highway Patrol MIOHighway Patrol MIO DispatchDispatch Traffic Management Team Media State DOT Headquarters HeadquartersLocalAgenciesLocalAgenciesAdjacentDistrictsAdjacentDistricts Highway Patrol Freeway Service Patrol Typical TMC Interfaces Vehicle Detection Stations Ramp Metering System MaintenanceMaintenance Closed Circuit Television Changeable Message Signs Highway Advisory Radio

11. Slide 11 InterCAD Results

12. Slide 12 InterCAD PHASES 1 and 2 PARTICIPANTS SAN DIEGO PD SAN DIEGO SHERIFF CHP BORDER DIV SAN DIEGO FD CDF HEARTLAND FIRE (JPA) NO COUNTY FIRE (JPA) FEDERAL FIRE USFS CALTRANS (TMC) Phase 1 participants (limited success) Planned Phase 2 participants Eventual Phase 2 installations OCEANSIDE PD/FD CARLSBAD PD/FD

13. Slide 13 InterCAD Technical Approach IBM Message Queue Manager (MQM) MQM Server (DEC Alpha, Win NT, OS/2 etc.) MQM Client (CAD Host) Regional Network Operator Initiates or updates incident record and designates addressee(s) Operator Reviews message and Initiates new incident or Updates existing Incident record MQM Server (DEC Alpha, Win NT, OS/2 etc.) MQM Client (CAD Host)

14. Slide 14 Phase 2 Capabilities (Planned) Addressable Consoles (& MDCs) Incident Type & Location Units Assigned & Status Addressed or Broadcast Messages Message Priority Levels Update Incident Entries

15. Slide 15 InterCAD Lessons Learned - I Lost project Champion (CHP Communications Center Lt.) Lost project Champion (CHP Communications Center Lt.) No agency leadership to fill void No agency leadership to fill void Reliance on a single CAD vendor for technical solution to CAD modifications Reliance on a single CAD vendor for technical solution to CAD modifications Lack of security vulnerability analysis Lack of security vulnerability analysis Not enough reliance on existing LE assets (e.g. ARJIS communications and governance structure) Not enough reliance on existing LE assets (e.g. ARJIS communications and governance structure)

16. Slide 16 InterCAD Lessons Learned - II Need a clear Concept of Operations (i.e. start w/ recognized systems engineering principles) – follow up w/ Requirements- Based Engineering Need a clear Concept of Operations (i.e. start w/ recognized systems engineering principles) – follow up w/ Requirements- Based Engineering Find an agency/key person champion Find an agency/key person champion Design to standards (you can design to IEEE 1512 even if not mature…) Design to standards (you can design to IEEE 1512 even if not mature…) Participate in standards effort to ensure its relevance to real world development Participate in standards effort to ensure its relevance to real world development Work within existing Public Safety technical environment to maximum degree possible Work within existing Public Safety technical environment to maximum degree possible

17. Slide 17 Interface Recommendations

18. Slide 18 Conceptual Public Safety/TMC Interface ARJIS Network SDPD CAD/MIS Message Server (Windows XP/2000) Message Server (Sun/Solaris) Regional IMTMS Network Other InterCAD Agencies ARJIS = Automated Regional Justice Information System Network Existing Law Enforcement Network Addresses Security Issues Operational concept defines information exchange needs Platform independent message service - Offload message processing from host CAD systems

19. Slide 19 Conceptual Information Sharing INCIDENT TYPE/LOCATION UNIT ASSIGNMENT UNIT STATUS INCIDENT DETAILS (AS OCCURRING) INCIDENT/TYPE/LOCATION HIGHWAY/ARTERIAL CONGESTION CONSTRUCTION/CLOSURES RECOMMENDED ROUTING CCTV VIDEO Over 90% of initial incident notifications go to 9-1-1 Transportation Public Safety

20. Slide 20 Inter-Console Message External Agency Message Dispatchers Call Takers Pseudo Console CAD - Message Server link MQ Series Message Server Pseudo Console CAD Interface Approach CHP SDPD TMC InterCAD Network

21. Slide 21 Common Carrier Regional IMTMS Network InterCAD ARJIS Network PD/FD Agency MQ Server InterCAD Seed (MQ Server) + Firewall Host CAD System (Future) IMX Terminal (Existing) InterCAD Network IMTMS Network CHP CAD Handshake Server Handshake Op W/S CAD Terminal CORBA Interface MQ Series Interface Public Safety Integration Migration Path

22. Slide 22 Standards Recommendations

23. Slide 23 Message Standards (IEEE 1512 Series) Network Tag Data Host CAD Data Common Msg Std Data MQ Series Server Tag Common Msg Std Data Data Translation Host CAD Message Server MQ Series Server Tag Dissimilar CADs/TMCs speak different languages TCP/IP

24. Slide 24 P1512 Future Requirements Must support object-oriented and Web Services/XML development Must support object-oriented and Web Services/XML development –Define standard objects for public safety –Standard message to object mappings –Transportation objects are being defined through NTCIP – may need extensions for broader IM concepts covered by P1512 –Implementation Guide must address Web Services architectures

25. Slide 25 Institutional Recommendations

26. Slide 26 Recommendations for Public Safety Integration Projects Involve Agency CEOs and Keep Apprised Involve Agency CEOs and Keep Apprised Governance Body – Agency Ownership Governance Body – Agency Ownership Public Safety Community Should Establish a Regional Architecture Approach to Information Sharing paralleling USDOT Effort Public Safety Community Should Establish a Regional Architecture Approach to Information Sharing paralleling USDOT Effort –Communications –Standards Adequate Outreach to Agencies at All Levels Adequate Outreach to Agencies at All Levels Develop a Plug and Play (Blueprint) Approach Develop a Plug and Play (Blueprint) Approach Mainstreaming Projects – RTP, O&M Mainstreaming Projects – RTP, O&M Involve multiple CAD vendors from the beginning Involve multiple CAD vendors from the beginning

27. Slide 27 InterCAD Next Steps Use lessons learned from original project Use lessons learned from original project Use the regional architecture (currently being revised for Final Rule compliance) Use the regional architecture (currently being revised for Final Rule compliance) Establish working level champions from both public safety and transportation Establish working level champions from both public safety and transportation CEO buy-in from both communities CEO buy-in from both communities Establish vendor integration team Establish vendor integration team Start modestly and add capabilities using a phased approach Start modestly and add capabilities using a phased approach

28. Slide 28 Summary Real Public Safety and Transportation integration is no longer a luxury or nice to have – it is essential for accommodating the increased complexity of regional incident management of all types: from traffic to terrorism Real Public Safety and Transportation integration is no longer a luxury or nice to have – it is essential for accommodating the increased complexity of regional incident management of all types: from traffic to terrorism Like any other transportation initiative, integration investments and recurring costs must be made compelling to executive management and elected officials Like any other transportation initiative, integration investments and recurring costs must be made compelling to executive management and elected officials

29. Slide 29 End