STARCOM21 Rebanding Overview
June 7th, 2007
STARCOM21 NETWORK
Agenda
• Project Status
• Rebanding Discussion
STARCOM21 NETWORK
STARCOM21 Network
ASTRO 25 Digital 700/800 MHz Trunking

Dedicated to IL Governmental Users






Built to Public Safety Standards





Voice Encryption Capable
Local Console Connectivity
State Wide Coverage and Roaming
APCO Level Six Interoperability
Fully Managed Communications
3 Zones - 197 Sites
Hardened, Secure, Monitored
Maintained and Staffed 24 x 7 x 365
Guaranteed Service Level Agreements
95% Area Mobile Coverage Statewide

In Building (8 dB) Coverage in Select Areas
(Chicago Area, 12 Major Cities)
Final System Acceptance Q307
PROJECT ORGANIZATION
Rich O’Herron
Project Director
Implementation
Support
Lance Weil
Project Manager
Mike Greenaway
Business Dev. Mgr.
Larry Ferden
ST, Team Leader
Doug Phelps
Network Mgr.
Fred Hilgenberg
ST
Sue Warren
Contract Mgr.
Brian Wasielewski
Engineering Mgr.
Marge Ponga
CSM
Vanessa Morrissette
System Engineer
Gaurav Doshi
System Engineer
STARCOM21 NETWORK
Craig Solberg
Technical Supp. Mgr.
MSO Technicians
Sue, Rob, Keith
Implementation
• Last Site To Complete Is Beloit
– Waiting on Tower Issues To Be Resolved
– Tollway Working With Tower Construction Vendor
• Harlem Irving Site Will Be Moved To The New Tower
Later in 2007
• Des Plaines Site Will Move From the Trailer Into the
Final Location Once EDACS Is Removed In Q3
STARCOM21 NETWORK
Completed Milestones
• Successfully completed the DAQ and BER testing Oct 12, 2006
with a 99% pass rate
• Implemented and Optimized 187 RF sites with 3 Master sites
across 3 Zones
• Successfully turned up 240 T1 circuits and 45 DS3 circuits to
provide the backhaul for the system
• Dispatch Centers installed and accepted during the same time
period
• Implemented MOSCAD for environmental alarms at each site
and tested with Starcom Full vision
• State Deployment Started in April
STARCOM21 NETWORK
Conditional Acceptance
• Original Contract language Did Not Accommodate
Partial System Acceptance
• Contract Amendment Agreed to In March
• Allows for Phased Rollout
• A Win/Win for State and Motorola
• Allows Orderly Rollout and Operational Testing
• Facilitates the Chicago Migration
STARCOM21 NETWORK
Starcom Deployment
• First ISP District Went Live March 28
• ISP Deploying South to North
– Coordinated With User Training and Radio Installation
– Roll Out Was on Portable Only Initially
• Two More Districts Cut Over in April
• Stopped Deployment in Late April Due to ISPERN
Patch Issues
• District Cutovers Will Start Back Up With Accelerated
Schedule
• Still Anticipate Completion of ISP Cutover on Original
Date of August
• State has started Installation of Mobiles in Zone 3
– Includes Futurecom VRS units
• Motorola has programmed all 4000+ ISP subscribers
with the 244 templates approved by ISP
STARCOM21 NETWORK
Customer ID Loading
Total ID’s loaded – 16,200 / 270 Man Hour Effort
•
•
•
•
•
•
•
•
ISP Mobiles/Portables – 4267
ISP Consoles - 5540
ITTF – 2269
St Clair – 2885
McLean – 740
Argonne – 68
Madison – 220
Other (Wabash, Lee, etc.) – 222
STARCOM21 NETWORK
Fleet Maps
Extensive Amount of Effort has Gone into Programming
All State of Illinois Templates have 29 Personalities and 21 Zones
Completed
7000+ Radios and 342 Templates
ISP Subscriber Units (Finished)
320 Templates (ISP keeps adding new templates)
4800 radios programmed (2 ½ times)
700 Futurecom Vehicle Repeaters (2 times)
ITTF (Finished)
2 Templates, 1800 radios
Argonne Labs
6 Templates, 55 radios (Finished)
Madison County
6 Templates, 200 radios
Ogle County
4 Templates, 60 radios
Lee County
2 Templates, 30 radios
Plainfield
2 Templates, 56 radios
STARCOM21 NETWORK
In progress
950+ Radios and 141+ Templates
Secretary of State (2/3 Finished)
44 Templates. 300 radios, 150 Futurecom Repeaters
Interstate Commerce Commission (Templates Done)
42 Templates, ~100 radios
Department of Natural Resources (Not Done)
42 Templates, ~200 radios
IEMA (Not Done)
2 Templates, ~20 radios
Executive Office of the Inspector General (Not Done)
1 Template, 30 radios
McHenry County
~10 Templates, ~300 radios
Will need to be done this year to make their timeline
Current User Community
Argonne Laboratory
Belvidere PD/FD
Boone County
Champaign Urbana Public Health
DuPage County Water Comm.
Glen Carbon
ITTF - ILEAS, MABAS, IESMA
IMERT
Lee County
Madison County
McLean County
McHenry County
Ogle County
St. Clair County
Wabash County E911
STARCOM21 NETWORK
Interested Parties
Ameren
Bond County
Cook County
City of Chicago
Metropolitan Pier Authority
Chicago - Organized Crime Division
Davenport IA
Edwardsville
FBI Southern Region
Henry County
Macon County/Decatur
Prairie Shield
Rock Island / Quad Cities Region
SIU-Edwardsville
Springfield/ Sangamon County
STARCOM21 NETWORK
System Upgrade
• Network successfully upgraded from 6.5 to 7.1 in April
• Only minor issues and no noticeable or reported customer
interruptions of service
• Cutover to new MSO’s was completed under 90 minutes
• UO Pre-staged And Configured Master Site Equipment
• Extensive Planning mitigated Down Time And End User
Impact
• Elite Console Upgrade ordered and Planned for June to
take consoles to 7.2
• Next Planned Upgrade is 7.4 In Late Q1 Or Early Q2 2008
STARCOM21 NETWORK
ISPERN Patch: The Problem
• Contract Calls for a Patch for VHF ISPERN to Starcom TG’s in all ISP District
• Every ISP Dist Has its Own Starcom TG to localize Impact on Starcom21 Network
• ISP ISPERN is Carrier squelch and the Dispatcher Bases are 100W at 300 ft
• When the Patch is Activated from the Starcom21 side, the Bases are Also Activated
• The Base Stations (because of Height, Power, and Carrier Squelch)
Activate the ISPERN Patches in all Surrounding Districts
• This Means that Each District has to Carry the ISPERN Traffic for Itself
and Every Surrounding District (Multiplies ISPERN traffic impact)
• Starcom21 Sites That are on the Border of 2 or More Districts Have to
Carry the ISPERN Talkgroups of all of the Surrounding Districts
• There is not Enough Channel Capacity to Handle 3, 4, or 5 ISPERN
Talkgroups Simultaneously, on a Single Site
• The End Result is Sites Bordering Multiple Districts are Busied Out and
Normal ISP Dispatch Traffic is Blocked
STARCOM21 NETWORK
ISPERN Patch: Initial Solution
• We Attempted to Use the Radio’s Scanning Function to Fix the Problem
• We limited each district’s ISPERN Talkgroup footprint to those sites
entirely within the district which eliminated the need for border sites
to carry multiple ISPERN Talkgroups. (This did not, however, stop
sites from having to carry the ISPERN traffic of surrounding districts)
• We had the mobiles and portables programmed to scan the ISPERN
Talkgroups of surrounding districts. (Required for the troopers to
render assistance to neighboring districts)
• We were depending on the VHF ISPERN RF to activate adjacent district
ISPERN patches
• In practice, the Troopers Found the Scanning Solution Unacceptable
• They Were Missing ISPERN Calls
• Found That Listening on Scan & Talking on In-District ISPERN Confusing
• After 3 Districts Were Deployed, the ISP Rejected This Solution
STARCOM21 NETWORK
ISPERN Patch: Current Status
• Prototype hardware was installed on the CEB, 3 voting
Receivers, and 4 Transmitters in District 9
• 15 St Technicians assisted in the installation as a training
& Solution evaluation exercise & Have embraced the solution
• Installation and level setting went relatively smooth
• Initial testing was very positive
• The CEB was able to tell the difference between a Base
and a Mobile and patch accordingly
• Operation of the CEB patch appeared stable
• We have ordered enough hardware to convert the entire
Starcom21 system (Delivery is expected in 1 week)
STARCOM21 NETWORK
ISPERN RX #1
PL
Decoder
ISPERN Patch
Only Activates
For Mobiles or
Portables
CEB Patches
ISPERN Based
On External Input
3KHz
Tone
Gen
Motorola Supplied
Audio to
ISP Apps
Audio
without
3KHz
Tone
CEB
ISPERN RX #2
Best
Receive Audio
Selected
PL
Decoder
3KHz
Tone
Gen
Motorola
or
GE
Voter
Motorola Supplied
ISPERN RX #3
3KHz
Notch
Filter
VOX
3KHz Tone
Detect
Audio + 3KHz =
No Relay Closure
Audio Only =
Relay Closure
Motorola Supplied Detector
PL
Decoder
ISPERN
Receiver
Voting is Not
Affected by
3KHz Tone
3KHz
Tone
Gen
Motorola Supplied
Base TX
With PL
ISPERN RX #4
PL Tone
Decoder Taps
RX Audio
PL Tone
Uniquely
Identifies Base
Transmissions
PL
Decoder
3KHz
Tone
Gen
Motorola Supplied
3KHz Tone
Mixed with
Receiver Audio
Receiver
Audio
3KHz Tone
At 10 dB
Below RX Audio
This solution uses a PL tone, that is
Not heard by users, to TAG Base Station
Transmissions. The PL Tone is converted
To 3KHz in order to pass through phone lines.
At the CEB, if the audio contains a 3KHz
Tone, the CEB does not activate the patch.
This solution has absolutely no effect
On the patching of Mobiles and Portables.
3KHz Tone
Is Activated When
PL Tone is Detected
Proposed Solution to Block Powerful Base Stations from Affecting Patches in Adjacent Districts
STARCOM21 NETWORK
Rebanding
Rebanding Background
• Interference has Been a Serious Problem for 800 MHz
Public Safety and Critical Infrastructure
Communications
• FCC Spent 2 1/2 Years Studying Problem with 10’s of
Thousands of Pages of Comments
• Report and Order was Designed to Reduce PS
Interference
• If You are Impacted, it is Mandatory--You Can’t get out of
It
• All Costs are Covered
• Disruption to Operations Will be Minimal
STARCOM21 NETWORK
High Level View of Motorola
Rebanding Process
TA
and/or
Nextel
Action
Customer
and
Motorola
Action
Customer
Presents
Quote to
Quote
Initial
Customer
Contact/
Call
Tools
 Check List
