Transcript Awesome PowerPoint Background Template - IEEE-SA

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
Slide 2
Topics Covered







Incident Response
Coordination Deficiencies
InterCAD Results
Interface Recommendations
Standards Recommendations
Institutional Recommendations
Next Steps
Slide 3
Why InterCAD?
Traffic Management
Center (TMC - DOT)
G’
Motorist Aid Patrol
F’
X
Incident
Location
Incident Response Truck
E
A
G’
Future
Regional
Network
Nearest Cell
Site
B
G
Wireless
Switching
Office
Public
Telephone
Network
F
Response Centers (EMC)
(PD/FD/EMS)
D
C
Public Safety Answering Point (EMC)
(Cellular 9-1-1 PSAP)
Slide 4
Incident Response Analysis

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
Slide 5
Why InterCAD?
Mutual Aid
Agency
Call Taker
Radio Dispatcher
Screen-toScreen
Communications
Originating Agency
Radio Dispatcher
Slide 6
Fundamental Barriers to
Information Sharing
Institutional inertia – resistance to change
 Lack of appreciation for other agencies’ needs
 NIH syndrome
 Lack of a regional vision
 Lack of known and respected champions
 Legacy (closed) systems
 Lack of a regional architecture
 Security concerns
 CAD vendor involvement in ITS Public Safety
Program

Slide 7
Operational Differences
TMC’s vs. Communications Centers
 On-Scene Interoperability vs. “Center-toCenter” Interoperability
 Law enforcement (patrol) vs. Fire/EMS (“inquarters”)

Slide 8
Integrating Incident Information
Fundamental System Differences
TRANSPORTATION
MANAGEMENT
•Data Fusion/Dissemination
•“Awareness” set by sensors
•Multi-agency incident mgmt
•Real-time facility mgmt
•Traveler Information
•New development systems
PUBLIC SAFETY
DISPATCH
•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
Slide 9
CAD Interfaces
Pen-Based
Computers
AVL
CAD
Mobile
Data
Computers
Same considerations apply to Fire/EMS equipment
Slide 10
Typical TMC Interfaces
Vehicle
Detection
Stations
Ramp
Metering
System
Closed
Circuit
Television
Traffic Management
Center (TMC)
• ATMS Software
• TMC Operators
• Highway Patrol MIO
• Dispatch
Traffic
Management
Team
Maintenance
Freeway
Service
Patrol
Changeable
Message
Signs
Highway
Patrol
Adjacent
Districts
Local
Agencies
Highway
Advisory
Radio
Media
State DOT
Headquarters
Slide 11
InterCAD Results
Slide 12
InterCAD PHASES 1 and 2
PARTICIPANTS
•SAN DIEGO PD
•SAN DIEGO SHERIFF
•CHP BORDER DIV
•OCEANSIDE PD/FD
•CARLSBAD PD/FD
•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
Slide 13
InterCAD Technical Approach
IBM Message Queue Manager (MQM)
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)
Regional
Network
MQM Server
(DEC Alpha,
Win NT, OS/2
etc.)
MQM Client
(CAD Host)
Slide 14
Phase 2 Capabilities (Planned)
Addressable Consoles (& MDC’s)
 Incident Type & Location
 Units Assigned & Status
 Addressed or Broadcast Messages
 Message Priority Levels
 “Update Incident” Entries

Slide 15
InterCAD Lessons Learned - I





Lost project “Champion” (CHP Communications
Center Lt.)
No agency leadership to fill void
Reliance on a single CAD vendor for technical
solution to CAD modifications
Lack of security vulnerability analysis
Not enough reliance on existing LE assets (e.g.
ARJIS communications and governance
structure)
Slide 16
InterCAD Lessons Learned - II





Need a clear Concept of Operations (i.e. start
w/ recognized systems engineering
principles) – follow up w/ RequirementsBased Engineering
Find an agency/key person champion
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
Work within existing Public Safety technical
environment to maximum degree possible
Slide 17
Interface Recommendations
Slide 18
Conceptual Public Safety/TMC Interface
Platform independent
message service Offload message
processing from host
CAD systems
ARJIS = Automated Regional
Justice Information System
Network
Other InterCAD Agencies
Existing Law
Enforcement
Network Addresses
Security Issues
Regional
IMTMS
Network
ARJIS
Network
SDPD CAD/MIS
Message Server
(Windows XP/2000)
Message Server
(Sun/Solaris)
Operational concept defines information exchange needs
Slide 19
Conceptual Information Sharing
INCIDENT/TYPE/LOCATION
HIGHWAY/ARTERIAL CONGESTION
CONSTRUCTION/CLOSURES
RECOMMENDED ROUTING
CCTV VIDEO
Transportation
Public Safety
INCIDENT TYPE/LOCATION
UNIT ASSIGNMENT
UNIT STATUS
INCIDENT DETAILS (AS OCCURRING)
Over 90% of initial incident notifications go to 9-1-1
Slide 20
CAD Interface Approach
CAD - Message
Server link
Inter-Console
Message
SDPD
“Pseudo” Console
TMC
Call Takers
“Pseudo” Console
MQ Series
Message
Server
External Agency
Message
Dispatchers
CHP
InterCAD
Network
Slide 21
“Handshake”
Op W/S
CAD
Terminal
Public Safety Integration
CORBA Interface
MQ Series
Interface
CHP CAD
InterCAD
ARJIS
Network
Common Carrier
Regional IMTMS
Network
InterCAD
Seed
(MQ Server)
+
Firewall
IMTMS
Network
“Handshake”
Server
PD/FD Agency
MQ Server
InterCAD
Network
Host CAD System
(Future)
IMX Terminal
(Existing)
Migration
Path
Slide 22
Standards Recommendations
Slide 23
Message Standards
(IEEE 1512 Series)
TCP/IP
Network
“Tag”
MQ Series
Server “Tag”
Common
Msg Std Data
Data
Message
Server
MQ Series
Server “Tag”
Common Msg Std Data
Data Translation
Host CAD
Host CAD Data
Dissimilar CAD’s/TMC’s speak different languages
Slide 24
P1512 Future Requirements

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
Slide 25
Institutional Recommendations
Slide 26
Recommendations for Public
Safety Integration Projects



Involve Agency CEO’s and Keep Apprised
Governance Body – Agency Ownership
Public Safety Community Should Establish a Regional
Architecture Approach to Information Sharing paralleling
USDOT Effort
– Communications
– Standards

Adequate Outreach to Agencies at All Levels
 Develop a “Plug and Play” (Blueprint) Approach
 Mainstreaming Projects – RTP, O&M
 Involve multiple CAD vendors from the beginning
Slide 27
InterCAD Next Steps
Use lessons learned from original project
 Use the regional architecture (currently
being revised for Final Rule compliance)
 Establish working level champions from
both public safety and transportation
 CEO buy-in from both communities
 Establish vendor integration team
 Start modestly and add capabilities using
a phased approach

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
 Like any other transportation initiative,
integration investments and recurring costs
must be made compelling to executive
management and elected officials

Slide 29
End