Exhibit C-1 -System Description
1.1
System Overview
The Orange County (“the County”) SmartX Core Migration Project, Phase I, will
provide a new Project 25 standards-based Master Site. This includes a Motorola
ASTRO 7.9 Master Site with SmartX and MGEG interfaces for Orange County. The
ASTRO25 7.9 Master Site represents Motorola’s latest wide area Project 25 trunked
offering. The SmartX and Motorola Gold Elite Gateway (MGEG) interfaces allow
the County to connect existing SmartZone 3.0 subsystems and Gold Elite dispatch
centers to the new ASTRO25 Master Site.
The high level block diagram for the Master Site is shown in Figure 0-1.
Figure 0-1: ASTRO 25 Master Site
Motorola Confidential Restricted
Use or disclosure of this proposal is
subject to the restrictions on the title page
Orange County
SmartX Core Migration Project, Phase I
Revised: September 30, 2010
Exhibit C-1 -System Description
1
This System Overview presents a high-level overview of the project. Additional
details for each subsystem can be found in subsequent sections:
Orange County
SmartX Core Migration Project, Phase I
Revised: September 30, 2010
2
Exhibit C-1 -System Description
Motorola Confidential Restricted
Use or disclosure of this proposal is
subject to the restrictions on the title page
1.2
Orange County SmartX Core Migration
The Orange County SmartX Core Migration consists of the following major sections:
♦
♦
♦
♦
ASTRO25 7.9 Master Site
MGEG and AEB
SmartX Site Converters and SmartX Routers
Network Manager Terminal
The ASTRO 25 system can continue to be expanded and enhanced to accommodate
the future growth needs of Orange County.
The system will be built with redundancy to provide high performance reliability.
This system meets the Project 25 standards for interoperability to maximize system
usage across other cities and agencies.
The ASTRO 25 Master Site equipment provides the interface between the simulcast
subsystems, IR subsystems and the dispatch console network. ASTRO 25 provides an
extra layer of user-friendly system and database management. The user-friendly
management architecture provides a GUI-based management terminal capable of
multi-tasking and presenting all of the information required to manage Orange
County’s system.
The current SmartZone 3.0 system infrastructure software / firmware will need to be
upgraded as shown in the chart below in order to be compatible with the ASTRO 25 /
SmartX solution:
Table 0-1:
Site Types
SmartZone 3.0 / 3.5
SmartZone 4.1
6809 Prime Site Controllers
SER 1Q06
Z release or later
IntelliRepeater Sites
SER 1Q06
Z release or later
Included in the project are six (6) Network Manager Terminals. The design includes
ZoneWatch, Affiliation, Unified Event Manager (UEM), Unified Network
Configurator (UNC) and User Configuration Manager (UCM) available for the
County’s system.
The ASTRO 7.9 Master Site is the interface, switching center and control point for
the Orange County Simulcast cells, IR sites and the NM terminals. The NM terminals
require an interface to the Master Site to perform their main functions.
Motorola Confidential Restricted
Use or disclosure of this proposal is
subject to the restrictions on the title page
Orange County
SmartX Core Migration Project, Phase I
Revised: September 30, 2010
Exhibit C-1 -System Description
3
1.2.1
Orange County SmartX Core Migration Equipment
Summary
This section provides an overview of the system components provided for Orange
County. Additional detailed information on each subsystem can be found in the
Equipment List section following this overview.
The following table summarizes the equipment for the proposed ASTRO 25 Master
Site equipment, to be located at Loma Ridge.
Table 0-2: Orange County Master Site Equipment
1.2.2
1.2.2.1
Item
1
Function
ASTRO 25 Master Site
2
SmartX Site Converter
3
ASTRO Master Site
Network Management
4
Audio Switching
5
Dispatch
Equipment
2 Redundant Zone controllers and NMS Server
2 Redundant Core Routers
2 Redundant Gateway Routers
2 Redundant Master Site LAN Switches
2 Domain Controllers
1 Core Security Management Server
2 Relay Panels
1 GPS Frequency Standard, FEI-Zyfer (Re-use
County existing equipment)
12 SmartX Site Converters
12 Universal Gateway (site router)
6 Network Management Terminals
1 Remote Network Management Terminal (Orange
County Communications Building, Eckhoff)
- Zone Historical Report Application Software
- Dynamic Reports Application Software
- Zone Watch Application Software
1 Terminal Server
1 Ambassador Electronics Bank - 2 Card cages
(Re-use County existing AEB)
2 MGEGs
1 TeNSr Channel Bank and associated modules
(Re-use County existing Channel bank)
1 MCC 7500 Dispatch Console
ASTRO 25 System Elements
Master Site Equipment
The Master Site is located at the Orange County Loma Ridge site. The Master Site
serves as the core of the ASTRO P25 trunked system and contains the zone
controller, support servers and WAN / LAN routing equipment. The term System
Master Site designates a site containing the User Configuration Server (UCS). At the
Master Site, the zone controller, audio distribution, and network management work
together to process calls, distribute audio, assign channel resources, and conduct
network management functions.
Orange County
SmartX Core Migration Project, Phase I
Revised: September 30, 2010
4
Exhibit C-1 -System Description
Motorola Confidential Restricted
Use or disclosure of this proposal is
subject to the restrictions on the title page
The Master Site is the central point for call processing and system management
within the zone. The Master Site equipment is described briefly in the following
sections.
1.2.2.2
Motorola MZC5000 Zone Controller
The Zone Controller is a powerful computer that provides call-processing and control
functions for the ASTRO 25 network. The zone controller is based upon the Sun®
server product line. The redundant zone controllers connect to the network through
the LAN switch. This LAN switch is used to switch system resources between the
zone controllers and provide high availability call management within the zone.
The zone controller determines the site and zone audio assignments and connects the
required resources into a single call. To insure uninterrupted call processing, this
important element is provided in a fully redundant configuration with automatic
switchover in the event of a failure:
♦
A zone controller may have a redundant state of either active or standby. While
both zone controllers are powered and enabled at the same time, only one zone
controller is actively participating in call processing tasks at any one time while
the second controller is in standby mode. The zone controller that is responsible
for call processing is in the active state. The zone controller that is not actively
processing calls in the zone is in the standby state. System information that is
necessary for call processing is downloaded to both zone controllers. The zone
controllers include hardware for storing data, controlling zone activities, and
communicating with zone resources
The Zone Controller’s software is divided into two areas: call processing and
resource management. The call processing functions include receiving call requests,
radio site registrations and talkgroup affiliations. The Zone Controller operates at the
Zone level, managing the remote RF and dispatch sites, checking call access
privileges, queuing of calls as required, selecting and assigning available channels at
its sites, issuing call grants to requesters, and monitoring and controlling and setup of
each call sequence in the Zone.
The resource management portion of the software includes the control and setup of
the packet switched network and management of the database containing information
pertaining to that Zones’ users, talkgroups and site information. The Zone controller
manages the RF resources within its Zone, assigning channels at the proper sites.
When a call request takes place, the Zone Controller acknowledges the call and
assigns channel resources within the Repeater sites where talkgroup members are
located. The setup occurs through the communication network that exists between the
remote sites and the Zone Controller. Simultaneously, the Zone Controller tells the
communication network which sites to send the IP addressed digital packet voice
traffic.
Motorola Confidential Restricted
Use or disclosure of this proposal is
subject to the restrictions on the title page
Orange County
SmartX Core Migration Project, Phase I
Revised: September 30, 2010
Exhibit C-1 -System Description
5
In summary, the zone controller is responsible for processing calls, managing audio
paths, controlling zone infrastructure, and providing services to subscribers and
console operators. The Zone Controller directs and controls most of the components
in the zone.
The Sun Netra T5220 using the Solaris operating system is used for the zone
controller.
Figure 0-2: Netra T5220 Server Front View.
Figure 0-3: Netra T5220 Server Rear View.
1.2.2.3
Network Management, LAN and User Interface
The system includes a trunked radio system Zone Controller Network Management
subsystem.
The Mission Critical ASTRO 25 Digital IP network management subsystem, referred
to as the Master Site, includes
♦
Servers and other components that forms the Motorola Private Radio Network
Management (PRNM) Suite.
♦
Local area Network and WAN routing solution
♦
Software and infrastructure required for user management, system management,
fault management, and performance management.
Orange County
SmartX Core Migration Project, Phase I
Revised: September 30, 2010
6
Exhibit C-1 -System Description
Motorola Confidential Restricted
Use or disclosure of this proposal is
subject to the restrictions on the title page
♦
System Control Processor and Management Servers
♦
Zone Domain Controllers
1.2.2.4
Network Management Servers and Software Suite
The Network Management System (NMS) can be viewed as a set of software
applications or tools used to manage the ASTRO 25 wide area trunked radio system
and its constituent components. The NMS hardware is based on a Sun Microsystems’
server. The NMS supports the following services:
♦
Fault Management – Applications are included for monitoring the status of the
transport network and the individual infrastructure components; displaying fault
information; forwarding alert information; and performing diagnostic procedures.
♦
Configuration Management – Facilities are provided for entering and
maintaining the operational parameters of the infrastructure components and user
devices (i.e., the mobile and portable radios).
♦
Accounting Management – NMS supports the tracking of radio usage of the
system by providing an optional interface to third-party accounting and / or
billing applications.
Performance Management – Standard and optional applications are available for
monitoring, reporting, controlling, and optimizing the use of system resources.
Security Management – NMS includes features for setting user privileges and
controlling their access to view and / or modify information contained in the
configuration databases.
♦
♦
The NMS subsystem is comprised of the following servers at the zone and system
levels of the ASTRO 25 system.
♦
♦
1.2.2.5
NMS zone-level servers (one each per zone): Air Traffic Router, Zone Database
Server, Unified Event Manager Server, and Zone Statistics Server.
NMS system-level servers (one each per system): User Configuration Server.
Server Function Description
Air Traffic Router
There is one Air Traffic Router (ATR). The ATR hosts a variety of real-time, data
processing applications to support user and system applications. This includes
processing real-time call transactions, sourcing Air Traffic Information Access
(ATIA) data stream to third-party applications, logs ATIA data to disk, routes Radio
Control Manager command and status packets to / from the Zone Controller, and
routes call logging packets from the Zone Controller to the Statistics servers.
Unified Network Configurator (UNC)
The next generation configuration management tool is the Unified Network
Motorola Confidential Restricted
Use or disclosure of this proposal is
subject to the restrictions on the title page
Orange County
SmartX Core Migration Project, Phase I
Revised: September 30, 2010
Exhibit C-1 -System Description
7
Configurator (UNC). The UNC replaces Zone Configuration Manager (ZCM),
Network Transport Management System (NTMS), and a portion of the Universal
User Configuration Manager. The UNC is the central point for configuring all system
elements.
Unified Event Manager (UEM)
The UEM handles most fault management tasks for the system. UEM utilizes SNMP
to handle object discovery, topology map generation and polling, and is integrated
with Motorola’s Router Management System to manage the Motorola brand routers
used in the transport network. The UEM is the central point for all fault management
activities in the ASTRO25 Master Site.
Zone Statistics Server (ZSS)
There is one Zone Statistics Server. The statistics server is the data repositories for
data statistics necessary to drive Historical Reports. Statistics such as the number of
Calls, Push-To-Talks, and Busies are accumulated over preset time intervals. Data
can be accumulated over a 1 hour interval and retained up to 10 days, or can be
accumulated monthly and retained for 1 year.
User Configuration Server (UCS)
There is one User Configuration subsystem. The UCS provides database storage and
back-end processes required for most system-wide functions. Included are the mobile
radio records, talkgroup records, and services to automatically distribute and replicate
these records in the UNC. The UCS is accessible to authorized users from any client
PC workstation in the system.
Network Manager Terminals
The NMS Windows-based client / server architecture distributes most of the user
application processing to the client PC workstations. This approach yields important
benefits:
♦
Application performance is less dependent on the number of concurrent users and
open applications;
♦
Personnel typically responsible for managing a radio system or computer network
are already familiar with, or easily trained to use, the Graphical User Interface
(GUI) of NMS applications that conform to Windows operating system
conventions; and the following applications run on or may be accessed from the
PC client workstations;
♦
System Profile
♦
User Configuration Manager
♦
Software Download
♦
Zone Profile
♦
Zone Configuration Manager
Orange County
SmartX Core Migration Project, Phase I
Revised: September 30, 2010
8
Exhibit C-1 -System Description
Motorola Confidential Restricted
Use or disclosure of this proposal is
subject to the restrictions on the title page
1.2.2.6
♦
ZoneWatch
♦
Affiliation Display
♦
Historical Reports
♦
Dynamic Reports
♦
Fault Manager using Unified Event Manager (UEM)
♦
Radio Control Manager (RCM)
♦
Radio Control Manager Reports
Network Equipment
Networking Equipment
The ASTRO 25 release Transport Network is engineered to meet the performance
requirements of a real time system transporting voice, call control, network
management, and ancillary network services. The Transport Network is a closed
network. Only Motorola supplied equipment, applications and services can be used
on the network.
1.2.2.7
Ethernet LAN Switches
Two HP 3500 LAN switches are used to support the Master Site LAN in the ASTRO
25 system. All the IP-based equipment in the Master Site, such as the routers, servers,
zone controllers, clients, and other IP-based equipment, are connected to one or more
of these switches.
Figure 0-4: HP Procurve 3500-48.
The two HP 3500-48 Ethernet LAN switches provide the backbone for the Master
Site LAN. These switches are interconnected by a gigabit Ethernet trunk to provide a
high speed link for redundantly supported subnets between the switches. Critical
equipment at the Master Site such as Gateway routers, Core routers, and Zone
Controllers are connected across both switches for high availability and reliability.
Motorola Confidential Restricted
Use or disclosure of this proposal is
subject to the restrictions on the title page
Orange County
SmartX Core Migration Project, Phase I
Revised: September 30, 2010
Exhibit C-1 -System Description
9
1.2.2.8
Core and Gateway Routers
Core routers route traffic between the Master Site and the remote sites (Simulcast
cells and IR sites via SmartX interface, ASTRO 25 Repeater sites, and MCC 7500
dispatch console sites). The core router interfaces to the Ethernet switch on two,
100Base-T links. The Core router provides WAN T1 ports for site link termination.
Core Routers
The Core routers perform tasks such as routing control, audio, data, and network
management traffic in and out of the Master Site. They provide control path
redundancy and the segregation of network management traffic. The primary router
provides the necessary services to the sites while the secondary serves as the standby
router. The core router can also be configured to receive Network Time Protocol
(NTP) and to interface with the network management server using SNMP.
The system requires two core routers. Each core router has two separate LAN
connections to the Ethernet switch. The core routers are capable of supporting any
combination of up to 24 RF sites and dispatch sites. Additional pairs of core routers
can be added to the system, if required, to support up to 96 RF sites and dispatch
sites.
Figure 0-5: ST6000 Core Router
Relay Panels
Passive relay panels and 12-port modules are added to the Core router equipment to
provide redundancy and port density. This feature allows for the Cooperative WAN
Routing. This allows for the core routers to have a direct interface to the various sites
in the system.
Orange County
SmartX Core Migration Project, Phase I
Revised: September 30, 2010
10
Exhibit C-1 -System Description
Motorola Confidential Restricted
Use or disclosure of this proposal is
subject to the restrictions on the title page
Figure 0-6: Relay Panel
Gateway Routers
Gateway routers are used for devices that require network redundancy and are
multicasting beyond their local LAN. Gateway routers provide several benefits for
the zone’s Master Site:
♦
They provide a single access point or gateway to access the core routers.
♦
They isolate multicast traffic from the various hosts they are servicing.
♦
Because there are two Gateway routers, they provide redundant connections for
hosts with redundant interfaces (zone controller) or load balancing devices.
The Gateway routers serve as the interface for all control information that flows
between the zone controller and the resources necessary to process a call. These
resources include RF sites, and consoles. Additionally, the Gateway routers serve as
the rendezvous point (Control RP) for control information. The Gateway routers use
10Base-T interfaces for connection to the LAN switch.
Figure 0-7: ST6000 Gateway Router.
Motorola Confidential Restricted
Use or disclosure of this proposal is
subject to the restrictions on the title page
Orange County
SmartX Core Migration Project, Phase I
Revised: September 30, 2010
Exhibit C-1 -System Description
11
1.2.2.9
Zone Core Synchronization
FEI-Zyfer CommSync II will be used as a Global Positioning Satellite (GPS)-based
frequency and time reference unit and it will be provided by Orange County.
1.2.2.10
Core Security Management Server
The Core Security Management Server (CSMS) consists of a Windows-based HP
Proliant DL360 G5 line Server with software components required to ensure that only
authorized users access the radio network system. The CSMS is required to safely
enable use of system interfaces for remote service access and remote network
management service activities.
The CSMS performs the following functions:
♦
♦
Administration of network antivirus software
Administration of network barrier components (i.e. firewall)
Figure 0-8: HP DL360 G5 Server Front View
Figure 0-9: HP DL360 G5 Server Rear View
Orange County
SmartX Core Migration Project, Phase I
Revised: September 30, 2010
12
Exhibit C-1 -System Description
Motorola Confidential Restricted
Use or disclosure of this proposal is
subject to the restrictions on the title page
1.2.2.11
Out of Band Management Terminal Server
Out-of-band management is one 48-port terminal server. This server provides
connections to all the serial (console) interfaces of the devices at the Master Site as
well as a LAN connection to the LAN switch to support Telnet. This connection
provides the means to program an IP address in any device which in turn allows
access to all the other programmable functions. The terminal server has a built in
modem that allows an operator to dial into the terminal server connected to the
Master Site LAN.
Figure 0-10: Terminal Server Front View
Figure 0-11: Terminal Server Rear View
1.2.2.12
Motorola Gold Elite Gateway (MGEG)
The Motorola Gold Elite Gateway (MGEG) interface allows an existing
CENTRACOM Elite dispatch system to communicate over and control a packetbased ASTRO 25 trunked radio system. The MGEG Gateway device performs the
functions that the DIUs did in previous releases. The MGEG connects the AEB to the
packet network. It vocodes / devocodes audio and translates IP packets to / from the
IP packet network. The MGEG allows for support of the CENTRACOM Gold Series
architecture (AEB, CEB, and Elite Ops) within the ASTRO 25 system.
The MGEG also allows console dispatch operators to participate in secure
communications. The audio between the MGEG and the subscriber is encrypted;
however, the audio between the MGEG and the console is not encrypted.
Motorola Confidential Restricted
Use or disclosure of this proposal is
subject to the restrictions on the title page
Orange County
SmartX Core Migration Project, Phase I
Revised: September 30, 2010
Exhibit C-1 -System Description
13
The MGEG is a rack-mounted Compact PCI chassis and is located with the AEB.
The chassis includes a CPU card, Voice Cards with a NIC (Ethernet) and Crypto
cards to support Secure Voice features to the console. The Crypto Card provides
encryption and decryption functions to the MGEG to allow secure dispatch.
Interfaces
The MGEG requires a router interface to the ASTRO 25 system. This router interface
is provided by the Gateway routers included in the Master Site design. The Gateway
router interfaces directly into the Master Site LAN switch.
The MGEG interfaces directly into the AEB via T1 circuits. Two T1 circuits are
required for each MGEG for a total of four T1s.
1.2.2.13
Ambassador Electronics Switch (AEB)
The Ambassador Electronics Bank is a large capacity Time Division Multiplex
(TDM) audio processing switch that is used to route the repeater and dispatch audio
throughout the system. The AEB can process at least 700 audio sources
simultaneously depending on the configuration. Its cardcage has up to 32 digital
audio buses, which interface to any combination of CEBs and / or channel banks.
The AEB is co-located with the Zone Controller. Orange County’s existing AEB in
this configuration works in conjunction with the MGEG to provide the interface to
provide audio switching service for the SmartZone system.
1.2.2.13.1 AMB Modules
Audio processing for the Embassy Switch occurs inside Ambassador Boards (AMB).
Each AMB has two T1 / E1 ports and has the capacity to process audio for up to two
links. These links may connect a Central Electronics Bank (CEB) and Interconnect
subsystem. All of the system’s CEBs are connected to the AEB in E1 + Manchester
configuration. During the migration and cutover, the new provided AEB and
associated AMB modules may need to be configured the same way as Orange
County’s existing AEB to support the new architecture.
1.2.2.14
MCC 7500 Dispatch Console
An MCC 7500 Dispatch IP Console consists of the following elements:
♦
♦
♦
♦
♦
Operator position computer
19" LCD Non-touch Monitor
Voice Processing Module (VPM)
Gooseneck Microphone
Eight Speakers (at Orange County’s request; standard is two)
The MCC 7500 Dispatch Console components are connected together and to the rest
of the ASTRO 25 system on an IP network via console site routers and switches. The
MCC 7500 Dispatch Console functions as an integrated component of the total radio
Orange County
SmartX Core Migration Project, Phase I
Revised: September 30, 2010
14
Exhibit C-1 -System Description
Motorola Confidential Restricted
Use or disclosure of this proposal is
subject to the restrictions on the title page
system, fully participating in system level features such as end-to-end encryption, and
agency partitioning. The encryption algorithms available include AES, DVP-XL,
DES-XL, DES-OFB, DVI-XL, and ADP. Since the network is IP-based, the
system’s interfaces and components can be distributed physically throughout the
network.
1.2.2.15
SmartX Site Converter
The SmartX Site Converter has been designed to enable 3600 SmartZone users to
gracefully migrate to the ASTRO 25 (P25) trunked platform. The SmartX interface
converts the circuit based voted audio and prime site control data to an IP format.
One SmartX box and corresponding router has been included in this design for each
simulcast cell and standalone site (IR and MTC3600 standalone) in the County’s
network. The 12 SmartX Site Converters and 12 routers are located at the Master
Site. They are mounted in the standard 19 inch racks. Both devices require AC
power. There is no redundancy to the SmartX Site Converter therefore a reasonable
number of spares, for easy replacement, have been included in this design.
Figure 0-12: Terminal Server Rear View.
Figure 0-13: Terminal Server Rear View.
1.2.2.15.1 SmartX Site Converter Operation
The SmartX Site Converter interfaces to the existing system through T1 connections.
Each SmartX interface can accept 2 T1 inputs. The voted audio from the Prime site
channel banks was separated onto these 2 T1s. One T1 line carries all the analog
audio and the other carries all the digital audio. The existing channel banks will need
to be reprogrammed to enable this configuration. The SmartX Site Converter
converts both the digital and analog audio into an IP format. The audio is then routed
Motorola Confidential Restricted
Use or disclosure of this proposal is
subject to the restrictions on the title page
Orange County
SmartX Core Migration Project, Phase I
Revised: September 30, 2010
Exhibit C-1 -System Description
15
to the ASTRO 25 Master Site via the Universal Gateway (connected to the ASTRO
25 Core routers).
The 7.9 Zone controllers, servers and LAN / WAN system handle the routing and
processing of the packets internal to the Master Site. Packets are routed to the
existing dispatch centers via the MGEG / AEB solution.
1.2.2.15.2 Fault / Alarms
The existing simulcast / IR system provides alarms to the central controller via the
site controller links. The Central controller aggregates these alarms and forwards
them to the Zone controller. The existing 3600 site alarms are routed to the SmartX
site converter (along with the voted audio). The data is converted to an IP format and
routed to the ASTRO25 Master Site (network manager). The ASTRO 25 event
browser receives and displays the 3600 site alarms from the SmartZone network. The
visual display of the alarms is very similar to the current message display.
1.2.2.15.3 Configuration
Both 3600 and 9600 subscribers are configured in the ASTRO 25 Network Manager
database. Site Converter parameters are managed in the ASTRO 25 Manager and
downloaded to the SmartX Site Converter.
1.2.2.15.4 Rack Spacing
Each SmartX Site Converter uses 1 Rack Unit of space. Additionally each Site
Converter uses a power supply which requires two Rack units of space (3 Power
supplies can fit on Rack mounted Tray). The site routers used in conjunction with the
SMART X converter also require 1 rack unit of space. The SmartX Site Converter
operates on AC power only.
1.2.2.16
ID and TALKGROUP DISPLAY
Radio Display:
The 3600 SmartZone radio personality displays caller ID information using the
7XXXXX format (if no alias available). The 3600 radio personality displays an alias
for the talkgroup selected.
Console Display:
The 3600 consoles (Gold Elite) display caller ID information using the 7XXXXX
format (if no alias available).
1.2.2.17
Universal Gateway (Site Router)
The Universal Gateway provides a T1 interface that handles all of the converted site
audio and control information to / from the SmartX box. The converted information
is routed to the Master Site’s Core routers. The site routers provide the following
function for the NM packets:
Orange County
SmartX Core Migration Project, Phase I
Revised: September 30, 2010
16
Exhibit C-1 -System Description
Motorola Confidential Restricted
Use or disclosure of this proposal is
subject to the restrictions on the title page
1.2.2.18
♦
Media conversion – the router converts the 10MB Ethernet LAN packets to IP
packets encapsulated in Frame Relay.
♦
Traffic prioritization – the router applies the correct prioritization marking to the
packets leaving the site.
♦
Fragmentation – the router fragments large IP packets per standards.
Equipment Upgrades
It is only required to upgrade the Simulcast Prime site controllers, IR base stations,
CEB / CENTRACOM Gold Elite and AEB equipment to the following chart below in
order to make the system compatible with the SMART X solution.
Table 0-3:
Site Types
SmartZone 3.0 / 3.5
6809 Prime Site Controllers
SER 1Q06
IntelliRepeater Sites
SER 1Q06
CEB / Centracom Gold Elite
SER 3Q09
AEB
SER 3Q09
TeNSr Interface Cards
The current TeNSr channel bank’s Interface card utilizes a memory fill battery. There
is a possibility that the Interface Cards are past manufacturers warranty and may fail
at any time. The batteries are not field replaceable, as they reside on an NV RAM
chip. If such is the case, the current cards must be pulled from the channel banks and
sent to the Zhone maintenance depot to have the batteries replaced. It is Motorola’s
understanding that the County has purchased newer Interface cards, as recent as
within the past two years, and that it is not necessary to replace the existing cards.
Motorola will work with the County to verify this. It is the County’s responsibility to
upgrade and repair all existing TeNSr hardware and boards.
1.2.2.19
Fleet Mapping
The ASTRO 25 system has one and only one fleetmap and all subscribers on the
system must have a unique individual ID within the ASTRO 25 fleetmap.
Additionally, all talkgroups on the system must have a unique talkgroup ID within
the ASTRO 25 fleetmap.
1.2.2.20
Roaming
The County’s system currently contains only SZ 3.0 site infrastructure. These
subsystems will all be tied to the 7.9 Master Site. Subscribers configured as
SmartZone will continue to automatically roam between the different Orange County
Motorola Confidential Restricted
Use or disclosure of this proposal is
subject to the restrictions on the title page
Orange County
SmartX Core Migration Project, Phase I
Revised: September 30, 2010
Exhibit C-1 -System Description
17
cells. Orange County subscribers with talkgroups programmed with the SmartNet
configuration will require fingertip / manual switching to roam from one cell to
another.
In the future, P25 sites may be added to the new 7.9 Master Site. In this
configuration, where there is a mix of P25 (9600) and SZ 3.0 (3600) subsystems, the
subscribers radios will not automatically roam between 3600 and 9600 sites. The user
will need to manually switch to an ASTRO 25 (9600) mode on the radio to operate
on the 9600 sites. Once switched to the new mode, radios will automatically roam
between ASTRO 25 sites in the system.
1.2.2.21
Subscribers
Subscribers and software upgrades are not included as part of this project.
1.2.2.22
T1 Paths
Net T1 Propagation Time
The "net" T1 propagation time difference between any two simulcast remote sites and
the "Prime" Controller site must be less than 5 milliseconds. For example, the
measured T1 propagation delay between the "Prime" Controller site and simulcast
remote site "A" could be 15 milliseconds and the measured propagation delay
between the "Prime" Controller site and simulcast remote site "B" could be 12
milliseconds. This would be a "net" T1 propagation time delay difference between
the two sites of 3 milliseconds.
Maximum T1 BER
The maximum T1 circuit BER (Bit Error Rate) required for proper operation of the
Motorola channel bank equipment is 10-7. For this reason, the loop protection switch
equipment must be set to cause a switch to take place at T1 BER of 10-7.
Clocking
All DS1 line rates must be traceable back to a primary reference source, i.e. a
common clocking standard.
The frame slip rate cannot exceed one frame slip per 14 days.
The clocking standard must have a fail-safe backup so that the system is not allowed
to go into a "free running" mode.
The clocking standard must have reverting capabilities such that if the primary clock
fails, then a backup clock will take over; however, when the primary clock has
returned to service, the system will revert back to the primary clock automatically.
DSX-1 Interconnection
The specifications on a DSX-1 interconnection shall be as follows:
Orange County
SmartX Core Migration Project, Phase I
Revised: September 30, 2010
18
Exhibit C-1 -System Description
Motorola Confidential Restricted
Use or disclosure of this proposal is
subject to the restrictions on the title page
Tolerance: Source timing for self-timed DS1 bit streams shall not exceed + / - 32 ppm
with respect to the basic rate. DS1 sinks should be capable of accepting a rate
deviation of + / - 130 ppm.
Line Code: B8ZS
Line Format: D4
Termination: One balanced twisted pair shall be used for each direction of
transmission.
Timing Jitter: Complies with BELLCORE specification TR-TSY-000499
ISSUE 2 DECEMBER 1988.
Four-wire Receiver Site Connections
The connections to the voting receiver sites require specifications on the order of
AT&T Type 3002 or Service Type 5 conditioned four-wire lines. The following is a
partial list of the Type 3002 specifications:
Insertion Loss @ 1 kHz: 16 Db
Loss Variation @ 1 kHz
Long-term: +/- 4 dB
Short-term: +/- 3 dB
Bandwidth:
2700 Hz (300-3000 Hz)
Frequency Response (ref. 1 kHz)
500-2500 Hz: loss, -2 to +8 dB
300-3000 Hz: loss, -2 to +12 dB
Delay Distortion
800-2600 Hz: 1750 microseconds
Max. Ave. Input Signal Level: 0 dBm at Network Interface
Max. Test Tone Level: 0 dBm at Network Interface
Frequency Shift: +/- 5 Hz
Phase Jitter:
less than 10 degrees
1.2.2.23
MOSCAD
MOSCAD continues to function as a standalone monitoring system and continues to
monitor the equipment at the 3600 sites. No changes will be made to the existing
MOSCAD system.
1.2.2.24
Future Expansion
The following equipment is not included in the current project. This section provides
a high level view of the equipment that will be required for expansion of capacity and
capability to serve the communications needs of all existing system members. This
section is not meant to replace the detailed design effort required to identify all
equipment and services necessary to expand the Master Site. That information will
be provided in a separate project.
♦
Site Infrastructure – The ASTRO 7.9 infrastructure is scalable and allows for the
addition of sites / subsystems as needed. All new site infrastructures to be
Motorola Confidential Restricted
Use or disclosure of this proposal is
subject to the restrictions on the title page
Orange County
SmartX Core Migration Project, Phase I
Revised: September 30, 2010
Exhibit C-1 -System Description
19
connected to the County’s P25 Master Site, including simulcast cells, stand alone
sites and conventional interface equipment are capable of being added by Orange
County.
♦
Dispatch Infrastructure – The 7.9 Master Site allows for the use of the new
MCC7500 dispatch architecture, which includes a desktop computer and routing
equipment. Additionally the 7.9 Master Site will support the use of the Motorola
Gold Equipment MGEG to connect the existing Gold Elite CEBs (connected to
the AEB). The County will have the ability to add MCC7500 dispatch positions,
licenses, dispatch switches / routers, and the interface routers / software to
connect future dispatch centers to the Master Site. There is only one MCC 7500
console dispatch position included in this proposal.
♦
High Performance Data (HPD) – The ASTRO 7.9 architecture being offered in
this design is inherently capable of providing High Performance Data (HPD)
services. When HPD service is required, the County will need to add the security
application, routers, licenses and site equipment needed to enable the feature.
♦
Integrated Voice and Data (IV& D) – The ASTRO 7.9 architecture being offered
in this project is inherently capable of providing Integrated Voice and Data
(IV&D) services. IV&D service is only available on ASTRO 25 RF sites.
♦
Unit ID Licenses – Additional unit ID licenses can be added for a combination of
Console / Subscriber IDs.
♦
Core routers and T1 routing – The 7.9 Master Site interfaces to the subsystem via
dedicated routers, Wan switch and a patch panel. Additional equipment will need
to be provided for each future site / subsystem that will be attached to the Master
Site.
♦
Subscribers – Subscriber equipment or upgrades have not been included in this
project. All subscribers must be capable and configured for ASTRO P25
Trunking (9600 control channel) to operate on future ASTRO 25 RF sites.
♦
Site preparation / Improvement – The County will need to make all necessary site
preparations needed to install all equipment including rack location, cable tray,
electrical power, grounding, and earthquake bracing. Motorola will work with
the County to identify these requirements.
Orange County
SmartX Core Migration Project, Phase I
Revised: September 30, 2010
20
Exhibit C-1 -System Description
Motorola Confidential Restricted
Use or disclosure of this proposal is
subject to the restrictions on the title page
1.3
Network and Fault Management Systems
1.3.1
Universal Event Manager
Unified Event Manager (UEM) is an application that provides reliable fault
management services for the ASTRO ® 25 Private Radio Systems.
The main functions of UEM are:
♦
♦
♦
♦
1.3.1.1
Discovery
Fault Management
Supervision
Synchronization
Overview
The Unified Event Manager (UEM) is a fault management application designed to
handle critical fault management functions such as processing fault notifications sent
by network elements, detecting and reporting loss of communication with managed
devices The UEM also provides management functions such as discovery of single or
all devices within a subsystem, ability to troubleshoot faults and send commands to
network elements.
The UEM presents the faults and, in general, the status of the network elements in
following four views:
♦
♦
♦
♦
Alarms View
Maps View
Network Events View
Network Database View
In essence, the UEM provides a central location for managing all radio, transport, and
environmental devices on the
system. The application
automatically discovers
Zone Maps > Physical > Summary View
devices on the network to
determine their real-time
status. Color-coded symbols
displayed on a topography
map provide a geographical
and hierarchical
representation of the entire
network. The UEM allows
each user to filter out and
customize the pertinent
information important to their roles and responsibilities.
Zone Maps
Physical
Detail View
Service
Features and benefits of the UEM are outlined in Table 0-4.
Motorola Confidential Restricted
Use or disclosure of this proposal is
subject to the restrictions on the title page
Orange County
SmartX Core Migration Project, Phase I
Revised: September 30, 2010
Exhibit C-1 -System Description
21
Table 0-4: Benefits of the UEM
Feature
Benefit
Centralized View of Entire
Communications Network
Network Managers can view the entire ASTRO 25 system
status and quickly isolate problems to the board level.
Intuitive Graphical User
Interface (GUI)
Network Managers can be quickly notified of failures on the
system and diagnose device problems, utilizing a display
and an intuitive GUI.
Auto Discovery of Devices
Components are automatically discovered and map views
are created to show the overall health of the network.
Active Alarms View and Alarm
Summary
Persistent single view all failure conditions in the network
and a quick reference summary of alarms by severity
allows users to quickly pinpoint the highest priority failures
Secure Device Access
SNMPv3 protocol with Triple DES and AES 256 bit
encryption to prevent security breach attempts
Northbound Interface
Real time event stream using a standard industry protocol
that can be used to forward events to a higher level
management application for added flexibility.
Email Notifications
User specified event notifications sent via email – which
could also be forwarded to a portable mobile device –
allows System Managers to simultaneously address other
tasks
Network Monitoring
Capabilities
Archive and export event history data for analysis
Remote Command Operation
Remote state change capability helps to avoid
unnecessary sites trips
The Unified Event Manager (UEM) gives the Network Manager virtually
instantaneous notification of any system deficiency or element failure.
UEM Event Browser
Figure 0-14 illustrates the UEM Event Browser screen.
Orange County
SmartX Core Migration Project, Phase I
Revised: September 30, 2010
22
Exhibit C-1 -System Description
Motorola Confidential Restricted
Use or disclosure of this proposal is
subject to the restrictions on the title page
Figure 0-14: UEM Event Browser Sample Screen.
The UEM event browser provides a way to look at all the events (or a filtered subset
of events) that are received by UEM. By default, when viewing an event, the event
browser displays Severity, Date / Time, Managed Resource, Entity, and Message.
Additional display properties are available. Up to 10,000 of the most recent events
from any managed device within a zone can be displayed.
UEM Alarm Browser
The UEM alarm browser (Figure 0-14) allows the user to view all alarms, or a
filtered subset of alarms. By default, when viewing an alarm, the alarm browser
displays Severity, Date / Time, Managed Resource, Entity, Message, and Owner /
Assignee information. Additional display properties are available. UEM supports
exporting events and alarms for future analysis.
Motorola Confidential Restricted
Use or disclosure of this proposal is
subject to the restrictions on the title page
Orange County
SmartX Core Migration Project, Phase I
Revised: September 30, 2010
Exhibit C-1 -System Description
23
Figure 0-15: UEM Alarm
Orange County
SmartX Core Migration Project, Phase I
Revised: September 30, 2010
24
Exhibit C-1 -System Description
Motorola Confidential Restricted
Use or disclosure of this proposal is
subject to the restrictions on the title page
1.4
Redundancy Analysis
The purpose of this section is to describe the multiple levels of redundancy inherent
to the system and the various fallback modes of operation, available to the users,
should a critical failure occur.
1.4.1
System Reliability Overview
A significant and material attribute of the system is how it performs during various
failure conditions. The ASTRO 7.9 system is designed with multiple levels of
redundancy and the ability to provide continued communications if a failure occurs.
Because the system is a lifeline to agency users and citizens; there is no tolerance for
system failure. The system can withstand multiple failures and still provide fullfeatured trunked communications. The following sections contain a comprehensive
analysis of the possible infrastructure failure scenarios, as well as a description of the
system redundancy built into the design, that helps mitigate some of these scenarios.
1.4.2
Failure of single MZC 5000 Zone Controller
The ASTRO 7.9 system includes fully redundant Zone Controllers (MZC5000)
located at the Orange County Loma Ridge equipment room.
Figure 0-16:
Motorola Confidential Restricted
Use or disclosure of this proposal is
subject to the restrictions on the title page
Orange County
SmartX Core Migration Project, Phase I
Revised: September 30, 2010
Exhibit C-1 -System Description
25
1.4.2.1
Failure Event Definition
In the event that the main Zone controller fails at Loma Ridge, it will result in
automatic switchover to the redundant Zone controller. The switchover to the
redundant Zone controller will take about 2 minutes for all sites to be back in Wide
Area Trunking. Between 45 seconds and 2 minutes, all Simulcast cells, A25 sites,
and console sites will return to Wide Area Trunking from the Site Trunking mode of
operation. Coverage for those cells, IR sites and A25 sites will not be degraded.
During the switchover period, the dispatchers will need to revert to the fallback
control stations to communicate with the users in the cells, IR sites or A25 sites that
are within the coverage area of the control stations.
1.4.2.2
Failure Event Detection and Notification
The ASTRO 7.9 system includes centralized fault management of the Master Site
equipment. When a fault is detected on the equipment located at the Master Site
including Zone controllers, support servers network equipment or terminals, the
Unified Event Manager (UEM) is notified of the fault and the user is provided with a
visual and audible alarm on the Network Management Client.
1.4.2.3
Failure Event Recovery
The ASTRO 7.9 system includes redundant Zone controllers. There is no failure
event recovery required for a failure of a single Zone controller, although it is
recommended that a technician is dispatched to the site where the failure occurred so
that appropriate measures can be taken to correct the failure. Once the failure is
corrected, the UEM will continue to show the alarm for a set period of time (default
is one hour). Following the set period of time the alarm will clear without user
intervention.
Orange County
SmartX Core Migration Project, Phase I
Revised: September 30, 2010
26
Exhibit C-1 -System Description
Motorola Confidential Restricted
Use or disclosure of this proposal is
subject to the restrictions on the title page
1.4.3
Failure of both MZC 5000 Zone Controllers
Figure 0-17:
1.4.3.1
Failure Event Definition
In the unlikely event that both the active and redundant Zone Controllers fail, the
simulcast cell sites will go into Site Trunking. During this time the dispatch operators
will revert to operating on Control Stations Wide area communications will be
restored once either one or both of the Zone Controllers are restored.
1.4.3.2
Failure Event Detection and Notification
When a fault is detected on the equipment located at the Master Site including Zone
controllers, support servers network equipment or terminals, the Unified Event
Manager (UEM) is notified of the fault and the user is provided with a visual and
audible alarm on the Network Management Client.
1.4.3.3
Failure Event Recovery
There is no failure event recovery required for this type of failure, although, it is
recommended that a technician is dispatched to the Master Site where the failure
occurred so that appropriate measures can be taken to correct the failure. Once the
failure is corrected, the UEM will continue to show the alarm for a set period of time
(default is one hour). Following the set period of time the alarm will clear without
user intervention.
Motorola Confidential Restricted
Use or disclosure of this proposal is
subject to the restrictions on the title page
Orange County
SmartX Core Migration Project, Phase I
Revised: September 30, 2010
Exhibit C-1 -System Description
27
1.4.4
Failure of ASTRO 7.9 Master Site Core Site Routers
The ASTRO 7.9 Master Site employs fully redundant Core routers. The Core routers
provided the WAN connection between the Master Site and the Prime Site, IR Site
(via SmartX interface) ASTRO25 sites and Dispatch centers.
1.4.4.1
Failure Event Definition
In the unlikely event that the main Core router fails, routing operations for the
affected Prime sites, IR sites and ASTRO25 sites, and console sites will be taken over
by the redundant core router. A user in the field that is on a call at the affected site /
cell / console site during the core router switchover will experience an audio gap in
their transmission that may last a few seconds. All other user groups and dispatch
console operators, that are not directly involved in a call with the affected site / cell /
console site, will remain unaffected by the core router switchover. The entire system
will remain in wide area communication mode.
1.4.4.2
Failure Event Detection and Notification
The ASTRO 7.9 system includes centralized fault management of the equipment at
the Master Site. When a fault is detected on the equipment located at the Master Site
including Zone controllers, support servers, network equipment or terminals, the
Unified Event Manager (UEM) is notified of the fault and the user is provided with a
visual and audible alarm on the Network Management Client.
1.4.4.3
Failure Event Recovery
The Master Site includes redundant Core site routers. There is no failure event
recovery required for this type of failure, although, it is recommended that a
technician is dispatched to take appropriate measures to correct the failure. Once the
failure is corrected, the UEM will continue to show the alarm for a set period of time
(default is one hour). Following the set period of time the alarm will clear without
user intervention.
Orange County
SmartX Core Migration Project, Phase I
Revised: September 30, 2010
28
Exhibit C-1 -System Description
Motorola Confidential Restricted
Use or disclosure of this proposal is
subject to the restrictions on the title page
1.4.5
Failure of both ASTRO 7.9 Master Site Core Site Routers
Figure 0-18:
1.4.5.1
Failure Event Definition
The Core Routers are configured so that they redundant. In the unlikely event that
both the main and redundant Core Routers at the active Master Site fail, will result in
the Simulcast cell reverting to Site Trunking. The dispatch operators will revert to
Control Station operation.
1.4.5.2
Failure Event Detection and Notification
The ASTRO 7.9 system includes centralized fault management of the equipment at
the Master Site. When a fault is detected on the equipment located at the Master Site
including Zone controllers, support servers, network equipment or terminals, the
Unified Event Manager (UEM) is notified of the fault and the user is provided with a
visual and audible alarm on the Network Management Client.
1.4.5.3
Failure Event Recovery
It is recommended that a technician is dispatched to take appropriate measures to
correct the failure by replacing the core router(s). Once the failure is corrected, the
UEM will continue to show the alarm for a set period of time (default is one hour).
Following the set period of time the alarm will clear without user intervention.
Motorola Confidential Restricted
Use or disclosure of this proposal is
subject to the restrictions on the title page
Orange County
SmartX Core Migration Project, Phase I
Revised: September 30, 2010
Exhibit C-1 -System Description
29
1.4.6
Failure of Master Site Enterprise Ethernet Switch
The ASTRO 7.9 Master Site includes dual LAN Ethernet switches. The dual Ethernet
switches provide redundant connections to the Zone controllers and Routers.
Figure 0-19:
1.4.6.1
Failure Event Definition
In the event that one of the Ethernet LAN switches should fail the redundant LAN
switch will continue to provide LAN switching services at the Master Site. The
redundant switch will continue to provide service to the Zone controller and routers.
In addition to providing the mentioned redundant services, the second LAN switch
will continue to provide LAN services only to those servers and terminals that are
connected to one of its Ethernet ports. Network Management Servers and terminals
that are instead connected to the failed LAN switches ports will not be available until
the switch is repaired. As such services provided by these devices will be unavailable
until switch has been restored. Data services associated to these devices will be out
for approximately 10 minutes since the data devices in the field need to context
activate onto the redundant Master Site. The user groups and dispatch console
operations that are associated to the non-failed switch will remain unaffected by the
LAN switch failure. The entire system will remain in wide area communication
mode.
Orange County
SmartX Core Migration Project, Phase I
Revised: September 30, 2010
30
Exhibit C-1 -System Description
Motorola Confidential Restricted
Use or disclosure of this proposal is
subject to the restrictions on the title page
1.4.6.2
Failure Event Detection and Notification
The ASTRO 7.9 system includes centralized fault management of all Master Site
equipment. When a fault is detected on the failed Ethernet Switch, the Unified Event
Manager (UEM) is notified of the fault and the user is provided with a visual and
audible alarm on the Network Management Client.
1.4.6.3
Failure Event Recovery
The Master Site includes dual Ethernet LAN switches. Therefore, the failure of a
LAN switch does not affect the field subscriber’s users and Dispatch operations that
are associated to the non-failed switch. Some system management services that are
associated to the failed switch may be interrupted and as such, it is recommended that
a technician is dispatched to take appropriate measures to correct the failure. Once
the failure is corrected, the UEM will continue to show the alarm for a set period of
time (default is one hour). Following the set period of time the alarm will clear
without user intervention. Once the failed switch has been repaired, the data field
devices will go back to operating conditions..
1.4.7
Failure of Both Master Site Enterprise Ethernet Switches
Figure 0-20:
Motorola Confidential Restricted
Use or disclosure of this proposal is
subject to the restrictions on the title page
Orange County
SmartX Core Migration Project, Phase I
Revised: September 30, 2010
Exhibit C-1 -System Description
31
1.4.7.1
Failure Event Definition
In the unlikely event that both Master Site Enterprise Switches fail at the Master Site,
the simulcast cell will go into Site Trunking. During the transition the dispatch
operators will revert to operating on Control Stations that can be selected from the
MCC 7500 console system. Restoration of the Master Site would require the
replacement of the defective Enterprise Switch components
1.4.7.2
Failure Event Detection and Notification
The ASTRO 7.9 system includes centralized fault management of all Master Site
equipment. When a fault is detected on the failed Ethernet Switches, the Unified
Event Manager (UEM) is notified of the fault and the user is provided with a visual
and audible alarm on the Network Management Client.
1.4.7.3
Failure Event Recovery
The Master Site includes dual Ethernet LAN switches. Therefore, the failure of a
LAN switch does not affect the field subscriber’s users and Dispatch operations that
are associated to the non-failed switch. Some system management services that are
associated to the failed switch may be interrupted and as such, it is recommended that
a technician is dispatched to take appropriate measures to correct the failure. Once
the failure is corrected, the UEM will continue to show the alarm for a set period of
time (default is one hour). Following the set period of time the alarm will clear
without user intervention. Once the failed switches have been repaired, the data field
devices will go back to operating conditions.
1.4.8
Voice Failure and Recovery Scenarios
The following sections describe the potential voice subsystem failures on the Orange
County simulcast subsystem, the detection and notification that is inherent to the
system design, and the recovery scenarios required to restore the voice subsystem to
normal operation.
1.4.9
Failure of Main Prime Site Controller at a Prime Site
The Orange County simulcast subsystem consists of redundant Simulcast Prime Site
Controllers (MTC 3600 and 6809) at various prime sites.
1.4.9.1
Failure Event Definition
In the event that the main Prime Site Controller fails, it will result in automatic
switchover to the redundant Prime site controller. The entire simulcast cell will
remain in wide area trunking. The failure will be transparent to all the system users.
Dispatch console operation will remain unaffected.
Orange County
SmartX Core Migration Project, Phase I
Revised: September 30, 2010
32
Exhibit C-1 -System Description
Motorola Confidential Restricted
Use or disclosure of this proposal is
subject to the restrictions on the title page
1.4.9.2
Failure Event Detection and Notification
The County system includes centralized fault management to all the Remote sites and
equipment. When a fault is detected on the main Prime Site Controller, the Unified
Event Manager (UEM) is notified of the fault and the user is provided with a visual
and audible alarm on the Network Management Client.
1.4.9.3
Failure Event Recovery
The Orange County system includes redundant Prime Site Controllers. Therefore, the
failure of the Main Prime Site Controller is transparent to the users. There is no
failure event recovery required for this type of failure, although it is recommended
that a County technician is dispatched to the Prime Site where the failure occurred so
that appropriate measures can be taken to correct the failure. Once the failure is
corrected, the UEM will continue to show the alarm for a set period of time (default
is one hour). Following the set period of time the alarm will clear without user
intervention.
1.4.10 Failure of Main and Redundant Simulcast Prime Site
Controller at a Prime Site
The Orange County simulcast subsystem consists of redundant Simulcast Prime Site
Controllers (MTC 3600) at various prime sites.
1.4.10.1
Failure Event Definition
In the unlikely event that both the Main Prime Simulcast Controllers fail, the cell will
revert to Simulcast Failsoft, where all transmitters’ sites operate in the conventional
simulcast mode. Coverage will not be degraded. Dispatchers will be able to
communicate to the simulcast cell via control stations or portable radios. A failsoft
word is sent from the USCI units to the Quantars, which in turn transmit the failsoft
word to the subscribers in the field. The failsoft word tells the subscribers to revert
from their talkgroups to the designated channels.
In failsoft the subscribers do not have the “always preferred” functionality. Instead,
the subscribers are constantly looking for a healthier cell and will automatically roam
once they see one.
1.4.10.2
Failure Event Detection and Notification
The County system includes centralized fault management to all the Remote sites and
equipment. When a fault is detected on the main Prime Site Controller, the Unified
Event Manager (UEM) is notified of the fault and the user is provided with a visual
and audible alarm on the Network Management Client.
Motorola Confidential Restricted
Use or disclosure of this proposal is
subject to the restrictions on the title page
Orange County
SmartX Core Migration Project, Phase I
Revised: September 30, 2010
Exhibit C-1 -System Description
33
1.4.10.3
Failure Event Recovery
The Orange County system includes redundant Prime Site Controllers. The failure of
the Main Prime Site Controller is transparent to the users. There is no failure event
recovery required for this type of failure, although it is recommended that a County
technician is dispatched to the Prime Site where the failure occurred so that
appropriate measures can be taken to correct the failure. Once the failure is corrected,
the UEM will continue to show the alarm for a set period of time (default is one
hour). Following the set period of time the alarm will clear without user intervention.
1.4.11 Master Site Network Management Servers
The ASTRO 7.9 system contains Network Management servers at the Orange County
Master Site. Each of these servers performs different duties or carries different data.
The failure of one of these servers will affect these duties and data streams, but the
ability of the system to communicate with field users will not be affected.
Failure Event Definition
The following table describes the effects of the failure of a server.
Table 0-5
Server
User
Configuration
Server
Failure Effect