First
Customer
Meeting
Customer &
Motorola
Notified
Customer &
Motorola
Notified
Motorola
Develops and
Delivers Quote to
Quote
Tools
 Check List
 Rebanding
Inventory Tool
 Process / Facts
Presentation
TA & Nextel
• Final Audit
• True-up of
costs
Approval of
Rebanding
Quote
Approval of
Quote to
Quote
TA Notifies
Licensee
TA & Nextel
Notified
Customer
Presents
Rebanding
Quote
Quote developed
and delivered to
Reband Customer
System
Implementation
of Rebanding
for customer
system
Tools
 Rebanding Inventory
Tool
 Quoting Tool
 MOPS /Test Processes /
SOWS
Subject to revision as TA provides guidelines
Customer
Acceptance
Tools
 Rebanding
Inventory Tool
 Change Order
Process
 Test Processes
809
Move
FCC’s Final Plan
700 MHz
Public
Safety
Band
NPSPAC
Public
Safety
230 Ch.
6 MHz
851
Interleaved spectrum
80 SMR, 50 Business,
50 Industrial
70 Public Safety
250 Ch. 12.5 MHz
Public Safety,
Hi Site SMR, Bus,
Industrial
280 Ch. 14 MHz
854
821
*No public safety system will be required to
remain in or relocate to the expansion band;
although they may do so if they choose
STARCOM21 NETWORK
824
Move
860 861
NPSPAC
Public
Safety
230 Ch.
6 MHz
ESMR Block
200 Channels
10 MHz
Guard Band**
General
Category
150 Channels
7.5 MHz
817
Stay
Expansion Band*
Current Channel Plan
700 MHz
Public
Safety
Band
815 816
854.7375
806
809.7375
800 MHz Band Plan Before and After
862
Cellular Like ESMR Block
280 Channels
14 MHz
866
Cellular
A&B
Cellular
A&B
869
**No public safety or (Critical Infrastructure &
Industry) CII licensee may be involuntarily
relocated to occupy the Guard Band.
Transition Administrator (TA)—Bearing Point Team
Selected by committee comprised of: APCO, UTC, ITA,
SouthernLinc, and Nextel
Organization:
Bearing Point for overall management
Squire-Sanders & Dempsey, LLP for legal
Baseline Telecom for technical
STARCOM21 NETWORK
General Responsibilities of the TA
• Collect Estimates From Licensees on System
Rebanding Costs
• Assign Replacement Frequencies
• Resolve Disputes Between Nextel and
Licensees on Cost Estimates
• Authorize Transfer of Funds
• Coordinate Relocation of NPSPAC Channels
with Regional Planning Committees
• Monitor Retuning Schedule and Resolve Delays
• Facilitate Resolution of Disputes by Mediation
• Establish Relocation Schedule by Prioritizing
Regions
STARCOM21 NETWORK
The Regional Wave Plan
• Established by Transition Administrator on Jan 31
– Accepted by FCC on March 11th
• Regions are Grouped into Four "Waves"
• Negotiation and Reconfiguration Periods Across the
Waves will Overlap
• Formal Start Date Notices Will be Issued for Each
Region so Timelines are Clear
• Channel 1-120 Band Gets Minimum of 9 Months to
Retune
• NPSPAC Gets Minimum of 15 months
• NPSPAC Negotiations in Each Region Start as Soon as
1-120 is Sufficiently Complete
STARCOM21 NETWORK
Regional Prioritization
Wave 1 Start Date 6/27/05
Wave 2 Start Date 10/3/05
Wave 3 Start Date 1/3/06
Wave 4 Start Date 4/3/06 (Tentative)
NPSPAC planning
starts 6 months after
1-120 planning
Southeast ESMR
Bandplan Area
STARCOM21 NETWORK
Retune/Reprogram/Update/Replace Definitions
• Retune: Updating the channel frequencies via the
Customer Programming Software/Radio Service
Software programming software
• Reprogram: Updating operating software via
software FLASH with new frequencies & band plan
• Update: One or more boards must be replaced in the
equipment to enable retuning or reprogramming
• Replace: Cannot be updated to support new
frequencies or band plans
STARCOM21 NETWORK
Rebanding Software Summary
• New Channel Assignment Required to Move NPSPAC to Lower Part
of Band
– Channel Spacing in 806-809 changes with new band plan
– Channel number to frequency translation must change
– Control channel list has been increased to allow old and new
assignments
– Failsoft channel list has been increased to allow old and new
assignments
• New Plan Allows Radios to Work on Either Upgraded or Not
Upgraded Site
– Simplifies rebanding migration process
– Minimizes disruption to Licensees
– Greatly reduces infrastructure costs and overlay requirements
• Reduces number of duplicate systems needed
– Enables system-wide mobility throughout customer migration
Current as of March 21, 2005
STARCOM21 NETWORK
Band Plan Migration
Site 1
Old Plan
New Plan (Includes Old Plan)
Site 2
Step 1 – Update Mobile with New Plan (Includes Old Plan)
STARCOM21 NETWORK
Band Plan Migration
Site 1
Old Plan
New Plan (Includes Old Plan)
Site 2
Step 1 – Update Mobile with New Plan (Includes Old Plan)
Step 2 – Update Site 1 with New Plan
STARCOM21 NETWORK
Band Plan Migration
Site 1
Old Plan
New Plan (Includes Old Plan)
Site 2
Step 1 – Update Mobile with New Plan (Includes Old Plan)
Step 2 – Update Site 1 with New Plan
Step 3 – Update Site 2 with New Plan
STARCOM21 NETWORK
SOI Rebanding
• Rebanding Proposal Effort is Under Way With
Anticipated Delivery of the FRA in June
• Rebanding will Include Approx. 9,000
Subscribers and Approx. 768 Base Stations
• Expected to Take Approx. 12 Months
• All Subscribers Must be Complete Prior to
Infrastructure
• Coordination Will be Required for all
Participating Agencies
STARCOM21 NETWORK
Example of Rebanding Timeline
STARCOM21 NETWORK
STARCOM21 Rebanding
Rebanding Process Scope
– Subscribers
•
•
•
•
Update templates
Flashing
Reprogram
Retune
– Infrastructure
• Reprogram
• Retune
STARCOM21 NETWORK
Initial Inventory Information Needed
Subscribers
– Mobiles – Model Family
•
•
Quantity
Department
– Portables – Model Family
•
•
Quantity
Department
– Control Stations – Model Family
•
•
Quantity
Location
STARCOM21 NETWORK
STARCOM21 Subscriber Process
Plan Is To Do One District at a Time in Each Zone
– Teams Working in Each Zone Simultaneously
• State Agency Subscribers Done at ISP District HQ (ISP,
OEIG, SOS, etc.)
• Other None State Agencies to be Done at Local MSS
Locations (ICC, ITTF, etc.)
• Counties with Large Quantities Would be Done at
County Facilities During the Week
– Teams Would be in a District for 1 Week on Average
– Each Agency is Responsible for Getting their Radios in
for Rebanding
– Once the Subscribers are Completed the Infrastructure
(FNE) Would be Done
• FNE is Rebanded by District
STARCOM21 NETWORK
Customer Responsibilities
• Review all submitted rebanding templates for accuracy
and approve if correct
• Scheduling with end users to coordinate availability of
the radios to be rebanded
• Provide access to the customer facility when the
rebanding effort is being done at customer location
• Provide folding tables and chairs for work area
• Provide master documentation of the number of radios
the customer has so that each radio can be verified by
Motorola and the customer that it has been completed
STARCOM21 NETWORK
Motorola Responsibilities
•
Motorola will provide technicians and other personnel to perform the
following tasks:
– Modify and test the existing templates to allow the rebanded radios to be
programmed with the rebanding templates.
•
Provide rebanding templates to customers to follow the same approval
process as has been done for all template approvals
•
Rebanding of the radios at the ISP District and local MSS shop locations,
this will include reflashing, reprogramming, retuning, and testing.
•
Provide all necessary programming materials and equipment (cables, flash
kits, software, computers, power supplies, etc.)
•
•
Assist with the documentation of the completed radios
Mark each radio in some fashion (e.g. put a colored sticker on the radio) to
designate it has been flashed/reprogrammed for rebanding
•
Coordinate and schedule the Motorola and subcontractor technicians
STARCOM21 NETWORK
First Steps
• Motorola will update subscriber templates with the data for rebanding
as the first step
• No changes will be made to any template other than those changes
required for rebanding!
• Each customer will need to signoff on their updated templates
• Once Templates are approved reprogramming can begin
STARCOM21 NETWORK
User Impact
•
Flash upgrading times vary
– Portable usually about 15 minutes
– Mobiles can take up to 40 minutes
 If your radios have been identified as needing flashing, it will take this extra
