ARINC PROPRIETARY
ARINC Wireless Interoperable Network Solutions (AWINSTM) An Architecture for IP - Based Communications Interoperability
Agenda
ARINC Overview Radio Interoperability AWINS Solution Overview Case Study: OPSCAN Case Study: Hurricane Katrina, and Operation Lifeline
Summary Questions
Page 2
ARINC Overview 75 years of proven experience in design, deployment and support of radio systems, worldwide Proven record of successful Public Safety communications
projects:
− Largest deployment of IP based LMR Interoperability for Public Safety OPSCAN in Washington State: 200 Frequencies, 42 agencies, 23 sites
− Mobile Command Vehicles supporting interoperability for FEMA, Anne
Arundel County, Maryland, Orange County Florida and others
− Implementation and on-going support of 900 mobile data computers and
supporting wireless infrastructure in Prince George’s County, MD
− Providing project management and technical oversight to reband over 6000
subscriber units and related infrastructure across 15 different state agencies that are affected by the 800 Mhz rebanding directive in Georgia
World’s largest private RF data link network with IP
interoperability
− Supports all major airlines, package carriers, and their suppliers
Manage over 16,000 Motorola, IDEN, and M/A COM 2-way land
mobile radios
− Includes all radios in use by TSA airport security Page 3
ARINC Overview An Integrator and more…
− − −
A Culture of providing Mission Critical Services
− − −
Full Service: Helpdesk, NOC, On Call Maintenance
Recognized performance during crisis Certified Radio Maintenance Repair for most Radio systems Quality Performance reviewed quarterly by the Board ISO Certified
ARINC, an Integrator who lives what we deliver!
Page 4
SAFECOM Interoperability “Wireless interoperability is the ability of public safety service and support providers to talk with each other via voice and data − − − −
on demand in real time when needed when authorized”
Source: SAFECOM, Improving Public Safety Wireless Communications and Interoperability (June 2004)
Page 5
The Interoperability Challenge Incompatible and aging communications equipment Limited and fragmented budget cycles and funding Limited and fragmented planning and coordination Limited and fragmented radio spectrum Limited equipment standards
Source:
National Task Force on Interoperability (February 2003)
Page 6
AWINS ARINC Wireless Interoperable Network Solutions (AWINS™) AWINS is a standards based architecture that enables interoperability among disparate communication devices Commercial-Off-The-Shelf (COTS) products Convergence of voice, video, and data Open standards based architecture
AWINS delivers a comprehensive interoperable communications solution for day-to-day and crisis operations that is significantly more cost effective than radio replacement.
Page 7
Why AWINS? AWINS will enable you to leverage existing investments such as existing radio
systems, networks and tactical interoperability solutions AWINS will take you beyond radio interoperability to include many other forms
of communications such as VoIP phones, regular phones, Cell phones and PCs ARINC, in conjunction with our partners, have performed extensive testing of
our architecture and it’s components to ensure a successful implementation AWINS can meet short-term implementation requirements and grow to meet
long-term objectives AWINS has been validated both in the lab and in many live customer
implementations − ARINC has worked with the leading gateway vendors and command and control
applications to develop a keen understanding of the capability of each solution − We have pre-built configurations that fit many popular radios from leading radio vendors Page 8
The AWINS Concept
Integrate existing RF Systems with a standards based IP Network Utilize centralized Command and Control software to provide audio management and conferencing capabilities Interconnect with other interoperability solutions already in place Bridge communications between legacy and future radio systems
including P25 compatible systems Move beyond “Radio Interoperability” to true “Communications
Interoperability” by supporting Voice, Video and Data in one system Deploy regionally and scale incrementally Deliver using a repeatable, tested, and trusted methodology
Page 9
AWINS Architecture The basis of AWINS is a common language for interoperability and a
command and control plane that manages access to information and directs communications to appropriate parties Internet Protocol (IP) is the primary building block − Worldwide standard that enables efficient transfer of voice, video and data − − − − −
on a common platform Many commercial products available Extremely scalable, very resilient Offers independence from “layer 1 and 2” technologies Enables Quality of Service (QOS) management techniques IP Multicast provides high degree of efficiency
Command and control is implemented at the application layer − COTS products with standards based interfaces
Page 10
AWINS Features A fully integrated, turnkey communications interoperability solution
− From requirements analysis and implementation to testing, training, and
ongoing support
Voice Communications among any of the following:
− Radios, PSTN (cell, pots, PBX), VoIP phones (Fixed and WiFi), PC clients,
and Nextel PTT. Even the audio component of a Video Teleconference
Discrete command and control with roles based user access − Configures Virtual Talk groups
Dial access to any radio or VTG − From any phone, anywhere
Long-term voice recording for forensics and training purposes A Single homogenous IP network that support Voice, Video, and Data
Page 11
Successful Integrations Radio Frequencies: − − − − − − − − −
900 MHz 800 MHz 700 MHz VHF Hi/Lo UHF Marine Aviation RACES HF
− Various combinations: P25 Trunked Conventional Digital Analog
Radio types: − − − − − −
Consoles Base Stations Mobiles Portables Repeaters Voting Systems
Additional Technology: − − − − − −
IP telephony PSTN Nextel PTT Cellular Video Conferencing Video Surveillance
IP networks: − − − − − −
Optical Microwave Copper (T1, Frame, etc) Satellite WiFi Mesh
Page 12
AWINS Logical Model Cisco ISR – Single Box UHF
800 Nextel PTT others
POTS, PBX, PSTN
VoIP Gateway
Cellular, GSM
VoIP Phone IP PBX Desktop Client Mobile Devices Video Conferencing
Standards Based IP Infrastructure
700
Tools and Applications LMR Gateway
VHF
Command and Control
IP
Recording Alert Systems Logging Consoles
Video Surveillance
Page 13
AWINS Architecture Site 1 Portable Portable
HF
VHF
Portable
Portable
VHF
700
Private IP Network
P25
Command and Control
Site 3 PSTN
Portable
UHF POTS
Site 2 800
Portable
Mobile/Cell
Nextel PTT
Trunked
Page 14
VoIP Voice over IP (VoIP) is the audio “language” within AWINS − AWINS utilizes a full set of IP standards including: ITU G.711 and G.729 codecs convert between analog audio and
digitized audio Multicast and Real Time Protocol (RTP) carry VoIP traffic H.323, SCCP, and SIP are used for signaling (call setup/tear down)
For non-native IP or VoIP technologies a “gateway” is used to translate to and from VoIP − LMR Gateway for Radio: An E&M port is used to obtain the analog audio from a radio
(base station, mobile, or handheld) 2 wire, 4 wire, or BIM Card interface − VoIP Gateway for POTS/PSTN/PBX: −
Conversion to VoIP by Cisco Unified CallManager or
CallManager Express Page 15
Path of a Radio Transmission UHF
VHF
Portable
Portable
Private IP Network
2/4 wire
E&M
CODEC
VoIP
IP Network
IP Network VoIP
CODEC
E&M 2/4 wire
Page 16
Key Components
LMR Gateway − Integrated Services Router (ISR) that provides connection to any type of
radio by converting E&M to VoIP
Management Server − Provides user interface and manages interoperability
Audio Mixer − Provides audio mixing services for Talk Groups
Voice Services − Cisco CallManager or CallManager Express provide IP telephony
integration
Page 17
Case Study: OPSCAN
− Interoperability in Northwest Washington
Page 18
The Need
The agencies that formed OPSCAN recognized the need for interoperability based on several events, including the capture of a terrorist arriving via a ferry from Canada and the shooting of a sheriff’s deputy − The lack of interoperable communications hampered both efforts
OPSCAN obtained grant funds and developed an RFP to build an Interoperability system throughout the region ARINC and the AWINS architecture was chosen to provide the solution
Page 19
The System
There are several components − The network − The Gateways − The Command and Control System
The Network is built among shared resources including WSP, USCG, and local networks − − − −
Leased T1 circuits Microwave T1 circuits ATM OC3 Microwave Backbone Redundant connections Assist with problems like Tankers moving in and out of port!
Page 20
The System
The Gateways are Cisco LMR gateways − Installed at 24 locations Including EMD at Camp Murray − Gateways support from 10 to 20 radios depending on model implemented
The Command and Control system is WAVE from Twisted Pair Solutions − Browser accessible at all locations and from a VPN − Being upgraded to version 2.0 SP3 − Redundant Management and Media servers
Page 21
OPSCAN VoIP Network - Transport Media and Router Placement Kelly Ridge Neah Bay Dispatch
Slip Point (Pearson Creek)
USCG Neah Bay
4
9
USCG
(3) Ediz Hook USCG
6 SERIAL
USCG s Ellis Lookout w
PA PS
Forks PD 5
Ocean Grove
WSP
4
6
USCG Bahokus
25 FD3-Sequim
Mem. Hosp.
8-T T1
Ellis Mtn 2
GATR
8
Jefferson Transit 6 Port Hadlock JeffCom
WSP (3)
9+2
2
15
Striped Peak
WSP-PA
PenComm 12
4 33
North Point
12 CC-EOC
3 USCG Maynard Peak
6
WSP
Clallam Transit
Gold Mtn. WSP
4 WSP Octopus Mtn
Capital Peak WSP
WSP Queets
WSP Neilton Pt.
WSP OC3 Micro-Wave (4Mb/s) Fiber-Optic (OPSCAN) 10 Mb/s USCG Micro-Wave (1.544 Mb/s) Ethernet Spur (OPSCAN) (10 Mb/s + T1)
WSP Cosmopolis
WSP Hoquiam
Router - Cisco 3845
Telco T-1 by Transit Agency Remote base control of repeaters OPSCAN-VOIP-Transport Media-Ver-F.vsd
Media connection - no router
Router - Cisco 3825
Clallam County WAN over NOANet FO Channelized Radio Spur (OPSCAN)
EMD-Camp Murray
Router - Cisco 2811
Transit Agency Cisco 2811 (Subsequent Contract Addition by Agency)
Page 22
Case Study: Hurricane Katrina, and Operation Lifeline
− Anne Arundel County
and ARINC respond in Jefferson Parish, Louisiana
Page 23
The Need
In the post-event analysis of Hurricane Isabel, Anne Arundel County Maryland recognized the need for “Mobile Command Vehicle” that would enable emergency services staff to respond more effectively to large scale disasters and events The county worked with ARINC and MBF Industries to develop “Mobile Command and Control Unit 1” (MCCU-1) which was delivered in the fall of 2005 − MBF built the truck − ARINC provided the communications infrastructure and acted as the
Project Manager
Page 24
County Objectives Anne Arundel County wanted a Mobile EOC that would allow them to: − Remain operational in the event the primary EOC is
unavailable. − Manage emergency operations using the National
Incident Management System (NIMS) from a mobile environment. − Stream video surveillance footage and have video
teleconferencing capabilities from the Mobile Command Vehicle back to the Anne Arundel County EOC − Establish Interoperable Communications with any
agency in the State of Maryland and jurisdictions in counties of border states. Page 25
MCCU Communications Capabilities Communications vehicle designed to allow for mobile
communications and RF interoperability. Systems include: − − − − − − − −
800 MHz UHF VHF High Band VHF Low Band Marine Band Aviation Band RACES VHF Voice/Packet (HAM/Amateur) RACES HF Band (HAM/Amateur)
Will allow for mobile communications and
interoperability between − − − −
17 RF Systems (479 Frequencies-250 programmed) 20 IP Phones 10 POTS/Cell connections Interconnected with County phone systems
Other capabilities include Video Teleconferencing,
Video Surveillance, and Data Applications.
Page 26
Anne Arundel Mobile Command Vehicle
Page 27
Position Layouts
Page 28
Katrina Support
MCCU-1 was requested by 3 different response efforts. Deployed on September 2nd, 2005 to provide communications and
logistics support to Operation Lifeline in Jefferson Parish, LA. Operation Lifeline was a response effort put together by the State of
Maryland to establish 6 medical clinics in Jefferson Parish to treat citizens and transport them to functioning hospitals. The MCCU was operational within 45 minutes of arriving at the mission
base camp, Meadowcrest Hospital The MCCU provided dispatch and interoperable communications for
over 20 different agencies with disparate radio systems.
Page 29
Success! At a ceremony honoring the Anne Arundel Team that participated in Operation lifeline, Chief Ron Blackwell of the Anne Arundel Fire Department summed up MCCU-1’s performance this way: “There are always some questions in your mind, will it do what we’ve been told when it’s most needed… this unit passed that test with flying colors”
The county also cancelled acceptance testing, confident that MCCU-1 was up to the task More importantly, Operation Lifeline treated over 6000 patients in 2 weeks
Page 30
Additional Interoperability Projects
Anne Arundel County Emergency Operations Center FEMA Mobile Command Vehicles Massachusetts Homeland Security Region 1 US First Air Force Homeland Defense Orange County Mobile Command Vehicle State of Maryland Mass Transit Administration Mobile
Command Vehicle City of Annapolis Mobile Command Vehicle St. Charles Parrish, LA
Page 31
AWINS Architecture Advantages A solution architecture that: − Protects legacy investments − Scalable and expandable − Leverages existing backbone infrastructure − Cost effective − Standards based − Provides near term availability
Page 32
Summary
ARINC has the technical expertise and experience to help public safety and private enterprises achieve their interoperability objectives Our solution provides you with: The ability to leverage existing infrastructure and interoperate with other Local, State and Federal agencies A highly reliable and affordable IP based architecture solution An easy-to-use, interoperable, showcase project
Page 33
ARINC PROPRIETARY
Learn more at
www.AWINS.net Contact: Marvin Ingram –
[email protected] Dave Chapman –
[email protected]