Zone Database
Server


Prevents the UCS database restore / replication process from
occurring.
User information cannot be edited
System-level parameters cannot be changed with the User
Configuration Management (UCM) application.
The ability of the system to process calls is not affected since the
zone controllers can utilize the information stored internally to
handle call processing during this type of failure.
Results in the loss of some fault management functionality; zone
configuration management.
The ability of the system to process calls is not affected since the
zone controllers can utilize the information stored internally to
handle call processing during this type of failure.
Orange County
SmartX Core Migration Project, Phase I
Revised: September 30, 2010
34
Exhibit C-1 -System Description
Motorola Confidential Restricted
Use or disclosure of this proposal is
subject to the restrictions on the title page
Server
Zone Statistical
Server
Failure Effect



Prevents the viewing of zone-wide historical and statistics.
The ATR buffers eight hours of data.
- If the ZSS recovers in this time, then no low level statistical
information will be lost.
- If the ZSS recovery takes more than eight hours, only the last
eight hours of data will be available.
The ability of the system to process calls is not affected since the
zone controllers can utilize the information stored internally to
handle call processing during this type of failure.
Air Traffic Router



Unified Event
Manager


The ATIA packet data and zone statistics will not be available.
Devices that depend on the ATIA stream are affected. Zone
statistics uploads to the ZSS are interrupted. Consolidation of zone
and system statistics is delayed until either the ATR recovers, or
eight hours elapse.
The ability of the system to process calls is not affected since the
zone controllers can utilize the information stored internally to
handle call processing during this type of failure.
Results in the loss of UEM fault / network management
functionality for the zone.
The ability of the system to process calls is not affected since the
zone controllers can utilize the information stored internally to
handle call processing during this type of failure.
Failure Event Detection and Notification
The ASTRO 7.9 system includes centralized fault management of all Master Site
equipment. When a fault is detected on the servers, the Unified Event Manager
(UEM) is notified of the fault and the technician is provided with a visual and audible
alarm on the Network Management Client. In the event that the UEM server
experiences a fault, the UEM application will not be operational on the Network
Management Terminal.
Failure Event Recovery
The Master Site includes Network Management Servers. The failure of a Network
Management Server will not affect dispatch operations, but is considered a major
failure. System management services that are associated to the failed server will be
interrupted and as such, it is imperative that a technician is dispatched to take
appropriate measures to correct the failure. Once the failure is corrected and the
device is working, the UEM will replace the alarm with a “Clear” event. The clear
event will remain visible for one hour at which time it will be removed from the
alarm screen without further user intervention.
Motorola Confidential Restricted
Use or disclosure of this proposal is
subject to the restrictions on the title page
Orange County
SmartX Core Migration Project, Phase I
Revised: September 30, 2010
Exhibit C-1 -System Description
35
1.4.12 Master Site CENTRACOM Button and LED Consoles
The Orange County simulcast subsystem consists of a CENTRACOM subsystem that
supports five dispatch buttons and LEDs (B&L) positions at the Loma Ridge
Dispatch Center and twenty-three modified B&L positions that support remote
dispatch centers.
Motorola no longer supports the hardware or certifies the operation of the buttons and
LEDs CENTRACOM dispatch equipment on a 7.9 ASTRO 25 network core.
Motorola configured and tested one position of B&L dispatch equipment on the
Interagency Communication Interoperability System (ICIS) SmartX system. The
B&L equipment passed all basic functionality tests.
As part of the SmartX project Motorola will interface these twenty-eight positions
into the 7.9 ASTRO 25 network. Orange County is responsible for the operation,
repair and maintenance of these twenty-eight positions. Motorola can not guarantee
or support these positions on the 7.9 ASTRO 25 network. The hardware is no longer
available or serviced by Motorola.
Failure Event Scenario: If any of these B&L Master Control Panels fail, the remote
dispatch center will continue to operate via local control stations tied to their local
CEB and Console Priority will be lost.
♦
♦
Fallback 1: Continue to operate via control stations without Console Priority
operation.
Fallback 2: Consolidate CEBs and remote operator positions / agencies
interfaced to the AEB. This option is to combine the smaller dispatch centers
(e.g. Placentia PD - 3 ops merge onto one CEB with La Palma PD - one op) to
free up ports on the AEB. Once AEB ports are available, these combined CEBs
can be integrated directly into the network (providing Console Priority) via the
AEB and MGEG equipment.
Failure Event Recovery: Orange County technical personnel are responsible to
replace the failed hardware with spare equipment.
Motorola’s solution will be to option cost and replace the B&L positions with MCC
7500 dispatch equipment.
1.4.13 Genesis
Motorola has worked with Genesis engineering and confirmed that the equipment and
software provided in this proposal will be sufficient for Genesis to continue to
support Orange County once the current SmartZone 3.0 system is migrated to the 7.9
platform.
It is the County’s responsibility to integrate existing Genesis system into the ASTRO
7.9 Master Site.
Orange County
SmartX Core Migration Project, Phase I
Revised: September 30, 2010
36
Exhibit C-1 -System Description
Motorola Confidential Restricted
Use or disclosure of this proposal is
subject to the restrictions on the title page
1.4.14 Network Management Remote Access
The ASTRO 7.9 system is designed to enable Orange County to have remote access
to the ASTRO 25 Master Site equipment for management, configuration, diagnostics,
and troubleshooting purposes. It also provides the hardware to allow Motorola’s
System Support Center to gain access to the system remotely when the County
requests the service.
The Juniper firewall SSG family of products is used to provide the Virtual Private
Network (VPN) remote access. The VPN firewall is intended to support internet
connectivity for the maintenance and service technician (Customer) through a VPN
Client. Once the VPN Client is connected, the service technician can access the
Network Management Client remotely.
The diagram below illustrates VPN connectivity to remotely gain access to the
Motorola Radio Network Infrastructure.
Figure 0-21:
Motorola Confidential Restricted
Use or disclosure of this proposal is
subject to the restrictions on the title page
Orange County
SmartX Core Migration Project, Phase I
Revised: September 30, 2010
Exhibit C-1 -System Description
37