time to reband the radio
 Radios with a DSP/Host version of 7.0 or newer do not need to be flashed! ( If
the radio shipped from Motorola after January 2006 it should be ok)
•
Each radio will need to be reprogrammed!
•
The process is as follows:
–
–
–
–
–
Motorola will test the radio on the system before reprogramming
Program the radio
Retest the radio on the system
Total time for portables should be about 15-20 minutes
Total time for mobiles should be between 20-25 minutes
• Mobiles can vary due to inaccessibility to the radio in the trunk
STARCOM21 NETWORK
Infrastructure Rebanding
•
Motorola’s proposed plan would be to reband all 3 zones simultaneously
and realistically won’t start until later in 07 or early 08 depending on the time
it takes the TA and Sprint to approve the FRA
– SOI wants to have the system run for 30 days before any changes are made
after final acceptance
•
Subscribers will be done first by teams consisting of MSS/Motorola Techs
•
– State radios (ISP, SOS, OEIG, etc.) will be done at the ISP district HQ in
each district
– ITTF, ICC, and other regional users will be done at the local shop locations
in each region
– Rebanded Subscribers will work on both old and new frequencies
FNE will be done by Motorola ST’s
•
DOC is being treated as a separate project
– 4068 subscribers at 13 different locations
– Each location has a Smart Net System
•
St Clair and McLean County are separate rebanding projects
– McLean can’t go until Starcom Rebands
STARCOM21 NETWORK
User Impact
• Each FNE site will take approximately 4 hours
– Worst case scenario is site will be off the air for a couple of hours
– Motorola is working on a process to limit down time & retune the site while live
• Pre-Validate Site is Functioning
• Measure and record TX power and Rx BER
• Perform Talkgroup call on site
– Reprogram new frequencies into stations
– Retune Combiners
– Revalidate site is functioning
•
•
• Measure and record TX power and RX BER
• Perform Talkgroup call on site
Simulcast Sites will take longer as each remote site needs to be done
simultaneously
Site Channel capacity during rebanding
– During the rebanding of each site there will be a diminished channel capacity
as each channel is done
– Has the potential to cause high busy quest at the site
STARCOM21 NETWORK
Potential Issues
– Motorola needs to understand each users
operational process
– Coordination must take place between users
and Rebanding team
– Radios not done before the FNE is done
may have trouble functioning on some sites
– Interference on New Frequencies
– Logistics and Scheduling
– Unexpected Hardware Failures
STARCOM21 NETWORK
ITTF Challenges
• Agencies are spread out, many rural
• Units may have been redeployed within each
group
• Unified Command Vehicles/ ITECS trailers
• Portable radios assignment/locations required
(i.e., SRT Teams)
• Communication method & distribution is key
STARCOM21 NETWORK
STARCOM21 Rebanding - ITTF Agencies
Current SummaryILEAS XTL5000 Control Stations
XTL5000 Mobiles
XTL5000 Consolette
XTS5000 Portables
MABAS XTL5000 Control Stations
XTL5000 Mobiles
XTS5000 Portables
IESMA XTL5000 Control Stations
XTL5000 Mobiles
Total STARCOM21 NETWORK
- 376
- 384
- 43
- 460
- 333
- 346
- 12
- 100
- 195
2249
Information Sharing and Sources
Transition Administrator
www.800ta.org
Motorola’s Public Website
www.motorola.com/800rebanding
Specific 800 MHz Rebanding Questions
RebandQs@motorola.com
STARCOM21 NETWORK
Questions?
Contacts:
Craig Solberg (Rebanding Manager) – 612-490-7641 Craig.Solberg@Motorola.com
Lance Weil (Project Manager) - 618-687-2233 Lance.Weil@Motorola.com
Dave Fagersten – 847-576-6110 Dave.Fagersten@Motorola.com